Document 1468883.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

12.1.3: Procurement Family Update - Current Rollup Patch : 18120913:R12.PRC_PF.B (Doc ID 1468883.1)
Modified: 17-Mar-2014 Type: README

In this Document Main Content What are the Procurement family updates and why are they recommended? Who should apply this patch? Applying the Oracle Procurement Update January 2014 for 12.1.3 Additional Recommended Patching How to perform an impact analysis for this patch Focus of this RUP: Purchasing Document Open Interface and Buyer Work Center Rollups Functional impact Details of fixes incorporated in Patch 18120913:R12.PRC_PF.B Most important fixes included in Patch 18120913:R12.PRC_PF.B Testing Recommendation - Key Business Flows Known issues on top of Patch 18120913:R12.PRC_PF.B Prior rollup documentation Still have Questions? References

APPLIES TO:
Oracle Purchasing - Version 12.1.3 to 12.1.3 [Release 12.1] Information in this document applies to any platform.

MAIN CONTENT
What are the Procurement family updates and why are they recommended?
Procurement releases regular rollup patches (RUPs) which compile important fixes that have been made to the products of the Procurement family. These patches are cumulative (Latest rollup include fixes from previous RUPs) and can be applied on top of Release 12.1.3 or R12.PRC_PF.B.delta.3. Customers on Release 12.1.1 or 12.1.2 should consider to implement the Oracle E-Business Suite release update pack Patch 9239090 or apply R12.PRC_PF.B.delta.3 Patch 9249354. These patches go through a full quality assurance testing and therefore increase the overall stability of the products when compared to one-off patches. The purpose of the RUPs is to provide highly reliable code that maximizes your experience with the products under the Procurement family.

Who should apply this patch?

Anyone that is on Release 12.1.3. Development and support advise customers on Release 12.1.3 to download and apply the latest patch. This is especially important for any organizations planning to upgrade, or are already in the process of upgrading to release 12.1.3.

Applying the Oracle Procurement Update January 2014 for 12.1.3

Follow these steps to apply the current procurement update: 1. Download and unzip Patch 18120913:R12.PRC_PF.B 2. Follow the instructions in the patch readme. Apply prerequisites: Patch 14185210:R12.FWK.B Patch 12678526:R12.FND.B Post-Update Steps: 3. Apply Patch 12625661:R12.PO.B 4. Follow instructions from Note 1406203.1 to validate the application accounting definitions

1 de 8

18/03/2014 12:38 p. m.

Document 1468883.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

5. For the Procurement Accounting processes (accruals and encumbrances) access Note 1594111.1 and follow the patching steps provided. 6. Procurement rollup patches incorporate root cause fixes for data integrity issues. In order to proactively identify and correct data that was previously entered, run the master data fix diagnostic: Run the data fix diagnostic from Note 1474734.1 R12: Master Data Fix Diagnostic to Validate Data Related to Purchase Orders and Requisitions Review the user friendly html output report. The report will show all known data integrity issues relating to the purchasing transactions created in the specified date range along with information on notes with root causes and/or data-fix patches. Follow the recommended actions to resolve data integrity issues.

Additional Recommended Patching

1. For Procurement Accounting processes (accruals and encumbrances) access Note 1594111.1 and follow the patching steps provided. This patching is additionally noted in the 'Post-Update Steps' section for the Procurement RUP above. 2. Oracle Internet Procurement Connector Patch 12334398:R12.AP.B resolves issue with invalid ITG_SYNCSUPPLIERINBOUND_PVT after applying Patch 12334398:R12.AP.B.

Good News! With this current RUP Patch 18120913:R12.PRC_PF.B the following patches have been included and do NOT need to be applied separately: a. 12.1.3: Procurement iSupplier Portal, Sourcing and Supplier Lifecycle Management (SLM) Rollup Patch : 17525552:R12.PRC_PF.B: This rollups accumulate fixes (and new features) related to the iSupplier, Sourcing and SLM functionality for release 12.1.3. See Note 1591198.1 for more information. b. 12.1.3: Purchasing Approvals Rollup Patch : 16932593:R12.PO.B: This Approval rollup accumulates fixes related to the Approvals functionality (including AME) for release 12.1.3. See Note 1567464.1 for more information.

