PJS_CUSTOM_F
This table contains persistent custom data that has been fully summarized and exists as leaf level data in Essbase.
Details
-
Schema: FUSION
-
Object owner: PJS
-
Object type: TABLE
-
Tablespace: FUSION_TS_TX_DATA
Primary Key
| Name | Columns |
|---|---|
|
PJS_CUSTOM_F_PK |
PROJECT_ELEMENT_ID, PROJECT_ELEMENT_ID_FLAG, TIME_ID, RBS_ELEMENT_ID, RBS_ELEMENT_ID_FLAG, CURRENCY_TYPE, CALENDAR_TYPE |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments | Status |
|---|---|---|---|---|---|---|
| SCENARIO | VARCHAR2 | 10 | Type of data in Essbase whether actuals, current baseline budget, etc. | |||
| PJS_SUMMARY_ID | NUMBER | 18 | The PJS_SUMMARY_ID is used by the transaction system to map a summarization event to a set of data to be summarized. | Active | ||
| PROJECT_ID | NUMBER | 18 | Contains the PROJECT_ID, not the Project Number (SEGMENT1) | Active | ||
| PROJECT_ELEMENT_ID | NUMBER | 18 | Yes | The PROJECT_ELEMENT_ID can be either the TASK_ID or the structure level ELEMENT_ID | Active | |
| PROJECT_ELEMENT_ID_FLAG | VARCHAR2 | 1 | Yes | This flag indicates whether the PROJECT_ELEMENT_ID is an interior node, or a self node (both of which have the same PROJECT_ELEMENT_ID). | Active | |
| TIME_ID | NUMBER | 18 | Yes | Period time ID | Active | |
| RBS_VERSION_ID | NUMBER | 18 | Resource breakdown structure version ID | Active | ||
| RBS_ELEMENT_ID | NUMBER | 18 | Yes | Resource breakdown structure element ID | Active | |
| RBS_ELEMENT_ID_FLAG | VARCHAR2 | 1 | Yes | Inernal flag | Active | |
| CURRENCY_TYPE | VARCHAR2 | 1 | Yes | Currency type | Active | |
| CURRENCY_CODE | VARCHAR2 | 3 | Currency code | Active | ||
| CALENDAR_TYPE | VARCHAR2 | 1 | Yes | Indicates whether PA or GL calendar | Active | |
| CUSTOM1 | NUMBER | Placeholder column used to store measures extracted with the custom PL/SQL API. | Active | |||
| CUSTOM2 | NUMBER | Placeholder column used to store measures extracted with the custom PL/SQL API. | Active | |||
| CUSTOM3 | NUMBER | Placeholder column used to store measures extracted with the custom PL/SQL API. | Active | |||
| CUSTOM4 | NUMBER | Placeholder column used to store measures extracted with the custom PL/SQL API. | Active | |||
| CUSTOM5 | NUMBER | Placeholder column used to store measures extracted with the custom PL/SQL API. | Active | |||
| CUSTOM6 | NUMBER | Placeholder column used to store measures extracted with the custom PL/SQL API. | Active | |||
| CUSTOM7 | NUMBER | Placeholder column used to store measures extracted with the custom PL/SQL API. | Active | |||
| CUSTOM8 | NUMBER | Placeholder column used to store measures extracted with the custom PL/SQL API. | Active | |||
| CUSTOM9 | NUMBER | Placeholder column used to store measures extracted with the custom PL/SQL API. | Active | |||
| CUSTOM10 | NUMBER | Placeholder column used to store measures extracted with the custom PL/SQL API. | Active | |||
| CUSTOM11 | NUMBER | Placeholder column used to store measures extracted with the custom PL/SQL API. | Active | |||
| CUSTOM12 | NUMBER | Placeholder column used to store measures extracted with the custom PL/SQL API. | Active | |||
| CUSTOM13 | NUMBER | Placeholder column used to store measures extracted with the custom PL/SQL API. | Active | |||
| CUSTOM14 | NUMBER | Placeholder column used to store measures extracted with the custom PL/SQL API. | Active | |||
| CUSTOM15 | NUMBER | Placeholder column used to store measures extracted with the custom PL/SQL API. | Active | |||
| LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | Active | ||
| LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | Active | |
| CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | Active | ||
| CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | Active | |
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | Active |