Results for “variable_name”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ECE_PROC_MAPPINGS_UPG is an upgrade staging table owned by the EC schema within the Oracle e-Commerce Gateway module. Its documented purpose is to serve as the upgrade table for ECE_PROCEDURE_MAPPINGS, the runtime repository that defines how inbound and outbound interface transactions are mapped to stored procedures and parameters during processing. Because it is an upgrade table, it exists primarily to hold pre-conversion data during migration from an earlier release to Oracle EBS 12.1.1 or 12.2.2, after which the seeded upgrade logic reads, transforms, and merges the staged rows into the production ECE_PROCEDURE_MAPPINGS table.

The object is documented with a status of VALID, six columns, and a primary key constraint named OCO_18586929 defined on PROCMAP_ID. No foreign key relationships are documented, and the heuristic Data Vault classification mined from the FK structure is standalone. In Data Vault modeling terms, this suggests treating the table as an isolated structure rather than a hub, link, or satellite; because it is a transient upgrade artifact with no declared parent relationships, it does not participate in a dimensional or Data Vault network in the conventional sense.

Key Information Stored

The documented physical schema consists of six columns. The most significant are:

  • PROCMAP_ID — the surrogate primary key, enforced by constraint OCO_18586929. It uniquely identifies each procedure mapping row carried through the upgrade.
  • TRANSTAGE_ID — identifies the interface transaction stage (for example, an inbound or outbound gateway transaction stage) to which the procedure mapping applies.
  • PARAMETER_NAME — the name of the parameter passed to the mapped procedure.
  • ACTION_TYPE — the action or operation category governing how the mapping is invoked.
  • VARIABLE_LEVEL — indicates the level at which the mapped variable is resolved (for example, header versus line level).
  • VARIABLE_NAME — the name of the runtime variable that supplies the parameter value.

PROCMAP_ID functions as the surrogate primary key and is the only documented unique identifier. TRANSTAGE_ID is the most likely business-key candidate, since procedure mappings are logically grouped by transaction stage, but the metadata does not document a unique index on it, so uniqueness should be verified before relying on it in joins.

Common Use Cases and Queries

The principal use case is verifying that an upgrade completed correctly. During a 12.1.1 or 12.2.2 migration, rows are staged here before being merged into ECE_PROCEDURE_MAPPINGS, so DBAs and technical consultants frequently compare staged rows against the production table to detect lost or duplicated mappings. A typical reconciliation query:

  • SELECT u.TRANSTAGE_ID, u.PARAMETER_NAME, u.VARIABLE_NAME FROM EC.ECE_PROC_MAPPINGS_UPG u WHERE NOT EXISTS (SELECT 1 FROM EC.ECE_PROCEDURE_MAPPINGS p WHERE p.PROCMAP_ID = u.PROCMAP_ID);
  • Counting rows per ACTION_TYPE and VARIABLE_LEVEL to confirm expected volumes survived the upgrade.
  • Joining staged and production tables on TRANSTAGE_ID to spot parameter-level discrepancies before the upgrade table is dropped.
  • Auditing VARIABLE_NAME and VARIABLE_LEVEL values to validate that runtime variable bindings were preserved.

Because the table is a transient artifact, its presence in a live environment after the upgrade window typically indicates an incomplete or unverified conversion.

Related Objects

The most significant related objects, based on the documented purpose and relationship data, are:

  • ECE_PROCEDURE_MAPPINGS — the production target of the upgrade; joined on PROCMAP_ID and TRANSTAGE_ID.
  • ECE_PROCEDURES — parent definitions of the procedures referenced by the mappings.
  • ECE_TRANSACTIONS / ECE_TRANSTAGES — transaction-stage definitions referenced by TRANSTAGE_ID.
  • ECE_PROC_PARAMETERS — parameter definitions aligned with PARAMETER_NAME.
  • FND_LOOKUPS — commonly used to decode ACTION_TYPE and VARIABLE_LEVEL values.

No foreign keys are documented for this table, so all joins above are logical rather than enforced, and referential integrity must be validated manually during upgrade verification.