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

Function FAGL_GET_ARCH_FI_DOCUMENT 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_ARCH_FI_DOCUMENT'".
EXPORTING
I_BUKRS = "
I_BELNR = "
I_GJAHR = "
* I_RLDNR = "
IMPORTING
ES_HEADER_ADD = "
ET_LEDGER = "
TABLES
* T_BKPF = "
* T_GLU1 = "
* T_BSED = "
* T_BSEG = "
* T_BSEG_EXT = "
* T_BSEC = "
* T_BSEGC = "
* T_BSET = "
* T_BVOR = "
* T_CDHDR = "
* T_CDPOS = "
EXCEPTIONS
DOCUMENT_NOT_FOUND = 1 INTERNAL_ERROR = 2
IMPORTING Parameters details for FAGL_GET_ARCH_FI_DOCUMENT
I_BUKRS -
Data type: BUKRSOptional: No
Call by Reference: Yes
I_BELNR -
Data type: BELNR_DOptional: No
Call by Reference: Yes
I_GJAHR -
Data type: GJAHROptional: No
Call by Reference: Yes
I_RLDNR -
Data type: FAGL_RLDNROptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FAGL_GET_ARCH_FI_DOCUMENT
ES_HEADER_ADD -
Data type: FAGL_HEADER_ADDOptional: No
Call by Reference: Yes
ET_LEDGER -
Data type: FAGL_RLDNR_TABOptional: No
Call by Reference: Yes
TABLES Parameters details for FAGL_GET_ARCH_FI_DOCUMENT
T_BKPF -
Data type: BKPFOptional: Yes
Call by Reference: Yes
T_GLU1 -
Data type: GLU1Optional: Yes
Call by Reference: Yes
T_BSED -
Data type: BSEDOptional: Yes
Call by Reference: Yes
T_BSEG -
Data type: BSEGOptional: Yes
Call by Reference: Yes
T_BSEG_EXT -
Data type: FAGL_T_BSEG_EXTOptional: Yes
Call by Reference: Yes
T_BSEC -
Data type: BSECOptional: Yes
Call by Reference: Yes
T_BSEGC -
Data type: BSEGCOptional: Yes
Call by Reference: Yes
T_BSET -
Data type: BSETOptional: Yes
Call by Reference: Yes
T_BVOR -
Data type: BVOROptional: Yes
Call by Reference: Yes
T_CDHDR -
Data type: CDHDROptional: Yes
Call by Reference: Yes
T_CDPOS -
Data type: CDPOSOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
DOCUMENT_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FAGL_GET_ARCH_FI_DOCUMENT 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_bkpf | TYPE STANDARD TABLE OF BKPF, " | |||
| lv_i_bukrs | TYPE BUKRS, " | |||
| lv_es_header_add | TYPE FAGL_HEADER_ADD, " | |||
| lv_document_not_found | TYPE FAGL_HEADER_ADD, " | |||
| lt_t_glu1 | TYPE STANDARD TABLE OF GLU1, " | |||
| lt_t_bsed | TYPE STANDARD TABLE OF BSED, " | |||
| lt_t_bseg | TYPE STANDARD TABLE OF BSEG, " | |||
| lv_i_belnr | TYPE BELNR_D, " | |||
| lv_et_ledger | TYPE FAGL_RLDNR_TAB, " | |||
| lv_internal_error | TYPE FAGL_RLDNR_TAB, " | |||
| lv_i_gjahr | TYPE GJAHR, " | |||
| lt_t_bseg_ext | TYPE STANDARD TABLE OF FAGL_T_BSEG_EXT, " | |||
| lt_t_bsec | TYPE STANDARD TABLE OF BSEC, " | |||
| lv_i_rldnr | TYPE FAGL_RLDNR, " | |||
| lt_t_bsegc | TYPE STANDARD TABLE OF BSEGC, " | |||
| lt_t_bset | TYPE STANDARD TABLE OF BSET, " | |||
| lt_t_bvor | TYPE STANDARD TABLE OF BVOR, " | |||
| lt_t_cdhdr | TYPE STANDARD TABLE OF CDHDR, " | |||
| lt_t_cdpos | TYPE STANDARD TABLE OF CDPOS. " |
|   CALL FUNCTION 'FAGL_GET_ARCH_FI_DOCUMENT' " |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_BELNR | = lv_i_belnr | |
| I_GJAHR | = lv_i_gjahr | |
| I_RLDNR | = lv_i_rldnr | |
| IMPORTING | ||
| ES_HEADER_ADD | = lv_es_header_add | |
| ET_LEDGER | = lv_et_ledger | |
| TABLES | ||
| T_BKPF | = lt_t_bkpf | |
| T_GLU1 | = lt_t_glu1 | |
| T_BSED | = lt_t_bsed | |
| T_BSEG | = lt_t_bseg | |
| T_BSEG_EXT | = lt_t_bseg_ext | |
| T_BSEC | = lt_t_bsec | |
| T_BSEGC | = lt_t_bsegc | |
| T_BSET | = lt_t_bset | |
| T_BVOR | = lt_t_bvor | |
| T_CDHDR | = lt_t_cdhdr | |
| T_CDPOS | = lt_t_cdpos | |
| EXCEPTIONS | ||
| DOCUMENT_NOT_FOUND = 1 | ||
| INTERNAL_ERROR = 2 | ||
| . " FAGL_GET_ARCH_FI_DOCUMENT | ||
ABAP code using 7.40 inline data declarations to call FM FAGL_GET_ARCH_FI_DOCUMENT
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