Tables/Tcodes in SAP SDImportant Tables for SAP SDSales and Distribution:Table DescriptionCustomers KNA1 General DataKNB1 Customer Master – Co. Code Data (payment method, reconciliation acct)KNB4 Customer Payment HistoryKNB5 Customer Master – Dunning infoKNBK Customer Master Bank DataKNKA Customer Master Credit Mgmt.KNKK Customer Master Credit Control Area Data (credit limits)KNVV Sales Area Data (terms, order probability)KNVI Customer Master Tax IndicatorKNVP Partner Function keyKNVD Output typeKNVS Customer Master Ship DataKLPA Customer/Vendor LinkSales Documents VBAKUK VBAK + VBUKVBUK Header Status and Administrative DataVBAK Sales Document - Header DataVBKD Sales Document - Business DataVBUP Item StatusVBAP Sales Document - Item DataVBPA PartnersVBFA Document FlowVBEP Sales Document Schedule LineVBBE Sales Requirements: Individual RecordsSD Delivery DocumeLIPS Delivery Document item data, includes referencing POLIKP Delivery Document Header dataBilling Document VBRK Billing Document HeaderVBRP Billing Document ItemSD Shipping Unit VEKP Shipping Unit Item (Content)VEPO Shipping Unit HeaderSAP SD Transaction codes ListI found a way to know hidden customizing Tcodes.Before executing customizing task you desire, point it and go to Edit-Display IMG Activity. Thenmark activity.Go to T.Code se16 and type in CUS_IMGACH table.Execute.Paste IMG Activity and run.You will see Tcode that belongs to IMG Activity.SAP SD Tips by: JavierThe most frequently used transaction codes are as follows:1. VS00 - Master data2. VC00 - Sales Support

3. VA00 - Sales4. VL00 - Shipping5. VT00 - Transportation6. VF00 - BillingOthers as follows:At Configuration:1. VOV8 - Define Sales documents type (header)2. OVAZ - Assigning Sales area to sales documents type3. OVAU - Order reasons4. VOV4 - Assign Item categoreies(Item cat determination)5. VOV6 - Scedule line categories6. OVAL - To assign blocks to relevant sales documents type7. OVLK - Define delivery types8. V/06 - Pricing9. V/08 - Maintain pricing procedure10.OVKP - Pricing proc determination11.V/07 - Access sequenceEnduser:1. Customer Master Creation-VD01 and XD01 (for full inclu company code)VD02 - Change CustomerVD03 - Display CustomerVD04 - Customer Account ChangesVD06 - Flag for Deletion CustomerXD01 - Create CustomerXD02 - Modify CustomerXD03 - Display Customer2. Create Other material ----MM003. VB11- To create material determination condition record4. CO09- Material availability Overview5. VL01 - Create outbound delivery with ref sales order6. VL04 - Collective processing of delivery7. VA11 - Create InquiryVA12 - Change InquiryVA13 - Display InquirySales & DistributionSales order / Quote / Sched Agreement / Contract· VA01 - Create Order· VA02 - Change Order· VA03 - Display Order· VA02 - Sales order change· VA05 - List of sales orders· VA32 - Scheduling agreement change· VA42 - Contract change· VA21 - Create Quotation· VA22 - Change Quotation· VA23 - Display Quotation

Billing· VF02 - Change billing document· VF11 - Cancel Billing document· VF04 - Billing due list· FBL5N - Display Customer invoices by line· FBL1N - Display Vendor invoices by lineDelivery· VL02N - Change delivery document· VL04 - Delivery due list· VKM5 - List of deliveries· VL06G - List of outbound deliveries for goods issue· VL06P - List of outbound deliveries for picking· VL09 - Cancel goods issue· VT02N - Change shipment· VT70 - Output for shipmentsGeneral· VKM3, VKM4 - List of sales documents· VKM1 - List of blocked SD documents· VD52 - Material DeterminationTask Specifc SD Transaction Codes 1How to configure tax?Use the following Tcodes:OBQ1 --- CONDITION TABLEOBQ2 --- ACCESSOBQ3 --- TAX PROCEDURE CALOBBG --- ASSIGN COUNTRY TO TAX PROCOVK3 --- CUSTOMER TAX CATEGORYOVK4 --- MATERIAL TAX CATEGORYOVK1 --- TAX DETERMINATION RULESOVK6 --- ASSIGN DELIVERY PLANTSand thenVK11 to maintain the condition record for the tax rate.I raise a sales order and is getting a error stating that "sales area is not defined".1) At SPRO-->SD-->Sales header-->Assign Sales area to Sales document - Combine your SalesOrganisations, Distribution Channels & Divisons2) At VOPA-->Assign Partner Determination procedure to your Account Group of Customer Masteryou are using.3) At VOPA--> Assign Partner Functions to your Account Group & Partner Determination procedureSteps to create a Vendor Master Data at the client level and how do we extend it todifferent company codes?Follow the following steps:1. Create a vendor account group OBD32. Define no. range for vendor account group XKN13. Assign number range to Vendor account group OBAS4. Define tolerance Group for vendor OBA3

5. Create 2 GL accounts FS00a) Purchases A/cb) S. creditors A/c6. Create Vendor master data XK017. change/block vendor master data XK02/XK058. Define document type and no. range OBA7a) KAb) KGc) KRd) KZ *-- VandnaHow to find the strategy group in sap sd?Menu path for Strategy Group is:Spro --> Production --> Production Planning --> Demand Management --> Planned IndependentRequirements --> Planning Strategy --> Define Strategy Group.OPPT -- Maintain Starategy GroupWe can see Strategy Group in Material Master Record - MRP 3 - Planning -- Strategy Group.10 - For Make to Order20 - For Make to StockTask Specifc SD Transaction Codes 2Where do we maintain "Item Category Usage" at the master level?Spro --> Sales and Distribution --> Sales --> Sales Documents --> Sales Document Item --> DefineItem Category UsageItem Category Usage: item category usages which control the usage of an item. Item categoryusage controls, for example, the system response if during document processing an item does notrefer to a material but to a text item. Item category usage can also be maintained via the itemcategoriesIn contracts we are creating quantity contract and value contracts in that we only putthe validity period after validity period that contract will close,but customer wantbefore one month closing the period system should alert with popup box like thiscontract is going to close, for this sales manager can follow up the customer for renualthe contract.Getting a pop-up when the Contract is going to expire is not a Standard SAP thing. For this youneed to do some programming. Instead of this the Std system has a reminder system where in theopen Contracts and Quotaions are popped up when you about to create a sales order.This setting is in the Sales order header ,Goto -- VOV8 --- Quotation and Outline agreement messagesIf you want to have different number range for different sales area where the settingsto be done.Number Rage are use to define what number to be assign to sales document type. Number rangecan be assign Internal or external.In internal number range system automatically assign a number to sales document according tonumber range define in system.In External number range user manually assign number to sales document.For Assigning Number Range use T-Code VN01Choose Intervals ---- Define your number range

Standard SAP SD ReportsReports in Sales and Distribution modules (LIS-SIS):Sales summary - VC/2Display Customer Hierarchy - VDH2Display Condition record report - V/I6Pricing Report - V/LDCreate Net Price List - V_NLList customer material info - VD59List of sales order - VA05List of Billing documents - VF05Inquiries list - VA15Quotation List - VA25Incomplete Sales orders - V.02Backorders - V.15Outbound Delivery Monitor - VL06oIncomplete delivery - V_UCCustomer Returns-Analysis - MC+ACustomer Analysis- Sales - MC+ECustomer Analysis- Cr. Memo - MC+IDeliveries-Due list - VL04Billing due list - VF04Incomplete Billing documents - MCV9Customer Analysis-Basic List - MCTAMaterial Analysis(SIS) - MCTCSales org analysis - MCTESales org analysis-Invoiced sales - MC+2Material Analysis-Incoming orders - MC(EGeneral- List of Outbound deliveries - VL06fMaterial Returns-Analysis - MC+MMaterial Analysis- Invoiced Sales - MC+QVariant configuration Analysis - MC(BSales org analysis-Incoming orders - MC(ISales org analysis-Returns - MC+YSales office Analysis- Invoiced Sales - MC-ESales office Analysis- Returns - MC-AShipping point Analysis - MC(UShipping point Analysis-Returns - MC-OBlocked orders - V.14Order Within time period - SD01Duplicate Sales orders in period - SDD1Display Delivery Changes - VL22SAP Sales and Distribution FrequentlyAsked QuestionMaster DataQ: Some materials have been blocked for procurement and production. Even though deletion flag

is set for a material/plant level, the order can be still entered ( with a warning message). Is there away to block such transactions for a material flagged for deletion?A: Sales Status field in the sales organization view of the material master may be used to blockany transaction for the material.Q: We can define our own exchange rate types and use them instead of the defaulted types, 'M','B' and 'G'. How can we overwrite default types in SD?A: Exchange rate gets copied from the customer master record. Exchange rate types are to bemaintained for the customer in the sales screen of the customer master record.ShippingQ: The PL00 condition is fine in delivery. But when we try to print to either the screen or printer, anerror V1032 occurs. Why?A: In order to use the Packing list PL00 (packing slip in delivery) you must do 'Packing' in thedelivery note (edit->packing)Q: we have to enter a shipping point while creating a delivery. Is it possible to create deliverywithout shipping points?A: When you are releasing a sales order, choose Sales document -> Subsequent functions->Create delivery, then the shipping point will be brought in from the sales order. In all otherscenarios you have to key in the shipping point. The above described scenario will only work if allitems on the sales order are to be shipped from the same shipping point.BillingQ: SAP allows a non-inventory item and an inventory item to be in the same document till deliverybut splits at the time of creation of billing document. Can we combine a non-inventory item with aninventory item in one invoice? Can we treat it as a value item in sales order so that it is priced andthen make it as a text item in delivery documents so that it appears in the same invoice and doesnot split?A1: Make the non-stock material deliverable, but not pickable. Both items will carry into thedelivery, and therefore appear on the same invoice.A2: Change the copy rule for orders->invoices and deliveries->invoices to specify that invoicecombination is permitted. However note that for system to create combined invoices, PO number,payment terms, sales organization, and distribution channel must be identical. Else undesirablecombinations may be created by the system.Pricing ConditionsQ: It is impossible to price at the material level (matnr) , when a material has a pricing reference(mvke-pmatn) set up against it in the master data. Pricing always look for the pref, even if a priceis set up against the material and not the pref. How can we price by material and pref?A: The field used to look up at the price is defined in Access sequence. You may find a step withPMATN as material number. If you insert a step with MATNR then the system will first look for thematerial, if not found (use the exclusion tick box) it will look for the pref.Customizing

Q: We generated a new condition table. Assigned the condition to access sequence. Created acondition record. Access sequence is assigned to the output type. But when we create a billingdocument, output screen comes up blank for the output type. When we look up DeterminationAnalysis, we get an error "Note 524 Access not made (Initialized Field)". What else is required to bedone?A: Assign output determination procedure to the header of the document and the output type.Q: How can we set up to have the VAT# be accepted in the Ship-To Master File Data Control screen?A: IMG->Fin. Acct.->AR and AP ->Customer acct->Master Record -> Prepare to Create Customer->Define Acct. Group.Q: We want to explode Bill of Material automatically at time of Order entry and explode anEquipment BOM in the sales order. What are the setting required?A: Use an item category that is configured for bills of material for having a sales BOM to explodeautomatically.Standard SAP item categories are :TAQ - Pricing and inventory control take place at the BOM header levelTAP - Pricing and inventory control take place at the BOM item levelThese can be automatically derived using the item category groups ERLA and LUMF, respectively.Q: How can we make the Customer Group 1 (or 2, 3, 4, 5) a mandatory field?A: Logistic General-> Logistics Basic Data: Business Partners -> Customers -> Control -> Defineaccount groups and field selection for customerChoose Customer Acct. GR. (double-click). -> Field Status: Sales data (double click) -> sales(double click) .Check the radio button against Customer Gr as REQ. ENTRY. Save the settings tomake customer GR entry mandatory .Q: Is there an user exit to copy the data into planning table?A: Use user exit MCP20001 and include ZXSOPU01.OthersQ: We get a report screen: "Goods issue: Problem Log" during the delivery process when activatingPost Goods Issue button. We want to include our own error message to this list if the selected batchis not on a customer defined table. What is the best way?A: Try User exit - USEREXIT_SAVE_DOCUMENT_PREPARELink Between SAP SD, MM & FI1. In SAP you will always get integration with other modules. SD will interact with FI, MM willinteract with SD :-1a. Looking at MM and SD interaction first, take the scenario of a third party order process. Thisprocess uses a purchase order (which is sent to your vendor). Also invoice verification is usedfurther along the process to check that the invoice you send to your customer is the same material

and quantity as that which the vendor sends to you (but obviously shippeddirectly to your customer).1b. Billing is an SD function. But SAP needs to know, when processing a customer's payment, towhich GL account the payment has to be processed. For instance payment of a UK based materialwould be placed in a different GL account to that of a non-UK based material. Furthermore, a UKbased customer may have a different GL account to that of an Export customer. This is configuredin Account Determination.2. ABAPers are there to essential do some bespoke development. Your integration, or interaction,with them would be when specifying the tables, fields, input fields, a simple process explanation,data mapping (if doing an interface from one system to another) etc. *-- ShaheeThe link between SD and MM :-1. When you create sales order in SD, all the details of the items are copied from Material master ofMM.2. MRP and availibility check related data is also taken from MM although you control this data inSD also.3. While you create inbound/outbound delivery with reference to a sales order,the shipping pointdetermination takes place with the help of the loading group, plant data, shipping conditions etc.This also refers to Material Master.4. The material which you are entering in a sales order must be extended to the sales area of yoursales order/customer otherwise you cannot transact with this material.There are many such links between SD and MM.Now the link between SD and FI :-1. Whenever you create a delivery with reference to a sales order, goods movement takes place inthe bacgground. eg. In case of standard sales order, you create an outbound goods delivery to thecustomer.Here movement 601 takes place. This movement is configured in MM. Also, this movement hitssome G/L account in FI. Every such movement of good s hits some G/L account.2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note,credit note etc) created in SD. Thus this is a link between SD and FI3. Tax determination: In case of a tax determination also, there is a direct link between SD and MMSD Integration points with other modulesSD module is highly integrated with the other modules in SAP.Sales Order –Integration Points Module•Availability Check - MM•Credit Check - FI•Costing - CO/ MM•Tax Determination - FI

•Transfer of Requirements - PP/ MMDelivery & Goods Issue –Integration Points Module•Availability Check - MM•Credit Check - FI•Reduces stock - MM•Reduces Inventory $ - FI/ CO•Requirement Eliminated - PP/ MMBilling -Integration Points Module•Debit A/R - FI/ CO•Credit Revenue - FI/ CO•Updates G/ L - FI/ CO(Tax, discounts, surcharges, etc.)•Milestone Billing - PSReturn Delivery & Credit Memo -Integration Points Module•Increases Inventory - MM•Updates G/ L - FI•Credit Memo - FI•Adjustment to A/R - FI•Reduces Revenue - FITips by: SubhaSD Transaction Code Flow:Inquiry / Document type INTcode for creation VA11,VA12,VA13. tables VBAK,VBAPQuotation / QTTcode for creation VA21,VA22,VA23. tables VBAK,VBAPPurchase Order POTcode for creation ME21,ME22,ME23. tables EKKO,EKPO.Sales Order ORTcode for creation VA01,VA02,VA03. tables VBAK,VBAPDelivery LFTcode for creation VL01,VL02,VL03. tables LIKP,LIPSBilling MNTcode for creation VF01,VF02,VF03. tables VBRK,VBRPTo create a sales order we need purchase order number and custmer number. Before that, tocreate a purchase order we need to have material no, vendor no.To create vendor tcode isxk01(create), xk02(change) , xk03(display)Tables are lfa1.To create custmer tcode is xd01, xd02, xd03.Table is kna1.After creating sales order using this no we can create delivery note tcode is vl01.Why Do We Assign Division to SalesOrganisation

In SAP, why do we assign division to Sales organisation not to distribution channel?In SAP Business ProcessSales Area= Sales Org.+Dist.Channel+Division.Its Triangular intractionSales organization/ \/ \Dist.Channel<----------------->DivisionSales Org controls Distribution Channel and DivisionDistribution Channel: The channel that is choosen the organization to make their product reach theend customer.(Network)Division: Ex: HLL--------> Detergents, Out of Home,Food Products,Health CareSectors/DepartmentsTATA Motars: Trucks/Bus,Cars,Heavy Vechiles Etc...Please note it is not:Sales organization||Dist.Channel||DivisionDivision is an Oragaizational Unit.The Division in the Material Master is not an Organizational Unit that can be used to maintainrelated fields. It is a field which is used to uniquely assign a material to a DivisionDuplicate customer purchase orderIf you are facing a problem with duplicate customer purchase order as your company does notallowed a same customer purchase order with the same sales order type.You can activated the check for duplicate purchase order with "VOV8".In the General Control Section, look for the field Check Purchase Order No and put in "A".Default First Date is not TodayWhen end user created a new sales order with VA01, default First Date wasn't today,why?Note:1. Before today, default First Date was always today.2. Nobody change system configuration.Although you mention that nobody change the system configuration, it is very unlikely that thesystem will mis-behaved after one day.Usually, after checking, you will find that someone have actually change the configuration as itcould not be a software bug since you have been using it for quite sometime without any problems.The date is control by each Sales Order Type for each Sales Document type whether is it a- OR - Standard Order,- RE - Returns etc.Verify the Sales order type configuration with the following path:

IMG: Sales and Distribution --> Sales --> Sales Docs --> Sales Doc Hdr --> Define Sales Doc Types(transaction vov8) will let you control this by sales document type.There is one field (Lead time in days) which "specify the number of days after the current date thatthe proposal for the requested delivery date in the sales document should be".This should be blank if you want the system to propose current day for delivery date.Auto proposed all the dates when creatingSales OrderHow can I make the system auto create all the Sales Order date during creation?Each Sales Order can have different date proposal settings.Follows this step to set the default Sales Order Type proposal date:- Goto VOV8, double click on sales order type.- Look and tick the fields Propose delivery date and Propose PO date.After making the necessary IMG changes, you need to input the Delivery Plant field for eachMaterials that you want the system to propose the default date.To change the Materials field Delivery Plant:Goto MM02, Select the View Sales: Sales Org. Data 1 and fill in the Delivery Plant.Testing:Now, try creating a new sales order for the material and SAP will auto proposed all the dates in thesales order.Define whether the Material can be used at which Salesand Distribution processHere you define how the system responds when entering a sales and distribution documentwith this material in the differenet Sales and Distribution Process Flow..You can use the material status, for example, to prevent orders from being entered forparts to be discontinued.ORTo temporary block the creation of Sales Order for a certain materials.Set the material status parameters in transaction SM30, Table Views V_TVMS.Click Maintain and double click into the Materials Status code.You can set three types of reponse for each Sales and Distribution process :-1. no dialog2. warning when entering the document3. error message (that is, the sales and distribution document cannot be entered onthe basis of the material status)Assign a Cost Center manually in a SalesOrder (VBAK-KOSTL)The Cost Center Determination settings is in OVF3 - but there are some cases where the CostCenter must be exceptionally changed.If the document category for order type in IMG VOV8 is defined to be "I" which belong to ordertype FD - Deliv.Free of Charge, then the field cost center is active for input during transactionVA01.Alternatively, you can specify an order reason and assign a cost center to an order reason.However the standard SAP works only at the header level though, so it would not work if cost

center is needed on the line item.The cost center are assign for such business transactions as :- Free deliveries- Returns- Deliveries of advertising materialsYou can also make cost center allocation dependent on the order reason, for example:Order reason: Damage in transitOrder reason: Free sampleBoth the IMG settings are done in transaction OVF3, either with/without the order reason.Sales and Distribution - Transfer ofRequirementsThe MRP department is informed about the quantities and deadlines by which incoming ordersshould be delivered. The system checks the availability of the goods based on the requesteddelivery date of the customer and creates MRP records which contain all necessary informationfor passing on to planning. It ensures that the goods are available in time for the delivery.Materials planning transfers the reported requirements and creates orders or purchaserequisitions from them etc.For controlling transfer of requirements, you have to carry out the following steps:1. Each requirement type has to be allocated to one requirement class only.2. The transfer of requirements must be switched on at requirements class level, the salesdocuments at schedule line level.3. You must define a check group. It is possible to have this check group proposed for theinitial creation of a material master record.4. Note that a plant must exist for transfer of requirements to be carried out at documentitem level.OVZG - Requirement classIt specifies the following points:- whether an availability check and a transfer of requirements is carried out for atransaction (for sales documents, fine tuning using the schedule line category is possible),- whether the requirements are relevant for MRP,- the allocation indicator from the sales view which controls the settlement of customerrequirements with requirements- whether an item is to be settled to an auxiliary account assignment,- the settlement profile,- the results analysis key.(Use transaction SM30 for V_* configuration)OVZH - Requirements typeV_TVEPZ_V - Assignment of requirement type to TransactionV_TVEP_V - Schedule line categoryOVZ2 - Define Checking GroupV_TMVFU - Define the checking group that the system proposes when you create a new materialmaster record. You can overwrite the default value for the checking group in thematerial master record.Define Tax Determination Rules

You specify the valid tax types in transaction OVK1. More than one tax type can be defined for acountry by defining the sequence.The SAP System determines the taxes automatically within pricing.In the standard SAP R/3 System, the elements of tax calculation are predefined (for example, taxcondition type "MWST" for taxes on sales and purchases).Assign the plant for Tax Determination in OX10, using the country key, the SAP System recognizeswhich tax type is valid for a plant and thus which taxes are relevant when creating an SDdocument.Define the Customer Taxes in OVK3, you will maintain the tax code in Customer Master.Define the Material Taxes in OVK4, which will then be maintain in Material Master.For example :-MWST GST 0 Tax ExemptMWST GST 1 Liable for TaxesNow, you define the Tax Determination in VK12.VK12 - Domestic Taxes/Export TaxesCondition Type MWSTCustomer Taxes Material Taxes Rate Taxes0 0 0 %0 1 0 %1 0 0 %1 1 9 %In this example, if both the Customer Master and Material Master Tax code is 1, Tax will be includedwhen you create the Sales Order.Tax Code in Customer Master / Sales OrderHow can we maintain the Tax Code (Tax code - which we maintain in MWST CondtionRecords) in Customer Master or in Sales Order?There are few points which I would like to remind you:1) MWST is a tax condition which is applied to customer to whom we are selling. The rate of tax isdepend on various parameteres, whether is fully liable for tax or expemted (in case of DefenceCustomer)2) There are few parameteres which we apply tax condition. Whether customer is tax liable?Whether material is tax exempted?For example, if you are selling a goods which are free for tax to any customer, put the Tax Indicator(at MMR as '0'). If yourmaterial is tax liable pur the Tax Indicator (at MMR as 1). If your customer is not liable for tax at all(like the case of IndianDefence organisations) put the Tax Indicator (at CMR as 0) or 1 in case fully tax liable.3) Now, at VK11 you need to mainatain your pricning conditions with all the combinations like:1 01 1

0 10 04) While maintaining your Material Master Records or Cusotmer Master Records, you must identify,which are tax liable and which are tax exempeted.5) In anycase, as a SAP standard Best Practises, while processing a sales order, you must retrieve aTax condition record from SAP database only and not entered Manually. Accordingly, at V/06, theMWST condition Defintions, the field for 'Manual Entries', it would be marked as - D (Not possible toprocess Manually).Due to this setting, normally, you cannot maintain Condition tax code during sales orderprocessing. And in Cusotmer Master, you can only maintain Tax Indicator and not Tax Code.6) In case your client insists for Manual entry of Tax code during Sales Order processing, you canchange the field at point 5) above to C-Manual entry is priority instead of D.Taxation Explain with an exampleI'm assuming that, the country is India and based on its requirement:Sales tax is a state government revenue. There are two types of sales taxes, Local sales tax &central sales tax. Local sales tax is intra state whereas CST is inter state.Example of LST : Point of sale i.e. delivering plant & ship to party are within the same state. Therates are defined by the respective state governments.Example of CST : The Delivering plant & Ship to party geographic locations are 2 different states.At the point of sales from one state, the ST goes to that state govt. & consignment is despatched tothe Ship to party. Once that consignment is received at the ship to party state, sales tax will belevied once the sales is registered there. For this case, the LST that is applicable by the Ship toparty further will not be applicable in all probability to be captured in SAP.Stock transfer : This does not attract any sales tax. The consignment is transferred from one Dplant to another D plant irrespective of inter/intra state sales. The invoice that is accompanied withthe consignment thus shall not have any final value. It's a zero value invoice, but the basic pricesneeded to be mentioned.The selling organisations normally needs to register with the sales tax authority of the respectivestate to have a warehouse or D plant to avoid the double taxation for their dealers/distributors.Now, the pricing procedure that is there in 4.7 is Factory sale with formula-JFACT, in which the CSTcondition type is JIN1 & the LST is probably JIN2. There may be surcharge cond types as well whichwill calculate the amount on either JIN1 or JIN2.For config :1.SPRO > S&D > Basic fn. > Pricing > Pricing control > Define & assign Pric. procedure > MaintainPric proc.

2. The tax rates are normally driven from the Tax classification of Customer & Material access. Todo this config, S&D >Basic fn. > Taxes. You need to include the condition type for country IN in'Define tax determin rule'.3. Same path : But go to Tax relevancy of master records where you configure the condition type &options of rates that will flow to these masters. One needs to understand here properly as u needto have unique combinations for picking the sales tax rates. I will try to demonstrate the smallestexample. Let's say, the LST rates are 2%,4% & 0%. I will have two options for material master here.1 for taxable & 2 for not taxable.For customer master, I will have 1-LST 2%, 2-LST4% & 3-LST0%. When I create master records forLST thru VK11 for JIN2, I will chose the access where the combinations of customer & material taxclassifications are available. If this access does not exist create it under an access sequence. Butnormally this is standard. The condition records will look like,Cust-Tax classi. Material tax claasi. Rate Tax code1 1 2% A12 1 4% A13 1 0% A1Remember, rates are flown from the tax codes. Tax codes can be created thru T code FTXP. This isnormally a FI job.Return material From customerYou need to receipt the rejected goods through SD Module (VA01 - Sales Order type RE).The steps are as follows :1. Create a return request. (Using Sales Order in SD)2. Create outbound delivery according to return request.3. If the setting is correct in the outbound delivery screen SAP will automatically switch post goodsissue button into post goods receipt. The setting is in sales order item category and delivery type.4. In the standard system the movement type used is 651.5. After post goods issues receipt is done using outbound delivery, the quantity is placed in blockedstock without value updating.6. You will then decide if the return quantity are indeed bad stock or not.7. Transfer Posting from block stock to unrestricted stock (mvt type 453), this will have accountingeffect (Debit Inventory, Credit COGS)8. Goods Issue to scrap account how to create new titles which can be used in creating the"address" view on the Vendor master.{T-Code: XK01}In config go to Basis Components --> basis services --> Address Management --> Maintain titletextsSAP SD: Scheduling Agreement Vs ContractA schedule agreement contains details of a delivery schedule but a contract just contains quantity

and price information and no details of specific delivery datesWhat's the difference between schedulling agreement with normal order?What's the condition for us to choose schedule line or order?Both of them contains schedule line, price, quantity.There are a couple major differences:(1) - Schedule agreements allow you to have 2 different sets of schedule lines (VBEP-ABART).Standard SAP you should have two sets of tabs - of schedule lines. One Forecast & the other JIT.Forecast forwards the schedule lines to planning (seen in MD04) and JIT passes them to shipping(VL10). They can be identical or different. Typically these are used for component suppliercustomers (namely Automotive). The customer will provide you 4-10 weekly buckets (usually aMonday date) of future forecast qtys. Also send you 1-2 weeks of individual FIRM ship dates - whichare entered on the JIT. It comes down to the customer not knowing exactly what they need nextweek, but they don't want to suprise you with a large order qty, where your lead times are 5+days. The forecasted qtys they sent last week should account for this.(2) Cumulative Quantities are tracked and influence how the schedule agreement passesrequirements to both forecasting and shipping. These qtys are sometimes requested by thecustomer on ASNs. Cumulative qtys reset at year end unless you've got a customer calendar oryou've modified standard SAP userexits to not reset.Schedule agreements are very nice when the customer sends EDI data (830s = forecast or 862s =JITs). Outside of that they can really cause trouble regarding daily maintenance, missingrequirements, cum qty corrections, year end processing, etc.One alternative would be to use customer independent requirements - entering the weekly,monthly forecasting qtys and entering standard sales orders (with or without multiple schedulelines) to represent the true firm qtys.Sales BOM ImplementationA bill of material (BOM) describes the different components that together create a product. A BOMfor a bicycle, for example, consists of all the parts that make up the bicycle: the frame, the saddle,wheels, and so on.Process FlowWhen you enter the material number of a bill of materials that is relevant for sales orderprocessing, the system displays the material that describes the whole bill of materials as a mainitem. The individual components are displayed as lower-level items.There are two ways to process a bill of materials in Sales. Once you have entered a bill of materialin a sales order, the system runs pricing, inventory control, and delivery processing at:- Main item level if the material is assembled, or- Component level if the material is not assembledThe type of processing used by the system is determined by the item category group that youenter in the material master record for relevant materials.Processing at Main Item LevelIf you want the system to carry out pricing, inventory control, and delivery processing at main itemlevel, enter ERLA in the Item category group field of the Sales: sales org. 2 screen in the

material master record of the finished product. This means that the components onlyfunction as text items and are not relevant for delivery. The following graphic shows how a bill ofmaterial is processed at main item level.Processing at Component LevelIf you want the system to carry out pricing, inventory control, and delivery processing at thecomponent level, enter LUMF in the Item category group field of the Sales: sales org. 2screen in the material master record of the finished product. In this case, only thecomponents are relevant for delivery. During processing the system automatically creates adelivery group. The latest delivery date among all the components becomes the delivery date forthe entire delivery group.How to Know that Sales BOM is working ornot?I have set up a sales BOM. How do I know or test that is is working or not?Once you enter a material (for whch you have created a BOM thru CS01) in the sales doc anothermaterial pops under the main material line item as a sub-item (s). If it doesn't then your BOM isn'tworking.In my experience BOMs work if all maintenance has been done properly.A number of things to check is:1. The bom hasn't been defined for the plant used, or you haven't defined the plant in SO.2. Main item category - has BOM application SD01 been assigned to it?3. Item categories for main items and sub-items have not been mainteined properly.4. Sales items maintenance - You should assign item categories for BOM header items and subitemsto a specific sales doc.5. Has the BOM itself been configured properly (i.e. right plant, BOM usage '5')?6. Are you trying it out on an order created after all BOM maintenance was done?7. Also , what's the 'Structure scope' set as? Anything except C may be useful here? We have thatset to A, since our BOMs are all single-level. You could set it to B if BOM are configured multi-level.Those are probably main reasons why BOM shouldn't work. Apart from that, just re-check yourwhole config - the truth is out there somwhere.What Is BOM Referring to SAP SDWhat is bill of material?By: MikeBILL OF MATERIALSWe need to maintain Material master records for the BOM Item and for the components also.The item category group of the BOM items is ‘ERLA/LUMF’ and the item category is ‘NORM’.Creating BOM item:- Logistics- Sales and distribution- Master data- Products- Bills of material

- Material BOMCS01 createSpecify the data for the following fields.Material: Specify the material for which components are to be maintained.Plant: Specify the plant of BOM item.BOM usage: Specify the application in which BOM is maintained (5 for SD).Alternative BOM: Specifies the sequence of a BOM within a group of BOMs.(L = stock item N = Non-stock item)In the overview screen specify the components which makes the main item and the correspondingquantities and save it.Note: During sales document processing if we enter the BOM item the system automaticallydetermines corresponding components.1) For the BOM to be exploded in the sales document the following customizing setting is required.A) If the item category group is ERLA the item category of the BOM is TAQ, in the definition ofwhich we have to specify the value A (Explode single level BOM) in the structure scope.B) If the item category group is LUMF the item category of the BOM item is TAP in the definition ofwhich we have to specify the value A in the field structure scope.2) If the item category group is LUMF the system shows price for the components but not for theBOM item. For this the following customizing setting is required.A) The item category of the BOM item is TAP which is not relevant for pricing, so the BOM item isnot Priced.B) The item category of the components is TAN which is relevant for pricing, so the components arepriced3) If the item category group is ERLA the system shows price for the BOM item but not forcomponents. For this following customizing setting is required.A) The item category of BOM item is TAQ, which is relevant for pricing, so the BOM is priced.B) The item category of components is TAE which is not relevant for pricing, so the components arenot priced.While creating sales document to get the list of alternative BOMs in the definition item category ofBOM item we have to check the field “Manual Alternative”24-07-2007ITEM CATEGORY DETERMINATION FOR BOM ITEMSD type ITCaGr Usg HLItCa DftItCaOR ERLA TAQOR NORM TAQ TAEOR LUMF TAPOR NORM TAP TANOR NORM TANOR NORM TAE TAE

OR NORM TAN TAENOTE: A – Explode single level BOM itemB – Explode multi level BOM itemCS01 – Transaction code for creating BOM ItemStatistical value ‘x’ or ‘y’Make TAP relevant for pricing but values for statistical only.Sales Order Mass ChangeI am a SAP SD consultant and recently faced with two new terms, mass order changeand ALV , I also need to know about the transaction code.There is transaction MASS which can be used to carry out mass changes in the sales order andother objects.Mass Maintenance: (Use to change multiple fields in multiple documents at the same time). I havedone mass change for customers; and orders should work the same way too.1) Try t-code [MASS] and select sales orders & execute2) Choose the table or tables for your selection criteria and also for fields you want to change.Then execute. (suppose your selection criteria fields are from "sales order header data" table andthe field you want to change, is in "item data" table)3) Put in the sales documents(21000000, 21000001) you want to change and also the items(10)you want to change.- click on " choose selection fields" button- From the Pool, move the fields you want to the "select fields" using arrows.4)From mass maintenace menu, click on "Enter new field values"-click on "sales order item data" tab and choose the field you want to change.(for example. I want to change plant for item 10)-enter the new value (of the plant to be)-click on "Adopt" and execute5)In "sales order item data" tab, you see the new value of the plant you entered at the top and theold values of item 10 are below.-click on "change field values" button. you see all the old values are changed to new values.-saveNote: it will take some time depending on how many records you have.Check: Go to [SM37] and see the status of the job you are running and once finished, export thespool file to a spreadsheet.Before you do mass maintenance, go to the particular table in [se16] and get the results. Then dothe mass maintenance and compare the results with this one. If they match, then you are good togo.Note: If you have any user exits that affect the results, ask them to deactivate the MODCHECKSstill you are done with mass maintenance & activate them again.Is there a way to change the billing date on a ton of sales orders with same old billingdate to a same new billing date?This can be done using the mass transaction:Transaction: MASSObject Type: BUS2032Tables: SD Document: Business item dataSel Field: Billing Date (MASSSDHE and MASSSDPO)

- Or you can just select by document numbers (May be more efficient)Execute - List will be provide for changesSel Chg Fld: Billing DateSet new billing date value in the New Values fieldClick on lower billing date columnClick on Carry out a Mass Change buttonClick on Save buttonSuggestion is to test this on a few orders in your development system to get a feel on how thisworks before applying this to any production data. MASS is a very powerful tool.I have 100000 sales orders whith an incorrect price and I would like to do a massivecondition update with pricing type "B" (Carry out new pricing). Is there a transaction orprogram for this?Go to VA05 execute the report. Select all sales orders you want to update the price, Go to the MenuEDIT --> MASS Change ---> New Pricing. System will display all the re-pricing options. Select B. Itwill re-price all the sales orders.You can try for one or two order initially check the results and if it is OK, then you can do for others.Release strategy for Sales orderIs it possible to have release strategy for sales order?Satish C JhaAs such SAP standard does not provide release strategy for sales orders similar to purchaseorders. However this requirement of your can be satisfied through authorisation profiles; what Imean to say is that the sale order to be kept incomplete by the person who does not have therequired authorisation & the person with proper authorisation will completeit for further processing. This is only one way of meeting your requirement.Balraj G SaigalIn order to emulate a release strategy similar to purchase orders you can use the status profile insales documents (BS02). IMG-Sales and distribution-Sales-Sales documents-Define and assignstatus profile.How to do rebate processingRebates Processs in SAP is divided into three components1) Configuring Rebates2) Setting Up Rebates3) Managing rebate agreeeements and paymentsPre-requsiistes- Check the following:1.The payer partner needs toi have the rebate field checked in the customer master on the salesarea-billing doc tab.2.The Billing type must be marked as relevant for rebates.3.The Sales Organisation must be marked as relevant for rebates.Condition Technique :Rebates, use the condition technique, but distinguish themselves from pricing in applying totransactions over time, versus on a transaction basis. Rebates have their wn field catalog and their

own condition table naming convention.So you could have two condition table "001" one for pricingand one for rebates, which could have different key fields. You need to use the technical namesA001 For pricing and KOTe001 for rebates when you use the query type using transaction SE 16..Use create access sequence (AS). Enter 1 in field category for rebate specific. AS after going thruthe right path of maintaining access sequence for rebates.The big difference between the rebate and the pricing access sequence is that there is no exclsuionflag available for rebate related AS. This means multiple tables for an access sequence can beaplied at the same time.Rebate related condition types are identified by codnition class -C.After defining and creating condition types for rebated include them in the pricing proceedure. Therequirement should be 24 here which implies that the accruals are calculated on the basis ofinvoice/bill.The other fields- alctyp and altcbv does not allow you to manipulate how a rebate is calculated.Also, remove the requiremnt 24, if u want to see reabtes at order time.Now payment of rebates:Payments can be maunal or in full settlement. When you do manual payments, it defines howmuch can be paid out during a partial settlemetn. You use partial settlement only when rebateagreement is defined for a full year but the paoyouts are supposed to happen on a monthly,quarterly or anyother specified period.These accurals are based on sales volume and when they are posted billing is created int ehfollwoing manner. Provision for accruals is debited and Sales revenue is credited. When rebatecredit memo is createdCustomer account/ is debited andAccrual provision account is credited.Also, please note that when rebates are created without dependent ona material but oncustomer/material you need to refer to a material for settlement.With Compliment: SriniI have this same problem found in:http://www.sap-img.com/sap-sd/rebate-process-with-ref-to-so.htmHowever, can somebody explain it as I have problem in understanding the link.What exactly do you wish to know in Rebates? The total outline of the Rebate process or each andevery step in the SAP system?First of all rebates are more or less discounts which are offered to customers. The rebates arebased on the volume of the business the customer does with you within a specified time. for eg ifthe customer agrees for Rs.1 Crore worth of business with u in 1 year, then you activate yourrebate porocess. if at the end of the year the customer DOES achieve the target u offer him say2/3/4 % whatever is decided. The rebates are passed on to the customer in the form of Creditnotes.The rebate can be given to the customer at one time or in installments also.This is broadly the outline of the rebate process.

R.SreeramNote : I recomend you to study the theory part of why rebate and why not a discount.This will help you understand better.May be I can help you with rebate process.(IN -IMG)1. define a rebate agreement type2. define a condition type group3. define a condition type and place this conditionType in the pricing procedure.(REQUIREMENT=24)ALSO IN THE PROCEDURE- ACCRUAL KEY = ERUYOU ALSO HAVE TO DO THE ACCOUNT DETERMINATION FOR REBATES.Once you have defined all the 3 and assignment starts.Assign the agreement type to the condition type groupAssign the cond type group to the condition type.Condition technique is also used in rebates.REBATE ACTIVATION- IN CUSTOMER MASTER, SALES ORGANISATION AND FOR THE BILLINGDOCUMENT.After having done this please proceed to maintain the condition record for the rebates (transactioncode-vbo1)Note: if you maintain the requirement coloumn with the requirement as 24 - the rebate will beaffected in the billing document and if you dont give the requirement as 24 your rebate will beaffected in the sales order.The rebate process is completed when you have created a credit memo to the customer.The document type for the partial settlement is R3.Please make sure you open two screens SO THAT YOU CAN COMPARE THE NEW ENTRIES WHATEVER YOU'RE DEFINING WITH THAT OF THE STANDARDS or first you try with the standard conditiontype boo1, boo2boo3 boo4.AFTER YOU HAVE FINISHED A COMPLETE SALES CYCLE OF CREATION ORDER , DELIVERY ANDBILLING.GO TO THE CONDITION RECORD IN CHANGE MODE (VB02) AND SETTLE THE ACCOUNT PARTIALLY.I hope this will be of any help to you.PraveenIn a simple way,1. First you need to create a Rebate agreement.2. Create condition record for rebate giving the rebate rate and accrual rate.3. when the rebate relevent billing doc is generated, the rebate and accruals are determined andposted in a seperate GL account as a noted item - amount to be settled. Also it gets copied in therebate agreement.4. create settlement run using credit memo request and then credit memo to settle this amountwith the customer.

This is what the link says.Rebate Process with Ref. to SOIf I need to make a rebate for a customer what is the process involved.I am providing some info on rebates which I know.Rebate agreemnts is based on agreement types.Conditon records which are created like B001 andB002 are linked to the rebate agreeements specifying the rebate rate + the accrual rates.conditionrecords specify the rebate rate and the accrual rates.Consider an example..You decided to give a rebate of 3% to a customer whose sales vol is $1000 for a particular SOThen the rebate value is $30..Now when you make the rebate settlement by doiing the Credit memo and you decide to pay $27,then the accounting will be generated saying 27$ paid towards rebate and 3$ is the accrual whichyou owe to the customerProcedure:Rebate agreement: Transaction code: VB01When you go to VB01, choose agreement type 0002 and then in conditions giveMaterial rebate1 2020 30Now create a sales order with a material say M-11 for SOrg 1000 12 00 with QTY 6Now check VB03 and see rebate agreemtent it will say Accruals 120 and payments 0since your rebate is not settled still.Rebate setllementGo to VB02 enter ur sales deal no, and change the agreemetn status to B then enter Shift+F12 andenter the amount to be paid for example u say $80Then check in rebate payments rebate doc and partial setllemetn since you have not paid in full.View the credit memo requestRemove the Billing bloock Go to VA01 and put order type G2 ,,,go to create with ref and enter urSales order no,,,save the doc now...Then go to VF01 and enter the credit memo reqst no generated...save the doc no and go to VF02and say release to accountingNow the final settlement will be this wayAccruals:120Accrual reversed:80Rebate pay:80Amount payable:40So the balance 40 is still the accrualThis is an example how a rebate will be processed with ref to a SO with an example.How to do a rebate agreement for aspecific customers with settings details?1. Create a condition by copying a a standard condition like BO03 in V/062. Assign this condition in the std pricing procedure with acct key as ERB and accural key as ERU -

