SAP FARMATCH_CHANGE_PAYMENT_ADVICE Function Module for









FARMATCH_CHANGE_PAYMENT_ADVICE is a standard farmatch change payment advice SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 farmatch change payment advice FM, simply by entering the name FARMATCH_CHANGE_PAYMENT_ADVICE into the relevant SAP transaction such as SE37 or SE38.

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



Function FARMATCH_CHANGE_PAYMENT_ADVICE 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 'FARMATCH_CHANGE_PAYMENT_ADVICE'"
  EXPORTING
   ID_BUKRS =  "
   ID_GJAHR =  "
   ID_BELNR =  "
   ID_BUZEI =  "
   ID_SGTXT =  "
   ID_NEBTR =  "

EXCEPTIONS
   INCORRECT_INPUT = 1    NOT_EXISTING = 2
.



IMPORTING Parameters details for FARMATCH_CHANGE_PAYMENT_ADVICE

ID_BUKRS -

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

ID_GJAHR -

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

ID_BELNR -

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

ID_BUZEI -

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

ID_SGTXT -

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

ID_NEBTR -

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

EXCEPTIONS details

INCORRECT_INPUT -

Data type:
Optional: No
Call by Reference: Yes

NOT_EXISTING -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FARMATCH_CHANGE_PAYMENT_ADVICE 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_id_bukrs  TYPE BUKRS, "   
lv_incorrect_input  TYPE BUKRS, "   
lv_id_gjahr  TYPE GJAHR, "   
lv_not_existing  TYPE GJAHR, "   
lv_id_belnr  TYPE BELNR_D, "   
lv_id_buzei  TYPE BUZEI, "   
lv_id_sgtxt  TYPE SGTXT, "   
lv_id_nebtr  TYPE NEBTR. "   

  CALL FUNCTION 'FARMATCH_CHANGE_PAYMENT_ADVICE'  "
    EXPORTING
         ID_BUKRS = lv_id_bukrs
         ID_GJAHR = lv_id_gjahr
         ID_BELNR = lv_id_belnr
         ID_BUZEI = lv_id_buzei
         ID_SGTXT = lv_id_sgtxt
         ID_NEBTR = lv_id_nebtr
    EXCEPTIONS
        INCORRECT_INPUT = 1
        NOT_EXISTING = 2
. " FARMATCH_CHANGE_PAYMENT_ADVICE




ABAP code using 7.40 inline data declarations to call FM FARMATCH_CHANGE_PAYMENT_ADVICE

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



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!