Skip to Content
Oct 26, 2011 at 10:16 AM

Truncate versioning of BRF+ applications


Hello forum,

We are on RU EHP05 and are seeking some guidence for the following problem:

I notice that when you truncate/discard versions of a BRF+ application in the development system, the information is not conveyed to the taget systems through the carrying transport requests - i.e. I have an application which has no inactive versions in my DEV AS (discarded with FDT_TRUNCATE_VERSIONING), but when I check the QAS AS after the import, I see that inactive versions still exist.

Effectively, this prevents me from deleting some objects in BRF+, because the target often complains about the existence of usages. The usages are in the inactive versions, but I am confused here, because I thought FDT_TRUNCATE_VERSIONING will discard them, and the transport system will convey the new state of the application to all the targets.

To be completely clear, I do manage to delete these objects, but they are not deleted in the target - only marked for deletion. However, I would like to have identical objects in all the systems.

The question is, how do we discard the inactive versions in our target clients? Is it possible to force this?

I tried doing it with the same FDT report, but it didn't work, and this really isn't the right approach, because traget clients are usually locked for customizing changes. While unlocking may be an option for some sandbox types of clients, we wouldn't want to do it for QAS, and even less so for productive clients.

Thanks in advance, and plz come back to me with any further questions.



Edited by: Srdjan Danicic on Oct 27, 2011 11:40 AM