Pricing Date

Pricing date based on delivery date Used 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 using the requested delivery date. If your requirement is for PR00 to alone to be priced at delivery date then this will not work.

Pricing date based on delivery date Used 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 using the 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 order and 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 / purchase order date segment. Then you can choose the follwoing options: Blank - Indicates the current date as the pricing date A - Indicates the date based on the requested delivery date B - Indicates the date based on the order validity start from date And 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 values mentioned 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 mentioned in 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 Condition Price Which 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 the prices 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| | -------------------------------------------------------------------------Fast Links:

Mass Update of condition pricing You 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 have to 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 work because 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). or if you don't want to do that Online, write your own abap report and use Function SD_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 sales price automatically The 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 the pricing 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 and some others using PR00, then you should use requirement routines to enable the correct price condition type at the right time. The second method involves more work as you need to write a formula (VOFM) to get that information. 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 subtotal B. The routine (created with transaction VOFM) is: RV64A901 FORM FRM_KONDI_WERT_600. XKWERT = KOMP-WAVWR. ENDFORM. The pricing procedure than looks like that: Step 1 VPRS statistical, subtotal B, reqt 4 Step 2 PR00 Altcty 600

Customer discounts on effort only -----Original Message----Subject: Customer discounts on effort only Hi All, We have a requirement of giving a discount to customer based on the total amount invoiced so far (across financial years). Where do we set this up? We have seen so far the discounts are calculated based on the value of the current invoice. The discount should be on a graduated scale basis for example 0 - 100000 No discount 100000 - 200000 5% 200000 - and above 10%

This means that discount would only start after the customer's net sale value crosses 100000. For example, if the customer has been billed for 99000 and the current invoice 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 amount billed so far, but only on the effort billed and not on reimbursements (like airfares, living expenses, visa charges, beeper charges etc). The discount applies only to the effort and not to the reimbursements. In the above example (invoice of 3000) say the effort billed is only 1500, the rest being reimbursements. The discount is only on the 500. (the rest being taken up by the lower limit for eligibility of 100000) For example the customer might have been billed say 150000 so far but actual effort billed might be only 90000, the rest being reimbursements of actual costs and hence the customer is not eligible for the discount. Kindly help, -----Reply Message----Subject: RE: Customer discounts on effort only Hi, The solution for this is Using rebate condition types and suitable condition records. Of this to handle your first problem that is the rebate has to be applied only on the "effort" you have to set up a line in the pricing procedure which 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 applied automatically when it reaches the first scale for which the values span few financial years. This I am not really sure whether it can be made possible in the invoice itself. But a work around is not giving the discount directly in the invoice but settling it against the rebate agreements by Credit notes periodically. Hope it helps. Thanks -----Reply Message----Subject: RE: Customer discounts on effort only Hi

Arent we looking at rebate agreeement. That appears to be a straightaway solution to your problem. You activate the sales organization and the payer for that Regards -----Reply Message----Subject: RE: Customer discounts on effort only I 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 basis G.Scale based on a formula ( be: your based amount is invoice ). Define scale formula. You need ABAPER to define it. 2. Using routine in Alt.calc.type ( tcode V/08 , Maintain Pricing Procedure ). Here, you also need ABAPER to create routine. hope this help

Steps to Create Commission for Agent For 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 FUNCTIONS Transaction Code: VOPA 2) Assign the Partner Functions to Partner Procedures Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS Transaction Code: VOPA 3) Create a Partner Procedure for the Commissionees Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS Transaction Code: VOPA 4) Create New Customer Account Group(s) for Commission Agents Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; LOGISTICS GENERAL ->; LOGISTICS BASIC DATA: BUSINESS PARTNERS ->; CUSTOMERS ->; CONTROL ->; DEFINE ACCOUNT GROUPS AND FIELD SELECTION FOR

CUSTOMER Transaction Code: OVT0 5) 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 ASSIGNMENT Transaction Code: VOPA 6) Assign the Partner Functions to the Partner Procedure for the Sales Document Header Menu Path: Tools ->; Business Engineer ->; Customizing ->; Sales and Distribution ->; Basic Functions ->; Partner Determination ->; Define Partner Functions Transaction Code: VOPA 7) 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 FUNCTIONS Transaction Code: VOPA 8) Edit the Pricing Communication Structure (KOMKAZ) to Hold the New Functions (Client Independent) Menu Path: Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; DICTIONARY Transaction Code: SE11 9) Edit MV45AFZZ – userexit_pricing_prepare_tkomk (Client Independent) Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR Transaction Code: SE38 10) Edit RV60AFZZ - userexit_pricing_prepare_tkomk (Client Independent) Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR Transaction Code: SE38 11) Edit MV45AFZB - userexit_new_pricing_vbkd changing new_pricing (Client Independent) Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR Transaction Code: SE38

The following code should be inserted into program MV45AFZZ to allow the system to re-execute pricing 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 SEQUENCES Transaction Code: OV24 14) Create Condition Tables (Client Independent) Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES Transaction 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 SEQUENCES Transaction Code: V/07 16) Create a new condition type Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE CONDITION TYPES ->; MAINTAIN CONDITION TYPES Transaction Code: V/06 17) Add the Condition Type to the Pricing Procedure Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE AND ASSIGN PRICING PROCEDURES ->; MAINTAIN PRICING PROCEDURES Transaction Code: V/08 11) Create Commsission Report ZZCOMMISSION (Client Independent) Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR Transaction Code: SE38

SD Questions About Pricing Condition The 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 own Condition Types,Condition

Tables & Access Sequences. What we do is, we just define our own pricing procedures by using the existing condition types (i.e: PR00, K004, K007, KA02, KF00 etc.) & then assign that Pricing Procedure with " Sales Area, Document Pricing Procedure & Customer Pricing Procedure " . After that we put the values against each Condition Types, mentioned in our Pricing Procedure by using 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 sequence table 304 is available. Now when I was entering the PR00 in VK31 it shows error Table 304 is not defining for the condition type PR02. But when I was entering the PR00 at VK11 it is accepting it. Difference between VK11 and VK31 - if you go through the menu path you will get the vk 31 as condition record from the tamplets whereas vk11 as simple condition record. In VK11 you can store condition record for more than one condition type. This means you can have same condition record for different condition types.This feature is given to enhance the system's performane and not to create the duplcation of the work for each condition type. Again system is not allowing to store the record in the vk31 for the condition type pr00 and access sequence pr02.This is because if you see this ac seq cointains two accessses 20 and 30 having the same table no.But you see there is the difference between the technical view of it for transfering the 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 item condition applies to each item in a sales document. Header condition can only be applied to an entire document. Difference between header and item condition - as YOU CORRECTLY SAID HEADER CONDITION IS APPLICABLE FOR THE WHOLE DOCUMENT where as item is for item.Ex-Say fright is dependent on the total weight of all the items in the documents then header condition adds on weights of all items 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

