Error while posting IDoc

[Former Member]

Hi ,

I am trying to send an IDoc from XI to R/3. I am getting the following error on XI in the transaction sxmb_moni.

Error: you have no authorization for basic types (activity 03)

any ideas on what the problem could be ?

Regards,

Praveen

[Former Member]

Hi Praveen,

This error you'll be getting in sxmb_moni is because of the lack of authorization for the user you have mentioned in your RFC destination in XI system.

Pls do see the help of your basis people and try seeing whether the user id you are using to connect to R/3 system is able to access all the transactions related to IDoc generation. Which all are the activities the user id is lacking you can identify as follows:

Login to R/3 system and then try using WE30 transaction and if its says you are not having authorization then use the transaction SU53. This gives which role/activity is missing in your profile.

Now seek Basis help in getting the relevant roles added to the user id you are using in your RFC destination from XI->R/3.

Cheers

JK

PS: Award points if this helps you.

[Former Member]

Hi Jayakrishnan,

That was really helpfull, now i am getting the message as Processed successfully in sxmb_moni but still i do not see any IDoc's in R/3(WE02). In sxmb_moni in XI the Outbound status shows a red flag .

any ideas on what might be wrong ?

Praveen

[Former Member]

Hi Praveen,

Since in XI outbound side there is a red flag meaning there is error on outbound side, there wont be any successful posting of idoc. Can you pls put in the trace here...

Also pls do check whether you have assigned the proper logical system in adapter specific identifiers to your sender business system, and also the correct port and RFC destination is maintained in IDX2.

Cheers

JK

[Former Member]

Hi Jaykrishnan,

Here is the trace ..

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Response

-->

- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">

<Trace level="1" type="T">Party normalization: sender</Trace>

<Trace level="1" type="T">Sender scheme external = XIParty</Trace>

<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>;

<Trace level="1" type="T">Sender party external =</Trace>

<Trace level="1" type="T">Sender party normalized =</Trace>

<Trace level="1" type="T">Party normalization: receiver</Trace>

<Trace level="1" type="T">Receiver scheme external =</Trace>

<Trace level="1" type="T">Receiver agency external =</Trace>

<Trace level="1" type="T">Receiver party external =</Trace>

<Trace level="1" type="T">Receiver party normalized =</Trace>

<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />

- <!-- ************************************

-->

<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>

<Trace level="1" type="T">COMMIT is done by XMB !</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />

<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />

<Trace level="1" type="T">****************************************************</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">XMB entry processing</Trace>

<Trace level="1" type="T">system-ID = XID</Trace>

<Trace level="1" type="T">client = 350</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = XIAFUSER</Trace>

<Trace level="1" type="Timestamp">2006-03-21T11:48:05Z CET</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">****************************************************</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />

- <!-- ************************************

-->

<Trace level="1" type="T">Message-GUID = 8EF80C20B8D011DAC952000BCD3F5F3D</Trace>

<Trace level="1" type="T">PLNAME = CENTRAL</Trace>

<Trace level="1" type="T">QOS = EO</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />

<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>

<Trace level="1" type="T">Queue name : XBTI0004</Trace>

<Trace level="1" type="T">Generated prefixed queue name = XBTI0004</Trace>

<Trace level="1" type="T">Schedule message in qRFC environment</Trace>

<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>

<Trace level="1" type="T">----

---

</Trace>

<Trace level="1" type="T">Going to persist message</Trace>

<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>

<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>

<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>

<Trace level="1" type="T">----

---

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />

- <!-- ************************************

-->

<Trace level="1" type="T">----

---

</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

<Trace level="1" type="T">system-ID = XID</Trace>

<Trace level="1" type="T">client = 350</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = XIAFUSER</Trace>

<Trace level="1" type="Timestamp">2006-03-21T11:48:06Z CET</Trace>

<Trace level="1" type="T">----

---

</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">

<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />

<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>

- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>

<Trace level="1" type="T">Cache Content is up to date</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>

<Trace level="1" type="T">Cache Content is up to date</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />

- <!-- ************************************

-->

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />

- <!-- ************************************

-->

<Trace level="1" type="T">number of receivers: 1</Trace>

<Trace level="1" type="T">Single-receiver split case</Trace>

<Trace level="1" type="T">Post-split internal queue name = XBTO2___0001</Trace>

<Trace level="1" type="T">----

---

</Trace>

<Trace level="1" type="T">Persisting single message for post-split handling</Trace>

<Trace level="1" type="T" />

<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>

<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>

<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>

<Trace level="1" type="T">----

---

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />

- <!-- ************************************

-->

<Trace level="1" type="T">----

---

</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

<Trace level="1" type="T">system-ID = XID</Trace>

<Trace level="1" type="T">client = 350</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = XIAFUSER</Trace>

<Trace level="1" type="Timestamp">2006-03-21T11:48:06Z CET</Trace>

<Trace level="1" type="T">----

---

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />

<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>

<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>

- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">

<Trace level="1" type="T">No mapping required</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

<Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV" />

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />

- <!-- ************************************

-->

<Trace level="1" type="T">----

---

</Trace>

