Show TOC

Background documentationAuthorizations in Change Management Services Locate this document in the navigation structure

 

The following activities are provided for Change Management Services (CM Services):

  • DICMServices.Create

    To create development configurations in the Development Infrastructure - Configuration Service, the user who performs the communication between ABAP and Java (HTTP destination) needs this action.

  • DICMServices.Modify

    To change development development configurations in the Development Infrastructure - Configuration Service, the user who performs the communication between ABAP and Java (HTTP destination) needs this action.

  • DICMServices.Delete

    To delete development configurations in the Development Infrastructure - Configuration Service, the user who performs the communication between ABAP and Java (HTTP destination) needs this action.

  • DICMServices.Export

    This action is required to start a release (export) of your own activities in the Developer Studio.

  • DICMServices.ExportForeign

    This action is required to start a release (export) of your own and third-party activities in the Developer Studio.

  • DICMServices.ExportAll

    This action is required to start a release (export) of your own and other activities in the Developer Studio as well as for exporting SDAs and SCAs with the Export Service.

  • DICMServices.Display

    This action is required to display configurations in the Development Infrastructure - Configuration Service.

  • DIImportService.Import

    The user that is used for the DeployWebProxy destination requires this action for starting an import.

    For more information on the user for the destination: Configuring CTS Deploy Web Services under Configuring HTTP Connection

  • DIDeployService.Display

    This action is required to display running deployments, for example, with the DI Deployer Servlet, and to display deployment logs with DI Log Viewer.

  • DIDeployService.Deploy

    The user that is used for the Deploy Web Service destination requires this action for executing a deployment on the runtime system. In addition, the user who triggers deployments using the DI Deployer Servlet requires this action.

  • DIDeployService.Configure

    The user that will be used for communication between ABAP and Java (HTTP destination) requires this action for configuring the Deploy Service.

  • DIDeployService.Administrator

    The user that will be used for communication between ABAP and Java (HTTP destination) requires this action for managing the Deploy Service.

Note Note

The role of a developer should include the following actions (in addition to existing CBS developer actions): DICMServices.Display, DIDeployService.Display, DICMServices.Export and (if required, for exporting the activities of other users) DICMServices.ExportForeign.

End of the note.