My Oracle Support Banner

Can't Create Lead-"Post Threshold Limit Reached" - Due To AfterChangesPosted (Doc ID 2582259.1)

Last updated on AUGUST 28, 2019

Applies to:

Oracle Fusion Sales Cloud Service - Version 11.13.18.02.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.13.18.02.0 version, Leads, Sales Campaigns

ACTUAL BEHAVIOR
---------------
Can't create Lead-"Post threshold limit reached" - due to AfterChangesPosted

Hi,

We've recently upgrade to R13 on our test environment CCFO-TEST. One of the changes coming as part of R13 was the deprecation of certain trigger points (AfterInsert, AfterUpdate, AfterCommit, etc.), and Oracle recommended moving any triggers defined on those trigger points to the instead use the AfterChangesPostedToDatabase trigger - see http://www.oracle.com/webfolder/technetwork/tutorials/tutorial/cloud/r13/wn/r13-2018-sales-wn.htm#F3381

As such we recently changed all triggers at AfterInsert, AfterUpdate, etc. to instead use the AfterChangesPostedToDatabase trigger. This includes an AfterInsert trigger we have defined on the Lead object which creates an Activity whenever a Lead is created/inserted. I've attached the two scripts for this - both the previous AfterInsert trigger and the new AfterChangesPostedToDatabase trigger (which has an added if statement if(getPrimaryRowState.isNew()) to ensure that it only runs at the point of insertion).

Since making this change we are unable to create any Leads - instead we are always greeted by the error message 'Post threshold limit reached. Some entities yet to be posted'. Looking in Oracle Support I can see that this error seems to be related to the use of AfterChangesPostedtoDatabase triggers and Oracle are advising not to use this trigger type. See: https://support.oracle.com/epmos/faces/DocContentDisplay?id=2405125.1

This is the complete opposite message given the R13 article which has advised moving to this trigger type. Please can you advise what the issue is and whether or not we should be using the AfterChangesPostedToDatabase trigger type?

EXPECTED BEHAVIOR
-----------------------
The message should be different


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
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.