SD - Pricing Condition Type

[Former Member]

Hi Experts,

I want to bring across custom condition type (Z001) in a sales document line-item level (Conditions) automatically when certain document conditions are met...that is, combination of sales org./sales doc./order reason (header).

I've done all the required config. but it still does not come up automatically in the sales document when required conditions are met...on clicking "Analysis" button I get a message "Condition record exists, but has not been set'. If I click on "Update" button and choose option "C" then it determines the pricing again and Z001 comes up fine. But shouldn't this be automatic without hitting the Update button?

Or do I have to set it via ABAP code in one of the user-exits (VOFM) or am I missing something in config.? Any idea how to "Set" this condition to be automatic?

Thanks in advance.

[Former Member]

There are different reasons for this:

1. The condition was deleted manually in the item condition screen.

2. 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 has been left completely and then started again.

If the condition type is used for subsequent settlement (rebate), there may be subsequent updating of business volume (the agreement is is created retrospectively). The document conditions do not contain the condition record, as the condition record was not created when pricing was carried out. Updating of business volume is carried out using special functions for subsequent settlement.

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

4. 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 requirements.

FYI.. See Long text for the message.

Thanks,

Shashi Reddy

[Former Member]

Sashi,

Thanks for the copy/paste of the system documentation that comes up in the pricing "Analysis" for a particular condition but I've already read this.

Has anyone else come across a similar issue like this one?

[Former Member]

In SD PRicing analysis, I am getting a message Condition record exists, but it is not set.

How to identify whether The condition record was created later.

Kindly update me how to go about in this regard.

Thanks in advance.

Varada

[Former Member]

Hi Sougata ,

y u are taking Sales Doc ? into access seq ? Thats the Problem , While SAP calling this Pricing Procedure these is a TEMP sales Doc would be Created ? So please remove that sales Document from the Acc.Seq.and check.

Regards

Prabhu

[Former Member]

Prabhu,

Sales doc. type (KOMK-AUART_SD) has to be there in access sequence because I want to default condition type Z001 in the pricing conditions of the SO <u>only when</u> sales doc. type = 'RE' and sales org. = 'AU01' and order reason (KOMK-AUGRU) = '010'.

[Former Member]

Hi ,

check in SPRO itself in the Condition Types

<b>heading is Changes Which Can be MADE</b>

                                                                                Manual entries      D Not possible to process manually                                                                                

Regards

Prabhu

[Former Member]

Sorry mate, I'm not sure what you're trying to say. I took off the tick from "Delete" checkbox in config. and made field 'Manual Entries' = 'D' (in Maintain Condition Types) but Z001 condition still does not come up. Any ideas?

[christian_wohlfahrt]

Hi Sougata ,

I had this behavior already, but in my case it was a problem with promotion numbers.

I guess it's because of a value change of your fields for the condition access of Z001. Sales organization and sales doc type are fixed before pricing for the first article is execute, but how about order reason? Is it possible, that order reason is set after the pricing was done initially? A later change of the order reason won't trigger pricing again.

When you now look into the analysis, the current values are taken -> condition is found in analysis, but wasn't found originally -> the strange message 'found but not taken' is raised.

Also a new pricing will now take your condition, so this would match my guess.

If this is the reason, make sure to get the order reason before articles are entered (or trigger a new pricing via user-exit - difficult for a header field). E.g. define a dummy reason 'standard order' and make this a required field -> no articles can be entered, before order reason is defined. Still a later change won't trigger correct condition re-determination.

Other possibility: trigger new document pricing in UE 'before save'.

Regards,

Christian

[Former Member]

Hi Christian,

Thanks for your input. My approach was incorrect. This issue cannot be resolved via VOFM. I solved it using other SO exit where new price is determined on checking VBAK fields 'Order Reason/Sales org./Sales doc.type' combination. I just set variable 'new_pricing' = 'C' at the point when user clicks on 'pricing' icon after setting the appropriate header reason.

Regards,

Sougata.