You are on page 1of 27

SAP Batch derivation

Definition
Transferring batch characteristics values or batch master fields from the sender batch to the receiving batch is called Batch Derivation. The component batches can pass on their Field values/characteristics values to the manufactured batch. Events at which the copy of characteristics values to the manufactured batch is possible = At Goods Receipt of the manufactured quantities At Release of order At Usage Decision At Batch Creation

Batch Derivation Example


The following is an example of batch derivation at production order or process order release.

Production order / Process order = 1000120 for Material M1

Step 1: Define the transfer characteristics from the issued or sending component batches to the manufactured batch.

Issued Component C1

Batch B1

Concerned Characteristics COLOR WIDTH LENGTH HEAT NUMBER COLOR WIDTH LENGTH

Value RED 2M 10 M H1 RED 3M 10 M

Require Transfer NO YES YES YES NO YES YES

Logic

Move Average Value Move Average Value Move the Minimum

B2

Move Average Value Move Average Value

HEAT NUMBER

H1

YES

Move the Minimum

Step 2: At Goods Receipt of the order or at Release of the manufacturing order or at usage decision, the transfer of characteristics can be triggered from the sending batch/es to the receiving batch/es.
Manufactured Material M1 Batch BX Concerned Characteristics DIAMETER WIDTH LENGTH HEAT NUMBER Value 5 MM 2.5 M 10 M H1 Whether Copied over

Move Average Value Move Average Value Move the Minimum

SAP Batch Derivation Types


There are 2 types of Batch Derivations, Pull and Push Batch Derivation.

Pull Derivation

Pull derivation exists when there are multiple sender batches and one receiver batch. Batch Master Characteristics values or Batch Master Field values can be transferred to the receiver batch from the sender batch. For a given characteristics either its value from the first batch can be copied over or an average value can be copied over to the receiver batch. Pull Derivation = Many Senders >>TRANSFERRED>> One Receiver = n senders

1 Receiver

Push Derivation

When there are many receivers and 1 sender. You have to choose whether the batch derivation is a push derivation in the sender condition record. An example of Push derivation can be: When you procure a component batch and use it to produce chemical products which are produced in bulk and stored in various bulk containers marked with unique batch numbers, in this case you if you want to transfer a component batch characteristics value or component batch master fields to the receiver batches, then you can do so using Push Batch Derivation.

Push Derivation = One Senders >>TRANSFERRED>> Many Receiver =

1 senders n Receiver

Steps in Settings up SAP Batch Derivation


One can use the following steps to set up batch derivation in SAP.

Step 1:

Activate Batch Where used list One should activate the Batch where used list, in the configuration with the BaWU Synchron.posting indicator on Allowing the system to figure out the sending batches and the sending characteristics values. There is no Transaction code for this, you have go to Logistic General >>> Batch >>> Batch Where Used List.

Step 2:

Batch Derivation Activation Batch Derivation should be active in configuration so as to use this functionality. Use transaction code DVSP.

Step 3:

Setting Batch Derivation Search Procedure Techniques

It becomes really impossible for us to inform the system about the sending batch number (for each and every batch) and the characteristics/rules to transfer to the receiving batch number/s. Thus we use the batch search procedures and conditions records to direct the system so that for all the sending material batches at the plant level should be considered in the search and its data should be transferred to the receiving material batches. A similar condition record should be set for the receiving side so that all the material batches at the receiving plant level should be considered in the search and they should receive the characteristics data. Setting the sending condition on sending plant and the receiving condition on the receiving plant is just an example. You could define the levels at which condition records should be defined through the standard condition table and access sequence configuration SAP makes it easier for the users to make various combinations of levels for the sending party and the receiving party, to do this you should choose the condition fields as supplied by SAP and create a condition table and use these tables or key combinations to assign them in an access sequence with priorities. This suggests that you can make use of more than one key combination assigned in priorities so that if the condition record for one combination is not found, the system can make use of the next condition record to search for the sending batches and the receiving batches involved in the transfer. Once the Condition tables, access sequences, strategy types, and search procedures are configured for the sending party and the receiving party, you should then create condition records at the defined levels or defined key combination, for the sending party and the receiving party. For example If the sending key combination or sending condition record is to be defined at the sending material-plant level, then you should define the actual sending material and the sending plant in the condition records and the characteristics involved in the transfer. On the other hand you should also define the condition records key combination for the receiving party, for example if you make a definition at the receiving material-receiving plant level; you should enter the actual receiving material and the receiving plant involved in the derivation, to help the system to search for the receiving batches. While you create the receiving condition records, you should maintain a set of transfer specific rules i.e., if the sender field/characteristics value is empty or the sender is overwriting any

