Results for “tp_code”

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

Overview

ECE_STAGE_LEVEL2_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite e-Commerce Gateway product (EC). It is registered as a VALID database object in both release 12.1.1 and 12.2.2. The view serves a narrow, purpose-built function: it is referenced by the Oracle Forms module ECERNCON.fmb, which retrieves staging information through this view rather than querying the underlying transaction table directly. The view projects a small, distinct set of attributes describing inbound or outbound e-Commerce Gateway transactions that have reached the first transaction level.

This view does not perform joins, aggregations, or transformations. Its only logical operation beyond column projection is a DISTINCT filter, which collapses duplicate rows returned by the base table. That behavior is significant for integrations and reports, because callers can rely on the view to return unique combinations of the three exposed attributes without writing their own de-duplication logic.

Underlying Base Objects

The documented metadata lists ECE_STAGE (exposed through a SYNONYM) as the sole referenced base object. ECE_STAGE is the core staging table for e-Commerce Gateway, holding transaction records captured or generated during the gateway's translation and processing cycles before they are committed to their target application tables.

The view text applies a single predicate against that table:

• TRANSACTION_LEVEL = 1 — restricts the result set to the first transaction level in the staging hierarchy.
• SELECT DISTINCT STATUS, TRANSACTION_TYPE, TP_CODE — returns only three columns, with duplicate combinations eliminated.

Because the definition is a straight filter and projection over a synonym resolving to ECE_STAGE, the view inherits the security, indexing, and performance characteristics of that table. It carries no materialization and reflects committed data in real time.

Key Columns

The view exposes exactly three columns. Their names correspond directly to attributes of ECE_STAGE:

• STATUS — the processing state of the staged transaction, used by the gateway to indicate whether a record is pending, processed, or errored.
• TRANSACTION_TYPE — identifies the kind of e-Commerce Gateway transaction, distinguishing among the document types the gateway supports.
• TP_CODE — the trading partner code. This is the attribute most commonly associated with the view in search contexts, since it identifies which trading partner a given transaction, status, and type combination belongs to.

Because of the DISTINCT clause, these columns are presented as a distinct combination set rather than a per-row record listing. The view therefore answers the question "which combinations of status, transaction type, and trading partner exist at level 1" rather than "what is every staged transaction."

Common Use Cases and Queries

The view is typically consumed by the e-Commerce Gateway concurrent form ECERNCON.fmb, not by end-user reports, but it can be queried directly for diagnostics and support. Typical scenarios include enumerating trading partners that currently have staged level 1 activity, auditing the statuses that appear for a given transaction type, and validating configuration data before running gateway programs.

A representative query enumerating all distinct combinations is:

SELECT status, transaction_type, tp_code
FROM   apps.ece_stage_level2_v
ORDER BY tp_code, transaction_type, status;

Filtering by trading partner, a common routine when investigating a specific partner:

SELECT status, transaction_type, tp_code
FROM   apps.ece_stage_level2_v
WHERE  tp_code = :p_tp_code;

Aggregating statuses per trading partner for a configuration review:

SELECT tp_code, status, COUNT(*) status_count
FROM   apps.ece_stage_level2_v
GROUP  BY tp_code, status
ORDER  BY tp_code, status;

Because the view returns only level 1 rows and applies DISTINCT, it is unsuitable for row-level auditing or for producing transaction counts that must include duplicates or deeper levels. For such purposes, query ECE_STAGE directly, adding an appropriate TRANSACTION_LEVEL predicate. Callers requiring the same behavior as ECERNCON.fmb should query this view to remain consistent with the form's retrieval logic.