Search Results cleared_base_amount

Overview

AMS_AP_CHECKS_V is a reporting view in the Oracle E-Business Suite (EBS) Marketing (AMS) module, described in the ETRM metadata as "Payables Checks." The view presents a denormalized, read-oriented projection of payment check data drawn primarily from the Oracle Payables (AP) schema. Its purpose is to expose check-level detail — including payment amounts, currency, exchange information, vendor and bank account attributes, and check lifecycle status — to Marketing applications and to ad hoc reporting or integration consumers that require a consistent, pre-joined representation of disbursement records.

Per the ETRM implementation metadata, AMS_AP_CHECKS_V is not implemented in this database for the documented configuration. This indicates that the object is a seeded or optional view that may not be deployed in every environment; its presence depends on the specific product installation and patch level. When present in EBS 12.1.1 or 12.2.2, it behaves as a standard read-only database view and is not maintained by concurrent programs.

Underlying Base Objects

The documented view text joins three primary AP objects:

• AP_CHECKS (aliased AC) — the central source of check rows, supplying identifiers, dates, amounts, clearing data, payment method and status lookup codes, vendor and site references, address attributes, bank account identifiers, voucher number, and the released, stopped, and void tracking columns.
• AP_BANK_ACCOUNTS (aliased ABA) — supplies bank account name, currency code, and the set of books identifier. Joins on bank account.
• AP_BANK_BRANCHES (aliased ABB) — supplies the bank name.
• AP_LOOKUP_CODES (aliased in the excerpt family as ALC1, ALC2, ALC3) — resolves the displayed meanings for payment type, payment method, and check status lookup codes.
• Additional referenced objects implied by the SELECT list include PO_VENDORS (PV) and PO_VENDOR_SITES (PVS) for vendor name, segment1, 1099 number, and vendor site code, and a global descriptive flexfield conversion type source (GDCT). The ETRM metadata lists no separately documented base tables for this view.

Key Columns

• CHECK_ID, CHECK_NUMBER, CHECK_DATE — primary identification and dating of the check.
• CURRENCY_CODE, AMOUNT, BASE_AMOUNT — transactional and functional currency amounts. The duplicated AC.AMOUNT entry appears in the documented text.
• EXCHANGE_DATE, EXCHANGE_RATE, EXCHANGE_RATE_TYPE, USER_CONVERSION_TYPE — currency conversion detail.
• CLEARED_AMOUNT, CLEARED_BASE_AMOUNT, CLEARED_DATE and the cleared exchange columns — bank reconciliation state.
• RELEASED_DATE, RELEASED_BY — the date a payment was released and the user who released it. This is directly relevant to the search term released_by.
• STOPPED_DATE, STOPPED_BY, VOID_DATE — stop and void lifecycle tracking.
• STATUS_LOOKUP_CODE, PAYMENT_METHOD_LOOKUP_CODE, PAYMENT_TYPE_FLAG — coded status values, with displayed meanings resolved via AP_LOOKUP_CODES.
• VENDOR_ID, VENDOR_NAME, VENDOR_SITE_ID, VENDOR_SITE_CODE — payee identification.
• BANK_ACCOUNT_ID, BANK_NAME, BANK_ACCOUNT_NAME, BANK_ACCOUNT_NUM, BANK_NUM, BANK_ACCOUNT_TYPE — disbursement bank detail.
• ORG_ID, SET_OF_BOOKS_ID — multi-org and ledger context.

Common Use Cases and Queries

Typical consumers filter payments by release, stop, or void status, or report disbursements by vendor, bank account, or ledger. A query targeting the searched attribute might be:

SELECT check_number, check_date, vendor_name, amount, currency_code,
       released_date, released_by, status_lookup_code
  FROM ams_ap_checks_v
 WHERE released_by = :user_name
   AND org_id = :org_id
 ORDER BY released_date DESC;

Other practical patterns include reconciling cleared versus cleared base amounts, auditing who stopped or voided payments, and joining to AMS campaign or activity tables where marketing spend must be tied to actual disbursements. Because the view is documented as not implemented in some environments, availability checks against ALL_VIEWS should precede its use in custom code.