SAP TXS_SEGMENT_WRITE_INIT Function Module for Initialize Segment









TXS_SEGMENT_WRITE_INIT is a standard txs segment write init SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Initialize Segment 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 txs segment write init FM, simply by entering the name TXS_SEGMENT_WRITE_INIT into the relevant SAP transaction such as SE37 or SE38.

Function Group: TXILM_SRV
Program Name: SAPLTXILM_SRV
Main Program: SAPLTXILM_SRV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function TXS_SEGMENT_WRITE_INIT 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 'TXS_SEGMENT_WRITE_INIT'"Initialize Segment
EXPORTING
I_UID = "UUID in Character-Darstellung
I_SEGNAME = "Tabellenname

EXCEPTIONS
CREATE_DATA_FAILED = 1 OPEN_WRITE_FAILED = 2 CX_XADK_DAS_SERVER = 3 CX_XADK_SYSTEM = 4 CX_XADK_METHODS = 5 MULTIPLE_RUNNING = 6
.



IMPORTING Parameters details for TXS_SEGMENT_WRITE_INIT

I_UID - UUID in Character-Darstellung

Data type: SYSUUID_C
Optional: No
Call by Reference: Yes

I_SEGNAME - Tabellenname

Data type: TABNAME
Optional: No
Call by Reference: Yes

EXCEPTIONS details

CREATE_DATA_FAILED -

Data type:
Optional: No
Call by Reference: Yes

OPEN_WRITE_FAILED -

Data type:
Optional: No
Call by Reference: Yes

CX_XADK_DAS_SERVER -

Data type:
Optional: No
Call by Reference: Yes

CX_XADK_SYSTEM -

Data type:
Optional: No
Call by Reference: Yes

CX_XADK_METHODS -

Data type:
Optional: No
Call by Reference: Yes

MULTIPLE_RUNNING - multiple_running

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TXS_SEGMENT_WRITE_INIT 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_uid  TYPE SYSUUID_C, "   
lv_create_data_failed  TYPE SYSUUID_C, "   
lv_i_segname  TYPE TABNAME, "   
lv_open_write_failed  TYPE TABNAME, "   
lv_cx_xadk_das_server  TYPE TABNAME, "   
lv_cx_xadk_system  TYPE TABNAME, "   
lv_cx_xadk_methods  TYPE TABNAME, "   
lv_multiple_running  TYPE TABNAME. "   

  CALL FUNCTION 'TXS_SEGMENT_WRITE_INIT'  "Initialize Segment
    EXPORTING
         I_UID = lv_i_uid
         I_SEGNAME = lv_i_segname
    EXCEPTIONS
        CREATE_DATA_FAILED = 1
        OPEN_WRITE_FAILED = 2
        CX_XADK_DAS_SERVER = 3
        CX_XADK_SYSTEM = 4
        CX_XADK_METHODS = 5
        MULTIPLE_RUNNING = 6
. " TXS_SEGMENT_WRITE_INIT




ABAP code using 7.40 inline data declarations to call FM TXS_SEGMENT_WRITE_INIT

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!