cancel
Showing results for 
Search instead for 
Did you mean: 

hello

Former Member
0 Kudos

how Pricing procedure to do

Accepted Solutions (0)

Answers (9)

Answers (9)

Former Member
0 Kudos

Hi Senthil,

AWARD POINTS TO THE PEOPLE WHO HAD REPLIED TO YOUR THREADS.

BY AWARDING POINTS YOU ENCOURAGE MORE PEOPLE TO PARTICIPATE IN THIS SDN TO SHARE THEIR KNOWLEDGE AND SPIRIT AND ALSO THEY CAN CHECK THEIR LEVEL OF INTERPRETATION OF THREAD AND ALSO HELP YOU TO HAVE SEVERAL PROCEDURES/METHODS FOR A SINGLE THREAD.

[<u>b]ENCOURAGE KNOWLEDGE GIVING.</b> <b>ENCOURAGE KNOWLEDGE</b> <b>SHARING.</b></u>

THIS IS MEANT FOR ALL WHO DO NOT AWARD POINTS AFTER THEY GET REPLIES.

MOHAN

Former Member
0 Kudos

it is help full for me

Lakshmipathi
Active Contributor
0 Kudos

Hi Senthil

1. Use transaction code <b>v/07</b> to create a access sequence and assign tables based on which you want to carry on

pricing as accesses.

2. Use transaction code <b>v/06</b> to define condition type. It can be for base price, discount, freight etc.,

(Do assign relevant access sequence)

3. Use transaction code <b>v/08</b> to define pricing procedure.

4. Assign this to your relevant sales area+ dpp+cupp.

While specifying requirement, we can give reqt no.<b>22</b> which specifies that plant has to be set. This is generally done for output taxes since output taxes depend upon the delivering plant. But directly there is no assignment between plant and pricing procedure.

Hope this helps,

Thanks

G. Lakshmipathi

Manoj_Mahajan78
Active Contributor
0 Kudos

Senthilkumar,

Process flow of determining a pricing procedure –

Transaction code – V/05. Menu path – IMG – sales and distribution – basic functions – pricing – pricing control – define condition tables. Here the function key F4 can be used to check if SAP standard has already provided the required condition table with relevant fields.

If there exists no suitable table to select from the list that serves the business purpose, a new table can be created using three digits with a number of 501 – 999 with required fields. Click on generate and a new table will be generated.

The next step is to create an access sequence with the tables defined or selected earlier (T-code = V/07). It is suggested to name the access sequence, same as the condition type, to promote ease of use.

Click on new entries and enter and description of the new access sequence you want to create. Then proceed with assigning the relevant condition tables by selecting ‘accesses’ folder.

Assign the relevant condition tables here and do not forget to ‘select the exclusive indicator’ as it restricts the system to further search for the record after its first successful attempt.

Be sure to use the ‘requirements’ field as much as possible while configuring access sequence as it will ensure no unnecessary reading of access steps and thus no unnecessary reading of all associated tables and fields in it.

Save and exit the access sequence created. The next step is to assign the access sequence to a condition type.

To create a condition type, proceed to t-code V/06.

Here, copy the closest condition type found and change the name. Do not forget to assign the relevant ‘Access Sequence’ here, while configuring the control data of condition type – and then save and exit. A new condition type is created which needs to be placed in a ‘pricing procedure’.

Proceed to ‘maintain pricing procedure’. Select the standard pricing procedure and go to control data – and then replace the condition type that was copied and renamed earlier with the new condition type created. Save and exit.

In order for the new pricing procedure to come into effect – document pricing procedure and customer pricing procedure have to be defined and assigned to the relevant sales areas under ‘define pricing procedure determination’.

Note: condition type is assigned in two places during this whole process –

Maintain pricing procedures – assigned to the relevant pricing procedure in control data.

Define pricing procedure determination – assigned to sales area with pricing procedure.

The basic difference is – the first case is the actual assignment of condition type to pricing procedure, which is mandatory in order for a pricing procedure to be effective. On the other hand the second case is the proposed condition type for fast entry which is directly proposed during the sales order processing at the item level. The second case has nothing to do with the functionality of the pricing procedure.