How to perform an impact analysis for this patch

While a patch may contain several hundred files, the impact on your system is most likely far less. Patches contain hard-prerequisites that are intended to make a patch work on a very low code baseline. The Patch Wizard Utility is a free utility that comes installed as part of the E-Business Suite Products and can be accessed via Oracle Applications Manager. This utility will give you a detailed impact analysis for any patch including RUPs. The analysis gives you an idea of how the patch application will impact your environment. Refer to Note 976188.1 for more information on the patch wizard utility.

Focus of this RUP: Purchasing Document Open Interface and Buyer Work Center Rollups
Although this is the lastest consolidated RUP for Procurement, the primary focus was on the Purchasing Document Open Interface (PDOI) and Buyer Work Center (BWC) which accumulate fixes related to the PDOI and BWC for release 12.1.3. These patches go through the same quality assurance testing as the Procurement family updates and will include critical new fixes that are not incorporated in the current Procurement family update. Functional impact Buyer Work Center (BWC) With this release enhancements to the BWC focus on the following main areas: Session Preferences-enables user to setup session preferences in the BWC BPA Lead Time-if a user updates a GBPA line additional information with lead time information and then creates a PO in the BWC with GBPA reference, with approval of PO the Promise date is derived Search Cleanup-code now validates all Search parameters enabling consistent searching in BWC Multiple Supplier Email Address in BWC Purchasing Document Open Interface (PDOI) With this release enhancements to PDOI include: Ability to create Purchase Orders (POs) with Requisition Reference Ability to create a Global Blanket Purchase Agreement (GBPA) and Global Contract Purchase Agreement (GCPA) reference through PDOI

2 de 8

18/03/2014 12:38 p. m.

Document 1468883.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

Ability to use Advance Pricing in PDOI Importing Contract Agreements through PDOI Utilizing PDOI to autocreate Sourcing/ Consumption Advice/Documentation Flows to create Standard Purchase Order/Blanket Purchase Agreements Ability to include Contract Reference in the Autocreate Form/Document Builder Create and Update Purchase Orders Using New Business Service Object (BSO) Web Service: With this release, you can use the new Business Service Object web service to create and update Purchase Orders of types: Standard Purchase Orders, Complex Purchase Orders, Global Blanket Purchase Agreements and Global Contract Purchase Agreements. Oracle Purchasing Buyer Work Center functions are supported by this web service. Details of fixes incorporated in Patch 18120913:R12.PRC_PF.B See Note 1608907.1 'Oracle Purchasing Release Notes for Release Oracle Procurement Recommended Patch Collection (January 2014)' for details on the new and changed features released with this patch. Additionally Note 1608907.1 contains links to corresponding Technical Documentation.

Most important fixes included in Patch 18120913:R12.PRC_PF.B

Bug number Functional area Purchase orders and requisitions processing Purchase orders and requisitions processing Purchase orders and requisitions processing Purchase orders and requisitions processing Purchase orders and requisitions processing Bug 15836292 Bug 14386329 Bug 13931180 Bug 13890183 Find that upon doing a cancel, the form does nothing and returns back to the cancel form. Poor performance in Create internal orders process FRM-41056 error when entering item information on Quotations form Uploading or Updating Blanket Agreement via PDOI Functionality Continuously Erroring with 'Errors were encountered while loading updates' When performing a search in buyer work center, it errors with 'You have encountered an unexpected error. Please contact the System Administrator for assistance' In Oracle Purchasing, release form closed abruptly when distribution window was closed Import Price Catalog error with ORA-6533 Purchase Order Unit Of Measure Is Not Matching Between The Line And Shipment - PO Line Has Different UOM Than Shipment After upgrade to 12.1.3, error when accessing the purchase order or requisition form : 'You are not setup as a worker. To access this form you need to be a worker' When creating a Requisition the item price is being rounded to 5 decimals When an automatic purchase order (created using Autocreate or through the buyer work center) is deleted, the requisition is not returned to the requisition pool Running mass close of purchasing documents closes more purchase orders than expected Symptoms

Bug 13885926

