HRPY_AU_CHK_PYSUM_OVERLAP SAP Function module - Check for payroll summary overlap

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

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

Pattern for FM HRPY_AU_CHK_PYSUM_OVERLAP - HRPY AU CHK PYSUM OVERLAP

CALL FUNCTION 'HRPY_AU_CHK_PYSUM_OVERLAP' "Check for payroll summary overlap
  EXPORTING
    l_fy_start_date =           "
    l_fy_end_date =             "
*   l_use_seqnr = 'N'           " c
*   p0626comp =                 " p0626         HR Master Record for Infotype 0626
  TABLES
    p0626a =                    " p0626         HR Master Record for Infotype 0626
  EXCEPTIONS
    OVERLAPPING_RECORD = 1      "               An active overlapping 626 record exists
    .  "  HRPY_AU_CHK_PYSUM_OVERLAP

ABAP code example for Function Module HRPY_AU_CHK_PYSUM_OVERLAP

The ABAP code below is a full code listing to execute function module HRPY_AU_CHK_PYSUM_OVERLAP 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:
it_p0626a  
 
 TYPE STANDARD TABLE OF P0626,"TABLES PARAM
wa_p0626a
 
 LIKE LINE OF it_p0626a
.


DATA(ld_l_fy_start_date) = 'some text here'.

DATA(ld_l_fy_end_date) = 'some text here'.

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

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

"populate fields of struture and append to itab
append wa_p0626a to it_p0626a.
.

CALL FUNCTION 'HRPY_AU_CHK_PYSUM_OVERLAP'
  EXPORTING
    l_fy_start_date =            ld_l_fy_start_date
    l_fy_end_date =              ld_l_fy_end_date
*   l_use_seqnr =                ld_l_use_seqnr
*   p0626comp =                  ld_p0626comp
  TABLES
    p0626a =                     it_p0626a
  EXCEPTIONS
    OVERLAPPING_RECORD =         1
    .  "  HRPY_AU_CHK_PYSUM_OVERLAP

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_l_fy_start_date
 
 TYPE STRING ,
it_p0626a
 
 TYPE STANDARD TABLE OF P0626 ,
wa_p0626a
 
 LIKE LINE OF it_p0626a,
ld_l_fy_end_date
 
 TYPE STRING ,
ld_l_use_seqnr
 
 TYPE C ,
ld_p0626comp
 
 TYPE P0626 .


ld_l_fy_start_date = 'some text here'. 

"populate fields of struture and append to itab
append wa_p0626a to it_p0626a.
ld_l_fy_end_date = 'some text here'.
ld_l_use_seqnr = 'Check type of data required'.
ld_p0626comp = 'Check type of data required'.