The following is the sequence when customizing for determining a pricing procedure –

Put the fields you need into the field catalog.

Create the condition tables.

Create the access sequence.

Assign the condition tables to the access sequence.

Create the condition type.

Assign the access sequence to the condition types.

Create the required determination procedure and assign the condition types to it.

Define the customer and document pricing procedures.

Assign the determination procedure and condition type to the relevant sales area, and to a combination of document pricing procedure and customer pricing procedure.

Lastly, create the necessary condition records (VK11).

Adding fields to the field catalog –

When creating a condition table one may need additional fields besides what exists in the standard field catalog. As an instance - if a business no longer wants to have a sales discount based on sales organization, customer group and material and instead it has decided to calculate the sales discount based on sales org, customer group and material group.

In this case a new condition table is created by selecting the required fields from the field catalog while creating the condition table. But in any case if the required field doesn’t exist in the field catalog, then the required field can be added to the field catalog from the ‘allowed fields’. It is also possible to add a new field to the list of ‘allowed fields’.

Pricing –

Menu path – IMG – sales & distribution – basic functions – pricing – pricing control – define & assign pricing procedures – maintain pricing procedures (V/08).

A pricing procedure consists of a list of condition types in a defined order, such as price, less discount, plus tax. Some controls exist in the pricing procedure. For example you can specify that a condition type is mandatory; it must have an entry defined either automatically or entered manually.

The pricing procedure is also used in account determination. This determines the general ledge (GL) accounts to which the prices, discounts and taxes must be posted. The condition types in the pricing procedure are linked to an account key. This key in turn is linked to the GL Accounts. This shows the integration between the pricing in the invoice and the financial accounting module.

It is suggested to use to the SAP standard pricing procedure RVAA01 to copy and make necessary changes according to the requirement while configuring a pricing procedure. The following is the control data of the pricing procedure in detail –

1. Step – this indicates the number of steps in the procedure. The first condition type should be step 10; the second condition type should be step 20 and so on. It is possible to number the steps in the intervals of 1, but it is not suggestible as it may cause inconvenience when changing the procedure in future.

2. Condition counter – this is used to show a second mini-step within an actual step. For example, you may have assigned all you freight surcharges to step 100. However there may be three condition types, each representing a different freight surcharge. Thus you can assign a freight condition type to step 100, counter 1; another to step 100, counter 2; another to step 100, counter 3 and so on.

3. Condition type – this is the backbone of the pricing procedure. The condition type is the link from the access sequence all the way to the actual condition record. When you enter a condition type, the description field is automatically filled in with the description from the condition type.

Note: A description without a condition type can be entered for sub-total or total or net price in between the condition types in the control data.

4. From & To columns – these are used in two circumstances –

a) To define the range for a sub-total – for example, if you want to add up all the condition types from step 10 to step 50; you would enter 10 and 50 in the From and To columns respectively.

b) To define the basis for a calculation – for example, if a discount is defined as a percentage, you need to indicate which step must be used as the basis for the calculation. If the calculation must be performed from step 100, you would enter 100 in the From field.

5. Conditions determined manually – indicates if the condition type it is assigned to is allowed to be processed automatically or only manually. Conditions, that are given this indicator in the pricing procedure, are only included in determination (price determination, output determination, and batch determination) either if they are entered manually, for example, on the condition overview screen in Pricing or if they are transferred from an external process, such as costing.

6. (Note: when assigning the pricing procedure to the sales documents, a condition type is also assigned to it; reason being that the condition type assigned to the sales document here is displayed in the sales document item level which can be manually changed - provided it is indicated while configuring the control data - conditions determined manually). This feature is more often used in case of costing and output determination.

7. Condition is Mandatory – the mandatory column identifies those condition types that are mandatory in the pricing procedure. Mandatory condition types are the sales price or the cost price. If the mandatory condition is missing in the pricing procedure, the system has an error in pricing and the respective sales order cannot be processed.

8. Condition is used for statistics - This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value). This can be used to represent the cost price of the material sold.

9. Print – determines which descriptions and associated values assigned to a step are printed on a document, such as order confirmation.