Purchase orders and requisitions processing Purchase orders and requisitions processing Purchase orders and requisitions processing Purchase orders and requisitions processing

Bug 13799611 Bug 13736932 Bug 13699463

Bug 13552967

Purchase orders and requisitions processing Purchase orders and requisitions processing

Bug 13250367 Bug 11887932

Purchase orders and requisitions processing

Bug 10371162

3 de 8

18/03/2014 12:38 p. m.

Document 1468883.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

Purchase orders and requisitions processing

Bug 10286564

For purchase orders imported through interface, Accrue On Receipt flag is unchecked for one time expense items even though the Purchasing Options has Accrue Expense Item At Receipt Contract Purchase Agreement should be defaulted in the Standard Purchase Order when using Advanced Pricing and Sourcing Partially or fully Reserved Requisition/PO/Release that got stuck in IN PROCESS or PRE-APPROVED status, will be set back to INCOMPLETE or REQUIRES REAPPROVAL status using Reset scripts Duplicate distribution lines are displaying the Purchase Order Summary form Prevent error 'Please undo the changes to the document in the current revision before taking the cancel action' when canceling revised purchase orders Prevent purchase orders to remain in requires reapproval status after being canceled Purchase order output (PDF) does not display ship to information when PO output for communication is run in debug mode In Oracle Purchasing, for a purchase order with budgetary control enabled project, if baselined cost budget is not available proper message is not shown Error in PSA_BC_XLA_PUB.Budgetary_Control when reserving or checking funds on a purchase order with foreign currency In Oracle Purchasing during the Reserve action on a Federal PO (with backing Requisition), the backing Requisition's Encumbered Flag and Encumbered Amount are not updated to correct values Unable to Reserve Purchase Order Due To Error DO_ACTION-070: ORA-01400 Generic error message 'Procedure PSA_BC_XLA_PUB.Budgetary_control returns an error without any details to the calling procedure' for encumbrance actions When attempting to Submit a Purchase Order for approval, error occurs: 'There exists a closed wip job for this document' In Oracle Purchasing, approval screen shows up only with buttons with no text on them Approval Options and Submit buttons were disabled when a BPA is opened in update mode from iProcurement Catalog Administration. The note entered in the response section of notification is not displayed in the action history when a purchase order is rejected

Purchase orders and requisitions processing Purchase orders and requisitions processing

Bug 12625661

Bug 9707155

Purchase orders and requisitions processing Purchase orders and requisitions processing

Bug 8337350 and Bug 12319476 Note 315607.1

Purchase orders and requisitions processing PDF delivery to supplier

Note 1379274.1 Bug 10388305

Encumbrance

Bug 14525049

Encumbrance

Bug 14229705

Encumbrance

Bug 13610367

Encumbrance Encumbrance

Bug 12972273 Bug 12824154

Approvals

Bug 14383315

Approvals Approvals

Bug 13545598 Bug 13337717

Approvals

Bug 12360278

4 de 8

18/03/2014 12:38 p. m.

Document 1468883.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

Bug 12332819 Approvals

When attempting to approve complex PO the following error occurs: UOM (Unit Of Measure) of Line # 1 does not match with the UOM (Unit Of Measure) of the corresponding Shipment # 0. Cannot Access Attached Zip File In Po E-Mail Supplier Notification Prevent approval notifications to fail with error ora-6512 at activity Get PO Attributes (PO_POAPPROVAL_INIT1.GET_PO_ATTRIBUTES) after upgrade to 12.1.3. In Oracle Purchasing, BPA were not getting approved if they were having any canceled lines with expiration date out of the effective range of the header Unexpected error java.lang.NullPointerException when attempting to view requisition details after using the "My Group's Requisitions" view When changing the expiration date for an agreement in Buyers Worbench, it only displays items in iprocurement for new lines but not for old lines Error 'An error has occurred during tax calculation which could impact tax information display' in requisition creation Changes in the supplier type descriptive flexfield (DFF) are not saved. Suppliers Accounting Tab failed with java error : java.sql.SQLSyntaxErrorException: ORA-01722: invalid number. Failed To Assign Addresses To Contact. Error message: SQLAPAP_INVALID_PARTY_SITE_FOR_CONT When adding another Operating Unit for existing Site for non-Federally Reportable Supplier: Warning: One or more operating units do not have an income tax reporting site specified for this 1099 federally reportable supplier

