Results for “ap_card_requests_all”

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

Overview

AP_CARD_REQUESTS_ALL is a Payables (AP) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 schemas. The AP schema owns the object, and ETRM classifies it as VALID. The documented product description states simply that the table is "Reserved for a future feature." This is an important framing point: the table exists structurally and carries full key, index, and foreign-key definitions, but Oracle does not expose it as an active functional component in the documented release. It therefore behaves as a dormant, provisioned container rather than a populated transactional table in standard environments.

Functionally, the table is positioned to hold corporate card issuance and maintenance requests submitted by employees. Its foreign keys point to card, card program, and card profile master data, and it references an employee. In Data Vault terms, the heuristic classification mined from the FK structure is a link. That is a modeling suggestion: the table's identity is largely defined by the relationships it records between an employee, a card, a program, and a profile, rather than by a single immutable business entity. Analysts should treat this suggestion as directional, not authoritative, and validate it against actual data before building downstream models.

Key Information Stored

The documented physical schema comprises 54 columns. The most significant are summarized below.

• CARD_REQUEST_ID — Surrogate primary key, enforced by AP_CARD_REQUESTS_PK and mirrored by the unique index AP_CARD_REQUESTS_U1. This is the only documented unique business-key candidate.
• EMPLOYEE_ID — Foreign key to PSB_EMPLOYEES, identifying the requester.
• CARD_ID — Foreign key to AP_CARDS_ALL, linking the request to an issued card.
• CARD_PROGRAM_ID — Foreign key to AP_CARD_PROGRAMS_ALL, identifying the card program under which the request is made.
• PROFILE_ID — Foreign key to AP_CARD_PROFILES_ALL, identifying the card profile or limit configuration.
• CARD_NUMBER — The requested or assigned card number.
• CARDMEMBER_NAME — Name of the cardmember associated with the request.
• REQUEST_TYPE_LOOKUP_CODE and REQUEST_STATUS_LOOKUP_CODE — Lookup-backed codes describing the nature and current status of the request.
• REQUEST_DATE and REQUEST_TEXT — Date of submission and free-form request narrative.
• LIMIT_OVERRIDE_AMOUNT and TRX_LIMIT_OVERRIDE_AMOUNT — Requested overrides to card and transaction limits.
• DEPARTMENT_NAME, LOCATION_ID, PHYSICAL_CARD_FLAG, and MOTHERS_MAIDEN_NAME — Request context and identity-verification attributes.
• ORG_ID — Multi-org operating unit discriminator.
• ATTRIBUTE1 through ATTRIBUTE30 — The standard EBS flexfield descriptor block, plus the WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

Because the table is reserved for a future feature, standard reporting use cases center on existence checks and completeness audits rather than operational reporting. A typical first query establishes whether any rows have been written in a given instance:

• SELECT COUNT(*) FROM ap.ap_card_requests_all;
• SELECT card_request_id, employee_id, card_id, request_status_lookup_code FROM ap.ap_card_requests_all WHERE org_id = :org_id;
• SELECT r.card_request_id, c.card_number, p.card_program_name FROM ap.ap_card_requests_all r JOIN ap.ap_cards_all c ON c.card_id = r.card_id JOIN ap.ap_card_programs_all p ON p.card_program_id = r.card_program_id;
• Data-lineage and ETRM impact analysis: enumerate the FK dependencies to assess the blast radius of any schema change.
• Custom extension development: if an implementation activates card request tracking, the table's existing columns and lookups provide the starting structure.

Related Objects

• AP_CARDS_ALL — joined on AP_CARD_REQUESTS_ALL.CARD_ID = AP_CARDS_ALL.CARD_ID.
• AP_CARD_PROGRAMS_ALL — joined on AP_CARD_REQUESTS_ALL.CARD_PROGRAM_ID = AP_CARD_PROGRAMS_ALL.CARD_PROGRAM_ID.
• AP_CARD_PROFILES_ALL — joined on AP_CARD_REQUESTS_ALL.PROFILE_ID = AP_CARD_PROFILES_ALL.PROFILE_ID.
• PSB_EMPLOYEES — joined on AP_CARD_REQUESTS_ALL.EMPLOYEE_ID = PSB_EMPLOYEES.EMPLOYEE_ID.
• AP_CARD_REQUESTS_PK / AP_CARD_REQUESTS_U1 — primary key constraint and unique index on CARD_REQUEST_ID.