PJC_TRANSACTION_CONTROLS
PA_TRANSACTION_CONTROLS stores the transaction controls defined for projects or tasks. Transaction controls are used to control what expenditure items can be charged to a particular project or task, and whether the items are non-billable. You can configure transaction controls by employee, expenditure category, expenditure type, and non-labor resource. . .
Details
-
Schema: FUSION
-
Object owner: PJC
-
Object type: TABLE
-
Tablespace: APPS_TS_TX_DATA
Primary Key
| Name | Columns |
|---|---|
|
PJC_TRANSACTION_CONTROLS_PK |
TXN_CONTROL_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| TXN_CONTROL_ID | NUMBER | 18 | Yes | TXN_CONTROL_ID ***** | |
| PROJECT_ID | NUMBER | 18 | Yes | The identifier of the project for which the transaction control applies | |
| TASK_ID | NUMBER | 18 | The identifier of the task for which the transaction control applies | ||
| CHARGEABLE_FLAG | VARCHAR2 | 1 | Yes | Flag that indicates if the expenditure items that apply to the transaction control classification can be charged | |
| BILLABLE_FLAG | VARCHAR2 | 1 | Yes | Flag that indicates if the expenditure items that apply to the transaction control are non-billable, or if their billability is determined from the task ***** | |
| CAPITALIZABLE_FLAG | VARCHAR2 | 1 | CAPITALIZABLE_FLAG ***** | ||
| 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_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. | |
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
| PERSON_ID | NUMBER | 18 | The identifier of the person for which the transaction control applies | ||
| PERSON_TYPE | VARCHAR2 | 20 | PERSON_TYPE ***** | ||
| JOB_ID | NUMBER | 18 | JOB_ID ***** | ||
| ORGANIZATION_ID | NUMBER | 18 | ORGANIZATION_ID ***** | ||
| EXPENDITURE_CATEGORY_ID | NUMBER | 18 | EXPENDITURE_CATEGORY_ID ***** | ||
| EXPENDITURE_TYPE_ID | NUMBER | Identifier of the Expenditure Type. ***** | |||
| NON_LABOR_RESOURCE_ID | NUMBER | 18 | NON_LABOR_RESOURCE_ID ***** | ||
| START_DATE_ACTIVE | DATE | Yes | First effective date of the transaction control | ||
| END_DATE_ACTIVE | DATE | The last effective date of the transaction control | |||
| 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. | |
| RULE_NUMBER | NUMBER | 18 | RULE_NUMBER ***** | ||
| TXN_CTRL_REFERENCE | VARCHAR2 | 240 | Transaction Control Reference identifier for which the transaction control applies. |
Foreign Keys
| Table | Foreign Table | Foreign Key Column |
|---|---|---|
| PJC_TRANSACTION_CONTROLS | pjf_projects_all_b | PROJECT_ID |
| PJC_TRANSACTION_CONTROLS | pjf_proj_elements_b | TASK_ID |
| PJC_TRANSACTION_CONTROLS | pjf_exp_categories_b | EXPENDITURE_CATEGORY_ID |
| PJC_TRANSACTION_CONTROLS | pjf_exp_types_b | EXPENDITURE_TYPE_ID |
| PJC_TRANSACTION_CONTROLS | pjf_non_labor_res_b | NON_LABOR_RESOURCE_ID |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| PJC_TRANSACTION_CONTROLS_U1 | Unique | Default | PROJECT_ID, TASK_ID, PERSON_ID, PERSON_TYPE, JOB_ID, ORGANIZATION_ID, EXPENDITURE_CATEGORY_ID, EXPENDITURE_TYPE_ID, NON_LABOR_RESOURCE_ID, START_DATE_ACTIVE |
| PJC_TRANSACTION_CONTROLS_U2 | Unique | Default | TXN_CONTROL_ID |