Skip to Content

The application SAP BusinessObjects Planning and Consolidation version for Netweaver (SBOP PC NW) contains delivered functionality to transport configuration.  In some cases transports may fail and the only way to correct the issue is to delete an appset and re-import it.   This blog lists the steps that I found successful in performing this activity.

 

Note: this process will effectively delete the appset in the target system; all master and transactional data will be destroyed!  Be sure to make backups of master and transactional data to so that they may be entered back into the restored appset! 

 

The situation:

Configuration for an appset had been transported into the target system.  At some point in the project the source system was refreshed leaving the old configuration in the target system. Attempts at reproducing the old configuration in the source system, then transporting the deletion, provided ineffective – primarily due to the difficulty of controlling the generated technical names of newly created BPC objects. The decision was made to delete the entire appset in the target system and re-transport the new configuration. 

 

The steps that needed to be taken to delete the appset are listed below.  All steps that were needed are listed below.  If you attempt this, please follow all steps in sequence.  Pay close attention as to which steps are executed in which systems!

 

1.  Target System only:  Delete the appset in the target system by using the delivered program (SE38):  UJS_ACTVIATE_CONTENT.  Enter the AppSet Id and uncheck all options except for “Delete the Appset”: 

 

 

image

 

 

2. Source and Target systems:  Delete all entries (source and target systems) in the tables ujt_trans_hdr and ujt_trans_obj by running the program (SE38) : UJT_DLT_TRANS_DATA.  Select the appset to be deleted (you may need to type the Appset name directly into the prompt box):

 

image

 

3) Target and Source Systems:  Verify that all table entries for the appset have been deleted.  Run program (SE38) : UJT_CHECK_TABLE_ENTRIES.  Enter the Appset name and UJ* to capture all BPC tables.

 

image

 

Target System: all UJ tables should indicate 0 rows

Source System:  Check that tables ujt_trans_hdr and ujt_trans_obj indicate 0 rows:

image

 

4. Only after steps 1-3 are completed: create a new transport (t-code: UJBPCTR) in the source system for the appset and release to the target system.

 

image

 

 

Note: this process will effectively delete the appset in the target system; all master and transactional data will be destroyed!  Be sure to make backups of master and transactional data to so that they may be entered back into the restored appset!

To report this post you need to login first.

6 Comments

You must be Logged on to comment or reply to a post.

  1. Jay Roble
    Having to delete an Appset seems pretty drastic to me. And a bad design.

    If we had to delete our order data table in our ECC system to do a transport, I think that system would be out the door.

    Also seems like a lot of extra work & risky for some thing that should just WORK!

    (0) 
    1. Sheldon Edelstein Post author
      I appreciate your comment, but please bear in mind that the situation that caused the development of this process was somewhat unusual and not typical.  In my experience BPC transports do in fact work.  For the unusual situation I described the procedure (admittedly somewhat extreme) was the most efficient solution.  My intent was only to share a process that worked in this unique situation.
      Regards,
      Sheldon
      (0) 
  2. Vinod Swarnapuri
    As Jay commented, this is not something that anyone would expect in a enterprise system…. that too a system where the legal consolidated data has to be stored.
    (0) 
  3. Jeffrey Holdeman
    Just wanted to share an experience from another BPC 7.5 SP03 customer…when they ran the appset deletion step using program UJS_ACTVIATE_CONTENT it did not delete the system-generated journals table for each application.  Consequently the transport import would fail.  This situation required the journals tables be dropped manually.  But subsequent import of the transport was successful. My understanding is the problem with these unwanted tables will be fixed in SP05.

    Best regards,

    Jeffrey Holdeman
    Americas Applications Regional Implementation Group (RIG)

    (0) 
  4. Sheldon Edelstein Post author
    When attempting to delete an appset make sure all BW configuration has been disconnected from any BPC objects prior to attempting to execute the deletion function.  BW objects, such as DTPs and Queries can lock individual BPC objects and prevent the deletion process from executing completely.
    (0) 
  5. george chen
    it should be UJS_ACTIVATE_CONTENT, not UJS_ACTVATE_CONTENT.

    anyway, this one more option for us to do. it is good and dangerous. we need to be careful.

    (0) 

Leave a Reply