Central Business Configuration(CBC)

This user guide explains how to integrate and manage SAP Central Business Configuration (CBC) with ReleaseOwl. It covers credential registration, environment setup, artifact synchronization, pipeline configuration, user story promotion, and monitoring through logs and reports to enable streamlined and traceable CBC deployments.

Credential Manager

1. Navigate to Administrative Manager.

2. Click on Register Credential.

3. Enter the required details:

   • Credential Name: Provide a name of your choice.

   • Credential Type: Select Central Business Configuration.

   • Scope: Choose the visibility of the credential:

     • Global – Accessible to all users.

     • Private – Accessible only to the user who created it.

   • User Name: Enter the SAP CBC username.

   • Password: Enter the SAP CBC password.

4. Click Save.

Environment Registration

1. Navigate to the Environment section.

2. Select Central Business Configuration and click Register.

1. Enter the required details:

• Name → Provide a meaningful name.

• Credentials → Select the credentials created in Credential Management.

• Host URL → Enter your tenant URL in the format: https://<tenantID>.cbc.ap.one.cloud.sap.

• Workspace → After entering the Host URL, the available CBC workspaces will be auto-populated in the dropdown, from which you can select the required workspace.

• Environment Type → Choose the appropriate type of environment (e.g., Development, Test, Production).

1. Click on the Create button to register the configuration.

Assign Environment to a Project

1. Go to the Projects section and select your project.

2. Enter necessary details and choose Project Type as SAP Public Cloud.

1. Click “Switch to Project” for the project you just created.

1. From the Projects dropdown (top-right corner), select Project Settings → Environment.

1. Click +Add to add a new environment.

1. On the subsequent screen, select the required environment from the Source list. Only artifacts with a defined source are synced to ReleaseOwl, and you can also add multiple source environments.

1. The environment is added to the corresponding project in ReleaseOwl.

2. Click on the Users tab. This tab lists all existing users associated with the project.

3. Click on the edit (lock) icon next to the user for whom you want to manage roles and permissions.

1. Scroll down to the Environments section.

2. Select the Deploy checkbox for the relevant environment(s) to grant the user deployment access.

Synchronize Artifacts

1. Switch to the Project View.

2. Click on Central Business Configuration in the Build section.

3. Within the CBC screen, click the Synchronize button.

4. When synchronization is triggered, the system retrieves Deploy Scope and Organizational Structure activities from CBC where the Action is set to Deploy.

1. These activities are then pulled into the project, ensuring that the latest CBC configurations are available for deployment workflows.

1. After synchronization, click on the Action button for the desired activity.

2. This will open detailed information about the selected activity.

1. Under the Versions tab, you can view the history of all modifications performed on the activity. Note: The Versions tab is not available in the CBC (Central Business Configuration).

   • If the task is in Open status and is synchronized with Central Business Configuration, the task will be reopened.

   • If the task is in Deploy status and is reopened on a later date, a new version will be created to capture the changes.

2. This allows teams to track changes over time and ensure accountability.

1. Change Logs: It shows the details of activity changes, including the Task Name, Area, Workspace, Changed By, and Changed On. It provides visibility into where the change was made and by whom, helping teams monitor updates across tasks and workspaces.

Creating a Release Pipeline

Release Pipelines in ReleaseOwl manage approvals, validations, deployments, automated tests, task assignments, and user story updates for SAP systems.

1. Create a New Release Pipeline

• Navigate to Release Pipelines.

• Click Create New Release Pipeline.

• Provide a Pipeline Name.

• Add stages (e.g., QA, Prod) and assign tasks to each stage.

Deployment Tasks

A Deployment Task is used to deploy artifacts into the target S/4HANA Public Cloud environment as part of a pipeline stage.

Steps to Configure a Deployment Task

1. In a Task Stage, click the Add button and select Deployment Task.

2. Fill in the required details:

• Name → Enter a meaningful name for the deployment task.

• Deploy Type → Select CBC.

• Select the Environment → Choose the target environment where the deployment should be executed.

Notification Options

• Notify Users : Sends an email notification to all users involved in the pipeline when the pipeline is triggered or when specific events occur. By selecting this you will see the following options:

• Notify To : Allows you to configure additional recipients for deployment notifications. Options include:

  • User: Notify a specific user.

  • Role : Notify all users assigned to a specific role.

  • Custom: Notify based on a custom component and role defined in ReleaseOwl.

• Notify Promotion User → Sends an email notification to the user who initiated the promotion (from a user story or release package), regardless of whether the task succeeds or fails.

1. After entering the details, click Save to add the deployment task.

Creating and Promoting a User Story

A User Story in ReleaseOwl is used to track, manage, and deploy tasks from the source system to the target (destination) environment.

Steps to Create and Promote a User Story

1. Create a User Story

   • Navigate to Change Management.

   • Click Create New User Story.

   • Enter the required details (e.g., Name, Description, and other metadata).

   • Save the User Story.

2. Add Artifacts

   • Open the User Story and click Edit.

   • Click the + Add button to attach CBC activities as artifacts.

   • After selecting the required artifacts, click Save.

3. Promote the User Story

• Once the artifacts are attached, click on the Promote button.

• Promotion moves the User Story into the defined pipeline stage, where it proceeds through tasks such as deployment according to the configured pipeline.

Deployment Logs

Deployment Logs are generated during the execution of a Deployment Task to provide end-to-end traceability of the deployment process. The logs include the following information:

• Deployed Environment: Specifies the target environment where the artifacts were deployed.

• Version: Indicates the version of the artifacts that were part of the deployment.

• User Story: Identifies the user story that triggered the deployment.

• Deployment Status: Displays the outcome of the deployment, either Successful or Failed.

• Tenant URL: Provides the URL of the tenant where the deployment was executed.

• Deployment ID: A unique identifier assigned to each deployment for traceability. Selecting the Deployment ID opens the execution details of the deployment task.