Preparation plan

Use this function to prepare shipments, generate a pick list, and print the pick tickets.

If the APPSOH—Order signature management parameter (VEN chapter, APP group) is set for approval circuit management, sales orders that comply with the established signature rules need to be Totally signed to be included.

You need to use the Orders function (GESSOH) to unlock sales orders that are blocked if the SCDTUNL—Authorization to unlock order parameter (VEN chapter, AUZ group) is set.

A Shipping preparation function is also available in VT mode. It can be accessed from a portable terminal, and is also used to create and validate the main information linked to shipping preparations and launch label prints automatically.

Use case examples

Multiple orders need to be shipped tomorrow. The orders contain the following:

  • Products from the "Toys" and "Food" statistical groups
  • Orders with late deliveries for the same customers

How to use the shipment preparation plan

  1. Create preparation codes that correspond with the "Toys" and "Food" statistical groups.

  2. In the plan, enter tomorrow's date as the preparation date. The preparation date is then the same as the shipping date.

    Product-site records do not include a preparation lead time.
  3. Clear the Break by shipping date and Break by order checkboxes.

Result

2 pick tickets are generated by statistical group. Orders are grouped by customer.

  • Pick ticket 1: is generated for the products in the "Toys" statistical group
  • Pick ticket 2: is generated for the products in the "Food" statistical group

Multiple orders need to be shipped to customers A and B tomorrow.
There are late orders for the same customers for the products PRD1 and PRD2 with different delivery types, D1 and D2.

List of orders:

  • Order 1: Delivery type D1, Customer A, Product PRD1
  • Order 2: Delivery type D1, Customer A, Product PRD2
  • Order 3: Delivery type (blank), Customer A, Product PRD2
  • Order 4: Delivery type D1, Customer B, Product PRD1
  • Order 5: Delivery type D2, Customer A, Product PRD2
  • Order 6: Delivery type (blank), Customer A, Product PRD2
  • Order 7: Delivery type D1, Customer B, Product PRD1

How to use the shipment preparation plan

  1. In the plan, enter tomorrow's date as the preparation date. The preparation date is then the same as the shipping date.

    Product-site records do not include a preparation lead time.
  2. Clear the Break by shipping date and Break by order checkboxes.

Result

4 pick tickets are generated. They group orders by customer and by delivery type:

  • Pick ticket 1: groups orders 4 and 7 for product PRD1 for customer B with delivery type D1
  • Pick ticket 2: groups orders 1 and 2 for products PRD1 and PRD2 for customer A
  • Pick ticket 3: groups orders 3 and 6 for product PRD2 for customer A with delivery type blank
  • Pick ticket 4: is for order 5 for product PRD2 for customer A with delivery type D2

Prerequisites

Refer to the documentation on Implementation.

Screen management

Entry screen

Use this screen to enter your selection criteria and the break parameters for the pick tickets.

Filters

Site (STOFCY)
The product storage site.
Picker (PREUSR)
The preparatory picker code to assign to the pick tickets.
Preparation list (PRLNUM)
The pick list.
Include additional lines (LSTWIOFLG)

Select the checkbox to add products on an existing list.

The checkbox is available when a list to be prepared is displayed. It provides access to the filters for a new search.

If pick tickets were generated, this functionality is not available.

Start - end range

Picking date until (PREDAT)

The last date for eligible lines to be included in the print. The current date is the default date.

The pick lead time on the Product-site record is also considered.
Only allocated quantities (ALLFLG)

Indicates that only allocated quantities are included.

Clear the checkbox if orders to prepare are set to Shipment order complete, so that order lines of this type are taken into account in the preparation.

From ship-to customer / To ship-to customer (BPCORDSTR / BPCORDEND)
Filter for results for a range of ship-to customers. For a single ship-to customer, enter the same customer code in the From ship-to customer and To ship-to customer fields.
Address / Address (BPAADDSTR / BPAADDEND)
Filter for results for a range of delivery customer address codes. For a single delivery address, enter the same address code in the start/from and end/to Address fields.
From route code / To route code (DRNSTR / DRNEND)
Filter for results for a range of customer routing codes. For a single routing, enter the same routing code in the From route code and To route code fields.
From carrier / To carrier (BPTSTR / BPTEND)
Filter for results for a range of carrier codes. For a single carrier, enter the same carrier code in the From carrier and To carrier fields.
From order no. / To order no. (SOHNUMSTR / SOHNUMEND)
Filter for results for a range of sales order numbers. For a single sales order, enter the same order number in the From order no. and To order no. fields.

Preparation origin

Orders (FLG1)
Indicates that sales orders are included.
Loan orders (FLG2)

Indicates that loan orders are included. These are orders that are shipped and not invoiced because they’re a loan to be returned.

A loan needs to be returned by a given date. The customer can be invoiced if they retain the goods.

Subcontract reorder (FLG3)
Indicates that subcontract reorder requirements are included.
Subcontract shortages (FLG4)
Indicates that subcontract order shortages are included.

Generation of preparation

Break on order (ORDRUP)

Indicates that a pick list is generated for each order.

Leave the checkbox clear to group multiple orders for the same ship-to customer.

Break by ship date (SHIRUP)

Indicates that a pick list is generated for each shipment date for the same ship-to customer.

Leave the checkbox clear to generate pick list including orders, regardless of the shipment date.

This checkbox only applies to a single customer. You cannot group orders for different ship-to customers on the same pick ticket.

Allocation type (ALLTYPFLG)
The allocation type to pick: Detailed or Global.

Stock movement

Destination location (LOCDESH)

The new destination location. For example, when the preparation is complete the picker can assign the list to a loading dock.

Select the Feed picking lines icon to assign the new destination location. Select the Deliverable action to carry out the stock change.

Feed picking lines (ALILOCDES)
Select the icon to replace all destination locations with the destination location defined in the Destination location field (LOCDESH).

Classification

Sort order (SRTCOD)

The preparation list sort order can be by order number, shipment date, or by product.

You can sort the preparation list by shipment date even if the shipment date is not included in the entry transaction.

Grid Stock to be prepared

Plan (COCHAGE)
Indicates that the line is selected.
Pick ticket (PRHNUM)
The pick ticket number.
Status (DLVFLG)
The pick status can be in process, deliverable, or delivered.
Source (ORITYP)
The origin of the line. This can be an order, loan order, subcontract reorder, or a subcontract shortage.
Order no. (ORINUM)
The order number.
Ship date (SHIDAT)
The shipment date. You cannot edit this field.
Product (ITMREF)
The product to process.
Description (ITMDES1)
The product description.
Subcontract loc. (REOLOC)

The location of the subcontractor for the subcontract reorder.

This field is only available if the line origin is set to subcontract reorder.

Quantity (QTYSTU)

The quantity in the stock unit calculated from the ordered quantity in the order unit.

The minimum purchase quantity or the required quantity is suggested by default. You cannot enter a quantity less than the default quantity. A warning is displayed if the entered quantity is not a multiple of the order unit.

You can modify the quantity if the order unit is a packing unit that cannot be used with other units such as the product purchase unit, supplier purchase unit, supplier packing unit, or stock unit. The unit conversion needs to be editable, as defined in the Packing unit table in the Units section on the product record.

If you modify the quantity in the stock unit, the conversion factor between the order unit and the purchase unit is adjusted.

STK (STU)
The unit in which the product is stored. It provides the key to prices, costs, volumes, etc.
Allocated qty. (ALLQTY)
The quantity allocated to the line being picked.
Shortage (SHTQTY)
The shortage quantity.
Allocation type (ALLTYP)
The allocation type to pick: Detailed or Global.
Requirement qty. (QTYSTUMAX)
The original pick quantity.
Sold-to (BPCORD)
The customer code.
Delivery address (BPAADD)

The delivery customer address code.

Select Address from the Actions icon to view the customer address.

You cannot edit this field after a delivery line is created, however you can view the address details. If you need to change the address, select Address / Delivery from the Action panel.

