SAP LTRM_ACTIVITY_SINGLE_GET Function Module for Returns a single activity from table LACTY
LTRM_ACTIVITY_SINGLE_GET is a standard ltrm activity single get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Returns a single activity from table LACTY 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 ltrm activity single get FM, simply by entering the name LTRM_ACTIVITY_SINGLE_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: LTRM
Program Name: SAPLLTRM
Main Program: SAPLLTRM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LTRM_ACTIVITY_SINGLE_GET 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 'LTRM_ACTIVITY_SINGLE_GET'"Returns a single activity from table LACTY.
EXPORTING
I_LOCAT = "Site
I_ACTVT = "Activity
IMPORTING
ES_LACTY = "Activity catalog
IMPORTING Parameters details for LTRM_ACTIVITY_SINGLE_GET
I_LOCAT - Site
Data type: LTRM_LOCATOptional: No
Call by Reference: No ( called with pass by value option)
I_ACTVT - Activity
Data type: LTRM_ACTVTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for LTRM_ACTIVITY_SINGLE_GET
ES_LACTY - Activity catalog
Data type: LACTYOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LTRM_ACTIVITY_SINGLE_GET 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_locat | TYPE LTRM_LOCAT, " | |||
| lv_es_lacty | TYPE LACTY, " | |||
| lv_i_actvt | TYPE LTRM_ACTVT. " |
|   CALL FUNCTION 'LTRM_ACTIVITY_SINGLE_GET' "Returns a single activity from table LACTY |
| EXPORTING | ||
| I_LOCAT | = lv_i_locat | |
| I_ACTVT | = lv_i_actvt | |
| IMPORTING | ||
| ES_LACTY | = lv_es_lacty | |
| . " LTRM_ACTIVITY_SINGLE_GET | ||
ABAP code using 7.40 inline data declarations to call FM LTRM_ACTIVITY_SINGLE_GET
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