Upload
others
View
1
Download
0
Embed Size (px)
Citation preview
PUBLIC
Global Roll-out, SAP
The Working Process Across Branch CompaniesIntercompany Integration Solution for SAP Business One
2PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
The Working Process Across Branch Companies:
▪ Topic 1: The Intercompany Trade Process
▪ Topic 2: Allocation of Amounts Across Branch Companies
▪ Topic 3: Centralized Payments
Process Overview
3PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
At the end of this course, you will be able to:
• Follow the workflow across companies:
▪ Run the intercompany trade process - post documents (AR/AP)
▪ Allocate expense and income amounts
▪ Post centralized payments
• Work with the involved master data in the different companies.
Topic Objective
4PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
The Working Process Across Branch Companies:
▪ Topic 1: The Intercompany Trade Process
▪ Topic 2: Allocation of Amounts Across Branch Companies
▪ Topic 3: Centralized Payments
Process Overview
5PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
▪ OEC Computers has three branches in the US: The head office in New York and
branches in California and Texas.
▪ All branches run SAP Business One.
▪ New York and California are selling the company products, while Texas
manufacturers them.
▪ When one of the retail companies receives an order from a customer, they place a
back-to-back purchase order to the manufacturing company.
▪ This initiates the intercompany trade process that allows an automatic document
flow.
The Intercompany Trade Process:
Business Scenario
6PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
▪ For each branch company define:
▪ Vendor
▪ Customer
▪ Define these master data records as Global
▪ Connect each customer and vendor record
to the relevant branch
▪ A Purchase Order for a vendor (Texas) in the
retail branch (NY) will initiate a Sales Order in
the manufacturer branch (Texas)
The Intercompany Trade Process
Prerequisites – Branch Business Partner
Branch Customer Code Vendor Code
OEC-NY OEC-NY-CUST OEC-NY-VEND
OEC-TX OEC-TX-CUST OEC-TX-VEND
OEC-CA OEC-CA-CUST OEC-CA-VEND
Purchase Order
OEC-TX-VEND
Sales Order
OEC-NY-CUST
OEC-NY OEC-TX
7PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Intercompany Trade – Document Flow
OE
C-N
Y
OE
C-T
X
Purchase Order Sales Order
A/R ReserveInvoice
Automatic using B1i
A/P ReserveInvoice
DeliveryGoods Receipt PO
A/R InvoiceA/P Invoice
A/R Debit MemoA/P Debit Memo
A/R Credit MemoA/P Credit Memo
Automatic using B1i
Automatic using B1i
Automatic using B1i
Automatic using B1i
User Action
User Action
User Action
User Action
User Action
Company A Company B
A/P CorrectionInvoice
A/P CorrectionInvoice Reversal
A/R CorrectionInvoice
A/R CorrectionInvoice Reversal
Goods Return Return
Automatic using B1i
Automatic using B1i
Automatic using B1i
Automatic using B1i
User Action
User Action
User Action
User Action
User Action
User Action
User Action
8PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Inter-Branch Transaction Scenario
Purchase Order Sales Order
A/R ReserveInvoice
Automatic using B1i
A/P ReserveInvoice
DeliveryGoods Receipt PO
A/R InvoiceA/P Invoice
A/R Debit MemoA/P Debit Memo
A/R Credit MemoA/P Credit Memo
Automatic using B1i
Automatic using B1i
Automatic using B1i
Automatic using B1i
User Action
User Action
User Action
User Action
User Action
Company A Company B
A/P CorrectionInvoice
A/P CorrectionInvoice Reversal
A/R CorrectionInvoice
A/R CorrectionInvoice Reversal
Goods Return Return
Automatic using B1i
Automatic using B1i
Automatic using B1i
Automatic using B1i
User Action
User Action
User Action
User Action
User Action
User Action
User Action
User Action
OE
C-N
Y
OE
C-T
X
9PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Inter-Branch Transaction Scenario
OE
C-N
Y
OE
C-T
X
Purchase Order Sales Order
A/R ReserveInvoice
Automatic using B1i
A/P ReserveInvoice
DeliveryGoods Receipt PO
A/R InvoiceA/P Invoice
A/R Debit MemoA/P Debit Memo
A/R Credit MemoA/P Credit Memo
Automatic using B1i
Automatic using B1i
Automatic using B1i
Automatic using B1i
User Action
User Action
User Action
User Action
User Action
Company A Company B
A/P CorrectionInvoice
A/P CorrectionInvoice Reversal
A/R CorrectionInvoice
A/R CorrectionInvoice Reversal
Goods Return Return
Automatic using B1i
Automatic using B1i
Automatic using B1i
Automatic using B1i
User Action
User Action
User Action
User Action
User Action
User Action
User Action
User Action
User Action
User Action
10PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Intercompany Trade – Document Status
Pending
Accept
Reject
Document
Total
Comparison
Engine
11PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
The Intercompany integration solution:
▪ Replicates serial numbers and batch numbers
as part of the document exchange cycles.
▪ Blocks creation of intercompany marketing
document until the base document is confirmed.
More about Marketing Documents
12PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Cancelling Marketing Documents
You can cancel most sales and
purchasing documents that trigger
postings:
▪ A corresponding cancellation document is created
▪ The base documents of the canceled documents
are reopened
▪ The application automatically cancels the reciprocal
document
13PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
▪ Make sure you create separate control
accounts for each of the business
partners representing a branch company
▪ In each branch you define the control
accounts for the business partners
representing the other branches
▪ This is the New York branch account
setup
Branch Business Partner
Dedicated Control Accounts
Branch Vendor Control
Account
Customer Control
Account
OEC-NY __ __
OEC-TXPayable OEC-TX
Company
Receivable OEC-TX
Company
OEC-CAPayable OEC-CA
Company
Receivable OEC-CA
Company
OEC-NYControl Account Setup
14PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Branch Business Partner
Dedicated Control Accounts
Steps 15 and 16 in the Intercompany Setup Wizard in each branch runs the
users through the steps relevant for setting up the Receivable and Payable
control accounts of the other branches.
15PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
▪ Let us look at the Texas control
account setup
Branch Business Partner
Dedicated Control Accounts
OEC-TXControl Account Setup
Branch Vendor Control
Account
Customer Control
Account
OEC-NYPayable OEC-NY
Company
Receivable OEC-NY
Company
OEC-TX__ __
OEC-CAPayable OEC-CA
Company
Receivable OEC-CA
Company
16PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
▪ Let us look at the California control
account setup
Branch Business Partner
Dedicated Control Accounts
OEC-CAControl Account Setup
Branch Vendor Control
Account
Customer Control
Account
OEC-NYPayable OEC-NY
Company
Receivable OEC-NY
Company
OEC-TXPayable OEC-TX
Company
Receivable OEC-TX
Company
OEC-CA__ __
17PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Branch Business Partner
Dedicated Control Accounts
In each branch, for
the business partners
representing the other
branches, define the
control account.
18PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Inter-Branch Transaction ScenarioIncluding an External Customer
Purchase Order Sales Order
A/R ReserveInvoice
Automatic using B1i
A/P ReserveInvoice
DeliveryGoods Receipt PO
A/R InvoiceA/P Invoice
A/R Debit MemoA/P Debit Memo
A/R Credit MemoA/P Credit Memo
Automatic using B1i
Automatic using B1i
Automatic using B1i
Automatic using B1i
User Action
User Action
User Action
User Action
User Action
Company A Company B
A/P CorrectionInvoice
A/P CorrectionInvoice Reversal
A/R CorrectionInvoice
A/R CorrectionInvoice Reversal
Goods Return Return
Automatic using B1i
Automatic using B1i
Automatic using B1i
Automatic using B1i
User Action
User Action
User Action
User Action
User Action
User Action
User ActionOE
C-N
Y
OE
C-T
X
User Action
Custo
mer
Emphases:
◼Choose a drop ship
WH
◼Check the Procurement
Document box
19PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Inter-Branch Transaction ScenarioIncluding an External Customer
Emphases:
◼ Choose a drop
ship WH.
◼ Check the
Procurement
Document box.
OE
C-N
YC
usto
mer
20PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Inter-Branch Transaction ScenarioIncluding an External Customer
OE
C-N
YC
usto
mer
OE
C-T
X
Emphases:
◼Choose the branch
vendor BP
◼Use the Ship to BP
field
Purchase Order Sales Order
A/R ReserveInvoice
Automatic using B1i
A/P ReserveInvoice
DeliveryGoods Receipt PO
A/R InvoiceA/P Invoice
A/R Debit MemoA/P Debit Memo
A/R Credit MemoA/P Credit Memo
Automatic using B1i
Automatic using B1i
Automatic using B1i
Automatic using B1i
User Action
User Action
User Action
User Action
User Action
Company A Company B
A/P CorrectionInvoice
A/P CorrectionInvoice Reversal
A/R CorrectionInvoice
A/R CorrectionInvoice Reversal
Goods Return Return
Automatic using B1i
Automatic using B1i
Automatic using B1i
Automatic using B1i
User Action
User Action
User Action
User Action
User Action
User Action
User Action
User Action
21PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Inter-Branch Transaction ScenarioIncluding an External Customer
Emphases:
◼ Choose the
branch vendor BP.
◼ Use the Ship to
BP field.
22PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Inter-Branch Transaction ScenarioIncluding an External Customer
OE
C-N
YC
usto
mer
OE
C-T
X
Emphases:
◼ Use the Create
Delivery option.
Purchase Order Sales Order
A/R ReserveInvoice
Automatic using B1i
A/P ReserveInvoice
DeliveryGoods Receipt PO
A/R InvoiceA/P Invoice
A/R Debit MemoA/P Debit Memo
A/R Credit MemoA/P Credit Memo
Automatic using B1i
Automatic using B1i
Automatic using B1i
Automatic using B1i
User Action
User Action
User Action
User Action
User Action
Company A Company B
A/P CorrectionInvoice
A/P CorrectionInvoice Reversal
A/R CorrectionInvoice
A/R CorrectionInvoice Reversal
Goods Return Return
Automatic using B1i
Automatic using B1i
Automatic using B1i
Automatic using B1i
User Action
User Action
User Action
User Action
User Action
User Action
User Action
User Action
User Action
User Action
23PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Inter-Branch Transaction ScenarioIncluding an External Customer
Emphases:
◼ Use the Create
Delivery option.
24PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
The Working Process Across Branch Companies:
▪ Topic 1: The Intercompany Trade Process
▪ Topic 2: Allocation of Amounts Across Branch Companies
▪ Topic 3: Centralized Payments
Process Overview
25PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
▪ The head office branch allocates expenses such as
travel, payroll, and audit
▪ The head office also allocates income earned from
Interest to the branch companies
Branch Allocation: Business Scenario
▪ At the end of each month the head office branch (NY) allocates expense
and income amounts to the other branch companies (California and Texas)
26PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
▪ You allocate expenses and
incomes to other branch
companies using the G/L
Branch Allocation window
G\L Branch Allocation Window
Financials → G/L Branch Allocation.
Top Matrix – Allocating Company
27PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
G\L Branch Allocation Window
▪ You allocate expenses and
incomes to other branch
companies using the G/L
Branch Allocation window
Financials → G/L Branch Allocation.
Bottom Matrix – Receiving Companies
28PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
G\L Branch Allocation - Target Company Allocation Account
▪ If you specify the target
company allocation
account for a branch code,
then this allocation account
will be used instead of the
receiving company´s
default expense account or
default income account
Financials → G/L Branch Allocation.
29PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
G\L Branch Allocation - Target Company Allocation Account
▪ To be able to specify the
target company allocation
account for a branch code,
run the Allocation Accounts
Synchronization option
Administration → System Initialization →
Company Details → Accounting Data tab.
30PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
▪ When you add the G/L Branch
Allocation form, a journal
entry is automatically created
in the current company, the
company that allocates the
amounts
(NY in our example).
Expense Allocation to Branch Companies
The Journal Entry in the Allocating Company
Dr Cr
Due From
BR002
R$ 250
Expense –
Management
Fee
$ 1000
Due From
BR003
$ 350
Due From
BR004
$ 400
Dr Cr
Due To BR001
$ 250
Default
Expense
Account
$ 250
Dr Cr
Due To BR001
$ 350
Default
Expense
Account
$ 350
Dr Cr
Due To BR001
$ 400
Default
Expense
Account
$ 400
Head Office
BR001
Subsidiary 1
BR002
Subsidiary 2
BR003
Subsidiary 3
BR004
G/L Allocation Screen
Journal Voucher Screen
Journal Voucher Screen
Journal Voucher Screen
Sender System
Receiver System
Receiver System
Receiver System
31PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
▪ When you add the G\L Allocation,
a journal voucher is created in
the allocated companies
(Texas and California)
Expense Allocation to Branch Companies
Journal Voucher in the Allocated Companies
Dr Cr
Due From
BR002
R$ 250
Expense –
Management
Fee
$ 1000
Due From
BR003
$ 350
Due From
BR004
$ 400
Dr Cr
Due To BR001
$ 250
Default
Expense
Account
$ 250
Dr Cr
Due To BR001
$ 350
Default
Expense
Account
$ 350
Dr Cr
Due To BR001
$ 400
Default
Expense
Account
$ 400
Head Office
BR001
Subsidiary 1
BR002
Subsidiary 2
BR003
Subsidiary 3
BR004
G/L Allocation Screen
Journal Voucher Screen
Journal Voucher Screen
Journal Voucher Screen
Sender System
Receiver System
Receiver System
Receiver System
32PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
▪ Make sure you define due from and due to
accounts in each branch company
▪ These accounts are used as the default
accounts for the transactions:
▪ G/L branch allocation
▪ A/P service invoice allocation
▪ Centralized payment
▪ In each branch you define the due from and
due to accounts for transactions representing
the other branches
Allocate Amounts Across Branch Companies
Prerequisites - Due To + Due From Accounts
Branch Due To Account Due From Account
OEC-NY __ __
OEC-TXDue to OEC-TX
Company
Due From OEC-TX
Company
OEC-CADue to OEC-CA
Company
Due From OEC-CA
Company
OEC-NYBranch Account Setup
33PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Due To + Due From Accounts Setup
34PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
▪ Another way to
allocate expense
amounts to other
branch companies
is by using the
Allocation window
on the A/P Service
Invoice document
A/P Service Invoice Allocation
35PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Additional Definitions for the G/L Allocation and the A/P Service Invoice
Allocation
Default Accounts Setup
36PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Additional Definitions for the G/L Allocation and
the A/P Service Invoice Allocation
Account Classification
Sending Company
37PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Additional Definitions for the G/L Allocation
and the A/P Service Invoice Allocation
Account Classification
Receiving Company
38PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Additional Definitions for the G/L Allocation and
the A/P Service Invoice Allocation
Account Classification
Receiving CompanyAccount Classification
Sending Company
39PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
The Working Process Across Branch Companies:
▪ Topic 1: The Intercompany Trade Process
▪ Topic 2: Allocation of Amounts Across Branch Companies
▪ Topic 3: Centralized Payments
Process Overview
40PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Centralized Payments:Business Scenario
▪ For this process, the branch companies
(California and Texas) need to delegate
outgoing payment lines to the paying branch
(NY)
▪ At the end of each month the head office branch (NY) centralizes the
outgoing payments and pays the company vendors on behalf of the other
branches (California and Texas)
41PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Centralized Payments Transaction Flow
Company B Head Office -BR001
Company A Subsidiary Company BR002
Dr Cr
Due From Account BR002
Vendor Account
Dr Cr
Vendor Account
Due to AccountBR001
Automatic using B1i
Dr Cr
Vendor Account
Cash/Bank Account
Delegation of payment line to BR001
User Action
Journal Entry
Outgoing Payment
OEC-NYOEC-TX
42PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Centralized PaymentsTransaction Flow
Company B Head Office -BR001
Company A Subsidiary Company BR002
Dr Cr
Due From Account BR002
Vendor Account
Dr Cr
Vendor Account
Due to AccountBR001
Automatic using B1i
Dr Cr
Vendor Account
Cash/Bank Account
Delegation of payment line to BR001
User Action
Journal Entry
Outgoing Payment
OEC-NYOEC-TX
© 2020 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/copyright for additional trademark information and notices.
www.sap.com/contactsap
Follow us