SAP Logistics

Material Determination uses condition technique to swap one material for another in a sales order when certain conditions apply. Substituting one product with another product is called material determination. The product is only substituted during the specific period. You can use material determination if you want the system to automatically substitute, for e.g.: Customer specific product numbers with your own material numbers. International article numbers (EAN's) with your own material numbers. Substituting discontinued materials with newer materials Seasonal products. SPRO- IMG- SD- Basic Functions- Material Determination- Maintain prerequisites for material determination Assign procedure to sales doc types: determination rule Condition Technique Create Condition Table Maintain Access Sequence Maintain Condition Type Maintain Procedure Assign Procedure to Doc Type Define substitute reasons: OVRQ   Define Substitution Reasons: go to

This functionality is used by SD, MM, PP, WM Module and can be handled at client , Plant and Material Level. Configuration Condition technique Condition table ------> All possible combinations of deriving batch will be created in the form of condition table Access sequence  -----> Assignment of Condition table will be done Strategy type ----> Assignment of Access sequence will be done and besides it In this selection class and the sort sequence will be assigned Controls Classification of batches, sort sequence and Batch split Batch search Procedure  -----> Assignment of strategy type for Procedure will be done Sales area and document type ----> Assign Batch search Procedure Automatic batch determination need to be activated at Sales order and Delivery Item category level. If batch is determined at sales order level then this will be copied over to Delivery. Ideally it's better to determine batch at delivery level. Create a material which is

Logic to display final approver name  Fetch FRGGR FRGSX FRGKE by passing EBELN and FRGRL Eq ‘X’ Into table EKKO Pass FRGGR FRGSX into table T16FS and Fetch FRGC1 , FRGC2 , FRGC3 , FRGC4 , FRGC5 , FRGC6 , FRGC7 , FRGC8. If NOT FGRC1 IS INTIAL AND FRGC2 IS INITIAL PASS FGRC1 INTO TABLE T16FW  AND FETCH OBJID PASS  OBJID INTO TABLE USR21 AND FETCH PERSNUMBER PASS PERSUMBER INTO TABLE ADRP AND FETCH NAME_TEXT Display NAME_TEXT in the report output to display processor name ELSEIf NOT FGRC2 IS INTIAL AND FRGC3 IS INITIAL PASS FGRC2  INTO TABLE T16FW  AND FETCH OBJID PASS  OBJID INTO TABLE USR21 AND FETCH PERSNUMBER PASS PERSUMBER INTO TABLE ADRP AND FETCH NAME_TEXT Display NAME_TEXT in the report output to display processor name ELSEIf NOT FGRC3 IS INTIAL AND FRGC4 IS INITIAL PASS FGRC3 INTO TABLE T16FW  AND FETCH OBJID PASS  OBJID INTO TABLE USR21 AND FETCH PERSNUMBER PASS PERSUMBER INTO TABLE ADRP AND FETCH NAME_TEXT Display NAME_TEXT in the repor

Commonly, Business contains conditions which should be applied to entire document i.e., header conditions.In general, maintaining the header condition in the sales or purchasing document leads to duplicating the condition value or amount to all line items instead of splitting the condition value amount the line items. Below is the case without Group Condition Business Process : In order to fix this issue, SAP has provided Group Condition Functionality which splits the header value among the line items instead of duplicating the header condition value. Below screenshots depict the Group Condition Functionality : Process Flow Thank you

Order Required field : The Order Required field is used to specify the document type to be referenced in the creation of this delivery. Default Ord. Type : Specify the default order type here. If a delivery is to be created without reference, you need to specify a “pseudo” order type, which is a reference order type that is required from an internal control point of view. For example, in the case of delivery type LO, the default order type is DL. This order type is configured like any other sales document. Item Requirement: This is a provision to attach a requirement routine for delivery items without reference to a sales document. 201 No ord.w.indep.item Maintaining this routine will restrict user from adding new items at delivery level 202 Order w IndpdntItem Maintaining this routine will allow user to add new items at delivery level independent of sales order or preceding document Delivery Rescheduling You can control whether a redetermination

During sales order processing, the system automatically determines individual purchase order items. However, you can also change standard items to individual purchase order items during sales processing manually. Material exclusive for Individual purchase order, If you procure a material exclusively by individual purchase order, you can define in the material master record that the material is always treated as an individual purchase order item during sales processing. The system will then automatically determine the appropriate item category TAB. To identify a material as an individual purchase order item in the material master record, enter BANC in the field Item category group on the Sales: sales org. 2 screen. Changing Manually in Sales Order If you want to use an individual purchase order to purchase a material that you normally produce yourself, you can overwrite the item category in the sales order, provided that the configuration of yo

Business at times as a part of product sales dumps stock at the customer location and will bill the customer based on the customer sales. The business scenario of employees taking samples to showcase at Expo can be mapped through consignment process as well. In this case, the employee needs to be created as a customer. The consignment process in SAP standard consist of four Steps: 1. Consignment fill up (send materials to customer consignment). 2. Consignment issue (issue materials from customer consignment to the customer) 3. Consignment return (return materials from customer ownership to customer consignment) 4. Consignment pickup (pickup consignment stock and move it to plant stock) Sales Process Sales Document Type Item Category Schedule Line Category Movement Type Relevant for Billing Consignment Fill Up KB or CF KBN E1 631 No Consignment Issue KE or CI KEN C0 or C1

Plant Determination in Sales Order 1st Preference: System fetches Delivering plant from Customer Material Info Record if Plant is not found at this level then system will look into 2nd Preference:   Delivering plant from Customer Master data if Plant is not found at this level then system will look into 3rd Preference : the Delivering plant for Material Master data If business user overwrites Plant at sales document level then this will be given highest preference. Shipping Point Determination Delivering Plant (Based on above conditions) + Shipping Conditions ( Sales Document Type or  Customer Master Data) + Loading Group ( Material Master ) Storage Location Determination Plant + Shipping Point + Storage Conditions ( Material Master )  ( MALA) Plant + Shipping Point + Situation  ( RETA) Route Determination Departure Zone or Country of the Delivering Plant + Destination Zone or Country of the Ship to Party + Shipping Condition from the Customer Master + Transport

Customer Master Data  KNA1 - General Data KNB1 - Company Code Data KNVV - Sales Area Data KNVP - Partner Function Data KNVI - Tax Classification Data Material Master Data MARA - Basic Data MARC - Plant Level Data MARD - Storage Location Data MARDH - Storage Location history Data MVKE - Sales Data MBEW - Accounting Data MBEWH - Accounting History Data Customer Material Info Record KNMT - Customer-Material Info Record Data Table Sales Document Data VBAK - Header Data VBAP - Item Data VBEP - Schedule Line Data VBKD - Business Data VBUK - Sales Document Status VBFA - Document Flow VBPA - Sales Partner Data Delivery Document Data LIKP - Header Data LIPS - Item Data Billing Document Data VBRK - Header Data VBRP - Item Data Pricng Tables KONV - Conditions (Transaction Data) Logic to fetch pricing data from KONV Table Fetch KNUMV (Condition Number)  from VBAK table and pass onto KONV table to fetch conditions data Pricing Field Catalog Structu

Cash sale  Ideally, there will be customers for whom transactions will happen through Cash Sale and in this case below are the points to be remembered. Cash sales have one-time customer account group and Cash sales (CS) are also not relevant for credit management is used during sales order processing Delivery automatically happens when you save the sales order.   Cash sales is order related billing and doesn't have credit active Cash sales items are not relevant for picking during delivery processing as you will be picking the goods on our own. Ideally business uses separate shipping point for Cash sales delivery processing Billing type 'BV' is used during Cash Sale process Cash sales uses RD03 as output which immediately prints the invoice Cancellation document type 'SV' is used for cash sales Ideally, cash settlement account determination procedure 'KOFIAC' is used and Cash settlement account will be debite