SAP LTR2_KB_API_SET_PROJECT_TYPE Function Module for Set field MT_INT_LAYER for project

Search SAP Function Modules

LTR2_KB_API_SET_PROJECT_TYPE is a standard ltr2 kb api set project type SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set field MT_INT_LAYER for project 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 set project type FM, simply by entering the name LTR2_KB_API_SET_PROJECT_TYPE 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_SET_PROJECT_TYPE 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_SET_PROJECT_TYPE'"Set field MT_INT_LAYER for project
  EXPORTING
   IV_PROJ_NAME =  "GUID
   IV_VALUE =  "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

EXCEPTIONS
   INVALID_PROJECT = 1    UNEXPECTED_ERROR = 2    NO_AUTHORIZATION_FOR_ACTION = 3    PROJECT_SAVING_FAILED = 4    NO_UPDATE_REQUIRED = 5 

.

IMPORTING Parameters details for LTR2_KB_API_SET_PROJECT_TYPE

IV_PROJ_NAME - GUID

Data type: LTR2_KB_NAME
Optional: No
Call by Reference: No ( called with pass by value option)

IV_VALUE - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

Data type: LTR2_KB_PROJECT_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

INVALID_PROJECT - project name is invalid

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

UNEXPECTED_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_AUTHORIZATION_FOR_ACTION - No authorization for this action

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PROJECT_SAVING_FAILED - Saving the LTR2_KB project failed

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_UPDATE_REQUIRED - No update of settings 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_SET_PROJECT_TYPE 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.

ABAP code using 7.40 inline data declarations to call FM LTR2_KB_API_SET_PROJECT_TYPE

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