SAP CFX_API_COLLABORATION_CHANGE Function Module for Change All Attributes of a Collaboration

Search SAP Function Modules

CFX_API_COLLABORATION_CHANGE is a standard cfx api collaboration change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change All Attributes of a Collaboration processing and below is the pattern details for this FM, 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 cfx api collaboration change FM, simply by entering the name CFX_API_COLLABORATION_CHANGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: CFX_API_COLLABORATION
Program Name: SAPLCFX_API_COLLABORATION
Main Program: SAPLCFX_API_COLLABORATION
Appliation area:
Release date: 04-Feb-2005
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CFX_API_COLLABORATION_CHANGE 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 'CFX_API_COLLABORATION_CHANGE'"Change All Attributes of a Collaboration
  EXPORTING
   I_COLLABORATION_ID =  "ID of Collaboration
   I_NAME =  "New Name of Collaboration
   I_DESCRIPTION =  "New Description of Collaboration
*  I_IS_SYNDICATE = CFXA0_SC_FALSE "Syndicate
   I_DEADLINE =  "Due Date and Time as UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
   I_IS_TEMPLATE =  "Template? 'yes' = yes or 'no' = no

 IMPORTING
   ES_FAULT =  "Error According to SOAP
   E_FAULTSTRING =  "Short Error Text for User

.

IMPORTING Parameters details for CFX_API_COLLABORATION_CHANGE

I_COLLABORATION_ID - ID of Collaboration

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

I_NAME - New Name of Collaboration

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

I_DESCRIPTION - New Description of Collaboration

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

I_IS_SYNDICATE - Syndicate

Data type: CFX_API_T_BOOL
Default: CFXA0_SC_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_DEADLINE - Due Date and Time as UTC Time Stamp in Short Form (YYYYMMDDhhmmss)

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

I_IS_TEMPLATE - Template? 'yes' = yes or 'no' = no

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

EXPORTING Parameters details for CFX_API_COLLABORATION_CHANGE

ES_FAULT - Error According to SOAP

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

E_FAULTSTRING - Short Error Text for User

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

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

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