Sometimes an environment deleted by the standard BPC operation, such as the Web Administration or the report UJS_ACTIVATE_CONTENT (clean option) leaves scrap data in the system.
This may be identified by /CPMB/<Environment Prefix> objects under unassigned nodes, or tables left under /CPMB/, /1CPMB/, or /B28/ namespaces that were related to the original environment.
While restoring or transporting an environment one may face issues such:
•"Environment <Environment Name> already exists with the prefix /CPMB/<Prefix Code>"
•"Table /1CPMB/<Object Name> already exists"
•"InfoObject /CPMB/<Object Name> already exists"
Steps to run the report:
1.Logged at the Netweaver backend, in the BW client go to transaction SE38:
2.Execute the report UJAA_CLEAN_DELETED_APPSET.
3.Parse the parameters:
a.APPSET: This is the original name used by both BW and BPC to refer to the Environment/InfoArea. If one don't know for sure the environment name, the tables generating the exception might hold this information in one of its fields.
b.APPS_PFX: This is the environment's technical name prefix. The prefix is the first 2 characters after the /CPMB/ namespace tag for almost every BPC object. For instance, a BPC dimension with technical name as '/CPMB/RUDZ1VW' belongs to an environment named SAP_PLANNING.
c.The parameters for UJAA_CLEAN_DELETED_APPSET in this case would be:
APPSET = SAP_PLANNING
APPS_PFX = RU
4.Execute.
5.Check if the affected scrap data has been removed from the system through the BW workbench and checking the affected BPC internal tables.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.