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.
If you want to encapsulate a screen sequence with all of its flow logic and application logic, you must ensure that all of the screens in the sequence are linked to a single ABAP program. The ABAP program contains all of the dialog modules called by the screens in the sequence.
It is not currently possible to assign screens to a single procedure (subroutine, function module, or method) – these belong instead to the main program of the procedure.
When you call a new main program in order to use a screen sequence (for example, using CALL TRANSACTION), a new SAP LUW begins. This may be an undesired effect, especially when you are trying to modularize a transaction that updates the database.
An alternative to this is to use an external procedure, whose main program is linked to a screen sequence, and which contains the corresponding dialog modules. Procedures run in the same SAP LUW and internal session as their calling program.
please check out the link below it will be helpful to you
Bluesky
