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 lists the default attributes for the Cerner target application.

Note:

Alias Pool, Alias Type and Alias are applicable from 12.2.1.3.0A.

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	Yes	Yes	Yes	No	Not applicable
Password	__PASSWORD__	String	No	Yes	No	No	Not applicable
Alias Pool	aliasPool	String	No	Yes	No	No	Not applicable
Alias Type	type	String	No	Yes	No	No	Not applicable
Alias	alias	String	No	Yes	No	No	Not applicable
Person First Name	person.firstName	String	Yes	Yes	Yes	No	Not applicable
Person Last Name	person.lastName	String	Yes	Yes	Yes	No	Not applicable
Person Middle Name	person.middleName	String	No	Yes	Yes	No	Not applicable
Person Suffix	person.suffix	String	No	Yes	Yes	No	Not applicable
Person Title	person.title	String	No	Yes	Yes	No	Not applicable
Personnel First Name	firstName	String	Yes	Yes	Yes	No	Not applicable
Personnel Last Name	lastName	String	Yes	Yes	Yes	No	Not applicable
Personnel Middle Name	middleName	String	No	Yes	Yes	No	Not applicable
Personnel Suffix	suffix	String	No	Yes	Yes	No	Not applicable
Personnel Title	title	String	No	Yes	Yes	No	Not applicable
Physician Indicator	physicianInd	String	No	Yes	Yes	No	Not applicable
Gender	gender	String	No	Yes	Yes	No	Not applicable
Directory Indicator	directoryIndicator	String	No	Yes	Yes	No	Not applicable
Logical Domain	logicalDomain	String	No	Yes	Yes	No	Not applicable
External Indicator	externalInd	String	No	Yes	Yes	No	Not applicable
Email	email	String	No	Yes	Yes	No	Not applicable
Birth Date	birthdate	Date	No	Yes	Yes	No	Not applicable
Begin Effective Dateime	beginEffectiveDateTime	Date	No	Yes	Yes	No	Not applicable
End Effective DateTime	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
Provider Specialty	providerSpecialty	String	No	Yes	Yes	No	Not applicable
Server		Long	Yes	No	Yes	Yes	No
Active Indicator	activeInd	String	No	No	Yes	No	Not applicable
Active Status Code	activeStatusCd	String	No	No	Yes	No	Not applicable
Data Status Code	dataStatusCd	String	No	No	Yes	No	Not applicable

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	Yes	Yes	Yes	No
Confidentiality Level	organization~__ORGANIZATION__~organizationRelationship.confidentialityLevel	String	No	Yes	No	Not Applicable

Figure 3-2 shows the default Organization entitlement mapping.

Figure 3-2 Default Attribute Mapping for Cerner Organization

Cerner Personnel Group Entitlement

Table 3-5 lists the attribute mappings for Personnel 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 Personnel Group

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

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

Figure 3-3 Default Attribute Mapping for Personnel 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	Yes	Yes	Yes	No
Confidentiality Level	organizationGroup~__ORGANIZATION__~organizationGroupRelationship.confidentialityLevel	String	No	Yes	No	Not Applicable

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

Figure 3-4 Default Organization Group entitlement mapping

Cerner Personnel Alias Entitlement

Table 3-7 lists the attribute mappings for Personnel 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 Personnel Alias

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

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

