2010 Aug 25 12:29 PM
Hello Experts,
I am doing a call transaction in a Z program like this:
CALL TRANSACTION c_yt01n USING t_bdc
MODE v_modo
UPDATE 'S'
MESSAGES INTO t_msg.
c_yt01n = YT01N (This is a copy of VT01N (create transport))
v_modo = N
I'm getting error "No batch input data for screen SAPMSSY0 0120 " after the call transaction execution. This is only happening for a particular shipping point.
Call transaction is getting executed without any issues if the mode is A, and the trasnport is created successfully
This is the BDC table
SAPMZV56A 1010 X
0 BDC_CURSOR VTTK-TPLST
0 BDC_OKCODE =MM_LFSL
0 VTTK-TPLST T130
0 VTTK-SHTYP BUD1
SAPLZV56L 1210 X
0 BDC_CURSOR S_VBELN-LOW
0 BDC_OKCODE =%094
0 S_VBELN-LOW 50033005
SAPLALDB 3000 X
0 BDC_CURSOR RSCSEL-SLOW_I(02)
0 BDC_OKCODE =ACPT
0 RSCSEL-SLOW_I(02) 50033006
0 RSCSEL-SLOW_I(03) 50033007
SAPLZV56L 1210 X
0 BDC_CURSOR S_VBELN-LOW
0 BDC_OKCODE =CRET
SAPMZV56A 1040 X
0 BDC_OKCODE =MM_TKAL
0 BDC_SUBSCR SAPLZV56I_PLAN_SCREEN 0110PLANNING
SAPMZV56A 1020 X
0 BDC_OKCODE =MM_ST01
0 BDC_SUBSCR SAPMZV56A 1025G_HEADER_SUBSCREEN2
0 BDC_CURSOR VTTKD-TKNUM_TMP
0 VTTKD-TKNUM_TMP 7250158986
SAPMZV56A 1020 X
0 BDC_OKCODE =MM_SICH
Do you have any idea what could be causing this issue? Is there some configuration missing for shipping point?
I found a couple of threads about program SAPMSSY0, but they are not helpful. Any ideas?
Thanks in advance!.
2010 Aug 25 2:26 PM
I think this is just a warning popup that you have to respond to.
So your program has to recognize whether or not this screen will be called and use separate logic for each case.
Rob
2010 Aug 25 2:26 PM
I think this is just a warning popup that you have to respond to.
So your program has to recognize whether or not this screen will be called and use separate logic for each case.
Rob
2010 Aug 25 7:45 PM
See whether any batch input session are struck by using SM35.
By manually processing it in foreground for those errored ones will give you picture why you are getting error for certain scenarios.