Internal Orders Intransit Lead Time

Internal Orders - Intransit Lead Times Setup Steps
Scope of this Article............................................................................................................ 1

Key Setups .......................................................................................................................... 2
Internal Customer Setup 11.5.10 ..................................................................................... 3
Inter-Location Transit Times / Shipping Networks Setup .................................................. 7
Patch Notes .................................................................................................................... 7
Shipping Networks Form - INVSDOSI ...................................................................... 8
Transit Times Form (or Inter-location Transit Times) WSHFILTM ..................... 9
Setup Sourcing Rules ........................................................................................................ 10
Collecting the Data for Order Scheduling ........................................................................ 11
Appendix A R12 and 12.1 Customer Setup ................................................................... 12
Appendix B - SQL and Technical Information................................................................. 15
References ......................................................................................................................... 17
Scope of this Article

This will demonstrate the key setups to allow Internal Orders to be created
successfully with correct Scheduled Ship Date and Arrival Date, showing the
offset of the transit time. The Need By Date on the Internal Requisition should be
the Arrival Date for the Internal Sales Order.
Additionally, starting in 11.5.10 with the new calendar functionality, we have
related articles to help manage this functionality with specific calendars
controlling when orders are shipping, transited and received.
This article assumes that the basic setups have been completed for the following:
1. Locations setup Inventory>Setup>Organizations>Locations
2. Organization setup Inventory>Setup>Organizations
3. Freight Carriers and assignments Inventory>Setup>Freight Carriers
1. Ship Methods are created here and assigned to the organizations
4. Customer setup including names, addresses
5. Optionally, starting in 11.5.10, the Carrier transit time can be managed by
a calendar when profile MSC: Use Shipping/Receiving Calendars = Yes
1. If your carrier does not work 24x7, then assign an appropriate
calendar to the Trading Partner - Carrier / Calendar Usage
Carrier.
2. The most common case is carrier moves only 5 days, like a 5 day
Org calendar so assigning the Org calendar to the Carrier makes
sure the transit days that cross over the weekend do not include the
weekends.
3. NAV: Order Management>Setup>Shipping>Calendars>Assign
4. Note 436771.1 - FAQ - Understanding the ATP Results and the
Availability Window of the Sales Order Form. This has
information on Calendar setups and for shipping on Specific Days
under the following Q/A
i. How Can I Setup Calendars To Ship to Customers Only On
Certain Days Of The Week?
ii. How Can I Setup Carrier Transit Calendar and Customer
Receiving Calendar?
Oracle Corporation 2003, 2009 For Internal and Customer Use only
Rev 2.0 Sepetember 2009
251449.1_Internal_Orders_Intransit_LT_Rev3.0.doc / pdf

Our example we will use the standard Vision database
Customer - Vision Cuts # 1021
Ship From D1- Singapore - organization_id = 229 / location_id 328
Ship to M1 Seattle organization_id = 207 / location_id = 207
Key Setups
1. When setting up the Internal Customer record while all field are important,
common error is the Request Date Type is NOT set to Arrival
a. This will cause the Schedule Ship Date to be the same as the Need by Date
on the Internal Requisition.
b. When this setup is complete, then the Order Date Type in the Sales Order /
Other tab should show Arrival
c. Customer Setup Request Date Type = Sales Order Header Order Date
Type
2. The Shipping Networks Form / Shipping Methods and Transit Times forms must
have matching records for Ship Method and Default Flag
3. AFTER you have setup the Shipping Networks / Ship Methods, then setup the
Sourcing Rule for Transfer From and make sure the Ship Method is populated.
4. Sourcing rule must be setup in the Assignment Set used for scheduling orders and
also for the ASCP plan. The following should match
a. Profile - MRP: ATP Assignment Set
b. Profile - MSC: ATP Assignment Set
c. In Plan Options of the ASCP Plan Assignment Set where internal orders
are planned and released.

Internal Customer Setup 11.5.10
NAV: Order Management>Customers>Standard (navigation will vary depending
on release.) See Appendix A for R12 navigation for Customer Setup
THEN find the Customer 1021 Vision
Click Find and the following screen appears - Now click OK
THEN highlight Seattle Address line and click OPEN

With Ship To row highlighted, Click OPEN
For the Details Tab

1. The Internal region and Location fields are critical setups.
2. Other fields may be required by your business practices.
THEN click the Order Management Tab

