EXPLAINED: Autorenewal questions in R12 (Doc ID 869426.1)

Last updated on AUGUST 23, 2016

Applies to:

Oracle Service Contracts - Version 12.0 to 12.1.3 [Release 12 to 12.1]
Information in this document applies to any platform.
***Checked for relevance on 20-Aug-2014***

Goal

This document is created to answer the following questions:

Question 1:
Are the listeners still mandatory to be scheduled when setting up the automatic renewal flow in R12?

Question 2:
Are queues still needed in R12 or can they be stopped (AQ$_OKC_AQ_EV_T, OKC_AQ_EV_QUEUE, OKC_AQ_OC_QUEUE)?

Question 3:
What are the workflow processes that need to be scheduled and by whom?

Question 4:
When executing the automatic renewal flow, sometimes the following error notifications can be seen when logged in as SYSADMIN user in (R) Workflow Administrator responsibility (N) Status Monitor:

Error:
ITEM TYPE = OKCALERT
ERROR NAME = WFENG_COMMIT_INSIDE
Error Message = 3146: Commit happened in in activity
ALERT_PROCESS.FUN_GENERIC-1/OKS_ASYNC_PVT.FUN_GENERIC

Why are these notifications generated and what do they mean?

Question 5:
After running Date Assembler some expected contracts are not renewed.  When Date Assembler is run again the following day, these contracts are no longer picked up for renewal even if they should have been selected by the date-based condition. Is there any change in the way that contracts are picked for renewal in R12?

Solution

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