1.

Define Batch Level:

We can set the batch level for batch management. Three unique options for a material are available:

 At plant level
 At material level
 At client level

If you choose plant level, the batch number is unique in conjunction with the respective material and the
plant. If you choose material level, the batch number is unique together with the material. At client level,
the batch number is unique in the whole client.

Note: If the material or client level for a material is chosen, check that no materials are in stock. If a
material exists in stock, the level may not be changeable.

2. Activate Batch Status Management:

The batch level should be set before the batch management is set to active. We can see Batch Status in
MSC3N screen if we activate Batch Status Management.

3. Activate Internal Batch Number Assignment:

In this configuration step, we setup the internal number assignment of batches to automatically active.
Path: Logistics General Batch Management  Batch Number Assignment  Activate Internal Batch
Number Assignment

4. Maintain Internal Batch Number Assignment Range

Respective Number range will be given for object

Path: Logistics General  Batch Management  Batch Number Assignment  Maintain internal Batch
Number Assignment Range

In the standard delivery, you maintain external and internal number ranges for the number range object
BATCH_CLT in Customizing under Logistics General Batch Management Batch Number Assignment
 Maintain Internal Batch Number Assignment Range / Maintain Number Range for External Batch
Number Assignment (transaction OMDA).

The number ranges assigned to a number range object cannot overlap. If you want to work with
overlapping number ranges, then you must create additional number range objects. In the customer
enhancements for batch number assignment, you define which number range object and number range
are used to determine the batch number. For more information, see the documentation on batch
management assignment in the Implementation Guide.

5. Creation of New Batches

In this configuration step, we can decide the batch creation is either manual or automatic or as per user
exit etc. This can be defined for each movement type

Path: Logistics - General  Batch Management  Creation of New BatchesDefine Batch Creation for
Goods Movements

Define Initial Creation of Data for Batch Master Transactions

Path: Logistics - General  Batch Management  Creation of New Batches Define Initial Creation of
Data for Batch Master Transactions

6. Batch Valuation

Path: Logistics - General  Batch Management  Batch Valuation Valuation for Goods Movement in
Inventory Management Activate Batch Classification for Goods Movements in IM

In this step, we specify for each movement type whether batch classification is possible during goods
movements and how it is to be carried out. If classification is activated, the object characteristics
contained in the batch class are assigned values automatically.

7. Batch Determination and Batch Check:

 Define Condition Tables

 Define Access Sequences
  Define Strategy Types

Define Inventory Management Strategy Types

 Batch Search Procedure Definition

Define Inventory Management Search Procedure

 Batch Search Procedure Allocation and Check Activation

Allocate IM Search Procedure/Activate Check

FIFO – First in First Out

FEFO- First Expiry First Out

8. Define Selection Classes (T Code - CL01)

In this step, we create class for the batch and assign the characteristics which were created with T Code
CT04. We assign this class to the Material under Class type 023

9. Define Sort Rules

a. Create Sort Sequence (T Code- CU70)

b. Change Sort Sequence (T Code- CU71)

In this step, we create Sort rule and assign respective Characteristic to the Sort rule. This sort rule will be
assigned to Batch Condition Record (T Code MBC1).

As per the sort rule, system will determine the order of Batch Numbers during Goods Movements

10. Configure Batch Where Used List:

Path: Logistics - General  Batch Management  Batch Where-Used List Make Settings for Batch
Where-Used List

This component determines how a batch is created and used in Production Planning PP through various
stages of production and displays the result in a list.

You can use this to find out:

 In which other batches a batch was used

 From which other batches a batch was created
This is important in the case of complaints and questions about product safety if the composition of
semi-finished and finished products must be documented across all production levels. The material type
is not important.

As well as batches, the system also displays production orders, manufacturing orders, subcontract
orders, and vendor batches. This enables you to trace a batch’s progress through each stage of
production.

