Results for “pn_payment_items_efc_n2”

12 results




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

Overview

PN.PN_PAYMENT_ITEMS_EFC is a shadow table owned by the PN (Property Manager) schema in Oracle E-Business Suite. It mirrors the structure and content of PN_PAYMENT_ITEMS_ALL for the specific purpose of supporting Euro functional currency reporting. When a set of books is defined with a Euro functional currency, corresponding EFC tables are used to store converted amounts so that reporting can be performed without repeatedly joining conversion logic to the transactional base table. The table resides in the APPS_TS_TX_DATA tablespace with PCT Free of 10 and is documented as VALID.

The 26 documented columns describe payment and billing items related to property management schedules, vendor obligations, and customer receivables. Because the table is a shadow for a transactional parent, its rows are keyed one-to-one to the parent through PAYMENT_ITEM_ID, which is enforced by the unique index PN_PAYMENT_ITEMS_EFC_U1. In Data Vault modeling terms, the heuristic classification mined from the foreign key structure is link: the table primarily records associations among a payment item, a payment schedule, a payment term, a vendor or vendor site, and a customer or customer site use. This is a modeling suggestion rather than a statement of EBS internal design.

Key Information Stored

The surrogate primary key of this table is PAYMENT_ITEM_ID, populated from the sequence PN_PAYMENT_ITEMS_EFC_S. It uniquely identifies a payment or billing item row and is also the sole business-key candidate through the unique index PN_PAYMENT_ITEMS_EFC_U1. The most significant columns include:

Common Use Cases and Queries

Typical reporting scenarios include Euro functional currency reconciliation, payment schedule analysis, and tracking of export actions to AP and AR. Because indexes exist on DUE_DATE, PAYMENT_SCHEDULE_ID, PAYMENT_TERM_ID, and the vendor pair, queries should filter on those columns where possible.

  • Reconciling EFC amounts against the base table: SELECT a.payment_item_id, a.actual_amount base_amt, e.actual_amount efc_amt FROM pn_payment_items_all a, pn_payment_items_efc e WHERE a.payment_item_id = e.payment_item_id;
  • Listing items pending export to Payables: SELECT payment_item_id, vendor_id, vendor_site_id, actual_amount FROM pn_payment_items_efc WHERE export_to_ap_flag = 'Y' AND transferred_to_ap_flag = 'N';
  • Filtering by due date range for period reporting, using PN_PAYMENT_ITEMS_EFC_N1.
  • Aggregating export currency amounts by PAYMENT_TERM_ID or VENDOR_ID for supplier exposure reporting.

Related Objects

The table participates in the following documented foreign key relationships and joins:

  • PN.PN_PAYMENT_ITEMS_ALL — the transactional base table; joined on PAYMENT_ITEM_ID.
  • PN.PN_PAYMENT_SCHEDULES_ALL — joined on PAYMENT_SCHEDULE_ID.
  • PN.PN_PAYMENT_TERMS_ALL — joined on PAYMENT_TERM_ID.
  • PO.PO_VENDORS — joined on VENDOR_ID.
  • PO.PO_VENDOR_SITES — joined on VENDOR_SITE_ID.
  • HZ_CUST_ACCOUNTS — joined on CUSTOMER_ID.
  • HZ_CUST_SITE_USES_ALL — joined on CUSTOMER_SITE_USE_ID.
  • GL.GL_SETS_OF_BOOKS — associated through SET_OF_BOOKS_ID for functional currency context.

These relationships confirm the table's role as a Euro functional currency shadow that preserves the same referential links as the base payment items table while adding converted amount storage.