Free 1Z0-1196-25 Practice Test

Control Central Search is the primary and most powerful tool within Oracle Utilities Customer Cloud Service for locating a wide range of business objects. It is specifically designed to allow users to search for entities such as devices, measuring components, service points, and usage subscriptions using an extensive set of criteria. Users can initiate searches based on identifiers or characteristics related to accounts, persons, premises, or the specific assets themselves, making it the central point for most operational inquiries and data retrieval tasks.

A. Unified Search: This is a general term for a global search feature. While the application has a global search, Control Central Search is the specific, feature-rich tool designed for the detailed, multi-criteria searches described.
B. Customer 360 Search: The Customer 360 is a comprehensive view of a single customer's information. It is the destination after a customer is found, not the primary tool for searching for various assets like devices or service points independently.
D. 360 Search: This is not a standard or official term for a search utility within the Oracle Utilities Customer Cloud Service. It is an imprecise distractor, likely derived from the "Customer 360" portal name. ---

1. Oracle Utilities Customer Cloud Service Business User Guide (Release 24A)

Part Number: F81303-01

Chapter 4: Searching for Information

Section: "About Control Central Search".

The document states

"Control Central is a powerful search tool that allows you to search for a variety of objects in the system

such as accounts

persons

premises

service points

devices

and more... You can search for these objects using a variety of information

such as an object's ID

a name

an address

a phone number

a characteristic

and so on." This directly confirms that Control Central is used to find the entities listed in the question.

2. Oracle Utilities Customer Cloud Service Business User Guide (Release 24A)

Part Number: F81303-01

Chapter 5: Maintaining Customer Information

Section: "The Customer 360 Portal".

This section describes the Customer 360 portal as a dashboard for viewing information about a specific customer. This supports the reasoning that it is a viewing tool

not the primary search mechanism for disparate objects like devices or service points.

A transfer adjustment in Oracle Customer Care and Billing (CC&B) is a specific mechanism designed to move a financial amount between two service agreements. This process is governed by two key principles. Firstly, the transfer is restricted to service agreements that belong to the same parent account; it cannot be used to move funds between different accounts. Secondly, the transaction is atomic. This means the debit adjustment on the source service agreement and the credit adjustment on the destination service agreement are created and finalized (frozen) simultaneously within a single transaction. This ensures financial integrity, as one part of the transfer cannot exist without the other.

B. The two adjustments (debit and credit) are intrinsically linked as part of a single transfer transaction; they are not created independently.
D. Approval profiles are configured at the Adjustment Type level. A single adjustment type is used for the transfer, so both legs of the transaction are subject to the same approval rules.
E. While the financial transactions for both adjustments are created when frozen, their posting to the General Ledger is a separate downstream batch process and not a defining characteristic of the transfer transaction itself.

1. Oracle Utilities Customer Care and Billing Business User Guide (Release 2.9.0.0.0)

Part Number E90236-01

Chapter 6: Maintaining Adjustments

Section: "Transferring Money Between Service Agreements"

Page 6-10.

This section explicitly states

"A transfer adjustment is a convenient mechanism to transfer monies between two service agreements that belong to the same account." This directly validates option A.

The description of the process details a single transaction screen and a single freeze action that results in two adjustments

confirming they are created and frozen together as an atomic unit

which validates option C.

2. Oracle Utilities Customer Care and Billing Administrative User Guide (Release 2.9.0.0.0)

Part Number E90234-01

Chapter 4: Setting Up Control Tables

Section: "Setting Up Adjustment Types"

Page 4-4.

This section describes the configuration of Adjustment Types

showing that the "Approval Profile" is a characteristic of the Adjustment Type itself. This supports the reasoning for why option D is incorrect

as a single transfer adjustment type would govern both the debit and credit.

In the Oracle Utilities framework, a Measurement entity represents a meter reading. The Validation, Editing, and Estimation (VEE) process operates on these measurements to ensure their accuracy before billing. When a previously billed read is corrected, a new or updated Measurement record is created. This new Measurement is the primary data entity that represents the corrected value. It serves as the fundamental trigger, or "notification," for the system to re-calculate usage for the affected period. Downstream processes, such as the usage calculation engine, detect this superseding measurement and then instantiate a new Usage Transaction, which in turn drives the billing correction. The Measurement is the authoritative source of the correction event.

