PO Output for Communication Report

What is PO Output for Communication? 

PO Output for Communication usually called as PO Print Report is one of the most important and standard report in Purchasing to communicate Purchase order information to supplier through an email in the format of PDF or text.

How to run PO Output for Communication report? 

1.This reports gets triggered as soon as a PO is approved. An email is sent to the supplier with PO information as an attachment and a copy of email is sent to the email address configured in the profile option “PO: Secondary Email address” as a backup.

2. We can also view this report output by opening an Approved Purchase Order and then navigating to “Inquire –> View Document” through menu option.

3.We can also run “PO Output for Communication” manually as a concurrent request.

How does PO Output for Communication report work? 

PO Output for Communication is a Java concurrent program which is triggered through a PO Approval workflow. This java program generates XML data whose XSD(XML Schema Definition) is defined as XML Publisher Data definition and output layout is defined in XSL-FO format as a template in XML Publisher.

Data Definition Name: Standard Purchase Order Data Source

Template Name: Standard Purchase Order Stylesheet

PO Approval workflow uses standard package “PO_COMMUNICATION_PVT.POXMLGEN” to generate XML Data. The XML data generated contains all the columns of the below SQL views

 PO_HEADERS_XML

PO_LINES_XML

PO_LINE_LOCATIONS_XML

PO_DISTRIBUTION_XML

 PO_PRICE_ADJUSTMENTS_XML

PO_RELEASE_XML

How to create a custom layout for PO Output for Communication report?

 To customize the layout of this report one must make a copy of seeded XSLFO stylesheet and modify it. But modifying XSLFO is not that easy as many of us dont know XSLFO markup language. The other way is to create traditional rtf layout. Below are the steps to apply rtf layout for this report.

Navigate to Purchasing Super user responsibility –> Setup –> Organizations –> Purchasing Options under Document Control section set value for “PO Output Format” field as PDF


Query to find if the Purchase Order information is sent to Supplier through email or not

SELECT   segment1,

           approved_date,

           supplier_notif_method,

           polc.displayed_field po_status,

           print_count,

           printed_date,

           from_user,

           to_user,

           STATUS,

           mail_status,

           original_recipient

    FROM   po_headers_all poh, wf_notifications wn, po_lookup_codes polc

   WHERE       1 = 1

           AND polc.lookup_type(+) = 'AUTHORIZATION STATUS'

           AND poh.authorization_status = polc.lookup_code(+)

           AND wn.user_key(+) = poh.segment1

           AND wn.item_key(+) = poh.wf_item_key

           AND supplier_notif_method = 'EMAIL'

           AND NVL (edi_processed_flag, 'N') <> 'Y'

           AND NVL (xml_flag, 'N') <> 'Y'

           AND message_name(+) = 'AME_EMAIL_PO'

           AND displayed_field = 'Approved'

ORDER BY   poh.po_header_id DESC;

 

What is PO Output for Communication? PO Output for Communication usually called as PO Print Report is one of the most important and standard report in Purchasing to communicate Purchase order information to supplier through an email in the format of PDF or text. How to run PO Output for Communication report? This reports gets triggered as soon as a PO is approved. An email is sent to the supplier with PO information as an attachment and a copy of email is sent to the email address configured in the profile option “PO: Secondary Email address” as a backup. We can also view this report output by opening an Approved Purchase Order and then navigating to “Inquire –> View Document” through menu option. We can also run “PO Output for Communication” manually as a concurrent request. How does PO Output for Communication report work? PO Output for Communication is a Java concurrent program which is triggered through a PO Approval workflow. This java program generates XML data whose XSD(XML Schema Definition) is defined as XML Publisher Data definition and output layout is defined in XSL-FO format as a template in XML Publisher. Data Definition Name: Standard Purchase Order Data Source Template Name: Standard Purchase Order Stylesheet PO Approval workflow uses standard package “PO_COMMUNICATION_PVT.POXMLGEN” to generate XML Data. The XML data generated contains all the columns of the below SQL views PO_HEADERS_XML PO_LINES_XML PO_LINE_LOCATIONS_XML PO_DISTRIBUTION_XML PO_PRICE_ADJUSTMENTS_XML PO_RELEASE_XML How to create a custom layout for PO Output for Communication report? To customize the layout of this report one must make a copy of seeded XSLFO stylesheet and modify it. But modifying XSLFO is not that easy as many of us dont know XSLFO markup language. The other way is to create traditional rtf layout. Below are the steps to apply rtf layout for this report. Navigate to Purchasing Super user responsibility –> Setup –> Organizations –> Purchasing Options under Document Control section set value for “PO Output Format” field as PDF

