Search Results fnd_err_type_lookup

Overview

The view APPS.IBY_EXT_FD_PMT_ERR_1_0_V is a reporting and integration construct within the Oracle Payments (IBY) module of Oracle E-Business Suite. It exposes payment transaction errors associated with payment records, presenting them in a flattened, denormalized form suitable for external consumption, Business Intelligence Publisher report generation, and integration interfaces. The view is versioned with the "1_0" suffix, indicating it conforms to a defined external interface contract used by downstream systems that extract payment error information from EBS.

Its principal role is to join the transactional error repository (IBY_TRANSACTION_ERRORS) with the base payment record (IBY_PAYMENTS_ALL) and to decorate raw error codes with human-readable meanings sourced from FND_LOOKUPS. This makes the view especially useful where error codes alone would be insufficient for end users or external systems. The name prefix "EXT_FD" (external financial data / funds disbursement) signals that the view is intended for external federation or data extraction rather than internal transactional processing.

Underlying Base Objects

Per the documented ETRM metadata, the view is owned by APPS and is defined over the following base objects:

• FND_GLOBAL (PACKAGE) — the standard EBS global context package, referenced for session and security context resolution.
• FND_LOOKUPS (VIEW) — the standard Oracle Application Object Library lookups view, used here to resolve error type and error status codes into their MEANING values.
• IBY_PAYMENTS_ALL (SYNONYM) — the master synonym for the payments table, supplying PAYMENT_ID.
• IBY_TRANSACTION_ERRORS (SYNONYM) — the synonym for the transaction errors table, the primary source of each error row.

The view text joins IBY_PAYMENTS_ALL to IBY_TRANSACTION_ERRORS on PAYMENT_ID = TRANSACTION_ID, filtered to TRANSACTION_TYPE = 'PAYMENT'. It joins FND_LOOKUPS twice: an outer join ((+)) on the error type against lookup type IBY_TRANSACTION_ERROR_TYPES, and an inner join on the error status against lookup type IBY_TRANSACTION_ERROR_STATUSES. The status join is an equijoin with no outer-join marker, meaning a row is returned only when the error status resolves to a valid lookup code; the type join is optional and may return NULL meaning if no lookup entry exists.

Key Columns

• PAYMENT_ID — from IBY_PAYMENTS_ALL; the unique identifier of the payment to which the error relates.
• TRANSACTION_ERROR_ID — from IBY_TRANSACTION_ERRORS; the primary key of the error record.
• ERROR_TYPE — the raw lookup code classifying the nature of the error, resolved via FND_ERR_TYPE_LOOKUP.
• MEANING — the displayed meaning of the error type, retrieved from FND_LOOKUPS. Note the view selects FND_ERR_TYPE_LOOKUP.MEANING twice in the projection, so the column appears duplicated in the select list.
• ERROR_CODE — the specific application error code raised during payment processing.
• ERROR_MESSAGE — the descriptive message text stored with the error.
• ERROR_DATE — the timestamp when the error was recorded.
• ERROR_STATUS — the status code of the error, joined to FND_ERR_ST_LOOKUP on lookup type IBY_TRANSACTION_ERROR_STATUSES (this is the lookup referenced by the user's search term "fnd_err_st_lookup").

The alias FND_ERR_ST_LOOKUP is the specific lookup alias that a user searching for "fnd_err_st_lookup" is encountering — it is the join source for error status meanings within this view.

Common Use Cases and Queries

The view is typically queried to list all errors for a given payment, to report on error statuses, or to feed an external system with payment exception data.

• Listing all errors for a specific payment:

  SELECT payment_id, transaction_error_id, error_type,
         error_code, error_message, error_date, error_status
  FROM   apps.iby_ext_fd_pmt_err_1_0_v
  WHERE  payment_id = :p_payment_id;

• Filtering by error status (the lookup resolved via FND_ERR_ST_LOOKUP):

  SELECT payment_id, error_code, error_message
  FROM   apps.iby_ext_fd_pmt_err_1_0_v
  WHERE  error_status = 'NEW';

• Integration extraction by error date range:

  SELECT payment_id, transaction_error_id, error_type, meaning,
         error_code, error_message, error_date
  FROM   apps.iby_ext_fd_pmt_err_1_0_v
  WHERE  error_date >= :p_from_date
  AND    error_date <  :p_to_date;

Because the view depends on FND_GLOBAL and FND_LOOKUPS, the querying session must be initialized with the correct application context (via FND_GLOBAL.APPS_INITIALIZE) to ensure the lookup joins resolve correctly and to respect any organization or security context applicable to the payment data. Where the error status lookup is incomplete, expect rows to be silently excluded by the inner join on IBY_TRANSACTION_ERROR_STATUSES.