discount 2% at header level which is also applicable to all the items b)Second is the accumulation of the values of all the item at the header level,as earlier explained for the weight/fright. These differenes are controlled through the indicator of group condition in the cond.type configuration. And so obviously header condition can not have the condition record and hence access sequence. SAP SD Tips by : Vishwajit Disallowing 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 Types Change condition type ZOBP's plus/minus indicator to "A" which means only positive is allowed. *-- Arvind Rana In 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 a particular condition type to be executed. Eg. PR00: req 2 ie item relevant for pricing VPRS/EKO1: req 4 ie cost Rebate BAO1 Req 24/Req 25 etc 2. Subtotal: this represents where a which table a value is stored, which can be processed for further 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 on volume 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 per unit., the base value is 45 units, but if the client wants a standard base value in some casesto be assumed inspite of maintaining the scale, an alternate base value is confihured, that is the base value based on which the order value is to be calculated changes. 5. Accruals: Accruals are maintained for rebate agreements, it constitutes the total accumulated value which customer has earned through rebate, one the rebate for certain amount is settled the amount from the accruals get deducted. *-- Nitin

Add a Field To New Condition Table in Pricing Add 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 sequenceTry to add the filed from the field catalog. In case the required combination field is not there, you can add the field through the following process to filed catalog and create the condition table. It is most 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 in structure 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 the field in the field catalog. Condition access, field catalog, allowed fields, KOMG, KOMK, KOMP, KOMPAZ, KOMKAZ, PSTYV are the 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 as a domain.As a short text, you can use, for example, 'ZZ - sales document item category' and as a field 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 and make the following entry: Component Component type: ZZPSTYV ZZPSTYV Save, 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 in USEREXIT_PRICING_PREPARE_TKOMP: MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV. In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include RV60AFZZ. Consider that you can also use this note as a help if you want to use other customerspecific fields as key fields in a condition table. For header fields, use structure KOMKAZ instead of structure KOMPAZ and USEREXIT_PRICING_PREPARE_TKOMK instead of USEREXIT_PRICING_PREPARE_TKOMP. For more information, see Transaction SPRO via the path 'Sales and Distribution -> System Modifications -> Create New Fields (Using Condition Technique) -> New Fields for Pricing' and OSS Note 21040.

Header Condition and Group Condition What are header conditions? Header conditions are those which appear in the header level of any sales order. these conditions are to be entered manually and get distributed automatically and the basis for distribution are taken 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 Chokshi

What 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 a material based on common property. Header Condition: This is a manual condition which you apply to header (Condition screen) of a sales 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 1 - 10 11 - 50 51 - 150

Discount Rs. 100.00 Rs. 105.00 Rs. 110.00 etc.

2. You are creating a sales order for a customer with five different items with different quantities as below ITEM 1 - 25 No's ITEM 2 - 3 No's ITEM 3 - 12 No's ITEM 4 - 27 No's ITEM 5 - 62 No's All the material is having the material group = 01. 3. While calculating the discount, because of this group condition, system add the quantities of items which have material group = 01. In the above example total quantity is = 109. System apply a 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 value based on individual item quantity which is as below. Discount ITEM 1 - 25 No's Rs. 105.00

ITEM 2 - 3 No's ITEM 3 - 12 No's ITEM 4 - 27 No's ITEM 5 - 62 No's

Rs. 100.00 Rs. 105.00 Rs. 105.00 Rs. 115.00

5. Is it clear now. Just try a sales order and see the out come Procedure 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.

Steps Involved In Condition Technique What are the 8 steps involved in condition technique? By: Rohit Joshi It starts with an understanding of the factors that influences the Price. Lets say it depends on Customer and Material. With this understanding now we will start with the Table where we will pass the above parameters. There is a table 5 which already has Customer and Material so we can now copy and rename it or use the same table in our Pricing Procedure. T Code VOK0 Step 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 Sequence Step 3. Define your Condition Type (There are four Price Types Basic Price, Discount, Freight and Tax) 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 Procedure and Customer Pricing Procedure along with Sales Organisation, Distribution Channel. Step 6. Maintain Condition Records for your Condition Types I guess you can make it 8 Steps by dividing some of the main steps. Few important things to note is following.. 1. XD01 - Create Customer - Always ensure that you pick the right Customer Pricing Procedure from here.

2. VA01 - Sales Order - Ensure that you have the right Document Pricing Procedure from here 3. While Creating Access Sequence, check your Fields and ensure that they appear with any warning (Highlighted in Red) 4. Do not forget to mention your Access Sequence while defining your Condition Type 5. Always remember that your Procedure Determination has only Basic Price as Condition Type 6. Do not forget to mention the Range (From To) while creating your Pricing Procedure. I made most of the mistakes that appear above. Hope it helps.

Sales Order Freight Condition In Header Condition ERP SAP ==> SD SAP Common questions: We are using the Freight in Header Condition. I maintained two line items in the Sales Order. So the Header freight is splitting irregularly for two line items (in item conditions) . How it is happening? Any formula is there? Header Conditions - Automatic pricing does not take header conditions into account; you can not create condition records for them in the standard system. Header conditions are entered manually in order processing. R/3 includes the following header conditions: - Percent discount (HA00) - Absolute discount (HB00) - Freight (HD00) - Order value (HM00) Header Condition: If this condition is marked as a header condition, it is possible to enter the condition type in the header condition screen. Checks for changing the condition manually are unaffected by this. Group Condition: Group conditions are helpfull incase of discounts. If group condition is selected then the discount percentage or quantity is applicable for the total sum of the quantity in the PO for those materials belonging to the same material group. Suppose if two materials of same matl grp have discounts for 100 qty and above but in PO if the two matls are bieng procured for 50 qty then they cant avail discounts but if group condition is selected then the sum of the quantity of both matl of same matl group is considered (50 + 50) and discount can be availed for 100 qty. Further Group condition: Indicates whether the system calculates the basis for the scale value from more than one item in the document.

The nature of header condition is that whatever value you are giving in sale order / billing, line item wise, it will be distributed proportionately. If you access V/06 and the header condition type, you can see that the condition type - does not have any access sequence - field Group condition is selected Normally Freight Header condition like condition type "HD00" is calculated on the basis of weight. This is a Manual condition and you have to enter it in the header screen. It will be proportionately distributed on each item on the basis of weight. If you will uncheck the group condition field, the same freight amount will be copied to each item, possibly irrespective of different weight which may not be logical. That is the standard behaviour of the header condition type. Based on whether the group condition field is ticked on or off, it will either split the header condition value to the items on pro-rata basis or it will just duplicate the header value to all the items. What you are experiencing with Fixed Amount Header conditions is standard behaviour. Please see below Notes: - 876617 FAQ: Header conditions / Header condition screen - 317112 Behavior of conditions w/ calculation rule B changed - 485740 Conditions with fixed amount in copy activities To achieve what you wish (absolute amount), solution is in the below Notes: - 84605 Transfer absolute amount condition to billing doc. - 25020 Value changes during over/underdelivery - 25144 Freight conditions during milestone billing

How To Use Condition Exclusion Type In SO What is meant by condition exclusion for Condition types and records? Condition Exclusion The system can exclude conditions so that they are not taken into account during pricing in sales documents. Material 4711 costs 150 USD. Some customers receive a discount of 10 USD per 100 pieces.

