Results for “iby_ecapp”

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

Overview

IBY_ECAPP is a transactional configuration table in the Oracle Payments (IBY) module of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores the registry of Electronic Commerce (EC) applications that have been enrolled with iPayment. Any Oracle Applications module that integrates with iPayment directly — through the iPayment Java or PL/SQL APIs — is treated as an EC application and requires a corresponding registration row in this table. The table therefore acts as the master reference for application-level identity within Oracle Payments, allowing iPayment to attribute payment instructions, payee records, and transaction processing activity to the correct source application.

The ETRM metadata assigns IBY_ECAPP a heuristic Data Vault classification of hub-leaning. From a dimensional modeling perspective, this suggests treating the table as a hub entity: ECAPPID is a stable, surrogate identifier for an EC application, and downstream transactional tables reference it rather than duplicating application attributes. The relatively small column count and its role as a parent to IBY_PAYEE reinforce this interpretation.

Key Information Stored

The documented physical schema for 12.2.2 contains eleven columns. The most significant are listed below.

• ECAPPID — the surrogate primary key, enforced by the unique index IBY_ECAPP_ECAPPID_U1 (ECAPPID, ZD_EDITION_NAME). This is the value propagated to dependent tables such as IBY_PAYEE.
• NAME — the descriptive, user-facing name of the registered EC application.
• APPLICATION_SHORT_NAME — the Oracle Applications short name identifying the integrated module. Together with ZD_EDITION_NAME it forms the business-key candidate indexed by IBY_ECAPP_APPSHORTNAME_U2.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Applications framework to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns recording who created and last modified the registration row, and through which login session.
• SECURITY_GROUP_ID — the multi-tenant security discriminator, with a foreign key to FND_SECURITY_GROUPS.
• ZD_EDITION_NAME — the editioning column that supports online patching in 12.2.x and participates in both unique indexes.

The coexistence of a surrogate key (ECAPPID) and a separate business-key candidate (APPLICATION_SHORT_NAME plus edition) is notable: the numeric identifier is used for referential integrity, while the short name provides the human-readable and integration-friendly identity.

Common Use Cases and Queries

Typical uses center on identifying which applications are enabled for iPayment and correlating payees to their originating application.

• Listing all registered EC applications with their surrogate and business identifiers:

  SELECT ecappid, name, application_short_name
  FROM   iby.iby_ecapp
  ORDER  BY application_short_name;

• Resolving the application behind a given payee record:

  SELECT p.payee_id, p.payee_name, e.name AS ec_application
  FROM   iby.iby_payee p, iby.iby_ecapp e
  WHERE  p.ecappid = e.ecappid;

• Auditing registration changes over a date range using the WHO columns.
• Reporting payee counts grouped by EC application to assess integration coverage.

Because the table is low-volume configuration data, queries are inexpensive and are frequently embedded in payment diagnostics and reconciliation reports.

Related Objects

• IBY_PAYEE — the principal dependent table; IBY_PAYEE.ECAPPID has a foreign key to IBY_ECAPP.ECAPPID, so every payee is associated with exactly one EC application.
• FND_SECURITY_GROUPS — referenced by IBY_ECAPP.SECURITY_GROUP_ID, providing the security group context for each registration row.
• iPayment Java and PL/SQL APIs — the integration interfaces that read the ECAPPID at runtime to attribute processing to a registered application.
• IBY_ECAPP_PK, IBY_ECAPP_ECAPPID_U1, IBY_ECAPP_APPSHORTNAME_U2 — the primary key constraint and unique indexes that enforce row identity and the application short-name business key.