Monitoring Services: Incorrect Revenue Number Is Mapped to Expenditure Item
(Doc ID 2848736.1)
Last updated on SEPTEMBER 07, 2023
Applies to:
Oracle Project Billing - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
This issue is handled via Monitoring Services.
The basic concept of the Monitoring Service is the ability to define and periodically look for events (faults, issues, availability) in the customer's instances and, as needed, when an event occurs, create / update a Service Request with a well-defined problem statement, the diagnostics collected, and specific steps defined for the engineer to easily solve the issue.
This monitoring service captures corruption where revenue is not visible for expenditure item even expenditure item has revenue amount. This corruption is caused as expenditure item is tagged to incorrect revenue number where data exists in draft revenue items and revenue distribution table but not in draft revenue header table.
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 |