Read more at: http://oracleappsdna.com/2015/04/faqs-of-po-output-for-communication-report/
Copyright © www.OracleAppsDNA.com

Do you want to meet your fellow Oracle Apps Consultants ?? then join us @ Facebook Home About Me: Shailender Thallam Contact Oracle Apps Interview Questions Ask a Question Home » Purchasing, XMLP FAQs on PO Output for Communication Report 19 April 2015 3,897 views 10 Comments Article by Shailender Thallam Here is a summary of what I have learnt of PO Output for Communication report on my recent engagement. What is PO Output for Communication? PO Output for Communication usually called as PO Print Report is one of the most important and standard report in Purchasing to communicate Purchase order information to supplier through an email in the format of PDF or text. How to run PO Output for Communication report? This reports gets triggered as soon as a PO is approved. An email is sent to the supplier with PO information as an attachment and a copy of email is sent to the email address configured in the profile option “PO: Secondary Email address” as a backup. We can also view this report output by opening an Approved Purchase Order and then navigating to “Inquire –> View Document” through menu option. We can also run “PO Output for Communication” manually as a concurrent request. How does PO Output for Communication report work? PO Output for Communication is a Java concurrent program which is triggered through a PO Approval workflow. This java program generates XML data whose XSD(XML Schema Definition) is defined as XML Publisher Data definition and output layout is defined in XSL-FO format as a template in XML Publisher. Data Definition Name: Standard Purchase Order Data Source Template Name: Standard Purchase Order Stylesheet PO Approval workflow uses standard package “PO_COMMUNICATION_PVT.POXMLGEN” to generate XML Data. The XML data generated contains all the columns of the below SQL views PO_HEADERS_XML PO_LINES_XML PO_LINE_LOCATIONS_XML PO_DISTRIBUTION_XML PO_PRICE_ADJUSTMENTS_XML PO_RELEASE_XML How to create a custom layout for PO Output for Communication report? To customize the layout of this report one must make a copy of seeded XSLFO stylesheet and modify it. But modifying XSLFO is not that easy as many of us dont know XSLFO markup language. The other way is to create traditional rtf layout. Below are the steps to apply rtf layout for this report. Navigate to Purchasing Super user responsibility –> Setup –> Organizations –> Purchasing Options under Document Control section set value for “PO Output Format” field as PDF 1.PO Output for Communication - Purchasing Options Create a custom rtf layout “XX Test PO Print” with data source as “Standard Purchase Order Data Source” Note: Application of template should be “Purchasing” not the custom application 3.PO Output for Communication -New Template Navigate to Purchasing Super user responsibility –> Setup –> Purchasing –> Document Types Find for document type “Purchase Order Standard” and update it with “XX Test PO Print” rtf layout as “Document Type Layout”. 4.PO Output for Communication - Document Types 2.PO Output for Communication - Document Types 5.PO Output for Communication - Document Types 6.PO Output for Communication - Document Types How to see XML tags generated by PO Output for Communication report? Usually we can see data in XML format in diagnostics form but for this report “View XML” option will be disabled. 7.PO Output for Communication - View XML Disabled To get the XML data we need to run the report with parameter “Test” value as “Debug” which generates a log file with XML Data along with some debug information. We need to save log file and remove content apart from XML Data and save the file with .xml as extension which can be used for rtf layout development. 8.PO Output for Communication - Parameters Note: To reflect the changes made on rtf layout, we need to run the report on the newly approved PO. Or to run the report for already approved PO run the concurrent program “PO Output for Communication” with ‘Regenerate Document‘ parameter as ‘Yes’. How to add additional columns to PO Output for Communication Report? As a seeded functionality we can add only the fields which are generated by seeded package “PO_COMMUNICATION_PVT.POXMLGEN” which lists all the columns of below SQL Views: PO_HEADERS_XML PO_LINES_XML PO_LINE_LOCATIONS_XML PO_DISTRIBUTIONS_XML To add any additional field, we need to customize “PO_COMMUNICATION_PVT.POXMLGEN” package as well as POAPPR workflow, but this is very herculean task which involves lot of effort and it is not upward compatible, means the customizations may go away on applying patches. The easiest way is to populate the additional values in attributes of underlying tables of above views, so that we can easily reference them in rtf layout without any customization. Query to find if the Purchase Order information is sent to Supplier through email or not SELECT segment1, approved_date, supplier_notif_method, polc.displayed_field po_status, print_count, printed_date, from_user, to_user, STATUS, mail_status, original_recipient FROM po_headers_all poh, wf_notifications wn,po_lookup_codes polc WHERE 1=1 AND polc.lookup_type(+)= 'AUTHORIZATION STATUS' AND poh.authorization_status = polc.lookup_code(+) AND wn.user_key(+) = poh.segment1 AND wn.item_key(+) = poh.wf_item_key AND supplier_notif_method = 'EMAIL' AND NVL (edi_processed_flag, 'N') <> 'Y' AND NVL(xml_flag,'N') <> 'Y' AND message_name(+) = 'AME_EMAIL_PO' AND displayed_field='Approved' ORDER BY poh.po_header_id DESC; If mail_status is MAIL, it means the email delivery is pending for workflow mailer to send the notification. If mail_status is SENT, its means mailer has sent email If mail_status is NULL & status is NULL or OPEN, its means that no need to send email as notification preference of user is “Don’t send email” or the Workflow mailer is not Up and Running Note: XML tag names are changed in R12 when compared with 11i For Further Reading How to Display Leading Zeros in XMLP Report – Excel Output XML Publisher Interview Questions with Answers Drop Shipment Functional Process and Technical Information PL/SQL Script to Generate XML Tags for XMLP Report FAQs on Oracle Alerts WOW! Did you like this post? We'll send more interesting posts like FAQs on PO Output for Communication Report to you! Enter your Email Address: Recent Posts from this Category Printing Dynamic Signatures on PO Output for Communication Report Different Headers and Footers for Different pages of XMLP Layout FAQs on PO Output for Communication Report XML Publisher Interview Questions with Answers SQL Query to find Status of GL and PO Accounting Periods Developing XML Publisher Reports using Data Template XMLP Error While Previewing RTF: Java execution failed. Please check the Java Option in the option dialog. XMLP: Error No. 53 while Previewing/Validating the report How to Display Leading Zeros in XMLP Report - Excel Output PL/SQL Script to Generate XML Tags for XMLP Report STAY CONNECTED Subscribe FREE updates on your Email | RSS COPYRIGHT This work is licensed under a Creative Commons-NonCommercial 2.5 License. Tags back to back order Business Events concurrent manager Cost Manager Diagnostics dropshipment Errbuf FNDLOAD FNDLOAD download FNDLOAD upload FND_DEVELOPER_MODE FND_DEVELOPER_MODE in routine fnd_request.submit_request How to port reports from one instance to another HRMS Profile Options hz_locations iStore items not available ldt files Line Status Flow MOAC Move Transaction Manager Pending Resource Transactions personalization pl/sql procedures porting reports profileoption Profile options Reports Retcode Sales Order line Status Flow Ship Confirm button greyed Shipping Transactions form table suffix WIP_COST_TXN_INTERFACE _A _ACN _ALL _AVN _B _F _S _TL _V _VL Categories Alerts (2) AOL and SYSADMIN (33) AOL SQL Scripts (22) APIs (3) Business Events (3) Costing (1) Custom PLL (1) Data Conversions/Interfaces (2) Extensions (1) General Ledger (2) HRMS (4) Interview Questions (8) Inventory (7) iRecruitment (1) iStore (1) OAF (8) OPM (4) Oracle Apps Basics (18) Oracle Learning Management (4) Oracle SQL (17) Order Management (13) Payables (3) Payments (3) Personalizations (4) PL/SQL (14) Profile Options (5) Purchasing (5) Receivables (7) Reports (2) Scripts (7) Security (1) Shipping Execution (2) Uncategorized (1) Unix / Shell Scripts (1) WIP Jobs (1) Workflows (16) XMLP (12) Recent Posts How to set ORG_ID for MOAC Enabled Concurrent Programs while Submitting from Backend A killer “Auto Refresh” option on Concurrent Request Window – New Features to Concurrent Request Form Attaching Concurrent Program Output as Workflow Email Notification Attachment XML Data for Positive Pay XML Data of AP Check Payments – Format Payments Instructions in R12 Customizing Oracle Payments XML extract to include Custom XML Tags Payables Interface Tables Oracle Sales Orders Interface/Conversion General Ledger Interface Tables SQL Query to Convert Comma separated String values to Rows Most Viewed MD50, MD70 and MD120 Templates – Free Download - 19,271 views [Decrypting User Password]How to find password of a User in Oracle Apps R12? - 18,557 views XML Publisher Interview Questions with Answers - 16,358 views Useful Information about Workflow Background Process Concurrent Program - 14,061 views PL/SQL Script to Submit a Concurrent Request from backend - 13,738 views Top PL/SQL Interview Questions with Answers - 13,304 views Information about Oracle APIs and How to find APIs of Oracle Modules? - 12,653 views Purpose of Formula column, Summary column and Place Holder column in Oracle Reports - 12,442 views How costing is performed on Inventory Material Transactions - 12,288 views SQL Query to list Active Responsibilities of a Active User - 12,138 views Recent Comments Recent Comments Chanakya Kolapalli Super article Shailender, thank you! FAQs on PO Output for Communication Report · 2 days ago Passion 4 Oracle nice . General Ledger Interface Tables · 1 week ago Shailender Thallam It is used to return error message to concurrent manager. Information on Errbuf and Retcode Parameters · 3 months ago Naveen Hi Shailender, Is there any specific reason to use errbuf as first parameter. Information on Errbuf and Retcode Parameters · 3 months ago OracleAppsDNA © 2014 OracleAppsDNA. Opinions expressed here are strictly those of the owner, Shailender Thallam, and those of the commenters. Articles cannot be reproduced without permission from the author. AddThis Sharing Sidebar Share to Facebook , Number of shares Share to Google+ Share to LinkedIn , Number of shares Share to Twitter Share to Email Share to PDFmyURL Share to StumbleUpon