10. Condition Subtotal - 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. These subtotals are used in other areas of the system such as in logistics information system. It is recommended that you assign the subtotal field 4 to the total value in the pricing procedure for Freight.

11. Requirement – this column is used to assign a requirement to the condition type. This requirement can then be used to exclude the system from accessing the condition type and trying to determine a value. This can be used to specify that the condition type, a discount, should only be accessed if the customer has a low risk credit group.

12. Alternative calculation type - specifies that the system is to use the formula represented in this column as an alternative in finding the value of the condition type, rather than by using the standard condition technique. This can be used to calculate complex tax scenarios. This field is used in obtaining values such as “Net Price”, ‘Profit Margin’ – where there wouldn’t be any access sequence to get the required value. Instead the system calculates net value using the existing amounts and the alternative calculation types. (formula: profit margin = net value – cost price)

13. 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. For example, one can specify a formula that uses a subtotal, such as 4, from the subtotal field; modify it slightly, such as dividing it by 2, and then using the resultant value as a base value for the condition type.

14. Account key - Key that identifies different types of G/L accounts. The account key enables the system to post amounts to certain types of revenue account. For example, the system can post freight charges (generated by the freight pricing condition) to the relevant freight revenue account.

15. Account key – accruals/provisions - Key which identifies various types of G/L accounts for accruals or provisions. With the aid of the account key, the system can post amounts to certain types of accruals accounts. For example, rebate accruals which are calculated from pricing conditions can be posted to the corresponding account for rebate accruals.

Note: when using a condition type using condition class B, prices, the system can only use one price per line item. Thus, should the system have a second price in the pricing procedure, it will invalidate all the previous pricing conditions. It does not benefit from having more than one price in the pricing procedure.

The following are a few important points to remember while configuring pricing procedure –

The discounts we give to the customer should not be deducted from (Gross value + Extra charges), instead all the discounts must be added together and the total discount value should be deducted from the Gross value alone before adding any extra charges such as freight.

The manual condition types most commonly used are RB00 – Discount (value) & HD00 – freight.

The most important part is the allocation of condition types to respective GL accounts –

• Pricing condition types – ERL

• Discount condition types – ERS

• Freight – ERF

• Output tax – MWS

The system automatically uses condition type VPRS as the condition to represent cost. Do not forget to mark statistics field and the requirement field (4) in configuring pricing procedure.

The rebate condition types are determined if a valid rebate agreement for the material has been created for the customer. SAP will use the rebate agreement to calculate an expected amount that this sale will contribute to the customer’s rebate. Accruals can be posted to the GL accounts. In this case the accrual account key ERU must be setup.

Rebate condition types must be defined as expense reimbursements in the condition type record, so that they are not included in the net value.

Pricing Procedure Determination –

The pricing procedure is allocated to the sales document or billing document by a determination rule, similar to other determination rules. The pricing procedure determination is based on the customer master record, the sales document and the sales area.

Pricing Procedure = Sales Area + Customer Pricing Procedure + Document Pricing Procedure

You can see this combination in OVKK

REWARD IF THIS HELPS...

Regds

MM

nisha_sharma1
Active Contributor
0 Kudos

hello Senthil,

go through this link:

<a href="http://help.sap.com/erp2005_ehp_02/helpdata/en/dd/5616cc545a11d1a7020000e829fd11/frameset.htm">pricing in SD</a>

Reward pts,if useful.

Regards,

nisha

Former Member
0 Kudos

Hi Senthilkumar

The price a customer is charged for sales depends on Tables.

LOOKING AT A PRICE TABLE FOR A SALES ORGANIZATION

MENU PATH

Logistics> Sales distribution> Sales support> Environment> Conditions> Prices>

Price list types

Field Name Input Value

Sales Organization 3000

Distribution Channel 03

Price list types 02

Document Currency USD

Valid on todays date

These Prices apply to all customer sales that match the variables input.

TO SEE A CUSTOMER SPECIFIC PRICE LIST

Logistics> Sales distribution> Sales support> Environment> Conditions> Prices> Customer Specific

Field Name Input Value

Sales Organization 3000

Distribution Channel 03

Customer 1351-995

Document Currency USD

Valid on todays date

Compare the price of the 1400-500-01 material on the two price lists.

ENTERING A CUSTOMER SPECIFIC PRICE

MENU PATH

Logistics> Sales distribution> Sales support> Environment> Conditions> Prices> Customer Specific> Conditions> Create

Field Name Input Value

Sales Organization 3000

Distribution Channel 03

Customer 1351-XX or a customer you have created

Valid from todays date

Material 1400-500-01

Rate 3500

Creating New Pricing Procedure:

What is the transaction code for creating new pricing procedure and how to attach it to specific plant?

You create PP in spro > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define and Assign Pricing Procedures > Maintain Pricing Procedures

You can't attach PP to specific plant. Pricing Procedure is determined thru trx OVKK. The defining parameters for pricing procedure determination are:

1. SalesOrg

2. Distribution Channel

3. Division

4. Document Procedure (defined in Sales doc\Billing doc maintenance)

5. Pricing procedure assigned to customer (defined in customer master)

Hope this helps.

Sabir

Reg pricing procedure.

1. Use transaction code v/07 to create a access sequence and assign tables based on which you want to carry on

pricing as accesses.

2. Use transaction code v/06 to define condition type. It can be for base price, discount, freight etc.,

(Do assign relevant access sequence)

3. Use transaction code v/08 to define pricing procedure.

4. Assign this to your relevant sales area+ dpp+cupp.

While specifying requirement, we can give reqt no.22 which specifies that plant has to be set. This is generally done for output taxes since output taxes depend upon the delivering plant. But directly there is no assignment between plant and pricing procedure.

Reward if useful to u

Former Member
0 Kudos

Hello Senthil,

The following the detailed notes on pricing procedure.

Process flow of determining a pricing procedure –

Transaction code – V/05. Menu path – IMG – sales and distribution – basic functions – pricing – pricing control – define condition tables. Here the function key F4 can be used to check if SAP standard has already provided the required condition table with relevant fields.

If there exists no suitable table to select from the list that serves the business purpose, a new table can be created using three digits with a number of 501 – 999 with required fields. Click on generate and a new table will be generated.

The next step is to create an access sequence with the tables defined or selected earlier (T-code = V/07). It is suggested to name the access sequence, same as the condition type, to promote ease of use.

Click on new entries and enter and description of the new access sequence you want to create. Then proceed with assigning the relevant condition tables by selecting ‘accesses’ folder.

Assign the relevant condition tables here and do not forget to ‘select the exclusive indicator’ as it restricts the system to further search for the record after its first successful attempt.

Be sure to use the ‘requirements’ field as much as possible while configuring access sequence as it will ensure no unnecessary reading of access steps and thus no unnecessary reading of all associated tables and fields in it.

Save and exit the access sequence created. The next step is to assign the access sequence to a condition type.

To create a condition type, proceed to t-code V/06.

Here, copy the closest condition type found and change the name. Do not forget to assign the relevant ‘Access Sequence’ here, while configuring the control data of condition type – and then save and exit. A new condition type is created which needs to be placed in a ‘pricing procedure’.

Proceed to ‘maintain pricing procedure’. Select the standard pricing procedure and go to control data – and then replace the condition type that was copied and renamed earlier with the new condition type created. Save and exit.

In order for the new pricing procedure to come into effect – document pricing procedure and customer pricing procedure have to be defined and assigned to the relevant sales areas under ‘define pricing procedure determination’.

Note: condition type is assigned in two places during this whole process –

Maintain pricing procedures – assigned to the relevant pricing procedure in control data.

Define pricing procedure determination – assigned to sales area with pricing procedure.

The basic difference is – the first case is the actual assignment of condition type to pricing procedure, which is mandatory in order for a pricing procedure to be effective. On the other hand the second case is the proposed condition type for fast entry which is directly proposed during the sales order processing at the item level. The second case has nothing to do with the functionality of the pricing procedure.

The following is the sequence when customizing for determining a pricing procedure –

Put the fields you need into the field catalog.

Create the condition tables.

Create the access sequence.

Assign the condition tables to the access sequence.

Create the condition type.

Assign the access sequence to the condition types.

Create the required determination procedure and assign the condition types to it.

Define the customer and document pricing procedures.

