SAP CO_SAP_BCAGENT Function Module for
CO_SAP_BCAGENT is a standard co sap bcagent 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 bcagent FM, simply by entering the name CO_SAP_BCAGENT 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_BCAGENT 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_BCAGENT'".
EXPORTING
ACCESSOR_REFERENCE = "
* AGENTTYPE = ' ' "
* VERSION = ' ' "
* SEGMENTNAME = ' ' "
* SEGMENTTYPE = ' ' "
* SELFMONI_NAME = ' ' "
* SELFMONI_EVENT = 'Agent_Register' "
* TRACE = "
* CAPTION = ' ' "
* DESCRIPTION = ' ' "
* INSTALLDATE = ' ' "
* STATUS = ' ' "
NAME = "
* NAMEFORMAT = ' ' "
* PRIMARYOWNERCONTACT = ' ' "
* PRIMARYOWNERNAME = ' ' "
IMPORTING
OBJECT_REFERENCE = "
OBJECT_HANDLE = "
CHANGING
* ADDITIONAL_PROPERTIES = "
* ROLES = "
* SELF_MONI_TID = "
EXCEPTIONS
COULD_NOT_CREATE_ATTACH_OBJECT = 1
IMPORTING Parameters details for CO_SAP_BCAGENT
ACCESSOR_REFERENCE -
Data type: CL_SLD_ACCESSOROptional: No
Call by Reference: Yes
AGENTTYPE -
Data type: STRINGDefault: SPACE
Optional: Yes
Call by Reference: Yes
VERSION -
Data type: STRINGDefault: SPACE
Optional: Yes
Call by Reference: Yes
SEGMENTNAME -
Data type: STRINGDefault: SPACE
Optional: Yes
Call by Reference: Yes
SEGMENTTYPE -
Data type: STRINGDefault: SPACE
Optional: Yes
Call by Reference: Yes
SELFMONI_NAME -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: Yes
SELFMONI_EVENT -
Data type: CDefault: 'Agent_Register'
Optional: Yes
Call by Reference: Yes
TRACE -
Data type: FLAGOptional: Yes
Call by Reference: Yes
CAPTION -
Data type: STRINGDefault: SPACE
Optional: Yes
Call by Reference: Yes
DESCRIPTION -
Data type: STRINGDefault: SPACE
Optional: Yes
Call by Reference: Yes
INSTALLDATE -
Data type: STRINGDefault: SPACE
Optional: Yes
Call by Reference: Yes
STATUS -
Data type: STRINGDefault: SPACE
Optional: Yes
Call by Reference: Yes
NAME -
Data type: STRINGOptional: No
Call by Reference: Yes
NAMEFORMAT -
Data type: STRINGDefault: SPACE
Optional: Yes
Call by Reference: Yes
PRIMARYOWNERCONTACT -
Data type: STRINGDefault: SPACE
Optional: Yes
Call by Reference: Yes
PRIMARYOWNERNAME -
Data type: STRINGDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CO_SAP_BCAGENT
OBJECT_REFERENCE -
Data type: CL_SLD_CIM_INSTANCEOptional: No
Call by Reference: Yes
OBJECT_HANDLE -
Data type: STRINGOptional: No
Call by Reference: Yes
CHANGING Parameters details for CO_SAP_BCAGENT
ADDITIONAL_PROPERTIES -
Data type: SLD_T_VALUELISTOptional: Yes
Call by Reference: Yes
ROLES -
Data type: SLD_T_VALUELISTOptional: Yes
Call by Reference: Yes
SELF_MONI_TID -
Data type: ALGLOBTIDOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
COULD_NOT_CREATE_ATTACH_OBJECT -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CO_SAP_BCAGENT 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_agenttype | TYPE STRING, " SPACE | |||
| lv_version | TYPE STRING, " SPACE | |||
| lv_segmentname | TYPE STRING, " SPACE | |||
| lv_segmenttype | TYPE STRING, " SPACE | |||
| lv_selfmoni_name | TYPE C, " SPACE | |||
| lv_selfmoni_event | TYPE C, " 'Agent_Register' | |||
| lv_trace | TYPE FLAG, " | |||
| lv_roles | TYPE SLD_T_VALUELIST, " | |||
| lv_caption | TYPE STRING, " SPACE | |||
| lv_object_handle | TYPE STRING, " | |||
| lv_description | TYPE STRING, " SPACE | |||
| lv_self_moni_tid | TYPE ALGLOBTID, " | |||
| lv_installdate | TYPE STRING, " SPACE | |||
| lv_status | TYPE STRING, " SPACE | |||
| lv_name | TYPE STRING, " | |||
| lv_nameformat | TYPE STRING, " SPACE | |||
| lv_primaryownercontact | TYPE STRING, " SPACE | |||
| lv_primaryownername | TYPE STRING. " SPACE |
|   CALL FUNCTION 'CO_SAP_BCAGENT' " |
| EXPORTING | ||
| ACCESSOR_REFERENCE | = lv_accessor_reference | |
| AGENTTYPE | = lv_agenttype | |
| VERSION | = lv_version | |
| SEGMENTNAME | = lv_segmentname | |
| SEGMENTTYPE | = lv_segmenttype | |
| SELFMONI_NAME | = lv_selfmoni_name | |
| SELFMONI_EVENT | = lv_selfmoni_event | |
| TRACE | = lv_trace | |
| CAPTION | = lv_caption | |
| DESCRIPTION | = lv_description | |
| INSTALLDATE | = lv_installdate | |
| STATUS | = lv_status | |
| NAME | = lv_name | |
| NAMEFORMAT | = lv_nameformat | |
| PRIMARYOWNERCONTACT | = lv_primaryownercontact | |
| PRIMARYOWNERNAME | = lv_primaryownername | |
| IMPORTING | ||
| OBJECT_REFERENCE | = lv_object_reference | |
| OBJECT_HANDLE | = lv_object_handle | |
| CHANGING | ||
| ADDITIONAL_PROPERTIES | = lv_additional_properties | |
| ROLES | = lv_roles | |
| SELF_MONI_TID | = lv_self_moni_tid | |
| EXCEPTIONS | ||
| COULD_NOT_CREATE_ATTACH_OBJECT = 1 | ||
| . " CO_SAP_BCAGENT | ||
ABAP code using 7.40 inline data declarations to call FM CO_SAP_BCAGENT
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_agenttype) | = ' '. | |||
| DATA(ld_version) | = ' '. | |||
| DATA(ld_segmentname) | = ' '. | |||
| DATA(ld_segmenttype) | = ' '. | |||
| DATA(ld_selfmoni_name) | = ' '. | |||
| DATA(ld_selfmoni_event) | = 'Agent_Register'. | |||
| DATA(ld_caption) | = ' '. | |||
| DATA(ld_description) | = ' '. | |||
| DATA(ld_installdate) | = ' '. | |||
| DATA(ld_status) | = ' '. | |||
| DATA(ld_nameformat) | = ' '. | |||
| DATA(ld_primaryownercontact) | = ' '. | |||
| DATA(ld_primaryownername) | = ' '. | |||
Search for further information about these or an SAP related objects