PJC_BC_PACKETS_H

PJC_BC_PACKETS_H holds all the transactions that copied from GL_BC_PACKETS. This a type of temporary table which holds all the relevant attributes of a transaction in addition to some other attribute values which are derived before they are populated into the project balances tables. Every time funds checking routine is invoked it purges all the records that were created before a specific period of time which is specified by a profile option and provided update budgetary control balances program is run on those records to transfer them to project balances.

Details

  • Schema: FUSION

  • Object owner: PJC

  • Object type: TABLE

  • Tablespace: Default

Primary Key

Name Columns

PJC_BC_PACKETS_H_PK

BC_PACKET_ID

Columns

Name Datatype Length Precision Not-null Comments
PACKET_ID NUMBER 18 Yes Budgetary control packet identifier. *****
DOCUMENT_HEADER_ID NUMBER 18 Yes Document header identifier. *****
DOCUMENT_DISTRIBUTION_ID NUMBER 18 Yes Document distribution identifier. *****
PROJECT_ID NUMBER 18 Yes Project identifier. *****
TASK_ID NUMBER 18 Yes Task identifier. *****
RBS_ELEMENT_ID NUMBER 18 Yes Resource Breakdown Structure element that this transaction maps to. *****
EXPENDITURE_TYPE_ID NUMBER 18 Yes Expenditure type for which this transaction was created. *****
EXPENDITURE_ITEM_DATE DATE Yes Date for which the transaction was charged. *****
ENTERED_DR NUMBER Yes Transaction debit amount in entered currency. *****
ENTERED_CR NUMBER Yes Transaction credit amount in entered currency. *****
ACCOUNTED_DR NUMBER Yes Transaction debit amount in accounting currency. *****
ACCOUNTED_CR NUMBER Yes Transaction credit amount in accounting currency. *****
ACCOUNTED_CURRENCY_CODE VARCHAR2 30 Yes Accounting Currency Code Identifier. *****
ENTERED_CURRENCY_CODE VARCHAR2 30 Yes Entered Currency Code Identifier. *****
ACCOUNTING_LEDGER_ID NUMBER 18 Yes Primary Ledger. *****
TXN_CCID NUMBER 18 Transaction CCID. *****
BC_PACKET_ID NUMBER 18 Yes Budget control record identifier. *****
PARENT_BC_PACKET_ID NUMBER 18 This column is populated if the transaction is a burden cost. It is populated with the bc_packet_id of the source. *****
BURDEN_METHOD_CODE VARCHAR2 10 Yes Indicates the burden method of the project, i.e. SAME, SEPARATE or NONE *****
GL_DATE DATE GL date of the cost transaction. *****
BUDGET_DATE DATE Yes Date used for XCC validation, i.e. PA_DATE or GL_DATE *****
STATUS_CODE VARCHAR2 1 Yes Status of the transaction being processed. *****
BALANCE_TYPE_CODE VARCHAR2 1 Yes Balance Type Identifier (Budget or Actual or Encumbrance). For Projects in Fusion V1.1, balance type is `Actual'. Derive code value from gl balance type. *****
BALANCE_SUBTYPE_ID NUMBER 18 Yes Balance Sub Type Identifier (For Projects V1.1, it is `Expense' while for V1.1+, when Grants is supported, source can also have transactions with balance sub type as `Encumbrance' for `Manual Encumbrance' transactions. Derive id from XCC balance subtype table. *****
BATCH_ID NUMBER 18 Yes Attribute that groups the transactions to be processed together. All transactions in a batch will either pass or fail, it's an all or none approach. For one-stop integration the value in the attribute will be copied from the `group expenditure item' attribute in PATI. *****
INTERFACE_ID NUMBER 18 Transaction interface process identifier. This attribute is populated for Project Cost processing only. *****
PLAN_VERSION_ID NUMBER 18 Yes Budget Plan Version that the transaction maps to. *****
IND_COMPILED_SET_ID NUMBER 18 Indirect Compile Set Identifier. This attribute is required for deriving burden. *****
DOCUMENT_TYPE VARCHAR2 3 Yes Document Type like Requisitions (REQ), Purchase Order (PO), Payable Invoices (INV) etc. *****
EVENT_ID NUMBER 18 Accounting Event raised by Projects. *****
SOURCE_EVENT_ID NUMBER 18 Accounting Event raised by non-projects team like Purchasing and Payables. *****
RBS_HEADER_ID NUMBER 18 RBS Header identifier that the RBS attributes map to. RBS Header Id mapping will be carried out separate line burden records. For same line burden and for raw transaction, one-stop process derives RBS Header Id mapping. *****
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_LOGIN VARCHAR2 32 Who column: indicates the session login associated to 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.
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.

Foreign Keys

Table Foreign Table Foreign Key Column
PJC_BC_PACKETS_H pjf_proj_elements_b TASK_ID
PJC_BC_PACKETS_H pjo_plan_versions_b PLAN_VERSION_ID
PJC_BC_PACKETS_H pjf_projects_all_b PROJECT_ID
PJC_BC_PACKETS_H pjf_rbs_elements RBS_ELEMENT_ID

Indexes

Index Uniqueness Tablespace Columns
PJC_BC_PACKETS_H_N1 Non Unique Default DOCUMENT_HEADER_ID, DOCUMENT_DISTRIBUTION_ID, DOCUMENT_TYPE
PJC_BC_PACKETS_H_U1 Unique Default BC_PACKET_ID