Pricing Procedure

[Former Member]

Hello all,

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

[Former Member · Accepted solution]

Hello friend,

Make use of transaction code V/08 to define pricing procedure.

And there is no way to attach a plant to a pricing procedure as per my knowledge. And I never find such requirement where we need to do that.

However if any requirement we have related to a plant where out records are totally dependent to plant. We can configure it with condition type in pricing procedure.

For that we can use requirement in the pricing procedure. You can give requirement no.10 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.

If not satisfied please tell me your scenario or you can send it to rajansinh@gmail.com

[Former Member]

Hi to All,

First You cant link the pricing procedure to plant.

Second, as our friend told creation of special sales document types for that plant is not possible. why because if the material is not available in that we have to get it from another plant in that situation what pricing procedure should consider?

The delivering plant will come to sales order from either CMIR, CMR or MMR

I Will give one tip pls work out on that.

While creating condition table take plant as one key field.

While you are maintaining condition record it is plant specific.

And also you maintain copy controls Pricing type will be " Carry out new pricing".

So when ever you change the plant also the price will be change.

I think this will work for u.

Sivalingeswara Rao.B

[Former Member]

<b>Hi,</b>

The transaction code for creating a new pricing procedure is V/08. You have to use the condition technique for creating the pricing procedure:

1. <b>V/03</b> - Create condition table.

2<b>. V/07</b> - create access sequence and assign the condition table to it.

3.<b> V/06</b> - create the conditin type and assign the access sequence to it.

4. <b>V/08</b> - create pricing procedure and arrange the condition types in a proper sequence.

5. <b>OVKK</b> - pricing procedure determination. Here you assign the pricing procedure to the combination of the sales area, document pricing procedure, customer pricing procedure. Create a new DPP in <b>OVKI</b> for the plant and use it above for the pricing procedure determination.

6. <b>VK11</b> - maintain the condition records for the condition types that have been marked as mandatory in the pricing procedure.

<b>Assigning the pricing procedure to the plant:</b>

As such the pricing procedure cannot be directly assigned to the plant. Do one thing, create a new sales document type specially for the required plant using transaction code <b>VOV8</b>. Assign the document pricing procedure to the sales document type just created using transaction code <b>OVKJ</b>. Now in <b>VA01</b> whenever you create the sales order for the material manufactured in the required plant the system will automatcally propose the required pricing procedure becuase of the sales document type..

Reward points if solution helps.

Regards,

Allabaqsh G. Patil

[Former Member]

hi,

In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. 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.

In SD, the steps to configure Pricing procedure are as under:

Step 1:

Condition table: 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: 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: 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: 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: 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.

5. Condition record: 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.

<b>Reward useful points</b>

Regards,

siva

[Former Member]

Hi,

For Defining and assigning pricing procedure t code is V/08. this pricing procedure we assign to the combination if Sales area, Document pricing procedure and customer pricing procedure. but not for the plant.

generally we did not assign the pricing procedure to the plant . i think that setting is not there in SAP.

rewards if Helpfull..

Regards,

Praveen Kumar.D

[Former Member]

Hi,

U can create a pricing procedure in T code V/08.

U can also work on pricing procedure in VOK0.

How can be pricing procedure is assigned to Plant?

Praveen.

[Former Member]

<b>V/08</b>

HI

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)

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.

Message was edited by:

SHESAGIRI.G

[Former Member]

sheshagiri, requirement no 22 is saying its for inter-company, its different. Please rechek it.