SAP BOM Test





SAP Bill of Materials


SAP BOM Definition



Bill of Materials is used for production or subcontracting or sales activities. It gives you a list of components required to manufacture a product for a given base quantity.

It is normally created by the product development team and changed over the product life-cycle by the same team.

A simple day to day example would be, to make 1 cup of Milk Coffee, you would need a list of materials, like 6 gm of Sugar, 4 gm of Coffee Powder, 0.3 Litres of Milk and some units of Gas (to boil the milk). In this example the base quantity is 1 Cup of Milk Coffee. Based on this example if a vendor sells 500 Cups of Milk Coffee every day, he would need to procure 3000 Tea Spoons of Sugar, 500 Sp

Uses - A Bill of Material contains the list of components/sub-assemblies required in desired quantities to produce a certain base quantity of the header material


If this is the definition of a Bill of Material, it can be used by MRP or Production order to evaluate the components and their quantities requried for production


MRP uses BOM to evaluate the components requried and computes the shortages of the same to trigger procurement


SAP BOM Types


You can create the following BOMs in the SAP - SAP BOM Types




· Material BOMs - We will Discuss Material BOMs only under SAP PP.

· Equipment BOMs

· Functional location BOMs

· Document structures

· Order BOM

· Work breakdown structure (WBS) BOM




Single level BOM & Multi Level BOM



With the use of the Bill of Material master data, you can create a list of materials required for producing an end product. The end product can be an assembly or a sub assembly.



Bill of materials in SAP is always created as single level bill of materials. Each level that is produced individually is represented by a Single Bill of Materials. All these relevant individual Single BOM subassembly levels if joined together form a Multi level BOM.



In general every product that is to be manufactured or subcontracted in SAP has a single level BOM. A combination of single level Bill of material exploded from top to bottom is called a multilevel Bill of Material.



For example



The Single level Bill of material of an Assembly “A” is as below



A (Base qty = 1 EA)



> B = 2 EA (Raw Material)



> C = 2 EA (Assembly)



The Single level Bill of material of a subassembly “C” is as below



C (Base qty = 1 EA)



> E = 1 EA



> F = 5 EA



A Multi level Bill of material for “A” would then be as below. A Multi level Bill of material is created through joining many single level Bills of materials as shown below.

A multi level bill of material is used to evaluate the multi level component requirement for producing the header material. A multi level BOM is used by the MRP system to evaluate the Material Requirements.



A (Base qty = 1 EA)



> B = 2 EA (Raw Material)



> C = 2 EA (Assembly)



> E = 2 EA (for producing 2 of “C” you would require 2 of “E” and 10 of “F”)



> F = 10 EA




Group BOM



When a BOM for a material remains the same regardless of the plant it is produced in, it is wise to create a central level BOM which has no reference to any plant, such a concept in SAP is called "GROUP BOM". You can then extend these Group BOMs' to all the plants where it is required. Thus you end up referencing the Group BOM to the plants rather than creating one at the plant which can be time consuming.



When you create a Group BOM, the system uses MARA level or client level materials. A specific material need not be extended to any plant for creating a Group BOM.



Creating a Group BOM - When you create a Group BOM you can use the same Transaction code CS01 to create it, but just ignore entering the plant code.



Extending a Group BOM - Using Transaction code CS07 you can extend the Group BOM to the plant, while doing this you have enter the plant at the bottom of the selection screen and not the plant option in the field number 2 of the selection screen.



Changing or Deleting and Extension - You can also delete an extension to a plant using transaction code CS08.




Alternate Bill of Materials



If you have a product that requires many Bill of materials because:



a) of use of varied components periodically or seasonally

b) of use of varied component quantities periodically or seasonally

c) of use of varied components for producing a certain lot size of production

d) of use of varied components quantities for producing a certain lot size of production



You should then go and create that many bill of material for the same product. This is possible through SAP BOM alternates.



Every time you create the first alternate SAP allocates the BOM Alternate number as “1”, the second alternate would get the BOM alternate number as “2” so on and so forth. You can create upto 99 Alternates for a material.




Creating a Bill of Material



To create a Bill of material (SAP BOM), you need to enter the following in the selection screen:



Selection Screen






Material

Enter the material number for which you are creating the Bill of materials.



Plant

Enter the plant; if you are creating plant specific Bill of Materials.



Validity Dates



When you are creating a Bill of Material, you have to “Valid from date” as today’s date or the BOM creation date. It is always wise to enter the “Valid from date” which is before or equal to the Work center validity date, the cost center validity date and the production version validity date.



BOM Usage



