Chapter 10 Batch Management and Serial Numbers

• These notes cover key concepts related to batch management, serialization, and integration between SAP S/4HANA and EWM.

Batch Uniqueness

• Batch uniqueness can be defined at the material level, plant level, and client level for material.
• Material-level uniqueness: the material and batch number combination is unique across plants.
• Plant-level uniqueness: the batch number is unique for the material and plant combination.
• Client-level uniqueness: the batch is unique for the entire client.

Batch Management Activation

• If batch management is active at the material level, the plant level is automatically activated in the material master.
• Activating batch management at the material level makes it active for all transactions applicable to that material across all plants.
• If batch management is active at the plant level, batches must be specified for each plant where batch management is required.
• Possible levels where batch management can be activated in SAP S/4HANA are the material level and plant level.

Batch Classification

• Class type 023 is used in standard SAP to classify batches.
• Batch classification helps track physical, chemical, or technical properties.
• Classification is mandatory for batch determination.
• Standard characteristics for classification include shelf-life expiration date and country of origin; custom characteristics can also be assigned.

Documentary Batches

• Documentary batches are used to trace batches without inventory assignment.
• There is no batch master for documentary batches.
• Batch statuses (Restricted or Unrestricted) cannot be maintained.
• Batch classification and determination are not possible during picking with documentary batches.

EWM Stock-Level Attributes

• Country of origin and shelf-life expiration date characteristics are copied from SAP S/4HANA to EWM when a batch is created in SAP S/4HANA.
• These values are assigned to stock attributes, and can be maintained manually or via inbound delivery in EWM.
• Batch status is also assigned to stock attributes.
• These values are used during batch determination to select the appropriate batch based on search criteria.

Serialization Integration

• Harmonized and nonharmonized serialization are available to integrate serial numbers between SAP S/4HANA and EWM.
• Harmonized serialization: the same serial number profile defined in SAP S/4HANA is used in EWM.
• Nonharmonized serialization: warehouse-dependent or warehouse-independent serialization can be defined.
• For nonharmonized serialization, the serial number profile for the material is assigned at the material master warehouse management execution view; EWM reads the serial number profile at the client level.

Serial Number Requirements in EWM

• Serial number requirements in EWM are defined for document items on the warehouse number level, stock level, or inventory management level.
• Document item serialization: the serial number is assigned to the inbound or outbound delivery document item and can't be visible in EWM stock.
• Warehouse number level serial requirements: the serial number is entered at the time of goods receipt or issue but is only tracked at the warehouse level.
• Stock level or inventory management level: the serial number is entered for each warehouse logistics transaction, and stock is visible at the storage bin level.

Serial Number Handling

• It’s not mandatory to assign serial numbers at goods issue when the serial requirement is defined for the document item.
• For serialization at the stock level or inventory management level, the serial number must be entered for every EWM logistical transaction.
• Provisional serial numbers created in EWM must be replaced with actual serial numbers in subsequent inbound delivery steps.
• Provisional serial numbers are created in EWM if no serial numbers are entered at the time of goods receipt for inbound delivery and must be enabled in warehouse settings.

Batch Creation

• Batches can be created in both SAP S/4HANA and EWM.
• In SAP S/4HANA: During inbound delivery creation or using Transaction MSC1N during production/process order creation.
• In EWM: In inbound delivery using Transaction /SCWM/PRDI or directly through Transaction /SCWM/WM_BATCH_MAINT.
• For embedded EWM, batches created in SAP S/4HANA are immediately available in EWM.
• For decentralized EWM, batch information is distributed between systems.
• During inbound delivery of purchased products, it is preferable to create the batch number before the inbound delivery is saved in SAP S/4HANA.

Batch Distribution

• The BATMAS IDoc message type is used to distribute batch information between SAP S/4HANA and EWM.
• This distribution occurs via a batch job scheduled for each change pointer.
• For immediate replication, table /SPE/V_EWM_DEST can be maintained with “IDoc transfer.”

Shelf Life

• When only minimum remaining shelf life is maintained without total shelf-life days, it is mandatory to enter the shelf-life expiration date (SLED) during goods receipt.
• Minimum remaining shelf life warns users during inventory transactions if the remaining shelf life is less than the maintained number of days in the material master.
• If the total shelf life is also maintained, the system calculates the SLED from the manufacturing data or the goods receipt date.