SAP KL_EXT_WRITE_PROTOCOL_OUTGOING Function Module for write data of one RFC-call to SDC to DB
KL_EXT_WRITE_PROTOCOL_OUTGOING is a standard kl ext write protocol outgoing SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for write data of one RFC-call to SDC to DB 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 kl ext write protocol outgoing FM, simply by entering the name KL_EXT_WRITE_PROTOCOL_OUTGOING into the relevant SAP transaction such as SE37 or SE38.
Function Group: KLEXT
Program Name: SAPLKLEXT
Main Program: SAPLKLEXT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function KL_EXT_WRITE_PROTOCOL_OUTGOING 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 'KL_EXT_WRITE_PROTOCOL_OUTGOING'"write data of one RFC-call to SDC to DB.
EXPORTING
I_CALLIDX = "Run Number for Single Transaction Check Log
I_RESULT = "Individual, user-defined character
I_UPDATE = "Individual, user-defined character
TABLES
I_RESULT_DETAILS = "Basic Key Figures
ERROR_ITAB = "OR: Structure of Error Handling
EXCEPTIONS
NO_DB_INSERT = 1 NO_COMMIT = 2
IMPORTING Parameters details for KL_EXT_WRITE_PROTOCOL_OUTGOING
I_CALLIDX - Run Number for Single Transaction Check Log
Data type: KL_CALLIDXOptional: No
Call by Reference: Yes
I_RESULT - Individual, user-defined character
Data type: DATATYPE-CHAR0001Optional: No
Call by Reference: No ( called with pass by value option)
I_UPDATE - Individual, user-defined character
Data type: DATATYPE-CHAR0001Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for KL_EXT_WRITE_PROTOCOL_OUTGOING
I_RESULT_DETAILS - Basic Key Figures
Data type: VTSL_TACOMP_ALVOptional: No
Call by Reference: Yes
ERROR_ITAB - OR: Structure of Error Handling
Data type: BAPIERROptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_DB_INSERT - Error when adding data record
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_COMMIT - Error during database commit
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for KL_EXT_WRITE_PROTOCOL_OUTGOING 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_callidx | TYPE KL_CALLIDX, " | |||
| lv_no_db_insert | TYPE KL_CALLIDX, " | |||
| lt_i_result_details | TYPE STANDARD TABLE OF VTSL_TACOMP_ALV, " | |||
| lv_i_result | TYPE DATATYPE-CHAR0001, " | |||
| lv_no_commit | TYPE DATATYPE, " | |||
| lt_error_itab | TYPE STANDARD TABLE OF BAPIERR, " | |||
| lv_i_update | TYPE DATATYPE-CHAR0001. " |
|   CALL FUNCTION 'KL_EXT_WRITE_PROTOCOL_OUTGOING' "write data of one RFC-call to SDC to DB |
| EXPORTING | ||
| I_CALLIDX | = lv_i_callidx | |
| I_RESULT | = lv_i_result | |
| I_UPDATE | = lv_i_update | |
| TABLES | ||
| I_RESULT_DETAILS | = lt_i_result_details | |
| ERROR_ITAB | = lt_error_itab | |
| EXCEPTIONS | ||
| NO_DB_INSERT = 1 | ||
| NO_COMMIT = 2 | ||
| . " KL_EXT_WRITE_PROTOCOL_OUTGOING | ||
ABAP code using 7.40 inline data declarations to call FM KL_EXT_WRITE_PROTOCOL_OUTGOING
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 CHAR0001 FROM DATATYPE INTO @DATA(ld_i_result). | ||||
| "SELECT single CHAR0001 FROM DATATYPE INTO @DATA(ld_i_update). | ||||
Search for further information about these or an SAP related objects