The program-technical objects that are generated during generation of a DataSource for UD connect can be created in transportable or local format. Transportable means that the generated objects can be transferred to another SAP BW system using the correction and transport system. The transportability of an object depends on, among other things, in which namespace it is created.
The delivery status allows for the generation of transportable objects in the SAP namespace. If this appears to be too laborious (see the dependencies listed below), there is also the option of switching to generation of local objects. To do this, you run the RSSDK_LOCALIZE_OBJECTS report in the ABAP editor (transaction: SE 38). Then the system switches to local generation. The objects generated afterward are not transportable. If the report is executed again, the generation is changed back to transportable. The status of already generated objects does not change. All new objects are created as transportable.
If you need to work with transportable objects, you should be aware of the following dependencies:
Because the generated objects are ABAP development objects, the user must be authorized as a developer. A developer key must be procured and entered. Generation requires the customer-specific installation number and can be generated online. The system administrator knows this procedure and should be included in the procurement. The key has to be procured and entered exactly once per user and system.
Because the generated objects were created in the SAP namespace, an object key is required. Like the developer key, this is customer specific and can also be procured online. The key is to be entered exactly once per object and system. Afterwards, the object is released for further changes as well. Further efforts are not required if there are repeated changes to the field list or similar.