Oracle International Corporation

John Neil Thuringer

Neil Bristow

Ram Razdan

Simon Jones

Himavantha Rao Sajja

Nigel Paul King

Neil Ramsay

Jon MacGoy

Roderic Michael Fine

Daniela Kantorova

Irene Gonzalez

Adrian Hunter

Daniel Matlin

Seamus Moran

A three-tier employment model provides flexibility when modeling even moderately complex relationships, such as where an employee has multiple job tasks or assignments for an employer. In such an example, a top level can store information for each employee defining the type of relationship that exists between the employee and the employer, such as where the employee works for multiple entities of the employer. A middle level can capture employment terms and conditions that are associated with the relationship(s), as well as one or many work assignments, such as salary information for each assignment. A bottom level can store the actual details of the work to be performed. A three-tier approach thus provides significant flexibility in modeling the employment of a person for an enterprise, and allows companies and enterprises to easily record the reality of their complex work relationships.

Multi-tier employment model for human capital management

Systems, methods, and machine-readable memories are provided for partitioning a multi-tenant database between tenants. A first level partition of data in a table within the database is defined. A second level partition of the data in the table within the database is defined. A request is received from an entity associated with a tenant to access a first datum stored in the database. The tenant is determined to be assigned to one or both of the first level partition and the second level partition. Access to the first datum is granted to a first entity where the tenant corresponds to the first tenant and the first datum corresponds to the first level partition parameter value. Access to the first datum is granted to a second entity where the tenant corresponds to the second tenant and the first datum corresponds to the second level partition parameter value.

Systems, methods, and machine-readable memories for partitioning a database

Techniques implementable in an enterprise application or application suite for managing the organizational structure of an enterprise. In one set of embodiments, a single, unified hierarchy can be defined for the organizational structure of an enterprise. The unified hierarchy can include high-level nodes that correspond to entities common to different manifestations of the organizational structure (e.g., reporting structure, cost structure, etc.). The unified hierarchy can also include lower-level nodes that are unique to a particular manifestation. By defining a single, unified hierarchy in this manner, organizational changes in the enterprise can be modeled in the application/application suite by simply updating the unified hierarchy (rather than updating multiple hierarchies). In addition, the unified hierarchy can be used to facilitate security provisioning and reporting.

Enterprise hierarchy

The invention is directed towards a method of partitioning data in a database. The database is configured to be accessed by an entity. The method comprises the steps of defining a first partition within the database, defining a second partition within the database and assigning selected data in the database to the first partition and the second partition, wherein data assigned to both the first partition and the second partition may only be accessed by an entity assigned to both said first partition and said second partition.

Method of partitioning a database

Growing community of inventors

Middlesex, United Kingdom

John Neil Thuringer