Results for “code_value”

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

Overview

AP_CARD_CODES_ALL is the Oracle Payables (AP) master table that stores the credit card code definitions used by an organization for corporate card programs. Each row represents a valid card code value that can be assigned to an employee's corporate credit card, validated against the issuing card program, and later matched during expense feed processing. The table is owned by the AP schema and is documented as VALID in ETRM for both Oracle EBS 12.1.1 and 12.2.2, containing 29 columns.

From a Data Vault modeling perspective, the heuristic classification of AP_CARD_CODES_ALL is hub-leaning. The table behaves as a durable business entity reference: its CODE_ID is a synthetic, non-intelligent identifier, while the descriptive attributes (CODE_VALUE, DESCRIPTION, INACTIVE_DATE, and the DFF attribute columns) act as descriptive satellites of that hub. The CODE_SET_ID foreign key to AP_CARD_CODES_ALL reinforces this pattern by grouping codes into a parent code set, which itself functions as a secondary grouping hub.

Key Information Stored

The most significant columns in AP_CARD_CODES_ALL are:

• CODE_ID — the surrogate primary key (AP_CARD_CODES_PK) and the sole unique index candidate (AP_CARD_CODES_U1). It is the value referenced by all downstream foreign keys.
• CODE_SET_ID — foreign key to AP_CARD_CODES_ALL's parent code set table (AP_CARD_CODE_SETS_ALL). It identifies the code set to which this code belongs and provides the business grouping context.
• CODE_VALUE — the actual card code value presented to users and validated during card entry and expense feed matching.
• DESCRIPTION — the human-readable description of the card code.
• INACTIVE_DATE — the date on which the code becomes inactive; null indicates an active code. This is the primary column used for effective-dating logic in queries and LOVs.
• ACCOUNT_SEGMENT_VALUE — the accounting segment value associated with the code, supporting default accounting derivation during expense feed processing.
• GROUP_FLAG — an indicator of whether the code functions as a grouping code rather than a leaf card code.
• ORG_ID — the operating unit (multi-org) identifier, enabling the same code set to be defined per business unit.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO columns used for audit trail and incremental extraction.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield (DFF) columns that gather any client-specific extensions configured on the code definition.

Common Use Cases and Queries

Typical reporting and validation scenarios for AP_CARD_CODES_ALL include listing active card codes for a given operating unit, joining to the code set, and confirming that a value entered on a corporate card is valid before posting expense feed lines.

• Active codes for an operating unit:
  SELECT c.code_id, c.code_value, c.description, cs.code_set_name
FROM ap_card_codes_all c, ap_card_code_sets_all cs
WHERE c.code_set_id = cs.code_set_id(+)
AND c.org_id = :p_org_id
AND (c.inactive_date IS NULL OR c.inactive_date > SYSDATE);
• Codes used on expense feed lines:
  SELECT f.code_id, c.code_value, COUNT(*)
FROM ap_expense_feed_lines_all f, ap_card_codes_all c
WHERE f.code_id = c.code_id
GROUP BY f.code_id, c.code_value;
• Codes with default accounting:
  Query rows where ACCOUNT_SEGMENT_VALUE is populated to review accounting defaults applied during expense feed processing.
• Incremental extraction for a data warehouse:
  Filter on LAST_UPDATE_DATE > :last_run to extract new and changed rows into a hub-and-satellite structure keyed by CODE_ID.

These patterns support card program audits, LOV maintenance, and integration with expense reporting tools.

Related Objects

The FK metadata identifies the following key relationships:

• AP_CARD_CODE_SETS_ALL — parent code set table; joined via AP_CARD_CODES_ALL.CODE_SET_ID = AP_CARD_CODE_SETS_ALL.CODE_SET_ID. AP_CARD_CODES_ALL is the child side of this relationship.
• AP_CARD_PROFILE_LIMITS_ALL — profile limit rules reference this table twice: AP_CARD_PROFILE_LIMITS_ALL.START_CODE_ID and AP_CARD_PROFILE_LIMITS_ALL.END_CODE_ID both point to AP_CARD_CODES_ALL.CODE_ID, defining the lower and upper bounds of a card code range.
• AP_EXPENSE_FEED_LINES_ALL — the expense feed line table records transactions whose card code is validated against AP_CARD_CODES_ALL.CODE_ID. This is the highest-volume referencing table.

Collectively, these objects form the corporate card configuration cluster in Oracle Payables: code sets define the containers, AP_CARD_CODES_ALL defines the individual card codes, AP_CARD_PROFILE_LIMITS_ALL constrains spending ranges, and AP_EXPENSE_FEED_LINES_ALL captures the transaction-level usage.