Results for “iby_accttype”

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

Overview

IBY_ACCTTYPE is a Payments (IBY) reference table within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. It holds the enumerated list of account types that the Payments module recognizes across the various payment instruments it manages. The table functions as a controlled lookup: rather than storing free-text descriptions of account classifications, dependent transactional and setup tables store a foreign key (ACCTTYPEID) that resolves against this central list. Typical members include Checking and Savings for bank accounts, and Visa, MasterCard, and Discover for credit cards, with the INSTRTYPE column providing the instrument-level grouping that distinguishes these categories.

Because payment instruments, payment methods, and bank account setups all depend on a consistent classification of account types, IBY_ACCTTYPE plays a foundational role in payment setup configuration and in the validation logic applied when payment records are created. Under the heuristic Data Vault classification derived from its foreign key topology, IBY_ACCTTYPE presents as a hub-leaning structure: it is a low-volatility reference entity whose primary key is referenced by multiple surrounding tables, and its own single outbound foreign key (SECURITY_GROUP_ID to FND_SECURITY_GROUPS) does not alter that characterization. This classification is a modeling suggestion rather than an EBS implementation detail.

Key Information Stored

The table is documented with 11 columns in the ETRM 12.2.2 physical schema. The most significant are:

• ACCTTYPEID — The surrogate primary key, defined by constraint IBY_ACCTTYPE_PK. This numeric identifier is the value propagated to all dependent tables. It is the object most frequently referenced when users search for iby_accttype_pk.
• ACCTTYPE — The descriptive name of the account type (for example, Checking, Savings, Visa, MasterCard), used for display and reporting.
• INSTRTYPE — The instrument type grouping that associates each account type with its payment instrument category, such as bank account or credit card.
• OBJECT_VERSION_NUMBER — The optimistic locking column used by the Oracle Applications Framework to detect concurrent updates.
• SECURITY_GROUP_ID — The foreign key to FND_SECURITY_GROUPS, supporting multi-organization and security-group partitioning of reference data.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — The standard EBS audit columns recording who created and last modified each row and when.
• ZD_EDITION_NAME — The editioning column introduced by the Online Patching (adop) architecture in 12.2, used to isolate edition-specific row versions.

The unique index IBY_ACCTTYPE_ACCTTYPEID_U1 covers ACCTTYPEID and ZD_EDITION_NAME, confirming the surrogate key as the business-key candidate within the editioning model.

Common Use Cases and Queries

IBY_ACCTTYPE is most often consumed through joins rather than queried directly. Setup validation verifies that an account type is valid for a given instrument before a bank account or credit card record is saved. Reporting queries resolve the ACCTTYPEID values stored on payment instruments into human-readable labels.

SELECT at.ACCTTYPEID, at.ACCTTYPE, at.INSTRTYPE
FROM   IBY.IBY_ACCTTYPE at
WHERE  at.INSTRTYPE = 'BANKACCOUNT'
ORDER  BY at.ACCTTYPE;

A typical reporting pattern joins the lookup to its dependents to list bank accounts with their account-type descriptions:

SELECT ba.BANKACCOUNTID, ba.ACCOUNT_NUMBER,
       at.ACCTTYPE, at.INSTRTYPE
FROM   IBY.IBY_BANKACCT ba,
       IBY.IBY_ACCTTYPE at
WHERE  ba.ACCTTYPEID = at.ACCTTYPEID;

Because the table is small and static, it is also useful in diagnostics — for example, confirming which account types exist before configuring a payment method or troubleshooting a failed instrument setup.

Related Objects

Three tables carry a documented foreign key column pointing to IBY_ACCTTYPE, and all use the ACCTTYPEID column as the join predicate:

• IBY_ACCPPMTMTHD — Payment method setup; IBY_ACCPPMTMTHD.ACCTTYPEID references IBY_ACCTTYPE.ACCTTYPEID.
• IBY_BANKACCT — Bank account definitions; IBY_BANKACCT.ACCTTYPEID references IBY_ACCTTYPE.ACCTTYPEID.
• IBY_CREDITCARD — Credit card definitions; IBY_CREDITCARD.ACCTTYPEID references IBY_ACCTTYPE.ACCTTYPEID.

In the reverse direction, IBY_ACCTTYPE itself references FND_SECURITY_GROUPS through SECURITY_GROUP_ID, tying its rows to the EBS security-group model. These four relationships constitute the complete documented dependency set for the table in Release 12.2.2.