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 issue

Former Member
0 Likes
1,211

Hi all,

I would like to ask for your inputs regarding an issue that I am facing right now. Here is the case:

IDOCs with Message type MBGMCR cannot be processed using RBDAPP01, it resulted to status 51, the reason it gave was "Please enter net price". But then, when re-processed using BD87, it was successfully done, having a status number 53.

Hoping to get some ideas from you people.

Regards,

Ealbert

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,094

This is weird, they should behave the same way. If I were in your place I would have debugged RBDAPP01 with watch point SY-MSGNO = <message number of error message> and see from where in the code it is escalating from. Put a break-point at the first statement of the parent routine and now try to execute BD87 to catch that break-point to see why the difference in behavior. I hope there are no custom user exits which are getting triggered only when the program is run.

Hi all,

I would like to ask for your inputs regarding an issue that I am facing right now. Here is the case:

IDOCs with Message type MBGMCR cannot be processed using RBDAPP01, it resulted to status 51, the reason it gave was "Please enter net price". But then, when re-processed using BD87, it was successfully done, having a status number 53.

Hoping to get some ideas from you people.

Regards,

Ealbert

6 REPLIES 6
Read only

Former Member
0 Likes
1,095

This is weird, they should behave the same way. If I were in your place I would have debugged RBDAPP01 with watch point SY-MSGNO = <message number of error message> and see from where in the code it is escalating from. Put a break-point at the first statement of the parent routine and now try to execute BD87 to catch that break-point to see why the difference in behavior. I hope there are no custom user exits which are getting triggered only when the program is run.

Read only

Former Member
0 Likes
1,094

Hello,

irspective of rbdapp01 or bd87 ,the idoc should process successful for any message type but inyour case why its happening like that...i dont know c..an you please check once again and try to debug the program then u may get solution.

Thanks and regards

Durga.K

Read only

Former Member
0 Likes
1,094

Hi,

"RBDAPP01" is not the correct program to process the in 51 status. Idoc in 51 status should be processed with "RBDMANI2". We use "RBDAPP01" to process idoc which is in 64 status.

Thanks,

Asit Purbey

Read only

Former Member
0 Likes
1,094

Hi,

This case is really weird. When I debugged, I found out that all programs used are SAP standard. I don't know what to do next. My colleagues are mentioning about OSS notes. I still have to investigate further.

Regards,

Read only

Former Member
0 Likes
1,094

Hi all,

I have a query in ABAP HR,

to create an Idoc , i have a Idoc basic type HRMD_A02

and extension Idoc is created with 'Z' , my issue is i need to add a segment (infotype structure) 'p0040' to the extension, but this infotype already has SAP Idoc segment in t-code SM31 table T777D,

can anyone tell me how can i add this infotype fields to my Idoc extension?

or

Is there any other way to add the infotype fields?

Many thanks in Advance

Cheers

Read only

0 Likes
1,094

Hi Alan,

For these kind of issue you should raise separate question rather than making it part of other's question thread.

Please elaborate more the point "but this infotype already has SAP Idoc segment" in your question.