Knowledge Management

Question:
Hi,
I'm using a call transaction in my program and the program should show the messages after the call transaction.
When i execute the program, the messtab(message table) is empty. Therefore, it doesnt display anything after executing the call transaction. The weird thing is, if i run debugging mode and execute line by line, after the call transaction, the messtab has data.
The data is
message type S: No batch input data for screen SAPMSSY3 0121
The transaction i'm running is ko8g.
Please advice.
Thanks in advance.
Answer:
I've checked the program and screen number from the message table. it's the debugging screen. How come such message will appear?
Please help! thanks
Answer:
I don't have an explanation for this (sometimes it happens sometimes not ...) but in your particular case maybee you could submit the program RKO7KO8G instead of doing a call transaction.
Actually its the program that si submitted when you chose Background processing (in 45B).
CaKe
Answer:
Just try
CALL TRANSACTION 'KO8G' USING BDCDATA MODE ....
REFRESH BDCDATA.
The Problem is sometimes you fill your BDC Tab from a loop and after calling the Transaction you might leave it filled.
Also as per Transaction KO8G, There is a popup for Controlling Area if it is executed for the First time after logging in, But once you set the Co. Ar. there is no popup, Have you considered this while designing your BDC.
Use FM K_KOKRS_SET to get rid of the Co.Ar. Screen.
KRK
Answer:
Hi,
I'm using a call transaction in my program and the program should show the messages after the call transaction.
When i execute the program, the messtab(message table) is empty. Therefore, it doesnt display anything after executing the call transaction. The weird thing is, if i run debugging mode and execute line by line, after the call transaction, the messtab has data.
The data is
message type S: No batch input data for screen SAPMSSY3 0121
The transaction i'm running is ko8g.
Please advice.
Thanks in advance.
Can you try to call transaction in forground (just comment out mode 'N' "Background)...my experience that this kind of message happens when you try to enter an incorrect data and you got a popup message.
Incho
Answer:
Referring to Kumar's suggestion,
I refresh the bdcdata everytime before i call the transaction. If i refresh the bdcdata after the call transaction, the messtab will also be filled with that weird message because the message is directly inserted into the messtab straight after a call transaction.
I'm using the function K_KOKRS_SET before i call transaction ko8g to get rid of the controlling area pop up.
Referring to Incho's suggestion,
I tried to set the dismode to A which will show me what is happening to the transaction while running the program. Everything is doing fine and after that transaction, the messtab is empty.
That weird message (S: No batch input data for screen SAPMSSY3 0121 )
only appears if i debug the program using f5 or f6. After debugging the program a few times, the message will disappear. It'll appear whenever it likes and disappear whenever it likes too.
I really have no idea what is wrong with the program.
Please advice.
Thanks.
Answer:
This may be coz of u r trying to populate a field which doest not exist at all in screen.
Well I tell u like this..there are situations where it is decided by configuration that if u enter a particular value on a filed, depending upon that in next screen/subscreen diffrent field come. So I guess u r trying to populate in the wrong field.
cheers
Kirti
Answer:
I've checked the BDC and i think everything is correct.
FORM f_transdp91.
  REFRESH bdcdata.
  PERFORM bdc_dynpro      USING 'SAPLVPK_GUI_INTRO' '0400'.
  PERFORM bdc_field       USING 'BDC_CURSOR'
                                'VPK_INPUT_SELECTION-VBELN'.
  PERFORM bdc_field       USING 'BDC_OKCODE'
                                '=ENTER'.
  PERFORM bdc_field       USING 'VPK_INPUT_SELECTION-VBELN'
                                 i_aufk-vbeln.
  PERFORM bdc_dynpro      USING 'SAPLVPK_GUI' '0100'.
  PERFORM bdc_field       USING 'BDC_OKCODE'
                                '=SAVE_BR'.
  PERFORM bdc_dynpro      USING 'SAPLSPO1' '0500'.
  PERFORM bdc_field       USING 'BDC_OKCODE'
                                '=OPT1'.
  REFRESH messtab.
  CALL TRANSACTION 'DP91'
                   USING bdcdata
                   MODE dismode
                   UPDATE upmode
                   MESSAGES INTO messtab.
ENDFORM.                      " f_transdp91
[/code]
Answer:
I cannot see Transaction DP91 in 4.0B.
Is it Tcode DP91 or KO8G
KRK
Answer:
Hi SAPbie,
i am also getting the same problem while i am running my transaction in back ground... T-code is 'CJR2'...
some one can help me out.......
Thnx in advance...
sumo
Answer:
Hi, I'm sorry. I pasted the wrong codes. but that transaction also show the weird message when i execute it.
This is the codes for KO8G.
FORM f_trans_ko8g.
  REFRESH bdcdata.
*If text checkbox is ticked
  IF cb_test = c_check.
    PERFORM bdc_dynpro      USING 'SAPLKO71' '1000'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LKO74-PERIO'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=AUSF'.
    PERFORM bdc_field       USING 'LKO74-PERIO'
                                  p_period.
    PERFORM bdc_field       USING 'LKO74-GJAHR'
                                  p_year.
    PERFORM bdc_field       USING 'LKO74-VAART'
                                   '1'.
    PERFORM bdc_field     USING 'LKO74-TESTLAUF'      " test run  tick
                                     c_check.
    PERFORM bdc_field       USING 'LKO74-LIST'     " detail  list
                                  c_check.
    PERFORM bdc_field       USING 'LKO74-TDCHECK'     " check  trans
                                  c_check.
    PERFORM bdc_field       USING 'CODIA-VARIANT'   " variant
                                  p_var.
 ELSE.
    PERFORM bdc_dynpro      USING 'SAPLKO71' '1000'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LKO74-TDCHECK'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=AUSF'.
    PERFORM bdc_field       USING 'LKO74-PERIO'
                                  p_period.
    PERFORM bdc_field       USING 'LKO74-GJAHR'
                                  p_year.
    PERFORM bdc_field       USING 'LKO74-VAART'
                                  '1'.
    PERFORM bdc_field      USING 'LKO74-TESTLAUF'     " test run empty
                                  space.
    PERFORM bdc_field       USING 'LKO74-LIST'          " detail list
                                  c_check.
    PERFORM bdc_field       USING 'LKO74-TDCHECK'       " check trans
                                  c_check.
    PERFORM bdc_field       USING 'CODIA-VARIANT'       " variant
                                  p_var.
  ENDIF.
  REFRESH messtab.
  CLEAR bdcdata.
  CALL TRANSACTION 'KO8G'
                   USING bdcdata
                   MODE dismode
                   UPDATE upmode
                   MESSAGES INTO messtab.
[/code]
Answer:
    PERFORM bdc_dynpro      USING 'SAPLKO71' '1000'.
Are you sure about this as I can see Program is SAPLKO74.
KRK
Answer:
If you're using CALL TRANSACTION ... USING... and you're in debug mode, make sure that you don't press F5 (single step) when it's about to start the actual call to the transaction. Otherwise you'll get that strange message as SAP wants to populate the debug screen with BDCDATA.
Better to place a break-point after the CALL TRANS... en press F8 upon calling the transaction
Cheers
Answer:
Kumar, I've double checked my bdc recording, and it is SAPLKO71.
Now i know why that weird message appears. It's because of that F5. No wonder the weird message only appears if i go into debugging mode.
Thanks to everyone who gave feedback to me. I've learnt something again here.
Answer:
In my case, it still persists. I've remove my break-points already but still the error occurs. Pls. help.