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.
DC6SAP S/4HANA: data that comes in
Select any card above to switch tool. 45 fields documented, status per field.
- 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)
| Entity | Field | Feeds metric | Status |
|---|---|---|---|
| A_JournalEntryItemBasic | CompanyCode | Entity filter | Documented (public docs) |
| A_JournalEntryItemBasic | FiscalYear | Periodisation | From knowledge |
| A_JournalEntryItemBasic | AccountingDocument | Traceability | From knowledge |
| A_JournalEntryItemBasic | LedgerGLLineItem | Key | From knowledge |
| A_JournalEntryItemBasic | Ledger | Filter on 0L | From knowledge |
| A_JournalEntryItemBasic | GLAccount | P&L mapping, revenue and EBITDA | From knowledge |
| A_JournalEntryItemBasic | AmountInCompanyCodeCurrency | Revenue, costs, EBITDA, gross margin | From knowledge |
| A_JournalEntryItemBasic | CompanyCodeCurrency | Conversion | From knowledge |
| A_JournalEntryItemBasic | DebitCreditCode | Sign logic | From knowledge |
| A_JournalEntryItemBasic | PostingDate | Revenue per month, DSO | From knowledge |
| A_JournalEntryItemBasic | DocumentDate | Cut-off | From knowledge |
| A_JournalEntryItemBasic | FiscalPeriod | Month and YTD, variance | From knowledge |
| A_JournalEntryItemBasic | ClearingDate | AR and AP duration, DSO and DPO | Documented (public docs) |
| A_JournalEntryItemBasic | ClearingAccountingDocument | Open-item status | From knowledge |
| A_JournalEntryItemBasic | CostCenter | Labour cost %, cost per site | From knowledge |
| A_JournalEntryItemBasic | ProfitCenter | Revenue and EBITDA per division | From knowledge |
| A_JournalEntryItemBasic | Segment | Division reporting (Eurest, InnoClean, Camille) | From knowledge |
| A_JournalEntryItemBasic | FunctionalArea | Cost of sales versus overhead | From knowledge |
| A_JournalEntryItemBasic | WBSElement / OrderID | Margin per contract | Uncertain |
| A_JournalEntryItemBasic | Customer / Supplier | AR and AP per party | From knowledge |
| A_JournalEntryItemBasic | FinancialAccountType | Split AR and AP | From knowledge |
| A_OperationalAcctgDocItemCube | NetDueDate | AR aging, DPO | From knowledge |
| A_OperationalAcctgDocItemCube | ClearingDate | DSO, AR aging | From knowledge |
| A_OperationalAcctgDocItemCube | AmountInTransactionCurrency | DSO, AR aging | From knowledge |
| A_OperationalAcctgDocItemCube | PaymentTerms | DPO policy | From knowledge |
| A_OperationalAcctgDocItemCube | CashDiscountDate1 | DPO policy | From knowledge |
| A_CostCenter | CostCenter | Site to division mapping | From knowledge |
| A_CostCenter | ValidityEndDate | Site to division mapping | From knowledge |
| A_CostCenter | CostCenterCategory | Site to division mapping | From knowledge |
| A_CostCenter | ResponsiblePerson | Site to division mapping | From knowledge |
| A_ProfitCenter | ProfitCenter | Contract and division mapping | Uncertain |
| A_ProfitCenter | ProfitCenterName | Contract and division mapping | Uncertain |
| A_ProfitCenter | Segment | Contract and division mapping | Uncertain |
| A_BillingDocument | BillingDocumentDate | Revenue per customer or contract | From knowledge |
| A_BillingDocument | TotalNetAmount | Revenue per customer or contract | From knowledge |
| A_BillingDocument | SoldToParty | Revenue per customer | From knowledge |
| A_BillingDocument | TransactionCurrency | Conversion | From knowledge |
| A_BillingDocumentItem | NetAmount | Revenue per contract | From knowledge |
| A_BillingDocumentItem | Product | Revenue per contract | From knowledge |
| A_BillingDocumentItem | ReferenceSDDocument | Revenue per contract | From knowledge |
| A_SalesOrder | SalesOrder | Contract value, backlog | From knowledge |
| A_SalesOrder | SoldToParty | Contract value, backlog | From knowledge |
| A_SalesOrder | TotalNetAmount | Contract value, backlog | From knowledge |
| A_SalesOrder | RequestedDeliveryDate | Contract value, backlog | From knowledge |
| A_SalesOrder | SalesOrganization | Contract value, backlog | From 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.
| Domain | Assumed tool |
|---|---|
| ERP and finance | SAP S/4HANA (Finance, Controlling, AR/AP) |
| HR master data | SAP SuccessFactors Employee Central |
| Planning and time registration | Quinyx |
| Procurement | Coupa |
| CRM, tenders, contracts | Salesforce Sales Cloud |
| Point of sale (staff restaurants) | Oracle MICROS Simphony |
| Recipes, food cost, stock | Apicbase |
| Food waste | Winnow or Leanpath |
| Quality and safety (audits) | SafetyCulture (iAuditor) |
| Vending | Nayax |
| Customer satisfaction | HappyOrNot |
Five questions for Nico
- 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?
- 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)?
- 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?
- 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?
- 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 field | SAP S/4HANA |
|---|---|
| entry_id | AccountingDocument + LedgerGLLineItem |
| company_code | CompanyCode |
| period, posting_date | FiscalYear + FiscalPeriod, PostingDate |
| gl_account | GLAccount |
| amount_eur | AmountInCompanyCodeCurrency |
| division | Segment / ProfitCenter (mapping needed) |
| cost_center, contract_ref | CostCenter, 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.
| Tool | Effort | Reason |
|---|---|---|
| Hard | Tenant-specific services, mapping of GL accounts and profit centres, unclear planning API and possibly a BW or Datasphere layer in between. | |
| Medium | Standard OAuth and good OData, but permissions per entity, GDPR handling and the open question where absence data lives. | |
| Medium | Good public docs and OAuth, but licence-gated modules, unclear v3 shift fields and a rate source needed from HR or payroll. | |
| Medium | Clear OAuth and scopes, but 50 records per page, contractual rate limits and payment data that lives elsewhere. | |
| Easy | Well-known REST API and SOQL, JWT auth and generous limits. Only the custom fields and the ACV definition need agreement. | |
| Medium | Well documented BI API with PKCE, but account setup by Compass IT, a version that is unknown and unreliable covers. | |
| Medium | Clear OAuth and modules, but an extra paid API module, unconfirmed JSON keys and a recipe mapping to the POS. | |
| Hard | No public API: depends on vendor cooperation or file exports, and Compass may run both tools across sites. | |
| Easy | Bearer token, a documented Feed API with incremental sync and workable rate limits. Only column names need a check. | |
| Medium | Simple Bearer auth and verified machine and sales fields, but limited history and unverified inventory data. | |
| Easy | Simple token auth and JSON, but an add-on must be activated and the feedback fields still need to be confirmed. | |
| Hard | The system belongs to the customer: depends on contract and goodwill, with no standard Compass access. |
Demo with sample data. Not company figures.