3.3 Attribute Mappings for Fusion Apps Target Application

The Schema page for a target 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 and provisioning operations.

Below table lists the user-specific attribute mappings between the process form fields in Oracle Identity Governance and Fusion Apps Connector attributes. The table also lists whether a specific attribute is used during provisioning or reconciliation and whether it is a matching key field for fetching records during reconciliation.

If required, you can edit the default attribute mappings by adding new attributes or deleting existing attributes as described in Creating a Target Application of Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-3 Default Attribute Mappings for Fusion Apps Target User Account

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Provision Field?	Recon Field?	Key Field?	Case Insensitive?
Account Type	userType	String	Yes	Yes	Yes	No	Not applicable
Id	__UID__	String	No	No	Yes	Yes	No
UserName	__NAME__	String	No	Yes	Yes	No	Not applicable
Password	password	String	No	Yes	No	No	Not applicable
Display Name	displayName	String	No	Yes	Yes	No	Not applicable
External Id	externalId	String	No	Yes	Yes	No	Not applicable
Work Email Address	emails.value	String	No	Yes	Yes	No	Not applicable
Emails Address Id	emails.EmailAddressId	String	No	Yes	Yes	No	Not applicable
Email Type	emails.type	String	No	Yes	Yes	No	Not applicable
Active	__ENABLE__	String	No	No	Yes	No	Not applicable
Last Name	name.familyName	String	Yes	Yes	Yes	No	Not applicable
First Name	name.givenName	String	No	Yes	Yes	No	Not applicable
Gender	legislativeInfo.Gender	String	No	No	Yes	No	Not applicable
Preferred Language	preferredLanguage	String	No	No	Yes	No	Not applicable
Last Modified	meta.lastModified	String	No	No	Yes	No	Not applicable
Created	meta.created	String	No	No	Yes	No	Not applicable
Hire Date	workRelationships.StartDate	String	No	No	Yes	No	Not applicable
Person Id	PersonId	String	No	No	Yes	No	Not applicable
Person Number	workerInformation.personNumber	String	No	No	Yes	No	Not applicable
Manager	workerInformation.manager	String	No	No	Yes	No	Not applicable
Worker Type	workRelationships.WorkerType	String	No	Yes	Yes	No	Not applicable
Action Code	workRelationships.assignments.ActionCode	String	No	Yes	Yes	No	Not applicable
Person Name Id	names.PersonNameId	String	No	Yes	Yes	No	Not applicable
Legal Employer Name	workRelationships.LegalEmployerName	String	No	Yes	Yes	No	Not applicable
Legislation Code	names.LegislationCode	String	No	Yes	Yes	No	Not applicable
Primary Phone Id	phones.PhoneId	String	No	Yes	Yes	No	Not applicable
Primary Phone Type	phones.PhoneType	String	No	Yes	Yes	No	Not applicable
Primary Phone Number	phones.PhoneNumber	String	No	Yes	Yes	No	Not applicable
Person Address Usage Id	addresses.PersonAddrUsageId	String	No	Yes	Yes	No	Not applicable
Address Id	addresses.AddressId	String	No	Yes	Yes	No	Not applicable
Address Type	addresses.AddressType	String	No	Yes	Yes	No	Not applicable
Address Line1	addresses.AddressLine1	String	No	Yes	Yes	No	Not applicable
Address Line2	addresses.AddressLine2	String	No	Yes	Yes	No	Not applicable
Floor	addresses.FloorNumber	String	No	Yes	Yes	No	Not applicable
Town Or City	addresses.TownOrCity	String	No	Yes	Yes	No	Not applicable
Region1	addresses.Region1	String	No	Yes	Yes	No	Not applicable
Region2	addresses.Region2	String	No	Yes	Yes	No	Not applicable
Region3	addresses.Region3	String	No	Yes	Yes	No	Not applicable
Postal Code	addresses.PostalCode	String	No	Yes	Yes	No	Not applicable
Country	addresses.Country	String	No	Yes	Yes	No	Not applicable
Period Of Service Id	workRelationships.PeriodOfServiceId	String	No	Yes	Yes	No	Not applicable
Job	workerInformation.job	String	No	No	Yes	No	Not applicable
Start Date	workRelationships.assignments.EffectiveStartDate	String	No	No	Yes	No	Not applicable
End Date	workRelationships.assignments.EffectiveEndDate	String	No	No	Yes	No	Not applicable
Business Unit Id	workRelationships.assignments.BusinessUnitId	String	No	Yes	Yes	No	Not Applicable
Business Unit	workRelationships.assignments.BusinessUnit	String	No	No	Yes	No	Not applicable
Department	workerInformation.department	String	No	No	Yes	No	Not applicable
Grade	workRelationships.assignments.GradeCode	String	No	No	Yes	No	Not applicable
Position	workRelationships.assignments.PositionCode	String	No	No	Yes	No	Not applicable
Location	workRelationships.assignments.LocationCode	String	No	No	Yes	No	Not applicable
Termination Date	workRelationships.TerminationDate	String	No	No	Yes	No	Not applicable
Projected Start Date	workRelationships.assignments.ProjectedStartDate	String	No	Yes	Yes	No	Not applicable
Proposed User Person Type	workRelationships.assignments.ProposedUserPersonType	String	No	Yes	Yes	No	Not applicable
Worker Id	workerId	String	No	Yes	Yes	No	Not applicable
IT Resource Name		Long	No	No	Yes	No	Not applicable

The following figure shows the default User account attribute mappings.

Figure 3-1 Default User Account Attribute Mappings

Fusion Apps Roles Entitlement

Below table lists the Roles form attribute mappings between the process form fields in Oracle Identity Governance and Fusion Apps Connector attributes. The table lists whether a given attribute is mandatory during provisioning. It also lists whether a given attribute is used during reconciliation and whether it is a matching key field for fetching records during reconciliation.

If required, you can edit the default attribute mappings by adding new attributes or deleting existing attributes as described in Creating a Target Application of Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-4 Default Attribute Mappings for Roles

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Recon Field	Key Field?	Case Insensitive?
Role Name	roles~ApplicationRoles~id	String	No	Yes	Yes	No

The following figure shows the default Roles entitlement mapping.

Figure 3-2 Default Attribute Mappings for the Roles

Fusion Apps Phone Numbers Attribute

Below table lists the Phone numbers form attribute mappings between the process form fields in Oracle Identity Governance and Fusion Apps Connector attributes. The table lists whether a given attribute is mandatory during provisioning. It also lists whether a given attribute is used during reconciliation and whether it is a matching key field for fetching records during reconciliation.

If required, you can edit the default attribute mappings by adding new attributes or deleting existing attributes as described in Creating a Target Application of Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-5 Default Attribute Mappings for Phone Number Child Attribute

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Recon Field	Key Field?	Case Insensitive?
Phone Id	phones~PhoneTypes~PhoneId	String	No	Yes	No	Not applicable
Phone Type	phones~PhoneTypes~PhoneType	String	No	Yes	No	Not applicable
Phone Number	phones~PhoneTypes~PhoneNumber	String	No	Yes	Yes	No

The following figure shows the default Phone Numbers child attribute mapping.

Figure 3-3 Default Attribute Mappings for Phone Numbers

Fusion Apps Secondary Emails Attribute

Below table lists the Secondary Emails form attribute mappings between the process form fields in Oracle Identity Governance and Fusion Apps Connector attributes. The table lists whether a given attribute is mandatory during provisioning. It also lists whether a given attribute is used during reconciliation and whether it is a matching key field for fetching records during reconciliation.

If required, you can edit the default attribute mappings by adding new attributes or deleting existing attributes as described in Creating a Target Application of Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-6 Default Attribute Mappings for Secondary Emails Child Attribute

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Recon Field	Key Field?	Case Insensitive?
Email Address Id	emails~__EMAIL__~EmailAddressId	String	No	Yes	No	Not applicable
Email Type	emails~__EMAIL__~EmailType	String	No	Yes	No	Not applicable
Email Address	emails~__EMAIL__~EmailAddress	String	No	Yes	Yes	No

The following figure shows the default Secondary Emails child Attribute mapping.

Figure 3-4 Default Attribute Mappings for Secondary Emails