Last updated on SEPTEMBER 26, 2017
Applies to:PeopleSoft Enterprise SCM Purchasing - Version 9.1 and later
Information in this document applies to any platform.
Old requisitions from prior periods should not automatically budget check just because the budget rules were changed in a way that cleared the budget exception on these old requisitions.
Steps to accomplish functionality:
1. Prevent old requisitions from being budget checked without some intervention from user.
Let's say that there was a rule in place that would generate a budget exception if any single requisition went over $5000. As a result of the rule, a number of requisitions are in budget exception and (for whatever reason) never revisited. Many months later (in a different financial period) , the budget rule is changed to allow any single requisition under $10,000.... suddenly, these year old requisitions from a prior, closed period are getting budget checked successfully. If the buyer's don't catch the really old date, they could process an old, stale requisition.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms