Results for “settlement_doc_id”

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

Overview

OZF_FUNDS_PAID_ALL is a Trade Management (OZF) transaction table that stores the funds paid details within Oracle E-Business Suite. It resides in the OZF schema and is classified as VALID in the ETRM reference for both 12.1.1 and 12.2.2. The table records the disbursement side of the accrual-and-settlement lifecycle in Oracle Trade Management, capturing each instance in which funds are paid out against a claim, claim line, or funds utilization record. It is the transactional counterpart to the accrual and utilization tables that govern trade promotion and customer rebate accounting.

Under the heuristic Data Vault classification mined from its foreign key structure, OZF_FUNDS_PAID_ALL is modeled as a link table. It resolves the many-to-many relationships between claims, claims lines, settlement documents, funds utilization records, and the underlying fund. This classification is a modeling suggestion only; the table is implemented as a standard EBS transactional entity with WHO columns and descriptive attributes.

Key Information Stored

The table contains 39 documented columns. The most significant include:

• PAID_ID — the surrogate primary key, enforced by the unique index OZF_FUNDS_PAID_U1 and constraint FUNDPD_PK. This is the single business-key candidate documented.
• UTILIZATION_ID — foreign key to OZF_FUNDS_UTILIZED_ALL_B, tying the payment to the specific funds utilization line it settles.
• CLAIM_ID and CLAIM_LINE_ID — foreign keys to OZF_CLAIMS_ALL and OZF_CLAIM_LINES_ALL respectively, identifying the claim and claim line being paid.
• SETTLEMENT_DOC_ID — foreign key to OZF_SETTLEMENT_DOCS_ALL, linking the payment to its supporting settlement documentation.
• FUND_ID — the fund against which the payment is applied.
• CURRENCY_CODE, EXCHANGE_RATE_TYPE, EXCHANGE_RATE_DATE, and EXCHANGE_RATE — the currency and conversion context captured at payment time.
• ORG_ID — the operating unit, supporting multi-org security.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, used for data-level access control.
• WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER support auditability and optimistic locking.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE identify the concurrent program that created the record.
• Fifteen ATTRIBUTE columns plus ATTRIBUTE_CATEGORY provide the standard EBS extensibility (DFF) framework.

Common Use Cases and Queries

Typical reporting use cases include reconciliation of payments against claims and utilization records, funds consumption analysis by fund or operating unit, and currency exposure reporting on settled amounts. A representative query joins the claim and utilization parents:

• Payments by claim: SELECT p.paid_id, p.claim_id, p.fund_id, p.currency_code, p.exchange_rate FROM ozf_funds_paid_all p WHERE p.claim_id = :claim_id ORDER BY p.creation_date DESC.
• Reconciliation to utilization: SELECT p.paid_id, p.utilization_id, u.amount FROM ozf_funds_paid_all p, ozf_funds_utilized_all_b u WHERE p.utilization_id = u.utilization_id.
• Settlement document audit: join SETTLEMENT_DOC_ID to OZF_SETTLEMENT_DOCS_ALL to verify each payment is backed by a document.
• Multi-org filtering: apply ORG_ID predicates for operating-unit-level reporting.

Related Objects

• OZF_FUNDS_UTILIZED_ALL_B — joined on UTILIZATION_ID; the parent utilization record that the payment settles.
• OZF_CLAIMS_ALL — joined on CLAIM_ID; provides claim header context.
• OZF_CLAIM_LINES_ALL — joined on CLAIM_LINE_ID; provides claim line detail.
• OZF_SETTLEMENT_DOCS_ALL — joined on SETTLEMENT_DOC_ID; the supporting settlement documentation.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; governs data-level security.

These relationships confirm OZF_FUNDS_PAID_ALL's role as a central link entity within the Trade Management funds settlement model.