Aeros CONNECT now has the ability to send, receive, and create inventory receivers based on Scheduled Deliveries in the Purchase Order routine. This process interfaces with Repete for the sending and receiving. The receivers are created in the Receive Against PO routine in ERP.
Pre-Requisites
- A PO with one or more Scheduled Delivery
Create Batch
The first step in the purchase order schedule batch process is creating a batch
Users must enter a valid ERP division and date range. Please note that the dates are the scheduled delivery dates not the PO date. Any POs with scheduled delieveries in the date range specified will be pulled into the batch.
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.
When the batch is created, the Initial column fields will be filled out. Each line represents a scheduled delivery and the include flag will be checked by default.
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.
Send to Batcher
Once the batch is brought up, the scheduled deliveries are ready to send to Repete CNX (Send Completed is unchecked).
If the send is successful, the Send Completed field would be checked and the rest of the Send band are populated with data. Note, scheduled deliveries can only be sent once.
At this point, the deliveries will now be in Repete and available for review.
Receive from Batcher
Once the tickets/receipts are ready for CONNECT, bring up the batch and press the Receive button. If tickets/receipts are not in a state for CONNECT to consume, this process doesn't do anything and has no side effects.
Once CONNECT is able to receive some tickets/receipts, the Receive band is updated with data. The scheduled deliveries are then ready for the next step, commit to ERP.
