SAP Function Modules
HR_E_GET_JUPER_DATA SAP Function module
HR_E_GET_JUPER_DATA 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 HR_E_GET_JUPER_DATA into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
34CT
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM HR_E_GET_JUPER_DATA - HR E GET JUPER DATA
CALL FUNCTION 'HR_E_GET_JUPER_DATA' "
EXPORTING
p_juper = " t001p-juper
* p_actual_date = SY-DATUM " d
IMPORTING
p_deleg_hacienda = " t5e02-dehac
p_admin_hacienda = " t5e02-adhac
p_empresa_nif = " t5e02-finnr
p_empresa_nombre = "
p_direcc_sigla = "
p_direcc_via_pub = "
p_direcc_numero = "
p_direcc_escalera = "
p_direcc_piso = "
p_direcc_puerta = "
p_direcc_cod_post = "
p_direcc_muncipio = "
p_direcc_provincia = "
p_persona_tel = "
p_persona_nombre = "
p_represent = " pesw0_juper_data-represent
p_juper_list = " pesw0_juper_list_tab
p_juper_data = " pesw0_juper_data
EXCEPTIONS
ERROR = 1 "
. " HR_E_GET_JUPER_DATA
ABAP code example for Function Module HR_E_GET_JUPER_DATA
The ABAP code below is a full code listing to execute function module HR_E_GET_JUPER_DATA 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_p_deleg_hacienda | TYPE T5E02-DEHAC , |
| ld_p_admin_hacienda | TYPE T5E02-ADHAC , |
| ld_p_empresa_nif | TYPE T5E02-FINNR , |
| ld_p_empresa_nombre | TYPE STRING , |
| ld_p_direcc_sigla | TYPE STRING , |
| ld_p_direcc_via_pub | TYPE STRING , |
| ld_p_direcc_numero | TYPE STRING , |
| ld_p_direcc_escalera | TYPE STRING , |
| ld_p_direcc_piso | TYPE STRING , |
| ld_p_direcc_puerta | TYPE STRING , |
| ld_p_direcc_cod_post | TYPE STRING , |
| ld_p_direcc_muncipio | TYPE STRING , |
| ld_p_direcc_provincia | TYPE STRING , |
| ld_p_persona_tel | TYPE STRING , |
| ld_p_persona_nombre | TYPE STRING , |
| ld_p_represent | TYPE PESW0_JUPER_DATA-REPRESENT , |
| ld_p_juper_list | TYPE PESW0_JUPER_LIST_TAB , |
| ld_p_juper_data | TYPE PESW0_JUPER_DATA . |
SELECT single JUPER
FROM T001P
INTO @DATA(ld_p_juper).
DATA(ld_p_actual_date) = 'Check type of data required'. . CALL FUNCTION 'HR_E_GET_JUPER_DATA' EXPORTING p_juper = ld_p_juper * p_actual_date = ld_p_actual_date IMPORTING p_deleg_hacienda = ld_p_deleg_hacienda p_admin_hacienda = ld_p_admin_hacienda p_empresa_nif = ld_p_empresa_nif p_empresa_nombre = ld_p_empresa_nombre p_direcc_sigla = ld_p_direcc_sigla p_direcc_via_pub = ld_p_direcc_via_pub p_direcc_numero = ld_p_direcc_numero p_direcc_escalera = ld_p_direcc_escalera p_direcc_piso = ld_p_direcc_piso p_direcc_puerta = ld_p_direcc_puerta p_direcc_cod_post = ld_p_direcc_cod_post p_direcc_muncipio = ld_p_direcc_muncipio p_direcc_provincia = ld_p_direcc_provincia p_persona_tel = ld_p_persona_tel p_persona_nombre = ld_p_persona_nombre p_represent = ld_p_represent p_juper_list = ld_p_juper_list p_juper_data = ld_p_juper_data EXCEPTIONS ERROR = 1 . " HR_E_GET_JUPER_DATA
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "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_p_deleg_hacienda | TYPE T5E02-DEHAC , |
| ld_p_juper | TYPE T001P-JUPER , |
| ld_p_admin_hacienda | TYPE T5E02-ADHAC , |
| ld_p_actual_date | TYPE D , |
| ld_p_empresa_nif | TYPE T5E02-FINNR , |
| ld_p_empresa_nombre | TYPE STRING , |
| ld_p_direcc_sigla | TYPE STRING , |
| ld_p_direcc_via_pub | TYPE STRING , |
| ld_p_direcc_numero | TYPE STRING , |
| ld_p_direcc_escalera | TYPE STRING , |
| ld_p_direcc_piso | TYPE STRING , |
| ld_p_direcc_puerta | TYPE STRING , |
| ld_p_direcc_cod_post | TYPE STRING , |
| ld_p_direcc_muncipio | TYPE STRING , |
| ld_p_direcc_provincia | TYPE STRING , |
| ld_p_persona_tel | TYPE STRING , |
| ld_p_persona_nombre | TYPE STRING , |
| ld_p_represent | TYPE PESW0_JUPER_DATA-REPRESENT , |
| ld_p_juper_list | TYPE PESW0_JUPER_LIST_TAB , |
| ld_p_juper_data | TYPE PESW0_JUPER_DATA . |
SELECT single JUPER
FROM T001P
INTO ld_p_juper.
ld_p_actual_date = 'Check type of data required'.
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 HR_E_GET_JUPER_DATA or its description.