PS BP Notes

A summary from various sources

https://docs.oracle.com/cd/F25059_01/fscm92pbr34/eng/fscm/fscc/task_PeopleSoftCommitmentControlReportsListAndGeneralDescription.html

• A successful Check Only budget entry will have a Budget Hdr Status of P to indicate a valid Budget Check Only. The value P is equivalent to N (not checked). Subsequently, after full processing, a successful budget check is indicated by the Budget Hdr Status V (valid), which indicates a successful budget check and posting to the Ledger_KK record.

• A Check Only that results in errors being logged updates the Budget Hdr Status to E (errors) and the applications links an access to the exception table functions as with normal budget checking and posting. Lines with errors are updated to an E (error) status. Those that are valid remain with an N (not checked) status.

• Note: If a budget transaction line is not subject to budget checking for any Commitment Control ledger groups assigned to the General Ledger business unit, the Budget processor sets the budget line status to B. If the budget transaction line is subject to budget checking, the budget line status has a V.

• Budget Type = Ledger Group

–AP = Appropriation (APPROP)

–OR = Organization (ORG)

–PR = Project /Grant (PROJ_GRT)

–RE = Revenue Estimate (REV_EST)

• Amount Field = Ledgers within Controlled Ledger Group

–Encumbered Amount = APPROP_ENC + Posted Total Amount

–Pre‐encumbered Amount = APPROP_PRE + Posted Total Amount

–Expended Amount = APPROP_EXP + Posted Total Amount

–Budget Amount = APPROP_BUD + Posted Total Amount

https://support.oracle.com/knowledge/PeopleSoft%20Enterprise/845460_1.html

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=226133918804235&parent=EXTERNAL_SEARCH&sourceId=PROBLEM&id=845460.1&_afrWindowMode=0&_adf.ctrl-state=ublcblto3_4

• Budget Period

-Budget Period equals Appropriation Year

-Budget Date derives Budget Period

-Budget Period no longer specified on transactions

-Accounting Date derives Fiscal Year and Accounting Period

• Table Changes

• LEDGER_BUDG replaced with LEDGER_KK
• BUD_JRNL_HEADER & BUD_JRNL_LN replaced with KK_BUDGET_HDR and KK_BUDGET_LN

• Link to KK tables 

•KK_SOURCE_HDR

* Header information for source transactions to GL

* This table has the source transaction information such as Voucher ID, Journal ID, etc. Join KK_ACTIVITY_LOG to get the amounts and ChartFields
* SEQUENCE_NBR_9 shows seq # of Trans processed by specific  KK_PROC_INSTANCE
* FY & PRD are not populated

*Key fields include: KK_TRAN_ID and KK_TRAN_DT. Other fields include SOURCE_TRAN (AP_VOUCHER, GL_JOURNAL, POENC, PREENC,CM_TRNXTN) SEQUENCE_NBR, KK_PROCESS_STATUS, PO_ID, REQ_ID,VOUCHER_ID, JOURNAL_ID.

•KK_SOURCE_LN

Only transaction line that pass budget checking and impacts the ledger will be inserted into KK_SOURCE_LN table.

•KK_ACTIVITY_LOG

* Child table of KK_SOURCE_LN ;
* Detailed listing of each round of BP transactions posted against budget, identified by SEQUENCE_NBR 

* used to update LEDGER_KK when successful BP of a tran, both LEDGER_KK and KK_ACTIVITY_LOG table are updated at the same time  

* stores the details behind the LEDGER_KK balances

* Does not store the source transaction ID (i.e. voucher number, journal id, etc.).
* KK_SOURCE_HDR, KK_SOURCE_LN & ACTIVITY_LOG are populated by BP from the corresponding Header table (PO_HDR, REQ_HDR, VOUCHER, JRNL_HEADER). If the field BUDGET_HDR_STATUS is "V", then the data has been populated in the KK tables.

* join KK_SOURCE_HDR by the KK_TRAN_ID, KK_TRAN_DT, * AND KK_TRAN_LN
* stores actual FY + PRD values

* Key fields include: SEQNBR, KK_TRAN_ID, KK_TRAN_DT, KK_TRAN_LN,REFERENCED_BUDGET, BALANCING_LINE, LEDGER_GROUP, LEDGER (ORG_PR, ORG_EN, ORG_EX), FISCAL_YEAR, ACCOUNTING_PERIOD.

•KK_TRANS_LOG

Captures all transactions related to each pass of BP ;
1-1 match to JRNL_LN for budget_line_status <> ‘B’
CF at detailed level
capture documents changes between each passes of the BP, identified by SEQUENCE_NBR 
for PO & REQ, BU=XXXXX while BU=AGY_NO on SOURCE_HDR
entries removed when PO is deleted

•KK_BP_LOG

        Active BP instance, cleared when done, not cleared on abend.

•KK_LIQUIDATION

Details what/has been liquidated against encumbrances

KK_SOURCE_TRAN = PO_POENC / REQ_PREENC

KK_TRAN_ID = predecessor document transaction id (PO trans id that is referenced to PO Voucher)

KK_REFD_ID = referenced document

KK_POSTED_AMT = total source tran amt

MONETARY_AMOUNT = the remaining open balance.

•KK_REFERENCED

Stores the reference data between Requisition and Purchase Order or Purchase Order and Voucher

•KK_BUDGET_HDR

Stored the budget journal header information associated with commitment control budget journals.

Key fields include: BUSINESS_UNIT, JOURNAL_ID, JOURNAL_DATE,UNPOST_SEQ

•KK_BUDGET_LN

Child record of the KK_BUDGET_HDR table and store the ChartField and Amount information associated with commitment control budget journals

Key fields include: BUSINESS_UNIT, JOURNAL_ID, JOURNAL_DATE,UNPOST_SEQ, JOURNAL_LINE

•KK_EXCPTN_TBL

Details exceptions per trans

•KK_OVERRIDE_TBL

Captures any overrides made to the KK ledger(s)

•KK_TRAN_ID_TBL

Last KK_TRAN_ID

•LEDGER_KK

Budget ledgers that store balances from budget checking.

Updated along with KK_ACTIVITY_LOG

Key fields include: BUSINESS_UNIT, LEDGER, FISCAL_YEAR,ACCOUNTING_PERIOD, All ChartFields

•LEDGER_BUDG_KK

Captures budget by KK ledger

reconciled to the activity/transaction logs

Trans Rules:

* PO Vchr: 2 rows on Activity_Log: 

1. DETAIL_EX: REFERENCED_BUDGET='N'; KK_QUANTITY>0; ACTIVITY=0 
2. DETAIL_EN: REFERENCED_BUDGET='Y'; KK_QUANTITY=0;  ACTIVITY=MONETARY_AMOUNT; MONETARY_AMOUNT= offset of DETAIL_EX, 

*  update KK_PROCESS_STATUS field to 'I' on tables KK SOURCE HEADER, KK_SHDR_GLJRNL, add data to PS_KK_BP_LOG for the journals that are locked when trying to open (Header Unlock)  them 

 Archiving for Commitment Control

https://docs.oracle.com/cd/E39583_01/fscm92pbr0/eng/fscm/fscc/concept_UnderstandingArchivingforCommitmentControl-9f227d.html#DeliveredArchiveProceduresforCommitmentControl-9f227b__cm0152e22