Results for “iby_f_crdt_app_status_b”

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

Overview

IBY_F_CRDT_APP_STATUS_B is a core setup and reference table in the Oracle Payments (IBY) module of Oracle E-Business Suite, holding the master definition of credit application statuses used during the credit card / funds capture lifecycle. Each row represents a distinct state that a credit application (payment authorization, settlement, or refund processing record) can occupy, such as authorized, settled, cancelled, or declined. The table is the base (the "_B" suffix denotes the base table in a translated pair) and is partnered with IBY_F_CRDT_APP_STATUS_TL, which stores the language-dependent translated status names.

Functionally, this object acts as the control list that governs which status values are valid, the permitted transitions between them, and whether updates are allowed while in a given status. It is referenced heavily by the credit card processing engine, the credit application transaction tables, and the state transition guard table. Because it holds the canonical set of statuses that drive payment processing logic, it is seeded with Oracle-delivered rows and is generally not maintained through online forms by end users.

Under a heuristic Data Vault classification, this table is best modeled as a hub: its primary key, CREDIT_APP_STATUS_ID, is a stable surrogate identifier, and multiple satellite and link-style relationships radiate outward from it. This classification is a modeling suggestion derived from the foreign key topology rather than an Oracle-prescribed designation.

Key Information Stored

The table contains 31 documented columns across the standard EBS audit, security, and descriptive attribute sets. The most significant are:

• CREDIT_APP_STATUS_ID — surrogate primary key (IBY_F_CRDT_APP_STATUS_B_PK) and the unique business identifier (IBY_F_CRDT_APP_STATUS_B_U1). This is the value propagated to all child tables.
• STATUS_CODE — the internal code identifying the status; the second unique index (IBY_F_CRDT_APP_STATUS_B_U2) enforces uniqueness, making it a business-key candidate.
• STATUS_CATEGORY_CODE — classifies the status into a higher-level grouping used by processing logic.
• STATUS_NUMBER — numeric ordering or sequence used for display and comparison.
• START_DATE_ACTIVE / END_DATE_ACTIVE — date range controlling the effective period of the status.
• UPDATE_ALLOWED_FLAG — indicates whether the underlying credit application record may be modified while in this status.
• SEEDED_FLAG — marks rows shipped by Oracle versus user-defined entries.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enabling multi-organization data security.
• OBJECT_VERSION_NUMBER — optimistic locking column preventing concurrent update conflicts.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the flexible descriptive flexfield segment columns.

The surrogate key (CREDIT_APP_STATUS_ID) should be used for joins and referential integrity, while STATUS_CODE and the translated name should be used in user-facing reporting.

Common Use Cases and Queries

Typical applications include building status lookup lists for credit application reporting, validating allowed state transitions in integration or reconciliation code, and resolving status IDs to translated labels for operational dashboards.

Resolving a status ID to its translated name:

• SELECT b.credit_app_status_id, t.status_name, b.status_code FROM iby.iby_f_crdt_app_status_b b, iby.iby_f_crdt_app_status_tl t WHERE b.credit_app_status_id = t.credit_app_status_id AND t.language = USERENV('LANG');

Listing currently active statuses for a picklist:

• SELECT credit_app_status_id, status_code FROM iby.iby_f_crdt_app_status_b WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);

Identifying statuses that block edits, useful before submitting corrections to a payment:

• SELECT status_code FROM iby.iby_f_crdt_app_status_b WHERE update_allowed_flag = 'N';

These queries support reconciliation reports, funds capture monitoring, and troubleshooting of stuck credit application records.

Related Objects

The table participates in several significant relationships:

• IBY_F_CRDT_APP_STATUS_TL — the translated satellite table; join on CREDIT_APP_STATUS_ID to obtain language-specific status names.
• IBY_F_T_CRDT_APPS_ALL_B — the credit application base table; each application references its current status via CREDIT_APP_STATUS_ID.
• IBY_F_T_CRDT_APP_ST_H — the credit application status history table; both OLD_STATUS_ID and NEW_STATUS_ID reference this table's CREDIT_APP_STATUS_ID.
• IBY_G_ST_TRANSITIONS — the allowed state-transition guard table; FROM_STATUS_ID and TO_STATUS_ID both reference CREDIT_APP_STATUS_ID, defining the valid movement graph between statuses.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID to enforce data-level security.

Together these objects form the status management backbone of Oracle Payments credit card processing, ensuring consistent, controlled, and auditable credit application state handling.