SAP SEO_EDITOR_CALL Function Module for









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

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



Function SEO_EDITOR_CALL 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_EDITOR_CALL'"
EXPORTING
ED_INSTANCE = "
ED_PROGRAM = "
ED_DYNNR = "
* LINK_DYNNR = '0200' "
.



IMPORTING Parameters details for SEO_EDITOR_CALL

ED_INSTANCE -

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

ED_PROGRAM -

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

ED_DYNNR -

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

LINK_DYNNR -

Data type: DYNNR
Default: '0200'
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for SEO_EDITOR_CALL 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_ed_instance  TYPE CL_WB_CLEDITOR, "   
lv_ed_program  TYPE RSNEWLENG-PROGRAMM, "   
lv_ed_dynnr  TYPE DYNNR, "   
lv_link_dynnr  TYPE DYNNR. "   '0200'

  CALL FUNCTION 'SEO_EDITOR_CALL'  "
    EXPORTING
         ED_INSTANCE = lv_ed_instance
         ED_PROGRAM = lv_ed_program
         ED_DYNNR = lv_ed_dynnr
         LINK_DYNNR = lv_link_dynnr
. " SEO_EDITOR_CALL




ABAP code using 7.40 inline data declarations to call FM SEO_EDITOR_CALL

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 PROGRAMM FROM RSNEWLENG INTO @DATA(ld_ed_program).
 
 
DATA(ld_link_dynnr) = '0200'.
 


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!