Figure 3-5 Default Attribute Mapping for Cerner Personnel 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~__PPR__~pprAccessName	String	Yes	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 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-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	Yes	Yes	Yes	No
Taxonomy Type	taxonomyFields~__TAXONOMY__~taxonomyType	String	Yes	Yes	No	Not Applicable
Begin Effective DateTime	taxonomyFields~__TAXONOMY__~beginEffectiveDateTime	Date	No	Yes	No	Not Applicable
End Effective DateTime	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	Yes	Yes	Yes	No
Secure Type	secureEmail~__SECUREEMAIL__~secureType	String	Yes	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
Role PsoID	roleProfile~__ROLEPROFILE__~toPsoID	String	No	Yes	No	Not Applicable
Role Profile	roleProfile~__ROLEPROFILE__~position	String	Yes	Yes	Yes	No
Display	roleProfile~__ROLEPROFILE__~display	String	Yes	Yes	No	Not Applicable
Begin Effective DateTime	roleProfile~__ROLEPROFILE__~beginEffectiveDateTime	Date	No	Yes	No	Not Applicable
End Effective DateTime	roleProfile~__ROLEPROFILE__~endEffectiveDateTime	Date	No	Yes	No	Not Applicable

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

Figure 3-9 Default Role Profile Entitlement Mapping

Cerner Location View Entitlement

Table 3-12 lists the attribute mappings for Location View 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.

Default Attribute Mappings for Location View

Table 3-12 Default Attribute Mappings for Location View

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	ReconField?	Key Field?	Case Insensitive
Location View Association Name	locationViewAssociation~__LOCATION__~locationViewAssociationName	String	No	Yes	Yes	No

Figure 3-10 Location View Assocication Name

Cerner Discern User Group Entitlement

Table 3-13 lists the attribute mappings for Discern User 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-13 Default Attribute Mappings for Discern User Group

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	ReconField?	Key Field?	Case Insensitive
Discern Security Group	discernSecurityGroup~__DISCERN__~discernSecurityGroupName	String	Yes	Yes	Yes	No

Figure 3-11 Default Discern User Group Entitlement Mapping

Cerner Personal Role

Table 3-14 lists the attribute mappings for Personal Role 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-14 Default Attribute Mappings for Personal Role

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	ReconField?	Key Field?	Case Insensitive
Personnel Role PsoID	personnelRole~__PERSONNALROLE__~toPsoID	String	No	Yes	No	Not Applicable
Role Type	personnelRole~__PERSONNALROLE__~roletypeCd	String	Yes	Yes	Yes	No
Active Status Ind	personnelRole~__PERSONNALROLE__~activeStatusInd	String	Yes	Yes	No	Not Applicable
Begin Effective DateTime	personnelRole~__PERSONNALROLE__~beginEffectiveDateTime	Date	No	Yes	No	Not Applicable
End Effective DateTime	personnelRole~__PERSONNALROLE__~endEffectiveDateTime	Date	No	Yes	No	Not Applicable

Figure 3-12 Default Personal Role Mapping

Cerner Supervisor Relationship

Table 3-15 lists the attribute mappings for Supervisor Relationship 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-15 Default Attribute Mappings for Supervisor Relationship

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	ReconField?	Key Field?	Case Insensitive
Supervisor Relationship PsoID	supervisorRelationship~__SUPERVISORRELATIONSHIP__~toPsoID	String	No	Yes	No	Not Applicable
Supervisor Personnel Id	supervisorRelationship~__SUPERVISORRELATIONSHIP__~supervisorPersonnelId	String	Yes	Yes	Yes	No
Supervisor Reltn Type Code	supervisorRelationship~__SUPERVISORRELATIONSHIP__~supervisorReltnTypeCd	String	Yes	Yes	No	Not Applicable
Organization Id	supervisorRelationship~__SUPERVISORRELATIONSHIP__~organizationId	String	No	Yes	No	Not Applicable
Begin Effective DateTime	supervisorRelationship~__SUPERVISORRELATIONSHIP__~beginEffectiveDateTime	Date	No	Yes	No	Not Applicable
End Effective DateTime	supervisorRelationship~__SUPERVISORRELATIONSHIP__~endEffectiveDateTime	Date	No	Yes	No	Not Applicable

Figure 3-13 Supervisor Relationship Mapping

Cerner Security Key Chain Entitlement

Table 3-16 lists the attribute mappings for Security Key Chain 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-16 Default Attribute Mappings for Security Key Chain

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	ReconField?	Key Field?	Case Insensitive
Security keychain Id	securityKeyChain~__KEYCHAIN__~keyChainId	String	Yes	Yes	Yes	No

Figure 3-14 Security Key Chain Entitlement

Cerner Address

Table 3-17 lists the attribute mappings for Address 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-17 Default Attribute Mappings for Address

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	ReconField?	Key Field?	Case Insensitive
Address PsoID	address~__ADDRESS__~toPsoID	String	No	Yes	No	Not Applicable
Address Type Code	address~__ADDRESS__~addressTypeCd	String	Yes	Yes	Yes	No
Street Address	address~__ADDRESS__~streetAddr	String	Yes	Yes	No	Not Applicable
Street Address2	address~__ADDRESS__~streetAddr2	String	Yes	Yes	No	Not Applicable
Street Address3	address~__ADDRESS__~streetAddr3	String	Yes	Yes	No	Not Applicable
Street Address4	address~__ADDRESS__~streetAddr4	String	Yes	Yes	No	Not Applicable
City	address~__ADDRESS__~city	String	Yes	Yes	No	Not Applicable
State	address~__ADDRESS__~state	String	Yes	Yes	No	Not Applicable
Zip Code	address~__ADDRESS__~zipCode	String	Yes	Yes	No	Not Applicable
Country	address~__ADDRESS__~countryCd	String	No	Yes	No	Not Applicable
Begin Effective DateTime	address~__ADDRESS__~beginEffectiveDateTime	Date	No	Yes	No	Not Applicable
End Effective DateTime	address~__ADDRESS__~endEffectiveDateTime	Date	No	Yes	No	Not Applicable

Figure 3-15 Default Address mapping

Cerner Phone

Table 3-18 lists the attribute mappings for Phone 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-18 Default Attribute Mappings for Phone

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	ReconField?	Key Field?	Case Insensitive
Phone toPsoID	phone~__PHONE__~toPsoID	String	No	Yes	No	Not Applicable
Phone Number	phone~__PHONE__~phoneNumber	String	Yes	Yes	Yes	No
Phone Type	phone~__PHONE__~phoneType	String	Yes	Yes	No	Not Applicable
Phone Format	phone~__PHONE__~phoneFormat	String	No	Yes	No	Not Applicable
Extension	phone~__PHONE__~extension	String	No	Yes	No	Not Applicable
Contact Code	phone~__PHONE__~contactCd	String	No	Yes	No	Not Applicable
Begin Effective DateTime	phone~__PHONE__~beginEffectiveDateTime	Date	No	Yes	No	Not Applicable
End Effective DateTime	phone~__PHONE__~endEffectiveDateTime	Date	No	Yes	No	Not Applicable

Figure 3-16 Default Phone Mapping

Cerner Credential

Table 3-19 lists the attribute mappings for Credential 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-19 Default Attribute Mappings for Credential

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	ReconField?	Key Field?	Case Insensitive
Credential PsoID	credential~__CREDENTIAL__~toPsoID	String	No	Yes	No	Not Applicable
Credential Name	credential~__CREDENTIAL__~name	String	Yes	Yes	Yes	No
Credential Type	credential~__CREDENTIAL__~type	String	Yes	Yes	No	Not Applicable
Renewal DateTime	credential~__CREDENTIAL__~renewalDateTime	Date	No	Yes	No	Not Applicable
State	credential~__CREDENTIAL__~state	String	Yes	Yes	No	Not Applicable
Id Number	credential~__CREDENTIAL__~idNumber	String	No	Yes	No	Not Applicable
Begin Effective DateTime	credential~__CREDENTIAL__~beginEffectiveDateTime	Date	No	Yes	No	Not Applicable
End Effective DateTime	credential~__CREDENTIAL__~endEffectiveDateTime	Date	No	Yes	No	Not Applicable

Figure 3-17 Default Credential Mapping

Cerner Bedrock Wizards

Table 3-20 lists the attribute mappings for Bedrock Wizards 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.

Default Attribute Mappings for Bedrock Wizards

Table 3-20 Default Attribute Mappings for Bedrock Wizards

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	ReconField?	Key Field?	Case Insensitive
Resource Name	bedrockWizardSecurity~__WIZARDS__~resource	String	No	Yes	Yes	No

Figure 3-18 Default Bedrock Wizards Mapping

Cerner Bedrock Reports

Table 3-21 lists the attribute mappings for Bedrock Reports 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-21 Default Attribute Mappings for Bedrock Reports

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	ReconField?	Key Field?	Case Insensitive
Resource Name	bedrockReportSecurity~__REPORTS__~resource	String	No	Yes	Yes	No

Figure 3-19 Bedrock Reports Mapping

Cerner Eprescribe

Table 3-22 lists the attribute mappings for Eprescribe 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-22 Default Attribute Mappings for Eprescribe

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	ReconField?	Key Field?	Case Insensitive
ToPsoID	eprescribe~__EPRESCRIBE__~toPsoID	String	No	Yes	Yes	No
Location Id	eprescribe~__EPRESCRIBE__~locationId	String	No	Yes	No	Not Applicable
Phone Number	eprescribe~__EPRESCRIBE__~phoneNumber	String	No	Yes	No	Not Applicable
Phone Type	eprescribe~__EPRESCRIBE__~phoneType	String	No	Yes	No	Not Applicable
Phone Format	eprescribe~__EPRESCRIBE__~phoneFormat	String	No	Yes	No	Not Applicable
Fax Phone Number	eprescribe~__EPRESCRIBE__~primaryFax.phoneNumber	String	No	Yes	No	Not Applicable
Fax Phone Type	eprescribe~__EPRESCRIBE__~primaryFax.phoneType	String	No	Yes	No	Not Applicable
Fax Phone Format	eprescribe~__EPRESCRIBE__~primaryFax.phoneFormat	String	No	Yes	No	Not Applicable
Street Addr	eprescribe~__EPRESCRIBE__~streetAddr	String	No	Yes	No	Not Applicable
Address Type code	eprescribe~__EPRESCRIBE__~addressTypeCd	String	No	Yes	No	Not Applicable
Street Addr2	eprescribe~__EPRESCRIBE__~streetAddr2	String	No	Yes	No	Not Applicable
City	eprescribe~__EPRESCRIBE__~city	String	No	Yes	No	Not Applicable
State	eprescribe~__EPRESCRIBE__~state	String	No	Yes	No	Not Applicable
ZipCode	eprescribe~__EPRESCRIBE__~zipCode	String	No	Yes	No	Not Applicable
Alias	eprescribe~__EPRESCRIBE__~alias	String	No	Yes	No	Not Applicable
Eprescribe Type	eprescribe~__EPRESCRIBE__~type	String	No	Yes	No	Not Applicable
Service Level Id	eprescribe~__EPRESCRIBE__~serviceLevelId	String	No	Yes	No	Not Applicable
MessageId	eprescribe~__EPRESCRIBE__~messageId	String	No	Yes	No	Not Applicable
Begin Effective DateTime	eprescribe~__EPRESCRIBE__~beginEffectiveDateTime	Date	No	Yes	No	Not Applicable
End Effective DateTime	eprescribe~__EPRESCRIBE__~endEffectiveDateTime	Date	No	Yes	No	Not Applicable

Figure 3-20 Eprescribe Mappings

Cerner EPCS

Table 3-23 lists the attribute mappings for EPCS 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.

Table 3-23 Default Attribute Mappings for EPCS

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	ReconField?	Key Field?	Case Insensitive
Resource Name	epcsLogicalAccess~__EPCS__~resource	String	No	Yes	Yes	No

Figure 3-21 Default Attribute Mappings for EPCS