PeopleSoft Commitment Control
Log tables that are updated by the budget processor:
KK_SOURCE_HDR
KK_SOURCE_LN
KK_ACTIVITY_LOG
KK_REFERENCED
KK_LIQUIDATION
KK_TRANS_LOG
KK_TRAN_ID_TBL
KK_OVERRIDE_TBL
KK_EXCPTN_TBL
KK_SOURCE_HDR
- When budget checking is run against a transaction, the budget processor will record the information KK_SOURCE_HDR.
- A unique KK_TRAN_ID is assigned for each transaction header being budget checked.
- The transaction header key is inserted into the table (e.g. Voucher ID, PO ID, Journal ID)
- Data stored in this table remains in the table as long as the transaction is not deleted.
- Even if there is no budget impacted by the transaction, the data in this table will remain in the table.
- This is an indicator that the transaction was budget checked (regardless of whether it passed or not).
KK_SOURCE_LN
- This table is a child table of KK_SOURCE_HDR and is linked by the KK_TRAN_ID.
- It stores transaction line information and KK_TRAN_LN is assigned to each line.
- Only transaction line that pass budget checking and impacts the budget ledger will be inserted into the KK_SOURCE_LN table.
- When the transaction is deleted, all rows associated with the transaction are deleted.
KK_ACTIVITY_LOG
- This table is a child table of KK_SOURCE_LN and is linked by the KK_TRAN_ID and KK_TRAN_LN.
- It stores budget level information used to update LEDGER_KK
- For each budget ledger that is impacted by the transaction line, a row is inserted to the table. Therefore, if there are two budget ledgers (e.g. APPROP and ORG) are impacted for a journal ID ABC, line1, then two rows are inserted to this KK_ACTIVITY_LOG table.
- Same as KK_SOURCE_HDR and KK_SOURCE_LN, when the transaction is deleted from the system the data associated with the transaction is deleted as well.
- The budget checking will update the LEDGER_KK base on the information on this table.
KK_LIQUIDATION
- This table is used to store and track open balances for documents that are referenced by subsequent transactions. This table is similar to open pre-enc/enc table in E&G 7.5.
- If the transaction is passed budget checking, one row per transaction line per commitment control ledger group is added or updated.
- If the source transaction is deleted all rows related to the transaction are deleted.
- KK_POSTED_AMT field represent the total source transaction amount.
- MONETARY_AMOUNT field represent the remaining open balance.
E.g.
PO amount = 100 (KK_POSTED_AMT = 100)
PO Voucher amount = 80.
---
Open balance = 20 (MONETARY_AMOUNT = 20)
KK_REFERENCED
- This table stored the link for procure to pay transactions.
- It stores the reference data between Requisition and Purchase Order or Purchase Order and Voucher.
- KK_TRAN_ID field stored the predecessor document transaction id (PO trans id that is referenced to PO Voucher)
- KK_REFD_ID field stored the referenced document. (PO Voucher trans id that is
Miscellaneous tables
KK_TRANS_LOG - Stores the history of a document. KK_TRANS_LOG contains much of the same data that KK_ACTIVITY_LOG stores. The primary difference between the tables is a sequence number that is defined on the transaction log. Each time a transaction is budget checked, the budget processor inserts data into the log record and increments the sequence number field by one. This allows users to see how documents change between passes of the budget processor.
This table is populated only if the _Update Transaction Log_ option in the Source Transaction definition is set to _Update Log_ (Commitment Control, Define Control Budgets, Budget Setup, Source Transactions, Options page).
KK_TRAN_ID_TBL - Stored the last transaction id used.
KK_OVERRIDE_TBL - Stored the user id or operator id that override the budget checking for a particular document.
KK_EXCPTN_TBL - Stores Commitment Control transaction budget checking exceptions.
Log tables that are updated by the budget processor:
KK_SOURCE_HDR
KK_SOURCE_LN
KK_ACTIVITY_LOG
KK_REFERENCED
KK_LIQUIDATION
KK_TRANS_LOG
KK_TRAN_ID_TBL
KK_OVERRIDE_TBL
KK_EXCPTN_TBL
KK_SOURCE_HDR
- When budget checking is run against a transaction, the budget processor will record the information KK_SOURCE_HDR.
- A unique KK_TRAN_ID is assigned for each transaction header being budget checked.
- The transaction header key is inserted into the table (e.g. Voucher ID, PO ID, Journal ID)
- Data stored in this table remains in the table as long as the transaction is not deleted.
- Even if there is no budget impacted by the transaction, the data in this table will remain in the table.
- This is an indicator that the transaction was budget checked (regardless of whether it passed or not).
KK_SOURCE_LN
- This table is a child table of KK_SOURCE_HDR and is linked by the KK_TRAN_ID.
- It stores transaction line information and KK_TRAN_LN is assigned to each line.
- Only transaction line that pass budget checking and impacts the budget ledger will be inserted into the KK_SOURCE_LN table.
- When the transaction is deleted, all rows associated with the transaction are deleted.
KK_ACTIVITY_LOG
- This table is a child table of KK_SOURCE_LN and is linked by the KK_TRAN_ID and KK_TRAN_LN.
- It stores budget level information used to update LEDGER_KK
- For each budget ledger that is impacted by the transaction line, a row is inserted to the table. Therefore, if there are two budget ledgers (e.g. APPROP and ORG) are impacted for a journal ID ABC, line1, then two rows are inserted to this KK_ACTIVITY_LOG table.
- Same as KK_SOURCE_HDR and KK_SOURCE_LN, when the transaction is deleted from the system the data associated with the transaction is deleted as well.
- The budget checking will update the LEDGER_KK base on the information on this table.
KK_LIQUIDATION
- This table is used to store and track open balances for documents that are referenced by subsequent transactions. This table is similar to open pre-enc/enc table in E&G 7.5.
- If the transaction is passed budget checking, one row per transaction line per commitment control ledger group is added or updated.
- If the source transaction is deleted all rows related to the transaction are deleted.
- KK_POSTED_AMT field represent the total source transaction amount.
- MONETARY_AMOUNT field represent the remaining open balance.
E.g.
PO amount = 100 (KK_POSTED_AMT = 100)
PO Voucher amount = 80.
---
Open balance = 20 (MONETARY_AMOUNT = 20)
KK_REFERENCED
- This table stored the link for procure to pay transactions.
- It stores the reference data between Requisition and Purchase Order or Purchase Order and Voucher.
- KK_TRAN_ID field stored the predecessor document transaction id (PO trans id that is referenced to PO Voucher)
- KK_REFD_ID field stored the referenced document. (PO Voucher trans id that is
Miscellaneous tables
KK_TRANS_LOG - Stores the history of a document. KK_TRANS_LOG contains much of the same data that KK_ACTIVITY_LOG stores. The primary difference between the tables is a sequence number that is defined on the transaction log. Each time a transaction is budget checked, the budget processor inserts data into the log record and increments the sequence number field by one. This allows users to see how documents change between passes of the budget processor.
This table is populated only if the _Update Transaction Log_ option in the Source Transaction definition is set to _Update Log_ (Commitment Control, Define Control Budgets, Budget Setup, Source Transactions, Options page).
KK_TRAN_ID_TBL - Stored the last transaction id used.
KK_OVERRIDE_TBL - Stored the user id or operator id that override the budget checking for a particular document.
KK_EXCPTN_TBL - Stores Commitment Control transaction budget checking exceptions.
No comments:
Post a Comment