Transports failure: Objects getting imported in target system

[Former Member]

Hi All,

Im facing a scenario, where Input schedules / reports are getting copied / imported from source system into target system, even when the TR request fails wit RC=8.

Now, I know that while transporting , Data entries from Dev system are only imported during the transport and then the program UJS_ACTIVATE_CONTENT program gets executed in target system rebuilding applications, dimensions etc based on the imported table entries.

In our case, we faced an issue "CPMB Name space error" (which we were able to rectify) but unfortunately, all templates fin target system were overwritten with templates from source system.

My doubt is , if the transport fails, the UJS_ACTIVATE_CONTENT program wouldnt have run and only import of table entries would have taken place.BUt how did the templates get overwritten?

Any useful pointers will be of great help.

Thanks in advance,

Sridhar

[Former Member]

Hi ,

Just Adding .....

SAP has released a note ,_1356959 - Rollback if fail to create application during transport_, which is part of BPC NW

SP04 release to rectify this problem of dirty entries ,incase of a failed transport request.

Thanks

Sridhar

[RichHeilman]

My doubt is , if the transport fails, the UJS_ACTIVATE_CONTENT program wouldnt have run and only import of table entries would have taken place.BUt how did the templates get overwritten?

Hi, first it is important to understand that when importing the TR into the target system, the UJS_CONTENT_ACTIVATION program is NOT called. UJS_CONTENT_ACTIVATION is only used for installing APSHELL. This program does leverage the underlying BPC transports framework though, which is called when importing a request.

Basically, what happens is the request is imported, this request only contains table entries. The entries are written to the shadow tables. THe "after import" method for BPC Appset, then reads theses shadow tables and writes them to the UJ tables, as well as creates the underlying BI objects.

Now to answer your question, it will usually be the after import method that is actually failing or sending errors. Not the actual import of the TR, since it is only table entries. So the import of the request is succesful, but the after import method fails, and in your case, the kind of error may not be handled gracfully, and hence creates an ABAP dump, which stops execution of the after import method without allowing it to clean up things, like in a ROLLBACK situation.

Regards,

Rich Heilman