Enter the BOM usage, which would specify the ultimate use of the BOM, i.e., a BOM whose usage is production can only be used in production or SAP PP, a BOM whose usage is Sales and Distribution can be used only for explosion in SAP SD (for example - variant configuration purposes and a Maintenance BOM would be used for Maintenance orders and a costing BOM will be used of costing purposes only to evaluate the product cost.



Therefore we can say that a BOM usage decides the end use of the BOM.



A BOM with a “Universal Usage” can be used for Production, Sales, costing, maintenance.






BOM Item Overview







Item number:

Since SAP gives you a facility to include Material components, texts, documents in the bill of materials, they need to be arrange sequentially one below the other, to do this you need to give an item number to each of the items added in the bill.

The standard number range for this number in increments of 0010.



Item Category



Therefore it is clear that a BOM is not only a list of components that is required to manufacture a product, but it also allows you to include texts, documents as items in the list. Therefore to avoid any confusion on what is the category of the item that is added, there is something called item category.







An item that is added can be a Material component - available in Stock item (something that would always be available in stock) or a Non-stock item (something that would never be available in stock and needs to be procured when the production order is created), or a Variable size item, which is designed with a length, breath and height, or an Intra material which is produced intermediately in the production processes and is consumed in the process. It only lasts momentarily in the process (this qty is added with a negative sign)



An item that is added can be a text item (one line text of 40 characters) or a document item (excel file or CAD Documents, Word document or any other document type).



An Item that is added to the BOM can be a Class item, which is used in variant configuration to classify and select components belonging to the 200 class type.



In the Picture above:



Item 0010 and Item 0020 is a Raw Material which are assigned in an "alternate group"



Item 0030 is a semi-finished material which has an "Assembly indicator" - Meaning that it also has a single level BOM



Item 0040 is a Text item to which you can assign any meaningful text for the shop floor/production to understand.



Item 0050 is a material that is to be received as a by-product or co-product. In this case it is a by-product.






Quantity and Unit of Measure

Specify the Quantity of the component added to the bill of materials. The unit of measure of the quantity added is the base unit of measure or the unit of issue mentioned in the material master Work scheduling views or plant data storage views. You cannot use any other UOM other than them.



Note Again - The Quantity for a BOM Item is

= Qty in base UOM or

= Qty in unit of issue in Matl Master Work Scheduling view or Plant Storage view




Item Details






Enter the following on the Item Detail – Basic Data screen –



Component Scrap



This is the scrap percentage used to increase the required quantities of the components by the calculated scrap quantity. This increment is used in MRP and SAP PP order.





Operation Scrap



Operation Scrap is that scrap which is expected in one operation for the quantity of a component to be processed.





Co-product



You can declare a component as a Co-product by specifying it with an indicator here and adding it with negative sign.



A co-product is a product that is produced during the production of the main header material, but has an appreciable selling price in the market. It is entered as Stock item in the BOM.



It is astonishing to find out that, when you produce something you can receive the main header material for which a production order is created as well as the co-product in the same way (through movement type MIGO or MB31 -101); to do you have to mention settlement proportion rule in the material or in the order thereby allocating percentage proportion of the production of each o the items (say 93% of the main header material and 7% of the co-product). You can only receive the quantities mentioned in the rule.





Fixed Quantity



You can mark a component and the quantities in the BOM as fixed quantities. By doing this the requirement qty of the component will always remain the same and will not be a multiple of the production order/planned order demanded quantity.





Recursive component



When you include the header material for which you are creating the BOM, back in to the list of components as a component used for production, the recursive indicator for that component should be put on.



For example, to produce H2S04, you require some amount of H2S04 as a Catalyst in the production process, so H2S04 component in the production of H2S04 is a recursive material component.



Other example can be use of recursivity when you are creating a BOM for "Reworking", which means you would be issuing the same material to produce/rework the same material.








Alternate Group



An alternate group is a grouping of components added to the BOM which belong to the same family. You can include alternates of a family that would co-exist in the BOM and its withdrawal/reservation for production will depend upon the usage probability, priority, strategy mentioned.



For example when you are producing a “PEN”, you require the Plastic A or Plastic B depending upon the availability in the market.



As soon as you enter an alternative item group in the item detail screen (say =”01”), you see an additional dialog box with the following data: ranking order, strategy, usage probability.



The BOM of “PEN” is as below:



PEN (1 Pen)



> Plastic A = 120 gm

(Alternate Group 01 / Priority 1 / Usage probability 100% / Strategy 2)



> Plastic B = 125 gm

(Alternate Group 01 / Priority 2 / Usage probability 0% / Strategy 2)



> Refill



SAP also provides strategies to help you decide between the alternates in the group.



Strategy 1 = by using strategy 1 in the alternate group, you can make the system withdraw components for production by using the usage probability (for example “A” = 70% and B = 30% always). Priority in this case is only used for sorting the materials in the usage order.



Strategy 2 = by using the strategy 2 in the alternate group, you can the system withdraw components for production only if 100% of any one of them is available. If 100% of none is available for withdrawal or reservation, the availability check for all items will confirm the available and in that case the reservation only occurs for the available quantity.



Special procurement & Phantom Assembly



If a certain product is marked with the special procurement = “50” in this view, the phantom indicator would be put on for the assembly.



A Phantom indicator indicates that the material master level mentioned here or the assembly level mentioned here is virtual or imaginary and MRP or production should not account for planning/reservation of this phantom assembly level by itself, though MRP or production should account for the planning/reservation of all the exploded child components in the phantom assembly BOM.




Item Detail – Status/Long Text screen






Item Status



Item status is pre-configured. If you are using a Material BOM with an usage “Production” which is to be used for production, the item status relevancy to production is auto-checked along with the costing relevancy indicators.



If you are using the Material BOM with a usage “Sales” the default indicators of relevancy to sales will be put on.



You can overpower them for certain components in the BOM as your wish.



Production Storage location



The Production storage location is pulled in from the components Material master – MRP 2 view, if it is available there. You can overwrite the value pulled in if you wish to. This is the location from which the component would be issued for production of the header material. This is useful information if you would be using material staging.





BOM Header Details






Base quantity



To create a BOM for a header material; you have to enter the base quantity for which you are creating the BOM for.



Alternate BOM text



Every BOM alternate needs to be described by a 40 Character text, so as to individually identify them.



BOM status



You can active a BOM or keep it deactivated by using the BOM status. If a BOM is deactivated then you can not use anywhere. The BOM status is preconfigured as "Always Active at creation".





Allocation of BOM Components to the Production Order



Normally the Bill of Material components are allocated to the operations in discrete manufacturing or the Phases in the Process manufacturing through the Routings or Recipes.



Use of Allocation of Components in Routing/Recipes -



Point number 1 - The allocation of operations or phases to the BOM components in the Routing or Recipes respectively is created to make a certain component available on the start date of that operation/phase. When you create a production order or process order with a Routing/Recipe which is already allocated with components, the MRP and the order creation programs in SAP use this information to make the component available on the start date of the operation/phase.



Point number 2 - The allocation of operations or phases to the BOM components in the Routing or Recipes respectively is created so that the necessary backflush components are automatically issued when you confirm the respective operation or phase.



If You Dont Allocate an operation or phase to the components -

SAP assumes that all the components are allocated to the first operation/phase and they would be available at the start of the Production order/Process order and they will be issued when the first operation/phase is confirmed.





SAP Phantom BOM



A Phantom BOM is a prepetual BOM or an Virtual BOM structure included in the Higher Level BOM for information purpose.

A Phantom BOM has an header material and components. The Header Material for which you want to create a Phantom BOM is declared as Phantom Material in the material master MRP View 2 (the special procurement key should be 52).

A Phantom Level itself is an Virtual level and is not considered as a stockable item in SAP and SAP Skips this Phantom Level in MRP while planning the overall higher level BOM structure and does not plan any material or scheduling requirements for the same.

Note: You can nevertheless stock a phantom level by creating the views like accounting, costing and plant storage location views. The requirement to stock a Phantom Level can only arise in very minimal number of business cases.

For example:



Normal BOM without Phantom Assembly:



A Car has Left Front Tyre, Left Back Tyre, Right Front Tyre and Right Back Tyre, Which can be represented as below:



CAR



> Left Front Tyre



> Right Front Tyre



> Left Back Tyre



> Right Back Tyre





Adding a Phantom Level to a Normal BOM :

The Level - "Tyres" is an Virtual level (an useless level) which is added in the overall BOM structure for information purpose and SAP will not plan the requirement for the material - "Tyre" but it will plan the requirements for Materials Left Front Tyre, Right Front Tyre, Left Back Tyre and Right Back Tyre.



CAR



> Tyres (Phantom Level)



> Left Front Tyre



> Right Front Tyre



> Left Back Tyre



> Right Back Tyre




Other Uses of Phantom BOM:



It is a know fact that every BOM Level is to be produced through seperate production order or process orders. Though if you want to have 2 (assembly level and sub-assembly level) levels in the same order, you can declare the sub-assembly level as a phantom level, which would result in creating only one order for the assembly level while the sub-assembly level would be exploded in this production order as components and you would aviod creating the sub-assembly level order.



Read more on how to do this on this website - http://www.sapsword.com/home/learn-sap-pp/sap-shop-floor-control/why-do-you-create-sap-production-order-or-process-order

Test

Study Material Contributed by Ulhas Kavle - Senior SAP Consultant, Mahindra Satyam


SAP Batch Determination

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

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 type’s 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


N

No selection at beginning of batch determination


O

Selection with no selection criteria


F

Selection criteria cannot be changed in batch determination










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

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 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.


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 Ascending/descending

LOBM_HSDAT Ascending

FIFO_LAST_GR_DATE 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.


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 Ascending/descending

LOBM_HSDAT Ascending

FIFO_LAST_GR_DATE 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.

Home

 Home

Post 2

Dear All, If you want to Learn SAP for Free. Click on the Link below WWW.SAPsWORD.COM Right now the site is in development and has some notes for SAP PP and PPPI as a starter. Regards Ulhas Kavle

Post 2