"TRFC with PSA not supported"

[Former Member]

Hello all,

When I try to import a transport request (consisting of a transfer structure of info source 0EC_PCA_1) into my production environment I get the following error message:

"Transfer method 'TRFC with PSA' is not supported by the source system"...

I also get the message that I should "Define the PSA in the source system".

How can I solve this?

Best regards,

Fredrik

Message was edited by: Fredrik Carlsson

[Former Member · Accepted solution]

Fredrik

It seems your transfer structure is not active in the Production. Please check this also look at this thread

Hope this helps

Thnaks

Sat

[Former Member · Accepted solution]

Thanks Sat,

The error message mentioned comes vhen trying to activate it...

I also get this error message:

" Start of the after-import method for object type R3TR ISFS (Aktiveringsmodus)

RFC connection to source system ARPCLNT300 is damaged ==> no Metadata upload"

What can I do about this?

BR,

Fredrik

[Former Member · Accepted solution]

Thanks,

The error occurs whenever I try to import something that relates to the transfer structures...

It must have to do with some setting somewhere?

Thankful for some assistance!

BR,

Fredrik

[Former Member · Accepted solution]

Fredrik

Do you have any issues to load data from R/3 to BW in Production system for other infosources because in your error message it says RFC connection to source system is damaged so what I am see here is source system connection problem in the Production system. Please check this and update.

Thnaks

Sat

[Former Member · Accepted solution]

Hello Sat,

I haven't loaded any data at all. The problem occurs when doing the transports into a fresh production system. I hasn't been used before, so I'm sure that the problem is related to errors in the connection between the BW prod system and the R/3 prod system (source system)...

However, the RFC connection seems to work (I performed a test)..

Do you know where to look for this error?

BR,

Fredrik

[Former Member · Accepted solution]

Hi,

I am curious about that question, because I am facing the same issue for more than a month.

Each time we import a transfer rule, the system is not able to activate it... So we have to do it manually.

Usually this error is linked to an authorization issue...But I can not find any evidence...

Fredrik, what kind of security rules do you have between your BW and the source system??? Do you use a ALE remote user ? or do you force the connection with the login and password of the connected user??

I am pretty lost in that problem....

Pierre-Yves

[Former Member]

I know these are old posts but notice they are still not answered.

I am get this error now and then and when I go and manually activate in our test system the activation works.(Open system and just activate) Before I knew about program below.

You can use this program: in sa38

RS_TRANSTRU_ACTIVATE_ALL

These prompts are given:

Source System:

InfoSource (* gen):

so if there are no errors with RFC Connections and etc. you can try running this program.

Mike