Search Results cn_source




Overview
Explore in AI Chat

Overview

The APPS.CN_SCA_INTERFACE_MAP_PVT package body is a private (PVT) PL/SQL implementation unit within the Oracle E-Business Suite (EBS) Contracts (CN) module, specifically the Contract Authoring / Sales Contract Agreement (SCA) integration framework. Its role is to map and stage contract data into the SCA open interface so that external or upstream sources can be validated and loaded into the core Contracts repository. In EBS 12.1.1 and 12.2.2, this object carries a VALID status in the APPS schema and is documented under ETRM 12.2.2 as a PVT-classified API, meaning it is not intended for direct invocation by external consumers but is called from higher-level public APIs or concurrent programs within the same product family.

Because the user searched on "cn_source", it is worth noting that CN_SOURCE is a documented table referenced by this package. The package depends on it alongside repository and object metadata tables such as CN_REPOSITORIES, CN_OBJECTS, and CN_MODULES, and it participates in the SCA header staging through CN_SCA_HEADERS_INTERFACE. The presence of FND_API, FND_MESSAGE, and FND_MSG_PUB dependencies confirms that the package conforms to the standard EBS API error-handling model, returning status and message stacks rather than raising raw exceptions.

Key Procedures and Functions

ETRM documents a single procedure for this private package:

  • GENERATE — The principal entry point that performs the interface mapping generation. It assembles the mapping between staged source records and target contract objects, driving the transformation from source-side metadata into the SCA interface structures. Its name and role indicate that it produces (or regenerates) the mapping rows consumed downstream by the SCA load process.

No parameter list is documented in the ETRM metadata, and none is asserted here. In practice, private APIs of this class typically accept a standard p_init_msg_list, p_commit, x_return_status, x_msg_count, and x_msg_data argument signature consistent with FND_API conventions, but the documented facts support only that a GENERATE routine exists.

Tables Accessed

The package references the following tables through APPS synonyms:

  • CN_SOURCE — source-definition metadata that identifies where contract data originates; central to the mapping logic given the user's search term.
  • CN_REPOSITORIES — repository definitions that group contract objects and modules.
  • CN_OBJECTS and CN_MODULES — the object and module metadata describing the contract entities being mapped.
  • CN_SCA_HEADERS_INTERFACE — the SCA open-interface header staging table into which mapped header rows are written.
  • CN_SCA_RULE_ATTRIBUTES — attribute-level rules governing how source values map to interface columns.
  • DBMS_APPLICATION_INFO, DBMS_SQL, DUAL, PLITBLM, and USER_ERRORS — utility and runtime objects, indicating dynamic SQL usage, session context tracking, compilation-error inspection, and use of a PL/SQL index-by table type.

Additionally, the package depends on CN_OBJECTS_PKG, CN_OBJ_PACKAGES_V, and CN_UTILS, which supply object retrieval and shared utility logic rather than direct table access.

Usage Notes

As a PVT package, CN_SCA_INTERFACE_MAP_PVT is not called directly from forms or from customer-written code. It is invoked by the corresponding public-layer SCA APIs and by concurrent programs in the Contracts product that stage and validate interface data. The metadata records that the package is referenced by one other package and references itself, consistent with a private implementation supporting a public wrapper. Customizations should target the public API layer rather than this private body, since its signature and internal logic are unguaranteed across patch levels in 12.1.1 and 12.2.2.