Getting Abended at Step FS_BP_PEOD.vTrnsLog.uExpYear When Budget Check Purchase Order After Apply Bug 32925838
(Doc ID 2814589.1)
Last updated on SEPTEMBER 23, 2024
Applies to:
PeopleSoft Enterprise SCM Purchasing - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
Getting ABENDED at Step FS_BP_PEOD.vTrnsLog.uExpYear When Budget Check Purchase Order After Apply Bug 32925838.
This happens when override budget exceptions messages and budget check Purchase Order again.
ERROR:
The issue can be reproduced at will with the following steps:
Scenario 1:
Setup:
1. Installation Option. Entry Event Setup. Check Upward/Downward Adjustment. Navigation: Setup Financials/Supply Chain > Install > Installation Options. Entry Event link
2. Set Business Unit Event Setup: PO Entry Event = 'PO_COMB', REQ Entry Event = 'PO_COMB', PROCARD Entry Entry = 'APVOUCHER'. Navigation: Setup Financials/Supply Chain > Business Unit Related > Purchasing Definition
3. Ledger for a Unit - Business Unit = ' US005'. Define Ledger Group only for 'CC_ORG' and 'DETAIL'. Navigation: Setup Financials/Supply Chain > Business Unit Related > Ledger for a Unit
4. Go to Budget Definition, Ledger Group = 'CC_ORG', Add Fund Code for Tab Key and Translation. Navigation: Commitment Control > Define Control Budgets > Budget Definitions
5. Go to Budget Definition. Ledger Group = 'DETAIL'. Define Prior Year Adj Chartfield = 'Fund Code'. Prior Year Adj Chartfield = Fund Code
6. Entry Event Source Definition for PO Upward Adjustment. Navigation: Setup Financials/Supply Chain > Common Definitions > Entry Event Source
7. Entry Event Source Definition for PO Downward Adjustment. Navigation: Setup Financials/Supply Chain > Common Definitions > Entry Event Source
8. Entry Event Process Definition – POPOST. Add EE Step POUP and setup. Navigation: Setup Financials/Supply Chain > Common Definitions > Define EE Process Step
9. Entry Event Process Definition – POPOST. Add EE Step PODN and setup. Navigation: Setup Financials/Supply Chain > Common Definitions > Define EE Process Step
10. Entry Event Code PO_COMB. Add the POUP and PODN Steps. Navigation: Setup Financials/Supply Chain > Common Definitions > Entry Event Code Definition
11. Add Budget Journal to Account/Fund/Dept (500000/F300/14000) to 2021 and 2022. Navigation: Commitment control > Budget Journals > Enter Budget Journals
12. Now Budget available: Navigation: Commitment control > Review Budget Activities > Budget Overview
Steps:
1.Create two line PO in year 2021. And Validate Budget Check. Navigation: Purchasing > Purchase Orders > Add/Update PO’s
2. Run Entry Event the PO. Navigation: Purchasing > Purchase Orders > Entry Event Request PO
3. Close line 1 via Buyer workbench. Override the PO to close and select the accounting date to 2022 and update Budget date equal to Accounting date. Navigation: Purchasing > Purchase Orders > Buyer’s Workbench
4. Run PO Budget Check. Navigation: Purchasing > Purchase Orders > Budget Check Purchase Order
5. Budget Check Exceptions. Navigation: Commitment Control > Review Budget Exceptions
6. Override Budget and Budget Check again. Process Monitor showing FS_BP with NO Success.
"Process XXXXXX ABENDED at Step FS_BP_PEOD.vTrnsLog.uExpYear (SQL) -- RC = 1427"
Scenario 2:
Setup:
- Installation Option. Entry Event Setup. Check Upward/Downward Adjustment. Navigation: Setup Financials/Supply Chain > Install > Installation Options. Entry Event link
- Set Business Unit Event Setup: PO Entry Event = 'PO_COMB', REQ Entry Event = 'PO_COMB', PROCARD Entry Entry = 'APVOUCHER'. Navigation: Setup Financials/Supply Chain > Business Unit Related > Purchasing Definition
- Ledger for a Unit - Business Unit = ' US005'. Define Ledger Group only for 'CC_ORG' and 'DETAIL'. Navigation: Setup Financials/Supply Chain > Business Unit Related > Ledger for a Unit
- Go to Budget Definition, Ledger Group = 'CC_ORG', Add Fund Code for Tab Key and Translation. Navigation: Commitment Control > Define Control Budgets > Budget Definitions
- Go to Budget Definition. Ledger Group = 'DETAIL'. Define Prior Year Adj Chartfield = 'Fund Code'. Prior Year Adj Chartfield = Fund Code
- Entry Event Source Definition for PO Upward Adjustment. Navigation: Setup Financials/Supply Chain > Common Definitions > Entry Event Source
- Entry Event Source Definition for PO Downward Adjustment. Navigation: Setup Financials/Supply Chain > Common Definitions > Entry Event Source
- Entry Event Process Definition – POPOST. Add EE Step POUP and setup. Navigation: Setup Financials/Supply Chain > Common Definitions > Define EE Process Step
- Entry Event Process Definition – POPOST. Add EE Step PODN and setup. Navigation: Setup Financials/Supply Chain > Common Definitions > Define EE Process Step
- Entry Event Code PO_COMB. Add the POUP and PODN Steps. Navigation: Setup Financials/Supply Chain > Common Definitions > Entry Event Code Definition
- Add Budget Journal to Account/Fund/Dept (500000/F300/14000) to 2021 and 2022. Navigation: Commitment control > Budget Journals > Enter Budget Journals
- Now Budget available: Navigation: Commitment control > Review Budget Activities > Budget Overview
Steps:
- Create two line PO in year 2022 and Validate Budget Check. Navigation: Purchasing > Purchase Orders > Add/Update PO’s
- Run Entry Event the PO. Navigation: Purchasing > Purchase Orders > Entry Event Request PO
- Close line 1 via Buyer workbench. Navigation: Purchasing > Purchase Orders > Buyer’s Workbench
- Run PO Budget Check. Navigation: Purchasing > Purchase Orders > Budget Check Purchase Order
- Budget Check Exceptions. Override Budget and Budget Check again. Navigation: Commitment Control > Review Budget Exceptions
- Run Entry Event Request PO. Navigation: Purchasing > Purchase Orders > Entry Event Request PO
- Back to PO. Update line 2 in the next accounting period, set amount = 156 (change the price to $52). Save PO
- Budget Check PO. Finished with ‘warning’
- At Purchase Order Exceptions pageo Override Budget and budget check. Navigation: Commitment Control > Review Budget Exceptions.
- Getting ABENDED at Step FS_BP_PEOD.vTrnsLog.uExpYear (SQL) -- RC = 1407
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 |