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 page), which you assigned to a structure item in the template project, on the behavior of the structure item and the assigned business content in the rollout (implementation) projects that have copied this template.The Global attribute F1 help contains further information about the values of the Global attribute.
Global Attribute Value |
||||||
---|---|---|---|---|---|---|
Global |
Standard Complete |
Standard Partial |
Harmonized |
Local |
No Global Attribute Set |
|
Structure Changes |
||||||
Change structure element or transaction selection by flagging In Scope |
Not allowed |
Not allowed |
Allowed |
Allowed |
Allowed |
Allowed |
Delete a Structure Element |
Not allowed |
Not allowed |
Not allowed |
Not allowed |
Not allowed |
Allowed |
Insert a structure element under the selected node |
Not allowed |
Allowed |
Allowed |
Allowed |
Allowed |
Allowed |
Delete a row in a tab (except Structure tab) |
Not allowed |
Not allowed |
Not allowed |
Not allowed |
Not allowed |
Allowed |
Change mode for tabs (if BAdI active) |
Not allowed |
Allowed |
Allowed |
Allowed |
Allowed |
Allowed |
Change Documents |
||||||
Change or delete documents based on a template |
Not allowed |
Not allowed |
Allowed |
Allowed |
Allowed |
Allowed |
Change or delete Blueprint-relevant documents |
Not allowed |
Not allowed |
Allowed |
Allowed |
Allowed |
Allowed |
Flag documents which are not based on templates, as Blueprint-relevant |
Not allowed |
Allowed |
Allowed |
Allowed |
Allowed |
Allowed |
Automatically copy blueprint-relevant documents to the Project Documentation tab at project generation |
Yes |
Yes |
No |
No |
No |
No |
Force copy of template changes in adjustment |
Yes |
Yes |
No |
No |
No |
No |
The General Documentation, Service Messages, and Administration tab pages do not contain any checks for global attributes.
For cutting out or changing the sequence in the structure, the system checks the same authorizations as for deleting structure elements from the template. On the Structure tab page, the global attribute also affects subnodes in the hierarchy. 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 as standard
Change the default effects of the global attributes (for example, tighten or relax the checks on specific tab pages)
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.