Documentation >
MAC-PAC Technical Library >
Manufacturing >
Just-in-Time >
Programs >
Flow Receipts to FA - Async - Purpose
Flow Receipts to FA - Async - Purpose
JT125E
The Flow Receipts to FA - Async program (JT125E) processes flow receipts and issues for a given plant. It is called from the asynchronous monitor, JTASYNCMON, when the monitor receives a message from the Flow Receipts/Issues Data Entry program (JT120E), or from the Electronic Data Collection Router program (BC200E), or from itself when a multi-level backflushed part has been processed. When called from the asynchronous monitor, the program reads one or several records from the asynchronous transaction file formatted in the Flow Receipts/Issues Data Entry program or from the Electronic Data Collection Router program, or from itself.
If the receipt comes from EDC, only one record is read, that matches the date, time and sequence number that are passed by the monitor. Otherwise, all records that match the date and time only are read and processed.
For each transaction record, the program processes receipts against Flow Authorizations. If a production schedule does not exist for a receipt, the program will create one dynamically. The program also processes issues against Flow Requirements if the part has component requirements. It takes the quantity entered in the flow receipt conversation and the Flow Authorization (JT100M), Multiple Location (IC130M), and Warehouse Balance (IC140M) files are updated. For lot-controlled parts, components are issued from the WIP balance (WBWIPB) on the Warehouse Balance file (IC140M) and the Lot Control file (IC150M) is updated. For Deduct Point parts, components are also issued from the WIP balance (WBWIPB) on the Warehouse Balance file (IC140M). For component issues, the on-hand-balance quantities on the Warehouse Balance (IC140M) and multiple location (IC130M) files are updated, and the flow requirements file (JT120M) is updated. The Part Master file (DE100M) is updated for both flow receipt and issue processing to set the requirements planning net change flag to reanalyze.
If the component is consumed and is a multi-level backflushed part, a flow receipt or a stock transfer (regardless of the part type) will be generated by creating a record in the corresponding asynchronous transaction file, and by sending a message to the asynchronous monitor, so that the movement is processed later (by JT125E or IC120E).
After processing the flow receipt and its associated component issues, a message is displayed to either the user or the EDC Message Queue, depending on the processing mode of the program, indicating processing has been completed. The message indicates whether the receipt was successful, partial, or unsuccessful.
Error messages are written to the Transaction Error Register. For EDC transactions, critical errors are not written to the Transactions Error Register, because these errors may be reviewed and corrected online using the Flow Receipt Error Maintenance program (BC120E).
Then, control is passed back to the asynchronous monitor.
