Results for “ozf_batches”

16 results




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

Overview

The OZF_BATCHES view is a reporting and integration interface within the Oracle Trade Management (OZF) module, part of the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases. It exposes batch-level records used in trade promotion and accrual processing, such as batch payment requests, deduction batches, and other grouped financial transactions. The view is owned by the APPS schema and holds a VALID status, making it a supported dictionary object for downstream queries, concurrent programs, and interface logic. Its primary design objective is to enforce organizational data security by filtering the underlying data based on the session's operating unit context, which is derived dynamically from the USERENV('CLIENT_INFO') value.

Because the view performs multi-org filtering at runtime, it returns only the batch rows relevant to the currently initialized organization. This behavior makes it well suited for responsibility-scoped reports, where the active organization determines visible data without requiring explicit ORG_ID predicates in application SQL.

Underlying Base Objects

The view is defined over a single base object, the synonym OZF_BATCHES_ALL, which resolves to the underlying OZF batch table. The view text selects an explicit column list from OZF_BATCHES_ALL and applies a WHERE clause that compares the row's ORG_ID to the organization value decoded from the client information string. Rows with a NULL ORG_ID are compared using the fallback token -99, allowing records not tied to a specific operating unit to remain accessible.

The join logic uses the following predicate:

  • NVL(ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTR(USERENV('CLIENT_INFO'),1,1),' ',NULL,SUBSTR(USERENV('CLIENT_INFO'),1,10))), -99)) = NVL(TO_NUMBER(DECODE(SUBSTR(USERENV('CLIENT_INFO'),1,1),' ',NULL,SUBSTR(USERENV('CLIENT_INFO'),1,10))), -99)

This pattern is characteristic of Oracle's Multi-Org architecture in Release 12, where CLIENT_INFO carries the current operating unit identifier established by the Forms session or by FND_GLOBAL initialization.

Key Columns

The view exposes standard WHO audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN), concurrency columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE), and a set of descriptive and financial attributes. Notable columns include:

Common Use Cases and Queries

Typical usage includes reconciling trade management batch payments against GL accruals, auditing currency conversions (where a search for exchange_rate_date applies directly), and driving custom reports scoped to an operating unit.

  • Listing batches with their conversion details:
    SELECT batch_id, batch_name, currency_code,
           exchange_rate_type, exchange_rate_date, exchange_rate,
           batch_amount, acctd_amount
    FROM   apps.ozf_batches
    WHERE  status_code = 'NEW';
  • Reviewing batches created within an operating unit over a period:
    SELECT batch_id, batch_type, batch_amount, creation_date
    FROM   apps.ozf_batches
    WHERE  org_id = :p_org_id
    AND    creation_date BETWEEN :p_from AND :p_to;
  • Auditing rate-date usage for GL tie-out:
    SELECT batch_id, currency_code, exchange_rate_date, exchange_rate
    FROM   apps.ozf_batches
    WHERE  exchange_rate_date IS NOT NULL
    AND    set_of_books_id = :p_sob_id;

Because the view already filters by operating unit, additional ORG_ID predicates are optional but are commonly added for clarity when sessions initialize Multi-Org through concurrent program contexts.