SAP PDOA_PAYMENT_GET Function Module for Edit Planned Remuneration









PDOA_PAYMENT_GET is a standard pdoa payment get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Edit Planned Remuneration 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 pdoa payment get FM, simply by entering the name PDOA_PAYMENT_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: PDOA
Program Name: SAPLPDOA
Main Program:
Appliation area: H
Release date: 23-Jun-1995
Mode(Normal, Remote etc): Normal Function Module
Update:



Function PDOA_PAYMENT_GET 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 'PDOA_PAYMENT_GET'"Edit Planned Remuneration
EXPORTING
* OTYPE = "
* FIELD = "
* INFOTYPE = "
* BEGDA = "
* ENDDA = "

TABLES
TEXTS = "
.



IMPORTING Parameters details for PDOA_PAYMENT_GET

OTYPE -

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

FIELD -

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

INFOTYPE -

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

BEGDA -

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

ENDDA -

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

TABLES Parameters details for PDOA_PAYMENT_GET

TEXTS -

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

Copy and paste ABAP code example for PDOA_PAYMENT_GET 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_otype  TYPE OBJEC-OTYPE, "   
lt_texts  TYPE STANDARD TABLE OF GSUDISP, "   
lv_field  TYPE GSUDISP, "   
lv_infotype  TYPE GSUDISP, "   
lv_begda  TYPE OBJEC-BEGDA, "   
lv_endda  TYPE OBJEC-ENDDA. "   

  CALL FUNCTION 'PDOA_PAYMENT_GET'  "Edit Planned Remuneration
    EXPORTING
         OTYPE = lv_otype
         FIELD = lv_field
         INFOTYPE = lv_infotype
         BEGDA = lv_begda
         ENDDA = lv_endda
    TABLES
         TEXTS = lt_texts
. " PDOA_PAYMENT_GET




ABAP code using 7.40 inline data declarations to call FM PDOA_PAYMENT_GET

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 OTYPE FROM OBJEC INTO @DATA(ld_otype).
 
 
 
 
"SELECT single BEGDA FROM OBJEC INTO @DATA(ld_begda).
 
"SELECT single ENDDA FROM OBJEC INTO @DATA(ld_endda).
 


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!