Several times we need to identify some information related to a particular user, position or organizational unit. Find bellow the step by step to create custom attributes and the options that SRM provide
Step 0 – Pre-Requisites
First of all we need to plan which will be the data source of our attribute.
The options we have are:
1- Use table BBP_ATTR_F1. Append the table and add a new field that will represent our attribute.
This option is useful when the attribute’s possible values are just simple and it is not restricted to a particular set of values or the possible values are Domain dependent.
2- Create a Custom table.
This option will be better in case of multiple values to choose that come from custom information.
3- Use Standard Table.
Choose this option if the attributes values should come from standard table. I.E Create an attribute whom possible values are product categories, in that case data source will be COMM_CATEGORY-CATEGORY_ID.
Step 1 – Create the Attribute
Go to SM30
Double Click in “Attributes” then create the own attribute.
At this screen we will choose the ID, Description and use the source that we determine in Step 0.
Apart of the data source here we will define if our new attribute will allow multiple values and also a range (Area) or individual value.
Step 2 – Assign Attribute to Scenario
Double click on “Scenarios” will see the BBP scenario details. It’s the only one provided as standard.
Apart of custom attributes, here we can change/display the inheritance definition or data source of standard values.
When we add the Attribute to the Scenario we need to choose the inheritance behavior by choosing one of the following options:
Normal Inheritance (Additive) -> This option will add inherited values to local values. It will only work if the attribute allow multiple values.
Local Values overwrite inherited values -> This option will work on single values and it’s the most recommended and flexible.
No Inheritance -> This option should be use carefully since may cause maintenance issues if the attribute supposed to be inherited.
Inherited values cannot be redefined locally. -> It means that the inherited value cannot be changed locally. Also should be careful when use this type.
Step 3 Assign Attributes to Object Types
Once the attribute have been assigned to scenario we must choose if will be at Organizational Unit Level, Position Level or the attribute belongs to Vendor Group (PPOMV_BBP transaction)
Step 4 – Save and Transport.
When you finish creation, save and the system will request a TR.
Bonus Track !
After you create the attribute it’s time to use it. To read values from structure should use FM RH_OM_ATTRIBUTES_READ or RH_OM_ATTRIBUTE_READ in case of reading only one attribute.
Good Luck !