SAP CHECK_INCOMING_PAYMENT_FLOW Function Module for TR-TM-SE: Check if Flow Is a Payment Receipt Flow

Search SAP Function Modules

CHECK_INCOMING_PAYMENT_FLOW is a standard check incoming payment flow SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for TR-TM-SE: Check if Flow Is a Payment Receipt Flow 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 check incoming payment flow FM, simply by entering the name CHECK_INCOMING_PAYMENT_FLOW into the relevant SAP transaction such as SE37 or SE38.

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

Function CHECK_INCOMING_PAYMENT_FLOW 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 'CHECK_INCOMING_PAYMENT_FLOW'"TR-TM-SE: Check if Flow Is a Payment Receipt Flow
  EXPORTING
   I_FLOW_TYPE =  "Transaction Type
   I_FLOW_CATEGORY =  "Flow Category
*  I_INCLUDE_OUTGOING =  "ausgehende Bewegungen berücksichtigen?

 IMPORTING
   E_INCOMING_PAYMENT_TYPE =  "Einstufiges/Zweistufiges ZE-Verfahren
   E_INCOMING_PAYMENT_STEP =  "Zweistufig: Stufe 1 oder 2
   E_PAYMENT =  "TRPM_CON_TRUE: zahlungswirksam
   E_IS_OUTGOING =  "ausgehende Bewegung

EXCEPTIONS
   ERROR_READING_FLOW_TYPE = 1    I_FLOW_TYPE_INITIAL = 2    I_FLOW_CATEGORY_INITIAL = 3 

.

IMPORTING Parameters details for CHECK_INCOMING_PAYMENT_FLOW

I_FLOW_TYPE - Transaction Type

Data type: TZB0A-SBEWART
Optional: No
Call by Reference: No ( called with pass by value option)

I_FLOW_CATEGORY - Flow Category

Data type: TZB0A-SBEWZITI
Optional: No
Call by Reference: No ( called with pass by value option)

I_INCLUDE_OUTGOING - ausgehende Bewegungen berücksichtigen?

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

EXPORTING Parameters details for CHECK_INCOMING_PAYMENT_FLOW

E_INCOMING_PAYMENT_TYPE - Einstufiges/Zweistufiges ZE-Verfahren

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

E_INCOMING_PAYMENT_STEP - Zweistufig: Stufe 1 oder 2

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

E_PAYMENT - TRPM_CON_TRUE: zahlungswirksam

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

E_IS_OUTGOING - ausgehende Bewegung

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

EXCEPTIONS details

ERROR_READING_FLOW_TYPE - Fehler beim Lesen der Bewegungsart

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

I_FLOW_TYPE_INITIAL -

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

I_FLOW_CATEGORY_INITIAL -

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

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

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