Search Results parameter_mapping_id

Overview

The VEA_PARAMETER_MAPPINGS table is a core data object within the Oracle E-Business Suite Automotive (VEA) module, present in both the 12.1.1 and 12.2.2 releases. It serves as a configuration and mapping table that defines the relationships between parameters used in different logical layers of the application. Specifically, its documented purpose is to map parameters from trading partner selector (TPS) program units to corresponding parameters in base layer program units. This mapping is essential for the dynamic execution and data flow between customizable, partner-specific logic and the foundational application logic, enabling the flexible business process configurations required in automotive industry implementations.

Key Information Stored

The table stores mapping records that link two distinct parameter definitions. Each record is uniquely identified by a composite primary key involving the LAYER_PROVIDER_CODE and PARAMETER_MAPPING_ID. The critical foreign key columns establish the relationships that define the mapping. The LAYER_PROVIDER_CODE and LAYER_HEADER_ID columns together reference a specific layer definition in the VEA_LAYER_HEADERS table, providing the context for the mapping. The TPS_PARAMETER_LP_CODE and TSP_PARAMETER_ID columns reference the source parameter from the trading partner selector, stored in the VEA_PARAMETERS table. Conversely, the PROGRAM_UNIT_PARAM_LP_CODE and PROGRAM_UNIT_PARAMETER_ID columns reference the target parameter in the base layer program unit, also stored in the VEA_PARAMETERS table.

Common Use Cases and Queries

This table is primarily accessed during the runtime execution of configured automotive business processes, where parameter values must be passed from selector logic to core logic. Common administrative and support tasks include auditing configuration setups and troubleshooting data flow issues. A typical query would retrieve all parameter mappings defined for a specific application layer to validate configuration.

SELECT tps_param.parameter_name AS tps_parameter,
       base_param.parameter_name AS base_parameter,
       map.*
FROM   vea_parameter_mappings map,
       vea_parameters tps_param,
       vea_parameters base_param
WHERE  map.layer_header_id = :p_layer_id
AND    map.tps_parameter_lp_code = tps_param.layer_provider_code
AND    map.tps_parameter_id = tps_param.parameter_id
AND    map.program_unit_param_lp_code = base_param.layer_provider_code
AND    map.program_unit_parameter_id = base_param.parameter_id;

Another use case involves identifying unmapped parameters for a given layer to ensure configuration completeness.

Related Objects

The VEA_PARAMETER_MAPPINGS table has defined foreign key relationships with two other core VEA tables, as documented in the ETRM metadata:

• VEA_LAYER_HEADERS: The mapping record is scoped to a specific application layer via the columns LAYER_PROVIDER_CODE and LAYER_HEADER_ID.
• VEA_PARAMETERS (Two Relationships):
  • References the trading partner selector parameter using TPS_PARAMETER_LP_CODE and TPS_PARAMETER_ID.
  • References the base layer program unit parameter using PROGRAM_UNIT_PARAM_LP_CODE and PROGRAM_UNIT_PARAMETER_ID.

These relationships are critical for maintaining referential integrity and for understanding the complete configuration data model within the VEA module.