SAP SEO_INTERFACE_CREATE_F_DATA Function Module for Interface dunkel anlegen









SEO_INTERFACE_CREATE_F_DATA is a standard seo interface create f data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Interface dunkel anlegen 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 seo interface create f data FM, simply by entering the name SEO_INTERFACE_CREATE_F_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function SEO_INTERFACE_CREATE_F_DATA 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 'SEO_INTERFACE_CREATE_F_DATA'"Interface dunkel anlegen
EXPORTING
* SAVE = SEOX_TRUE "
* SCWB_LANGU = "for internal use only

CHANGING
INTERFACE = "

EXCEPTIONS
EXISTING = 1 IS_CLASS = 2 NOT_CREATED = 3 DB_ERROR = 4
.



IMPORTING Parameters details for SEO_INTERFACE_CREATE_F_DATA

SAVE -

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

SCWB_LANGU - for internal use only

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

CHANGING Parameters details for SEO_INTERFACE_CREATE_F_DATA

INTERFACE -

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

EXCEPTIONS details

EXISTING -

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

IS_CLASS -

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

NOT_CREATED -

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

DB_ERROR -

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

Copy and paste ABAP code example for SEO_INTERFACE_CREATE_F_DATA 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_save  TYPE SEOX_BOOLEAN, "   SEOX_TRUE
lv_existing  TYPE SEOX_BOOLEAN, "   
lv_interface  TYPE VSEOINTERF, "   
lv_is_class  TYPE VSEOINTERF, "   
lv_scwb_langu  TYPE SYLANGU, "   
lv_not_created  TYPE SYLANGU, "   
lv_db_error  TYPE SYLANGU. "   

  CALL FUNCTION 'SEO_INTERFACE_CREATE_F_DATA'  "Interface dunkel anlegen
    EXPORTING
         SAVE = lv_save
         SCWB_LANGU = lv_scwb_langu
    CHANGING
         INTERFACE = lv_interface
    EXCEPTIONS
        EXISTING = 1
        IS_CLASS = 2
        NOT_CREATED = 3
        DB_ERROR = 4
. " SEO_INTERFACE_CREATE_F_DATA




ABAP code using 7.40 inline data declarations to call FM SEO_INTERFACE_CREATE_F_DATA

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.

DATA(ld_save) = SEOX_TRUE.
 
 
 
 
 
 
 


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!