User has no authorization to send IDOCS of type

[Former Member]

Hi Gurus,

I am sending an IDOC of type OILDEB02 from XI to R/3. I have done the configuration (we20, we21 etc). The message is processing successfully and not reaching the R/3.

When I checked in IDX5, after cclicking the 'transaction id', i see this message.

Caller: XIAFUSER

No authorization to send IDOCS of type OILDEB02.

Do we need to create the XI service users in the R/3 system?

I wanted to know what is missed in this configuration?

Thanks

Kalyan

[bhavesh_kantilal]

Kalyan

You are sending IDOC from XI to the R3 system and so you need the authorizations to pos the IDOC's in the R3 system.

You need to create an User id in your R3 system ( can be a service or a dialog user id -- Using Service User id is better though ) with the auhorizations mentioned in the Note : <b>837595</b> . This user id and password should be used in the RFC destination you have created in XI for the r3 system.

Regards,

Bhavesh

[Former Member]

Bhavesh,

Thanks for the reply. It was helpful. When I am sending the IDOC from XI to R/3, I have disabled the EDI_DC40 in the mapping so that it could automatically get the control record from XI.

So, it looks like XI is using XIAFUSER to send the IDOCS from XI to R/3, even though I have speicified my user id in the RFC destination created for the R/3 in XI.

From your reply, it is clarified that I need to create the service user XIAFUSER in the R/3 system to which I am sending the IDOCS to.

Please confirm this.

Thanks

Kalyan

[bhavesh_kantilal]

Kalyan,

>><i>it looks like XI is using XIAFUSER to send the IDOCS from XI to R/3, even though I have speicified my user id in the RFC destination created for the R/3 in XI.</i>

In the RFC destination, did you select CURRENT USER? Please do not select this. If you do not select Current user, the User id and password used in the RFC destination would be used to post the IDOC.

<i>it is clarified that I need to create the service user XIAFUSER in the R/3 system to which I am sending the IDOCS to.</i>

You need to create a Service User id or even user your own user id with the credentials pointed out in the Note I have mentioned in my first reply. This should be an R3 user id.

do not select Current User and let me know.

Regards,

Bhavesh

[Former Member]

Bhavesh,

I have not selected the 'current user' option. I will create the XIAFUSER in the R/3 system and try using it in the RFC destination to the R/3 system. And let you know if there is a problem.

Thanks

Kalyan

[bhavesh_kantilal]

Kalyan,

You need not create the XIAFUSER in your R3 system .

According to sap Note : 837595 , this is what you would need to do with your Log On user id of the R3 system,

<i>In transaction PFCG, extend the role of the logon user by adding the following authorizations:

Authorization object S_RFC

Field name RFC_TYPE value FUGR

Field name RFC_NAME value EDIMEXT, SDTX

Field name ACTVT value 16

Authorization object S_IDOCDEFT

Field name ACTVT value 03

Field name EDI_CIM value ' '

Field name EDI_DOC value TXTRAW01

Field name EDI_TCD value WE30

Authorization object S_CTS_ADMI

Field name CTS_ADMFCT value TABL

Authorization object S_TABU_DIS

Field name ACTVT value 03

Field name DICBERCLS value

Note: You can activate the display of the technical names of objects and fields in authorizations maintenance by choosing the 'Technical Names' function from the 'Utilities' menu.

Then save and execute the 'Generate' function. Then choose 'Back' to return to role maintenance and switch to the 'Users' tab. Press the 'User comparison' button to execute this function.</i>

I repeat, I dont think you need to create an user id with XIAFUSER on R3.

Regards,

Bhavesh

[Former Member]

Bhavesh,

I have my user id and password in the RFC destination to R/3 system. I have not selected the 'current user' option either.

I don't know how the user XIAFUSER is sending the IDOCS. I am totally confused aroung this. Even in the runtime parameters it is showing XIAFUSER as the user. See the below messages.

SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SAP:Date>20061023</SAP:Date>

<SAP:Time>195926</SAP:Time>

<SAP:Host>xxxx04</SAP:Host>

<SAP:SystemId>xD3</SAP:SystemId>

<SAP:SystemNr>76</SAP:SystemNr>

<SAP:OS>Linux</SAP:OS>

<SAP:DB>ORACLE</SAP:DB>

<SAP:Language />

<SAP:ProcStatus>003</SAP:ProcStatus>

<SAP:AdapterStatus>007</SAP:AdapterStatus>

<SAP:User>XIAFUSER</SAP:User>

<SAP:TraceLevel>1</SAP:TraceLevel>

<SAP:Logging>1</SAP:Logging>

<SAP:LogSeqNbr>008</SAP:LogSeqNbr>

<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>

<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>

<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>

<SAP:PipelineElementId />

Please help me in this regard.

Thanks

Kalyan

[bhavesh_kantilal]

Kalyan,

Are you trying a File to IDOC ? In that case, as the file adapter would have started the processing of the message in integration engine , you have the XIAFUSER as the User in Trace .

The IDOC will be sent out only by the User id in your RFC destination. Just check for the following,

1. The rfc destination and port in the IDOC adapter are the valid ones you have created for the R3 system in Sm59 and IDX1 respectively

2. Go to IDX2 and try to manually import the Idoc metadata. See if this is successful.

3. In the RC destination in Sm59, try a test connection and remote log on.

4. Finally check if the user id has the roles mentioned in my porevious reply and if yes, things should work.

Regards,

Bhavesh

[Former Member]

Bhavesh,

I am using File to IDOC interface.

I have checked all the items you mentioned. Everything is working as expected.

<i>1. The rfc destination and port in the IDOC adapter are the valid ones you have created for the R3 system in Sm59 and IDX1 respectively

***THESE ARE VALID

2. Go to IDX2 and try to manually import the Idoc metadata. See if this is successful.

• MANUAL IMPORT IS SUCCESSFUL

3. In the RC destination in Sm59, try a test connection and remote log on.

• TEST CONNECTION AND REMOTE LOG ON WERE SUCCESSFUL.

4. Finally check if the user id has the roles mentioned in my porevious reply and if yes, things should work.

• I didn't check this on. But there was no error regarding my user id.

</i>

After I run the interface, XI is showing the processing successful and the IDOC is not received at R/3.

When I checked in IDX5 in XI, after clicking the transaction id, the message is saying that -

Caller XIAFUSER

Function module: IDOC_INBOUND_ASYNCHRONOUS

Target system: R/3 SYSTEM RFC destination I have created in XI

Status text: No authorization to send IDocs with message type OILDEB

Any thoughts??

Thanks

Kalyan

[bhavesh_kantilal]

Hi,

>><i>After I run the interface, XI is showing the processing successful and the IDOC is not received at R/3.</i>

Go to transaction SM58 , and check if there is any entry for TRFC errors. This will give us the reason why the IDOC was not sent to the R3 system.

Also, make the User id as * in SM58 while searching for TRFC errors / log.

Regards,

Bhavesh

[Former Member]

Kalyan,

Make sure that in the RFC destination from your XI server to R/3 system is using user existing in your R/3 system. Also this user id of R/3 system should have all the IDoc related transactional authorization. Pls do check this.

Cheers

JK

[Former Member]

Bhavesh,

SM58 has the same error as I explained. It is showing caller as 'XIAFUSER' even though I have used my user id in the RFC destination to R/3 system.

Thanks

Kalyan

[Former Member]

Bhavesh,

I am not mapping to any of the EDI_DC40 fields for the IDOC. Is that a problem?

Thanks

Kalyan