Requisition and Purchase Order Have KK Tables Out of Sync With KK FS Tables (Doc ID 2572613.1)

Last updated on FEBRUARY 01, 2023

Applies to:

Symptoms

Requisition and Purchase Orders have KK tables out of sync with KK FS tables. 

When creating requisitions and purchase orders that are controlled by project and fund sources, table KK_ACT_LOG_FS gets out of sync with table KK_ACTIVITY_LOG. Also, table LEDGER_KK_FS gets out of sync with table LEDGER_KK.
The first time the requisition or purchase order is budget checked the tables are in sync.  If an additional line is added and the requisition or purchase orders budget checked again, tables KK_ACT_LOG_FS and KK_ACTIVITY_LOG are now out of sync.

If a third line is added now tables KK_ACT_LOG_FS and KK_ACTIVITY_LOG and tables LEDGER_KK_FS and LEDGER_KK are out of sync.

The issue can be reproduced at will with the following steps:

Replication steps for Requisition:
1. Navigation: Purchasing > Requisitions > Add/Update Requisitions. Add a new Requisition for business unit US006. Save and validate budget check.
2. Run this sql to get the kk_tran_id and kk_tran_dt for this requisition:
  select * from ps_kk_source_hdr where business_unit = 'US006' and req_id = '0000000002'
3. Execute queries to see sync between KK_ACTIVITY_LOG and KK_ACT_LOG_FS showing sync data.
4. Execute queries to see sync between LEDGER_KK and LEDGER_KK_FS showing the same amount.
5. So far, looks syncronized.
6. Add a second line to the requisition. Use the same chartfields that are in the first line. Do not change the accounting date or budget date.
7. Save and budget check the requisition.
8. Execute queries to see sync between KK_ACTIVITY_LOG and KK_ACT_LOG_FS
9. Execute queries to see sync between LEDGER_KK and LEDGER_KK_FS
10. KK_ACTIVITY_LOG and KK_ACT_LOG_FS is unsync now. Only line 2 exists in KK_ACT_LOG_FS
11. LEDGER_KK and LEDGER_KK_FS still showing the same amount.
12. Add a third line to the requisition. Keep the same chartfields and dates. Save and budget check.
13. Execute queries to see sync between KK_ACTIVITY_LOG and KK_ACT_LOG_FS
14. Execute queries to see sync between LEDGER_KK and LEDGER_KK_FS
15. KK_ACTIVITY_LOG and KK_ACT_LOG_FS is unsync now. Only line 3 exists in KK_ACT_LOG_FS
16. LEDGER_KK and LEDGER_KK_FS the amounts of these 2 records are not syncronized.

Replication Steps for Purchase Orders:
1. Navigation: Purchasing > Purchase Orders > Add/Update POs. Add a new PO for business unit US006. Save and Validate budget check.
2. Run this sql to get the kk_tran_id and kk_tran_dt for this PO:
  select * from ps_kk_source_hdr where business_unit = 'US006' and po_id = '0000000001'
3. Execute queries to see sync between KK_ACTIVITY_LOG and KK_ACT_LOG_FS showing sync data.
4. Execute queries to see sync between LEDGER_KK and LEDGER_KK_FS showing the same amount.
5. Add a second line to the PO. Do not change dates or chartfields. Save and budget check.
6. Execute queries to see sync between KK_ACTIVITY_LOG and KK_ACT_LOG_FS.
7. Execute queries to see sync between LEDGER_KK and LEDGER_KK_FS
8. KK_ACTIVITY_LOG and KK_ACT_LOG_FS is unsync now. Only line 2 exists in KK_ACT_LOG_FS
9. LEDGER_KK and LEDGER_KK_FS still showing the same amount.
10. Add a third line to the PO. Save and budget check.
11. Execute queries to see sync between KK_ACTIVITY_LOG and KK_ACT_LOG_FS
12. Execute queries to see sync between LEDGER_KK and LEDGER_KK_FS
13. KK_ACTIVITY_LOG and KK_ACT_LOG_FS is unsync now. Only line 3 exists in KK_ACT_LOG_FS
14. LEDGER_KK and LEDGER_KK_FS the amounts of these 2 records are not syncronized.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.