SAP Function Modules
EXIT_SAPLLMOB_508 SAP Function module - USER EXIT - DATA FROM CUSTOMER SCREEN (DUMMY-1760)
EXIT_SAPLLMOB_508 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 EXIT_SAPLLMOB_508 into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
XLHU
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM EXIT_SAPLLMOB_508 - EXIT SAPLLMOB 508
CALL FUNCTION 'EXIT_SAPLLMOB_508' "USER EXIT - DATA FROM CUSTOMER SCREEN (DUMMY-1760)
IMPORTING
o_rlmob_psave = " Push button
o_rlmob_pclear = " Push button
o_rlmob_pback = " Push button
o_rlmob_pnext = " Push button
o_rlmob_clenum = " rlmob-clenum Bar code field for storage unit number
o_vekp_exidv = " External shipping unit ID
o_vekp_werks = " Plant
o_vekp_lgort = " Storage location
o_lein_lgnum = " Warehouse number
o_lein_lgtyp = " Storage type
o_lein_lgpla = " Storage bin
o_rlmob_cmatnr = " Shipping material
o_rlmob_phudtl = " Push button
o_rlmob_pimopt = " Push button
o_rlmob_pwmopt = " Push button
o_rlmob_phuidgen = " Push button
o_current_field = " c
TABLES
o_verification_errors = " sprot_u Customer verification data
. " EXIT_SAPLLMOB_508
ABAP code example for Function Module EXIT_SAPLLMOB_508
The ABAP code below is a full code listing to execute function module EXIT_SAPLLMOB_508 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).
| ld_o_rlmob_psave | TYPE STRING , |
| ld_o_rlmob_pclear | TYPE STRING , |
| ld_o_rlmob_pback | TYPE STRING , |
| ld_o_rlmob_pnext | TYPE STRING , |
| ld_o_rlmob_clenum | TYPE RLMOB-CLENUM , |
| ld_o_vekp_exidv | TYPE STRING , |
| ld_o_vekp_werks | TYPE STRING , |
| ld_o_vekp_lgort | TYPE STRING , |
| ld_o_lein_lgnum | TYPE STRING , |
| ld_o_lein_lgtyp | TYPE STRING , |
| ld_o_lein_lgpla | TYPE STRING , |
| ld_o_rlmob_cmatnr | TYPE STRING , |
| ld_o_rlmob_phudtl | TYPE STRING , |
| ld_o_rlmob_pimopt | TYPE STRING , |
| ld_o_rlmob_pwmopt | TYPE STRING , |
| ld_o_rlmob_phuidgen | TYPE STRING , |
| ld_o_current_field | TYPE C , |
| it_o_verification_errors | TYPE STANDARD TABLE OF SPROT_U,"TABLES PARAM |
| wa_o_verification_errors | LIKE LINE OF it_o_verification_errors . |
"populate fields of struture and append to itab
append wa_o_verification_errors to it_o_verification_errors. . CALL FUNCTION 'EXIT_SAPLLMOB_508' IMPORTING o_rlmob_psave = ld_o_rlmob_psave o_rlmob_pclear = ld_o_rlmob_pclear o_rlmob_pback = ld_o_rlmob_pback o_rlmob_pnext = ld_o_rlmob_pnext o_rlmob_clenum = ld_o_rlmob_clenum o_vekp_exidv = ld_o_vekp_exidv o_vekp_werks = ld_o_vekp_werks o_vekp_lgort = ld_o_vekp_lgort o_lein_lgnum = ld_o_lein_lgnum o_lein_lgtyp = ld_o_lein_lgtyp o_lein_lgpla = ld_o_lein_lgpla o_rlmob_cmatnr = ld_o_rlmob_cmatnr o_rlmob_phudtl = ld_o_rlmob_phudtl o_rlmob_pimopt = ld_o_rlmob_pimopt o_rlmob_pwmopt = ld_o_rlmob_pwmopt o_rlmob_phuidgen = ld_o_rlmob_phuidgen o_current_field = ld_o_current_field TABLES o_verification_errors = it_o_verification_errors . " EXIT_SAPLLMOB_508
IF SY-SUBRC EQ 0. "All OK 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_o_rlmob_psave | TYPE STRING , |
| it_o_verification_errors | TYPE STANDARD TABLE OF SPROT_U , |
| wa_o_verification_errors | LIKE LINE OF it_o_verification_errors, |
| ld_o_rlmob_pclear | TYPE STRING , |
| ld_o_rlmob_pback | TYPE STRING , |
| ld_o_rlmob_pnext | TYPE STRING , |
| ld_o_rlmob_clenum | TYPE RLMOB-CLENUM , |
| ld_o_vekp_exidv | TYPE STRING , |
| ld_o_vekp_werks | TYPE STRING , |
| ld_o_vekp_lgort | TYPE STRING , |
| ld_o_lein_lgnum | TYPE STRING , |
| ld_o_lein_lgtyp | TYPE STRING , |
| ld_o_lein_lgpla | TYPE STRING , |
| ld_o_rlmob_cmatnr | TYPE STRING , |
| ld_o_rlmob_phudtl | TYPE STRING , |
| ld_o_rlmob_pimopt | TYPE STRING , |
| ld_o_rlmob_pwmopt | TYPE STRING , |
| ld_o_rlmob_phuidgen | TYPE STRING , |
| ld_o_current_field | TYPE C . |
"populate fields of struture and append to itab
append wa_o_verification_errors to it_o_verification_errors.
SAP Documentation for FM EXIT_SAPLLMOB_508
The function transfers data from customer screen if the customer exit
is activated. Customer screen should be created in module pool
...See here for full SAP fm documentation
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 EXIT_SAPLLMOB_508 or its description.
EXIT_SAPLLMOB_508 - USER EXIT - DATA FROM CUSTOMER SCREEN (DUMMY-1760) EXIT_SAPLLMOB_506 - USER EXIT - DATA FROM CUSTOMER SCREEN (DUMMY-1705) EXIT_SAPLLMOB_505 - USER EXIT - DATA FROM CUSTOMER SCREEN (DUMMY-1704) EXIT_SAPLLMOB_504 - USER EXIT - DATA FROM CUSTOMER SCREEN (DUMMY-1703) EXIT_SAPLLMOB_503 - USER EXIT - DATA FROM CUSTOMER SCREEN (DUMMY-1702) EXIT_SAPLLMOB_502 - USER EXIT - DATA FROM CUSTOMER SCREEN (DUMMY-1701)