PJR_SUM_ROLLUP
The PJR_SUM_ROLLUP table contains the data that is aggregated up the resource pool hierarchy. The PJR_RESOURCE_POOLS_B table contains the parent child hierarchy. The PJR_RESOURCE_POOL_ASSIGNMENTS table contains the resource pool structure node for each resource.
Details
-
Schema: FUSION
-
Object owner: PJR
-
Object type: TABLE
-
Tablespace: FUSION_TS_TX_DATA
Primary Key
| Name | Columns |
|---|---|
|
PJR_SUM_ROLLUP_PK |
ENTERPRISE_ID, RESOURCE_POOL_ID, RESOURCE_ID, ASSIGNMENT_ID, TXN_DATE, ROLLUP_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| ENTERPRISE_ID | NUMBER | 18 | Yes | Enterprise identifier that uniquely identifies a tenant in a multi-tenant environment. | |
| RESOURCE_POOL_ID | NUMBER | 18 | Yes | A particular node in the resource pool structure. | |
| RESOURCE_ID | NUMBER | 18 | Yes | A resource associated to a resource pool structure node. | |
| ASSIGNMENT_ID | NUMBER | 18 | Yes | Assignment of a resource who is associated with a resource pool structure node. | |
| TXN_DATE | DATE | Yes | A date on which a resource has available hours, target hours, projected hours, or any combination of those hours. | ||
| ROLLUP_ID | NUMBER | 18 | Yes | Distinguishes rows with the same attributes that are inserted concurrently by different process instances. | |
| WEEK8_FLAG | VARCHAR2 | 1 | Indicates that a date is within the next 8 weeks starting from the previous Sunday. The date can represent available, target, or projected hours for a resource. Values are Yes and No. | ||
| WEEK4_FLAG | VARCHAR2 | 1 | Indicates that a date is within the next 4 weeks starting from the previous Sunday. The date can represent available, target, or projected hours for a resource. Values are Yes and No. | ||
| WEEK2_FLAG | VARCHAR2 | 1 | Indicates that a date is within the next 2 weeks starting from the previous Sunday. The date can represent available, target, or projected hours for a resource. Values are Yes and No. | ||
| WEEK1_FLAG | VARCHAR2 | 1 | Indicates that a date is within the current week starting from the previous Sunday. The date can represent available, target, or projected hours for a resource. Values are Yes and No. | ||
| AVAILABLE_HOURS | NUMBER | Hours that a resource is available to work on project assignments and nonproject events. Determined by the availability cache for a resource. | |||
| TARGET_HOURS | NUMBER | Target hours that a resource is expected to work. Calculated by multiplying target utilization by available hours. | |||
| PROJECTED_HOURS | NUMBER | Hours that a resource is assigned to project work in the future. Determined by the project resource assignments for a resource. | |||
| LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
| LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
| CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
| CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
| OBJECT_VERSION_NUMBER | NUMBER | 9 | Yes | Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried. | |
| BILLABLE_PROJECTED_HOURS | NUMBER | Number of hours the resource is projected to work on billable project assignments. |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| PJR_SUM_ROLLUP_U1 | Unique | FUSION_TS_TX_IDX | ENTERPRISE_ID, RESOURCE_POOL_ID, RESOURCE_ID, ASSIGNMENT_ID, TXN_DATE, ROLLUP_ID |