Results for “resale_adjustment_id”

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

Overview

OZF_RESALE_ADJUSTMENTS_ALL is a Trade Management (OZF) transaction table that stores chargeback price adjustment records. In Oracle E-Business Suite 12.1.1 and 12.2.2, the table holds the financial and pricing detail that results when a distributor or reseller submits a chargeback claim against a resale agreement. Each row represents a single adjustment line, capturing the original agreement terms, the corrected or claimed terms, the calculated price, and the amounts claimed, allowed, and accepted through the claim adjudication workflow.

The table belongs to the OZF schema and is documented in ETRM as containing 52 columns. Its primary key is OZF_RESALE_ADJUSTMENTS_ALL_PK, defined on RESALE_ADJUSTMENT_ID, which is also the single unique index (OZF_RESALE_ADJUSTMENTS_U1). A heuristic Data Vault classification mined from the foreign key structure suggests the table functions as a link, since it resolves relationships among resale lines, resale batches, price list lines, and security groups rather than acting as an independent hub or a pure descriptive satellite.

Key Information Stored

The most significant columns fall into several functional groups:

• Identity and concurrency: RESALE_ADJUSTMENT_ID (surrogate primary key), OBJECT_VERSION_NUMBER, and the standard WHO audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY.
• Parent references: RESALE_BATCH_ID and RESALE_LINE_ID, which tie the adjustment to its batch and originating resale line.
• Original agreement context: ORIG_SYSTEM_AGREEMENT_NAME, ORIG_SYSTEM_AGREEMENT_TYPE, ORIG_SYSTEM_AGREEMENT_CURR, ORIG_SYSTEM_AGREEMENT_PRICE, ORIG_SYSTEM_AGREEMENT_QUANTITY, and ORIG_SYSTEM_AGREEMENT_UOM.
• Corrected agreement context: AGREEMENT_ID, AGREEMENT_NAME, AGREEMENT_TYPE, AGREEMENT_PRICE, AGREEMENT_UOM_CODE, CORRECTED_AGREEMENT_ID, and CORRECTED_AGREEMENT_NAME.
• Claim amounts and pricing: CLAIMED_AMOUNT, TOTAL_CLAIMED_AMOUNT, ALLOWED_AMOUNT, TOTAL_ALLOWED_AMOUNT, ACCEPTED_AMOUNT, TOTAL_ACCEPTED_AMOUNT, CALCULATED_PRICE, ACCTD_CALCULATED_PRICE, CALCULATED_AMOUNT, PRICED_QUANTITY, PRICED_UOM_CODE, and PRICED_UNIT_PRICE.
• Status and adjudication: STATUS_CODE, CREDIT_CODE, CREDIT_ADVICE_DATE, LINE_AGREEMENT_FLAG, TOLERANCE_FLAG, LINE_TOLERANCE_AMOUNT, OPERAND, and OPERAND_CALCULATION_CODE.
• Price list and security: LIST_HEADER_ID, LIST_LINE_ID, ORG_ID, and SECURITY_GROUP_ID.

RESALE_ADJUSTMENT_ID is the surrogate key; the ETRM metadata does not document a natural business-key unique index beyond this column, so no alternate business key is asserted.

Common Use Cases and Queries

Typical reporting scenarios include chargeback claim reconciliation, distributor accrual analysis, and dispute tracking. A representative query joining the adjustment to its resale line and batch is:

• SELECT a.RESALE_ADJUSTMENT_ID, a.RESALE_LINE_ID, a.RESALE_BATCH_ID, a.STATUS_CODE, a.CLAIMED_AMOUNT, a.ALLOWED_AMOUNT, a.ACCEPTED_AMOUNT FROM OZF_RESALE_ADJUSTMENTS_ALL a WHERE a.STATUS_CODE = :status;
• Aggregate amounts by agreement: SELECT a.AGREEMENT_ID, SUM(a.CLAIMED_AMOUNT), SUM(a.ALLOWED_AMOUNT) FROM OZF_RESALE_ADJUSTMENTS_ALL a GROUP BY a.AGREEMENT_ID;
• Join to QP_LIST_LINES via LIST_LINE_ID to report the price list detail behind each adjustment.

These patterns support accrual reporting, credit memo generation, and analysis of tolerance exceptions flagged through TOLERANCE_FLAG and LINE_TOLERANCE_AMOUNT.

Related Objects

• OZF_RESALE_LINES_ALL — referenced by RESALE_LINE_ID; the parent resale line for each adjustment.
• OZF_RESALE_BATCHES_ALL — referenced by RESALE_BATCH_ID; the batch that groups resale activity.
• QP_LIST_LINES — referenced by LIST_LINE_ID; the price list line providing pricing context.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID; governs data security filtering.
• OZF_RESALE_ADJUSTMENTS_ALL_PK / U1 — the primary key and unique index enforcement objects on RESALE_ADJUSTMENT_ID.

Together these relationships confirm the table's role as a transactional link within the Trade Management chargeback model.