Pricing Condition overlap check fail due to prior marked for deletion records

[former_member662689]

We use SAP Trade Management to control pricing setup. We have some issues in ECC where a Pricing Condition has been marked for deletion due to cancellation of a Customer List Price, and a new List Price has been setup which overlaps with the previously cancelled one, but the new Pricing Conditions are not being setup in ECC (and we see no error message!).

We believe there is some sort of overlap check but we cannot understand how this process should be working.

1. After the original pricing condition has been marked for deletion, is there a process that should be running in ECC to actually delete/archive these records so overlap check doesn't fail? Maybe we are not running this?

2. Should the overlap check be configured to ignore any currently existing marked for deletion records. If this is the case then our overlap condition check must not be defined correctly. How/where do we change this?

Many Thanks

Simon

[michael_piesche]

simon.crowder99, please follow up on your open question.

• comment answers or your question if there are still open issues.
• otherwise mark an answer as accepted if it helped you solve your problem
• or post an answer of yourself and accept it if you found another useful solution yourself
• or redirect your question to another question that is related and was useful to solve your problem
• in the end, close your question

[michael_piesche]

(A) If Condition records originate in ECC, they are exchanged from ECC to CRM by BDOCs either by the initial or the delta load. In rare cases the exchange does not work properly. One of the following steps helps:

1. Try to recreate the condition in ECC with Trx. VK11 (delta load)
2. Download the condition records again for your condition table with Trx. R3AS (initial load, deletes all records in CRM first and fills it with the existing ones from ECC)
3. Delete the faulty record manually (not actually recommended, but a last resort)

(B) If Condition records originate in CRM, they are also exchanged by BDOCs, this time from CRM to ECC. If you are using standard conditions and access tables, everything should be setup by default. Did you check in CRM customizing for your condition that it can be maintained in CRM. Otherwise, you still might want to check the following:

1. ECC: SPRO->Integration with Other mySAP.com Components->CRM->Basic Functions->Data Exchange Conditions (also check the documentation for this IMG-activity)
   The following entry should exist to allow CRM to maintain condition records and replicate them to ERP:
   Usage A (Pricing)
   Table xxx (condition table)
   Application V (Sales/Distribution)
   Condition Type xxxx (condition type)
   Logical System xxxxxxx (CRM Destination)
2. Customizing settings for pricing techniques have to be replicated from ECC to CRM.
   In CRM use Trx. R3AS and Object DNL_CUST_CNDALL
3. In case Objects fail to finish the load, you might want to check SMQ1, SMQ2 and SWM01 in CRM but also SMQ1 and SMQ2 in ECC. In order to reload those, you have to delete the Queue Entries. You can also check the log of object COND_EXCHANGE with Trx. SLG1

If you still have issues, please check the following blog to debug the exchange of those conditions: https://blogs.sap.com/2015/12/07/debugging-conditions-upload-from-crm-to-ecc/

[former_member662689]

Hi Michael, thanks for the info. Will try above and feedback.

Simon