on 10-29-2007 8:09 AM
i have a idoc to file problem,
the idoc is sent from R/3 to XI,
the problem is IDOC is sent from R/3,
it didnt reach to XI.....
i have checked.......we05 in R/3, it gives a status 3,
then i checked SM58 in R/3, it shows nothing,
when i check in idx5 in XI, theres no trace of that idoc....and no trace of the scenario run in SXMB_MONI
pls help, where can i trace the idoc.....
pls help
If you don't selected the option "Transfer IDoc Immediatly" I suggest you, for test porpose only to use report RBDMOIND.
This report refresh the state of IDoc. If it is all OK your IDoc should change their state from 3 to 12.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
it you ahve sent the IDOC from R/3 and no error exists in Sm58 then only place it can have stcu in the queues, you check the outbound queue smq11...if any data is stuck there......
it will enter enter the XI if provided all the configuration you have doen properly....
1. Make sure no error in Sm58
2. Queues are cleared ( both in Xi and R/3)
then your idoc will enter XI...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sudeep,
Have you imported/reimported the IDOC METADATA into XI using IDX2?
Regards,
Sarvesh
Message was edited by:
Sarvesh Singh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
if it is showing nothing in sm58 then you just check thw login details in the partner profile maintained.
got to we20, in this go to technical setting and check for the login credentials.
Thanks
Rinku
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi sudeer,
Did You Check It In WE19.(Test Tool For Idoc Processing)
If Not Do The Following Steps:
<u><b>Step1:</b></u>
>> Give Your Existing Idoc Number.
<u><b>Step 2:</b></u>
>> Basic Type is Your Message type.
Ex: MATMAS05 or CREMAS05.
<u><b>Step 3:</b></u>
>> In Your Existing MATMAS05 or CREMAS05 Structure say EDIDC,
>> You Should Fill Your Mapped Entries In Data Structure of EDIDC.
>> So that Those Fields Gets Framed as Segments.
<u><b>Step 4:</b></u>
>> After Doing It goto Menu Bar and Click Idoc And Goto Edit Control Record.
<u><b>Step 5:</b></u>
>> Now You Give Your Sender And Receiver Port Number Along With Your
Logical System And Message Type again its Your MATMAS05 or
CREMAS05 .
<u><b>Step 6:</b></u>
>> After Doing It Click Standard Outbound Processing.
<u><b>Step 7:</b></u>
>> It Will Say what Happened To your Idoc.
<u><b>Step 8:</b></u>
>> It Is For Sure That if This Processing Fails It Wont Go To XI..
Regards,
Dhayanandh .S
Dont forget To Provide Points If Found Helpful...
Message was edited by:
DHAYANANDH SIVASANKARAN
Hi Sarvesh,
I Suppose that it would grind to hear some key Differences between WE19 and WE05.
>>The Function Module is Background for WE19 that provides a trace message, telling you that instances in the configuration could not be processed and processing is terminated.
>> If you are processing the configuration in the foreground, you see a list of the input data that could not be processed. The program then assumes that you know about this data, and does not terminate.
>> These Traces You Wont get it in WE05.
>> It is Silly to ask about the following Details after getting the Status Message after knowing that the Selected Idoc as sent.
"Have you imported the IDOC METADATA into XI using IDX2?
Also check you RFC connection and correct PORT number in R/3 to send the IDOC to XI."
Siva,
I will apricate you for this.
As you know WE19 is a test tool for IDOC & WE05 is to see the IDOC.
Yes it is wrong to ask the port and rfc connction to check in r/3 of XI once the idoc status is 3.
But what's wrong to ask to check the idoc metadata in IDX2? Can you explain me. Why we should not check this?
User | Count |
---|---|
81 | |
25 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.