The setup of customer attributes has been change in SAP Solution Manager 7.2. You can create customer attributes for elements of the Process Management application in transaction SOLMAN_SETUP, in the section “Process Management”, step 6:
In this application you can add customer attribute types to the Solution Documentation model. You can then store additional data in those customer attributes. The setup application helps you to create all necessary objects (attribute type, extension, UI settings). For details, you can read the documentation of the activity (push the “Information” button after navigating to the corresponding application):
Define Customer Attributes
The entry screen allows you to add an attribute to your entire Solution Documentation model – to ALL elements of Process Management or to three subsets of Process Management elements: either structure elements or assignments or selected assignment groups:
If you need to add only a specific attribute to an element of the current model, go to the “Advance Model Settings”:
Switch to the change mode with the button:
Now, you can add your attribute, for example to describe if a process or process step is relevant for monitoring. In this case you could create an attribute “ZMonitoring” (a customer namespace must be used) with a short text “Monitoring Relevant” and input values “Yes”/”No”.
Choose “New Entries”:
To provide input values, you need to use a proper data element for the attribute. You can use an existing data element which has already defined values you need. You can also create your own data element with a value help containing input values you need. If you do not know how to create own data table with your specific data elements then please review this blog:
How to create customer attributes for projects – Part 1
For a simple attribute like the “Monitoring Relevant” with input values “Yes”/”No” we can use any existing data elements e.g. “XVALV”:
Press “Save”. You will be prompted to save your changes in a development package – enter the package name:
Save and go “Back” and select the new attribute:
Double click on the “Model Extension” and select the “ZCUSTOMER_EXTENTION”. If the extension does not exist, then you need to create it.
In the next step you have to assign your attribute to the elements of the Solution Documentation - double click on “Assign Attribute Types to Element Types”:
Choose “New Entries” and add the element types you want your attributes be used for – in this case this will be a process and process step including their reference elements:
In our example four elements are relevant. Chose if your attribute is a single or multi value attribute and save your entries:
Go to “Advance UI Settings”:
Choose “New Entry” and add your attribute to an attribute group e.g. “CUSTOMER””:
Save it in your customizing transport request.
Now, the attribute should be visible in the Process Management application (transition SOLDOC). You can assign the attribute value in the “Attribute Pane”, in the section “Customer Attributes” of the structure elements the attribute was defined for:
Setting attribute value:
Searching for Information Using “Advance Search”
You can then use the search capabilities or the “List” viewer to find the processes and process steps based on the attribute value:
Specify the search criteria:
Searching for Information Using “List”
In the “List” viewer:
Select the relevant attribute grouping:
Result:
Additional note:
If you try to create customer attributes for elements in transaction SOLMAN_SETUP and the systems prevents you to do it displaying a message “Content activation is not yet completed -> action cancelled”:
Make sure you have finalized the content activation procedure (if your system was upgraded) or you opted out the content activation procedure (if your system is a new install). Only if the system is a new install and you do not need to activate any content from projects/solutions, you can use the transaction PREPARE_ACTIVATION to quit the content activation process.
Adjusting the Search Model
After you changed the process model (e.g. added new attributes) you need to regenerate the search model. Please review the blog for further information:
https://blogs.sap.com/2016/10/31/configure-embedded-search-trex-solution-documentation-solman-7.2/
In this application you can add customer attribute types to the Solution Documentation model. You can then store additional data in those customer attributes. The setup application helps you to create all necessary objects (attribute type, extension, UI settings). For details, you can read the documentation of the activity (push the “Information” button after navigating to the corresponding application):
Define Customer Attributes
The entry screen allows you to add an attribute to your entire Solution Documentation model – to ALL elements of Process Management or to three subsets of Process Management elements: either structure elements or assignments or selected assignment groups:
If you need to add only a specific attribute to an element of the current model, go to the “Advance Model Settings”:
Switch to the change mode with the button:
Now, you can add your attribute, for example to describe if a process or process step is relevant for monitoring. In this case you could create an attribute “ZMonitoring” (a customer namespace must be used) with a short text “Monitoring Relevant” and input values “Yes”/”No”.
Choose “New Entries”:
To provide input values, you need to use a proper data element for the attribute. You can use an existing data element which has already defined values you need. You can also create your own data element with a value help containing input values you need. If you do not know how to create own data table with your specific data elements then please review this blog:
How to create customer attributes for projects – Part 1
For a simple attribute like the “Monitoring Relevant” with input values “Yes”/”No” we can use any existing data elements e.g. “XVALV”:
Press “Save”. You will be prompted to save your changes in a development package – enter the package name:
Save and go “Back” and select the new attribute:
Double click on the “Model Extension” and select the “ZCUSTOMER_EXTENTION”. If the extension does not exist, then you need to create it.
In the next step you have to assign your attribute to the elements of the Solution Documentation - double click on “Assign Attribute Types to Element Types”:
Choose “New Entries” and add the element types you want your attributes be used for – in this case this will be a process and process step including their reference elements:
In our example four elements are relevant. Chose if your attribute is a single or multi value attribute and save your entries:
Go to “Advance UI Settings”:
Choose “New Entry” and add your attribute to an attribute group e.g. “CUSTOMER””:
Save it in your customizing transport request.
Now, the attribute should be visible in the Process Management application (transition SOLDOC). You can assign the attribute value in the “Attribute Pane”, in the section “Customer Attributes” of the structure elements the attribute was defined for:
Setting attribute value:
Searching for Information Using “Advance Search”
You can then use the search capabilities or the “List” viewer to find the processes and process steps based on the attribute value:
Specify the search criteria:
Searching for Information Using “List”
In the “List” viewer:
Select the relevant attribute grouping:
Result:
Additional note:
If you try to create customer attributes for elements in transaction SOLMAN_SETUP and the systems prevents you to do it displaying a message “Content activation is not yet completed -> action cancelled”:
Make sure you have finalized the content activation procedure (if your system was upgraded) or you opted out the content activation procedure (if your system is a new install). Only if the system is a new install and you do not need to activate any content from projects/solutions, you can use the transaction PREPARE_ACTIVATION to quit the content activation process.
Adjusting the Search Model
After you changed the process model (e.g. added new attributes) you need to regenerate the search model. Please review the blog for further information:
https://blogs.sap.com/2016/10/31/configure-embedded-search-trex-solution-documentation-solman-7.2/
- SAP Managed Tags:
14 Comments
