Conditions in new conditions table are not visible in transaction COMMPR01

[Former Member]

Hi guys,

we created a new condition table in ERP for customers that use price lists.
We made an initial load of the conditions and everything worked fine.
The new condition table CNCCRMPRCUS834 is created in CRM and filled with some conditions.

The problem ist, that these conditions are not visible in transaction commpr01 and therefore not in the web ui.

All the other condition tables are visible in the transaction (if conditions for the product exist).

The only difference between the new conditon table and the others is the field price_list and this does not exists in transaction commpr01 in the conditions tab.

Could this be the problem? And is there a way to make the new conditons visible in the transaction?

Thank you very much!

Best regards
Chris

[michael_piesche]

christian.ahrens, 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]

In general, you always have to customize maintenance groups for conditions if you want to make them visible for example in COMMPR01, WebUI or Trx. /SAPCND/GCM and others. Therefore, you have to add the new conditions and tables to the maintenance group for their specific context, e.g. for COMMPR01.

• SPRO->CRM->Master Data->Pricing->Conditions and Condition Technique->Condition Technique: Basics->Create Maintenance Group

The conditions you see right now in those contexts are there most likely by the default setup of the CRM system since they have been customized within certain maintenance groups. Or somebody else has already customized those before you.

Therefore, you can either add your conditions to the existing relevant maintenance group (Scenario A), or you create a new one (Scenario B):

Scenario A:

1. SPRO Task "Assign Condition Group to Application CRM": Check what maintenance group is assigned to the Folder "Product" with application "CRM". By default, that should be "PRODUCTCRM"
2. SPRO Task "Define Maintenance Groups for Context": Also check that this maintenance group has the assigned context "PRODUCT"
3. SPRO Task "Create Maintenance Group": Choose the previous determined maintenance group and assign the new conditions with their relevant access tables to it

Scenario B:

1. SPRO Task "Create Maintenance Group": Create a maintenance group and assign the conditions with their relevant access table

2. SPRO Task "Define Maintenance Groups for Context": Choose Context "PRODUCT" and assign your maintenance group to this context (choose GCM if you want to display all sorts of conditions with Trx. /SAPCND/GCM)

3. SPRO Task "Assign Condition Group to Application CRM": Choose Folder "Product" and add a record with application "CRM" and also with your maintance group