Skip to Content
author's profile photo Former Member
Former Member

Can condition exclusion be sales area specific

Hi Experts,

I need to find out if i can make a conditio exclusion sales area specific. My requirement is that i have 5 different sales area using the same pricing procedures. For 4 of them, i need to use an exclusive exclusion between 2 codnition types, but for one of the sales area, i need both of the condition types, basically no exclusion for this sales area for this condition types.

The pricing procedure is same across sales area and i need all other exclusions maintained ofr this PP for all the sales areas. Only one exclusion is not needed for one of the sales areas.

Any ideas/sugesstions?

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Nov 21, 2011 at 02:50 PM


    I don't think we can restrict exclusion based on sales area through configuration.

    If you want to use only one condition (out of two) in some specific sales area, why don't you create another pricing procedure as the copy of the existing one and use? In this you can put exclusion parameters.



    Add a comment
    10|10000 characters needed characters exceeded

    • What you are asking is not possible through standard system using configuration alone.

      Condition exclusion assigned to a pricing procedure cannot be controlled based on sales area or other criteria, once assigned and condition exclusion applies to the pricing procedure wherever it is used.

      What you can do though is to inactivate a condition type say ZCT2 based on condition type say ZCT1. You can put the logic in pricing formula (alternative calculation type formula) against ZCT2 in pricing procedure

      You get all the condition types in XKOMV table inside the formula for ZCT2. So if ZCT2 is below ZCT1 in the pricing procedure, by the time ZCT2 is being evaluated the value of ZCT1 is already in XKOMV table. You can fetch ZCT1 value compare and inactivate ZCT2 by setting XKOMV-KINAK = 'X' for respective sales areas. You can get sales area information in variables KOMK-VKORG, VTWEG, SPART etc. Also tell your developer to use his own work area for XKOMV header. The values in the header of XKOMV should not be changed as they may be used in further logic.

      Only thing here is that the condition type that needs to be inactive should be below the one that you use to inactivate it, in the pricing procedure

      Work with a developer and revert back if you have any issue.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.