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.
Is there any table where I can get condition type and its access sequence assigned KONV KONP T685A Table T685A will give you the condition type details. Table T682 will give you access sequence details.

T685 table. Usage A - Pricing Application V you will get condition type and it's access sequence. Pricing procedures - T683 Access sequence - T682 You can't see access sequence in T685A

condition types
In this step you define condition types to use in Profitability Analysis (CO-PA). A condition type is a key used that defines the attributes of a condition and identify the condition in the system. You can use condition types to calculate expected costs or sales deductions. For example, you can define conditions to create expected costs as a percentage of the sales revenue or based on the quantity sold. In addition, you can define price conditions to determine the standard price of the product sold. And you can define base conditions to find or calculate values to be used as a basis for calculating other conditions in a costing sheet. The attributes of a condition type are defined by the following: o Condition category o Calculation type o Condition class o Scale basis In addition, you can set other flags for each condition type to determine whether it can be changed during condition analysis and for condition master record maintenance. The following contains a description of these attributes of a condition type. Condition category The condition category is used to classify conditions according to predefined criteria, such as whether the condition is a base value or a price. The following condition categories can be used in CO-PA: E Cash discount G Transfer price K Base value excluding tax S Standard cost T Moving average cost " " (no condition category): for conditions that do not fit into any of the above categories, such as surcharges and deductions For conditions of the category G, the system reads either the standard price ("S") or the moving average price ("V") of the material, depending on which price control flag is set in the material master. condition class B. No access sequence is required for this condition type. For condition category S , the system reads the standard price from the material master regardless of the price control. For condition category T , the system reads the moving average price from the material master regardless of the price control. Condition types of the categories G, S, and T do not require access sequences. The condition category E lets you calculate a percentage from the payment key in the customer master record. Conditions of this category have has no effect unless a payment key exists in the master record of the customer you entered. Calculation type The calculation type determines how the system calculates the value for a condition. The result can be an absolute value (such as a price) or a percentage which refers to a quantity. The following calculation types can be used in CO-PA:

A Percentage B Fixed amount C Quantity-dependent D Gross-weight-dependent E Net-weight-dependent F Volume-dependent Condition class The condition class divides condition types into one of the following classes: A Discounts or surcharges B Prices Scale basis The scale basis determines how the system interprets scaled condition records of a condition. The scale can be based on quantities or values. The following scale bases can be used in CO-PA: B Value scale C Quantity scale Change options The change options let you determine which parameters of the condition type can be changed during condition analysis. You can specify which of the following can be changed: amount/percent, value, calculation type, or quantity conversion. You can also allow users to delete the condition type. Condition record maintenance Under condition record maintenance, you can define whether the system should check scaled rates. That is, you can determine whether the scales must be defined in ascending or descending order. The following overview shows which combinations of the parameters (condition category, calculation type, condition class, scale basis, and access sequence) are required for different condition types.

Konditionsart a) Define reference value

CCat. CalcT. C.cl. Sc.B. A.C. K B B -

b) Price from material master

ba) Price acc. to price control bb) Standard price S

G C

C B

B -

bc) Moving average price

c) Cash discount from cust. master d) Percentage surcharge/reduction

da) Without scale

yes

db) With value scale dc) With quantity scale

A A

A A

B C

yes yes

e) Quantity-dependent surcharge/reduction

ea) Without scale eb) With value scale

C C

A A B

yes yes

ec) With quantity scale

yes

f) Fixed value fa) Without scale B B yes

fb) With value scale

yes

The change options and condition record maintenance are independent of these settings. All condition types not assigned to the categories K, G, S, T, or E, must be assigned to an access sequence. This assignment is required so that you can maintain condition records for that condition type (such as a discount of 1 USD per unit). The following examples show how the condition types listed here need to be defined. Where an access sequence is required, it is assumed that this access sequence calls for the system to read a condition table that uses the characteristic "Material group". Example 1 A base condition is defined for revenues from Sales and Distribution (SD). In the costing sheet you can use this base condition to calculate surcharges and reductions. Entries Condition type: Define tracing factor Condition category: K, Calculation type: B, Condition class: B Example 2 The value is read from the material master depending on the quantity. For example, if the standard price for the material M099312 is USD 100 and the imputed quantity is 5 units, a condition calculates the value USD 500.

