SAP FM_LG_ACCOUNTS_DERIVE Function Module for Interface for value types and G/L accounts assignment
FM_LG_ACCOUNTS_DERIVE is a standard fm lg accounts derive SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Interface for value types and G/L accounts assignment 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 fm lg accounts derive FM, simply by entering the name FM_LG_ACCOUNTS_DERIVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMBL_LGBT_E
Program Name: SAPLFMBL_LGBT_E
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FM_LG_ACCOUNTS_DERIVE 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 'FM_LG_ACCOUNTS_DERIVE'"Interface for value types and G/L accounts assignment.
EXPORTING
I_FLAG_ACCOUNT_DERIVE_VT = "Flag for account derivation via value type only
TABLES
T_IFMVTGL = "
IMPORTING Parameters details for FM_LG_ACCOUNTS_DERIVE
I_FLAG_ACCOUNT_DERIVE_VT - Flag for account derivation via value type only
Data type: FMDY-XFELDOptional: No
Call by Reference: Yes
TABLES Parameters details for FM_LG_ACCOUNTS_DERIVE
T_IFMVTGL -
Data type: IFMVTGLOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FM_LG_ACCOUNTS_DERIVE 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: | ||||
| lt_t_ifmvtgl | TYPE STANDARD TABLE OF IFMVTGL, " | |||
| lv_i_flag_account_derive_vt | TYPE FMDY-XFELD. " |
|   CALL FUNCTION 'FM_LG_ACCOUNTS_DERIVE' "Interface for value types and G/L accounts assignment |
| EXPORTING | ||
| I_FLAG_ACCOUNT_DERIVE_VT | = lv_i_flag_account_derive_vt | |
| TABLES | ||
| T_IFMVTGL | = lt_t_ifmvtgl | |
| . " FM_LG_ACCOUNTS_DERIVE | ||
ABAP code using 7.40 inline data declarations to call FM FM_LG_ACCOUNTS_DERIVE
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 XFELD FROM FMDY INTO @DATA(ld_i_flag_account_derive_vt). | ||||
Search for further information about these or an SAP related objects