SAP PAYMENT_EXTERN_IHC Function Module for Payment Order: Transfer Data to Feeder System
PAYMENT_EXTERN_IHC is a standard payment extern ihc 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 Order: Transfer Data to Feeder System 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 payment extern ihc FM, simply by entering the name PAYMENT_EXTERN_IHC into the relevant SAP transaction such as SE37 or SE38.
Function Group: FBQ4
Program Name: SAPLFBQ4
Main Program: SAPLFBQ4
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function PAYMENT_EXTERN_IHC 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 'PAYMENT_EXTERN_IHC'"Payment Order: Transfer Data to Feeder System.
EXPORTING
I_SENDER = "Ordering Party Data
* I_XDOC = ' ' "X-Zahlungsauftrag erfolgt beleghaft
* I_ORIGIN_TRNSTYPE = ' ' "ursprüngliche Vorgangsart
* I_RETURNKEY = ' ' "Return Reason
I_REF_BKKRS = "Referenzbankkreis im BKK
I_REF_NUMBER = "Referenznummer Zahlungsauftrag im BKK
IMPORTING
E_RETURN = "0-Weitergabe des Zahlungsauftrags war ok
TABLES
T_RECEIVER = "Recipient Data
T_PAYM_NOTE = "Verwendungszweckzeilen
T_MESG = "Table for Messages
IMPORTING Parameters details for PAYMENT_EXTERN_IHC
I_SENDER - Ordering Party Data
Data type: IBKKPO_SNDOptional: No
Call by Reference: No ( called with pass by value option)
I_XDOC - X-Zahlungsauftrag erfolgt beleghaft
Data type: IBKKPOHD-XDOCUMENTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_ORIGIN_TRNSTYPE - ursprüngliche Vorgangsart
Data type: IBKKPOHD-S_TRNSTYPEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_RETURNKEY - Return Reason
Data type: IBKKPOHD-RETURNKDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_REF_BKKRS - Referenzbankkreis im BKK
Data type: IBKKPOHD-BKKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_REF_NUMBER - Referenznummer Zahlungsauftrag im BKK
Data type: IBKKPOHD-PAORNOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for PAYMENT_EXTERN_IHC
E_RETURN - 0-Weitergabe des Zahlungsauftrags war ok
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for PAYMENT_EXTERN_IHC
T_RECEIVER - Recipient Data
Data type: IBKKPO_RCVOptional: No
Call by Reference: No ( called with pass by value option)
T_PAYM_NOTE - Verwendungszweckzeilen
Data type: IBKK_PYNOTOptional: No
Call by Reference: No ( called with pass by value option)
T_MESG - Table for Messages
Data type: IBKKMESGOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PAYMENT_EXTERN_IHC 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_e_return | TYPE SY-SUBRC, " | |||
| lv_i_sender | TYPE IBKKPO_SND, " | |||
| lt_t_receiver | TYPE STANDARD TABLE OF IBKKPO_RCV, " | |||
| lv_i_xdoc | TYPE IBKKPOHD-XDOCUMENT, " SPACE | |||
| lt_t_paym_note | TYPE STANDARD TABLE OF IBKK_PYNOT, " | |||
| lt_t_mesg | TYPE STANDARD TABLE OF IBKKMESG, " | |||
| lv_i_origin_trnstype | TYPE IBKKPOHD-S_TRNSTYPE, " SPACE | |||
| lv_i_returnkey | TYPE IBKKPOHD-RETURNK, " SPACE | |||
| lv_i_ref_bkkrs | TYPE IBKKPOHD-BKKRS, " | |||
| lv_i_ref_number | TYPE IBKKPOHD-PAORN. " |
| CALL FUNCTION 'PAYMENT_EXTERN_IHC' "Payment Order: Transfer Data to Feeder System |
| EXPORTING | ||
| I_SENDER | = lv_i_sender | |
| I_XDOC | = lv_i_xdoc | |
| I_ORIGIN_TRNSTYPE | = lv_i_origin_trnstype | |
| I_RETURNKEY | = lv_i_returnkey | |
| I_REF_BKKRS | = lv_i_ref_bkkrs | |
| I_REF_NUMBER | = lv_i_ref_number | |
| IMPORTING | ||
| E_RETURN | = lv_e_return | |
| TABLES | ||
| T_RECEIVER | = lt_t_receiver | |
| T_PAYM_NOTE | = lt_t_paym_note | |
| T_MESG | = lt_t_mesg | |
| . " PAYMENT_EXTERN_IHC | ||
ABAP code using 7.40 inline data declarations to call FM PAYMENT_EXTERN_IHC
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 SUBRC FROM SY INTO @DATA(ld_e_return). | ||||
| "SELECT single XDOCUMENT FROM IBKKPOHD INTO @DATA(ld_i_xdoc). | ||||
| DATA(ld_i_xdoc) | = ' '. | |||
| "SELECT single S_TRNSTYPE FROM IBKKPOHD INTO @DATA(ld_i_origin_trnstype). | ||||
| DATA(ld_i_origin_trnstype) | = ' '. | |||
| "SELECT single RETURNK FROM IBKKPOHD INTO @DATA(ld_i_returnkey). | ||||
| DATA(ld_i_returnkey) | = ' '. | |||
| "SELECT single BKKRS FROM IBKKPOHD INTO @DATA(ld_i_ref_bkkrs). | ||||
| "SELECT single PAORN FROM IBKKPOHD INTO @DATA(ld_i_ref_number). | ||||
Search for further information about these or an SAP related objects