SAP B2B Backoffice

SAP B2B Backoffice refers to the back-office module of SAP Commerce Cloud that is specifically designed for managing B2B (business-to-business) commerce operations. It provides a web-based interface where administrators, sales representatives, and customer service teams can manage various aspects of a B2B e-commerce platform.

To connect SAP B2B Backoffice to Relyance AI, you will need to configure two integration objects: InboundB2BCustomer and InboundB2BUnits, besides providing Backoffice information such as URL, username and password.

In SAP B2B Backoffice:

1. Go to the Backoffice Integration UI perspective and select Integration APIs > Authentication.

2. Select the mentioned objects and set the auth type to Basic.

In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the Settings (bottom-left corner).
3. Select Integrations.
4. Search and locate the SAP B2B 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.
   • Select the Process DSRs checkbox if necessary.
8. Confirm the integration Status reflects Connected.

The Authentication step asks for:

• Backoffice URL: Provide the URL of your backoffice. Example: https://backoffice.your-backoffice.model-t.cc.commerce.ondemand.com; required.
• Username: required; held as a secret.
• Password: required; held as a secret.

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. Username and Password are 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. Backoffice URL identifies which tenant, region or host to talk to. A wrong value there fails authentication and looks exactly like a bad secret.

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. 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.

resource "relyance_integration_connection" "sap_b2b" {
  vendor = "sap_b2b"
  name   = "<your connection name>"

  auth = {
    method = "username-password"
    params = {
      url = "<url>"
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      username = var.sap_b2b_username
      password = var.sap_b2b_password
    }
    secrets_wo_version = 1
  }

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