Search Results ozf_xref_map

Overview

OZF_XREF_MAP is a Trade Management (OZF) schema table in Oracle E-Business Suite Release 12.1.1 and 12.2.2, created specifically to support integration with Siebel Trade Promotion Management (TPM). The table stores cross-reference mapping information that links Oracle EBS promotion and list-line identifiers to their corresponding external identifiers maintained in the Siebel TPM system, allowing the two applications to reconcile promotional deal structures across disparate naming conventions.

The documented physical schema reflects five columns owned by OZF, with a foreign key relationship to QP_LIST_LINES. In EBS terms the object functions as a cross-reference bridge rather than a transactional or master-data entity: it does not hold pricing, quantity, or accounting facts of its own. From a dimensional or Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is standalone. Practically, this suggests the table is best modeled as an independent mapping or reference object — it carries its own surrogate key (MAP_ATTR_ID) and a single outbound reference to a parent list line, but no downward dependents were documented, so it neither behaves as a conventional hub with satellites nor as a link joining two business hubs.

Key Information Stored

The five documented columns carry the mapping payload and its associations. The most important are:

• MAP_ATTR_ID — the surrogate primary key for the mapping row, uniquely identifying each cross-reference record.
• LIST_LINE_ID — the foreign key to QP_LIST_LINES, anchoring the mapping to a specific Oracle EBS list line (a promotion or modifier line within a price list or promotion list).
• LIST_LINE_NUMBER — the business-facing number of the Oracle list line, used as a human-readable business key candidate alongside the surrogate LIST_LINE_ID.
• XREF_LINE_ID_VALUE — the external (Siebel TPM) identifier value for the corresponding line, populated during integration.
• XREF_LINE_NUMBER_VALUE — the external line number value from Siebel TPM, providing the second half of the cross-reference pair.

No unique indexes were documented in the ETRM metadata beyond the primary key; consequently, LIST_LINE_ID combined with the XREF_* value columns are the natural business-key candidates for de-duplication and reconciliation logic. Together, the LIST_LINE_ID/LIST_LINE_NUMBER pair represents the EBS side and the XREF_* columns represent the Siebel side of each mapping.

Common Use Cases and Queries

Typical usage centers on integration reconciliation and troubleshooting rather than transactional reporting. Common scenarios include verifying that every promoted list line was propagated to Siebel TPM, identifying orphaned or unmapped lines, and resolving discrepancies between EBS and Siebel line numbering during a migration or integration cycle.

A representative query joining the mapping to its parent list line:

• SELECT m.MAP_ATTR_ID, m.LIST_LINE_ID, m.LIST_LINE_NUMBER, q.NAME, m.XREF_LINE_ID_VALUE, m.XREF_LINE_NUMBER_VALUE FROM OZF.OZF_XREF_MAP m, QP.QP_LIST_LINES q WHERE m.LIST_LINE_ID = q.LIST_LINE_ID;
• Unmapped-line detection: compare count of QP_LIST_LINES against OZF_XREF_MAP grouped by LIST_LINE_ID.
• Reverse lookup from a Siebel value: query by XREF_LINE_ID_VALUE or XREF_LINE_NUMBER_VALUE to return the Oracle LIST_LINE_ID.
• Duplicate-detection reporting across LIST_LINE_ID and the XREF columns.

Related Objects

The dominant documented relationship is the foreign key from OZF_XREF_MAP.LIST_LINE_ID to QP_LIST_LINES.LIST_LINE_ID, which makes QP_LIST_LINES the primary parent and the principal join partner for all queries. Adjacent objects commonly consulted in the same Trade Management and Advanced Pricing context include QP_LIST_HEADERS, which heads the list to which each line belongs, and QP_PRICING_ATTRIBUTES, used to enrich list-line detail. Integration and concurrency programs that read or write the mapping — such as Trade Management integration concurrent requests and the OZF promotion APIs — depend on this table to persist external identifiers. Siebel TPM cross-reference staging and interface tables are the functional counterpart on the external side. Master-data views over QP list structures may also be joined when reporting promotion line attributes alongside their mapped Siebel identifiers.