existing characteristics values in the receiving batch then should it error out the transfer or issue an warning or do nothing and on the other hand you can direct the system to send minimum/maximum/average value of the sender characteristics if there are more than one sender batches or more than one value is defined for the characteristics in the sending batch. The Batch derivation procedures and the condition records, for the sending party and the receiving party, which are set, it helps the search for all the concerned sending batches and the receiving batches, and identifies the rules defined in them, so that the characteristics values can be transferred to the receiving batches.

Steps in setting up Batch Derivation Condition techniques

1. Create Sending Condition Tables

SAP provides a set of standard key combination sets or preconfigured sending condition tables. Conditions tables are created with a combination of conditions field all provided. You cannot add your own field. Each Condition table contains a key combination. You can alternatively create your own sending key combination/condition tables other than that provided by SAP as shown above, by creating a custom sending condition table. Following set of sending conditions fields can be used to create your own sending key combination or sending condition table (Use configuration Transaction code DSC1): Receiver Material Receiver Material Type Sender Material Sender Material Type Sender Plant The key combinations or condition tables (for the sender) as provided by Standard SAP are as below: Sender Material Number (Table 010) Sender Material Type (Table 011) Receiving material + sending material (Table 012) Receiving material type + sending material type (Table 013) Sending Plant (Table 502) You can create your own condition table 901 with the following condition fields Sending material + Sending Plant (Table 901)

2. Create Receiving Condition Tables

SAP provides a set of standard key combinations set in preconfigured receiving condition tables. Conditions tables are created with a combination of conditions field all provided. You cannot add your own condition field. Each Condition table contains a key combination. You can alternatively create your own receiving key combination/condition tables other than that provided by SAP as shown above, by creating a custom receiving condition table. Following set of receiving conditions fields can be used to create your own key combination or receiving condition table (Use configuration Transaction code DRC1): Material Number Material Type Receiving Plant The key combinations or condition tables (for receiver) as provided by Standard SAP are as below: Receiving Material Number (Table 001) Receiving Material Type (Table 002) Receiving Plant (Table 501) You can create your own condition table 902 with the following condition fields Receiving material + Receiving Plant (Table 902)

3. Create Sender Access sequence,

Create Sender access sequence so as to help in searching the attributes of the sender batches. Some field key combinations or sending condition tables are already grouped together in priority sequence in the standard SAP Batch derivation access sequence BDS1. The field combination which are set in a priority sequence in the configuration represent the field key combination that would be used to create the master data for sending party, which in-turn would help in searching the attributes of the sender batches. If you choose to create your own access sequence, you may do so; when you do that you have to assign the sending condition tables in your own defined priority sequence. Transaction code is DSC5 to create access sequences in configuration.

SAP offers the following receiving condition tables (key combinations) for use in the access sequence BDS1 arranged in a priority: 10 Receiving material + sending material (Table 012) 20 Sender Material Numbers (Table 010) 30 Sending Plant (Table 502) You can create your own sending access sequence arranged in a required access sequence: You can call this sending access sequence as ZDS1 10 Sending Plant (Table 502) 20 Sending material + Sending Plant (Table 901)

4. Create Receiver Access sequence,

Create receiver access sequence to search for the attributes of the receiver batches. Some field key combinations or receiver condition tables are already set up in the standard SAP Batch derivation access sequence BDR1. The receiver condition tables which are set in a priority sequence in the configuration represent the field key combination that would be used to create the condition record master data for receiving party, containing the characteristics and rules, which in-turn would help in searching the attributes of the receiver batches. If you choose to create your own receiver access sequence, you may do so; when you do that you have to assign the receiver condition tables in your own defined priority sequence. Transaction code is DRC5 SAP offers the following receiving condition tables for use in the access sequence BDR1 arranged in a priority sequence: 10 Receiving Material Number (Table 001) 20 Receiving Material Type (Table 002) 30 Receiving Plant (Table 501) You can create your own receiving access sequence arranged in a required access sequence: You can call this sending access sequence as ZDR1 10 Receiving Plant (Table 501) 20 Receiving material + Receiving Plant (Table 902)

5. Sending Condition Type (Strategy type)

Sending Condition types is created to assign the sending access sequence to it. Standard SAP already has done this for you. In SAP, the standard sending condition type BDS1 is created and assigned to the standard sending access sequence BDS1.

Transaction code is DSC6.

6. Receiver Condition Type (Strategy type)

Receiver condition types are created to assign the receiving access sequence to it. Standard SAP already has done this for you. In SAP, the standard receiving condition type BDS1 is created and assigned to the standard receiving access sequence BDS1.

Transaction code is DRC6.

7. Sending Batch Derivation Search Procedure

Sending Batch Derivation Search Procedure contains the sending Condition type. Various condition types are assigned in a priority sequence for use for searching the sending batches and its data.

Note: You can choose to assign more than one condition type set in a priority while building a search procedure. Transaction code is DSC7.

8. Receiver Batch Derivation Search Procedure

Receiver Batch Derivation Search Procedure contains the receiving Condition type. The various condition types are assigned in a priority sequence for use for searching the receiving batches. Note: You can choose to assign more than one condition type set in a priority while building a search procedure. Transaction code is DRC7.

Step 4:

Define the Batch Derivation Event

Defining derivation event would tell the system of a business event to trigger batch derivation, i.e., a point in time to transfer batch characteristics values from a sender batches to a receiver batches. The transaction code to configure the derivation events is DVC8. To configure the batch derivation event, the following information is fed to the system: A) When do you want to trigger the batch derivation? The answer to this question decides when you would wish to trigger the batch derivation

@ Release of production/process order @ Goods receipt from production/process order @ Usage Decision @ Manual Batch Derivation @ Batch Master creation

B) What would be the Sender/Receiver Batch Determination Procedure?

The answer to this question decides the search of the sender batch and the receiver batches to copy/compute the batch characteristics values for the receiver batches.

Assign a Sender Batch Derivation Search Procedure Assign a Receiver Batch Derivation Search Procedure

C) What is the type of Batch Derivation?

The answer to this question decides what would be the type of Batch Derivation that is required for business use.

Static batch derivation transfers the characteristics values of the sender batches to the receiver batches. A derivation log is generated in the derivation Monitor. Dynamic batch derivation does not transfer the characteristics values of the sender batches to receiver batches, it only simulates the transfer. The receiving batches are not automatically updated with the transferred values; you would have to manually change it.

D) Do you want to display the batch derivation results The answer to this question decides whether the derivation results are displayed.

Display in Errors Hide when ok Always Display Always Hide

Following steps can be followed to implement batch derivation in your organization:

Step 5:

Creating Sending Condition Records or Sending Batch search Strategies

When you configure the system till the creation of batch derivation search procedures for both sending and receiving parties, you would eventually create the master data for the sending conditions. To create the sending condition records you should follow the process as below using the transaction code DVS1/DVS2/DVS3: Choose the batch derivation strategy from the drop down >>> Then choose a key combination as set in access sequence >>> and then create the sending batch derivation strategy master data by

entering values for the condition fields of the key combination >>> Enter the characteristics that you would want to transfer the values from the sending batches >>> Save. There is not much of data entry when you create the sending condition record apart from assigning the characteristics for which values are to be transferred to the receiving batches. You can set master data for more than one key combination (a key combination decides the master data level at which the master data is created), but the system at the time of execution would first access the first condition key combination and check whether the master data exists for the sending batches, if the sending batches are not found using the first sending condition record master data, the system would check whether the master data for the sending batches exists for the second key combination condition and if the batches are not found using the master data under the second sending condition records then it will go to the next key combination in the access sequence and search whether master data for the sending batches is created for the third key combination, so on and forth.

Step 6:

Creating Receiving Condition Records or Receiving Batch search Strategies

When you configure the system till the creation of batch derivation search procedures for both sending and receiving parties, you would eventually create the master data for the receiving conditions. To create the receiving condition records you should follow the process as below using the transaction code DVR1/DVR2/DVR3: Choose the batch derivation strategy from the drop down >>> Then choose a key combination as set in access sequence >>> and then create the receiving batch derivation strategy master data by entering values for the condition fields of the key combination >>> Assign the characteristics for which you want to receive the characteristics values >>> Assign rules for the characteristics. The Rules for the receiving characteristics are concerned with the following sending characteristics attributes:

