SAP ALM_TRANSACTION_ANALYSIS Function Module for ALM: Detail View of Relevant Transactions in Gap Analysis Result
ALM_TRANSACTION_ANALYSIS is a standard alm transaction analysis SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for ALM: Detail View of Relevant Transactions in Gap Analysis Result 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 alm transaction analysis FM, simply by entering the name ALM_TRANSACTION_ANALYSIS into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMG3_D
Program Name: SAPLRMG3_D
Main Program: SAPLRMG3_D
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ALM_TRANSACTION_ANALYSIS 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 'ALM_TRANSACTION_ANALYSIS'"ALM: Detail View of Relevant Transactions in Gap Analysis Result.
EXPORTING
I_DATE = "
TABLES
IT_FIELDS = "
IMPORTING Parameters details for ALM_TRANSACTION_ANALYSIS
I_DATE -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ALM_TRANSACTION_ANALYSIS
IT_FIELDS -
Data type: ALM99_FIELD_TABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ALM_TRANSACTION_ANALYSIS 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_date | TYPE SY-DATUM, " | |||
| lt_it_fields | TYPE STANDARD TABLE OF ALM99_FIELD_TAB. " |
|   CALL FUNCTION 'ALM_TRANSACTION_ANALYSIS' "ALM: Detail View of Relevant Transactions in Gap Analysis Result |
| EXPORTING | ||
| I_DATE | = lv_i_date | |
| TABLES | ||
| IT_FIELDS | = lt_it_fields | |
| . " ALM_TRANSACTION_ANALYSIS | ||
ABAP code using 7.40 inline data declarations to call FM ALM_TRANSACTION_ANALYSIS
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 DATUM FROM SY INTO @DATA(ld_i_date). | ||||
Search for further information about these or an SAP related objects