However, a specific customer can buy the material for 100 USD. Since this is a particularly good price, the customer should not also have a discount of 10 USD per 100 pieces. Therefore, this discount is to be excluded from pricing. To do this, you must follow two steps: You must set a condition exclusion indicator for the price. You can do this in two ways: If you want to set the condition exclusion indicator a follows then you specify it: - for all condition records of a condition type (e.g. with condition type PR00) when defining a condition type in SD Customizing - for an individual condition record (e.g. only for material 4711) in the detail screen of a condition record (in the Condition exclusion field) You must set a condition for the discount in the pricing procedure in Customizing for sales. If this condition is set, the discount is not valid if the condition exclusion indicator is set. Condition 2 is available in the standard R/3 System. The condition exclusion indicator is not valid for condition supplements. This means that if a condition record contains condition supplements they will be taken into account during pricing. Condition Exclusion Group – In any normal situation there could be more than one condition type in a pricing procedure offering a discount to a customer. Should the discounts be automatically determined, there is the risk that the customer will receive all the relevant discounts and thus purchase the product for a lower price than he should. By using ‘condition exclusion groups’ you can ensure that the customer does not receive all the discounts, but instead only receives the best of the available discount condition types. Menu path – IMG - Sales & Distribution - Basic functions – pricing – condition exclusion – condition exclusion for groups of conditions (OV31). A condition exclusion group is merely a grouping of condition types that are compared to each other during pricing and result in the exclusion of particular condition types within a group or entire groups. It is important to note that the condition types you want the system to compare must exist in the pricing procedure and must have valid condition records created for them.

If for example, a sales order is created using the pricing procedure that the exclusion group is assigned to, you can see that the condition offering the most favorable discount to the customer is represented in the pricing procedure. For instance, condition type K007 has offered a discount of 10% off the sale price or a real value of $30, while another condition type K005 has offered a real value discount of $10. The system then takes the best discount for the customer between the two, which is K007 and makes the other discount K005 inactive. This can be seen by double clicking on the condition type K005, where you can find a entry saying ‘Inactive A condition exclusion item’. There are four possible methods of using condition exclusion groups – A – best condition between the condition types B – best condition within the condition types C – best condition between the two exclusion groups D – exclusive E – least favorable within the condition type F – least favorable within the two exclusion groups Configuring ‘Condition Exclusion Groups’ First step is to define a ‘condition exclusion group’ by using a four character alpha numeric key. Next step is to assign the relevant condition types to the exclusion groups such as discount condition types, freight condition types. After completing the assignment of the condition types to the exclusion group, proceed with assigning the condition exclusion group to the relevant pricing procedure. After selecting the pricing procedure for which you want the condition exclusion to be active, select the folder ‘Exclusion’ where you can assign the relevant condition exclusion procedure to the relevant condition exclusion group. When using the condition exclusion group to find the best condition record in a condition type – only use one condition type per exclusion group. The most important thing to remember here is to “deactivate” the Exclusive Indicator on the access sequence assigned to that condition type. Otherwise, the system will merely find the first condition record and stop searching for other records.

Pricing Report & Condition Index What is difference between pricing report & condition index? Pricing Report: A Pricing report basically helps to get the list of all the pricing details which we have maintained in the system. We can get details of all the condition types including the scales. We can get the details as per our requirement i.e., Sales org/Dc/Division/Plant /material etc wise. The selection criteria would be as per the Key combination which you select in the IMG screen You get following information from pricing report. 1. It informs you about the customer specific price agreements that were made within a certain period 2. From pricing report you can know which condition records exist for freight charges 3. Which condition records exist for customers in a particular region or country You can create your own pricing reports with V/LA. Also V/LD is very useful. This can be customized. The sales personnel use it to 1. get information for price (discounts) that existed at previous period (Say June 200X) 2. Inform potential buyer about the current price (and discounts) 3. Review price and discounts. Though all the above T Codes and there are many More standard SAP Reports have very high utility, it is not widely used. Clients prefer customized reports when it comes to pricing reports - all Z programs and Transactions. These kind of reports are generally required by the Top Management for periodical review // Finance team for price control // Master data team for record purposes // Process audits by Internal/external agency // Of late, for every SOX audit done in the company...especially the change records for prices. Condition Index

Condition index is very useful for searching the condition record for a customer. It becomes easier and faster to search for condition records for a customer or material just like it become easier to search a topics in the book with help of index. You have to mark the "condition index" check box in the condition type and you have to activate the index in customization. You can set the discount for fast ten orders through "condition update". First, in your discount condition type(V/06) activate the "condition update" check box. Second, in the condition record, in additional data put "maximum number of orders" as 10. You may also create the condition record for discount through VK31. Now go to change(VK32), scroll to the right, you will find a column "N". This is maximum number of order field. Here you can put value 10 and save it. Now, system will give the discount to the first 10 orders.

What Is Condition Base Value? Where does the standard condition base value (Default one) is determined for a Condition type? First check the Material Master UOM Conversion - Additional Data - Units of Measure. Condition base value is a concept used in pricing procedure and actual term used is alternate condition base value. This is a formula assigned to a condition type in order to promote an alternate base value for the calculation of the value. If you have to calculate price of a material then you have to have a base value for it. For e.g. if you want to calculate the discount of 10 % for a material then you have to have a base value on which this 10% is calculated. Normally you take the condition value of the base price of the material to calculate the value. Now, you don't want to take the base value and take other value as base value which are derived on some formula. So you create a routine which will do the mathematical operations in the routine and derive you a value which is now used as the base value for calculating the condition value for a particular condition type. As per my understanding there is Alternative Condition Base Value, It is a routine which is assigned to the condition type in the pricing procedure.

Go to transaction V/08 here you select pricing procedure then go in to the control data of the pricing procedure here you can find Alter native Condition Base Value in the 14th column of the pricing procedure control data. What is the difference between: 1. Conditional base value 2. Conditional value. 3. Conditional amount 1. Conditional base value When a value is derived for a condition type, based on certain calculation this value is taken as base. 2. Conditional value. For the number of units ordered depending on the condition amount mentioned this value is derived. 3. Conditional amount This is nothing but the unit list price what you are mentioning for the line item. 1) What is the role of alternative calculation type, condition base value, requirement in pricing procedure? 2) Where do we define value for alternative condition base value and alternative calculation type so that system picks up different value, when the value for alternative condition base value and alternative calculation type is mention in pricing procedure? **Alternative Calculation Type:** This function allows you use a formula as an alternative in finding the value of the condition type, instead of standard condition technique. this can be used to calculate complex tax structures. Alternative condition base value The alternative condition base value is a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value. Example

An absolute header discount is, for example, distributed in the standard system according to the cumulative value of the items. If the system distributes the absolute header discount according to volume based on the Alternative formula for condition base value , a header discount of $30 results in the following discounts: Item Value Volume . 1 $1000 2 cbm 2 $500 4 cbm Stand. disc. Volume disc.(With Formula) $20 $10 $10 $20 Condition formula for alternative calculation type Alternative formula to the formula in the standard system that determines a condition. Requirement This function is used to assign a requirement to the condition type. This requirement can be used to exclude the system from accessing the condition type and trying to determine the value. This can be used to specify that the condition type should only be accessed if the customer has a low risk credit.

