Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Idoc doubt ??

Former Member
0 Likes
968

Hi All,

I have one doubt.Scenario is from xi to r3.In XI, idoc sent successfully but in R3 , theres an error of 51 , Application document not posted.

Batch 1090 10 770 440 not exists.

Could you tell me what is the exect issue??

Regards,

Asha Prasad

1 ACCEPTED SOLUTION
Read only

h_senden2
Active Contributor
0 Likes
920

the function module that processes the idoc in R3 generates an error (for instance in a call transaction) with Batch 1090 10 770 440 not exists.

So the batch number does not exist in the R3 system.

regards,

Hans

8 REPLIES 8
Read only

h_senden2
Active Contributor
0 Likes
921

the function module that processes the idoc in R3 generates an error (for instance in a call transaction) with Batch 1090 10 770 440 not exists.

So the batch number does not exist in the R3 system.

regards,

Hans

Read only

raja_narayanan2
Active Participant
0 Likes
920

Hi...

first check in R3 whether your able to create the document which is like in you idoc application. becaz some values will not be there in your idoc application and that values is required in R3.. so the application document not posted error will come....

hope this will help you...

Regards

Raja

Read only

Former Member
0 Likes
920

any relation with this??

pk

Read only

Former Member
0 Likes
920

Asha,

I am sure this is due to the erraneous data that is coming from file to XI and then entering the R/3.

This is happening because the idoc that you are using to update R/3 is missing certain OBLIGATORY/ Mandatory fields in 1 or more segments. Or may be the data type of of the field in the segments of the idoc is receiving data type of different symentic attribute .

You can ask to correct the File data.

You can make the SOURCE FIELDS in messege Mapping as 1:1 occurance instead of 0:1 occurance for MANDATORY fields... This will enable you to restrict the data from file to reach R/3. It will through error in XI itself!!And you can test it by dry testing which Obligatory/ Mandatory field it is missing!! [ dry testing means coping load from SXMB_MONI and putting it in the TEST tab of messege mapping and executing it and checking the Target messege...]

Finally it can be corrected 1 last way by reprocessing the erranous data in WE02/05 by putting correct data in the Mandatory fields and reprocessing them

Asha, remember the fact that when the idoc is getting populated from XI and updating R/3, it is using a standard / z function module. That function module is preventing updation of the idocs because , there are conditions in them which prevent complete updation if IDOC doesnt carry data for obligatory fields.

If any further doubts, pls feel free to revert back,

Regards,

Arnab

.

Text deleted by moderator

Read only

matt
Active Contributor
0 Likes
920

Do not ask for points - please read the Rule of Engagement.

matt

Read only

0 Likes
920

Hi Matt,

This wont repeat again!

<<moderator message - we all make mistakes! note - moved to correct forum... >>

Regards,

Arnab !

Read only

0 Likes
920

Appreciated.

Read only

Former Member
0 Likes
920

procrdd that function module in inbound