Custom configuration not getting called after the upgrade

[former_member273311]

Hi CRM Gurus,

Recently we upgraded our CRM system from CRM 7 EHP 2 to EHP3.

Component: BT120H_CPL

View: Details

Neither the component is enhanced, nor the view. Only custom configuration is defined for the view.

After the upgrade, we noticed that the default configuration is always getting called, even if we have maintained a custom role config key for a custom business role.

However, in the non upgraded system, whenever we login with our custom business role, custom configuration is getting called.

After analyzing the issue, we found that there has been new code addition in DO_CONFIG_DETERMINATION method of IMPL class.

This code addition makes the Object type and subobject type as Default, as a result of which system doesn't find the custom configuration.

In debugging mode, if we skip the execution of these new lines, correct custom configuration is getting called.

Please suggest what could be done to resolve this.We need the custom configuration to be loaded at run time without having to enhance the component itself. Previously(before EhP3) this was possible by defining the business role and including the role config key.

Awaiting your response.

Thanks in Advance.

[former_member273311]

With the implementation of note 2179433 - No role configuration key is determined for complaints,

the issue for complaints is resolved.

However, similar type of issue appears on the search screen of Sales Orders. Custom configuration is not getting determined as no coding part for sales order is put in the DO_CONFIG_DETERMINATION of CL_ERP_S_ERPORDSQ_IMPL.

Please refer the screen shot.

Definitely, there must be a SAP note to have this fixed.
If anyone has faced this issue, please suggest.

[BGarcia]

Hi Visser,

As simple solution, can't you make a copy of your custom configuration maintaining role key and component usage, and defining object type and subtype as <default>?

The only problem I can see in this approach is if you want to show multiple configurations depending on different transaction types for this specific view.

Kind regards,

Garcia