Minimum Transfer Quantity (MTQ) For ASCP - Alternate Routing Designator Is Hidden In Staging Table Via Legacy Collection (Doc ID 2142782.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Advanced Supply Chain Planning - Version 12.2.4 and later
Information in this document applies to any platform.

Symptoms

Issue :
============
when doing Legacy collections - Minimum Transfer Quantity(MTQ)  not working as expected.

 

Details :

============

When uploading RoutingOperation.dat file the following error was raised :
The combination of SR_INSTANCE_CODE,COMPANY_NAME,ORGANIZATION_CODE,ROUTING_NAME does not refer to a valid record in the table MSC_ST_ROUTINGS. Please submit complete MSC_ST_ROUTINGS information before submitting data for
MSC_ST_ROUTING_OPERATIONS.

For OperationResource file the following error: The value provided for ROUTING_NAME is invalid. Please resubmit this record with a valid value for ROUTING_NAME

 

 

Additional information:
========================
Example:
~~~~~~~~~~~~~~~~~~~~~~
Item = AAA
BOM Components = BOMBOM
Routing = In this using Operation 10 which uses Machine-1 as Resource
----------------------------------------------------------------------------------------
Item = BBB
BOM Components = AAA (first item in this example)
Routing = In this using Operation 10 which uses System-1 as Resource
----------------------------------------------------------------------------------------
Both AAA and BBB have different BOM and are salable items.

When a sales order for BBB is planned by ASCP first Operation-10 from Routing-AAA Produces AAA and only after complete quantity of AAA is produced then next operation-10 for routing-BBB is scheduled.

Expectation: is to have both the operations for different routings should overlap so that time is saved.

To achieve this, MTQ functionality was used.

As per OATemplateReadme.html in RoutingOperation.dat , Minimum Transfer Quantity was populated with value 0.1, but even though this, the plan output did not show the Overlapping of Operations as expected .

 

On a side note : prior to actually hitting the error described in the issue above, as per Routing.csv for the Assembly YYYYYYYYY there are 4 different records / routing names used.
These are the alternate routing defined for item YYYYYYYYY.

When trying to assign Alternate Routing Designator, the collection process showed an error when this was uploaded with the Routing,. As a workaround for this, the Alternate Routing Designator was removed from Routing, and uploaded as four routing for one Assembly.

Question is , How to collect Alternate Routing Designator through the Routing file.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms