Table of Contents 


Introduction

Delivery represent the preparation of the goods at plant or warehouse. This is at that time that the  (Batch allocation / Picking / Packing) is done. The Delivery document is an RCS internal document which initializes the set of necessary tasks to organize the transportation and to physically prepare the goods before their shipment. A ‘Delivery’ document can only be created on the earliest of the 2 following dates :

  •  Date of availability of the goods
  •  Date of transportation organization (In case of shipping, this date may precede the date of availability of the goods, due to the required booking of a container before having it at your disposal).


Delivery processes and functions available in WP2 are described in the documentation here..

This document contains information related to:

  • Overview of processes and Delivery typology.
  • Main functions & data of a Delivery.
  • Managing Deliveries.
  • Delivery texts and outputs

Delivery Types Used in RCS

  1. Outbound Delivery (LF). 

  2. Inbound Delivery (EL).

  3. Return Delivery (LR).

  4. Replenishment Delivery (NL).

  5. Replenishment Cross-company Delivery (NLCC)

  6. Delivery for stock transfers (UL). 

  7. Delivery for Sub con (LB).

  8. Restock Transport Order (NLR)

Documentation 


LE_EN11 Overview of Logistic Processes and Typology

EN13_ TRAINING SUPPORT-Deliveries


Creation of the delivery

In order to create a delivery the order has to be completed and should be free of Credit Blocks and Delivery blocks. The Order should also be free of any Compliance blocks and ATP blocks.  The delivery can only be created at the earliest of Material availability date or transportation organisation date (In case of export orders this date may precede the date of availability of the goods, due to the required booking of a container before having it at your disposal).

  1. Creating an outbound delivery for a sales order

  2. Creating a collective processing of documents  due for delivery for earlier operations

  3. Delivery Split

  4. Copy Control

For Composites BU, specific business requirements require various changes in the copy control between STO and delivery. This includes:

              a. Service level, FedEx account number, single packing list fields will be copied from the SO/ PO item level ( Additional Data B) to the delivery item, for downstream processes.

              b. For the delivery type RL, Returns (PO), the incoterms will be copied from PO item to delivery header.


SBS_FFS_Solstice Aero _ Copy Control_STO to Delivery

SBS_FFS_Solstice Aero _ Copy Control_Order to Delivery_V4

SBS_FFS_Solstice Aero _ Copy Control_Order to Delivery UL


Creation of a delivery for stock transfers between two storage locations of the same plant

Two different processes have been customized to create a delivery for stock transfers between two storage locations of the same plant:

  • 2-step transfer between 2 storage locations of restricted stock (Siew for Silica). The stock transfer can be done for unrestricted-use, quality inspection and blocked stock.
  • 1-step tranfer between 2 storage locations, from 311 mvt, with delivery and shipment


Batch allocation

Batch Allocation is the process where the appropriate batches are assigned/ allocated to the delivery to be shipped to the customer. It involves setting up Batch search strategies, Batch Determination procedures. 

  • The customer specifications are recorded in a batch search strategy. If there are no requirements communicated by the customer, there is at least a strategy defined at plant level, which meets standard quality norms.
  • The system tries always to use the most precise batch search strategy it can find, therefore it will search in priority a strategy defined at ship-to party level.
  • The batches are selected in the batch allocation process and displayed sorted by shelf life.
  • If no batch is found, a message is displayed.

Batch search Strategy

  • In a Batch Search Strategy, you define the values according to which the system is to find batches. It is used during the batches allocation to the delivery. By default, the system uses the basic strategy set for the material at Plant level (mandatory), which meets the Standard Quality Norm. 

  • Whenever a customer requests other specifications different of the standard Quality Norm, other batch search strategies can be created to define selection criteria (either automatic or manual) of batches which meet the customer’s requirements. Business units decide who is responsible for the creation and the management of these data

  • The most precise Batch search strategy is defined at the "ship-to" Customer/ plant /  Material level
  • Creation / modification / deletion of 'Batch Search Strategy' at customer 'ship-to' level is done by the enterprise, but the one managed at plant level is always managed centrally by the Data Administrators.
  • Among other things, a batch search strategy contains the following settings :
    •  Batch Selection criteria (remaining shelf life, manufacturing plant…)
    •  Sorting rules
    •  Maximum number of batches.

