SAP CA_SYSTEMAPPLICATIONSERVER Function Module for

Search SAP Function Modules

CA_SYSTEMAPPLICATIONSERVER is a standard ca systemapplicationserver 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 ca systemapplicationserver FM, simply by entering the name CA_SYSTEMAPPLICATIONSERVER 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 CA_SYSTEMAPPLICATIONSERVER 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 'CA_SYSTEMAPPLICATIONSERVER'"
  EXPORTING
   ACCESSOR_REFERENCE =  "
   ABAP_OR_JAVA =  "
   MGD_SYS_HANDLE =  "
   APPSRV_HANDLE =  "
*  SELFMONI_NAME = ' ' "
*  SELFMONI_EVENT = ' ' "
*  TRACE = ' ' "

 IMPORTING
   ASSOCIATION_REFERENCE =  "
   ASSOCIATION_HANDLE =  "

CHANGING
*  NONKEY_ASSOCIATION_PROPERTIES =  "
*  SELF_MONI_TID =  "

EXCEPTIONS
   COULD_NOT_CREATE_ATTACH_ASSOC = 1 

.

IMPORTING Parameters details for CA_SYSTEMAPPLICATIONSERVER

ACCESSOR_REFERENCE -

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

ABAP_OR_JAVA -

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

MGD_SYS_HANDLE -

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

APPSRV_HANDLE -

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

SELFMONI_NAME -

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

SELFMONI_EVENT -

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

TRACE -

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

EXPORTING Parameters details for CA_SYSTEMAPPLICATIONSERVER

ASSOCIATION_REFERENCE -

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

ASSOCIATION_HANDLE -

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

CHANGING Parameters details for CA_SYSTEMAPPLICATIONSERVER

NONKEY_ASSOCIATION_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_ASSOC -

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

Copy and paste ABAP code example for CA_SYSTEMAPPLICATIONSERVER 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.

ABAP code using 7.40 inline data declarations to call FM CA_SYSTEMAPPLICATIONSERVER

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