Shipping updates
Active SHP transactions are picked up from WL Transaction Inquiry. The line item and header information is updated in the WL Entry Batch Shipping Report, similar to these functions:
- Sales Shipping Feedback Entry
- Transfer Shipping Feedback Entry
- VA Shipping Feedback Entry when standard system orders, transfers, and VA work orders are shipped
Orders being processed through the system have a work-in-process status in WL Transaction Inquiry. Successful updates show with an inactive status.
Orders, warehouse transfers, and VA work orders can be processed concurrently with the WL Entry Batch Shipping Report. You must set up the system to process them at the same time and at the same interval. Your TWL administrator can set up a separate report for each function. This is so that processing occurs at different times to coincide with the frequency and schedules of the related activities.
For example, your warehouse may process customer orders frequently throughout the day. However, it only processes warehouse transfers when the delivery truck arrives to pick up shipments. It only processes VA work orders on a weekly basis. The data being communicated from TWL is set up so that duplicate data is not transmitted more than once if three reports are running simultaneously.
If changes were made to an order while the order was being picked, the order is changed in the WL Entry Batch Shipping Report to reflect the changes. For example, some of the line item quantity may have been returned to stock or to unavailable. If so, then the order and the system records are updated in the WL Entry Batch Shipping Report.
A full order update transaction is sent to complete the shipping process. This action updates the full order if the order is shipped, or if sent to backorder for products that were not shipped. The order header is updated with the shipped date, freight add-ons, ship via, and number of packages shipped.
Because the order has been loaded on the truck, changes cannot be made to the line items. Although, addons, at the header level, can be adjusted. Addons can be manually changed in the system, after a TWL order has been shipped. If so, then the charges on the manifest are different from the invoice charges. Labor lines can be manually added to the order, after a TWL order has been shipped. This labor might be added to cover assistance with packaging or shipping. Journals are opened during the update process for sales orders, transfers, and VA work orders as needed. Transactions posted to these journals are closed per function, so postings are not crossed. If two journals are opened for a single user, then the two journals could potentially cause duplicate postings and transmission errors. We recommend that you set up two different stored reports for two different operators. This is to process the customer orders and warehouse transfers at staggered times during the day to avoid a processing overlap.
Be aware of when a WL Entry Batch Receiving Report is scheduled as a stored report. This is so that you can stagger the processing times enabling a report to finish processing before another report is started.
The operators you assign to the stored reports must be unique and cannot be assigned to any other processing function. For example, to process customer orders, you set up a stored report for operator DEF with specific option settings. This table shows the option settings:
| Option | Value |
|---|---|
| 1. Sales Order Entry Shipping Process? | Yes |
| 2. Warehouse Transfer Process? | No |
| 3. Value Add Shipping Process? | No |
| 4. Check for Locks Prior to Processing? | Yes |
| 5. Run OEERS on OE Non Stock Lines? | No |
Then, for example, to process transfers, you set up a stored report for operator JKL with different option settings. Ensure you set up this stored report so that it does not begin processing until the stored report for customer orders is finished. This table shows the option settings:
| Option | Value |
|---|---|
| 1. Sales Order Entry Shipping Process? | No |
| 2. Warehouse Transfer Process? | Yes |
| 3. Value Add Shipping Process? | No |
| 4. Check for Locks Prior to Processing? | Yes |
| 5. Run OEERS on OE Non Stock Lines? | No |
Then, for example, to process VA work orders, you set up a stored report for operator UVW with different option settings. Be sure to set up this stored report so that it does not begin processing until the stored report for orders and transfers is finished. This table shows the option settings:
| Option | Value |
|---|---|
| 1. Sales Order Entry Shipping Process? | No |
| 2. Warehouse Transfer Process? | No |
| 3. Value Add Shipping Process? | Yes |
| 4. Check for Locks Prior to Processing? | Yes |
| 5. Run OEERS on OE Non Stock Lines? | No |
The same shipping updates that the Sales Shipping Feedback Entry and Transfer Shipping Feedback Entry functions perform are initiated in the WL Entry Batch Shipping Report. This update includes closing the shipping journal and updating General Ledger and Inventory Control. If processing stops before the journal is successfully closed, you must manually close the journal. The journals are not opened by the WL Entry Batch Shipping Report; other functions that open the journals are launched. The report output provides order information and relevant error messages.