Batch Determination 

  • The Batch determination is the function to determine batches that match customer specifications on the basis of certain selection criteria.
  • The batch determination is done in the delivery. The determination can be performed automatically or manually.
  • If batches have already been specified in the sales order (derogation sale), they are copied to the delivery, and cannot be changed there
  • You still have the option of triggering manual batch determination, if you have already used automatic batch determination previously, but want to use other batches than those the system selected using the sort rules.
  • The determination mode (automatic or manual) depends on the item category in the sales order :
    • If item category is TAN : When the delivery is created, the system tries automatically to locate a batch complying with the batch search strategy which is applicable.
    • If item category is ZMAN, batches will have to be located manually. In the sales order, the item category is determined from the item category group set in the ‘Sales Org. Data 2’ view of the material.
    •  In standard, when the item category group of the material is NORM, then the item category determined in the sales order is TAN.  When the item category group of the material is ZMAN, then the item category is ZMAN.  
    • For some plants, we can assign the item category ZMAN to all materials shipped from this plant. It prevents any automatic batch determination, whatever the item category group in the material master data. 
    • Other item categories support automatic batch determination : ZKLB (Industrial item) in late differentiation, TAB (Individual purchase order), ZKLN (Sample auto batch).
  • The customer requirements are recorded in a batch search strategy. If there are no requirements communicated by the customer, there is at least a strategy defined at plant level, to propose batches without quality issues.
  • The system always tries to use the most precise batch search strategy it can find, therefore it will search in priority a strategy defined at ship-to party level.
  • Multiple batches can be allocated through batch split.
  • If no batches are determined by batch search strategy, then a blank screen is returned in the determination.
  • For Composites business, the batch search strategy will also consider the customer material specifications as part of the selection criteria which are placed in the sales order/stock replenishment order and the batch soft allocation (sales document link in the batch) in order to determine the batches that were produced for a specific order.
  • For Aero business, there are three different strategies based on the process.
    • Make to Order: Batch search strategy is enhanced to consider the new batch characteristics included in the batch classification (Sales order number, sales order line, specifications, etc) including single batch requirement.
    • Make to Stock with Specifications: Batch search strategy FIFO will be used along with passed specifications
    • Make to Stock: Batch search strategy FIFO will be used

Picking

Picking is the action to pick-up the goods (In general, to move them from their storage place to another warehouse area where they are prepared for shipment), also called ‘goods preparation’. 

Picking process can occur only when :

  • Batches are allocated
  •  Packaging is determined
  •  Transfer order has been created        
  • A pick ticket/loading sheet is issued.
  • Printing is automatic at transfer order creation. To re-print the pick ticket, use LT31 with print code 21.

The transfer order’ is the representation in the system of the picking action.  The ‘pick ticket’ is the form issued at the Transfer Order creation, with the information needed for the goods preparation in the warehouse and loading (batch number, packing instructions…). The ‘loading sheet’ is the equivalent of the pick ticket, for bulk materials.  After the physical goods preparation, the picking process is completed by the confirmation of the transfer order : Operation which consists in confirming the quantities actually picked. Labels are printed. The ‘loading’ phase starts.

Packing

A product is sold under a commercial label in its contact packaging and manufactured  according to an accurate bill of materials.

  • The SAP standard functionality ‘Packing Instructions’ (POP) helps to manage automatically the different ways of packing and handling materials, during the delivery creation. It avoids to manage particular packing instruction in the customer or order texts.
  • One instruction  = One way of packing a material
  • A packing instruction describes the packaging material, if materials or batches can be mixed or not…
  • You can have one or more ‘Packing Instructions’ per material
  • Therefore, a second SAP functionality ‘Packing Instruction-Determination record’ (POF) is mandatory to define where and for who the packing instruction applies, for example :
    • At Plant/Shipping condition/Material/Ship-to-party level
    • At material level (This record is mandatory and always entered at Shipping    point level by the Logistics department)
    •  At Ship-to / Material level (possibly)

Packing Instructions for Composites BU

  • For Composites business, there is a specific process to setup the packing instructions in order to give to the users the option to manage the number of units, pallets and gross weight of the product.
  • All materials that can be shipped will be setup with a generic packaging material on its master data.
  • Packing instructions will be setup per plant and packaging material (boxes, drums, etc)
  • This will allow to the EDA (Enterprise data administrator) create generic packing instructions that can be used by all plants, reducing drastically the number of instructions to be created.
  • The generic instructions will also enable the system to ask to the user the number of units, pallets and gross weight of the product as for Composites business it is not possible to have this information automatically calculated.

FSD on semi-auto packaging implemented by Solstice

Gross weight calculation

Some customization has been done to centralize the calculation of the gross weight in the delivery instead of calculating it for each output.


Shipping point modification/determination

Thanks to some customization, it is possible to automatically propose to change the shipping point of a delivery after it has been created. This is useful in some plants like Collonge where it is not known at delivery creation from which shipping point (central warehouse or external warehouse) the goods are going to be shipped.






  • No labels