Professional Documents
Culture Documents
!
"
#
$
What are the basic setup steps required to use the Internal Requisition Functionality?
The following steps outline the setups required, followed with an internal requisition creation example:
%&# Inventory
(Ensure the responsibility has access to both the source and destination inventory organizations).
^ Internal Ordered
^ Internal Orders Enabled
^ OE Transactable
^ Save the item
Remaining in the form, with the item still present, choose 'Tools/Organization Assignments' from the top
text menu.
Ensure that the item is assigned to both the Source and Destination Inventory Organizations and save.
In this example, the Item will have a destination of 'V1 - Vision Operations' and the source will be 'M1 -
Seattle Mfg'.
'( )*+
Navigation: Setup/Organizations/Shipping Networks
^ Enter the Inventory Organization that will be the Source and the scope should be From or To
Organizations
^ Choose the Transfer Type
Ô - means that when the Internal Sales Order is shipped the receipt process in the
destination organization is done automatically
Ô
- means that when the Internal Sales Order is shipped - the destination
inventory organization has to manually do the receiving process in Purchasing
^ Choose Internal Order Required checkbox - Save
) - 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).
^ Choose the Inventory Organization that will be the Source Inventory Organization
^ Enter 'Miscellaneous Receipt' - Choose 'Transaction Lines'
^ Enter the Item created and then a sub-inventory, quantity, etc...
This step is being done to satisfy the Internal Sales Order which is created, as it ensures there will be
ample quantity On Hand to
perform the shipping portion of the Internal Sales Order process.
%&# Order Management Super User
,
Navigation: Customers/Standard - define the Customer appropriately in both operating units for the
source and destination inventory organizations
^ -&" - in the Internal Block - choose the Location which was created in Step 3
^ This association ties the customer to the location (Explanation will be confirmed as to why in
upcoming steps)
^ Move to enter other pertinent information such as price list, etc, save - Close this sub-form only.
It is also recommended to create a Bill To Usage record for the new customer.
Pass in the Source Inventory Organization Code - and then ensure the Customer is created in the
Operating Unit for the Source Inventory Organization.
%&# Purchasing Super User
4'(
Navigation: Requisitions/Purchase Requisitions
5
The reason for this error is that the code is trying to match the Location that is currently entered on the
form to a
customer, and the customer association is not found. This was done earlier in step 4. The solution to this
error is to
setup the employee record to default a location that was associated with a customer (as in step 4 above)
or prior to
entering the item, move to the destination section of the form and enter an inventory organization and
location that is
properly assigned to a customer, followed with entry of the item.
Navigation: Reports/Run
It can be used as a confirmation that the requisition has been inserted into the oe_lines_iface_all table:
This is possible using the Order Management Responsibility - and navigating to Orders/Import
Orders/Corrections (above)
^ 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 )0delete 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.
l
# How can the Internal Requisition be resubmitted to the Order Management interface tables?
In the po_requisition_headers_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.
l
1%"3#c
(
0
'"
*
%
0-"2%
Please ensure that Patch 4756100 has been applied to the system. 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. Prior to this patch - the validation was only checking that a Customer
Existed in the Operating Unit that the Destination Deliver To Inventory Organization belonged too rather
than the Source Inventory Organization. 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.
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.
8""% 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.
^ Enter the parameters for the Order Import request - Choosing Source Internal and Order
Reference the Requisition Number
^ Submit the request and confirm it completes with success
l
#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.
l
# Where is the schedule Ship Date coming from?
The scheduled ship date is passed from the requisition Need By Date, it cannot be defaulted any
differently.
l
#How is the Order Type being chosen?
This is coming from the Purchasing Options - Responsibility Purchasing Super User -
Setup/Organizations/Purchasing Options.
^ Choose Concurrent and Confirm the Pick Release process has completed with success
The pick release process is responsible for moving the quantity from the sub-inventory (selected during
the miscellaneous transaction earlier) for the Source Organization - to the Staging sub-inventory.
^ Enter the Internal Sales Order in the field 'From Order Number'
^ Choose Find and then move to the Delivery Tab
^ Next choose Ship Confirm from the actions and then the GO Button
In the new sub-form that appears - take the defaults or adjust appropriately and choose Ok
During this stage, the quantity is being transacted between the staging sub-inventory and the destination
inventory organization.
Earlier, when setting up the shipping network setups, was chosen - meaning the receipt will be
conducted at the time of ship confirm.
l
# Sometimes the following error occurs, why?
This error means that a destination sub-inventory was not entered on the Requisition form in the
destination section of the form. This is visible in the requisition in step 7 of this note.
To correct this error, query the item in the item master and view the Destination Organization details of
the item using the inventory responsibility.
^ Move to the Receiving Tab - and enter a Default Receiving Subinventory in the lower right hand
corner - save
^ Next, still in inventory - Navigate to Transactions/Transaction Open Interface - query on the item
in question
^ Choose 'Find' and then next to the record returned in error choose 'Submit' checkbox and save
Next run of the inventory interface transaction manager will process the record using the new default sub-
inventory entered into the item's receiving tab. If using iprocurement, the default sub-inventory can be
set in the iProcurement preferences, and will be used when creating the requisitions, avoiding the error all
together for future requisitions.
%
#
1. Note 224341.1 supplies an excellent diagnostic script to verify all setups are complete for Internal
Requisition creation.
2. Note 133464.1 delivers the omse11i.sql script, which when executed for the Internal Sales Order,
delivers all table data for Purchasing, Receiving, Inventory and Order Management.
l,
#
1. The following sql confirms that the Create Internal Orders concurrent process has inserted the
requisition into the Order Management Interface tables.
2. The following sql can be used to confirm the Location defined in Oracle Purchasing is tied to a
Customer in Order Management. The script shows that last ten locations created in order of creation
date.
3. The following sql can be used to review the requisition, sales order, and receipt number. It is offered to
assist in showing the joins between the various tables.
"
M&*