Application Development 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: 

No batch input data for screen SAPMSSY3 0131 in Sales order IDOC

former_member125661
Contributor
0 Kudos

I am processing Sales order IDOCS in status 64 using RBDAPP01 .Some of them error out to status 51 with the message -

No batch input data for screen SAPMSSY3 0131 .

I know the standard IDOC inbound process tries to simulate the posting in a BDC like process.

Now, I went to we19 and the screen hangs up in a pop up in the partners tab with partner type 'WE' and my shipto (which is actually filled in the IDOC), missing..upon repeatedly hitting enter, it goes thru and an idoc is posted in status 53. But still unable to get through the root of this issue.

Any, insight will help.

3 REPLIES 3

Former Member
0 Kudos

hi,

there are some breakpoints in abap code ...

regards,darek

0 Kudos

What break points are you talking about ?

I found the issue. There is a fix for it in a OSS notes - 944538

Former Member
0 Kudos

Hi,

I think the pop-up is generated through and user-exit for which recording is missing. This is why your idoc stays in status 64...

Handle the screen recording in the user exit IDOC_INPUT_ORDERS

    • user exit routine

PERFORM customer_function_dynpro.

FORM CUSTOMER_FUNCTION_DYNPRO.

CALL CUSTOMER-FUNCTION '002'

EXPORTING DXVBAK = XVBAK

DVTCOMAG = VTCOMAG

DLAST_DYNPRO = LAST_DYNPRO

DXMESCOD = IDOC_CONTRL-MESCOD

TABLES DXBDCDATA = BDCDATA

DXVBAP = XVBAP

DXVBEP = XVBEP

DYVBEP = YVBEP

DXVBADR = XVBADR

DYVBADR = YVBADR

DXVBPA = XVBPA

DXVBUV = XVBUV

DIDOC_DATA = IDOC_DATA

DXKOMV = XKOMV

DXVEKP = XVEKP

DYVEKP = YVEKP

EXCEPTIONS

USER_ERROR = 01.

Regards,

Krishnakumar