# SAP C4C (Cloud for Customer)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/35094010535309/ext-1d407e99a1.png)
**SAP C4C (Cloud for Customer)** is a cloud-based Customer Relationship Management (CRM) solution from SAP. It helps businesses manage sales, service, and marketing activities, aiming to improve customer engagement and loyalty.

To connect SAP C4C with Relyance AI, you will need a valid user ID and password.

Please note the URL to be used will depend on the instance you use.

#### In the Relyance AI application:

![Screenshot](https://assets.relyanceuat.xyz/images/docs/35094010535309/35094010528269.png)
1. Login to your Relyance account.
2. Navigate to the Settings (bottom-left corner).
3. Select Integrations.
4. Search and locate the **SAP Cloud for Customer** integration card and click it to open its connections.
5. Scroll down until the **Connection Properties** section.
6. Choose your settings accordingly and **Save Properties**.
7. On the **Edit Connection** section, choose **Basic Auth** and complete the **URL**, **Username** and **Password** fields, and hit **Connect**.
8. Confirm the integration Status reflects **Connected**.

![Screenshot](https://assets.relyanceuat.xyz/images/docs/35094010535309/35093948038797.png)

The **Authentication** step asks for:

- **URL**: required.
- **Username**: required.
- **Password**: required; held as a secret.

<!-- failure-modes:begin (generated from the integration catalog; do not hand-edit) -->

## If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. **A feature you enabled returns nothing.** Some scopes belong to a feature rather than to the connection: **Data subject requests** needs `Default`. Turning the feature on after the connection exists does not widen the grant it already holds, so re-authenticate the connection.
2. **A credential rotated at the vendor is not picked up here.** **Password** is stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.
3. **Check the address fields before suspecting the credentials.** **URL** identifies which tenant, region or host to talk to. A wrong value there fails authentication and looks exactly like a bad secret.

<!-- failure-modes:end -->

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). Non-secret fields go in `auth.params`; secret fields go in `auth.secrets_wo`, which is write-only — never stored in Terraform state. Rotate secrets by bumping `auth.secrets_wo_version`.

```hcl
resource "relyance_integration_connection" "sap_cloud_for_customer" {
  vendor = "sap_cloud_for_customer"
  name   = "<your connection name>"

  auth = {
    method = "username-password"
    params = {
      url = "https://account123.crm.ondemand.com"
      username = "<username>"
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      password = var.sap_cloud_for_customer_password
    }
    secrets_wo_version = 1
  }

  scans = { "data-inspection" = { enabled = true } }
}
```

<!-- terraform-examples:end -->