SAP LNGT_SE63_REQUEST_WRITE Function Module for
LNGT_SE63_REQUEST_WRITE is a standard lngt se63 request write SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 lngt se63 request write FM, simply by entering the name LNGT_SE63_REQUEST_WRITE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SKTO
Program Name: SAPLSKTO
Main Program: SAPLSKTO
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function LNGT_SE63_REQUEST_WRITE 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 'LNGT_SE63_REQUEST_WRITE'".
EXPORTING
TARGETLANG = "Target Language
UNAME = "SAP System, User Logon Name
TRKORR = "
IMPORTING
USED_REQUEST_HEADER = "
TABLES
OBJECTS = "Object lists for worklists
TLIST = "Tables with attributes
LINES = "
* FAULTY_OBJECTS = "Object lists for worklists
* OBJLIST = "Objects
* KEYLIST = "Table Keys
EXCEPTIONS
ILLEGAL_LANGUAGE = 1 RECORDING_FAILED = 2
IMPORTING Parameters details for LNGT_SE63_REQUEST_WRITE
TARGETLANG - Target Language
Data type: SY-LANGUOptional: No
Call by Reference: No ( called with pass by value option)
UNAME - SAP System, User Logon Name
Data type: SY-UNAMEOptional: No
Call by Reference: No ( called with pass by value option)
TRKORR -
Data type: TRWBO_REQUEST_HEADER-TRKORROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for LNGT_SE63_REQUEST_WRITE
USED_REQUEST_HEADER -
Data type: TRWBO_REQUEST_HEADEROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for LNGT_SE63_REQUEST_WRITE
OBJECTS - Object lists for worklists
Data type: LWRKOBJOptional: No
Call by Reference: No ( called with pass by value option)
TLIST - Tables with attributes
Data type: TABLISTOptional: No
Call by Reference: No ( called with pass by value option)
LINES -
Data type: TABLINOptional: No
Call by Reference: No ( called with pass by value option)
FAULTY_OBJECTS - Object lists for worklists
Data type: LWRKOBJOptional: Yes
Call by Reference: No ( called with pass by value option)
OBJLIST - Objects
Data type: TR_OBJECTSOptional: Yes
Call by Reference: No ( called with pass by value option)
KEYLIST - Table Keys
Data type: TR_KEYSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ILLEGAL_LANGUAGE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
RECORDING_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LNGT_SE63_REQUEST_WRITE 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: | ||||
lt_objects | TYPE STANDARD TABLE OF LWRKOBJ, " | |||
lv_targetlang | TYPE SY-LANGU, " | |||
lv_illegal_language | TYPE SY, " | |||
lv_used_request_header | TYPE TRWBO_REQUEST_HEADER, " | |||
lt_tlist | TYPE STANDARD TABLE OF TABLIST, " | |||
lv_uname | TYPE SY-UNAME, " | |||
lv_recording_failed | TYPE SY, " | |||
lt_lines | TYPE STANDARD TABLE OF TABLIN, " | |||
lv_trkorr | TYPE TRWBO_REQUEST_HEADER-TRKORR, " | |||
lt_faulty_objects | TYPE STANDARD TABLE OF LWRKOBJ, " | |||
lt_objlist | TYPE STANDARD TABLE OF TR_OBJECTS, " | |||
lt_keylist | TYPE STANDARD TABLE OF TR_KEYS. " |
  CALL FUNCTION 'LNGT_SE63_REQUEST_WRITE' " |
EXPORTING | ||
TARGETLANG | = lv_targetlang | |
UNAME | = lv_uname | |
TRKORR | = lv_trkorr | |
IMPORTING | ||
USED_REQUEST_HEADER | = lv_used_request_header | |
TABLES | ||
OBJECTS | = lt_objects | |
TLIST | = lt_tlist | |
LINES | = lt_lines | |
FAULTY_OBJECTS | = lt_faulty_objects | |
OBJLIST | = lt_objlist | |
KEYLIST | = lt_keylist | |
EXCEPTIONS | ||
ILLEGAL_LANGUAGE = 1 | ||
RECORDING_FAILED = 2 | ||
. " LNGT_SE63_REQUEST_WRITE |
ABAP code using 7.40 inline data declarations to call FM LNGT_SE63_REQUEST_WRITE
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."SELECT single LANGU FROM SY INTO @DATA(ld_targetlang). | ||||
"SELECT single UNAME FROM SY INTO @DATA(ld_uname). | ||||
"SELECT single TRKORR FROM TRWBO_REQUEST_HEADER INTO @DATA(ld_trkorr). | ||||
Search for further information about these or an SAP related objects