Search Results ap_card_profiles_all




Overview
Explore in AI Chat

Overview

The AP_CARD_PROFILES_ALL table is a core data object within the Oracle E-Business Suite Payables (AP) module, specifically for the Corporate Credit Card (CCC) functionality. It serves as the master repository for defining and managing credit card profiles. These profiles are templates or rule sets that are assigned to credit cards distributed to employees. The table's primary role is to centralize the configuration of spending controls, accounting rules, and program associations, ensuring consistent policy enforcement across all corporate cards issued to the workforce.

Key Information Stored

The table stores the defining attributes of a credit card profile. While the full column list is not provided in the excerpt, the documented foreign keys and context reveal critical data points. The primary key, PROFILE_ID, uniquely identifies each profile. Essential columns include CARD_PROGRAM_ID, linking the profile to a specific credit card program in AP_CARD_PROGRAMS_ALL, and CARD_GL_SET_ID, which associates the profile with a General Ledger account set for standard transactions. The EXCEPTION_CLEARING_CCID column holds the Code Combination ID (CCID) that defines the clearing account for exception items. Other typical profile data stored would include profile name, description, effective dates, and various flags controlling transaction validation and employee liability.

Common Use Cases and Queries

A primary use case is reporting and auditing which profiles are assigned to employees' cards to verify policy compliance. Administrators often query this table to review profile settings before mass card issuance or program changes. Common SQL patterns include joining to card and employee tables to list active assignments. For example, to find all cards with a specific profile's accounting setup:

  • SELECT acpa.card_id, acpa.employee_id, acp.profile_name, acgs.name gl_set_name FROM ap_cards_all acpa, ap_card_profiles_all acp, ap_card_gl_sets_all acgs WHERE acpa.profile_id = acp.profile_id AND acp.card_gl_set_id = acgs.card_gl_set_id AND acp.profile_name = '&PROFILE_NAME';

Another critical use case is troubleshooting accounting errors by verifying the GL accounts (EXCEPTION_CLEARING_CCID) linked to a profile or analyzing spending by joining profile limits.

Related Objects

The table has integral relationships with several key Payables objects, as documented by its foreign keys. It is a central hub in the credit card data model.

  • AP_CARD_PROGRAMS_ALL: A profile belongs to one card program (CARD_PROGRAM_ID).
  • AP_CARD_GL_SETS_ALL: A profile uses one GL account set for standard transactions (CARD_GL_SET_ID).
  • GL_CODE_COMBINATIONS: A profile specifies a clearing account for exceptions (EXCEPTION_CLEARING_CCID).
  • AP_CARDS_ALL: One-to-many relationship. Many individual cards (PROFILE_ID) can be assigned to a single profile.
  • AP_CARD_PROFILE_LIMITS_ALL: One-to-many relationship. A profile can have multiple spending limits (PROFILE_ID) defined (e.g., per transaction type).
  • AP_CARD_REQUESTS_ALL: One-to-many relationship. Card requests can be associated with a specific profile (PROFILE_ID).