SAP Function Modules
BUS_SCR_CONTAINER_MAIN SAP Function module
BUS_SCR_CONTAINER_MAIN is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name BUS_SCR_CONTAINER_MAIN into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
BUSS_SCGEN
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM BUS_SCR_CONTAINER_MAIN - BUS SCR CONTAINER MAIN
CALL FUNCTION 'BUS_SCR_CONTAINER_MAIN' "
* EXPORTING
* iv_xall = SPACE " boole-boole
* iv_xdelete = SPACE " boole-boole Flag: Delete All Generated Subscreen Containers
* iv_xdialog = SPACE " boole-boole
* TABLES
* it_client = " bus_client_range Clients
* it_objap = " bus_objap_range Application Objects
* it_dynid = " bus_dynid_range Screens
EXCEPTIONS
FOREIGN_LOCK = 1 "
IMPORT_ERROR = 2 "
SELECTION_NOT_ALLOWED = 3 "
MAX_USELINES = 4 "
GENERATION_NOT_NECESSARY = 5 " There are no screens to be regenerated
MAX_SECTION = 6 "
SCREEN_LAYOUT_NOT_ALLOWED = 7 "
MAX_TRDYN = 8 "
SYSTEM_ERROR = 9 " System Error
MAX_VIEW = 10 "
TRDYN_FAIL = 11 "
ERRORS_IN_PROTOCOL = 12 "
. " BUS_SCR_CONTAINER_MAIN
ABAP code example for Function Module BUS_SCR_CONTAINER_MAIN
The ABAP code below is a full code listing to execute function module BUS_SCR_CONTAINER_MAIN including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).
| it_it_client | TYPE STANDARD TABLE OF BUS_CLIENT_RANGE,"TABLES PARAM |
| wa_it_client | LIKE LINE OF it_it_client , |
| it_it_objap | TYPE STANDARD TABLE OF BUS_OBJAP_RANGE,"TABLES PARAM |
| wa_it_objap | LIKE LINE OF it_it_objap , |
| it_it_dynid | TYPE STANDARD TABLE OF BUS_DYNID_RANGE,"TABLES PARAM |
| wa_it_dynid | LIKE LINE OF it_it_dynid . |
DATA(ld_iv_xall) = some text here
DATA(ld_iv_xdelete) = some text here
DATA(ld_iv_xdialog) = some text here
"populate fields of struture and append to itab
append wa_it_client to it_it_client.
"populate fields of struture and append to itab
append wa_it_objap to it_it_objap.
"populate fields of struture and append to itab
append wa_it_dynid to it_it_dynid. . CALL FUNCTION 'BUS_SCR_CONTAINER_MAIN' * EXPORTING * iv_xall = ld_iv_xall * iv_xdelete = ld_iv_xdelete * iv_xdialog = ld_iv_xdialog * TABLES * it_client = it_it_client * it_objap = it_it_objap * it_dynid = it_it_dynid EXCEPTIONS FOREIGN_LOCK = 1 IMPORT_ERROR = 2 SELECTION_NOT_ALLOWED = 3 MAX_USELINES = 4 GENERATION_NOT_NECESSARY = 5 MAX_SECTION = 6 SCREEN_LAYOUT_NOT_ALLOWED = 7 MAX_TRDYN = 8 SYSTEM_ERROR = 9 MAX_VIEW = 10 TRDYN_FAIL = 11 ERRORS_IN_PROTOCOL = 12 . " BUS_SCR_CONTAINER_MAIN
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 4. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 5. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 6. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 7. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 8. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 9. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 10. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 11. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 12. "Exception "Add code for exception here ENDIF.
ABAP code to compare 7.40 inline data declaration with original syntax
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_iv_xall | TYPE BOOLE-BOOLE , |
| it_it_client | TYPE STANDARD TABLE OF BUS_CLIENT_RANGE , |
| wa_it_client | LIKE LINE OF it_it_client, |
| ld_iv_xdelete | TYPE BOOLE-BOOLE , |
| it_it_objap | TYPE STANDARD TABLE OF BUS_OBJAP_RANGE , |
| wa_it_objap | LIKE LINE OF it_it_objap, |
| ld_iv_xdialog | TYPE BOOLE-BOOLE , |
| it_it_dynid | TYPE STANDARD TABLE OF BUS_DYNID_RANGE , |
| wa_it_dynid | LIKE LINE OF it_it_dynid. |
ld_iv_xall = some text here
"populate fields of struture and append to itab
append wa_it_client to it_it_client.
ld_iv_xdelete = some text here
"populate fields of struture and append to itab
append wa_it_objap to it_it_objap.
ld_iv_xdialog = some text here
"populate fields of struture and append to itab
append wa_it_dynid to it_it_dynid.
Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name BUS_SCR_CONTAINER_MAIN or its description.