A. Correction Note: This is not a standard, defined entity in the Oracle Utilities data model for this purpose; it is a plausible but incorrect distractor.
B. Off Cycle Bill Generator: This is a batch process that creates a bill, not a data entity representing a notification of a corrected read.
D. Usage Transaction: This entity is a result of the corrected read. It is created after the system is notified by the new measurement, but it is not the initial notification itself.
E. Usage Request: This entity is used to initiate the original usage calculation process, not to signal a subsequent correction to a reading.

1. Oracle Utilities Customer to Meter Cloud Service (23C) - Business User Guide

Chapter: "About Validation

Editing

and Estimation (VEE)". This chapter details how the VEE process is centered on validating

editing

and creating final

billable measurements. It establishes that the Measurement is the core entity managed in this process. A correction is fundamentally an edit to a measurement

making the Measurement entity the representation of that change.

2. Oracle Utilities Customer to Meter Cloud Service (23C) - Business User Guide

Chapter: "About Usage and Usage Transactions"

Section: "Correcting Billed Consumption". The documentation states

"When you correct a read that has been used to create a bill segment

the system automatically creates a usage transaction for the corrected read." This shows the process is triggered by the corrected read (represented by the Measurement entity)

which then leads to the creation of a Usage Transaction. The Measurement is the cause

and thus the notification.

3. Oracle Utilities Meter Data Management Business User Guide (2.7.0.1)

Chapter 4: "Validation

Editing

and Estimation"

Page 4-1. The guide describes VEE as a process that "validates initial measurements... and creates final

billable measurements". This reinforces that the entire correction and validation lifecycle is centered on the Measurement entity

which serves as the definitive record and notification of data quality and changes for downstream systems like billing.

To support billing with smart meter interval data on an existing Time-of-Use (TOU) rate, the system must be configured to map intervals to the correct TOU periods. This requires a "TOU Mapping" usage calculation rule. There are two valid architectural approaches for implementing this logic:
1. Create a new, dedicated Usage Calculation Group for smart meters (A).
2. Modify the existing Usage Calculation Group by adding the new rule (E). Regardless of the chosen approach, the system needs to dynamically apply the correct logic based on the meter type. This is achieved by configuring plug-in logic on the usage subscription (or its type) to identify the appropriate "new or existing" usage calculation group at runtime (C).

B. Usage calculation rules are components of a Usage Calculation Group, not configured directly in a Customer Rate Schedule extendable lookup.
D. This option is too specific as it only refers to identifying a "new" usage calculation group, while option C correctly encompasses both scenarios (new or existing group).
F. The primary link between a usage subscription and its usage calculation group is determined dynamically by a plug-in, not via a Customer Rate Schedule extendable lookup.

1. Oracle Utilities Customer Cloud Service Administrative User Guide (23C)

Chapter: Usage Calculation

Section: Defining Usage Calculation Rules

Subsection: TOU Mapping.

This section details the purpose of the "TOU Mapping" rule type: "This type of usage calculation rule is used to process interval usage by mapping interval reads to the appropriate time of use periods defined on a TOU Map." This supports the core requirement of using a TOU mapping rule as stated in options A and E.

2. Oracle Utilities Customer Cloud Service Administrative User Guide (23C)

Chapter: Usage Calculation

Section: How is a Usage Calculation Group Determined?

This section outlines the hierarchy for determining the usage calculation group

with the first step being the "Determine Usage Calculation Group algorithm on the usage subscription type." This confirms that dynamic identification via plug-in logic is the standard mechanism

supporting the action described in option C. It also invalidates options B and F

which propose using extendable lookups.

3. Oracle Utilities Customer Cloud Service Administrative User Guide (23C)

Chapter: Usage Calculation

Section: Defining Usage Calculation Groups.

This section describes the process of creating and maintaining Usage Calculation Groups and their associated rules. It implicitly supports both creating a new group (Option A) and modifying an existing one by adding new rules (Option E) as standard configuration actions.

In Oracle Fusion Cloud Applications, system-wide behaviors like duplicate person prevention are configured at a high, central level. This configuration involves enabling the feature and defining the matching rules the system will use (e.g., based on name, date of birth, national identifiers). The option "Installation Options" is the most appropriate generic term for this type of enterprise-level setup page. In practice, this corresponds to tasks such as "Manage Enterprise HCM Information" for employees or "Manage Enterprise Data Quality Matching Configurations" for customer data, which govern the entire application's behavior for identifying duplicates.

