Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 
Former Member
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:


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:
Former Member
0 Kudos
Very insightful Ewa! Thanks for the level of detail for clarity...

0 Kudos
Thanks for custom attribute. By default there is Request for Change ID as attribute. Could we add as customer attribute Change Document ID?

Br Leena
Former Member
0 Kudos

I tried to follow your blog  and manged to create Customer Attributes with single Value , when i tried to create a  multi-value attribute that can have several values, what Data Element do i have to choose?

when I choose Data Element: XVALV, how do i  add the additional values.

or is there any specific Data Element that i need to choose for multiple Value attributes,in our scenario i need to create more than 20 Custom Values under 1 Attribute type.


Thank you in Advance.


0 Kudos
Hi Ewa,

I have duplicate attributes maintained in the table, though i delete the attributes from the "Define attributes" and "Assign attributes to element types" I am still able to see them in the SOLDOC screen at every level. Is there any other table from which i should remove the entries.


Former Member
0 Kudos
Dear Ewa,


Thanks for the blog, with this we  were able to create a customer field and make it searchable.

We would also like to have this field visible in the history of a document in the branch(visible via right click on the document in the structure, display history), much the same as the value of the keywords field is visible there.

Would you happen to have information about how to enable this?

Kind regards,

Former Member
Hello Ewa,

We have created an multivalue attribute (country) so that we can define that a process applies to many countries.  We followed the instructions from this blog, and we were able to create the new attribute, and though it is defined as multi-value, we are not allowed to enter more than one value.

We use an data element that refers to a domain we have created with 5 possible values.

Any idea how to solve it?


Esteban Hartzstein
Active Contributor
0 Kudos
We too are having the same issue, we have define Multiple Value Attributes but we only get Single value when we maintain. Probably we both are trying to do same thing here 🙂 Maintain global roll out attribute against a Process. If you found out any solution, then pls let us know as well.

Former Member
0 Kudos
Thanks Ewa, indeed.

I have a question.  We are trying to create an attribute that uses BU_PARTNER.  We are having issues for any soldoc item to accept it.  It seems to us that only one business partner is acceptable per soldoc item.  By default, there is one BP-type field (Responsible).  The thing is that we add our field, and we are able to retrieve the BP in SolDoc, but when we try to save, we get an error that the BP we are trying to use is incorrect, although that same BP was accepted as responsible.  Any idea about that possible restriction of a BP per SolDoc item?  Any idea how to bypass it?  Thanks,  Juan
Former Member
0 Kudos
We found the solution.  If you are in SP06 already, you will not experience the reported issue, but if you are in an earlier patch, first implement SAP Note 2443570 and create the Data Element SMUD_BU_PARTNER_EXT mentioned there.  After that, you should be able to add as many BPartners as required without restrictions.



Former Member
0 Kudos
Hi Ewa and others 🙂

Is there any option how to set the custom attribute as read-only field and maintain the value via runtime (add the value during custom code processing)?


Former Member
0 Kudos
Hi Vivek,

Did you figure this one out yet? I have exactly the same issue in SPS 05


0 Kudos
Hi Vivek,

did you manage the Multiple Value Attributes?

Thank you,


Active Contributor
0 Kudos
Thank you.

This comment is also an additional source of information about deleting an Attribute (mostly because this is the first blog found for "delete customer attribute solution documentation") and I don't see the need to publish about that topic since it's exact the same procedure to create, but backwards (I could cheaply copy/paste backwards this post and call it a day with a real procedure, but I won't).


If you, reader, ever need to delete on purpose Customer Attributes from elements process (you are refactoring modelling, or that attribute was dropped, or whatever be your mischief reasons), KBA 2549970 drop a hint about how to do it on question "I created a customer attribute by accident. How can I delete it?".

You may be discouraged by the last line that if you do it wrong then "solution documentation application will dump" (a scenario that SAP could potentially avoid happening if they coded an event on that View Cluster), but take your time reading this blog (if you never created an attribute), take notes of each step done to create it, and do it backwards for deleting it.

The steps to delete an attribute, summed up, are:

  1. Remove its UI settings

  2. Remove ALL its assignments from Model extensions. F1 or ask an ABAP to locate that table to check if multiple Model Extensions exists and you are lazy enough to check them or learn how to filter by contents.

  3. Finally, delete its definition.

This is the general rule, but that doesn't mean your must follow it blindly. Take your time, either  reading and preparing before or sorrowing later (with dump and fixing it).

Also, do not forget that values are lost once you delete an attribute.


0 Kudos

@Vivek_Hegde : were you able to manage the multiple attribute selection