While you create the receiving condition records, you should maintain a set of transfer specific rules i.e., if the sender field/characteristics value is empty or the sender is overwriting any existing characteristics values in the receiving batch then should it errorout the transfer or issue an warning or do nothing and on the other hand you can direct the system to send minimum/maximum/average value of the sender characteristics if there are more than one sender batches or more than one value is defined for the characteristics in the sending batch.

You can set master data for more than one key combination (a key combination decides the master data level at which the master data is created), but the system at the time of execution would first access the first condition key combination and check whether the master data exists for the receiving batches, if a receiver batch derivation master data does not exists for the first key combination and the system fails to search the receiving batches using this condition record, it would further check whether the master data for the receiving batches is covered in the second key combination condition and if the master data does not exists under this given condition then it will go to the next key combination condition in the access sequence and search whether master data for the sending batches is created for the third key combination conditions, so on and forth.

Step 6:

The Actual Derivation

Once the batch derivation configuration is done and the master data is set, the derivation is triggered at the point where it is defined for. SAP issues messages of success or error or information when the derivation finishes. You can define in transaction code DVC8 Batch derivation Event configuration, if you want such messages to be popped-up after the derivation.

Batch Determination
Define Batch Determination
Batch Determination is used in inventory management, production, sales and distribution, warehouse management. It is used to select batches and allocate the same in a manufacturing order or in an outbound delivery or in a goods issue/goods transfer in inventory management.

In Production, Sales & Distribution, in inventory management or in warehouse management, batch determination is used to search and allocate batches for the components in production order/process order or to search and allocate the delivery batches in a customer based outbound delivery or to search for batches and allocate batches in goods issues. The tools that batch determination uses is the determination condition techniques based on the condition tables, access sequence and strategy types. These condition types are enough to choose and allocate batches. Though additionally batch determination uses selection classes and its characteristics values to choose batches and/or uses sorting rules to choose sort batches while selection based on characteristics and its values. We have already learnt in batch derivation documentation, how the search procedures condition techniques help in searching the sending batches and receiving batches and thus derive the transfer of characteristics values. Similarly you can use the search procedures techniques to search and select batches during batch determination.

SAP Batch Determination Condition Techniques


You can follow the steps as below to create Batch Search Procedure Techniques:

First Step Create Batch Determination Condition tables

Batch determination condition tables once created become the key combination fields for searching batches. Eventually the condition records or search strategies are created as master data based on these key combinations. The Condition Tables are created separately for IM, Production, WM and Sales.

Second Step Create Batch Determination Access sequence

Batch determination access sequences have multiple condition tables (key combinations) assigned in a sequence of priority. This facility allows you to create data for many key combinations so that even if the search of batches fails on the first key combination condition the rest in the priority would help in search. The Access Sequences are created separately for IM, Production, WM and Sales. The below screen-shot shows all the screens involved in the access sequence configuration.

Third Step Create Batch Strategy Types

Batch Search Strategy holds multiple access sequences, though not assigned in any sequential priority. The assignment of the strategy types is separately for IM, Production, WM and Sales. The strategy types or condition types are assigned in priority in the next step called Batch Search Procedure Definition. The strategy types configuration holds the selection criteria and the sort rules used in batch determination techniques. Strategy types are used ultimately to create the batch search master data or batch search condition record so that the system would know the exact level at which search for batches is to be carried out along with the selection/sort rules of these batches. It is obvious that batch search strategy is used to search batches on certain rules, because you want to automate the process and do not want it to do it manually for each and every batch. Thus you have to aid the system in putting in a decision such as - search all the batches of a given plant or search all the batches of a given set of material at a plant or search batches for a given component or etc.

Additionally the system gets a help from the selection criteria or the sort rules to select and sort the batches for a characteristics value. Though the selection criteria and the sort rules are optional if the condition tables and the strategy types are enough to search and assign the batches

to the business objects. The selection and sort rules can be defined separately and assigned to the strategy type. See the explanation below: Create Selection class (Optional in Batch Determination) Selection class is used to help the system choose a certain batch based on the characteristics and their fixed values. Therefore when you create a selection in SAP using transaction code BMC1 (BMC2/BMC3). You would then assign the selection class to the strategy and use the same in the condition record master data. In the condition records you need to enter the required fixed values against any class characteristics that you would want to use to search the batches. Create Sort Rules (Optional in Batch Determination) Sort Rules are used to help the system sort the batches for the given class characteristics. When you create the sort rules in Batch determination, you would select the characteristics on which you would want to sort the batches for selection and assignment to an object. The characteristics on which the sort rules are based upon (LAST_GR) is shown in the screen-shot below.

