Use the CSU menu in the navigation menu to see consumption, entitlement and procurement reports for Cloud Service Units (CSU) for customers with Technology Cloud services, as explained in the following sections:
|
Note: To view the CSU menu, you must have at least one active Oracle Public Cloud service, and your My Oracle Support account must have privileges to view service and/or change requests. |
The CSU menu (
) provides information about the consumption and purchase activity, as well as details about the CSUs for the customer. The consumption activity is presented as a monthly statement view. The purchase activity displays CSUs purchased by the customer.
By default, information on the Dashboard, List, and Chart views defaults to the current month, with the filter in the upper right corner set to Recent Activities. For more information on how to display CSU data for any of the previous 12 months, see the Generating Reports for Different Time Periods section in Chapter 3, "Working with Oracle Pulse".
To access the CSU dashboard:
Sign in to Oracle Pulse as explained in the Accessing Oracle Pulse section in Chapter 1, "Introduction".
The Pulse Dashboard is displayed by default.
Click CSU in the navigation menu.
The CSU Dashboard page opens.
Click the icons in the upper left corner to acccess the views on the CSU dashboard:
Click
to access the CSU Dashboard view.
Click
to access the CSU List view.
Click
to access the CSU Chart view.
This section describes how to use the reports on the CSU Dashboard view to analyze your account details, as explained in the following sections:
Location: On the CSU Dashboard view (
) at Customer Level, when the filter in the upper right corner is set to Recent Activities. For more information on how to access the CSU Dashboard view, see Accessing the CSU Dashboard.
The Balance of Last Statement widget specifies the CSU balance at the close of the previous reporting period.
Location: On the CSU Dashboard view (
) at Customer Level, when the filter in the upper right corner is set to Recent Activities or to any of the previous 12 months. For more information on how to access the CSU Dashboard view, see Accessing the CSU Dashboard.
The Purchased widget specifies the number of CSUs you have purchased for your services in the month subject to the statement.
Location: On the CSU Dashboard view (
) at Customer Level, when the filter in the upper right corner is set to Recent Activities or to any of the previous 12 months. For more information on how to access the CSU Dashboard view, see Accessing the CSU Dashboard.
The Credits widget specifies the number of credits awarded for use in the month subject to the statement.
Location: On the CSU Dashboard view (
) at Customer Level, when the filter in the upper right corner is set to Recent Activities. For more information on how to access the CSU Dashboard view, see Accessing the CSU Dashboard.
The Posted Charges widget specifies the number of CSUs that will be charged at the end of the current month.
Location: On the CSU Dashboard view (
) at Customer Level, when the filter in the upper right corner is set to Recent Activities. For more information on how to access the CSU Dashboard view, see Accessing the CSU Dashboard.
The Pending Charges widget specifies the number of CSUs that may be charged at the end of the current month.
Location: On the CSU Dashboard view (
) at Customer Level, when the filter in the upper right corner is set to Recent Activities. For more information on how to access the CSU Dashboard view, see Accessing the CSU Dashboard.
Chart View: The Posted Activities chart shows the breakdown by activity for CSUs that will be charged at the end of the month.
Click the Open Table View icon (
) in the lower right corner of a chart to open the Posted Activities table view in expanded mode.
Table View: The table view shows details about each activity for which CSUs will be charged at the end of the month:
Activity: Specifies the type of the activity for which CSUs will be charged at the end of the month.
MOS Ref#: Specifies the MOS identification number of the SR or RFC.
Environment: Specifies the designated environment where the SR or RFC was applied.
Activity Date (UTC): Specifies the date when the activity was applied.
Charge: Specifies the CSU cost.
Status: Specifies the status of the activity. All activities included in this chart are in Posted status.
ID: Specifies the identification number of the transaction.
Location: On the CSU Dashboard view (
) at Customer Level, when the filter in the upper right corner is set to Recent Activities. For more information on how to access the CSU Dashboard view, see Accessing the CSU Dashboard.
Chart View: The Pending Activities chart shows the breakdown by activity for CSUs that may be charged at the end of the month.
Click the Open Table View icon (
) in the lower right corner of a chart to open the Pending Activities table view in expanded mode.
Table View: The table view shows details about each activity for which CSUs may be charged at the end of the month:
Activity: Specifies the type of the activity for which CSUs may be charged at the end of the month.
MOS Ref#: Specifies the MOS identification number of the SR or RFC.
Environment: Specifies the designated environment where the SR or RFC was applied.
Activity Date (UTC): Specifies the date when the activity was applied.
Charge: Specifies the CSU cost.
Status: Specifies the status of the activity. All activities included in this chart are in Pending status.
ID: Specifies the identification number of the transaction.
Location: On the CSU Dashboard view (
) at Customer Level, when the filter in the upper right corner is set to any of the previous 12 months. For more information on how to access the CSU Dashboard view, see Accessing the CSU Dashboard.
The Starting Balance widget specifies the posted CSU balance at the close of the previous reporting period.
Location: On the CSU Dashboard view (
) at Customer Level. For more information on how to access the CSU Dashboard view, see Accessing the CSU Dashboard.
The Consumed widget specifies the number of CSUs you have consumed for your services in the month subject to the statement.
Location: On the CSU Dashboard view (
) at Customer Level. For more information on how to access the CSU Dashboard view, see Accessing the CSU Dashboard.
The Ending Balance widget specifies the posted CSU balance at the end of the reporting period.
This section describes how to use the charts on the CSU Dashboard view to analyze your consumed Cloud Service Units, as explained in the following sections:
Location: On the CSU Dashboard view (
) at Customer Level. For more information on how to access the CSU Dashboard view, see Accessing the CSU Dashboard.
The Consumed By Activity chart shows the breakdown of CSU charges by activity. The following activities are counted towards your CSU consumption quota:
Backup
CEMLI
Configuration
Datafix
Patch
Refresh
Service Request
Start & Stop
Location: On the CSU Dashboard view (
) at Customer Level. For more information on how to access the CSU Dashboard view, see Accessing the CSU Dashboard.
The Consumed By Environment chart provides a clear insight into the number of CSUs used for each of your environments, divided by activity type.
This section describes how to use the tables on the CSU List view to view Cloud Service Units details, as explained in the following sections:
Location: On the CSU List view (
) at Customer Level, under the Activities tab. For more information on how to access the CSU List view, see Accessing the CSU Dashboard and Navigating the CSU Dashboard.
The Activities table shows the list of activities for the selected month. Each record displays the following information:
Activity: Specifies the type of the activity subject to the RFC or SR. Available options include:
Backup
CEMLI
Configuration
Datafix
Patch
Refresh
Start & Stop
MOS Ref#: Specifies the MOS identification number of the RFC or SR.
|
Note: Click a MOS Ref# value or its associated See details icon to open the request in My Oracle Support. |
Environment: Specifies the designated environment where the RFC or the SR will be applied.
Activity Date (UTC): Specifies the date when the activity was applied to the statement balance.
Charge: Specifies the CSU cost. For activities included with your purchased services, the CSU charge is 0.
Status: Specifies the status of the activity in the current statement. Available options include:
Booked
Pending
Expired
ID: Specifies the identification number of the transaction.
More Info: Click the Entitlement icon (
) to get details about an activity you are entitled to, and the charge is 0, or click the View Dispute icon (
) to get details about an activity for which a dispute has been initiated.
By default, this report shows data for the current month, with the filter in the upper right corner set to Recent Activities. The reporting period can be changed to show data for any of the previous 12 months. To define a custom reporting period, click the page time selector in the upper right corner, as explained in the Generating Reports for Different Time Periods section in Chapter 3, "Working with Oracle Pulse".
Use the Activities table to:
sort records, as explained in the Sorting Records section in Chapter 3, "Working with Oracle Pulse".
view full CSU consumption summary, as explained in Viewing CSU Consumption Summary.
initiate and view disputes for transactions performed on a particular environment, as explained in Disputing Activities.
export data in MS Excel format, as explained in the Exporting Data section in Chapter 3, "Working with Oracle Pulse".
To see the full CSU consumption summary, in the Activities table, click the activity whose summary you want to see. The Activity Details page opens, providing the following information:
MOS Ref#: Specifies the MOS identification number of the RFC or SR.
|
Note: Click a MOS Ref# value or its associated See details icon to open the request in My Oracle Support. |
Service: Specifies the type of the service subject to the activity.
Environment: Specifies the designated environment where the RFC or the SR will be applied.
Charge: Specifies the CSU cost. For activities included with your purchased services, the CSU charge is 0.
Activity: Specifies the type of the activity subject to the RFC or SR. Available options include:
Backup
CEMLI
Configuration
Datafix
Patch
Refresh
Start & Stop
Activity Date (UTC): Specifies the date when the activity was applied to the statement balance.
Status: Specifies the status of the activity in the current statement. Available options include:
Booked
Pending
Expired
Requested by: Specifies the requestor of the RFC or SR. Available options include:
Oracle
Customer
ID: Specifies the identification number of the transaction.
Request Category: Specifies the Orion category, type and subtype for RFCs or the product, component and subcomponent for SRs.
For eligible activities, the dispute process allows you to request consumed CSU charges to be credited back to you following an internal review. This section describes how to initiate and view disputes for activities performed during the latest completed statement period.
Initiating a Dispute
Disputes can be initiated only for transactions performed on a particular environment during the previous statement period. To initiate a dispute, you must have the Customer Authorized Approver privilege for the environment the transaction is associated with.
To initiate a dispute:
In the Activities table, click the activity for which you want to initiate a dispute.
The Activity Details page opens.
Click the Dispute this Activity link in the lower right corner of the window.
The New Dispute dialog box opens, showing the following information:
MOS Ref#: This field is automatically populated with the identification number of the RFC or SR.
Activity Type: This field is automatically populated with the type of the activity subject to the RFC or SR.
Activity ID: This field is automatically populated with the ID of the activity subject to the RFC or SR.
Environment: This field is automatically populated with the designated environment where the RFC or the SR was applied.
Primary Contact: This field is automatically populated with the email address of the Authorized Approver who initiated the dispute.
Reason: Select a justification for the dispute. Available options include:
Oracle Requested
Work completed on wrong environment
Other
Alternate Contact: Select an alternate contact name and phone number of the person who may be contacted in regard to the dispute.
From the Reason list, select a justification for the dispute.
From the Alternate Contact list, select the email address of the person who may be contacted in regard to the RFC.
Click Submit.
A confirmation message is displayed at the top of the Activities table, and the View Dispute icon (
) is displayed next to the activity within 30 minutes from the time the dispute was submitted.
Viewing a Dispute
To view a dispute, you must have the Authorized Approver privilege for the customer support identifier (CSI) associated with the environment against which the dispute was raised.
To view a dispute, click the View Dispute icon (
) next to the activity in question. The Request Detail window opens, showing the following information:
the Summary tab provides a description of the identifying data points of the activity, as explained in Viewing CSU Consumption Summary.
the Dispute tab provides detailed information about the dispute:
MOS Ref#: Specifies the MOS identification number of the RFC or SR.
Status: Specifies the current status of the dispute request. Available options include:
Open: New
Open: Acknowledge
Closed: Credit
Closed: Denied
Environment: Specifies the designated environment where the RFC or the SR was applied.
Credit Issued: Specifies the number of units credited, if any.
Activity: Specifies the type of the activity subject to the RFC or SR.
Dispute Date (UTC): Specifies the date when the dispute was created.
Reason: Specifies the justification for the dispute. Available options include:
Oracle Requested
Other
Primary Contact: Specifies the authorized approver who initiated the dispute request.
Alternate Contact: Specifies an alternate contact name and phone number of the person who may be contacted in regard to the dispute.
Oracle Response: Contains comments from the Oracle reviewing team. Available options include:
Oracle Requested
Work completed on wrong environment
Other
Location: On the CSU List view (
) at Customer Level, under the Entitlement tab. For more information on how to access the CSU List view, see Accessing the CSU Dashboard and Navigating the CSU Dashboard.
The Entitlement table provides details about the CSUs you purchased for your services, as well as the CSUs that have been credited to you. Each record displays the following information:
Start date (UTC): Specifies the date when the CSUs become effective.
Expiry date (UTC): Specifies the date by when you can use your purchased CSUs.
Count: Specifies the number of CSUs you are entitled to at a particular point in time.
Status: Specifies the status of the CSU. Available options include:
Active
Expired
Pending
Use the Entitlement table to:
sort records, as explained in the Sorting Records section in Chapter 3, "Working with Oracle Pulse".
filter records, as explained in Filtering Records.
Use the filter in the upper right corner of the Entitlement tab to display only the records of interest. Available options include:
All Entitlement: Use this option to display all the CSUs you are entitled to use. This is the default selection.
Active Entitlement: Use this option to display only the CSUs that are still available for use.
Expired Entitlement: Use this option to display only the CSUs that have expired.
Pending Entitlement: Use this option to display only the CSUs that are being used in the current month.
This section describes how to use the Projection chart on the CSU Chart view to analyze Cloud Service Units consumption trend, as explained in Projection Chart.
Location: On the CSU Chart view (
) at Customer Level. For more information on how to access the CSU Chart view, see Accessing the CSU Dashboard and Navigating the CSU Dashboard.
The Projection chart offers a graphical representation of the overall usage and the forecasted consumption of available CSUs.