Results for “pn_adjustment_summaries”

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

Overview

PN_ADJUSTMENT_SUMMARIES is a table in the PN (Property Manager) schema of Oracle E-Business Suite, documented as valid in release 12.1.1 and 12.2.2. Its documented description is "Summary of Adjustement." It holds one row per adjustment event applied against one or more payment terms, with the header-level schedule date and adjusted amount. The table therefore functions as the summarization or header layer of the adjustment model, with its transactional lines held in PN_ADJUSTMENT_DETAILS.

From a Data Vault modeling perspective, the FK structure is best described as satellite-leaning. The table is not a pure hub, since it carries a descriptive foreign key (PAYMENT_TERM_ID) and measurable attributes (ADJ_SCHEDULE_DATE, SUM_ADJ_AMOUNT). It sits above the detail table, which references it via ADJUSTMENT_SUMMARY_ID, making it a parent in a classic header-detail relationship.

Key Information Stored

The nine documented columns fall into three groups: the surrogate primary key, the standard EBS audit columns, and the adjustment business attributes.

• ADJUSTMENT_SUMMARY_ID — the surrogate primary key, enforced by PN_ADJUSTMENT_SUMMARIES_PK and also unique in PN_ADJUSTMENT_SUMMARIES_U1. Every detail row in PN_ADJUSTMENT_DETAILS stores this value.
• PAYMENT_TERM_ID — the foreign key to PN_PAYMENT_TERMS_ALL, identifying the payment term against which the adjustment is raised.
• ADJ_SCHEDULE_DATE — the schedule date of the adjustment, and the second column of the unique index PN_ADJUSTMENT_SUMMARIES_U2 (PAYMENT_TERM_ID, ADJ_SCHEDULE_DATE). This composite key is the business-key candidate: it means a payment term may have at most one adjustment summary per schedule date.
• SUM_ADJ_AMOUNT — the summarized adjustment amount for the payment term and schedule date.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS audit and concurrent-manager context columns, used for row-level whom/when tracking and for identifying the login responsibility under which the row was created or changed.

Common Use Cases and Queries

The table is principally used to report and reconcile adjustment activity by payment term and schedule date, and to drive drill-down into the detail lines.

Retrieving all summaries for a given payment term, ordered chronologically, is the most common access pattern and exploits PN_ADJUSTMENT_SUMMARIES_U2:

• SELECT adjustment_summary_id, payment_term_id, adj_schedule_date, sum_adj_amount FROM pn_adjustment_summaries WHERE payment_term_id = :payment_term_id ORDER BY adj_schedule_date;

Joining to the detail table produces the adjustment audit trail for a period:

• SELECT s.adjustment_summary_id, s.payment_term_id, s.adj_schedule_date, s.sum_adj_amount, d.* FROM pn_adjustment_summaries s, pn_adjustment_details d WHERE s.adjustment_summary_id = d.adjustment_summary_id AND s.adj_schedule_date BETWEEN :from_date AND :to_date;

Aggregate reporting can verify that the stored SUM_ADJ_AMOUNT agrees with the sum of the corresponding detail amounts, and joining to PN_PAYMENT_TERMS_ALL provides the payment term name for user-facing reports. Because the table is satellite-leaning, reports should preserve the composite business key (PAYMENT_TERM_ID, ADJ_SCHEDULE_DATE) alongside the surrogate ID to maintain traceability across loads.

Related Objects

• PN_ADJUSTMENT_DETAILS — the child table; joined on PN_ADJUSTMENT_DETAILS.ADJUSTMENT_SUMMARY_ID = PN_ADJUSTMENT_SUMMARIES.ADJUSTMENT_SUMMARY_ID. This is the primary dependent object.
• PN_PAYMENT_TERMS_ALL — the parent of the payment-term FK; joined on PN_ADJUSTMENT_SUMMARIES.PAYMENT_TERM_ID = PN_PAYMENT_TERMS_ALL.PAYMENT_TERM_ID.
• PN_ADJUSTMENT_SUMMARIES_PK — the primary key constraint/index on ADJUSTMENT_SUMMARY_ID.
• PN_ADJUSTMENT_SUMMARIES_U1 — unique index on ADJUSTMENT_SUMMARY_ID.
• PN_ADJUSTMENT_SUMMARIES_U2 — unique index on (PAYMENT_TERM_ID, ADJ_SCHEDULE_DATE), representing the business-key candidate.

Writers to this table should also account for the standard audit columns, which are populated by the EBS runtime and are relied upon by concurrent processing and diagnostics.