SAP Business One Financial Consolidation

Transcription

1 Configuration Guide SAP Business One 9.0 integration for SAP NetWeaver Document Version: All Countries

2 Typographic Conventions Type Style Example Example EXAMPLE Example Example <Example> EXAMPLE Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Textual cross-references to other documents. Emphasized words or expressions. 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. 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. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER SAP SE or an SAP affiliate company. All rights reserved Typographic Conventions

3 Document History Version Date Change Release to Customer Update for SAP Business One releases Document SAP SE or an SAP affiliate company. All rights reserved 3

4 Table of Contents 1 Introduction Scenario Description Systems and Releases General Prerequisites Preparation Steps in the SAP Business One System Landscape Checking Country and Localization-Specific Settings Creating Consolidated Business Partner Records Checking Default Values Synchronizing the Chart of Accounts and Account Assignment Configuration in SAP Business One integration for SAP NetWeaver Creating System ID-Specific Properties for a Sending SAP Business One Company Setting up and Activating the Scenario Package Table of Contents

5 1 Introduction 1.1 Scenario Description (sap.b1.financialcons) consolidates journal entries created in your local SAP Business One companies in a central consolidation database. This provides you with consolidated journal entry-based financial data of your entire SAP Business One company network. Scenario Overview The consolidation of journal entries in the distributed SAP Business One environment is the prerequisite for financial reports in the central SAP Business One consolidation database. The following is consolidated into the central SAP Business One consolidation database: New journal entries created in local SAP Business One companies Updates to previously consolidated journal entries that have been updated in local SAP Business One companies The scenario transfers the following journal entries to the central consolidation SAP Business One company: Journal entries automatically created by logistic documents postings in the local SAP Business One company Journal entries manually created by the local accounting responsible in the local SAP Business One company The central consolidation of SAP Business One provides a consolidated view of the financial situation of the local SAP Business One companies to internal and external parties. It is, for example, suitable for consolidated tax reporting (ELSTER), consolidated EU sales reports, consolidated balance sheets, and P/L reporting. You can correct data in the central SAP Business One consolidation company. The central SAP Business One company is a virtual company not intended for any company-related business transactions. You need to maintain all default values of the local SAP Business One companies in both the central consolidation SAP Business One company and the local SAP Business One database. You map values with differing keys, due to Introduction 2017 SAP SE or an SAP affiliate company. All rights reserved 5

6 the SAP Business One database table and depending on the key generation procedure, using the SAP Business One integration for SAP NetWeaver value mapping function. This integration scenario is an event-triggered scenario to retrieve journal entry inserts and updates from the local SAP Business One companies. It enhances journal entry data with additional information concerning the EU tax relevance flag and the reference document-related federal tax ID from the respective ship-to address It also enhances journal entry data with the subsidiary identifier maintained in the SysID. The subsidiary identifier is stored in the receiving consolidation company journal entry for later identification of the journal entry origin. The following steps describe the SAP Business One Financial Consolidation integration scenario: The responsible creates or updates logistic documents or manual journal entry records in the local SAP Business One companies. SAP Business One or SAP Business One event sender creates corresponding events. The system retrieves the data and sends it to SAP Business One integration for SAP NetWeaver for further processing. SAP Business One integration for SAP NetWeaver receives the data and determines the receiving SAP Business One company. SAP Business One integration for SAP NetWeaver prepares the data, for example, providing the correct field structure and expected values. SAP Business One integration for SAP NetWeaver sends the data to the target system. SAP Business One integration for SAP NetWeaver inserts or updates journal entries into the consolidation database. 1.2 Systems and Releases You can use the scenario with the following systems and releases: System Release SAP Business One SAP Business One 8.8, 8.81, 8.82, 9.0, 9.1, 9.2 SAP Business One integration for SAP NetWeaver 9.0 SAP Business One 8.82, 9.0, 9.1, 9.2 version for SAP HANA 1.3 General Prerequisites You have installed SAP Business One integration for SAP NetWeaver. You have created system entries for all systems, you have set up technical connections between the systems, and you have successfully tested them. If you cannot use the scenario packages without changes, copy the scenario steps of the packages to your namespace and adjust the definitions. For more information about installing SAP Business One integration for SAP NetWeaver and setting up the technical system landscape, see the Administrator's Guide. SAP SE or an SAP affiliate company. All rights reserved Introduction

7 1.4 Preparation Steps in the SAP Business One System Landscape To prepare the scenario, do the following: Check the country and localization settings for the involved companies Create consolidated business partner records Check the default values of the involved companies Synchronize the chart of accounts and account assignment Checking Country and Localization-Specific Settings If you plan to transfer your journal entries from SAP Business One companies with different localization settings to a central consolidation SAP Business One company, set up the system currency of the local SAP Business One with the currency of the central SAP Business One. The scenario retrieves and transfers all journal entry values in system currency to the central SAP Business One. The system currencies of local SAP Business One companies and the local currency of the SAP Business One consolidation company must be the same Creating Consolidated Business Partner Records In your central consolidation SAP Business One company, create all business partner records that are relevant for journal entry data. To guarantee that all related customer business partner records are available in the central consolidation Business One company, and then subsequently distributed to the local SAP Business One companies, consider using the SAP Business One Master Data Distribution: Business Partner integration scenario Checking Default Values Before consolidating journal entries from your local SAP Business One company in the central SAP Business One consolidation database, ensure that all default values of the local databases also exist in the central consolidation database. Ensure that all VAT tax keys affected by journal entry postings in the local SAP Business One company are also available in the central consolidation SAP Business One company. Introduction 2017 SAP SE or an SAP affiliate company. All rights reserved 7

