Search Results cn_sca_interface_map_pvt




Overview

APPS.CN_SCA_INTERFACE_MAP_PVT is a private PL/SQL package within the Oracle EBS Channel Revenue Management (formerly Trade Management) module. Its name reflects its role: CN denotes the Channel Revenue application family, SCA denotes the Supplier/Channel Accounting interface layer, and INTERFACE_MAP indicates a mapping utility that translates interface staging data into the internal repository structures used by the rules engine. As a private (PVT) package, it is not intended to be called directly by external consumers; it is a helper component invoked by other packages within the same application layer to support the loading and generation of interface mapping records. The package has a VALID status in the APPS schema and is documented across both 12.1.1 and 12.2.2 release families.

Key Procedures and Functions

The ETRM metadata documents a single public program unit within this package:

  • GENERATE — The core entry point of the package. Based on its name and its table dependencies, GENERATE is responsible for producing the mapping records that reconcile inbound interface rows with the repository, rule, and module definitions held in the CN data model. It orchestrates the creation or regeneration of interface mappings, using the interface header staging table and rule attribute definitions as inputs, and writes results into the appropriate CN repository structures. Because it is a private API, no public parameter list is exposed; it is intended for intra-package and sibling-package invocation only.

Tables Accessed

The package reads and writes a defined set of tables, all via APPS synonyms:

  • CN_SCA_HEADERS_INTERFACE — The interface staging header table; source of inbound records awaiting mapping.
  • CN_SCA_RULE_ATTRIBUTES — Rule attribute definitions used to determine how interface records are mapped to rules.
  • CN_REPOSITORIES — The repository master that receives or aligns with generated mapping entries.
  • CN_OBJECTS and CN_MODULES — Metadata defining the objects and modules that participate in the mapping, used to resolve targets.
  • CN_SOURCE — Source definitions that contextualise the origin of mapping data.
  • DBMS_SQL and PLITBLM — Dynamic SQL and PL/SQL table utilities, indicating that GENERATE builds and executes dynamic statements at runtime.
  • DBMS_APPLICATION_INFO — Used to register module and action names for concurrent request monitoring.
  • DUAL and USER_ERRORS — Auxiliary references; USER_ERRORS is typically consulted when dynamic SQL compilation is part of the process.

Usage Notes

CN_SCA_INTERFACE_MAP_PVT is invoked indirectly. The ETRM dependency data shows it is referenced by CN_SCA_CRRULEATTR_PVT, the rule attribute private package, and it also references itself recursively during processing. This pattern confirms that GENERATE is called as part of a larger rule-attribute and interface-mapping workflow, likely triggered by concurrent programs or form-driven actions that submit channel revenue interface processing. The presence of DBMS_APPLICATION_INFO indicates it can run under a concurrent manager, and the reliance on dynamic SQL (DBMS_SQL, PLITBLM) means behavior is data-dependent — the exact statements executed vary with the contents of CN_OBJECTS, CN_MODULES, and CN_SCA_RULE_ATTRIBUTES. Customisations should not call this package directly; instead, the supported integration point is the parent private package or the public concurrent program that drives it. Changes to the underlying CN metadata tables will directly affect mapping generation, so any extension or data fix must respect the structure expected by GENERATE.