SAP HR_BG_READ_PYRES_INTERVAL Function Module for Read and process payroll results









HR_BG_READ_PYRES_INTERVAL is a standard hr bg read pyres interval SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read and process payroll results processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for hr bg read pyres interval FM, simply by entering the name HR_BG_READ_PYRES_INTERVAL into the relevant SAP transaction such as SE37 or SE38.

Function Group: 3BG1
Program Name: SAPL3BG1
Main Program: SAPL3BG1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function HR_BG_READ_PYRES_INTERVAL pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'HR_BG_READ_PYRES_INTERVAL'"Read and process payroll results
EXPORTING
PERNR = "Personnel number
TPALL = "Single-character flag
MODE = "Single-character flag
BEGDA = "Start Date
ENDDA = "End Date
* INPER = "In-period for payroll
* BONDT = "Off-cycle payroll payment date
* PAYTY = "Payroll type
* PAYID = "Payroll ID
TPRUN = "Single-character flag

TABLES
* RUNS = "
* MYRG = "
* RTDET = "Type for a table of payroll results
* RTRUN = "
* RTALL = "Payroll Results: Results Table
.



IMPORTING Parameters details for HR_BG_READ_PYRES_INTERVAL

PERNR - Personnel number

Data type: PERNR-PERNR
Optional: No
Call by Reference: Yes

TPALL - Single-character flag

Data type: CHAR1
Optional: No
Call by Reference: Yes

MODE - Single-character flag

Data type: CHAR1
Optional: No
Call by Reference: Yes

BEGDA - Start Date

Data type: BEGDA
Optional: No
Call by Reference: Yes

ENDDA - End Date

Data type: ENDDA
Optional: No
Call by Reference: Yes

INPER - In-period for payroll

Data type: PC261-INPER
Optional: Yes
Call by Reference: Yes

BONDT - Off-cycle payroll payment date

Data type: PC261-BONDT
Optional: Yes
Call by Reference: Yes

PAYTY - Payroll type

Data type: PC261-PAYTY
Optional: Yes
Call by Reference: Yes

PAYID - Payroll ID

Data type: PC261-PAYID
Optional: Yes
Call by Reference: Yes

TPRUN - Single-character flag

Data type: CHAR1
Optional: No
Call by Reference: Yes

TABLES Parameters details for HR_BG_READ_PYRES_INTERVAL

RUNS -

Data type: PBGPY_RUNS_T
Optional: Yes
Call by Reference: Yes

MYRG -

Data type: PBGPY_MYRG_T
Optional: Yes
Call by Reference: Yes

RTDET - Type for a table of payroll results

Data type: HRPAYBG_TAB_OF_RESULTS
Optional: Yes
Call by Reference: Yes

RTRUN -

Data type: PBGPY_RTRUN_T
Optional: Yes
Call by Reference: Yes

RTALL - Payroll Results: Results Table

Data type: PC207
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for HR_BG_READ_PYRES_INTERVAL Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lt_runs  TYPE STANDARD TABLE OF PBGPY_RUNS_T, "   
lv_pernr  TYPE PERNR-PERNR, "   
lv_tpall  TYPE CHAR1, "   
lv_mode  TYPE CHAR1, "   
lt_myrg  TYPE STANDARD TABLE OF PBGPY_MYRG_T, "   
lv_begda  TYPE BEGDA, "   
lt_rtdet  TYPE STANDARD TABLE OF HRPAYBG_TAB_OF_RESULTS, "   
lv_endda  TYPE ENDDA, "   
lt_rtrun  TYPE STANDARD TABLE OF PBGPY_RTRUN_T, "   
lv_inper  TYPE PC261-INPER, "   
lt_rtall  TYPE STANDARD TABLE OF PC207, "   
lv_bondt  TYPE PC261-BONDT, "   
lv_payty  TYPE PC261-PAYTY, "   
lv_payid  TYPE PC261-PAYID, "   
lv_tprun  TYPE CHAR1. "   

  CALL FUNCTION 'HR_BG_READ_PYRES_INTERVAL'  "Read and process payroll results
    EXPORTING
         PERNR = lv_pernr
         TPALL = lv_tpall
         MODE = lv_mode
         BEGDA = lv_begda
         ENDDA = lv_endda
         INPER = lv_inper
         BONDT = lv_bondt
         PAYTY = lv_payty
         PAYID = lv_payid
         TPRUN = lv_tprun
    TABLES
         RUNS = lt_runs
         MYRG = lt_myrg
         RTDET = lt_rtdet
         RTRUN = lt_rtrun
         RTALL = lt_rtall
. " HR_BG_READ_PYRES_INTERVAL




ABAP code using 7.40 inline data declarations to call FM HR_BG_READ_PYRES_INTERVAL

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
"SELECT single PERNR FROM PERNR INTO @DATA(ld_pernr).
 
 
 
 
 
 
 
 
"SELECT single INPER FROM PC261 INTO @DATA(ld_inper).
 
 
"SELECT single BONDT FROM PC261 INTO @DATA(ld_bondt).
 
"SELECT single PAYTY FROM PC261 INTO @DATA(ld_payty).
 
"SELECT single PAYID FROM PC261 INTO @DATA(ld_payid).
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!