Search Results ego_func_params_map_interface

Overview

EGO_FUNC_PARAMS_MAP_INTERFACE is an interface (staging) table in the EGO schema, belonging to the Advanced Product Catalog module of Oracle E-Business Suite. It functions as an integration and batch-processing surface through which external sources or concurrent programs supply parameter-mapping definitions for catalog functions. The table captures how function parameters are mapped to item catalog attributes, attribute groups, and units of measure, together with the orchestration columns (process identifiers, transaction identifiers, status codes, and request metadata) that drive the mapping process and record its outcome.

In practice, rows are loaded into the interface table, processed by catalog mapping logic, and then reconciled to permanent structures. Because it is an interface object, most of its content is transient, though the diagnostic columns persist for troubleshooting failed or partially processed loads.

Under the heuristic Data Vault classification mined from the foreign-key structure, this object is assessed as standalone. From a dimensional-modeling perspective, no parent hub relationships were detected; the single documented foreign key to MTL_ITEM_CATALOG_GROUPS_B suggests a lightweight reference link rather than participation in a governed hub-and-satellite pattern. This classification is a modeling suggestion only and should be validated against functional requirements.

Key Information Stored

The table is documented with 27 columns in ETRM 12.2.2. The most significant are:

• FUNCTION_ID / FUNCTION_NAME — identifies the catalog function whose parameters are being mapped; the ID provides the stable key while the name offers the human-readable label.
• ITEM_CATALOG_GROUP_ID / ITEM_CATALOG_NAME — the catalog group context. ITEM_CATALOG_GROUP_ID is the documented foreign key referencing MTL_ITEM_CATALOG_GROUPS_B.
• ATTR_GROUP_ID / ATTR_GROUP_NAME / ATTR_ID / ATTR_NAME — the attribute group and attribute being mapped, in both surrogate and descriptive form.
• PARAMETER_ID / PARAMETER_NAME — the function parameter that receives the mapped value.
• UOM_PARAMETER / MAPPED_UOM_PARAMETER / UOM_PARAM_VALUE_TYPE / FIXED_UOM_VALUE — the unit-of-measure mapping configuration, including the value type and any constant UOM value to be applied.
• PROCESS_STATUS — the processing state of the interface row, the primary filter for error handling.
• SET_PROCESS_ID / TRANSACTION_ID / TRANSACTION_TYPE — grouping and provenance identifiers linking rows to a logical load or business transaction.
• REQUEST_ID / PROGRAM_APPLICATION_ID / PROGRAM_ID / PROGRAM_UPDATE_DATE — concurrent program and request diagnostics for the run that inserted or updated the row.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — the standard EBS WHO audit columns.

No unique index or business-key constraint is documented in the supplied metadata. Absent that, combinations such as FUNCTION_ID plus ITEM_CATALOG_GROUP_ID plus ATTR_ID plus PARAMETER_ID plus SET_PROCESS_ID serve as practical business-key candidates for de-duplication, while the WHO columns provide audit traceability.

Common Use Cases and Queries

Typical scenarios include pre-load validation of mapping interfaces, monitoring of concurrent-program outcomes, and reconciliation of failed rows. A representative status query:

• SELECT SET_PROCESS_ID, FUNCTION_NAME, ITEM_CATALOG_NAME, ATTR_NAME, PARAMETER_NAME, PROCESS_STATUS, REQUEST_ID FROM EGO_FUNC_PARAMS_MAP_INTERFACE WHERE PROCESS_STATUS = 'ERROR';
• Error triage by program run: filter on PROGRAM_ID, PROGRAM_UPDATE_DATE, or REQUEST_ID to isolate rows created by a specific concurrent request.
• Dependency validation: join to MTL_ITEM_CATALOG_GROUPS_B on ITEM_CATALOG_GROUP_ID to confirm that mapped catalog groups exist before promotion to the permanent mapping tables.
• UOM audit reporting: select the UOM_PARAMETER, MAPPED_UOM_PARAMETER, and FIXED_UOM_VALUE columns to verify that conversion and fixed-value rules are applied consistently across functions.
• Volume and throughput reporting: aggregate by TRANSACTION_TYPE and SET_PROCESS_ID to measure batch sizes and processing cadence.

Because the table is an interface, queries should generally be scoped by process or request identifiers to avoid scanning residue from prior runs.

Related Objects

• MTL_ITEM_CATALOG_GROUPS_B — referenced through ITEM_CATALOG_GROUP_ID; the catalog group master.
• MTL_ITEM_CATALOG_GROUPS_TL — supplies translated catalog group names for reporting joins.
• EGO_FUNC_PARAMS_MAP — the permanent mapping table that interface rows are typically promoted into.
• EGO_ATTR_GROUPS_VL / EGO_ATTRS_VL — resolve ATTR_GROUP_ID and ATTR_ID to descriptive attribute metadata.
• FND_CONCURRENT_REQUESTS — joins on REQUEST_ID for concurrent program status and log diagnostics.
• FND_APPLICATION / FND_PROGRAM — resolve PROGRAM_APPLICATION_ID and PROGRAM_ID to the executing program.
• EGO_CATALOG_FUNCTIONS — the function definition referenced by FUNCTION_ID.

These relationships make the table a useful diagnostic complement to the permanent catalog mapping structures within the EGO product family.