cancel
Showing results for 
Search instead for 
Did you mean: 

No authorization to send IDocs with message MATMAS

Former Member
0 Kudos

I have XSDL from MDM to post MATMAS into R/3.

I tested the whole scenario in Config and its working fine. I can also see a checquered flag in SXMB_MONI. Nevertheless, my outbound status seems to be in RED flag with a message No authorization to send IDocs with message MATMAS.

Am I missing something with regards to authorizations in XI or R/3 End?

Thanks

Shiva

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

solved

Former Member
0 Kudos

hi shiva

In XI , you have configured an RFC destination in Sm59 for the SAP system . You post the Idoc to the SAP using this RFC destination,.

The user id and password given in this RFC destination is that of your R3 user id and password. So, the authorizations of this user id does not match with the authorization needed to post an idoc. and the authorizations would be needed to be added by your R3 team to this user id.

Please refer to this note for the authorizations, 837595

note:reward points if solution found helpfull.....

regards

chandrakanth.k

Former Member
0 Kudos

Hi,

For configuring/Receiving IDoc to target system, U must have the following Authorizations in receiving system.

S_IDOCCTRL - General Access to IDoc Functions

S_IDOCDEFT - Access to IDoc Development

S_IDOCMETA - IDoc Metadata: Load and Display IDoc Metadata in XI

S_IDOCMONI - Access to IDoc Monitoring

S_IDOCPART - Access to partner profile

S_IDOCPORT - Access to port descriptionS_IDOCREPA - Access to Repair Programs

RFC, Port creation, Partner Profile generation, Logical system creation... etc are single time configuration steps. ensure that the sender/receiver steps are defined properly in Ur source/target systems.

Thanks

Swarup

Former Member
0 Kudos

swarup,

all these are already added to the respective user.

but then, why is the idoc posted with 51 status?

Former Member
0 Kudos

1. Check whether RFC destination exists between XI and R3.

2. Also check you are working in right SWCV and Namespace.

also see Thread:

"IDOC error: No authorization to send IDocs with message type MATMAS in SM58 " on XI forum.

BR,

Alok

Former Member
0 Kudos

hi alok,

i checked all of them

its not working still

any more?

Former Member
0 Kudos

See the thread's last answer, you need authorization for all Idocs S_IDOC_ALL. just check it with your basis guy.

Regards,

Alok

Former Member
0 Kudos

i had them added to this user id.

any more clues please

aashish_sinha
Active Contributor
0 Kudos

Hi,

what is the status in BD87?

Have they been sent?

If so, check the queues in SMQ1 and SMQ2.

Also, Check BD75

Regards

Aashish Sinha

PS : reward points if helpful

Former Member
0 Kudos

Our basis guy have given some roles and that problem is solved now.

Now i have one more problem.

i checked in BD87 in R/3.

i can see them in 51 status. application document not posted.

message: Messages have been issued: number 0000000000202012

what is the reason for this?

thanks

siva

Edited by: shiva g on Mar 24, 2008 10:18 AM

aashish_sinha
Active Contributor
0 Kudos

Hi,

You use the IDoc Adapter in the Exchange Infrastructure and you try to use the IDocs to receive or send data. For these IDocs, an attempt is made to load the IDoc metadata from an R/3 reference system with an SAP NetWeaver Release lower than 6.20.

This occurs either at runtime, whereby the relevant messages run into 'System error' status, or when you use transaction IDX2 during manual loading of the metadata. In this case, the reference ystem is called by RFC and the logon user of the RFC destination does not have the necessary authorizations for determining the metadata.

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

this will solve your problem. For why it happened , do googling [:)]

Regards

Aashish Sinha

PS : reward points if helpful

Former Member
0 Kudos

basis guy has given sap_all on a temporary basis for testing purpose. so do u think i need to extend the user with all those roles u have given?

aashish_sinha
Active Contributor
0 Kudos

Yes !!!