Rounding Off Condition Not Appearing In Sales Order In sales order Diff condition type is not coming, when checked in analysis it says requirement 013 is not fulfilled, but in pricing procedure I've assigned the requirement as 013, alt.cal type-16, alt CBV-4. Please refer to the following documentation for requirement 013: RE LV61A013 Title

Rounding as per Table T001R Purpose This is an example of a pricing requirement. This requirement is met if an entry has been made in the 'Unit to be rounded up to' field in Table T001R. Table T001R stores the rounding rules for company code and currency combinations. This requirement can be assigned to the condition type in the pricing procedure that is used to calculate the difference when rounding. Using this requirement, the difference is only calculated when necessary. Example A company has the requirement to carry out rounding for certain company code and currency combinations. This information is stored in Table T001R. In the document pricing procedure, the user has configured the SAP delivered condition type DIFF to calculate the difference when rounding occurs. The user also assigns pricing requirement '13' to the condition type DIFF in the pricing procedure so that the condition is only calculated when a corresponding entry has been maintained in the table T001R. Please check the customizing table T001R. or try this go to IMG path --> SAP Netweaver --> General Settings --> Currencies --> Define rounding rules for currencies. Here maintain the rounding unit which will be stored in Table T001R. then in the t-code ob90 you can maintain that. Go to v/08 maintain in condition base value 16 routine. Purpose This is an example of a condition value formula. This type of formula can be used to influence the value shown for the condition in pricing. A condition value formula is assigned to a condition type or value line in the pricing procedure. Formula '16' was delivered along with condition type DIFF to support the rounding unit rules that can be defined in T001R for company code / currency combinations. Condition type DIFF was delivered to perform the rounding at the end of the pricing procedure with the total value. Using formula '16', the system computes the rounded value and assigns the difference to the condition type DIFF. In-17 c.base value Round according to T001R

Purpose This is an example of a condition value formula. This type of formula can be used to influence the value shown for the condition in pricing. A condition value formula is assigned to a condition type or value line in the pricing procedure. Formula '17' was delivered so that a condition value could be rounded off according to the rounding unit rules (e.g. plus 5 or 10 or 100 units) that can be defined in T001R for company code / currency combinations. When formula '17' is assigned to a condition type, the condition value will always be rounded using T001R. Where I can do setting of rounding profile for a new created condition type? 1) Create Rounding rule ( Unit of measure rounding rules ) Path : Materials --> SPRO Quantity Optimizing and Allowed --> Order Optimizing --> Purchasing --> Management Unit of Measure Rounding Rules --> Logistics Units of Measure Here give new rounding rule and % rounding up and down values 2) Create Unit of measure groups Path : Order Optimizing --> Purchasing --> Materials Management --> SPRO Unit of Measure --> Quantity Optimizing and Allowed Logistics Units of Measure Groups Create new group for YD and ROL 3) Dynamic rounding profile Path : Order Optimizing --> Purchasing --> Materials Management --> SPRO Maintain Rounding --> Quantity Optimizing and Allowed Logistics Units of Measure Profile Here give Rounding profile name and plant and click on Dynamic to create new profile In next screen give desc. For rounding profile, rounding off method as 2, and rounding rule which you have created. Assign created Rounding profile in info record also UOM group Maintain minimum order qty as 1 Rol and Order unit as ROL in Info record

In material master maintain conversion as 1 Rol = 3500 yards

How To Create Field in KOMP, KOMG New Fields in Pricing To use a field in pricing, one creates a condition table. This condition table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document and item data in SD is stored in data tables, such as VBAK and VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog. The field catalog is a structure (KOMG) that consists of two tables (KOMK and KOMP). These tables contain the header and item data for pricing respectively. They are called KOM “x” because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the fields of tables KOMK and KOMP. If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures. To use a field not defined in the field catalog, you need to add this field to the KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps: 1. Create the field in the KOMK (header data) and KOMP (item data) tables using the standard includes provided for this requirement. 2. Write the code in the user exit to read the transaction data and transfer it to the KOM “x” structures. Menu Path The menu path here is IMG, Sales and distribution, System modification, Create new fields (using the condition technique), New fields for pricing. Adding the Field to KOMK and KOMP This process requires some knowledge of the ABAP dictionary and how to use the ABAP

dictionary to create and change fields and tables. You may have to use an ABAP skill to assist you. If the field is from the header table (for example, the order table VBAK), you’ll need to add it to the include table KOMKAZ in table KOMK. If the field is from the item table (for example, the order item table VBAP), you’ll need to add it to the include table KOMPAZ in table KOMP. Let’s say you need to use the “base material” to define a price and the base material is not in the pricing field catalog. The base material is a field on the material master basic data screen and is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to the KOMPAZ include table. Note When you add a field to these tables, it must start with “ZZ.” Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARAWRKST. After adding the field, generate the structure KOMP. This field is not available in the field catalog and can be used in condition tables. Writing the ABAP Code The field in the communications structure will be blank unless the ABAP code transfers the data from the material master to the field KOMPZZWRKST. Pricing occurs in the order and in the invoice, so you need to put this code in both places. For the order transaction, write the ABAP code in user exit USEREXIT_PRICING_PREPARE_TKOMP in include program MV45AFZZ. For the billing transaction, write the ABAP code in user exit USEREXIT_PRICING_PREPARE_TKOMP in RV60AFZZ. Note : The TKOMP is for the item level. If you are writing the code for a field at the header level, you would use the user exits that end with TKOMK. The ABAP code would select the Base material field from the material master table using the material from table VBAP/VBRP. It would then transfer this field to the structure TKOMP from MOVE MARAWRKST to TKOMP-ZZWRKST.

Billing cannot be Release to Accounting This SAP message will appear if the system is unable to find the G/L codes match from the configuration in transaction VKOA No account is specified in item 0000001001 Message no. F5 670 Diagnosis No account was specified for account type "S" in item "0000001001" of the FI/CO document.

System Response The Financial Accounting program cannot process the document. Procedure A system error has probably occurred in the application you called up. Check the data transferred to item "0000001001" of the FI/CO document. Assuming that one of the key combination is Account Assignment Group, you will have to check whether 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) have been 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 sales order 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 will not be able to determine the Account Assignment Group manually.

Default Start Variant for VF04 There 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 -> Administration Select the layout display variant you want and click :Edit -> Define default settings

Condition Exclusion which will be determined in the billing document The system can exclude conditions so that they are not taken into account during pricing. For example: Material 4711 costs 150 USD. Some customers receive a discount of 10 USD per 100 pieces. However, a specific customer can buy the material for 100 USD. Since this is a particularly good price, the customer should not also have a discount of 10 USD per 100 pieces. 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 copied from 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_PR Define 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 pricing program logic will include only the higher price one, excluding the rest that are lower price.

Steps for creating a new or changing an existing Billing Document Types Create/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 to accounting. During document processing, you can manually transfer blocked billing documents to accounting by selecting: Billing -> Change -> Release accounting 2) Account determination procedure 3) 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 must be blank and the account determination procedure must be empty. 2) Cancellation billing document types: : A check is made to see if the cancellation billing 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 with VBTYP '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 the cancellation billing document type partner functions are empty or if those that correspond to the billing type used are empty. Next, make sure that you maintain the copy control for the Billing Types: Sales documents in VTFA

