prestep in pricing???

[Former Member]

hello gurus...

what are prestep in pricing to enhance pricing performance.

regards

vishal

[former_member184771]

This message was moderated.

[Former Member]

This message was moderated.

[Former Member]

According to me, Prestep for configuring Pricing Procedure is the detail from Client regarding the calculation steps in Pricing. It is recommended to take the calculation steps from Client in Excel Sheet, along with logic for arriving at Final Price.

Pricing Procedure can be configured in isolation. To get accurate Pricing Procedure at correct place, the Pricing determination is done based on Sales Area + Customer Pricing Procedure + Document Pricing Procedure.

Write-up on 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.

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.

Regards,

Rajesh Banka

[safeer_rahman2]

Hi Vishal...

Before configuring the pricing procedure you are supposed to maintain the following...

1.Maintain the Customer pricing procedure in Customer master though XD01 or XD02

2.Maintain Document pricing procedure in Doc type through VOV8

3.Create tables and assign them to the access sequence though V/07.

4.Assign the access sequence to the Conditon types through V/06

5.Maintain condition records for the table through VK11 or VK12

6.Create the Pricing procedure with conditon types V/08

7.Assign the Pricing procedure to the Custoemr pricing procedure , document pricing procedure and the Sales area...

This is the pre-step in pricing...

Hope this helps... Kindly reward if you find this informative...

Thanks,

Safeer Rahman

[Former Member]

Pricing pre-step allows you to make checks using header data and thereby avoid the system making multiple checks at item level.

For example look at requirement routine 3 - Foreign currency doc(LV61A003). This is checking only header fields (komk-waerk and komk-hwaer) and so the code is put in the pre-step section kobev_003 as well as the normal section kobed_003. It helps because the pre-step check is done earlier and less frequently and so the condition can be excluded earlier and thus performance is better.

However, for requirement routine 2 - Item with pricing. The check is at item level (komp) and so the code can only be executed at item level in the kobed section.

Now look at routine 9 - qualif for cash discount. In this case some of the checks are at header level and some at item level. In the kobev section only header checks are included, but in the kobed section header and item are included.

So if you can make checks at header level, put them in the kobev section to improve performance.

Similarly it may be beneficial to set up price condition optimisation at header level (table T682V). Suppose you have a pricing procedure where you have two main price conditions ZP01 and ZP02. These are maintained at customer/material level, but as a business practice you would only use either ZP01 or ZP02 for a given customer for all the materials that the customer purchases.

In that case you could optimise the access using field Customer. It means the system will first read the table using only customer number to see if there are any entries at all and only if some are found will it read again(later) using the full key.

If the header read fails, the condition table won't be read at item level for that access step. So it means in this case after finding no ZP01 records at all for a customer, then for all other items being priced in the same document for the same customer it will no longer read the ZP01 access and thus avoid unnecessary table reads.

[claudia_neudeck]

Hello,

the prestep in pricing is the prgram LV61AA12.

This program is triggered in everey time if a pricing is running.

I hope that the information are helpful.

Regards

Claudia

[Former Member]

Hi ,

For enhansing the priing related performance consider the following steps:

(1) Maintain proper access sequence in the correct order.

(2) U can go for Buffering if it is a big orginization with frequent pricing determoination.

(3) Ensure to make use of Exclusion indicator to save time.

(4) Dont assign Access sequence for manual conditions.

(5) Make use of requirnments for condition types higher up in th pricing proc so that time is not wasted unnecessarly on frtcting condition records which would not be used .

There are few of the most commonly used techniques for saving time n enhansing the pricing performance. Reward accordingly.

Cheerzz..

Subbzz..

[Former Member]

Hi,

1.U should make sure that which fields should be used in the condition tables

2.u have to anlyse ur requirements and based on that u should decide which condition types to be used.

3.as per the requirements u may have to use new pricing procedures instead of standard one..

Regards..

Yogi..

[Former Member]

Hi Vishal,

There are many points which we have to consider before configuring Pricing, like :

1.Document Pricing Procedure

2.Customer Pricing Procedure

3.Whether there is any requirement of Common Distribution Channel / Division for Pricing.

4.And Proper categorization of all Condition Type for the respective pricing procedure.

Hope your query has been answered.

Cheers !!!

Imzo