Discovery Brief For internal preparation
Vol. 01 / №01
SAP × Group Integration · Question Set

Before we
build, we ask.

A technical discovery brief for the SAP team — every answer we need before writing the first line of integration code, in one pass.

Prepared by
Osama
For
SAP Technical Team
Scope
Payroll · Finance · HR
Target
OData / MCP access
Intent

We are integrating SAP Payroll, Finance, and HR data into our internal AI agent and n8n automation layer. The goal of this session is to leave with a clear map of available APIs, authentication paths, rate limits, and integration patterns — enough to start building, not just scoping.

01

Environment & access

  • Which SAP products are in scope — S/4HANA (Cloud or On-Premise), ECC, SuccessFactors Employee Central, Employee Central Payroll (ECP), or classic HCM Payroll?
  • Is there a sandbox or QA tenant we can use for integration development, and how do we request access?
  • Data center / region for each system (relevant for latency and data residency)?
  • Are there IP allow-listing requirements from our side (our n8n server)?
02

Authentication & security

  • Supported auth methods — OAuth 2.0 (which grant types), Basic Auth, API Key, X.509, SAML assertion?
  • Token lifetime, refresh mechanism, and rotation policy?
  • Is mTLS required for production calls?
  • Can we get a dedicated technical / service user per integration, and what RBAC roles will be assigned?
  • Any requirement to go through SAP BTP Destination Service or Cloud Connector?
03

SuccessFactors HR (Employee Central)

  • Is OData v2, OData v4, or both exposed? Which entities are available in each?
  • Access to core entities: PerPerson, EmpEmployment, EmpJob, EmpCompensation, PerPersonal, FOCompany, FOCostCenter?
  • Is the Compound Employee API enabled (for full employee snapshots)?
  • Delta / incremental query support (lastModifiedDateTime filtering)?
  • Visibility of custom fields (cust_*) via API?
  • Are Intelligent Services / Event Center webhooks available for HR events (hire, termination, job change)?
04

Payroll

  • Is payroll on Employee Central Payroll (ECP) or on-prem HCM? This determines the integration pattern.
  • API access to payroll results (RT, BT, CRT, IT tables) — directly or via extractor?
  • Payslip retrieval endpoint (PDF or structured)?
  • Wage type catalog, cost distribution, and posting documents to FI?
  • Off-cycle payroll triggers via API?
  • Pay statement / earnings statement data per employee per period?
  • How are payroll postings to Finance exposed — direct GL document API, or batch extract?
05

Finance (S/4HANA · ECC)

  • Which API layer — OData services (SAP API Business Hub), SOAP BAPIs, RFC, or CDS views exposed as OData?
  • GL endpoints: API_JOURNALENTRY_SRV, API_OPLACCTGDOCITEMCUBE_SRV, or equivalent?
  • Trial balance, balance sheet, P&L extraction — standard API or custom CDS view?
  • AR / AP: customer / vendor master, open items, aging — which services?
  • Cost center, profit center, internal order master data APIs?
  • Posting period control — can we read which periods are open?
  • Document attachment APIs (for invoices, etc.)?
  • Multi-company-code support and how company codes are filtered in queries?
06

OData technical specifics

  • Full $metadata URL for each service (we need this to generate clients)?
  • Support for $batch, $filter, $expand, $select, $orderby?
  • Default page size and max page size? Server-driven paging cursor format?
  • Concurrency control — ETags, If-Match headers required for writes?
  • Action / Function imports for non-CRUD operations (e.g., posting, approving)?
07

Rate limits, quotas & bulk access

  • Documented rate limits per service (calls/minute, calls/day, concurrent connections)?
  • Throttling behavior — 429 responses with Retry-After, or hard cutoff?
  • For large extracts, is there a bulk extract / Data Export Service / OData stream option vs paginated reads?
  • Any quota implications for our license tier?
08

Integration patterns

  • Recommended pattern: direct OData, or routed through SAP Integration Suite / Cloud Platform Integration (CPI) iFlows?
  • If CPI is mandatory, who owns the iFlow development — us or SAP team?
  • Webhooks / event-driven push (Intelligent Services, SAP Event Mesh) — what events are available?
  • Is there an SAP Build Process Automation or Joule integration layer we should leverage?
09

MCP & AI integration

  • Does SAP currently expose an MCP (Model Context Protocol) server, or is one on the roadmap (Joule / AI Foundation)?
  • Is SAP AI Core or Generative AI Hub available on our tenant, and can it be a bridge for LLM agents?
  • Any SAP guidance / restrictions on connecting third-party LLM agents (e.g., Claude via n8n) directly to OData?
10

Documentation & tooling

  • Access to SAP API Business Hub for the relevant packages?
  • Postman collections or OpenAPI specs available?
  • A named technical contact for integration questions during build?
11

Operations, SLA & lifecycle

  • API versioning and deprecation policy (notice period for breaking changes)?
  • Change / maintenance windows and how we get notified?
  • Where do we see API logs / errors on the SAP side for debugging?
  • Support channel and escalation path for integration incidents?
12

Commercial

  • Any per-call, per-user, or per-volume licensing implications for the APIs we'll consume?
  • Difference in cost / licensing between direct OData vs going through CPI iFlows?
Don't leave the room without —

Four strategic asks.

  1. One named technical contact assigned to our integration project for the duration of the build.
  2. A sandbox with realistic data (anonymized, production-like) for Payroll, Finance, and HR — not an empty shell.
  3. $metadata URLs delivered upfront for every relevant service. That single artifact unblocks ~80% of the integration build.
  4. Confirmation of the auth flow they want us to use before we write a line of code — ideally OAuth 2.0 client credentials for our n8n service identity.
Generate PDF and email final brief
0 / 0