Entries Condition type: Allocation value according to price control Condition category: G, Calculation type: C, Condition class: B Condition type: Standard price Condition category: S, Calculation type: C, Condition class: B Condition type: Moving average Condition category: T, Calculation type: C, Condition class: B Example 3 The percentage for the cash discount is taken from the customer master. Entries: Condition type: Define cash discount from customer master Condition category: E, Calculation type: A, Condition class: A

Example 4 1. You can maintain the following condition record for materials group 312: 1% surcharge/reduction (e.g. from revenue as the imputed freight or sales commissions) Entries Condition type: Define fixed percentage surcharge/reduction Condition category: -, Calculation type: A, Condition class: A, with access sequence 2. You can maintain the following value stack for materials group 312: 3% surcharge/reduction (e.g. from net revenue as a rebate) starting at sales of USD 10,000 3.5% surcharge/reduction (e.g. from net revenue as a rebate) starting at USD 50,000 Entries Condition type: Define scaled percentage surcharge Condition category: -, Calculation type: A, Condition class: A, Scale basis B, with access sequence 3. You can define the following quantity scale for materials group 312: 1% surcharge/reduction (e.g. from net revenue as a rebate) starting at a sales quantity of 1000 units 2% surcharge/reduction (e.g. from net revenue as a rebate) starting at a sales quantity of 10,000 units

Entries Condition type: Define percentage surcharge/reduction scaled by quantity Condition category: -, Calculation type: A, Condition class: A, Scale basis: C, with access sequence Example 5 1. You can define the following condition record for materials group 312:

Surcharge/reduction of USD 1 (e.g. for packaging) Entries Condition type: Define non-scaled quantity-based surcharge/reduction Condition category: -, Calculation type: C, Condition class: A, Scale basis -, with access sequence 2. You can define the following value scale for materials group 312: USD 0.10 surcharge/reduction per unit (e.g. as a customer discount) starting at revenue of USD 100 USD 0.20 surcharge/reduction per unit (e.g. as a customer discount) starting at revenue of USD 500 Entries

Condition type: Define value-scaled surcharge/reduction Condition category: -, Calculation type: C, Condition class: A, Scale basis: B, with access sequence

3. You can define the following quantity scale for materials group 312: USD 0.10 surcharge/reduction per unit (e.g. as a quantity discount) starting at 1000 units USD 0.30 surcharge/reduction per unit (e.g. as a quantity discount) starting at 10,000 units Entries

Condition type: Define quantity-scaled surcharge/reduction Condition category: -, Calculation type: B, Condition class: B, Scale basis: -, with access sequence

4. You can define the following quantity scale for materials group 312: USD 50.00 fixed (e.g. for additional services) starting at sales of 1000 units USD 70.00 fixed (e.g. for additional services) starting at sales of 10,000 units Entries

Condition type: Define fixed value with quantity scale Condition category: -, Calculation type: B, Condition class: B, Scale basis: C, with access sequence

Activities
Create your CO-PA-specific condition types. Note that you must define and save your access sequences before you can assign these to your condition types and create condition records.

Further Notes

You can delete condition records that are no longer valid. Once you have done this, these condition records will no longer be used in valuation. However, they still remain in the system until the next reorganization. How to delete a condition record To delete a condition record, go to the IMG activity "Create condition records", call up the detail screen for the condition record, and choose "Cond.records-Cond.type". You can delete condition records here using the function "Edit -> Delete". As stated above, this deactivates the condition record, which is indicated by a checkmark in the column "D" on the detail screen. You can reactivate the condition record by choosing "Edit -> Cancel deletion". Of course, this is only possible as long as the condition record remains in the system. Once it has been deleted during a reorganization, it can no longer be activated. How to reorganize condition records Once you have set the deletion indicator for condition records, you can remove these records from the system by reorganizing your conditions. You do this using the archiving object SD_COND in archive administration (transaction SARA). To reorganize your condition records in Profitability Analysis, you need to create an archive file and select those condition records with use "A" and application "KE". For more information on archiving, see the online documentation for transaction SARA.