Professional Documents
Culture Documents
Batch Configuration v2
Batch Configuration v2
Batch Management
Plant level
One batch can have different specifications in different plants. Batch data is not transferred in case of stock
transfers between plants
Material Level (Standard SAP setting)
One batch number can be assigned to different materials, but a combination of a batch and a material has the
same specifications in all plants
Client Level (Proposed setting for Flowserve)
One batch number is always unique in the system. Two materials cannot have the same batch.
Note: This setting has to be made in each system separately, it is not transported. If the setting is
changed, a conversion program has to be run to convert existing batches
More info
Batch Status Management
Note: This setting has to be made in each system separately, it is not transported. If the setting is
changed, a conversion program has to be run to convert existing batches
© 2019 Deloitte The Netherlands Insert your footer here - confidential 3
Batch Numbering
Internal and External
• Automatic batch numbering can be activated separately for batch-managed materials that are
procured with an account assignment category in the PO.
• PTP Integration topic
• In FLS120 this was active for plant 1000
• Recommendation: Activate for NL01
• For each movement type you can set whether entry of a shelf life date is possible and whether
the system should run a check on the minimum required shelf life
• In inbound deliveries, batches can be created automatically or the user can create batches using
a pop-up, where, the manufacturing date / SLED and COO can be entered
• The minimum remaining shelf life should then be maintained in the material master data (if not
maintained, no validation is performed. It is not mandatory)
• The shelf life expiration date can be calculated automatically based on the goods receipt date, if
a total shelf life is maintained in the material master data
• If the SLED is to be maintained, the shelf life can be entered manually or calculated based on the
manufacturing date. This is a material + plant level setting
• Recommendation movement type 101: Enter and check
• Recommendation deliveries: Batch installation + classification, SLED check.
• Batch classification is required to use the batch determination functionality. If classification takes
place, batch characteristics are filled in the batch master
• While creating new batches in inbound deliveries, classification can take place in the foreground
or in the background
• Manufacturing date, SLED, last Goods Receipt date, next check date, external batch number,
batch vendor, Status, can be filled in in the batch characteristics automatically
• Country of origin can be entered in a batch, but it will not automatically be filled as a
characteristic that can be used in batch determination. If this is required, a user exit is available*
• Recommendation: During the processing of inbound deliveries, classification should take place in
the foreground only for mandatory characteristics. No mandatory required
• When the user did not create a batch during delivery creation, EWM can automatically generate a
batch
• If any information (COO, Shelf life, etc.) needs to be maintained later on, the user can edit this
in the batch master
• Proposal EWM: Automatic batch creation without check. Teach users to create the batch when
creating the delivery, and if they forget they edit the batch directly in the batch master
• When creating a sales order or outbound delivery, the system can automatically select which
batches are to be picked on IM level
• This setting is activated per sales order item type or delivery item type
• The system searches for batches based on a condition record indicating:
− Batch selection criteria (Only batches with certain characteristics are to be selected)
− Batch sorting criteria (Batches are sorted for selection based on a certain characteristic. E.g.
SLED)
This search procedure consists of one or more condition types (also called strategy types):
The condition types are assigned to access sequences, defining at which level the condition can be
maintained. For example, a condition can be set at material level, or material + customer level:
Batch Determination IM: Master Data
o
The batch search strategy is maintained using the strategy / condition types as master data
o
In the batch search strategy you can…:
o Assign a sorting sequence (how available batches are sorted for selection)
o Define the selection criteria (if only batches with certain characteristics are to be selected)
• If the batch is not predetermined in the outbound delivery on IM level, it is also possible to
execute the batch determination in EWM
• The batch determination can also be executed in EWM using the same criteria as on IM level. A
prerequisite is that batch determination in IM is activated
• Recommendation: Do not pass on selection criteria to EWM. Manage batch determination in EWM
via picking strategies (see next slide)