What Are The Steps Required To Setup An Internal Requisition
What Are The Steps Required To Setup An Internal Requisition
1)
Modified: 17-Jul-2013 Type: HOWTO
In this Document
Goal
Solution
Step 1 - Creating the Item
Step 2 - Creating the Shipping Network
Step 3 - Create the Internal Location
Step 4 - Conduct a Miscellanous Transaction (Receipt)
Step 5 - Create the Internal Customer - Assign the Location
Step 6 - Item Price Information
Step 7 - Creating the Requisition
Step 8 - Submitting the Create Internal Orders Concurrent Request
Step 9 - Import the Internal Sales Order
Step 10 - Execute Pick Release/Ship Confirm
Step 11 - Conduct the Receipt in the Destination Organization
Step 12 - Confirm the Quantity is Delivered
References
APPLIES TO:
GOAL
What are the basic setup steps required to use the Internal Requisition Functionality?
SOLUTION
Testcase Scnario: The following setups will demonstrate the flow of an Internal Requisition between two inventory organizations.
In this example, the item will be procured internally from the M2 - Boston Manufacturing inventory organization
In this example, the setups are being done to allow the user to Enter a Receipt in M1 after the item has been shipped from M2 (Intransit).
Please Note - If the Source and Destination Inventory Organizations are the same, then this step is conditionally not required. (Essentially the Item is being transferred
between subinventories in the same Inventory Organization).
The location created will be used to tie the Destination Location in the requisition form to the Internal Customer to be used on the Sales Order form.
Purchasing does not allow the entry of a Customer - therefore it passes the location to Order Management.
During Order Import in Order Management - the system locates the Customer Record to which the Location is assigned. Associating the location to the customer record will be
done in the later steps.
This step is being done to satisfy the Internal Sales Order which is created, as it ensures that there will be ample quantity On Hand (in M2) to perform the shipping portion of
the Internal Sales Order process from the M2 inventory organization.
Step 5 - Create the Internal Customer - Assign the Location
Enter the Location that was created in Step 3 (Ex. M1-Internal Location)
Apply and save the record
PLEASE NOTE: The Customer must be created in the Operating Unit of the Source Inventory Organization that is used on the Internal Requisition. You can check the Operating
Unit for the Source Inventory Organization by using the following sql:
The price used on the requisition comes from the item costs section.
The screen to follow shows the item price that is used when creating the Internal Requisition. This is how purchasing derives the price when creating the Internal Requisition. It
uses the price for the Cost - in the Source Inventory Organization. Whatever the price is in the Source Inventory Organization used on the requisition - the price is derived. The
reason is that the Sales Order is being created in the Source Organization, so the price in the Source Organization must be used.
Step 7 - Creating the Requisition
Question: Why is the Source Inventory Organization Not showing the inventory organization which was setup in the shipping networks?
If the internal requisition is going to be for a cross operating unit scenario - then it should be noted that the HR: Security Profile is used.
Both operating units for which the inventory organizations belong too must exist in the HR: Security Profile.
To confirm the operating units for the inventory organizations - this sql can be used:
Confirm that the operating units in the given output exist in the security profile that is set for the HR: Security Profile - profile.
Please note that the calculate_price_flag is inserted as N into the Order Management interface tables. This means that Purchasing is going to pass the price and it will not be
impacted or recalculated when imported into Order Management. This is proper functionality. We are currently tracking on Enhancement Request Bug 3095239 that would allow
the use of an Internal Price List.
The following sql can be used to review the data in the oe_iface tables.
SELECT *
FROM OE_HEADERS_IFACE_ALL
WHERE order_source_id = 10
AND orig_sys_document_ref IN
(SELECT REQUISITION_HEADER_ID
FROM PO_REQUISITION_HEADERS_ALL
WHERE segment1 = '&requisition_number');
SELECT *
FROM OE_LINES_IFACE_ALL
WHERE order_source_id = 10
AND orig_sys_document_ref IN
(SELECT REQUISITION_HEADER_ID
FROM PO_REQUISITION_HEADERS_ALL
WHERE segment1 = '&requisition_number');
This is possible using the Order Management Responsibility - and navigating to Orders/Import Orders/Corrections
Be sure to choose Lines first - and then choose the delete icon from the toolbar - then delete the header
Deletion of the header record will NOT delete the line - it is not a cascade delete option. If the header is deleted prior to the line - it is not possible to ever again locate the line
in this form - sqlplus will have to be used to remove the line.
Enhancement Bug 4966920 has been created to improve this form and add the cascade delete functionality and now is implemented with the following
Patch 13702362 - AFTER HEADER IS DELETED, ORPHAN DATA IS LEAVED IN SALES ORDER INTERFACE TABLES>>
Question: How can the Internal Requisition be resubmitted to the Order Management interface tables?
In the po_requisition_headers_all and po_requisition_lines_all table there is a column 'transferred_to_oe_flag'. Setting this column to a value of 'N' followed with a run of the
Create Internal Orders process will again post the requisition data into the Order Management interface tables. There are currently no options available through the Oracle
Purchasing forms that allow the updating of this flag, so sqlplus would have to be used.
Question (Problem): When Running the Create Internal Sales Order Process - it completes with Success but no records are inserted into the Order
Management Interface Tables?
When the internal requisition is created the code needs to validate that the customer was created in the Operating Unit that the Source Inventory Organization belongs too.
When the Create Internal Sales Order process runs, if the Deliver to Location is not tied to a Customer Ship To Site in the Operating Unit of the Source Inventory Organization
used on the requisition - then it will not insert data into the oe_headers_iface and oe_lines_iface table.
Please review the previous step 5 and use the sql given to ensure that the Customer was created in the Operating Unit that belongs to the Source Inventory Organization. For
this example, it would be required to check the Purchasing Options for the Operating Unit which M2 is belonging too.
VERY IMPORTANT ALSO REGARDING Create Internal Orders - In Release 12 you must make sure that you are choosing an Order Type in the Purchasing Options - that
was created in the SAME operating unit for the Purchasing Options you are setting up.
Ex. If you are in the Germany Purchasing Options - then ensure you choose a Order Management Order Type that was created in Germany Order Management. BEWARE - The
list of values for Order Type is showing Transaction Types from other Operating Units. So, if you are in Germany Purchasing Options and then choose a France Created
Transaction Type - no Records will be inserted during the Create Internal Orders Process. This is fixed in Release 12.1.1 and beyond.
Also, remember that whatever the Source Inventory Organization that is used on the Internal Requisition - the purchasing options must be setup for that Source Organizations
Operating Unit. So if the internal requisition has two inventory organizations from different Operating Units - ensure the Purchasing Options have been setup for both of the
Inventory Organizations Operating Units - as the code is going to check the Purchasing Options from the operating unit of the Source Organization to obtain the Order Type to
use - as the Sales Order is going to be created in the Source Organizations Operating Unit.
Question: Does the Purchasing Create Internal Orders process pass flexfield values from the Purchase Requisition?
Currently, the Create Internal Orders process does not pass any values from flexfields. If there are mandatory/required flexfields setup on the Order Lines table in Order
Management, a value will have to be defaulted as a default value from some other method in order for the import process to complete successfully.
Operating Unit - Operating Unit of the Source Inventory Organization (Ex. M2)
Order Source - Internal (or the order type being used
Order Reference - Requisition Number
Submit the request. Confirm that it completes.
The following queries can be used to confirm that the Internal Sales Order was created.
SELECT *
FROM OE_ORDER_HEADERS_ALL
WHERE order_source_id = 10
AND orig_sys_document_ref IN
(SELECT REQUISITION_HEADER_ID
FROM PO_REQUISITION_HEADERS_ALL
WHERE segment1 = '&requisition_number');
SELECT *
FROM OE_ORDER_LINES_ALL
WHERE order_source_id = 10
AND orig_sys_document_ref IN
(SELECT REQUISITION_HEADER_ID
FROM PO_REQUISITION_HEADERS_ALL
WHERE segment1 = '&requisition_number');
Once the Pick Release has been completed, requery the Internal Sales Order in the shipping transactions form.
The field 'Next Step' should now be showing Ship Confirm.
Choose the Delivery tab
While in the Delivery form, choose actions 'Ship Confirm'
The Ship Confirm submission form appears.
The selections above were all defaulted into the ship confirm submission form. Choose OK.
Requerying the record shows that the Next Step is to Run Interfaces.
This represents running the Interface Trip Stop process.
In this example, the Interface Trip Stop ran automatically.
Navigation: Shipping/Interfaces/Run - Interface Trip Stop
If required, run the Interface Trip Stop process for the Trip that was created.
Confirm that it completes with success.
The shipping process in M2 will also automatically create the receipt in M1 - if the Shipping Network was setup to have a transfer type of Direct. For this
example, Intransit was used to as to be able to demonstrate the receiving process.
REFERENCES
BUG:3095239 - ER: NEED TO USE INTERNAL PRICE LIST FOR INTERNAL ORDER NOT COST
BUG:4966920 - ENHANCEMENT: FIX TO THE CORRECTIONS FORM