Copyriat (¢) 2023, oral. Al ight reserved. Orel Conde Purchase Order Documents Interface (PDOT) Enhancement Features and Considerations (Doc ID 1939713.1) In this Document Impact: known Issues: References, (Oracle Purchasing - Version 12.1.3 to 12.2.4 [Release 12.1 to 12.2] Information in this document applies to any platform. Explain the changes made to the Purchase Order Documents Interface (POT) code in order to enhance the functionality and to make it consistent across the Purchasing module and list known issues caused by these changes. This applies to the new feature implemented as part of the 12.1.3 Oracle Procurement Recommended Patch Collection (lanuary 2014), patch 18120913:R12.PRC_PFB or later The PDOI code was rewritten In order to accommodate new features that enhances the PDOI functionality and to make it consistent ‘across the Purchasing module, Some of the features implemented are: ‘+ Ablity to create a Purchase Order (PO) with Requisition Reference ‘+ Ablity to create a Global Blanket Purchase Agreements (GBPA) and Global Contract Purchase Agreement (GCPA) reference through PDOT ‘+ Ability to use Advance Pricing in PDOT + Importing Contract Agreements through PDOL ‘+ Maintain consistency of defaulting values across the Buyer Work Center (BWC), Autocreate and PDO! programs Some issues have been identified with the code that have already been fixed and it is highly recommended to apply the latest Recommended Patch Collection (RPC), also known as the Rollup Patch (RUP). Currently itis patch 18911810:R12.PRC_PFB (Juli4 RPC), For the complete details on the RPC refer to Note 1468883,1, Impact: + Anew workflow process called PDOT Auto Approval Process (POOL AUTO_APPROVE) is now launched when the import concurrent program is executed with Approval Status parameter as APPROVED. This workfiow is available under the same PO Approval Item Type (POAPPRV). The purpose ofthis workflow includes: @- Run submission check ©. Reserve the document if encumbrance is enabled 2 Approve the document. Approval authorty is nt checked, just approve the document «Check ifthe Approved Supplier List (ASL) and sourcing rules should be created based on that PDOI parameter and accordingly launch that concurrent program The Workflow (WF) will be submitted in background mode in order to reduce the wait time of the import process. At the tend of the impart process, it launches the Workflow Background Process to complete the approval process. For this reasonensure the WE Background concurrent process is submitted propelry and it completes normal, in order for the imported documents to get properly approved. If necessary, run the concurrent program manually ‘+ Anew profile option PO: Use PDOI Autocreatewas created, The default and recommended value of this profile is Null. This profile option is purely for the purpase of technical level execution, it determines whether the Autocreate feature in Oracle Purchasing will execute the code used in PDOI to automatically create standard purchase orders and blanket purchase agreements, The values avallable for this profile option are: © Null or Yes. Recommended value «No. This profile option must be set to No only when suggested by Oracle Note: This profile is obsoleted in 12.2 - as the autocreate process will always be utilizing the new PDOI cadeline. ‘+ When importing PO documents, the PDO will now call the same Account generator workflow as when the PO document is created from the frm. The import will no longer honor the accrual, variance, and budget accounts from the interface tables. This is to maintain consistency with behavior from the forms. The logic is that if a valid account is present on the Purchase (Order Distribution Deliver to Person or the Buyer Employee records - then the account is not used from the interface table. Only if there is not an account present on the Deliver To Person (distribution) or Buyer/Agent (header) - will the value be used that is being passed in PO_DISTRIBUTIONS_INTERFACE.CHARGE_ACCOUNT_ID. More details present in Note 1590446.1. ‘+ PDOI concurrent program (Import Standard Purchase Orders and Import Price Catalogs) now includes a new parameter called Group Lines. When this parameter is set to Yes, the PDOT will group all the lines satisfying the matching conditions into @ single line. Shipments will also be grouped based on the matching conditions. The matching criteria works similar to how it works in the Autocreate form, Some of the criteria includes: Purchase basis, Matching basis, Item(id, description, revision, category), Unit of Measure (UOM), Source dacument, as well as the profiles PO: Use Need-by Date for Default Grouping and PO: Use Ship-to for Default grouping. Ifthe lines do not match the criteria they will nt be grouped despite the value of the parameter. ‘+ Prior to POOL enhancement patch, PO_LINES_INTERFACE was used to import BPA Price Breaks. But after PDO! Enhancement Patch, PO_LINE_LOCATIONS._ INTERFACE needs to be used to import Price Breaks. This has great impact to customers because customers usually use add-on programs to populate interface tables. Please refer to BUG 20642259 and Bug 20032995. Known Issues: ‘+ PO document gets stuck in pre-approved status after importing via PDOI auto-approve when the Approval Management Engine (AME) is enabled. To fix this issue, apply patch 19234290. ‘+ When trying to Import/Autocreate expense items, the Accrue on Receipt flag was always defaulted from the Purchasing setup (Accrue Expense Item "Receipt”) and doesn't honor the user passed value/receipt required flag. To fix ths issue apply patch 19598349, ‘+ When using Endeca product, PDOI runs for long time (bad performance). This is reported and fixed in bug 19906312. Please apply corresponding patch. ‘+ When importing documents, the documents get stuck/remains in "IN-PROCESS" status until the WF Background process is submitted manually. The workflow background process is not picking up the documents. Fix is available in patch 20272485, (replacement of 19627524). For a complete description of the patch see Note 1608907.1, ‘NOTE:1468883.1 - 12.1.3: Procurement Family Update ~ Consolidated Rollup Patch :29931278:R12.PO.B NOTE:1915603.1 - Purchase Order Import Returns Grouping Error For Lines With Multiple Shipments Error: This line cannot be ‘grouped as the matching criteria is not satisfied. NOTE: 1608907 1 - Oracle Purchasing Release Notes for Release Oracle Pracurement Recommended Patch Collection (January 2014) Dian find what you ae loking for?