Search Results insert_resource_extns




Overview

CSL_JTF_RESOURCE_EXTNS_ACC_PKG is an Oracle EBS 12.1.1 / 12.2.2 PL/SQL package owned by the APPS schema and classified under the API classification type OTHER. It is a member of the CSL family of packages associated with the CRM Foundation and Resource Manager modules. The package exists to maintain the ACC (Advanced Compensation / auxiliary cache) shadow copy of resource-extension records defined in JTF_RS_RESOURCE_EXTNS. It encapsulates the replication logic that keeps an alternate copy of resource-extension rows synchronized with the base table so that downstream consumers — particularly the accelerator or cached structures referenced by the "ACC" suffix — can read resource-extension data without querying the primary JTF table directly. The package exposes a single Boolean replication predicate and a symmetric set of DML wrappers for insert, update, and delete operations on a resource extension identified by its surrogate key. No business validation or complex transactional orchestration is performed here; the package's role is purely to channel changes into the ACC table structure while observing the replication eligibility rule defined by Replicate_Record.

Key Procedures and Functions

The package declares four documented program units, which together form a complete change-propagation interface. None of the documented signatures expose parameter lists beyond the resource extension identifier and resource identifier; parameter details should be taken from the package specification rather than inferred.

  • REPLICATE_RECORD — A Boolean function that evaluates whether a given resource-extension record is a candidate for replication into the ACC target. It acts as the gatekeeper for the three DML procedures, returning TRUE when replication should proceed and FALSE when it should be bypassed. Callers typically invoke it before firing an insert, update, or delete so that records excluded by replication policy are not duplicated.
  • INSERT_RESOURCE_EXTNS — Public procedure invoked when a resource-extension row must be inserted into the ACC table. It is the insert counterpart within the synchronization set and is called from the base table's insert path.
  • UPDATE_RESOURCE_EXTNS — Public procedure invoked when an existing resource-extension row must be updated in the ACC table. It propagates column-level changes from the base record to the ACC copy.
  • DELETE_RESOURCE_EXTNS — Public procedure invoked when a resource-extension row must be removed from the ACC table. This is the routine that executes when a base resource extension is deleted and its ACC shadow must be purged. Because it is a documented public entry point, it is the correct hook for custom code that must remove an ACC copy rather than issuing direct DML against the ACC table.

Tables Accessed

The only documented table referenced through APPS synonyms is JTF_RS_RESOURCE_EXTNS, the base Resource Manager table storing the descriptive extension attributes of a resource (for example, the additional columns carried on a resource record beyond the core JTF_RS_RESOURCE row). The package reads from this table to resolve the record being processed and to evaluate the Replicate_Record predicate, and it writes the corresponding row into the ACC-side structure maintained by this package family. Because the ACC target is not listed as a separately documented synonym, the write destination should be treated as the ACC variant managed internally by the package rather than the base JTF table itself.

Usage Notes

CSL_JTF_RESOURCE_EXTNS_ACC_PKG is not intended for direct end-user invocation. It is called programmatically from the base resource-extension maintenance path whenever a resource extension is created, changed, or removed, and it is referenced by three other packages in the EBS code base, indicating that the resource-extension DML is funneled through this API by upstream application logic. Typical invocation points include Resource Manager forms and the resource-extension APIs that wrap base-table DML, as well as any concurrent program or interface that bulk-maintains resource extensions. Custom integrators who must delete a resource extension should call Delete_Resource_Extns rather than issuing a DELETE against the ACC structure, because the procedure centralizes the replication checks and any dependent cleanup. Because the package is owned by APPS and marked OTHER in the API classification, it carries no formal public-API support commitment; changes to it are delivered as patched PL/SQL and should not be extended or overridden by customer code.