<IDOC_ADAPTER> ATTRIBUTE_IDOC_METADATA

[Former Member]

Hi Experts,

We have a scenario cXML to IDoc using BPM, which is working ok in Development environment.

But when it is transported to SIT environment got failed. please see the details below

<SAP:Category>XIAdapter</SAP:Category> 
  <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code> 
  <SAP:P1>You have no authorization for extensions (activity 03)</SAP:P1> 
  <SAP:P2 /> 
  <SAP:P3 /> 
  <SAP:P4 /> 
  <SAP:AdditionalText /> 
  <SAP:ApplicationFaultMessage namespace="" /> 
  <SAP:Stack>Error: You have no authorization for extensions (activity 03)</SAP:Stack> 
  <SAP:Retry>M</SAP:Retry>

Please suggest on how to resolve the issue.

Thanks in advance.

MK

[Former Member]

Hi,

If you are using an extended IDoc, make sure that the extended IDoc's metadata is present in XI system (t-code IDX2). If not import the metadata manually using IDX2.

Also, from the error it seems that the service user maintained in the RFC destination used in the IDoc adapter does not have the necessary authorization to process IDoc extensions. Try providing SAP_ALL access to this user temporarily and see if the error persists. If the issue is resolved, then you can find out the exact role required to be assigned to this user. But if the issue persists, then its not related to authorization.

Regards,

Riyaz

[Former Member]

thanks Riyaz,

can you Please show the steps to provide the SAP_ALL access to the user.

[Former Member]

Hi,

You will need to ask your basis administrator to provide SAP_ALL access to the particular service user. Basis person should be able to do the needful.

Regards,

Riyaz

[Former Member]

hi mk

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

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

reward points if helpfull

rgrds

kummari

Edited by: kummari on Jul 8, 2008 7:40 AM

[former_member214364]

Hi Mk,

Did you do Authorization Test in RFC Destination to SAP System from SM59 Tcode.

Cheers,

Jag

[Former Member]

Jag,

The RFC destination to the SAP system is working fine.

can you please suggest further to resolve the issue.

Thank you.

MK

[former_member214364]

Hi Mk,

I guess its problem with Authorizations in SAP for the user used in RFC destination to SAP.

Could you please check Authorizations of the user(RFC destination) i.e Profiles and Activities in SAP using PFCG Tcode.

and also extend role of logon user as given in note- 837595.

Thanks,

Jag

Edited by: jag on Jul 8, 2008 2:50 PM

[Former Member]

Thanks for the reply.

The IDoc metadata is properly loaded. and structure is also ok.

Is this not something related to authorization issue.

Please suggest to resolve the issue.

[Former Member]

hi,

The structure of the message does not correspond to the IDoc structure. Compare the payload of the XI message with the IDoc structure shown in transaction WE60 in the target SAP system.

If the IDoc structure is changed in the sender or receiver system, the metadata cache in the XI system must be updated as well because this data is used to convert the IDoc to an XML structure or the XML to an IDoc structure. To update the metadata in the XI system you must delete the old metadata in transaction IDX2. During processing of the next XI message using this data the cache will be filled automatically.

regards

kummari

[former_member208856]

The problem is related to idoc matadata is not uploaded on the system.

please check in the tcode : IDX2, that the idoc matadata is uploaded properly or not ?

please upload the same properly.

Regards,

Sandeep Kaushik