Revenue Recognition _RR1

download Revenue Recognition _RR1

of 99

  • date post

    29-Nov-2014
  • Category

    Documents

  • view

    997
  • download

    6

Embed Size (px)

Transcript of Revenue Recognition _RR1

EHP3 for SAP ERP 6.0 June 2009 English

Revenue Recognition Processing (474)Building Block Configuration Guide

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

Evaluation notes were added to the output document. To get rid of these notes, please order your copy of ePrint 5.0 now.

SAP Best Practices

Revenue Recognition Processing (474): Configuration Guide

Copyright Copyright 2009 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP AG

Page 2 of 99

Evaluation notes were added to the output document. To get rid of these notes, please order your copy of ePrint 5.0 now.

SAP Best Practices

Revenue Recognition Processing (474): Configuration Guide

IconsIcon Meaning Caution Example Note Recommendation Syntax

Typographic ConventionsType Style Description Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation. Example text EXAMPLE TEXT Emphasized words or phrases in body text, titles of graphics and tables. Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE. Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools. on the keyboard, for example, function keys (such as F2) or the ENTER key. Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

Example text

EXAMPLE TEXT Keys

SAP AG

Page 3 of 99

Evaluation notes were added to the output document. To get rid of these notes, please order your copy of ePrint 5.0 now.

SAP Best Practices

Revenue Recognition Processing (474): Configuration Guide

ContentsRevenue Recognition Processing (474)....................................................................................... 8 1 2 Purpose ............................................................................................................................... 8 Preparation .......................................................................................................................... 8 2.1 3 Prerequisites .............................................................................................................. 8

Configuration........................................................................................................................ 9 3.1 3.1.1 Financials................................................................................................................... 9 Create New G/L Accounts ...................................................................................... 9 Chart of Accounts: Accounts .......................................................................... 9

3.1.1.1 3.1.2 3.2 3.2.1

Creating a Cost Element for GL Account .............................................................. 12 Logistics ................................................................................................................... 14 Assign Material Master G/L Accounts ................................................................... 14 Check Master Data Relevant For Account Assignment ................................. 14 New Rev. Acct Determination w/ new G/L .................................................... 15

3.2.1.1 3.2.1.2 3.2.2

Maintain Output Determination ............................................................................. 16 Output Condition Type: Sales Docs.............................................................. 16 Output Condition Type: Billing ...................................................................... 19 Output Determination Procedure: Billing ....................................................... 22 Output Determination Procedure: Sales Docs............................................... 23

3.2.2.1 3.2.2.2 3.2.2.3 3.2.2.4 3.2.3

Pricing.................................................................................................................. 24 Define Condition Tables ............................................................................... 24 Create Access Sequences ........................................................................... 25 Pricing Condition Type ................................................................................. 26 Pricing Procedure ........................................................................................ 28 Pricing Procedures: Customer and Document .............................................. 32

3.2.3.1 3.2.3.2 3.2.3.3 3.2.3.4 3.2.3.5 3.2.4

Billing Doc Type ................................................................................................... 34 Define Billing Doc Types .............................................................................. 34

3.2.4.1 3.2.5

SD Sales Document ............................................................................................. 36 Incompleteness Procedure ........................................................................... 36

3.2.5.1 3.2.6

Define Item Categories ......................................................................................... 37 Item Category Groups .................................................................................. 37 Item Categories............................................................................................ 38 Assign Partner Determination Procedure to Item Category ........................... 42 Assign Incompleteness Procedure to Item Categories .................................. 42 Delivery Item Categories .............................................................................. 43

3.2.6.1 3.2.6.2 3.2.6.3 3.2.6.4 3.2.6.5 3.2.7

Contracts.............................................................................................................. 44

SAP AG

Page 4 of 99

Evaluation notes were added to the output document. To get rid of these notes, please order your copy of ePrint 5.0 now.

SAP Best Practices 3.2.7.1 3.2.7.2 3.2.7.3 3.2.7.4 3.2.7.5 3.2.8

Revenue Recognition Processing (474): Configuration Guide

Date Determination Rule .............................................................................. 44 Cancellation Rule ......................................................................................... 45 Define Cancellation Procedure (Contract)..................................................... 46 Assign Cancellation Rule to Cancellation Procedure..................................... 46 Update Contract Profile ................................................................................ 47

Create Sales Document Type .......................................................