SAP IMA_GET_TEXT_PAYM_METHOD Function Module for IO: Gets Description of Payment Method









IMA_GET_TEXT_PAYM_METHOD is a standard ima get text paym method SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IO: Gets Description of Payment Method 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 ima get text paym method FM, simply by entering the name IMA_GET_TEXT_PAYM_METHOD into the relevant SAP transaction such as SE37 or SE38.

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



Function IMA_GET_TEXT_PAYM_METHOD 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 'IMA_GET_TEXT_PAYM_METHOD'"IO: Gets Description of Payment Method
EXPORTING
* IV_EZAWE = "Incoming Payment Method
* IV_AZAWE = "Outgoing payment methods
* IV_OPBUK = "Company Code Group
* IV_VKONT = "Contract Account Number
* IV_GPART = "Business Partner Number

IMPORTING
EV_TEXT_EZAWE = "
EV_TEXT_AZAWE = "

EXCEPTIONS
WRONG_PARAMETERS = 1 ACCOUNT_NOT_FOUND = 2 COMPANY_NOT_FOUND = 3 NOT_FOUND_IN_COUNTRY = 4 NOT_FOUND_IN_COMPANY = 5 NOT_VALID = 6
.



IMPORTING Parameters details for IMA_GET_TEXT_PAYM_METHOD

IV_EZAWE - Incoming Payment Method

Data type: EZAWE_KK
Optional: Yes
Call by Reference: Yes

IV_AZAWE - Outgoing payment methods

Data type: AZAWE_KK
Optional: Yes
Call by Reference: Yes

IV_OPBUK - Company Code Group

Data type: OPBUK_KK
Optional: Yes
Call by Reference: Yes

IV_VKONT - Contract Account Number

Data type: VKONT_KK
Optional: Yes
Call by Reference: Yes

IV_GPART - Business Partner Number

Data type: GPART_KK
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for IMA_GET_TEXT_PAYM_METHOD

EV_TEXT_EZAWE -

Data type: SIMAFLDS-TEZAWE
Optional: No
Call by Reference: Yes

EV_TEXT_AZAWE -

Data type: SIMAFLDS-TAZAWE
Optional: No
Call by Reference: Yes

EXCEPTIONS details

WRONG_PARAMETERS - Incorrect Parameter Transfer

Data type:
Optional: No
Call by Reference: Yes

ACCOUNT_NOT_FOUND - Contract account not found

Data type:
Optional: No
Call by Reference: Yes

COMPANY_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

NOT_FOUND_IN_COUNTRY -

Data type:
Optional: No
Call by Reference: Yes

NOT_FOUND_IN_COMPANY -

Data type:
Optional: No
Call by Reference: Yes

NOT_VALID -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for IMA_GET_TEXT_PAYM_METHOD 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_iv_ezawe  TYPE EZAWE_KK, "   
lv_ev_text_ezawe  TYPE SIMAFLDS-TEZAWE, "   
lv_wrong_parameters  TYPE SIMAFLDS, "   
lv_iv_azawe  TYPE AZAWE_KK, "   
lv_ev_text_azawe  TYPE SIMAFLDS-TAZAWE, "   
lv_account_not_found  TYPE SIMAFLDS, "   
lv_iv_opbuk  TYPE OPBUK_KK, "   
lv_company_not_found  TYPE OPBUK_KK, "   
lv_iv_vkont  TYPE VKONT_KK, "   
lv_not_found_in_country  TYPE VKONT_KK, "   
lv_iv_gpart  TYPE GPART_KK, "   
lv_not_found_in_company  TYPE GPART_KK, "   
lv_not_valid  TYPE GPART_KK. "   

  CALL FUNCTION 'IMA_GET_TEXT_PAYM_METHOD'  "IO: Gets Description of Payment Method
    EXPORTING
         IV_EZAWE = lv_iv_ezawe
         IV_AZAWE = lv_iv_azawe
         IV_OPBUK = lv_iv_opbuk
         IV_VKONT = lv_iv_vkont
         IV_GPART = lv_iv_gpart
    IMPORTING
         EV_TEXT_EZAWE = lv_ev_text_ezawe
         EV_TEXT_AZAWE = lv_ev_text_azawe
    EXCEPTIONS
        WRONG_PARAMETERS = 1
        ACCOUNT_NOT_FOUND = 2
        COMPANY_NOT_FOUND = 3
        NOT_FOUND_IN_COUNTRY = 4
        NOT_FOUND_IN_COMPANY = 5
        NOT_VALID = 6
. " IMA_GET_TEXT_PAYM_METHOD




ABAP code using 7.40 inline data declarations to call FM IMA_GET_TEXT_PAYM_METHOD

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 TEZAWE FROM SIMAFLDS INTO @DATA(ld_ev_text_ezawe).
 
 
 
"SELECT single TAZAWE FROM SIMAFLDS INTO @DATA(ld_ev_text_azawe).
 
 
 
 
 
 
 
 
 


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!