8 1.4.4 Synchronizing the Chart of Accounts and Account Assignment Before transferring journal entries from local SAP Business One companies to the central consolidation SAP Business One, ensure that the chart of accounts is synchronized in all databases. If you cannot synchronize the chart of accounts, use the SAP Business One integration for SAP NetWeaver value mapping function to map the account values from sender values to the expected receiver account values. For more information, see section 2.2. Setting up and Activating the Scenario Package SAP SE or an SAP affiliate company. All rights reserved Introduction

9 2 Configuration in SAP Business One integration for SAP NetWeaver 2.1 Creating System ID-Specific Properties for a Sending SAP Business One Company You maintain SysID-specific properties for each subsidiary in the system landscape. System ID-specific properties are available per system type. When you create a system landscape entry, this entry gets a unique system ID (SysID). You can maintain values for properties for the SysID. SAP Business One integration for SAP NetWeaver accesses the properties at runtime and uses them for message processing, for example, for automatically setting defaults, option selection, and so on. All scenario packages that use the systems as senders or receivers, can access the SysID-specific properties. Example In the intercompany purchasing scenario package, SAP Business One integration for SAP NetWeaver uses SysID-specific properties to automatically set a default for the subsidiary customer number in the purchase document message from the subsidiary SAP Business One. SAP Business One integration for SAP NetWeaver uses this subsidiary customer number in structure mapping to replace the vendor number in the document header with a customer number. This causes the receiver headquarters SAP Business One to create a sales order based on the purchase order message. Procedure 1. To start SAP Business One integration for SAP NetWeaver, choose Start All Programs SAP Business One integration for SAP NetWeaver SAP Business One integration for SAP NetWeaver. 2. To log on, in the B1i Administrative Login user interface, enter the user name and password. 3. Choose SLD and select the SLD entry for your subsidiary. 4. To set a value for the Subsidiary Identifier system type property, choose the Properties button and enter the ID of the local SAP Business One company. The journal entry message posted in the central consolidation SAP Business One company contains this subsidiary identifier to identify the local SAP Business One company, from which the journal entry comes. Note All other properties are not relevant for the SAP Business One intercompany financial consolidation scenario. You can ignore them. 5. Save your settings. Configuration in SAP Business One integration for SAP NetWeaver 2017 SAP SE or an SAP affiliate company. All rights reserved 9

10 2.2 Setting up and Activating the Scenario Package You use the setup functions of scenarios to configure your intercompany purchasing scenario. To set up the scenario, do the following: Select scenario steps. Select the sender systems. Select receiver systems. You can use either the existing integration framework functions or the setup wizard ( ). The description below uses the setup wizard. Procedure 1. To start SAP Business One integration for SAP NetWeaver, choose Start All Programs SAP Business One integration for SAP NetWeaver SAP Business One integration for SAP NetWeaver. 2. To log on, in the B1i Administrative Login user interface, enter the user name and password. 3. To setup your scenario, choose Scenarios Setup. 4. In the Scenario Package Identifier field, select the sap.financialcons scenario package and choose (Setup Wizard). The step Selection of Scenario Steps displays the scenario steps for the scenario package. 5. Select the Activate checkbox for the sap.b1je2b1je scenario step, choose the Save button, and choose Next. 6. In the Senders section select the subsidiary systems. In the Receivers section select the headquarters or consolidation SAP Business One and choose Next. 7. Choose the Next button until you reach the Value Mapping step. The scenario does not require filter definitions and properties. 8. In the Value Mapping user interface, define values for all available mappings and for all system combinations; choose Next. The AccountNo mapping field is available: To create a value mapping, choose New. o In the Mapping Definitions section, to select the sender system, choose the (ellipsis) button. o To select a receiver system, choose the second the (ellipsis) button. o To define mapping values, choose the Modify button. In the Value Mapping Table that opens, do the following: o To add a value pair, click on the Add button. o In the first field, enter the value for the sender system. o In the second field, enter the value for the receiver system. o Save your settings and close the window. 9. As there are no scheduler settings necessary, choose Next, and finally choose Deploy to finalize the scenario setup. 10. To activate your scenario, choose the Activate button. SAP SE or an SAP affiliate company. All rights reserved Configuration in SAP Business One integration for SAP NetWeaver

11

12 SAP SE 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 SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE and its affiliated companies ( SAP Group ) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see for additional trademark information and notices.