Comprehensive and Detailed Explanation From Exact Extract:
In Oracle Utilities Customer to Meter, when a frozen bill segment is cancelled and rebilled due to an issue, the system handles the financial transactions and bill presentation as follows:
Statement A: "Both the originating and cancellation financial transactions are swept onto the same bill and the Show on Bill switches on the financial transactions will be deselected." This is correct.
According to the Oracle Utilities Customer to Meter Billing Guide, when a bill segment is cancelled, both the original (originating) and cancellation financial transactions are included in the bill, but their
"Show on Bill" switches are deselected to prevent them from appearing as line items on the customer's bill, ensuring clarity.
Statement C: "The bill will only include the newly created bill segment details for the customer to see and the cancelled bill segment details will be suppressed from all subsequent bills." This is also correct.
The documentation specifies that after cancellation, only the new (rebilled) bill segment is visible to the customer, and the cancelled bill segment is suppressed to avoid confusion.
The other statements are incorrect:
Statement B: Including both the original and new bill segments for the customer to see would create confusion and is not standard practice in the system.
Statement D: The cancelled bill segment details are not included in the following bill; they are suppressed entirely after cancellation.
Statement E: The "Show on Bill" switches are deselected, not selected, to ensure the cancelled transactions do not appear on the bill.
Thus, the correct answers areAandC, as they accurately reflect the system's handling of cancelled and rebilled segments.
Reference:
Oracle Utilities Customer to Meter Billing Guide, Section: Bill Segment Cancellation and Rebilling Oracle Utilities Customer to Meter Implementation Guide, Chapter: Billing Processes

Comprehensive and Detailed Explanation From Exact Extract:
In Oracle Utilities Customer to Meter,bill segment calculation linesdetail how a bill segment's amount is calculated based on the rate calculation rules. Multiple calculation lines can be generated when there are changes in the rate structure during a billing period that affect proration. The Oracle Utilities Customer to Meter Configuration Guide specifies thata change in the proratable rate version calculation group for a rate schedule and a proratable bill factor value in the rate version calculation group during a billing period(Option D) can cause multiple bill segment calculation lines. This occurs because the system must prorate the charges for different periods within the billing cycle, creating separate lines for each applicable rate or bill factor.
The other options are incorrect:
Option A: A change in the rate schedule itself is not typically proratable within a single billing period; it would result in a new bill segment, not multiple calculation lines.
Option B: Multiple calculation lines can be produced, so this is incorrect.
Option C: A change in the bill factor value alone may not necessitate multiple lines unless combined with a rate version change.
Option E: A change in the rate version calculation group alone is insufficient without the additional impact of a proratable bill factor change.
Thus, the correct answer isD, as it accurately describes the conditions leading to multiple calculation lines.
Reference:
Oracle Utilities Customer to Meter Configuration Guide, Section: Rate Calculation and Bill Segment Calculation Lines Oracle Utilities Customer to Meter Implementation Guide, Chapter: Rate Configuration

Comprehensive and Detailed Explanation From Exact Extract:
In Oracle Utilities Customer to Meter, bills are typically generated through background processing for accounts in open bill cycles. However, the system also supports additional batch processing options for flexibility. According to the Oracle Utilities Customer to Meter Configuration Guide:
Option B: "A specific account" can be targeted for bill generation via background processing using batch controls, allowing for individual account billing outside of a standard bill cycle.
Option C: "Subset of accounts belonging to an open bill cycle or cycles for a specific customer class" is supported, enabling targeted billing for specific customer classes within open bill cycles.
Option E: "A user-defined list of accounts" can be processed via batch controls, allowing business users to specify a custom list of accounts for billing.
The other options are incorrect:
Option A: Accounts not belonging to a specific open bill cycle cannot be processed via standard batch controls for bill generation, as bill cycles are a prerequisite for most billing processes.
Option D: While similar to Option C, this option is less specific and redundant, as the system typically requires additional criteria (e.g., customer class) to define the subset, making Option C the more accurate choice.
Thus, the correct answers areB,C, andE, reflecting the system's capabilities for targeted bill generation.
Reference:
Oracle Utilities Customer to Meter Configuration Guide, Section: Batch Processing for Billing Oracle Utilities Customer to Meter Implementation Guide, Chapter: Billing Automation