Approvals

Bug 12330727 Bug 10627841

Approvals

Approvals

Bug 9931066

iProcurement

Bug 14808582

iProcurement

Bug 13343886

iProcurement

Bug 12562286

iSupplier iSupplier

Bug 9654468 Bug 12731705

iSupplier

Bug 12983048

iSupplier

Bug 16354733

Testing Recommendation - Key Business Flows

This section includes guidelines with information about key business flows that need to be tested after applying Patch 18120913:R12.PRC_PF.B Functional area BWC Preferences Case 1: 1. Business user logs into application and configures Purchase Options line type as Goods and Match Approval level as 3-Way. 2. Navigate to Buyer Work Center> Preferences. 3. Configure Preference fields Line type as Amount Based and Match Approval level as Key Business Flow Expected Result The Line type defaults from preferences as Amount Based and Match Approval level also defaults from Preferences.

5 de 8

18/03/2014 12:38 p. m.

Document 1468883.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

2-Way. 4. Create Standard Purchase Order in Buyer Preference values get cleared off. Work Center. Enter header, line, shipment, and distribution information. 5. Save Case 2: 1. Business user logs out from application. 2. Business user login again to the application. BWC Deriving Promise Date based on Lead time 1. Create GBPA from Buyer Work Center. Update line additional information with lead time. 2. Create Standard Purchase Order from Buyer Work Center. Refer the GBPA created. 3. Verify the source information displays lead time. 4. Submit Purchase Order for approval. 5. Ensure Document status is updated to approved status. Standard Purchase Order promise date is updated based on GBPA lead time. Promise date = PO approved date + lead time (as per GBPA).

BWC Search

1. Search option from BWC Requisition lines Search option retrieves values based on and Summary are streamlined. search parameters. 2. Search from Order, Agreement at line, Shipment, and Distribution are streamlined. Import Purchase Order to interface with Requisition reference, GBPA and Contracts. Standard Purchase Order, Agreement, Complex PO can be created thru XML. Purchase Order created with reference document once import standard purchase order API has completed. Document is imported and can be verified thru the UI.

PDOI enhanced to support document reference and CPA Web Services

Known issues on top of Patch 18120913:R12.PRC_PF.B

This section will be regularly updated with issues found during and after the application of 18120913:R12.PRC_PF.B. Functional area Patch Application Patch Application Fix Reference See Note 1354793.1 for fix. Apply Patch 18085870:R12.PO.B Symptoms When applying Patch 17525552 or Patch 18120913 error 'index POS_SUPPLIER_SEARCH_INDEX does not exist' occurs. ORA-20101 AND ORA-20001 after applying Patch 18120913: ORA-20101: Independent Value Set Validation Type Mismatch. Please make sure Dependent Value Set depends on an Independent Value Set. ----- Error Message Stack ----ORA-20001: LDR.up_vset_depends_on()(LEAF, PO_PDOI_SOURCING_LEVEL, PO_ASL_ENABLE_FLAG) raised exception. ORA-20101: Independent Value Set Validation Type Mismatch. Please make sure Dependent Value Set depends on an Independent Value Set. Patch Application Use the Force command. Execute the following manually from a new On application of 18120913 patch fails and log file shows something like: ================= $FND_TOP/bin/WFLOAD &ui_apps 0 Y UPGRADE @POS:patch/115/import/US/POSSPAPM.wft Community Thread 3511030 References Community Thread 802230

Bug 18378259

6 de 8

18/03/2014 12:38 p. m.

Document 1468883.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

terminal. $FND_TOP/bin /WFLOAD apps/apps_password 0 Y FORCE @POS:patch/115 /import /US/POSSPAPM.wft If customized, then you should load the workflow as above and then re-apply your customizations. Restart the worker if the patch session is not terminated, if adpatch session is terminated.