A. Person: This is the user interface for creating or managing individual person records, not for configuring system-wide rules.
B. Person Contact Type: This setup defines types of relationships (e.g., Emergency Contact) and is not related to duplicate entity prevention.
C. Person Identifier Type: This defines types of identifiers (e.g., National ID). While these identifiers are used by the duplicate check logic, this screen is not where the overall system feature is enabled or its matching rules are configured.
E. Person Type: This is used to classify a person (e.g., Employee, Contingent Worker) and has no role in the configuration of duplicate prevention.

1. Oracle Fusion Cloud HCM

Implementing Global Human Resources (Release 24B)

Chapter: Enterprise and Workforce Structures

Section: Duplicate Person Validation.

Reference Details: This section states

"You enable duplicate person validation on the Manage Enterprise HCM Information page. On this page

you can also specify the person-matching criteria for your enterprise." This confirms that the configuration is at a high

enterprise level

which is conceptually represented by "Installation Options".

2. Oracle Fusion Cloud Customer Data Management

Implementing Customer Data Management (Release 24B)

Chapter: Set Up Data Quality

Section: How Data Quality Is Processed.

Reference Details: This chapter explains that duplicate identification for parties (including persons) is managed by Data Quality Management (DQM). The setup requires configuring matching rules in the "Manage Enterprise Data Quality Matching Configurations" task. This is a system-wide configuration

not specific to an identifier type.

3. Oracle Fusion Cloud Applications Common

Implementing Common Features for SCM (Release 24B)

Chapter: Application Common Components

Section: Define Application Taxonomy.

Reference Details: This guide discusses foundational setups. While not using the exact term "Installation Options" (which is more common in PeopleSoft)

it describes the hierarchy of setup tasks

with enterprise-level configurations being the highest level for controlling application-wide behavior

reinforcing the correctness of option D's concept.

A Usage Subscription is the foundational agreement or contract that must be established before any consumption charges can be calculated. This subscription defines the specific product or service being consumed, the unit of measure, the pricing model (e.g., rate per unit), and the billing frequency. Without this active subscription, the system has no basis for rating, calculating, or billing the customer for their usage. It is the primary entity that links a customer to a usage-based service.

A. Usage Calculation Request: This is a process or job that initiates the calculation, but the subscription must already exist for the request to have something to calculate.
B. Usage Request: This is a generic term for a transactional request and not the core contractual agreement required for billing.
C. Usage Subscription Quantity: This represents the amount of usage consumed, which is determined during the calculation process, not a prerequisite for it.
E. Usage Transaction: These are the individual records of consumption that are fed into the calculation process, but the subscription must exist first to define the rules for processing them.

1. Oracle® Fusion Cloud SCM

Implementing Subscription Management (Release 24B)

F91531-02

Chapter 11: Usage Processing

Section: How You Process Usage for Subscriptions.

The document states

"To bill your customers for usage

you must first create a subscription with a usage-based product. The subscription can be a new one or an existing subscription to which you have added a usage-based product." This explicitly identifies the subscription as the initial requirement.

2. Oracle® Fusion Cloud SCM

Using Subscription Management (Release 24B)

F91530-02

Chapter 2: Subscriptions

Section: Overview of Subscriptions.

This section defines a subscription as the "negotiable agreement between a business and a customer for a recurring service

" establishing it as the prerequisite contract that governs the entire billing relationship

including usage-based charges.

In Oracle's billing engine, proration is triggered when a rate component designated as "proratable" changes during a billing period. This process creates multiple bill segment calculation lines to accurately calculate charges for the distinct periods before and after the change. A change to a proratable bill factor's value, a change to a different proratable calculation group (e.g., for seasonal rates), or a combination of both during the billing cycle are all events that initiate proration. Each prorated period results in a separate calculation line under the same bill segment calculation header, reflecting the specific rate details effective for that portion of the time.

A. Change of proratable rate schedule during a billing period A change in the rate schedule on a service agreement typically results in the creation of a new, distinct bill segment, not multiple calculation lines within the original one.
B. Nothing - there can be only one bill segment calculation line This is incorrect. The system is designed to handle proration, which explicitly creates multiple calculation lines to accommodate mid-period changes in rate components.

1. Oracle Utilities Customer Care and Billing Business User Guide (Release 2.8.0.0.0)

E90229-01

Chapter 4: Billing

Section: The Big Picture of Billing

Subsection: An Illustration of Proration.

This section explains the concept: "Proration occurs when an element of a rate changes during a bill period... When a bill segment is prorated

the system creates a bill segment calculation line for each portion of the bill period." It explicitly mentions that changes to bill factors and calculation groups trigger this.

