Provisioning and Post-Provisioning

Objective

After completing this lesson, you will be able to provision next-gen SAP Ariba Suite applications using SAP for Me and complete the required post-provisioning configuration steps to prepare the system for user onboarding and data replication.

Provisioning SAP Ariba Suite Applications

This video provides the steps to provision Foundation Suite and Next-Gen Ariba.

With identity foundations, shared services, and the business network established, Nova Retail Group is ready to activate their next-gen SAP Ariba application environments.

Unlike current-gen provisioning approaches that relied on ticket-driven coordination, next-gen SAP Ariba provisioning introduces a standardized, SAP-managed experience integrated with SAP for Me.

Before You Begin

Make sure all three prerequisites have been completed in SAP for Me:

  • SAP Cloud Identity Services (SCI) — provisioned and activated
  • Foundation for SAP Business Suite — status: Ready
  • SAP Business Network (SBN) — status: Ready

Key Considerations

  • The S-user triggering provisioning must have Edit Cloud Data authorization against the installation number of the product or package
  • Always provision Test before Production
  • For Test, Demo, And Development (TDD) licenses: You can only provision a test environment — a production environment is not included
  • Only SAP Ariba Invoicing and SAP Ariba Buying support the Development tenant type — no other SAP Ariba solutions support a Development tenant on Production
  • If possible, provision all required applications together in a single session. If you add an application later, choose Existing Solution to reuse the existing SCI tenant, Business Data Orchestration system, and master data
  • Integration systems (SCI, shared services) are automatically retrieved from the Foundation for SAP Business Suite provisioning — do not switch the SCI tenant post-provisioning

Note

For customers on SAP S/4HANA Cloud Public Edition, the provisioning path is different. Public Edition uses a native integration that SAP manages directly — no SAP Integration Suite, managed gateway add-on is required. Consultants must scope this difference explicitly: integration tasks, timelines, and skill sets are not the same as for Private Cloud or on-premise environments

Provisioning SAP Ariba Suite Applications

Caution

Foundation for SAP Business Suite and SAP Business Network must be in status Ready before provisioning any SAP Ariba Suite application
  1. Sign in to SAP for Me using your S-user ID or SAP Universal ID.
  2. Go to Portfolio & Products→My Product Packages→SAP Ariba Suite.

    SAP Ariba Suite represents the full procurement suite — only solutions you are entitled to are displayed.

  3. Choose Go to Application or the Applications tab — all available SAP Ariba Suite applications are displayed.
  4. Choose Start Provisioning→New Solution.

    Note

    If you have already provisioned one application and want to add another, choose Start Provisioning→Existing Solution or go to the Solutions tab and choose Edit.
  5. Fill in General Information and select Next Step:
    • Name — unique (max 63 chars; cannot be renamed after creation)
    • Path — select or create a resource group
    • Business Type — Development or Test first; Production last. Development only available for SAP Ariba Invoicing and SAP Ariba Buying
  6. Select applications and choose Next Step.

    Applications in your subscription are automatically selected. Recommendation: select all entitled applications at once for successful integration and shared services reuse.

  7. Set up systems and select Next Step — specify integration details per application:
    ApplicationParameters
    SAP Ariba ContractsFoundation for SAP Business Suite System (same landscape); SCI System auto-filled
    SAP Ariba SourcingFoundation for SAP Business Suite System; SCI System auto-filled
    SAP Ariba Category ManagementSAP Ariba Sourcing System; Foundation for SAP Business Suite System; SCI System auto-filled
    SAP Ariba InvoicingFoundation for SAP Business Suite System; SCI System auto-selected from Business Suite tenant
    SAP Ariba Supplier ManagementFoundation for SAP Business Suite System; SCI System auto-filled
    SAP Ariba BuyingRefer to Setting Up SAP Ariba Buying Using SAP for Me
  8. Configure parameters and select Next Step.

    Note

    Data Center is pre-filled from your contract (EU30 or US30) — validate it matches your required region.
  9. Specify a Formation Name, select Review, verify all information, then select Finish.
  10. Monitor provisioning status: Go to Portfolio & Products→SAP Ariba Suite→Resources— status changes to Request Submitted; monitor until Ready.

To find tenant URLs: My Product Packages→SAP Ariba Suite→Customer Landscape, then select the system link under Provisioned System→Access Information.

Once all applications show Ready, proceed to the Post-Provisioning tile.

Post-Provisioning: Verification, Configuration, and Readiness

Provisioning creates the tenant infrastructure — but a freshly provisioned next-gen SAP Ariba environment is not yet ready for business use. A series of post-provisioning steps is required to connect the identity layer, verify application access, configure foundational settings, and prepare the system for data replication and business process configuration.

These post-provisioning steps are often underestimated in project planning. They are not optional configuration tasks — they are mandatory prerequisites before the system can authenticate users, process transactions, or connect to ERP backends. Budget time in your project plan for each step, and do not schedule end-user access or UAT before confirming that all post-provisioning validation checks have passed.

Note

Unlike SAP Cloud Identity Services, next-gen SAP Ariba Suite applications do not send an e-mail notification when provisioning completes. The administration team must actively monitor SAP for Me to detect completion or failure. Establish a monitoring cadence during the provisioning window and build this into your implementation runbook.

Step 1: Verify Provisioning Status and Tenant URLs

  1. Log in to SAP for Me and navigate to Systems & Provisioning→Resources.
  2. Confirm all provisioned applications show status Ready.
  3. Select each application tile to reveal the tenant URL.
  4. Open each URL in a browser and confirm the login page loads (you should see the SCI login prompt).
  5. If any application shows Failed, choose Retry to retrigger provisioning. If it fails again, open a support case (see Getting Support section).

Expected URLs to verify:

  • SAP Ariba Launchpad (SAL): your main entry point
  • Administration Center: configuration and management
  • Each individual application (Buying, Sourcing, Contracts, Invoicing, Supplier Lifecycle and Performance): accessible via SAL tiles

Step 2: Connect Core Data Management (CDM) and SAP Cloud Identity Services

Note

This is a mandatory one-time setup that enables user replication from SCI into CDM.

  1. Open the SCI Administration Console (https://<tenant>.accounts.ondemand.com/admin).
  2. Navigate to Applications & Resources→Applications.
  3. Locate the CDM application entry (created during provisioning).
  4. Generate the Client ID and Client Secret for the CDM connection.
  5. Save these credentials securely — this is a one-time generation. If lost, you must regenerate, which will invalidate the existing connection.
  6. In the Administration Center, navigate to the CDM connection settings and enter the Client ID and Secret.

Step 3: Initial Admin Login and Role Verification

  1. Log in to the SAP Ariba Launchpad using the technical admin user created during SCI provisioning.
  2. Confirm you can see the Administration Center tile.
  3. Open the Administration Center and verify you have access to:
    • User Groups (NAMS)
    • Source System Management
    • Application Configuration
    • Transport Management
  4. If tiles are missing, verify the admin user is assigned to the correct authorization groups in NAMS.

Step 4: Configure Source System Management

Before any data can flow from your ERP to next-gen SAP Ariba, you must register your ERP system(s) as source systems.

  1. In the Administration Center, navigate to Source System Management.
  2. Register your ERP system using the BusinessSystemID (logical system name from ERP).
  3. Confirm SAP Integration Suite, managed gateway (formerly CIG) add-on connectivity is established.

Verify the connection status shows Connected.

Note

Until Source System Management is correctly configured and connected, no business data can flow between the ERP and the SAP Ariba applications.

For a greenfield implementation, you are setting up a fresh connection. There is no migration of existing integration configurations from current-gen. The SAP Integration Suite, managed gateway add-on on the ERP side must be installed and configured before this step succeeds.

Step 5: Confirm Integration Readiness

Before moving to data replication, verify the following:

CheckHow to VerifyIf It Fails
SAP Integration Suite, managed gateway add-on installed on ERPCheck ERP transaction for component versions (ARBCI1/ARIBCI2/S4CI1)Install required support pack: Supported Backend Systems and Components
Cloud Connector configuredOpen Cloud Connector admin and verify the connection to BTP subaccountFollow SAP Help: Cloud Connector setup guide
SAP Integration Suite, managed gateway reachable from Admin CenterSource System Management shows "Connected"Check Cloud Connector tunnel, firewall rules, destination config
SCI-CDM connection activeUsers replicate successfully from SCI to CDMRegenerate client credentials, verify CDM app registration in SCI
SBN linked to formationSAP for Me > Formations shows sbncore tenantChoose "Include Systems" to associate SBN

Common Post-Provisioning Issues

SymptomLikely CauseResolution
Tenant URL returns 403 or blank pageSCI trust not established or user not replicatedVerify CDM-SCI connection; check user exists in SCI
Admin Center tiles missingUser not in correct NAMS groupAssign user to Administrator group in NAMS
Provisioning status stuck on "In Progress"Backend provisioning queue delayWait 3–5 hours; if still stuck, open SAP support case
Source System shows "Disconnected"Cloud Connector not running or destination misconfiguredRestart Cloud Connector; verify BTP destination
"Formation not found" errorSBN not linked to SAP Ariba Suite formationIn SAP for Me, go to Formations and include SBN system

Getting Support

If you encounter issues that cannot be resolved through the steps above:

  1. Go to SAP for Me→Services & Support→New Case.
  2. Select the provisioned tenant as the system.
  3. The component will be auto-filled based on the selected product.
  4. Describe the issue with specific error messages and screenshots.

SAP Help Resources

Summary

  • All three prerequisites (SCI, Foundation for SAP Business Suite, SAP Business Network) must show status Ready in SAP for Me before provisioning SAP Ariba Suite applications.
  • Always provision Test before Production for SAP Ariba Suite applications; the Development tenant type is only available for SAP Ariba Buying and SAP Ariba Invoicing.
  • No e-mail notification is sent when SAP Ariba Suite provisioning completes — the admin must check SAP for Me manually.
  • Post-provisioning steps are mandatory before the system is usable: verify tenant URLs, connect CDM to SCI, confirm admin access, configure Source System Management, and validate integration readiness.
  • For SAP S/4HANA Cloud Public Edition customers, the provisioning and integration path is different — no managed gateway add-on is required.