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.
In the PBO module of the screen in which you have made changes, loop at screen and make the screen-inactive = 0.
Here is a sample code am pasting for your refernec that I have used in IW21 . Here based on the notification type some fields are made invisible. Itr is always easier if you assign your custom button to a screen group.
we have to write the logic in the PBO module of the sub screen created in the screen exit or in the PBO function exit for that enhancement? I have tried in both.
And the object 'SCREEN' does not have the component INACTIVE'.
You have to write the code in the PBO of the subscreen. And about the field, sorry instead of writing ACTIVE i have written inactive.
You can also use SCREEN_INVISIBLE field as I have done in the example pasted.
If this does not work , please activate the function group once by going to hierarchy and check. I have faced a similar issue while making changes for me23n transaction. Hope this works for you.
While you are in the Flow Logic screen of the subscreen click on the hierarchy button. That will show you the function group on the left side panel. Activate that function group and then try.
About disabling the field on the screen, i think you have to write the code in the subscreen modules and not function exits. I may be wrong but function exits are usually provided for the flow of data between the screen and the system like storing the user entered values in the database and retrieving for display like that. Also check the documentation of the exit. That will provide you the better picture of how the exit is gonna function.
Bluesky
