0% found this document useful (0 votes)

105 views66 pages

Maintain Site Master FDD

Uploaded by

Sharmila Dutta

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

105 views66 pages

Maintain Site Master FDD

Uploaded by

Sharmila Dutta

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

Compass Group Doc No: BP310_OPS_9.1.

2 Maintain Site Master Data

Matrix Rev:
0.4 Page 1 of 66
Business Process Design
9.1.2 Maintain Site Master Data Modified: 30 June 2022

OPERATIONS

FSC1

FUNCTIONAL DESIGN DOCUMENT (FDD)

DOCUMENT NUMBER: 9.1.2 Maintain Site Master

Internal
1
Compass Group Doc No: BP310_OPS_9.1.2 Maintain Site Master Data
Matrix Rev:
0.4 Page 2 of 66
Business Process Design
9.1.2 Maintain Site Master Data Modified: 30 June 2022

Document Information
Project ID FSC1
Release Switzerland Deploy
Business Owner Andy Porter
Document Title 9.1.2 Maintain Site Master
Version 0.3
Date Created 16/08/2021
Author Suchit RaviChandra, Arnd von Minckwitz, Matt Leefe
Document Location Link to Sharepoint

Document Versions
Version Date Author Summary of Changes
V0.1 16/08/2021 Suchit RaviChandra Create
V0.2 27/10/2021 Arnd von Minckwitz Chapter 5 Detail Design
V0.3 22/04/2022 Matt Leefe Design Updates & Clarifications
V0.3 16/09/2022 Suchit R & Satheesh C Reference site details updated (POS type 3
added)

References
Document Type Document Name Document No. Location

SAP Enterprise [Link]

Structure Org sites/MatrixDrop2Review/_layouts/
Structure Switzerland 15/[Link]?sourcedoc=%7B38E2242C-
3D47-49A4-8AAC-
D14B660C6076%7D&file=Organisation
%20Structure%20Switzerland
%[Link]&action=edit&mobileredir
ect=true

List of BPD’s Covered in this Document

BPD Ref Document Name Comments

9.1.2 Maintain Site Master

Peer Reviewer

Name Role Signature Date

Internal
2
Compass Group Doc No: BP310_OPS_9.1.2 Maintain Site Master Data
Matrix Rev:
0.4 Page 3 of 66
Business Process Design
9.1.2 Maintain Site Master Data Modified: 30 June 2022

Operations WSL 25/01/2022

Jose Aguirre Jose Aguirre
(Work Stream Lead)

Document Reviewers

Name Role Signature Date

Heather Pascoe Compass Operations Solution Lead Heather Pascoe 06/05/2022

Rajiv 18/05/2022
Compass Operations SAP Consultant Rajiv Padmanabhan
Padmanabhan

Dinesh Compass Solution Architect – Dinesh Chowdhury 13/05/2022

Chowdhury Optional Reviewer

Document Approvers

Name Role Signature Date

Compass Operations Regional Process Andy Porter 02/02/2022

Andy Porter
Owner - Approver

Agreed-FDD lite

Name Role Signature Date

Anthony Roberts IBM Solution Architect

Compass Operations Solution

Heather Pascoe
Lead

Operations WSL (Work Stream

Jose Aguirre
Lead)

Andy Porter Operations RPO

Internal
3
Compass Group Doc No: BP310_OPS_9.1.2 Maintain Site Master Data
Matrix Rev:
0.4 Page 4 of 66
Business Process Design
9.1.2 Maintain Site Master Data Modified: 30 June 2022

Switzerland Local IT and

Daniel Ruegg
Business Lead

Marco Mathys CPO

Table of Contents

1. Document Overview..............................................................................................................
1.1 Purpose...............................................................................................................................
1.2 Scope (L3 Processes in Scope)...........................................................................................
Internal
4
Compass Group Doc No: BP310_OPS_9.1.2 Maintain Site Master Data
Matrix Rev:
0.4 Page 5 of 66
Business Process Design
9.1.2 Maintain Site Master Data Modified: 30 June 2022

1.3 Scope - Local exceptions – Switzerland.............................................................................

2. Requirements.........................................................................................................................
2.1 Core Business Requirements........................................................................................
2.2 Non-Functional Requirements (NFRs).........................................................................
2.3 Local Business Requirements (Switzerland)...............................................................
3. Key Design Decisions, Principles & Controls.................................................................
3.1 Key Design Decisions.....................................................................................................
3.2 Internal Controls.............................................................................................................
3.3 Assumptions & Dependencies.....................................................................................
3.4 Cross Functional Integration Topics...........................................................................
3.5 Risks & Issues................................................................................................................
4. Solution Design Overview...................................................................................................
4.1 Site (Unit) Create / Change / Display...............................................................................
4.2 Business Partner (Outlet) Create / Change / Display.......................................................
4.3 Site (Unit) and Business Partner (Outlet) Close...............................................................
4.4 Applications Included in Solution Design........................................................................
4.5 Local Design Considerations - Switzerland.....................................................................
5. Detail Solution Design.........................................................................................................
5.1 Architectural Description.................................................................................................
5.1.1 Solution Flow Design Core........................................................................................
5.1.2 Localisation Considerations - Switzerland................................................................
5.2 Front End Apps.................................................................................................................
5.2.1 Data Model Considerations.......................................................................................
5.2.2 API/Service & Schemes.............................................................................................
5.2.3 Screen Design / Flow.................................................................................................
5.2.4 Localisation Considerations – Switzerland................................................................
5.3 SAP Solution Design (Core Design)................................................................................
5.3.1 Core Detail Solution Design......................................................................................
5.3.2 Localisation Considerations - Switzerland................................................................
5.4 Integration Considerations ...............................................................................................
5.4.1 Core Design...............................................................................................................
5.4.2 Localisation Considerations - Switzerland................................................................
6. Master Data Requirements to Support Solution..................................................................
6.1 SAP Data Objects.............................................................................................................
6.2 Front End Apps Data Requirements.................................................................................
7. SAP RICEFW List...............................................................................................................
8. Open Design Topics.............................................................................................................
9. Key SAP Transactions / Fiori Tiles and Roles....................................................................

Internal
5
Compass Group Doc No: BP310_OPS_9.1.2 Maintain Site Master Data
Matrix Rev:
0.4 Page 6 of 66
Business Process Design
9.1.2 Maintain Site Master Data Modified: 30 June 2022

1. Document Overview
1.1 Purpose
This document provides the L3 processes build packages detailed information.

1.2 Scope (L3 Processes in Scope)

L3 Process: 9.1.2 Maintain Site Master Build Package

Build Package: 9.1.2 (1) Maintain Site Master Build Package

Scope Covered in the build package:

1. Create Unit
2. Create Outlet
3. Update Unit
4. Update Outlet
5. Close Unit
6. Close Outlet

1.3 Scope - Local exceptions – Switzerland

Please refer to the detailed sections that outline exceptions.

Internal
6
Compass Group Doc No: BP310_OPS_9.1.2 Maintain Site Master Data
Matrix Rev:
0.4 Page 7 of 66
Business Process Design
9.1.2 Maintain Site Master Data Modified: 30 June 2022

2. Requirements
A live Jira Dashboard of the latest version of the Matrix Business Requirements (both Functional &
Non-Functional) can be found at this link.

The latest version of the Requirements at the time this document was signed off have been inserted
into the document below in section 2.1 - 2.3.

2.1 Core Business Requirements

Release 1 (Switzerland)

Jira ID Summary Status

MTRX-774 Create and Update a Head Office Location and Approved
Departments
MTRX-772 Create and Update an Outlet Approved
MTRX-771 Create and Update a Unit Approved
MTRX-767 Create a Master Data Admin Pack Approved
MTRX-1575 Set & Update the Unit and Outlet Status Approved
MTRX-781 Report on Unit and Outlet Status Approved
MTRX-779 Close a Unit, Outlet or Head Office Location and Approved
Provide a Reason Code
MTRX-776 Report on Unit, Outlet or Head Office Approved
Setup/Amendments Prior to Approval
MTRX-773 Assign and Update Specific User Roles to an Outlet Approved
(Segregation of Duty - SOD)

Release 2 (Next Country Deployment)

Jira ID Summary Status

MTRX-1588 Approve Amendments to a Unit or Outlet Approved
MTRX-1585 Approve a Unit or Outlet Closure Approved
MTRX-780 Send a Confirmation that a Unit, Outlet or Head Office Approved
Location has been Closed
MTRX-778 Send a Confirmation that a New Unit, Outlet or Head Approved
Office Location has been Created or Amended
MTRX-777 Approve a Unit, Outlet or Head Office Location and Approved
Departments
MTRX-770 Retention of the Completed Master Data Administration Approved
Pack
MTRX-769 Master Data Workflow to Support Unit & Outlet Approved
Creation and Updates
MTRX-768 Populate a Master Data Admin Pack - Unit & Outlet Approved
Internal
7
Compass Group Doc No: BP310_OPS_9.1.2 Maintain Site Master Data
Matrix Rev:
0.4 Page 8 of 66
Business Process Design
9.1.2 Maintain Site Master Data Modified: 30 June 2022

Creation & Amendments

2.2 Non-Functional Requirements (NFRs)

At the time of writing no NFRs specific to this L3 identified.

2.3 Local Business Requirements (Switzerland)

At the time of writing no Local Business requirements specific to this L3 identified.

3. Key Design Decisions, Principles & Controls

3.1 Key Design Decisions

A list of the relevant Key Design Decisions (KDDs) relating to the current definition of the Level 3
process area are shown in the table below.

Note: The full list of KDDs can be found in JIRA via this Link.

MTX ID Description DA Outcome Approval

Date
Long time ago, DA decided to keep workflows out of the core scope (with an
exception for above country master data) and leave the in-country solution to
individual countries.

Many countries already have workflows in place (e.g. CH and DE). Not
having workflows or ending up with Excel templates would be a step
Workflows backwards for these countries.
16 June
MTX-19689 &
2021
Approvals RPO's are raising this KDD asking to bring workflows back in scope (as per
requirements in MTRX project). The Compass Core Business Team are
agnostic in relation to the workflow solution, not necessarily a specific system
workflow. What is needed is an efficient, transparent and reusable solution to
manage review and approval of (master) data, invoices and a few other
items.

Proposal is to assess the requirements during the CH workshops for every

potential workflow and approval steps what the best solution is. Use
system standards where possible (e.g. PO approvals) but consider other options
where more (cost) efficient and bring back to DA for decisions.

Note: Subsequently it was decided that Master Data related workflows (as per this
L3) would not be designed/built for Release 1 in Switzerland but would be
deferred until the next country deployment (R2). Instead, Switzerland should
Internal
8
Compass Group Doc No: BP310_OPS_9.1.2 Maintain Site Master Data
Matrix Rev:
0.4 Page 9 of 66
Business Process Design
9.1.2 Maintain Site Master Data Modified: 30 June 2022

focus on enhancing their current offsystem process to make it as efficient as

possible.
As an outcome of JIRA issue
MTX-1042, Head Office
(Company Code) will be setup as a Site.

