cancel
Showing results for 
Search instead for 
Did you mean: 

Pricing condition records should not be picked up

Former Member
0 Kudos

Hi,

I have configured a scenario for Supplementary Invoice for which I created a new sales order type. The requirement is such that this order type should not pick the pricing condition records that have been created in VK11. Please suggest how can this be configured.

Do I have to use any Userexits, if so which one?

Regards,

Abhishek

Accepted Solutions (1)

Accepted Solutions (1)

Lakshmipathi
Active Contributor
0 Kudos

Dear Abhishek

As you would be aware, all condition types in a pricing procedure will be determined based on the combination of sales area, document pricing procedure and customer pricing procedure.

Since your requirement is that for one particular sale order type, PR00 should not flow, two options are there.

- have a new document pricing procedure in VOV8, create a new pricing procedure and assign this new pricing procedure in OVKK

- apply User exits in the program MV45AFZZ - USEREXIT_PRICING_PREPARE_TKOMP

thanks

G. Lakshmipathi

Answers (3)

Answers (3)

Former Member
0 Kudos

If possible, add Sales Doc Field VBAK-AUART in your access sequence for PR00. Depending on your scenario you can add field or create new table at the TOP; mark it 'Exclusive' . Then by maintaining the Record as ZERO for PR00.

Alternatevely, you can write your requirement for PR00 in Pricing Procedure.

Regards

Arun

Former Member
0 Kudos

Since PR00 is a mandatory Pricing Condition, system would save the order as incomplete, if PR00 is created with Zero value.

Other possible way to address this requirement is:

Create an Alternate Calculation Type and assign it to all the Price Condition types in your Relevant Pricing Procedure..

In the alt calculation type formula maintain the code as if Sales document type is "'So and So" then KWERT equals to ZERO and KWART equals Zero.

Also add the Document type field AUART to allowed fields in the Pricing Field Catalog, if its not present already.

Thanks

Sai

Former Member
0 Kudos

As mentioned by you, you have created a new Sales Order Type, you can create a new document pricing procedure, based on which you can determine a new pricing procedure.

To configure new Document Pricing Procedure:

IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Define Document Pricing Procedure. (Maintain the new Document Pricing Procedure in new Sales Order Type)

Maintain a new Pricing Procedure, maintaining the Condition Types as manual. Maintain the determination of Pricing Procedure appropriately.

Pricing Procedure Determination:

In SD, Pricing Procedure is determined (T.Code: OVKK) 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.

Pricing Procedure Configuration:

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

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

Former Member
0 Kudos

if u doese nt want to get picked then better do not maintain the cnd recrds and keep all the cnd types manual in the pri proc.why to go for user exits?????

Former Member
0 Kudos

As I had mentioned earlier the requirement is such that the condition records should not be picked only for one particular sales order type. For all the other sales order types the system should pick the condition records.

Former Member
0 Kudos

you can do it like this

define an incompletion procedure in such a way that that sales order should take if the document is incomplete, i mean if you delete the line item prices.

please correct me if i am wrong . it is just an idea!!!!!!:)

Former Member
0 Kudos

Hi,

Assign different document pricing procedure that sales document type.

In pricing procedure determination assign different pricing procedure for that combination.

Regards,

Chandra