1. Request Date Type Arrival This is critical so that when the Internal
Req is sent to Order Management, is offsets the Scheduled Ship Date
form the Need By Date on the Internal Requisition.
2. Price List
3. Warehouse
4. Ship Method optional should match to default method in Inter-locations
Lead times form as shown below.
5. Other fields may be required per your business practices
Now SAVE your work!

Inter-Location Transit Times / Shipping Networks Setup
BOTH of these forms, while they look very similar, are different, and are
responsible for setting up this process completely and correctly. They MUST be
setup exactly the same for Ship Methods and Default Flag!
Patch Notes
In 11.5.10 it has been noted that three critical patches are required before this
functionality is working as designed.
The latest GOP/ATP Rollup patch for SCP_PF.J/11.5.10 from Section II
of Note 223026.1 - List of High Priority Patches for the APS Suite.
Shipping Patch 5745021 which contains the latest version of the form
WSHFILTM.fmb - 115.21.11510.8 Inter-Locations transit times form
Inventory Patch 5262930 to get INVSDOSI.fmb 115.44.115100.8 for the
Shipping Networks form
For 11.5.8 and below fixed in 11.5.9
There are two patches that fix how the Inter-Location Transit Times populate the
table MTL_INTERORG_SHIP_METHODS
Patch 2894224 for Inter-Location Lead Times fixes the form so that
saving of the record populates all 4 relevant fields
FROM_LOCATION_ID, TO_LOCATION_ID, and now also
FROM_ORGNANIZATION_ID, TO_ORGANIZATION_ID
Patch 2937723 is the data fix that populates FROM_LOCATION_ID and
TO_LOCATION_ID where the %ORGANIZATION_ID is not NULL
IMPORTANT You must enter setups in the Shipping Networks form

first and NOT in the Transit Times form
1. Both forms populate table MTL_INTERORG_SHIP_METHODS
2. When you enter the setups in Shipping Networks form, then 4 key
columns are populated in MTL_INTERORG_SHIP_METHODS
FROM_ORGANIZATION_ID
TO_ORGANIZATION_ID
FROM_LOCATION_ID
TO_LOCATION_ID
If you enter in Transit times form first, only the two Location columns are
populated and this causes data corruption.
3. SO if you find that you have setup for Organization to Organization that
do not have all 4 columns populated, then you must delete the setups in
the Transit Times form and re-enter the setups in the Shipping Networks
form.
You can check this by querying in the Transit Times form to get the
FROM_LOCATION_ID and TO_LOCATION_ID using
/Help/Diagnostics/Examine, then run SQL to check
select * from mtl_interorg_ship_methods where from_location_id =
&from_loc_id and to_location_id = &to_loc_id;

Shipping Networks Form - INVSDOSI
NAV: Inventory>Setup>Organizations>Shipping Networks
Then for Organization M1 Scope To Organization - click Find
In this screen below highlight From D1 to M1
NAV: Tools> Shipping Methods
Note that the Ship Methods and the Default Flag are the same.
Transit Times Form (or Inter-location Transit Times) WSHFILTM

NAV: Order Management>Shipping>Regions and Zones>Transit Times
OR
NAV: Inventory>Setup>Organizations>Inter-Location Transit Times
1. Enter the From Location D1 Singapore
2. Enter the To Location M1 Seattle
3. Enter at least one Ship Method, with an Intransit time, and check the Default
Flag to the right.
3.1 Yellow Freight Truck - TL Standard is our Default Method
4. Save your work
Final Note: It may be that the Shipping Methods shown above will default in
correctly after applying the patches mentioned above.
BUT it is imperative that these two screens match, SO check all setups and
confirm.
Setup Sourcing Rules

Key Point: The Sourcing Rules setup should be at Org level NOT All Orgs
level. You cannot enter the ship method for specific org to org transfer when rule
is setup at All Orgs level.
10
Collecting the Data for Order Scheduling

The ATP routines are called during scheduling to determine the status and
availability of an item. These are the routines that calculate when an item can be
available for use and schedule the shipping accordingly.
Data Collection will collect the necessary setups when a Complete Refresh of
Collections is performed. For reference to the setups and running of Data
Collections, please refer to:
Note 145419.1 - How to Set Up Data Collection for Order Management ATP
Availability
11

Appendix A R12 and 12.1 Customer Setup
Navigate to the Customers form
Then query your Organization customer record
Then click to open the customer record

And move to the Site region at the bottom of the page to find your customer site address
12

Bottom of page click Select button for Customer and see Accounts appear, click on
Details
On Order Management Tab - set Request Date Type to Arrival and Save
13

