SEGMENTDEFINITION_CLOSE SAP Function module

SEGMENTDEFINITION_CLOSE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name SEGMENTDEFINITION_CLOSE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: EDIJ
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM SEGMENTDEFINITION_CLOSE - SEGMENTDEFINITION CLOSE

CALL FUNCTION 'SEGMENTDEFINITION_CLOSE' "
  EXPORTING
    segmenttyp =                " edisegmhd-segtyp  Segment Type
  IMPORTING
    segmentdefinition =         " edisegmdef    Segment definition
    task =                      " e070-trkorr   Transport task
* CHANGING
*   order =                     " e070-trkorr   Transport Request
  EXCEPTIONS
    SEGMENT_NOT_EXISTING = 1    "               Segment Does Not Exist
    LOCK_ERROR = 2              "               Lock Problem
    CHANGE_FAILED = 3           "
    NO_AUTHORITY = 4            "               No Authorization
    TRANSPORT_ERROR = 5         "               Transport Problem
    .  "  SEGMENTDEFINITION_CLOSE

ABAP code example for Function Module SEGMENTDEFINITION_CLOSE

The ABAP code below is a full code listing to execute function module SEGMENTDEFINITION_CLOSE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_segmentdefinition  
 
 TYPE EDISEGMDEF
,
ld_task  
 
 TYPE E070-TRKORR
.

 

SELECT single TRKORR 
  FROM E070 
  INTO @DATA(ld_order).



DATA(ld_segmenttyp) = some text here
.

CALL FUNCTION 'SEGMENTDEFINITION_CLOSE'
  EXPORTING
    segmenttyp =                 ld_segmenttyp
  IMPORTING
    segmentdefinition =          ld_segmentdefinition
    task =                       ld_task
* CHANGING
*   order =                      ld_order
  EXCEPTIONS
    SEGMENT_NOT_EXISTING =       1
    LOCK_ERROR =                 2
    CHANGE_FAILED =              3
    NO_AUTHORITY =               4
    TRANSPORT_ERROR =            5
    .  "  SEGMENTDEFINITION_CLOSE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_order
 
 TYPE E070-TRKORR ,
ld_segmentdefinition
 
 TYPE EDISEGMDEF ,
ld_segmenttyp
 
 TYPE EDISEGMHD-SEGTYP ,
ld_task
 
 TYPE E070-TRKORR .



SELECT single TRKORR 
  FROM E070 
  INTO ld_order.


ld_segmenttyp = some text here