SAP PCLO_GET_VALUE_DATE_PAYMENT Function Module for









PCLO_GET_VALUE_DATE_PAYMENT is a standard pclo get value date payment 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 pclo get value date payment FM, simply by entering the name PCLO_GET_VALUE_DATE_PAYMENT into the relevant SAP transaction such as SE37 or SE38.

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



Function PCLO_GET_VALUE_DATE_PAYMENT 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 'PCLO_GET_VALUE_DATE_PAYMENT'"
  EXPORTING
   PF_ZAHLA =  "
*  PF_PERIOD_BEGDA =  "
*  PF_PERIOD_ENDDA =  "
   PF_PAYMENT_BEGDA =  "
   PF_PAYMENT_ENDDA =  "
   PF_MOLGA =  "
   PF_ABKRS =  "
*  PF_ABKRS_BEGDA = '19000101' "
*  PF_ABKRS_ENDDA = '99991231' "
*  PF_PAPER =  "
*  PF_PERIOD_VALUE_DATE =  "

 IMPORTING
   PFX_VALUE_DATE =  "

EXCEPTIONS
   ERROR = 1    PAYMENT_NOT_IN_PERIOD = 2
.



IMPORTING Parameters details for PCLO_GET_VALUE_DATE_PAYMENT

PF_ZAHLA -

Data type: DZAHLA
Optional: No
Call by Reference: No ( called with pass by value option)

PF_PERIOD_BEGDA -

Data type: BEGDA
Optional: Yes
Call by Reference: No ( called with pass by value option)

PF_PERIOD_ENDDA -

Data type: ENDDA
Optional: Yes
Call by Reference: No ( called with pass by value option)

PF_PAYMENT_BEGDA -

Data type: BEGDA
Optional: No
Call by Reference: No ( called with pass by value option)

PF_PAYMENT_ENDDA -

Data type: ENDDA
Optional: No
Call by Reference: No ( called with pass by value option)

PF_MOLGA -

Data type: MOLGA
Optional: No
Call by Reference: No ( called with pass by value option)

PF_ABKRS -

Data type: ABKRS
Optional: No
Call by Reference: No ( called with pass by value option)

PF_ABKRS_BEGDA -

Data type: BEGDA
Default: '19000101'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PF_ABKRS_ENDDA -

Data type: ENDDA
Default: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PF_PAPER -

Data type: PC2PAPER
Optional: Yes
Call by Reference: No ( called with pass by value option)

PF_PERIOD_VALUE_DATE -

Data type: DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for PCLO_GET_VALUE_DATE_PAYMENT

PFX_VALUE_DATE -

Data type: DATUM
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ERROR -

Data type:
Optional: No
Call by Reference: Yes

PAYMENT_NOT_IN_PERIOD -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PCLO_GET_VALUE_DATE_PAYMENT 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_error  TYPE STRING, "   
lv_pf_zahla  TYPE DZAHLA, "   
lv_pfx_value_date  TYPE DATUM, "   
lv_pf_period_begda  TYPE BEGDA, "   
lv_pf_period_endda  TYPE ENDDA, "   
lv_pf_payment_begda  TYPE BEGDA, "   
lv_payment_not_in_period  TYPE BEGDA, "   
lv_pf_payment_endda  TYPE ENDDA, "   
lv_pf_molga  TYPE MOLGA, "   
lv_pf_abkrs  TYPE ABKRS, "   
lv_pf_abkrs_begda  TYPE BEGDA, "   '19000101'
lv_pf_abkrs_endda  TYPE ENDDA, "   '99991231'
lv_pf_paper  TYPE PC2PAPER, "   
lv_pf_period_value_date  TYPE DATUM. "   

  CALL FUNCTION 'PCLO_GET_VALUE_DATE_PAYMENT'  "
    EXPORTING
         PF_ZAHLA = lv_pf_zahla
         PF_PERIOD_BEGDA = lv_pf_period_begda
         PF_PERIOD_ENDDA = lv_pf_period_endda
         PF_PAYMENT_BEGDA = lv_pf_payment_begda
         PF_PAYMENT_ENDDA = lv_pf_payment_endda
         PF_MOLGA = lv_pf_molga
         PF_ABKRS = lv_pf_abkrs
         PF_ABKRS_BEGDA = lv_pf_abkrs_begda
         PF_ABKRS_ENDDA = lv_pf_abkrs_endda
         PF_PAPER = lv_pf_paper
         PF_PERIOD_VALUE_DATE = lv_pf_period_value_date
    IMPORTING
         PFX_VALUE_DATE = lv_pfx_value_date
    EXCEPTIONS
        ERROR = 1
        PAYMENT_NOT_IN_PERIOD = 2
. " PCLO_GET_VALUE_DATE_PAYMENT




ABAP code using 7.40 inline data declarations to call FM PCLO_GET_VALUE_DATE_PAYMENT

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.

 
 
 
 
 
 
 
 
 
 
DATA(ld_pf_abkrs_begda) = '19000101'.
 
DATA(ld_pf_abkrs_endda) = '99991231'.
 
 
 


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!