Transport BRF+ Application from $Temp packge

I am not sure if you have already come across the phase associate with Copy the BRF+ application from $Temp package in order to make it transportable.

At the start of my implementaion project on GRC V:11 and SAP:04, I had created one BRF+ application and saved it to a $Temp package so as to avoid to capture it into a Transport Request, as I had to do some more configurations with the never ending requirements. So, when I completed all the configurations, I tried to put into TR which But couldn’t fo that as I had saved it into $Temp so, got stucked.

So; to make an application transportable you have to follow these below steps:

1) Copy the application from $Temp package to SAP Development package

Execute BRF+ transaction code –> Navigate to the application which is saved into $Temp package

Application1.png

2) Right click on the application –> Copy

/wp-content/uploads/2014/06/copy_474210.png

3) On the new screen, enter the New-Application name (target application name), description and short text.

You need to make sure to uncheck the box for “Create Local Application”. Missing in doing it, you would agai end up copying the targer application into $Temp package.

/wp-content/uploads/2014/06/copy1_474211.png

If you have created a package specifically for BRF+ then you can mention the package name under “Development package” . If not, then you can create with transaction code: SE21 as below:

PACKAGE.png

/wp-content/uploads/2014/06/package1_474213.png

Fill in all the required details and confirm.

Now, after putting the development package, mention the Softwarre component and make sure to confirm the check box for “include contained objects”. Click Copy.

It will ask to enter the TR, but you would see the error screen as below:

/wp-content/uploads/2014/06/transport_474214.png

This is due to a bug within the GRC V:11 which would get resolved after implementin SAP Note# 2029700 http://service.sap.com/sap/support/notes/2029700

Thanks to SAP to provide this note, and now I am able to copy the application from $Temp package to SAP Development package to make it Transportable.

Thought of to share this experience with SCN-Community members to help them if they came across with this issue.

Cheers!!

Ameet

To report this post you need to login first.

5 Comments

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

  1. Colleen Hebbert

    Hi Ameet

    That’s awesome news and thanks for sharing! For too long their advise is to go create the Application in BRF+ firs and then come back to IMG to generate the functions, etc

    I just with the creating rules in IMG had an option to specify transport first up so it would not end up in the $TMP directory

    My one was when I wanted to clean my transports and not able to find in BRF+ where to create a new transport. I found SE38 program BRF_TRANSPORT but haven’t tested it out

    Regards

    Colleen

    (0) 
    1. Ameet kumar Post author

      Hi Colleen,

      I am glad to know that you found my document as useful.

      Yes, I understand about the complexities involved with BRF+ applications transport management especially when you have it saved it locally and I know the pain better than anybody else in here 🙂

      I haven’t tried yet with BRF_TRANSPORT, but as far as I know you need to mention the Application class from flight demo or system, which I am not aware of and so would give it a try too.

      Warm Regards,

      Ameet

      (0) 
  2. Harinam SanKirtan

    Nice article,

    I presume that the Function ID gets changed also during the “copy”, therefore you need to add the new BRF+ rule as a new agent in MSMP and alter the path/stage settings and replace the old “local” agent with the new “transportable/copied” agent.

    Let me know if this is the case.

    (0) 
    1. Ameet kumar Post author

      Hi Hari,

      Sorry for this late reply.

      Yes, Rule ID will get changed each time you copy application to a new one and then you have to map this new ID with the MSMP instance accordingly.

      Regards,

      Ameet

      (0) 

Leave a Reply