Can The Initialize Credit Summaries Program Be Run With Parameter Lock table as 'No'?
(Doc ID 947692.1)
Last updated on OCTOBER 01, 2019
Applies to:Oracle Order Management - Version 188.8.131.52 to 184.108.40.206 [Release 11.5.10]
Information in this document applies to any platform.
Initialize Credit Summaries, OEXINIC
***Checked for relevance on 26-APR-2011***
***checked for currency 23-Apr-2013***
Initialize credit summaries is taking more time than expected. Further we use 'Pre-calculated
Exposure' in credit check rule so that the credit check engine access the summary table instead of
the transactional table at the time of credit checking.
Also we are running Initialize credit summaries with lock tables as "Yes" which is causing
problems in performing the transactions for our other sites.
Can Initialize credit summaries be run with lock tables as "No", as by doing this other sites can perform transactions without any hurdles?
As whenever we run this program with Lock table as 'Yes', one or more sites get an impact at they
are in different time zone.
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