Search Results update_acc

Overview

CSM_ACC_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose is to provide generic procedures that manipulate "ACC" tables and mark dirty records for users in process. In the Oracle EBS architecture, ACC tables are the Application Change Control staging tables used by the Oracle iSetup and Applications Configuration Management (ACM) infrastructure to capture, track, and publish configuration data changes. The package therefore functions as a low-level data manipulation layer that other configuration management packages call to insert, update, delete, and resolve records across arbitrary ACC staging tables without each caller needing to know the physical table structure in advance.

The source header indicates the package was created in September 2002 by Anurag, with a later revision header dated 2005 (csmeaccs.pls 120.1). ETRM classifies this object's API type as OTHER, meaning it is a supporting/internal package rather than a published business API. This classification is consistent with its role as a shared utility invoked by other infrastructure code rather than directly by end users.

Key Procedures and Functions

The ETRM metadata documents four procedures, three of which are visible in the supplied source excerpt:

• INSERT_ACC — Inserts a new row into a specified ACC table. It accepts a list of publication item names, the target ACC table name, the sequence name used to generate the primary key, the user ID, and up to three primary key columns (each with numeric, character, and date value variants) so that the procedure can address tables with composite or single-column keys.
• DELETE_ACC — Removes a row from a specified ACC table. It takes the publication item list, the ACC table name, and up to three primary key definitions expressed as name/value pairs (numeric, character, or date), matching the key structure established by INSERT_ACC.
• UPDATE_ACC — Modifies an existing row in an ACC table. Consistent with the INSERT_ACC and DELETE_ACC signatures, it operates on a named ACC table using the same primary key parameter pattern.
• GET_ACC_ID — Resolves and returns the ACC identifier for a given record or publication item. This is the object the user searched for ("get_acc_id"). Callers use it to obtain the surrogate ACC ID after an insert or to look up an existing ACC ID before performing an update or delete, ensuring the correct staging row is targeted.

The package also declares a PL/SQL collection type, t_publication_item_list, a table of VARCHAR2(30) that carries the list of publication items affected by each operation. This type is central to the package's design, allowing a single call to associate a change with multiple publication items at once.

Tables Accessed

ETRM records the following objects referenced through APPS synonyms:

• ASG_USER — Used to resolve or validate the user identity passed into the procedures. The user ID is required because the package marks dirty records on behalf of a specific user in process, supporting the configuration management dirty-record tracking model.
• JTF_RS_RESOURCE_EXTNS — The resource extensions table from the CRM/JTF resource model, referenced for user/resource attribute lookups associated with the change-tracking logic.
• DBMS_SQL — The Oracle dynamic SQL package. Because CSM_ACC_PKG accepts an arbitrary ACC table name at runtime, it must build and execute SQL dynamically using DBMS_SQL (or a comparable native dynamic mechanism) to target tables unknown at compile time.
• PLITBLM — The PL/SQL internal index-by table management package, used internally for manipulating PL/SQL collections such as t_publication_item_list.

Usage Notes

CSM_ACC_PKG is not intended for direct invocation by end users or through standard EBS forms. It is an internal infrastructure package: ETRM indicates it is referenced by 46 other packages, reflecting its role as a shared utility consumed by the broader Application Configuration Management stack. Typical callers invoke INSERT_ACC, DELETE_ACC, UPDATE_ACC, and GET_ACC_ID as part of iSetup/ACM extract-and-publish processing, where configuration changes must be staged, flagged as dirty for specific users, and later reconciled.

Because the procedures accept dynamic table and column names, custom extensions that reuse these procedures must supply valid, existing ACC table names and correctly typed primary key values matching the target table's columns. The package's dependency on ASG_USER and JTF_RS_RESOURCE_EXTNS means it assumes the standard EBS user and resource schema are present. The 2005 file revision and the absence of later changes in the documented metadata suggest the package has remained stable across the 12.1.1 and 12.2.2 releases, and customizations should treat it as a read-only, non-supported internal API rather than a formally supported integration point.