SAP FI_VENDOR_ALTERN_PAYER_CHECK Function Module for









FI_VENDOR_ALTERN_PAYER_CHECK is a standard fi vendor altern payer check 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 fi vendor altern payer check FM, simply by entering the name FI_VENDOR_ALTERN_PAYER_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function FI_VENDOR_ALTERN_PAYER_CHECK 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 'FI_VENDOR_ALTERN_PAYER_CHECK'"
EXPORTING
I_LIFNR = "
* I_FILKD = "
I_BUKRS = "Company Code
I_EMPFB = "
* I_LFB1_HEAD_OFFICE = "

EXCEPTIONS
PAYER_INVALID = 1
.



IMPORTING Parameters details for FI_VENDOR_ALTERN_PAYER_CHECK

I_LIFNR -

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

I_FILKD -

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

I_BUKRS - Company Code

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

I_EMPFB -

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

I_LFB1_HEAD_OFFICE -

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

EXCEPTIONS details

PAYER_INVALID -

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

Copy and paste ABAP code example for FI_VENDOR_ALTERN_PAYER_CHECK 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_i_lifnr  TYPE LFA1-LIFNR, "   
lv_payer_invalid  TYPE LFA1, "   
lv_i_filkd  TYPE BSEG-FILKD, "   
lv_i_bukrs  TYPE LFB1-BUKRS, "   
lv_i_empfb  TYPE BSEG-EMPFB, "   
lv_i_lfb1_head_office  TYPE LFB1. "   

  CALL FUNCTION 'FI_VENDOR_ALTERN_PAYER_CHECK'  "
    EXPORTING
         I_LIFNR = lv_i_lifnr
         I_FILKD = lv_i_filkd
         I_BUKRS = lv_i_bukrs
         I_EMPFB = lv_i_empfb
         I_LFB1_HEAD_OFFICE = lv_i_lfb1_head_office
    EXCEPTIONS
        PAYER_INVALID = 1
. " FI_VENDOR_ALTERN_PAYER_CHECK




ABAP code using 7.40 inline data declarations to call FM FI_VENDOR_ALTERN_PAYER_CHECK

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 LIFNR FROM LFA1 INTO @DATA(ld_i_lifnr).
 
 
"SELECT single FILKD FROM BSEG INTO @DATA(ld_i_filkd).
 
"SELECT single BUKRS FROM LFB1 INTO @DATA(ld_i_bukrs).
 
"SELECT single EMPFB FROM BSEG INTO @DATA(ld_i_empfb).
 
 


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!