1. Tables and Views for Project Management
  2. PJC_TXN_CONTROLS_STAGE

PJC_TXN_CONTROLS_STAGE

PJC_TXN_CONTROLS_STAGE is used for importing transaction controls defined for projects or tasks provided in a comma separated values file. Transaction controls are used to control the expenditure items that are charged to a particular project or task, and whether the items are nonbillable. You can import transaction controls by employee, expenditure category, expenditure type, and nonlabor resource.

Details

  • Schema: FUSION

  • Object owner: PJC

  • Object type: TABLE

  • Tablespace: INTERFACE

Primary Key

Name Columns

PJC_TXN_CONTROLS_STAGE_PK

TXN_CONTROL_ID

Columns

Name Datatype Length Precision Not-null Comments
TXN_CONTROL_ID NUMBER 18 Yes Internal identifier of the transaction control record.
TXN_CTRL_REFERENCE VARCHAR2 240 Yes Transaction Control Reference identifier for which the transaction control applies.
LOAD_STATUS VARCHAR2 10 Load Status of the record.
STATUS_CODE VARCHAR2 1 Status of the transaction control record being processed. Status values are populated by the application during processing and include P for Pending, I for Individual Valid Columns, R for Rejected, and A for Accepted.
PROJECT_NUMBER VARCHAR2 25 Number of the project to which the transaction control applies.
PROJECT_NAME VARCHAR2 240 Name of the project to which the transaction control applies.
PROJECT_ID NUMBER 18 Identifier of the project to which the transaction control applies.
TASK_NUMBER VARCHAR2 100 Number of the task to which the transaction control applies.
TASK_NAME VARCHAR2 255 Name of the task to which the transaction control applies.
TASK_ID NUMBER 18 Identifier of the task to which the transaction control applies.
EXPENDITURE_CATEGORY_NAME VARCHAR2 240 Expenditure category to which the transaction control applies.
EXPENDITURE_CATEGORY_ID NUMBER 18 Internal identifier of the expenditure category to which the transaction control applies.
EXPENDITURE_TYPE VARCHAR2 240 Expenditure type name to which the transaction control applies.
EXPENDITURE_TYPE_ID NUMBER 18 Internal identifier of the expenditure type to which the transaction control applies.
NON_LABOR_RESOURCE VARCHAR2 240 Nonlabor resource to which the transaction control applies.
NON_LABOR_RESOURCE_ID NUMBER 18 Internal identifier of the nonlabor resource to which the transaction control applies.
PERSON_NUMBER VARCHAR2 30 Number of the person to whom the transaction control applies.
PERSON_NAME VARCHAR2 2000 Full name of the person to which the transaction control applies.
PERSON_ID NUMBER 18 Identifier of the person to which the transaction control applies.
PERSON_TYPE_MEANING VARCHAR2 80 Name identifying the type of person to whom the transaction control applies. Valid values are Contingent Worker and Employee.
PERSON_TYPE VARCHAR2 20 Code identifying the type of person to whom the transaction control applies. Valid values are CWK for Contingent Worker and EMP for Employee.
PERSON_EMAILID VARCHAR2 240 Email Id of the person to which the transaction control applies.
JOB_NAME VARCHAR2 240 Job name to which the transaction control applies.
JOB_ID NUMBER 18 Identifier of the job to which the transaction control applies.
ORGANIZATION_NAME VARCHAR2 240 Name of the organization to which the transaction control applies.
ORGANIZATION_ID NUMBER 18 Internal identifier of the organization to which the transaction control applies.
CHARGEABLE_FLAG VARCHAR2 1 Indicates whether the expenditure items that apply to the transaction control are chargeable.
BILLABLE_FLAG VARCHAR2 1 Indicates whether the expenditure items that apply to the transaction control are nonbillable, or if their billable status is determined from the task.
CAPITALIZABLE_FLAG VARCHAR2 1 Indicates whether the expenditure items that apply to the transaction control are noncapitalizable, or if their capitalizable status is determined from the task.
START_DATE_ACTIVE DATE From date of the transaction control. If no value is provided at the transaction control level, then the from date is set to either the project start date or the task start date depending on whether the transaction control is defined at the project or task levels. If the transaction control is defined at the task level and the task start date is not provided, then the project start date is used.
END_DATE_ACTIVE DATE To date of the transaction control.
LIMIT_TO_TXN_CONTROLS_FLAG VARCHAR2 1 Indicates whether the transaction controls are inclusive or exclusive. Valid values are Y and N.
REQUEST_ID NUMBER 18 Enterprise Service Scheduler: indicates the request ID of the job that created or last updated the row.
JOB_DEFINITION_NAME VARCHAR2 100 Enterprise Service Scheduler: indicates the name of the job that created or last updated the row.
JOB_DEFINITION_PACKAGE VARCHAR2 900 Enterprise Service Scheduler: indicates the package name of the job that created or 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.
LOAD_REQUEST_ID NUMBER 18 Yes Identifier of the ESS job that populated data from the interface table into the database.
LAST_UPDATE_LOGIN VARCHAR2 32 Who column: indicates the session login associated to the user who last updated the row.
CREATED_BY VARCHAR2 64 Yes Who column: indicates the user who created the row.
CREATION_DATE TIMESTAMP Yes Who column: indicates the date and time of the creation of the row.
LAST_UPDATED_BY VARCHAR2 64 Yes Who column: indicates the user who last updated the row.
LAST_UPDATE_DATE TIMESTAMP Yes Who column: indicates the date and time of the last update of the row.

Indexes

Index Uniqueness Tablespace Columns
PJC_TXN_CONTROLS_STAGE_N1 Non Unique Default PROJECT_ID, TASK_ID
PJC_TXN_CONTROLS_STAGE_N2 Non Unique Default PROJECT_NAME, STATUS_CODE
PJC_TXN_CONTROLS_STAGE_U1 Unique Default TXN_CONTROL_ID