# Central Business Configuration

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** <a href="#credential-manager" id="credential-manager"></a>

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 **Public Cloud**.
   * **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**.

<figure><img src="https://1890383800-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDWyxe6hm5vqosFaByVgs%2Fuploads%2F8mjcJYfYtlHzAYfaPKP1%2Fimage.png?alt=media&#x26;token=a3c95af4-3db7-405e-b5af-ae366a60498e" alt=""><figcaption></figcaption></figure>

### **Environment Registration** <a href="#environment-registration" id="environment-registration"></a>

1. Navigate to the **Environment** section.
2. Select **Central Business Configuration** and click **Register**.

<figure><img src="https://1890383800-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDWyxe6hm5vqosFaByVgs%2Fuploads%2FGJWn6oFZ50LgTdE5Sja1%2Fimage.png?alt=media&#x26;token=6bbc9eff-80d7-4545-b210-bd4db1cce44e" alt=""><figcaption></figcaption></figure>

3. 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 workspaces will be **auto-populated** in the dropdown. Select the respective workspace.
* **Environment Type** → Choose the appropriate type of environment (e.g., Development, Test, Production).

4. Click on the **Create** button to register the configuration.

<figure><img src="https://1890383800-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDWyxe6hm5vqosFaByVgs%2Fuploads%2F3jPewowFIrZEMmWzUfRJ%2Fimage.png?alt=media&#x26;token=61df8355-efc4-47fa-ac3a-fd93424ab74b" alt=""><figcaption></figcaption></figure>

### **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**.

<figure><img src="https://1890383800-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDWyxe6hm5vqosFaByVgs%2Fuploads%2Fo1X0OMxzDphrATktjwVi%2Fimage.png?alt=media&#x26;token=f4778f32-e392-4316-9cd7-5032cb3a6367" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://releaseowl.gitbook.io/releaseowl-docs/~gitbook/image?url=https%3A%2F%2F1890383800-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FDWyxe6hm5vqosFaByVgs%252Fuploads%252FoY3Qi0wCDH1IdOUqlqCM%252Fimage.png%3Falt%3Dmedia%26token%3D4a0c87d4-12f3-49cd-b4c6-dd80e8051c41&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=36fc4a&#x26;sv=2" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://releaseowl.gitbook.io/releaseowl-docs/~gitbook/image?url=https%3A%2F%2F1890383800-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FDWyxe6hm5vqosFaByVgs%252Fuploads%252FFRngNLa4zFflP57OEDkW%252Fimage.png%3Falt%3Dmedia%26token%3D7cb30c81-5048-4fd4-840b-1394ad9d2003&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=e25e5410&#x26;sv=2" alt=""><figcaption></figcaption></figure>

5. Click **+Add** to add a new environment.

<figure><img src="https://1890383800-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDWyxe6hm5vqosFaByVgs%2Fuploads%2F5rrFQAQ0GIIpLv1A5bCi%2Fimage.png?alt=media&#x26;token=1dd9589b-8257-4d84-9528-8cc475742af6" alt=""><figcaption></figcaption></figure>

6. In the subsequent screen, choose the required environment from the list displayed by selecting Source. Only the artifacts with source are synced to ReleaseOwl.

<figure><img src="https://releaseowl.gitbook.io/releaseowl-docs/~gitbook/image?url=https%3A%2F%2F1890383800-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FDWyxe6hm5vqosFaByVgs%252Fuploads%252FiLZgyh0opkwImR2q0yzw%252Fimage.png%3Falt%3Dmedia%26token%3D97bb773c-438d-4a7a-aefd-805cb5853316&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=602ae35e&#x26;sv=2" alt=""><figcaption></figcaption></figure>

7. The environment is added to the corresponding project in ReleaseOwl.
8. Click on the **Users** tab. This tab lists all existing users associated with the project.
9. Click on the **edit (lock)** icon next to the user for whom you want to manage roles and permissions.

<figure><img src="https://1890383800-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDWyxe6hm5vqosFaByVgs%2Fuploads%2FCaNamDstXGeZjJk4sL82%2Fimage.png?alt=media&#x26;token=dfb27eb7-a1d0-4daa-813c-7de7a1e4d856" alt=""><figcaption></figcaption></figure>

10. Scroll down to the Environments section.
11. Check the Deploy checkbox for the relevant environment(s) to enable deploy access.

<figure><img src="https://releaseowl.gitbook.io/releaseowl-docs/~gitbook/image?url=https%3A%2F%2F1890383800-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FDWyxe6hm5vqosFaByVgs%252Fuploads%252F0cPCCoVERKPduu1KvXau%252Fimage.png%3Falt%3Dmedia%26token%3D01ab2d64-1f49-44a5-87c6-b2880a7956fa&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=a378ba3d&#x26;sv=2" alt=""><figcaption></figcaption></figure>

