Last updated on SEPTEMBER 02, 2016
Applies to:Oracle Service Contracts - Version 22.214.171.124 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.
OKSAUDET.FMB - Service Contracts Authoring
A contract is in a user-defined status. The contract is then opened for update and goes to QA Hold status. When the QA check is run successfully, the contract goes to the 'Active' status (seeded) rather than the status it was at before being opened for update. The contract is always returned to whatever status is defined as the default for the Active status type.
A further symptom is that after running the QA Check the header and line status may not be in synch.
The contract should return to whatever the status it was in before it was opened for update.
Steps to reproduce:
1. Go to (R) Service Contracts Manager (N) Launchpad
2. Search for an existing contract with a user-defined active type status and open for update so that it goes to QA Hold status.
3. Run QA Check on the contract
- the contract status will change to the default active type status - usually 'Active' instead of returning to the status prior to opening it for update.
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