Agreement Task Customer Mismatch
Last updated on OCTOBER 30, 2017
Applies to:Oracle Project Billing - Version 188.8.131.52 and later
Information in this document applies to any platform.
User created an agreement using tasks tied to two different customer numbers. User was able to add a task and baseline it with a different customer number than the customer number on the agreement itself.
This caused error 12, however, the user cannot reverse the transaction using the original TASK number because it has a different number than the agreement itself.
The user created another task using the customer on the agreement, however, the system is giving them an error on attachment.
Issue occurs when user does not save the records at the fund level once they are finished entering information to prevent the customer number from being able to be changed.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms