Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Sap CI EHP 6

2,532 views

Published on

SAP Convergent Invoicing

Published in: Software, Technology

Sap CI EHP 6

  1. 1. SAP Convergent Invoicing PUBLIC Document Version: 26.04.2012
  2. 2. (C) SAP AG 2 Copyright © Copyright 2012 SAP AG. All rights reserved. SAP Library document classification: PUBLIC 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. 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, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Oracle and Java are registered trademarks of Oracle and its affiliates. 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. Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.
  3. 3. (C) SAP AG 3 IOS is a registered trademark of Cisco Systems Inc. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc. INTERMEC is a registered trademark of Intermec Technologies Corporation. Wi-Fi is a registered trademark of Wi-Fi Alliance. Bluetooth is a registered trademark of Bluetooth SIG Inc. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, 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 other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company. Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. 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.
  4. 4. (C) SAP AG 4 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.
  5. 5. (C) SAP AG 5 Icons in Body Text Icon Meaning Caution Example Note Recommendation Syntax Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library. Typographic Conventions Type Style Description Example text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation. Example text Emphasized words or phrases in body text, graphic titles, and table titles. EXAMPLE TEXT Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. <Example text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.
  6. 6. (C) SAP AG 6 SAP Convergent Invoicing ..................................................................................................................15 Billing in Contract Accounts Receivable and Payable...................................................................15 Basic Concepts of Billing in Contract Accounts Receivable and Payable ...............................18 Billable Item ..............................................................................................................................19 Billable Item Class....................................................................................................................20 Billable Item Types...................................................................................................................20 Source Transaction ..................................................................................................................20 Source Transaction Type.........................................................................................................21 Billable Item Packages.............................................................................................................22 Interface Component................................................................................................................22 Basic Data for Billing ............................................................................................................23 Receivables/Payables (Reduced Interface) .......................................................................24 Receivables/Payables (Extended Interface).......................................................................25 Subitems ...............................................................................................................................25 External Reference of the Billable Item...............................................................................26 External Master Data Reference .........................................................................................27 Contract Reference ..............................................................................................................27 Billing Quantity......................................................................................................................27 Usage Period ........................................................................................................................27 Tax Jurisdiction Code...........................................................................................................28 External/Internal Account Assignment................................................................................28 Deferred Revenues - Time-Based.......................................................................................29 Deferred Revenues - Event-Based .....................................................................................29 Offsetting in Invoicing...........................................................................................................29 Basic Data for Payment Processing....................................................................................30 Payment Reference..............................................................................................................30 Card Payment.......................................................................................................................30 Payment Card Data..............................................................................................................31 Externally-Determined Tax Data .........................................................................................31 Assigning External/Internal Tax Codes...............................................................................31 External/Internal Tax Type for Other Taxes .......................................................................32 Tax Codes for Externally Determined Tax..........................................................................32 SAP Convergent Charging...................................................................................................33 CRM Order............................................................................................................................33 Basic Data for Telecommunications Taxes (US)................................................................34 External Provider Contract Reference ................................................................................34
  7. 7. (C) SAP AG 7 Prepaid ..................................................................................................................................35 Refill of Prepaid Quantities/Packages.................................................................................35 Refill of Credit on Prepaid Accounts ...................................................................................35 Billable Item Status...................................................................................................................36 Record Type .............................................................................................................................37 Billing Process ..........................................................................................................................38 Subprocess...............................................................................................................................39 Billing Type................................................................................................................................40 Type of Billing Document Item.................................................................................................41 Billing Target Date....................................................................................................................41 Billing Cycle ..............................................................................................................................41 Scheduling in Billing .................................................................................................................42 Parallel Processing Criteria in Billing ......................................................................................44 Generierung von Pflegedialogen für Verbrauchspositionen .....................................................45 Configuration of Billable Item Classes........................................................................................47 System Landscape...................................................................................................................49 Interfaces for Billable Item Classes.........................................................................................51 Customer Fields in Billable Item Classes ...............................................................................52 Interface Generation.................................................................................................................52 Generierung von Pflegedialogen für abrechenbare Positionen............................................54 Billable Item Management...........................................................................................................57 Processing Rules and Program Enhancements ....................................................................57 Transferring Raw Data into Billable Status.............................................................................59 Changing of Raw Data and Error Handling ............................................................................60 Data Storage.............................................................................................................................60 Displaying Billable Items..........................................................................................................61 Reversing Billable Items ..........................................................................................................62 Deleting Billed Items.................................................................................................................63 Billing Processes in Contract Accounts Receivable and Payable ............................................64 Flow of Billing Processes.........................................................................................................65 Flow Control for Billing .........................................................................................................66 Data Selection.......................................................................................................................67 Selection of Billable Items ................................................................................................67 Controlling the Selection ..................................................................................................69 Creation of Billing Units........................................................................................................69 Aggregation of Billable Items...............................................................................................70 Example 1..........................................................................................................................72
  8. 8. (C) SAP AG 8 Example 2..........................................................................................................................73 Example 3..........................................................................................................................74 Example 4..........................................................................................................................75 Example 5..........................................................................................................................77 Example 6..........................................................................................................................78 Billing Document.......................................................................................................................79 DDIC Structures and Layer Model ......................................................................................80 Billing Document Header..................................................................................................81 Billing Document Items.....................................................................................................82 Reversal Data....................................................................................................................83 Tax Items...........................................................................................................................83 Payment Data Items .........................................................................................................83 Source Items .....................................................................................................................84 Additional Items.................................................................................................................85 Entering the Document Number and Assigning the Document Type...............................85 Enhancements of the Billing Document..............................................................................87 Automatic Billing: Creating Billing Documents...........................................................................87 Creating Billing Documents in Dialog .........................................................................................88 Reversing a Billing Document in Dialog .....................................................................................90 Archiving Billing Documents........................................................................................................91 Enhancement Options in Billing ..................................................................................................91 Integration of Billing in Other Applications..................................................................................96 Billable Item Transfer ...............................................................................................................96 Account Assignments...........................................................................................................97 Transactions..........................................................................................................................97 Tax Codes for Internal Tax Determination..........................................................................98 Tax Codes for Externally Determined Tax..........................................................................98 Tax Type for Externally Determined Other Taxes..............................................................99 Integration with SAP Customer Relationship Management ................................................100 Integration with SAP Convergent Charging..........................................................................101 Updating Billable Items to SAP NetWeaver BW ..................................................................105 Invoicing in Contract Accounts Receivable and Payable............................................................106 Basic Terms of Invoicing in Contract Accounts Receivable and Payable..............................107 Invoicing Processes ...............................................................................................................108 Invoicing Functions.................................................................................................................109 Source Document Categories ...............................................................................................110 Source Document Types .......................................................................................................111
  9. 9. (C) SAP AG 9 Invoicing Types.......................................................................................................................111 Invoicing Categories...............................................................................................................112 Target Date for Invoicing........................................................................................................112 Billing Cycle ............................................................................................................................112 Scheduling for Invoicing.........................................................................................................113 The Term Invoice in Invoicing................................................................................................116 Invoicing Processes in Contract Accounts Receivable and Payable (FI-CA)........................117 Process Flow of Invoicing Processes ...................................................................................119 Processing Options ............................................................................................................120 Activating/Deactivating Invoicing Functions .....................................................................121 Examples: Activating/Deactivating Invoicing Functions...............................................122 Mandatory Invoicing Functions......................................................................................123 Activation/Deactivation of Invoicing Functions..............................................................124 Customer-Defined Invoicing Functions .........................................................................125 Data Selection.....................................................................................................................125 Invoicing Orders..............................................................................................................125 Selection Control.............................................................................................................127 Creating Invoicing Units .....................................................................................................128 Notes and Examples for Configuring Grouping Variants.............................................129 Event 2601 ......................................................................................................................132 Selection of Open Items.....................................................................................................133 Documents..............................................................................................................................134 Invoicing Documents..........................................................................................................134 DDIC Structures and Layer Model.................................................................................135 Invoicing Document Headers.....................................................................................137 Invoicing Document Items..........................................................................................137 Reference Table of Posting Documents....................................................................138 Invoicing and Reversal History Source Documents .................................................139 Reversal Data for Invoicing Document......................................................................139 Charges and Discounts for Invoicing Documents.....................................................139 History Records for Charges and Discounts in Invoicing Document.......................140 Offsetting Items of Invoicing Document.....................................................................141 Enhancements to the Invoicing Document ...................................................................143 Document Number Assignment and Document Type..................................................143 Posting Documents ............................................................................................................144 Document Number Assignment and Document Type..................................................145 Functions of Invoicing in Contract Accounts Receivable and Payable...............................146
  10. 10. (C) SAP AG 10 Invoicing of Billing Documents...........................................................................................146 Linking the Documents...................................................................................................147 Transactions....................................................................................................................147 Invoicing Items ................................................................................................................148 Business Partner Items ..................................................................................................149 Summarization Transaction........................................................................................150 Account Determination ...............................................................................................150 General Ledger Items.....................................................................................................151 Account Determination ...............................................................................................151 CO Account Assignment ............................................................................................152 Making System Settings for the CO-PA Account Assignment.............................152 Linking the Line Items.....................................................................................................153 Tax Calculation ...............................................................................................................154 Internal Tax Calculation..............................................................................................155 Determination of the Tax Code ..............................................................................155 Displaying Tax in Invoices......................................................................................156 Maintaining Keys for the Tax Display.................................................................156 Clearing Tax Differences ........................................................................................157 External Tax Calculation.............................................................................................158 External Tax Calculation with Internal Handling .......................................................159 Calculation of Telecommunications Tax....................................................................160 External Account Derivation...........................................................................................161 Supplementing Posting and Invoicing Items.................................................................162 Deferred Revenue Postings...........................................................................................162 Invoicing of SD Documents................................................................................................163 Invoicing of SD Documents with FI-CA Sample Document.........................................166 Invoicing of SD Documents Without FI-CA Sample Document...................................168 Invoicing SD Billing Documents (VBRK).......................................................................169 Reversal of SD Billing Documents (VBRK)...................................................................171 Invoicing Billing Requests ..............................................................................................171 Reversing Billing Document Requests..........................................................................172 Collective Invoicing.............................................................................................................173 Invoicing Individual Accounts.........................................................................................174 Invoicing Collective Bill Accounts ..................................................................................175 Invoicing List .......................................................................................................................176 Preselect Invoicing Document for Invoicing List...........................................................177 Create Invoicing List .......................................................................................................177
  11. 11. (C) SAP AG 11 Creation of Preliminary Invoices........................................................................................178 Additional Functions...........................................................................................................180 Surcharges and Discounts.............................................................................................181 Selecting Open Items for Additional Functions.........................................................181 Charges and Discounts ..............................................................................................182 Individual Charges and Discounts .............................................................................184 Debit Entry of Statistical Documents.............................................................................184 Calculating Interest on Open Items ...............................................................................185 Calculation of Interest on Cash Security Deposits .......................................................186 Releasing/Adjusting Cash Security Deposits................................................................186 Activating Line Items Posted Before Invoicing..............................................................187 Transferring Open Items.................................................................................................189 Automatic Account Maintenance ...................................................................................189 Manual Account Maintenance (Dialog Call)..................................................................190 Enhanced Automatic Account Maintenance.................................................................190 Enhanced Manual Account Maintenance......................................................................191 Reversal of Statistical Line Items...................................................................................192 Subitems..........................................................................................................................192 Setting Installment Plan to Due......................................................................................193 Writing Off........................................................................................................................193 Dunning ...........................................................................................................................194 Payment Forms...............................................................................................................194 Payment History..............................................................................................................195 Determination of the Payment Method..........................................................................195 Official Document Number Assignment........................................................................196 Rounding per Posting Document...................................................................................197 Rounding per Invoicing Document ................................................................................197 Creation of Additional (Customer-Specific/Industry-Specific) Documents..................198 Plausibility Checks for Source Documents ...................................................................199 Plausibility Checks for Invoicing Documents ................................................................200 Offsetting in Invoicing .....................................................................................................201 Activating Documents from Revenue Distribution........................................................204 Stamp Tax.......................................................................................................................205 Ad Hoc Invoicing .............................................................................................................205 Invoicing Additional Periodic Source Documents.........................................................206 Payment Reference ........................................................................................................207 Card Payment (Payment Method).................................................................................208
  12. 12. (C) SAP AG 12 Card Payment with Immediate Clearing........................................................................209 Balance Change of Prepaid Account ............................................................................209 Account Maintenance for Prepaid Account...................................................................210 Manual Account Maintenance for Prepaid Account .....................................................211 Determination of Due Date ................................................................................................211 Update.....................................................................................................................................212 Performing Invoicing ..................................................................................................................213 Reversing Invoicing Documents................................................................................................214 Making System Settings for Invoicing Reversal...................................................................215 Performing Invoicing Reversals.............................................................................................217 Reversing Billing Documents ....................................................................................................217 Making System Settings for Billing Reversal........................................................................219 Reversing Billing Documents.................................................................................................219 Special Features When Reversing Billing Documents from Billing in FI-CA......................220 Making System Settings for Reversing Billing Documents from Billing in FI-CA...............220 Reversing Billing for Documents from Billing in FI-CA ........................................................221 Special Considerations for Reversal of Billing Documents from External Systems..........221 Invoice Printing...........................................................................................................................222 Making System Settings for Invoice Printing........................................................................223 Program Enhancements in Events........................................................................................224 Displaying the Invoicing Document...........................................................................................225 Clarification in Invoicing .............................................................................................................226 Validation ................................................................................................................................227 Plausibility Checks for Source Documents.......................................................................228 Plausibility Checks for Invoicing Documents....................................................................229 Contract Account Check ....................................................................................................230 Error Messages...................................................................................................................231 Validation in the Invoicing Process....................................................................................231 Validation in the Billing Process ........................................................................................233 Validation in Invoice Order Analysis..................................................................................233 Validation in Billing Document Display..............................................................................234 Validation in Billing Document Transfer............................................................................234 Clarification Case ...................................................................................................................235 Data Model..........................................................................................................................235 Data Storage.......................................................................................................................236 Statuses and Processing Statuses of Clarification Cases...............................................238 Clarification Case Category...............................................................................................240
  13. 13. (C) SAP AG 13 Clarification Reason ...........................................................................................................241 Control Document...............................................................................................................241 Clarification Processing..........................................................................................................242 Clarification Processing in Dialog......................................................................................242 Automatic Clarification Processing....................................................................................245 Enhancement Options in Invoicing ...........................................................................................245 Program Enhancements............................................................................................................246 Archiving in Invoicing in Contract Accounts Receivable and Payable ...................................246 Integration of Invoicing in Other Applications...........................................................................246 Integration of Invoicing with Sales and Distribution (SD) ....................................................246 Integration of SAP Customer Relationship Management....................................................248 Making System Settings in the CRM System...................................................................249 Making Settings for the Account Determination in the ERP System ..............................249 Determination of Contract Account in ERP System.........................................................251 Notes for Mapping CRM Billing Documents in the ERP System ....................................251 Integration of Billing Systems ................................................................................................253 Transferring Billing Documents .........................................................................................253 Billing Document from Data Transfer ............................................................................254 Inbound Interface for Billing Documents .......................................................................256 BAPI BAPI_ISTBILLDOC_CREATEMULTIPLE.......................................................257 BAdI Methods for Inbound Interface ......................................................................260 Enhancement of Tables of Billing Document........................................................261 Enhancement of Tables of Billing Document ....................................................263 Billing Document Headers......................................................................................264 Billing Document Items ...........................................................................................267 Items Relevant for Posting and Printing.............................................................271 Internal Tax Determination..................................................................................272 Billing Document Tax Items....................................................................................274 Account Determination with External Tax Calculation......................................276 Account Determination with External Tax Calculation......................................277 Billing Document Additional Items .........................................................................277 Creating Billing Documents ....................................................................................278 Reversing Billing Documents with BAPI_ISTBILLDOC_CANCEL..............................279 Reversing Uninvoiced Billing Documents..................................................................280 Reversing Invoiced Billing Documents ......................................................................282 Calling BAdI Methods in the BAPI BAPI_ISTBILLDOC_CANCEL..........................284 Testing Reversals of Billing Documents....................................................................286
  14. 14. (C) SAP AG 14 Adjusting Billing Documents with BAPI_ISTBILLDOC_ADJUST................................287 Adjusting Uninvoiced Billing Documents...................................................................289 Adjusting Invoiced Billing Documents........................................................................290 Repeating Adjustment of Invoiced Billing Documents..............................................291 Reversing Adjustment Billing Documents .................................................................292 Testing Adjustments of Billing Documents................................................................293 ALE Interfaces.................................................................................................................294 Displaying Billing Documents.........................................................................................294 Update to SAP NetWeaver BW.............................................................................................295 DataSource 0FC_INVDOC_00..........................................................................................296 BW Extraction Orders.........................................................................................................297 Event 2710..........................................................................................................................298 Extracting Documents ........................................................................................................298 Extraction of Invoiced Billable Items .................................................................................300 Extraction Method for SAP NetWeaver BW (BW)............................................................300 Master Data in SAP Convergent Invoicing...................................................................................301 Product........................................................................................................................................303 Provider Contract .......................................................................................................................305 System Settings for Accessing Provider Contracts..............................................................307 Displaying and Changing Provider Contracts.......................................................................308 Authorization Objects for Provider Contracts .......................................................................311 Referencing of Provider Contracts........................................................................................311 Replication of Business Partners and Accounts ......................................................................312
  15. 15. (C) SAP AG 15 SAP Convergent Invoicing Together the Billing in Contract Accounts Receivable and Payable and Invoicing in Contract Accounts Receivable and Payable components form SAP Convergent Invoicing. Integration SAP Convergent Invoicing offers you the possibility of integrating the following applications: SAP Convergent Charging SAP Customer Relationship Management Contract Accounts Receivable and Payable This comprehensive integration enables you to implement the business process from the consumption of a service through pricing and billing right up to dispatch of the invoice to the customer. SAP Convergent Invoicing SAP ERP SAP Convergent Charging Consumption Mediation Rating Charging Billing Invoicing Contract A/R & A/P Consume to Cash Scenario Billing in Contract Accounts Receivable and Payable Billing in Contract Accounts Receivable and Payable (FI-CA) manages billable items and groups them together into billing documents, which you process further in Invoicing in Contract Accounts Receivable and Payable through to the creation of the invoice to the customer. Integration Billing in Contract Accounts Receivable and Payable processes one-off charges that you make in SAP Customer Relationship Management (CRM). You can integrate one-off charges from SAP CRM directly with Billing in Contract Accounts Receivable and Payable. In addition, Billing in Contract Accounts Receivable and Payable is integrated with SAP Convergent Charging.
  16. 16. (C) SAP AG 16 SAP Convergent Charging offers service industries the following functions for billing services (such as, telephone calls for telecommunications providers): Price modeling for services (transactions) Rating Charging Based on this integration, you can adopt billable items directly from SAP Convergent Charging to Billing in Contract Accounts Receivable and Payable. SAP Convergent Invoicing subsequently groups the priced services into invoices that you send to customers, and posts the invoice amounts in Contract Accounts Receivable and Payable. Example The following illustrates the integration of SAP Convergent Charging and SAP Convergent Invoicing using an example from the telecommunications industry. A customer has a cellular network contract with a telephone company; the telephone company bills the customer monthly for services (phone calls and SMS). 1. Consumption The customer sends an SMS with his cellular phone. He thereby consumes a service of the telephone provider. The telephone network transfers the SMS usage data, that means that the content of the SMS is sent to the recipient. The telephone provider records information about the SMS consumption, such as the date, the time and the telephone number, and passes on this data. 2. Mediation The telephone provider converts the payment-relevant information for the SMS consumption into a uniform format. 3. Rating SAP Convergent Charging determines a price for the SMS based on the rate in the cellular network contract; the rating process converts the service data into a monetary amount. 4. Charging SAP Convergent Charging, using the technical information for the SMS consumption (such as the telephone number), determines the invoice recipient and the customer account to be debited. 5. Billing Billing in Contract Accounts Receivable and Payable takes over the billing-relevant data for the SMS consumption and processes this data. Billing groups the data together with other existing SMS consumption of the customer and summarizes the data in a billing document. This means the system performs a preliminary aggregation of structured data records (billable items) according to technical and business criteria. Note
  17. 17. (C) SAP AG 17 Billing in Contract Accounts Receivable and Payable works without time zones. That means that Billing in Contract Accounts Receivable and Payable adopts the unconverted date and time from the external rating and charging system. End of the note. 6. Invoicing Based on the billing document and possibly additional source documents from other systems, Invoicing in Contract Accounts Payable and Receivable creates an invoice for the customer for the total monthly amount and posts this total amount to the contract account of the business partner as a receivable. 7. Contract Accounts Receivable and Payable You manage the receivable using the standard processes of Contract Accounts Receivable and Payable and collect the receivable from the customer (incoming payment, dunning). End of the example. Features Billing in Contract Accounts Receivable and Payable groups the billable items into billing documents. The document flow is as follows: 1. Transfer and storage of billable items from external systems (for example, SAP Convergent Charging) 2. Management of billable items and creation of billing documents using the processes of Billing in Contract Accounts Receivable and Payable. 3. Further processing of billing documents using the processes of Invoicing in Contract Accounts Receivable and Payable 4. Archiving of Billing Documents The processes shown in the figure can run asynchronously.
  18. 18. (C) SAP AG 18 Contract Account Billing Document Billable Items Billing Billed Items Billable Items Transfer Items Items Runtime 1 2 Archiving 3 Design time Billable Item Management Billing Document Flow of Billing Basic Concepts of Billing in Contract Accounts Receivable and Payable The following sections give you an overview of the concepts and parameters: That define and control billing processes With which you can design the billing process and adjust it to your needs In addition to the most important concepts, the following sections also explain the usage of the individual elements, the possibilities available when using them are explained on the basis of examples and the settings in the Implementation Guide are discussed.
  19. 19. (C) SAP AG 19 Design Time Contract Account Billing Process Billing Document Runtime Billing Process Invoicing Category Billing Type unitBilling Unit Selection Variant Billable Item Subprocess Grouping Variant Billing Process Billable Item The billable item represents an item that is to be billed. The creation of billable items is triggered by a business transaction or a business event. Structure The billable item class determines the technical properties of a billable item. A billable item can have various statuses. Billing considers only those billable items that have the status Billable. Once the items have been successfully processed in billing, the system assigns them the status Billed. The system manages the various statuses of billable items from a technical perspective by using different database tables. The system stores billable items in a separate database table for each status and billable item class. An exception to this rule is the status Billed. For this status, you can specify in Customizing how many tables you want to use and how these are used. In relation to the database tables used, the system also differentiates based on the following record types: Main items These represent the actual receivable or payable. Record types dependent on main items These represent attachments to the main items.
  20. 20. (C) SAP AG 20 The main items and the dependent record types use separate database tables. Billable Item Class The billable item class determines the technical properties of a billable item. These technical properties include: Database tables in which the system stores billable items depending on their status and their record type Function modules that accept billable items Function modules that save the billable items in the respective database tables Specific fields of billable items that you have added either through the selection of interface components or through customer fields Billable Item Types A billable item type (item type), in conjunction with the subprocess, defines the business significance of the billable item. Each item type is assigned to one or more subprocesses. Using the item type, you can influence the scope of the selection for billable items when you define the selection variant. You also have the option of using the item type to determine a grouping variant for aggregation. You define the billable item type in Customizing for Contract Accounts Receivable and Payable under Billing in Contract Accounts Receivable and Payable Basic Data Define Item Types . Source Transaction The source transaction is defined by the source transaction type and the source transaction ID. A source transaction represents a group of billable items that are related in a business sense. You define the business significance and processing rules for a source transaction with the source transaction type. The system processes billable items by source transaction, consisting of the source transaction ID and the type of source transaction. A source transaction can include billable items of different record types. Note
  21. 21. (C) SAP AG 21 SAP does not define the source transaction. At the same time, the system fully supports source transactions with regard to selection, navigation and transparency. The source transaction should comprise the items of a common business transaction. If you are using the integration between SAP Convergent Charging and SAP Convergent Invoicing, the ID of the set of priced items acts as the source transaction, since the billable items come from pricing. End of the note. Source Transaction Type The source transaction type defines the business significance of the source transaction ID both from the point of view of Billing in Contract Accounts Receivable and external systems. The source transaction type also defines the rules for interpreting the source transaction ID and the source transaction in follow-on processes. Together with the source transaction ID, the type of source transaction forms a source transaction. You define the source transaction type in Customizing for Contract Accounts Receivable and Payable under Integration Billing in Contract Accounts Receivable and Payable Basic Data Define Source Transaction Types . Here you can set the following processing rules for the source transaction type: Individual processing of billable items in a source transaction The standard is for the system to process all billable items of a source transaction together. Select this processing rule only if you want to process the individual items of your source transactions separately. Note The system groups logically-related billable items in packages in the inbound interface. As a rule, the system assigns billable items to an individual package. The composition of packages of billable items differs, however, when dependent record types are used (see Billable Item Packages). End of the note. Internal assignment of the source transaction ID by billable items If you make this setting, the system assigns the source transaction ID internally. Each billable item receives a unique source transaction ID (GUID). Note The system fully supports the source transaction in terms of selection and navigation in billing. Therefore, select this processing rule only if you are not able to assign the source transaction a useful external value. Note that internal assignment of the source transaction is only supported if you do not use dependent record types. Otherwise errors occur during the transfer of billable items.
  22. 22. (C) SAP AG 22 End of the note. Example As standard, SAP Convergent Charging transfers all priced items with the source transaction type CCCIT to SAP Convergent Invoicing. End of the example. Billable Item Packages Billing in Contract Accounts Receivable and Payable supports document-like administration and processing of logically-related billable items in packages. The system composes these packages during the transfer of billable items according to the following attributes of billable items: Source transaction Subprocess Master data Related payment and tax data (see Record Type) The system always regards and processes the items of a package as a unit. In particular, the system bills the items together or withdraws them from processing together. Individual items of a package are identified using sequence numbers. Note A package of billable items generally corresponds to a source transaction. In this case the package number is equivalent to the internal number of the source transaction. Note the recommendations in the Source Transaction section. End of the note. Example In an internet download you want to pay multiple items of a source transaction together with an externally authorized credit card item. During the transfer, the system groups the affected items into a common processing package (package of billable items). The individual items of a package cannot be processed separately in follow-on processes. Interface Component An interface component maps a business process from the billing point of view. It defines which business transactions are represented by a class of billable items (such as deferred revenues and clearance of down payments). Interface components constitute the interface for a class of billable items.
  23. 23. (C) SAP AG 23 SAP supplies preconfigured interface components that can be used immediately. These include basic components required for a record type as well as additional optional components that you can add to a class. Note You cannot use customer-defined interface components. End of the note. You can find an overview of available interface components in Customizing for Contract Accounts Receivable and Payable under Integration Billing in Contract Accounts Receivable and Payable Billable Item Classes Define Interface Components . When you define billable item classes, you assign interface components to the classes. On the basis of this assignment, the system generates interfaces in which it automatically integrates the fields of the interface component. An interface, in turn, comprises function modules that transfer the data as well as tables in which the system stores the data. Note Some interface components correspond to invoicing functions in Billing in Contract Accounts Receivable and Payable or augment them. End of the note. Structure Initially, an interface component is comprised of such information as an interface name and a description. It can also have a data element that documents the interface. Going further, an interface component is also defined by the following settings: The assigned structures Structures are assigned based on the record type and the status. You can also define that entries that do not belong to the record type of the main item are only active conditionally. Prerequisite components This setting indicates which interface components function as prerequisites. The basic components are not listed here; these are defined separately. Program Enhancements These are function modules that the system calls at the defined times. The function modules are used for enrichment and checks. Basic Data for Billing
  24. 24. (C) SAP AG 24 The interface component Basic Data for Billing is the basis for billable items. It contains the most important selection and administrative data of the billable item. This interface component is a basic component that is active in every class of billable items. It is relevant is for the main items record type. If this interface component is active, you can select additional customer fields for main items when configuring the classes of billable items. For more information, see Customer Fields in Billable Item Classes. Note Note that in the standard billing scenario, you can only process billable items that contain, in addition to the basic data, account assignment information as part of the structure of the billing document. You can add the corresponding fields using, for example, the interface component Receivables/Payables (Reduced Interface). End of the note. Receivables/Payables (Reduced Interface) The interface component Receivables/Payables (Reduced Interface) provides the fields in the interface for the transfer of billable items with which you derive the principal account assignment information for the structure of a billing document in invoicing. When the billable items are transferred from an external system, there is no prerequisite that they have the formats and values of the account assignment attributes known in the SAP system. Activate this interface component if account assignment information required for posting is unknown to the sending system and you want to derive the information from the externally-set attributes of the billable items. The system derives the account assignments from the settings in Customizing for Contract Accounts Receivable and Payable under Integration Billing in Contract Accounts Receivable and Payable Billable Item Transfer Account Assignment Derivation in the following activities: Define Account Assignments Define Main Transactions and Subtransactions (for billable items that do not have account assignment to a product) Define Main and Subtransactions for Items with Product Account Assignment (for billable items that have account assignment to a product) Additionally, in posting area 8123 you can derive the tax code from an external tax code (activity Define Tax Code for Internal Tax Determination).
  25. 25. (C) SAP AG 25 This interface component corresponds to interface component Receivables/Payables (Extended Interface); however, the interface is restricted to the attributes of billable items required for the derivation of account assignment information. Receivables/Payables (Extended Interface) The interface component Receivables/Payables (Extended Interface) provides the fields in the interface for the transfer of billable items with which you transfer the principal account assignment information for the structure of a billing document in invoicing. Activate this interface component if you can already transfer or derive the account assignment information at the interface and the corresponding fields have not already been provided by other interface components. If the billable items do not contain account assignment information, you must ensure that the system interprets the items correctly in the billing program (if necessary in the customer implementation of an event). You do this either by deriving the account assignments in billing or applying other functions. When the billable items are transferred from an external system, there is no prerequisite that they have the formats and values of the account assignment attributes known in the SAP system. You can assign external account assignments to internal account assignments using the interface component External/Internal Account Assignment. Interface component Assigning External/Internal Tax Codes is also available. Alternatively, you can use interface component Receivables/Payables (Reduced Interface), in which the aforementioned derivations are executed automatically. Subitems The interface components Subitems of Billable Items and Subitems of Billed Items cause the system to take subitems into account in its administration of the statuses billable and billed for main items. These interface components are optional; they are relevant for the main items record type.
  26. 26. (C) SAP AG 26 Main Items Subitems Linked via BITPACKCNO_IT Relationship Between Main and Subitems If this interface component is active, you can define which fields remain in the main item and which in the subitem when configuring the classes of billable items in Customizing. You make this setting in Customizing for Contract Accounts Receivable and Payable under Integration Billing in Contract Accounts Receivable and Payable Billable Item Classes Maintain Billable Item Classes with the Optimize button. Example A rating system collects the main items for a particular customer throughout the day. At a particular point in time, the system transfers the data to Billing in Contract Accounts Receivable and Payable. The values of the main items differ in only a few fields. To optimize performance and data retention, you summarize the matching values in a main record and store the divergent values separately in a supplementary table. To do this, activate the interface component Subitems of Billable Items or Subitems of Billed Items. If one of the interface components is active for a class, you can use the Optimize button when configuring the classes of billable items in Customizing to define which fields are assigned to the subitems – the ones for which you expect deviating values. End of the example. External Reference of the Billable Item
  27. 27. (C) SAP AG 27 The interface component External Reference of the Billable Item provides the external reference of the billable item in the billable items structure. The external reference of the billable item is found in the raw data of all record types by default. The field is used for the unique identification of a billable item in the inbound interface. If the external reference is to be available within billing or after billing, you can ensure this using the External Reference of the Billable Item. External Master Data Reference The interface component External Master Data Reference is used in the derivation of master data from external master data references. It contains the contract account number and the business partner number in the external system. Activate this interface component only if you want to transfer billable items that have no contract account or business partner data and for which you want to derive the master data from the external references. Contract Reference The interface component Contract Reference contains the contract reference. You use this interface component in the classes of billable items whose items you want to be able to explicitly link to a contract. Billing Quantity The interface component Billing Quantity makes it possible to store the billing quantity in the billable item. Usage Period You use the interface component Usage Period in your billable item classes in order to specify a usage period based on dates and times. The interface component contains the following fields: Date From
  28. 28. (C) SAP AG 28 Time From Date To Time To The interface component Basic Data for Billing already contains the fields Date From and Date To. If you also need to be able to enter times, use the interface component Usage Period in addition. Example The usage period encompasses the time from the start to the end of a telephone call. End of the example. Tax Jurisdiction Code The interface component Tax Jurisdiction Code contains the tax jurisdiction code. You use this interface component in the billable item classes to transfer the tax jurisdiction (for example for tax determination in the US). The interface component Receivables/Payables (Reduced Interface) is the prerequisite for the interface component Tax Jurisdiction Code. External/Internal Account Assignment The interface component External/Internal Account Assignment is used for the derivation of internal account assignments of billable items from the account assignment information from the external system. When the billable items are transferred from an external system, there is no prerequisite that they have the formats and values of the account assignment attributes known in the SAP system. Instead, you can transfer the account assignments of the external system to the interface in the predefined fields (external item IDs) and use them to derive the account assignments for the billable items to be used in the SAP system. The interface component External/Internal Account Assignment contains the external item IDs for the derivation of the following account assignments of the billable items: Company code Division Business area
  29. 29. (C) SAP AG 29 Segment Main transaction Subtransaction The system derives the account assignments using the settings in Customizing for Contract Accounts Receivable and Payable under Integration Billing in Contract Accounts Receivable and Payable Billable Item Transfer Account Assignment Derivation Define Account Assignments in the following activities: Define Account Assignments Define Main Transactions and Subtransactions (for billable items that do not have account assignment to a product) Define Main and Subtransactions for Items with Product Account Assignment (for billable items that have account assignment to a product) Function module FKK_BIX_IFCOMP_ACC_ASSG_MAP_30 executes the required steps. The interface component External/Internal Account Assignment requires that the structure of the billable item contains the aforementioned account assignment fields. These are provided, for example, by the interface component Receivables/Payables (Reduced Interface). Deferred Revenues - Time-Based The interface component Deferred Revenues - Time-Based provides the fields in the interface for the transfer of billable items that you use to transfer the application and control data to invoicing that is required for the invoicing function Deferred Revenues. Activate this interface component only if you use the invoicing function Deferred Revenues. Deferred Revenues - Event-Based The interface component Deferred Revenues - Event-Based provides the fields in the interface for the transfer of billable items that you use to transfer the application and tax data to invoicing that is required for the invoicing function Event-Based Deferred Revenues. Activate this interface component only if you use the invoicing function Event-Based Deferred Revenues. Offsetting in Invoicing
  30. 30. (C) SAP AG 30 The interface component Offsetting in Invoicing provides the fields in the interface for the transfer of billable items that you use to transfer the application and control data to invoicing that is required for the invoicing function Offsetting in Invoicing. Activate this interface component only if you use the invoicing function Offsetting in Invoicing. Basic Data for Payment Processing The interface component Basic Data for Payment Processing is a basic component. If the interface component is active: The system adds the payment data items record type to a class of billable items You can add customer fields to the record type payment data items when configuring classes of billable items in Customizing For more information, see Customer Fields in Billable Item Classes. Payment Reference The interface component Payment Reference provides the fields for generation of the payment reference in invoicing in the interface for the transfer of billable items. The payment reference is used in the payment of posting items derived from the billable items. Card Payment The interface component Card Payment provides the fields in the interface for the transfer of billable items that are used to transfer the card data for payment processing of the receivables that result from billable items. The invoicing functions Card Payment (Payment Method) and Card Payment with Immediate Clearing process the card data. Activate this interface component only if you use one of these invoicing functions.
  31. 31. (C) SAP AG 31 Payment Card Data The interface component Payment Card Data augments the interface component Card Payment. This interface component provides the fields in the interface for the transfer of billable items with which you transfer detail information (in particular authorization data) about payment cards. The system does not store the card data details transferred through the interface directly in the billable items but in a card data supplement (table DFKK_PCARD). The system stores the key for the card data supplement as a reference to the card data details in the billable item. Externally-Determined Tax Data The interface component Externally-Determined Tax Data is a basic component. If the interface component is active: The system adds the tax items record type to a class of billable items You can add customer fields for the record type tax items when configuring classes of billable items in Customizing For more information, see Customer Fields in Billable Item Classes. Assigning External/Internal Tax Codes The interface component Assigning External/Internal Tax Codes is used to derive the internal tax code or tax determination code from an external tax code for billable items with the tax determination type Internal Tax Calculation (01). When the billable items are transferred from an external system, there is no prerequisite that they have the values known in the SAP system for the tax account assignment. You can transfer the tax code from the external system using the External Tax Code field in the interface. The interface component Assigning External/Internal Tax Codes contains the field for the external tax code as the basis for deriving the tax code or tax determination code. The system performs the derivation based on the settings in Customizing for Contract Accounts Receivable and Payable under Integration Billing in Contract Accounts Receivable and Payable Billable Item Transfer Account Assignment Derivation Define Tax Code for Internal Tax Determination .
  32. 32. (C) SAP AG 32 External/Internal Tax Type for Other Taxes The interface component External/Internal Tax Type for Other Taxes is used to transfer billable items with the tax determination type External Tax Calculation (Other Tax) (02). With external tax handling the tax is not calculated in Contract Accounts Receivable and Payable but in the external billing system. The external system transfers the billable items with the complete tax items to billing in the SAP system, which transfers the items to Contract Accounts Receivable and Payable using invoicing. The billing document created by invoicing indicates the items as tax items. Contract Accounts Receivable and Payable posts and treats the items not as tax items but as revenue items. However, generally the values and the format of the tax account assignments sent by the external system do not match the account assignments for other taxes in Contract Accounts Receivable and Payable. It is necessary to derive the internal codes from the external codes. The interface component External/Internal Tax Type for Other Taxes contains fields through which you can transfer the values for external tax codes and from which the system then derives the codes for posting other taxes in the SAP system. The system performs the derivation based on the settings in Customizing for Contract Accounts Receivable and Payable under Integration Billing in Contract Accounts Receivable and Payable Billable Item Transfer Account Assignment Derivation Define Tax Type for Other Taxes Determined Externally . Activate this interface component only if you want to transfer billable items for which the tax has already been determined externally and which you post as other taxes in the SAP system. Tax Codes for Externally Determined Tax The interface component Tax Codes for Externally Determined Tax is used to transfer billable items with the tax determination type External Tax Calculation with Internal Handling (03). The external system transfers billable items to Accounting in the SAP system that already contain all tax-relevant information (including tax amounts). Accounting in the SAP system forwards these items to Contract Accounts Receivable and Payable through Invoicing. The billing document created by Invoicing indicates these items as tax items. Contract Accounts Receivable and Payable posts them as tax items. If the external tax codes do not correspond with the internal IDs of the SAP system, you must derive the internal codes from the external ones. The interface component External Tax Calculation with Internal Handling contains fields through which you transfer the values for external tax codes and from which the system then derives the codes for posting taxes in the SAP system. The system performs the derivation based on the settings in Customizing for Contract Accounts Receivable and Payable under Integration Billing in Contract Accounts Receivable and Payable Billable Item Transfer Account Assignment Derivation Define Tax Code for Tax Determined Externally . Activate this interface only if you want to transfer billable items with previously determined tax amounts.
  33. 33. (C) SAP AG 33 SAP Convergent Charging The interface component SAP Convergent Charging is used for the transfer of billable items from SAP Convergent Charging. Note If you activate the SAP Convergent Charging interface component, the system automatically activates the interface component Receivables/Payables (Reduced Interface). End of the note. CRM Order The interface component CRM Order derives the internal account assignments of the billable items from the account assignment information from Customer Relationship Management (CRM). When the billable items are transferred from CRM, there is no prerequisite that they have the formats and values of the account assignment attributes known in the SAP system. Instead, you can transfer the account assignments of the external system to the interface in the defined (by SAP CRM) fields and use them to derive the account assignments for the billable items to be used in the SAP system. The interface component CRM Order contains the external values for the derivation of the following account assignments of the billable items: Billing subprocess Billable item class Type of the billable items Company code Division Business area Segment Main transaction Subtransaction The system performs the derivation on the basis of the settings in the activities under Transfer of One-Off Charges from Customer Relationship Management in Customizing for Contract Accounts Receivable and Payable under Integration Billing in Contract Accounts Receivable and Payable Billable Item Transfer . The interface component CRM Order requires that the structure of the billable item contains the aforementioned account assignment fields. These are provided, for example, by the interface
  34. 34. (C) SAP AG 34 component Receivables/Payables (Reduced Interface). This interface component also requires interface components External Reference of the Billable Item and Contract Reference. Basic Data for Telecommunications Taxes (US) The interface component Basic Data for Telecommunications Taxes (US) is an optional interface component. It is relevant is for the main items record type. It contains specifications for the calculation of telecommunications taxes in the US and Canada. Select the interface component Basic Data for Telecommunications Taxes (US) only if you need to calculate telecommunications taxes for billable items, as is the case for telephone connections and text messages to the US or Canada. External Provider Contract Reference The interface component External Provider Contract Reference contains a reference to a provider contract. You use the interface component External Provider Contract Reference in billable item classes with items that relate to contract items of a provider contract. When the billable items are transferred from an external system, there is no prerequisite that they have the formats and values of the account assignment attributes known in the SAP system. Instead, the system adopts the following account assignment attributes from the provider contract item: Company code Division Business area Segment Profit center The system derives the main transaction and subtransaction from the settings in Customizing for Contract Accounts Receivable and Payable under Integration Billing in Contract Accounts Receivable and Payable Billable Item Transfer Account Assignment Derivation Define Main and Subtransactions for Items with Product Account Assignment . The interface component requires that the structure of the billable item contains the account assignment fields mentioned above. These are provided, for example, by the interface component Receivables/Payables (Reduced Interface).
  35. 35. (C) SAP AG 35 Prepaid The interface component Prepaid makes the basic fields available for billable items that are needed for processing actions on prepaid accounts. The interface component Prepaid is mandatory for processing billable items that relate to prepaid usage and refills. For refill items, the interface component Refill of Credit on Prepaid Accounts is also required. This interface component can process only those billable items that fulfill these prerequisites: The Prepaid (PREPAID) field contains the value X. The Prepaid Account (PPACC) field contains a valid prepaid account. Prepaid usages are processed in invoicing by the invoicing function Invoicing of Billing Documents. This processing is very much similar to the processing of postpaid usages. Prepaid refills are processed in invoicing by the invoicing function Balance Change of Prepaid Account. Refill of Prepaid Quantities/Packages The interface component Refill of Prepaid Quantities/Packages makes the necessary fields for refilling quantities or packages on prepaid accounts available on the interface for billable items. The interface component Refill of Prepaid Quantities/Packages is optional for the processing of prepaid refill items. The interface component Refill of Credit on Prepaid Accounts is a prerequisite for this interface component. A refill package can consist of up to three components, also called refillable units. The refill of a prepaid account using a refill package is transferred to the interface by a single item with the status Raw. In the REFPK field, this item contains the refill package, and transfers the refillable units and their number in the following field pairs: TUSE1 CNTU1 (Requested Number for Component 1) TUSE2 CNTU2 (Requested Number for Component 2) TUSE3 CNTU3 (Requested Number for Component 3) When the billable items are created, the interface component generates a separate item for each component. In this item, the refillable unit and the related number are transferred to the fields Refillable Units (TUSEX) and Requested Number (CNTUX). Refill of Credit on Prepaid Accounts
  36. 36. (C) SAP AG 36 The interface component Refill of Credit on Prepaid Accounts makes the necessary fields for refilling credit on prepaid accounts available on the interface for billable items. The interface component is mandatory for processing billable items for prepaid refills. The interface component Prepaid is a prerequisite for this interface. The interface component can process only those billable items that fulfill these prerequisites: The Balance Change (PPREFILL) field contains the value X. The Prepaid (PREPAID) field contains the value X. The Prepaid Account (PPACC) field contains a valid prepaid account. Prepaid refills are processed in invoicing by the invoicing function Balance Change of Prepaid Account. Billable Item Status A billable item has one of the following statuses: 0 (Raw) 1 (Raw excepted) 2 (Billable) 3 (Billable excepted) 4 (Billed)
  37. 37. (C) SAP AG 37 Billable Raw Billable Excepted Raw Excepted BilledBilled … Billed Interaction Between Billable Item Statuses Upon transfer, billable items in Contract Accounts Receivable and Payable get the status billable. If the system cannot identify master data, billable items receive the status Raw. You can also influence this behavior using upload rules (see Upload Rules and Program Enhancements). The billing process changes billable items from the status billable to the status billed. The system uses separate tables for each status. For more information, see Transferring Raw Data into Billable Status and Changing Billable Items and Error Handling. Record Type The record type groups characteristics of billable items which are related in a business sense. Structure The system administers data of the following record types separately in the database and the main memory: IT (main items) PY (payment data items) TX (tax items)
  38. 38. (C) SAP AG 38 Billable items of the record type IT are required and provide the fundamental data for billing. The other record types are dependent record types that the system cannot bill without existing IT records (such as credit card supplements). The system uses separate tables for each record type. Main Items Payment Data Items Tax Items Linked via PY_GROUP Linked via TAX_GROUP Linking of Main Items with Dependent Record Types Billing Process The billing process is the umbrella term for the execution of billing in Contract Accounts Payable and Receivable according to defined rules. These rules are defined by parameters that you use to control the billing process. When defining a billing process, you specify which billable items the system selects for billing. You can also influence the grouping and the aggregation level of the billable items. This flexibility adds to the flexibility of using modification-free enhancements by means of includes and events. Note In the following situations there is a link to billing processes: Billing processes serve as selection parameters of the mass activity for billing in Contract Accounts Receivable and Payable.
  39. 39. (C) SAP AG 39 They define number ranges for billing documents that are dependent on the billing processes. End of the note. You create new billing processes in Customizing for Contract Accounts Receivable and Payable under Integration Billing in Contract Accounts Receivable and Payable Billing Processes Define Billing Processes . Structure A billing process specifies which subprocesses it supports. At least one subprocess is mandatory. You can control the following at the level of the subprocess: Selection of items to be billed You have to assign a selection variant to each subprocess. This selection variant controls the selection of the items to be billed in billing for a certain contract account. Grouping of billable items into billing units To group billable items in invoicing into a common invoice, you can assign each subprocess a separate grouping variant that the system uses to automatically group together billable items. Using the billing types assigned to it, the billing process also classifies the billing documents from a business perspective. In billing, you can use the billing process to control the aggregation of billable items using an additional grouping variant. Subprocess The subprocess in combination with the item type represents the business significance of a billable item. Each subprocess is assigned to one or more billable item classes. The subprocess is an independent processing branch within the billing process with regard to selection and the grouping of billable items and their processing for a billing document. The system assigns the billable items to one of the subprocesses as soon as they are created. You cannot process these billable items together with the billable items of other subprocesses in a common billing document. The following control options exist: Selection of the billing worklist For each subprocess you can define which billable item classes the system is to select and process. You can further refine the selection by specifying per class the type and source transaction type of the billable item. Grouping of the billable items in billing units
  40. 40. (C) SAP AG 40 You can assign to each subprocess an individual grouping variant for automatic summarization of billable items for which the system creates a common invoice. Definition of the billing type You create new subprocesses in Customizing for Contract Accounts Receivable and Payable under Integration Billing in Contract Accounts Receivable and Payable Basic Data Define Billing Subprocesses . Example You have two distinct groups of billable items (for example from two different industries). The system should do the following with these items: Bill them at different intervals Select them according to different considerations Group them into billing units and process them in billing documents You achieve this by assigning the groups their own subprocesses. You can then process the two subprocesses together or in separate billing processes. If business-related dependencies exist between the subprocesses, such as with music downloads and royalties, it may be useful to assign both subprocesses to the same billing process. A business dependency in the music download example may occur if, for example, there is a requirement that royalties only be billed once the corresponding music downloads (payables) have been billed. Billing Type The billing type characterizes the composition of billing units and classifies billing documents. You can use the billing type optionally instead of the determination of the document type and the source document type of the billing document. The billing type is also available in events for billing (for example, in the events 8120, 8125, and 8130). You create new billing types in Customizing for Contract Accounts Receivable and Payable under Integration Billing in Contract Accounts Receivable and Payable Billing Processes Define Billing Types . Example You want to distinguish between billing documents that belong to periodic billing and billing documents that arise due to the contract being ended (final billing documents). You make this distinction using the billing type. For final billing documents, you want to add additional informational items that are not relevant for posting. At event 8125, you use the billing type to control the creation of the additional billing document items.
  41. 41. (C) SAP AG 41 Type of Billing Document Item The type of billing document item (ITEMTYPE) describes the business significance of the document items of a billing document. The system derives the type of billing document item from the subprocess and the item type of the billable item linked with the document item. As a result, the business significance of the billable item is represented by the item type of the billing document item, and is transferred, for example, to invoicing and invoice printing. You assign the type of billing document item to the attributes subprocess and item type of billable item in Customizing for Contract Accounts Receivable and Payable under Integration Billing in Contract Accounts Receivable and Payable Billing Processes Assign Billing Item Types . Billing Target Date The target date for billing is the earliest possible billing time for a billable item. The billing target date defines that a billable item may not be billed until the specified date has been reached (in relation to the billing date). Only in expert mode for billing can you bill billable items before they reach the target date. The system determines the target date for billing using scheduling. You can specify in Customizing the date that you want to serve as the baseline date for the determination. Based on the baseline date, the system determines the target date for billing using the determination rules that you also define in Customizing. You define both the baseline date and the calculation rules in Customizing for Contract Accounts Receivable and Payable under Integration Billing in Contract Accounts Receivable and Payable Basic Data Scheduling Define Rules for Determining the Billing Date . Example You specify the baseline date as the creation date of the billable item and always bill the billable items on a fixed day. End of the example. Billing Cycle The billing cycle is used to specify billing periods. The billing cycle specifies the period end and the length of a billing period.
  42. 42. (C) SAP AG 42 The actual billing time span can differ from the billing period. Example You do not transfer billable items from the month of January into the system until February. The invoice for the month of February, therefore, has a billing time span that goes back into January, whereas the billing period consists only of the month of February. End of the example. You define the billing cycle in Customizing for Contract Accounts Receivable and Payable under Integration Billing in Contract Accounts Receivable and Payable Basic Data Scheduling Define Billing Cycle or under Integration Invoicing in Contract Accounts Receivable and Payable Invoicing Invoicing Processes Scheduling for Invoicing Define Billing Cycle . Then you enter the technical key of the billing cycle in the contract accounts or in the provider contract items of your business partners. Depending on the configuration of the billing cycle, you can overwrite the period end date at the level of the contract account. You can use the billing cycle in scheduling for determining the target date of billing or the target date of invoicing. Scheduling in Billing Using scheduling, the system determines the target date for billing, that is, the earliest possible date for billing of billable items (see Target Date for Billing). Features Scheduling helps both to technically distribute the load on the system, as well as allowing you to specify a customer-specific billing date. You can use the billing cycle to influence the determination of the target date of billing and the target date of invoicing. If a billing cycle is entered in the contract account, then it applies (if no further changes are made) to both billing and invoicing. You can enter a different billing cycle in the provider contract items than in the contract account. As a result, billing could take place on a weekly basis and invoicing take place every two weeks. If you do not need this separate control, then it is sufficient to enter the billing cycle either in the contract account or in the provider contract. If you do not want to use cycle-based billing or invoicing for certain billable items or source documents, you can define different rules for these objects. Regardless of whether or not you use billing cycles, you can influence the billing date and invoicing date as follows: You can specify grace days, such as two days after the creation of the invoicing order. You can define periods, such as every 14 days. You can configure special factory calendars.
  43. 43. (C) SAP AG 43 If you want special dates to be valid for certain contract accounts, you can define different rules for them that are dependent on the selection characteristic for scheduling. Note The standard system determines the billing date and the invoicing date cycle-based at the end of the period – as long as a billing cycle is entered in the contract account or provider contract and no different rules for determining the times of execution are entered in the system. In all other cases, the rules for determining the target date of billing and the target date of invoicing specify the times when billing or invoicing is executed. End of the note. Activities You make the system settings for scheduling in Billing in Contract Accounts Receivable and Payable in Customizing for Contract Accounts Receivable and Payable under Integration Billing in Contract Accounts Receivable and Payable Basic Data Scheduling as follows: 1. In the activity Define Selection Characteristic of Scheduling, you have the option of entering an indicator for finer control of scheduling. Using the selection characteristic, you can influence the determination of the target date of billing and invoicing at the level of the contract account. 2. If you want to use billing cycles in scheduling, in the activity Define Billing Cycle, define a billing cycle and configure the controls for determining the periodicity and for determining the billing period. You also specify here if these properties can be overwritten in the contract account. 3. In the activity Enter Rules for Determining the Billing Date, you define the rules for determining the target date for billing. In addition, you specify if the target date of billing is synchronized with the billing cycle (in relation to either the beginning or the end of the billing period). 4. In the activity Assign Rules for Determining the Billing Date, you define the derivation of the rule for determining the billing date. Example Your customers receive an invoice for each contract (provider contract). The date of the invoice creation is determined from the date the contract was signed. If the customer has several contracts, then payment is to be made using a common contract account. To ensure that all billing-relevant data is in the system at the time of billing, you define a waiting period for billing of 2 days after the end of the billing period. Invoicing is to take place directly after billing. 1. You define the billing cycle ZMC1, which uses the validity start of the provider contract item as the day of the period end. As the frequency, you use M1 (monthly). 2. You assign billing cycle ZMC1 to the items of the provider contract. 3. You define the rule Z001 for determining the billing date. The date of creation of the billable item should serve as the baseline date for the calculation. 4. In addition, the rule should be cycle-based in regard to the period end. In the calculation rules, you enter 2 additional days.
  44. 44. (C) SAP AG 44 A customer signed a contract on November 5. For a billable item created on December 17, the following dates result based on the system configuration: Baseline date for determining the target date of billing is December 17. Billing is cycle-based in relation to the period end. The system determines the end of the billing period in which December 17 lies. The period determined in this way extends from December 6 to January 5 of the following year. (The period end corresponds to the date the contract was signed.) The system adjusts the baseline date for determining the target date to the period end that was determined. That means that the baseline date is January 5. The calculation rule Z001 adds two additional days to the baseline date. The target date for billing the billable items from December 17 is therefore January 7 of the following year. Parallel Processing Criteria in Billing Features For mass processing of billable items in processes that run in parallel, the system divides the data into multiple billing packages. This ensures that each parallel process can exclusively process one or more billing packages. The system already divides billable items into individual billing packages when the billable item is created, by deriving an attribute (KEYPP) in the billable item for the billing package. For parallel billing, the system divides the total of the billable items into a maximum of 1000 billing packages. In the standard system, the system assigns all billable items of a business partner to a single billing package. The items are thereby processed by a single process. By specifying additional parallel processing criteria, you can distribute these items to several billing packages. You can thereby benefit from parallel billing of business partners with a high volume of billable items in multiple processes running in parallel. You can use any fields of the billable item as parallel processing criteria. Recommendation Use only those criteria as parallel processing criteria that, owing to their business significance, should lead to the processing of billable items in different billing documents. Examples of these criteria include the contract account, contract, currency and billing period. End of the recommendation. Example If you use the contract account as a parallel processing criterion, then different billing processes running in parallel process the different contract accounts of a business partner. If you use the source transaction as a parallel processing criterion, then different billing processes running in parallel process billable items with different source transactions. End of the example.

×