SAP CD_EVALUATION_PERIODS Function Module for Returns Period(s) to be Evaluated with Original View to Table
CD_EVALUATION_PERIODS is a standard cd evaluation periods SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Returns Period(s) to be Evaluated with Original View to Table 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 cd evaluation periods FM, simply by entering the name CD_EVALUATION_PERIODS into the relevant SAP transaction such as SE37 or SE38.
Function Group: RPHI
Program Name: SAPLRPHI
Main Program: SAPLRPHI
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CD_EVALUATION_PERIODS 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 'CD_EVALUATION_PERIODS'"Returns Period(s) to be Evaluated with Original View to Table.
EXPORTING
* BONUS_DATE = '00000000' "Key Date for Check
INPER_MODIF = "Period Parameters
INPER = "Payroll Period
* PAY_TYPE = ' ' "Payroll category
* PAY_IDENT = ' ' "Payroll identifier
* ALL_RESULTS_OF_RUN = 'X' "
TABLES
RGDIR = "Cluster Directory
EVPDIR = "Periods to be Evaluated
* IABKRS = "Payroll Areas
EXCEPTIONS
NO_RECORD_FOUND = 1
IMPORTING Parameters details for CD_EVALUATION_PERIODS
BONUS_DATE - Key Date for Check
Data type: PC261-BONDTDefault: '00000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)
INPER_MODIF - Period Parameters
Data type: PC261-IPERMOptional: No
Call by Reference: No ( called with pass by value option)
INPER - Payroll Period
Data type: PC261-INPEROptional: No
Call by Reference: No ( called with pass by value option)
PAY_TYPE - Payroll category
Data type: PC261-PAYTYDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
PAY_IDENT - Payroll identifier
Data type: PC261-PAYIDDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
ALL_RESULTS_OF_RUN -
Data type: RP_XFELDDefault: 'X'
Optional: Yes
Call by Reference: Yes
TABLES Parameters details for CD_EVALUATION_PERIODS
RGDIR - Cluster Directory
Data type: PC261Optional: No
Call by Reference: No ( called with pass by value option)
EVPDIR - Periods to be Evaluated
Data type: PC261Optional: No
Call by Reference: No ( called with pass by value option)
IABKRS - Payroll Areas
Data type: ABKRS_CDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_RECORD_FOUND - No Valid Payroll Result Found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CD_EVALUATION_PERIODS 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_rgdir | TYPE STANDARD TABLE OF PC261, " | |||
lv_bonus_date | TYPE PC261-BONDT, " '00000000' | |||
lv_no_record_found | TYPE PC261, " | |||
lt_evpdir | TYPE STANDARD TABLE OF PC261, " | |||
lv_inper_modif | TYPE PC261-IPERM, " | |||
lv_inper | TYPE PC261-INPER, " | |||
lt_iabkrs | TYPE STANDARD TABLE OF ABKRS_CD, " | |||
lv_pay_type | TYPE PC261-PAYTY, " ' ' | |||
lv_pay_ident | TYPE PC261-PAYID, " ' ' | |||
lv_all_results_of_run | TYPE RP_XFELD. " 'X' |
  CALL FUNCTION 'CD_EVALUATION_PERIODS' "Returns Period(s) to be Evaluated with Original View to Table |
EXPORTING | ||
BONUS_DATE | = lv_bonus_date | |
INPER_MODIF | = lv_inper_modif | |
INPER | = lv_inper | |
PAY_TYPE | = lv_pay_type | |
PAY_IDENT | = lv_pay_ident | |
ALL_RESULTS_OF_RUN | = lv_all_results_of_run | |
TABLES | ||
RGDIR | = lt_rgdir | |
EVPDIR | = lt_evpdir | |
IABKRS | = lt_iabkrs | |
EXCEPTIONS | ||
NO_RECORD_FOUND = 1 | ||
. " CD_EVALUATION_PERIODS |
ABAP code using 7.40 inline data declarations to call FM CD_EVALUATION_PERIODS
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 BONDT FROM PC261 INTO @DATA(ld_bonus_date). | ||||
DATA(ld_bonus_date) | = '00000000'. | |||
"SELECT single IPERM FROM PC261 INTO @DATA(ld_inper_modif). | ||||
"SELECT single INPER FROM PC261 INTO @DATA(ld_inper). | ||||
"SELECT single PAYTY FROM PC261 INTO @DATA(ld_pay_type). | ||||
DATA(ld_pay_type) | = ' '. | |||
"SELECT single PAYID FROM PC261 INTO @DATA(ld_pay_ident). | ||||
DATA(ld_pay_ident) | = ' '. | |||
DATA(ld_all_results_of_run) | = 'X'. | |||
Search for further information about these or an SAP related objects