Results for “from_type_lookup_code”

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

Overview

JAI_PO_COPYDOC_T is a transient staging table owned by the JA schema and delivered as part of the Oracle E-Business Suite Asia/Pacific Localizations (JA) product family. Its documented purpose is to hold Purchase Order data temporarily while the Purchase Order Copy functionality executes. When a user invokes a copy action against a source purchase order, the localization logic assembles the header, line, and shipment rows required for the target document into this table before committing them to the core purchasing tables. Because the object serves purely as an intermediate buffer, its contents are meaningful only for the duration of the copy operation and are expected to be transient.

From a dimensional modeling perspective, the metadata's FK structure suggests classifying JAI_PO_COPYDOC_T as a link table. It carries foreign keys pointing to three separate purchasing entities — PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL — plus a second reference to PO_HEADERS_ALL for the source document. This pattern of multiple entity references joined by a shared context (the copy run) is characteristic of a link construct rather than a hub or satellite.

Key Information Stored

The table exposes fifteen documented columns. The most significant grouping is the set of foreign-key identifiers that tie each staged row back to the purchasing schema. PO_HEADER_ID references PO_HEADERS_ALL and identifies the target header context; PO_LINE_ID references PO_LINES_ALL; and LINE_LOCATION_ID references PO_LINE_LOCATIONS_ALL, anchoring the shipment-level detail.

The source document is captured separately through FROM_HEADER_ID, which also references PO_HEADERS_ALL, and FROM_TYPE_LOOKUP_CODE, which records the origin document type being copied. Together these allow the copy logic to distinguish what was read from what is being written.

Business-key attributes carried on the staged rows include LINE_NUM, SHIPMENT_NUM, ITEM_ID, and TYPE. These mirror the human-readable identifiers of the purchase order line and shipment being reproduced. No unique index is documented in the supplied metadata, and the column list contains no dedicated single-column surrogate key; the identity of a staged row is therefore best treated as the combination of PO_HEADER_ID, PO_LINE_ID, and LINE_LOCATION_ID within the scope of an active copy operation.

Standard EBS audit columns are present: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER. The OBJECT_VERSION_NUMBER column supports optimistic locking on any programmatic update path.

Common Use Cases and Queries

The primary use case is diagnostic: confirming that a copy operation populated the staging table correctly. A typical query joins the staged shipment rows to the source header to verify the mapping between origin and target.

• SELECT t.po_header_id, t.from_header_id, t.line_num, t.shipment_num, t.item_id FROM jai_po_copydoc_t t WHERE t.from_header_id = :p_source_header_id;
• Detecting orphaned staging rows, in which a staged line references a PO_HEADER_ID that never materialized in PO_HEADERS_ALL: SELECT t.* FROM jai_po_copydoc_t t WHERE NOT EXISTS (SELECT 1 FROM po_headers_all h WHERE h.po_header_id = t.po_header_id);
• Auditing which source documents have been copied, by aggregating FROM_HEADER_ID and FROM_TYPE_LOOKUP_CODE.
• Reconciling line counts between the source and the target documents during functional testing of the localization.

Because the table is temporary by design, persistent reporting against it is not recommended. Any query should be issued while a copy run is in progress or immediately afterward, before the process clears its rows.

Related Objects

The documented foreign keys define the core relationship set. The following objects are the most significant dependencies:

• PO_HEADERS_ALL — referenced twice, via JAI_PO_COPYDOC_T.PO_HEADER_ID (target header) and JAI_PO_COPYDOC_T.FROM_HEADER_ID (source header).
• PO_LINES_ALL — referenced via JAI_PO_COPYDOC_T.PO_LINE_ID, supplying the line-level target context.
• PO_LINE_LOCATIONS_ALL — referenced via JAI_PO_COPYDOC_T.LINE_LOCATION_ID, supplying the shipment-level target context.
• PO_DISTRIBUTIONS_ALL — the natural downstream recipient of distribution data generated from copied lines and shipments, joined on LINE_LOCATION_ID.
• PO_ACTION_HISTORY — records the copy action against the resulting purchase order for audit purposes.
• FND_LOOKUP_VALUES — resolves FROM_TYPE_LOOKUP_CODE into its descriptive document-type meaning.

Direct runtime readers and writers of this table are the JA localization copy programs rather than public APIs; the Purchasing open interface and the standard PO Copy concurrent program do not depend on it. Consequently, integration effort should target PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL, treating JAI_PO_COPYDOC_T strictly as an internal staging artifact.