SAP CO_SAP_APPSERVER Function Module for









CO_SAP_APPSERVER is a standard co sap appserver 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 co sap appserver FM, simply by entering the name CO_SAP_APPSERVER into the relevant SAP transaction such as SE37 or SE38.

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



Function CO_SAP_APPSERVER 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 'CO_SAP_APPSERVER'"
  EXPORTING
   ACCESSOR_REFERENCE =  "
*  SELFMONI_EVENT = 'System_Register' "
*  TRACE = ' ' "
*  SID = ' ' "
   ABAP_OR_JAVA =  "
   APPSERVERNAME =  "
*  NUMBER = ' ' "
*  INSTANCEID = ' ' "
*  HOSTNAME = ' ' "
*  SYSTEMHOME = ' ' "
*  SELFMONI_NAME = ' ' "

 IMPORTING
   OBJECT_REFERENCE =  "
   OBJECT_HANDLE =  "
   QUALIFIED_NAME =  "

CHANGING
*  ADDITIONAL_PROPERTIES =  "
*  SELF_MONI_TID =  "

EXCEPTIONS
   COULD_NOT_CREATE_ATTACH_OBJECT = 1
.



IMPORTING Parameters details for CO_SAP_APPSERVER

ACCESSOR_REFERENCE -

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

SELFMONI_EVENT -

Data type: C
Default: 'System_Register'
Optional: Yes
Call by Reference: Yes

TRACE -

Data type: FLAG
Default: SPACE
Optional: Yes
Call by Reference: Yes

SID -

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

ABAP_OR_JAVA -

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

APPSERVERNAME -

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

NUMBER -

Data type: STRING
Default: SPACE
Optional: Yes
Call by Reference: Yes

INSTANCEID -

Data type: STRING
Default: SPACE
Optional: Yes
Call by Reference: Yes

HOSTNAME -

Data type: STRING
Default: SPACE
Optional: Yes
Call by Reference: Yes

SYSTEMHOME -

Data type: STRING
Default: SPACE
Optional: Yes
Call by Reference: Yes

SELFMONI_NAME -

Data type: C
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for CO_SAP_APPSERVER

OBJECT_REFERENCE -

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

OBJECT_HANDLE -

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

QUALIFIED_NAME -

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

CHANGING Parameters details for CO_SAP_APPSERVER

ADDITIONAL_PROPERTIES -

Data type: SLD_T_VALUELIST
Optional: Yes
Call by Reference: Yes

SELF_MONI_TID -

Data type: ALGLOBTID
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

COULD_NOT_CREATE_ATTACH_OBJECT -

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

Copy and paste ABAP code example for CO_SAP_APPSERVER 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_object_reference  TYPE CL_SLD_CIM_INSTANCE, "   
lv_accessor_reference  TYPE CL_SLD_ACCESSOR, "   
lv_additional_properties  TYPE SLD_T_VALUELIST, "   
lv_could_not_create_attach_object  TYPE SLD_T_VALUELIST, "   
lv_selfmoni_event  TYPE C, "   'System_Register'
lv_trace  TYPE FLAG, "   SPACE
lv_sid  TYPE STRING, "   SPACE
lv_object_handle  TYPE STRING, "   
lv_self_moni_tid  TYPE ALGLOBTID, "   
lv_abap_or_java  TYPE FLAG, "   
lv_qualified_name  TYPE STRING, "   
lv_appservername  TYPE STRING, "   
lv_number  TYPE STRING, "   SPACE
lv_instanceid  TYPE STRING, "   SPACE
lv_hostname  TYPE STRING, "   SPACE
lv_systemhome  TYPE STRING, "   SPACE
lv_selfmoni_name  TYPE C. "   SPACE

  CALL FUNCTION 'CO_SAP_APPSERVER'  "
    EXPORTING
         ACCESSOR_REFERENCE = lv_accessor_reference
         SELFMONI_EVENT = lv_selfmoni_event
         TRACE = lv_trace
         SID = lv_sid
         ABAP_OR_JAVA = lv_abap_or_java
         APPSERVERNAME = lv_appservername
         NUMBER = lv_number
         INSTANCEID = lv_instanceid
         HOSTNAME = lv_hostname
         SYSTEMHOME = lv_systemhome
         SELFMONI_NAME = lv_selfmoni_name
    IMPORTING
         OBJECT_REFERENCE = lv_object_reference
         OBJECT_HANDLE = lv_object_handle
         QUALIFIED_NAME = lv_qualified_name
    CHANGING
         ADDITIONAL_PROPERTIES = lv_additional_properties
         SELF_MONI_TID = lv_self_moni_tid
    EXCEPTIONS
        COULD_NOT_CREATE_ATTACH_OBJECT = 1
. " CO_SAP_APPSERVER




ABAP code using 7.40 inline data declarations to call FM CO_SAP_APPSERVER

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_selfmoni_event) = 'System_Register'.
 
DATA(ld_trace) = ' '.
 
DATA(ld_sid) = ' '.
 
 
 
 
 
 
DATA(ld_number) = ' '.
 
DATA(ld_instanceid) = ' '.
 
DATA(ld_hostname) = ' '.
 
DATA(ld_systemhome) = ' '.
 
DATA(ld_selfmoni_name) = ' '.
 


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!