SAP GLO_FAA_TD_READ_MULTIPLE Function Module for
GLO_FAA_TD_READ_MULTIPLE is a standard glo faa td read multiple 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 glo faa td read multiple FM, simply by entering the name GLO_FAA_TD_READ_MULTIPLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: GLO_FAA_READ_ASSETDATA
Program Name: SAPLGLO_FAA_READ_ASSETDATA
Main Program: SAPLGLO_FAA_READ_ASSETDATA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GLO_FAA_TD_READ_MULTIPLE 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 'GLO_FAA_TD_READ_MULTIPLE'".
EXPORTING
ID_ORGUNIT = "
ID_ASSET = "
ID_SUBNUMBER = "
* ID_FROM_DATE = '19000101' "
* ID_TO_DATE = '99991231' "
* IB_SORT_DESCENDING = ' ' "
* IB_BYPASSING_MEMORY = ' ' "
* IB_RESET_BUFFER = ' ' "
TABLES
ET_GLOFAATMDPNDNT = "
EXCEPTIONS
NOT_FOUND = 1 NOT_ACTIVATED = 2
IMPORTING Parameters details for GLO_FAA_TD_READ_MULTIPLE
ID_ORGUNIT -
Data type: BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
ID_ASSET -
Data type: ANLN1Optional: No
Call by Reference: No ( called with pass by value option)
ID_SUBNUMBER -
Data type: ANLN2Optional: No
Call by Reference: No ( called with pass by value option)
ID_FROM_DATE -
Data type: ADATUDefault: '19000101'
Optional: Yes
Call by Reference: No ( called with pass by value option)
ID_TO_DATE -
Data type: BDATUDefault: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IB_SORT_DESCENDING -
Data type: XFELDDefault: ' '
Optional: Yes
Call by Reference: Yes
IB_BYPASSING_MEMORY -
Data type: XFELDDefault: ' '
Optional: Yes
Call by Reference: Yes
IB_RESET_BUFFER -
Data type: XFELDDefault: ' '
Optional: Yes
Call by Reference: Yes
TABLES Parameters details for GLO_FAA_TD_READ_MULTIPLE
ET_GLOFAATMDPNDNT -
Data type: GLOFAATMDPNDNTOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
NOT_ACTIVATED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for GLO_FAA_TD_READ_MULTIPLE 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_not_found | TYPE STRING, " | |||
| lv_id_orgunit | TYPE BUKRS, " | |||
| lt_et_glofaatmdpndnt | TYPE STANDARD TABLE OF GLOFAATMDPNDNT, " | |||
| lv_id_asset | TYPE ANLN1, " | |||
| lv_not_activated | TYPE ANLN1, " | |||
| lv_id_subnumber | TYPE ANLN2, " | |||
| lv_id_from_date | TYPE ADATU, " '19000101' | |||
| lv_id_to_date | TYPE BDATU, " '99991231' | |||
| lv_ib_sort_descending | TYPE XFELD, " ' ' | |||
| lv_ib_bypassing_memory | TYPE XFELD, " ' ' | |||
| lv_ib_reset_buffer | TYPE XFELD. " ' ' |
|   CALL FUNCTION 'GLO_FAA_TD_READ_MULTIPLE' " |
| EXPORTING | ||
| ID_ORGUNIT | = lv_id_orgunit | |
| ID_ASSET | = lv_id_asset | |
| ID_SUBNUMBER | = lv_id_subnumber | |
| ID_FROM_DATE | = lv_id_from_date | |
| ID_TO_DATE | = lv_id_to_date | |
| IB_SORT_DESCENDING | = lv_ib_sort_descending | |
| IB_BYPASSING_MEMORY | = lv_ib_bypassing_memory | |
| IB_RESET_BUFFER | = lv_ib_reset_buffer | |
| TABLES | ||
| ET_GLOFAATMDPNDNT | = lt_et_glofaatmdpndnt | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| NOT_ACTIVATED = 2 | ||
| . " GLO_FAA_TD_READ_MULTIPLE | ||
ABAP code using 7.40 inline data declarations to call FM GLO_FAA_TD_READ_MULTIPLE
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.| DATA(ld_id_from_date) | = '19000101'. | |||
| DATA(ld_id_to_date) | = '99991231'. | |||
| DATA(ld_ib_sort_descending) | = ' '. | |||
| DATA(ld_ib_bypassing_memory) | = ' '. | |||
| DATA(ld_ib_reset_buffer) | = ' '. | |||
Search for further information about these or an SAP related objects