Read more at: http://oracleappsdna.com/2015/04/faqs-of-po-output-for-communication-report/
Copyright © www.OracleAppsDNA.com

FAQs on PO Output for Communication Report 19 April 2015 3,897 views 10 Comments Article by Shailender Thallam Here is a summary of what I have learnt of PO Output for Communication report on my recent engagement. What is PO Output for Communication? PO Output for Communication usually called as PO Print Report is one of the most important and standard report in Purchasing to communicate Purchase order information to supplier through an email in the format of PDF or text. How to run PO Output for Communication report? This reports gets triggered as soon as a PO is approved. An email is sent to the supplier with PO information as an attachment and a copy of email is sent to the email address configured in the profile option “PO: Secondary Email address” as a backup. We can also view this report output by opening an Approved Purchase Order and then navigating to “Inquire –> View Document” through menu option. We can also run “PO Output for Communication” manually as a concurrent request. How does PO Output for Communication report work? PO Output for Communication is a Java concurrent program which is triggered through a PO Approval workflow. This java program generates XML data whose XSD(XML Schema Definition) is defined as XML Publisher Data definition and output layout is defined in XSL-FO format as a template in XML Publisher. Data Definition Name: Standard Purchase Order Data Source Template Name: Standard Purchase Order Stylesheet PO Approval workflow uses standard package “PO_COMMUNICATION_PVT.POXMLGEN” to generate XML Data. The XML data generated contains all the columns of the below SQL views PO_HEADERS_XML PO_LINES_XML PO_LINE_LOCATIONS_XML PO_DISTRIBUTION_XML PO_PRICE_ADJUSTMENTS_XML PO_RELEASE_XML How to create a custom layout for PO Output for Communication report? To customize the layout of this report one must make a copy of seeded XSLFO stylesheet and modify it. But modifying XSLFO is not that easy as many of us dont know XSLFO markup language. The other way is to create traditional rtf layout. Below are the steps to apply rtf layout for this report. Navigate to Purchasing Super user responsibility –> Setup –> Organizations –> Purchasing Options under Document Control section set value for “PO Output Format” field as PDF 1.PO Output for Communication - Purchasing Options Create a custom rtf layout “XX Test PO Print” with data source as “Standard Purchase Order Data Source” Note: Application of template should be “Purchasing” not the custom application 3.PO Output for Communication -New Template Navigate to Purchasing Super user responsibility –> Setup –> Purchasing –> Document Types Find for document type “Purchase Order Standard” and update it with “XX Test PO Print” rtf layout as “Document Type Layout”. 4.PO Output for Communication - Document Types 2.PO Output for Communication - Document Types 5.PO Output for Communication - Document Types 6.PO Output for Communication - Document Types How to see XML tags generated by PO Output for Communication report? Usually we can see data in XML format in diagnostics form but for this report “View XML” option will be disabled. 7.PO Output for Communication - View XML Disabled To get the XML data we need to run the report with parameter “Test” value as “Debug” which generates a log file with XML Data along with some debug information. We need to save log file and remove content apart from XML Data and save the file with .xml as extension which can be used for rtf layout development. 8.PO Output for Communication - Parameters Note: To reflect the changes made on rtf layout, we need to run the report on the newly approved PO. Or to run the report for already approved PO run the concurrent program “PO Output for Communication” with ‘Regenerate Document‘ parameter as ‘Yes’. How to add additional columns to PO Output for Communication Report? As a seeded functionality we can add only the fields which are generated by seeded package “PO_COMMUNICATION_PVT.POXMLGEN” which lists all the columns of below SQL Views: PO_HEADERS_XML PO_LINES_XML PO_LINE_LOCATIONS_XML PO_DISTRIBUTIONS_XML To add any additional field, we need to customize “PO_COMMUNICATION_PVT.POXMLGEN” package as well as POAPPR workflow, but this is very herculean task which involves lot of effort and it is not upward compatible, means the customizations may go away on applying patches. The easiest way is to populate the additional values in attributes of underlying tables of above views, so that we can easily reference them in rtf layout without any customization. Query to find if the Purchase Order information is sent to Supplier through email or not SELECT segment1, approved_date, supplier_notif_method, polc.displayed_field po_status, print_count, printed_date, from_user, to_user, STATUS, mail_status, original_recipient FROM po_headers_all poh, wf_notifications wn,po_lookup_codes polc WHERE 1=1 AND polc.lookup_type(+)= 'AUTHORIZATION STATUS' AND poh.authorization_status = polc.lookup_code(+) AND wn.user_key(+) = poh.segment1 AND wn.item_key(+) = poh.wf_item_key AND supplier_notif_method = 'EMAIL' AND NVL (edi_processed_flag, 'N') <> 'Y' AND NVL(xml_flag,'N') <> 'Y' AND message_name(+) = 'AME_EMAIL_PO' AND displayed_field='Approved' ORDER BY poh.po_header_id DESC; If mail_status is MAIL, it means the email delivery is pending for workflow mailer to send the notification. If mail_status is SENT, its means mailer has sent email If mail_status is NULL & status is NULL or OPEN, its means that no need to send email as notification preference of user is “Don’t send email” or the Workflow mailer is not Up and Running Note: XML tag names are changed in R12 when compared with 11i