Log filename :$APPL_TOP/admin/CLONEP6 /log/l1242614.req wferr: - 1602: Could not save. - 1400: Could not save to database. MODE=UPGRADE EFFDATE=<null> - 1404: Please first load this entity or check protect and custom level of PROCESS_ACTIVITY 'WFSTD/FED_BUILD_PA_AP_INVO_ACCT_GEN'. Oracle Workflow Definition Loader 2.6.4.0. Access level: 20, Mode: UPGRADE ITEM_TYPE 'WFSTD' is protected, no changes were saved. ITEM_ATTRIBUTE 'WFSTD/EVENTNAME' is customized, no changes were saved. ITEM_ATTRIBUTE 'WFSTD/N' is protected, no changes were saved. ITEM_ATTRIBUTE 'WFSTD/REQUESTOR_USERNAME' is protected, no changes were saved. ITEM_ATTRIBUTE 'WFSTD/OWNER_ROLE' is protected, no changes were saved. ITEM_ATTRIBUTE 'WFSTD/FORWARD_FROM_DISPLAY_NAME' is protected, no changes were saved. ITEM_ATTRIBUTE 'WFSTD/REQUESTOR' is customized, no changes were saved Worker fails on POS_SUPPLIER_SEARCH_INDEX.sql with error like: sqlplus -s APPS/***** @/ebsz/appl/app/apps_st/appl/pos /12.0.0/patch/115/sql/POS_SUPPLIER_SEARCH_INDEX.sql Connected. DECLARE * ERROR at line 1: ORA-20000: possearchindex.sql(500): ORA-20000: Exception at POS_SUPPLIER_SEARCH_INDEX_PKG.create_index(1800): ORA-20000: Exception at POS_SUPPLIER_SEARCH_INDEX_PKG.create_index(1800): ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine ORA-20000: Oracle Text error: DRG-10754: memory size must be between 1024 and 1073741824 Bug 18260653 Patch application failing with nvoking Utility FndXdfCmp ... Class: oracle.apps.fnd.odf2.FndXdfCmp Method: applyXDF Arguments: &un_apps &pw_apps &un_apps &pw_apps &jdbc_protocol &jdbc_db_addr index &fullpath_icx_patch/115 /xdf_icx_cat_items_ctx_hdrs_tlp_n5.xdf &fullpath_fnd_patch/115/xdf_xsl Exception occured in retrieving tablespace information Error is :Closed Connection Could not retrieve tablespace information for object ICX_CAT_ITEMS_CTX_HDRS_TLP_N5 Community Thread 3511030

Patch Application

For DBMS 11.2.0.3 apply Database Patch 16706896 or for DBMS 11.2.0.4 apply Database Patch 17402822, then re-apply Patch 18120913.

Patch Application

See Note 1631178.1 for fix.

7 de 8

18/03/2014 12:38 p. m.

Document 1468883.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

Autocreate

See Note 1629612.1 for fix.

Bug 18168010 Autocreate is failing with: Unexpected error occurred during autocreate. Workflow error shows: Error Message ORA-01403: no data found ORA-01403: no data found Error Stack po_autosetup_notification_data.setup_notification_data()

Accounting

Follow instructions from Note 1406203.1 to validate the application accounting definitions.

Internal Testing Funds reservation fails with an error: The application accounting definition Purchasing Encumbrance Application Accounting Definition owned by Oracle is not validated. Please validate the application accounting definition or update the application accounting .....

If there are any additional errors on patch application (ie, errors in the worker log, invalids etc.) log a thread with the EBS Patching Community.

Prior rollup documentation

Refer to Note 1549958.1 to see documentation for prior procurement rollups.

Still have Questions?

Join our growing Oracle Procurement Community and learn from your peers and Oracle on how to address your unique issues in Procurement. 1. Access the Community page directly at http://communities.oracle.com or via My Oracle Support with https://supporthtml.oracle.com, log in then click on the Community tab. 2. In Select a sub-space to participate or start a discussion enter Procurement. 3. Double click on Procurement (MOSC) from the list. 4. Click on Start a Discussion link under the Actions section and submit your question.

REFERENCES
NOTE:222339.1 - Procurement Family Patch Release History

8 de 8

18/03/2014 12:38 p. m.