The list is used for all plants but can also be restricted to certain plants. For batches in other areas, for
example Sales and Distribution (SD) or Warehouse Management ( LE-WM) , the Pick-Up List shows
where batches are used.

11. Shelf Life Expiration Date (SLED):

Set Expiration Date Check

Path: Logistics - General  Batch Management  Shelf Life Expiration Date(SLED)  Set Expiration
Date Check

Expiration date check will be activated at Plant Level. And we can keep specific settings for each
movement type. If the shelf life check expiration date check is active, you must enter the shelf life
expiration date or the production date of the material at the time of a goods receipt. At the time of
goods receipt, the system checks whether the remaining shelf life is sufficient. If this is not the case, a
warning or error message is issued, depending on the system settings.

When the goods receipt is posted, the shelf life expiration date is recorded in the material document.

Batch Creation manually – MSC1N/MSC2N/MSC3N

Batch Condition Records – MBC1/MBC2/MBC3

 Batch creation through Goods Receipt:

During 101, 501

 Impact of Total Shelf Life and Remaining Shelf Life in Material Master:

Remaining Shelf Life = SLED – Today’s Date

1. Characteristics

 DXBATCH_SLED
 DXBATCH_MFD
 DXBATCH_LASTGR
 DXBATCH_REMSHELFLIFE
 DXBATCH_BSTATUS

2. Class
 DX_BATCHCLASS

3. Sort Sequence

 DXBATCH_FIFO1
  DXBATCH_FEFO1

4. Strategy Type
 DX01

5. Batch Search Procedure

 DX0001
6. Batch Search Procedure allocation
Test Materials

1. 3993 ---- Without Remaining Shelf life and Total Shelf life
2. 3994 ---- Only with remaining Shelf Life
3. 3995 ---- With Both Remaining and Total Shelf Life

Test Case 1.

With Material 3993 (Without any Shelf life)

PO: 4500019225 (1000 Qty)

GRN: 5000001897 (400 Qty, Batch: 00001, GRN Date: 04.10.2018)

GRN: 5000001898 (200 qty, Batch: 00002, GRN Date: 03.10.2018)

GRN: 5000001899 (400 Qty, Batch: 00003, GRN Date: 02.10.2018)

Test Case 2.

With Material 3994 (Only with Remaining Shelf Life)

PO: 4500019226 (1000 Qty)

GRN: 5000001900 (200 Qty, Batch: 00004, GRN Date: 04.10.2018) (Expiry Date: 31.12.2018)

GRN: 5000001901 (500 Qty, Batch: 00005, GRN Date: 04.10.2018) (Expiry Date: 30.11.2018)

GRN: 5000001902 (300 Qty, Batch: 00006, GRN Date: 03.10.2018) (Expiry Date: 25.11.2018)

Test Case 3.

With Material 3995 (Both Remaining and Total Shelf Life)

PO: 4500019226(1000 Qty)

GRN: 5000001903 (200 Qty, Batch: 00007, GRN Date: 04.10.2018) (Expiry Date: 01.01.2019)

GRN: 5000001904 (400 Qty, Batch: 00008, GRN Date: 04.10.2018) (Expiry Date: 23.11.2018)

GRN: 5000001905 (400 Qty, Batch: 00009, GRN Date: 04.10.2018) (Expiry Date: 01.12.2018)

Test 4: Batch Determination based on GR date (FIFO)

We need to maintain Condition record for Batch Strategy Type.

Transaction: MBC1

Selection Criteria and Sort sequence need to assign.

MIGO

Goods Issue
Test Case 5: Batch Determination Based on Shelf Life Expiration Date(FEFO)

Material: 3994

MBC1

Maintain Selection criteria and Sort Sequence

MIGO

Goods Issue
Test Case 6: Batch Determination Based on Shelf Life Expiration Date(FEFO)

Material: 3995

MBC1

MIGO

Goods Issue
Test 7: Receiving Single Material with multiple Batches
Test 8: Batch Where Used List

Transaction: MB56