ABAP programs to copy BW objects

Similarly, to BW objects deletion program there are few more tools for different operations on the BW’s object. For a copy operation there are following ABAP programs available:

RS_COPY_TLOGO                  Copying and Deleting TLOGO Objects

RSO_COPY_TLOGO                Copying TLOGO Objects with References

RS_COPY_TLOGO – serves for purposing of copying a different types of BW objects between its Business Content Delivered (D) version to/from its Active (A) and modified (M) versions. For an overview of supported objects, see the program’s selection screen. It ca also delete the A, D or M versions of the selected objects. In addition, it can copy and delete texts associated with the objects. The operations executed by the report are is technically performed by a call of function module RSTLOGO_DELETE_TLOGO_MULTI_OBJ. The program it self is with the BW for a long time since the year 2003.

RSO_COPY_TLOGO – purpose is to copy BW (TLOGO) objects with its references. So called copy package is prepared that is executing the copy task. Within the package details like the objects names and objects types needs to be specified. The copy operation within the report is technically handled via ABAP class CL_RSO_COPY.

As always, use extreme cautions while working with those programs. Always test the scenario what do you need to achieve in sand box type of the WB system before you process for real.

 

More information:

RS_DELETE_TLOGO program to delete BW objects

What is TLOGO in SAP BW terms?

RS_DELETE_TLOGO program to delete BW objects

Normally BW developers use dedicated IDE to work with the BW’s objects. Whether in an old BW’s world it is SAP GUI’s t-code like RSA1 or in case of reporting BEx tools like Query Designer to delete the BE objects that re not needed anymore. Or in a new BW’s world, it is an SAP HANA Studio where the BW objects can be deleted. In case of the BW object there is a TLOGO term used that refers to transportable BW object type.

There may a situations popping up from time to time that may result in automating the deletion of not needed BW’s objects. To do that SAP is providing an ABAP program called RS_DELETE_TLOGO. Needless to say that as with any deletion it needs to be used with a great amount of a caution! What the program does is to delete BW objects not needed anymore. As an examples a scenarios of mass deletion can be covered with the program. Another example can be that as currently many customers are moving their BW’s deployment to BW4/HANA there is a necessity to delete old objects as well.

The program deletes an active (A) version of particular BW objects. If the objects that needs to be deleted was activated from the Business Content and a delivered (D) versions should be deleted then there is another program to be used: RS_DELETE_D_VERSION_FOR_TLOGO.

One thing to remember while working with those deletion programs is that sequence of objects deletion is important. It is important in order to be kept away from situations when it is not possible to delete some object due to its dependency. One of the way that can help to explore the object’s dependency is Transport Connection. Other way can be a various Where-Used functions for particular BW object.

Examples of some object’s dependency can be:

Process Chains cannot be deleted if objects used in them (DTPs, InfoPackages) are not deleted. Sequence would be, delete DTPs, InfoPackages prior the PC deletion.

Correction (Thanks to comment from a reader of the blog):

Particular objects like DTPs, InfoPackages included in the Process Chain cannot be deleted if the objects are used in them PC. Sequence would be delete the chain prior the DTPs, InfoPackages etc. deletion.

InfoSource or transfer structure must not be deleted before corresponding data sources are deleted. Otherwise it won’t be possible to delete the InfoSource/transfer structures.

 

More information:

2390883 - Clean up system to migrate to B4HANA

1112972 - RS_DELETE_TLOGO using BI InfoSets

2478346 - BW4SL - Other Front-end Objects