PRICING: exclusion flag KZEXL not working.

[Former Member]

Hello world this is the problem:

We have created a custom pricing table with the following standard fields:

SOLD_TO_PARTY CRMT_ACS_H_SEL SOLD_TO_PARTY

PROD_SEG_GUID CRMT_ACS_H_SEL PROD_SEG_GUID

In order to insert a condition for standard field PROD_SEG_GUID, we had to implement BADI

/SAPCND/ROLLNAME. It seems that this field is managed only for campaign related conditions in the standard, anyway our implementation works.

After that we added this table as step 2 of 5 steps in an access sequence, all the steps are marked with the exclusion flag (KZEXL).

Now during pricing procedure, the system determines the condition correctly but it does not stop in case a valid condition exist for the custom table, while it stops for all other steps.

Ex.

Step 1 -> no record

Step 2 -> no record

Step 3 -> no record

Step 4 -> 10%

Step 5 -> 20%

Pricing solution: 10%

Ex 2.

Step 1 -> no record

Step 2 -> 15%

Step 3 -> no record

Step 4 -> 10%

Step 5 -> 20%

Pricing resul:

15%

10%

20%

Despite the exclusion flag is set in the access sequence, pricing takes in account even the other conditions..

[Former Member]

Could this be due to the fact that the PROD_SEG_GUID field is a multivalue field (set indicator IS_MULTI_VALUED in table /SAPCND/T681FA )?

Apparently this resets the exclusion flag during access sequence processing. This seems as a restriction of the standard behaviour that could be addressed by an OSS message.

Edited by: Emmanuele Prudenzano on Jul 27, 2010 5:47 PM