Shipping Method LOV In Sourcing Rule Return Wrong Values -Planning for Intransit Days Incorrect
(Doc ID 557816.1)
Last updated on JULY 08, 2020
Applies to:Oracle Advanced Supply Chain Planning - Version 126.96.36.199 and later
Information in this document applies to any platform.
FORM:MSCFDDSR.FMB - Define Sourcing Rules/Bills of Distribution
EXECUTABLE:MSCNEW - Memory-Based Planner
11.5.10 in Production
This issue ONLY OCCURS when Sourcing Rule is defined and maintained in the ASCP Application.
If sourcing rule is collected, then this issue will NOT occur.
You can check if Sourcing Rule is collected by checking MSC_SOURCING_RULES.COLLECTED_FLAG - 1 = Collected / 2 = Created in ASCP.
This only occurs when version of form is 115.76.11510.8
MSCFDDSR.FMB is corrupted by the fix in bug 6344603
When trying to create or update sourcing rule in ASCP and set shipping method, the value returned by the LOV is the shipping method text and not the ship method code.
Since the wrong value is written to the table, the planing engine will not calculate the shipping LT for this sourcing rule after the creation or update (old sourcing rules contain the correct value).
Results are as follows:
1. Original Plan output before updating the Sourcing Rule Ship Method
SUGGESTED DUE DATE 20-NOV-08
OLD DUE DATE 13-DEC-08
SHIPPING METHOD 000001_HDD_Grd-3_T_GND (ship method)
INTRANSIT DAYS = 21
2. THEN editing sourcing rule with new ship method -
3. THEN PLAN RESULTS SHOW
SUGGESTED DUE DATE 11-DEC-08
OLD DUE DATE 13-DEC-08
SHIPPING METHOD HDD_Grd-3 (this is ship method TEXT from the same method shown above)
INTRANSIT DAYS = 0
4. THEN updating shipping method for this rule using
UPDATE MSC_SR_SOURCE_ORG T
SET T.ship_method = '000001_HDD_Grd-3_T_GND'
WHERE T.ship_method LIKE 'HDD_Grd-3'
5. THEN plan results are back to same as #1
NAV: ASCP / Sourcing / Sourcing Rules
Note: Only Sourcing Rules created in ASCP can be maintained in ASCP application.
Open the Sourcing Rule and Query the ship method
Show only the Ship Method Text and then writes this to the form and the table.
Planning is not correct and cannot continue without SQL update of the tables.
Production cannot proceed with these plan results!!
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document