SAP Function Modules
EXIT_SAPLLMOB_630 SAP Function module - USER EXIT - DATA FROM CUSTOMER SCREEN (DUMMY 1405)
EXIT_SAPLLMOB_630 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_630 into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
XLRF
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM EXIT_SAPLLMOB_630 - EXIT SAPLLMOB 630
CALL FUNCTION 'EXIT_SAPLLMOB_630' "USER EXIT - DATA FROM CUSTOMER SCREEN (DUMMY 1405)
IMPORTING
o_rlmob_psave = " Push button
o_rlmob_pclear = " Pushbutton
o_rlmob_pback = " Push button
o_rlmob_pnext = " Push button
o_rlmob_pdetail = " Push button
o_rlmob_ppgup = " Push button
o_rlmob_ppgdn = " Push button
o_rlmob_pdiff = " Push button
o_ltap_kzqui = " Input Field
o_rlmob_clgpla = " Bin Verification Field
o_rlmob_clenum = " Storage Unit Verification Field
o_rlmob_cmatnr = " Material Verification Field
o_rlmob_cqty = " Quantity Verification Field
o_rlmob_penter = "
/cwm/saplxlrf_exits = " ise_saplxlrf_exits IS Erweiterungsstruktur - SAPLXLRF UserExits
TABLES
o_verification_errors = " sprot_u Customer Verification Data
. " EXIT_SAPLLMOB_630
ABAP code example for Function Module EXIT_SAPLLMOB_630
The ABAP code below is a full code listing to execute function module EXIT_SAPLLMOB_630 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_pdetail | TYPE STRING , |
| ld_o_rlmob_ppgup | TYPE STRING , |
| ld_o_rlmob_ppgdn | TYPE STRING , |
| ld_o_rlmob_pdiff | TYPE STRING , |
| ld_o_ltap_kzqui | TYPE STRING , |
| ld_o_rlmob_clgpla | TYPE STRING , |
| ld_o_rlmob_clenum | TYPE STRING , |
| ld_o_rlmob_cmatnr | TYPE STRING , |
| ld_o_rlmob_cqty | TYPE STRING , |
| ld_o_rlmob_penter | TYPE STRING , |
| ld_/cwm/saplxlrf_exits | TYPE ISE_SAPLXLRF_EXITS , |
| 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_630' 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_pdetail = ld_o_rlmob_pdetail o_rlmob_ppgup = ld_o_rlmob_ppgup o_rlmob_ppgdn = ld_o_rlmob_ppgdn o_rlmob_pdiff = ld_o_rlmob_pdiff o_ltap_kzqui = ld_o_ltap_kzqui o_rlmob_clgpla = ld_o_rlmob_clgpla o_rlmob_clenum = ld_o_rlmob_clenum o_rlmob_cmatnr = ld_o_rlmob_cmatnr o_rlmob_cqty = ld_o_rlmob_cqty o_rlmob_penter = ld_o_rlmob_penter /cwm/saplxlrf_exits = ld_/cwm/saplxlrf_exits TABLES o_verification_errors = it_o_verification_errors . " EXIT_SAPLLMOB_630
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_pdetail | TYPE STRING , |
| ld_o_rlmob_ppgup | TYPE STRING , |
| ld_o_rlmob_ppgdn | TYPE STRING , |
| ld_o_rlmob_pdiff | TYPE STRING , |
| ld_o_ltap_kzqui | TYPE STRING , |
| ld_o_rlmob_clgpla | TYPE STRING , |
| ld_o_rlmob_clenum | TYPE STRING , |
| ld_o_rlmob_cmatnr | TYPE STRING , |
| ld_o_rlmob_cqty | TYPE STRING , |
| ld_o_rlmob_penter | TYPE STRING , |
| ld_/cwm/saplxlrf_exits | TYPE ISE_SAPLXLRF_EXITS . |
"populate fields of struture and append to itab
append wa_o_verification_errors to it_o_verification_errors.
SAP Documentation for FM EXIT_SAPLLMOB_630
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_630 or its description.
EXIT_SAPLLMOB_630 - USER EXIT - DATA FROM CUSTOMER SCREEN (DUMMY 1405) EXIT_SAPLLMOB_620 - USER EXIT - DATA FROM CUSTOMER SCREEN (DUMMY 1404) EXIT_SAPLLMOB_610 - USER EXIT - DATA FROM CUSTOMER SCREEN (DUMMY 1403) EXIT_SAPLLMOB_600 - USER EXIT - DATA FROM CUSTOMER SCREEN (DUMMY 1402) EXIT_SAPLLMOB_590 - USER EXIT - DATA FROM CUSTOMER SCREEN (DUMMY 1400) EXIT_SAPLLMOB_580 - USER EXIT - DATA FROM CUSTOMER SCREEN (DUMMY 1321)