Planned Innovation:

Migration from SD Revenue Recognition

July, 2015 Customer
Legal Disclaimer

The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the
permission of SAP. This presentation is not subject to your license agreement or any other service or subscription
agreement with SAP. SAP has no obligation to pursue any course of business outlined in this document or any related
presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation
and SAP's strategy and possible future developments, products and/or platforms directions and functionality are all
subject to change and may be changed by SAP at any time for any reason without notice. The information on this
document is not a commitment, promise or legal obligation to deliver any material, code or functionality. This document
is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement. This document is for informational purposes and
may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this document, and
shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential
damages that may result from the use of this document. This limitation shall not apply in cases of intent or gross
negligence.

All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements,
which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 2

Agenda

 SD Revenue Recognition
 What can be migrated from SD Revenue Recognition ?
 Operational Load and SD Revenue Recognition
 First transfer of RAI‘s based on SD Revenue Recognition
 Adaptation of SD Revenue Recognition data

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 3

Current SD Revenue Recognition in SAP ERP

Integrated solution in SD affecting FI and supporting different methods of Revenue Recognition

(time-based, performance-based).

Sales and Distribution Financials CO

Accounts Receivables
Invoice
Order
Billing plan Unbilled Receivables
•periodic
• milestone

SD Contract
Delivery Deferred Revenues

Revenue
Billing plan
• periodic Recognition
• milestone
Process Revenues

Controlling Profitability Analysis

Objects from Sales and Distribution affecting Revenue Recognition
Solution Revenue Recognition
© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 4
SD Revenue recognition process

 SD Sales Order

 SD Sales Order item level :

– periodic billing plan
– milestone billing plan
– BOM‘s (with different level‘s for invoicing and delivery)

 SD Credit Memo request

 SD Debit Memo request

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 5

SD Revenue recognition category

• ‚A‘ time related revenue recognition ( new concept for revenue distribution )

• ‚B‘ service related revenue recognition ( incoming invoice and POD so far not supported from RA )

• ‚D‘ billing related, time related revenue recognition ( new concept in Revenue Accounting)

• ‚F‘ credit / debit memos with reference to predecessor

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 6

Operational Load and SD Revenue Recognition

 The operational load provides functionality for selecting sales orders with the select options :
– Company Code
– Sales Organization
– Distribution Channel
– Sales Document Type
– Sales Document
– Created on

 no difference between the migration of sales order items which are relevant for SD Revenue Recognition and
sales order items that or not relevant for SD revenue recognition. Both can be selected / migrated with the same
run ( Follow-on documents will be migrated as well )

The operational load creates Revenue Accounting Items and can be executed step wise per company code and migration
package
before the operational load VF47 can be used to check the SD Revenue Recognition database

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 7

transfer revenue accounting items created with operational load

 SD Revenue Recognition category is removed in sales orders / invoices

• For reference the values will be stored.

 set the sales order item relevant for Revenue Accounting as well as the follow-on documents.
• The revenue accounting relevance will also be applied for deliveries.

 SD Revenue Recognition revenue lines will be marked as migrated to Revenue Accounting

 after the transfer the SD Revenue Recognition data are available

 VF45 can be executed also for the migrated sales order items

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 8

Initial Load Timing

Transfer First open Initial Load

Date period Execution

IL

Documents created / Documents created / Integration Component is

posted here will be taken posted here will be
over as cumulated values assigned to their correct
No postings period
Postings as usual
active and transfers data
from relevant orders
Postings as usual
During Initial Load,
processed orders are
locked, to prevent that
follow-on documents get
lost

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 9

Adaptation of SD Revenue Recognition data

 revenues posted after the transfer date with SD Revenue Recognition relevance must be reversed

 invoices created after ther transfer date with SD Revenue Recogntion relevance must be reversed

 both values will be posted by the information created with the Revenue Accounting Items

© 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 10

Thank you
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf,Germany

Gabi Hoffmann
E: gabriele.hoffmann@sap.com

© 2015 SAP SE or an SAP affiliate company. All rights reserved.