SAP SEGMENT_CREATE Function Module for









SEGMENT_CREATE is a standard segment create 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 segment create FM, simply by entering the name SEGMENT_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function SEGMENT_CREATE 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 'SEGMENT_CREATE'"
EXPORTING
* WI_SET_GENFLAG = ' ' "
* SEGMENTEDITOR = ' ' "

IMPORTING
SEGMENTDEFINITION = "Segment definition
TASK = "Transport task

CHANGING
SEGMENTHEADER = "Segment header
* DEVCLASS = "Package
* ORDER = "Transport Request

TABLES
SEGMENTSTRUCTURE = "

EXCEPTIONS
LOCK_ERROR = 1 CREATION_FAILED = 2 NO_AUTHORITY = 3 TRANSPORT_ERROR = 4 NAMESPACE_VIOLATION = 5
.



IMPORTING Parameters details for SEGMENT_CREATE

WI_SET_GENFLAG -

Data type: TADIR-GENFLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SEGMENTEDITOR -

Data type: CHAR1
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SEGMENT_CREATE

SEGMENTDEFINITION - Segment definition

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

TASK - Transport task

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

CHANGING Parameters details for SEGMENT_CREATE

SEGMENTHEADER - Segment header

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

DEVCLASS - Package

Data type: TADIR-DEVCLASS
Optional: Yes
Call by Reference: No ( called with pass by value option)

ORDER - Transport Request

Data type: E070-TRKORR
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for SEGMENT_CREATE

SEGMENTSTRUCTURE -

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

EXCEPTIONS details

LOCK_ERROR - Lock Problem

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

CREATION_FAILED - Creation Failed

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

NO_AUTHORITY - No Authorization

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

TRANSPORT_ERROR - Transport Problem

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

NAMESPACE_VIOLATION -

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

Copy and paste ABAP code example for SEGMENT_CREATE 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_lock_error  TYPE STRING, "   
lv_segmentheader  TYPE EDISEGMHD, "   
lv_wi_set_genflag  TYPE TADIR-GENFLAG, "   SPACE
lt_segmentstructure  TYPE STANDARD TABLE OF EDISEGSTRU, "   
lv_segmentdefinition  TYPE EDISEGMDEF, "   
lv_task  TYPE E070-TRKORR, "   
lv_devclass  TYPE TADIR-DEVCLASS, "   
lv_segmenteditor  TYPE CHAR1, "   SPACE
lv_creation_failed  TYPE CHAR1, "   
lv_order  TYPE E070-TRKORR, "   
lv_no_authority  TYPE E070, "   
lv_transport_error  TYPE E070, "   
lv_namespace_violation  TYPE E070. "   

  CALL FUNCTION 'SEGMENT_CREATE'  "
    EXPORTING
         WI_SET_GENFLAG = lv_wi_set_genflag
         SEGMENTEDITOR = lv_segmenteditor
    IMPORTING
         SEGMENTDEFINITION = lv_segmentdefinition
         TASK = lv_task
    CHANGING
         SEGMENTHEADER = lv_segmentheader
         DEVCLASS = lv_devclass
         ORDER = lv_order
    TABLES
         SEGMENTSTRUCTURE = lt_segmentstructure
    EXCEPTIONS
        LOCK_ERROR = 1
        CREATION_FAILED = 2
        NO_AUTHORITY = 3
        TRANSPORT_ERROR = 4
        NAMESPACE_VIOLATION = 5
. " SEGMENT_CREATE




ABAP code using 7.40 inline data declarations to call FM SEGMENT_CREATE

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 GENFLAG FROM TADIR INTO @DATA(ld_wi_set_genflag).
DATA(ld_wi_set_genflag) = ' '.
 
 
 
"SELECT single TRKORR FROM E070 INTO @DATA(ld_task).
 
"SELECT single DEVCLASS FROM TADIR INTO @DATA(ld_devclass).
 
DATA(ld_segmenteditor) = ' '.
 
 
"SELECT single TRKORR FROM E070 INTO @DATA(ld_order).
 
 
 
 


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!