SAP /ASU/GET_VERSION_HEADERS Function Module for Fetch all the ASU Version Headers in a given language
/ASU/GET_VERSION_HEADERS is a standard /asu/get version headers SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Fetch all the ASU Version Headers in a given language 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 /asu/get version headers FM, simply by entering the name /ASU/GET_VERSION_HEADERS into the relevant SAP transaction such as SE37 or SE38.
Function Group: /ASU/TOOLS_DB_ACCESS
Program Name: /ASU/SAPLTOOLS_DB_ACCESS
Main Program: /ASU/SAPLTOOLS_DB_ACCESS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function /ASU/GET_VERSION_HEADERS 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 '/ASU/GET_VERSION_HEADERS'"Fetch all the ASU Version Headers in a given language.
EXPORTING
LANGU = "R/3 System, current language
USER = "R/3 System, user logon name
TABLES
ASU_HEADERS = "Text table for ASU Version Header
IMPORTING Parameters details for /ASU/GET_VERSION_HEADERS
LANGU - R/3 System, current language
Data type: SY-LANGUOptional: No
Call by Reference: No ( called with pass by value option)
USER - R/3 System, user logon name
Data type: SYUNAMEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for /ASU/GET_VERSION_HEADERS
ASU_HEADERS - Text table for ASU Version Header
Data type: /ASU/HEADER_SCROptional: No
Call by Reference: Yes
Copy and paste ABAP code example for /ASU/GET_VERSION_HEADERS 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_langu | TYPE SY-LANGU, " | |||
| lt_asu_headers | TYPE STANDARD TABLE OF /ASU/HEADER_SCR, " | |||
| lv_user | TYPE SYUNAME. " |
|   CALL FUNCTION '/ASU/GET_VERSION_HEADERS' "Fetch all the ASU Version Headers in a given language |
| EXPORTING | ||
| LANGU | = lv_langu | |
| USER | = lv_user | |
| TABLES | ||
| ASU_HEADERS | = lt_asu_headers | |
| . " /ASU/GET_VERSION_HEADERS | ||
ABAP code using 7.40 inline data declarations to call FM /ASU/GET_VERSION_HEADERS
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 LANGU FROM SY INTO @DATA(ld_langu). | ||||
Search for further information about these or an SAP related objects