Last updated on SEPTEMBER 09, 2013
Applies to:Oracle Purchasing - Version 12.1.3 and later
Information in this document applies to any platform.
REQIMPORT: Requisition Import
Using Multiple Operating Units, Blanket Releases are not created from the Approved Requisitions released from Advanced Supply Chain Planning (ASCP).
Checking the Requisitions, has been notice that even if ASL and Sourcing are setup, no Source Document is present at Requisition line level.
Steps to reproduce
1. Advanced Supply Chain Planner.
2. Release the planned order.
3. Requisition is created via Requisition Import, however it has not properly sourced the Blanket Agreement.
- Create Releases runs however the release is not created
- PO: Automatic Document Sourcing is set to Yes
Note: Manually creating the requisition works properly, the Blanket is sourced properly.
FND logging taken on the Source Instance where the requisition import was run - showed the following:
po.plsql.PO_AUTOSOURCE_SV.should_return_contract.010 1 Destination Doc Type: REQ Document Type Code: REQUISITION Document Subtype: PURCHASE
po.plsql.PO_AUTOSOURCE_SV.should_return_contractshould_return_contract.010.EXCEPTION 4 ;SQLERRM = ORA-01403: no data found
po.plsql.PO_AUTOSOURCE_SV.document_sourcing.045.EXCEPTION 4 ;SQLERRM = User-Defined Exception
po.plsql.po_message_s.Document_sourcing.045.EXCEPTION 4 ;SQLERRM = User-Defined Exception
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms