Person Mappings
Map people to their managers and cost centers to add organizational context to AI costs.
Pre-General Availability: 2026-10-27
The following legal notice applies to Oracle pre-GA releases. For copyright and other applicable notices, see Oracle Legal Notices.
Pre-General Availability Draft Documentation Notice
This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.
This documentation is not a commitment by Oracle to deliver any material, code, functionality or services. This documentation, and Oracle Pre-GA programs and services are subject to change at any time without notice and, accordingly, should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality for Oracle’s Pre-GA programs and services remains at the sole discretion of Oracle. All release dates or other predictions of future events are subject to change. The future availability of any future Oracle program or service should not be relied on in entering into any license or service agreement with Oracle.
A person mapping associates an individual's email address with a management hierarchy and cost center. Cost Advisor uses this mapping for per-user costs from OpenAI ChatGPT, Codex, and Work, and Anthropic Enterprise. Select one of two sources: Fusion HCM or a CSV file.
For the recommended setup, also add a project ID mapping for OpenAI API, Anthropic Console, and OCI Generative AI costs. Project ID mapping supports CSV upload only and can be used with either person mapping source. Each mapping supplies its hierarchy independently. See How Cost Advisor Uses the Mappings.
Selecting a Source
- Fusion HCM: Import the supplied HCM Extract template into Fusion HCM and use a dedicated integration account to retrieve employee, manager, and cost center information for person mapping. You don't need to prepare a person mapping CSV file for this source. This option requires HCM preparation and identity domain configuration. See Adding a Person Mapping from Fusion HCM.
- CSV file: Select this option if you don't have Fusion HCM or prefer to upload person and organizational information manually. Supply person, manager, and cost center relationships using the person mapping template. See Adding a Person Mapping from a CSV File.
Person Mapping CSV Fields
Each row maps one person's email address to manager emails and a cost-center code. Use the following fields in the supplied template.
| Field | What to enter |
|---|---|
person_id | The individual's work email address used to identify their per-user costs. Enter an email address rather than an employee number or display name. |
m1 through m11 | Manager email addresses, ordered from the highest level in the hierarchy you provide (m1) to the person's immediate manager in the lowest populated level. Leave the remaining levels blank and keep all columns. |
cost_center_code | The cost-center code to associate with the person. |
For example, for a hierarchy of CEO, vice president, manager, and employee Alex, enter Alex's email in person_id, the CEO's email in m1, the vice president's email in m2, and the manager's email in m3. Leave m4 through m11 blank. The manager fields describe Alex's reporting chain. Alex's own email belongs in person_id.
If this row specifies cost center CC-100, Cost Advisor associates Alex's applicable per-user costs with that cost center and management hierarchy. This person mapping doesn't assign costs from an OpenAI API project that Alex owns. Use a project ID mapping for those costs. See the CSV example in Adding a Person Mapping from a CSV File.
Preparing Mapping Data
Work with the owners of your personnel and cost center information to provide approved data. Use the identifiers and formats required by the supplied extract or CSV template. Include only the information needed for the mapping. For example, a CSV file with extra columns or unsupported details can upload successfully but fails validation.
A CSV file for a person mapping isn't interchangeable with a project ID mapping file or the metadata files used in the EPM application. Use the template for the task you're performing.