Search Results ap_card_profile_limits_all




Overview
Explore in AI Chat

Overview

The AP_CARD_PROFILE_LIMITS_ALL table is a data object within the Oracle E-Business Suite Payables (AP) module. As per the official ETRM documentation, its primary description is "Reserved for a future feature." This indicates the table's structure is in place within the application's schema, but its associated functionality is not active or exposed in the current releases, including versions 12.1.1 and 12.2.2. Its intended role, inferred from its name and relationships, is to store limit-based rules or constraints associated with card profiles, likely for corporate purchasing or payment card management. Being an "ALL" table signifies it is a multi-organization structure capable of storing data for multiple operating units.

Key Information Stored

While the specific business purpose is reserved, the table's primary key and foreign key constraints define its core structural elements. The central column is PROFILE_LIMIT_ID, which serves as the unique identifier (primary key) for each limit record. The table is fundamentally linked to a card profile via the PROFILE_ID column, which references the AP_CARD_PROFILES_ALL table. Furthermore, it establishes relationships with card codes through two columns: START_CODE_ID and END_CODE_ID. Both columns are foreign keys to the AP_CARD_CODES_ALL table, suggesting the table is designed to define limits applicable to a range of card codes (e.g., merchant category codes). Other typical columns in such a structure, though not explicitly listed in the provided metadata, could include limit amounts, currencies, period types (daily, monthly), and effective dates.

Common Use Cases and Queries

Given its "reserved" status, there are no standard application use cases or user interfaces leveraging this table in the documented EBS releases. Direct data manipulation or reporting from this table is not a standard practice. Should investigation be required for data cleanup or migration purposes, a basic query to examine any existing data would follow this pattern:

SELECT profile_limit_id, profile_id, start_code_id, end_code_id
FROM ap_card_profile_limits_all
WHERE org_id = :org_id;

Any operational reporting or integration related to card profile limits would utilize other, active application tables, interfaces, or standard APIs.

Related Objects

The table maintains defined foreign key relationships with other Payables tables, as documented in the ETRM metadata:

  • AP_CARD_PROFILES_ALL: Linked via the PROFILE_ID column. This is the parent table for card profile definitions.
  • AP_CARD_CODES_ALL: Linked via two separate foreign keys.
    • START_CODE_ID: References the beginning of a card code range for the limit.
    • END_CODE_ID: References the end of a card code range for the limit.

The primary key constraint AP_CARD_PROFILES_LIMITS_PK on the PROFILE_LIMIT_ID column ensures the uniqueness of each record within this table.