If Cubing is in use, the cubing logic will be applied when this process is run. Refer to Database Warehouse for and overview of the Cubing functionality and the set up requirements.
When selecting a run from this screen an error report is generated, this should be kept and filed for future reference if any queries arise. The system checks for conditions where the order should not have a pick slip printed, for example either temporarily unavailable or automatic backorder. The errors on this report mean a Picking Slip has not been printed. These show on the Warehouse Pool screen.
The Warehouse Pick Plan Selection displays the merged customer orders by picking slip number. All orders visible are at the order status D (in pick). The picking slip header (WHTRA00P) status is W (Available to warehouse). The order status is therefore DW.
Orders come into this screen from the Customer service pick plan selection option, where the orders are merged and an Order Category is assigned to the picking slip.
An audit trail is produced showing order movement, being the order status showing movement backwards and forwards from K to D, D to K, D to P, etc. These status movements can be seen on the Date Stamp. RVS on the Date Stamp is the status for reversing from D to K.
The user can force orders to backorder once the orders are ready to be released “to pick” in the warehouse. Orders can be forced to backorder regardless of the Stock status and the customer backorder acceptance flag.
Consignment Notes can be printed at this stage if TMSDS/PRT-CON has been setup as K=Picking Slips.
TMSDS/PRT-SMRY determines whether to print picking slips in detail or summary or both and immediately when available, for the selected Device types. The Device type entered on the selection screen is matched to this Control File. If found then the type of print (D, S, B or I) will be used to produce paper picking slips. If I is selected it will be treated as D Detail and print one picking slip per invoice. Note D= 1 picking slip per invoice, S= 1 picking slip per batch (run).
TMSDS/PRT-SMRY also determines whether or not a batch container is to be generated for summary pick runs by WHO210 for picking a group of small orders into a tote. This is followed by deconsolidation and creates multiple totes within the same run. A tote label is also printed followed by the summary picking list, using the warehouse run number from the Batch Container File (WHBCH00P).
When assigning picking slips to a batch container the total container weight will not exceed the container weight limit if it is defined on the Container Types File (WHCT00P). There can be multiple batch containers per run. Batch containers will optionally generate for a run and split picking slips into multiple batch containers based on cubed capacity of the batch container.
TMSWH/USE-RF contains a yes/no/both flag for each type of movement within a warehouse, designating warehouses, which use radio frequency functionality and those that do not. NOTE: All warehouses should have an entry in this Control File. A generic entry may be used by entering **** under the warehouse heading.
TMSDS/WH-RUN determines whether the pick run should be automatically generated by Warehouse, Pick Run or Category.
TMSWH/CNV-DIMN Conversion from title dimension to location dimension. This Control File determines what devices are to be used in the picking process. For example, does a pallet fit on the device type?
The Customer Masterfile has a flag to indicate whether or not the customer wants orders to merge. Orders can be merged with other orders or released backorders currently held on the system. This allows a single delivery of two or more orders to the one site. Order consolidation flag (OCON) is soft coded in control file TMSDS/CM-OCON to define how to merge picking slip/invoice and how to trigger invoice merge process, either automatically by system or manually released for invoice. Merging or Consolidating Invoices is a way to reduce external costs per invoice in the case of off site warehousing and to reduce customer minimum order charges if applicable. At Order Entry the operator can override the merge flag to cater for special circumstances where the order is not to be merged with any others. Orders can be merged by Billing Number instead of Customer Number.
Orders will not merge if they differ in certain respects. These are:
- Immediate document print
- Order is not an Invoice (for example a credit or a return)
- Order is an Advice
- Order Type (picking method) is different: direct to invoice will not merge with already delivered
- Customer does not allow consolidation
- Customer number differs
- Delivery details differ
- Payment Terms differ
- Payment Types differ – one order is cash with order and the other is credit card with order
- Tax numbers differ
- Warehouse codes differ
- Different document types
- Different document subtypes
- Delivery address is overridden
- Tax code overridden
- Type of sale code on the order header differs
- Carrier code differs
- Forwarding agent differs
- Delivery number differs
- Delivery Run Stop number differs
- Title is not a stock item
- Source of transaction codes differ
- Today’s day is greater than the backorder cut-off date
- Title is flagged as new release (no stock)
