# SAP SuccessFactors MCP connector

The SAP SuccessFactors connector brings employee records, jobs, compensation, terminations and org structure into Elaichi, so Claude, ChatGPT, Cursor and the Elaichi Agent can answer questions from them inside each person's own SAP SuccessFactors access.

Source: https://elaichi.ai/connectors/sapsuccessfactors/

## Facts

| | |
| --- | --- |
| Application | SAP SuccessFactors |
| Category | HRIS |
| AI tools | 32 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once SAP SuccessFactors is connected

- List everyone who joined the Berlin location this month with job codes
- Which employment terminations happened in March, grouped by department?
- Show emergency contacts and phones for employees in cost center 4100

## Connect SAP SuccessFactors in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick SAP SuccessFactors.
2. Optionally set Share with, then press Connect.
3. Paste a SAP SuccessFactors API key. One person generates a token in SAP SuccessFactors and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which SAP SuccessFactors tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## SAP SuccessFactors MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## SAP SuccessFactors MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## SAP SuccessFactors MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect SAP SuccessFactors to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a SAP SuccessFactors tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with SAP SuccessFactors through Elaichi

### Answer a headcount question before the meeting

HR. Ask how many people sit in a department, division or location today and get the number from live SAP SuccessFactors employment records, not last month's spreadsheet.

### Pull the new joiner list every Monday

People Ops. List everyone whose employment started this month, with their job code, department and manager relationship, ready to paste into the onboarding plan.

### Check compensation before the pay run

Payroll. Look up recurring and one-off pay components for a pay group and spot anything that changed since the last cycle.

### Map people to cost centers for the forecast

Finance. Get every active employment grouped by cost center, company and business unit so the headcount budget matches what SAP SuccessFactors actually holds.

### Reconcile leavers against system access

IT. List employment terminations from the past two weeks and compare them with who still has accounts, so offboarding does not lag behind.

### Find a report's emergency contact fast

Managers. When something happens, ask for an employee's emergency contacts, phone numbers and work location and get them in seconds without opening SAP SuccessFactors.

## Frequently asked questions

### How do I connect SAP SuccessFactors to Claude?

Connect SAP SuccessFactors in Elaichi by pasting in an API key from your SAP SuccessFactors account; there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Claude can start answering questions from your SAP SuccessFactors records.

### Does SAP SuccessFactors work with ChatGPT and Cursor as well as Claude?

Yes. Once SAP SuccessFactors is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect SAP SuccessFactors once and every client picks it up.

### What can an AI agent actually do with my SAP SuccessFactors data?

An agent can look up people, their emails, phones, addresses, national IDs and emergency contacts, and read their employments, jobs, compensation, pay components and terminations in SAP SuccessFactors. It can also read the org structure: companies, locations, departments, divisions, business units, cost centers, pay groups, job codes and job functions. Short, concrete asks such as "list terminations in March by department" work better than long sentences.

### Does connecting SAP SuccessFactors give the AI access to everyone's records?

No. Every call to SAP SuccessFactors runs inside the access of the person who signed in, so the agent sees the same employees, compensation and org data that person could already open. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what SAP SuccessFactors already allows.

### Can my team share one SAP SuccessFactors connection?

Yes. One person connects SAP SuccessFactors with the API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in as themselves, so the audit log names the actual person behind every lookup.

### Can I stop an agent from deleting or changing things in SAP SuccessFactors?

This SAP SuccessFactors connector reads records; it does not change or delete anything. Even so, Elaichi restrictions work per action, so you can switch off any lookup, such as compensation or national IDs, for a team. A restricted action is never advertised to Claude, ChatGPT or Cursor, so no prompt can reach it.

### What happens to a SAP SuccessFactors connection when someone leaves?

Offboarding a person in Elaichi ends their access to SAP SuccessFactors through every client at once. A shared SAP SuccessFactors connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting SAP SuccessFactors once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.

### Does the SAP SuccessFactors MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. SAP SuccessFactors is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

