Search Results translate_adp_row




Overview
Explore in AI Chat

Overview

The APPS.AR_CMGT_DP_TABLE_HANDLER package is a data-maintenance utility within the Oracle Receivables Credit Management (AR_CMGT) module of Oracle E-Business Suite. Its purpose is to encapsulate the insert, update, delete, translation, and loading of credit-management data point definitions. A "data point" is a configurable unit of information that Credit Management evaluates when scoring customers, displaying information on the credit checklist, or driving credit decisions. This package provides the low-level table handler — an AUTHID CURRENT_USER PL/SQL unit — through which the seeded and user-defined data point metadata is maintained in the underlying base, translation, and view tables.

The package was originally shipped with a header identifying revision 120.12 dated 2006, reflecting its role as a stable seeded object. In ETRM 12.2.2 it carries an API classification of OTHER, indicating it is not a formally published public API but a supporting handler used internally by Credit Management and by related setup or migration utilities.

Key Procedures and Functions

The package exposes ten documented procedures, organized into three functional groups.

  • Standard row maintenance: INSERT_ROW, UPDATE_ROW, and DELETE_ROW manage the base data point records, accepting data point naming, category and sub-category, scoring and checklist flags, enabled flag, application and parent identifiers, package and function names, return data type and date format, and audit columns.
  • ADP (application data point) row maintenance: INSERT_ADP_ROW and UPDATE_ADP_ROW provide an alternate insert/update path for application data points, adding a function_type parameter and ordering the remaining attributes consistently with the ADP variant.
  • Translation and loader utilities: ADD_LANGUAGE adds a language row for a data point; TRANSLATE_ROW updates the translated text (such as name and description) for an existing data point in a target language; LOAD_ROW and LOAD_ADP_ROW perform the standard loader pattern of insert-or-update; and TRANSLATE_ADP_ROW applies the translation update specifically to the ADP variant of the record.

The search term "translate_adp_row" corresponds directly to TRANSLATE_ADP_ROW, the procedure used to maintain the translated attributes of an application data point definition.

Tables Accessed

The package operates against a small set of documented objects, referenced through APPS synonyms.

  • AR_CMGT_DATA_POINTS_B — the base table holding data point definitions; INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOAD_ROW write here.
  • AR_CMGT_DATA_POINTS_S — the sequence source used to generate primary key values for new data point rows.
  • AR_CMGT_DATA_POINTS_TL — the translation table storing language-specific name and description text; ADD_LANGUAGE, TRANSLATE_ROW, and TRANSLATE_ADP_ROW maintain this table.
  • FND_LANGUAGES — the Oracle Application Object Library language repository, consulted to validate or resolve installed languages during translation operations.
  • DUAL — used for single-row utility queries and sequence value retrieval.

This structure follows the standard Oracle multi-language base/translation design, in which physical columns live in the _B table while translatable text is held in the _TL table.

Usage Notes

In practice, AR_CMGT_DP_TABLE_HANDLER is invoked indirectly rather than directly by end users. It is typically called from Credit Management setup forms, from concurrent programs that seed or upgrade data point definitions, and from custom code that registers user-defined data points or migrates configurations between environments. The LOAD_ROW and LOAD_ADP_ROW procedures are the natural entry points for loader-based deployment, while the TRANSLATE variants are used after the base row exists to populate language-specific text. Because the package is classified as OTHER rather than a supported public API, Oracle recommends that customizations treat it as an internal handler and, where possible, use the established setup interfaces instead of calling these procedures directly. Its dependencies on the base, sequence, and translation tables mean that any direct invocation must supply a valid data point identifier, application identifier, and audit columns to preserve data integrity.