Results for “iby_f_t_crdt_apps_all_b”

42 results




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

Overview

IBY_F_T_CRDT_APPS_ALL_B is the base table of the Oracle Payments (IBY) credit application entity in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the header-level record for each credit application raised against a payment transaction summary, capturing financing terms requested or granted by a buyer, the lifecycle status of the application, associated XML documents, and the audit and multi-tenancy columns standard to the IBY schema. The table is the "_B" (base) member of a translated pair; user-facing descriptive text is held in the companion table IBY_F_T_CRDT_APPS_ALL_TL, keyed by the same CREDIT_APP_ID.

Heuristic Data Vault classification identifies this object as a hub. It carries a single-column surrogate primary key, IBY_F_T_CRDT_APPS_ALL_B_PK on CREDIT_APP_ID, and is referenced by multiple downstream entities rather than resolving a many-to-many relationship itself. This classification is a modeling suggestion derived from the foreign-key topology and should be treated as guidance rather than a documented Oracle design decision.

Key Information Stored

The table is documented with 49 columns. The core identifying and business columns are:

Common Use Cases and Queries

Credit applications are queried to report on outstanding buyer credit requests, to monitor expiring applications, and to join financing terms back to the originating transaction summary. A typical status report joins the base table to its status lookup and translated name table:

  • List active applications for an operating unit: SELECT ca.CREDIT_APP_ID, ca.TRXN_SUMMARY_ID, st.STATUS_LOOKUP_CODE, tl.NAME FROM IBY_F_T_CRDT_APPS_ALL_B ca, IBY_F_CRDT_APP_STATUS_B st, IBY_F_T_CRDT_APPS_ALL_TL tl WHERE ca.CREDIT_APP_STATUS_ID = st.CREDIT_APP_STATUS_ID AND ca.CREDIT_APP_ID = tl.CREDIT_APP_ID AND ca.ORG_ID = :p_org_id.
  • Identify applications nearing expiry: filter on EXPIRING_FLAG or EXPIRATION_DATE within a rolling window.
  • Trace an application to its payment transaction: join TRXN_SUMMARY_ID to IBY_TRXN_SUMMARIES_ALL.
  • Retrieve printed output: join CREDIT_APP_XML_ID and TERMS_N_CONDITIONS_XML_ID to IBY_TRXN_DOCUMENTS.

Because the base table is subject to translation, all user-facing queries should resolve names through IBY_F_T_CRDT_APPS_ALL_TL rather than assuming a single-language base table.

Related Objects

The following objects are most significant in the credit application relationship graph:

  • IBY_TRXN_SUMMARIES_ALL — referenced via TRXN_SUMMARY_ID; the parent transaction summary.
  • IBY_F_CRDT_APP_STATUS_B — referenced via CREDIT_APP_STATUS_ID; the status definition.
  • IBY_TRXN_DOCUMENTS — referenced twice, via CREDIT_APP_XML_ID and TERMS_N_CONDITIONS_XML_ID.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID.
  • IBY_F_T_CA_GRNTRS_B — child table; references this table via CREDIT_APP_ID.
  • IBY_F_T_CRDT_APPS_ALL_TL — translated attributes, keyed by CREDIT_APP_ID.
  • IBY_F_T_CRDT_APP_REVS — revision history per credit application.
  • IBY_F_T_CRDT_APP_ST_H — status history per credit application.
  • IBY_F_T_EMAIL_NOTIF_LOG and IBY_G_T_MESSAGES — notification and messaging records keyed by CREDIT_APP_ID.