Fourth Step - Create a Batch Search procedure

A Batch Search procedure holds multiple strategy types assigned in sequential priority. The Batch search procedure thus becomes the final configuration which holds the total search configuration together. The Batch Search Procedures are created separately for IM, Production, WM and Sales.

Fifth Step - Batch Search Procedure Allocation and Check Activation

In this step you allocate the batch search procedure to the respective modules. In the case of inventory management, the Batch search procedures are assigned to the Movement types. In the case of production or process order, the batch search procedures are assigned to the production plants and order types. In the case of Sales and Distribution the Batch Search Procedures are assigned to the Sales Areas and Sales document type. In the case of Warehouse Management, the Batch Search procedures are assigned to the Warehouse number and they can be also assigned to the warehouse number + Movement type combination. The below screen shot shows the batch search procedure assigned to various SAP logistical areas. There are 4 screens illustrated in one screen shot below.

Sixth Step Creation of Batch Search Condition records or Batch Search Strategy

When the entire configuration for batch search condition techniques is done, you would create the Batch search condition records using varied transaction codes: For Inventory management - MBC1 Create, MBC2 Change, MBC3 Display For Production order/Process order - COB1 Create, COB2 Change, COB3 Display For Sales and Distribution - VCH1 Create, VCH2 Change, VCH3 - Display For Warehouse Management - LS51 Create, LS52 Change, LS53 Display

The Batch Determination Search Strategy or Condition records can be created as below:

Step 1: Enter the Strategy Type For example C001 in Production order Scenario

Step 2: Press Enter

Step 3: A Key combination is provided by the system to choose from. Choose a Key combination for which you want to create the condition record for. The Key combination in this case is Order type + Plant + Component.

Step 4: Enter the Values for the order type, plant and the component combination for which you want the system to search the batches during batch determination. Also enter the Validity Period for which the Batch Master Strategy would be valid and can be used by the system. Enter the values of the following fields while creating the batch strategy master data or you can also have the values of these fields brought in from the Batch strategy type configuration

Number of allowed Batch splits Enter the allowed number of batch splits during batch determination. Batch splits specifies the number of batches that can be picked so as to satisfy the requirement quantity. Select the Change allowed indicator If you want the number of batch splits to be flexible and it can be changed as per the situation, so as to satisfy the quantity required. Over delivery Allowed If you select this indicator, the batch split can pick up batches whose batch quantity could possibly exceed the requirement quantity. UOM to display the batch quantities in, during the batch determination process. It could be in stock keeping UOM or in unit of entry of the document. Select the Dialog for Batch determination If the batch determination is run in the foreground and if you want the results of batch determination to pulled-up in a dialog box, you should select this indicator. Forget this indicator if batch determination is always carried out in the background. Routines You can assign Routines to help in quantity proposal. If there is no special routine that you have created for batch determination then you can set this field with a default value as 1. Routines in SAP would carry out certain functions. For example you can write a routine to select the batches in batch determination based on your own special rules and logics which cannot be covered by search procedures, selection classes and sort rules. Selection Type Specifies the following options which are self explainable. Immediate selection according to selection criteria No selection at beginning of batch determination Selection with no selection criteria Selection criteria cannot be changed in batch determination

N O F

Step 5: If you are working with selection classes, you can assign the characteristics values for which you want the system to select the batches during batch determination as shown in the screen shot below. If you are working with Sort rules as well, you can assign a sort rule (create the sort rule before you create the Batch Search Strategy).

Illustration of Batch Determination Condition Technique Configuration

This particular Illustration of Batch determination condition techniques configuration is shown for SAP PP/PPPI.

Step 4: Create Batch Search Procedure 0010 CO0001 10 ZP01 (Existing Standard SAP Batch Search Strategy) 0010 ZP0001 10 ZP01 (Assign here - Batch Search Strategy Z001) Step 3: Create Batch Search Strategy Z001 (Assign Here Access Sequence Z001) C001 (Existing Standard SAP Search Strategy) Step 2: Create Access Sequence 0010 Z001 10 901 ZCD1 (Assign Here Condition Tables ZCD1) 0010 Z001 20 902 ZCD2 (Assign Here Condition Tables ZCD1) 0010 Z001 30 903 ZCD3 (Assign Here Condition Tables ZCD1)

