The Global Attribute in Group Rollout 
You can lock this structure element against changes in the rollout project, or allow subsidiaries to change it partially or completely, by giving its Global attribute appropriate values.
The following table shows the effect of the values of the Global attribute (transaction tab), which you assigned to a structure element in the template project, on the behavior of the structure element and the assigned business content, in the rollout (implementation) projects which have copied this template.
The Global attribute F1 help contains further information about the values of the Global attribute.
The Global Attribute in Group Rollout
Global Attribute Value |
Select/deselect structure elements and transactions (scope) |
Display mode in tab |
Cut/paste/delete structure nodes |
Delete a row |
Change documentation |
Create blueprint-relevant documentation |
Copy blueprint-relevant documents to the Project Documentation tab automatically at project generation |
Force copy of template changes in adjustment |
|---|---|---|---|---|---|---|---|---|
Global |
Not allowed |
Display only |
Locked |
Forbidden on all tabs |
Not allowed |
Not allowed |
Yes |
Yes |
Default |
Not allowed |
Changeable |
Cannot cut |
Forbidden on all tabs |
Not allowed for Blueprint-relevant documentation from the template project |
Allowed |
Yes |
Yes |
Partly default |
Allowed |
Changeable |
Cannot cut |
Not allowed in the Structure tab |
Not allowed in the Structure tab |
Allowed |
No |
No |
Harmonized |
Allowed |
Changeable |
Cannot cut |
Not allowed in the Structure tab |
Not allowed in the Structure tab |
Allowed |
No |
No |
Local |
Allowed |
Changeable |
Cannot cut |
Not allowed in the Structure tab |
Not allowed in the Structure tab |
Allowed |
No |
No |
Initial |
Allowed |
Changeable |
Allowed |
Allowed |
Allowed |
Allowed |
No |
No |
The General Documentation, Messages and Administration tabs contain no Global attribute checks.
For cutting out or changing the sequence in the structure, the system checks the same authorizations as for deleting structure elements from the template. In the Structure tab, the Global attribute also affects subnodes. So you can also delete a global process from a local scenario. To prevent the deletion of a Global attribute in a local scenario, implement the BAdI BADI_SA_DEFINE_GLOBAL_ATTR with the parameter FORBID_OBJECT_DELETE.
By implementing the BAdI BADI_SA_DEFINE_GLOBAL_ATTR, you can:
hide global attributes delivered by default
change the default effects of the global attributes (e.g. tighten or relax the checks in specified tabs)
define customer-specific global attributes and their effects
SAP delivers a default implementation of the BAdI (default implementation class CL_SA_DEFINE_GLOBAL_ATTR). You can base your own implementation it. The BAdI documentation contains further information about Defining Global Attribute Values.
Only the Project Leader has full authorization to change and delete elements from the template. The project leader can perform the activity which is normally forbidden, after confirming warning messages. He needs authorization for the authorization object S_PROJ_GEN with the value GLOB in the field PROJ_FUNC. The role Project Leader (SAP_SOLAR_PM) contains this authorization.