Oracle EBS

Below are the queries to get the error records information while processing interface data. AP Invoices:   SELECT    airl.last_update_date process_date,    HU.NAME,   nvl(ail.invoice_line_id,aii.invoice_id) process_id,   'AP' module,   'Import AP Invoice' interface_name,   aii.source source,   NVL(SUBSTR( ail.dist_code_concatenated,1,instr(ail.dist_code_concatenated,'.',1,1)-1),'ALL') company,   'ERROR' status,   ail.line_type_lookup_code ,   airl.parent_table ,   ail.description ,   NVL(ail.distribution_set_name,dist_code_concatenated) ,   pvsa.vendor_site_code ,   listagg(NVL(airl.reject_lookup_code,'AP_INV_ERROR') ,';') within group (order by NVL(airl.reject_lookup_code,'AP_INV_ERROR')) error_code,   listagg(flv.meaning,';')  within group (order by NVL(flv.meaning,'AP_INV_ERROR'))error_summary,   NULL error_details,   pv.vendor_name ,   pv.segment1 ,   aii.invoice_amount,   aii.i

I would like to share my experience on developing the reports which output should print on the preformed stationary using the dot matrix printers. If we have to print the output on dot matrix printer it would be better if we should generate the report which  gives the output in normal plain text format. We can generate the text output reports either by using oracle RDF reports or XSL-FO text output bi publisher report. Before starting the development  we need to ensure the below points. we should have the exact hard copy of stationary (or photo copy of it) on which data should print. If we get photo copy then it should have the same dimensions like length and width of the original stationary. Has to fix or load the stationary in dot matrix printer as per the printer guidelines always.  Identify the number of lines should feed for each copy of the print so that we can make sure in the report should generate same number of lines for each copy. Identify for each section of inf

PO Print PDF Report: Oracle EBS provided  a standard functionality to print the PO report directly from the PO form itself by clicking tools menu and view PDF option. Once we select that option output will be rendered in PDF format in the browser instantly. Internally it will run the concurrent program 'PO Output For Communication'. This concurrent program is of JAVA type which will uses the seeded package  'PO_COMMUNICATION_PVT'  for generating the XML data and later this XML data will be processed and formatted by using the XSL template of data definition 'Standard Purchase Order Data Source' in case of standard PO's. Oracle by default will provide one standard BI publisher template for this. In case if we want to have custom layout for this report we can build a new template for the same data definition and this template has to be used while doing the setup for PO Document types. Creating Custom Template and Setup this for PO Document type: To c

RDF Reports FAQ: DATA TRIGGERS: Ref Cursor Query.  This uses PL/SQL to fetch data for the report. In this a PL/SQL function need to be specified to return a cursor value from a cursor variable. Group Filter:  This is PL/SQL function that determines which record to be included in a group in the property of PL/SQL.  The function must return a BOOLEAN value. True … Includes the current record in the report. False…. Excludes the current record from the report. Formula  These are PL/SQL functions that populate formula or place holder columns. Validation Trigger    These are also PL/SQL functions that are executed when parameter values specified on the command line and when the run time parameter form is accepted.  Are also used to validate the initial value property of the parameter. Layout Triggers Format Trigger. These are PL/SQL functions executed before the object is formatted. Used to dynamically change the formatting attributes of the object