Step 1: Create Condition Table 901 ZCD1 (Choose Here Condition Fields from a set provided) Choose Condition Fields Plant Step 1: Create Condition Table 902 ZCD2 (Choose Here Condition Fields from a set provided) Choose Condition Fields Component + Plant Step 1: Create Condition Table 903 ZCD3 (Choose Here Condition Fields from a set provided) Choose Condition Fields Order type + Plants + Manufactured Material + Component

Pre-requisite for SAP Batch Determination in SAP PP/WM


When you want to use batch determination in SAP PP/WM you should also use the Batch Entry Field in MRP3 View: For the Batch Determination to work in production order for the components, you should have a value for the batch entry field. The values if set to 3 will carry out batch determination

automatically and if set to blank will not carry out batch determination for the components in the production.

Batch Determination in Logistical areas

Batch Determination In Production


Batch determination is used in production to search for component batches in the production order or in the process order component list. It also reserves the batches for the production order. These batches once assigned get included in the reservation list created for the order. The selection of inventoried component batches can be based on the simple batch search procedure techniques with or without the selection class and sort rules. Determination of batches can be an automatic procedure or can be triggered manually. Note that:

The components should be batch managed If selection rules and sort rules are to be applied for determination of batches, the components should be classified with a class. Most of the times the selection is on Batch Class. Though you can select on the basis of any other class.

For the batch search procedure to work as per your conditions records, selection rules and sort rules, you should configure batch determination in Production order and/or Process order (as per the type of manufacturing set up) and maintain the required master data: a) Create the required configuration for Batch search procedures using the path Logistics >>> Batch Management >>> Batch Determination and Batch Check b) Then assign Production order and/or Process order Batch search procedure to the Order type and Plant combination using the path -- Logistics >>> Batch Management >>> Batch Determination and Batch Check >>> Batch Search Procedure Allocation and Check Activation >>> Assign Search Procedures to Production and Activate Check c) Create condition records in the front end using transaction code COB1 (Change/Display - COB 2/ COB3)

Example:

As a simple example, you would want to manufacture a product M1 with batch managed components C1, C2, C3; out of which you would like to have the system automatically select batches for the product C3 based on the following rules: The selection classes and the sort rules can be illustrated as below:

Select Batches which has a selection class (Batch Class) called as = ZCOMPONENT. This batch class should have been assigned to the component The Values of the following characteristics are entered while creating the selection class. The other characteristics which exist in the class are not used for selection purpose.
o o o o

pH = <=3 COLOR = RED LOBM_RLZ = < 100 Days (Remaining Shelf Life for Batch) LOBM_ZUSTD = Released (Standard Characteristics for Batch Status)

Though please note that use of selection class is optional; this example uses selection class since the business process demands. Depending upon the batch master strategy or the condition record created for a given production order or process order strategy type (for example with a key combination = Manufactured Material + Plant + Component) and depending upon the selection class rules set for the selection classes, the system would select the component batches.

Selection of the component batches should also be based on a FIFO Sort rule (First In First Out) so that the component batches lying in stock do not age out. To do this you would create the sort rule with a Characteristics LOBM_HSDAT (Date on which batch was produced) placed in ascending order and FIFO_LAST_GR_DATE (which is a reference characteristics referencing the field last GR data MCHA + LWEDT) also placed in ascending order of selection. ZSORT_SEQ_1 Production Order Component Selection Sort Sequence Characteristics LOBM_HSDAT FIFO_LAST_GR_DATE Ascending/descending Ascending Ascending

Batch Determination In Sales and Distribution


