ACCOUNTING POLICIES (Policy)	3 Months Ended
Aug. 31, 2015
Accounting Policies [Abstract]
Recent Accounting Pronouncements	Recent Accounting Pronouncements Cloud Computing Arrangements that Include a Software Element: In April 2015, the Financial Accounting Standards Board (FASB) issued ASU 2015-05, Intangibles—Goodwill and Other—Internal-Use Software (Subtopic 350-40): Customer’s Accounting for Fees Paid in a Cloud Computing Arrangement (ASU 2015-05). ASU 2015-05 provides guidance to customers about whether a cloud computing arrangement includes software. If a cloud computing arrangement includes a software license, the customer should account for the software license element of the arrangement consistent with the acquisition of other software licenses. If a cloud computing arrangement does not include a software license, the customer should account for the arrangement as a service contract. The new guidance does not change the accounting for a customer’s accounting for service contracts. ASU 2015-05 is effective for us in our first quarter of fiscal 2017 with early adoption permitted using either of two methods: (i) prospective to all arrangements entered into or materially modified after the effective date and represents a change in accounting principle; or (ii) retrospectively. We are currently evaluating the impact of our pending adoption of ASU 2015-05 on our consolidated financial statements. Revenue Recognition: In May 2014, the FASB issued ASU 2014-09, Revenue from Contracts with Customers: Topic 606 (ASU 2014-09), to supersede nearly all existing revenue recognition guidance under U.S. GAAP. The core principle of ASU 2014-09 is to recognize revenues when promised goods or services are transferred to customers in an amount that reflects the consideration that is expected to be received for those goods or services. ASU 2014-09 defines a five step process to achieve this core principle and, in doing so, it is possible more judgment and estimates may be required within the revenue recognition process than are required under existing U.S. GAAP, including identifying performance obligations in the contract, estimating the amount of variable consideration to include in the transaction price and allocating the transaction price to each separate performance obligation, among others. The original effective date of ASU 2014-09 would have required us to adopt the standard in our first quarter of fiscal 2018. In August 2015, the FASB issued ASU 2015-14, Revenue from Contracts with Customers (Topic 606): Deferral of the Effective Date (ASU 2015-14), which defers the effective date by one year while providing the option to early adopt the standard on the original effective date. Accordingly, we may adopt the standard either in our first quarter of fiscal 2018 or our first quarter of fiscal 2019 using either of two methods: (i) retrospective application of ASU 2014-09 to each prior reporting period presented with the option to elect certain practical expedients as defined within ASU 2014-09; or (ii) retrospective application of ASU 2014-09 with the cumulative effect of initially applying ASU 2014-09 recognized at the date of initial application and providing certain additional disclosures as defined per ASU 2014-09. We are currently evaluating the timing and the impact of our pending adoption of ASU 2014-09 on our consolidated financial statements.

ACCOUNTING POLICIES (Policy)

3 Months Ended

Aug. 31, 2015

Cloud Computing Arrangements that Include a Software Element: In April 2015, the Financial Accounting Standards Board (FASB) issued ASU 2015-05, Intangibles—Goodwill and Other—Internal-Use Software (Subtopic 350-40): Customer’s Accounting for Fees Paid in a Cloud Computing Arrangement (ASU 2015-05). ASU 2015-05 provides guidance to customers about whether a cloud computing arrangement includes software. If a cloud computing arrangement includes a software license, the customer should account for the software license element of the arrangement consistent with the acquisition of other software licenses. If a cloud computing arrangement does not include a software license, the customer should account for the arrangement as a service contract. The new guidance does not change the accounting for a customer’s accounting for service contracts. ASU 2015-05 is effective for us in our first quarter of fiscal 2017 with early adoption permitted using either of two methods: (i) prospective to all arrangements entered into or materially modified after the effective date and represents a change in accounting principle; or (ii) retrospectively. We are currently evaluating the impact of our pending adoption of ASU 2015-05 on our consolidated financial statements.

Revenue Recognition: In May 2014, the FASB issued ASU 2014-09, Revenue from Contracts with Customers: Topic 606 (ASU 2014-09), to supersede nearly all existing revenue recognition guidance under U.S. GAAP. The core principle of ASU 2014-09 is to recognize revenues when promised goods or services are transferred to customers in an amount that reflects the consideration that is expected to be received for those goods or services. ASU 2014-09 defines a five step process to achieve this core principle and, in doing so, it is possible more judgment and estimates may be required within the revenue recognition process than are required under existing U.S. GAAP, including identifying performance obligations in the contract, estimating the amount of variable consideration to include in the transaction price and allocating the transaction price to each separate performance obligation, among others. The original effective date of ASU 2014-09 would have required us to adopt the standard in our first quarter of fiscal 2018. In August 2015, the FASB issued ASU 2015-14, Revenue from Contracts with Customers (Topic 606): Deferral of the Effective Date (ASU 2015-14), which defers the effective date by one year while providing the option to early adopt the standard on the original effective date. Accordingly, we may adopt the standard either in our first quarter of fiscal 2018 or our first quarter of fiscal 2019 using either of two methods: (i) retrospective application of ASU 2014-09 to each prior reporting period presented with the option to elect certain practical expedients as defined within ASU 2014-09; or (ii) retrospective application of ASU 2014-09 with the cumulative effect of initially applying ASU 2014-09 recognized at the date of initial application and providing certain additional disclosures as defined per ASU 2014-09. We are currently evaluating the timing and the impact of our pending adoption of ASU 2014-09 on our consolidated financial statements.