Recognizing the Standard Deployment Scope for SAP Ariba Strategic Sourcing Suite

Objective

After completing this lesson, you will be able to identify different personas

Understanding SAP Business Moule Sourcing and Contracts Scope

A Deployment Description provides a high-level overview of the Deployment Services, including set up and initial configuration of the Cloud Service in support of a single-system go live.

SAP Ariba offers supplemental services in addition to the baseline services, but the Deployment Description encompasses all of the basic, key configurations.

SAP Ariba Sourcing Scope

Once complete and accurate information is received from the Customer, SAP Ariba Shared Services will configure the test site with the provided customer-specific information, and will assist / support the respective activities for each:

  • Master Data and Site Customizations
    • Customer logo
    • Customization of predefined event message email templates
    • Site data as regions, departments, currency conversion rates and units of measure
    • Supplier/Bidder Agreement
    • Supplier common data
  • RFx Management
    • Enable out of the box reverse auction templates
    • Enable out of the box RFI templates
    • Enable out of the box RFP template
    • Enable out of the box forward auction templates

    SAP Ariba will review and configure a maximum of one (1) custom RFP template based on the out of the box Request for Proposal template that has:

    • A maximum of fifteen (15) lines of content (sections, questions, line items or lots)
  • Workflow - Full Sourcing Project Template

    SAP Ariba will create one (1) Sourcing Process template that has:

    • A maximum of fifty (50) tasks/phases in the process
    • A maximum of five (5) process configuration conditions
    • A maximum of ten (10) questions
    • A maximum of five (5) groups
    • A maximum of twenty (20) documents on document tab
    • The Ariba Best Practice Process template will be configured in the Customer site
  • Form Development

    One (1) form is included, meeting but not exceeding the specifications below:

    • A maximum of fifty (50) form header fields (line and header combined)
    • A maximum of ten (10) conditions (visibility, editability, and validity)
  • Document Management within Sourcing Library

    Upload a maximum of twenty (20) Document attachments to the process template or into the Sourcing Library

  • Custom Fields

    Build a maximum of five (5) custom header fields within the Sourcing Project class that can be used for searching and reporting.

    • This does not include modifications that are made to standard header fields within the same class.
  • Custom Report

    Review how to access and run prepackaged sourcing reports and provide guidance for creation of custom reports.

    • One (1) custom report included during deployment

SAP Ariba Contracts Scope

  • Master Data and Site Customization
    • Customer logo
    • Customization of predefined event message email templates
    • Site data such as regions, departments, currency conversion rates and units of measure
    • Electronic contracts and associated customer header field data
    • Workflow information, including tasks, documents and team members
    • Clauses for Clause Library and associated header field data
    • Conditions for clause usage
  • Process Configuration - Contract Workspace Template
    • Configure one (1) contract process template to Customer requirements (define phases, tasks; a maximum of thirty (30) tasks, a maximum of twenty (20) process configuration conditions, a maximum of ten (10) questions)
    • Load a maximum of ten (10) process-related documents
    • Set up team members and access controls for the template
    • Configure standard review/approval rules on the tasks in the template
  • Contract Loading (Repository)
    • Load a maximum of two hundred and fifty (250) contracts / five hundred (500) documents
      • Full load will only be made into the production site
      • A sample load will be done in the test site
    • Provide structured templates and explanation for bulk load of collected contract data
    • Provide guidance in gathering all soft copy contract documents to be uploaded into contract workspaces and completing the Contract repository data collection template
    • Review the Contract Repository template for completeness and format
  • Form Development

    One (1) form is included, meeting but not exceeding the specifications below:

    • A maximum of fifty (50) form header fields (line and header combined)
    • A maximum of ten (10) conditions (visibility, editability, and validity)
  • Main Agreement an Clause Library Set-up
    • Create one main agreement document in the template (limited to fifty (50) clauses per main agreement)
    • Create a maximum of ten (10) conditions for clause usage
    • Create a maximum of five (5) document properties that automatically populate content within the main agreement
    • Provide guidance for the collection and evaluation of legacy contract documents / clauses for inclusion in Clause Library
    • Configure and load a maximum of twenty (20) preferred and twenty (20) alternate clauses into the library from the main agreement document
    • Add descriptive information / instructional text for each clause if desired
    • Configure Clause Library approvals and notification settings
  • Custom Fields

    Build a maximum of ten (10) custom header fields within the Contract Request and Contract Workspace classes that can be used for searching and reporting.

    • This does not include modifications that are made to standard header fields within the same classes
  • Custom Report

    Review how to access and run prepackaged contracts reports, and provide guidance for creation of custom reports.

    • One (1) custom report included during deployment
  • Electronic Signature Configuration

    Customer must have a subscription with an SAP Ariba approved and supported Third Party Electronic Signature Provider for SAP Ariba to provide the services outlined:

    • Guide Customer on configuration of parameters for electronic signature functionality
    • Review options for signature task set-up
    • Provide a demo to the Customer showing the signature task workflow
    • Advise Customer on requirements for electronic signature functionality
    • Troubleshoot set-up as needed (on SAP Ariba side only)

Explaining SAP Business Moule Supplier Lifecycle and Performance Scope

SAP Ariba will configure the following limits across all templates and questionnaires:

  • A maximum of one hundred sixty (160) content questions
  • A maximum of thirty-five (35) tasks
  • A maximum of ten (10) conditions

The SAP Ariba Deployment Lead will enable templates in the site as outlined below within the configuration limits listed above:

  • Supplier Request
    • Enable and configure out of the box Supplier Request template
      • A maximum of one (1) survey
    • Enable and configure out of the box Self-Registration Request template
      • A maximum of one (1) survey
  • Supplier Registration
    • Enable and configure out of the box Supplier Registration template
      • A maximum of one (1) internal survey
      • A maximum of one (1) external survey
  • Supplier Configuration
    • Configure a maximum of one (1) process template
      • Configure a maximum of one (1) intake form
    • Configure a maximum of two (2) Modular Questionnaires (MQs)
  • Preferred Suppliers

    Enable and configure out of the box Preferred Suppliers template

SAP Business Moule Supplier Performance Management (SPM) Scope

SAP Ariba will work with the Customer during the deployment to define a Supplier Performance Management ("SPM") process and develop the Key Performance Indicators and KPI Measures that comprise the surveys and scorecards. The process, Key Performance Indicators and KPI Measures that are defined will be in accordance with the allowances for the deployment.

  • Ariba will configure the module with process, survey and scorecard templates defined by the Customer.
  • Ariba will configure a maximum of five (5) custom project header fields for searching and reporting on SPM projects.
  • SPM Process Workflow
    • Configure one (1) SPM Process template that has:
    • A maximum of thirty (30) phases/tasks in the process
    • A maximum of ten (10) documents included within the process
    • A maximum of five (5) questions and ten (10) conditions on the SPM process
  • SPM Survey

    Configure a maximum of three (3) surveys that contain a maximum of 25 total combined questions (i.e., a maximum of twenty-five (25) total questions) and place in the document library. (i.e., the twenty-five (25) questions can be included in one (1) survey or broken out across three (3) surveys)

  • SPM Scoreboard

    Configure a maximum of three (3) scorecards that contain a maximum of twenty-five (25) total combined Key Performance Indicators and KPI Measures, with the surveys and existing SAP Ariba Analysis reports as the data sources. (i.e., the twenty-five (25) combined KPI's and measures can all be included in one (1) scorecard or broken out across three (3) scorecards)

  • SPM Reporting

    SAP Ariba will enable available standard reports and provide guidance for custom reports in SPM

Great, so the Deployment Description expands on the scope of the deployment which is mentioned in the Project Kickoff and Deployment Overview presentations. Got it!

Log in to track your progress & complete quizzes