on 06-11-2008 7:21 AM
Hi Gurus,
I am doing a FILE TO IDOC scenario for taking Material Master data from the MDM system and posting the IDOC into the R/3 system..
The entry is there in MONI with the chequred flag but there is no IDOC in we02 of the R/3 system.
Also , i pasted the payload from teh MONI and checked in the mapping and the test was shown to be successful.
Can Anyone please tell me what can be the cause and its probable solution?
Thanks in advance,
Shweta.
Hi Swetha,
1.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
2.Check trfc queue in sm58
3.If message stuck in the queues either restart it from SXI_MONITOR or SMQ1.
Make sure ur checking the correct dest system for recv idocs and any logs in idx5.
Test like this:
Create a test message in transaction we19 inside your target system and fill the same data as are in XI message.
Also please check the status of the queues (SMQ1) and try to upload metadata definition manually in IDX2.
Regards,
Vinod.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shweta,
How are you filling the Control Record of IDoc. If you are mapping it in Message Mapping then check the checkboxes "Apply Control records value from Payload", "Take Sender from Payload" and "Take Receiver from Payload" in Receiver Communication Channel. If you are not handling them in Message Mapping and want Communication Channel to handle it then uncheck these checkboxes.
Thanks,
Punit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
(1) Error Category - CO_TXT_OUTBINDING_NOT_FOUND
The problem is in Technical routing.
Check whether the receiver determination and interface determination objects are active in change lists tab. If they are not active, activate the objects.
Also check the if the receiver determination and interface determination objects are referenced to the same namespace or not. Sender and receiver interface objects should always refer to the same Namespace.
(2) Error Scenario - ATTRIBUTE_IDOC_METADATA
Check the receiver communication channel (Created using IDOC adapter). In this communication channel check if the two mandatory parameters are passed correctly.
Following is further info on those two mandatory parameters.
(i)Check if the RFC destination which is created in XI to connect the target SAP R/3 system is working fine.
(ii)Check if the port that has been created in XI is in the form SAP<SID of R/3 system>. If not, create in the form of SAP<SID of R/3 system>. To this port, specify the above RFC Destination.
(3) Error Scenario - IDOC not yet created in target SAP R/3 system.
Go to R/3 system and check at Tcode WE05 if the IDOC has been created successfully. If error is u2018"Partner profile not configured" check point 9.
Suppose IDOC did not get created at R/3 end and all the pipeline steps were successful in SXMB_MONI, then go to Tcode : IDX5 in XI and click on Transaction ID field and check the status description which explains the problem.
(4) Error Scenario - Partner profile not configured.
Go to Tcode WE20 in R/3 system and check if the partner profile has been configured correctly and is filled with the inbound parameters.
regards
chandra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
check IDoc status in SM58 in XI
Whether you have authorizations to send IDocs
Regards,
Shabari
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check the port and RFC destination you have mentioned in IDoc adapter ...is the same as found in IDX1 in XI.
Try to test this RFC destination
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
11 | |
10 | |
9 | |
8 | |
6 | |
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.