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.
BDC sessions are not my speciality so I hope this makes sense!
We have a program that creates a batch job via BDC. The BDC needs to enter data into a parameter field on the selection screeen of the program it applies to. However, the program that is 'called' from the BDC session can also be run by users and we do not want the parameter to be available to them - only to the batch job. We have therefore created the parameter with the NO-DISPLAY option but this causes an error saying that the the field cannot be found. If we remove the NO-DISPLAY option then it works fine. Presumably as the BDC session emulates a user it is subject to the same restrictions as an ordinary user. Does anybody know of a way of solving this?
What you can try out here is that U can try to modify the screen depending on the way ur executing the program. U can do this in the event AT SELECTION SCREEN OUTPUT.This event block allows you to modify the selection screen directly before it is displayed..Here's a piece of code from SAP help which may give u some idea.
I had thought of using a variant but the data was going to change each time and as Anurag pointed out would still require ectivating de-activating the field anyway.
In the end I opted for the loop within the At selection-screen output event. I used most of the solution provided by Varun as specifying screen-name = 'P_TEST' did not hide the parameter label. However, I included an IF statement checking the value of sy-binpt ( = 'X' ) and did screen-active = '1' instead of -invisible = '1', which just sets the filed to have a '*' input mask. Here is my actual code for reference:.
PARAMETERS: p_test type c MODIF ID SC1.
AT SELECTION-SCREEN OUTPUT.
LOOP AT screen.
IF screen-group1 = 'SC1'.
IF sy-binpt = 'X'.
screen-active = '0'.
MODIFY screen.
ENDIF.
ENDIF.
ENDLOOP.
Bluesky
