topic Re: Pricing routine in Application Development and Automation Discussions

Pricing routine

Former Member — Thu, 02 Aug 2007 09:19:34 GMT

Hi,

I have developed a pricing routine.

I need to have billing plan dates.

VA42~~-> select any line item~~-. billing plan tab.

To get these dates i m using FPLT table.

But when i do any change in contract and billing plan changes on screen.

the corresponding change in table takes place only after saving the contract.

Is there any structure or can way by which i can use the billing plan date from screen in the pricing routine?

Re: Pricing routine

Former Member — Thu, 02 Aug 2007 09:24:32 GMT

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.

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

It is assumed that document pricing procedure, customer pricing procedure, ... are in place.

For more information, please check this document.

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/SDBFPR/SDBFPR.pdf

http://www.sap-img.com/sap-sd/creating-new-pricing-procedure.htm

Regards

Re: Pricing routine

Former Member — Thu, 02 Aug 2007 10:21:08 GMT

Thanks for quick reply.

But My concern is not related to pricing procedure.

Its with the pricing routine.

I have to use billing plan dates inside the routine.

And i don't know what structure to be use?

Re: Pricing routine

Former Member — Thu, 02 Aug 2007 10:24:05 GMT

Hi,

<b>VOFM pricing routines</b>, requirement routines are used in SD and MM.

data transfer routines are specific to SD.

VOFM is a transaction where form routines are created.

like user-exits, form routines are used to do extra functionality. we have different routines like condition routines, data routines etc..

once we define the routines we will assign them to standard flow in VTAA transaction(we have header, data categories here we will assign our routine based on our requirement).

for a real-time scenario say when you are creating a sales order from a contract, and you need to check the contract..say for a contract with order type 'ZTYP' you should not allow creating the sales order then you can do this check with the help of routine..

or when creating a sales order you need to validate few fields say a quantity field less than 10 should not be allowed, or if you need to default some values in the fields you can use these routines.

read OSS #: 327220

Check the below link:

Look at the below PDF file ..

www.saptechsolutions.com/pdf/VOFMCopyRequirementRoutines.pdf

http://www.sap-img.com/sap-sd/creating-new-pricing-procedure.htm

Look at the below links also to create the pricing Routines in VOFm

http://www.sapprofessionals.org/?q=vofm_requirement_and_formulas_for_sap_sd_pricing

Regards