SAP SEGMENT_EXTERNAL_NAME_GET Function Module for









SEGMENT_EXTERNAL_NAME_GET is a standard segment external name get 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 external name get FM, simply by entering the name SEGMENT_EXTERNAL_NAME_GET 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_EXTERNAL_NAME_GET 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_EXTERNAL_NAME_GET'"
EXPORTING
SEGMENTTYP = "
* RELEASED = ' ' "Released in
* APPLREL = ' ' "IDoc Development: Application Release of Segment Definition

IMPORTING
EXPORTLENGTH = "
SEGNAM30 = "
SEGNAM40 = "
VERSION = "Segment version

EXCEPTIONS
SEGMENT_NOT_EXISTING = 1 VERSION_NOT_EXISTING = 2 CONVERSION_NOT_AVAILABLE = 3
.



IMPORTING Parameters details for SEGMENT_EXTERNAL_NAME_GET

SEGMENTTYP -

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

RELEASED - Released in

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

APPLREL - IDoc Development: Application Release of Segment Definition

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

EXPORTING Parameters details for SEGMENT_EXTERNAL_NAME_GET

EXPORTLENGTH -

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

SEGNAM30 -

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

SEGNAM40 -

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

VERSION - Segment version

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

EXCEPTIONS details

SEGMENT_NOT_EXISTING - Segment Does Not Exist

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

VERSION_NOT_EXISTING -

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

CONVERSION_NOT_AVAILABLE -

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

Copy and paste ABAP code example for SEGMENT_EXTERNAL_NAME_GET 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_segmenttyp  TYPE STRING, "   
lv_exportlength  TYPE EDISEGMDEF-EXPLENG, "   
lv_segment_not_existing  TYPE EDISEGMDEF, "   
lv_released  TYPE EDISEGMDEF-RELEASED, "   SPACE
lv_segnam30  TYPE EDI_DD-SEGNAM, "   
lv_version_not_existing  TYPE EDI_DD, "   
lv_applrel  TYPE SEGDEFARL, "   SPACE
lv_segnam40  TYPE EDI_DD40-SEGNAM, "   
lv_conversion_not_available  TYPE EDI_DD40, "   
lv_version  TYPE EDISEGMDEF-VERSION. "   

  CALL FUNCTION 'SEGMENT_EXTERNAL_NAME_GET'  "
    EXPORTING
         SEGMENTTYP = lv_segmenttyp
         RELEASED = lv_released
         APPLREL = lv_applrel
    IMPORTING
         EXPORTLENGTH = lv_exportlength
         SEGNAM30 = lv_segnam30
         SEGNAM40 = lv_segnam40
         VERSION = lv_version
    EXCEPTIONS
        SEGMENT_NOT_EXISTING = 1
        VERSION_NOT_EXISTING = 2
        CONVERSION_NOT_AVAILABLE = 3
. " SEGMENT_EXTERNAL_NAME_GET




ABAP code using 7.40 inline data declarations to call FM SEGMENT_EXTERNAL_NAME_GET

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 EXPLENG FROM EDISEGMDEF INTO @DATA(ld_exportlength).
 
 
"SELECT single RELEASED FROM EDISEGMDEF INTO @DATA(ld_released).
DATA(ld_released) = ' '.
 
"SELECT single SEGNAM FROM EDI_DD INTO @DATA(ld_segnam30).
 
 
DATA(ld_applrel) = ' '.
 
"SELECT single SEGNAM FROM EDI_DD40 INTO @DATA(ld_segnam40).
 
 
"SELECT single VERSION FROM EDISEGMDEF INTO @DATA(ld_version).
 


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!