EGL9.2.KK Drill Down From Activity Log Via Component KK_INQ_BD_DETAIL_T To Transaction Throw SQL Error"Field does not exist -- KK_XCP_TRAN_VW1.KK_SOURCE_TRAN. (180,104) FUNCLIB_KK.KK_EVENT.FieldFormula Name:panel_event PCPC:535 Statement:2 Called from:
(Doc ID 2992355.1)
Last updated on DECEMBER 14, 2023
Applies to:
PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
When choosing Go to Source Entry/Inquiry from Review kk Activity log , the following error message appears :
Field does not exist -- KK_XCP_TRAN_VW1.KK_SOURCE_TRAN. (180,104) FUNCLIB_KK.KK_EVENT.FieldFormula Name:panel_event PCPC:535 Statement:2 Called from:KK_FROM_XCP_SRC_ID.MENUITEM1.GO_TO_SRC_ENTRY.ItemSelected Statement:37
A reference to a record.field name was made and the record.field name was not found to exist. Verify that the field exists on the page in which the PeopleCode program is being executed. Review the program for errors. If necessary, run a PeopleCode trace to determine the program that failed
The issue can be replicated following the next steps :
1. Go to Commitment Control>Review Budget Activities>Review KK Activity Log and add an inquiry run control. Choose Transaction Type=GL_JOURNAL and ledger group = CC_ORG and Search.
2. Click on Return to Budget Detail.
3. For the Expense line, choose drill to Activity Log.
4. For 1 journal, choose Drill Down.
5. Next to Journal Id , choose View Other links.
6. When clicking on both “Go to Source Entry” and “Go to Source Inquiry” , the following error message appears :
“Field does not exist -- KK_XCP_TRAN_VW1.KK_SOURCE_TRAN. (180,104) FUNCLIB_KK.KK_EVENT.FieldFormula Name:panel_event PCPC:535 Statement:2 Called from:KK_FROM_XCP_SRC_ID.MENUITEM1.GO_TO_SRC_ENTRY.ItemSelected Statement:37
A reference to a record.field name was made and the record.field name was not found to exist. Verify that the field exists on the page in which the PeopleCode program is being executed. Review the program for errors. If necessary, run a PeopleCode trace to determine the program that failed.”
More information can be found in the attached replication document.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |