cancel
Showing results for 
Search instead for 
Did you mean: 

No pricing procedure could be determined

Former Member
0 Kudos

Hi

I have created a internal customer . When i am trying to create a sales order for this customer its giving a error "No pricing procedure could be determined". I have maintained pricing condition record for this customer and material in VK11.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member

Hi,

Just check ur entry in thye tcode OVKK(Sales area and customer pricing procedure indicator in CMR and document pricing procedure indicator in document type(vov8 tcode)).

Regards,

kishore.

Answers (5)

Answers (5)

ozgursaglam
Explorer
0 Kudos

Hello,

If the customizing is not missing, check the requirement(kobed) field in the calculation schema.

Former Member
0 Kudos

Hi Friend,

Pricing is determined by combination of Sales Organisation, Distribution Channel, Division, Customer Pricing Procedure and Document Pricing Procedure.

First of all there are some few criterial needs to be entered for pricing

Please follow the same below----

Reasons For Making Any Pricing Procedure in SAP

Pricing in SD (in detail)

For creating a condition Table:

1) There are almost all the regularly used Conditon Table predefined in the system from 001 to 500.

See what best you can use the Standard Tables to avoid further errors.

2) In case you should define the new condtion Table,

a) Goto TCode: V/03

b) Give a Table any number from 501-999

Press execute and reach to next screen.

c) Check up whether the field you are looking is already added in Field catalogue.

d) Double click on the fields you want to make a Table..one by one. Note that the sequence here is important in higher hierarchical to lower..

Eample : Sales Org, DC, Division, Customer and then Material etc..,

e) After selecting, click on the Techincal View buttin (redone) and reach to next screen.

7) Check which key should be in header and which key should be footer. Use check and uncheck functionalities there..

Once you are through with all the above steps ..click on generate button.

Check the Table is generated or not.

You can check it at V/04 or V/05 or in SE11.

Can Sales Order and Billing Have Different Pricing

Yes, can have 2 different pricing procedures

1. One for Sales Order

2. Another at the Billing

Let us take an example:

Generally in the Pharma industry this procedure is adopted becuase all the goods are batch price based.

1. In the Pharma Industry whenever the goods are manufactured it will done in a batch to keep track and price is fixed, I mean there will be a Batch Master which has a certain price fixed for it. This Batch Master will have certain number of batches . These batches will have the number series generated wither by internal or external generation depending upon the client requirement

2. So till all the batches are produced as per that particular Batch Master will have the same price. Like that there will n number of batches will different different prices

3. So when you are preapring Sales Order you be only putting the tenative price for the goods that are sold

4. Then at the time of delivery we will be picking up the goods from different batches basing on the required delivery quantity and finally we do the PGI.

5. This is called Delivery Based Pricing becuase your price for the goods will be determined at the time of the delivery as the goods picked up from the different batches which have different prices. ( Mind it there will very less difference in the prices).

6. So at the time of Billing the Pricing Procedure behaves differently depending upon the differnent batches that are picked basing on the batch determination.

7. So the prices which are detemined from different batches will be the actual prices at which the goods are billed to the customer along with other condition that are applied as required.

Reasons For Making Any Pricing Procedure in SAP

1. Why we are maintaining separate pricing procedure for inter company sales and business processs.

2. What is the different between standard and inter company pricing procedure and what type condition type we are using in this intercompany.

There are two simple reasons for making any Pricing Procedure in SAP SD Modules.

1) Business Reason. What are the pricing aspects or strategies you want to apply for the client requirement in order to sell their

goods or render services, is all about the reason for various pricing procedures.

Eg: Domestic sales pricing procedure,

- Export Pricing Procedure,

- A rebate pricing procedure or

- A High Discount oriented pricing Procedures.

- A repair pricing procedures.

You have your own conditions intended to few transactions only. Put all this conditions as a set defining your own Procedures. It may even include special requirements and formulas applied for such Pricing Procedures.

2) A special pricing procedures, in order to facilitate added functionalities of SAP pricing architecture, we must define new

pricing procedure. SAP Standard programmes checks these special Indicators in-order to do some required functions.

As a example 1, you need to have a Pricing procedure for condition supplement inorder to use the condition supplements. The condition supplement pricing procedure must be given in the condition type definitions (v/06) of the Pricing Condition where you need to supplement, without which SAP SD Condtion Supplements functionality doesnt work.

As a example 2, you need to have a Pricing procedure for Inter Company Billing Conditions(IV01 & IV02) inorder to be active for Inter Company Billing specific transactions. Thus make sure that, the procedure wouldnot apply for non-Inter company transactions.

Eg: KA0000 for Condition Supplement for KA00

- PR0000 for Condition Supplement for PR00

