Last updated on OCTOBER 12, 2016
Applies to:Oracle Advanced Collections - Version 12.1.3 and later
Information in this document applies to any platform.
If you do not use MOAC and instead have separate responsibilities setup for each Operating Unit due to the nature of your business requirements and you are running at the Delinquency level, you could experience this issue.
You've set IEX: Strategy Unique Fulfillment profile option for only one responsibility to Yes, but you notice that when you run IEX: Strategy Fulfillment Mailer it is only processing 1 Dunning Letter per customer and cancelling the other Work Items for the Delinquencies on that customer.
This behavior would be correct if the IEX: Strategy Unique Fulfillment is set to Yes for the responsibility that submitted the concurrent process.
Checking iexpstmb.pls reveals that the context is not being set correctly in the Check_Dunning procedure.
The line to check the context is actually commented out -
--FND_GLOBAL.Apps_Initialize(l_user_id, l_resp_id, l_resp_appl_id);
Development explains that when we clear each pending work item workflow with workflow background process, there is no filtering by Operating Unit so the performance was degraded. Therefore, the suggestion from Development is to set this profile to No for all responsibilities.
The following bug was logged to remove the ability to set the profile at the Responsibility level in order to avoid this type of an issue.
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