Assign the determination procedure and condition type to the relevant sales area, and to a combination of document pricing procedure and customer pricing procedure.

Lastly, create the necessary condition records (VK11).

Adding fields to the field catalog –

When creating a condition table one may need additional fields besides what exists in the standard field catalog. As an instance - if a business no longer wants to have a sales discount based on sales organization, customer group and material and instead it has decided to calculate the sales discount based on sales org, customer group and material group.

In this case a new condition table is created by selecting the required fields from the field catalog while creating the condition table. But in any case if the required field doesn’t exist in the field catalog, then the required field can be added to the field catalog from the ‘allowed fields’. It is also possible to add a new field to the list of ‘allowed fields’.

Pricing –

Menu path – IMG – sales & distribution – basic functions – pricing – pricing control – define & assign pricing procedures – maintain pricing procedures (V/08).

A pricing procedure consists of a list of condition types in a defined order, such as price, less discount, plus tax. Some controls exist in the pricing procedure. For example you can specify that a condition type is mandatory; it must have an entry defined either automatically or entered manually.

The pricing procedure is also used in account determination. This determines the general ledge (GL) accounts to which the prices, discounts and taxes must be posted. The condition types in the pricing procedure are linked to an account key. This key in turn is linked to the GL Accounts. This shows the integration between the pricing in the invoice and the financial accounting module.

It is suggested to use to the SAP standard pricing procedure RVAA01 to copy and make necessary changes according to the requirement while configuring a pricing procedure. The following is the control data of the pricing procedure in detail –

1. Step – this indicates the number of steps in the procedure. The first condition type should be step 10; the second condition type should be step 20 and so on. It is possible to number the steps in the intervals of 1, but it is not suggestible as it may cause inconvenience when changing the procedure in future.

2. Condition counter – this is used to show a second mini-step within an actual step. For example, you may have assigned all you freight surcharges to step 100. However there may be three condition types, each representing a different freight surcharge. Thus you can assign a freight condition type to step 100, counter 1; another to step 100, counter 2; another to step 100, counter 3 and so on.

3. Condition type – this is the backbone of the pricing procedure. The condition type is the link from the access sequence all the way to the actual condition record. When you enter a condition type, the description field is automatically filled in with the description from the condition type.

Note: A description without a condition type can be entered for sub-total or total or net price in between the condition types in the control data.

4. From & To columns – these are used in two circumstances –

a) To define the range for a sub-total – for example, if you want to add up all the condition types from step 10 to step 50; you would enter 10 and 50 in the From and To columns respectively.

b) To define the basis for a calculation – for example, if a discount is defined as a percentage, you need to indicate which step must be used as the basis for the calculation. If the calculation must be performed from step 100, you would enter 100 in the From field.

5. Conditions determined manually – indicates if the condition type it is assigned to is allowed to be processed automatically or only manually. Conditions, that are given this indicator in the pricing procedure, are only included in determination (price determination, output determination, and batch determination) either if they are entered manually, for example, on the condition overview screen in Pricing or if they are transferred from an external process, such as costing.

6. (Note: when assigning the pricing procedure to the sales documents, a condition type is also assigned to it; reason being that the condition type assigned to the sales document here is displayed in the sales document item level which can be manually changed - provided it is indicated while configuring the control data - conditions determined manually). This feature is more often used in case of costing and output determination.

7. Condition is Mandatory – the mandatory column identifies those condition types that are mandatory in the pricing procedure. Mandatory condition types are the sales price or the cost price. If the mandatory condition is missing in the pricing procedure, the system has an error in pricing and the respective sales order cannot be processed.

8. Condition is used for statistics - This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value). This can be used to represent the cost price of the material sold.

9. Print – determines which descriptions and associated values assigned to a step are printed on a document, such as order confirmation.

10. Condition Subtotal - 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. These subtotals are used in other areas of the system such as in logistics information system. It is recommended that you assign the subtotal field 4 to the total value in the pricing procedure for Freight.

11. Requirement – this column is used to assign a requirement to the condition type. This requirement can then be used to exclude the system from accessing the condition type and trying to determine a value. This can be used to specify that the condition type, a discount, should only be accessed if the customer has a low risk credit group.

12. Alternative calculation type - specifies that the system is to use the formula represented in this column as an alternative in finding the value of the condition type, rather than by using the standard condition technique. This can be used to calculate complex tax scenarios. This field is used in obtaining values such as “Net Price”, ‘Profit Margin’ – where there wouldn’t be any access sequence to get the required value. Instead the system calculates net value using the existing amounts and the alternative calculation types. (formula: profit margin = net value – cost price)

13. 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. For example, one can specify a formula that uses a subtotal, such as 4, from the subtotal field; modify it slightly, such as dividing it by 2, and then using the resultant value as a base value for the condition type.

14. Account key - Key that identifies different types of G/L accounts. The account key enables the system to post amounts to certain types of revenue account. For example, the system can post freight charges (generated by the freight pricing condition) to the relevant freight revenue account.

15. Account key – accruals/provisions - Key which identifies various types of G/L accounts for accruals or provisions. With the aid of the account key, the system can post amounts to certain types of accruals accounts. For example, rebate accruals which are calculated from pricing conditions can be posted to the corresponding account for rebate accruals.

Note: when using a condition type using condition class B, prices, the system can only use one price per line item. Thus, should the system have a second price in the pricing procedure, it will invalidate all the previous pricing conditions. It does not benefit from having more than one price in the pricing procedure.

The following are a few important points to remember while configuring pricing procedure –

The discounts we give to the customer should not be deducted from (Gross value + Extra charges), instead all the discounts must be added together and the total discount value should be deducted from the Gross value alone before adding any extra charges such as freight.

The manual condition types most commonly used are RB00 – Discount (value) & HD00 – freight.

The most important part is the allocation of condition types to respective GL accounts –

• Pricing condition types – ERL

• Discount condition types – ERS

• Freight – ERF

• Output tax – MWS

The system automatically uses condition type VPRS as the condition to represent cost. Do not forget to mark statistics field and the requirement field (4) in configuring pricing procedure.

The rebate condition types are determined if a valid rebate agreement for the material has been created for the customer. SAP will use the rebate agreement to calculate an expected amount that this sale will contribute to the customer’s rebate. Accruals can be posted to the GL accounts. In this case the accrual account key ERU must be setup.

Rebate condition types must be defined as expense reimbursements in the condition type record, so that they are not included in the net value.

Pricing Procedure Determination –

The pricing procedure is allocated to the sales document or billing document by a determination rule, similar to other determination rules. The pricing procedure determination is based on the customer master record, the sales document and the sales area.

Pricing Procedure = Sales Area + Customer Pricing Procedure + Document Pricing Procedure

Reward points pls.

Regards,

Govind.

Former Member
0 Kudos

Hi Senthil,

Also follow this link where people had contributed for important sd topics

<u>https://www.sdn.sap.com/irj/sdn/wiki</u>

Award points if it adds information.

Thanks

Mohan

Former Member
0 Kudos

Hi,

hi,

In the pricing procedure you specify the condition types which are to be used in pricing. At the same time, you define the sequence in which the condition types are to be brought into play.

Which pricing procedure is valid for a business transaction depends on the following criteria:

customer

sales document type

sales area

You create PP in spro > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define and Assign Pricing Procedures > Maintain Pricing Procedures

You can't attach PP to specific plant. Pricing Procedure is determined thru trx OVKK. The defining parameters for pricing procedure determination are:

1. SalesOrg

2. Distribution Channel

3. Division

4. Document Procedure (defined in Sales doc\Billing doc maintenance)

5. Pricing procedure assigned to customer (defined in customer master)

Reg pricing procedure.

1. Use transaction code v/07 to create a access sequence and assign tables based on which you want to carry on

pricing as accesses.

2. Use transaction code v/06 to define condition type. It can be for base price, discount, freight etc.,

(Do assign relevant access sequence)

3. Use transaction code v/08 to define pricing procedure.

4. Assign this to your relevant sales area+ dpp+cupp.

While specifying requirement, we can give reqt no.22 which specifies that plant has to be set. This is generally done for output taxes since output taxes depend upon the delivering plant. But directly there is no assignment between plant and pricing procedure.

Award points if it adds information.

Thanks

Mohan