Results for “po_reschedule_interface”

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

Overview

PO_RESCHEDULE_INTERFACE is a Purchasing (PO) module interface table in the APPS schema that serves as a staging area for requisition rescheduling data. Its documented description identifies it as the "Requisition reschedule interface table," meaning it holds inbound records that reassign quantities and schedule dates on requisition distribution lines. In Oracle EBS 12.1.1 and 12.2.2, interface tables of this type feed concurrent programs that validate rows, apply business logic, and post changes to base transaction tables. The table resides in the PO schema (owner: PO) and is documented with 19 columns in ETRM 12.2.2.

Based on the mined foreign key structure, PKR (primary key relationship) status: the heuristic Data Vault classification for PO_RESCHEDULE_INTERFACE is standalone. In Data Vault modeling terms, such an object does not function as a true hub, link, or satellite because it carries no independent business key relationships beyond its own surrogate key; it behaves as a transient staging entity. Modelers should treat it as a landing interface rather than a conformed dimensional structure.

Key Information Stored

The table's primary key is PO_RESCHEDULE_INTERFACE_PK, defined on the LINE_ID column. LINE_ID is the surrogate identifier for each interface row, not a business key derived from source documents. Documented business-relevant columns include:

• LINE_ID — surrogate primary key for each interface record.
• QUANTITY — the new or requested reschedule quantity for the requisition line.
• NEED_BY_DATE — the requested new need-by date driving the reschedule.
• ORIG_QUANTITY — the original requisition quantity prior to rescheduling, retained for audit and comparison.
• ORIG_NEED_BY_DATE — the original need-by date before the reschedule request.
• SHIP_METHOD — shipping method associated with the rescheduled delivery.
• ESTIMATED_PICKUP_DATE — expected pickup date relevant to the reschedule timing.
• PROCESS_ID — groups interface rows processed together in a single run.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — standard concurrent program audit columns identifying the submitting request and program.
• AUCTION_HEADER_ID, AUCTION_DISPLAY_NUMBER — sourcing/auction reference fields; AUCTION_HEADER_ID is documented as a foreign key to PON_AUCTION_HEADERS_ALL.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical usage centers on loading reschedule requests from external systems or spreadsheets, validating them, and invoking the requisition reschedule concurrent program. Practitioners query pending rows by PROCESS_ID to confirm batches before processing, and reconcile ORIG_QUANTITY/ORIG_NEED_BY_DATE against QUANTITY/NEED_BY_DATE to verify intent.

• Pending reschedule review: SELECT line_id, quantity, need_by_date, orig_quantity, orig_need_by_date FROM po.po_reschedule_interface WHERE process_id = :p_process_id;
• Change detection: filter rows where QUANTITY differs from ORIG_QUANTITY or NEED_BY_DATE differs from ORIG_NEED_BY_DATE.
• Audit tracing: join REQUEST_ID to FND_CONCURRENT_REQUESTS to identify the submitting program and completion status.
• Auction-linked reschedules: join AUCTION_HEADER_ID to PON_AUCTION_HEADERS_ALL for sourcing context.
• Daily reporting: aggregate records by CREATION_DATE or PROCESS_ID to trend reschedule volume.

Related Objects

The documented foreign key relationship anchors this table to the sourcing schema; other dependencies follow from standard EBS interface processing patterns.

• PON_AUCTION_HEADERS_ALL — referenced via AUCTION_HEADER_ID, linking reschedule rows to auction headers.
• PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL — base requisition tables receiving posted reschedule data.
• PO_REQ_DISTRIBUTIONS_ALL — distribution-level destinations for quantity and date changes.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to trace the submitting concurrent program.
• FND_CONCURRENT_PROGRAMS — joined on PROGRAM_ID and PROGRAM_APPLICATION_ID to identify the processing program.
• PO_RESCHEDULE_INTERFACE_PK — the primary key constraint on LINE_ID enforcing row uniqueness.

Because the object is standalone and interface-oriented, its records are transient by design: rows are consumed and typically purged after the reschedule program completes successfully.