1. U90 - B2B Master Agreement with Counter Sharing Process Diagram

2. ©2014 SAP AG. All rights reserved.2 U90 - B2B Master Agreement with Counter Sharing (1/4) Sales Employee SAP Customer Relationship Management System SAP ERP Create Master Agreement A 1 Create Sharing Order A Create Sharing Contract System SAP Convergent Charging Submit Sharing Order A Create Sharing Contract Create Sharing Contract (Common Object Layer) 2 3 Next Page

3. ©2014 SAP AG. All rights reserved.3 Create Provider Contract with Reference to Master Agreement U90 - B2B Master Agreement with Counter Sharing (2/4) Sales Employee SAP Customer Relationship Management Billing Agent SAP ERP System SAP Convergent Charging Previous Page Create Discount Agreements B Create Invoice Agreement B Create Invoicing List Agreement B Create Provider Order with Reference to Master Agreement A Create Provider Contract Next Page A 2 3 Next Page B Create Partner/Product Groups B

4. ©2014 SAP AG. All rights reserved.4 U90 - B2B Master Agreement with Counter Sharing (3/4) Billing Agent SAP ERP System SAP Convergent Charging Previous Page A Update Billable Items 4 Sales Employee SAP Customer Relationship Management Create Filter for Master Agreement for Counter Sharing Scenario D Create Invoice Agreement for Counter Sharing B Next Page Receive a Chargeable Item Identify a Charge Plan Execute the Charge Plan Generate Charged Items Send the Charged Items Activate a Recurring Charge Previous Page B Execute Billing for Usage 1 Execute Billing for Discount 1 Execute Invoicing 2

5. ©2014 SAP AG. All rights reserved.5 U90 - B2B Master Agreement with Counter Sharing (4/4) Billing Agent SAP ERP System SAP Convergent Charging Previous Page Sales Employee SAP Customer Relationship Management Create Invoicing List C (U93) Preliminary Invoice

6. ©2014 SAP AG. All rights reserved.6 Icon Legend (1/2) IconName CRM UI: CRM_UI -> Provider Contr.Mngmt -> Provider Master Agreements Business Role: PROV-SALES Provider Sales and Order Mngmt Master Agreement Change: Initial Screen: Transaction FP_MA2 SAP ECC menu (for FICAX): Accounting -> Financial Accounting -> Contract Accounts Receivable and Payable ->Master Data -> For Integration with Rating and Charging -> Master Agreement -> Edit SAP ECC menu (for TELCO): Telecommunications -> Business Master Data -> For Integration with Rating and Charging -> Outline Agreement -> Edit Transaction FKKINV_S – Individual Invoicing SAP ECC menu (for FICAX): Accounting -> Financial Accounting -> Contract Accounts Receivable and Payable -> Convergent Invoicing -> Invoice Documents -> FKKINV_S Create SAP ECC menu (for TELCO): Telecommunications -> Contract Accounts Receivable and Payable -> Convergent Invoicing -> Invoice Documents -> Create Filter for Billable Items Change: Transaction FP_FILTER2 SAP ECC menu (for FICAX): Accounting -> Financial Accounting -> Contract Accounts Receivable and Payable ->Master Data -> For Integration with Rating and Charging -> Master Agreement -> Edit Filter SAP ECC menu (for TELCO): Telecommunications -> Business Master Data -> For Integration with Rating and Charging -> Outline Agreement -> Edit Filter A BCD

7. ©2014 SAP AG. All rights reserved.7 Icon Legend (2/2) IconName CRM middleware, BDOC type = BUS_TRANS_MSG RFC CRM_ISX_CONTRACT_MAINTAIN To replicate a provider contract. Web service: chargingContractMaintain. See also: To find a contract: Web service chargingContractFind Explicit activation of a contract (necessary before refill): Web service: chargingContractBulkActivate RFCs: /1FE/ _BIT_CREATE_API: Loads a set of billable items into SAP CI. The billable items matches the billable item class structures ( is the name of the billable item class e.g. /1FE/AK01_BIT_CREATE_API) FKK_BIX_BITCAT_LIST_GET_SAPCC: Reads the name of the available billable item classes. FKK_BIX_BITCAT_STRUC_GET_API : Reads the billable item class structure FKK_BIX_SUBPROCESS_LIST_GET: Reads the SUBPROCESS enumeration FKK_BIX_BITTYPE_LIST_GET : Reads the BITTYPE enumeration FKK_PREP_MESSAGE : Loads the notification into SAP CI Billing in Contract Accounts Receivable and Payable (Mass Creation): Transaction FKKBIX_M SAP ECC menu (for FICAX): Accounting -> Financial Accounting -> Contract Accounts Receivable and Payable -> Convergent Invoicing ->Periodic Processing -> Billing -> Execute Billing SAP ECC menu (for TELCO): Telecommunications -> Contract Accounts Receivable and Payable ->Convergent Invoicing ->Periodic Processing -> Billing -> Execute Billing Invoicing (Mass Creation): Transaction FKKINV_M SAP ECC menu (for FICAX): Accounting -> Financial Accounting -> Contract Accounts Receivable and Payable -> Convergent Invoicing -> Periodic Processing -> Invoicing -> Execute Invoicing SAP ECC menu (for TELCO): Telecommunications -> Contract Accounts Receivable and Payable -> Convergent Invoicing -> Periodic Processing -> Invoicing -> Execute Invoicing 1 2 3 4 1 2

8. Appendix

9. ©2014 SAP AG. All rights reserved.9 Process Diagram Legend User Role * ≈≈ * : SAP System (PPMS name), or non-SAP System, or lane for steps outside software LaneProcess Step Process Step Outside Software Optional Process Step Outside Software Optional Automatic Process Step 1 Automatic Process Step 1 Process Step (manual or automatic) 1 A Optional Process Step (manual or automatic) 1 A Optional Manual Process Step A Manual Process Step A Process Step Outside Scope Item Scope A Interface User Interface (UI) Batch Script Interface (like A2A/ B2B Message) 1 A 1 Sequence flow Connection Documents Gateways Events Data flow Inline / Standalone Output Document 1 1 1 1 Accounting Document A Link to SAP Best Practice Processes or scope items Page Link ( ) Link to SAP Best Practice Process Link Incoming Link Outgoing Link Timer Event Message XOR OR AND Complex

10. Thank you

11. ©2014 SAP AG. All rights reserved.11 © 2014 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG (or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.http://global12.sap.com/corporate-en/legal/copyright/index.epx Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP AG or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP AG or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP AG or SAP affiliate company 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. In particular, SAP AG or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP AG’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP AG or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.