2. Oracle Utilities Customer Care and Billing Business User Guide (Release 2.8.0.0.0)

E90229-01

Chapter 13: Setting Up Rates

Section: Defining Rate Versions

Subsection: Rate Version - Main.

The documentation for configuring a Rate Version includes the "Prorate" checkbox for Calculation Groups. It states

"Turn on this switch if the calculation group may be prorated... For example

if you have seasonal rates

you would prorate the calculation groups that contain the seasonal calculation rules." This directly supports options D and E.

3. Oracle Utilities Customer Care and Billing Business User Guide (Release 2.8.0.0.0)

E90229-01

Chapter 13: Setting Up Rates

Section: Setting Up Bill Factors

Subsection: Bill Factor - Main.

The documentation for Bill Factor configuration details the "Proratable" switch. The description clarifies that if this switch is on

"the system will prorate bill segments when the bill factor's value changes mid-way through a bill segment's bill period." This directly supports option C.

In Oracle Utilities Customer Cloud Service, the agent-assisted Start/Stop/Transfer process uses a parent Customer Service Request (CSR) to manage the overall workflow. When prerequisites are required, such as a field activity for a meter installation or collecting a deposit, child CSRs are created to manage these tasks. The parent CSR transitions to the "Waiting for Additional Actions" state. This state effectively pauses the main process, pending the completion of these prerequisite child CSRs. Once all required child CSRs are completed, the parent CSR can proceed to the next state to finalize the service start or transfer.

A. Start Service Processing: This state is incorrect because it represents the active phase where the service agreement is being created, which occurs after all prerequisites have been met.
C. Waiting for Completion: This is a generic state. "Waiting for Additional Actions" is the specific, designated state in this process flow for handling prerequisite child CSRs.
D. Pending: This is typically an initial state for a CSR before processing begins, not the state used to wait for prerequisite actions mid-process.
E. Start Service Set Up: This describes the initial data gathering and configuration phase of the request, not the waiting period for dependent tasks to be executed.

1. Oracle Utilities Customer Cloud Service Business User Guide (25A)

Chapter: Managing Customer Service Requests

Section: "About the Start/Stop/Transfer Service Process". This section details the orchestration role of the parent CSR

stating

"The parent CSR moves to the 'Waiting for Additional Actions' state while it waits for the child CSRs to complete." This confirms that this state is used specifically for processing prerequisites.

2. Oracle Utilities Customer Cloud Service Administrative User Guide (25A)

Chapter: Business Object

Section: "Anatomy of a Business Object". This chapter explains that business objects have defined lifecycles with specific states. The "Waiting for Additional Actions" state is a standard state in the C1-CustomerServiceRequest business object's lifecycle designed for scenarios where the process must pause for dependent activities.

In Oracle Utilities Customer to Meter (C2M), decommissioning an asset is a key part of its lifecycle management. This process involves changing the asset's status to a final, non-operational state, such as "Retired" or "Scrapped". The asset record is not deleted; instead, it is preserved along with its complete history, including installation records, maintenance activities, and operational data (e.g., meter readings). Retaining this historical data is essential for regulatory compliance, auditing purposes, and for performing historical analysis on asset performance and failure rates.

B. It is permanently deleted along with all related records. This is incorrect. C2M is a system of record that must maintain a complete audit trail. Deleting historical asset data would violate data integrity principles and regulatory requirements.
C. It is reassigned to a different customer account. This describes a transfer of service or asset ownership, which is a different business process. Decommissioning specifically means taking an asset out of active service permanently.
D. It is automatically replaced with a new asset in the same location. While decommissioning an asset may trigger a workflow to install a replacement, the replacement is a separate, subsequent action and not an automatic, integral part of the decommissioning step itself.

1. Oracle Utilities Customer To Meter Business User Guide (Release 2.9.0.1.0)

Part Number E99223-01

Chapter 5: Asset Management

Section: "About Assets". The documentation describes the asset lifecycle

which involves transitioning through various statuses. The final statuses

such as "Retired" or "Disposed

" signify the end of the asset's service life

but the record and its history are maintained within the system for reference.

2. Oracle Utilities Application Framework Business Process Guide (Release 4.5.0.0.0)

Part Number F53253-01

Chapter 2: Implementation Tools

Section: "Lifecycle of a Business Object". This guide explains the underlying framework principle that business objects (like assets) transition through statuses via business rules. Final statuses do not equate to deletion

ensuring data is archived and available for historical queries rather than being purged.

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).