How to find OPP Log information for a specific XML Publisher request

When a concurrent request for an Xml Publisher concurrent Request ends up with a Warning.
If you have system administrator access you can access the Output Post Processor Log using the Concurrent -- Manager Menu. If you don't have access to System Administrator Responsibility, using the following query you can get the location of the log that's stored on the application server.
From the Log:
+------------- 1) PUBLISH -------------+ 
Beginning post-processing of request 19280863 on node SERVER at 15-MAY-2014 13:39:18. Post-processing of request 192808 failed at 15-MAY-2014 13:39:18 with the error message: One or more post-processing actions failed. Consult the OPP service log for details. 

The actual error returned by the XML Publisher Core engine is captured in the OPP log file.
One of the easiest way to obtain the OPP log file is to run the below script from the database by providing request_id.

SELECT fcpp.concurrent_request_id req_id, fcp.node_name, fcp.logfile_name
FROM fnd_conc_pp_actions fcpp, fnd_concurrent_processes fcp
WHERE fcpp.processor_id = fcp.concurrent_process_id
AND fcpp.action_type = 6
AND fcpp.concurrent_request_id = &request_id;


The log file name would have the path.



If you have System Administrator then


 1) System Administrator > Concurrent > Manager > Administer
 2) Search for 'Output Post Processor'
 3) Click the 'Processes' button
 4) Click the Manager Log button. This will open the 'OPP'
 
 

Comments

Post a Comment

Popular posts from this blog

Create attachments and attach them to Sales Order Header or Order Lines

Use the API below to create the attachment. This could be a limited text that you want on the order header or line. OE_FND_ATTACHMENTS_PUB.CREATE_SHORT_TEXT_DOCUMENT (1.0, --version P_SHORT_TEXT, --Text to be added as attachment P_CATEGORY_ID, -- Attachment category id P_DESCRIPTION, -- Attachment description NULL, V_SECURITY_ID, --The value is 4 for no security NULL, 'Y', 'O', -- One time usage SYSDATE, NULL, NULL, V_DOCUMENT_ID , -- Document id returned by the API V_RETURN_STATUS_CS, V_MSG_COUNT_CS, V_MSG_DATA_CS); Pass V_DOCUMENT_ID from above API into below second API OE_FND_ATTACHMENTS_PUB.ADD_ATTACHMENT (1.0, P_ENTITY_NAME, --Value of this parameter would be 'OE_ORDER_HEADERS' for header level attachment -- and 'OE_ORDER_LINES' for line level attachment P_PK1_VALUE, --line id or header id (For line level or header level attachment) NULL, NULL, NULL, NULL, 'N', NULL, V_DOCUMENT_ID , --Document id from above ap...
Read more

Link XLA Tables With AR Tables To Get Information From GL

There is   no one-to-one mapping between AR, XLA and GL. The data that actually posts to the GL is the XLA table data, not AR. Depending on the AAD rules you have defined, one row that appears in AR could become 10 in XLA_DISTRIBUTION_LINKS, but when the data is posted into the GL, the accounts of the same type and ccid are merged to a single entry. For example, a transaction could have 34 gl_dist rows, but 201 rows in ar_distribution_links, but when it actually posts, consolidates to 9 rows in gl_import_references. The main link to bind information together is the gl_sl_link_id. It will show in the gl_je_lines, gl_import_refernces and xla_ae_lines table. Also, the XLA_DISTRIBUTION_LINKS table contains the application_id, event_id, ae_header_id, ae_line_num from the XLA Tables and source_distribution_id_num_1 will be the cust_trx_line_gl_dist_id in the case of a transaction. ACTION: COMPLETE TRANSACTION : RA_CUSTOMER_TRX_ALL.CUSTOMER_TRX_ID = RA_CUST_TRX_LINE_GL_DIST_ALL.CUS...
Read more