Results for “ap_card_profiles_limits_pk”

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

Overview

AP_CARD_PROFILE_LIMITS_ALL is a Payables (AP) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. Per ETRM (Electronic Technical Reference Manual) metadata, the object is owned by the AP schema, holds VALID status, and is described as "Reserved for a future feature." This description indicates that Oracle registered the table structure and its API/relationship footprint during the design and release cycle but has not activated the functionality it is intended to support in the documented releases. In practice, the table exists in the AP schema with a complete physical definition and referential integrity, but is not populated or maintained by standard Payables processing for corporate card profile management.

The table is a child in a multi-table relationship. Its documented foreign keys point to AP_CARD_PROFILES_ALL (the parent corporate card profile entity) and, twice, to AP_CARD_CODES_ALL. This dependency pattern distinguishes it from AP_CARD_PROFILES_ALL itself: whereas AP_CARD_PROFILES_ALL holds the profile header or definition, AP_CARD_PROFILE_LIMITS_ALL appears intended to store per-profile limit and control rules, such as amount caps, count caps, and time-unit constraints that would be evaluated during card transaction validation.

ETRM's heuristic Data Vault classification for this object is link. As a modeling suggestion, this classification reflects the table's role as an associative structure: it sits between AP_CARD_PROFILES_ALL and AP_CARD_CODES_ALL and carries its own descriptive attributes, making it neither a pure hub nor a pure satellite. The relational pattern (two references to the same dimension table, AP_CARD_CODES_ALL) also suggests a start-to-end or range-based modeling pattern typical of limit definitions.

Key Information Stored

The table carries 30 documented columns in the ETRM 12.2.2 physical schema. The most significant are summarized below.

• PROFILE_LIMIT_ID — the surrogate primary key. It is the sole column in the primary key constraint AP_CARD_PROFILES_LIMITS_PK and in the unique index AP_CARD_PROFILE_LIMITS_U1. This is the business-key candidate exposed for joins and lookups; there is no other unique index documented.
• PROFILE_ID — foreign key to AP_CARD_PROFILES_ALL. Identifies the corporate card profile to which the limit belongs.
• START_CODE_ID and END_CODE_ID — both foreign keys to AP_CARD_CODES_ALL. They define the code range (or boundary codes) over which the limit applies.
• EXCLUSION_FLAG — indicates whether the referenced code or range is treated as an exclusion from the profile limit.
• TIME_UNIT_LOOKUP_CODE — a lookup-driven value defining the period or unit against which the limit is measured (for example, a daily, weekly, or per-transaction basis).
• COUNT — numeric quantity limit, expressed in the unit identified by TIME_UNIT_LOOKUP_CODE.
• AMOUNT — monetary limit value associated with the profile and code range.
• ORG_ID — operating unit or organization identifier, enabling multi-org (MOAC) partitioning of the limit rows.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard audit and concurrent-manager who-columns present on almost all Oracle EBS transactional tables.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (descriptive flexfield) extension columns, allowing clients to add context-sensitive limit attributes without schema changes.

Common Use Cases and Queries

Because the table is documented as reserved for a future feature, production use in 12.1.1 and 12.2.2 is typically limited to (a) schema verification during upgrades or patching, (b) impact analysis before applying patches that alter the AP card schema, and (c) data-model documentation and reverse-engineering exercises. Reporting queries are usually constructed to confirm emptiness or to model future behavior rather than to extract live business data.

• Confirming the table is unpopulated in the current instance:

  SELECT COUNT(*) FROM ap.ap_card_profile_limits_all;

• Reviewing structural metadata (columns, data types, nullability):

  SELECT column_name, data_type, nullable
  FROM   dba_tab_columns
  WHERE  owner = 'AP'
  AND    table_name = 'AP_CARD_PROFILE_LIMITS_ALL'
  ORDER BY column_id;

• Listing defined limits joined to their parent profile:

  SELECT p.profile_id, l.profile_limit_id, l.amount, l.count,
         l.time_unit_lookup_code, l.exclusion_flag
  FROM   ap.ap_card_profile_limits_all l
  JOIN   ap.ap_card_profiles_all      p
    ON   p.profile_id = l.profile_id;

• Resolving start and end codes for a limit:

  SELECT l.profile_limit_id,
         sc.code AS start_code,
         ec.code AS end_code
  FROM   ap.ap_card_profile_limits_all l
  LEFT JOIN ap.ap_card_codes_all sc ON sc.code_id = l.start_code_id
  LEFT JOIN ap.ap_card_codes_all ec ON ec.code_id = l.end_code_id;

• Checking multi-org distribution by operating unit:

  SELECT org_id, COUNT(*) FROM ap.ap_card_profile_limits_all GROUP BY org_id;

In 12.2.2 specifically, upgrade and patching teams often query DBA-level metadata (DBA_TABLES, DBA_CONSTRAINTS, DBA_INDEXES) to verify that AP_CARD_PROFILES_LIMITS_PK and AP_CARD_PROFILE_LIMITS_U1 exist intact, since a broken unique index here would block any future activation of the feature.

Related Objects

The following objects are the most significant dependencies for AP_CARD_PROFILE_LIMITS_ALL, derived from the documented foreign keys and primary key.

• AP_CARD_PROFILES_ALL — parent table. Joined via AP_CARD_PROFILE_LIMITS_ALL.PROFILE_ID = AP_CARD_PROFILES_ALL.PROFILE_ID. Provides profile-level context (card program, employee, default limits).
• AP_CARD_CODES_ALL — referenced twice. Joined via START_CODE_ID and END_CODE_ID. Supplies the code dictionary against which limits and exclusions are expressed.
• AP_CARD_PROFILES_LIMITS_PK — the primary key constraint on PROFILE_LIMIT_ID; guarantees row uniqueness.
• AP_CARD_PROFILE_LIMITS_U1 — the unique index on PROFILE_LIMIT_ID underlying the PK, and the only documented business-key candidate.
• AP_CARD_CODES_ALL (reverse relationship) — any dependent lookups or reporting on card codes must account for this table's FK columns when building exclusion logic.
• AP_CARD_PROFILES_ALL (reverse relationship) — profile deletion or merge logic must respect this child table to preserve referential integrity.
• DBA_TAB_COLUMNS / DBA_CONSTRAINTS / DBA_INDEXES — data dictionary views used to validate the physical structure during upgrades to 12.2.2.
• FND Lookups (TIME_UNIT_LOOKUP_CODE) — the lookup type referenced by the time-unit column; not an FK, but required for any interpretation of COUNT values.

Together these relationships confirm that AP_CARD_PROFILE_LIMITS_ALL is a structurally complete but functionally dormant component of the Payables corporate card data model in EBS 12.1.1 and 12.2.2.