In the Sales Order form, the Other tab, you can use Folder /Show Field to see the Order
Date Type if it is not already visible.
14

Appendix B - SQL and Technical Information
Once the data is collected the following SQL should reveal the setups are present
in the system.
Verifying setups in Transit Time and Shipping Networks
SELECT
from_organization_id from_org,
to_organization_id to_org,
from_location_id from_loc,
to_location_id to_loc,
ship_method,
intransit_time time,
default_flag DF
FROM
mtl_interorg_ship_methods
WHERE
from_organization_id = 229 and
to_organization_id = 207
FROM_ORG TO_ORG FROM_LOC TO_LOC SHIP_METHOD
TIME DF
229
207
328
207 000001_United Par_A_3DS
3
2
229
207
328
207 000001_United Par_P_UPSG
14
1
select
loc.location_id, -- LOCATION_ID from ERP Source Instance
location_code,
sr_tp_site_id,
-- ERP Source SITE_USE_ID that appears in Sales Order
tp_site_id
-- Cross reference id assigned during data collections
from
msc_tp_site_id_lid tpsid,
msc_location_associations loc
where
tpsid.partner_type = 2
and -- 2 = Customer
loc.partner_site_id = tpsid.tp_site_id
and
loc.sr_instance_id = tpsid.sr_instance_id
and
loc.organization_id is null
-- Organization_id must be NULL for internal orders
LOCATION_ID
472
1998
328
207
LOCATION_CODE
HR- San Jose
M4-Minneapolis
D1- Singapore
M1- Seattle
SR_TP_SITE_ID
1001
1026
1123
1168
TP_SITE_ID
2742
2773
3077
3075
If this SQL does not return the expected values, then check the setups for Data
Collections in Note 145419.1 Particularly the profile option MSC: Collection
Window for Trading Partner Changes (Days) which must be NULL.
15

The following is the trail of inter-locking columns that tracks these relationships
through the ERP Source and APS Destination tables.
Source ERP information stored in the transactional schemas (INV, BOM, WIP,
MRP, ONT, etc) are collected to the APS Destination schema MSC so that the
APS Suite can use it.
Reference Tables:
MSC_INTERORG_SHIP_METHODS
MSC_LOCATION_ASSOCIATIONS to MSC_TP_SITE_ID_LID
PARTNER_TYPE
PARTNER_SITE_ID = TP_SITE_ID
MSC_TP_SITE_ID_LID
SR_TP_SITE_ID
PARTNER_SITE_ID
Note: PARTNER_SITE_ID and PARTNER_ID are dynamically assigned during
the ODS Data Load of Data Collections. PARTNER_SITE_ID numbers can be
relational (location_id) OR are assigned via a sequence and have no relational
value to any ERP Source data depending on the type of partner relationship. For
Internal Orders, these are assigned by the sequence.
Source ERP Tables
OE_ORDER_LINES_ALL
SR_TP_SITE_ID = SHIP_TO_ORG_ID
HZ_CUST_SITE_USES_ALL
SITE_USE_ID = SR_TP_SITE_ID
PO_LOCATION_ASSOCIATIONS_ALL
SITE_USE_ID = SR_TP_SITE_ID
LOCATION_ID
MTL_INTERORG_SHIP_METHODS
LOCATION_ID = FROM_LOCATION_ID
LOCATION_ID = TO_LOCATION_ID
Notes:
1. SR% Columns In MSC tables, these refer to values from the ERP Source
Instance.
2. SR_INSTANCE_ID = The MSC Tables use this to identify the Source
ERP Instance. IF you are collecting from more than one Source instance,
THEN you will need to stripe the above data accordingly
3. PARTNER_TYPE
a. 1 = Supplier
b. 2 = Customer
c. 3 = Organization
16

References
Note 145419.1 - How to Set Up Data Collection for Order Management ATP
Availability
Note 436771.1 - FAQ - Understanding the ATP Results and the Availability Window of
the Sales Order Form
Oracle Corporation 2003, 2009

This article is delivered in draft form and not guaranteed to be suitable for any purpose.
Version 3.0 March 2014 fixed setup order, added sql check and sourcing rules info.
Version 2.0 September 2009 added R12 appendix
Version 1.1 October 2003
Comments may be directed to david.goddard@oracle.com - dagoddar
17

Internal Orders Intransit Lead Time

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Internal Orders Intransit Lead Time

Diunggah oleh

Hak Cipta:

Format Tersedia

Internal Orders - Intransit Lead Times Setup Steps

Scope of this Article............................................................................................................ 1

Scope of this Article