SAP FI_TRANSFER_VENDOR_DATA Function Module for









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

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



Function FI_TRANSFER_VENDOR_DATA 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_TRANSFER_VENDOR_DATA'"
EXPORTING
I_HEADA = "
I_HEADB = "
* I_BRNCA = "
* I_BRNCB = "
.



IMPORTING Parameters details for FI_TRANSFER_VENDOR_DATA

I_HEADA -

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

I_HEADB -

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

I_BRNCA -

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

I_BRNCB -

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

Copy and paste ABAP code example for FI_TRANSFER_VENDOR_DATA 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_heada  TYPE LFA1, "   
lv_i_headb  TYPE LFB1, "   
lv_i_brnca  TYPE LFA1, "   
lv_i_brncb  TYPE LFB1. "   

  CALL FUNCTION 'FI_TRANSFER_VENDOR_DATA'  "
    EXPORTING
         I_HEADA = lv_i_heada
         I_HEADB = lv_i_headb
         I_BRNCA = lv_i_brnca
         I_BRNCB = lv_i_brncb
. " FI_TRANSFER_VENDOR_DATA




ABAP code using 7.40 inline data declarations to call FM FI_TRANSFER_VENDOR_DATA

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!