Search Results payment_server_error_msg

Overview

The view IGS_FI_INV_INT belongs to the Oracle E-Business Suite product family IGS – Student System, a module classified as obsolete in Release 12.1.1 and 12.2.2. The object functions as an integration interface over student financial invoice data, consolidating billing, fee, and payment-processing attributes into a single denormalized projection. Its role is to expose invoice records to downstream consumers such as payment servers, receipt-processing routines, and external banking or credit-card gateways.

The view is defined with an organization-level security predicate that filters rows against the value stored in the USERENV('CLIENT_INFO') session context, restricting visibility to the currently selected operating unit. This is consistent with the multi-org architecture used throughout the Student System schema.

Where the user searches for customer_bank_account_id, the column is exposed directly by the view text and is relevant to direct-debit and ACH-style payment flows.

Underlying Base Objects

The documented view text selects exclusively from IGS_FI_INV_INT_ALL, the multi-organization base table that stores invoice-interface rows. No other base tables, synonyms, or joins are documented in the ETRM metadata; the ETRM record lists no referenced base objects, and the view is annotated as not implemented in this database.

• IGS_FI_INV_INT_ALL — the sole documented source, carrying all invoice, fee, payment, and audit attributes.
• Organization security — applied through the ORG_ID column and USERENV('CLIENT_INFO'), matching the standard multi-org view pattern.
• Columns — the view projects approximately ninety columns, including the complete set of ATTRIBUTE1–ATTRIBUTE10 descriptive flexfield segments and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN).
• Concurrent request context — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE link rows to the batch process that produced them.

Key Columns

• INVOICE_ID / INVOICE_NUMBER — primary identifier and human-readable invoice reference.
• PERSON_ID — the student or sponsor party associated with the invoice.
• SPONSOR_CD, FEE_TYPE, FEE_CAT, FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER — describe the fee and calendar context of the charge.
• COURSE_CD, ATTENDANCE_MODE, ATTENDANCE_TYPE, TERM_ID — academic delivery context.
• INVOICE_AMOUNT, INVOICE_AMOUNT_DUE, AUTHORIZED_AMOUNT, CURRENCY_CD, EXCHANGE_RATE — monetary and currency detail.
• CUSTOMER_BANK_ACCOUNT_ID / CUSTOMER_BANK_ACCOUNT_NAME — the bank account used for direct-debit settlement; central to the user's search.
• RECEIPT_METHOD_ID / RECEIPT_METHOD_NAME / PAYMENT_METHOD / PAYMENT_STATUS — payment routing and state.
• CREDIT_CARD_CODE, CREDIT_CARD_HOLDER_NAME, CREDIT_CARD_EXPIRATION_DATE, CREDIT_CARD_APPROVAL_CODE, CREDIT_CARD_APPROVAL_DATE — card capture and authorization.
• PAYMENT_SERVER_ORDER_NUMBER, PAYMENT_SERVER_TXN_DATE, PAYMENT_SERVER_TXN_STATUS, PAYMENT_SERVER_ERROR_CODE, PAYMENT_SERVER_ERROR_MSG, BEP_ERROR_CODE, BEP_ERROR_MSG, ERROR_LOCATION — gateway and bank-error tracing.
• STATUS, PAYMENT_STATUS, PROCESSED_IN_SSA — processing state indicators.
• ORG_ID — operating unit discriminator enforcing security.

Common Use Cases and Queries

Typical usage includes reviewing invoices routed through bank-account payment methods, reconciling payment-server responses, and auditing fee waiver processing.

• Locate invoices settled against a specific customer bank account:

SELECT invoice_id, invoice_number, person_id,
       customer_bank_account_id, customer_bank_account_name,
       invoice_amount_due, payment_status
  FROM igs_fi_inv_int
 WHERE customer_bank_account_id = :p_bank_account_id
   AND org_id = :p_org_id;

• Report payment-server errors for a processing run:

SELECT invoice_id, payment_server_order_number,
       payment_server_error_code, payment_server_error_msg
  FROM igs_fi_inv_int
 WHERE request_id = :p_request_id
   AND payment_server_error_code IS NOT NULL;

• Reconcile direct-debit receipts against receipt methods by term and fee category.

Because the view is organization-secured, consumers must initialize CLIENT_INFO to the target operating unit; otherwise the predicate resolves to a default that may suppress rows. In Release 12.2.2 the object remains obsolete, and no base objects are documented in ETRM, so verification against the live data dictionary is advisable before relying on the view for new integrations.