Progressive releases (outbound 830/862) generated through Supply chain direct

Progressive releases or schedules generated through supply chain direct are not visible through PO maintenance as they are auto generated so their is no need to make them visible in maintenance. They can be inquired through PO inquiry.

ILVS production reporting through Shop floor

 CMS provides specialized functionality of production reporting of ILVS through shop floor. This functionality is provided using specialized shop floor events which are aware of ILVS. These events are These events make shop floor engine aware of sequential requirements received through EDI document 866 or through broadcast.  These events are  10160, 330060, 40061,10102,40062,51061,51060.

Moving data manually from TrustedLink to CMS

If you are moving data manually from TrustedLink TLI then you should initiate an EDI request first using 'Retrieve Documents from EDI Flat File' functionality from RAMN05/2 before actually moving the data from TLI to interface files. This will lock the EDI engine for manual retrieval of data. Failure to do so will put you at the mercy of EDI activity happening at the time. For example let's suppose you move data from TLI to interface files but before you start an EDI request an outbound ASN may clear the data.

Reporting queued repetitive production and Purging

When repetitive production is reported, by default, system will use build schedule to purge the production demand from the system. If you are queuing repetitive production then production demand removed from the system may not be the earliest in the queue but the oldest build schedule (please refer to earlier post build vs production schedule). CMS can be configured to remove production demand based on queue number assigned to repetitive production. This can be configured using production master table and selecting reporting tab. 

EDI Tips, Fun Facts, Troubleshooting and more

One of the most powerful feature of CMS is EDI whether it is doing supply chain direct, or whether handling Steel procurement it can do all. I have worked for more than a decade as integral part of EDI team and designed many functionality myself. I would be sharing tips, historical fun facts and troubleshooting tips.

Stay tune.

Production Schedule vs Build Schedule

When a production order is created two types of schedules are created. One is production and the other is build schedule. When you print a manager's report you are looking at production schedule. When you print build schedule you are looking at build schedule. Production schedule represents when a production order will start and end. Build schedule represents when actually it will be build.

It is very critical to understand the difference between too as they influence the outcome of MRP, finite scheduling, white board scheduling , how production demand will be removed from the system when production is reported, inventory allocations etc.

Build schedule is represented by three tables called PLAN, FIRM and SOFT. They are not identical tables. I usually use SQL with union to get the data from them in unison.

In future I will be posting tips explaining how to configure they system to achieve desire results.