Target e.g. F1 - Invoice F1 - Invoice

Source OR - Standard Sales Order ZOR - Your Sales Order

Billing documents in VTFF e.g. G2 - Debit Memo F1 - Invoice G2 - Debit Memo F2 - Invoice Deliveries in VTFL e.g. F1 - Invoice LF - Delivery F1 - Invoice ZOR - Your Delivery Usually 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 assign it Define the possible block indicators in SM30 - V_TVFS and allocate 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, or 2. item categories in SM30 - V_TVAP, by filling the fields Billing Block.

Billing Plan for Milestone Billing Milestone billing means distributing the total amount to be billed over multiple billing dates in the billing plan. As each milestone is successfully reached, the customer is billed either a percentage of

the entire project cost or simply a pre-defined amount. During sales order processing, the system determines from the item category whether a billing plan is required and, if so, which type of plan The 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 milestone billing have different overview screens so that you can enter data relevant to your processing. For example, for milestone billing, you must be able to enter data to identify the individual 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 and construction projects. Such projects often include a series of milestones that mark the completion of different stages of the work. In the SAP R/3 System, milestones are defined in a network along with planned and actual dates for the completion of work. The milestones are also assigned to the billing dates in the billing plan. Each milestone-related billing date is blocked for processing until the Project System confirms that the milestone is completed.

Delivery-relevant order items for which a milestone billing plan applies are billed on the basis 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 individual schedule 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, select 1. 2.

Item -> Schedule lines. Mark the schedule line and select Procurement details.

The following figure shows an example of milestone billing where only the Contract have been billed : Order

Item

Turbine

100,000

Billing Plan Billing date Description Billing Status 01-10-94 Contract 01-03-95 Assembly 01-04-95 Maintenance 01-05-95 Acceptance 01-06-95 Final invoice

%

Value

10 30 30 30 ..

10,000 30,000 30,000 30,000 ..

Billing Block x x x x

Milestone x x x x

Network/Activities Milestone Assembly Maintenance Acceptance

Estimate 01-03-95 01-04-95 01-05-95

Actual 01-03-95

For each billing date in a milestone billing plan, you can specify whether the billing date is: 1. fixed 2. always updated with the actual date of the milestone 3. updated with the actual date of the milestone, if the date is earlier than the planned billing date for the date

Billing Plan Function and Processing Explain what is Billing Plan.

x

Billing plan processing includes the following functions:           

Automatic creation of billing plan dates Pricing Billing block Billing index Billing status Billing rule for milestone billing Fixed dates in milestone billing Document flow Creating with reference Exchange rate determination Automatic Creation of Billing Plan Dates

In Customizing for Sales, you control how the system automatically creates the schedule of dates in a billing plan. The system determines the schedule of individual dates based on general date information, such as the start and end dates. This general date information is copied either from contract header data or from proposals in the billing plan type. Pricing Sales document items are billed as each billing date in the plan becomes due. The system determines the amount to be billed either from the condition records that are applicable to the item or from the values that are explicitly entered in the billing plan for a particular billing date. In milestone billing, for example, you can specify a percentage to be billed or an actual amount. Billing block A billing block can be set for each date in a billing plan. The block prevents processing for a particular billing date but does not necessarily affect any of the other dates in the plan. In milestone billing, the system automatically sets a billing block for each billing date. This block remains in effect until the project system reports back that the milestone in the corresponding network has been successfully completed. At this point the system removes the block. Billing index For every billing date in a plan, the system creates and updates a billing index. If a billing date is blocked for billing, the system copies this information into the index. Billing status The system assigns a billing status to each billing date in the plan. The status indicates to what extent the billing has been processed for that particular date. After billing has been

carried out successfully, the billing status is automatically set to ‘C’. This prevents a billed date from being billed again. Billing Rule for Milestone Billing For every date in the milestone billing plan, you can specify a billing rule. The rule determines how the billing amount for the particular date is calculated. For example, you can specify whether the billing amount is a percentage of the total amount or whether it is a fixed amount. In addition, you can specify that the amount to be billed is a final settlement that takes into account billing that has not yet been processed. For example, price changes may take place after billing dates in the plan have already been processed. The price differences can be taken into account during final settlement. Final settlement is not automatically proposed in the billing plan by the system; you must enter it manually during processing. Fixed dates in milestone billing You can control for each date in a billing plan, whether the date is fixed or whether the system copies the date from the planned or actual milestone dates in a project. Document flow After a particular date in a billing plan is processed for billing, the system updates the document flow for the corresponding sales document item. The document flow for the sales document displays the following data:   

Creation date Billing date Billed value

Creating with reference When you define a billing plan type in Customizing for Sales, you can enter the number of an existing billing plan to serve as a reference during subsequent billing plan creation. During sales order processing for items that require billing plans, the system automatically proposes the reference plan and, if necessary, re-determines the billing dates (based on the current date rules) for inclusion in the new billing plan. Exchange rate determination

In the billing plan with partial billing, you can store a certain exchange rate for each date. The amount billed is the amount determined after using this exchange rate to convert from the local currency into the document currency. An exchange rate can also be stored at item level for the sales document (field: Exchange rate for FI on the Billing tab page. This fixed rate is valid for all dates in the item billing plan for which no rate is specified in the billing plan. If an exchange rate is entered both for the date in the billing plan and at item level in the exchange rate field, then the system uses the rate specified for the date during billing. If no exchange rate is entered for the the date or at item level, then the system uses the exchange rate used for invoice creation and it is forwarded to FI. When using a header billing plan, all billing plans linked to this header billing plan are automatically updated. If, for example, you enter an exchange rate manually for the first date in the header billing plan, this is automatically copied to the corresponding dates for the item billing plans.

SAP Billing - Combine Billing for deliveries with different date When using transaction VF04 or Billing (background), the date of the billing document (e.g. the current date) must be entered (In VF04 : settings, default data.) In VF06 or background: variant with parametrization) to avoid an unwanted split due to the billing date. This OSS notes is very helpful :11162 - Invoice split criteria in billing document 36832 - Invoice split in fields from the sales order

Billing Spilt by Item Category Is it possible to split invoice Item category wise. I mean If in sales order there is TAN and TANN then the invoice should split,is it possible? Naina Yes, it is possible. Create a modification of copy control routine for billing and use VBAP-PSTYV as an additional split criteria there. Martishev Sabir

Thank you for your reply. Can you please tell me the exact steps what should I add under that(additional split criteria). Naina In trx VTFA (if your billing is sales order based) choose your billing type and SO type, there select your item categories and there select the field VBRK/VBRP data. In that field you will see the currently used routine. With the help of your ABAP guy create a copy of that routine under a different 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 criteria DATA: 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 criteria DATA: BEGIN OF ZUK, MODUL(3) VALUE '001', VTWEG LIKE VBAK-VTWEG, SPART LIKE VBAK-SPART,

