Results for “iby_batch_state”

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

Overview

APPS.IBY_BATCHES_ALL_V is a public Oracle E-Business Suite view owned by the APPS schema, registered under FND Design Data as IBY.IBY_BATCHES_ALL_V with a status of VALID. It is documented in the E-Business Tax and Receivables Management (ETRM) reference metadata for both Oracle EBS 12.1.1 and 12.2.2. The view exposes batch-level information for payment processing in the Oracle Payments (IBY) module, allowing a merchant or business to review details associated with a settlement batch submitted to a back-end payment system.

Because it is a public view, IBY_BATCHES_ALL_V is intended for custom reporting, data extraction, and integration purposes rather than for transactional processing within the standard application forms. Unlike an entity table, it does not support inserts or updates and is not referenced by any other database object, so it acts purely as a reporting and query surface. Its scope is defined to cover all organizations, as indicated by the "_ALL_" naming convention and the presence of ORG_ID in the column list, which supports multi-org reporting requirements.

Underlying Base Objects

According to the documented dependency information, APPS.IBY_BATCHES_ALL_V references four base objects, each exposed as an APPS synonym:

• IBY_BATCHES_ALL — the central batch entity table that holds the primary batch attributes such as merchant batch identifier, status, close date, and totals.
• IBY_BEPINFO — the back-end payment (BEP) configuration table, which supplies the payment system name displayed in the view, such as Cybercash or Verifone.
• IBY_PAYEE — the payee definition table, providing the payee name associated with the batch.
• FND_LOOKUP_VALUES — the standard Oracle Application Object Library lookup view, used to resolve coded values such as batch state or status into their user-facing meanings.

The view therefore represents a join across transactional batch data, payment system configuration, payee master data, and lookup-driven reference values. No other database object depends on IBY_BATCHES_ALL_V, confirming that it is a terminal reporting object within the IBY schema.

Key Columns

The view exposes thirteen columns. The most significant are described below:

• MERCHBATCHID (VARCHAR2, 80) — the merchant batch identifier that uniquely identifies the settlement batch.
• BATCHSTATUS (NUMBER) — the numeric status of the batch, typically resolved through lookup values.
• BATCHSTATE (VARCHAR2, 80) — the textual state of the batch, with documented values including batch-accepted (0), batch-sent (1), batch-queued (2), batch-rejected (3), batch-processed (4, not currently used), batch-error-at-cc (5), batch-not-found (6), and batch-unknown (7).
• PAYEENAME (VARCHAR2, 80) — the name of the payee associated with the batch.
• BATCHCLOSEDATE (DATE) — the date on which the batch was closed.
• BEPNAME (VARCHAR2, 80) — the name of the back-end payment system, such as Cybercash or Verifone.
• VPSBATCHID (VARCHAR2, 80) — the batch identifier assigned by the back-end payment system.
• NUMTRXNS (NUMBER) — the count of transactions contained in the batch.
• BATCHTOTAL (NUMBER) — the total net amount for the batch.
• BATCHSALES (NUMBER) — the total inflow amount for the batch.
• BATCHCREDIT (NUMBER) — the total outflow amount, including return and credit transaction values.
• PAYMENTMETHODNAME (VARCHAR2, 80) — the name of the payment method used.
• ORG_ID (NUMBER, 15) — the organization identifier supporting multi-org security and reporting.

Common Use Cases and Queries

Typical scenarios include reconciling merchant batches against back-end payment system reports, monitoring batch states for failures or rejections, analyzing settlement totals by payment method or payee, and feeding batch data into custom operational dashboards. Because BATCHSTATE literally carries its meaning in text, filtering on it is straightforward for exception reporting.

The recommended query pattern, as documented, is:

SELECT MERCHBATCHID, BATCHSTATUS, PAYEENAME, BATCHCLOSEDATE, BEPNAME, VPSBATCHID, NUMTRXNS, BATCHSTATE, BATCHTOTAL, BATCHSALES, BATCHCREDIT, PAYMENTMETHODNAME, ORG_ID FROM APPS.IBY_BATCHES_ALL_V;

For example, to identify batches that failed at the credit card processor, a report could add the predicate WHERE BATCHSTATE = 'batch-error-at-cc'. To reconcile financial totals, aggregation over BATCHTOTAL, BATCHSALES, and BATCHCREDIT grouped by BEPNAME and PAYMENTMETHODNAME provides a net-versus-inflow-versus-outflow summary. In multi-organization deployments, ORG_ID should be constrained through the standard MO profile to enforce organization-level access.