Results for “card_number”

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

Overview

The OIE_SRS_CARD_NUMBER_V view is a reporting object owned by the APPS schema within the Oracle E-Business Suite Payables (AP) module. Its name reflects its primary function: supplying masked corporate card numbers for use by Oracle iExpenses and the Self-Service/Internet Expenses reporting subsystem (OIE), particularly for the Statement Reconciliation Suite (SRS) and card program identification. In Oracle EBS 12.1.1 and 12.2.2 the view is documented as VALID and is consumed as a read-only data source, typically by concurrent programs, BI Publisher reports, and OAF-based pages that need to display an employee's card details without exposing full credit card data.

The view answers a common functional requirement — how to resolve a corporate card to its assigned employee, its parent card program, and its associated operating unit — while substituting cleartext PAN data with the IBY masked card number. Because the underlying reference is IBY_CREDITCARD.INSTRID, the view is tightly coupled to Oracle Payments (IBY) infrastructure, which centralizes sensitive card data and enforces masking. The user search term card_program_name corresponds directly to the CARD_PROGRAM_NAME column, making this view the canonical source for joining card records to the human-readable program description stored in AP_CARD_PROGRAMS_ALL.

Underlying Base Objects

The view is defined as a DISTINCT join across four physical sources plus supporting date-tracked employee objects. Documented base objects include:

• AP_CARDS_ALL (synonym) — the master corporate card table holding CARD_ID, CARD_PROGRAM_ID, EMPLOYEE_ID, CARD_REFERENCE_ID, and ORG_ID.
• AP_CARD_PROGRAMS_ALL (synonym) — the card program definition table providing CARD_PROGRAM_NAME.
• IBY_CREDITCARD (synonym) — the Payments credit card repository exposing MASKED_CC_NUMBER keyed by INSTRID.
• PER_EMPLOYEES_X (view) — the date-tracked employee view supplying EMPLOYEE_ID and FULL_NAME.
• HR_GENERAL, HR_PERSON_NAME, HR_SECURITY (packages) — invoked at runtime to resolve person names and enforce HR security, ensuring users only see employees within their security profile.

Join predicates link CARD.CARD_PROGRAM_ID = CARD_PROG.CARD_PROGRAM_ID, CARD.EMPLOYEE_ID = EMP.EMPLOYEE_ID, and CARD.CARD_REFERENCE_ID = ICC.INSTRID.

Key Columns

• CARD_ID — Surrogate primary key from AP_CARDS_ALL, used to relate back to the card record.
• CARD_NUMBER — Exposed column label resolving to ICC.MASKED_CC_NUMBER; the masked display value of the corporate card.
• FULL_NAME — Employee name resolved via PER_EMPLOYEES_X and HR name/security packages.
• CARD_PROGRAM_NAME — Description of the card program from AP_CARD_PROGRAMS_ALL; the target of the card_program_name search.
• ORG_ID — Operating unit identifier supporting Multi-Org access control and security filtering.

Common Use Cases and Queries

Typical scenarios include statement reconciliation displays, expense entry validation, and card administration reporting. A representative query follows:

• List cards by program: SELECT card_id, card_number, full_name, card_program_name, org_id FROM apps.oie_srs_card_number_v WHERE card_program_name = :program_name ORDER BY full_name;
• Employee card lookup: SELECT card_number, card_program_name FROM apps.oie_srs_card_number_v WHERE full_name LIKE :name;
• Multi-Org filtered extract: SELECT * FROM apps.oie_srs_card_number_v WHERE org_id = :org_id;

Because the view applies DISTINCT and HR security, it is safe for user-facing reports; however, the absence of an unmasked number makes it unsuitable for card issuance or token provisioning processes, which read directly from IBY_CREDITCARD.