EXIT_SAPLHRPFD00VSIP_001 SAP Function module - HR-PF: User Exit for PC Operations

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

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

Pattern for FM EXIT_SAPLHRPFD00VSIP_001 - EXIT SAPLHRPFD00VSIP 001

CALL FUNCTION 'EXIT_SAPLHRPFD00VSIP_001' "HR-PF: User Exit for PC Operations
  EXPORTING
    action =                    " p02vs_lval    HR-CH: Processing control value, long form
*   tclas = 'A'                 " pme17-tclas   Transaction class for data storage
    kasse =                     " t5cp0-kasse   Pension fund
    pernr =                     " p0001-pernr   Personnel number
    pafgr =                     " t5cax-pafgr   HR-CH: Parameter area grouping
    pplan =                     " t5ca4-pplan   Processing schedule
*   rdate =                     " t5cp2-endda   Valid to date
*   entry =                     " t5cpb         HR-CH: Pension fund postings
    testmode =                  " char1         Single-Character Flag
  CHANGING
    evl =                       " p02vs_evl_info_record  HR-CH: PC Interpreter Status Description
    exc_record =                " p02vs_exc_record  HR-CH: PC Exception Description
    values =                    " p02vs_value_tab  HR-CH: PC Value Table
    par_record =                " p02vs_par_record  HR-CH: PC Operation Parameter (Runtime)
    .  "  EXIT_SAPLHRPFD00VSIP_001

ABAP code example for Function Module EXIT_SAPLHRPFD00VSIP_001

The ABAP code below is a full code listing to execute function module EXIT_SAPLHRPFD00VSIP_001 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_evl) = 'Check type of data required'.

DATA(ld_exc_record) = 'Check type of data required'.

DATA(ld_values) = 'Check type of data required'.

DATA(ld_par_record) = 'Check type of data required'.

DATA(ld_action) = 'Check type of data required'.


DATA(ld_tclas) = some text here
 

SELECT single KASSE 
  FROM T5CP0 
  INTO @DATA(ld_kasse).



DATA(ld_pernr) = Check type of data required
 

SELECT single PAFGR 
  FROM T5CAX 
  INTO @DATA(ld_pafgr).

 

SELECT single PPLAN 
  FROM T5CA4 
  INTO @DATA(ld_pplan).

 

SELECT single ENDDA 
  FROM T5CP2 
  INTO @DATA(ld_rdate).


DATA(ld_entry) = 'Check type of data required'.

DATA(ld_testmode) = 'Check type of data required'.
.

CALL FUNCTION 'EXIT_SAPLHRPFD00VSIP_001'
  EXPORTING
    action =                     ld_action
*   tclas =                      ld_tclas
    kasse =                      ld_kasse
    pernr =                      ld_pernr
    pafgr =                      ld_pafgr
    pplan =                      ld_pplan
*   rdate =                      ld_rdate
*   entry =                      ld_entry
    testmode =                   ld_testmode
  CHANGING
    evl =                        ld_evl
    exc_record =                 ld_exc_record
    values =                     ld_values
    par_record =                 ld_par_record
    .  "  EXIT_SAPLHRPFD00VSIP_001

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_evl
 
 TYPE P02VS_EVL_INFO_RECORD ,
ld_action
 
 TYPE P02VS_LVAL ,
ld_exc_record
 
 TYPE P02VS_EXC_RECORD ,
ld_tclas
 
 TYPE PME17-TCLAS ,
ld_values
 
 TYPE P02VS_VALUE_TAB ,
ld_kasse
 
 TYPE T5CP0-KASSE ,
ld_par_record
 
 TYPE P02VS_PAR_RECORD ,
ld_pernr
 
 TYPE P0001-PERNR ,
ld_pafgr
 
 TYPE T5CAX-PAFGR ,
ld_pplan
 
 TYPE T5CA4-PPLAN ,
ld_rdate
 
 TYPE T5CP2-ENDDA ,
ld_entry
 
 TYPE T5CPB ,
ld_testmode
 
 TYPE CHAR1 .


ld_evl = 'Check type of data required'.
ld_action = 'Check type of data required'.
ld_exc_record = 'Check type of data required'.

ld_tclas = some text here
ld_values = 'Check type of data required'.

SELECT single KASSE 
  FROM T5CP0 
  INTO ld_kasse.

ld_par_record = 'Check type of data required'.

ld_pernr = Check type of data required

SELECT single PAFGR 
  FROM T5CAX 
  INTO ld_pafgr.


SELECT single PPLAN 
  FROM T5CA4 
  INTO ld_pplan.


SELECT single ENDDA 
  FROM T5CP2 
  INTO ld_rdate.

ld_entry = 'Check type of data required'.
ld_testmode = 'Check type of data required'.