Results for “card_exp_type_lookup_code”

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

Overview

AP.AP_CARD_PARAMETERS is a Payables reference table that stores card expense type mappings. Its documented description, "Card Expense Type Mappings," indicates that it associates a card expense type lookup value with a specific expense report parameter set, providing the configuration linkage that determines how corporate card transactions are classified and processed during expense report import and Payables invoice creation.

The table resides in the AP schema and is marked VALID in Oracle EBS 12.1.1 and 12.2.2. It is a narrow configuration table with only seven documented columns, typical of setup or control data rather than transactional volume. Its primary key, AP_CARD_PARAMETERS_PK, is a composite of CARD_EXP_TYPE_LOOKUP_CODE and PARAMETER_ID, reinforcing that the row represents a mapping between an expense type and a parameter set rather than an independently identified business entity.

Under the heuristic Data Vault classification mined from the foreign key structure, this object is satellite-leaning. In Data Vault modeling terms, that suggests treating it as descriptive configuration attached to a parent hub keyed on PARAMETER_ID, rather than as a hub or link in its own right.

Key Information Stored

The documented columns group into three functional areas: the mapping business keys, the parent reference, and standard EBS audit columns.

• CARD_EXP_TYPE_LOOKUP_CODE — The card expense type lookup code. This is one half of the composite primary key and one half of the unique index AP_CARD_PARAMETERS_U1, making it a business-key candidate for the mapping.
• PARAMETER_ID — The identifier of the expense report parameter set. This is the second half of the composite primary key and of the unique index, and it is the foreign key column pointing to AP_EXPENSE_REPORT_PARAMS_ALL.
• CREATED_BY — The user who created the mapping row, standard WHO column audit data.
• CREATION_DATE — The date and time the mapping row was created.
• LAST_UPDATED_BY — The user who most recently updated the mapping row.
• LAST_UPDATE_DATE — The date and time of the most recent update.
• LAST_UPDATE_LOGIN — The login session identifier associated with the last update, used for audit and concurrency tracking.

Because the table has no single-column surrogate key, the pair (CARD_EXP_TYPE_LOOKUP_CODE, PARAMETER_ID) serves as both the declared primary key and the unique business-key index AP_CARD_PARAMETERS_U1. No additional descriptive columns are documented beyond the audit set.

Common Use Cases and Queries

Typical uses center on verifying card expense type configuration and reporting which expense type mappings exist for a given parameter set.

• Confirming that a card expense type is mapped for a specific expense report parameter set before importing card transactions.
• Auditing configuration changes across environments by reviewing the WHO audit columns.
• Reporting all card expense type mappings grouped by PARAMETER_ID to understand expense report setup coverage.

A representative query joins the parent parameter table to enrich the mapping rows:

SELECT acp.card_exp_type_lookup_code, acp.parameter_id, p.parameter_name
FROM ap.ap_card_parameters acp, ap.ap_expense_report_params_all p
WHERE acp.parameter_id = p.parameter_id;

For a simple mapping listing, select the two key columns ordered by PARAMETER_ID. To detect duplicates or gaps, aggregate on CARD_EXP_TYPE_LOOKUP_CODE and count distinct PARAMETER_ID values.

Related Objects

The most significant dependency documented is the foreign key relationship to the expense report parameters table.

• AP_EXPENSE_REPORT_PARAMS_ALL — Parent table referenced by AP_CARD_PARAMETERS.PARAMETER_ID. Join on PARAMETER_ID to obtain parameter names and setup details.
• AP_CARD_PARAMETERS_PK — Composite primary key constraint on (CARD_EXP_TYPE_LOOKUP_CODE, PARAMETER_ID).
• AP_CARD_PARAMETERS_U1 — Unique index on the same two columns, the business-key candidate for the mapping.
• FND_LOOKUP_VALUES — Reference source for the CARD_EXP_TYPE_LOOKUP_CODE lookup values used in the mapping.
• AP_CARD_PARAMETERS related expense report and card import interfaces that consume the parameter mapping during Payables processing.

Because the documented relationship data is limited to a single foreign key, additional dependent objects should be confirmed against the specific 12.1.1 or 12.2.2 instance before relying on them for integration design.