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

Disabling screens.

Former Member
0 Likes
386

Hi guys,

I am calling transaction VL31N from my custom program.

set PARAMETER ID 'LIF' FIELD '114390'.

set PARAMETER ID 'BES' FIELD '45077732322'.

CALL TRANSACTION 'VL31N' AND SKIP FIRST SCREEN.

is there a way to capture events (user clicks) somehow from my custom program and cancel it?

I want user to not be able to press some key combinations that will popup search screen for example.

Thank you.

1 ACCEPTED SOLUTION
Read only

Sandra_Rossi
Active Contributor
0 Likes
346

you may use transaction and screen variants (SHD0 transaction). See SAP library or forum for more information.

Screen variants allow you to act on GUI elements (and user commands).

Transaction variant makes the connections between a transaction and screen variants.

When you call the transaction, you need to indicate the transaction variant to be used, by calling RS_HDSYS_CALL_TC_VARIANT (note: you may not create a Z transaction of type "transaction variant" because you use skip first screen, as explained in Note 318448 - Call and skip first screen).

you may use transaction and screen variants (SHD0 transaction). See SAP library or forum for more information.

Screen variants allow you to act on GUI elements (and user commands).

Transaction variant makes the connections between a transaction and screen variants.

When you call the transaction, you need to indicate the transaction variant to be used, by calling RS_HDSYS_CALL_TC_VARIANT (note: you may not create a Z transaction of type "transaction variant" because you use skip first screen, as explained in Note 318448 - Call and skip first screen).

1 REPLY 1
Read only

Sandra_Rossi
Active Contributor
0 Likes
347

you may use transaction and screen variants (SHD0 transaction). See SAP library or forum for more information.

Screen variants allow you to act on GUI elements (and user commands).

Transaction variant makes the connections between a transaction and screen variants.

When you call the transaction, you need to indicate the transaction variant to be used, by calling RS_HDSYS_CALL_TC_VARIANT (note: you may not create a Z transaction of type "transaction variant" because you use skip first screen, as explained in Note 318448 - Call and skip first screen).