Search Results code_set_id

Overview

The AP_CARD_CODE_SETS_ALL table is a core data structure within the Oracle E-Business Suite Payables (AP) module, specifically supporting the management of corporate credit card programs. It functions as a master repository for defining and storing descriptive information about credit card code sets. These code sets are logical groupings of transaction codes (e.g., MCC - Merchant Category Codes) that are assigned to and utilized by specific card programs. The table's role is to provide a centralized definition that can be referenced across the system to standardize how credit card transaction data is categorized and processed, enabling consistent validation, reporting, and reconciliation of corporate card expenses. Its "ALL" suffix indicates it is a multi-organization table, storing data partitioned by the operating unit.

Key Information Stored

The primary data stored in this table defines the identity and attributes of a code set. The most critical column, as indicated by the user's search and the primary key definition, is CODE_SET_ID. This is the unique system-generated identifier for each code set record. While the provided metadata excerpt does not list all columns, typical columns in such a master definition table would include: CODE_SET_NAME for the user-defined name of the set; DESCRIPTION; ENABLED_FLAG to control active status; START_DATE_ACTIVE and END_DATE_ACTIVE for setting valid date ranges; and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN). The ORG_ID column is present to support multi-org architecture.

Common Use Cases and Queries

This table is primarily accessed during the setup and maintenance of credit card programs and for reporting on code set usage. Common operational scenarios include creating a list of all active code sets for a given operating unit to assign to a new card program, or querying the details of a specific set referenced in an error during transaction import. A typical query pattern involves joining to related transaction tables for analysis.

• Listing all code sets for an operating unit: SELECT code_set_id, code_set_name, description FROM ap_card_code_sets_all WHERE org_id = :org_id AND enabled_flag = 'Y' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
• Finding which card program uses a specific code set: SELECT prog.card_program_name FROM ap_card_programs_all prog WHERE prog.card_code_set_id = :p_code_set_id;

Related Objects

As per the documented foreign key relationships, AP_CARD_CODE_SETS_ALL is a parent table to two key transactional tables in the credit card management flow.

• AP_CARD_CODES_ALL: This child table stores the individual transaction codes (e.g., specific MCCs) that belong to a code set. The foreign key AP_CARD_CODES_ALL.CODE_SET_ID links each code directly to its parent set defined in this table.
• AP_CARD_PROGRAMS_ALL: This table defines the card programs themselves. The foreign key AP_CARD_PROGRAMS_ALL.CARD_CODE_SET_ID links a specific card program to the code set it uses for validating and categorizing incoming transactions.

These relationships establish that a single code set definition (in AP_CARD_CODE_SETS_ALL) can contain many individual codes (in AP_CARD_CODES_ALL) and can be assigned to one or more card programs (in AP_CARD_PROGRAMS_ALL).