Professional Documents
Culture Documents
In this Document
Goal
Solution
Step 1 - Creating the Item
Step 2 - Creating the Shipping Network
Step 3 - Create the Internal Location
Step 4 – Create Shipping Method and assign to Org
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
In this example, the item will be procured internally from the M2 - Boston
Manufacturing inventory organization
Assign the item to the inventory organizations which are involved in the Internal Requisitioning
process.
M1 will be the destination inventory organization and M2 will be the Source Inventory
Organization.
In the Vision Demo instance, the Purchasing and Order Management Attributes are
controlled at Item Master level.
By choosing the attributes at the item master level (V1) automatically sets these
attributes for all organizations which
are assigned (ex. M1 and M2). By choosing the attributes at the Item Master level -
they are already set for all
inventory organizations assigned.
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.
Step 5 – Assign Shipping method and intransit times to the shipping Networks
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 8 - Creating the Requisition
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.
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');
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.
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.
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.
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.
Operating Unit - Operating Unit of the Source Inventory Organization (Ex. M2)
Order Source - Internal (or the order type being used
Order Reference - Requisition Number
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');