cancel
Showing results for 
Search instead for 
Did you mean: 

Context node attribute ambiguity between two CRM WebUI context nodes of same base entity

Former Member
0 Kudos

Hi,

I've just come across one ambiguity in CRM WebUI context node attributes as mentioned below.

While browsing through BSP component workbench in SAP I find that the attribute COMM_TYPE_TEXT is available in context node BUILSTANDARDADDRESS of view BP_HEAD/CORPACCOUNTDETAILSOV but it is not available in context node DETAILSTANDARDADDRESS of view IUICMD/DETAILCCOUNT although both of them use the same base entity BUILSTANDARDADDRESS.

Any idea ?

Thanks and Regards,

Sumoy Sen.

Accepted Solutions (0)

Answers (2)

Answers (2)

praveen_kumar194
Active Contributor
0 Kudos

one thing is, attribute can be hidden by design layer settings. see for second context is there any design object associated. you can right click on it and choose design layer. if there is any design object check in the design layer settings to see that particular attribute is hidden or not.

second chance, it could be an attribute that is added manually. see if it has STRUCT. notation. if it has generally it is part of base entity. if it doesnot have it, then it could be manually added attribute model or value.

Former Member
0 Kudos

Hi Sumoy Sen,

  May be that attribute is a separately added Model Attribute to that Context node.

For a Context node we can add Model attributes and Value attributes separately.

If that is a Model attribute which is added separately in BP_HEAD component you cannot find it in other Components. The Key structure of BuilStandardaddress will be common for all the components.

In Each component were you used this context node, you can add value attributes and model attributes which will be specific to that component,.

Regards,

    DP.