SAP SPOT_COMPOSITE_EDITOR_VERSION Function Module for









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

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



Function SPOT_COMPOSITE_EDITOR_VERSION 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 'SPOT_COMPOSITE_EDITOR_VERSION'"
  EXPORTING
   I_OBJECT =  "
   I_SPOT_HEADER =  "
   I_REF =  "
   I_MOD_LANGU =  "
   I_ORG_LANGU =  "
   I_SHORTTEXT =  "
.



IMPORTING Parameters details for SPOT_COMPOSITE_EDITOR_VERSION

I_OBJECT -

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

I_SPOT_HEADER -

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

I_REF -

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

I_MOD_LANGU -

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

I_ORG_LANGU -

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

I_SHORTTEXT -

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

Copy and paste ABAP code example for SPOT_COMPOSITE_EDITOR_VERSION 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_i_object  TYPE SEU_OBJKEY, "   
lv_i_spot_header  TYPE ENHSPOTCOMPHEAD, "   
lv_i_ref  TYPE CL_ENH_SPOT_COMPOSITE_EDITOR, "   
lv_i_mod_langu  TYPE LANGU, "   
lv_i_org_langu  TYPE LANGU, "   
lv_i_shorttext  TYPE STRING. "   

  CALL FUNCTION 'SPOT_COMPOSITE_EDITOR_VERSION'  "
    EXPORTING
         I_OBJECT = lv_i_object
         I_SPOT_HEADER = lv_i_spot_header
         I_REF = lv_i_ref
         I_MOD_LANGU = lv_i_mod_langu
         I_ORG_LANGU = lv_i_org_langu
         I_SHORTTEXT = lv_i_shorttext
. " SPOT_COMPOSITE_EDITOR_VERSION




ABAP code using 7.40 inline data declarations to call FM SPOT_COMPOSITE_EDITOR_VERSION

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!