PSTYV LIKE VBAP-PSTYV, Material Master --> Settings for Key Fields --> Data Relevant to Sales and Distribution --> Define Product Hierarchies --> Maintain Product Hierarchy Product hierarchies can be created using code OVSV. A product hierarchy is assigned to the material master record. The hierarchy is broken down into specific levels, each level containing its own characteristics. A product hierarchy is recorded by the sequence of digits within a hierarchy number. The hierarchy number can have a maximum of 18 digits with a maximum number of nine levels. Thus by assigning the hierarchy number to the material, one can determine a classification of the material. This hierarchy can be used in pricing with each level being used as field in the condition technique. It’s like if you are having category CAR. In that many cars come into picture. CAR>>MARUTI>>SX4, Swift, zen, alto. B>> 01 >>01

Then from above example B0101 is the hierarchy for SX4. So in that hierarchy many cars come, like variants and all the things. In this way you can take e.g. of wood products also. It shows the next level of the product. How many levels that product are having.

How To Configure Product Hierarchy Product Hierarchy: Product hierarchies are the domain of materials management. A product hierarchy is assigned to the material master record. This hierarchy is broken down into specific levels, each level containing its own characteristics. A product hierarchy is recorded by the sequence of digits within a hierarchy number. This hierarchy number may have a maximum of 18 digits with a maximum of 9 levels. The custom Product hierarchies can be maintained in V/76. Product Hierarchy Number of chars at Various level: In the standard system, the product hierarchy consists of up to 3 levels. The first and second levels have 5 digits and the third level has 8. The maximum number of digits is 18 and the maximum number of levels is 9. You can define hierarchy nodes at the individual levels of the product hierarchy. The product hierarchy can be structured via DDIC structure PRODHS. In the standard system, a product hierarchy can be created with up to three levels. The individual levels can contain the following number of digits: Level number of allowed digits: 15 25 38 This can be changed as of Release 3.0, where it is possible to extend the maximum number of levels to 9. If you want to change the standard setting of PRODHS, e.g. you want to change the number of levels, proceed as follows: 1. Create an appropriate domain in the Data Dictionary (type CHAR with the required length).

2. Assign these domains to the standard data elements PRODH1, PRODH2, ..., PRODH9. Please note that you should use these standard data elements. 3. Change the structure PRODHS by creating or deleting fields with reference to the data elements. Choose ZZPRODHN as field name, where n is the position of the field in the structure PRODHS. You want to change the structure of the product hierarchy from 5/5/8 digits to 5/5/5/3. Proceed as follows: Create the following domains: ZPRODH3 with length 5, category CHAR, ZPRODH4 with length 3, category CHAR, Change structure PRODHS: Structure PRODHS in the standard system: Structure Fields Data element Category Length PRODHS -> PRODH1 PRODH1 CHAR 5 PRODH2 PRODH2 CHAR 5 PRODH3 PRODH3 CHAR 8 Changes according to example: Structure Fields Data element Category Length PRODHS -> PRODH1 PRODH1 CHAR 5 PRODH2 PRODH2 CHAR 5 PRODH3 PRODH3 CHAR 5 ZZPRODH4 PRODH4 CHAR 3

Please take help of ABAPER in extending the levels of Product hierarchy. Configure for Product hierarchy at : SPRO-> IMG-> Logistics - General-> Material Master-> Settings for Key Fields-> Data Relevant to Sales and Distribution-> Define Product Hierarchies

Implement the Product Allocation Functionality We are required to implement product allocation functionality in SAP R/3 (Enterprise Version). We tried to do the elaborate steps as per the implementation guide but are not successful. Can you kindly help by giving the simple steps for implementation. Please see if the following helps: Configuration Overview; Allocation Specific Usage 1.Allocation Procedure (OV1Z) The product allocation procedure is the parent of the entire allocation process. All materials that are to be included in the allocation scheme are required to have an allocation procedure assigned to it in the material master. In addition, as of release 4.0, it is in the procedure that the method of allocation is defined. The user has the opportunity to set an indicator to identify their choice of two different methods (discrete and cumulative allocation) to evaluate the quantities to be considered for product allocation. 2.Allocation Object (OV2Z) The allocation object is the root level of the allocation process where actual data is entered and planned in LIS. The object allows the user to further break down a procedure into smaller parts for future validation of components comprising a specific material 3.Allocation Hierarchy Mapping (OV3Z) Primarily, this transaction permits the assignment of an allocation procedure to an LIS information structure. Secondly, a character is assigned to the information structure to permit collective planning. Finally, the user can assign a step level to the procedure and information structure to sequence the order in which allocation quantities are checked. This functionality allows the user the opportunity to check product allocation against several product allocation scenarios, before the required quantity is confirmed 4.Define Consumption Periods (OV5Z) The allocation consumption periods functionality is only valid if the allocation method flag has been set (OV1Z). If you have de-selected the method field, this functionality is not available. The consumption window indicates the number of past and future periods 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 their corresponding 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 to accommodate BOM listings of constrained materials 6.Activate Allocation for Requirement Class (OVZ0) In order to turn on allocation in the standard order processing functionality, the requirements class must have a flag indicating that allocation is relevant. 7.Activate Allocation for Schedule Line Category (OVZ8) In order to turn on allocation in the standard order processing functionality, the schedule line must have a flag indicating that allocation is relevant 8.Create Planning Hierarchy (MC61) In order to adequately establish allocation quantities, the user must initially determine the level at which the allocation is to take place and the aggregation factor of the allocation quantities. In this step, the levels for the collective allocation search procedure are also 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 aggregation indicators to be established. This transaction simply reads the hierarchy established in the planning table and then generates a collective mask character for each level of the hierarchy 10.Modify Planning Hierarchy (MC62) This step is a repeat of MC61 where the initial hierarchy was established. In order to complete the hierarchical set up, the collective allocation (mask character) hierarchy must now be maintained with the appropriate aggregation factors 11.Allocation Procedure Assignment to Material Master (MM02) At the root level of the allocation process are the materials. Each material that is to be considered in allocation scenario must be mapped to an allocation procedure. In order entry, then, when a material is entered with a valid allocation procedure in the material master, the allocation data is verified prior to confirming the line item ordered 12.List of Suitable Structures (OV9Z) This report is used to identify potential LIS information structures that can be used in the product allocation process. This report simply reads through the data dictionary and selects all the active information structures that contain the field product allocation object (KONOB) as the first field. This data can then be utilized in the mapping transaction (OV3Z) to link the allocation procedure step to an information structure (previous step).

Sending a billing document by e-mail First, your SAP system must be configure by the basis people in order for you to send an external mail.

Whether it can send pdf or other file format will depends on the Mail Server you are using. The basis people must also maintain the conversion parameters so that SAP knows how to convert the billing documents to be send as a pdf file or other desired format specified by your company. Finally, you have define the IMG in Maintain Output Determination for Billing Documents (Output type MAIL)

SAP Customizing Picking Output From Release 4.5A, the system does no longer display the actions for SD picking in the implementation guide. If you want to use the picking list according to the "old" procedure, you can maintain the list as follows: o Carry out Transaction V/38 to maintain the output types. o Carry out Transaction OVLT to assign the picking list types to the shipping points. o

Carry out Transaction V/53 to assign the picking lists to own forms and programs.

Program for Sales Order by Customer, Date, Sales Sales Order by Organisation, Customer - To create the Sales Order by More no of Date's User's can easily take the Report from this by selecting Different kinds like Customer Specific [And/Or] Sales Organisation Specific [And/Or] duration of date but Here Date is Mandatory Fields user must have to give date as a selection criteria In Second level this report will interact with user where they can select date to see the full Details of Sales Order Selection - Sales Organisation - Date - Customer this will be usefull when Selecting the Checkbox Standard Variants - Output - Sales Order

Example Date SalesOrderNo Material Amount Currency 10.01.2007 8530 732 1000 INR *&---------------------------------------------------------------------* *& Report ZCHE_SALES_ORDER *&--------Done by V.Chellavelu on 11.01.2007 --------------------------* REPORT

zche_sales_order

.

****************************Declarations******************************** TABLES: vbkd,vepvg.",vbak,vbap,vbpa,vakpa, vapma. DATA: BEGIN OF sal OCCURS 0, ch TYPE checkbox, vbeln LIKE vbak-vbeln, netwr LIKE vbak-netwr, matnr LIKE vbap-matnr, waerk LIKE vbak-waerk, dat LIKE vbak-erdat, END OF sal. DATA: newsal LIKE sal OCCURS

" sales document "Net Value of the SalesOrder "material no. "curr. "date. 0 WITH HEADER LINE.

DATA: amount LIKE vbak-netwr, date2(15),date3(8),date4(1), date5(2),date6(2). DATA: lin LIKE sy-curow VALUE 1,"Screens, vertical cursor position at "PAI available in SYST struc. checkbox TYPE c , dat LIKE vbak-erdat. *******************Selection**Screen**Design**************************** SELECTION-SCREEN BEGIN OF BLOCK blk1 WITH FRAME TITLE text-001. PARAMETERS: vkorg LIKE vepvg-vkorg, vtweg LIKE vepvg-vtweg, spart LIKE vepvg-spart. SELECT-OPTIONS date FOR vbkd-bstdk DEFAULT sy-datum TO sy-datum OBLIGATORY. SELECTION-SCREEN END OF BLOCK blk1. SELECTION-SCREEN BEGIN OF BLOCK blk2 WITH FRAME TITLE text-002. SELECTION-SCREEN BEGIN OF LINE. SELECTION-SCREEN POSITION 10. PARAMETERS: chk1 AS CHECKBOX. SELECTION-SCREEN POSITION 20. PARAMETERS: kunnr1 LIKE vbpa-kunnr. SELECTION-SCREEN END OF LINE. SELECTION-SCREEN END OF BLOCK blk2. ********************First**Level**Operation***************************** IF chk1 'X'. IF vkorg ''. PERFORM organisation. ELSE. PERFORM organisation_else.

ENDIF. ELSE. IF vkorg ''. PERFORM cus_orga. ELSE. PERFORM cus_orga_else. ENDIF. ENDIF. * Displaying the contents which is selected from table by * -selection conditions SORT sal BY dat. LOOP AT sal. ON CHANGE OF sal-dat. * FORMAT HOTSPOT ON. IF sy-tabix = 1. WRITE: sy-vline, sal-ch AS CHECKBOX,sal-dat . CLEAR amount. ELSE. WRITE:sy-vline, amount,/ sy-vline, sal-ch AS CHECKBOX,sal-dat. CLEAR amount. ENDIF. ENDON. amount = amount + sal-netwr. AT LAST. WRITE:sy-vline, amount. ULINE. SUM. * FORMAT HOTSPOT OFF. FORMAT COLOR = 3. WRITE:/ ' Total Amount:', sal-netwr UNDER amount. ENDAT. ENDLOOP. **********************Interaction with report************************** SET PF-STATUS 'BANU'. " To create Application ToolBar for Display Button * To verify Double click on BANU AT USER-COMMAND. " This will execute after pressing Display Button CASE sy-ucomm. WHEN 'DISP'. free newsal. DO. READ LINE lin FIELD VALUE sal-ch INTO checkbox. IF sy-subrc NE 0. EXIT. ENDIF. IF checkbox = 'X'. PERFORM datecon. PERFORM process. ENDIF. lin = lin + 1. ENDDO. PERFORM selection.

ENDCASE. ************************ SUB ROUTINE Area ****************************** *This Process SubRoutine will assign the values from current * -InternalTable (sal) into other IT(newsal), by date which is * - selected by CheckBox FORM process. LOOP AT sal WHERE dat = dat. newsal-ch = 'X'. newsal-vbeln = sal-vbeln. newsal-netwr = sal-netwr. newsal-matnr = sal-matnr. newsal-waerk = sal-waerk. newsal-dat = sal-dat. APPEND newsal. ENDLOOP. ENDFORM. "process *&---------This will display the values for selected dates from new --* *---------------------internal Table (newsal)-------------------------* *& Form SELECTION *&--------------------------------------------------------------------* *---------------------------------------------------------------------* FORM selection. ULINE. FORMAT COLOR = 1. WRITE:sy-vline,'Date',AT 14 sy-vline, 'Order NO', AT 27 sy-vline, 'Order Material', AT 48 sy-vline,'Order Value(AMT) Currency '. FORMAT COLOR OFF. ULINE. LOOP AT newsal. ON CHANGE OF newsal-dat. IF sy-tabix 1. WRITE:/ sy-vline, AT 14 sy-vline,AT 27 sy-vline,AT 48 sy-vline. WRITE:/ sy-vline,newsal-dat,sy-vline,AT 27 sy-vline,AT 48 sy-vline. ELSE. WRITE: sy-vline,newsal-dat,sy-vline,AT 27 sy-vline,AT 48 sy-vline. ENDIF. ENDON. WRITE:/ sy-vline, AT 14 sy-vline,newsal-vbeln,sy-vline, newsal-matnr, sy-vline, newsal-netwr, newsal-waerk. AT LAST. SUM. ULINE. FORMAT COLOR = 3. WRITE:/ sy-vline, AT 15 'Total Amount for selected month:', newsal-netwr UNDER newsal-netwr. FORMAT COLOR OFF. ULINE. ENDAT. ENDLOOP. lin = 1. FREE newsal. ENDFORM. "SELECTION * This Date convertion is must for pick the particular Date from the

* -displayed line, and here we are reversing the Date like YYYY/MM/DD * -because to Check or assign the date we need to give in reverse order *&--------------------------------------------------------------------* *& Form DATECON *&--------------------------------------------------------------------* * text *---------------------------------------------------------------------* FORM datecon. date2 = sy-lisel(17). SHIFT date2 LEFT BY 4 PLACES. WHILE date2 ''. SHIFT date2 RIGHT. date4 = date2+11. IF date4 '.'. CONCATENATE date4 date3 INTO date3. ENDIF. ENDWHILE. date5 = date3(2). date6 = date3+2. date3 = date3+4. CONCATENATE date3 date6 date5 INTO date3. dat = date3. * SORT dat BY dat. * DELETE ADJACENT DUPLICATES FROM dat COMPARING dat. ENDFORM. "DATECON * Here we are doing different kinds of selections by the EndUser's needs *&---------When user selectiong an Sales Organisation-----------------* *& Form ORGANISATION *&--------------------------------------------------------------------* * text *---------------------------------------------------------------------* FORM organisation. SELECT f~vbeln p~matnr c~netwr c~waerk p~audat INTO (sal-vbeln, sal-matnr, sal-netwr,sal-waerk, sal-dat) FROM ( vakpa AS f INNER JOIN vbak AS c ON f~vbeln = c~vbeln ) INNER JOIN vapma AS p ON f~vbeln = p~vbeln WHERE p~audat IN date AND p~vkorg = vkorg. APPEND sal. ENDSELECT. ENDFORM. "ORGANISATION *&---------Without Sales Organisation i.e All Organisation------------* *& Form ORGANISATION_ELSE *&--------------------------------------------------------------------* * text *---------------------------------------------------------------------* FORM organisation_else. SELECT f~vbeln p~matnr c~netwr c~waerk p~audat INTO (sal-vbeln, sal-matnr, sal-netwr,sal-waerk, sal-dat) FROM ( vakpa AS f INNER JOIN vbak AS c ON f~vbeln = c~vbeln ) INNER JOIN vapma AS p ON

f~vbeln = p~vbeln WHERE APPEND sal. ENDSELECT. ENDFORM.

p~audat IN date.

"ORGANISATION_ELSE

*&------------When Selecting Customer by choosing CheckBox------------* *& Form CUS_ORGA *&--------------------------------------------------------------------* * text *---------------------------------------------------------------------* FORM cus_orga. SELECT f~vbeln p~matnr c~netwr c~waerk p~audat INTO (sal-vbeln, sal-matnr, sal-netwr,sal-waerk, sal-dat) FROM ( vakpa AS f INNER JOIN vbak AS c ON f~vbeln = c~vbeln ) INNER JOIN vapma AS p ON f~vbeln = p~vbeln WHERE p~audat IN date AND p~vkorg = vkorg AND p~kunnr = kunnr1. APPEND sal. ENDSELECT. ENDFORM.

"CUS_ORGA

*&------------Without Customer by without choosing CheckBox-----------* *& Form CUS_ORGA_ELSE *&--------------------------------------------------------------------* * text *---------------------------------------------------------------------* FORM cus_orga_else. SELECT f~vbeln p~matnr c~netwr c~waerk p~audat INTO (sal-vbeln, sal-matnr, sal-netwr,sal-waerk, sal-dat) FROM ( vakpa AS f INNER JOIN vbak AS c ON f~vbeln = c~vbeln ) INNER JOIN vapma AS p ON f~vbeln = p~vbeln WHERE p~audat IN date AND p~kunnr = kunnr1. APPEND sal. ENDSELECT.

How To Maintain Output Types in SD ERP SAP ==> SD SAP When I am creating a bill and saving it and then giving issue output to and then header preview, the system does not respond. Should I maintain condition records? Where and how to maintain? For getting any output either by print, Fax, or any media you have to do output determination. output determination is also carried by Condition techniques. The detail procedure for Output Determination is : OutPut Determintaion :

Output is a form of media from your business to one of its business partners or it can be within the organization. The output can be sent to any of the partners defined in the document. Outputs are usually in the form of Order Confirmations, Freight List, Delivery Notes, Invoices & Shipping Notifications. Determining form of output is output determination. Types of Output: Print Output, Fax, Telex, E-Mail & EDI (Electronic Data Interchange) --> PRINT OUTPUT: Configuration path: ( following are the steps) 1) SPRO-> IMG-> Basic Functions-> Output Control-> Output Determination-> Output Determination using Condition Technique- >Output Determination for Sales Documents (or you can use output determination for billing documents depending on your requirement). 2) Create Condition Table: select the field Sales Doc Type from field catalog & Save 3) Maintain Access Sequence: 4-digits code & description. 4) Assign condition table to access sequence. Select Accesses line item and Go To Fields. Fields will display the fields we have selected in the condition table i.e. sales doc type. Maintain Output Types: AF00: Inquiry AN00: Quotation BA00: Order Confirmation LD00: Delivery RD00: Invoice Select BA00 & Copy & Rename. Give the same 4-digit code as given to access sequence. You Can Maintain: Languages of Output Partners (to whom you need to send output)

Print Program- print specification Sap Script- layout Assign Output Types to Partner Functions: go to new entries & assign your output type to partner functions. Maintain Output Determination Procedure: V10000 (Standard Procedure). Go to new entries and create your own 6-digit code with description. Select the procedure, go to Control Data. Here mention the output type i.e. condition type and leave requirement and manual only columns as blank. Determination Rule: link the 6-digit procedure code to doc types. Create Condition Records: VV11. Select document type and click on Communication. Mention partner function, medium, time. Output device: LP01, Spool request Name: SD_003, Suffix 2: order_confir & flag on print immediately. Once you press enter you will come across 2 key combinations: Sales organisation/ Customer Number: fill SO, Customer No, Partner Function Abbreviation, Partner to whom the output should be sent, time, medium, language. It contains: Sales Orgnisation, Customer, Partner Function (The abbreviated form of the name that identifies the Partner) (During output determination, the system determines the recipient of the output from the master record for the specified partner function. In this field, you can explicitly specify a recipient that will override the standard partner. There must also be a master record for the partner that is specified explicitly.), Medium, Time & Language.} Order Type: Document Type, Partner Function (abbreviation), Partner, Medium, Time & Language. Path For Output Determination For Sales Documents: Logistics -> Sales/distribution -> Master data -> Output -> Sales Document -> Create (t-code VV11) Path for Output Determination for Delivery Documents : Logistics -> Sales/distribution -> Master data -> Output -> shipping -> Create ( t-ode VV21) Path for Output Determination for Billing Documents : Logistics -> Sales/distribution -> Master data -> Output -> Billing Document -> Create ( t- code VV31)

Printing Block For Credit Block SO

Can we get the print if the order /delivery is blocked after static credit limit check? Please follow the below path: IMG - Logistics Execution - Shipping - Deliveries - Define Reasons for Blocking in Shipping - Execute - Define Reasons for Blocking in Shipping Here select the delivery block that is blocking your order/delivery, and uncheck if the option Print is checked. Display View "Deliveries: Blocking Reasons/Criteria": Overview DB Delivery block descr Order Conf.

Print DDueList

SpK

SpW

01 Credit limit 02 Political reasons 03 Bottleneck material 04 Export papers missng 05 Check free of ch.dlv 06 No printing 07 Quantity Change 08 Kanban Delivery Printing block field: Indicates whether the system automatically blocks output for sales documents that are blocked for delivery. Example : In the case of sales orders that are blocked for delivery because of credit reasons, you may want to block the printing of order confirmations. Note: The particular output that is affected by a delivery block is determined in output control.

PS: If the document is exceeds by the credit limit output type will not determine and as well as we should not give the output type in sales order. We have to assign the routine 2 to sales order output types and 3 routine to delivery output types to restrict from output if the docuement exceeds by credit limit.