[Describing the Customer to Meter Product] Various records in Customer to Meter reference field and lookup values from their relevant application components. What is used to map similar field and lookup values between application components?

Domain Value Maps (DVMs) are a standard feature within the Oracle Utilities Application Framework (OUAF), upon which Customer to Meter (C2M) is built. DVMs are specifically designed to facilitate data integration by creating a mapping between the values of a field in one application component or system and the corresponding values in another. For example, a DVM can translate a status code 'A' from a source component to 'Active' in a target component, ensuring semantic consistency across different parts of the application landscape.

B. Master Configurations: These are used to define core business objects and their behavior within the application, not for mapping field values between components.
C. Lookups: Lookups define a list of permissible values for a specific field within a single application context, but they do not perform translation between different components.
D. Feature Configurations: These are used to enable, disable, or modify the behavior of specific application features and functionalities, not for data value mapping.
E. Extendable Lookups: This is a type of lookup that allows customer-defined values. Like standard lookups, their purpose is to define a list of values, not to map them. ---

1. Oracle Utilities Application Framework V4.5.0.0.0

Administration Guide: In the "Integration" section

under "Setting Up Domain Value Maps

" the documentation states

"Domain Value Maps (DVM) are used to map values from a field in one application to a corresponding field in another application." (Document ID: E97222-01

Chapter 13: Integration

Page 13-10).

2. Oracle Utilities Customer To Meter 2.9.0.0.0

Business User Guide: While not defining DVMs directly

the guide describes various business processes that rely on consistent data across different functional areas (e.g.

billing

service management). The underlying OUAF framework uses DVMs to ensure this consistency during integrations. (Reference to the concept of data consistency across modules).

3. Oracle Fusion Middleware Concepts Guide 12c (12.2.1.4.0): As the foundational technology

this guide provides a detailed definition: "A domain value map (DVM) enables you to look up values in one domain and find corresponding values in another domain... For example

one domain may use a city code of SFO

while another domain uses a city code of San Francisco." This concept is directly implemented in OUAF. (Document ID: E92018-01

Chapter 2: Introduction to Oracle SOA Suite

Section 2.10.3 Domain Value Maps).