PMIQ_BUPA_READ_PERSONAL_DATA SAP Function module - Read student personal data from DB

PMIQ_BUPA_READ_PERSONAL_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 PMIQ_BUPA_READ_PERSONAL_DATA into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: PMIQ_HR
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM PMIQ_BUPA_READ_PERSONAL_DATA - PMIQ BUPA READ PERSONAL DATA

CALL FUNCTION 'PMIQ_BUPA_READ_PERSONAL_DATA' "Read student personal data from DB
  EXPORTING
*   iv_plvar = '01'             " wplog-plvar   Plan Version
    iv_stobjid =                " piq_bpsync-stobjid  Global information for student data synchronisation(HR->BP)
*   iv_valdt = SY-DATUM         " sy-datum      Date and Time, Current (Application Server) Date
*   iv_begda = '19000101'       " begdatum      Start Date
*   iv_endda = '99991231'       " enddatum      End Date
  IMPORTING
    es_personaldata =           " p1702         Infotype 1702: Personal Data
    et_personaldata =           " piq_p1702     Table type for 1702
  EXCEPTIONS
    STUDENT_ERROR = 1           "               Student master data has error
    .  "  PMIQ_BUPA_READ_PERSONAL_DATA

ABAP code example for Function Module PMIQ_BUPA_READ_PERSONAL_DATA

The ABAP code below is a full code listing to execute function module PMIQ_BUPA_READ_PERSONAL_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).

DATA:
ld_es_personaldata  
 
 TYPE P1702
,
ld_et_personaldata  
 
 TYPE PIQ_P1702
.



DATA(ld_iv_plvar) = some text here


DATA(ld_iv_stobjid) = Check type of data required

DATA(ld_iv_valdt) = '20210129'.

DATA(ld_iv_begda) = '20210129'.

DATA(ld_iv_endda) = '20210129'.
.

CALL FUNCTION 'PMIQ_BUPA_READ_PERSONAL_DATA'
  EXPORTING
*   iv_plvar =                   ld_iv_plvar
    iv_stobjid =                 ld_iv_stobjid
*   iv_valdt =                   ld_iv_valdt
*   iv_begda =                   ld_iv_begda
*   iv_endda =                   ld_iv_endda
  IMPORTING
    es_personaldata =            ld_es_personaldata
    et_personaldata =            ld_et_personaldata
  EXCEPTIONS
    STUDENT_ERROR =              1
    .  "  PMIQ_BUPA_READ_PERSONAL_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_es_personaldata
 
 TYPE P1702 ,
ld_iv_plvar
 
 TYPE WPLOG-PLVAR ,
ld_et_personaldata
 
 TYPE PIQ_P1702 ,
ld_iv_stobjid
 
 TYPE PIQ_BPSYNC-STOBJID ,
ld_iv_valdt
 
 TYPE SY-DATUM ,
ld_iv_begda
 
 TYPE BEGDATUM ,
ld_iv_endda
 
 TYPE ENDDATUM .



ld_iv_plvar = some text here

ld_iv_stobjid = Check type of data required
ld_iv_valdt = '20210129'.
ld_iv_begda = '20210129'.
ld_iv_endda = '20210129'.