How to Update SM_CRM Search Criteria to Report based on the value of a Custom Field

[robynhosby]

In this blog, I will show how to report in CRM_UI (SM_CRM) based on a new custom UI field created in AET. This is using SolMan 7.1 SP 11.

The requirement was to add a new field to the Request for Change (ZMCR) UI and allow the new field reportable in the Search Criteria.

To add the new custom UI field, I followed the steps in this post, so I won’t go into those details.

http://scn.sap.com/people/tzanko.stefanov2/blog/2008/11/18/application-enhancement-tool-creating-and...

The requirement was to enable the new custom field to appear in the Search Criteria in SM_CRM here...

Tcode SM_CRM.  Confirm you have Configuration mode checked and select SAVE....

Select Change Request Management -> Requests for Change...

On the Search screen, select Show Configurable Areas…

 

Highlight the Search Criteria section and select…

If a Z Configuration Area does not already exist for the selected area, create one…

Select the Component Name to copy and COPY…

Confirm you are maintaining the Z business role.

Change the Usage, Type, and Subtype to <DEFAULT>. Select CONTINUE.

Select the newly created Configuration Area.

Locate the custom field that you want to show in the Search Criteria in the list of Available Search Criteria.

...error “500 SAP Internal Server Error - Exception condition “PROBLEM_WITH_QUERY raised” appeared…

In my case, I found that this error was caused by the enhancement generation not entirely completing when the custom field was added.  The new field was not found in table CRMC_REPDY.

To resolve this error, in tcode AXTSHOW, I needed to manual re-generate the enhancement.

Before re-generating, the high level was green, but the Appends and other objects were not active. I selected Generate Enhancement to complete this step.

After re-generating,  the new field was successful….

This caused the field entry to be created in table CRMC_REPDY…

Now, new field is reportable in SM_CRM…