Runtime error RFC_NO_AUTHORITY has occurred while ...

Hi All,

I have one IDOC to file scenario.

It was working fine in Develpoment.

But in QA it is failing in SM58 as Runtime error RFC_NO_AUTHORITY has occurred.

Same error i am getting when i am trying to create metadata in PI (quality) box.

I have checked with my basis ,and they are telling they have provided SAP_ALL role to RFC user in PIQ.

Weird thing is this,other IDOC to file scenarios are working fine which was imported earlier.

Could you please help me.

Regards,

Monika

SAP Managed Tags:
SAP Process Integration

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (9)

HI All,

Problem solved.

It was because of the idoc meta data program IDX_META_SYNTAX_READ.

While updating the meta data ,This program was taking the RFC destination of the old client.

After debugging the program, we got to know. then in program we chnaged the port value.

and it worked.

I guess,the value was not refreshed from cache.so we have to do it manually..

Thanks for all your support

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

You are welcome....

Good that you solve issue...

so its turn out that that was not authorization issue...

ST22 give you Idea where to start looking...

--------------

|RE|RFC_ERROR_SYSTEM_FAILURE

|CT|No RFC authorization for function module IDX_META_SYNTAX_READ.

|CR|INCL_RFC_ERROR_SYSTEM_FAILURE

---------------

Cheers,

Yogesh

Hi All,

Do we need to create a TCP/IP connection RFC also for IDOC adapter in ECC.

I just checked in DEV ECC and found a TCP/IP RFC which is pointing to the PID.

And it is not present in QAS ECC though DEV ECC connection test is failed.

I am not sure about that,could you please share some thoughts.

I read Micheal's blog http://scn.sap.com/community/pi-and-soa-middleware/blog/2010/10/21/pixi-pi-73-new-java-based-idoc-ad...

Came to know that TCP/IP RFC is for Idoc_AAe Adapter but i am not using that.

I am still using Idoc adapter(Abap)One.

So i guess this is not relevant to my issue but any thoughts are most welcome.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hello

Please save file attached to this message. Change file extention to .SAP from .txt. Upload this role through PFCG and assign to IDOC user and try again.

Thanks.

Yogesh

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

JFYI

Adding sap_all will not give required RFC authorization(s_rfcacl), we need to provide it explicitly, educate your basis also.

Try using above role/adding the objects I suggested (Both same).

Hi Yogesh/Jayadeep,

I have forwarded th message to my basis,Lets see what happens.

Between i would like to inform you,my other sap outbound interfaces are working fine except this new scenario.

Hi Yogesh,

Basis has confirmed that they have provided this authorization to RFC user.

so still my issue is unresolved.

Regards,

Monika

Hello Monica,

Can you please attach error message screenshot to this so I can take a look.

Thanks

Yogesh

Hi Yogesh,

Pl find the error shot.

Thanks for all your support

Regards,

Monika

Hello Yashwant,

Can you please check in ST22 that there is no error log created for this error.

If Yes, please provide log.

Thanks

Yogesh

HI Yogesh,

Pl find the log from ST22.

Hi All,

The connection test and authorization test is successful in RFC destination in both PI and ERQ.

Regards,

Monika

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

You need to give authorization objects s_rfc and s_rfcacl to RFC user in target system to resolve the issue.

Regards,

Jayadeep

Hi,

Is authorization test for rfc destination in ecc system is successfully ?

Regards

Hari.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

A few cents,

Have you checked the RFC destination for the IDOC has the Logon Screen option unmarked?

Regards

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Monika,

you need to corresponding authorizations inside the SAP system (user which you put inside the destionation used for the port).

Regards,

Udo

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Udo,

Checked user in SAP system also.It also has sap_all authorization.

Hi Monika (is that your name?),

test the destination. Try to replace the user in the destination (the destination in PI pointing to backend which you use for port / IDX1). Check if you can log on remote. Something must be wrong with the user.

When you execute a message for the first time, PI will automaticly request the IDoc meta data via that destination. If you ve send that message from the backend you will see exactly this error message there in SM58 what is a bit confusing.

Regards,

Udo

Hi Monika,

Check whether connectiont test is working or not for RFC destination in SM59 in ECC. If connection test fails then problem with RFC destination.

Regards,

Arindam

Hi Arindam,

connection test is successful

Hi Udo,

i forgot to mention a imp detail.

For this perticular scenario,We are using IDOC sender communication channel as we are doing bundling of idocs.

The interface is working fine in Dev but failing in QA.

Our Dev is in 7.3 but QA in PI7.31.

Am i missing any important setting?

Regards,

Monika

Hi Monika,

the difference in release versions is unusal, but anyway, you could suffer other problems, for example java mappings which run on one system but not on the other. I think in long term it might be recommendable to go for the same release versions.

There are some OSS notes handling RFC authorization errors as far as i remember. You should search for the error msg in OSS.

But is the error still coming up if you replace the user in the destination (which points from PI to SAP)?

Regards,

Udo

Ya i know it is unusual..

We'll upgrade the DEV very shortly.

between,i asked my basis to replace the user,they'll come back shortly.

Hi Udo ,

No luck,Same problem after replacing the user.

Hi Monika,

It might not be a matter of the PIAPPLUSER user. Check the RFC destination in sm59 in ECC, to see which PI user is maintained there. This is the user that is used for connections. And this is also the user that you should check the authorizations of.

Regards,

Greg

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Greg,

I have checked the SM59 in ecc also.

That user has all the roles and authorization.

I have checked authorization check also.everything seems alright.

It has SAP_ALL authorization.

Regards,

Monika

HI Yashwanth,

Check this thread about the same issue: http://scn.sap.com/message/6656061#6656061

What user have you assingned the SAP_ALL role?, Have you checked the SAP_ALL authorization to the PIAPPLUSER?

Regards.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

HI Inaki,

Ya ,SAP_ALL has been provided to PIAPPLUSER.

and scenario which was configured earlier and transported to QA is working fine.

i am facing this problem in a new scenario.

In development, it is working fine.

Basis has confirmed that they have provided all the neccessary authorization to all the user.

Ask a Question

Top Q&A Solution Author

User

Count