SAP LTRM_REASONS_GET Function Module for Get reason
LTRM_REASONS_GET is a standard ltrm reasons 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 Get reason 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 reasons get FM, simply by entering the name LTRM_REASONS_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_REASONS_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_REASONS_GET'"Get reason.
EXPORTING
I_LOCAT = "Site
I_LANGU = "Language
I_OBJECT = "Application objects,supported by ext./int. status conversion
TABLES
T_REASONS = "
IMPORTING Parameters details for LTRM_REASONS_GET
I_LOCAT - Site
Data type: LTRM_LOCATOptional: No
Call by Reference: Yes
I_LANGU - Language
Data type: SYLANGUOptional: No
Call by Reference: Yes
I_OBJECT - Application objects,supported by ext./int. status conversion
Data type: LTRM_OBJCTOptional: No
Call by Reference: Yes
TABLES Parameters details for LTRM_REASONS_GET
T_REASONS -
Data type: LTRM_IT_REASONOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for LTRM_REASONS_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, " | |||
| lt_t_reasons | TYPE STANDARD TABLE OF LTRM_IT_REASON, " | |||
| lv_i_langu | TYPE SYLANGU, " | |||
| lv_i_object | TYPE LTRM_OBJCT. " |
|   CALL FUNCTION 'LTRM_REASONS_GET' "Get reason |
| EXPORTING | ||
| I_LOCAT | = lv_i_locat | |
| I_LANGU | = lv_i_langu | |
| I_OBJECT | = lv_i_object | |
| TABLES | ||
| T_REASONS | = lt_t_reasons | |
| . " LTRM_REASONS_GET | ||
ABAP code using 7.40 inline data declarations to call FM LTRM_REASONS_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