Search Results duplicate_collateral_data
Overview
AR_CMGT_CONTROLS is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Credit Management (AR_CMGT) module, which supports credit review, scoring, case folder management, and credit decisioning for customers and customer sites. The package is classified under the ETRM API taxonomy as OTHER, indicating that it is an internal, non-public API rather than a formally published extension interface.
Functionally, AR_CMGT_CONTROLS provides the data population and duplication layer that underpins Credit Management case folders. Case folders represent discrete credit review events. The package assembles the supporting evidence for a review, including third-party credit bureau data, aging analysis, financial and trade references, bank references, collateral, recommendations, and analyst notes. It also duplicates an existing case folder in its entirety when a reviewer needs to clone a prior analysis. The header comment dates the source to 2005, and the package remains present in the 12.2.2 code line, reflecting its status as long-lived internal infrastructure.
Key Procedures and Functions
The ETRM metadata documents twenty-four procedures and functions. The primary population routines are:
- POPULATE_CASE_FOLDER — creates a case folder record, associating it with a party, customer account, account site, credit request, check list, score model, review type, and limit currency.
- POPULATE_CASE_FOLDER_DETAILS and UPDATE_CASE_FOLDER_DETAILS — write and modify individual data point values and scores within a case folder.
- POPULATE_DNB_DATA — loads Dun & Bradstreet credit bureau data into the case folder from a specified source table, key, and key type.
- POPULATE_RECOMMENDATION — records a credit recommendation, recommended credit limit, and credit review date against a credit request.
- POPULATE_DATA_POINTS, POPULATE_ADD_DATA_POINTS, POPULATE_AGING_DTLS, UPDATE_AGING_DTLS, POPULATE_CF_ADP_DETAILS, and UPDATE_CF_ADP_DETAILS — populate scoring data points, additional data points, aging buckets, and additional data point details.
The duplication routines — DUPLICATE_CASE_FOLDER_TBL, DUPLICATE_CASE_FOLDER_DTLS, DUPLICATE_AGING_DATA, DUPLICATE_DNB_DATA, DUPLICATE_FINANCIAL_DATA, DUPLICATE_TRADE_DATA, DUPLICATE_BANK_DATA, DUPLICATE_COLLATERAL_DATA, and DUPLICATE_OTHER_DATA — copy each category of credit evidence from a source case folder to a new one, allowing reviewers to reuse a prior analysis as a starting point.
Tables Accessed
The package reads and writes through APPS synonyms. Case folder headers reside in AR_CMGT_CASE_FOLDERS and AR_CMGT_CASE_FOLDERS_S, with numbering controlled by AR_CMGT_CASE_FOLDER_NUMBER_S. Line-level data points are held in AR_CMGT_CF_DTLS and AR_CMGT_CF_DTLS_S. Aging details reside in AR_CMGT_CF_AGING_DTLS; D&B bureau details in AR_CMGT_CF_DNB_DTLS; recommendations in AR_CMGT_CF_RECOMMENDS and AR_CMGT_CF_RECOMMENDS_S; and analyst notes in AR_CMGT_CF_ANL_NOTES and AR_CMGT_CF_ANL_NOTES_S. Bank reference data is stored in AR_CMGT_BANK_REF_DATA, AR_CMGT_BANK_REF_DATA_S, AR_CMGT_BANK_REF_ACCTS, and AR_CMGT_BANK_REF_ACCTS_S. The _S tables denote the treated or secure variants used by the Credit Management schema design.
Usage Notes
AR_CMGT_CONTROLS is an internal package and is not intended for direct customer invocation. It is called by Credit Management forms and related controllers when a user creates a case folder, scores a credit request, or copies an existing folder. Four other packages reference it, forming the call chain that drives credit analysis screens. Custom code should not call these procedures directly, because signatures are subject to change without notice and no public API contract is published. Developers requiring Credit Management integration should use the documented public APIs in the AR_CMGT family. The procedural signature conventions — IN parameters for inputs and OUT NOCOPY VARCHAR2 parameters for error and result messages — confirm the package is designed for internal, error-tolerant orchestration rather than external consumption.