Data catalog

The assumed software stack of Compass Group Luxembourg, the API fields each tool would deliver and the dashboard metrics they feed. The stack is an assumption to validate with Nico.

DC1Tools

12

Across 12 domains, assumed stack

DC2Documented fields

234

87 fields documented, status per field

DC3Tools with public field docs

25%

3 of 12 (3 partly); 7 from knowledge, 2 uncertain. Not tested live.

DC4Fields documented

37%

87 of 234 fields seen in public docs (not tested live)

DC5Browse the tools

Filter by domain, verification or access. The search box also looks inside field names, entities and metrics.

12 of 12 tools

DC6SAP S/4HANA: data that comes in

Select any card above to switch tool. 45 fields documented, status per field.

From knowledgeERP & financeAccess: Admin-issued credentialsOpen API docs
API
OData (API_JOURNALENTRYITEMBASIC_SRV, API_OPLACCTGDOCITEMCUBE_SRV, API_COSTCENTER_SRV, API_BILLING_DOCUMENT_SRV, API_SALES_ORDER_SRV)
Authentication
Cloud: communication arrangement with communication user (Basic) or OAuth 2.0. On-premise: SAP Gateway with Basic, OAuth 2.0 (SAML bearer) or X.509.
Access and approval
Compass IT must issue a read-only communication user and activate the services (for example in /IWFND/MAINT_SERVICE on-premise). Exact communication scenario IDs are unconfirmed.
Connection effort
HardTenant-specific services, mapping of GL accounts and profit centres, unclear planning API and possibly a BW or Datasphere layer in between.

Derived dashboard metrics

  • Revenue and EBITDA per division
  • Gross margin per contract
  • Budget variance
  • DSO and AR aging
  • DPO
  • Labour cost %

Feeds dashboard pages

  • /overviewExecutive overview
  • /pnlP&L and budget
  • /cashCash and working capital
  • /contractsContracts and sites
  • /workforceWorkforce and labour

Fields (45)

EntityFieldFeeds metricStatus
A_JournalEntryItemBasicCompanyCodeEntity filterDocumented (public docs)
A_JournalEntryItemBasicFiscalYearPeriodisationFrom knowledge
A_JournalEntryItemBasicAccountingDocumentTraceabilityFrom knowledge
A_JournalEntryItemBasicLedgerGLLineItemKeyFrom knowledge
A_JournalEntryItemBasicLedgerFilter on 0LFrom knowledge
A_JournalEntryItemBasicGLAccountP&L mapping, revenue and EBITDAFrom knowledge
A_JournalEntryItemBasicAmountInCompanyCodeCurrencyRevenue, costs, EBITDA, gross marginFrom knowledge
A_JournalEntryItemBasicCompanyCodeCurrencyConversionFrom knowledge
A_JournalEntryItemBasicDebitCreditCodeSign logicFrom knowledge
A_JournalEntryItemBasicPostingDateRevenue per month, DSOFrom knowledge
A_JournalEntryItemBasicDocumentDateCut-offFrom knowledge
A_JournalEntryItemBasicFiscalPeriodMonth and YTD, varianceFrom knowledge
A_JournalEntryItemBasicClearingDateAR and AP duration, DSO and DPODocumented (public docs)
A_JournalEntryItemBasicClearingAccountingDocumentOpen-item statusFrom knowledge
A_JournalEntryItemBasicCostCenterLabour cost %, cost per siteFrom knowledge
A_JournalEntryItemBasicProfitCenterRevenue and EBITDA per divisionFrom knowledge
A_JournalEntryItemBasicSegmentDivision reporting (Eurest, InnoClean, Camille)From knowledge
A_JournalEntryItemBasicFunctionalAreaCost of sales versus overheadFrom knowledge
A_JournalEntryItemBasicWBSElement / OrderIDMargin per contractUncertain
A_JournalEntryItemBasicCustomer / SupplierAR and AP per partyFrom knowledge
A_JournalEntryItemBasicFinancialAccountTypeSplit AR and APFrom knowledge
A_OperationalAcctgDocItemCubeNetDueDateAR aging, DPOFrom knowledge
A_OperationalAcctgDocItemCubeClearingDateDSO, AR agingFrom knowledge
A_OperationalAcctgDocItemCubeAmountInTransactionCurrencyDSO, AR agingFrom knowledge
A_OperationalAcctgDocItemCubePaymentTermsDPO policyFrom knowledge
A_OperationalAcctgDocItemCubeCashDiscountDate1DPO policyFrom knowledge
A_CostCenterCostCenterSite to division mappingFrom knowledge
A_CostCenterValidityEndDateSite to division mappingFrom knowledge
A_CostCenterCostCenterCategorySite to division mappingFrom knowledge
A_CostCenterResponsiblePersonSite to division mappingFrom knowledge
A_ProfitCenterProfitCenterContract and division mappingUncertain
A_ProfitCenterProfitCenterNameContract and division mappingUncertain
A_ProfitCenterSegmentContract and division mappingUncertain
A_BillingDocumentBillingDocumentDateRevenue per customer or contractFrom knowledge
A_BillingDocumentTotalNetAmountRevenue per customer or contractFrom knowledge
A_BillingDocumentSoldToPartyRevenue per customerFrom knowledge
A_BillingDocumentTransactionCurrencyConversionFrom knowledge
A_BillingDocumentItemNetAmountRevenue per contractFrom knowledge
A_BillingDocumentItemProductRevenue per contractFrom knowledge
A_BillingDocumentItemReferenceSDDocumentRevenue per contractFrom knowledge
A_SalesOrderSalesOrderContract value, backlogFrom knowledge
A_SalesOrderSoldToPartyContract value, backlogFrom knowledge
A_SalesOrderTotalNetAmountContract value, backlogFrom knowledge
A_SalesOrderRequestedDeliveryDateContract value, backlogFrom knowledge
A_SalesOrderSalesOrganizationContract value, backlogFrom knowledge

Notes and limitations

  • SAP and Salesforce docs could not be fetched in the research session, so nearly all SAP field names come from knowledge. Check them against $metadata of the real tenant or the SAP Business Accelerator Hub.
  • A_JournalEntryItemBasic reads ACDOCA (Universal Journal). Items that exist only in BSEG are not included.
  • Margin per contract only works if contracts have their own profit centre or WBS element. Unconfirmed.
  • Budget or plan data: the API is unclear (Planning data API versus an SAP Analytics Cloud export). Unconfirmed.
  • Group reporting is often extracted via Datasphere or BW, in which case OData is not the source.
  • Rate limits: no fixed public figure. Use $top and $skip, $select and delta on PostingDate, and run a nightly batch.

DC7Assumed stack: to validate with Nico

This stack is an assumption based on what is common at group subsidiaries in contract catering. Nothing here is confirmed by Compass Group Luxembourg.

DomainAssumed tool
ERP and financeSAP S/4HANA (Finance, Controlling, AR/AP)
HR master dataSAP SuccessFactors Employee Central
Planning and time registrationQuinyx
ProcurementCoupa
CRM, tenders, contractsSalesforce Sales Cloud
Point of sale (staff restaurants)Oracle MICROS Simphony
Recipes, food cost, stockApicbase
Food wasteWinnow or Leanpath
Quality and safety (audits)SafetyCulture (iAuditor)
VendingNayax
Customer satisfactionHappyOrNot

Five questions for Nico

  1. ERP and planning: which ERP holds the ledger (SAP S/4HANA Cloud or on-premise, or Dynamics 365 or Oracle), and does the budget live in the ERP, in SAP Analytics Cloud or in Excel?
  2. HR, payroll and time: is SuccessFactors really the HR master, which tool schedules and records hours (Quinyx, Kelio or other), and where is sickness absence registered (payroll, CNS, HR system)?
  3. Contracts: do contracts have their own profit centre or WBS element, and is Salesforce (or another CRM or register) the source for renewals and tenders?
  4. Operations: which of Simphony, Apicbase, Winnow or Leanpath, SafetyCulture, Nayax and HappyOrNot does Luxembourg itself use, and which data sits only on group-level Compass platforms?
  5. Access and governance: who issues API credentials (local IT or Compass group), and may the data leave the Compass environment (GDPR, hosting location)?

Source: _plan/PLAN.md (assumed stack), _plan/research/F-finance-hr.md, G-operations.md

DC8Unified data model

Where each normalised dashboard field would come from in every tool. A dash means the tool does not provide it. [?] means unconfirmed.

General ledger lines for revenue, costs, EBITDA and budget versus actual. Only SAP delivers this.

Normalised fieldSAP S/4HANA
entry_idAccountingDocument + LedgerGLLineItem
company_codeCompanyCode
period, posting_dateFiscalYear + FiscalPeriod, PostingDate
gl_accountGLAccount
amount_eurAmountInCompanyCodeCurrency
divisionSegment / ProfitCenter (mapping needed)
cost_center, contract_refCostCenter, WBSElement / ProfitCenter [?]
version (actual or budget)Ledger / planning API [?]

Source: _plan/research (sections Gemeenschappelijk datamodel in F and G)

DC9Connection effort

A rough estimate per tool based on authentication, approval, rate limits and open questions. Not a quote.

ToolEffortReason
HardTenant-specific services, mapping of GL accounts and profit centres, unclear planning API and possibly a BW or Datasphere layer in between.
MediumStandard OAuth and good OData, but permissions per entity, GDPR handling and the open question where absence data lives.
MediumGood public docs and OAuth, but licence-gated modules, unclear v3 shift fields and a rate source needed from HR or payroll.
MediumClear OAuth and scopes, but 50 records per page, contractual rate limits and payment data that lives elsewhere.
EasyWell-known REST API and SOQL, JWT auth and generous limits. Only the custom fields and the ACV definition need agreement.
MediumWell documented BI API with PKCE, but account setup by Compass IT, a version that is unknown and unreliable covers.
MediumClear OAuth and modules, but an extra paid API module, unconfirmed JSON keys and a recipe mapping to the POS.
HardNo public API: depends on vendor cooperation or file exports, and Compass may run both tools across sites.
EasyBearer token, a documented Feed API with incremental sync and workable rate limits. Only column names need a check.
MediumSimple Bearer auth and verified machine and sales fields, but limited history and unverified inventory data.
EasySimple token auth and JSON, but an add-on must be activated and the feedback fields still need to be confirmed.
HardThe system belongs to the customer: depends on contract and goodwill, with no standard Compass access.

Demo with sample data. Not company figures.