8/4/2019 6998819 16 Fields Description in Pricing Procedure Copy

1/4

Step:

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

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

Ex.: 10, 15 etc.

Counter:

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.

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

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

counter.

Condition Type:

It represents pricing element in pricing procedure as a base price, discount, freight

and tax.

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.

Ex.: PR00 - Price

K004 - Material Discount

K005 - Customer/Material Discount

K007 - Customer Discount.

Description:

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:

8/4/2019 6998819 16 Fields Description in Pricing Procedure Copy

2/4

This indicator specifies whether the specific condition type can be determined manually

during sales order processing.

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

to be automatic.

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

For Discounts and Freights, The entry should be manual.

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.

If we uncheck the box, in VA01 when we go to conditions at the header/item level, the

condition type will be listed.

Mandatory:

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

procedure.

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.

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.

Mandatory check box should be checked in condition types which are compulsorily

required in pricing procedure. Ex.: PR00, MWST.

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:

This indicator if it is activated will not allow the value of the condition type to be taken

into net value calculation.

It is used only for information purposes only.

This indicator causes a surcharge or discount to be set in the document statistically

(that is, without altering the value).

This is commonly used for condition types

o SKTO - Cash Discount

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

Print:

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:

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

which table and which field.

8/4/2019 6998819 16 Fields Description in Pricing Procedure Copy

3/4

Controls whether and in which fields condition amounts or subtotals (for example, a

customer discount or the cost of a material) are stored.

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

individual amounts.

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:

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

requirement.

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

type.

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).

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".

This Requirement will ensure that these condition types will appear only during the

billing document processing.

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

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

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

o We have a list of requirements, we can ask ABAP consultant to create new

requirement based on the client requests.

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

AltCty - Condition formula for alternative calculation type:

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

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

formulas.

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.

Ex.: 950 0 Profit Margin 11.

So we assign 11 - Profit Margin.

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

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

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

o We have a list of routines, we can ask ABAP consultant to create new routines

based on the client requests.

o And we assign the application type.

8/4/2019 6998819 16 Fields Description in Pricing Procedure Copy

4/4