Read more at: http://oracleappsdna.com/2015/04/faqs-of-po-output-for-communication-report/
Copyright © www.OracleAppsDNA.com

FAQs on PO Output for Communication Report 19 April 2015 3,897 views 10 Comments Article by Shailender Thallam Here is a summary of what I have learnt of PO Output for Communication report on my recent engagement. What is PO Output for Communication? PO Output for Communication usually called as PO Print Report is one of the most important and standard report in Purchasing to communicate Purchase order information to supplier through an email in the format of PDF or text. How to run PO Output for Communication report? This reports gets triggered as soon as a PO is approved. An email is sent to the supplier with PO information as an attachment and a copy of email is sent to the email address configured in the profile option “PO: Secondary Email address” as a backup. We can also view this report output by opening an Approved Purchase Order and then navigating to “Inquire –> View Document” through menu option. We can also run “PO Output for Communication” manually as a concurrent request. How does PO Output for Communication report work? PO Output for Communication is a Java concurrent program which is triggered through a PO Approval workflow. This java program generates XML data whose XSD(XML Schema Definition) is defined as XML Publisher Data definition and output layout is defined in XSL-FO format as a template in XML Publisher. Data Definition Name: Standard Purchase Order Data Source Template Name: Standard Purchase Order Stylesheet PO Approval workflow uses standard package “PO_COMMUNICATION_PVT.POXMLGEN” to generate XML Data. The XML data generated contains all the columns of the below SQL views PO_HEADERS_XML PO_LINES_XML PO_LINE_LOCATIONS_XML PO_DISTRIBUTION_XML PO_PRICE_ADJUSTMENTS_XML PO_RELEASE_XML How to create a custom layout for PO Output for Communication report? To customize the layout of this report one must make a copy of seeded XSLFO stylesheet and modify it. But modifying XSLFO is not that easy as many of us dont know XSLFO markup language. The other way is to create traditional rtf layout. Below are the steps to apply rtf layout for this report. Navigate to Purchasing Super user responsibility –> Setup –> Organizations –> Purchasing Options under Document Control section set value for “PO Output Format” field as PDF 1.PO Output for Communication - Purchasing Options Create a custom rtf layout “XX Test PO Print” with data source as “Standard Purchase Order Data Source” Note: Application of template should be “Purchasing” not the custom application 3.PO Output for Communication -New Template Navigate to Purchasing Super user responsibility –> Setup –> Purchasing –> Document Types Find for document type “Purchase Order Standard” and update it with “XX Test PO Print” rtf layout as “Document Type Layout”. 4.PO Output for Communication - Document Types 2.PO Output for Communication - Document Types 5.PO Output for Communication - Document Types 6.PO Output for Communication - Document Types How to see XML tags generated by PO Output for Communication report? Usually we can see data in XML format in diagnostics form but for this report “View XML” option will be disabled. 7.PO Output for Communication - View XML Disabled To get the XML data we need to run the report with parameter “Test” value as “Debug” which generates a log file with XML Data along with some debug information. We need to save log file and remove content apart from XML Data and save the file with .xml as extension which can be used for rtf layout development. 8.PO Output for Communication - Parameters Note: To reflect the changes made on rtf layout, we need to run the report on the newly approved PO. Or to run the report for already approved PO run the concurrent program “PO Output for Communication” with ‘Regenerate Document‘ parameter as ‘Yes’. How to add additional columns to PO Output for Communication Report? As a seeded functionality we can add only the fields which are generated by seeded package “PO_COMMUNICATION_PVT.POXMLGEN” which lists all the columns of below SQL Views: PO_HEADERS_XML PO_LINES_XML PO_LINE_LOCATIONS_XML PO_DISTRIBUTIONS_XML To add any additional field, we need to customize “PO_COMMUNICATION_PVT.POXMLGEN” package as well as POAPPR workflow, but this is very herculean task which involves lot of effort and it is not upward compatible, means the customizations may go away on applying patches. The easiest way is to populate the additional values in attributes of underlying tables of above views, so that we can easily reference them in rtf layout without any customization. Query to find if the Purchase Order information is sent to Supplier through email or not SELECT segment1, approved_date, supplier_notif_method, polc.displayed_field po_status, print_count, printed_date, from_user, to_user, STATUS, mail_status, original_recipient FROM po_headers_all poh, wf_notifications wn,po_lookup_codes polc WHERE 1=1 AND polc.lookup_type(+)= 'AUTHORIZATION STATUS' AND poh.authorization_status = polc.lookup_code(+) AND wn.user_key(+) = poh.segment1 AND wn.item_key(+) = poh.wf_item_key AND supplier_notif_method = 'EMAIL' AND NVL (edi_processed_flag, 'N') <> 'Y' AND NVL(xml_flag,'N') <> 'Y' AND message_name(+) = 'AME_EMAIL_PO' AND displayed_field='Approved' ORDER BY poh.po_header_id DESC; If mail_status is MAIL, it means the email delivery is pending for workflow mailer to send the notification. If mail_status is SENT, its means mailer has sent email If mail_status is NULL & status is NULL or OPEN, its means that no need to send email as notification preference of user is “Don’t send email” or the Workflow mailer is not Up and Running Note: XML tag names are changed in R12 when compared with 11i