<Trace level="1" type="T">---- Outbound IDoc-Adapter -

---

</Trace>

<Trace level="1" type="T">----

---

</Trace>

- <Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-ENTER_PLSRV">

<Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>

<Trace level="1" type="T">Get Information from IS-Header Objekt</Trace>

<Trace level="1" type="T">Get Information from SD-IDoc-Endpoint</Trace>

<Trace level="1" type="T">Sender and Receiver after Header-Mapping</Trace>

<Trace level="1" type="T">Sender service FTP2IDoc</Trace>

<Trace level="1" type="T">Receiver service CVI_B_SYS</Trace>

<Trace level="1" type="T">Get IDoc-XML from the Resource Objekt</Trace>

- <Trace level="1" type="B" name="IDX_XML_TO_IDOC">

<Trace level="1" type="T">Parse XML-BODY</Trace>

<Trace level="1" type="T">Get the Metadata for port PCVI</Trace>

<Trace level="1" type="T">Convert one IDoc</Trace>

<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>

<Trace level="1" type="T">Convert Segment-Types to Segment-Definitions</Trace>

</Trace>

<Trace level="1" type="T">Call Outbound IDoc-Adapter</Trace>

<Trace level="1" type="T">Call Outbound IDoc-Adapter</Trace>

- <Trace level="1" type="B" name="IDX_OUTBOUND_XMB">

<Trace level="1" type="T">FM IDOC_INBOUND_ASYNCHRONOUS with RFCDEST= RFC_CVI</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

</Trace>

<Trace level="1" type="T">----

---

</Trace>

<Trace level="1" type="T">Async processing completed OK.</Trace>

<Trace level="1" type="T">system-ID = XID</Trace>

<Trace level="1" type="T">client = 350</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = XIAFUSER</Trace>

<Trace level="1" type="Timestamp">2006-03-21T11:48:06Z CET</Trace>

<Trace level="1" type="T">----

---

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!-- ************************************

-->

</SAP:Trace>

I have checked the port and rfc destinations.

[former_member187339]

Hi,

Just check your Idoc Adapter(in runtime workbench) and see whats the message its showing.

Regards

Suraj

PS: Since Jayaktishnan's suggestion helped you, you can assign points for that.

[Former Member]

Hi Praveen,

You need to configure the partner profile in R/3 system from which you will be sending the IDoc not in XI system.

Check this link.

/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi

Thanks,

Prateek

[STALANKI]

It is some authorization issue for the user that is specified in the RFC Destination.Check with your basis team for resolving it.

[Former Member]

hi,

Make sure that the idoc type you are using exists in the R/3 system.

We encountered such a problem when we were trying to use an idoc type that was not available in the R/3 current version but was available in the previous version.

Regards,

Smitha.

[Former Member]

Praveen,

Another thing you can try is once you have configured your RFC connection, make sure you test it with "Remote Logon". If this is not successful then it would mean that the username you are using to log into XI does not have proper authorization.

[Shabarish_Nair]

Do check that thread.

[Former Member]

Hi,

Are you sending the idoc via trfc port from we19??

did u check all the settings that needed to be done at xi and R3 side??just cross check.

Steps are:

Scenario: IDOC > xi>FILE

Configurations in R/3 side

1. SM 59 (RFC destinations)

Create a RFC destination on the XI server. The connection type should be R/3 connection. The target host needs to be the XI server.

2. WE 21 (Ports in IDOC processing)

Create a transactional port. Provide the RFC destination created in this.

3. BD 54

Create a logical system.

4. WE 20 (Partner Profiles)

a. Create a new partner profile under partner type LS.

b. Assign the message type in outbound parameters.

c. Open the message type (Dbl click) and configure the receiver port to the port created.

Configurations in XI server

1. SM59 (RFC destination)

Configure the RFC destination specific to the R/3 system.

2. IDX1 (Port maintenance in IDOC Adapter)

Create a port and provide the RFC destination.

3. SXMB_ADM

Select the integration engine configuration. Select the category as RUNTIME and hit the specific configuration button and add an entry ACK_SYSTEM_FAILURE in the parameters with current value as 1 and default 0. This I believe is a one time configuration.

Then test by,

WE 19 (IDOC test tool)

Regards,

Anirban

[bhavesh_kantilal]

Hi,

Looks like, either the Configuration of your IDOC adapter has some error or , it does not have the authorization to access the R3 system. Check if you got the authorization in the R3 system and also check, if the partnet profile has been created in the r3 system.

Regards,

Bhavesh

[Former Member]

Hi Anirban,

i have done all these configurations.

When i try to configure the outboud parameters in partner profile (we20) in XI it says that

Entry MATMAS does not exist in table EDIMSG.

any ideas ?

Regards,

Praveen

[Former Member]

hI,

yes thats beacause you are trying it in xi abap stack, if you see my earlier post, i had written we20 under R3 confugurations,

Try that in R3 side and let us know,

All the best.

Anirban.

[Former Member]

Hi Anirban

my scenario is FTP -> XI ->(IDoc) R/3

i have configured the inbound and outbound parameters in WE20 in the R/3 side.

still it is not working.

praveen.