My Oracle Support Banner

Commitment Control Source Transaction Type PO_PROCARD Should Be Set to Amount Type "Planned" Not Actuals (Doc ID 2759098.1)

Last updated on MARCH 11, 2021

Applies to:

PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

Currently the Commitment Control Amount Type for Source Transaction Type PO_PROCARD Definition is set to "Actuals and Recognized" when it should be set to "Planned" since it does not affect spending authority. Then when the budget validation of PCard transaction lines occurs, a row for $0 amount is being logged in KK_ACTIVITY_LOG under the Expense ledger. This causes a $0 amount row for each PCard transaction line that passes budget validation to appear in each Activity Log inquiry such as Budgets Overview and Budget Details. Since 1000's of $0 amount rows for budget validation of PCard transaction lines are appearing in each Activity Log inquiry, business users then cannot view the regular non-$0 amount rows because it exceeds the number of rows that can be displayed in Activity Log inquiries.

The delivered Commitment Control Amount Type for Source Transaction Type PO_PROCARD Definition should be set to "Planned". Then when an additional ledger of type "Planned" is added to the expense commitment control ledger group with "Affect Spending Authority" turned off, the budget validation of PCard transactions will then correctly post to the "Planned" ledger and not affect spending authority.

Also when the user inquires on the Activity Log for the "Expense" ledger then PCard transactions will not fill up the Expense ledger inquiry and will instead appear in the Planned ledger inquiry.

Replication Steps:
1.Given the delivered Commitment Control Amount Type for Source Transaction Type PO_PROCARD Definition set to "Actuals and Recognized" instead of "Planned"
2.Load PCard transaction lines
3.Run budget validation of PCard transaction lines
4.Use Activity Log inquiry, e.g. via Budgets Overview and/or Budget Details; and see that there are 1000's of $0 amount rows for budget validation of PCard transaction lines which prevent being able to see the regular non-$0 amount rows because it exceeds the number of rows that can be displayed in Activity Log inquiries

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


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