Outlining the Configuration Requirements

Objective

After completing this lesson, you will be able to describe the configuration requirements for Central Procurement

Fiori Apps for SAP S/4HANA Central Procurement

Configuration Expert - Business Process Configuration

  • Central Procurement Interface Monitor
  • Central Procurement Job Monitor
  • Central Procurement Operations Monitor
  • Default settings for users
  • Manage Workflows for Central Purchase Contracts
  • Manage Workflows for Centrally Managed Purchase Orders
  • Manage Workflows for Centrally Managed Purchase Requisitions
  • Monitor Compatibility of Central Procurement Operations
  • Schedule Import of Purchasing Documents
  • Schedule Import of Release Orders
  • Schedule Update of Price Details for Central Purchase Contracts
  • Schedule Output for Centrally Managed Purchase Orders
  • Schedule Output for Central Purchase Contracts

Employee - Procurement

  • Confirm Receipt of Goods
  • Create Purchase Requisitions
  • My Purchase Requisitions

Purchaser

  • Create Purchase Order Centrally
  • Create Purchase Orders from Central Quotations
  • Global Purchasing Spend
  • Manage Central Purchase Contracts
  • Manage Central RFQs
  • Manage Purchase Orders Centrally
  • Manage Purchase Requisitions Centrally
  • Manage Central Supplier Quotations
  • Mass Changes to Central Purchase Contracts
  • Monitor Central Purchase Contract Items
  • Monitor Mass Changes - Central Purchase Contracts
  • Monitor Purchase Requisition Items Centrally
  • Price History for Central Purchase Contract Items
  • Process Purchase Requisitions Centrally
  • Process Central Purchase Contracts
  • Schedule Automation of Business Processes
  • Manage Rules for Automation of Business Processes
  • Schedule Extraction of Purchase Orders for Central Procurement Analytics
  • Monitor Schedule Extraction of Purchase Orders for Central Procurement Analytics
  • Manage Team Hierarchies
  • Manage Teams and Responsibilities
  • Manage Situation Types - Extended
  • Monitor Situations
  • Manage Situation Types
  • Manage Situation Types - Message Based

Application User centric business roles:

Employee: SAP_BR_EMPLOYEE_PROCUREMENT

Central Purchaser: SAP_BR_CENTRAL_PURCHASER

Strategic Buyer (CP analytic apps): SAP_BR_BUYER

Application Admin centric business role:

Key User / Admin: SAP_BR_BPC_EXPERT

Exemplary view, most current list see Fiori Apps Library

Configuration Steps Overview

These steps are the main processes to get central procurement up. For detailed info, please investigate the setup guide for the scenarios, which can be found in the Process Navigator.

The graphic shows steps to configure Connectivity, Hub system, Backend and Unified Key Data Mapping for central procurement process.

Connectivity

Install integration components

  • 2491065 HUBERPI for ERP ECC Connected Backend
  • 2573672 HUBS4IC for S/4HANA OP Connected Backend

Setup RFC-Connections (SM59)

Screenshot of the Configurations of RFC Connections page.

Define locigal systems (BD54)

Screenshot of the Change View Logical Systems: Overview page.

Define connected systems

Screenshot of the Change View Connected Systems: Overview page.

Assign connected System to RFC-Connection

Screenshot of the Change View Hub System Connection for OP: Overview page.

Setup SOA-Services (SOA Manager)

Screenshot of the Web Service Configuration page.

Configure RFC-Connections for UI Integration (SM59)

Configuration Hub System

Activate Central Procurement Hub

Select Hub Activation from the Dialog Structure.

Activate Central Procurement scenarios relevant for your solution

Select the relevant scenarios for Procurement Hub.

Configure APIs (Control Plane)

Screenshot of the Change View API Control Plane for Bounded Context: Overview page.

Arrange DMS document type and number ranges to your needs

Screenshot of the Document Types Central Contract Change page.
Screenshot of the Edit Intervals: Purchasing document, Object EINKBELEG page.

Configure Backend System(s)

In the connected backend systems, you have to configure oData Services, so that the central hub system can consume them. Services are for example related to document transfer or status updates.

For scenario specific content: See configuration guide

Screenshot of the Service Catalog in the Activate and Maintain Services page.

Unified Key Mapping Service (UKMS)

In the complex landscape of central procurement, each connected system in the landscape have its own data management and governance. In the absence of such data management, there is no way for central purchaser to work with centralized master data. It gets more difficult with multiple business scenario and verity of master data objects.

With Unified Key Mapping Service for Central Procurement, Central Purchaser can process following central purchasing scenarios.

  • Ability to process Purchase Requisitions from various suppliers and materials across the connected systems.
  • Ability to process Purchase Orders from various suppliers and materials across the connected systems.

You can create, edit, or delete key mapping information for material by creating, editing, or deleting records in mapping groups. A mapping group specifies the key mapping data for object IDs that are mapped to each other. Each mapping group includes an object type, a business system, an object ID type, and an object ID. Each object instance can have one or more object IDs. There are mapping groups for:

  • Materials
  • Suppliers
  • Note Types in Purchase Requisition and Purchase Order (used to replicate texts in purchase requisitions and purchase orders from connected system to central procurement system)
  • DMS Document Types

For Supplier Data

Screenshot of the Key Mapping Supplier page.

More Info (or Check the 2XT Guide for Central Purchasing)

In case the customer does not have harmonized master data across his connected backend systems, then UKMS can be used in order to map master data values from CP hub to each connected backend.