Read more at: http://oracleappsdna.com/2015/04/faqs-of-po-output-for-communication-report/
Copyright © www.OracleAppsDNA.com

FAQs on PO Output for Communication Report 19 April 2015 3,897 views 10 Comments Article by Shailender Thallam Here is a summary of what I have learnt of PO Output for Communication report on my recent engagement. What is PO Output for Communication? PO Output for Communication usually called as PO Print Report is one of the most important and standard report in Purchasing to communicate Purchase order information to supplier through an email in the format of PDF or text. How to run PO Output for Communication report? This reports gets triggered as soon as a PO is approved. An email is sent to the supplier with PO information as an attachment and a copy of email is sent to the email address configured in the profile option “PO: Secondary Email address” as a backup. We can also view this report output by opening an Approved Purchase Order and then navigating to “Inquire –> View Document” through menu option. We can also run “PO Output for Communication” manually as a concurrent request. How does PO Output for Communication report work? PO Output for Communication is a Java concurrent program which is triggered through a PO Approval workflow. This java program generates XML data whose XSD(XML Schema Definition) is defined as XML Publisher Data definition and output layout is defined in XSL-FO format as a template in XML Publisher. Data Definition Name: Standard Purchase Order Data Source Template Name: Standard Purchase Order Stylesheet PO Approval workflow uses standard package “PO_COMMUNICATION_PVT.POXMLGEN” to generate XML Data. The XML data generated contains all the columns of the below SQL views PO_HEADERS_XML PO_LINES_XML PO_LINE_LOCATIONS_XML PO_DISTRIBUTION_XML PO_PRICE_ADJUSTMENTS_XML PO_RELEASE_XML How to create a custom layout for PO Output for Communication report? To customize the layout of this report one must make a copy of seeded XSLFO stylesheet and modify it. But modifying XSLFO is not that easy as many of us dont know XSLFO markup language. The other way is to create traditional rtf layout. Below are the steps to apply rtf layout for this report. Navigate to Purchasing Super user responsibility –> Setup –> Organizations –> Purchasing Options under Document Control section set value for “PO Output Format” field as PDF 1.PO Output for Communication - Purchasing Options Create a custom rtf layout “XX Test PO Print” with data source as “Standard Purchase Order Data Source” Note: Application of template should be “Purchasing” not the custom application 3.PO Output for Communication -New Template Navigate to Purchasing Super user responsibility –> Setup –> Purchasing –> Document Types Find for document type “Purchase Order Standard” and update it with “XX Test PO Print” rtf layout as “Document Type Layout”. 4.PO Output for Communication - Document Types 2.PO Output for Communication - Document Types 5.PO Output for Communication - Document Types 6.PO Output for Communication - Document Types How to see XML tags generated by PO Output for Communication report? Usually we can see data in XML format in diagnostics form but for this report “View XML” option will be disabled. 7.PO Output for Communication - View XML Disabled To get the XML data we need to run the report with parameter “Test” value as “Debug” which generates a log file with XML Data along with some debug information. We need to save log file and remove content apart from XML Data and save the file with .xml as extension which can be used for rtf layout development. 8.PO Output for Communication - Parameters Note: To reflect the changes made on rtf layout, we need to run the report on the newly approved PO. Or to run the report for already approved PO run the concurrent program “PO Output for Communication” with ‘Regenerate Document‘ parameter as ‘Yes’. How to add additional columns to PO Output for Communication Report? As a seeded functionality we can add only the fields which are generated by seeded package “PO_COMMUNICATION_PVT.POXMLGEN” which lists all the columns of below SQL Views: PO_HEADERS_XML PO_LINES_XML PO_LINE_LOCATIONS_XML PO_DISTRIBUTIONS_XML To add any additional field, we need to customize “PO_COMMUNICATION_PVT.POXMLGEN” package as well as POAPPR workflow, but this is very herculean task which involves lot of effort and it is not upward compatible, means the customizations may go away on applying patches. The easiest way is to populate the additional values in attributes of underlying tables of above views, so that we can easily reference them in rtf layout without any customization. Query to find if the Purchase Order information is sent to Supplier through email or not SELECT segment1, approved_date, supplier_notif_method, polc.displayed_field po_status, print_count, printed_date, from_user, to_user, STATUS, mail_status, original_recipient FROM po_headers_all poh, wf_notifications wn,po_lookup_codes polc WHERE 1=1 AND polc.lookup_type(+)= 'AUTHORIZATION STATUS' AND poh.authorization_status = polc.lookup_code(+) AND wn.user_key(+) = poh.segment1 AND wn.item_key(+) = poh.wf_item_key AND supplier_notif_method = 'EMAIL' AND NVL (edi_processed_flag, 'N') <> 'Y' AND NVL(xml_flag,'N') <> 'Y' AND message_name(+) = 'AME_EMAIL_PO' AND displayed_field='Approved' ORDER BY poh.po_header_id DESC; If mail_status is MAIL, it means the email delivery is pending for workflow mailer to send the notification. If mail_status is SENT, its means mailer has sent email If mail_status is NULL & status is NULL or OPEN, its means that no need to send email as notification preference of user is “Don’t send email” or the Workflow mailer is not Up and Running Note: XML tag names are changed in R12 when compared with 11i

Read more at: http://oracleappsdna.com/2015/04/faqs-of-po-output-for-communication-report/
Copyright © www.OracleAppsDNA.com