Oracle 2010 Annual Report Download - page 166

Download and view the complete annual report

Please find page 166 of the 2010 Oracle annual report below. You can navigate through the pages in the report by either clicking on the pages listed below, or by using the keyword search tool below to find specific information within the annual report.

Page out of 272

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272

product support revenues. While the basis for software license revenue recognition is
substantially governed by the accounting guidance contained in ASC 985-605,
Software-Revenue Recognition, we exercise judgment and use estimates in connection
with the determination of the amount of software and services revenues to be recognized
in each accounting period.
For software license arrangements that do not require significant modification or
customization of the underlying software, we recognize new software license revenues
when: (1) we enter into a legally binding arrangement with a customer for the license of
software; (2) we deliver the products; (3) the sale price is fixed or determinable and free
of contingencies or significant uncertainties; and (4) collection is probable. Revenues that
are not recognized at the time of sale because the foregoing conditions are not met are
recognized when those conditions are subsequently met.
Substantially all of our software license arrangements do not include acceptance
provisions. However, if acceptance provisions exist as part of public policy, for example,
in agreements with government entities where acceptance periods are required by law, or
within previously executed terms and conditions that are referenced in the current
agreement and are short-term in nature, we generally recognize revenues upon delivery
provided the acceptance terms are perfunctory and all other revenue recognition criteria
have been met. If acceptance provisions are not perfunctory (for example, acceptance
provisions that are long-term in nature or are not included as standard terms of an
arrangement), revenues are recognized upon the earlier of receipt of written customer
acceptance or expiration of the acceptance period.
The vast majority of our software license arrangements include software license updates
and product support contracts, which are entered into at the customers option and are
recognized ratably over the term of the arrangement, typically one year. Software license
updates provide customers with rights to unspecified software product upgrades,
maintenance releases and patches released during the term of the support period. Product
support includes internet access to technical content, as well as internet and telephone
access to technical support personnel. Software license updates and product support
contracts are generally priced as a percentage of the net new software license fees.
Substantially all of our customers renew their software license updates and product
support contracts annually.
Revenue Recognition for Multiple-Element Arrangements – Software Products and
Software Related Services (Software Arrangements)
We often enter into arrangements with customers that purchase both software related
products and services from us at the same time, or within close proximity of one another
(referred to as software related multiple-element arrangements). Such software related
multiple-element arrangements include the sale of our software products,
software license updates and product support contracts and other software related services
whereby software license delivery is followed by the subsequent or contemporaneous
delivery of the other elements. For those software related multiple-element arrangements,
we have applied the residual method to determine the amount of software license
revenues to be recognized pursuant to ASC 985-605. Under the residual method, if fair
value exists for undelivered elements in a multiple-element arrangement, such fair value
of the undelivered elements is deferred with the remaining portion of the arrangement
consideration recognized upon delivery of the software license or services arrangement.
We allocate the fair value of each element of a software related multiple-element
arrangement based upon its fair value as determined by our vendor specific objective
evidence (VSOE – described further below), with any remaining amount allocated to the
software license.
Revenue Recognition for Hardware Systems Products and Hardware Systems Related
Services (Nonsoftware Elements)
Revenues from the sale of hardware systems products represent amounts earned primarily
from the sale of computer servers and storage products. Our revenue recognition policy
for these nonsoftware deliverables is based upon the accounting guidance contained in
ASC 605, Revenue Recognition, and we exercise judgment and use estimates in
connection with the determination of the amount of hardware systems products and
hardware systems related services revenues to be recognized in each accounting period.
Revenues from the sales of hardware products are recognized when: (1) persuasive
evidence of an arrangement exists; (2) we deliver the products and passage of the title to
the buyer occurs; (3) the sale price is fixed or determinable; and (4) collection is
reasonably assured. Revenues that are not recognized at the time of sale because the
foregoing conditions are not met are recognized when those conditions are subsequently
met. When applicable, we reduce revenues for estimated returns or certain other incentive
programs where we have the ability to sufficiently estimate the effects of these items.
Where an arrangement is subject to acceptance criteria and the acceptance provisions are
not perfunctory (for example, acceptance provisions that are long-term in nature or are
not included as standard terms of an arrangement), revenues are recognized upon the
earlier of receipt of written customer acceptance or expiration of the acceptance period.
Our hardware systems support offerings generally provide customers with software
updates for the software components that are essential to the functionality of our systems
and storage products and can also include product repairs, maintenance services, and
technical support services. Hardware systems support contracts are entered into at the
customers option and are recognized ratably over the contractual term of the
arrangements.
Revenue Recognition for Multiple-Element Arrangements – Hardware Systems Products
and Hardware Systems Related Services (Nonsoftware Arrangements)
Beginning in fiscal 2010, we have applied the provisions of Accounting Standards
Update No. 2009-13, Revenue Recognition (Topic 605) Multiple-Deliverable Revenue
Source: ORACLE CORP, 10-K, June 28, 2011 Powered by Morningstar® Document Research