Upload
khangminh22
View
2
Download
0
Embed Size (px)
Citation preview
PUBLIC
SAP Business One, Global Roll-out
July, 2018
Intercompany Integration Solution for SAP Business One Intercompany Integration Solution vs. Multiple Branches: How to Decide?
2PUBLIC© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Agenda
1. Schematic Solution Positioning
2. Intercompany Integration Solution for SAP Business One
3. Multiple Branches for SAP Business One
4. Functionalities Side by Side
5. Scenario Demonstration
3PUBLIC© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Customer-Specific Customization / Development
Inte
gra
tion
& A
uto
ma
tio
n L
eve
l
Complex Customer RequirementsSimple Customer Requirements
MULTI-INSTANCEMASTER DATA REPLICATION AND CONTENT SHARING
STANDARDIZED PROCESSES ACROSS BUSINESS ENTITIES VISIBILITY INTO OPERATIONS ACROSS BUSINESS ENTITIES
CENTRALIZED ADMINISTRATION AND MONITORING IMPROVED CONTROL AND COLLABORATION
MULTI-CURRENCY CROSS
LOCALIZATION
Solutions by Software Solution Partners
Intercompany Integration Solution
Multiple Branches
Intercompany Portfolio for SAP Business One/Schematic Solution Positioning Highest Flexibility in Addressing Manifold Intercompany Requirements
4PUBLIC© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Agenda
1. Schematic Solution Positioning
2. Intercompany Integration Solution for SAP Business One
3. Multiple Branches for SAP Business One
4. Functionalities Side by Side
5. Scenario Demonstration
5PUBLIC© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Intercompany Integration Solution for SAP Business One
▪ Connects and integrates companies with multi-business units or subsidiaries
▪ Automates complex business processes
▪ Facilitates financial transactions and consolidation across
SAP Business One systems out of the box
▪ Supports companies running different SAP Business One installations
▪ Supports companies using different SAP Business One localizations
▪ Is an SAP add-on and requires additional intercompany licenses to be purchased (1:1 ratio)
▪ Requires knowledge on intercompany processes, financials, and B1iF
6PUBLIC© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Agenda
1. Schematic Solution Positioning
2. Intercompany Integration Solution for SAP Business One
3. Multiple Branches/Business Units for SAP Business One
4. Functionalities Side by Side
5. Scenario Demonstration
7PUBLIC© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Multiple Branches/Business Units for SAP Business One
▪ Automates simple business processes in the same database
▪ Divides or separates one legal entity into different business units in the
same database (business units are typically either cost centers or
profit centers, these “branches” must not represent separate legal entities)
▪ Increases transparency and reporting needs by the units
▪ Does not run on B1iF platform
▪ Does not require no additional license
▪ Is part of the SAP Business One core offering. For details, see Enabling Multiple Branches/Business Units
8PUBLIC© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Agenda
1. Schematic Solution Positioning
2. Intercompany Integration Solution for SAP Business One
3. Multiple Branches for SAP Business One
4. Functionalities Side by Side
5. Scenario Demonstration
9PUBLIC© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Combination of Intercompany Integration Solution and Multiple Branches*SAP Note 2639394
Starting with Intercompany integration solution 2.0 PL26, enterprises can use the intercompany solution
with branch enabled companies.
The option to operate both in parallel extends the possibilities of SAP Business One:
• Enterprises with multiple legal entities may want to use multiple branches solution and Intercompany
integration solution together to handle various business scenarios such as:
• Using Intercompany solution to integrate subsidiaries in different geographies and using multiple
branches solution to handle different business units in one of the subsidiary companies.
• Using multiple branches solution and integrating subsidiaries in different geographies using
Intercompany Solution.
• Customers who already use multiple branches for their business units and additionally want to
integrate legal units, subsidiaries, or separate SAP Business One company databases, can now
extend their software with SAP’s successful add-on for Intercompany integration solution.
* Requires either PL26 of the intercompany integration solution in conjunction with SAP Business One 9.3 PL01-PL04
or PL27 of the intercompany integration solution in conjunction with SAP Business One 9.2 PL11, and higher versions
10PUBLIC© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Combination of Intercompany Integration Solution and Multiple Branches*Landscape Example
Entity
Entity
Entity
Entity
Entity US
Branch 1
Branch …
Branch 2
Entity ARG
Branch 1
Branch …
Branch 2
Different legal entities of an enterprise using SAP Business One with various localizations. Some entities
using Multiple Branches function to separate business units. Intercompany solution can be used to connect
and integrate all entities into one system landscape.
* Requires either PL26 of the intercompany integration solution in conjunction with SAP Business One 9.3 PL01-PL04
or PL27 of the intercompany integration solution in conjunction with SAP Business One 9.2 PL11, and higher versions
11PUBLIC© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Functionalities Side by Side 1/2
Process/Feature Intercompany Integration Solution
for SAP Business One
Multiple Branches in
SAP Business One
Complex Business Scenarios such as multiple productions sites Yes No
Handling of different Business Processes/ Industries Yes No
Simple Business Scenario Yes Yes
Suitable for sales units Yes Yes
Cross Localization Yes No
Multi-Currency Support for intercompany transactions Yes No
Different Chart of Accounts Yes No
Restricted to single database No Yes
Master Data sharing Yes Yes
Item Master Data Allocation Yes No
Data Owner Ship for business partner master data Yes No
Manage different Authorization setups/concepts for different
Branches/ Business UnitsYes No
12PUBLIC© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Functionalities Side by Side 2/2
Process/Feature Intercompany Integration Solution
for SAP Business One
Multiple Branches in
SAP Business One
Consolidated Credit Limit Check Yes Yes
Credit Limit Check per business unit Yes No
Different Inventory valuation per business unit Yes No
Automated Document Exchange cycle Yes No
Intercompany Workflow Yes No
Accounting Reporting Yes Yes
Inventory Reports Yes Yes
Sales Analysis Report Yes Yes
Standard process for Year End Closing for different Companies
or independent BranchesYes No
Tax Reporting for different business units Yes No
Note:
Please use licenses according to the SAP Business One Licensing Terms.
13PUBLIC© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Agenda
1. Schematic Solution Positioning
2. Intercompany Integration Solution for SAP Business One
3. Multiple Branches for SAP Business One
4. Functionalities Side by Side
5. Scenario Demonstration
14PUBLIC© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Multiple Branches:
User is assigned to Branch2 but still has access and
can modify master data from other branches without
any errors from the system. There is no additional
authorization for Master Data in SAP Business One.
Items are visible and can be modify by all users
depending on license authorization.
Intercompany:
User is assigned to Branch1US and has no
authorization to add, update or remove Global Master
Data. Visualization is still possible, any other action
for a Global Master Data is forbidden. Possibility to
provide add, update and remove authorization by
individual for global master data.
Scenario – Master Data Sharing
Click here to view the Multiple Branches and Intercompany clips
15PUBLIC© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Multiple Branches:
Since the database will be sub-divided in business
units, there is no possibility to have cross
localizations (i.e. US and Canada) in the same
database.
Intercompany Integration Solution:
The solution allows connecting different databases
and there is also the possibility to have different
localizations.
The integration solution supports a number of SAP
Business One localizations, see the Administrator’s
Guide. If there is a need beyond current localization
scope, see SAP Note 2154976 – Using the
intercompany integration solution for non-localized
countries. Actually the integration solution is currently
being used in more than 60 countries.
Scenario – Cross Localization
Click here to view the Multiple Branches and Intercompany clips
16PUBLIC© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Multiple Branches:
For customers who present Credit Limit, Multiple
Branches does not provide additional feature. A credit
limit applies to all Business Units defined in the
database without any segregation.
Intercompany Integration Solution:
For customers who present Credit Limit,
intercompany provides the ability to define a local
credit limit and a global credit limit check.
Scenario – Credit Limit
Click here to view the Multiple Branches and Intercompany clips
17PUBLIC© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Multiple Branches:
When using Multiple Branches, as the customer will
have only one database, the same chart of accounts
will be shared by all business units. There is no
segregation between accounts by business unit.
Intercompany Integration Solution:
When using intercompany, as the customer will have
more than one database, different chart of accounts
can be used. Every company will have a dedicated
chart of accounts that can be similar or totally different
from the other branches.
Scenario – Chart of Accounts
Click here to view the Multiple Branches and Intercompany clips
18PUBLIC© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Multiple Branches:
Allows the duplication of marketing documents
(GRPO or AP Invoices) to facilitate the flow of
information. The process is manually performed by
the user and the marketing documents will not
present any link between each other.
Intercompany Integration Solution:
The document exchange process is automated when
using intercompany. By using the pre-defined
intercompany scenarios, B1iF will automatically
create marketing documents between companies
running with intercompany.
Scenario – Document Exchange
Click here to view the Multiple Branches and Intercompany clips
19PUBLIC© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Multiple Branches:
Customer can use branches as basic selection
criteria for SAP Business One reports, such as:
Ageing Reports, General Ledger, Balance Sheet,
Trial Balance, P&L Report, Document Journal
Reports etc.
Intercompany Integration Solution:
Customers can run reports independently of the
databases. There is the possibility to use the
Consolidation company to generate consolidate
financial reports.
Intercompany also provides additional reports, such
as: Branch Inventory in Warehouse report, Branch
Balances Report etc.
Scenario – Generating Reports
Click here to view the Multiple Branches and Intercompany clips
20PUBLIC© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Key links for more information on the Intercompany Integration Solution
▪ SAP Community Blog
▪ Check the SAP Business One YouTube playlist
▪ SAP Help Portal for various assets on Intercompany Integration
such as the Administrator's Guide or the User Guide
© 2018 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 or an SAP affiliate company.
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 or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP 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 SE 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 SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE 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, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
www.sap.com/contactsap
Follow all of SAP