Tuesday, September 16, 2014

QA Check in Oracle Service Contracts (OKS) R12

QA Check in Oracle Service Contracts (OKS) R12

Quality Assurance Check (QA Check) is a standard functionality of Oracle Service Contracts (OKS). Whenever a new contract is getting activated or some updates happen to a contract, the system checks for certain validations to make sure that the contract meets is the required criteria. Typically the criteria can be business restrictions (PO Number Required, Term should be either monthly or quarterly) or integrity requirements (No overlapping billing schedules, no serial in multiple orders). Users can also add new custom PL/SQL Functions and add them to the QA Checklist.

QA Checklist is defined by the profile option value "OKS: Default QA Checklist". It can be setup at Site, Application and Responsibility levels. The default value for this profile is "Default Service Contracts Quality Assurance Check List".

Profile Option Name: OKS: Default QA Checklist (This is accessed by System Administrator responsibility)

Maintain (add and remove conditions) are done by:

Responsibility: Service Contracts Setup
Navigation Path: Functions > Quality Assurance

Here is an example of a QA Checklist Screenshot: qa check - configure
The Severity level can be STOP and WARNING. When STOP condition occurs, the QA will fail and the contract cannot be activated without fixing the root cause. WARNING allows contracts to be proceeded, even though user has to review the cause.

Even though contract is active, pressing UPDATE button will change the status to QA_HOLD. This can be reactivated only by successfully completing QA Check.

To add a new condition during the activation, add an additional line and link to the required function.