pricing simulation

[#1]

hello, friends.

need your help... i understand that there is no standard transaction in SD to simulate pricing (other than using a dummy sales order). however, we have pricing reports using V/LD so that we could list condition types based on access sequence.

we have a requirement to list simulated pricing as it would appear in the sales order, so a possible format could be:

PR00 material price

+ surcharges (e.g. KF00)

- discounts (e.g., K004, K005, K007, etc.)

Net total Price (with or without taxes)

we could get the condition type details from tables such as KONP, KONH, etc... but if a condition type such as PR00 was created for a material using several combination keys (e.g. customer/material, material with release status, etc...)or different sales areas, and all are valid at the same time, could anyone suggest how we could determine which access sequence/exclusivity should apply and from which table the data could be retrieved?

many thanks in advance...

[Former Member · Accepted solution]

If valid Condition record are maintained for multiple combination for Condition Type PR00, the moment the first valid Condition record is found, it will not look for other records, even if it is maintained. So, by default the first valid ccondition record should be considered and not multiple.

Regards,

Rajesh Banka

[Former Member · Accepted solution]

thank you, rajesh. i also understand the sequence of the accesses as relevant for the price determination, together with the exclusivity settings for each access.

but where and when is the selection of the access done? i would think it is during sales order processing, and is there a specific sub-routine for price determination during sales order processing?

thanks again...

[Former Member · Accepted solution]

You have mentioned it correctly that it is done during sales order processing. Pricing is determined based on condition technique.

Regards,

Rajesh Banka

[Former Member]

used both helpful approaches.

many thanks.

[former_member217082]

Hi Jonathan

If you have a condition type with several key combination's then system will search from the first condition table assigned to the access sequence and it will keep on searching till the last condition table. and it will pick the last record which has been maintained .

Secondly , if any exclusive indicator is maintained in the access sequence then it wont search for the next key combination but it will stop searching and it will pick the record with the existing key combination

So if you create the sales order then it will search for the sales area on which it has been created and material record will picked up based on that record only , because the material will also be determined on the sales area on which the customer is also there .

Regards

Srinath

[Former Member]

thank you, sri nath. yes, i agree that the system searches through the access sequence. i guess i need to explain my objective.

friends, my intention is to replicate the way price is determined during sales order processing, and show the results in a tabular format, so that the user can see the theoretical net prices for a material or group of materials, given certain combinations, on a certain pricing date. as such, could anyone help me determine which program/sub-routine does the price determination?

many thanks!!!

[Former Member]

This is not available in Standard SAP. It will require a development, as SD does not has any price simulator.

In the Development key fields will be as under:

Sales Document Type

Sales Area

Customer

Material

Regards,

Rajesh Banka

[Former Member]

Hi Jonathan,

You may use SAP standard price catalogues for simulating pricing for a customer (transaction code is VPRE). However the out put would be in idoc format, you may need to develop a customized report to extract data from these idocs if you need report format (using tables EDIDC and EDIDD). Please note that pricing simulation is based on invoice, hence if doc. pricing procedure is same for order and invoice, you will get best results.

Hope that helps.

Thanks

Murali

[Former Member]

Hi Jonathan,

We had a similar requirement. We built a custom report around function module 'PRICING'. This function module can simulate what the order process goes through as long as you pass in the correct information that influences your price calculation. Basically the input comm_head_I and comm_item_i correspond with KOMK and KOMP pricing communication structures. You must pass in all relevant data that can influence price including which pricing procedure to use in KALSM. You can test this by going into SE37 and executing a single test by manually adding the data that influences your price.

If you are not clear what data is required in your pricing call, set a break point in MV45AFZZ move fields to komk and komp then execute an order. You can review the data in the communication structures that is required. Hope this helps.

Regards,

Matt

[Former Member]

thanks, my friends.

i will try all of your ideas and i will update this thread.

my warmest regards...