Head Office There is no requirement for creating Intercompany Customer and Vendor 27
MTX-1095
Sites separately. This role will be fulfilled by the Head Office
Site both for FI only or non FI
(operational)

Following successful completion to the MAP Sales & Retention business process,
a new Site or Sites needs to be created, updated or re-opened in the system in
order to enable Site mobilisation.
Site Master
MTX-290 For Business loss, following the loss of a Client, an existing Client or Sites can be
Data Process closed down in the system in order to ensure a clean exit.

The Site Master is to be created directly in Production rather than the 14

development system, as this
is the process used in Compass India.

Above-country Matrix Strategy and Governance will be in place for Master Data
definition and ownership.
Organisation
MTX-318 23
Design Centralised co-located Master Data Team with cross-functional
input - at country level

3.2 Internal Controls

The latest version of the document describing which Key Financial Controls (KFC’s) relate to this
business process and the way how Matrix will be compliant is available via this Link

The Risk & Control Matrix for this process can be found in this Folder

3.3 Assumptions & Dependencies

The assumptions and dependencies related to this process are shown in the table below:

ID Assumption/Dependency Assumption/Dependency Detail

Description
Master Data Admin Pack is correctly prepared by Contract
MSM-D1 Master Data Admin Pack Administrator. Pack will contain all relevant details to start
setup of S/4 Site Master data and other related objects.
Internal
9
Compass Group Doc No: BP310_OPS_9.1.2 Maintain Site Master Data
Matrix Rev:
0.4 Page 10 of 66
Business Process Design
9.1.2 Maintain Site Master Data Modified: 30 June 2022

System users are correctly assigned to the business users

and user has adequate authorisation to complete the
MSM-A1 User Roles & Authorization manage Contract process end to end. The user has
adequate authorisation to complete the creation or updating
of a Site.
Reference Site per each Company is created by Project
Matrix Team (Functional team). It is a onetime activity and
MSM-A2 Reference Site
is available to be used for creation of Sites.
Relevant Migration Services are activated and functional.
SAP S/4 HANA (Production/Quality/Development) is
System Connectivity & SLT
MSM-A3 connected and the relevant job is setup to perform SAP
Replication
Landscape Transformation (SLT) Replication

Internal
10
Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 11 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

3.4 Cross Functional Integration Topics

The following integration topics apply for this business process:

Integration
ID Integration Topic Description Owner BPD Reference

2.2.1 Maintain Client Contract Master

MSM-I1 Client Contract Setup Operations
Data
9.1.5 Maintain Article Master Data &
MSM-I2 Extending Articles to Sites Operations
Selling Catalogue
9.1.5 Maintain Article Master Data &
Selling Catalogue
MSM-I3 Sales Pricing per Unit Operations
3.2.3 Pricing, Promotion and Discount
Management
Finance Master Data Maintenance for 9.1.1 Maintain Finance Master Data
MSM-I4 Profit Centre and Cost Centre for Finance
Sites.
4.2.1 Manage Vendor Article
MSM-I5 Vendor Sub-range assignment to Sites Procurement
Catalogue
Manage Vendor Article Catalogue 4.2.1 Manage Vendor Article
MSM-I6 maintenance for Site (procurement Procurement Catalogue
listing)
Above Unit Concept Management for 3.2.1 Above Unit Concept
MSM-I7 Operations
Assignment of Concept to Site Management & Central Menu Planning
Purchase Requisition and Ordering 4.3.1 Purchase Requisition and
MSM-I8 Procurement
from Site Ordering
4.1.3 Manage Procurement Reporting
MSM-I9 In-Unit Goods Receipt Management Operations
5.2.4 Goods and Service Receipt
MSM-I10 POS Inbound for Consumer Sales Operations 6.3.1 POS Inbound
POS Outbound for Site Specific Sales 6.3.2 POS Outbound
MSM-I11 Operations
Prices
MSM-I12 Manage In-Unit Inventory, stock take Operations 5.2.1 Inventory Management

Functional Design Document Internal 11

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 12 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

3.5 Risks & Issues

The Matrix Program risks and issues are mastered in Jira. The latest status of risks and issues is available
via this Link.

A list of the risks and issues related to this process, applicable at the time of writing of this document, is
shown in the table below:

Risks / Issue
Jira ID Description

As an action of MTX-290, the decision was made to create Site Master

& perform Configuration related assignment directly in production
environment similar to what Compass India currently does.
Create & Assign
• This is not a Best Practice to create Site in production
MTX-1389 Site in Production
directly
System directly
• This require opening of configurable fields in
production, which will also impact other business processes &
violation of Access & SOD
• Development & Quality Systems will not be in Sync
with production for Sites
• Risk of table Inconsistencies

Risk Mitigation: Usage of Reference Site to copy customizing and

usage of additional level of Access & SOD controls for changes in
production.
There are 1.6m possible Site name IDs available for usage across all
countries.

The allocation and consumption of these Site IDs for each country is an
Site ID name off-system data governance process to be managed centrally Above-
MTX-1571 allocation by Country. There is no way to control this process in standard system and
Country pre-Allocate a Site ID interval by Country.
If the data governance is not followed, the country runs the risk that
any ID can be used by any user in any other country. Issue
Mitigation: Data Governance

For Internal Control risks, Controls and Mitigations refer to section 3.2 Internal Controls.

Functional Design Document Internal 12

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 13 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

4. Solution Design Overview

L3 Process: 9.1.2 Maintain Site Master

- Reference Site:

A Reference Site will be created for each Distribution Chain (Sales Org + Distribution Channel) in the
country Switzerland. Master Data team will be the responsible team for the Reference Site creation
process. These Reference sites should also be created using input from multiple teams like
Procurement, Finance and Operations.

1. POS Type 1 Reference Sites for CH are:

 CBZZ Reference Site for CH10

 CBZY Reference Site for CH11

2. POS Type 1 Reference Sites for CH are:

 CBZW Reference Site for CH10

 CBZV Reference Site for CH11

- Master Data Admin Pack (MDAP) is the source of data, which notifies the SAP S4 system to Create
or Update (change and close) the Units (Site) and Outlets (Business Partner).

- Once the notification is received from the MDAP, based on the type of notification (Create or
Update), below processes will be started in the SAP S4 system.

Functional Design Document Internal 13

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 14 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

4.1 Site (Unit) Create / Change / Display

- The site master creation template (list of fields) is filled with the basic information from MDAP and
circulated between the cross streams like Finance, Operations and Procurement.

- Each team will update the field values in the site master creation template and once that activity is
completed by all the teams, the site master creation template is shared with the Master Data team.

- Master Data team uses the site master creation template and create the actual site in the SAP S4
system by choosing the right reference site (already created in the SAP S4 system) or change the
existing site in the SAP S4 system.

- Sites will be linked to Outlets through the Partner Function “ZO” in the “Site Customer – Sales” Role.

Note:
i. Master Data team might use the upload tool (Fiori app Mass Site Creation; transaction
ZWDA_OPS_E002_MASS_SITE) or manual creation process (transactions WB01 / WB02 and
BP) to create or change the Site and the relevant Site Business Partners in the SAP S4
system based on the number of sites to be created or changed.
ii. Site master creation template also carries the relevant fields of the site business partners.
iii. The Master Data Manager can display the Site Master and Site Business Partner using
transactions WB03 and BP to check that the site has been correctly set up before the Status
of the site master and BP site can be changed to active.
iv. The Master Data Manager can also review the data, status and set up of the site and related
outlets using the OPS_FSC_R_0118_Unit and Outlet status report. For more details, see
[Link]

4.2 Business Partner (Outlet) Create / Change / Display

- The outlet creation template (list of fields) is filled with the basic information from MDAP and
circulated between the cross streams like Finance, Operations and Procurement.

- Each team will update the fields in the outlet master creation template and once that activity is
completed by all the teams, the outlet master creation template is shared with the Master Data
team.

- Master Data team uses the outlet master creation template and create or change the outlet in the
SAP S4 system.

Note:
i. Master Data team might use the upload tool (Fiori app Mass Site Creation; transaction
ZWDA_OPS_E002_MASS_SITE) or manual creation process (transaction BP) to create or
change the Outlet in the SAP S4 system based on the number of outlets to be created or
changed.

Functional Design Document Internal 14

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 15 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

ii. The Master Data Manager can display the Outlet Business Partner using transaction BP to
check that the outlet has been correctly set up before the Status of the BP site (outlet) can
be changed to active.
iii. The Master Data Manager can also review the data, status and set up of the site and related
outlets using the OPS_FSC_R_0118_Unit and Outlet status report. For more details, see
[Link]

4.3 Site (Unit) and Business Partner (Outlet) Close

- Site closure checklist (list of Actions for each team like Finance, Operations and Procurement) is
filled with the required information from MDAP and circulated with all the teams.
- Site closure checklist is designed in such a way that, each team actions are sequenced. So that, the
site closure process is completed successfully.

Note:
i. Master Data Team or Operations Team should take the responsibility in monitoring the
checklist flow and the actions closure in both checklist and SAP S4 system. – Check with
business.
ii. For the detailed design of the Site closure flow in SAP S4, please refer to the SiteClose_SAP
Flow_V1.0 spreadsheet and the SiteCloseInSAP_Flow tab in green colour.

4.4 Applications Included in Solution Design

- SAP S4

4.5 Local Design Considerations - Switzerland

- CH (Switzerland) will transfer the existing legacy SAP ERP plants which are in scope for Migration
like A001 -> C001, means keeping the numerical part of the plant key from Legacy System in the
Unit (Site) code in S4HANA. The initial data migration of CH Units (sites) and Outlets will be
performed using the DATA_C_001_GL - Conversion RICEFW (ETL) - Master Data – Sites data load.

Functional Design Document Internal 15

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 16 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

5. Detail Solution Design

5.1 Architectural Description

5.1.1 Solution Flow Design Core

The Unit is created as a Site Master and a Site Business Partner in S4HANA. The Unit’s Outlet/s are created
as Outlet Business Partners and connected to the Site Business Partner using the Outlet (ZO) partner
function:

Then the Site Business Partner is connected to each Trading Client Business Partner that the Unit services
using the Unit (ZU) partner function. In the following example, the Trade Client is connected to the two
Units that service it:

Functional Design Document Internal 16

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 17 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

5.1.2 Localisation Considerations - Switzerland

Switzerland will use Site Master and BP sites / outlets.

5.2 Front End Apps

Not applicable

5.2.1 Data Model Considerations

Not Applicable

5.2.2 API/Service & Schemes

Not Applicable

5.2.3 Screen Design / Flow

Not Applicable

5.2.4 Localisation Considerations – Switzerland

Not Applicable

Functional Design Document Internal 17

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 18 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

5.3 SAP Solution Design (Core Design)

The site master will be created with Transaction WB01. During this, the BP for the site is created at the same
time (in principle Transaction BP relates to WB0x transactions and usage).

