I was recently working with a customer which uses the Transport Express (TE) tool for transporting changes through their BPC landscape. Their requirement was to update Development and Quality systems using Production in order to align the technical name of all the BPC dimensions and attributes.
Following are the steps I had to take to ensure a successfully restored system using the Production backup file.
1) Disable the Transport Express settings.
This step will require a Basis Resource to perform the disabling.
This is a mandatory requirement as whenever a change is made in the system (in this case delete) it will trigger a TE request in the background but the deletion log was not capturing this and the successful delete message was in fact misleading.
2) Delete the BPC Environment that needs to be restored by using the program UJS_ACTIVATE_CONTENT and selecting “Clean the Environment”
3) Make sure that the /CPMB/”Environment ID” node is deleted
4) Check that all the BPC items are deleted by checking that there are no items with a technical name starting with /CPMB/* under the “Unassigned Nodes”. If the Transport Express tool was active when executing step 2, you will find items here.
Following is an example of 2 items that were not deleted but moved to “Unassigned Nodes”
5) If there are scrap items that were not cleared, use the program UJAA_CLEAN_DELETED_APPSET to delete the items.
APPSET: is the Environment ID
APPS_PFX: this parameter is the environment’s technical name prefix. The prefix are the first 2 characters after the /CPMB/ namespace. In the following example the values are “FU”.
Example of technical name prefix
6) If the log shows items were not deleted then manually delete the remaining items (this might require you to delete some internal tables as well, the reference of the table will be indicated in the delete log).
Example of log
7) When all items for the environment that need to be restored are deleted, run transaction UJBR
It is important to select “Use Tech Names from Backup Files” in order to maintain the same technical names.
In our case, we had to load the backup file on the server /usr/sap/trans/ as the file was 1.4 GB and the program would error when it was trying to read from the local PC.
The restore will start with building the BPC structures and then load the master data. In this example I restored both Metadata and Master Data at once but this uses up a lot of resources and I would overall suggest to Restore Metadata Tables first and then Master Data.
8) The ultimate check is to connect to the BPC admin and see if all the models, dimensions, business rules etc are visible. If all the structures are in, go into each dimension and check whether the master data is in.
9) Reactivate the TE tool.