4.3 Attribute Mappings for Fusion Apps Authoritative Application

The Schema page for an Authoritative application displays the default schema (provided by the connector) that maps Oracle Identity Governance attributes to target system attributes. The connector uses these mappings during reconciliation.

Below table lists the user-specific attribute mappings between the reconciliation fields in Oracle Identity Governance and target system attributes. The table also lists the data type for a given attribute and specifies whether it is a mandatory attribute for reconciliation.

You may use the default schema that has been set for you or update and change it before continuing to the next step. You can edit the default attribute mappings by adding new attributes or deleting existing attributes as described in Creating an Authoritative Application of Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 4-3 Default Attribute Mappings for Fusion Apps User Account in Authoritative Application

Display Name Target Attribute Data Type Mandatory? Recon Field? Default Value for Identity Display Name
FAAccountID __UID__ String No Yes Not Applicable
User Login __NAME__ String Yes Yes Not Applicable
Email emails.value String No Yes Not Applicable
Status __ENABLE__ String No Yes Not Applicable
Last Name name.familyName String No Yes Not Applicable
First Name name.givenName String No Yes Not Applicable
Display Name displayName String No Yes Not Applicable
Preferred Language preferredLanguage String No Yes Not Applicable
Gender legislativeInfo.Gender String No Yes Not Applicable
PersonID PersonId String No Yes Not Applicable
Employee Number workerInformation.personNumber String No Yes Not Applicable
Manager Login workerInformation.manager String No Yes Not Applicable
Job workerInformation.job String No Yes Not Applicable
Common Name workerInformation.businessUnit String No Yes Not Applicable
Department Number workerInformation.department String No Yes Not Applicable
Mobile phones.PhoneNumber String No Yes Not Applicable
Telephone Number phones.Extension String No Yes Not Applicable
Generation Qualifier workRelationships.LegalEmployerName String No Yes Not Applicable
User Type workRelationships.assignments.UserPersonType String No Yes Not Applicable
Hire Date names.EffectiveStartDate String No Yes Not Applicable
Start Date workRelationships.StartDate String No Yes Not Applicable
End Date workRelationships.TerminationDate String No Yes Not Applicable
Job Start Date workRelationships.assignments.EffectiveStartDate String No Yes Not Applicable
Job End Date workRelationships.assignments.EffectiveEndDate String No Yes Not Applicable
Title workRelationships.assignments.PositionCode String No Yes Not Applicable
GradeCode workRelationships.assignments.GradeCode String No Yes Not Applicable
Locality Name workRelationships.assignments.LocationCode String No Yes Not Applicable
ManagerId workRelationships.assignments.managers.ManagerAssignmentNumber String No Yes Not Applicable
Country addresses.Country String No Yes Not Applicable
Postal Address addresses.TownOrCity String No Yes Not Applicable
PO Box addresses.Building String No Yes Not Applicable
Floor addresses.FloorNumber String No Yes Not Applicable
Home Postal Address addresses.AddressLine1 String No Yes Not Applicable
State addresses.Region1 String No Yes Not Applicable
Postal Code addresses.PostalCode String No Yes Not Applicable
Xellerate Type   String No Yes End-User
Organization Name   String No Yes Xellerate Users
Role   String No Yes Full-Time

Following figure shows the default User account attribute mappings.

Figure 4-1 Default Attribute Mappings for Fusion Apps User Account in Authoritative Application

Default Attribute Mappings for Fusion Apps User Account in Authoritative Application