V/083.Create a Rebate Agreement in VBO1 (It is O = Owl and not zero). No will be generatedchoose 003 - Customer rebates, enter the customer code, the validity and check for the status shldbe in Open, click on the conditions enter the percentage and accrual amount. You also can havescales in this. Also you need to maintain the material for the settlement4. Create a sales order for that customer and check the rebate agreement.5. You can see the rebate condition in the invoice only.6. Once you have posted the invoices, then go to rebate agrrement no. clicl on verficayion and itwill show the order details.7. For settlement change the status of the rebate to B - release for the settlement.8. Credit memo request will b generated copy the no. and go to VA02, remove the blocks if any andcreate an invoice (credit memo).this will show u the accrual amount.9. In both the invoice and the credit memo check the posting - accounting document it will show uthe accrual as negative.10. Again go to rebate aggreement and check the status it will show you D - Final settlement ofagreement already carried outConsignment Sales Process in SAPThe consignment process in SAP standard consist of four small processes:Consignment fillup (send materials to customer consignment).Here you have a consignment fillup order and a consignment fillup delivery.Consignment issue (issue materials from customer consignment to the customer).Here you have a consignment issue order, consignment issue delivery and a consignment issueinvoice. (the flow is very similar to a normal OR flow, but the materials are issued from theconsignment stock instead of plant stock unrestricted).Consignment return (return materials from customer ownership to customer consignment).Here you have a consignment return order, consignment return delivery and a consignment returninvoice. (the flow is very similar to a normal RE flow, but the materials are returned to theconsignment stock instead of plant stock returns).Consignment pickup (pickup consignment stock and move it to plant stock).Here you have a consignment pickup order and a consignment pickup delivery.Note that in consignment fillup and consignment pickup there are no invoices since there is nochange of ownership for the materials.How to perform a consignment order?In consignment orders you are allowing the stock to sit in your customer location. Once he informsthat he used the stock you will invoice him. If he returns the stock you will accept the stock to takeit back.It is defined in 4 steps.1. Consignment fill up:Sales document type is KBItem category KBNshedule line category E1

In this step, you are not invoicing the customer. document flow is sales order ---- delivery itemcategory. It will not be relevent for billing and pricing because you are not charging money forthese goods in this step.In schedule line category, you will set movement type 631 & set for availability check and TOR.2. Consignment Issue.Once the customer informed you that he used all the goods or partial goods then you will createconsignment issue for used goods.Sales document: KEItem category: KENshedule line category: C0 or C1Here you are invoicing the customer(because he used the goods). you are assigning the deliverydocumnt and billing document to the sales document.In item category, you are setting relevent for billing, pricing, special stock.In schedule line category, your setting is 633 movement type, relevent for availability check & TOR.3. Consignment Return:Customer found that some goods are damaged or he not able to sold the goods he want to send itback. that you are creating this document.Sales document type: KRItem category: KRNShedule line category: D0You will assign delivery document and billing to sales document. you will create return order, returndelivery, return billing.Your setting item category relevent for billing, returns, pricing, special stock.Your setting schedule line item category: 634 movement type, NO availability NO TOR.4. Consignment Pick up:Even if you create the consignment return the goods are not come to direct to your plant. For thatyou need to create consignment pick up. here the owner ship is not changing so you do not need tocreate billing.Assign retrun delivery to sales document type.Sales document: KAItem category: KANschedule line category: F0 & F1Your setting item category relevent for returns. any shedule line category relevent for 632movement type, MRP, availability check, delivery.Now you check your plant stock. Stock will increaseIssue free goods to selected CustomersClient wants to issue free goods to selected customers after the said customer buys aspecified quantity of a good during the festive season starting 02 December to midJanuary. for example customer A buys 34 cartons of Corn Ice-cream, we offer him 12free corns. this should then reflect as cost in our accounts. the rest of the system isalready up and running and should not be inconvinienced. How do I set it up?1.Run trans. VBN2 to first create master record for free goods as follows:Enter following information in selection screen:

- Free goods type: NA00- Sales org, distribution channel, customer # and execute.Now in next screen create the record as follows:- First select the exclusive button and verify that you are in exclusive view.(that is if you want exclusive)- Material#, Min qty - Say 34 cartons. (check in what units you want to manage)From: 34 cartonsunit of measure:Free goods: 12 PcsUnit of measure: PcsCalcualtion type: 1 or try the other optionsDeliver control: Blank or any of the other options suitable to you.Now save and exit.Now run VA01 for 34 cartons and press enter. The system will automatically propose the freegoodsitem at no additional charge. Try higher order qtys and see if the free goods qty are scaling up.If not adjust the calculation parameters in the master record screenIt should be transaction VBN1. Sorry for the error.VBN2 is to change the record. VBN1 creates it.Kris JIf you want to give free goods to some of the customers than1. create a customer group say 99 for FREE GOODSIn Free Goods Menu:2. add a feild catalog for CUSTOMER GROUP3. create a condition table (free goods) say 555 only for customer group4. create a sequence say FREE with condition table 5555. create a condition type say FREE with6. maintain pricing procedure say ZFREE with condition type FREENow assign:7. Active Free goods Determination or Assign with your sales organisation this procedure ZFREE8. Create free goods determination with transaction code /nvbn1 for FREE with Key Csuomer Group99 for exclusiveGive customer Group say 99 and from 34 to 34 free 12Supressing Fields in Sale OrderTo make optional / mandatory you can use in IMG - S&D-> Basic > Functions-> Log of incompleteProcedures => select the fields > from the tables and the system will check for them (OVA2/VUA2)To make a filed entry enabled or grey (non-entry allowed):User exits in the program MV45AFZZ-USEREXIT_FIELD_MODIFICATIONThis user exit can be used to modify the attributes of the screen fields.To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be editedtogether during a modification in ABAP.If a field has no field name, it cannot be allocated to a group. The usage of the field groups

(modification group 1-4) is as follows:Modification group 1: Automatic modification with transaction MFAWModification group 2: It contains 'LOO' for step loop fieldsModification group 3: For modifications which depend on check tables or on other fixed informationModification group 4: is not usedThe FORM routine is called up for every field of a screen. If you require changes to be made, youmust make them in this user exit. This FORM routine is called up by the module FELDAUSWAHL.With Compliments by: Taner YukselActually suppressing fielding sales orders userwise is quite easy. We are doing it in our company.For this we use userexit FORM USEREXIT_FIELD_MODIFICATION in MV45AFZZ.Below is the sample codeIF SCREEN-NAME = 'VBKD-ABSSC'.AUTHORITY-CHECK OBJECT 'ZMV45AFZZ' ID 'SCRFNAME' FIELD SCREEN-NAME.IF sy-subrc = 0.SCREEN-INPUT = 1.else.SCREEN-INPUT = 0.ENDIF.endif.You place the authority check object in authorization profile in the role of the users, who shouldhave access to the field (in this case it is VBKD-ABSSC), and there assign the corresponding fieldsthat are to be accessed via this userexitSome Light on Batch DeterminationOn batch determination, the whole process, how it is determined automatically in theorder.A1) Normaly we use batch determination at delivery level, because at the time of order materialmay or may not be created.for this material should be configured with batch and batchdetermination should be checked in sales views of material.A2) Batch Determination during order Creation.For this you need to maintain a Classes d for you Material. Depending on the Manufacturingprocess you can define the characteristics for your material.Ex: Purity for Medicines, Resistance for Electric Items.You need to create a class (You might have to create a new class type) which incorporates thecharacteristic.First Create the Characteristic Using Ct04 and then using Cl02 create the Class including thischaracteristic.Then in your material master Classification View Enter this class.Then Create a Batch for the particular plant and Stor Loc using MSC1N.Give the value of thecharacteristics in this batch.Then go to SPRO ->Logistics General ->Batch Management and maintain the Condition Technique

(Procedure, Strategy Types and assignment to sales docs etc).Then Create the Batch Determination Record using VCH1Difference between Item Proposal andMaterial DeterminationWhat is the difference between the item proposal and material determination productproposal?Item proposal and product proposal are the same.Item proposal is the list of materials and order quantities that can be copied into the sales orderfrom the customer master data.We use VA51 to create the item proposal. Here we get a number.This number is then linked to thecustomer master data in the sales view. This is very commonly used.Material determination is very closely related to item proposal /product proposal and is used toswap one material for another in the sales order using the condition technique. I have not seenMaterial determination procedures used in the projects I have worked.SAP Tips by: Prashanth HarishItem Proposal or Product proposal:"Item proposal is same as product proposal & SAP uses the two terms interchangeably."An item proposal is a list of materials and order quantities that can be copied into the sales order.Items can also be selected from a list and copied into a sales order."1) Use transaction [VOV8] to configure the document type ("MS" for product proposal).2) Use transaction [VA51] to create a proposal.3) Enter the item proposal on the sales area data (sales tab) of the customer master record.4) In [VA01] to create a sales order, Select Edit & propose items."Material determination:"Material determination uses the condition technique to swap one material for another whencertain conditions apply. Materialdetermination is triggered by the material entered in the line item of the sales order.Use transaction [VB11] to create a material determination condition record. And [OV12] forconfiguration of material determination.Material determination is useful when old product is becoming obsolete or a new product isreleased by the company at specific date."Steps for SD Variant ConfigurationSome light on Variant Configuration in Detail.The procedure is as follows:Create a Material - KMAT type with Item category (002)Create Charateristics in CT04 - Zbike, where in values mention the Color of the bile likeRed, Blue etcCreate another characteristics in CT04 - ZPrice, where directly go the additional data taband maintain the table SDCOM and field VKOND (ABAP Dictionary it will ask for)Assign these two characteristics to a Class in CL01 - ZBikeclass ( Type 300) incharacteristics tab page.Then go to CU41 Configuration profile select the material and enter the description click onthe class assignment ie assign Zbikclass.Now go back to CT04 - enter Zbike -go to values- select Red- go to extras - Other

Dependencies - Select Procedure enter in front 10 write - $self.ZPrice='Red' and saveNow go back go to extras - Other Dependencies - assignments and assign relationship ( bydefault it will come just save)Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter infront of 10 write - $self.ZPrice='Blue' and saveNow go back go to extras - Other Dependencies - assignments and assign relationship ( bydefault it will come just save)Now go to VK11 - Enter VA00 (Condition)(For Std RVA001 Pricing Procedure) - enter variantRed and Blue give the rates accordingly and create the sales order. *-- ShaikZaheeruddinTell me about variant configaration?What are the type of questions we can expect in that?Variant configuration is used where you have a configurable material like computer (made up ofcomponents like processor, monitor, keyboard, mouse etc). These components are called ascharacteristics in variant config. Again this will be having values like processor can be either P4 orP3, monitor can be 15" or 17" etc.Based on the values selected the variant pricing will happen using the condition type VA00.Possible questions you can expect are:- What is variant configuration?- What is characteristic?- What is value?- What is class?- What is configuration profile?- What is dependency and what are the types?- What is a variant table?- And the transaction codes for the above.Number Ranges In Sales OrderThis is regarding number ranges defining and assigning tips which you can follow as below:Whenever there is a new Sales Org being created, you will be required to maintain Number Rangesfor Sales Documents which are allowed for your New Sales Area.Number Ranges can be maintained Internally by the system, however it can be maintainedexternally also if you customize it accordingly.In Standard SAP the Transaction code for Maintaiing Number ranges externally is VN01.Defining - The same can be reached through in IMG as : Sales & Distribution-->Sales-->SalesDocument Header-->Define Number Ranges for Sales Documents.Here you provide the system a specific Number range as follows:Number range Key +Start Number range+ End Number Range+Current NumberFor Example: If you want to propose the following Number Range*1 9000076000 9000076999 0The Current Number field will be kept zero as you are proposing new number range and no salesdocuments have been created on it , Obviously..*1 is a Unique Two digit Alphanumeric Key, while proposing your key, you should ensure that itshould not be there in the system as existing.

If you propose a key that is there in the system or if the Number Range (Start and End Series) isthere in the system already, the system will throw a message that Interval already already exists.So choose a key that is unique, and which is not there in the system.Here , by making this , you are assigning a Key to a Number Range Series.All the symbols can be used along with numbers from 0 to 9 and Alphabets from A to Z and in anyorder. For example: !1, ^A, BB,Z*,M2.........Assigning - In Assigning, you assign the particular Sales Document to the Number Range you havealready proposed as above.The Assigning Part is done as follows:The Two digit Alpha Numeric Key is maintained or Assigned to the respective Sales Document typein V0V8.This can also be reached in IMG by:Sales & Distribution-->Sales-->Sales Document Header-->Define Sales Document TypesLocate the particular Sales Doc Type, and double click on it to display it configuration. Here you putthe Two Digit Number key in the Field- "Number range External Assignment"Besides this:If a new Shipping Point is created then Delivery Number ranges are required to be maintained.Similarly,If a new Plant is created then Billing Number Ranges are required to be maintained.What is Debit note and Credit noteWhat is Debit note and Credit note? What is the purpose? How we create?1. A transaction that reduces Amounts Receivable from a customer is a credit memo. For eg. Thecustomer could return damaged goods. A debit memo is a transaction that reduces AmountsPayable to a vendor because, you send damaged goods back to your vendor.2. Credit memo request is a sales document used in complaints processing to request a creditmemo for a customer. If the price calculated for the customer is too high, for example, because thewrong scale prices were used or a discount was forgotten, you can create a credit memo request.The credit memo request is blocked for further processing so that it can be checked. If the requestis approved, you can remove the block. The system uses the credit memo request to create acredit memo.You can use credit memos in Sales and Distribution (SD) for assigning credit memo requests to theopen invoices and in Financial Accounting (FI) for assigning credit memos and payments to theopen invoices and carry out clearing with them. If you use both Financial Accounting (FI) and Salesand Distribution (SD), there is a 1:1 relationship between the credit memo request and the creditmemo item posted in Financial Accounting (FI). As soon as you bill the credit memo requesttogether with other sales orders, or distribute the items of one credit memo request to severalbilling documents, the assignment is no longer valid and the system will not process it.For credit memos, credit memo requests, and payments, you have the following assignment

