SAP CD_READ_DATE_RANGE_WITH_PAYDT Function Module for
CD_READ_DATE_RANGE_WITH_PAYDT is a standard cd read date range with paydt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 read date range with paydt FM, simply by entering the name CD_READ_DATE_RANGE_WITH_PAYDT into the relevant SAP transaction such as SE37 or SE38.
Function Group: RPHI
Program Name: SAPLRPHI
Main Program: SAPLRPHI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CD_READ_DATE_RANGE_WITH_PAYDT 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_READ_DATE_RANGE_WITH_PAYDT'".
EXPORTING
BEGDA = "
ENDDA = "
TABLES
RGDIR_IN = "
RGDIR_OUT = "
IMPORTING Parameters details for CD_READ_DATE_RANGE_WITH_PAYDT
BEGDA -
Data type: PC261-FPBEGOptional: No
Call by Reference: Yes
ENDDA -
Data type: PC261-FPENDOptional: No
Call by Reference: Yes
TABLES Parameters details for CD_READ_DATE_RANGE_WITH_PAYDT
RGDIR_IN -
Data type: PC261Optional: No
Call by Reference: Yes
RGDIR_OUT -
Data type: PC261Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CD_READ_DATE_RANGE_WITH_PAYDT 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: | ||||
lv_begda | TYPE PC261-FPBEG, " | |||
lt_rgdir_in | TYPE STANDARD TABLE OF PC261, " | |||
lv_endda | TYPE PC261-FPEND, " | |||
lt_rgdir_out | TYPE STANDARD TABLE OF PC261. " |
  CALL FUNCTION 'CD_READ_DATE_RANGE_WITH_PAYDT' " |
EXPORTING | ||
BEGDA | = lv_begda | |
ENDDA | = lv_endda | |
TABLES | ||
RGDIR_IN | = lt_rgdir_in | |
RGDIR_OUT | = lt_rgdir_out | |
. " CD_READ_DATE_RANGE_WITH_PAYDT |
ABAP code using 7.40 inline data declarations to call FM CD_READ_DATE_RANGE_WITH_PAYDT
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 FPBEG FROM PC261 INTO @DATA(ld_begda). | ||||
"SELECT single FPEND FROM PC261 INTO @DATA(ld_endda). | ||||
Search for further information about these or an SAP related objects