SAP LTIF_RESOURCE_VALIDATE Function Module for Check Logon Data
LTIF_RESOURCE_VALIDATE is a standard ltif resource validate SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Logon Data 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 ltif resource validate FM, simply by entering the name LTIF_RESOURCE_VALIDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: LTIF_SERVICES_PRSNT
Program Name: SAPLLTIF_SERVICES_PRSNT
Main Program: SAPLLTIF_SERVICES_PRSNT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LTIF_RESOURCE_VALIDATE 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 'LTIF_RESOURCE_VALIDATE'"Check Logon Data.
EXPORTING
I_LOCAT = "Site
I_DEVICE = "Device
I_RSTYP = "Resource type
I_WORKER = "R/3 System, user logon name
I_WROLE = "Working role
IMPORTING
O_RSTYP = "Resource type
O_WROLE = "Working role
O_DEVICE = "Device
O_RSLOC = "Resource's location
IMPORTING Parameters details for LTIF_RESOURCE_VALIDATE
I_LOCAT - Site
Data type: LMBI_LOCATOptional: No
Call by Reference: Yes
I_DEVICE - Device
Data type: LMBI_DEVICEOptional: No
Call by Reference: Yes
I_RSTYP - Resource type
Data type: LMBI_RSTYPOptional: No
Call by Reference: Yes
I_WORKER - R/3 System, user logon name
Data type: SYUNAMEOptional: No
Call by Reference: Yes
I_WROLE - Working role
Data type: LMBI_WROLEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for LTIF_RESOURCE_VALIDATE
O_RSTYP - Resource type
Data type: LMBI_RSTYPOptional: No
Call by Reference: Yes
O_WROLE - Working role
Data type: LMBI_WROLEOptional: No
Call by Reference: Yes
O_DEVICE - Device
Data type: LMBI_DEVICEOptional: No
Call by Reference: Yes
O_RSLOC - Resource's location
Data type: LMBI_RESOURCE_LOCATIONOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for LTIF_RESOURCE_VALIDATE 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 LMBI_LOCAT, " | |||
| lv_o_rstyp | TYPE LMBI_RSTYP, " | |||
| lv_o_wrole | TYPE LMBI_WROLE, " | |||
| lv_i_device | TYPE LMBI_DEVICE, " | |||
| lv_i_rstyp | TYPE LMBI_RSTYP, " | |||
| lv_o_device | TYPE LMBI_DEVICE, " | |||
| lv_o_rsloc | TYPE LMBI_RESOURCE_LOCATION, " | |||
| lv_i_worker | TYPE SYUNAME, " | |||
| lv_i_wrole | TYPE LMBI_WROLE. " |
|   CALL FUNCTION 'LTIF_RESOURCE_VALIDATE' "Check Logon Data |
| EXPORTING | ||
| I_LOCAT | = lv_i_locat | |
| I_DEVICE | = lv_i_device | |
| I_RSTYP | = lv_i_rstyp | |
| I_WORKER | = lv_i_worker | |
| I_WROLE | = lv_i_wrole | |
| IMPORTING | ||
| O_RSTYP | = lv_o_rstyp | |
| O_WROLE | = lv_o_wrole | |
| O_DEVICE | = lv_o_device | |
| O_RSLOC | = lv_o_rsloc | |
| . " LTIF_RESOURCE_VALIDATE | ||
ABAP code using 7.40 inline data declarations to call FM LTIF_RESOURCE_VALIDATE
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