Results for “build_acct_from_code_flag”

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

Overview

AP_CARD_PROFILES_ALL is a Payables (AP) module table that stores information about the profiles assigned to credit cards distributed to employees. Within the Oracle EBS 12.1.1 and 12.2.2 data model, the table functions as the central configuration object that defines how a corporate or procurement credit card program behaves for a specific group of cardholders. A profile controls approval routing, accounting defaults, notification behavior, and clearing-account treatment for every card and card request associated with it. The table resides in the AP schema and is documented as VALID in the ETRM repository.

From a dimensional modeling perspective, the heuristic Data Vault classification of this table is satellite-leaning. This classification is a modeling suggestion derived from the foreign key topology: AP_CARD_PROFILES_ALL carries descriptive, mutable attributes about a credit card configuration entity, and it depends on parent reference data rather than acting purely as an intersection. Designers implementing a Data Vault or analytic layer may therefore wish to model it as a satellite attached to a card program hub, with the program relationship treated as a link.

Key Information Stored

The table is documented with 37 columns. The primary key is AP_CARD_PROFILES_PK, defined on the surrogate identifier PROFILE_ID. A unique index, AP_CARD_PROFILES_U1, is also defined on PROFILE_ID, making it the principal business-key candidate for row-level identification. Because AP_CARD_PROFILES_ALL is a multi-organization table (indicated by the _ALL suffix and the presence of ORG_ID), rows are partitioned by operating unit, so PROFILE_NAME is only unique within an operating unit context in practice.

• PROFILE_NAME and DESCRIPTION — the user-facing identity and free-text purpose of the profile.
• CARD_PROGRAM_ID — foreign key to AP_CARD_PROGRAMS_ALL, tying the profile to the overarching card program.
• CARD_GL_SET_ID — foreign key to AP_CARD_GL_SETS_ALL, defining the GL set used for accounting.
• EXCEPTION_CLEARING_CCID — foreign key to GL_CODE_COMBINATIONS, the clearing account for exception transactions.
• DEFAULT_ACCT_TEMPLATE — the default accounting template applied when building card distributions.
• BUILD_ACCT_FROM_CODE_FLAG and DIRECT_ACCT_ENTRY_FLAG — controls governing how accounting is derived or entered.
• MGR_APPROVAL_REQUIRED_FLAG, MGR_APPROVAL_LOOKUP_CODE, EMP_NOTIFICATION_LOOKUP_CODE — approval and notification behavior settings.
• ADMIN_EMPLOYEE_ID — the administrator responsible for the profile.
• ALLOW_PERSONAL_STATUS_FLAG — whether personal (non-business) transactions are permitted.
• ORG_ID — operating unit partitioning key.
• INACTIVE_DATE — date the profile is retired from use.
• The ATTRIBUTE1–ATTRIBUTE15 and ATTRIBUTE_CATEGORY columns — the standard Oracle EBS descriptive flexfield (DFF) segment set.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage centers on setup validation, approval-rule auditing, and card program reporting. A common query joins the profile to its program to confirm configuration completeness:

• List active profiles for an operating unit: SELECT profile_id, profile_name, card_program_id FROM ap_card_profiles_all WHERE org_id = :org AND inactive_date IS NULL;
• Identify profiles requiring manager approval: WHERE mgr_approval_required_flag = 'Y';
• Audit clearing account assignments by joining EXCEPTION_CLEARING_CCID to GL_CODE_COMBINATIONS.
• Reconcile card populations by counting AP_CARDS_ALL rows grouped by PROFILE_ID and ORG_ID.
• Report on DFF attribute usage by selecting ATTRIBUTE_CATEGORY with the relevant ATTRIBUTEn columns.

Reporting is frequently performed against the _ALL table directly, filtered by ORG_ID to respect multi-org security.

Related Objects

The FK relationships documented in the ETRM metadata identify the core dependencies:

• AP_CARD_PROGRAMS_ALL — parent program; joined on CARD_PROGRAM_ID.
• AP_CARD_GL_SETS_ALL — GL set definition; joined on CARD_GL_SET_ID.
• GL_CODE_COMBINATIONS — clearing account; joined on EXCEPTION_CLEARING_CCID.
• AP_CARDS_ALL — child cards referencing PROFILE_ID.
• AP_CARD_PROFILE_LIMITS_ALL — per-profile transaction limits referencing PROFILE_ID.
• AP_CARD_REQUESTS_ALL — card requests referencing PROFILE_ID.

These relationships confirm the table's role as the configuration anchor for the entire credit card lifecycle within Oracle Payables.