## All 32 SAP SuccessFactors tools

Every tool below is callable through https://api.elaichi.ai/mcp once SAP SuccessFactors is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all SAP SuccessFactors odata per persons** (List). List SuccessFactors `PerPerson` records from `/odata/v2/PerPerson`. You can use this OData API to display non-effective-dated biological information about an employee such as date and place of birth, and date of death. Key `personIdExternal`. Delta queries on `lastModifiedDateTime`.
Returns `personIdExternal`, `dateOfBirth`, `homeAddressNavDEFLT`, `perPersonUuid`, `personId`, `createdBy` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/PerPerson/$metadata`.
- **List all SAP SuccessFactors odata per personals** (List). List SuccessFactors `PerPersonal` records from `/odata/v2/PerPersonal`. Key `personIdExternal + startDate`. Effective-dated (one row per time slice; defaults to today, use `fromDate`/`toDate` for history). Delta queries on `lastModifiedDateTime`.
Returns `personIdExternal`, `startDate`, `aboriginalPerson`, `birthNameAlt1`, `certificateEndDate`, `certificateStartDate` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/PerPersonal/$metadata`.
- **List all SAP SuccessFactors odata per emails** (List). List SuccessFactors `PerEmail` records from `/odata/v2/PerEmail`. This PerEmail API enables you to read, update, create, or delete an employee's email address. Key `personIdExternal + emailType`. Delta queries on `lastModifiedDateTime`.
Returns `personIdExternal`, `emailType`, `emailAddress`, `isPrimary`, `operation`, `createdBy` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/PerEmail/$metadata`.
- **List all SAP SuccessFactors odata per phones** (List). List SuccessFactors `PerPhone` records from `/odata/v2/PerPhone`. This entity contains an employee's phone numbers. Key `personIdExternal + phoneType`. Delta queries on `lastModifiedDateTime`.
Returns `personIdExternal`, `phoneType`, `areaCode`, `countryCode`, `extension`, `isPrimary` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/PerPhone/$metadata`.
- **List all SAP SuccessFactors odata per address deflts** (List). List SuccessFactors `PerAddressDEFLT` records from `/odata/v2/PerAddressDEFLT`. The PerAddressDEFLT contains information about a person's addresses. Effective-dated (one row per time slice; defaults to today, use `fromDate`/`toDate` for history). Delta queries on `lastModifiedDateTime`.
Returns `address1`, `address1Alt1`, `address3`, `address5`, `addressType`, `city` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/PerAddressDEFLT/$metadata`.
- **List all SAP SuccessFactors odata per national IDS** (List). List SuccessFactors `PerNationalId` records from `/odata/v2/PerNationalId`. This entity contains national identification card information for an employee. Key `personIdExternal + country + cardType`. Delta queries on `lastModifiedDateTime`.
Returns `personIdExternal`, `country`, `cardType`, `isPrimary`, `nationalId`, `notes` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/PerNationalId/$metadata`.
- **List all SAP SuccessFactors odata per emergency contacts** (List). List SuccessFactors `PerEmergencyContacts` records from `/odata/v2/PerEmergencyContacts`. This entity contains emergency contact information of an employee. Key `personIdExternal + name + relationship`. Delta queries on `lastModifiedDateTime`.
Returns `personIdExternal`, `name`, `relationship`, `operation`. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/PerEmergencyContacts/$metadata`.
- **List all SAP SuccessFactors odata per person relationships** (List). List SuccessFactors `PerPersonRelationship` records from `/odata/v2/PerPersonRelationship`. Key `personIdExternal + relatedPersonIdExternal + startDate`. Effective-dated (one row per time slice; defaults to today, use `fromDate`/`toDate` for history).
Returns `personIdExternal`, `relatedPersonIdExternal`, `startDate`, `endDate`, `firstName`, `isAccompanyingDependent` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/PerPersonRelationship/$metadata`.
- **List all SAP SuccessFactors odata emp employments** (List). List SuccessFactors `EmpEmployment` records from `/odata/v2/EmpEmployment`. The entity contains information such as the termination date, possibility of rehire, payroll information and so on. Key `personIdExternal + userId`. Delta queries on `lastModifiedDateTime`.
Returns `personIdExternal`, `userId`, `StockEndDate`, `assignmentClass`, `assignmentIdExternal`, `benefitsEligibilityStartDate` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/EmpEmployment/$metadata`.
- **List all SAP SuccessFactors odata emp jobs** (List). List SuccessFactors `EmpJob` records from `/odata/v2/EmpJob`. Key `userId + startDate + seqNumber`. Effective-dated (one row per time slice; defaults to today, use `fromDate`/`toDate` for history). Delta queries on `lastModifiedDateTime`.
Returns `userId`, `startDate`, `seqNumber`, `company`, `eventReason`, `managerId` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/EmpJob/$metadata`.
- **List all SAP SuccessFactors odata emp job relationships** (List). List SuccessFactors `EmpJobRelationships` records from `/odata/v2/EmpJobRelationships`. Key `userId + relationshipType + startDate`. Effective-dated (one row per time slice; defaults to today, use `fromDate`/`toDate` for history). Delta queries on `lastModifiedDateTime`.
Returns `userId`, `relationshipType`, `startDate`, `attachment`, `attachmentFileName`, `attachmentFileSize` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/EmpJobRelationships/$metadata`.
- **List all SAP SuccessFactors odata emp compensations** (List). List SuccessFactors `EmpCompensation` records from `/odata/v2/EmpCompensation`. This entity contains information about compensation for an employee. Key `userId + startDate + seqNumber`. Effective-dated (one row per time slice; defaults to today, use `fromDate`/`toDate` for history). Delta queries on `lastModifiedDateTime`.
Returns `userId`, `startDate`, `seqNumber`, `benefitsRate`, `bonusTarget`, `endDate` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/EmpCompensation/$metadata`.
- **List all SAP SuccessFactors odata emp pay comp recurrings** (List). List SuccessFactors `EmpPayCompRecurring` records from `/odata/v2/EmpPayCompRecurring`. Key `userId + payComponent + startDate + seqNumber`. Effective-dated (one row per time slice; defaults to today, use `fromDate`/`toDate` for history). Delta queries on `lastModifiedDateTime`.
Returns `userId`, `payComponent`, `startDate`, `seqNumber`, `currencyCode`, `effectiveLatestChange` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/EmpPayCompRecurring/$metadata`.
- **List all SAP SuccessFactors odata emp pay comp non recurrings** (List). List SuccessFactors `EmpPayCompNonRecurring` records from `/odata/v2/EmpPayCompNonRecurring`. This entity contains information about nonrecurring components of an employee's pay. Key `userId + payComponent + startDate + seqNumber`. Delta queries on `lastModifiedDateTime`.
Returns `userId`, `payComponent`, `startDate`, `seqNumber`, `value`, `employmentNav`. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/EmpPayCompNonRecurring/$metadata`.
- **List all SAP SuccessFactors odata emp employment terminations** (List). List SuccessFactors `EmpEmploymentTermination` records from `/odata/v2/EmpEmploymentTermination`. This entity contains employment or global assignment termination information for an employee. Key `personIdExternal + userId + endDate`. Delta queries on `lastModifiedDateTime`.
Returns `personIdExternal`, `userId`, `endDate`, `StockEndDate`, `benefitsEndDate`, `bonusPayExpirationDate` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/EmpEmploymentTermination/$metadata`.
- **List all SAP SuccessFactors odata fo companies** (List). List SuccessFactors `FOCompany` records from `/odata/v2/FOCompany`. The FOCompany entity represents the Generic Object Legal Entity. Key `externalCode + startDate`. Effective-dated (one row per time slice; defaults to today, use `fromDate`/`toDate` for history).
Returns `externalCode`, `startDate`, `country`, `currency`, `defaultLocation`, `defaultPayGroup` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/FOCompany/$metadata`.
- **List all SAP SuccessFactors odata fo locations** (List). List SuccessFactors `FOLocation` records from `/odata/v2/FOLocation`. This entity contains a company location. Key `externalCode + StartDate`. Effective-dated (one row per time slice; defaults to today, use `fromDate`/`toDate` for history). Delta queries on `lastModifiedDateTime`.
Returns `externalCode`, `StartDate`, `addressNavDEFLT`, `description`, `endDate`, `geozoneFlx` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/FOLocation/$metadata`.
- **List all SAP SuccessFactors odata fo departments** (List). List SuccessFactors `FODepartment` records from `/odata/v2/FODepartment`. The FODepartment entity represents the Generic Object Department. Key `externalCode + startDate`. Effective-dated (one row per time slice; defaults to today, use `fromDate`/`toDate` for history).
Returns `externalCode`, `startDate`, `costCenter`, `description`, `description_defaultValue`, `description_localized` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/FODepartment/$metadata`.
- **List all SAP SuccessFactors odata fo divisions** (List). List SuccessFactors `FODivision` records from `/odata/v2/FODivision`. The FODivision entity represents the Generic Object Division. Key `externalCode + startDate`. Effective-dated (one row per time slice; defaults to today, use `fromDate`/`toDate` for history).
Returns `externalCode`, `startDate`, `description`, `description_defaultValue`, `description_localized`, `endDate` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/FODivision/$metadata`.
- **List all SAP SuccessFactors odata fo business units** (List). List SuccessFactors `FOBusinessUnit` records from `/odata/v2/FOBusinessUnit`. The FOBusinessUnit entity represents the Generic Object Business Unit. Key `externalCode + startDate`. Effective-dated (one row per time slice; defaults to today, use `fromDate`/`toDate` for history).
Returns `externalCode`, `startDate`, `description`, `description_defaultValue`, `description_localized`, `endDate` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/FOBusinessUnit/$metadata`.
- **List all SAP SuccessFactors odata fo cost centers** (List). List SuccessFactors `FOCostCenter` records from `/odata/v2/FOCostCenter`. The FOCostCenter entity represents the Generic Object Cost Center. Key `externalCode + startDate`. Effective-dated (one row per time slice; defaults to today, use `fromDate`/`toDate` for history).
Returns `externalCode`, `startDate`, `businessUnitFlx`, `costcenterManager`, `description`, `endDate` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/FOCostCenter/$metadata`.
- **List all SAP SuccessFactors odata fo pay groups** (List). List SuccessFactors `FOPayGroup` records from `/odata/v2/FOPayGroup`. The FOPayGroup entity represents the Generic Object Pay Group. Key `externalCode + startDate`. Effective-dated (one row per time slice; defaults to today, use `fromDate`/`toDate` for history).
Returns `externalCode`, `startDate`, `dataDelimiter`, `decimalPoint`, `description`, `description_defaultValue` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/FOPayGroup/$metadata`.
- **List all SAP SuccessFactors odata fo job codes** (List). List SuccessFactors `FOJobCode` records from `/odata/v2/FOJobCode`. The FO JobCode entity represents the Generic Object Job Classification. Key `externalCode + startDate`. Effective-dated (one row per time slice; defaults to today, use `fromDate`/`toDate` for history).
Returns `externalCode`, `startDate`, `defaultEmployeeClass`, `defaultJobLevel`, `defaultSupervisorLevel`, `description` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/FOJobCode/$metadata`.
- **List all SAP SuccessFactors odata fo job functions** (List). List SuccessFactors `FOJobFunction` records from `/odata/v2/FOJobFunction`. The FOJobFunction entity represents the Generic Object Job Function. Key `externalCode + startDate`. Effective-dated (one row per time slice; defaults to today, use `fromDate`/`toDate` for history).
Returns `externalCode`, `startDate`, `description`, `description_defaultValue`, `description_localized`, `endDate` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/FOJobFunction/$metadata`.
- **List all SAP SuccessFactors odata fo pay grades** (List). List SuccessFactors `FOPayGrade` records from `/odata/v2/FOPayGrade`. You can use this entity to define a pay level for employees. Key `externalCode + startDate`. Effective-dated (one row per time slice; defaults to today, use `fromDate`/`toDate` for history). Delta queries on `lastModifiedDateTime`.
Returns `externalCode`, `startDate`, `companyFlx`, `currency`, `description`, `endDate` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/FOPayGrade/$metadata`.
- **List all SAP SuccessFactors odata fo event reasons** (List). List SuccessFactors `FOEventReason` records from `/odata/v2/FOEventReason`. Key `externalCode + startDate`. Effective-dated (one row per time slice; defaults to today, use `fromDate`/`toDate` for history). Delta queries on `lastModifiedDateTime`.
Returns `externalCode`, `startDate`, `annualizationFactor`, `description`, `emplStatus`, `event` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/FOEventReason/$metadata`.
- **List all SAP SuccessFactors odata employee times** (List). List SuccessFactors `EmployeeTime` records from `/odata/v2/EmployeeTime`. You can use this API to manage employee absences such as vacation, sick leave, and other paid time off.
Returns `absenceDayClassification`, `absenceDurationCategory`, `approvalStatus`, `cancellationWorkflowRequestId`, `comment`, `countryExtensionITA` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/EmployeeTime/$metadata`.
- **List all SAP SuccessFactors odata time accounts** (List). List SuccessFactors `TimeAccount` records from `/odata/v2/TimeAccount`. When an employee has a time profile assigned with time types that refer to time account types, time accounts need to be created.
Returns `accountClosed`, `accountType`, `bookingEndDate`, `bookingStartDate`, `endDate`, `externalCode` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/TimeAccount/$metadata`.
- **List all SAP SuccessFactors odata time account details** (List). List SuccessFactors `TimeAccountDetail` records from `/odata/v2/TimeAccountDetail`. The entity describes account bookings resulting from different scenarios such as leave request creation or manual adjustments.
Returns `TimeAccount_externalCode`, `accrualPeriodId`, `advanced`, `bookingAmount`, `bookingDate`, `bookingType` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/TimeAccountDetail/$metadata`.
- **List all SAP SuccessFactors odata time types** (List). List SuccessFactors `TimeType` records from `/odata/v2/TimeType`. A time type is created for each type of leave. You can use this entity to read the time types created.
Returns `absenceClass`, `absenceCountingConfiguration`, `absenceRequestingWithinFlextimeBandwidthAllowed`, `absenceRetentionGroup`, `absenceSource`, `accrualRecalculationRelevance` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/TimeType/$metadata`.
- **List all SAP SuccessFactors odata time type profiles** (List). List SuccessFactors `TimeTypeProfile` records from `/odata/v2/TimeTypeProfile`. You can use this entity to view the time type profile of an employee. You specify which time types the employee is allowed to take.
Returns `availableAllowanceTypes`, `availableTimeTypes`, `bookTimeOffInLieuOnTimeSheetApproval`, `bookWorkingTimeOnTimeSheetApproval`, `country`, `defaultImportAttendanceTimeType` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/TimeTypeProfile/$metadata`.
- **List all SAP SuccessFactors odata employee time sheets** (List). List SuccessFactors `EmployeeTimeSheet` records from `/odata/v2/EmployeeTimeSheet`. This entity contains information related to a time sheet of an employee, including the time recording method and the time valuation rules.
Returns `absencesExist`, `allowance`, `approvalStatus`, `comment`, `editable`, `employeeTimeSheetEntry` and more. Dates are OData V2 Microsoft-JSON (`/Date(ms)/`), not ISO-8601; the full per-tenant field set, `cust_*` included, is in `/odata/v2/EmployeeTimeSheet/$metadata`.