Onboarding

Prerequisites

  • You've procured the licenses and have entitlements enabled in your global account for SAP Solution Sales Configuration, cloud edition.

  • SAP Variant Configuration and Pricing onboarding is complete. For steps on SAP Variant Configuration and Pricing onboarding, refer to: Administration Guide for SAP Variant Configuration and Pricing.

Context

Use your subaccount to subscribe to the SAP Solution Sales Configuration, cloud edition application.

Procedure

  1. Go to SAP Business Technology Platform's Cockpit, see Access the Cockpit.
  2. Log on using the S-user and password that you received with the purchase of our solution.
  3. From the welcome email, choose the global account to add additional members.

    For detailed steps, see Managing Global Accounts and Subaccounts Using the Cockpit.

  4. Create the subaccounts as described in Create A Subaccount.
    Use the following values:

    Name

    Description

    Display Name

    Depending on your integration scenario, give distinct subaccount display names.

    Subdomain

    Provide your own name.

    Region

    Europe (Frankfurt)(cf-eu10)
  5. Add entitlements to the subaccount as described in Configure Entitlements and Quotas for Subaccounts.
  6. Select the appropriate service plan.

    For available service plans, see Service Plan

  7. Subscribe to SaaS application, SAP Solution Sales Configuration. For detailed steps see, Subscribe to Multitenant Applications Using the Cockpit.
  8. Create a service instance for the service SAP Solution Sales Configuration.

    For detailed information on how to create service instances, see. Creating Service Instances

  9. Create a service binding.

    For detailed information on how to create service binding, see Creating a Service Binding.

  10. Assign user roles.
    1. For roles and their descriptions, see: User Roles
    2. To assign the role of Administrator to your S-user, see: Define a Role Collection.
  11. Cross-Origin Resource Sharing CORS.

    Cross-Origin Resource Sharing CORS is a mechanism that uses additional HTTP headers to tell a browser to let a web application running at one origin (domain) have permission to access selected resources from a server with a different origin. A web application performs a cross-origin HTTP request when it requests a resource of an origin (domain, protocol or port) different from its own origin. This is a general insight into CORSInformation published on non-SAP site

    For the service calls that are triggered from a client rendered UI, one can secure the sales configuration service by setting allowed CORS domains. The allowed CORS domains for service calls is set in the Administration UI. By default no domain is allowed, Only the domains set in the Administration UI will be allowed. Multiple domains can be set as comma separated values.

    In addition to the standard headers that are supported, the implemented CORS handling of the Sales Configuration service allows:

    • If-Match

    • If-None-Match

    • Cookie

    • X-CorrelationID

    The service exposes the headers:

    • Set-Cookie

    • ETag

    Scenarios with the CORS domain

    If the Origin does not match the maintained Origin in the CORS setting, the service will return error status 403 Forbidden and body Invalid CORS request.

    If the given HTTP method is not among the allowed methods (other than GET, DELETE, POST, PUT and PATCH) error 403 Forbidden is returned.

    If the Origin matches the maintained Origin, service returns valid response.