on 09-26-2006 7:14 AM
Hi, I am very new to XI,As per the procedure i done the all settings for File2Idoc Scenario.From sender location file was pickup by the IS.But not reach to receiver side.I check in RWB/Message Monitoring from my sender interface.The messages are intially shown "Adapter Engine - STATUS : Waiting" After some time its shown "System Error".See the below Figure of my problem.In this situation what are the things i have to check.Plz suggest.Early response is appreciable.
Hi,
WHat is the exact error ? Are you getting any error in the transaction code SXMB_MONI ? If so what is the error ?
1) go to transaction SMQ2 and check the status of the Queue.
Have a look into this blog-/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
2) Hope all your configurations related to Idoc is correct? i.e in XI system SM59, IDX1, IDX2 entry.
Hope this helps,
Regards,
Moorthy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Anjan..
send me ur mail id ...
i can send u docs on file to idoc and idoc configuration
Cheers,
raghavesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Check out this link might be helpful
http://help.sap.com/saphelp_nw04/helpdata/en/49/e3fb40ef74f823e10000000a155106/TEMPLATE_image002.jpg
Thanks,
Prakash
Hi Anjan,
Just to give you a better understanding, cross check whether you have done the following steps:-
SLD-
1) Create a Product/Software Component
2) Technical System pointing to R/3 system
3) Business System for the above technical system
In the Repository
1) Import the Software component created in the sld
2) Create a namespace,
3) import the idoc and then create sender data type/message type etc and mapping
4) Mapping Rules is depends on the requirement
In the Directory
1) Create a Scenario /import the business system
2) Create Receiver/Interface determination
3) Create communication channels for sender and receiver
4) Sender Agreeement and Receiver Agreement.
Then the file adapter configuration is depend on the input file format.
Also you need to have Logical destionation created in the XI , and the IDX1 entry
In R/3 Port, Partner profiles etc should be created
Have a look into this document~
While doing an File -> XI -> IDoc scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you will need a sender agreement for the file.
4. In this configuration note that you will also need a receiver agreement for the IDOC.
For any File -> XI -> IDoc scenario ref:
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
Hope this helps you.
Regards.
Praveen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Anjan,
Can you send the Screen print to me too.
ID- agasthuri@gmail.com
Regards
Agasthuri Doss
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sent/Receive IDOC:
you need to do the following:
In XI
SM59 - R3 connection pointing to R3
IDX1 - define the port with the above dest.
In R3
SM59 - R3 connection pointing to XI
WE21 - define the port with the above dest.
WE20 - Partner profile type outbound/Inbound
From sender location file was pickup by the IS.But not reach to receiver side.I
>>> what do u see in message monitoring in RWB .. do post the trace here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am unable to add the Picture here.i.e Message Display over in Message Monitoring.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
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.