In case you are in a situation where you have an existing (external) TPZ file at hand that you would like to use and modify within your own Enterprise Service Repository, you will encounter that you are not able to change to edit mode. You may only view the entities and assets within. Please be aware that this is not the normal use case, yet it becomes a very challenging problem in case one encounters such a situation (see Remarks for further infos).
System Integrators for example might have different assets in the ESR that they would like to sell to various customers in order to tailor them to the specific needs of the customer. It might therewith be necessary to import external ESR content into another ESR. In our case for example, we currently support partners on modeling and defining their own Enterprise Services - partner delivered Enterprise Services. This involves discussions surrounding their specific scenarios, service candidates and ultimately hands-on support. This support embraces initial modeling and defining of their services and later on going into review circles to finalize the service definition in according with SAPs Modeling and Design Methodology. As consequence we do exchange ESR content (TPZ files), which are then further used in another ESR(s).
So here's how to enable write access for imported TPZ files and the underlying content:
After importing the Software Component + Software Component Version(s) via Tools -> Import Design Objects, the respective name appears on the left side of the navigation bar/ or gets updated. Navigate to the Software Component Version you would like to modify. Right click and choose PROPERTIES and the following screen will appear:
Please activate the two checkboxes
(a) Objects Are Original Objects
(b) Objects Are Modifiable
Save and that's it. You are now able to modify the entities within the Software Component Version. You can add new model or definition entities or change existing ones.
Remarks:
(1) This concept is specifically geared for the manual exchange of TPZ files into different, not interlinked Enterprise Services Repositories. Automated processes supported by the ESR are not covered in this blog but do exist and need to be considered when migrating content from for example DEV -> QUA -> PROD systems in one landscape.
(2) SAP delivers predefined XI content. It is in no way recommended from SAP to modify this predefined XI content (e.g. XI CONTENT SAP GLOBAL 2.0)
4 Comments