Results for “user_dc_profile_code”

34 results




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

Overview

IBY_FNDCPT_USER_DC_PF_B is a foundation table within the Oracle Payments (IBY) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It stores user-defined (customer-configured) fund capture disbursement profiles, specifically the "user" debit card processing profile definitions that govern how debit card transactions are captured, settled, and queried against a funding account. The "_B" suffix designates this as the base (or "B") table in a translated pair, with the corresponding "_TL" table holding language-specific descriptive attributes.

From a Data Vault modeling perspective, this table is classified heuristically as satellite-leaning. It functions primarily as a descriptive satellite extending a core disbursement profile reference, since it holds attributes (configuration references, effective dating, audit columns) rather than pure hub or link structure. This classification is a modeling suggestion based on the foreign key topology, not a formal Oracle designation.

Key Information Stored

The table contains 13 documented columns. The surrogate primary key is enforced by the IBY_FNDCPT_USER_DC_PF_B_PK constraint, and the business-key candidate is the unique index IBY_FNDCPT_USER_DC_PF_B_UPC_U1 on USER_DC_PROFILE_CODE, which uniquely identifies each user debit card profile.

Common Use Cases and Queries

This table is typically queried when diagnosing debit card fund capture behavior, auditing which account and transaction configurations a user profile references, or reporting on active versus inactive profiles. A common pattern joins the base table to its translation table for the profile name:

  • Listing active profiles: SELECT user_dc_profile_code FROM iby_fndcpt_user_dc_pf_b WHERE inactive_date IS NULL OR inactive_date > SYSDATE;
  • Retrieving descriptive names: join IBY_FNDCPT_USER_DC_PF_TL on USER_DC_PROFILE_CODE.
  • Resolving the funding account: join to IBY_BEPKEYS on BEP_ACCOUNT_ID.
  • Auditing configuration references across the three transaction config columns to trace which online, settlement, and query configurations a profile uses.

Reporting use cases include reconciliation of profile-to-account mappings and validation of settlement configuration coverage prior to payment processing runs.

Related Objects

  • IBY_FNDCPT_USER_DC_PF_TL — Translation table joined on USER_DC_PROFILE_CODE; holds language-dependent profile text.
  • IBY_BEPKEYS — Referenced via BEP_ACCOUNT_ID; provides bank/account key context for the profile.
  • Self-referencing relationship via SYS_DC_PROFILE_CODE for system-derived profile linkage.
  • The transaction configuration identifiers (ONLINE_DEB_TRANS_CONFIG_ID, SETTLEMENT_TRANS_CONFIG_ID, QUERY_TRANS_CONFIG_ID) resolve to transaction configuration definitions within the IBY payments framework.

Together these objects form the configuration backbone for user-defined debit card disbursement processing in Oracle Payments.