pricing scenario

[Former Member]

Hi Team,

Can anyone give me a scenario in SD pricing where standard SAP fails? Now...

1.what was the scenario?

2. How did we solve it...steps needed please

It should be a functional solution ...where a functional consultant has asked customized the business with his sharpness ........ ABAP based(where we write a routine or something) solution is not preferred....

Kindly share the scenario+steps....i respect your time..

Regards,

saprules

[Former Member]

Ideally SD Pricing Scenario does not fails. It is just a matter of designing it appropriately. As concerns to meeting some specific requirements, it is possible that a routine requires to be coded through Abap to meet the requirement.

Write-up in Pricing Procedure:

Determination of Pricing Procedure:

In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure through T.Code: OVKK. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.

Configuration of Pricing Procedure:

Step 1:

Condition table (T.Code: V/04): If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).

Step 2:

Access Sequence (T.Code: V/07): If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.

Step 3:

Condition Type (T.Code: V/06): If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.

Step 4:

a. Pricing Procedure (T.Code: V/08): It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.

b. Pricing Procedure (T.Code: VOK0): After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure. (Also check 16 fields in Pricing Procedure below)

5. Condition record (T.Code: VK11 / VK12): Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.

Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.

16 fields in Pricing Procedure:

u2022 Select the pricing procedure which is the standard and copy it and create our own pricing procedure.

u2022 Highlight it and double click the Control icon in the LHS screen.

u2022 We can see that there are 16 columns in the pricing procedure, these are going to be used by the system to control the condition types.

u2022 The detail description of each column is given below.

Step:

u2022 Number that determines the sequence of the conditions with in a procedure.

u2022 It indicates the position of the condition type in pricing procedure.

u2022 Ex.: 10, 15 etc.

Counter:

u2022 System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.

u2022 Access number of the conditions with in a step in the pricing procedure.

u2022 During automatic pricing, the system takes into account the sequence specified by the counter.

Condition Type:

u2022 It represents pricing element in pricing procedure as a base price, discount, freight and tax.

u2022 The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.

u2022 Ex.: PR00 - Price

K004 - Material Discount

K005 - Customer/Material Discount

K007 - Customer Discount.

Description:

u2022 System copies description of condition type from its description (V/06).

From and To:

1. From: This can be used as a base to the condition type for calculating further value.

2. From and To: The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.

Manual:

u2022 This indicator specifies whether the specific condition type can be determined manually during sales order processing.

u2022 If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.

u2022 For Base Price and Taxes, the entry should be automatic.

u2022 For Discounts and Freights, The entry should be manual.

u2022 If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.

u2022 If we uncheck the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.

Mandatory:

u2022 This indicator specifies that particular condition type is mandatory in the pricing procedure.

u2022 If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.

u2022 If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.

u2022 Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.

u2022 If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.

Statistical:

u2022 This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.

u2022 It is used only for information purposes only.

u2022 This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).

u2022 This is commonly used for condition types

u2022 SKTO - Cash Discount

u2022 VPRS - Cost (Moving average price/Standard Price).

Print:

u2022 The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.

Subtotal:

u2022 The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.

u2022 Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored.

u2022 If the same fields are used to store different condition amounts, the system totals the individual amounts.

u2022 These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.

Requirement:

u2022 It is a routine that is written by an ABAP consultant according to the business requirement.

u2022 By defining Requirement in condition technique we can restrict the access of condition type.

u2022 To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).

u2022 For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".

u2022 This Requirement will ensure that these condition types will appear only during the billing document processing.

u2022 If new Requirements are to be defined we follow the procedure given below.

u2022 Go to T.Code: VOFM. - Maintain Requirements & Formulas

u2022 Click on the "Requirements" in the top menu and then click on "pricing".

u2022 We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.

u2022 And we assign the application type like V - Sales/Distribution etc.

AltCty - Condition formula for alternative calculation type:

u2022 It is again a Routine that is written by ABAP Consultant.

u2022 It is an alternative formula for the condition type that can be used instead of standard formulas.

u2022 For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.

u2022 Ex.: 950 0 Profit Margin 11.

u2022 So we assign 11 - Profit Margin.

u2022 If new routines are to be defined we follow the procedure given below.

u2022 Go to T.Code: VOFM. - Maintain Requirements & Formulas

u2022

u2022 Click on the "Formulas" and then on the "Condition Values".

u2022 We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.

u2022 And we assign the application type.

AltCBV - Alternative formula for condition base value:

u2022 Formula for determining the condition basis as an alternative to the standard.

u2022 It is again a Routine that is written by ABAP Consultant.

u2022 It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.

u2022 Ex.: Freight - KF00.

u2022 Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.

u2022 In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.

u2022 During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.

u2022 Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.

AcyKy - Account Key/ Accrls - Accruals:

u2022 The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.

u2022 In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.

u2022 ERB Rebate sales deduct.

u2022 ERF Freight revenue

u2022 ERL Revenue

u2022 ERS Sales deductions

u2022 ERU Rebate accruals

u2022 For Ex.,

u2022 For all Price condition types like PR00 etc. we assign ERL - Revenue.

u2022 For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.

u2022 For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.

u2022 For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.

u2022 This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.

u2022 This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.

Regards,

Rajesh Banka