Pricing

[former_member949397]

HI,

When I was creating new condition table no,what r the things

I have to select from the table.After that while creating v/07,How can define assess seq,And their fields,WHat r the condition type v/06 i will choose/While defining v/08 How I can define procedure & Control.Please explain me all the points i.e-v/03,v/07,v/06 &v/08.ANd how Link to ovkk.Please solve this issue.

Thanks & regards,

Rajendra.

[Former Member]

hi rajendra,

what yor are asking is the complete pricing procedure configuration.

pl check this notes and let us know if there is doubt in anything.

PRICING:

Pricing is the combination of creating correct pricing procedure that map the business needs & processes, such as correct pricing & discounting, & keeping to the legal requirements placed on the business, such as adhering to the tax laws of the country.

SPRO- IMG- SD- Basic Functions- Pricing- Pricing Control—

Create Condition Table: V/03, V/04, V/05

Define Access Sequence: V/07

Define Condition Types: V/06

Define & Assign Pricing Procedure

Maintain Pricing Procedure: V/08

Define CuPP: OVKP

Define DoPP: OVKI. The DoPP indicator is used to determine pricing in conjunction with the sales area & CuPP.

Assign DoPP to Order Types & Billing Types: OVKJ & OVTP

Define Pricing Procedure Determination: OVKK

Create Condition Table: V/03, 04, 05

Put the most general field for e.g., Sales Orgn in the highest position & the most specific field in the lowest. After organizational fields, place fields from doc header before those that come from item level (customer comes before material).

Sales Orgn, Distbn Channel, Div, Cust, Mat: Customer Specific Price

Sales Orgn, Distbn Channel, Div, Price List Type, Mat: Price List

Sales Orgn, Distbn Channel, Div, Mat: Material Price.

Maintain Access Sequence: V/07

Go to new entries, define 4-digit acc seq. Select acc seq, go to Accesses and place the cond tables and check exclusive indicator (which determines that if a cond record is successfully found, the system will stop searching further). Select each cond table and go to Fields.

• There are some cond types for which you do not create cond records (header discounts that you can only enter manually). These cond types do not require an access sequence.

Define Condition Type: V/06

They are used in the pricing procedure to define how the cond is going to perform, such as either a %tage or a fixed amount. The cond type can be automatic or it can allow manual changes. Copy the required cond type and rename. Then assign acc seq to cond type.

If you use different calculation types for what are otherwise the same conditions (for e.g., %tage, as fixed amt, qty dependent), you do not have to define different cond types in customizing. You can set different calculation type when maintaining cond records.

Access Sequence

Condition Class: surcharge & discounts or prices

Plus/Minus: -ve, +ve or both

Calculation Type: fixed amt, %tage, qty, wt, voln

Rounding rule: commercial, round up and round down

Group Cond

Manual Entry: whether manual or automatic entry has priority

Header Cond: after entering the header cond type click on the button activate. The cond amt of the header conditon is copied as it is to all the line items in the doc.

Item Cond

Amount/ Percent: check & u can change the amount or % for the cond type during data processing

Delete: check & the cond record may be deleted from the doc.

Value: check & the value of the cond type can be changed during data processing

Calculation Type: check & the cal type can be changed during doc processing

Valid from & to

Scale Basis: determines how the system interprets a pricing scale in a cond, for e.g., the scale can be based on qty, wt, voln

Check Value: indicates whether the scale rates must be entered in ascending or descending order.

Define and Assign Pricing Procedure: V/08

A pricing proc consists of a lists of cond types in a defined order, such as price less discount plus tax. Go to new entries, define 6-digit pricing proc with descp. Select the 6-digit pricing proc and go to Control Data, you will be faced with an empty structure.

Step: the no that determines the sequence no of a cond type with in a procedure

Counter: second mini step with in an actual step

Conditon type: specify the cond type

From & To: if you specify the ref steps in these fields, the cond values of the 2 steps specified and steps in between are totaled

Manual:

Mandatory: whether a cond type is mandatory when system carries out pricing

Statistical: the value represented in this step will not alter the overall value

Print: which cond types should be printed on a doc (order confirmation, invoices)

Subtotal: controls whether & in which fields the cond amts or subtotals are stored

Requirement: for a cond type to be executed in the sales doc the requirement specified here must be satisfied. (It is a gateway)

Alternative Calculation Type: alternative formula to the formula in the std system that determines the cond. In the std SAP system for the cust expected price EDI1, the alt cal type is 9, which means it contains a routine with a logic which states that the difference between the customer expected price & the net value is zero.

Alternative Cond Base Value: alternative formula for determining the cond basis (amt to which the discount or surcharge in a scale refers)

Account Key: this field enables the system to post the sales value to different G/L accounts. ERL: sales revenues, ERS: sales deductions, ERF: freight revenue.

Accruals: this is exclusively for rebate cond types BO01 & BO02. Key, which identifies various types of G/L accounts for accrual postings.

TAX: MWST

Tax is calculated on the following parameters:

Plant

Ship to party region

Customer tax classification

Material tax classification

Pricing Procedure Determination: OVKK: Determination Rule

Before one can proceed with the determination rule, one needs to maintain the CuPP & DoPP. One needs to assign a single character alphanumeric key with a short descp. Then assign the DoPP to the sales doc types. This will ensure that for e.g., all sales orders created using order type OR, which has been assigned a DoPP of 1, will all use the same pricing proc if created in the same sales area & with the same CuPP. In some instances, you may not want to have the same pricing proc for a sales doc, as you may want in a billing doc. For this reason, you may allocate a different DoPP to a billing doc.

Do not forget to assign the CuPP indicator to your CMD in the Sales Screen

Sales Orgn + Distbn + Division + CuPP indicator + DoPP indicator = Pricing Procedure

regards

sadhu kishore

[Lakshmipathi]

dear rajendra

You were supposed to post 5 seperate questions but you have clubbed all in one.

Instead of asking a generic question, why dont you explain your process and ask doubt from that so that it will be easy for others to reply.

I dont think you will be able to understand all these impacts in one explanation, as each and every tocde (V/03, V/06 etc) will have its own functionality and it will be difficult for the mebers to consolidate and post.

thanks

G. Lakshmipathi