cancel
Showing results for 
Search instead for 
Did you mean: 

Transport Fails with Transfer Method 'TRFC with PSA' is not supported by the Source System

0 Kudos
393

I am making a small code change to a custom routine in a Transfer Rule (for 0COSTCENTER_ATTR). When I transport the change to BWQ the transport has the error RSAR508 Transfer Method 'TRFC to PSA' is not supported by Source System.

This is a very longstanding dataflow (its still 3.x) and has worked for years. The transfer rule is already set to PSAand has been for a long time.

I have run a check on the source system and it comes up with no errors.

The transport does actually apply the code change and I can activate the transfer rule by running the activate program via SE38. It then works fine. I want to understand though why I am getting this error as I can see no reason for it.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member

Hi Joel,

Please check

SM59 > Open RFC connection to Source system > Top menu > Utilities > Test > Authorization test

Also check if the Client/User is maintained correctly for this RFC connection here.

538052 - Maintenance of Myself destination in BW

Best regards, Andras

0 Kudos

Hi Andras,

Thanks for your reply.

From BWQ I have tested in SM59 both the connection to ECC and BWQ Myself. I have tested remote login, connection test and authorization test and all work.

If its a transport from BWD to BWQ why do I need to look at the Maintenance of the Myself destination in BW?

The one thing that I have noticed is that the user in the SM59 connection for the BWQ myself RFC has been changed to a system user from a dialog user. Will that make a difference as the note states "The entered user must be a dialog user".

Former Member
0 Kudos

Hi,

If source system is BWD, check the RFC connection to BWD if authorization test is OK and Client/User is correctly maintained.

Best regards, Andras

0 Kudos

Thanks again for replying.

The RFC connection from BWD to BWQ or BWQ to BWD or both?

To be honest I cant see that we have configured an RFC from BWD to BWQ or vice versa.