SAP FAP_PP_GET_CANDIDATE_PAYMENT Function Module for Payment proposal: Get candidate payment

Search SAP Function Modules

FAP_PP_GET_CANDIDATE_PAYMENT is a standard fap pp get candidate payment SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Payment proposal: Get candidate payment 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 fap pp get candidate payment FM, simply by entering the name FAP_PP_GET_CANDIDATE_PAYMENT into the relevant SAP transaction such as SE37 or SE38.

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

Function FAP_PP_GET_CANDIDATE_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 'FAP_PP_GET_CANDIDATE_PAYMENT'"Payment proposal: Get candidate payment
  EXPORTING
   IV_RUN_DATE =  "Date on Which the Program Is to Be Run
   IV_RUN_ID =  "Additional Identification
   IV_PAYING_COMPANY_CODE =  "Paying company code
   IV_SENDING_COMPANY_CODE =  "Sending company code
   IT_ITEM_KEY =  "Item key
   IS_PAYMENT_KEY =  "Payment key

 IMPORTING
   ET_CANDIDATE_PAYMENT =  "Candidate payment
   ET_MSG =  "Return parameter table

.

IMPORTING Parameters details for FAP_PP_GET_CANDIDATE_PAYMENT

IV_RUN_DATE - Date on Which the Program Is to Be Run

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

IV_RUN_ID - Additional Identification

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

IV_PAYING_COMPANY_CODE - Paying company code

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

IV_SENDING_COMPANY_CODE - Sending company code

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

IT_ITEM_KEY - Item key

Data type: CL_FAP_PAYTPRPSL_ITEM=>TY_T_ITEM_KEY
Optional: No
Call by Reference: Yes

IS_PAYMENT_KEY - Payment key

Data type: CL_FAP_PAYTPRPSL_PAYMENT=>TY_S_PAYMENT_KEY
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for FAP_PP_GET_CANDIDATE_PAYMENT

ET_CANDIDATE_PAYMENT - Candidate payment

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

ET_MSG - Return parameter table

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

Copy and paste ABAP code example for FAP_PP_GET_CANDIDATE_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.

ABAP code using 7.40 inline data declarations to call FM FAP_PP_GET_CANDIDATE_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.

Search for further information about these or an SAP related objects