Batches can be assigned to the quantity based contracts or in quotations early in the process so that they can be reserved for the customer. Though assigning to these objects can lock your inventory, thus disallowing it to be used for any other customer delivery. Similarly in the sales order, you can assign the batches through automatic determination based on condition techniques supported by selection classes and/or sort rules. You could have the determination done manually as well in the sales order. Assignment of the batches to the Sales orders is required if the customer requests batches of a certain specification set or if you want to choose batches in the sales order based on certain sort rules or based on certain characteristics values maintained by you to classify the inventory. Since there is no Batch Split in Sales order Batch determination allowing the system to assign multiple partial batches, the system finds itself incompetent to assign multiple partial batches to satisfy the sales order line item demand. Even though with such as shortfall in functionality, if you still want to allocate batches to the sales order line item through Batch determination you can do so and call the batch selection screen through manual batch determination and have the batches chosen manually to satisfy the quantities. Whereas In Outbound Deliveries, you can use Batch determination and have the system allocate batches or pick the batches. The Good News is that outbound delivery has the functionality of Batch split and allocation of multiple batches to satisfy the sales order line item quantity. Having Batch determination late in the sales business process would make sure that the inventory is not locked up for a very long time. Batch determination in the outbound deliveries can be triggered manually or can be automated as per the configuration. You can also change the determined batches and overwrite the same till they are issued to the customer. Batch Determination in outbound deliveries can be made using the condition techniques, the selection classes and the sort rules. Follow the example below to know more about batch determination in outbound deliveries.

For the batch search procedure to work as per your conditions records, selection rules and sort rules, you should configure batch determination in Sales and Distribution and set up the required master data: d) Create the required configuration for Batch search procedures using the path Logistics >>> Batch Management >>> Batch Determination and Batch Check

e) Then assign Sales and Distribution Batch search procedure to the sales area and document type using the path -- Logistics >>> Batch Management >>> Batch Determination and Batch Check >>> Batch Search Procedure Allocation and Check Activation >>> Allocate SD Search Procedure/Activate Check f) Create condition records in the front end using transaction code VCH1 (Change/Display - VCH2/VCH3).

Example:

If you want to carry out batch determination for all the materials that are sold out of the plant through an outbound delivery, then you can create a condition technique with or without the selection classes and sort rules. Though in outbound delivery batch determination, most of the customers would mandatorily base their batch allocation on selection classes, values of the characteristics in these classes and sort rules. The selection classes and the sort rules can be illustrated as below:

Select Batches which has a selection class (Batch Class) called as = ZCOMPONENT. The Values of the following characteristics are entered while creating the selection class. The other characteristics which exist in the class are not used for selection purpose.
o o

LOBM_RLZ = < 20 Days (Remaining Shelf Life for Batch) LOBM_ZUSTD = Released (Standard Characteristics for Batch Status)

Though please note that use of selection class is optional; this example uses selection class since the business process demands.

Selection of the finished product batches should also be based on a FIFO Sort rule (First In First Out) so that the batches lying in stock do not age out. To do this you would create the sort rule with a Characteristics LOBM_HSDAT (Date on which batch was produced) placed in ascending order and FIFO_LAST_GR_DATE (which is a reference characteristics referencing the field last GR data MCHA + LWEDT) also placed in ascending order of selection. ZSORT_SEQ_2 Outbound Delivery Selection Sort Sequence Characteristics LOBM_HSDAT FIFO_LAST_GR_DATE Ascending/descending Ascending Ascending

Batch Determination In Inventory Management


It is logical that for all the movement types which are involved in goods issue, you would want to search for batches from inventory. The business processes can be goods issue to production order or process order, transfer posting, return to supplier etc. For the batch search procedure to work as per your conditions records, selection rules and sort rules, you should configure batch determination in inventory management and set up the required master data: g) Create the required configuration for Batch search procedures using the path Logistics >>> Batch Management >>> Batch Determination and Batch Check h) Then assign Inventory management batch search procedure to the movement types using transaction code OMCG (Logistics >>> Batch Management >>> Batch Determination and Batch Check >>> Batch Search Procedure Allocation and Check Activation >>> Allocate IM Search Procedure/Activate Check) i) Create condition records in the front end using transaction code MBC1 (Change/Display - MBC2/MBC3).

If you want to be generic, you can have the condition tables set at the Plant level or Movement type + Plant level; whereas if you want to be more specific or detailed you can have the condition tables set at Movement type + Plant + Material level. On the other hand, if you have forgotten to enter any batch determination condition techniques or if you have forgotten to assign them to the movement types, the system would eventually carry out an availability checks and choose a batch for you (for which you would have to put an asterisk - *, in the batch field while creating the goods movement. Use in Inventory Management - When you create the goods issues, you can enter an Asterisk * in the Batch Field and expect the system to throw up a batch number. Putting an asterisk would provide an available batch number from the stock or provides a batch number as per the batch search condition techniques set. And if you have forgotten to configure batch determination in inventory management, the system would search the batches based on standard availability checks and provide you with a batch number.