3.3.1 Attribute Mappings for the 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.

Table 3-3 lists the user-specific attribute mappings between the process form fields in Oracle Identity Governance and Cerner target application 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 Creating a Target Application in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-3 Default Attributes for Cerner Target Application

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Provision Field?	Recon Field?	Key Field?	Case Insensitive?
Cerner ID	__UID__	String	No	No	Yes	Yes	No
User Name	__NAME__	String	No	Yes	Yes	No	Not applicable
Password	__PASSWORD__	String	No	Yes	No	No	Not applicable
First Name	firstName	String	No	Yes	Yes	No	Not applicable
Last Name	lastName	String	No	Yes	Yes	No	Not applicable
Middle Name	middleName	String	No	Yes	Yes	No	Not applicable
Suffix	suffix	String	No	Yes	Yes	No	Not applicable
Title	title	String	No	Yes	Yes	No	Not applicable
PhysicianInd	physicianInd	String	No	Yes	Yes	No	Not applicable
Gender	gender	String	No	Yes	Yes	No	Not applicable
DirectoryIndicator	directoryIndicator	String	No	Yes	Yes	No	Not applicable
LogicalDomain	logicalDomain	String	No	Yes	Yes	No	Not applicable
Birth Date	birthdate	Date	No	Yes	Yes	No	Not applicable
Begin Effective DateTime	beginEffectiveDateTime	Date	No	Yes	Yes	No	Not applicable
End EffectiveDateTime	endEffectiveDateTime	Date	No	Yes	Yes	No	Not applicable
Position	position	String	No	Yes	Yes	No	Not applicable
Status	__ENABLE__	String	No	No	Yes	No	Not applicable
Server		Long	Yes	No	Yes	Yes	No

Figure 3-1 shows the default User account attribute mappings.

Figure 3-1 Default Attribute Mappings for Cerner User Account

Cerner Organization Entitlement

Table 3-4 lists the attribute mappings for Organization between the process form fields in Oracle Identity Governance and Cerner target application 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 in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-4 Default Attribute Mappings for Organization

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Recon Field?	Key Field?	Case Insensitive?
Organization Name	organization~__ORGANIZATION__~organizationName	String	No	Yes	Yes	No

Figure 3-2 shows the default Organization entitlement mapping.

Figure 3-2 Default Attribute Mapping for Cerner Organization

Cerner Personal Group Entitlement

Table 3-5 lists the attribute mappings for Personal Group between the process form fields in Oracle Identity Governance and Cerner target application 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 in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-5 Default Attribute Mappings for Personal Group

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Recon Field?	Key Field?	Case Insensitive?
Personal Group Name	personnelGroup~__PERSONNALGROUP__~personnelGroupName	String	No	Yes	Yes	No

Figure 3-3 shows the default Personal Group entitlement mapping.

Figure 3-3 Default Attribute Mapping for Personal Group

Cerner Organization Group Entitlement

Table 3-6 lists the attribute mappings for Organization Group between the process form fields in Oracle Identity Governance and Cerner target application 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 in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-6 Default Attribute Mappings for Organization Group

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Recon Field?	Key Field?	Case Insensitive?
Organization Group Name	organizationGroup~__ORGANIZATION__~organizationGroupName	String	No	Yes	Yes	No

Figure 3-4 shows the default Organization Group entitlement mapping.

Figure 3-4 Default Organization Group entitlement mapping

Cerner Personal Alias Entitlement

Table 3-7 lists the attribute mappings for Personal Alias between the process form fields in Oracle Identity Governance and Cerner target application 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 in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-7 Default Attribute Mappings for Personal Alias

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Recon Field?	Key Field?	Case Insensitive?
AliasID	alias~__ALIAS__~toPsoID	String	No	Yes	Yes	No
Alias Pool	alias~__ALIAS__~aliasPool	String	No	Yes	No	Not applicable
Alias Type	alias~__ALIAS__~type	String	No	Yes	No	Not applicable
Alias	alias~__ALIAS__~alias	String	No	Yes	Yes	No
BeginEffectiveDateTime	alias~__ALIAS__~beginEffectiveDateTime	Date	No	Yes	No	Not applicable
EndEffectiveDateTime	alias~__ALIAS__~endEffectiveDateTime	Date	No	Yes	No	No applicable

Figure 3-5 shows the default Personal Alias entitlement mapping.

Figure 3-5 Default Attribute Mapping for Cerner Personal Alias

Cerner PPR Access Entitlement

Table 3-8 lists the attribute mappings for PPR Access between the process form fields in Oracle Identity Governance and Cerner target application 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 in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-8 Default Attribute Mappings for PPR Access

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Recon Field?	Key Field?	Case Insensitive?
PPR Access Name	pprAccess~__PPRACCESS__~pprAccessName	String	No	Yes	Yes	No

Figure 3-6 shows the default PPR Access mapping.

Figure 3-6 Default PPR Access Mapping

Cerner Taxonomy

Table 3-9 lists the attribute mappings for Taxonomy between the process form fields in Oracle Identity Governance and Cerner tar get application 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 in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-9 Default Attribute Mappings for Taxonomy

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Recon Field?	Key Field?	Case Insensitive ?
TaxonomyPsoID	taxonomyFields~__TAXONOMY__~toPsoID	String	No	Yes	No	Not Applicable
Taxonomy Id	taxonomyFields~__TAXONOMY__~taxonomyId	String	No	Yes	Yes	No
Taxonomy Type	taxonomyFields~__TAXONOMY__~taxonomyType	String	No	Yes	No	Not Applicable
BeginEffectiveDateTime	taxonomyFields~__TAXONOMY__~beginEffectiveDateTime	Date	No	Yes	No	Not Applicable
EndEffectiveDateTime	taxonomyFields~__TAXONOMY__~endEffectiveDateTime	Date	No	Yes	No	Not Applicable

Figure 3-7 shows the default taxonomy mapping.

Figure 3-7 Default Taxonomy Mapping

Cerner Secure Email

Table 3-10 lists the attribute mappings for Secure Email between the process form fields in Oracle Identity Governance and Cerner target application 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 in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-10 Default Attribute Mappings for Secure Email

DisplayName	TargetAttribute	Data Type	Mandatory Provisioning Property?	ReconField?	Key Field?	Case Insensitive?
EmailPsoID	secureEmail~__SECUREEMAIL__~toPsoID	String	No	Yes	No	Not Applicable
Address	secureEmail~__SECUREEMAIL__~address	String	No	Yes	Yes	No
Secure Type	secureEmail~__SECUREEMAIL__~secureType	String	No	Yes	No	Not Applicable

Figure 3-8 shows the default secure email mapping.

Figure 3-8 Default Secure Email Mapping

Cerner Role Profile Entitlement

Table 3-11 lists the attribute mappings for Role Profile between the process form fields in Oracle Identity Governance and Cerner target application 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 in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-11 Default Attribute Mappings for Role Profile

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	ReconField?	Key Field?	Case Insensitive
RolePsoID	roleProfile~__ROLEPROFILE__~toPsoID	String	No	Yes	No	Not Applicable
RoleProfile	roleProfile~__ROLEPROFILE__~position	String	No	Yes	Yes	No
Display	roleProfile~__ROLEPROFILE__~display	String	No	Yes	No	Not Applicable

Figure 3-9 shows the default role profile entitlement mapping.

Figure 3-9 Default Role Profile Entitlement Mapping