SAP

SAP is a suite of applications used to collect and store business data in areas such as …

  • product planning, purchasing, and supply chain management
  • Manufacturing and delivery
  • inventory management
  • shipping and payment
  • finance

To use Skuid’s pre-configured SAP data source type, you’ll need to do two things:

  1. Set up an SAP Gateway service.
  2. Create an authentication provider for the SAP Gateway service.
  3. Set up a new data source that uses that authentication provider.

Configuration

In SAP

To use SAP with Skuid, you’ll need to set up an SAP Gateway service.

Warning

Because SAP configuration can potentially impact others in the enterprise, we recommend you work with your company’s IT Administrator to set this up correctly.

Ask the IT Admin to:

  • Set up an SAP Gateway service exposing SAP data:

    • use appropriate CRUD permissions set for this Gateway
    • configure all CRUD data operations for each data object to accept batch requests
      • All edits from Skuid to SAP are sent as OData batch requests—even if the update affects only a single record.
      • Skuid adheres to the OData specifications for all data interactions.
    • Give you—as the Skuid admin—the service document URL for the service.

    Note

    This URL will provide the SAP domain and “path to service” information needed to set up the datasource in Skuid (below).

In Skuid

Using basic HTTP authentication with username and password credentials

  1. Navigate to Configure > Data Sources > Data Source.
  2. Click New Data Source.
  3. Select SAPGateway.
  4. Enter a name for your data source.
  5. Click Next Step.

In Step 2: Configure Connection and Authentication, add your data source settings.

Connection Details:

  • URL: This field will be prepopulated with https://<SAP_DOMAIN>/sap/opu/odata/<PATH_TO_SERVICE> Enter the values for <SAP_DOMAIN> and <PATH_TO_SERVICE> based on your SAP instance.
  • Use Apex Proxy: Checked.

Authentication:

  • Authentication Method: Leave this as Separate Authentication URL.
  • Authentication URL: This URL typically needs to match the URL field in the Connection Details column.
  • Credential Source: You may select how to store your SAP credentials within Skuid:
    • Share a set of credentials among all users in your site (Shared: Org-Wide).
      • Note: Depending on your enterprise configuration, this is typically not recommended.
    • Share credentials between certain users by profile (Shared: Per-Profile, with optional Org-wide Default)
    • Have individual users enter their credentials within Skuid (Per-User, with optional Profile / Org-wide Defaults)

Note

For more information on credentialing options, see Authentication and Skuid as well as Share credentials or use credentials stored within Skuid from our Salesforce data source topic.

Using other methods for authentication

If you are authenticating to SAP using a method besides HTTP auth—such as SAML— you must make the following adjustment in the Authentication section of Authentication Request Details > Auth Request Headers:

  • In Authentication Request Details > Auth Request Headers, remove Authorization: Basic {{$Auth.BasicAuth}}
  • In Headers to send with every request > Common Request Headers, remove Authorization: Basic {{$Auth.BasicAuth}}