Search Results iby_tangible




Overview
Explore in AI Chat

Overview

The IBY_TANGIBLE table is a core data object within the Oracle E-Business Suite (EBS) Payments (IBY) module. It serves as a central repository for storing high-level information about tangible payment items, specifically bills or orders. In the context of the Payments architecture, this table acts as a master record for the underlying business document that necessitates a payment transaction. Its primary role is to provide a referential entity that can be linked to detailed payment transaction summaries, enabling the tracking and reconciliation of payments back to their original source documents across the financial ecosystem of EBS.

Key Information Stored

While the provided ETRM metadata does not list specific columns beyond the primary key, the structural information reveals critical data points. The table's primary key is the column MTANGIBLEID, which uniquely identifies each bill or order record. A significant foreign key relationship is established via the column SOURCE_OBJECT_TYPE_CODE, which links to the JTF_OBJECTS_B table. This linkage is fundamental to the Oracle Trading Community Architecture (TCA) model, indicating that tangible items are categorized and defined as specific object types within the broader EBS framework. This structure allows the Payments module to generically support bills and orders originating from various source applications.

Common Use Cases and Queries

The primary use case for the IBY_TANGIBLE table is in payment inquiry and reconciliation reporting. Financial users and system integrators query this table to understand the universe of documents that have entered the payment stream. A common reporting pattern involves joining IBY_TANGIBLE to the transaction summaries table to get a complete view of a payment's origin and status. For example, to list all tangible items along with their associated payment transaction counts, one might use a query such as:

  • SELECT t.mtangibleid, t.source_object_type_code, COUNT(ts.mtangibleid) AS trx_count FROM iby_tangible t LEFT JOIN iby_trxn_summaries_all ts ON t.mtangibleid = ts.mtangibleid GROUP BY t.mtangibleid, t.source_object_type_code;

Another critical use case is during data validation and cleanup, where queries check for orphaned records or validate the integrity of the SOURCE_OBJECT_TYPE_CODE against the JTF_OBJECTS_B table.

Related Objects

The IBY_TANGIBLE table has defined relationships with several other key Payments objects, as per the provided metadata. Its most important relationship is with the IBY_TRXN_SUMMARIES_ALL table, where MTANGIBLEID serves as a foreign key. This connection is vital, as it ties detailed payment transaction records to their source document. Furthermore, the table is linked to the foundational JTF_OBJECTS_B table through the SOURCE_OBJECT_TYPE_CODE column, anchoring payment documents within the standard EBS object taxonomy. These relationships underscore IBY_TANGIBLE's role as a pivotal junction between the transactional payment data and the master definition of business object types.