on 11-30-2011 5:54 AM
Hi all,
We are facing issues with data is posting wrongly in File to Idoc scenario. When we test this scenario everything shows success in XI but in R/3 idoc generating with 64 status and data is not posting correctly. Suppose our second field if we send more than 20 length it is trimming upto 20 only. If we change offset to take 40 length to second field again it is taking 20 legth of sceond field and rest of third field values. As i have been checked with Abapper they were saying like whatever data we are sending to R/3 it will be coming as a single structure(Sdata) . But i have been checked outbound XML also in that everything shows fine. Is there anything problem in Xi . I have been re-imported idoc in XI also and it is equipment master Idoc. They have been used offset also still no use. My doubt is why from second field on wards data is posting worngly.They have used structure sdata.
Example:
Suppose, Outbound XML in XI:
<Idoc>
<Field1>abc
<Field2>4364255166110335211
<Field3>Computer
<Field4>Laptop
<Field5>sdas
<Idoc>
Idoc in R/3:
Field1:abc
Field2:43642551661 Computer Laptop
Field3: sdas
Field4:
Field5:
Could anybody help me on this. Why is data wrongly posting here...
Rgrds,
Aparna.
Hi,
Problem has been solved. Segment has not been released in R/3 . After releasing i have been re imported Idoc again. Now data is posting correctly. Thanks for all
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
When outbound XMl is correct then why In R/3 Idoc has not been posted correctly?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
i have faced same issue before.
in receiver communication channel for IDoc you have to specify some important parametres port and sap release so on...
while cretaing a port you have to give rfc destination in your port by using t-code IDX1.
go to rfc destination which was you given in port. check in your destination, tab MDMP & UNICODE.
Flag or disflag the option UNICODE/NO-UNICODE and test again.
once again check your message mapping.
regrds,
ganesh.
Edited by: ganesh.nijampudi on Nov 30, 2011 7:47 AM
though you re-imported the idoc, did you refreshed the caches, pl check it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Are you getting correct output payload in message mappng in ESR, & in MONI ..... if not check your message mapping once also check payload in idx5 ....and idoc status 64(IDoc is not transferred to the application) ...check whether collect option is enabled or not...trigger transmission of the IDoc using report RBDAPP01 or , plan a regular job in background processing for this report.
Regards,
Priyanka
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
24 | |
11 | |
9 | |
7 | |
5 | |
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.