|
|
---|
The first step in the purchase order schedule batch process is creating a batch | |
Users must enter a valid ERP division and date range. - The division must exist in the ERP table Division
- The process returns a warning if the date range overlaps an existing batch, but will continue the creation.
The creation process includes only in-progress purchase orders belonging to the selected division. From these purchase orders, the create process will search for in-progress PO delivery schedules not previously included in a batch. | |
The process populates staging records with information from the purchase order, purchase order line, and delivery schedule records. | Staging Field | Source Table | Source Column |
---|
PurchaseOrderNumber | POPurOrd | purordno | PurchaseOrderID | POPurOrd | POSeqNo | VendorID | POPurOrd | supplierseqno | PurchaseOrderStatus | POPurOrd | postatus | PurchaseOrderDate | POPurOrd | pdt | PurchaseOrderLineID | POLine | POLineSeqNo | ItemCode | POLine | ItemCd | ItemMasterID | ItemMaster | ItemMasterID | PurchaseOrderScheduleID | PODelSched | PODelSchedID | Comment | PODelSched | Comment | Request_Cancelled | PODelSched | true when status=N | Send_DeliveryQuantity | PODelSched | delqty |
|
- The process creates a batch header record in PurchaseOrderSchedule_Batch
- For each PO delivery schedule the creation process retrieves, it creates a staging record in PurchaseOrderSchedule_Stage
- It then opens the batch form and displays the new batch.
- The include flag is on by default for all records.
- The form has separate grid bands that group fields by their workflow process. These are
- Initial (Create): Populate by the batch creation process
- Send: Send date and sent flag populated when the staging record data have been successfully sent to Repete
- Receive: The timestamp and transaction adjustments populated when the batch has received updates from Repete.
- Commit: Timestamp and completion flag set when the process has created PO receipts in ERP for the staging record.
| |
|
|