Search Results msc_tp_id_lid_n1

Overview

MSC.MSC_TP_ID_LID is a table in the MSC (Advanced Supply Chain Planning) schema of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. Its documented purpose is to support the collections program by maintaining the correspondence between trading partner identifiers in the source application instance and the planning identifiers generated on the planning server. In practical terms, it functions as a cross-reference between external, source-facing partner keys and the internally generated TP_ID used within planning engines such as Collaborative Planning and Advanced Supply Chain Planning.

The table is physically stored in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, and its indexes reside in APPS_TS_TX_IDX. ETRM documents the primary key MSC_TP_ID_LID_PK over (SR_TP_ID, PARTNER_TYPE, SR_INSTANCE_ID), with a business-key candidate provided by the unique index MSC_TP_ID_LID_U1 over (SR_INSTANCE_ID, SR_TP_ID, PARTNER_TYPE, SR_COMPANY_ID). ETRM's relationship mining reports MSC.MSC_TP_ID_LID as standalone, which is a heuristic Data Vault modeling suggestion that it be treated as its own hub rather than as a dependent satellite joined through foreign keys to another parent table.

Key Information Stored

The columns documented for this table capture both source-side and planning-side identity information:

• SR_INSTANCE_ID — Identifier of the source application instance from which the trading partner record originated. Central to every correspondence and part of both the primary key and the unique index.
• SR_TP_ID — The trading partner identifier as defined in the source application instance. The principal source-side business key.
• PARTNER_TYPE — Numeric indicator of the partner category, distinguishing supplier from customer. Part of the composite primary key.
• TP_ID — The trading partner identifier generated on the planning server. This is the value consumed by planning logic and is indexed non-uniquely via MSC_TP_ID_LID_N1 for fast lookup by planning key.
• SR_COMPANY_ID — Represents the source company identifier tied to a company name in MSC_COMPANIES; documented as being used in Collaborative Planning.
• AGGREGATE_DEMAND_FLAG — Flag indicating whether demand for the partner is aggregated, relevant to planning calculations.
• SR_CUST_ACCOUNT_NUMBER — VARCHAR2(240) holding the customer account number from the source.
• RESOURCE_TYPE — Numeric classification of the resource type associated with the partner record.

The surrogate key is the composite (SR_TP_ID, PARTNER_TYPE, SR_INSTANCE_ID). The unique index MSC_TP_ID_LID_U1 — the object referenced by the user's search — extends uniqueness to include SR_COMPANY_ID, making the four-column combination the documented business-key candidate.

Common Use Cases and Queries

Typical usage centers on resolving a source partner identifier to its planning counterpart, or auditing the completeness of the collection process. A common pattern is to join on the planning key:

• Lookup of a planning server identifier: SELECT TP_ID FROM MSC.MSC_TP_ID_LID WHERE SR_INSTANCE_ID = :inst AND SR_TP_ID = :src AND PARTNER_TYPE = :type;
• Reverse resolution from planning to source: use index MSC_TP_ID_LID_N1 via WHERE TP_ID = :tp_id;
• Segregating suppliers from customers: filter on PARTNER_TYPE.
• Corporate reconciliation for Collaborative Planning: join to MSC_COMPANIES on SR_COMPANY_ID.
• Aggregate-demand reporting: filter on AGGREGATE_DEMAND_FLAG.

The documented query text selects all eight columns from the table, which is suitable as a baseline extraction for validation reports verifying that every source trading partner in a collection run received a planning identifier.

Related Objects

ETRM states that MSC.MSC_TP_ID_LID references no database objects and is referenced by the APPS.MSC_TP_ID_LID synonym. Beyond that, the table's semantics imply functional alignment with the following MSC objects:

• APPS.MSC_TP_ID_LID — The dependent synonym through which application code accesses the underlying table.
• MSC.MSC_COMPANIES — Joined via SR_COMPANY_ID to resolve company names in Collaborative Planning scenarios.
• MSC.MSC_SYSTEM_ITEMS and other collection output tables — Share source-instance and planning-key mapping patterns generated by the same collection program.
• MSC.MSC_ST_TP — Supplier and customer staging information collected from the source instance, matching on SR_INSTANCE_ID.
• MSC.MSC_TP_LOCATIONS — Partner address and location data, resolved through TP_ID.
• Collection programs and concurrent requests in the MSC module that populate this table during the loading cycle.

The object is classified as valid in ETRM and remains proprietary and confidential Oracle information.