SAP LTR2_KB_API_UI_SYS_ANALYSIS Function Module for UI API for Conversion Rule Assignment
LTR2_KB_API_UI_SYS_ANALYSIS is a standard ltr2 kb api ui sys 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 UI API for Conversion Rule Assignment 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 ltr2 kb api ui sys analysis FM, simply by entering the name LTR2_KB_API_UI_SYS_ANALYSIS into the relevant SAP transaction such as SE37 or SE38.
Function Group: LTR2_KB_INTERFACE_RFC
Program Name: SAPLLTR2_KB_INTERFACE_RFC
Main Program: SAPLLTR2_KB_INTERFACE_RFC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function LTR2_KB_API_UI_SYS_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 'LTR2_KB_API_UI_SYS_ANALYSIS'"UI API for Conversion Rule Assignment.
EXPORTING
IV_PROJ_GUID = "Name of Object in LTR2 KB
* IV_RUNID = "LTR2 KB: Process Control - Run ID
EXCEPTIONS
INVALID_PROJ_GUID = 1 NO_AUTHORIZATION_FOR_ACTION = 2 UNEXPECTED_ERROR = 3 GUI_ACCESS_REQ = 4
IMPORTING Parameters details for LTR2_KB_API_UI_SYS_ANALYSIS
IV_PROJ_GUID - Name of Object in LTR2 KB
Data type: LTR2_KB_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
IV_RUNID - LTR2 KB: Process Control - Run ID
Data type: LTR2_KB_PC_RUNIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_PROJ_GUID - Invalid LTR2_KB project GUID
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_AUTHORIZATION_FOR_ACTION - No authorization for requested action
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNEXPECTED_ERROR - An unexpected error occured
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
GUI_ACCESS_REQ - GUI access required
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LTR2_KB_API_UI_SYS_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_iv_proj_guid | TYPE LTR2_KB_GUID, " | |||
| lv_invalid_proj_guid | TYPE LTR2_KB_GUID, " | |||
| lv_iv_runid | TYPE LTR2_KB_PC_RUNID, " | |||
| lv_no_authorization_for_action | TYPE LTR2_KB_PC_RUNID, " | |||
| lv_unexpected_error | TYPE LTR2_KB_PC_RUNID, " | |||
| lv_gui_access_req | TYPE LTR2_KB_PC_RUNID. " |
|   CALL FUNCTION 'LTR2_KB_API_UI_SYS_ANALYSIS' "UI API for Conversion Rule Assignment |
| EXPORTING | ||
| IV_PROJ_GUID | = lv_iv_proj_guid | |
| IV_RUNID | = lv_iv_runid | |
| EXCEPTIONS | ||
| INVALID_PROJ_GUID = 1 | ||
| NO_AUTHORIZATION_FOR_ACTION = 2 | ||
| UNEXPECTED_ERROR = 3 | ||
| GUI_ACCESS_REQ = 4 | ||
| . " LTR2_KB_API_UI_SYS_ANALYSIS | ||
ABAP code using 7.40 inline data declarations to call FM LTR2_KB_API_UI_SYS_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.Search for further information about these or an SAP related objects