### **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 fetches all activities from CBC that meet the following criteria:

* **Status** = *Open*
* **Action** = *Deploy*

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

<figure><img src="https://1890383800-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDWyxe6hm5vqosFaByVgs%2Fuploads%2Fmo9M0f19By79PTgVqdmD%2Fimage.png?alt=media&#x26;token=ae5f22cc-e370-4ebc-8210-0938d0181fc0" alt=""><figcaption></figcaption></figure>

6. After synchronization, click on the **Action** button for the desired activity.
7. This will open detailed information about the selected activity.

<figure><img src="https://1890383800-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDWyxe6hm5vqosFaByVgs%2Fuploads%2Fm1zbJv2hek3LSSfTceMp%2Fimage.png?alt=media&#x26;token=2ad6a512-87f4-4c63-a0ac-8d7d18a76731" alt=""><figcaption></figcaption></figure>

8. Under the **Versions** tab, you can see a history of all modifications performed on the activity.
   * Each version entry includes:
     * **Modified By** – The user who performed the change.
     * **Modified Date** – The timestamp when the change was applied.
     * **Status** – Indicates the state of the activity at the time of modification, such as:
       * *Open* – The activity is currently open and in progress.
       * *Closed/Completed* – The activity has been finalized and no further modifications are expected.
9. This allows teams to track changes over time and ensure accountability.

<figure><img src="https://1890383800-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDWyxe6hm5vqosFaByVgs%2Fuploads%2FbCCyGJakhZ6XMG8SkkPz%2Fimage.png?alt=media&#x26;token=463cdca1-d0bb-4ef9-8011-fde535b811ed" alt=""><figcaption></figcaption></figure>

10. **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.

<figure><img src="https://1890383800-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDWyxe6hm5vqosFaByVgs%2Fuploads%2FQXgnVvE2zyYTOoocgEeD%2Fimage.png?alt=media&#x26;token=06e343d5-350e-4065-95a6-197d85e4c2d0" alt=""><figcaption></figcaption></figure>

### **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**.

<figure><img src="https://1890383800-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDWyxe6hm5vqosFaByVgs%2Fuploads%2Fylqy7ZsMo6Jouk06utf2%2Fimage.png?alt=media&#x26;token=c439857f-f7aa-4a59-8ef6-57f064b6a57d" alt=""><figcaption></figcaption></figure>

* Provide a **Pipeline Name**.

<figure><img src="https://1890383800-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDWyxe6hm5vqosFaByVgs%2Fuploads%2F8mZa7hWbFih2QjgUoPIg%2Fimage.png?alt=media&#x26;token=96fda005-1b2e-41a3-be3e-c9eafcb46590" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://1890383800-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDWyxe6hm5vqosFaByVgs%2Fuploads%2FjTUgZfvLWuv6c36nI0ri%2Fimage.png?alt=media&#x26;token=b184f546-b3c9-4585-8c8a-71ee624de795" alt=""><figcaption></figcaption></figure>

**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.
* **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.
* **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.

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

<figure><img src="https://releaseowl.gitbook.io/releaseowl-docs/~gitbook/image?url=https%3A%2F%2F1890383800-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FDWyxe6hm5vqosFaByVgs%252Fuploads%252FwonM23bT0N26ZFUfrLHz%252Fimage.png%3Falt%3Dmedia%26token%3D312a9a79-83e9-43d1-b558-76c0be6e1941&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=ee0157a8&#x26;sv=2" alt=""><figcaption></figcaption></figure>

**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 will go through tasks such as **Validation**, **Approval**, and **Deployment** based on the configured pipeline.

<figure><img src="https://1890383800-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDWyxe6hm5vqosFaByVgs%2Fuploads%2FlRcsTDUFKRKxBI0LiSuK%2Fimage.png?alt=media&#x26;token=975e06e6-3c80-4d8f-b2ed-90e69b063b7c" alt=""><figcaption></figcaption></figure>

#### **Deployment Logs**

The **Deployment Logs** are generated during execution of a **Deployment Task** and provide full traceability of the deployment process.

**Details captured in Deployment Logs:**

* **Deployed Environment** → Provides information about the target environment where the artifacts were deployed.
* **Version** → Provides details of the version of the artifacts included in the deployment.
* **User Story** → Provides details of the associated user story that triggered the deployment.
* **Deployment Status** → Provides details of whether the deployment was *Successful* or *Failed*.
* **Tenant URL** → Provides details of the tenant URL where the deployment was executed.
* **Deployment ID** → Provides a unique identifier for the deployment, ensuring easy traceability.

<figure><img src="https://1890383800-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDWyxe6hm5vqosFaByVgs%2Fuploads%2FhOjN9tsWcqNQrAwYpATA%2Fimage.png?alt=media&#x26;token=3ce0535c-b20c-45ef-a38c-c47dc0294fcd" alt=""><figcaption></figcaption></figure>