a. Main prerequisites are the creation of the Profit Center and Cost Center/s to represent the Unit and
Outlet/s respectively. For more details, refer to 9.1.1 Maintain Finance Master Data BPD and FDD.
b. After that, the known BP Outlets of a Unit should be created with their BP Roles Site so that the BP
Outlets can be connected later to the BP Unit. The relevant Cost Center will be assigned to each BP
Outlet.
c. After that, the Site Master and BP Unit for the BP Roles Site is created. It is possible to assign the
Outlets after creation of the Unit using Partner Function ZO (Outlet).
d. As the Unit is related to the Trade Client, the BP Trade Customer must be updated to assign the
Units that service this Trade Customer using Partner function ZU (Unit).
e. Real-time replication of the SAP S/4 site will take place automatically from SAP S/4 to SAP CAR
within the same environment via SLT (SAP Landscape Transformation).
f. Partner profiles for Inbound and Outbound are set up automatically in SAP S/4 whenever a new Site
is created. SAP copies the partner profiles from the Reference Site, provided these have been set
up by the IT team.
g. In SAP CAR (Customer Activity Repository), Inbound and Outbound partner profiles are set up by the
IT team for each new Site.
h. The partner profiles ensure that the newly created site has two-way communication from SAP S/4
to SAP CAR and POS, for outbound master data transfer and for inbound consumer sales and
payments. For more details, refer to 6.3.1 POS Inbound and 6.3.2 POS Outbound BPD and FDD.

Functional Design Document Internal 18

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 19 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

i. When a Unit or Outlet is created or changed in S4HANA, app specific Unit/Outlet master data
attributes are uploaded via spreadsheet into the REACT app database for use across all apps as
required. See section 7.2 Front End Apps Data Requirements for more details
j. In CH, BP Units (Sites) and BP Outlets are manually created in the POS system as part of the
organisational data set up in TC POS.
[Link]

Once set up, the Unit (Site) and Outlet master data is used by S4HANA transactions and REACT apps across
multiple Level 3 processes. See section 5.4 Integration Considerations for more details.

The following shows an example of the relationships between sites, profit centers, outlets, cost centers and
receiving delivery addresses:

BP Delivery
BP Outlet Address
assigned to assigned to
Compan BP Site via BP Outlet via
y BP Profit ZO partner ZD partner
Code Site Site Name Site Center BP Outlet Outlet Name Cost Center function function
80000001
4 142 Lightcube CH0C142000 800000014
80000001
800000014
5 14210 Mondelez Shop CH0C142100 800000015
142 80000001
CH10 C142 C142 CH0C142000
Lightcube 6 14220 Mondelez Coffee Points CH0C142200 800000016
80000001
7 14250 Allreal Restaurant Catering CH0C142500 800000017
800000017
80000001
8 14260 Allreal Coffee Points CH0C142600 800000018

In summary:

 The Unit (Site) Number (e.g., C142) is the middle 4 characters of the Profit Center (e.g.
CH0C142000). The Profit Center is not stored as a field on the Site Master or Site business partner.
However, the Unit Name can be used to store the site number on the Profit Center.

 The Cost Center (e.g., CH0C142600) is maintained on the Outlet business partner (e.g., 800000018)
in the FI Site Customer role in the Company Code data in the Destination Cost Center on the
Customer: Ctry-Spec Enh tab.

 The Outlet business partners are assigned to the Unit (Site) business partner using the Outlet (ZO)
partner function.

 The Receiving Delivery Address is assigned to the Outlet business partner using the Delivery Address
(ZD) partner function.

The technical S4HANA field mapping between profit centres / units (sites) and cost centres / outlets is
detailed in the Profit Center Unit Client Outlet Lookup document contained in
[Link]

Functional Design Document Internal 19

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 20 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

During the lifecycle of Units / Outlets the status will be updated manually by using Change Transactions
WB02 or BP.

Notes:
 Automatic status updates are not recommended for FSC1/CH due to the complexity and possibility
of running into status deadlocks across different process areas.
[Link]
 The initial data migration of CH Units (sites) and Outlets will be performed in each S4HANA
environment (e.g., Development, QA, Pre-Production and Production) using the DATA_C_001_GL -
Conversion RICEFW (ETL) - Master Data – Sites data load.
 Post go live, new sites and outlets will be created in each environment where the site master data is
required, either individually using transactions WB01 and BP or via mass upload using the Mass Site
Creation Fiori app transaction ZWDA_OPS_E002_MASS_SITE. CH are not planning to use the SAP
Site Distribution (DRFOUT) functionality to replicate site master data between environments.
 After go live, the master data team will create new sites directly in Production.
 Pre-production will be refreshed with data from Production on an agreed basis so any new Units
created directly in Production will be available for UAT purposes in Pre-Prod after the refresh.
 New sites will only need to be created in Development, Quality or Pre-Production systems on an
exception basis, if the site behaves differently to existing sites or the site is needed to test new
functionality.
[Link]

For details of the Level 4 processes, refer to Matrix 2021 - BPD 9.1.2 Maintain Site Master.

For the Process Step Tables including the roles, SAP transactions and Fiori apps, refer to 9.1.2 Maintain Site
Master (v4 Post Solutions Review) - role mapping.

Functional Design Document Internal 20

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 21 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

5.3.1 Core Detail Solution Design

Partner functions

Functional Design Document Internal 21

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 22 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

BP Roles
The BP Roles which must be maintained are shown in the box at bottom left hand side.

BP Grouping, Account Groups and Partner Procedure

A new BP Grouping/Account Group for outlets has been introduced to separate BP Outlets from Trade
Customer BP numbers: [Link]

Functional Design Document Internal 22

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 23 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

The following is considered.

 New BP Grouping for Outlets ZOUT is assigned a new internal number range.
X5: 080000000 – 0899999999
 New Account group for Outlets “ZOUT” as a copy of “ZCST” (similar for Vendor)
 Number Range X5 for SD Customer (KNA1) and MM Vendor (LFA1) – same definition as above for
new BP Grouping, but external, because they are using the assigned BP number in the background.
 Assignment of BP Grouping ZOUT to Account Group ZOUT
 Assignment of new Account Group to Partner Functions (especially ZO).

Fields in Scope for Transaction WB01 Create Site

When a site is created with Transaction WB01, at a certain point of the dialog (Button), Transaction BP is
called to create the Business Partner for the Site.

[Link] Site Master

Site number: This will be an externally assigned number entered manually by the user. The site number
range for the system is A to ZZZZ. Each country has its own series of site numbers allocated within the
system number range. Sites for CH Switzerland will use the C series from C000 to CBZZ.

Functional Design Document Internal 23

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 24 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

The site number is 4 characters long and is the same as the BP Site number for a Unit. Example C001.

All sites will have Customer/Finance and Vendor/Finance BP Roles.

There will be n Reference Sites set up for creation of sites with Reference, one per Organisation (Comp
Code -Sales Area). A reference site is a model site which will simplify the creation of a new site by copying
the data from the reference site to the new site at the time of creation.

There will be n Site (Plant) Profiles set up for use when creating site, one per Reference Site. The Site Profile
contains key attributes for site creation such as:
 Plant category
 Plant with Supplier
 BP Grouping
 Cust. acc. Group
 Supp. acc. Group
 BP Role Grouping
 Reference Site
 Copy Rule

As stated in the Swiss Enterprise Structure, Storage Locations are not being used by CH in S/4HANA so do
not need to be set up against Sites (Plants). This has been confirmed by Solution Architecture:
[Link]

[Link].1 Organisational Data and Calendar

 A site master will be assigned to:

o one of the Company Codes CH10 or CH11
o one Purchase Org CH01
o one of the Sales Areas CH10/00/01 or CH11/00/01 (following the Company Code above)
 Calendar
The Calendar for Switzerland will be CH.

Functional Design Document Internal 24

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 25 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

There will be no head office or operational sites for company code CH12 on the basis that there is no
purchasing or billing carried out by this legal entity. It will be represented by a standalone inter-
company business partner.
[Link]
[Link]

[Link].3 Listing/Material Planning

 Listing
o Listing Conditions for Assortments
o Ticked
o Subsequent Listing Indicator
o Defaulted to 1
o Listing Procedure
o In S4HANA, the listing procedure can be defaulted from the assortment, article or site
o The Listing Procedure is not used at the Site Master level by CH. The Managed Order
Guide (MOG) Workbench and Selling Catalogue functionality do not use the Site Listing
Procedure in the listing of procurement or sales articles respectively.
[Link]
o Listing Basic Rule

Functional Design Document Internal 25

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 26 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

o This defines the basic rule for how retail assortments are checked by S4HANA in SD
documents (sales orders, deliveries). Not used by CH sites as SAP SD sales orders and
deliveries are not in scope.

[Link].4 Purchasing/Distribution
Not used.

[Link].5 POS

 POS Outbound Profile.

Term that groups together the parameters for POS outbound processing in profiles
CH will use profile “CH01”.
 POS Inbound Profile
Term grouping together several parameters for the internal interfaces into profiles.
CH will use profile “CH01”
 POS Currency
Currency in which the POS systems of a plant manage their sales data.
CH will use Swiss Francs (CHF).
 Assort. List Profile
o The Assortment List Profile should be added to the Site when it is ready to receive master
data information (i.e., when it is about to go-live in Production).
o CH will use profile CH01 for POS Type 1 sites and profile CH02 for POS Type 3 sites. POS
Type 2 and Mixed POS sites are not being used by CH. The Assortment List Profile is not
maintained for No POS sites.
[Link]
[Link]

Functional Design Document Internal 26

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 27 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

[Link].6 Layout/Blocks

[Link].6.1 Layout data:

Not used.

[Link].6.2 Block:

[Link]
 Blocking Reasons
 01 SAP Standard – not used
 ZC Closed and ZF Future Store are blocks used by France but not by FSC1
 The following Blocking Reason Codes and status combinations will be used by CH: The
descriptions of Order and Billing Blocks follow the Blocking Reason Codes
Blocking Reason Code Order Block Billing Block POS Outbound
Z1 DRAFT|| Order block Z1|| Billing Block Z1|| Block POS Outbound
blank
Z2 ACTIVE: || Order Block Z2|| Billing Block Z2|| Block OS Outbound
blank
Z5 SERVICE Order block Z5|| Billing Block Z5|| Block POS Outbound
DISCONTINUED: || blank
Z6 CLOSED: || Order block Z6|| Billing Block Z6|| Block POS Outbound
flagged
 Block from
The date from which the block is to be valid.
 Block to
The date to which the block is to be valid.
It is only possible to set one Reason code. If a block should be valid in the future, the Reason code
for today would be “Blank”. Blank will be handled like CLOSED. Recommendation: The Block From
and To dates should only be maintained when setting the Blocking Reason to Closed, as Purchase
Orders cannot be raised with delivery dates after the Block From date.
[Link]
[Link]

Functional Design Document Internal 27

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 28 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

In addition, the Block From and To Dates should only be populated when the Blocking Reason is set
to Closed, as the site cannot be assigned to an Assortment otherwise:
[Link]

[Link].7 Functions behind the Buttons:

 Material Groups
Material Groups will not be used here.
 Listed Articles
o This area is maintained via WSM3 “Mass Listing” and the listed articles are displayed at this
place.
o Dummy Site CBZX is used to control the Listing of Swiss Articles for the TCPOS system
 Assigned Assortments
Procurement don’t use it; Ops don’t use it.
 Opening Hours
Procurement don’t use it. No OPS Business Requirement

For Information: No classification is in scope for Site Master (Confirmed by PRC and OPS). Classifications are
used with BP Site Vendors. See below for details.

BP Site (both Units and Outlets) Fields

 BP site for a Unit
o The BP for a Unit is created out of the Site Master.
o Vendor and Customer related data are maintained.
 BP site for an Outlet
o There will be an BP site for outlet in the case there is only 1 Outlet in this Unit.

[Link] BP Role General

 BP site Number for a Unit or an Outlet – the number range will be pre-configured
o Unit (external number range): A – ZZZZ
o Outlets (internal number range) 0800000000 0899999999
 BP Grouping – The Grouping is pre-configured; this will allow system to pick up the correct Number
Range for Sites/Outlets as described above under BP site Number.
o Units: ZSIT
o Outlets: ZOUT

[Link].1 Address
All kind of BP Site must have mandatory address data: Name, Street, House number, Country, (Region),
Communication Language.
The following fields for Name and Search Term are discussed in
[Link]
As there is no global governance on that so far, this should become the CORE Rule too.

Functional Design Document Internal 28

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 29 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

 Name
The NAME1 Field should be maintained in a way, that every BP can be identified. NAME1 of the address
from BP outlet / BP Unit should follow the description of Profit Center / Cost Center - but without the
key information (e.g., …C142…) - to have a proper name in the address. So, Profit Center / Cost Center
must contain a meaningful and usable wording in name for identification within Compass Organisation
which is then used in BPs too and fulfil the needs in OPS.

 Search Terms
The Search Terms should be maintained in a way, that the Site Number is included, and all Outlets of a
Unit can be selected with Wildcard “*”. should follow the last digits of the Cost Center and should be
populated per definition always in Search Term1.
C142 Unit
C142000 Outlet 1
C142110 Outlet 2
In this case C142* would list all BP Sites. Using only the number without leading character might lead to
a conflict with other countries. So, it should be unique.

In Summary - Search Term 1 will contain Site Number (middle part of Profit Center e.g., CH0C142000)
for BP units or last 7 digits of Cost Center (e.g., CH0C142000 or CH0C142100) for BP outlets, because
these will be unique and standardized expressions across the Compass organisation.

C142 → BP Number C142 = Unit

C142000 → BP Number 800000014 = Outlet 1 of C142

C142001 → BP Number 800000015 = Outlet 2 of C142

Note: Print programs will have their specific logic to handle required addresses. The program can
consider addresses in Customizing on Company Code (->legal Entity) or Sales Area (->Seller) or in case of
unit/outlet the BP (-> delivery address for a PO, sender-receiver address in stock transfer, provider of
the service to a client maybe in quote/order or billing).
 Address and Communication – the below fields will be used to define address and communication
method for a client:
o Postal Code
o City
o Street / House number
o Country
o Region (optional)
o Language – The language is used for communication.
o Email/Fax/Telephone can be maintained for BP site
Note: The BP Site email address should be populated on all POS Type 3 (non-connected) sites so
that S4HANA master data such as articles and pricing can be emailed in readable format (e.g.
OP_FSC_R_024 - POS Outbound - Output Pricing information in Human readable form for POS type
3)

Functional Design Document Internal 29

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 30 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

[Link].2 Identification
Even though this tab is displayed for BP Role General, Site Customer and Site FI Customer, the BP Role
General shows all the fields used by Matrix.

[Link].2.1 Organisational Data

Not used.

[Link].2.2 Industries
Not used by Finance / Procurement.

[Link].2.3 Identification Numbers

 External BP Number (optional, text field)
For Swiss BP Outlets loaded at data migration, it will contain the legacy cost center.

 Identification Number
The Global Location Number (GLN) for BP sites (Units and Outlets) will be entered in the Identification
Number for the ID Type of BUP005. The GLN is printed on the CH Purchase Order, if entered.

[Link].2.4 Tax Numbers

Not used. In CH, Units (Sites) or Outlets do not have their own UID or Tax numbers.
[Link]

[Link].2.5 Trade Compliance

Not used

[Link].3 Status
Not used. Status will be on org dependent levels. Might become relevant when Archiving of Data into a
System Archive will be done. Please refer to Status section within Sales Area Data below for how BP Site and
Outlet statuses are managed. Please refer to Blocks section above for how Site Master statuses are
managed.

[Link] BP Role Site FI Customer

Functional Design Document Internal 30

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 31 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

[Link].1 Control
Even this tab is shown for BP Role General, Site Customer and Site FI Customer, the BP Role Site FI Customer
shows at least all fields.

[Link].1.1 Control Parameters

 Authorisation Group (Business Partner General)
The Authorisation Group at the Business Partner general level can be used to control which countries
can access which business partner general data (i.e., restricting S/4 users to creating, changing or seeing
only their country’s BPs). CH01 is available to assign to Swiss Site and Outlet BPs.
[Link]

 Trading Partner Number

Used by Finance (Intercompany). Trading Partners are assigned to Head Office Site BPs and
intercompany business partners only. It is not required to assign Trading Partners to each
operational site BP. The following have been defined for CH. Note: There are additional Company
IDs for legal entities in other countries:
Company ID Name Country Currency
CH10 Compass Group (Schweiz) AG CH CHF
CH11 Restorama AG CH CHF
CH12 Creative New Food Dream Steam CH CHF
[Link]
[Link]

[Link].1.2 Data Origin

Not used

[Link].1.3 Notes
Not used

Functional Design Document Internal 31

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 32 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

[Link].2 Payment Transactions

Even this tab is shown for BP Role General, Site Customer and Site FI Customer, the BP Role Site FI Customer
shows at least all fields.

[Link].2.1 Bank Details

No Bank Details for BP site for Unit and BP site for Outlets.

[Link].2.2 Payment Cards

No payment cards information will be maintained.

[Link].3 Status

[Link].3.1 Archiving Flag

This Flag is used to control technically, that this BP is valid for Archiving to an Archive System. If
Archiving Program identifies that it is fine to archive, then BP Data will be removed from Database
into the Archive Database -> later

[Link].3.2 Lock
 Central Block
Blocks Finance Functions for whole BP.
 Not Released
If ticked, SAP displays a warning message in BP Transaction. As Compass use Status ’DRAFT’ in Sales
Area Data which are planned to be checked in OPS Processes, this could be used as information for
the Data Maintainer that the site /outlet business partner set up hasn’t been finalized.

[Link].4 Credit Profile

This tab is shown only for BP Role Site FI Customer.
 Risk Class
Will be used, but only for information. There is no Credit Check Functionality in the transactions.

[Link].5 Legal Data

This tab shown the same fields for BP Roles Site Customer and Site FI Customer.
Not used

[Link].6 Company Code related Data for Site Customer

[Link].1.1 Company Code

 Company Code (mandatory, value field)
o CH10/CH11 to access company code specific data.

[Link].7 Customer: Account Management

 Reconciliation Account (mandatory, value field)
16800000 Intercompany Rbles Current Account (CH legacy account 12000)
 Sort Key

Functional Design Document Internal 32

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 33 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

Used by Finance.
 Authorisation Group (Company Code Data)
Not used at this level
[Link]
Note: As COMPASS will use a single S/4HANA System, at least sales area, company code and purchasing
org data access should be restricted across different Compass organisations.
Note: See Authorisation Group (Business Partner General) in Control view for additional restriction
possibilities.

 Previous Account Number (optional, text field)

o For Swiss BP Units loaded at data migration, it will contain the legacy system plant code. For
Swiss BP Outlets loaded at data migration, it will contain the legacy system cost center.

[Link].8 Customer: Payment Transactions

[Link].8.1 Payment Data

[Link].8.2 Automatic Payment Transactions

 Payment Method
Not used for BP Sites. Payment method is optional for customers. Payment method is for use with the
payment program so is primarily for use with vendors.
[Link]
[Link]
 House bank
Not used
 Payment Block

[Link].8.3 Additional Company Code Data

Not used

[Link].8.4 Payment Advice Notice

Not used

Functional Design Document Internal 33

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 34 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

[Link].9 Customer: Correspondence

[Link].9.1 Dunning Data

 Dunning Procedure
Dunning is not relevant for Site or Outlet BPs. Only used with Trade or 3rd Party Clients.
[Link]

[Link].9.2 Correspondence
Not used

[Link].9.3 Payment Notices

Not used

[Link].10 Customer: Insurance

Not used

[Link].11 Customer: Status

[Link].11.1 Posting Block

 Selected Company Code.
As there is 1:1 Relation of Site customer to Company Code this flag has the same effect as “All
Company Codes”

[Link].11.2 Deletion Blocks

These fields are related to physical Data Archiving – not in scope.

[Link].12 Customer: Withholding Tax

[Link].12.1 Withholding Tax Types

[Link].13 Customer: Texts

CH doesn’t have any company code related texts.
Later Release.

[Link].14 Customer: Ctry-Spec. Enhancement

 Destination Cost Center
o In case of a BP site for an Outlet, the Cost Centre which belongs to that Outlet must be entered.
o Note: The Cost Centre is optional because it is not required for the BP site for a Unit.
 Collective Procedure
o Collective Procedure (Top de Procedure Collective) is a reporting field that will be sent through
an interface from an external system Ellisphere for BP Customers in France.
o Not used by CH BP Sites or Customers
[Link]

Functional Design Document Internal 34

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 35 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

[Link] BP Role Site Customer

[Link].1 Customer: General Data

Even this tab is shown for BP Roles Site Customer and Site FI Customer, the BP Role Site Customer shows at
least all fields.

[Link].1.1 General Data

 Vendor Number
In case the Vendor is extended as a customer, this field must be populated with the BP Number, which
is the Number of the Vendor too. After saving, the data of the BP Vendor is updated with the Customer
number automatically.

[Link].2 Customer: Tax Data

Even this tab is shown for BP Roles Site Customer and Site FI Customer, the BP Role Site Customer shows at
least all fields.

[Link].3 Customer: Additional Data

[Link].3.1 Attributes

Functional Design Document Internal 35

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 36 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

The General Attributes are only available in BP sites.

 General Attribute 1 - Band

Not used in FSC1 by Operations
Note: Procurement uses “Group Key” to represent the Band for pricing purposes

 General Attribute 2 – POS Type

o Will be used on units as POS data is not sent to POS at outlet level in CH.
o The following values will be available:

T1 Type 1 Connected
T2 Type 2 Partially Con
T3 Type 3 Non-Connected
Z1 Mixed POS
Z2 No POS
SAP Standard entries are removed.

Functional Design Document Internal 36

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 37 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

 General Attribute 3 – Inventory Model:

France is using None (NO). Not used by FSC1.
Inventory management/consumption/ yield management model:
o MN Minimum
o NO None
o TG Target
[Link]

 General Attribute 4 - Site Type:

Not used for FSC1 – covered in Profit Centre and Cost Centre Data
FR uses HO
o BT HO & Operational
o CK Central Kitchen
o HO Head Office used by France (Benjamin L)
o OP Operational
[Link]

 General Attribute 5 - Go Live

Not used by FSC1.
o Not Live
o Live
[Link]

 General Attribute 6: Unit/Outlet Closing Reason

o This Attribute is set at the time when Status “Service Discontinued” is maintained in the Order
Block and Billing Block fields on the Site or Outlet BP.
o The following values will be available and used for Units and Outlets

ZC1 Cntr Lost/Terminated

ZC2 Closure of Service
ZC3 Closure of Site
ZC4 Closure Site/Outlet
ZC5 Closure/Re-opening
Note as additional information:
o Contract Lost/Terminated → as per CRM
o Closure of Service → as per CRM
o Closure of Site → as per CRM
o Closure of Site/Outlet → initiated by Compass e.g., Loss making unit or outlet
o Closure/Re-opening → as a result of a change of Legal Entity or key Reporting Attribute or
vacating one

SAP Standard entries are removed.

Functional Design Document Internal 37

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 38 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

[Link]

 General Attribute 7: Unit/Outlet Stock Ownership

The Ownership of Stock will be held in Field General Attribute 7 of BP. The field becomes optional
for Role BP Site Customer. It is used for Units and Outlets for reporting and by the Stock Count app
to generate finance postings for stock counts but only for Compass owned stock. The following
values are available.

Value Description
001 Compass owned Stock
002 Client owned Stock
SAP Standard entries are removed.
[Link]
[Link]

 General Attribute 8 – Outlet Size

o Populated for outlets and used in reporting:
Value Description
001 Small
002 Medium
003 Large
o [Link]
o [Link]
o [Link]

[Link].4 Customer: Unloading Points

Even this tab is shown for BP Roles Site Customer and Site FI Customer, the BP Role Site Customer shows at
least all fields.

Not used as we don’t use SAP SD deliveries.

[Link].5 Customer: General Texts

This tab shown the same texts for BP Roles Site Customer and Site FI Customer.

There are no texts to be migrated from CH and no requirement to have specific texts in BP site.
Later Release.

[Link].6 Transport Data

This tab is only shown for BP Roles Site Customer.

Functional Design Document Internal 38

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 39 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

Not used, as FSC1 does not use Logistic Functionality in SAP.

[Link].7 Sales Area related Data

[Link].7.1 Sales Area

The below fields will be used to choose the Sales Area for a Unit/Outlet to access Sales Area specific data:
 Sales Organization: for CH -> CH10/CH11 (value field)
 Distribution Channel: 00 (value field)
 Division: 01 (value field)

[Link].8 Orders
 Currency (mandatory field, value field)
This will be a value field. Usually, the local currency is selected. The currency is used in transactional
data.
 Price Group
o The Price group contains the Format/Concept. It can be used to set up article Sales Prices at
the Format/Concept level on either units or outlets. There are two accesses to maintain the
sales price at the Format level:
 Article / Price Group --> applies at Unit (Site) Price Group level
 Article / Plant / Outlet / Price Group --> applies at Outlet Price Group level
For CH in Release 1, Format (Price Group) level prices are not required:
[Link]
o CH are not planning to use Format level price functionality at go live but may use it in the
future: [Link]
o The following Price Group values are available. (SAP Standard Entries are removed)

01 Smartfridge
02 Smarthub
03 Smart&fresh
04 Starbucks
05 Dallucci
06 Mix&Match
07 Pot&Spoon

 Sales Price List

o Sales Price List defines the Sector, Subsector or Geographical area from a sales pricing
perspective. It can be used to set up article Sales Prices at the Sector, Subsector or
Geographic levels.
o All Units need to have a sector, sub-sector or geographical recommended sales price list
assigned

Functional Design Document Internal 39

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 40 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

o The outlet will always carry the same sector/subsector as the related Unit.
o The following Sectors and Subsectors will be available for CH:

B1 Business & Industry

E1 Education
H1 Healthcare & Seniors
CA Business 1
CB Business 2
CC Industry 1
CD Schools & Nurseries 1
CE Schools & Nurseries 2
CF Higher Education 1
CG Higher Education 2
CH Healthcare 2
[Link]
[Link]

[Link].9 Deliveries
Not used

[Link].10 Billing
 Payment Terms (value field)
The Payment Terms are maintained in 2 areas: Company Code data and Sales Area Data.
The values within the BP Customer should be the same.
The payment terms for customers provided by Business can be found here:
[Link]
 Account Assignment Category (value field)
This field is used to determine Revenue Accounts during POS Billing of the Site. Not required for
Outlets. The following settings will be used:
 Z1: Compass Traded - for units where Compass trade on the own and Compass retain consumer
payments received
 Z2: Non-Compass Traded - for units where Compass trade on behalf of the client and the client
retains consumer payments received
[Link]
[Link]
[Link]
[Link]
 Tax Determination (mandatory field)

Functional Design Document Internal 40

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 41 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

The tax related fields in the Sales Area data are used for Tax determination. Based on the definition
of the tax classification for the BP customer, tax condition records can be set up as master data.
The following tax classifications for BP site are valid:
 1 = Taxable (used for BP Customer/ BP sites) x% normal tax rate (CH 7.7%)
 2 = Reduced tax (not maintained in BP Sites, but may be populated in tax conditions / POS
Inbound / Billing for “take away”) (CH 2.5%)
 3 = Special (used for BP sites/outlets for “Hotels and room service” → (CH 3.7%), 2 Swiss
Units)
 Note: 0 = Tax Exempt is only used with Trade or 3rd Party Clients. Not used by Unit and
Outlet BPs.
Country and Tax Category are defaulted by the System.
[Link]

[Link].11 Partner Functions

SAP terminology Partner Functions (described above under Partner Functions)
The main and mandatory partner Functions SP sold-to, SH ship-to, PY payer, BP bill-to are required by SAP.
They are automatically defaulted with the BP number.
 The BP site for a Unit will have additionally Partner Functions to link Outlets which belongs to the
Unit.
o Partner Function ZO Outlets is used to assign the BP Outlet to a BP Unit.
o There are 1-n Outlets possible. At minimum, 1 Outlet must be assigned.
Note: The system doesn’t complain if no Outlet is assigned to a BP Unit as there is a single
partner determination procedure for Units, Outlets, Trade and 3rd Party Clients.

Functional Design Document Internal 41

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 42 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

 The BP site for an Outlet will not have additional partner functions.

Functional Design Document Internal 42

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 43 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

[Link].12 Additional Data

[Link].12.1 Customer Groups

Customer groups are available for BP trade customers and BP site customers.

Functional Design Document Internal 43

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 44 of 66

Functional Design Document Internal 44

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 45 of 66

[Link].13 Status
 Sales Block
The following Blocks will be used to manage the Status of a BP site for both Units and Outlets. For
Units it should be in sync with the Site Master’s Blocking Reason Code.
o Order Block for selected Sales Area

Functional Design Document Internal 45

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 46 of 66

[Link].14 Customer: Texts

CH doesn’t have any sales related texts which can be migrated. There is no requirement for texts at this
place.
Later Release.

[Link].15 Documents
Not Applicable

[Link].16 Additional Data (2)

Not used, as Compass don’t use Logistic Functionality in SAP.

[Link].17 Transport Data

Not used, as Compass don’t use Logistic Functionality in SAP.

[Link] BP Role Site FI Vendor

[Link].1 Vendor: General Data

Not Applicable

[Link].2 Vendor: Tax Data

As the BP Roles for Site FI Vendor and Site Vendor shown different but not all content, Vendor: Tax Data
shows up here and in BP Role Site Vendor too.

[Link].3 Vendor: Texts

Not Applicable

[Link].4 Company Code related Data for Site Vendor

[Link].4.1 Company Code

 Company Code (mandatory, value field)
o CH10/CH11 to access company code specific data.

Functional Design Document Internal 46

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 47 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

[Link].5 Vendor: Account Management

 Reconciliation Account (mandatory, value field)
o 21800000 Intercompany Payables Current Account

[Link].6 Vendor: Payment Transaction

 Payment Terms (mandatory, value field)
There are 4 mandatory fields for Payment terms in the following areas of BP site data. Vendor
Procurement, Vendor Finance, Customer Sales, Customer Finance. Within Vendor or Customer, the
payment terms should be the same.
o Note that payment terms entered on a Site/Outlet vendor at the company code level will need
to be approved using the Confirm Critical Vendor Changes transaction codes FK08/FK09. This is
an audit requirement that changes to sensitive fields on the BP vendor (as well as the creation
of a new vendor) must be released by an approver in the Finance area.
 Check Double Invoice
o flagged
 Payment Methods
o Not applicable as a Site will not be paid as a vendor

[Link].7 Vendor: Correspondence

Not used

[Link].8 Vendor: Status

Not Applicable

[Link].9 Vendor: Withholding Tax

Not used

[Link].10 Vendor: Texts (purchase Org specific)

Not used

[Link].11 Vendor: Country-Spec. (Enhancement)

Not used

[Link] BP Role Site Vendor

[Link].1 Vendor: General Data

 Group Key
Price Band for Purchasing price determination for Site Vendors only. For CH sites, the band represents a
pre-defined group of sites within a country (in format Bxx, e.g., B01, B02, …) and will be maintained in
the Group Key, which is an essential parameter to drive the correct purchase price determination during
the procurement ordering process. Not applicable for CH Outlet Vendors or for French Site Vendors. See

Functional Design Document Internal 47

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 48 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

4.2.3 Manage Purchase Pricing FDD for more details. [Link]

30081

[Link].2 Vendor: Tax Data

As the BP Roles for Site FI Vendor and Site Vendor shown different but not all content, Vendor: Tax Data
shows up here and in BP Role Site FI Vendor.
- Not used

[Link].3 Procurement Monitoring

Not used

[Link].4 Vendor: Texts

From CH there are no texts to migrate.

[Link].5 Classification
The BP site for Vendors will have Classification Data that can be accessed via More > Extras > Classification.
For Classification maintenance, transaction code CL20N can be used as well.

There will be one global Class and each Country will have additionally one local Class. Both must be
maintained.

Global class: Z_VENDOR_GLOBAL

Local class: Z_VENDOR_LOCAL_CH Class type: 010

The following characteristics are valid for a site Vendor.

 Vendor-Compliance Type
 Sector
 Subsector

Functional Design Document Internal 48

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 49 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

Notes:

 The possible list of values available for the Sector and Sub-Sector characteristics will be maintained
in a custom table ZTOTC_SEC_SUBSEC using transaction code ZOTC_ASORTMENTS_01, rather than
as a list of characteristic values. This is because the list of values is shared across Site Vendors, BP
Vendors, Profit Centers and the Procurement MOG Workbench (See WRICEF ID OPS_FSC_E_0034 -
Operational sector & sub-sector table for more information).
 Assign Approved Vendor to Unit. The characteristic values on the vendor business partner and site
business partner will be compared. If the values match, those vendors will be listed in a dynamic
view along with any other previous status maintained in the status table for the respective vendor
and site. Thus, an Approved Vendor List (AVL) for each Unit is generated (See WRICEF ID
PRO_FSC_E_0085 - Approved Vendor List (AVL) and the 9.1.3 Maintain Business Partner - Vendor
FDD for more information).

Functional Design Document Internal 49

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 50 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

[Link].6 Purchasing related Data

General Note: Only mandatory fields are populated. No further fields required so far by Procurement.

[Link].6.1 Purchasing Organisation

 Purchase Organisation: For CH the Purchase Organisation CH01 is available.

[Link].7 Purchasing Data

 Order Currency (mandatory, value field)
 Payment Terms (mandatory, value field)
FIN provides Payment Terms and Mapping

[Link].8 Partner Functions (Vendor)

There are 3 Partner Functions defaulted by the System Standard: VN Vendor, OA Ordering Address, PI
Invoicing Party. In addition, Partner Function ZD is used to store the Receiving Delivery Address for each
Outlet BP.

Different Outlets within a Unit may be assigned with a common Outlet to represent the ZD Receiving
Delivery Address. The ZD partner functions will be available in the front-end Ordering App so that the
appropriate ZD Receiving Delivery Address can be assigned to the Purchase Order and printed on the PO
form.

The following example shows how this assignment might be set up:

BP
Delivery
BP Outlet Address
assigned assigned to
to BP Site BP Outlet
via ZO via ZD
Company BP Profit Cost partner partner
Code Site Site Name Site Center BP Outlet Outlet Name Center function function
800000014 142 Lightcube CH0C142000 800000014

800000015 14210 Mondelez Shop CH0C142100 800000015 800000014

142
CH10 C142 C142 CH0C142000 800000016 14220 Mondelez Coffee Points CH0C142200 800000016
Lightcube
14250 Allreal Restaurant
800000017 Catering CH0C142500 800000017 800000017
800000018 14260 Allreal Coffee Points CH0C142600 800000018

For some Outlets in CH, an additional ZD Delivery Address is required which is different from any of the
Unit’s Outlet addresses. In this case, then the Delivery Address will be created as an Outlet business partner
using the BP Grouping ZOUT. But it will only be extended to the ZSTVN1 Site Vendor BP role so that it can
be assigned as a ZD Delivery Address to the relevant Outlet BP vendors.

ZD Delivery Addresses are assigned at the Outlet BP level within the Site Vendor BP role:

Functional Design Document Internal 50

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 51 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

[Link]

[Link].9 Additional Purchasing Data

Not used

[Link].10 Supplier: Retail Attributes

Not used

[Link].11 Interchangeability
Not used

[Link].12 Vendor: Texts

From CH there are no texts to migrate.

[Link].13 Supply Region

Not used

[Link] BP Role BP Retail site

This BP Role ZSTBUP is created automatically by the System when the BPs for a Unit are created.
No input required.

Functional Design Document Internal 51

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 52 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

[Link] BP Role Collection Management

Not used. Collection Management is not relevant for Site or Outlet business partners. It is only used with
Trade Clients.
[Link]

Update a Unit (WB02/BP)

The Update (Change) of Site Master or BP sites are dealing with the same fields.
Mainly two areas are in scope for changes:
 Blocking Reason, Order Block, Delivery Block and Unit/Outlet Closing Reason if the status of a Unit
or Outlet has changed
 Assigning an additional Outlet Partner Function (ZO) to add a new Outlet to a BP Site.

Further Notes:
 There are no BP Relationships to be built.
 There are no Contact Persons so far planned for sites or outlets.

5.3.2 Localisation Considerations - Switzerland

Swiss Enterprise Structure objects start with “CH” or “C”

Swiss transfers the existing plants which are in scope for Migration like A001 -> C001, means keeping the
numerical part of the plant key from Legacy System.

[Link] Reference Sites for CH

There will be 2 Reference Sites for creation with Reference. One belongs to Company Code CH10 / Sales
Area CH10/00/01 and the second one belongs to Company Code CH11 / Sales Area CH11/00/01. These
Reference Sites must be fully maintained with all 5 Site BP Roles and with partner profiles for Inbound and
Outbound POS communication. [Link]

Reference Sites for CH will be: CBZZ and CBZY:

 CBZZ Reference Site for CH10
 CBZY Reference Site for CH11

Functional Design Document Internal 52

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 53 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

There will be 1 Site (Plant) Profile for each Reference Site, which controls the creation of new sites and BP
sites for Units. For Switzerland, Site Profiles ZC01 and ZC02 have been set up for reference sites CBZZ and
CBZY respectively.
 ZC01 for CH10 and Reference Plant CBZZ
 ZC02 for CH11 and Reference Plant CBZY

[Link] Dummy Sites for CH

 CBZX - Dummy Site for CH Articles for TCPOS
This specific Dummy Site is used in the Listing process to control the listing and sending of Swiss
Articles to the POS system once, rather than for every site (see OP_FSC_I_134 Transfer article
master data from SAP to TCPOS for more details)

 CBZW - Dummy Site for Bonus Buys & Promotions

This specific Dummy Site is used with Bonus Buys & Promotions to support the creation of Bonus
Buys at the Outlet level (see OP_FSC_E_046 Assign Promotions to Units and Outlets for more
details)

The Dummy sites will be assigned only to CH10 organisation. This means, Reference Site is CBZZ.

Functional Design Document Internal 53

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 54 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

5.4 Integration Considerations

5.4.1 Core Design

Unit (Site) and Outlet master data is used by S4HANA transactions and REACT apps across multiple Level 3
processes:

L3 Process S4 Functionality / Integration Area

REACT App
2.2.1 Maintain Client S4 Conditional Contract Units and Outlets can be assigned within the business volume
Contract Master Data Management selection criteria of Client Contracts.
3.1.2 Ingredient & Recipe & Ingredient All Recipes will be created Above Unit, rather than In Unit, for
Recipe Management Management app use within the Menu Planning apps. Recipe Management
Reporting includes recipe performance reporting by unit.
3.2.1 Above Unit Above Unit Concept Concepts (e.g., Shopping Lists, Central Recipe Lists,
Concept Management Management & Menu Hospitality Concepts and Central Menu Plans) are maintained
Planning app and assigned to units/outlets.
3.2.2 In-Unit Concept In Unit Menu Planning In unit menu planning and shopping cart creation of articles
Management app to procure for an outlet.
3.2.3 Pricing, S4 Price Condition, Article sales prices can be maintained at country, sector, sub-
Promotion and Promotion & Bonus Buy sector, format, unit and outlet levels.
Discount Management maintenance
Promotions and Bonus Buys can be maintained at country,
sector, sub-sector, unit group, outlet group, unit and outlet
levels.
4.2.4 Manage S4 Approved Product List Approved Product List maintained per country, with filters
Approved Product List (APL) report, Managed per unit.
Order Guide (MOG)
Managed Order Guides maintained per sector/sub-sector
Workbench, Site Product
linked to units.
Catalogue (SPC) report
Site Product Catalogue list of articles can be created at
sector / subsector and site level, based on Approved Product
List with Managed Order Guide and Approved Vendor List
rules applied.
4.3.1 Purchase Ordering app / S4 Shopping Carts (Purchase Requests) can be created for a unit
Requisition and Procurement and its outlets and converted into Purchase Orders.
Ordering
4.3.2 Manage Supplier Goods Receipt app / S4 Return POs and Vendor Credit Notes can be raised by units
Claims Procurement for good receipt discrepancies.
4.5.1 Production, Production, Yield & Record yield and waste from production for an outlet.
Preparation & Waste Management App
Execution
4.5.3 Yield and Waste
Management

Functional Design Document Internal 54

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 55 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

5.2.1 Manage In-Unit Stock Count app Stock counts are requested and recorded per outlet.
Inventory
5.2.4 Manage In-Unit Goods Receipt app / S4 Goods and service receipt notes are recorded for
Goods Receipt Goods Receipt units/outlets.
5.2.6. Manage Goods Stock Transfers app Request and approve transfers of stock between different
Transfer units or outlets.
6.2.1 Manage Client Quote & Orders app Quotes, orders and billing information for clients within an
Quotes and Orders outlet is created and maintained.
6.3.1 POS Inbound POS systems Sales and payment information within units and outlets is
recorded on POS systems and REACT apps, transferred via
SAP CAR and posted into S4.
6.3.2 POS Outbound S4 POS Outbound Data SAP article, assortment listing, pricing and promotions data
Transfer for units and outlets is transferred to POS Type 1 systems and
emailed to POS Type 3 units.
6.3.3 Consumer Sales BI Sales Analytics In-Unit Dashboard and In-Unit Product Gross Profitability
Analytics Reports Report provide analytics per unit.
7.1.3 Intercompany S4 Intercompany Head Office Site BPs and Intercompany customers (for
Accounting Reconciliation Compass legal entities not yet live on S/4HANA) will be
assigned with a Trading Partner Number (Company ID) to
support identification of intercompany postings and
intercompany reconciliation, netting and settlement.
7.1.4 Period End In Unit Closing Cockpit Unit manager confirms completion of various unit activities
Closing app for the period.
7.3.3 In-Unit Sales and EOD app – POS Type 3 Sales transactions (e.g., revenue, non-revenue, payments) are
Payment Accounting and Cashbook functions recorded for each outlet in POS Type 3 units, based on the
POS system report.
Cashbook transactions (e.g., cash payments received and
made, bank deposits, cash transfers, cash counts) are
recorded for each unit outlet.
9.1.1 Finance Master S4 Profit Centre (Unit) Units and outlets are created and maintained as profit
Data Management and Cost Centre (Outlet) centres and cost centres respectively.
maintenance
9.1.3 Maintain S4 Approved Vendor List A list of approved vendors is generated for each unit, based
Business Partner – (AVL) on matching vendor and unit characteristics, and can be
Vendor manually adjusted.
9.1.4 Maintain S4 Business Partner Units are assigned to Trade Clients as ZU Unit partner
Business Partner - maintenance functions.
Customer
9.1.5 Maintain Articles S4 Assortment Selling Catalogues of articles are created and assigned to
maintenance sectors or units.

For more details on each process and functionality, see the corresponding BPD and FDD documentation.

Functional Design Document Internal 55

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 56 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

5.4.2 Localisation Considerations - Switzerland

In CH, BP Units (Sites) and BP Outlets will be manually created in the POS system TC POS, as part of the
Unit/Outlet creation process.

Below table provides the list of Legacy systems where Units and Outlets needs to be updated. List needs to
be further enriched in country specific deployments:

Country Legacy System Used for Units & Outlets Updated by &
update mechanism Frequency
CH Touchway Menu Planning/ Content Manual Unit/ Outlet creation
Management System (CMS)
CH Eaternity Carbon Footprint estimation Manual Unit/ Outlet creation
CH MIK Reporting Manual
CH Webshop Ordering Not Integrated Not integrated
CH TC POS Point of Sale (POS) Manual Unit/ Outlet creation
CH Success Factors Payroll Activities Manual Unit/ Outlet creation
(TBC)

[Link]

Functional Design Document Internal 56

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 57 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

6. Master Data Requirements to Support Solution

6.1 SAP Data Objects
 Site (Plant) Master for Units

Note: A Site Master is one business object made up of several components including site master data,
plant configuration and Customer and Vendor Business Partner master data.

Functional Design Document Internal 57

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 58 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

 Business Partner for Units (Sites) and Outlets

Note: Customer / Vendor Integration (CVI) in S/4HANA bidirectionally integrates Business Partner data
with Customer and Vendor Master data in real time as SAP S/4HANA SD, MM and other modules still
use the classic SAP ERP Customer and Vendor tables.

6.2 Front End Apps Data Requirements

Typically, the REACT apps read and post data via Odata services (in the same way that an SAP Fiori app
works). OData services typically access the database via function calls in the SAP application layer and can
read a CDS view or an S4HANA table. A CDS view has the advantage to push the joining conditions down to
the DB layer which promotes efficiency.

As well as accessing the basic S4HANA unit and outlet data (e.g., business partner number, name, address)
and the assignment of outlets to units via the ZO Outlet partner function, REACT apps use the following
specific unit/outlet information maintained in S4HANA:

L3 Process REACT App Data Requirement

4.3.1 Purchase Ordering app The Unit Vendor ZD partner functions will be available in the
Requisition and front-end Ordering App so that the appropriate ZD Receiving
Ordering Delivery Address can be assigned to the Purchase Order and
printed on the PO form.
5.2.1 Manage In-Unit Stock Count app The Unit/Outlet Stock Ownership field (General Attribute 7) is
Inventory used by the Stock Count app to generate finance postings for
stock counts only for units/outlets that contain Compass
owned stock.
5.2.4 Manage In-Unit Goods Receipt app The Destination Cost Centre belonging to the selected outlet

Functional Design Document Internal 58

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 59 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

Goods Receipt is populated on any new Purchase Order items added during
Goods Receipt.
6.2.1 Manage Client Quote & Orders app Customer Group 5 in Switzerland represents the “Billing
Quotes and Orders Brand” at outlet level and controls the Consumer Brand logo
printed on Quotes & Orders in the app.
7.3.3 In-Unit Sales and EOD app – POS Type 3 The POS Type (General Attribute 2) indicates whether POS
Payment Accounting and Cashbook functions Type 3 transactions need to be recorded in the EOD app for
Type 3 Non-Connected units/outlets.

The current Matrix security access model for the Apps checks the profit centre, which is mapped to from
the unit, outlet or cost centre depending on the App and process being transacted.
When a Unit or Outlet is created or changed in S4HANA, app specific Unit/Outlet master data attributes are
uploaded via spreadsheet into the REACT app database for use across all apps as required. Here are
examples of the app specific attributes and data that is maintained:

App Functional Area Unit/Outlet App Attribute Example Data Notes

Basic Country CH From Cost Center or Profit
Center
Basic CoArea CG01 Controlling area
Basic ProfitCenter CH0C125000 From Cost Center
Basic Unitname 125 ETH From Profit Center
Basic Costcenter CH0C125100 From Cost Center
Basic Outletname 12510 ETH From Cost Center
Cafeteria
Basic ReferenceSiteID C125 SAP Site
Basic CompanyCode CH10
Basic Sector
Basic Subsector
Basic Segment 0000001010
Cashbook CashJournal 0012 Related to an outlet
Cashbook isCashJournal Yes Logic flag
Cashbook CashFloat
Cashbook CashLimit
Cashbook Currency CHF
Modules CreditCard Yes/no
Modules CLC Yes/no
Modules Non PO Accruals Yes/no
Modules Inventory Yes/no
Modules FoodTransfer Yes/no

Functional Design Document Internal 59

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 60 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

Modules RevenueTransfer Yes/no

Modules LabourTransfer Yes/no
Modules KPI Yes/no
Modules P2P GR Invoices Yes/no
Modules OTC SD-Billing Yes/no
Ordering Delivery ID Related to Cost Center
Ordering Delivery Address Related to Cost Center
Quotation BP - Trade Customers 1 to n
Quotation Site Customers 1 to n
Concept Management Flexibility Rules TBD unit or concept

For more details on each process and app functionality, see the corresponding BPD and FDD
documentation.

Functional Design Document Internal 60

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 61 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

7. SAP RICEFW List

RICEFW list in 9.1.2 (1) Maintain Site Master Build Package

Updated List of RICEFW can be derived from the link below:

Link

Jira Description Status

MTX-19831 DATA_C_001_GL - Conversion RICEFW (ETL) - Master Data - Approved
Sites
MTX-14737 FIN_FSC_E_001 A document explaining how a unit is Cancelled - content of
represented in Compass is required to avoid confusion FSD still valid
MTX-21153 OP_FSC_E_039 Enhance POS Outbound Delta Transaction Approved
WDBU_HPR (SAP Incident 500960)
MTX-23557 OP_FSC_E_143 Missing Link between Outlet and Cost Center Cancelled

Functional Design Document Internal 61

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 62 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

8. Open Design Topics

Requirement Description Sl# Open Point Action
MTRX-773 Assign and Update 1 We have planned to use Action MTX-22587 managed
Specific User Roles to an Master Data team to create by Heather Pascoe and Vikas
Outlet (Segregation of Outlets in the SAP S4 Jain.
Duty - SOD) system.
Action Closed.
The business expectation in
the requirement is not clear.

MTRX-771 Create and Update a 1 Operational Organisation Action MTX-21678 contains

Unit Levels - For the first look in the solution.
the business requirement,
There are 9 free text
this field looks like an
attributes at Profit Center
Additional Attribute, but
level which will contain the
after discussing with
information.
business, expectation is to
create an Organisation Action Closed.
Hierarchy Structure and
need to assign Units and
Outlets to the hierarchy.
MTRX-772 Create and Update an 1 Whether the Outlets should Confirmed in the meeting
Outlet also act as Vendor in any between Operations Team
business scenario? and Business Team on
26.08.2021.

Yes. Outlets should have

Vendor Role and Vendor FI
Role.
MTRX-772 Create and Update an 2 Attributes - Confirmed in the meeting
Outlet i. Outlet Size (i.e., Large, between Operations Team
Medium, Small) and Business Team on
ii. Consumer Brand, if 24.08.2021.
applicable (e.g., Costa
i. Outlet size is a reporting
Coffee, Cafe Dallucci)
attribute that is not requiring
iii. Sales Price List (i.e.,
additional functionality
Sector or Sub-sector) and
confirmation whether outlet ii. Consumer Brand is a
specific pricing is applicable reporting attribute that no
iv. Contract Pricing requiring additional
Conditions (e.g., 10% below functionality. One Outlet can
sector price list) only have one Consumer
v. POS Type, there could be Brand
more than 1 POS type in
each outlet

Functional Design Document Internal 62

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 63 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

vi. Ordering and Goods Confirmed in the meeting

Receipt Location(s) between Operations Team
vii. Inventory Ownership and Business Team on
(i.e., Compass or Client 26.08.2021.
owned)
v. POS Type – Business is
happy with the configuration
available (France Design).
Available in the Site Customer
ZSTCU1 – General role.

Confirmed via Action MTX-

22588 for the following:
iii. This is available as the
Price List on the BP Site. The
outlet will always carry the
same sector/subsector as the
related Unit.
iv. Contract Pricing Conditions
will be handled via SD Pricing
Conditions with different key
combinations, including Unit
and Outlet levels MTX-23737
vi. Ordering and Goods
Receipt Location(s). When
Purchase Orders are raised
against the Unit and Cost
Center, then each outlet will
be linked to cost center and
each cost center will have its
own address
vii. Inventory Ownership (i.e.,
Compass or Client owned) will
be held in the General
Attribute 7 of the BP Site
MTRX-772 Create and Update an 3 Attributes - Action MTX-21754 closed.
Outlet i. Concepts
Action MTX-22588 closed.
ii. Contract Menu Conditions i. Concepts are not
(e.g., organic only, halal maintained in the Outlet
only, 5 main courses per (business partner) master
day). Note: This may be set data instead, it is available in

Functional Design Document Internal 63

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 64 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

up/ amended directly in the "In Unit Concept

above unit concept Management". MTX-23922
management
ii. Contract Menu Conditions
are not maintained in the
iii. Link to other
Outlet (business partner)
outlets/units for
master data instead, it is
ordering/transactions and
available in the "Menu
production (e.g., the outlet
Planning". MTX-23923
produces meals for another
outlet or orders on behalf of iii. Link to other outlets/units
another outlet/unit and/or for ordering/transactions and
regularly transfers or production are not
receives other costs or cash maintained in the Outlet
from another outlet) (business partner) master
data
MTRX-779 Close a Unit, Outlet or 1 Status “Service Closed:
Head Office Location and Discontinued” means only
Both Status values are
Provide a Reason Code the Purchase related
available to set on the Site
Transactions block and
Master Blocking Reason and
“Closed” means both
the Site BP Order and Billing
Purchase and Sales related
Block fields.
transactions are blocked.
General Attribute 6:
Unit/Outlet Closing Reason
will be set when Status
“Service Discontinued” is
maintained in the Order Block
and Billing Block fields on the
Site or Outlet BP.
MTRX-1575 Set & Update the Unit 1 Site Master (Unit) - Action Jira MTX-21190 has
and Outlet Status been closed. The following
Statuses “Draft” and statuses are available on the
“Active” are yet to be Site Master and BP Site:
designed.
Z1 Draft
Z2 Active
Z5 Service Discontinued
Z6 Closed
MTX-20608 The Authorisation Group 1 What solution will be used: Managed via action MTX-
at the Business Partner 20544
i. to ensure that users can
general level can be
only create/change general
used to control which
level master data relevant to
countries can access Action Closed
their own country
which business partner
general data (i.e., ii. to ensure that search
restricting S/4 users to results return master data
creating, changing, relevant to their country
displaying or listing only
their country’s BPs).

Functional Design Document Internal 64

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 65 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

CH01 is available to
assign to Swiss Business
Partners.
MTX-24085 BP Site/Customer and 1 Align on Additional Data / Closed with alignment on
Site Unit: Classification / Customer Groups which Attributes & Customer
Additional fields / Groups will be used for CH
Customer Groups unit and outlet BPs

N/A Material Ledger default 1 Which Material Ledger Type Closed - Material Ledger Type
in System should be assigned to Site CG01 will be used, as
Masters? confirmed by Finance

MTX-24023 Procurement Copy 1 FSD assumes a site exists for MTX-27038

Payment Terms from CH12 to determine a
Company Code purchasing org for the Closed. Confirmed by
company code. Not possible Solution Architecture that
Enhancement
to create a Site for company there is no need to have
PRO_FSC_E_133 Purchase Org/Sales Org or
code CH12 as sales and sales
areas are not in scope for Site in this co code as no
CH12. purchase orders or SD billing.
CH12 is A005 in legacy. Only
Licence fees are handled
through this company so no
meaningful business
processes. There is one inter-
company invoice per year
from CH10 to CH12 which will
be handled using an inter-
company business partner for
CH12.

Functional Design Document Internal 65

Compass Group Doc No: 9.1.2 Maintain Site Master
Project Matrix Rev: V0.3 Page 66 of 66

9.1.2 Maintain Site Master Modified: 31/05/2022

9. Key SAP Transactions / Fiori Tiles and Roles

SAP SAP Transaction and Description / Technical Fiori App ID Role
GUI / Fiori Tile
Fiori
Fiori Create Site WB01 In Country Master Data
Maintainer
Fiori Maintain Site WB02 In Country Master Data
Maintainer
Fiori Display Site WB03 In Country Master Data
Maintainer
Fiori Maintain Business Partner BP In Country Master Data
Maintainer
Fiori Display Customer List F2640 In Country Master Data
Maintainer
BI Unit & Outlet Status Report Z_OPS_UNITOUTLET_118 In Country Master Data
Maintainer
In Country Master Data
Manager

Notes:
 The Unit & Outlet Status Report (OPS_FSC_R_0118 BI report) can be used to review the data, status
and set up of the site and related outlets. For more details, see
[Link]

Functional Design Document Internal 66

Business Data IDoc Types Overview
No ratings yet
Business Data IDoc Types Overview
1 page
SAP SD Questionnaire
No ratings yet
SAP SD Questionnaire
9 pages
SAP AFS Manual for New Joiners
No ratings yet
SAP AFS Manual for New Joiners
156 pages
Site Management
No ratings yet
Site Management
45 pages
FS Ingredients Article Master Test Script
100% (1)
FS Ingredients Article Master Test Script
6 pages
SAP POS Bonus Buy Integration Guide
No ratings yet
SAP POS Bonus Buy Integration Guide
12 pages
Country of Origin Enhancement Spec
No ratings yet
Country of Origin Enhancement Spec
20 pages
SD Sales Scenario and Org Structure in IS-Retail
No ratings yet
SD Sales Scenario and Org Structure in IS-Retail
13 pages
BOM Empties V2
No ratings yet
BOM Empties V2
2 pages
SAP POS Data Management Overview
No ratings yet
SAP POS Data Management Overview
16 pages
Master Data Governance Mass Import Solution For Retail and Fashion Management - Article Substitution
No ratings yet
Master Data Governance Mass Import Solution For Retail and Fashion Management - Article Substitution
18 pages
Journey From Posdm To Posdta (Car)
No ratings yet
Journey From Posdm To Posdta (Car)
2 pages
DRFOUT Screenshots
No ratings yet
DRFOUT Screenshots
3 pages
SAP IDoc Partner Profile Guide
No ratings yet
SAP IDoc Partner Profile Guide
18 pages
Contents:: Course Goals Course Objectives Course Content Course Overview Diagram Main Business Scenario Background To AFS
No ratings yet
Contents:: Course Goals Course Objectives Course Content Course Overview Diagram Main Business Scenario Background To AFS
15 pages
SAP Customer Master Structure: Account Groups
No ratings yet
SAP Customer Master Structure: Account Groups
2 pages
11 ICP310 SAP AFS Sales Information System
No ratings yet
11 ICP310 SAP AFS Sales Information System
12 pages
Customer Hierarchy Guide
100% (1)
Customer Hierarchy Guide
16 pages
Distributing Business Partner Master Data From SAP CRM
No ratings yet
Distributing Business Partner Master Data From SAP CRM
28 pages
SAP TM Presentation
No ratings yet
SAP TM Presentation
21 pages
SAP Sales Organization and Channel Setup
No ratings yet
SAP Sales Organization and Channel Setup
11 pages
SAP SD Depot Process Guide
No ratings yet
SAP SD Depot Process Guide
47 pages
SAP Structure for Chico Creek Brewery
100% (1)
SAP Structure for Chico Creek Brewery
55 pages
Reference Purchasing Organization
No ratings yet
Reference Purchasing Organization
3 pages
SAP Business Process Overview
No ratings yet
SAP Business Process Overview
3 pages
FDS0019 GAP0080 O2C GTS Commercial Invoice
100% (1)
FDS0019 GAP0080 O2C GTS Commercial Invoice
22 pages
Select The First Option For Bonus Buy at Site Level
100% (1)
Select The First Option For Bonus Buy at Site Level
14 pages
KBA 173587 - Settings For The Pricing Worklist Sap KBA Knowledge Document
No ratings yet
KBA 173587 - Settings For The Pricing Worklist Sap KBA Knowledge Document
6 pages
S4HANA Business Value
100% (1)
S4HANA Business Value
24 pages
Integrating The Best Run Businesses
No ratings yet
Integrating The Best Run Businesses
57 pages
Inbound Delivery and Freight Management Guide
No ratings yet
Inbound Delivery and Freight Management Guide
1 page
JD - SAP IS-Retail Pricing and Promotion
No ratings yet
JD - SAP IS-Retail Pricing and Promotion
1 page
Structured Article Maintenance in SAP ERP PDF
No ratings yet
Structured Article Maintenance in SAP ERP PDF
6 pages
KGSSAPALink 45
No ratings yet
KGSSAPALink 45
99 pages
SAP AFS Retail Interface - Characteristic
100% (1)
SAP AFS Retail Interface - Characteristic
6 pages
Qsands Sis
No ratings yet
Qsands Sis
24 pages
SAP F&R Insights: Wawa's Journey
No ratings yet
SAP F&R Insights: Wawa's Journey
23 pages
Picking Packing and Goods Issue
100% (1)
Picking Packing and Goods Issue
6 pages
Appex Corporation: Structure and Control Issues
No ratings yet
Appex Corporation: Structure and Control Issues
10 pages
DT103v Presentation v2 1698948303809001JlIr
No ratings yet
DT103v Presentation v2 1698948303809001JlIr
22 pages
Master Datanew
No ratings yet
Master Datanew
27 pages
PLM - FSPEC.016 - Create-Update Article From Specification
No ratings yet
PLM - FSPEC.016 - Create-Update Article From Specification
159 pages
Oil & Gas: Warning
No ratings yet
Oil & Gas: Warning
16 pages
Business Rules Management with BRFplus
No ratings yet
Business Rules Management with BRFplus
5 pages
BATCH MANAGEMENt
No ratings yet
BATCH MANAGEMENt
30 pages
Retail Best Practices Overview
No ratings yet
Retail Best Practices Overview
6 pages
Retail Assortment Planning Guide
100% (1)
Retail Assortment Planning Guide
28 pages
SAP ERP Sales & Distribution Structures
No ratings yet
SAP ERP Sales & Distribution Structures
60 pages
Solution Builder
100% (1)
Solution Builder
2 pages
MSC SD Functional Spec Sales Order Report
No ratings yet
MSC SD Functional Spec Sales Order Report
10 pages
Executive Summary
No ratings yet
Executive Summary
4 pages
SAP HANA Sizing Questionnaire
No ratings yet
SAP HANA Sizing Questionnaire
8 pages
SAP Track & Trace: Supply Chain Visibility
No ratings yet
SAP Track & Trace: Supply Chain Visibility
6 pages
Creating Condition Records in SAP S/4 HANA
No ratings yet
Creating Condition Records in SAP S/4 HANA
5 pages
SAP Retail Assort
0% (1)
SAP Retail Assort
1 page
Functional Design Document Operations - Maintain Articles - V0.3
No ratings yet
Functional Design Document Operations - Maintain Articles - V0.3
81 pages
Workshop IMIS Certification1
No ratings yet
Workshop IMIS Certification1
25 pages
Functional Design Document Operations - Manage Client Contract
No ratings yet
Functional Design Document Operations - Manage Client Contract
50 pages
R-APDRP BSPHCL IT Solution Design
No ratings yet
R-APDRP BSPHCL IT Solution Design
18 pages
Sample Sap PP Business Blueprint Document For Textile Company - Doc Google Docs
No ratings yet
Sample Sap PP Business Blueprint Document For Textile Company - Doc Google Docs
18 pages
Sales Marketing Resume Sample
No ratings yet
Sales Marketing Resume Sample
8 pages
Pranav Tiwari 2220739
No ratings yet
Pranav Tiwari 2220739
61 pages
Trade Marketing Strategies Overview
50% (4)
Trade Marketing Strategies Overview
27 pages
CRM Group Assignment UCSI 2
No ratings yet
CRM Group Assignment UCSI 2
19 pages
Beena Yadav: Recruitment Manager Profile
No ratings yet
Beena Yadav: Recruitment Manager Profile
4 pages
Advantages and Challenges To Online Seller During The New Normal Among Selected Students
100% (1)
Advantages and Challenges To Online Seller During The New Normal Among Selected Students
23 pages
Commercial Real Estate International Business Trends
100% (2)
Commercial Real Estate International Business Trends
21 pages
Mercado Livre Enemies at The Gate
No ratings yet
Mercado Livre Enemies at The Gate
45 pages
Business Regulatory Framework Unit1 Unit2
No ratings yet
Business Regulatory Framework Unit1 Unit2
3 pages
Company 4-4 BS
No ratings yet
Company 4-4 BS
17 pages
Approved Monthly GST Data For Publishing May 2025
No ratings yet
Approved Monthly GST Data For Publishing May 2025
4 pages
Sample JDs - Sheet1
No ratings yet
Sample JDs - Sheet1
23 pages
The North Face Media Plan
100% (2)
The North Face Media Plan
23 pages
Principles of Retail Management
100% (1)
Principles of Retail Management
226 pages
Marketing Plan Template
No ratings yet
Marketing Plan Template
5 pages
E-Retailing in India
100% (1)
E-Retailing in India
99 pages
EIJBM
No ratings yet
EIJBM
18 pages
Sales Tax Lecture Notes
No ratings yet
Sales Tax Lecture Notes
21 pages
Business Plan Horse Breeding
100% (1)
Business Plan Horse Breeding
12 pages
Chapter 1
No ratings yet
Chapter 1
12 pages
Garnier
No ratings yet
Garnier
27 pages
Case Study
No ratings yet
Case Study
44 pages
Sales Process PPT 1
No ratings yet
Sales Process PPT 1
29 pages
Marketing Strategies in Banks
100% (1)
Marketing Strategies in Banks
79 pages
Real Estate Marketing Expert Resume
No ratings yet
Real Estate Marketing Expert Resume
2 pages
Sap SD Faqs
No ratings yet
Sap SD Faqs
7 pages
Tax Invoice: Bill To Matarani Infrastructure Pvt. LTD
No ratings yet
Tax Invoice: Bill To Matarani Infrastructure Pvt. LTD
8 pages
Definition of Costing
No ratings yet
Definition of Costing
22 pages
Customer-Driven Marketing Strategies
No ratings yet
Customer-Driven Marketing Strategies
43 pages
Future Group Central Mall Internship Report
50% (8)
Future Group Central Mall Internship Report
123 pages