- ICAA01 for Inter-Company Billing

Here I would like to remind about a important field in pricing.

In V/08 of defining a new Pricing Procedure, in main screen, you have a field called TSPP (Transaction Specific Pricing Procedure). This has to be ticked on for Intercompany Billings.

The SAP help reads for this field as Under:

Transaction-specific pricing procedure

Pricing procedure transaction-specific indicator

Before Release 4.0A, no special pricing procedures were used for intercompany billing and rebate credit memos, programs were just set accordingly to deal with these situations. As of Release 4.0A you are offered greater flexibility in the form of the option to define special pricing procedures for intercompany billing and rebate credit memos. For reasons of future compatability, you will still be able to use the old program specifications. For this reason, you must set this indicator if you want to create a special pricing procedure. This is to prevent the program settings being used.

This indicator is also used as of Release 4.0A to redetermine the condition class and the statistical condition indicator when copying from a reference document.

Example:

You copy prices from a shipment document to the billing document. The prices should lead to a surcharge in the billing document. This is guaranteed by the redetermination of the condition class in the pricing procedure.

Same case with Standard Pricing procedure or Inter Company Pricing Procedure.

This configuration is done when user request for new pricing condition type other than the standard ones provided by the system.

Screen to tcode VA01 u2013 Create New Sales Order for customers

- Double Click the Item

- Then Click the Conditions Tabstrips

Define Condition types

V/05 - Condition Table for V/07

e.g. a business may no longer wants to have a sales discount based on the sales organization, customer group, and material, but decided that the discount should be based on the sales organization, customer group and material group.

V/06 u2013 Create new condition types by copying a similar conditions type and changing it according to your needs.

Double click on the condition type to change the control options

V/07 u2013 Access Sequences for condition type

V/08 u2013 Pricing Procedures for condition types.

The pricing procedure is also used in the account determination. This determines the general ledger accounts to which prices, discounts and taxes must be posted.

Click on the Pricing Procedures e.g. PR0000 u2013 Condition Supplements for PR00

Click Control u2013 e.g. Tick Mdt if you want the condition type to be mandatory

OV34 u2013 Define account key

OV35 - Assign account key

Actky u2013 Revenue account

Accrls u2013 Accruals account

OVKK u2013 Determine which Pricing Procedures to use for which Condition Type.

Price with additional decimals

You can add additional decimals for a currency through a work around method.

Set up a currency letu2019s say instead of USD call it US$ ( OY03 ) and define the number of decimal places ( OY04 ) to be 3 or more depending on your requirement.

Maintain the exchange rate for between US$ and USD to be 1 to 1 ( OBBS and OB08 ).

Create pricing condition records for those customers requiring 3 decimal places using Current US$ instead of USD.

That will give you 3 decimal places for your prices. However, one thing you will have to watch out for is rounding.

You can try transaction OB90, define rounding rule for currency. Here you define the rounding rule for your customeru2019s currency.

Control Pricing Conditions based on Order Type

4.6x

e.g. You create an order type ZP00 for QT u2013 Quotation and does not wish it to be used in OR u2013 Standard Order.

Follows this steps :-

IMG u2013 Sales and Distribution -> Basic Functions -> Pricing Control -> Define and Assign Pricing Procedures

Define document pricing procedure

e.g. Q u2013 Quotation

Assign document pricing procedures to order types

e.g. Assign Q to Order Type QT u2013 Quotation

Maintain pricing procedures

e.g. Copy Standard Pricing Procedure to e.g. ZQT (all the pricing conditions list will only be allowed in order type QT u2013 Quotation

Define Pricing Procedure Determination

e.g. Copy and assign Document Pricing Q and Pricing Procedure ZQT accordingly

Users will receive Message no. V1 206 u201CCondition ZP00 is missing in pricing procedure A V ZQTu201C.

Create a New Pricing Conditions Key Combination

4.6x

In VK12, click the Key Combination button. You can see a list of available key combination for your price master.

Now, let create a new key combination e.g. Customer + Sales Document + Material

IMG u2013 Sales and Distribution -> Basic Functions -> Pricing Control -> Define Condition Tables -> Create condition tables

e.g. 900

Selected fields

Sales organization

Distribution channel

Customer

Sales document

Material

Click Generate to activate it

IMG u2013 Sales and Distribution -> Basic Functions -> Pricing Control -> Define Condition Tables -> Defince Access Sequences -> Maintain Access Sequences

Select PR00 u2013 Price

Click Accesses

Click New entries

AcNo Tab Exclusive

50 90 X u2013 Tick

Save your entries

IMG u2013 Sales and Distribution -> Basic Functions -> Pricing Control -> Define Condition Tables -> Defince Access Sequences -> Optimize accesses

Copy an existing PR00 and substitute the AcNo with 50

Finally, goto VK12 and key in the new price master for PR00.

Next, goto VA02 and test out the material. If it didnu2019t work check the pricing date in the header details. Is the pricing date within the validity period?

Pricing Release Procedures

4.6x

Define Processing Status u2013 SM30 -> V_T686E

You are free to design your own processing status flow.

e.g. from 01 -> 02 or

from 01 -> 02 -> 03

To convert the old Pricing Condition with the release status use program SD_MOVE_A004_TO_A304.

For the standard tables, the following pairs of condition tables are intended to be used:

u2018oldu2019 <u2013> u2018newu2019 VAKEY fields

A004 <u2013> A304 VKORG + VTWEG + MATNR

A005 <u2013> A305 VKORG + VTWEG + KUNNR + MATNR

A006 <u2013> A306 VKORG + VTWEG + PLTYP + WAERK + MATNR

A007 <u2013> A307 VKORG + VTWEG + (SPART) + KUNNR

For example, if you are using A005 u2013> A305, you have to copy the program to ZSD_MOVE_A005_TO_A305 and amend the program Source and Target table.

First test run by ticking both option. If you confirm that there are no errors, then run by unticking both options.

Be careful while executing the conversion program as it can erase all your existing pricing condition data.

Once the conversion is completed, you can activate the Customer/Material with release status :-

IMG -> Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control -> Define Access Sequences -> Maintain Access Sequences

In VK12, you will be able to choose the new Customer/Material with the release status column per material.

Delivery Pricing Conditions

4.6x

Configure the pricing procedure at delivery with the required condition type to determine freight. Also have the copying control from delivery to billing at item level with Price source as D for Delivery. While you execute billing you would get the prices from the sales order as well as from deliveries.

If you were to look at the pricing procedure RVAA01 you will see there was a section dedicated to the various freight charges. Normally, I would use one of the available condition types and create a condition master based on the Incoterms

Former Member
0 Kudos

Hi

pricing procedure is determined based on

(pricing procedure in sales document type) + (sales org) + ( dist channl) + ( division) + (pricing

procedure in sold to party master record) .

so first note the pricing procedure in sales doc type you used

then note the pricing procedure in customermaster(sold to) that you have created

also note Salesorg Distchannel and Division for that customer

now goto SPRO->sales and distribution->Basic function->Pricing->pricingcontrol->Define and assign pricing procedure and select maintain pricing procedure.

here u find list of pricing procedures note any one of pricing procedure that you want to be determined in sales order

Finally go to OVKK and maintain a entry for all the things noted above and save it.

Now when u create a order for that customer u will get that Pricing procedure determined

Thanks

Rathan

Former Member
0 Kudos

Hi,

First define the customer pricing procedure.And assign it to your customer master.

The path is:

SPRO>Sales and Distribution>Basic functions>Pricing>Pricing control.Define and assign pricing procedures.

Select define customer pricing procedure.

Here you can define a new one.

If there are any entries then you can use them if you want.

Else define a new one.

Goto XD02.Enter your customer number and Sales area.Goto Sales tab.

Enter the pricng procedure there for the field "Cust.pric.proc." which is in Pricing/statistics tab.

Similarly define a new document pricing procedure.Or you can use the existing one.Consider we are using an existing one.Then check what is the document pricing procedure for your order type.

The path is:

SPRO>Sales and Distribution>Basic functions>Pricing>Pricing control.Define and assign pricing procedures.

Select "Assign document pricing procedures to order types".

Note it down.

SPRO>Sales and Distribution>Basic functions>Pricing>Pricing control.Define and assign pricing procedures.

Now go to "Define Pricing Procedure Determination".Or the T.Code is OVKK.

Maintain the values you have defined there.Save.

Now try.

Regards,

Krishna.

Former Member
0 Kudos

Hi,

Pricing procedure determined from the following combination:

i.e. Sales Area (sales Organization + Distribution Channel + Division) + Document Pricing Procedure + Customer Pricing Procedure.

Document pricing procedure we maintained in the Sales document types (Tr.code VOv8)

for example - Standard document pricing procedure is 'A'

Customer pricing procedure we maintain in Customer Master data (XD01)

for example - Standard document pricing procedure is '1'

So you can determine the pricing procedure by going to transaction code OVKK.

I think this information will be helpful to you.

Good Luck

Regards

Ashis

Former Member
0 Kudos

Hi There,

Pricing procedure determined by the combinatioon of Sales Area + Custmer Pricing Procedure ( frm Cust Master) + document pricing procedure ( from documnet type) , This we assigned in OVKK.

Please check the setting in OVKK.

Thanks,

Raja