SAP SGT_VALIDATE_SEGMENT Function Module for Event: Pflege Konditionen: Feldprüfung









SGT_VALIDATE_SEGMENT is a standard sgt validate segment SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Event: Pflege Konditionen: Feldprüfung 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 sgt validate segment FM, simply by entering the name SGT_VALIDATE_SEGMENT into the relevant SAP transaction such as SE37 or SE38.

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



Function SGT_VALIDATE_SEGMENT 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 'SGT_VALIDATE_SEGMENT'"Event: Pflege Konditionen: Feldprüfung
EXPORTING
FIELDNAME = "Allowed Fields for Condition Structures
VALUE = "
KOMG_I = "Sample Structure for the Variable Key
KONP_I = "
T681E_I = "

CHANGING
CHECK_FIELD = "
RETURNCODE = "
.



IMPORTING Parameters details for SGT_VALIDATE_SEGMENT

FIELDNAME - Allowed Fields for Condition Structures

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

VALUE -

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

KOMG_I - Sample Structure for the Variable Key

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

KONP_I -

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

T681E_I -

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

CHANGING Parameters details for SGT_VALIDATE_SEGMENT

CHECK_FIELD -

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

RETURNCODE -

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

Copy and paste ABAP code example for SGT_VALIDATE_SEGMENT 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_fieldname  TYPE SEFELD, "   
lv_check_field  TYPE CHAR1, "   
lv_value  TYPE CHAR1, "   
lv_returncode  TYPE SUBRC, "   
lv_komg_i  TYPE KOMG, "   
lv_konp_i  TYPE KONP, "   
lv_t681e_i  TYPE T681E. "   

  CALL FUNCTION 'SGT_VALIDATE_SEGMENT'  "Event: Pflege Konditionen: Feldprüfung
    EXPORTING
         FIELDNAME = lv_fieldname
         VALUE = lv_value
         KOMG_I = lv_komg_i
         KONP_I = lv_konp_i
         T681E_I = lv_t681e_i
    CHANGING
         CHECK_FIELD = lv_check_field
         RETURNCODE = lv_returncode
. " SGT_VALIDATE_SEGMENT




ABAP code using 7.40 inline data declarations to call FM SGT_VALIDATE_SEGMENT

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!