Oracle Fusion ERP integration, REST API - Integration Data schema

The Oracle Fusion ERP schema of the integration data defines what data is imported within the integration.

In this section:

  • Account
  • Permission Types
    • Role
    • DataSecurity

Account

The user objects are imported from Oracle Fusion ERP and displayed as the Account objects in ObserveID. The attributes of users are displayed as Additional Properties objects of the Account.

Account Property

Type

Description

Id

String

The unique identifier of the user.

Description

String

 

Category

String

 

Location

String

 

CreatedAt

DateTime

The date and time when the user was created.

LastModifiedAt

DateTime

The date and time when the user was modified last time.

ExternalId

String

An external identifier for the user, which is defined by the web service consumer.

FirstName

String

Required. The first name of the user.

LastName

String

Required. The last name of the user.

PreferredLanguage

String

Preferred Language.

Emails

Strings

The e-mail addresses of the user. The service provider uses canonical form of these addresses, for example, [email protected] instead of [email protected]. Canonical type values are work, home, and other.

UserCategory

String

User Category associated with a User.

AssignServiceAdminRoles

Boolean

Assign Service Admin Roles to user

AccountType

String

Provides Info if a user has a Person or Party association.

EnableTwoFactorAuthentication

String

Enable Two factor authentication to user.

PartyNumber

String

PartyNumber associated with a User.

PartyUsage

String

Party Usage Code associated with a user example:Supplier Contact,Partner Contact,Customer Contact.

PersonNumber

String

Person Number associated to a User.

Manager

String

Manager associated to the worker.

Job

String

Job Associated to the worker.

BusinessUnit

String

BusinessUnit associated to the worker.

Department

String

Party Usage Code associated with a user example:Supplier Contact,Partner Contact,Customer Contact.

Permission Types

The table below provides a list of schema attributes imported from Oracle Fusion ERP and defining the permissions according to their permission type. The attributes are stored in ObserveID as Additional Properties of the permissions of the respective permission types.

Permission Property

Type

Description

Role

Id

String

A unique identifier for the user, which is defined by the web service provider.

Description

String

Description of the Fusion Application Role.

Category

String

Category of the Fusion Application Role.

Location

String

 

CreatedAt

DateTime

The date and time when the role was created.

LastModifiedAt

DateTime

The date and time when the role was modified.

ExternalId

String

An external identifier for the role, which is defined by the web service consumer.

FirstName

String

 

LastName

String

 

PreferredLanguage

String

 

Emails

String

 

UserCategory

String

 

AssignServiceAdminRoles

Boolean

 

AccountType

String

 

EnableTwoFactorAuthentication

String

 

PartyNumber

String

 

PartyUsage

String

 

PersonNumber

String

 

Manager

String

 

Job

String

 

BusinessUnit

String

 

Department

String

 

DataSecurity

SecurityContextValue

String

The value of the security context associated with a role. For example, for a specific business unit, a financials job role is assigned the security context of that business unit. This value can be used as a criteria for assigning data access to a user name. This is the value for a single-part security context or the value for the first part of a multi-part context.

SecurityContextValue2

String

The value of the security context associated with a role. For example, for a specific business unit, a financials job role is assigned the security context of that business unit. This value can be used as a criteria for assigning data access to a user name. This is the value for the second part of a multi-part context.

SecurityContextValue3

String

The value of the security context associated with a role. For example, for a specific business unit, a financials job role is assigned the security context of that business unit. This value can be used as a criteria for assigning data access to a user name. This is the value for the third part of a multi-part context.