File-to-IDOC, idoc is missing in R/3

[Former Member]

Hi Gurus, I got successful message(checked flag) in sxmb_moni after executing file to idoc scenario. But, I <b>can not see the IDOC CREMAS05 in ECC(r/3)</b> using we02/we05.

Partner profile was set up in (ECC server) in which partner number is logical system name(XI0CLNT100) of XI server. "CREMAS" is available in inbound parameters of this profile. Anything else I need to check in R/3 ?

In XI, i have maintained port/rfc destination and are used in IDOC adapter. I have tested RFC destination to connect to R/3 which works fine.

Please help.

[Former Member · Accepted solution]

Kindly check receiver determination and communication channels.

[Former Member · Accepted solution]

Yes. I see red flag in middle(msg has err status on outbd. side).

Here is the log for IdocOutbound. How do I debug this ? Can we use DOCNUM to trace the problem ?

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

- <!-- Response

-->

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

<SAP:TABNAM>EDI_DC40</SAP:TABNAM>

<SAP:MANDT>100</SAP:MANDT>

<SAP:DOCREL>700</SAP:DOCREL>

<SAP:DOCNUM>0000000000010009</SAP:DOCNUM>

<SAP:DIRECT>2</SAP:DIRECT>

<SAP:IDOCTYP>CREMAS05</SAP:IDOCTYP>

<SAP:CIMTYP />

<SAP:MESTYP>CREMAS</SAP:MESTYP>

<SAP:MESCOD />

<SAP:MESFCT />

<SAP:SNDPOR>SAPXI0</SAP:SNDPOR>

<SAP:SNDPRN>MDMSBX01</SAP:SNDPRN>

<SAP:SNDPRT>LS</SAP:SNDPRT>

<SAP:SNDPFC />

<SAP:RCVPOR>SAPEC0</SAP:RCVPOR>

<SAP:RCVPRN>EC0CLNT100</SAP:RCVPRN>

<SAP:RCVPRT>LS</SAP:RCVPRT>

<SAP:RCVPFC />

<SAP:TEST />

<SAP:SERIAL />

<SAP:EXPRSS />

<SAP:STD />

<SAP:STDVRS />

<SAP:STATUS><b>03</b></SAP:STATUS>

<SAP:OUTMOD />

<SAP:SNDSAD />

<SAP:SNDLAD />

<SAP:RCVSAD />

<SAP:RCVLAD />

<SAP:STDMES />

<SAP:REFINT />

<SAP:REFGRP />

<SAP:REFMES />

<SAP:CREDAT>2007-04-19</SAP:CREDAT>

<SAP:CRETIM>15:29:44</SAP:CRETIM>

<SAP:ARCKEY>78B86500EEC511DBA67D000F203CD31A</SAP:ARCKEY>

</SAP:IDocOutbound>

[Former Member · Accepted solution]

hey

dis means ur file is being picked up properly but not delivered,chech the partner profile

thanx

ahmad

[Former Member · Accepted solution]

Partner profile looks ok. In ECC server, partner type is defined with logical name of XI server. "CREMAS" was defined as message type in inbound parameters.

But, I am sending <b>CREMAS05</b> from XI where as <b>CREMAS</b> is defined as inbound parameter. Would this be a problem ?

How do i make sure partner profile works ok with XI ? Thanks for your help

[prabhu_s2 · Accepted solution]

check with idx5

[Former Member · Accepted solution]

Yes. I see them in idx5 how do i push them ?

[Former Member · Accepted solution]

> Partner profile looks ok. In ECC server, partner type

> is defined with logical name of XI server. "CREMAS"

> was defined as message type in inbound parameters.

>

> But, I am sending <b>CREMAS05</b> from XI where as

> <b>CREMAS</b> is defined as inbound parameter. Would

> this be a problem ?

>

There won't be a problem.

.

> How do i make sure partner profile works ok with XI ?

Create a test message in transaction we19 inside your target system and fill the same data as are in XI message.

> Thanks for your help

Also please check the status of the queues (SMQ1) and try to upload metadata definition manually in IDX2.

Regards,

Wojciech

[Former Member · Accepted solution]

Hi,

If message stuck in the queues either restart it from SXI_MONITOR or SMQ1.

Regards,

Wojciech

[prabhu_s2 · Accepted solution]

are u checking the correct dest system for recv idocs and any logs in idx5

[Former Member · Accepted solution]

Hi Mallik,

CREMAS is message type and CREMAS05 is an instance of the message type(IDOC Type). The "05" in the end is the version of the Idoc type version...that configuration is correct....you can post CREMAS01...05 with this configuration.

please chec the control record that your populating for this idoc....i.e port & partner profiles...

hope this wil help u

Thank you

[Former Member · Accepted solution]

In IDX5, i clicked on display que entry which took me to tRFC transaction screen. I found there is an error message "No authorizations to send IDOC..." Target system ECC server, Function Module "IDOC_INBOUND_ASYNCHRONOUS".

Which service user should have authorization ? and what type of authorization/role needed ?

Thanks in advance for help

[prabhu_s2 · Accepted solution]

check notes 837595 to find the list of authro req for idoc postings

[prabhu_s2 · Accepted solution]

also u can run su53 to find out the authorization u are missing once the interface is triggered or after u execute for idx5. check for this also.

Message was edited by:

Prabhu S

[Former Member · Accepted solution]

Hi,

Assign a role for the user used in your RFC. The best way to configure it is to use communication or system user.

You need this authorization:

S_BI-WX_RFC

S_BI-WHM_RFC.

Please check also this note:

150315

Regards,

Wojciech

[Former Member]

Hey Mallik ,

IN ECC what is the LS name u have used for configuring the partner profile.

Seeing the payload you have pasted on the forum it seems that the IDOC will be pushed to the LS MDMSBX01.

So in ECC configure the logical system as MDMSBX01 and in the inbound parameters do the configuration for the CREMAS IDOC .

Once you are done with it retrigger the scenario.

I think it should work now

Regards

Nikhil

[Former Member]

Hello,

Could you pelase check whether the idoc metadata has been uploaded in to xi server or not .i.e through the transacion idx2.

Regards,

kiran kumar.

[Former Member]

hey

check the whole line in SXMB_MONI,a lot of times we get the chequered flag in the beginning but a red flag somewhere in between,see all the columns in moni

thanx

ahmad