Skip to Content

BRF+ Transports fails with errors then BRF+ application inactive in target system.

Issue Explanation: When we import BRF+ application using transport from Dev system to SIT/UAT/Prod if transports imported with return code 12/8 then in target system that BRF+ application will be in active.

Then we have two options to fix issue

1. Using FDT_HELPERS tcode we can re import failed transports then it will activated BRF+ application in SIT/UAT/prod

Or

2. Create new transport with BRF+ application and import to target system if new transport import successful into target system then it will activate BRF+ application in Target system.


Here I am covering first option next blog I will cover second option

Step 1:

Please prepare transport before release

Transport.png

Step 2:

Then Release Transport in Source system

Transport.png

Step 3:

Please inform Basis to run import job to target system

Step 4:

Check transport import log

Tcode: SE01

Provide your transport and click on Log Tab

Transport.png

Step 5:

Transport fails with return error code 8

Transport.png

Step 6:

Open BRFPLUS workbench and check BRF+ application it will be inactive mode in target system

Transport.png

Step 6:

Login into target system and Open FDT_HELPERS tcode in target system

Transport.png

Step 7:

Expand BRFplus –  Transport

Transport.png

Step 8:

Select BRFplus: Transport phase Execution

Transport.png

Step 9:

Click on Execute

Transport.png

Step 10:

Next you will see below screen

Transport.png

Step 11:

Provide your transport like below and select radio button After import Processing then click on Execute button

Transport.png

Step 12:

It will show you result is successfully generated BRF+ application in target system

Transport.png

To report this post you need to login first.

8 Comments

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

  1. Anindya Chaudhuri

    Running this report may not solve the issue always. But even if the issue is not solved, it will show the error messages that you can check and analyze. The same error messages can be found in transport log.

    Use FDT_TRANS_MASS_CHECK to analyze and correct Before Export problem (Source System)

    Use report FDT_TRANS_Q_RESTART to restart the after import processing for all yet not activated transports.(Target System)

    Use report FDT_TRANS_MASS_CHECK to search and classify meta data content inconsistencies.

    Use report FDT_DCONV_0012 to fix inconsistent entries of the transport queue, is there is any.

    Also, try to analyze the TR log from SE09 or log in STMS.

    (0) 
    1. Christian Lechner

      Hi

      the report FDT_DCONV_0012 is not part of the FDT_HELPERS transaction. It is linked to note1387939 (which references some other notes). So I would handle that report with care as it is not part of the official collection of helper reports.

      Cheers

      Christian

      (0) 
    2. Rajesh Vadde Post author

      Thanks for our comments Anindya.

      As i mentioned in above blog this is just one option if this option is not resolving issues we have to go with option which you mentioned. Soon i will post that option as well.

      Once again thank you very much for your comment.

      Thanks,

      Raj

      (0) 
  2. Mariel Claus

    Hi,

    I´m having problems with transporting rules within development system with scc1. It does´t return error 8. It returns code 4 but changes are not transported.

    Can you help on this please?

    thanks,

    Mariel

    (0) 
    1. Christian Lechner

      Hi Mariel,

      can you please ask that question as a question in the Business Rules Management Space. The Comments on a blog are not really fitting for this kind of request

      BR

      Christian

      (0) 

Leave a Reply