Search Results iby_result_codes




Overview
Explore in AI Chat

Overview

IBY_RESULT_CODES is a reference and control table in the Oracle Payments (IBY) module of Oracle E-Business Suite, holding in the IBY schema. It defines the set of result codes that payment processes, payment instructions, and interface request handlers can return when a request is processed. Each row pairs a specific result code with the request interface it belongs to, providing the vocabulary that Payments uses to classify the outcome of an operation — for example a successful validation, a format rejection, or a transient processing error. Application code, concurrent programs, and the Payments Result Codes setup UI read this table to translate a stored code value into a category and a message, so that users and downstream processes can react consistently.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is standalone. No dependent or parent FK relationships were identified, which suggests IBY_RESULT_CODES can be treated as a standalone reference dimension rather than a hub, link, or satellite. Its business key (REQUEST_INTERFACE_CODE, RESULT_CODE) is stable enough to anchor a small reference set, but it does not participate in a wider hub-and-link network within the documented metadata.

Key Information Stored

The table documents eleven columns. The most important are:

  • REQUEST_INTERFACE_CODE — identifies the Payments interface or request type to which the result code applies; part of the primary key.
  • RESULT_CODE — the code value itself; the second component of the primary key.
  • RESULT_CATEGORY — the classification that groups codes into families such as success, warning, or error, driving how callers interpret the outcome.
  • MESSAGE_NAME — the message identifier used to resolve the user-facing text for the code, typically through the Oracle message dictionary.
  • OBJECT_VERSION_NUMBER — the optimistic locking column used by the ORM layer when rows are updated.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS Who columns capturing audit and accountability information.
  • ZD_EDITION_NAME — the editioning column used by the EBS online patching (adop) architecture in 12.2.x to isolate editions of the row.

The surrogate key is not a single numeric column here; the primary key is the unique key IBY_RESULT_CODES_UK over (REQUEST_INTERFACE_CODE, RESULT_CODE), which also functions as the business key. A second unique index, IBY_RESULT_CODES_U1 over (REQUEST_INTERFACE_CODE, RESULT_CODE, ZD_EDITION_NAME), supports the edition-aware access pattern. There is no separate generated ID column documented.

Common Use Cases and Queries

Typical uses include validating that a returned code is defined for a given interface, joining result codes to payment process results for reporting, and populating LOVs in the Result Codes setup form. A simple lookup pattern is:

  • SELECT result_code, result_category, message_name FROM iby.iby_result_codes WHERE request_interface_code = :interface_code;
  • SELECT r.request_interface_code, r.result_code, r.result_category FROM iby.iby_result_codes r WHERE r.result_category = 'ERROR';

Reporting queries frequently join this table to interface result or process result tables to attach a human-readable category to raw outcome codes. Because the table is small and reference-like, it is a good candidate for caching in the mid-tier or for extraction into a reporting dimension. Analysts should remember that in 12.2.x the ZD_EDITION_NAME column must be filtered or grouped appropriately when querying under online patching.

Related Objects

The documented FK structure shows no explicit foreign keys, so related objects are inferred from the shared business key and Payments conventions:

  • IBY_FD_PAYMENT_RESULTS — stores payment processing outcomes whose result codes resolve through this table via RESULT_CODE and REQUEST_INTERFACE_CODE.
  • IBY_FD_PAYMENT_INSTRUCTIONS — references result codes when a payment instruction records its last processing status.
  • IBY_TRANSACTION_CODES / IBY_TRANSACTIONS — transaction result classifications use the same code vocabulary.
  • IBY_EXT_BANK_ACCOUNTS / account validation result records — account validation outcomes are catalogued with result codes.
  • FND_MESSAGES — resolves MESSAGE_NAME into translatable message text.
  • IBY_RESULT_CODES_UK / IBY_RESULT_CODES_U1 — the unique indexes enforcing the business key and edition-aware uniqueness.

Consult the Payments Result Codes setup and the IBY table reference for 12.1.1 and 12.2.2 before extending or updating this table.