cancel
Showing results for 
Search instead for 
Did you mean: 

Pricing Issue

Former Member
0 Kudos

Hi All,

I have created a new item category copying the item category TAN. While creating the sales order I am manually changing this item category. It is not picking up some of the condition types. There is no requirement for these condition types. When I carry out new pricing (in VA02) these conditions are picked up.

What could be the reason.

Thanks.

Regards,

Varada

Message was edited by:

VARADARAJAN SRINIVASAN

Accepted Solutions (1)

Accepted Solutions (1)

rmazzali
Active Contributor
0 Kudos

maybe you need to trigger the pricing redetetmination in MV45AFZB USEREXIT_NEW_PRICING_VBAP.

Roberto

Answers (2)

Answers (2)

Former Member
0 Kudos

Good Afternoon,

Perhaps you are not using the correct pricing type in your copy control. Please test with a different pricing type.

What does the condition analysis say after you copy? Does it say:

CONDITION RECORD EXISTS, BUT HAS NOT BEEN SET....?

If so then this can have different causes:

The condition was deleted manually in the item condition screen.

The condition record was created later. Please note that order

processing and pricing have buffer mechanisms. This means that a newly

added condition record might only be found after order processing have

been left completely and then started again.

When an item was added, the condition record was accessed with key

fields other than change time. This could lead to different results in

the requirements check at the time of adding and the change time. This

can occur when modifications are made.

In billing (or when copying orders): Certain condition types were not

determined in the source document (this is usually controlled by the

pricing requirements). When creating the document, the document flow

(TVCPF,TVCPA) is processed using a pricing type that does not

redetermine these condition types, although they are supposed to be

called via the requirments."

Please check if any of those reasons apply to your problem.

Note that the condition type is determined just in the moment when

the billing item is created. And it then that the userexit fills the

field. When you save the billing document, pricing is called.

Some of the possibilities that may be causing this problem are :

1. Pricing Type in copy control

note #24832

2. Wrong coding in USEREXIT_PRICING_PREPARE_TKOMK + TKOMP.

You should check, whether Routine KOBEV_xxx contains queries for

queries for structure KOMP (OSS note 130416).

3. In condition type, scale is set, but in condition record, there

aren't any scales.

I hope you find all this information helpful!

Kind Regards,

Martina McElwain

SD Forum Moderator

Former Member
0 Kudos

do the item category determination for your new item category

rewards is helpful if it helps you