Backflush Lot and Serial Controlled Materials During Operation Completion Using a REST API and File-Based Data Import

Welcome to the demo of the 24D backflush lot and serial controlled materials during operation completion using a REST API and file-based data import in Fusion Manufacturing.

Manufacturers want to simplify production reporting with automatic backflushing of materials based on actual usage. The materials can be locked and serial-enabled also. In addition, they want to integrate with a mobile device such as a hand-held barcode scanner, a manufacturing execution system, or a warehouse management system as the means for recording production completion. Now you can report the completion of a work order operation with specific lot and serial numbers for all materials using the REST APIs and File-Based Data Import, FBDI, for operation transactions in discrete and process manufacturing work orders.

This capability can backflush one or multiple item lots and serials from the designated supply subinventory and locator. For lot-controlled materials, lots can be manually specified for defaulted based on manual first in, first out, FIFO, and first expired first out, FEFO, logic depending on the setting of the lot selection during backflush planned parameter. For serial-controlled materials, serial numbers can be manually specified for material backflash. This enhancement increases user productivity as well as helps maintain traceability of materials.

This demo shows you how backflush lot and serial controlled materials during operation completion using a REST API and file-based data import enhances your business. First, let us review the demo scenario. I have created a work order PNDS-1208001 with two operations for lot enabled product PN-LOTPROD1. Operation 10 has two components. PN-LOTCOMP1 is lot enabled and PN-SERCOMP1 is serial enabled. Both components have operation pull supply type.

Operation 20 has one component. PN-LOTCOMP2 is lot-enabled and operation pull as supply type. We will complete first operation using operation transaction REST API and complete the second operation using the FBDI template. Then we'll review the details in production transaction history. Let us start the demo.

Work order PNDS-1208001 for lot-enabled product PN-LOTPROD1. The work order PNDS-1208001 with two operations, Operation 10 and Operation 20. Operation 10 has two components, PN-LOTCOMP1 one and PN-SERCOMP1. Component PN-LOTCOMP1 is lot enabled and PN-SERCOMP1 is serial enabled. Both components have operation pull supply type. Operation 20 has one component, PN-LOTCOMP2, which is lot enabled and has operation pool as supply type.

You can now backflush lot and serial enabled materials using the work order operation transactions REST API. For lot-enabled materials, if the lot selection during backflush planned parameter is set to manual, you must specify the lot details for the lot enabled materials. If it is set to lot FIFO or lot FEFO, system will automatically select the lot for materials. For serial-enabled materials, you must always specify the serial numbers of materials for work order operation transactions REST API.

Let us now run the operation transaction REST API with the lot and serial details of components PN-LOTCOMP1 and PN-SERCOMP1. We are backflushing one quantity of each item. We can see the script has run successfully.

In the work order, you can see that the issued quantity has been updated for both the components in Operation 10. Let us review the details in production transaction history now. You can see that the serial and lot numbers backflushed using operation transaction REST API are appearing here. The FBDI for work order operation transaction import for discrete manufacturing and process work order operation transaction import have been enhanced to allow the users to mention lot and serial details of materials.

New worksheets have been included in both FBDI templates for specifying material, material lot, and material serial details. Similar to REST, if the lot selection during backflush planned parameter is set to manual, you must specify the lot details for the materials. For lot FIFO or lot FEFO system will automatically select the lot for materials. For serial enabled materials, you must always specify the serial numbers of materials.

We have mentioned that the lot enabled item PN-LOTCOMP2 will be backflushed. Operation 20 is the last operation. So the assembly item PN-LOTPROD1 will be completed. The assembly item PN-LOTPROD1 is a lot-enabled product. So we have to mention the lot number of the item PN-LOTPROD1 here.

As the component PN-LOTCOMP2 at Operation 20 is lot enabled, we have to provide the lot number of the component. After creating the zip file, load the details in operation transaction interface. Select and upload the zip file created. Let us review the scheduled process. The scheduled process has successfully completed.

Now import the data from the operation transaction interface. We have selected the batch number specified in the FBDI file. The scheduled process has successfully completed. Let us review the details in work order UI now. You can see that issued quantity has been updated for component PN-LOTCOMP2. The completed quantity of assembly also has been updated. Let us check in the production transaction history now.

You can see that the lot number of components PN-LOTCOMP2, as mentioned in the FBDI sheet, is shown here. This is how you can backflush lot and serial controlled materials during operation completion using a REST API and file-based data import in fusion manufacturing. With this, we are at the end of the demo.