This function is used to automatically mass generate lists and/or picking tickets, and to print them.
If only the preparation lists are generated, the picking tickets can be generated later from the Preparation plans function.

Selection criteria can be specified, as well as a number of parameters which will be used as break criteria upon creation of the preparation lists and picking tickets.
Note The delivery type, present on the orders, is implicitly taken into account as a break criterion.

 

Warning Notes:

  • If the approval circuit is managed (parameter APPSOH - Order signature management), the sales orders complying with the established signature rules are not taken into account unless they are Totally signed.
  • If the sales orders are manually blocked (parameter SCDTUNL - Authorization to unlock order - chapter Sales, group Authorizations), they cannot be selected until a user has unlocked them (blocking field in the Order function).

Prerequisite

See also Refer to documentation Implementation

Screen management

Entry screen

Selections

Site (field STOFCY)

Enter or select the storage site where the selected product is active.

The Selection icon (magnifying glass) only suggests products that are referenced in the products-sites table.
Picker (field PREUSR)

The preparatory code entered in this field is assigned by default to the picking lists and notes.
Picking date until (field PREDAT)

The date entered in this field is used to take into account the eligible lines with a date lower or equal to the date entered.
Note The picking lead-time indicated in theProduct-site record is also taken into account.
Only allocated quantities (field ALLFLG)

If orders exist in a "complete order delivery" to be prepared, this box must not be checked so order lines of this type are taken into account in the preparation.
From ship-to customer (field BPCORDSTR)

This is a range used to process customers by code.
This field suggests that a customer code be selected to filter the orders to be displayed.
You can enter the initials of the customers only and so expand the search.

Address (field BPAADDSTR)

This field is used to select the adress code of the delivered client (start range).

To ship-to customer (field BPCORDEND)

This field is used to select a second customer code in order to filter the orders to be displayed.
This code can be identical to the one of the first range.

You can enter the initials of the customers only and so expand the search.
Address (field BPAADDEND)

This field is used to select the adress code of the delivered client (end range).

From route code (field DRNSTR)

This drop down list is used to select the routing code set up in the Customer record.

To route code (field DRNEND)

This field is used to select the routing code (end range).

From carrier (field BPTSTR)

This field is used to select a carrier code (start range).

To carrier (field BPTEND)

This field is used to select a carrier code (end range).
The carrier can be identical to the first selected carrier.

From order no. (field SOHNUMSTR)

This field is used to select the order number (start range).

To order no. (field SOHNUMEND)

This field is used to select the order number (end range).

From delivery priority (field DLVPIOSTR)

This drop-down list is used to generate the picking list depending on the delivery criteria: "Normal", "Urgent" or "Very urgent".

To delivery priority (field DLVPIOEND)
From preparation code (field PRECODSTR)

This field is used to add an other selection criteria for each picking code.

To preparation code (field PRECODEND)

Preparation origin

Orders (field FLG1)

When this box is checked, the sales orders are taken into account.
Loan orders (field FLG2)

When this box is checked, the loan orders are taken into account.
These orders are shipped and normally not invoiced because they will be the object of a loan return.

Note A loan is bound to be returned at a given date. It can be invoiced if the goods are kept by the customer.

Subcontract reorder (field FLG3)

When this box is checked, the sub-contracting reorder requirements are taken into account.
Subcontract shortages (field FLG4)

When this box is checked, the sub-contracting shortages are taken into account.

Formulas

Orders (field FOR1)

Enter, select or create additional filters with the formula editor.
Subcontract reorder (field FOR2)

Enter, select (or use the formula editor) a calcul expression concerning the replenishment of sub-contract locations, using Sage Adonix format.
Subcontract shortages (field FOR3)

Enter, select (or use the formula editor) a calcul expression concerning sub-contracting shortgages, using the Sage Adoniw format.

Preparation list parameters

Break on ship-to customer (field BPDRUP)

When unchecked, this box is used to regroup several picking lists for a same ship-to customer.
When this box is checked, the system generates always the same number of picking lists, no matter which the ship-to customer.
Break on route (field DRNRUP)

When this box is unchecked, the system regroups the order lines whatever the route number code.

When this box is checked, the system generates as many picking lists as orders having a different route number code.
Break on picking code (field PRERUP)

This box -unchecked- is used to group several picking list for a single picking code.
If this box is checked, the system generates the same number of picking lists whatever the picking code is.
Simulation (field SIMU)

Preparation list

Print (field LPRFLG)

When checked, this box launches the automatic print.

Document (field LPRNAM)

This field is used to specify the print support document of the preparation list (label, slip, etc).

Destination (field LPRDEN)
Server (field LPRSRV)

This field is used for the set up of the printing criterias for printing the preparation list (PDF, RTXT file, etc).

Printer (field LPRIMP)

This field is used to define the printer.

Pick ticket parameters

Generate pick ticket (field GENBPR)

This box is used to generate picking tickets depending on the parametrized allocation type (Detail or Global shortage).

Allocation type (field ALLTYPFLG)

The value selected in this list is reused when generating the picking notes (detailed or global allocation).

Break on order (field ORDRUP)

This box -when not checked- is used to group several picking lists for a single order.
If this box is checked, the system will generate the same number of lists whatever the order.
Break by ship date (field SHIRUP)

If this box is checked, the system generates as many picking tickets as there are shipment dates, for the same ship-to customer.
If this box is unchecked, the system generates picking tickets including orders, regardless of the shipment date.

Warning This criterion is applied to one single customer only: it is not possible to group orders of different ship-to customers in the same picking ticket.

Picking ticket

Print (field BPRFLG)

When checked, this box launches the automatic print.

Document (field BPRNAM)

This field is used to specify the print support document of the picking note (label, slip, etc).

Destination (field BPRDEN)
Server (field BPRSRV)

This field is used to set up the issue criteria for the picking note print (PDF, TXT file, etc.).

Printer (field BPRIMP)

This field is used to define the printer.

Specific Buttons

Memo

This button is used to save under a Memo code the current values of the screen, irrespective of the screen, with the goal of reusing the setup. The memo is linked to the user:

Note If a memo code called STD associated with the screen exists, it is loaded right upon entering the corresponding function.

For further information on the advanced use of the Memo button, refer to the documentation on the General ergonomics of the SAFE X3 software.

Recall

This button is used to load criteria and information previously defined and saved under a memo code.

Delete Memo

This button is used to delete a Memo code previously saved.

Limits

If some orders to prepare exist as "shipment order complete", the "Only allocated quantities" check box must not be selected, so that the order lines of this type can be taken into account in the preparation.

Error messages

The only error messages are the generic ones.

Tables used

See also Refer to documentation Implementation