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

ale

Former Member
0 Likes
806

hi

i have used bd87, bd75,sm58, sm12,sm21, we14 etc., pls give me exact tcodes to solve these errs listed down.

how to solve he follg inbound errs ?

1. idocs added (50)

2. applicn doc notposted (51)

3. idoc with errors added (56)

4. sytax error (60)

5. idoc dipatched to applicn (64)

how to solve he follg outbound errs ?

1. data passed to port

2. syntax err

3, ale service err

4. idoc ready for dispatch

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
754

Hi Uma,

1. idocs added (50) - this is not an error

2. applicn doc notposted (51) - problem with the ports

3. idoc with errors added (56) - you are missing some data.try to find throug debug

4. sytax error (60) - Check the segments

5. idoc dipatched to applicn (64) - Thisis not an error. Run the program <b>RBDAPP01</b> to process all IDOC records

how to solve he follg outbound errs ?

1. data passed to port

2. syntax err

3, ale service err

4. idoc ready for dispatch - Run <b>RSEOUT00</b> Program.

Best way is try to debug the IDO Cthrough WE19.

Mark the helpful answers

Thanks

Eswar

7 REPLIES 7
Read only

Former Member
0 Likes
754

Hi,

You can debug the Idoc from Tcode : we19.

it may help you

Thanks

Sunil

Read only

former_member404244
Active Contributor
0 Likes
754

Hi,

The status above 50 are inbound idocs

1. idocs added (50)

2. applicn doc notposted (51)

3. idoc with errors added (56)

4. sytax error (60)

5. idoc dipatched to applicn (64)

so all the above r inbound .

1>status -51 means u r the data coming from idoc not posted .

2>status-56 means ur reciver configuration is not correct

3>ststus-60 means there is error in the idoc data.

4>status-50 and status-64 are not errors.

Reagrds,

nagaraj

Read only

Former Member
0 Likes
754

hi,

2) application doc not posted. we can resolve this by execuitng BD87 and execute. right click on message type and press process.

If data is sent from one sender sucessfully but in the receiver, data did not get posted. then, we get this error.

Regards,

Sailaja.

Read only

Former Member
0 Likes
754

Hi Uma Maheshwari,

Try Program RBDINPUT.

I hope that program will help you.

if suits ur need, pls award points.

satish

Read only

Former Member
0 Likes
755

Hi Uma,

1. idocs added (50) - this is not an error

2. applicn doc notposted (51) - problem with the ports

3. idoc with errors added (56) - you are missing some data.try to find throug debug

4. sytax error (60) - Check the segments

5. idoc dipatched to applicn (64) - Thisis not an error. Run the program <b>RBDAPP01</b> to process all IDOC records

how to solve he follg outbound errs ?

1. data passed to port

2. syntax err

3, ale service err

4. idoc ready for dispatch - Run <b>RSEOUT00</b> Program.

Best way is try to debug the IDO Cthrough WE19.

Mark the helpful answers

Thanks

Eswar

Read only

Former Member
0 Likes
754

Hi,aftre running t.Code BD87 u can see those error records etc..Also u can find idocs which are ready for Posting..Put the cursor on Yellow color icon and Click on the Process Tab....

But those records will be saved with ur Userid..

So it s better to run those Idocs with the Inbound job...so that those records will be stored with the user OPCBATCH ...

Read only

Former Member
0 Likes
754

Hi Uma,

All the messages listed in statusare not errors.

Please see that only messages marked in Red are errors.

And coming to error identification. if your Idoc is not successfully posted then its depend on the data youare using in IDOC.

Please look into the Data first.

Then if its still giving errors then try to post a document mannually with all the data that you pass in IDOC.

Then you will get some idea on what is the error.

If still error persists then debug the FM in WE19.

BR,

Ravi,