options:- Assignment to a single invoice- Assignment of a partial amount to an invoice- Assignment to several invoicesWhen you post credit memos, the payment programme processes them automatically. If the creditmemo is specifically related to a particular open invoice item, the payment program automaticallyattempts to offset the credit memo against the open item. If it is not possible to completely offsetthe credit memo against an invoice, you can post a debit memo to the vendor, who is to reimbursethe amount. Then you can apply a multilevel dunning program.3. Debit memo request is a sales document used in complaints processing to request a debitmemo for a customer. If the prices calculated for the customer were too low, for example,calculated with the wrong scaled prices, you can create a debit memo request. The debit memorequest can be blocked so that it can be checked. When it has been approved, you can remove theblock. It is like a standard order. The system uses the debit memo request to create a debit memo.4. As mentioned above, creating a credit or debit memo request enables you to create credit ordebit memos based on a complaint. For this first create a sales document with the order type for acredit or debit memo request. You can create the debit or credit memo requests in the followingways:– Without reference to an order– With reference to an existing orderHere you enter which order the complaint refers to.– With reference to an invoiceHere you enter which invoice the complaint refers to.In all cases, you specify the value or quantity that should be in the credit or debit memo5. You can block the credit or debit memo request from being billed in Customizing. Go to Sales ->Sales Documents -> Sales document header -> Define sales document type and select the billingblock field in the billing section. This request can later be reviewed along with similar ones, - ifnecessary, by another department. The request for a credit or debit memo can then be approvedor rejected.Configure Intercompany Stock TransportOrderExplain STO.STO is Stock Transport order. It is used for inter company transfer of goods. Plant to plant transferand even transferring raw material to Third party contractors (Job Work).The Process is you create a STO do delivery against the STO and create a Billing Document againstthe STO.How to configure the inter-company Stock Transport Order? - PrasseeMaterial should exist in both the plants (Delivering & Ordering),Internal customer should be assigned to the ordering plant ( MM -> Purchasing -> Purchase Order

-> Setup stock transport order -> assign the internal customer to the ordering plant and assign theSales area of the internal customer.Tcode : OMGNAssign its Sales area to the delivering plantAssign the document type and Delivery type NB and NLCCAssign the Supplying plant --> Receiving Plant --> NBTake the delivering plant and assign the sales area.Vendor master has to be created and assaign the supply source ( Delivering Plant).Create a puchase order ME21N ---> SaveDelivery VL10 G ---> Calculation rule (appropriate) --> Assaign the purchase order number hereand execute.Select the Delivery creation line and do the back ground process.Start the log display and see the delivery document number by the documents buttonGoto VL02N --> do picking and PGI --> Then do the MIGO with respect to the delivery document.Billing (Intercompany pricing conditions should be set).Third Party SalesProcess Flow for 3rd Party SalesCustomize the third party sales in summary:1. Create Vendor XK012. Create Material – Material Type as "Trading Goods". Item category group as "BANS".3. Assign Item Category TAS to Order type that you are going to use.4. A sale order is created and when saved a PR is generated at the background5. With reference to SO a PO is created (ME21N). The company raises PO to the vendor.6. Vendor delivers the goods and raises bill to company. MM receives the invoice MIRO7. Goods receipt MIGO8. Goods issue9. The item cat TAS or Schedule line cat CS is not relevant for delivery which is evident from theconfig and, therefore, there is no delivery process attached in the whole process of Third partysales.10. Billing *-- Seema DharSD - 3rd party sales order Create Sales OrderVA01Order TypeSales org, distr chnl, divEnterSold toPO #MaterialQuantityEnterSaveSD - 3rd party sales order View the PR that is created with a third party sales orderVA01Order Number

Goto Item OverviewItem ->Schedule ItemSD - 3rd party sales order View the PR that is createdME52NKey in the PR numberSaveSD - 3rd party sales order Assign the PR to the vendor and create POME57Key in the PR numberToggle the "Assigned Purchase Requisition"ExecuteCheck the box next to the materialAssign Automatically buttonClick on "Assignments" buttonClick on "Process assignment"The "Process Assignment Create PO" box , enterDrag the PR and drop in the shopping basketSaveSD - 3rd party sales order Receive GoodsMIGO_GRPO NumberDN NumberBatch tab , click on classificationSerial Numbers tabDate of ProductionFlag Item OKCheck, just in casePostSaveSD - 3rd party sales order Create InvoiceMIROInvoice DateLook for the PO , state the vendor and the MaterialCheck the boxClilck on "Copy"Purchase Order Number (bottom half of the screen)AmountState the baseline dateSimulate & PostInvoice Number*Invoice blocked due to date varianceSD - 3rd party sales order Create a delivery orderVL01NIn the order screen , go to the menu Sales Document , select "Deliver"Go to "picking" tabState the qty and save

SD - 3rd party sales order Create a billing documentVF01Ensure that the delivery document is correct in theEnterGo to edit -> LogSaveCross Selling : How To Configure(1) Cross Selling: How to configure and the menu path details.(2) While creating individual order I face one error 'Plant not assigned to ControllingArea': How to configure controlling area and menu path.(3) Menu of path of subsequent Delivery Free of Charge.By : AhmednspCross selling is a concept by which the business can improve the sales. By using this concept thebusiness can offer combination material for ordered material.Ex: If the customer placed for the order for computer then computer stand can be suggested as acombination material. It can be mapped by using cross selling concept that uses conditiontechnique.When the user raises the sales order and specifies ordered material then system automaticallypup-up a box in which system displays suggested materialConfiguration settings:1) Define determination procedure for cross selling:Path:- IMG- SD- Basic function- Cross selling- Define determination procedure for cross sellinga) Create condition table:Here we define condition table ex: - materialb) Maintain access sequence:Here we define access sequence ex: C001 and assign condition table ex:011 that we define inprevious step.c) Define condition type:Here we define condition type C001 and assign it to access sequence C001 that we define inprevious step.d) Maintain procedure:Go to new entries and define cross selling profile Ex: CS0001 and assign our condition type C001that we define inthe previous step.2) Maintain customer/document procedures for cross selling:a) Define customer procedure for cross selling:Here we define customer cross selling profile Ex: "B" -- cross sellingb) Define documents procedure for cross selling:Here we define document cross selling procedure ex: `B"- cross sellingc) Assign document procedure for cross selling to sales document:

Choose sales document type "OR" and assign document cross selling procedure ex: "B"3) Define and assign cross selling profile:a) Define cross selling profile:Go to new entries, specify cross selling profile key with description- Specify cross selling pricing procedure (CS0001)- Assign the pricing procedure (RVA001)- Specify cross selling dialog box indicator WIf it is "A" – dialog box appears only in request.It is blank – dialog box appears in request and after date is releasedCheck cross selling ATP indicator: If you check it , system carry out ATP check for cross sellingproduct.b) Assign cross selling profile:- Go to new entries, specify sales area- Specify customer cross selling procedure –B- Specify document cross selling procedure – B- Assign cross selling profile -- CS0001Maintain condition record for cross selling (VB41):Path:- Logistics- SD- Master data- Products- Cross selling- VB41Specify condition type C001Specify the order material, select condition line itemClick on alternative material icon and maintain alternative material with cross selling deliveryconditions optionsBlank – Out bond delivery takes place regardless of main item"A" -- Out bond delivery only if main item has been partially deliveredGo to VD02, sales area section of sales tabAssign customer procedure for product proposal - BSave it and exitGo to VA01; raise the sales order with order material check the effect.4) Path to created controlling area:Img-->Ent Str-->Defintio-->Controlling-->Maintain Controlling Area , here you can createcontrolling areaAn Example Of Third Party SalesScenario:2 companies are created in system - India & Singapore Customer places sales order forparticular material on Singapore. Singapore is not able to produce the same. They passon the order to India for processing. After processing India ships the material directlyto the customer along with necessary documentation. Invoice copy is passed on toSingapore. Final Commercial Invoice will be raised by Singapore. How can the abovescenario handled?By: Balaji

You can do this using third party sales.The third party sales process is as under.1) Singapore company creates an order for the singapore customer.2) Because of the configuration settings of the sales document type, item category & schedule linecategory, as soon as the order is saved a PR (purchase requisition) is automatically generated. Thisis converted into PO (purchase order) and sent to the indan company.3) Indian company supplies the material directly to the singapore customer.4) Indian company sends the invoice to the singapore company.5) Singapore company does the invoice verification in MM using tcode MIRO.6) Singapore company raises the invoice to the singapore customer.In standard SAP, item category TAS is used for this. The schedule line category is CS. Here you cansee a field 'order type' with value 'NB'. This triggers the automatic creation of the PR.Plus in the material master also you need to do certain settings.1) If you are always following a third party process for a material then you have to create thematerial using item category group BANS. The procurement type should be marked as externalprocurement (F) in MRP 2 view of the material master record.2) If you are not always allowing third party order processing then you can create a materialmaster record with item category group as NORM and the procurement type should be marked as(X) meaning both types of procurement (in house manufacturing and external procurement).In the item category the billing relevance should be 'F'CINSAP SD CIN ConfigurationWhat is CIN?CIN Means Country India VersionIn Indian Taxing procedure, Excise Duty plays a vital role in manufacturing cenario’s. Excise relatedconfiguration is known as CIN configuration. CIN Configuration is a topic in itself.Some info on CIN Configuration (it may not appear as understandable below, but if you check onscreen, it will be understood better)Country Version India comes with four pricing procedures as follows:- JINFAC (Sales from manufacturing plants)- JINEXP (Export sales)- JINDEP (Sales from depots)- JINSTK (Stock transfersCIN: IMG > Logistics - General > Tax on Goods Movement > India > Basic Settings > MaintainExcise RegistrationsIn this IMG activity, you maintain the data relating to your excise registrations.- Enter each of your excise registrations, specifying a four-character code for each ExciseRegistration IdsIn this activity, you maintain excise registration IDs. You create one ID for each of your business's

excise registrations.- For each excise registration in your business create a registration ID, and state:- Which taxes the registration covers (additional excise duty, special excise duty, and cess) Fieldsfor any taxes that are not covered will be hidden in transactions involving excise duty.- The maximum number of items to be printed on each excise invoice- Whether you are allowed partial CENVAT creditsMaintain Registration ID NUMBER, Excise code number, excise registration numberECC Number: Specifies the organization's ECC number.Excise Registration Number: A number assigned to each premises or location that has registeredas a manufacturer with the excise authorities.Every entity with an excise registration number is required to keep its own excise books.Excise range: Specifies the excise range in whose area the excise registration is located.Excise Division: Specifies the excise division in whose area the excise registration is located.Excise Collectorate: The code of the excise collectorate in whose area the excise registration islocated.Indicator for confirming, AED usage Additional Excise duty Percentage.These are livable under the additional duties of excise act. These duties are in addition to basicexcise duty and special excise duty. Example - Additional Excise duty is livable in case of textileproducts, tobacco and sugar.Similarly for SED CESS Number of Items in Excise Invoice Shows the maximum number of lineitems that the authorities allow per excise invoice.Dependencies - This information is used when you create an excise invoice in Sales andDistribution (SD) for factory sales and for other movements. This information is used to split thetransfer postings' items into multiple subcontracting challans.Excise register set description: Description of the excise registers set.Partial CENVAT Credit: Indicates that the excise registration ID is allowed to credit only a portion ofits input excise duty to its CENVAT accountDependencies - When you post a goods receipt, the system splits the input excise duty on thematerial into its deductible and nondeductible amounts. It posts the deductible duty to theappropriate CENVAT account, and adds the nondeductible duty to the material value.This information is also shown when you post the vendor's excise invoice.Maintain Company Code Settings.In this IMG activity, you maintain the data relating to your company codes.Document Type for CENVAT Postings.It controls, which document type the system uses when making CENVAT postings in FinancialAccounting (FI). Here ED is document type for cenvat posting.Indicator for providing debit account overwritingDebit Account Overwrite Indicator. X - Indicates debit accounts can be overwritten. Use In excisejournal voucher transaction. It provides the flexibility to the user to enter the debit account of hischoice depending on the nature of transaction.Automatic balance Indicator - Excise year start month. The calendar month marking the beginningof the excise year. This start month represents the month for the start of the excise invoice

number range. The month 04 is entered here indicating April of the calendar year as the startmonth for excise invoices. Any change by the Excise authorities regarding start month should betaken care of by an entry in this field and initialization.Excise invoice selection procedure :Excise invoice selection type. To indicate the method opted bythe company for selecting the excise invoice. It can be either earliest or latest invoices that werereceived. Number of excise invoices to be selected Indicates the number of excise invoices thatneeds to be selected in the excise invoice selection.Days to be considered for excise invoice selection Number of days from document date for exciseinvoice selection.Example - If the value of this field is 20 and today is 28-03-97. The excise invoice selection willshow the related invoices only for the period 08-03-97 to 28-03-97.Document type for TDS FI posting: Financial accounting document type for TDS posting.Document type for FI posting on Utilisation Financial accounting document type for TDS posting.Indicator for item level excise duty round off - This indicator is to be used for deciding whether Itemlevel exciseduty amount rounding off is required during procurement cycle. If marked 'X' then the excise dutyamount will be rounded off to the nearest rupee at the Purchase order level. This will not round offthe CENVAT credit to be taken. If the duty amount is less than one rupee then no rounding is doneRounding off of Excise duty for outgoing excise invoice - You can round off the Excise amount to bepaid during an outgoingExcise invoice by marking this indicator as 'X'. The rounding is done at the item level for each itemwhere the amount is greater than 1 Rupee.Immediate Credit on Capital Goods - Instructs the system, when you verify a goods receipt forcapital goods, to immediately post half of the input excise duty to the appropriate CENVATaccounts. The rest is posted the CENVAT on hold account, for use in the following year.CVD Clearing Account - Specifies which G/L account the system credits when you take a CENVATcredit on countervailing duty in the Incoming Excise Invoices transaction.Exchange rate type - Key representing a type of exchange rate in the system.- You enter the exchange rate type to store different exchange rates. Example - You can use theexchange rate type to define a buying rate, selling rate, or average rate for translating foreigncurrency amounts. You can use the average rate for the currency translation, and the bank buyingand selling rates for valuation of foreign currency amounts.Exchange rate type to be used for Export excise duty converts - When you are creating an Exciseinvoice for export sales then the exchange rate for duty calculation will be picked up using thisExchange rate type.Maintain Plant Settings - In this IMG activity, you maintain excise information relating to your

plants.Plant Settings - In this activity, you maintain excise information relating to your plants.For each plant:- Specify whether it is a manufacturing site or a depot.- Assign it an excise registration ID. - You can assign the same ID to more than one plant, ifrequired.Depot - Indicates that the plant in question is a depot. - Depots are required to prepare register RG23D, and follow different procedures for goods receipt and invoice generation.- Number of goods receipt per excise invoice.- Multiple GR for one excise invoice, Single credit- Multiple GR for one excise invoice, multiple creditMaintain Excise Groups - In this IMG activity, you define your excise groups. For each excise group,you can also control how various excise invoice transactions will work.Excise Groups - In this activity, you define excise groups. An excise group allows you to maintain aseparate set of excise registers and excise accounts. The RG 23A, RG 23C and PLA serial numbersare created for an excise group.Recommendation - Under normal circumstances, excise authorities require every business tomaintain only one set of excise registers and one set of accounts. But through exemption from theauthorities, multiple books can be maintained.If your company has only one set of excise registers, then you need to maintain only one excisegroup.1. Create one excise group for each set of registers that you need to keep.2. Assign the excise groups to plants.3. Maintain whether this Excise group is for a depot or not.If you receive only one consignment for an Excise challan then you can leave GR's per EI as blank.If you receive multiple GR's for a given Excise challan and would like to avail multiple credit markthe GRs per EI as 'Multiple GR's for one excise invoice, multiple credit'. Alternatively if you want toavaila the credit only after all the goods receipts have been made mark it as ' Multiple GR for oneexcise invoice, single credit'.4. If you want to automatically create Excise invoice during Sales cycle at the time of billing the tickthe indicator 'Create EI'5. During depot sales if you do not want to do RG23D selection and posting separately and wouldlike to complete RG23D selection in one step mark the indicator 'RG23D Auto post'. This will postthe selected records into RG23D automatically. You cannot cancel the selection later.

6. If the indicator 'Default GR qty' is marked system will default the Excise challan quantity on tothe Goods receipt if the Excise invoice number is given in the pop-up.7. If the indicator 'Folio no create' is marked system will generate Folio numbers for RG23D duringreceipt of excise invoice into depot.8. 'Automatic posting' when ticked will post the Excise invoice other movements automaticallyalong with creation in single step.9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of material intoBlocked stock .10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material throughinter plant transfers.11. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt ofmaterial into consumption stock. Excise Group Governs which set of excise registers a businesstransaction will be included in.Following is the relation between excise group, plant and registration. - In define excise groups inCustomizing.Then, in transactions involving excise duty, for example, when you post a vendor's excise invoice,you specify which excise group you are using. This information tells the system which G/L accountsto post the excise to. At the end of the period, when you come to prepare your excise registers,you create different sets for each excise group.Indicates that the plant in question is a depot. - Depots are required to prepare register RG 23D,and follow different procedures for goods receipt and invoice generation.- GR Per Excise Invoice- Multiple GR for one excise invoice , Multiple credit- Multiple GR for one excise invoice , Single CreditCreate Excise Invoice Automatically - Instructs the system to automatically create a Sales andDistribution (SD) excise invoice immediately you create a commercial invoice or a pro formainvoice.The excise invoice is created in the background. - If you want to make use of this function, youmust also define thedefault plant, excise group, and series groups in Customizing for Sales and Distribution (SD), bychoosing Excise Group - Series Group Determination.RG23D Sales Creation and posting option - RG23D Automatic Option if selected will create Depotexcise invoice by posting the selection of excise invoices in single step. If this is not selected thenyou need to separately do RG23D selectionfollowed by PGI and then RG23D verification and posting. If you need automatic posting of RG23Dselection then the Post Goods Issue should have been completed before running RG23D selection.

Default excise qty in GR - If this indicator is ticked then while doing Goods Receipt using 'MB01'system will default the excise invoice quantity on to the Goods receipt document.Folio number for depo Posting - If this indicator is marked then while creating Excise invoice forother movements system automatically does the Verify and Post. You need not separately Post theexcise invoiceAlso we can set indicator for creation of part 1 for:- Blocked stock- Stock transport order- Consignment stockMaintain Series Group - In this IMG activity, you define the different excise series groups withinyour company. Series groups allow you to maintain multiple number ranges for the outgoing excisedocuments. Based on excise regulations and exemptions from the authorities you can maintainmultiple number series for outgoing documents. But each of these series has to be declared to theexcise authorities.- Define excise series groups based on type of outgoing document- Assign series group to excise registration ID- If no financial postings are required for an Excise invoice in this seris group then you tick the 'Noutilization' indicator.- If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment thenmark the 'Immediate Utilization' Iindicator. Example - You could define two series groups, group001 for excise invoices, and group 002 for 57 F4 documents.- No account postings for CENVAT in sales cycle- No utilization FlagIf you do not need any CENVAT utilization for an excise invoice but would like to just generate anexcise invoice then you need to mark this indicator.If the flag is checked then system will create an Excise invoice in the given Series group but therewill not be any account postings or Part2 postings.Immediate Utilization of CENVAT - Specifies that when you create an excise invoice, the systemimmediately pays the amount from CENVAT and creates the Part II entry. Such invoices will not belisted for fortnightly utilization.If you have both fortnightly and immediate utilization for the same excise group, the accountdetermination within CIN IMG should point to the ED interim account.Account determination for immediate payment will be done exactly the same as being done forfortnightly utilization program.Maintain Excise Duty Indicators - In this IMG activity, you maintain the excise duty indicators.IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of

Excise Duty > Select Tax Calculation ProcedureIn this IMG activity, you specify which tax procedure you want to use for determining excise dutiesand sales taxes on input materials in India.- If you use condition-based excise determination, use a copy of the tax procedure TAXINN.- If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.This tax procedure also supports condition-based excise determination, so that you can work withboth concurrently.We strongly recommend that new customers use condition-based excise determination. Note thatonce you have started using a tax procedure, you cannot switch to another one, otherwise you willnot be able to display old documents.Maintain Excise Defaults - In this IMG activity, you define which tax procedure and pricing conditiontypes are used in calculating excise taxes using formula-based excise determination.If you use condition-based excise determination, fill out the CVD cond. field and leave all the othersblank.If you use formula-based excise determination, fill out all of the fields as follows:- Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.- Specify the purchasing and sales conditions types used for basic excise duty, additional exciseduty, special excise duty, and cess.- Specify the conditions in the sales order that are used for excise rates.- Specify the countervailing duty condition type used for import purchase ordersSee also : SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> MaterialsManagement (MM) -> Condition-Based Excise Determination and -> Formula-Based ExciseDetermination.IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination ofExcise Duty >Condition-Based Excise DeterminationWhen you enter a purchasing document, for example, a purchase order, the R/3 Systemautomatically calculates the applicable excise duties using the condition technique.Features : The standard system comes with two tax calculation procedures. TAXINN is only supportscondition-based excise determination, whereas TAXINJ supports condition-based excisedetermination and formula-based excise determination. Both tax procedures contain conditiontypes that cover all of the excise duties and sales taxes applicable.Since the exact rates of excise duty can vary on a large number of factors, such as which vendoryou purchase a material from, or which chapter ID the vendor stocks the material under, youcreate condition records for every sort of excise duty.When you come to enter a purchasing document, the system applies the excise duty at the ratesyou have entered in the condition records.Customizing : Make the settings in Customizing Basic -> India -> for Logistics – General, by

choosing Taxes on Goods Movements Account -> Excise Duties Using Condition Technique and …->Settings Determination.These activities include one activity where you define a tax code for condition-based excisedetermination.Master Data - Create condition records for all excise duties that apply, and enter the tax code forcondition-based excise determination in each.Day-to-Day Activities - When you enter a purchase order or other purchasing document, enter thetax code for condition-based excise determination in each line item. The system then calculatesthe excise duties using the condition records you have created.When the ordered materials arrive, you post the goods receipt and the excise invoice. The systemposts the excise duty to the appropriate accounts for deductible input taxes when you enter theexcise invoice.Creating Condition Records for Excise Duty1. In the command field, enter FV11 and choose .2. Enter the condition type that you want to create a condition record for and choose .The Key Combination dialog box appears.3. Select the combination of objects that you want to create the condition record for. On thedialog box, Control Code means "chapter ID." So, for example, to create a condition record for a taxthat applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code.4. Choose .5. Enter data as required. - In the Tax Code field, enter the dummy tax code that you havedefined.6. Save the condition record.Formula-Based Excise Determination - When you execute a business transaction involvingmaterials that are subject to excise duty, the system automatically calculates the duty for you.In order for the system to be able to determine which rate of excise duty to apply, you must havemaintained all the data on the Excise Rate Maintenance screen, which you can MasterData®access from the SAP Easy Access screen by choosing Indirect Taxes Excise RateMaintenance.You maintain the following types of data:- Plant master dataYou assign each of your plants an excise duty indicator. You can use the same indicator for all theplants with the same excise status from a legal point of view, such as all those that are in anexempt zone. See also the information about manufacturers that are only entitled to deduct acertain portion of the duty (see Partial CENVAT Credit).- Vendor master dataFor each of your vendors with the same excise status from a legal perspective, you define anexcise duty indicator. You must also specify the vendor type – for example, whether the vendor is amanufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a

small-scale industry. For each permutation of plant indicator and vendor indicator, you then createa final excise duty indicator.- Customer master dataSimilarly, you assign the same excise duty indicator to each of your customers that share the samelegal excise status.Again, for each permutation of plant indicator and customer indicator, you then create a finalexcise duty indicator.- Material master dataEach material is assigned a chapter ID.- Excise tax rateFor every chapter ID and final excise duty indicator, you maintain the rate of excise duty.If your business only qualifies for partial CENVAT credit, you must customize your systemaccordingly.Let us consider an example to illustrate how the system determines which rate of excise duty toapply to a material. Assume you are posting a sale of ball bearings to a customer. The systemautomatically determines the rate of excise duty as follows:1. Looks up the customer master data to see what status you have assigned the customer.Let's assume you've assigned the customer status 3.2. Looks up the plant master data to see what status you have assigned the plant. Similarly, yourplant has status 2.3. The system looks up the table under Excise Indicator for Plant and Customer to see what thefinal excise duty indicator is for customer status 3 and plant status 2: It is 7.4. The system determines the chapter ID of the ball bearing for the plant.Let’s assume the chapter ID at plant for the ball bearings is 1000.01.5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies tochapter ID 1000.01 understatus 7.Define Tax Code for Purchasing Documents - In this IMG activity, you define a tax code for thepurposes of calculating excise duty when you enter purchasing documents. Only carry out thisactivity if you use condition-based excisedetermination.- Create a new tax code, and set the tax code type to V (input tax). Do not make any other settingsfor it.- Assign Tax Code to Company CodesIn this IMG activity, assign the tax code for purchasing documents to the company codes where itwill be used.Only carry out this activity if you use condition-based excise determination.Classify Condition Types - In this IMG activity, you specify which condition types you use for whichsort of tax. Note that this only applies to condition types that you use with the new excisedetermination method. The system uses this information when you create a document fromanother one. For example, when you enter an incoming excise invoice from a

purchase order, or when you create an outgoing excise invoice from a sales order, the systemdetermines the various excise duties in the excise invoice using the information that you haveentered here. In addition, when you create a purchasing document, the system only uses thecondition types that you enter here.- For taxes on purchases, use the condition types contained in the tax procedure.- For taxes on sales, use the condition types contained in the pricing procedures.The standard system comes with sample settings for the tax calculation procedures and pricingprocedures.Use these settings as a basis for your own.IMG > Logistics - General > Tax On Goods Movement > India > Account DeterminationDefine G/L Accounts for Taxes - In this IMG activity, you specify which G/L accounts you will use torecord which taxes.Requirements - You have set up G/L accounts for each of the processing keys listed below.- Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 areused as clearing accounts during excise invoice verification.- VS1 (basic excise duty)- VS2 (additional excise duty)- VS3 (special excise duty)- VS5 (sales tax setoff)- MWS (central sales tax)- MW3 (local sales tax)- ESA (service tax)- ESE (service tax expense)Specify Excise Accounts per Excise Transaction - In this IMG activity, you specify which exciseaccounts (for exciseduty and CENVAT) are to be posted to for the various transaction types. Enter all the accountsthat are affected by each transaction type. If you use sub transaction types, enter the accounts foreach sub transaction type as well.Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if thepayment of excise duty has to be done fortnightly. The fortnightly CENVAT payment utility picks upthe credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining theCENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.Example:- Excise TT DC ind Account name- GRPO CR CENVAT clearing account- GRPO CR RG 23 BED account- GRPO DR CENVAT on hld accountSpecify G/L Accounts per Excise Transaction - In this IMG activity, you assign the excise andCENVAT accounts to G/Laccounts. When you come to execute the various transactions, the system determines which G/Laccounts to post to by looking at the:

- Excise group- Company code- Chart of accountsFurthermore, if you want separate account determination settings within an excise group, you canalso use sub transaction types.RequirementsYou have already:- Defined the G/L accounts- Defined the excise groups- Maintained the transaction accountsActivities - For each excise group, assign the excise and CENVAT accounts to G/L accounts. Formost businesses, one set of accounts will suffice for all transactions.Note : you need not remit the CENVAT to the excise department immediately, so maintain thecredit account for transaction type DLFC as an excise duty interim account. This will be set offwhen you remit the duty. Config setting needed to be done in order to get the Excise DetailsScreen in Material Master.Even though this functionality is available in enterprise version, a small configuration step has tobe made in Screen Sequences for Material Master.Following document helps you to do this configuration.- Material Master à Logistics General1. Go to IMG Define Structure of Data Screen for each Configuring the Material master ScreenSequence.2. Select your screen sequence. Usually it would be 21. Select the same and click on Data Screenin the left frame.3. Once the data screens are exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is“Foreign Trade: Import Data”. Select the same and click on Sub screens in the left frame.4. Go to the last sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab viewsub screen and ensure that the sub screen is blank.5. Now in the last sub screen i.e. no.6 you delete SAPLMGD1 – 0001 and instead addSAPLJ1I_MATERIAL_MASTER and in the screen no. 2205.6. Save the setting.7. Create a Material Master and check whether in Screen Foreign Trade– Import, Excise related sub screen appears.CustomerCustomizing Customer Hierarchy in SDHow to configure and maintain the SD Customer Hierarchy?All the customizing is in SD/Master Data/Bussiness Partner/Customers/Customers hierarchy1) Define hierarchy type: just put and ID and a name to the new hierarchy.2) Set partner determination: if you want to user the hierarchy in price determination, then, in theorders, at the header level, you have to have a Partner Procedure with a partner function for eachlevel. In the partner procedure, in each partner function you must indicate the source partnerfunction. With this informacition, in the order, you obtain the bussiness partner for each partnerfunction.

3) Assign acount groups: you indicate which accounts groups are allowed for being part or yourhierarchy.4) Assign sales areas: symple you indicate wich sales areas are allowed in your hierarchy. (Hereyou can customize common sales areas, just for not having to build de hierarchy in all the differentsales areas).5) Assigning hierarchy type for pricing: you indicate which classes of documentos uses hierarchy inpricing determination.It is possible to maintain so called customer hierarchies. This might be useful when for exampleyou create a condition discount for a customer that is part of such a hierarchy structure. Allsubnodes in the hierarchy below that customer, will thus receive the same discount.Customer hierarchy setup, firstly decide the hierarchy type to be used.The standard is type A.You can also assign a partner function to the customer so that the higher level customer in thehierarchy is copied into a sales order as a partner function - but you don't need that right?Next assign your customer account group to the hierarchy type. And enter the combinations thatwill be allowed for creating the hierarchy.You want to assign a ship-to to a payer. So enter the ship to account group and enter the payeraccount group as the higher level.You must also make an entry for permitted sales area assignments. So if you want to a hierarchyfor customers in the same sales area then enter the sales area and enter the same one as thehigher level sales area.All these settings can be found in the IMG. Under SD - master data - business partners - customers- customer hierarchyYou use for example customer hierarchy when you have an company like Unilever and you agreeboth on a discount. Unilever does have different locations / businesses and you have to maintainthe discount for all customers. If you use a customer hierarchy you can maintain the discount forthe partner in the top of the hierarchy and in this way it will be valid for all customers in thehierarchy.Availability CheckAvailability Check on QuotationSAP standard does not do an availability check on the quotation, as it is not a definiteorder, usually just a pricing quote.When it is converted to an order, the first availability check is carried out, as well as credit checks.The system will check stock in the plant, plus what is contained in the availability checking rule(scope of check) eg: can add POs for replenishment, purchase reqs, different planned orders, andsubtract sales orders, deliveries etc already created against that material in that plant (andpossibly Storage location).If there is enough stock in the plant/SLoc, the system will give you a confirmed date, or give you adate based on the production time or purchasing time from the material master. The date thesystem proposes is based on the customer's requested delivery date.

SAP first backward schedules looking at the required delivery date, less transportation time, lesstransportation lead time, less pick and pack time, less production/purchase time if applicable. Ifthe date it calculates is equal or later than today’s date, then it will confirm the customer’srequired date. If it falls in the past, SAP will then forward schedule for today’s date, plus the timeslisted above to get the date when the customer can actually have it.ATP is the single most complex part of the SD module, depending upon how PP and MRP is set up.MRP works semi-separately, depending on how it is set up. Basically, MRP looks at the demand onthe plant, and if it the stock does not meet expected sales orders and deliveries, it will create apurchase requisition (outside purchase) or requirement or planned order (for production) to coverthe shortfall. When MRP is started, it will turn the PR into a PO or the requirement into a productionorder.SD material Determination based on availabilitycheckFor SD material Determination you can create a Substitution reason and on theStrategy field, the following info. is available:Product selection in the background is performed on the basis of the availability check.We want to have the material determination only in case on material shortage. Weexpect the Substitution reason to give us this functionallity. It does not hovever takethe availabilty into account before substitution.We thought the worse case is to create a ABAP which is linked to the "requirement"field in the Procedure (OV13).Has anyone had the same requirement? Is this a bug or just incorrectly documented?I also encountered this abnormally recently using material determination. In order to combat theproblem, the first product substitution should be for the original material. I've illustrated this below:Original Product: ABCSubstitutes: DEF, XYZIn order to perform product substitution ONLY in the case of ATP failure for product ABC, structurethe Material Determination record as follows:Material Entered: ABC Substitutes: ABCDEFXYZThere seems to be a devaition at availability check and or on a conceptual note still.Availability check can be configured both at requiremnt class and at the schedule line categorieslevel.Whilst the availabilty check at the requirement class level via global and mandatory configurationthe schedule line catgry availability check deals with the order.It is mandatory that the reqmnt class is flagged off for avlblty check and the schdelu line cat neednot be.The following are the mandatory for Availability check to happen--

1. Must be swithced on at the requirment class level and at the schedule line level.2. Reqmnt type must exist by which a requiremnt class can be found3. There must exist a plant and is defined4.Checking group must be defined in Material Master records(it controls whthr the system is tocreate individual or collective reqmnt)A combination of checking gropup and checking rule will determine the scope of availbaility check.Creating Multiple Materials in MaterialDeterminationMaterial Determination is used to swap one material for another.It is possible to get a list ofmaterials for substituiton,but remember you can substitue only one material from the list.This can be done through substituiton reason T Code [OVRQ]See the substitution reason number for Manual Material Selection- check the Entry box- check the Warning box- select A for Stategy- save.Go To VB11 to create Material Determination (taking into consideration that all the previous stepsfor material determiantion i.e. maintaining condition types,maintaining procedures for materialdetermination and assigning procedures to sales doc. types have been done)Create one material determination,dont forget to give the Subst reason on top and also on the line.Click the Variants Icon on top left-Sreen opensSpecify different materials you want to swap with the material you have enterdNote that the subst reason is already copied on the screenRemember materials should be of the same sales area,atleast Divisions should be same.Backward and Forward SchedulingBackward scheduling is the calculation of deadline dates: the arrival time at the customer site iscalculated as the earliest possible goods receipt time at the customers unloading point on therequested delivery date. All four of the delivery and transportation scheduling lead times aresubtracted from the customer's requested delivery date to determine if this date can be met.The transit time, loading time, and pick/pack time are subtracted from the customer’s requesteddelivery date to calculate the required material availability date.The system calculates backward scheduling as follows:Requested delivery date minus transit time = Goods issue dateGoods issue date minus loading time = Loading dateLoading date minus transportation lead time = Transportation scheduling dateLoading date minus pick/pack time = Material availability dateBy default, the system will calculate delivery dates the closest day, taking into consideration theworking days of the shipping point and a rounding profile. In this case the system assumes a 24hour work day and lead times can be entered in days up to 2 decimal points. This is referred to asdaily scheduling.Precise scheduling calculated down to the day, hour and minute is supported. This allows thescheduling of a delivery within a single day. It is activated by maintaining the working hours for a

particular shipping point.Backward scheduling is always carried out first. If the material availability date or transportationscheduling date is calculated to be in the past, the system must then use forward scheduling.Forward scheduling is also done if no product is available on the material availability datecalculated by backward scheduling. The system does an availability check to determine the firstpossible date when product will be available. This new material availability date forms the startingpoint for scheduling the remaining activities. The loading time, pick/pack time, transit time, andtransportation lead time are added to the new material availability date to calculate the confirmeddelivery date.Account PayableSettlement Downpayment with Installmentpayment TermScenario :- Problem with Down payment settlement using installment payment term.1. When we create Sales order, (sales item value = 100) use payment term :0009 (Installment Payment term, 30%, 40%, 30%). In the Billing Plan, I specify 2 records, 1strecord isDownpayment request 30% of Order value, billing type is FAZ . the 2nd record is Final invoice100%, billingtype is F2.2. Create Billing type Down payment request , it will document as Noted item in the accountingdocument.3. Receive Downpayment from customer via FI screen , at this stage the asccounting document iscreated as followingDr. Cash/Bank 30Cr. Advance from customer 304. When I create Billing document for the sales item, the down payment value will be proposed forsettlement at BillingCreation, I then accept the default value of down payment clearing. The accounting document isas belowDr. AR 30 (*split AR by installment payment term)AR 40AR 30Cr. Sales 100Dr. Advance from customer 30Cr. AR 9 (DP. 30% * 30)Cr AR 12 (DP. 30% * 40)Cr AR 9 (DP. 30% * 30)It seems SAP settlement Down payment by Installment Payment term. I was wondering that isthere are alternative or an option to setup the Down payment settlement independent ofInstallment term. I meant, I don't want to have the last 3 Credit item as above, I want only 1 lineitem of credit, the accounting should beDr. AR 30 (*split AR by installment payment term)AR 40AR 30

Cr. Sales 100Dr. Advance from customer 30Cr. AR 30 (Not separate by Installment payment term)Solutions : Suggesstions on how I could proceed?Your problem with Down payment settlement is common. Many users object to the down paymentor security lodgement mechanism. In our case we often park and apply the advance manually tofinal invoice.However, following the above case we sometimes use this with our PS orders:1. Create Sales order, (sales item value = 100) with billing plan with three steps 30% downpayment,30% std billiing onorder completion and 70% on delivery. A little different to your original Billing Plan, but 1strecord is Downpaymentrequest 30% of Order value, billing type is FAZ . the 2nd & 3rd records are std F2 invoices 30% ,70%.2. Create Billing type Down payment request , it will document as Noted item in the accountingdocument.3. Receive Downpayment from customer via FI screen , at this stage the accounting document iscreated as following :-Dr. Cash/Bank 30Cr. Security deposit payment 30 ( In many countries this may be subject to TAX laws)4. Create the First Billing documents , the down payment value will be proposed for settlement atBilling Creation, thenaccept the default value of down payment clearing as these equal each other. The accountingdocument is as belowDr. AR 30Cr. Sales 30Dr. Advance from customer 30Cr. AR 305. Create the Second Billing document ( down payment value has expired and will not be proposed)The accountingdocument is as below is then standard for the last installement.Dr. AR 60Cr. Sales 60This alternative provides a cleaner option with the Downpayment.Customized SD ABAP ReportsSales and Distribution - Upload ConditionPricingRV14BTCI - Batch Input for Uploading Condition PricingAfter executing the program, you have to use SM35 to process the update program.Envirionment : 4.6xRequire flat file :-ROW 1 BGR00ROW 2 BKOND1

ROW 3 BKOND2 - no scaleROW 4 BKOND2 - no scaleROW 5 BKOND3 - with scaleROW 6 BKOND2 - no scaleSample flat file for uploading table A305 - Customer/Material with release status :-0BIPRICE 123SAPABAP X1VK15 A305V PR002ALL 990000123456SAP8204142100 2002043020020401 50USD 100PC2ALL 990000123456SAP8217168100 2002043020020401 50USD 100PC3 100PC 23 200PC 12ALL 990000123456SAP8220133910There a total of 4 flat file format :-BGR00 - Session Header Record------------------------------------------------------------------------------------------| Field name | Description | Report header | Cat. | Length | Dec. |------------------------------------------------------------------------------------------| STYPE | Record type | 0 | CHAR | 000001 | 000000 || GROUP | Group name | BI Session Name | CHAR | 000012 | 000000 || MANDT | Client | Your client no | CLNT | 000003 | 000000 || USNAM | User ID | Queue user ID | CHAR | 000012 | 000000 || START | Lock until: | Queue start date | DATS | 000010 | 000000 || XKEEP | Keep indicator | X - don't delete SESS| CHAR | 000001 | 000000 || NODATA | No batch input | / | CHAR | 000001 | 000000 |------------------------------------------------------------------------------------------BKOND1 - Header Record------------------------------------------------------------------------------------------| Field name | Description | Report header | Cat. | Length | Dec. |------------------------------------------------------------------------------------------| STYPE | Record type | 1 | CHAR | 000001 | 000000 || TCODE | Transaction code | TCode = VK15 | CHAR | 000020 | 000000 || KVEWE | Usage | U | CHAR | 000001 | 000000 || KOTABNR | Table | Table e.g. 305 | CHAR | 000003 | 000000 || KAPPL | Application | App e.g V | CHAR | 000002 | 000000 || KSCHL | Condition type | CTyp e.g PR00 | CHAR | 000004 | 000000 |------------------------------------------------------------------------------------------BKOND2 - Main Data Record------------------------------------------------------------------------------------------| Field name | Description | Report header | Cat. | Length | Dec. |------------------------------------------------------------------------------------------| STYPE | Record type | 2 | CHAR | 000001 | 000000 || VAKEY | VarKey | VarKey | CHAR | 000100 | 000000 || DATBI | Valid to | Valid to | DATS | 000010 | 000000 || DATAB | Valid on | Valid on | DATS | 000010 | 000000 || KBETR | Amount | Amount | CHAR | 000015 | 000000 || KONWA | R/2 table | R2tab | CHAR | 000005 | 000000 |

| KPEIN | R/2 table | R2tab | CHAR | 000005 | 000000 || KMEIN | | | CHAR | 000003 | 000000 || MWSK1 | Tax code | Tx | CHAR | 000002 | 000000 || KONMS | Scale UoM | UoM | UNIT | 000003 | 000000 || MXWRT | Amount | Amount | CHAR | 000015 | 000000 || GKWRT | Amount | Amount | CHAR | 000015 | 000000 || STFKZ | Scale type | S | CHAR | 000001 | 000000 || KZNEP | Exclusion | CndEx | CHAR | 000001 | 000000 || LOEVM_KO | Deletion indic. | D | CHAR | 000001 | 000000 || SKONWA | R/2 table | R2tab | CHAR | 000005 | 000000 |------------------------------------------------------------------------------------------BKOND3 - Scale Data Record------------------------------------------------------------------------------------------| Field name | Description | Report header | Cat. | Length | Dec. |------------------------------------------------------------------------------------------| STYPE | Record type | 3 | CHAR | 000001 | 000000 || KSTBM | Quantity | Quantity | CHAR | 000018 | 000000 || KONMS | Scale UoM | UoM | UNIT | 000003 | 000000 || KBETR | Amount | Amount | CHAR | 000015 | 000000 |------------------------------------------------------------------------------------------Sales Order Changed History Display** Sales Order Changed History Display** You can execute the report by :* 1. Change Date* 2. User Name* 3. Sales Order Number** Submitted by : SAP Basis, ABAP Programming and Other IMG Stuff* http://www.sap-img.com*REPORT ZSDCHANGE LINE-SIZE 132 NO STANDARD PAGE HEADINGLINE-COUNT 065(001)MESSAGE-ID VR.TABLES: DD04T,CDHDR,CDPOS,DD03L,DD41V,T685T,VBPA,TPART,KONVC,VBUK.DATA: BEGIN OF ICDHDR OCCURS 50.

INCLUDE STRUCTURE CDHDR.DATA: END OF ICDHDR.SELECT-OPTIONS: XUDATE FOR ICDHDR-UDATE,XNAME FOR ICDHDR-USERNAME,XVBELN FOR VBUK-VBELN.SELECTION-SCREEN SKIP.SELECTION-SCREEN BEGIN OF BLOCK BLK1 WITH FRAME TITLE TEXT-001.PARAMETERS: SUDATE RADIOBUTTON GROUP R1,SNAME RADIOBUTTON GROUP R1,SOBID RADIOBUTTON GROUP R1.SELECTION-SCREEN END OF BLOCK BLK1.DATA: WFLAG,WCHANGENR LIKE CDHDR-CHANGENR,WUDATE LIKE CDHDR-UDATE,WNAME LIKE CDHDR-USERNAME,WVBELN LIKE VBUK-VBELN,WDEC1 TYPE P DECIMALS 3,WDEC2 TYPE P DECIMALS 3,WDEC3 TYPE P DECIMALS 3,WDEC4 TYPE P DECIMALS 3.DATA: UTEXT(16) VALUE 'has been changed',ITEXT(16) VALUE 'has been created',DTEXT(16) VALUE 'has been deleted'.DATA: BEGIN OF ICDSHW OCCURS 50.INCLUDE STRUCTURE CDSHW.DATA: END OF ICDSHW.DATA: BEGIN OF ITAB OCCURS 10.INCLUDE STRUCTURE CDSHW.DATA: UDATE LIKE CDHDR-UDATE,USERNAME LIKE CDHDR-USERNAME,CHANGENR LIKE CDHDR-CHANGENR,VBELN(10),POSNR(6),ETENR(4),INDTEXT(200),END OF ITAB.SELECT * FROM VBUK WHERE VBELN IN XVBELN.CLEAR CDHDR.CLEAR CDPOS.CDHDR-OBJECTCLAS = 'VERKBELEG'.CDHDR-OBJECTID = VBUK-VBELN.PERFORM READHEADER.PERFORM READPOS.LOOP AT ITAB.CASE ITAB-TABNAME.WHEN 'VBPA'.

IF ITAB-FNAME = 'KUNNR' ORITAB-FNAME = 'LIFNR' ORITAB-FNAME = 'PARNR' ORITAB-FNAME = 'PERNR' ORITAB-FNAME IS INITIAL.MOVE ITAB-TABKEY TO VBPA.SELECT SINGLE * FROM TPART WHERE SPRAS = SY-LANGUAND PARVW = VBPA-PARVW.IF SY-SUBRC = 0.REPLACE '&' WITH TPART-VTEXT INTO ITAB-INDTEXT.ENDIF.ENDIF.WHEN 'VBAP'.IF ITAB-FNAME IS INITIAL.REPLACE '&' WITH 'Item' INTO ITAB-INDTEXT.ENDIF.WHEN 'KONVC'.MOVE ITAB-TABKEY TO KONVC.SELECT SINGLE * FROM T685T WHERE SPRAS = SY-LANGUAND KVEWE = 'A'AND KAPPL = 'V'AND KSCHL = KONVC-KSCHL.IF SY-SUBRC = 0.REPLACE '&' WITH T685T-VTEXT INTO ITAB-INDTEXT.ENDIF.ENDCASE.IF ITAB-INDTEXT(1) EQ '&'.REPLACE '&' WITH ITAB-FTEXT(40) INTO ITAB-INDTEXT.ENDIF.IF ITAB-CHNGIND = 'I'.REPLACE '%' WITH ITEXT INTO ITAB-INDTEXT.ELSEIF ITAB-CHNGIND = 'U'.REPLACE '%' WITH UTEXT INTO ITAB-INDTEXT.ELSE.REPLACE '%' WITH DTEXT INTO ITAB-INDTEXT.ENDIF.CONDENSE ITAB-INDTEXT.MODIFY ITAB.ENDLOOP.ENDSELECT.IF SUDATE = 'X'.SORT ITAB BY UDATE VBELN POSNR ETENR.ELSEIF SOBID = 'X'.SORT ITAB BY VBELN POSNR ETENR UDATE.ELSE.SORT ITAB BY USERNAME VBELN POSNR ETENR UDATE.

ENDIF.LOOP AT ITAB.CLEAR WFLAG.IF SUDATE = 'X'.IF WUDATE NE ITAB-UDATE.SKIP.WRITE:/001 ITAB-UDATE,023 ITAB-USERNAME,037(10) ITAB-VBELN.WFLAG = 'X'.WUDATE = ITAB-UDATE.WCHANGENR = ITAB-CHANGENR.ENDIF.ELSEIF SOBID NE 'X'.IF WVBELN NE ITAB-VBELN.SKIP.WRITE:/001 ITAB-VBELN.WVBELN = ITAB-VBELN.ENDIF.ELSE.IF WNAME NE ITAB-USERNAME.SKIP.WRITE:/001 ITAB-USERNAME.WNAME = ITAB-USERNAME.ENDIF.ENDIF.IF WCHANGENR NE ITAB-CHANGENR.WRITE:/023 ITAB-USERNAME,037(10) ITAB-VBELN.WFLAG = 'X'.WCHANGENR = ITAB-CHANGENR.ENDIF.IF WFLAG = 'X'.WRITE: 013 ITAB-CHNGIND,049 ITAB-POSNR,057 ITAB-ETENR,065 ITAB-INDTEXT(60).ELSE.WRITE: /013 ITAB-CHNGIND,049 ITAB-POSNR,057 ITAB-ETENR,065 ITAB-INDTEXT(60).ENDIF.WRITE:/065 ITAB-F_OLD.WRITE:/065 ITAB-F_NEW.ENDLOOP.

FORM READHEADER.CALL FUNCTION 'CHANGEDOCUMENT_READ_HEADERS'EXPORTINGDATE_OF_CHANGE = CDHDR-UDATEOBJECTCLASS = CDHDR-OBJECTCLASOBJECTID = CDHDR-OBJECTIDTIME_OF_CHANGE = CDHDR-UTIMEUSERNAME = CDHDR-USERNAMETABLESI_CDHDR = ICDHDREXCEPTIONSNO_POSITION_FOUND = 1OTHERS = 2.CASE SY-SUBRC.WHEN '0000'.WHEN '0001'.MESSAGE S311.LEAVE.WHEN '0002'.MESSAGE S311.LEAVE.ENDCASE.ENDFORM.FORM READPOS.LOOP AT ICDHDR.CHECK ICDHDR-UDATEIN XUDATE.CHECK ICDHDR-USERNAMEIN XNAME.CALL FUNCTION 'CHANGEDOCUMENT_READ_POSITIONS'EXPORTINGCHANGENUMBER = ICDHDR-CHANGENRTABLEKEY = CDPOS-TABKEYTABLENAME = CDPOS-TABNAMEIMPORTINGHEADER = CDHDRTABLESEDITPOS = ICDSHWEXCEPTIONSNO_POSITION_FOUND = 1OTHERS = 2.CASE SY-SUBRC.WHEN '0000'.LOOP AT ICDSHW.CHECK ICDSHW-CHNGIND NE 'E'.CLEAR ITAB.

MOVE-CORRESPONDING ICDHDR TO ITAB.MOVE-CORRESPONDING ICDSHW TO ITAB.CASE ITAB-TABNAME.WHEN 'KONVC'.MOVE ICDHDR-OBJECTID TO ITAB-VBELN.MOVE ICDSHW-TABKEY(6) TO ITAB-POSNR.WHEN OTHERS.MOVE ICDSHW-TABKEY+3(10) TO ITAB-VBELN.MOVE ICDSHW-TABKEY+13(6) TO ITAB-POSNR.MOVE ICDSHW-TABKEY+19(4) TO ITAB-ETENR.ENDCASE.MOVE '& %' TO ITAB-INDTEXT.APPEND ITAB.CLEAR ITAB.ENDLOOP.WHEN OTHERS.MESSAGE S311.LEAVE.ENDCASE.ENDLOOP.ENDFORM.TOP-OF-PAGE.WRITE:/ SY-DATUM,SY-UZEIT,50 'SALES ORDER CHANGE HISTORY',120 'Page', SY-PAGNO.WRITE: / SY-REPID,60 'SALES ORDERS STATISTICS'.SKIP.ULINE.IF SUDATE = 'X'.WRITE:/001 'Change Date',013 'Time',023 'User Name',037 'Sale Order',049 'Line',057 'Sch No',065 'Changes'.ELSEIF SOBID = 'X'.WRITE:/001 'Sale Order',013 'Line',021 'Sch No',029 'Change Date',041 'Time',051 'User Name',065 'Comment'.ELSE.

WRITE:/001 'User Name',015 'Time',025 'Change Date',037 'Sale Order',049 'Line',057 'Sch No',065 'Changes'.ENDIF.ULINE.*--- End of ProgramHUMBasic Process of how Packing WorksLet's say you want to pack a material shirt_jai in test_pack.Using MM01, create material type=packaging test_pack[SPRO]IMG-Logistics Execution-Shipping-Packing-Define Packaging Material TypesLet's say JPAC. The settings that I chose:Plant determ. - Plant is entered manually in handling unitPack. matl. cat. - Packaging materialsGenerate Dlv. Items - blankNumber assignment - Number range interval 'HU_VEKP'IMG-Logistics Execution-Shipping-Packing-Define material group for packaging materialLet's say JGRPIMG-Logistics Execution-Shipping-Packing-Define allowed packaging materialsJGRP - JPACMM02: Check settings for the materialsFirst, test_packSales:General/Plant -> Matl. Grp. Pack. Matls: JGRP (Note)Sales:General/Plant -> Packaging Mat. Type: JPAC (Note)Basic Data 1 -> Material: JMATThen, shirt_jaiSales:General/Plant -> Matl. Grp. Pack. Matls: JGRPSales:General/Plant -> Packaging Mat. Type: -Basic Data 1 -> Material: JMATVL01N Outbound Delivery -> PackingEnter the materials at top and at bottom(Select shirt_jai andEdit - Pack)This is how the basic process of packing works.The "Packing Process" with an ExampleExample:You created a order for a material(R-1160 - hard disks) for a qty - 120 pieces.You need to create a delivery and

A)pack 40 pieces each of the material are grouped together into larger cardboard boxes (PK-100 -shipping/packing material) andB)these 3 cardboard boxes are put into pallet (PK-095).Solution:A)Packing 40 pieces each of material (40 x 3 = 120 pieces)1)Goto [VL02N] to change the delivery, you already created.Or you can do the following steps while you are creating a delivery also.2)Go to "pack" icon.3)In the upper section, enter the "packing material" (PK-100)4)In the lower section, change the "partial quantity" to 40 of material R-1160.5)Select both the lines of upper section and lower section and click the green ok. It generates ashipping unit/handling unit number.6)Now, select both lines of upper & lower section & click the button "per part. qty" (New HU perpart qty of material)Check: click "General Overview" icon to see whether it packed 40 pieces of material in 3 cartons.B)Packing all 3 cartons in one big carton(PK-095)1) from above screen, click "pack HUs" (pack shipping unit)2)enter the packaging material (PK-095) in the upper section and select this line.3)select 3 lines of PK-100 in lower section since you want to pack them in PK-095.4)selecting both lines, click "pack" icon.5)Now all the 3 cartons(PK-100 with 40 pieces each of material) are packed in one big carton (PK-095).Check: "General overview" icon.Then "save" the delivery.PricingDifference between Condition TypePlease explain the difference between Ek01 ( Actual Cost) and EK02 Calculated Cost.These are the condition type that will display the results of the unit costing for certain type ofsales document.EK01 :If you use this condition type, the result of unit costing is issued to the first position on theconditions screen for the item. The value can be used as a basis for price determination.EK02:If you use this condition type, the result of unit costing is simply a statistical value which you cancompare with the price.Please note the following points :1) The condition type must have condition category 'Q' (costing).2) The condition type must agree with the condition type defined for unit costing in the pricingprocedure.I have a customer who is being offered two discounts ie k007 and k005, now I want toexclude k007 for the next 2

orders or so? I have set the exclusion indicator for the condition type,but still thecondition is being accepted when I create a sales order. Am I missing something, howdo I do it?I think u need to change the validity of the condition record for the condition type K007 defining itnot valid for that particular 2 months. And also the settings of the Requirements as it is correctthat it overrules the exclusion.Accumulate the amount of condition types inaccounting documentTo accumulate the amount of condition types in accounting document without affecting the pricingdisplay in billing document.As an illustration :-ZPXX 3500ZDXX 1000-ZWXX 500-(all condition types are shown separately in pricing view)Journal:Dr Vendor 2000Cr Sales 2000 (ZPXX - ZDXX - ZWXX)One way to do it is :-Mark the condition types you want to group as statistical and remove the account assignment key.Create a subtotal in your pricing procedure that will add them together and put in the accountassignment key for it. This way the individual components will still display on your pricing screenbut FI will only get one posting.Hiding Price Condition Types on a SalesDocumentUp to now you, you still cannot exclude certain condition types and subtotal lines from beingprocessed or displayed in the condition screen by restricting the authorizations.You have to implement SAP Note No. 105621 - Authorization check for the condition screenCreating New Pricing ProcedureWhat is the transaction code for creating new pricing procedure and how to attach it tospecific plant?You create PP in spro > Sales and Distribution > Basic Functions > Pricing > Pricing Control >Define and Assign Pricing Procedures > Maintain Pricing ProceduresYou can't attach PP to specific plant. Pricing Procedure is determined thru trx OVKK. The definingparameters for pricing procedure determination are:1. SalesOrg2. Distribution Channel3. Division4. Document Procedure (defined in Sales doc\Billing doc maintenance)5. Pricing procedure assigned to customer (defined in customer master)Hope this helps.

SabirReg pricing procedure.1. Use transaction code v/07 to create a access sequence and assign tables based on which youwant to carry onpricing as accesses.2. Use transaction code v/06 to define condition type. It can be for base price, discount, freightetc.,(Do assign relevant access sequence)3. Use transaction code v/08 to define pricing procedure.4. Assign this to your relevant sales area+ dpp+cupp.While specifying requirement, we can give reqt no.22 which specifies that plant has to be set. Thisis generally done for output taxes since output taxes depend upon the delivering plant. Butdirectly there is no assignment between plant and pricing procedure.What is "alt cal type" & "alt base value" &"Requirement field" in the Pricing ProcedureCan any one explain exactly what is "alt cal type" & "alt base value" and also "Requirement field" in the pricing procedure?The alternate base value is used as the calculation basis only, while the alternate calculation isused to modify the final value.For example, imagine you have a condition type ZZ01, with a condition record maintained (masterdata) for $100. Now, condition ZZ02 also exists lower in the schema, but with a rate of 10%. Thestandard calculation would result in a final value of $110.The alternate base value could say, "don't use $100 as the basis -- use the original price PR00 only,which was $90." Then, the final value would be $100 + (10% of $90) = $109.The alternate calculation routine says, "ignore the 10% altogether. Instead, use an externallycalculated 20%." Then, you end up with a final value of $100 + (20% of $100) = $120.Put them both together, and you could end up with $100 + (20% of $90) = $118.Now once again,Alternative Calculation Type:Normally if you want to calculate a value you have to use a calculation type for determinating thevalue. This calculation type is either addition, subtraction or multiplication. Similarly SAP also hasgot a default calculation type in the control data of the condition type. There you have the optionsof either Qty based , Fixed Amount Based or Percentage based.Here what happens is suppose if you define Your condition type that calculates the base price of amaterial on Qty based. Then the calculation will be done based on the quantity of the material. Ifthe customer orders 10 Nos and you have maintained a unit price of 100 Rs for each material thenthe value determined is 1000 INR. Similarly if the discount condition type , you maintain the

calculation type as %. This means if you maintain the value of 10 % in the condition record. Thenthis percentage is taken as the calculation type and the condition value is determined.In some cases you have to forego the default calculation types and use the customer specificmethod for calculating a value. For ex if you are calculating the Freight charges for a Material . itdepends on so many criteria like, the weight, volume and also the minimum amount etc etc, inthose cases, you forego the default value and then use the alternative calculation type incalculating the condition value against the particular condition.Alternative Condition Base value :If you have to calculate any value then you have to have a base value for it. For ex if you want tocalculate the discount of 10 % for a material then you have to have a base value on which this10% is calculated. Normally you take the condition value of the base price of the material tocalculate the value.Now you don't want to take the base value and take other values as base value which are derivedon some formulae. So you create a routine which will do the mathematical operations in the routineand derive you a value which is now used as the base value for calculating the condition value for aparticular condition type.Requirement:A factor in the condition technique that restricts access to a condition table. The system onlyaccesses a condition table to determine the price if the requirement specified has been met.Example:The system uses an access sequence to determine the price of a material. One of the accesses inthe sequence contains the requirement "in foreign currency." The system only uses the tablebehind this access if the sales order for which the price must be calculated is in a foreign currencyRe-pricing in a QuotationHow can I, or am I able to find anything on a way of RE-Pricing be done in a QUOTATION?You can always 'Update" pricing manually in a quotation the same way you do in a sales order,either in create or change modes. Menu path Edit --> New Pricing or press the 'Update pricing'button on the item conditions tab.If you are asking how to reprice a quotation when it converts into a sales order, that can be donewith the copy controls of the Item Category. IMG: Sales & Dist --> Sales --> --> Maintain CopyControl for Sales Docs --> Sales Doc to Sales Doc (transaction vtaa). Just choose the combination ofdocuments and the respective item category. The field you need to be concerned with is "Pricingtype".However, from a business process perspective it makes absolutely NO sense to reprice a quotationwhen converting to a sales order. After all, the entire point of using quotations is to firm up detailslike pricing before creating the sales orderQuantity Based Discounts in Bulk QuantitiesSales

You're looking to implement quantity based discounts in 4.6c. You are trying to sellitems in specific bulk quantities, and only give the discount for specific quantityintervals.For example, if a customer orders 1 piece, 2 pieces, 3, etc. of part ABC, the price is$100.If the customer orders 10 pieces of part ABC, the price is $50.However, this is not only a standard minimum quantity discount. If the customer tries toorder 11 pieces, 12, 13, etc. it should return $100 again.The only values for which $50 should apply are 10, 20, 30, etc. - multiples of the bulkquantity 10.You have discussed changing your part number to reflect a bulk qty of 10, however youhave in house consumption that is allowed to consume only 1 part at a time. You wouldvastly prefer to keep one part number that you order from the supplier, consumeinternally and ship externally.You are fairly certain there is basic functionality that covers this, but you're just notsure where to start.Taking your requirements literally. Standard SAP scale pricing will not do it in that you only want thereduced price to come into effect when the order quantity is multiple of some bulk factor.It is agreed with that creating a separate material number is not a good idea.You can try this :-1. Define/Select a UOM for selling in bulk (i.e. cas, pallet, box whatever)2. Maintain UOM conversion between your base UOM and this new UOM3. Configure you bulk pricing condition type by usual means (it should be a base price rather thandiscount).4. Place this new bulk price behind your normal "PR00" price in the pricing procedure5. Create a new condition base value routine via VOFM where you check XKWERT to see if it is awhole number. If it is not then set XKWERT to zero.6. Assign this new routine to your bulk price condition in your pricing procedure in ALT conditionbase value column.7. Maintain bulk price conditon record in the Bulk UOMDetermine Sales Price with Shipping PointYou are trying to use shipping point as a key field (with sales org. distribution channeland ship-to party together) to determine the sales price. You created a condition tablewith the above key fields, and maintained the relevant setting (access sequence,condition type and pricing procedure).There is an error message in the sales order pricing analysis ("access not made" in theshipping point field).In the access sequence, you found that the shipping point field's document structure isKOMK.Can you put to item level field in the condition table and access sequence?Structure KOMK refers to header of the sales order, but shipping point of course is on item level.

You'll have to do some settings to reach your goal, it is possible.Step 1Append structure KOMP. Do this by changing through SE11 the table KOMPAZ.This is the include for structure KOMP.Add a component e.g. ZZVSTEL with component type VSTEL.Save, activate.If you want to make more points, assign search help H_TVST to the component.Ask a programmer if you don't understand this part.Step 2Change user exit MV45AFZZ. Say there that field ZVSTEL should be filled with information fromyour shipping point.Do this under part FORM USEREXIT_PRICING_PREPARE_TKOMP.The coding should be like tkomp-zzvstel = vbap-vstel.Save, generate.Step 3Make a new table as you did before, but first maintain your new field in Condition: allowed fields.When you create your new table you will see you have two shipping points.With the button technical view you can check which one ZZVSTEL or VSTEL.Step 4Finish with the steps you did before. That was ok.Now, you will see in your sales order that the shipping point is filled with informationPricing date based on delivery dateUsed transaction VOV8.This configuration is by order type.There is a field called proposal for pricing date.There you can select pricing date as requested delivery date.A - Proposed pricing date based on the requested dlv.date (Header)This control is set at the document level as oppose to the condition type level (PR00).That means your other condition types such as surcharges and discounts are also determined usingthe requested delivery date.If your requirement is for PR00 to alone to be priced at delivery date then this will not work.How pricing date is determine in the sales orderand billing document? Where is the setting?The pricing date is proposed based on the setting you make in the Sales document configuration.( T code : VOV8)You have a field" Prop.f.pricing date " in the Requested delivery date / pricing date / purchaseorder date segment.Then you can choose the follwoing options:Blank - Indicates the current date as the pricing dateA - Indicates the date based on the requested delivery dateB - Indicates the date based on the order validity start from dateAnd the pricing in the billing document is copied from thte sales order / Delivery document..It again depends on the setting u have in the copy control from order - billng or delivery - billing.

In the copy control, in the item settings you have two fields relavant for this.One is pricing source and the other is pricing type.The pricing sources are generally the order. But if you want you can change it to other valuesmentioned in the drop down,but this values have no effect if the pricing type is B.Any other value other than B in the pricing type will take the reference document price mentionedin the pricing source field.but for the pricing type B. The new price is determined in the billing order.Report to Check the Entered Pricing ConditionPriceWhich is the best transaction code to check the Pricing condition price entered in"VK11"?Other than "VK13", to display the price, you can use V/LD - Execute Pricing Report to check theprices entered into the Pricing Master.Normally Pricing Report - "07 Cust.-specific Prices with Scale Display" will do.Other Pricing Reports you can tried are these:---------------------------------------------------------------------------|LR|Report title |-- ------------------------------------------------------------------------|01|Comparison of Price Lists Without Scale Display ||02|Comparison of Price Groups Without Scale Display ||03|Incoterms with Scale Display ||04|Incoterms Without Scale Display ||05|Price List Types Without Scale Display ||06|Price List Types with Scale Display ||07|Cust.-specific Prices with Scale Display ||08|Cust.-specific Prices W/out Scale Display ||09|Material List/Material Pricing Group with Scale Display ||10|List Mat./Mat.Pricing Groups Without Scale Display ||11|Price Groups With Scale Display ||14|Taxes ||15|Material Price ||16|Individual Prices ||17|Discounts and Surcharges by Customer ||18|Discounts and Surcharges by Material ||19|Discounts and Surcharges by Price Group ||20|Discounts and Surcharges by Material Group ||21|Discounts and Surcharges by Customer/Material ||22|Discounts and Surcharges by Customer/Material Group ||23|Discounts and Surcharges by Price Group/Material ||24|Discounts and Surcharges by Price Group/Material Group ||25|VAT/ATX1 ||26|Canada/USA ||27|I.E.P.S Mexico ||28|Conditions by Customer |

|30|Conditions by Customer Hierarchy ||31|Price List with Release Status ||AC| ||AD| |---------------------------------------------------------------------------Mass Update of condition pricingYou can update the condition pricing for a range of sales order.For e.g. if you create sales order for 15 months or so, and at the beginning of each year, you haveto update the prices for lots of sales orders.Other than using VA02 and make an Update of the conditions at item level which is a big workbecause you will have lots of open sales order after so many months.Use VA05, select your Orders and on the result screen :-click Edit- > Mass Change -> New Pricing (menu).orif you don't want to do that Online, write your own abap report and use FunctionSD_BULK_CHANGE (check where-Used at SE37, Trace VA05 on how to fill the parameters,Function MPRF => New Pricing)Make Material Master Price of a material as salesprice automaticallyThe first method is not to set the pricing condition VPRS as statistical.Simply remove PR00 and it will work fine if you always use VPRS as your pricing base inside thepricing procedure.VPRS will reads both prices based on the price control in the material master.Price control S for standard price.Price control V for moving average price.It is this simple if you do not have any other "Prices" in the price procedure.However, if you are using one pricing procedure where for some items you price using VPRS andsome others using PR00, then you should use requirement routines to enable the correct pricecondition type at the right time.The second method involves more work as you need to write a formula (VOFM) to get thatinformation.This is how it goes :-1. Set VPRS to be the first step in the pricing procedure and to be subtotal B (as standard).2. Set PR00 with alt. calc. type formula, which sets the value of PR00 to be equal to the subtotalB.The routine (created with transaction VOFM) is:RV64A901FORM FRM_KONDI_WERT_600.XKWERT = KOMP-WAVWR.ENDFORM.The pricing procedure than looks like that:Step 1 VPRS statistical, subtotal B, reqt 4Step 2 PR00 Altcty 600Customer discounts on effort only

-----Original Message-----Subject: Customer discounts on effort onlyHi All,We have a requirement of giving a discount to customer based on the totalamount invoiced so far (across financial years).Where do we set this up? We have seen so far the discounts are calculatedbased on the value of the current invoice.The discount should be on a graduated scale basis for example0 - 100000 No discount100000 - 200000 5%200000 - and above 10%This means that discount would only start after the customer's net salevalue crosses 100000.For example, if the customer has been billed for 99000 and the currentinvoice is for 3000, a discount of 5% should be given on 2000 i.e. 100.Another complication is that, the discount is not based on the total amountbilled so far, but only on the effort billed and not on reimbursements (likeairfares, living expenses, visa charges, beeper charges etc). The discountapplies only to the effort and not to the reimbursements. In the aboveexample (invoice of 3000) say the effort billed is only 1500, the rest beingreimbursements. The discount is only on the 500. (the rest being taken up bythe lower limit for eligibility of 100000)For example the customer might have been billed say 150000 so far but actualeffort billed might be only 90000, the rest being reimbursements of actualcosts and hence the customer is not eligible for the discount.Kindly help,-----Reply Message-----Subject: RE: Customer discounts on effort onlyHi,The solution for this is Using rebate condition types and suitable conditionrecords.Of this to handle your first problem that is the rebate has to be appliedonly on the "effort" you have to set up a line in the pricing procedurewhich gives the rebate basis i.e the value to be used for rebate cond types.This I believe solves your problem of rebate only on effort.Your second problem i.e the discount should start getting appliedautomatically when it reaches the first scale for which the values span fewfinancial years. This I am not really sure whether it can be made possiblein the invoice itself. But a work around is not giving the discount directlyin the invoice but settling it against the rebate agreements by Credit notesperiodically.Hope it helps.Thanks-----Reply Message-----Subject: RE: Customer discounts on effort onlyHi

Arent we looking at rebate agreeement. That appears to be a straightawaysolution to your problem. You activate the sales organization and thepayer for thatRegards-----Reply Message-----Subject: RE: Customer discounts on effort onlyI am in SAP R/3 rel.30F.We have 2 options to meet your requirement.1. Using scale in condition type ( tcode V/06 ), choose scale basisG.Scale based on a formula ( be: your based amount is invoice ). Definescale formula. You need ABAPER to define it.2. Using routine in Alt.calc.type ( tcode V/08 , Maintain PricingProcedure ). Here, you also need ABAPER to create routine.hope this help-----End of Message-----Steps to Create Commission for AgentFor creating commission agent, you have to follow below steps.1) Establish Partner Functions for the Commissionee(s)Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->;BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONSTransaction Code: VOPA2) Assign the Partner Functions to Partner ProceduresMenu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->;BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONSTransaction Code: VOPA3) Create a Partner Procedure for the CommissioneesMenu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->;BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONSTransaction Code: VOPA4) Create New Customer Account Group(s) for Commission AgentsMenu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; LOGISTICS GENERAL ->;LOGISTICS BASIC DATA: BUSINESS PARTNERS ->; CUSTOMERS ->; CONTROL ->; DEFINE ACCOUNTGROUPS AND FIELD SELECTION FOR CUSTOMERTransaction Code: OVT05) Assign the Partner Functions to the Customer Account Group(s)Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->;

BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS ->; GOTO ->;PARTNER FUNCTIONS ->; ENVIRONMENT ->; ACCOUNT GROUP ASSIGNMENTTransaction Code: VOPA6) Assign the Partner Functions to the Partner Procedure for the Sales Document HeaderMenu Path: Tools ->; Business Engineer ->; Customizing ->; Sales and Distribution ->; BasicFunctions ->; Partner Determination ->; Define Partner FunctionsTransaction Code: VOPA7) Assign the Partner Functions to the Partner Procedure for the Sales Document Item (OPTIONAL)Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->;BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONSTransaction Code: VOPA8) Edit the Pricing Communication Structure (KOMKAZ) to Hold the New Functions (ClientIndependent)Menu Path: Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; DICTIONARYTransaction Code: SE119) Edit MV45AFZZ – userexit_pricing_prepare_tkomk (Client Independent)Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITORTransaction Code: SE3810) Edit RV60AFZZ - userexit_pricing_prepare_tkomk (Client Independent)Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITORTransaction Code: SE3811) Edit MV45AFZB - userexit_new_pricing_vbkd changing new_pricing (Client Independent)Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITORTransaction Code: SE38The following code should be inserted into program MV45AFZZ to allow the system to re-executepricing if the user makes a change to the relevant partner function (alteration, addition, deletion).13) Add the KOMKAZ Fields to the Pricing Field Catalog (Client Independent)Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->;BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->;MAINTAIN ACCESS SEQUENCESTransaction Code: OV2414) Create Condition Tables (Client Independent)Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->;BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->;MAINTAIN ACCESS SEQUENCESTransaction Code: V/03

15) Create an access sequence containing the new tables (Client Independent)Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->;BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->;MAINTAIN ACCESS SEQUENCESTransaction Code: V/0716) Create a new condition typeMenu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->;BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE CONDITION TYPES ->; MAINTAINCONDITION TYPESTransaction Code: V/0617) Add the Condition Type to the Pricing ProcedureMenu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->;BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE AND ASSIGN PRICINGPROCEDURES ->; MAINTAIN PRICING PROCEDURESTransaction Code: V/0811) Create Commsission Report ZZCOMMISSION (Client Independent)Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITORTransaction Code: SE38SD Questions About Pricing ConditionThe Most Important Tips in Pricing For SAP SD Module to crack interviews...Whenever we define our pricing procedures, we remain least interested in creating our ownCondition Types,ConditionTables & Access Sequences. What we do is, we just define our own pricing procedures by using theexisting condition types (i.e: PR00, K004, K007, KA02, KF00 etc.) & then assign that PricingProcedure with " Sales Area, Document Pricing Procedure & Customer Pricing Procedure " .After that we put the values against each Condition Types, mentioned in our Pricing Procedure byusing the T-Code "VK11". But we also need to know about the Condition Tables, Condition Types &Access Sequence Creation. So for that purpose we have to use the following T-Codes respectively :"V/05", "V/06" & "V/07". Now it will become easy to create the same.Also to inform that, using T-Codes is more smarter than following paths through IMG screen.Utsav Mukherjee - utsavmukherjee143@hotmail.What is the difference of VK11 and VK31 (condition records)?My condition type is PR00 and Access sequence is PR02. And in this access sequencetable 304 is available. Now when I was entering the PR00 in VK31 it shows error Table304 is not defining for the condition type PR02. But when I was entering the PR00 atVK11 it is accepting it.

Difference between VK11 and VK31 - if you go through the menu path you will get the vk 31 ascondition record from the tamplets whereas vk11 as simple condition record. In VK11 you canstore condition record for more than one conditiontype. This means you can have same condition record for different condition types.This feature isgiven to enhance the system's performane and not to create the duplcation of the work for eachcondition type.Again system is not allowing to store the record in the vk31 for the condition type pr00 and accesssequence pr02.This is because if you see this ac seq cointains two accessses 20 and 30 having thesame table no.But you see there is the difference between the technical view of it for transferingthe data from document field and condition field,so you can not maintain the data at VK31.What is the difference between Header condition and Item condition? I know itemcondition applies to each item in a sales document. Header condition can only beapplied to an entire document.Difference between header and item condition - as YOU CORRECTLY SAID HEADER CONDITION ISAPPLICABLE FOR THE WHOLE DOCUMENT where as item is for item.Ex-Say fright is dependent onthe total weight of all the items in the documents then header condition adds on weights of allitems and calculates the record accordingly.You have two different types of the header conditions.a) In one you can duplicate the same value throughout the document for each item.Say discount2% at header level which is also applicable to all the itemsb)Second is the accumulation of the values of all the item at the header level,as earlier explainedfor the weight/fright.These differenes are controlled through the indicator of group condition in the cond.typeconfiguration.And so obviously header condition can not have the condition record and hence access sequence.SAP SD Tips by : VishwajitDisallowing Condition Types - How I can accomplish the following:Be able to DISALLOW Z0BP Condition type to be negative ( Invoice Block)You can modify condition type from customising;Sales and Distribution->Basic Functions->Pricing->Pricing Control->Define Condition Types->Maintain Condition TypesChange condition type ZOBP's plus/minus indicator to "A" which means only positive is allowed.*-- Arvind RanaIn pricing procedure there are column such as requirement, sub total altclty, altbv,accurals. What are these and where we calculate all these values which we put.1. Requirement: Denoted by nos and maintained in VOFM, this is a condition required for aparticular condition type to be executed. Eg. PR00: req 2 ie item relevant for pricingVPRS/EKO1: req 4 ie costRebate BAO1 Req 24/Req 25 etc2. Subtotal: this represents where a which table a value is stored, which can be processed forfurther calculation.Eg. for PR00, if this value is to be used for credt check of a customer, we mark the subtotal as A.

3 Alternate Calculation type: this is also denoted by numbers and maintained in VOFM. Eg.Suppose for 45 units , each unit is charged $100 per unit, the order value comes out to be $4500,that is calculation is done as per unit price, if the client wants calculation type to be based onvolume or wieght, alternate calculation type can be configured.4. Alternate base value: Denoted by no. and maintained in VOFM.Eg, if the pricing scale is maintained and pricing for 45 units comes under the scale of $100 perunit., the base value is 45 units, but if the client wants a standard base value in some casesto beassumed inspite of maintaining the scale, an alternate base value is confihured, that is the basevalue based on which the order value is to be calculated changes.5. Accruals: Accruals are maintained for rebate agreements, it constitutes the total accumulatedvalue which customer has earned through rebate, one the rebate for certain amount is settled theamount from the accruals get deducted.Add a Field To New Condition Table in PricingAdd a field to a new condition table in Pricing (Condition Technique):-I will explain you the process with below example...Please follow steps in below sequence-Try to add the filed from the field catalog. In case the required combination field is not there, youcan add the field through the following process to filed catalog and create the condition table. It ismost common that one or other time we need to use this function while configuring multi tasking &complex Pricing Architecture.Here I'm giving a simple guide to add fields to the Pricing Field Catalogues:For example you want to use field PSTYV ('Sales document item category') that is included instructure KOMP ('Pricing Communication Item') as a key for a condition table.When you create a condition table (Transaction V/03), however, the system does not propose thefield in the field catalog.Condition access, field catalog, allowed fields, KOMG, KOMK, KOMP, KOMPAZ, KOMKAZ, PSTYV arethe other terms which we need to know about, to add Fields.Reason and Prerequisites:For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG('Allowed Fields for Condition Structures').Proceed as follows:1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose PSTYV asa domain.As a short text, you can use, for example, 'ZZ - sales document item category' and as afield label, you can use the field labels of PSTYV.Save, check and activate your entries.2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode andmake the following entry:Component Component type:ZZPSTYV ZZPSTYVSave, check and activate the change you made.3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures

KOMG and KOMP because structure KOMPAZ is included in both structures.4. Call up Transaction SPRO. Navigate to 'Sales and Distribution -> Basic Functions -> Pricing ->Pricing Control' and execute 'Define Condition Tables'.Choose 'Conditions: Allowed fields' and include ZZPSTYV as a new entry.5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.6. Supply the new field you defined by including the following source code line inUSEREXIT_PRICING_PREPARE_TKOMP:MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.In order processing you find the user exit in Include MV45AFZZ, and in billing document processingyou find it in Include RV60AFZZ.Consider that you can also use this note as a help if you want to use other customer-specific fieldsas key fields in a condition table.For header fields, use structure KOMKAZ instead of structure KOMPAZ andUSEREXIT_PRICING_PREPARE_TKOMK instead ofUSEREXIT_PRICING_PREPARE_TKOMP.For more information, see Transaction SPRO via the path 'Sales and Distribution -> SystemModifications -> Create New Fields (Using Condition Technique) -> New Fields for Pricing' and OSSNote 21040.Header Condition and Group ConditionWhat are header conditions?Header conditions are those which appear in the header level of any sales order. these conditionsare to be entered manually and get distributed automatically and the basis for distribution aretaken from the NET VALUE of items mentioned at item level.When we go to the conditions section in a sales order, where the details of pricing is mentioned,here we add these conditions.Whenever any Header Condition is used, it overrides the PR00 condition type.Examples of header condition.- HA00 - % Based Header Condition.- RB00 - Absolute or numeric value which applies to all items.- HB00 - Numeric value or Absolute value. *-- Vivek ChokshiWhat is the difference between group condition and header condition?Group Condition: You can use this is feature of a condition type to apply price or discount for amaterial based on common property.Header Condition: This is a manual condition which you apply to header (Condition screen) of asales document. This amount is applicable to all items.Usage of this feature is to apply price / discount for a specific group of materials.1. You maintained a discount based condition record fbased on material group ( = 01 for example).You maintained scales also.Qty Discount1 - 10 Rs. 100.0011 - 50 Rs. 105.00

51 - 150 Rs. 110.00 etc.2. You are creating a sales order for a customer with five different items with different quantities asbelowITEM 1 - 25 No'sITEM 2 - 3 No'sITEM 3 - 12 No'sITEM 4 - 27 No'sITEM 5 - 62 No'sAll the material is having the material group = 01.3. While calculating the discount, because of this group condition, system add the quantities ofitems which have material group = 01. In the above example total quantity is = 109. System applya discount of Rs. 110.00 to each item irrespective of the individual quantities.4. If you have not activated the group condition feature, system determines the discount valuebased on individual item quantity which is as below.DiscountITEM 1 - 25 No's Rs. 105.00ITEM 2 - 3 No's Rs. 100.00ITEM 3 - 12 No's Rs. 105.00ITEM 4 - 27 No's Rs. 105.00ITEM 5 - 62 No's Rs. 115.005. Is it clear now. Just try a sales order and see the out comeProcedure to Test:1. Create 3 materials. Maintain Material Group of each item is same.2. Activate the condition type as a group condition.3. Create a condition record for this condition type with scales.4. Process a sales order for a customer with these three material with different quantities.5. Check the outcome.Steps Involved In Condition TechniqueWhat are the 8 steps involved in condition technique?By: Rohit JoshiIt starts with an understanding of the factors that influences the Price. Lets say it depends onCustomer and Material. With this understanding now we will start with the Table where we will passthe above parameters. There is a table 5 which already has Customer and Material so we can nowcopy and rename it or use the same table in our Pricing Procedure.T Code VOK0Step 1. Define/Choose your Table (with the requirement parameters that influence the price)Step 2. Define your Access Sequence and include the above Table in your Access SequenceStep 3. Define your Condition Type (There are four Price Types Basic Price, Discount, Freight andTax) and include your Access Seq. Its always better to copy the Price Types provided by SAP.Step 4. Now comes your Pricing Procedure where you include include Condition Types and format.

Step 5. Now comes Procedure Determination where you specify the Document Pricing Procedureand Customer Pricing Procedure along with Sales Organisation, Distribution Channel.Step 6. Maintain Condition Records for your Condition TypesI guess you can make it 8 Steps by dividing some of the main steps. Few important things to note isfollowing..1. XD01 - Create Customer - Always ensure that you pick the right Customer Pricing Procedure fromhere.2. VA01 - Sales Order - Ensure that you have the right Document Pricing Procedure from here3. While Creating Access Sequence, check your Fields and ensure that they appear with anywarning (Highlighted in Red)4. Do not forget to mention your Access Sequence while defining your Condition Type5. Always remember that your Procedure Determination has only Basic Price as Condition Type6. Do not forget to mention the Range (From To) while creating your Pricing Procedure.BillingBilling cannot be Release to AccountingThis SAP message will appear if the system is unable to find the G/L codes match from theconfiguration in transaction VKOANo account is specified in item 0000001001Message no. F5 670DiagnosisNo account was specified for account type "S" in item "0000001001" of the FI/CO document.System ResponseThe Financial Accounting program cannot process the document.ProcedureA system error has probably occurred in the application you called up. Check the data transferredto item "0000001001" of the FI/CO document.Assuming that one of the key combination is Account Assignment Group, you will have to checkwhether have the Account Assignment Group been input in the Customer Master (Billing tabstrips -Accounting sections - Field name: Acct assgmt group).The Account Assignment Group will be copied automatically into the sales order.Check whether the configuration in transaction VKOA have been done correctly.Check whether the sales order (VA03 - Goto - Header - Financial Accounting - Field name:AcctAssgGr) have been filled in automatically.Check whether the billing document (VF03 - Goto - Header - Header - Field name: AcctAssgGr) havebeen filled in automatically.If the customer master have not been maintained and the user have already input the sales order,then the user will have to maintained the Account Assignment Group manually either in the salesorder or the billing documents.Take note for One Time Customer, the user have to input the Account Assignment Group manually

into the sales order. One Time Customer can be used by many customer, therefore, the system willnot be able to determine the Account Assignment Group manually.Default Start Variant for VF04There are two types of variant in VF04.One is the selection variant before clicking the Display Billing List Button.You can set the start variant via SE93 using the Change mode.The second variant is the Billing Layout display variant.This is after clicking the Display Billing List Button.After creating your layout display variant, you can set it by clicking :-Settings ->Display Variant-> AdministrationSelect the layout display variant you want and click :-Edit ->Define default settingsCondition Exclusion which will be determined inthe billing documentThe system can exclude conditions so that they are not taken into account duringpricing.For example:Material 4711 costs 150 USD. Some customers receive a discount of 10 USD per 100pieces.However, a specific customer can buy the material for 100 USD. Since this is aparticularly good price, the customer should not also have a discount of 10 USD per 100pieces. Therefore, this discount is to be excluded from pricing.To create a condition exclusion procedure which will be determined in the billing document.Assign the procedure to the pricing schema, and maintain copy control so that pricing is not copiedfrom Sales Order.To achieve this, copy the standard pricing to a ZXXXX Pricing.Define new document pricing procedure in SM30 - V_TVKV for billing.Assign new document pricing procedures to billing types in SM30 - V_TVFK_PRDefine the Condition Exclusion Groups in OV31.Assign the Condition type for the Condition Exclusion Groups in OV32.Assign the Billing Pricing Procedure in VOK8 for the Condition Exclusion Groups.When billing document is being created just enter manually your new price and the pricingprogram logic will include only the higher price one, excluding the rest that are lower price.Steps for creating a new or changing an existingBilling Document TypesCreate/Change your Billing types configuration in VOFA.Some of the IMG stuff are :-1) To block automatic transfer of the billing document to accounting, mark the field.Indicates whether the system blocks automatic transfer of the billing document toaccounting.During document processing, you can manually transfer blocked billing documents to

accounting by selecting:Billing -> Change -> Release accounting2) Account determination procedure3) Output determination procedure etc. ...After customizing, use transaction VCHECKVOFA to check your configuration :-1) Proforma billing types: If it is a proforma billing type, (VBTYP = U), the field mustbe blank and the account determination procedure must be empty.2) Cancellation billing document types: : A check is made to see if the cancellationbilling document type has the right VBTYP. An F2 invoice, for example, (VBTYP 'M')can only be canceled with billing type S1 with VBTYP 'N' . A billing type withVBTYP '5' can only be canceled with the VBTYP '6' and vice versa.3) Cancellation billing document type partner functions A check is made to see if thecancellation billing document type partner functions are empty or if those thatcorrespond to the billing type used are empty.Next, make sure that you maintain the copy control for the Billing Types:Sales documents in VTFATarget Sourcee.g. F1 - Invoice OR - Standard Sales OrderF1 - Invoice ZOR - Your Sales OrderBilling documents in VTFFe.g. G2 - Debit Memo F1 - InvoiceG2 - Debit Memo F2 - InvoiceDeliveries in VTFLe.g. F1 - Invoice LF - DeliveryF1 - Invoice ZOR - Your DeliveryUsually for copy control, you let the rest of the settings remains as SAP defaults.You only assign the new Billing Document Types.After that use transaction VCHECKTVCPF to check your Copy control customizing.Billing Block will not worked if you did not assignitDefine the possible block indicators in SM30 - V_TVFSandallocate them to the billing types concerned in SM30 - V_TVFSP.Your Billing Block will not worked if you did not assigned it to the desired billing types.You can auto block by :-1. sales document type in transaction VOV8, fields Billing Block,or2. item categories in SM30 - V_TVAP, by filling the fields Billing Block.Billing Plan for Milestone BillingMilestone billing means distributing the total amount to be billed over multiple billingdates in the billing plan.As each milestone is successfully reached, the customer is billed either a percentage ofthe entire project cost or simply a pre-defined amount.During sales order processing, the system determines from the item category whether abilling plan is required and, if so, which type of planThe type of billing plan that is determined at this point is set up in Customizing and

cannot be changed in the sales document.Billing plans for periodic billing and milestone billing plans for project-related milestonebilling have different overview screens so that you can enter data relevant to yourprocessing.For example, for milestone billing, you must be able to enter data to identify theindividual milestones.IMG configuration requires :-1. Maintain billing plan types for milestone billing in OVBO.2. Define date description in SM30 - V_TVTB.3. Maintain Date Category for Billing Plan Type IN OVBJ.4. Allocate date category in SM30 - V_TFPLA_TY.5. Maintain date proposal for Billing Plan Type in OVBM.6. Assign Billing Plan Type to Sales Documents Type in OVBP.7. Assign Billing Plan Type to Item Categories in OVBR.8. Define rules for determining the date in OVBS.Milestone billing is typically used for billing projects, such as plant engineering andconstruction projects. Such projects often include a series of milestones that mark thecompletion of different stages of the work. In the SAP R/3 System, milestones are definedin a network along with planned and actual dates for the completion of work. The milestonesare also assigned to the billing dates in the billing plan.Each milestone-related billing date is blocked for processing until the Project Systemconfirms that the milestone is completed.Delivery-relevant order items for which a milestone billing plan applies are billed on thebasis of the requested delivery quantity and not on the total of the confirmed quantities.The connection between the project and the sales document item is made in the individualschedule lines of the item. Each schedule item can be assigned to a network in a project.To display the project-related data for a schedule line, proceed as follows:In one of the overview screens of the sales document, select1. Item -> Schedule lines.2. Mark the schedule line and select Procurement details.The following figure shows an example of milestone billing where only the Contract havebeen billed :Order Item Turbine 100,000Billing PlanBilling date Description % Value Billing Block Milestone Billing Status01-10-94 Contract 10 10,000 - x x01-03-95 Assembly 30 30,000 x x01-04-95 Maintenance 30 30,000 x x01-05-95 Acceptance 30 30,000 x x01-06-95 Final invoice .. .. xNetwork/ActivitiesMilestone Estimate ActualAssembly 01-03-95 01-03-95Maintenance 01-04-95Acceptance 01-05-95For each billing date in a milestone billing plan, you can specify whether the billing

date is:1. fixed2. always updated with the actual date of the milestone3. updated with the actual date of the milestone, if the date is earlier than theplanned billing date for the dateSAP Billing - Combine Billing for deliveries withdifferent dateWhen using transaction VF04 or Billing (background), the date of the billing document (e.g. thecurrent date) must be entered (In VF04 : settings, default data.)In VF06 or background: variant with parametrization) to avoid an unwanted split due to the billingdate.This OSS notes is very helpful :-11162 - Invoice split criteria in billing document36832 - Invoice split in fields from the sales orderBilling Spilt by Item CategoryIs it possible to split invoice Item category wise. I mean If in sales order there is TANand TANN then the invoice should split,is it possible?NainaYes, it is possible. Create a modification of copy control routine for billing and use VBAP-PSTYV asan additional split criteria there.Martishev SabirThank you for your reply. Can you please tell me the exact steps what should I addunder that(additional split criteria).NainaIn trx VTFA (if your billing is sales order based) choose your billing type and SO type, there selectyour item categories and there select the field VBRK/VBRP data. In that field you will see thecurrently used routine. With the help of your ABAP guy create a copy of that routine under adifferent number and add your lines of code. Let's say you use routine 001.FORM DATEN_KOPIEREN_001.* Header data* VBRK-xxxxx = ............* Item data* VBRP-xxxxx = ............* Additional split criteriaDATA: BEGIN OF ZUK,MODUL(3) VALUE '001',VTWEG LIKE VBAK-VTWEG,SPART LIKE VBAK-SPART,END OF ZUK.ZUK-SPART = VBAK-SPART.ZUK-VTWEG = VBAK-VTWEG.VBRK-ZUKRI = ZUK.ENDFORM.

This is how it should look after modification:* Header data* VBRK-xxxxx = ............* Item data* VBRP-xxxxx = ............* Additional split criteriaDATA: BEGIN OF ZUK,MODUL(3) VALUE '001',VTWEG LIKE VBAK-VTWEG,SPART LIKE VBAK-SPART,PSTYV LIKE VBAP-PSTYV, <- New lineEND OF ZUK.ZUK-SPART = VBAK-SPART.ZUK-VTWEG = VBAK-VTWEG.ZUK-PSTYV = VBAP-PSTYV. <- New lineVBRK-ZUKRI = ZUK.ENDFORM.After this routine is created and activated place it as the default copy control routine instead of theold ones.Maximum number of items in FI reached Messageno. F5 727If you hit the above erros when you create an invoice in SD, the corresponding accountingdocument is not created.The error is as follows:Maximum number of items in FI reached Message no. F5 727DiagnosisThe maximum number of items for an FI document ('999') has been exceeded.System responseFI documents have a 3-digit item counter that limits the number of items permitted per document.ProcedureIf the documents with an excessive number of items come from another application area(e.g. sales, logistics, order accounting), you can configure the system to the effect thatthese documents are summarized in FI. "How could this error be solved as none of your invoices are getting accounted in FI?To overcome this, the only way was to break the accounting invoices, 1 with 950 items and theother with the rest.Prepaid process possible-----Original Message-----Subject: Prepaid process possibleI am looking for information on how we could implement a prepaid process. By "prepaidprocess" I mean:- Customer sends to us his order- If customer is set as "prepaid", we produce an invoice for him to pay- Once we have received his payment, we release the sales order for delivery

- no further billing document is produced.I found information in online documentation about "down payments" (I imagine that ourprepaid process could be a 100% required down payment) but it does not seem that itwould work. From what I understood it looks like the billing plan is handled based upon theitem category, which implies the processing is "material" specific not "customer" specific.What we do now:- We have defined a risk category "prepaid" which is assigned to our prepaid customer.This risk category automatically block the sales order for delivery.- We receive the sales orders and produce a Pro Forma invoice from it, and send it tocustomer- Once we receive the payment, we release the sales order for delivery and produce theinvoices.- We post the payment we received earlier against this last invoice.As you see, this requires a lot of manual work and a lot of time is wasted to match alldocuments together. There most be a more efficient way to handle this, anybody have anyhints?-----Reply Message-----Subject: RE: Prepaid process possibleHi again!You are right! However, if you create a new item category for the prepaid scenario, you canselect what item category (and process) to use at order entry. It is also possible to code auser exit so that only certain customers will get the prepaid process. This can be done alsowith item category groups (can be used to determine what default item category thatshould appear). This would mean that you either have different materialnumbers for thedifferent processes or use different distribution channels in the sales order. DC 10 could bethe normal process and DC 20 the prepaid process. Then you need to create the salesviews in material master for DC 20 for all materials that should be possible to run in theprepaid scenario, and enter the "prepaid item category group in the sales item categorygroup field in material master.Here is a proposal of customizing activities to achieve this:1. Create a new item category as a copy of the normal item category used for non-prepaidsales. (Change the billing in the item category to order related billing with no billing plan)2. Create a new item category group "ZXXX" or something of your choice with thedescription "Prepaid" or something like that.3. In item category assignment, add or check entries so that you have the order type used,and item category group defaulting the new item category.4. Check copy control from sales document to billing document for the new item category.Also delivery copy control could be good to check.5. Create a new distribution channel and assign it to the company structure (plant, salesorg etc)6. Extend your material(s) with views for the new distribution channel and enter the "ZXXX"item category group in the field for sales item category group (I think it is on sales 2 screenbut I am not sure, can't access a system right now).Now you should be able to create a sales order with the new distribution channel wherethe new item category is defaulted. Check that the sales order is completed when bothbilling and goods issue for the delivery is posted. If not check the completion rule in the

new item category.Good luck-----End of Message-----Restricting Number Of Items In Billing DocHow I can restrict number of items in an invoice?If I enter more than 8 items in a sales order and those items get copied into deliverydoc then to billing doc. But our client want to restrict number items to 8 (max) in aninvoice.You can restrict delivery with delivery tolerance, thereby causing invoicing of the desired.orGo to SPRO>>>IMG>>>Sales & Distribution>>>Billing>>>Billing Documents>>>Countryspecificfeatures>>>Maintain Maximum No. Of Billing Items.This is where you can define a maximum number of items allowed for all billing documents within agiven sales organization.However, maintaining data here is not enough alone to bring about a billing split by number ofbilling items.You must also go to copying control for order/delivery to billing document at item level under "DataVBRK/VBRP" and maintain routine 006 "individual invoice limited" or a similar routine that accessesthe data maintained here.Credit ManagementHow To Do Configuration For Credit ManagementCredit and risk management takes place in the credit control area. According to your corporaterequirements, you can implement credit management that is centralized, decentralized, orsomewhere in between.An organizational unit that represents the area where customer credit is awarded and monitored.This organizational unit can either be a single or several company codes, if credit control isperformed across several company codes. One credit control area contains credit controlinformation for each customer.For example, if your credit management is centralized, you can define one credit control area for allof your company codes.If, on the other hand, your credit policy requires decentralized credit management, you can definecredit control areas for each company code or each group of company codes.Credit limits and credit exposure are managed at both credit control area and customer level. Youset up credit control areas and other data related to credit management in Customizing forFinancial Accounting. The implementation guide is under Enterprise Structure -> Definition orAssignment -> Financial Accounting and then Maintain credit control area. You assign customers tospecific credit control areas and specify the appropriate credit limits in the customer master record.Tips by : Kapilaa

Settings for determining the credit control area of a document. The settings of items 1 - 4 aretaken into account according to their priority. The credit control area found is stored in field VBAKKKBER.1. Transaction OB38Check which credit control area is assigned to the company code.Company code:Credit control area:2. Transaction OVFLCheck which credit control area is assigned to the sales area.Sales area:Credit control area:3. Transaction XD02 or VD02Check which credit control area is assigned to the payer.Payer:Credit control area:4. Transaction SE37Is user exit EXIT_SAPV45K_001 being used?5. Transaction OBZKFor the settings under items 2 - 4, field "All company codes" must be marked in TransactionOB45, or the credit control area must be entered under the relevant company code in tableT001CM of the credit control areas allowed.Company code:Credit control areas allowed:6. Settings for the credit checks7. Transaction OVAKWhich settings do exist for the sales document type used?Sales document:Check credit:Credit group:8. Transaction OVADWhich settings do exist for the delivery type used?Delivery type:Credit group for delivery:Credit group for goods issue:9. Transaction OB01Credit management/Change risk categoryDefinition of the risk category for each credit control area. This risk category can beassigned to a credit account by using Transaction FD32.10. Transaction OVA8Here, the individual credit checks for key fieldso credit control areao risk categoryo credit group are set. Take these key fields from the above settings and go to the detailscreen. In particular, check whether fields "Reaction" and "Status/block" are setcorrectly. To carry out follow-up actions in case of a credit block, the credit checkstatus must be set (field "Status/block").

11. Transaction FD32Credit master data for the payer of the relevant document.Credit account:Credit limit:Risk category:Currency:12. Settings for updating the credit values Update of the credit values is required for the limitcheck (static or dynamic credit limit check).13. Transaction OVA7Update of the credit value is active for the corresponding item type if the check box is marked.This field corresponds tofield "Active receivable" in Transaction VOV7.Item type:Active receivable:14. Transaction V/08, PricingIn the pricing procedure used for pricing, subtotal "A" must be entered in a line fordetermining the credit value (mark the pricing procedure and doubleclick on "Control").Usually, the net value plus taxes is used. This way the system is determined to use thissubtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used forupdate and credit check.You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".Pricing procedure:Line with subtotal = 'A':15. Transaction OB45Which update group (field "Update") do you use in the relevant credit control area? Thedefault setting is "12". If you use another update group, check whether this is fine withyou. If you open an OSS message, please tell us the alternative update group.Credit control area:Update:16. Transaction OMO1Which kind of update did you choose for structure S066?In any case, "Synchronous update (1)" has to be chosen as the kind of update.All other settings will lead to errors.MRP block for Credit limit attained CustomersHow to block the requirement (MD04) generated by the item category in a sales orderwhen the customer has attained the credit limit? The MRP requirements still appeareven though the schedule is zero.You should try and use one of the standard requirements.See in transaction "VOFM".Under Requirements / Subsequent Functions / Reqs.Availablity.Try using routine 103, you may have to tweak if it doesn't work exactly as you'd like.For example, you can write a routine 903 because you only wanted this reaction for certainbusiness units. Irregardless, using a routine similar to this will prevent the requirement fromappearing in MD04 for orders blocked on credit.Code:DATA: W_ZSDCRD TYPE ZSD_CREDITBLCK.

DATA: W_CMGST LIKE VBUK-CMGST.SELECT SINGLE * INTO W_ZSDCRDFROM ZSD_CREDITBLCKWHERE KKBER = VBAK-KKBERAND CTLPC = VBAK-CTLPC.IF SY-SUBRC = 0 AND VBUK-CMGST CA 'B'.IMPORT VBUK-CMGST TO W_CMGST FROM MEMORY ID 'CREDIT'.IF W_CMGST = SPACE.MESSAGE I706(Z1).EXPORT VBUK-CMGST TO MEMORY ID 'CREDIT'.ENDIF.*} REPLACE*{ INSERT DEVK966908 1*} INSERT* Read the subsequent function information for the messagePERFORM FOFUN_TEXT_READ USING GL_FOFUNCHANGING FOFUN_TEXT.MESSAGE ID 'V1' TYPE 'E' NUMBER '849'WITH FOFUN_TEXTRAISING ERROR.*{ INSERT DEVK966908 2*} INSERTENDIF.ENDFORM.Credit Mgmt Dynamic checking-----Original Message-----Subject: Credit Mgmt Dynamic checkingFrom: Richard DraganiHi credit experts,Does anyone know how I can automatically re-execute a dynamic credit check a few days prior toshipment for future dated sales orders. Any ideas would be appreciated.Rich Dragani-----Reply Message-----Subject: Re: LOG: Credit Mgmt Dynamic checkingFrom: Swami SubramanyanProgram RVKRED08? Or manually execute function module SD_ORDER_CREDIT_RECHECK.RegardsSwami-----Reply Message-----Subject: Re: Credit Mgmt Dynamic checkingFrom: Leslie PaolucciWe check credit at the time of the delivery (at delivery creation and before picking) and use theblocked sales doc process/list to release them. This can be set up in customizing under riskmanagement-> credit management.

-----End of Reply Message-----Sales value field in not getting updated aftercreating the billing-----Original Message-----Subject: Sales value field in not getting updated after creating the billingwe are on 4.6b. we are going for credit management but facing one problem. in fd32-customer credit management change - the sales value feild in not getting updated aftercreating the billing.eg. when i create the order - the order value get updated in the sales value in fd32. aftercreating the delivery - that value remains same in the feild of sales value. but when i amgoing for billing (delivery related), the bill value is appearing in 'receivables' but the amountin 'sales value' is not getting reduced. because of this the credit exposure is increasingcontinuously.update group for corrosponding credit ctrl area is 12. also the item is mark for creditupdate.can anyone tell the missing link?thanking in advance-----Reply Message-----Subject: RE: Sales value field in not getting updated after creating the billingHi,You need to check couple of settings like:1. Your customer should be assigned the credit control area.2. In your Item Category Credit should be active.Regards,-----Reply Message-----Subject: RE: Sales value field in not getting updated after creating the billingcustomer is assign to concorn CCA and item category is mark for credit active-----Reply Message-----Subject: RE: Sales value field in not getting updated after creating the billingHi,Check the credit update group in the transaction OB45. The credit update group controlswhen the values of open sales orders, deliveries and billing documents are updated. Itshould be '000012'.Further also refer to the OSS note 18613.Have fun-----End of Message-----Difference Between Simple and Automatic CreditCheck TypesExplain in detail difference between simple and automatic credit check types. Inautomatic check, difference between static and dynamic checks.SIMPLE CREDIT CHECK : Tr.Code - FD32It Considers the Doc.Value + Open Items.Doc.Value : Sales Order Has been saved but not deliveredOpen Item : Sales Order has been saved , Delivered, Billed & Transfered to FI, but not received thepayment from the customer.

Eg: Customer Credit Limit is Rs.1,00,000/-Suppose Doc.Value + Open Item Value is Rs.1,10,000/-Here credit limit exceeds then system reacts.Options : A) Warning MessageB) Error Message (Sales Order won't be saved)C) Error Message with Delivery BlockAUTOMATIC CREDIT CHECK : Give extra credit facilities to the particular customer.STATIC CREDIT LIMIT DETERMINATION :Checking Group + Risk Catageory + Credit Control Area.A) Credit Checking Groups : Types of Checking Groups.01) Sales02) Deliveries03) Goods IssueAt all the above 3 levels orders can be blocked.B) Risk Catageory : Based on the risk catageories company decide how much credit has to give tothe customer.HIGH RISK (0001) : LOW CREDITLOW RISK (0002) : MORE CREDITMEDIUM RISK(0003) : Average CreditStatic Credit Check it checks all these doc value & check with the credit limit1) Open Doc.Value / Sales Order Value : Which is save but not delievered2) Open Delivery Doc.Value : Which is delivered but not billed3) Open Billing Doc.Value : Which is billed but not posted to FI4) Open Item : Which is transfered to FI but not received from the customer.DYNAMIC CREDIT CHECK : 1) Open Doc2) Open Delivery3) Open Billing4) Open Items5) Horizon Period = Eg.3MonthsHere the System will not consider the above 1,2,3& 4 values for the lost 3 monthsThen assign the Sales Doc & Del Documents.Sales Doc.Type(OR) + credit Check(0) + Credit Group (01)Credit Limit Check for Delivery Type : Del.Type (LF) + Del CreditGroup (02) + Goods Issue Credit Group (03)Set Up for Credit Card Payment ProcessingGiven below is the set up for credit card payment processing:Set Up Credit Control Areas:Define Credit Control AreaTransaction: OB45Tables: T014Action: Define a credit control area and its associated currency. The Update Group should be‘00012’. This entry is required so the sales order will calculate the value to authorizeAssign Company Code to Credit Control AreaTransaction: OB38Tables: T001

Action: Assign a default credit control area for each company codeDefine Permitted Credit Control Area for a CompanyCodeTransaction:Tables: T001CMAction: For each company code enter every credit control area that can be usedIdentify Credit PriceTransaction: V/08Tables: T683SAction: Towards the end of the pricing procedure, after all pricing and tax determination, create asubtotal line to store the value of the price plus any sales tax. Make the following entries:Sub to: “A”Reqt: “2”AltCTy: “4”Automatic Credit CheckingTransaction: OVA8Tables: T691FAction: Select each combination of credit control areas, risk categories and document types forwhich credit checking should be bypassed. You need to mark the field “no Credit Check” with thevalid number for sales documents.Set Up Payment GuaranteesDefine Forms of Payment GuaranteeTransaction: OVFDTables: T691KAction: R/3 is delivered with form “02” defined for payment cards. Other than the descriptor, theonly other entry should be “3” in the column labeled “PymtGuaCat”Define Payment Guarantee ProcedureTransaction:Tables: T691M/T691OAction: Define a procedure and a description.Forms of Payment Guarantee and make the following entries Sequential Number “1”Payment Guarantee Form “02”Routine Number “0” Routine Number can be used to validate payment card presence.Define Customer Payment Guarantee FlagTransaction:Tables: T691PAction: Define a flag to be stored in table.Create Customer Payment Guarantee = “Payment Card Payment Cards (All Customers can usePayment Cards)”.Define Sales Document Payment Guarantee FlagTransaction:Tables: T691RAction: Define the flag that will be associated with sales document types that are relevant forpayment cards

Assign Sales Document Payment Guarantee FlagTransaction:Tables: TVAKAction: Assign the document flag type the sales documents types that are relevant for paymentcards.Determine Payment Guarantee ProcedureTransaction: OVFJTables: T691UAction: Combine the Customer flag and the sales document flag to derive the payment guaranteeprocedurePayment Card ConfigurationDefine Card TypesTransaction:Tables: TVCINAction: Create the different card types plus the routine that validates the card for length and prefix(etc…)Visa , Mastercard, American Express, and DiscoverCreate the following entries for each payment cardAMEX American Express ZCCARD_CHECK_AMEX MonthDC Discover Card ZCCARD_CHECK_DC Month*****MC Mastercard ZCCARD_CHECK_MC MonthVISA Visa ZCCARD_CHECK_VISA MonthThe Routines can be created based on the original routines delivered by SAP.*****SAP does not deliver a card check for Discover Card. We created our own routine.Define Card CategoriesTransaction:Tables: TVCTYAction: Define the card category to determine if apayment card is a credit card or a procurement card.Create the following two entriesCat Description One Card Additional DataCC Credit Cards No-check No-checkPC Procurement Cards No-check CheckDetermine Card CategoriesTransaction:Tables: TVCTDAction: For each card category map the account number range to a card category. Multiple rangesare possible for each card category or a masking technique can be used. Get the card numberranges from user community. Below is just a sample of what I am aware are the different types ofcards.Visa Credit Expires in 7 days.400000 405500405505 405549

405555 415927415929 424603424606 427532427534 428799428900 471699471700 499999Visa Procurement Expires in 7 days.405501 405504405550 405554415928 415928424604 424605427533 427533428800 428899Mastercard Credit Expires in 30 days500000 540499540600 554999557000 599999Mastercard Procurement Expires in 30 days540500 540599555000 556999American Express Credit Expires in 30 days340000 349999370000 379999Discover Card Credit Expires in 30 days601100 601199Set Sales Documents to accept Payment Card Information Transaction:Tables: TVAKAction: Review the listing of Sales Document types and enter “03” in the column labeled “PT” foreach type which can accept a payment cardConfiguration for Authorization RequestMaintain Authorization RequirementsTransaction: OV9ATables: TFRMAction: Define and activate the abap requirement that determines when an authorization is sent.Note that the following tables are available to be used in the abap requirement (VBAK, VBAP,VBKD, VBUK, and VBUP).Define Checking GroupTransaction:Tables: CCPGAAction: Define a checking group and enter thedescription. Then follow the below guidelines for the remaining fields to be filled.AuthReq Routine 901 is set here.PreAu If checked R/3 will request an authorization for a .01 and the authorization will be flagged assuch. (Insight does not use pre-authorization check).

A horizon This is the days in the future SAP will use to determine the value to authorize(Insight does not use auth horizon period).Valid You will get warning message if the payment card is expiring within 30 days of order entrydate.Assign Checking Group to Sales DocumentTransaction:Tables: TVAKAction: Assign the checking group to the sales order types relevant for payment cardsDefine Authorization Validity PeriodsTransaction:Tables: TVCINAction: For each card type enter the authorization validity period in days.AMEX American Express 30DC Discover card 30MC Master card 30VISA Visa 7Configuration for clearing housesCreate new General Ledger AccountsTransaction: FS01Tables:Action: Two General Ledger accounts need to be created for each payment card type. One for A/Rreconciliation purposes and one for credit card clearing.Maintain Condition TypesTransaction: OV85Tables: T685Action: Define a condition type for account determination and assign it to access sequence “A001”Define account determination procedureTransaction: OV86Tables: T683 / T683SAction: Define procedure name and select the procedure for control. Enter the condition typedefined in the previous step.Assign account determination procedureTransaction:Tables:Action: Determine which billing type we are using for payment card process.Authorization and Settlement ControlTransaction:Tables: TCCAAAction: Define the general ledger accounts for reconciliation and clearing and assign the functionmodules for authorization and settlement along with the proper RFC destinations for each.Enter Merchant ID’sTransaction:Tables: TCCM

Action: Create the merchant id’s that the company uses to process payment cardsAssign merchant id’sTransaction:Tables: TCCAAAction: Enter the merchant id’s with each clearinghouse accountDunning Process In Credit ManagementExplain about dunning process in credit management?Let me explain in simple terms:1) You have a Customer which you had felt, he is doing good business and supplied material onCredit of 45 days.2) Since this customer is good as you felt, you have not managed Credit Checks as well. So, he hadcomfortably reached to the fullest credit (or even more) which you can afford for any customer.3) One fine day you got realised that, there is very bad debt with this customer and need torecover from him and till then, there will be no further supply to the customer.4) Your company's legal department has laid a policy that, inorder to recover any bad debts, like:a) We will send a normal payment reminder.b) In case customer doesnt respond, we will send at least further reminder (dunning notice) may be9 times(9 reminders) (Dunning level) and what intervels of time (dunning frequency)c) Still if the customer doesnt resopond for the reminders, you will file a law suit against thecustomer for recoveringthe Payments.d) Finally, after getting veridict, you may proceed for auction of his property or as per the order forLaw.Now in SAP, the definition of Dunning procedure is a pre-defined procedure specifying howcustomers or vendors are dunned.For each procedure, the user defines- Number of dunning levels- Dunning frequency- Amount limits- Texts for the dunning noticesIn SAP, you will maintain the Dunning Procedure at customer master. Referring to this your SDTeam / FI Team (user team) will effect DunningPS: You might remembered the dunning procedure laid by Relaince Mobile, sometime back, sendingstreet rowdies for recovering the bad debts from users. That is dunning. Remember Reliance, youwill not forget dunning forever.Product AllocationImplement the Product Allocation FunctionalityWe are required to implement product allocation functionality in SAP R/3 (EnterpriseVersion).We tried to do the elaborate steps as per the implementation guide but are notsuccessful. Can you kindly help by giving the simple steps for implementation.

Please see if the following helps:Configuration Overview; Allocation Specific Usage1.Allocation Procedure (OV1Z) The product allocation procedure is the parent of the entireallocation process. All materials that are to be included in the allocation scheme are required tohave an allocation procedure assigned to it in the material master. In addition, as of release 4.0, itis in the procedure that the method of allocation is defined. The user has the opportunity to set anindicator to identify their choice of two different methods (discrete and cumulative allocation) toevaluate the quantities to be considered for product allocation.2.Allocation Object (OV2Z) The allocation object is the root level of the allocation process whereactual data is entered and planned in LIS. The object allows the user to further break down aprocedure into smaller parts for future validation of components comprising a specific material3.Allocation Hierarchy Mapping (OV3Z) Primarily, this transaction permits the assignment of anallocation procedure to an LIS information structure. Secondly, a character is assigned to theinformation structure to permit collective planning. Finally, the user can assign a step level to theprocedure and information structure to sequence the order in which allocation quantities arechecked. This functionality allows the user the opportunity to check product allocation againstseveral product allocation scenarios, before the required quantity is confirmed4.Define Consumption Periods (OV5Z) The allocation consumption periods functionality is only validif the allocation method flag has been set (OV1Z). If you have de-selected the method field, thisfunctionality is not available. The consumption window indicates the number of past and futureperiods to be used in the allocation check.5.Control Product Allocation (OV4Z) In order for the allocation process to function properly,allocation control records are created primarily to map allocation procedure steps to theircorresponding objects so that the allocation data records can be located for validation. Secondly,validity periods must be established to indicate when the allocation control records are active.Finally, the user has the option of establishing a conversion factor per allocation control record toaccommodate BOM listings of constrained materials6.Activate Allocation for Requirement Class (OVZ0) In order to turn on allocation in the standardorder processing functionality, the requirements class must have a flag indicating that allocation isrelevant.7.Activate Allocation for Schedule Line Category (OVZ8) In order to turn on allocation in thestandard order processing functionality, the schedule line must have a flag indicating thatallocation is relevant8.Create Planning Hierarchy (MC61) In order to adequately establish allocation quantities, the usermust initially determine the level at which the allocation is to take place and the aggregation factorof the allocation quantities. In this step, the levels for the collective allocation search procedure arealso identified.9.Generate Masking Character (OV7Z) Upon completion of the level determination for the planning

hierarchy, the collective allocation masking character must be generated to allow aggregationindicators to be established. This transaction simply reads the hierarchy established in the planningtable and then generates a collective mask character for each level of the hierarchy10.Modify Planning Hierarchy (MC62) This step is a repeat of MC61 where the initial hierarchy wasestablished. In order to complete the hierarchical set up, the collective allocation (mask character)hierarchy must now be maintained with the appropriate aggregation factors11.Allocation Procedure Assignment to Material Master (MM02) At the root level of the allocationprocess are the materials. Each material that is to be considered in allocation scenario must bemapped to an allocation procedure. In order entry, then, when a material is entered with a validallocation procedure in the material master, the allocation data is verified prior to confirming theline item ordered12.List of Suitable Structures (OV9Z) This report is used to identify potential LIS informationstructures that can be used in the product allocation process. This report simply reads through thedata dictionary and selects all the active information structures that contain the field productallocation object (KONOB) as the first field. This data can then be utilized in the mappingtransaction (OV3Z) to link the allocation procedure step to an information structure (previous step).