Search Results card_prog

Overview

APPS.OIE_SRS_CARD_NUMBER_V is a reporting view in Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 that consolidates corporate card, card program, employee, and masked credit-card information into a single, denormalized projection. It is owned by the APPS schema and is primarily associated with the Oracle Internet Expenses (OIE) module, where it supports Self-Service Expenses reporting and integration scenarios that need to resolve a card identifier to its masked number and owning card program. The view joins four base objects — AP_CARDS_ALL, AP_CARD_PROGRAMS_ALL, PER_EMPLOYEES_X, and IBY_CREDITCARD — and returns a distinct set of rows scoped by ORG_ID. Because it exposes the masked card number rather than the full PAN, it is safe for use in reporting layers where sensitive payment instrument data must be restricted, while still enabling the reconciliation of a CARD_ID to a human-readable program name and employee name.

Underlying Base Objects

The view is defined over the following documented base objects:

• AP_CARDS_ALL (SYNONYM) — the master corporate card record, supplying CARD_ID, CARD_PROGRAM_ID, EMPLOYEE_ID, CARD_REFERENCE_ID, and ORG_ID.
• AP_CARD_PROGRAMS_ALL (SYNONYM) — the card program definition, supplying CARD_PROGRAM_NAME.
• PER_EMPLOYEES_X (VIEW) — the HR employee view, supplying FULL_NAME for the cardholder.
• IBY_CREDITCARD (SYNONYM) — the payment instrument table, supplying MASKED_CC_NUMBER via the INSTRID join.
• HR_GENERAL, HR_PERSON_NAME, HR_SECURITY (PACKAGES) — indirectly referenced by the PER_EMPLOYEES_X view, which invokes these HR security and name-resolution packages to enforce row-level access and derive the formatted full name.

The joins are equijoins on CARD_PROGRAM_ID, EMPLOYEE_ID, and INSTRID. Because PER_EMPLOYEES_X is secured through HR_SECURITY, the effective result set of this view is filtered by the querying user's HR security profile, ensuring that cardholder names are only visible where the user is entitled to see them.

Key Columns

• CARD_ID — surrogate identifier of the corporate card record from AP_CARDS_ALL; the primary correlation key for the view.
• MASKED_CC_NUMBER — the masked credit-card number sourced from IBY_CREDITCARD, suitable for display without exposing the full card number.
• FULL_NAME — the cardholder's formatted full name, resolved through PER_EMPLOYEES_X and its HR name/security packages.
• CARD_PROGRAM_NAME — the descriptive name of the card program to which the card belongs, from AP_CARD_PROGRAMS_ALL.
• ORG_ID — the operating unit identifier carried from the card record, enabling multi-org filtering and reporting.

Common Use Cases and Queries

The view is typically used to present cardholder-facing or administrator-facing lists of corporate cards, to reconcile card transactions against the program that issued them, and to support audit or expense-review reports where the masked number is sufficient. Because the definition uses SELECT DISTINCT, callers should expect de-duplication across the joins but should not rely on it to guarantee uniqueness when additional columns are added.

SELECT card_id,
       masked_cc_number,
       full_name,
       card_program_name,
       org_id
  FROM apps.oie_srs_card_number_v
 WHERE org_id = :p_org_id
 ORDER BY full_name;

To locate a specific cardholder by name:

SELECT card_id,
       masked_cc_number,
       card_program_name
  FROM apps.oie_srs_card_number_v
 WHERE full_name LIKE :p_name || '%';

To group cards by program for administrative reporting:

SELECT card_program_name,
       COUNT(DISTINCT card_id) card_count
  FROM apps.oie_srs_card_number_v
 WHERE org_id = :p_org_id
 GROUP BY card_program_name;

Note that the object references resolve to synonyms in the APPS schema; queries should always be issued as APPS.OIE_SRS_CARD_NUMBER_V and are subject to the HR security profile of the executing user.