SAP FAGL_GET_MISSING_INFO Function Module for
FAGL_GET_MISSING_INFO is a standard fagl get missing info 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 fagl get missing info FM, simply by entering the name FAGL_GET_MISSING_INFO into the relevant SAP transaction such as SE37 or SE38.
Function Group: FAGL_MIGRATION
Program Name: SAPLFAGL_MIGRATION
Main Program: SAPLFAGL_MIGRATION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FAGL_GET_MISSING_INFO 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 'FAGL_GET_MISSING_INFO'".
EXPORTING
I_MGPLN = "Migration Plan
* I_RLDNR = "
* I_BUKRS = "Company Code
IMPORTING
ET_FAGL_MIG_002 = "Table Type for FAGL_MIG_002
ET_BUKRS = "Table of Company Codes
ET_LEDGER = "Table of Ledgers
EXCEPTIONS
INVALID_INPUT = 1 NO_BUKRS = 2 NO_LEDGER = 3
IMPORTING Parameters details for FAGL_GET_MISSING_INFO
I_MGPLN - Migration Plan
Data type: FAGL_MGPLNOptional: No
Call by Reference: Yes
I_RLDNR -
Data type: RLDNROptional: Yes
Call by Reference: Yes
I_BUKRS - Company Code
Data type: BUKRSOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FAGL_GET_MISSING_INFO
ET_FAGL_MIG_002 - Table Type for FAGL_MIG_002
Data type: FAGL_T_MIG_002Optional: No
Call by Reference: Yes
ET_BUKRS - Table of Company Codes
Data type: FAGL_T_BUKRSOptional: No
Call by Reference: Yes
ET_LEDGER - Table of Ledgers
Data type: FAGL_T_RLDNROptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_INPUT - Import Parameters Incorrect
Data type:Optional: No
Call by Reference: Yes
NO_BUKRS -
Data type:Optional: No
Call by Reference: Yes
NO_LEDGER -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FAGL_GET_MISSING_INFO 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_mgpln | TYPE FAGL_MGPLN, " | |||
| lv_invalid_input | TYPE FAGL_MGPLN, " | |||
| lv_et_fagl_mig_002 | TYPE FAGL_T_MIG_002, " | |||
| lv_i_rldnr | TYPE RLDNR, " | |||
| lv_et_bukrs | TYPE FAGL_T_BUKRS, " | |||
| lv_no_bukrs | TYPE FAGL_T_BUKRS, " | |||
| lv_i_bukrs | TYPE BUKRS, " | |||
| lv_et_ledger | TYPE FAGL_T_RLDNR, " | |||
| lv_no_ledger | TYPE FAGL_T_RLDNR. " |
|   CALL FUNCTION 'FAGL_GET_MISSING_INFO' " |
| EXPORTING | ||
| I_MGPLN | = lv_i_mgpln | |
| I_RLDNR | = lv_i_rldnr | |
| I_BUKRS | = lv_i_bukrs | |
| IMPORTING | ||
| ET_FAGL_MIG_002 | = lv_et_fagl_mig_002 | |
| ET_BUKRS | = lv_et_bukrs | |
| ET_LEDGER | = lv_et_ledger | |
| EXCEPTIONS | ||
| INVALID_INPUT = 1 | ||
| NO_BUKRS = 2 | ||
| NO_LEDGER = 3 | ||
| . " FAGL_GET_MISSING_INFO | ||
ABAP code using 7.40 inline data declarations to call FM FAGL_GET_MISSING_INFO
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