Batch Mgmt. in SAP SD

5,113 views
4,740 views

Published on

Published in: Business
3 Comments
5 Likes
Statistics
Notes
  • More than 5000 registered IT consultants and IT corporate's. Request IT online training at http://www.todaycourses.com
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • hi, as per your one slide, its mention that, item category determination of, TANN is like this way - SALES DOC. TYPE (OR) (TA) + ITEM CATEGORY GROUP (NORM) + USAGE (FREE) + HIGHER LEVEL ITEM CATEGORY (NILL) is determine TANN, but it should be SALES DOC. TYPE (OR) (TA) + ITEM CATEGORY GROUP (NORM) + USAGE (FREE) + HIGHER LEVEL ITEM CATEGORY (TAN) is determine TANN, pls change it on your slide,..
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Enable to download
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
5,113
On SlideShare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
0
Comments
3
Likes
5
Embeds 0
No embeds

No notes for slide

Batch Mgmt. in SAP SD

  1. 1. P age |1 Batch Management : What ever materials that are produced inside a plant that are produced in batches so as to catch hold of any defectives or while implementing the LIFO and FIFO methods. For creating batches under SAP SD following things are done: a) First of all the characteristics are defined under CT04 b) The classes are defined under CL02 [CT04] These are the features of the material and after defining these characteristics the classes are defined under CL02 for which the class type is assigned as 023 Then go to MM01 i.e. material master and maintain classification view also With classes and characteristics assigned to them. Under the sales: general/plant tab maintain the checking group of availability check as CH, & check batch management box. Then maintain the IMG configuration settings for batch management under logistics general Definition – Batch Level:  Batch unique at plant level  Batch unique at material level  Batch unique at client level for a material Batch unique at plant level: If the batch data has been maintained at plant level then batch data is specific to particular plant under one company code. Batch unique at material level: If batch data has been maintained at material level then batch data has to be maintained separately from plant to plant under company Batch unique at client level for a material: If batch data has been maintained at client level then batch data is same across all plants under all company codes under one client for a single material. Activate internal batch number assignment and maintain internal batch number assignment with batch object as batch_clt The sales and distribution search procedure would be SD0001 i.e. standard SD search procedure and the strategy type will be SD04. ҉ ۩ = ∑Ω₤∞∆Create PDF files without this message by purchasing novaPDF printer (http://www.novapdf.com)
  2. 2. P age |2 Activate automatic batch determination in SD for sales order item (VOV7) and for delivery item categories (OVLP) Create the batch condition records at VCH1 and maintain the batch master at MSC1N. Rebates Rebates are special discounts which have a time duration & a reference to specific sales volume. Go to the sales & distribution  Billing  Rebate processing Under rebate processing there are rebate agreements like Group rebate, Material rebate, Customer rebate, Hierarchical rebate, etc. Rebates follow the condition technique concept & we need to activate the rebates for the particular sales organization & need to select billing document type relevant for rebates. Various other modifications/configurations which needs to be performed. For e.g. maximum rebate, minor rebates etc.  Maintain pricing procedure for Rebates We need to include the particular condition type for the selected rebate agreement type in our pricing procedure at control data. For e.g. we opted for 0002 –material rebate then we need to assign condition type BO02 respective to 0002 at control data of our pricing procedure The other settings are: cond. type BO02; Subtotal 7(KOMP-BONBA), A/c key ERB, & Accruals ERU, Requirement 24 So as to take a basic amount to calculate rebate.  Go to VBO1: & create a rebate agreement Enter the recipient customer # and click upon the conditions tab so as to create and maintain the condition record. & Save it. Note down the rebate agreement #. Raise the sales order, click upon the item conditions tab, then do the delivery and billing. Rebates are not activated at sales order level but gets activated at billing. ҉ ۩ = ∑Ω₤∞∆Create PDF files without this message by purchasing novaPDF printer (http://www.novapdf.com)
  3. 3. P age |3 Settings: Default Values Control data Manual Payment Settlement Text Determn Pricing Exercises  Condition Exclusion Group  Condition Supplement  Scales in pricing Condition Exclusion Group: Best or least favourable condtions between: a) Condition types b) Within condition types c) Between 2 condition exclusion groups Define condition exclusion group  Assign condition types to the exclusion group  Maintain condition exclusion for pricing procedure Condition Supplement: Business wants to grant discount or discounts for each & every sales transaction with in specified time period With the help of this functionality the required condition types are automatically determined in each & every sales transaction along with basic price. Go to VK11 or VK12, select the condition record and then go to Go to, and click on propose condition supplements icon and maintain the condition record, and save it. Scales There are two types of scales i.e. Normal scale and Graduated scale. Normal Scale Graduated Scale 1-10 EA 1000 1-10 EA 1000 11-20 EA 999 11-20 EA 900 21-30 EA 998 21-30 EA 800 ҉ ۩ = ∑Ω₤∞∆Create PDF files without this message by purchasing novaPDF printer (http://www.novapdf.com)
  4. 4. P age |4 If order qty is 25, then 25*998 1st 10 pcs. 10*1000 = 10000 2nd 10 pcs. 10*900= 9000 3rd 5 pcs. 5*800= 4000 Total 24950 /- 23000/25 = 920/- In graduated scale system calculates the avg. price by taking each level of the scale. It is favorable to the business. Settings: Condition type PR02, Acc. Seq. K005, Condition type B, Calculation type C, Manual entries D, Scale basis C, and Scale type D Go to V/08 and include condition type PR02 instead of PR00. Free Goods Free goods can be determined:  Manually (User has to specify the higher level line item to the free good line item, sys. Automatically determines that line item as a free good)  Automatically: Using condition technique concept Automatically : a) Inclusive (9+1) b) Exclusive (10+1) Constraint: Free goods can only be determined on documents whose document category is ‘C’ (Sales Order). Free goods pricing procedure determination: Sales area + Customer pricing procedure + Doc. pricing procedure = Free goods pricing procedure Item category for free goods item: ҉ ۩ = ∑Ω₤∞∆Create PDF files without this message by purchasing novaPDF printer (http://www.novapdf.com)
  5. 5. P age |5 TA+NORM+NIL+NIL=TAN TA+NORM+FREE+NIL=TANN Choose our pricing procedure & include condition type R100 with requirement 55, alternative formula for condition base value 28. Maintain the condition records for free goods under VBN1 There are two types of calculation formula for free goods i.e. Pro-rata and Unit reference Pro rata (Proportional): formula calculates free goods proportionately to the ordered quantity i.e. if 20 for 100 then 32 for 160 (160*20/100) Unit reference: This routine calculates free goods for every order unit reference i.e. if 20 for 100 then 40 for 200 but 0 for 160. For condition type NRAB the settings are 59 in requirement & alt. formula for cond. base value as 29. Special Functions:  Condition Record Maintenance  Lower Limit and Upper Limit  Mass Maintenance  Copy control for conditions  Quantity Index Condition Record Maintenance All the changes which needs to be made are to be carried out at master records level only.  To change the data select the condition record and maintain the selection screen and save it or go to VK12  Condition type can be deleted at the item condition screen of the sales order  Select the condition record and change it with Amount/percentage icon  Cond. Value = Cond. amount * order quantity If it is activated the condition value can be changed during sales order processing. ҉ ۩ = ∑Ω₤∞∆Create PDF files without this message by purchasing novaPDF printer (http://www.novapdf.com)
  6. 6. P age |6  The calculation type can be changed from qty. to % while doc. processing with the help of Calculation type icon  Deletion from database Lower limit and upper Limit The lower or upper limit of the condition type can be controlled during the sales order processing a) IMG……..Pricing Pricing control define cond. types  Define upper/Lower lmt. for condtion types b) Go to VK11 or VK12, select condition record and go to, go to details & maintain upper/lower lmt. Mass maintenance : Go to VK12, Specify the condition type and maintain the selection screen for certain range of materials, then choose all the condition records and click upon the change amount icon & specify the percentage or the absolute amount with which condition amounts are going to be increased or decreased. Copy control for Conditions : Condition records can be copied from same cond. type to same cond. type or different cond. types so that it reduces data maintenance level. Go to V/08 and include K020 between discount condition steps. Under XD02 maintain customer price group as 01. And maintain condition records for K020 under VK11 for Customer group 01 Generate sales order for this customer with price group as 01 and 02 respectively and check whether the condition type K020 has been granted or not. Go to VK12 of K020 and Select the condition record and click upon copy condition icon Specify target customer grp. as 02 to 100 Target cond. type as K020 Check Display button and Execute. Select new group and click on continue and Save the record. ҉ ۩ = ∑Ω₤∞∆Create PDF files without this message by purchasing novaPDF printer (http://www.novapdf.com)
  7. 7. P age |7 Check the K020 under the item condition screen of sales order generated for customer with price group 02. Quantity Index a) Condition Index b) Condition update Condition Index: It is created so as to update the condition related information in all sales transactions where that condition type is being used. Path: IMG….Pricing Maintain condition index all the 3 steps Maintain condition records with condition index i.e. V_i7 (create Condition) Maintain selection screen and execute; save it Generate sales order including our condition type created in V_i7 and save it Go to V/i5 (Change condition) Change the condition amount and under VA02 update the new pricing. Condition Update: By using this functionality the usage of the condition type can be restricted to : 1) Max. no. of sales orders 2) Condition amount 3) Condition base value Go to V/i5, select condition table & condition record, go to Go to  Additional data  and specify the maximum number of orders e.g. 2 For reference purpose if Z004 is the condition type, then Generate 3 sales orders to find that Z004 has been deactivated from the 3rd sales order. ҉ ۩ = ∑Ω₤∞∆Create PDF files without this message by purchasing novaPDF printer (http://www.novapdf.com)
  8. 8. P age |8 Pricing Report Pricing report can be generated for every condition type for evaluation purpose through V/LA and can be executed through V/LD Path: IMG….Pricing Maintain pricing reportCreate report (V/LA) Save it and go to V/LD and specify the pricing report and execute, maintain selection screen and execute, check the report. Dataflow According to dataflow organizational structure data is going to be captured into various configuration tables with reference to which master data is going to be captured that is going to be captured into various master data tables and with reference to master data tables various transactions are going to be captured into various transaction tables or transparent tables. So as to capture various transactions system may require the data from various tables for e.g. configuration master data etc. So that the transaction tables are made up with fields from those tables but due to certain performance point of view all the fields cannot be included in transaction tables whatever the data that is required to process transactions only those fields has been included in the transaction tables. During document processing the document may require certain data for certain basic functions for certain business requirement e.g. pricing. For that kind of data SAP has developed certain structures that are communicated by the system during document processing so that they are referred as a communication structures e.g. KOMK – Pricing communication header. KOMP- Pricing communication item, KOMG- Field catalogue. KOMK represents header level data, KOMP represents item level data, KOMG is made up with fields from KOMK & KOMP. So that if any new field is going to be appended to those communication structures that should be appended according to the position of the field at sales document header e.g. customer classification field- KLABC is existed in master data table KNVV so that it should be appended to KOMK as well as KOMG. Config. Settings: IMG SD System modification Create new fields New fields for pricing(a) Use include for new fields in dictionary (b) Use user exits for new fields Include KLABC in the field catalogue: IMGPricing ctrlDefine: conditions allowed fields. ҉ ۩ = ∑Ω₤∞∆Create PDF files without this message by purchasing novaPDF printer (http://www.novapdf.com)

×