Results for “source_object_type_code”

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

Overview

IBY_TANGIBLE is a Payments (IBY) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores information about the bills or orders processed through Oracle Payments. In the payments data model, a "tangible" represents the underlying document — an invoice, bill, order, or other payable/receivable instrument — for which a payment transaction is initiated. The table therefore acts as the document registry that anchors transaction summaries to their originating business objects, carrying amount, currency, reference, and issuance information required by payment formatting, funding, and reconciliation processes.

From a Data Vault modeling perspective, the mined foreign-key structure classifies IBY_TANGIBLE as hub-leaning. This is a heuristic suggestion only: the table owns a single-column surrogate primary key (MTANGIBLEID) and is referenced by downstream transaction tables, which is characteristic of a hub or core entity. However, because it also carries descriptive attributes such as AMOUNT, MEMO, and ISSUEDATE, it functions in practice as a combined hub-and-attribute table rather than a pure hub.

Key Information Stored

The documented physical schema for IBY_TANGIBLE in ETRM 12.2.2 comprises 19 columns. The most significant are:

• MTANGIBLEID — Surrogate primary key, enforced by IBY_TANGIBLE_PK and the unique index IBY_TANGIBLE_MTANGIBLEID_U1. This is also the foreign-key target referenced by IBY_TRXN_SUMMARIES_ALL.
• TANGIBLEID — The business identifier of the tangible document, distinct from the surrogate key.
• AMOUNT and CURRENCYNAMECODE — The monetary value and currency of the bill or order.
• ACCTNO — Account number associated with the tangible, typically the payer or payee account used for payment routing.
• REFINFO and MEMO — Free-form reference information and payment memo text transmitted with the payment instruction.
• ISSUEDATE — The date the underlying document was issued.
• ORDER_MEDIUM — The medium by which the order or bill was placed.
• EFT_AUTH_METHOD — The electronic funds transfer authorization method applied to the tangible.
• SOURCE_OBJECT_TYPE_CODE and SOURCE_OBJECT_ID — Polymorphic reference identifying the originating object type and instance (SOURCE_OBJECT_TYPE_CODE joins to JTF_OBJECTS_B).
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant data segregation.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — Standard EBS audit and concurrency-control columns.

Common Use Cases and Queries

IBY_TANGIBLE is most commonly queried when tracing a payment transaction back to its originating bill or order, when reconciling paid amounts against transaction summaries, or when building payment reporting that requires document-level detail.

A typical join links tangibles to their transaction summaries and resolves the source object type:

• SELECT t.MTANGIBLEID, t.TANGIBLEID, t.AMOUNT, t.CURRENCYNAMECODE, s.PAYMENT_ID FROM IBY_TANGIBLE t, IBY_TRXN_SUMMARIES_ALL s WHERE t.MTANGIBLEID = s.MTANGIBLEID;
• Resolving the polymorphic source: join SOURCE_OBJECT_TYPE_CODE to JTF_OBJECTS_B to obtain the object type name for a given SOURCE_OBJECT_ID.
• Reporting by issuance period: aggregate AMOUNT by CURRENCYNAMECODE filtered on ISSUEDATE ranges.
• Memo and reference extraction for bank file generation, using MEMO and REFINFO.

Because SECURITY_GROUP_ID is present, queries executed under a secured responsibility are automatically filtered by the security group, which must be accounted for in custom reporting against this table.

Related Objects

• IBY_TRXN_SUMMARIES_ALL — The principal dependent table; its MTANGIBLEID column references IBY_TANGIBLE.MTANGIBLEID, forming the link between a tangible document and its payment transaction summary records.
• JTF_OBJECTS_B — Referenced by IBY_TANGIBLE.SOURCE_OBJECT_TYPE_CODE; supplies the object-type metadata that decodes the SOURCE_OBJECT_ID.
• FND_SECURITY_GROUPS — Referenced by IBY_TANGIBLE.SECURITY_GROUP_ID; governs row-level security across the table.
• IBY_TANGIBLE_PK / IBY_TANGIBLE_MTANGIBLEID_U1 — The primary key constraint and unique index that enforce uniqueness of MTANGIBLEID and define the Oracle Payments APIs and concurrent programs that populate the IBY payment tables maintain referential integrity with these dependent objects.