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

Z condition table inactive


1. I have created a new condition table A997 in ECC.

2. In order to replicate it to CRM I followed instructions I was given (R3AS for DNL_CUST_CNDALL, SE37 to reset IPC buffer and SM52 to reset VMC) in the PRD environment.

3. As this was not working I searched for other means so I added my condition table for the specific discount condition type to table MNTCNT (ECC - SPRO - Integration ... - CRM - Basic functions - Data exchange conditions) without reading the IMG documentation (I know, my bad).

This MNTCNT is only filled in PRD, not in our QAS or DEV environment.

As we inherited this CRM system from the past, I wanted to set things right and ajusted the table in DEV and transporting it to QAS and PRD.

4. After repeating step 2 in all environments, I found back CUS997 in DEV and QAS, but not in PRD.

5. Next I contacted an external consultant who told me to open the ECC PRD system for cross client changes. This worked out well and CUS997 is in CRM PRD.

6. I noticed when performing VK11 for A997 that this was not possible in ECC, making me realize what I had done in step 3 was incorrect.

7. I corrected the MNTCNT table and A997 was back usable from within ECC. Test orders were fine, taking correct discounts ...

Now we come to my actual problem.

After step 3 something else must have gone wrong for the condition tables (A983 and A984 for the record) that should only be updatable from within CRM (they were already in table MNTCNT and nothing changed).

The result is that in the existing service contracts all price agreements are in status yellow telling me that the conditions cannot be maintained in CRM.

This means they are currently not updatable nor can new contracts be given price agreements.

If I search for condition tables CUS983 and CUS984 in CRM PRD customizing, I notice that there are 2 lines for each of them now, both in status inactive:

a CUS983 (blank)


c CUS984 (blank)


In CRM DEV and CRM QAS only 1 line for both can be found (the one with the CRM table name).

My guess is that in PRD a and c should become active again.

As I cannot test in DEV or QAS because of different situations, I do not risk to make this change.

What would be the impact? Are existing conditions not deleted?

Could someone shed a light on this?

Many thanks in advance!

Best regards,


Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jul 05, 2012 at 02:20 PM

    Hi Geert,

    For the analysis, can you send the screenshots of table CUS983 in CRM PRD, with the complete log in the below window.

    IMG > CRM > Basic functions > Pricing > Define settings for pricing > Create condition table

    Best regards,


    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Vincent,

      Finally figured out what triggered the /SAPCND/T681M table to be empty.

      The MNTCNT table was only filled in PRD till now.

      With the changes I made, I wanted to do it all the correct way and started transporting from DEV.

      As initially the logical system in MNTCNT was empty, I assumed that it would automatically detect the correct client settings.

      Apparently it doesn't, because now I added the client in the PRD customizing and after replicating the conditions again, /SAPCND/T681M is filled and we can start updating contract discounts again.

      All your help was very much appreciated and it helped me a great deal to better understand the concepts of CRM pricing conditions.

      Thanks again!!!

      Best regards,


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.