Warehouse (WRH)
The warehouse code. You can only edit this field if the WRH activity code is set.
Lot (LOT)
The identification number or batch code the product is stored in.
Sublot (SLO)
The subdivision of the lot.
Serial number / Ending serial number (SERNUM / SERNUMF)
Filter for a range of product serial numbers. For a single serial number, enter the same serial number in the from Serial number and Ending serial number fields.
Location (LOC)
The transaction location.
Status (STA)
The inspection and quality assurance rating of the product in the specific lot or batch.
Identifier 1 / Identifier 2 (PALNUM / CTRNUM)
A record identifier.
PAC (PCU)

The supplier packing unit.

The product can have multiple packing units:

  • A packing unit defined on the product record. These units are proposed when entering the stock transaction. The number of packing units that can be entered is subject to the NUC—Number of packing units activity code.
  • A packing unit linked to the supplier and defined on the product-supplier record.
  • 2 customer packing units defined on the product-customer record. These can be used as sales units in order entry.
PAC-STK conv. (PCUSTUCOE)

The stock unit to packing unit conversion factor: Quantity in STK = Qty in PAC * conversion factor.

You can edit the conversion factor if the packing Unit field (PCU) and the Stock unit field (STU) have different values.

Target location (LOCDES)

The destination location. The location is used in the product-site grid and in the stock movement entry.

The values are stored in the 2707 local menu.

Packaging (PCK)

The number of products, expressed in the sales unit, that can be placed in the packaging. It’s initialized after the product is entered, based on the sales unit and the shipping site:

  • If the order sales unit is initialized to the customer product sales unit, the packaging is initialized to that for the customer product.
  • If the customer product sales unit does not exist, the order sales unit is initialized to the product sales unit. The packaging is initialized for the product-site or to the product category if not defined for the product-site.
  • If you modify the shipping site for the line so that it's different from the shipping site on the order header, the packaging is initialized to the customer product or to the product-site if not defined for the customer.

After the line is entered and validated, the packaging is not reinitialized if you modify the shipping site for the line. You need to enter it manually.

This information and the packaging capacity are used for preparation or shipment. During the declared packing, the packaging code is entered if it’s displayed in the original delivery or pick tickets documents.

Packaging capacity (PCKCAP)

The number of products, in the sales unit, that the packaging can contain.

This value is initialized by default with the quantity on the product-site record.

Line type (LINTYP)
The line type distinguishes a classic product from a kit or a bill of material (BOM).
Delivery type (SDHTYP)
The delivery type associated with the order type.
Stock issues
Select Stock issues from the Actions icon to view the stock issues details.
Pick ticket
Select Pick ticket from the Actions icon to view the pick ticket details.
Order
Select Order from the Actions icon to view the order details.
Stock by site
Select Stock by site from the Actions icon to view the stock levels for the product at the site.

Reports

By default, the following reports are associated with this function:

Bullet point  LISTEPREPA: Preparation list

Bullet point  LISTEPREPAALL: Picking list allocated prod.

This can be changed using a different setup.

Specific actions

Search Select the Search action to start the search for eligible lines that meet the entered criteria.
Include all Select the Include all action to select all the table lines before the preparation plan number is generated.
Exclude allSelect the Exclude all action to exclude all table lines.
CriteriaSelect the Criteria action for additional selection criteria.
Prep listSelect the Prep list action to create the pick list from the selections in the table. A number is assigned to the pick list. You can then enter the pick list number in the Preparation list field in the Filters block.
Pick ticketSelect the Pick ticket action to generate pick tickets from the lines in the preparation plans.
DeliverableSelect the Deliverable action if the pick list is complete.

Actions menu

Select the Transaction action to view the format of the Shipment preparation plans entry transation.
Select the Journal traceability action to view the journal hierarchy.

Limitations

Leave the Only allocated quantities checkbox clear if some orders to prepare are set to Shipment order complete, so that the order lines of this type can be taken into account in the preparation.

Error messages

In addition to the generic error messages, the following messages can appear during the entry:

There is no 'Picking origin' ticked
Unavailable Location
Do you want to erase the destination locations of the picking lines?
The quantity entered is larger than the quantity remaining to be picked

Tables used

Refer to the documentation on Implementation.