How to display the OA Framework Page attachment image stored in FND_LOBS table in the BI Publisher report output

 Problem: 

The attachments in the form images that are uploaded from OA Framework Pages will be stored in FND_LOBS tables, How to display these images in the BI Publisher report output.

Solution: 

Step 1: First we need to identify the record in fnd_lobs table .

        select FILE_ID,FILE_NAME ,FILE_DATA    from fnd_lobs where file_id = 695482.

        The file_data column actually contains the image content.

Step 2: Now the data that is stored in file_data column of fnd_lobs table is of type BLOB and we cannot display the BLOB data type directly in BI Publisher reports and we need to convert them to CLOB.

Step 3: create function to convert blob to clob

CREATE OR REPLACE FUNCTION APPS.BLOB_CLOB_TEST(p_source BLOB)
RETURN CLOB IS v_result CLOB;
BEGIN 

DBMS_LOB.createtemporary(lob_loc=>v_result,CACHE=>FALSE,dur=>0);
Wf_Mail_Util.EncodeBLOB(p_source,v_result);
RETURN (V_RESULT);
END BLOB_CLOB_TEST; 

Step 4: Use this function in the below SQL query to get the CLOB data type for column file_data.

            select FILE_ID,FILE_NAME ,BLOB_CLOB_TEST(FILE_DATA) IMAGE_FILE

    from fnd_lobs where file_id = 695482

Step 5: Use the query written in Step 4 in BI Publisher data xml.

Step 6: Display the element IMAGE_FILE in the RTF with below syntax in the field.

        <fo:instream-foreign-object content-type="image/jpg" height="1.25 in" width="1.5                 in">  <xsl:value-of select=".//IMAGE_FILE"/>  

Step 7: Run BI Publisher program and the output will show the image.

Concurrent program end in ERROR with "Program was terminated by signal 11'

  Issue: The concurrent program ends in error and the error message in the log file is "

Program was terminated by signal 11"

Cause of the Issues: This issue is occurred mostly in custom programs or the core programs.

custom programs: The reason for the error in custom programs is if you are calling core API's or submitting the core standard concurrent programs and those programs are upgraded to include additional parameters and if you are not including those parameters in your package or program then you get the error.

Core/Standard Programs: The reason for the error in standard programs is, if you have upgraded only the core programs and not packages, then either the program or the package which is not addressing the additional parameters exists then you get this error.

Solution: Identify the backend programs/packages or scripts which are calling with missing parameters added during changes or upgrade by Oracle and then add those parameters and retest the issue. The issue should be resolved.

Query to find the Operating Unit Name for the Journal Ledger created in Oracle Apps General Ledger

 Below is the query which gives details about legal entity name, ledger name and operating unit name 

SELECT * FROM XLE_LE_OU_LEDGER_V where ledger_id in (select ledger_id from gl_je_headers where name ='Journal Name' and description like 'Journal%Import%230808858%')