Takeda global SAP FSCM solution IHC/SEPA/BCM€¦ · · 2017-03-27Takeda global SAP FSCM solution...
Transcript of Takeda global SAP FSCM solution IHC/SEPA/BCM€¦ · · 2017-03-27Takeda global SAP FSCM solution...
Takeda global SAP FSCM solution – IHC/SEPA/BCM
Presenter: Jose Eximeno
Takeda Pharmaceutical Company Limited
|2017.03 | Takeda global SAP FSCM solution 1
Agenda
1 About Takeda
2 In-House Bank and Payment Factory
3 SEPA SDD and SCT
4 BCM
5 Impacted Business Areas
3
About Takeda - An R&D driven pharmaceutical company with global presence
|2017.03 | Takeda global SAP FSCM solution
4
About Takeda – A success story with a strong heritage
1781
1914 1962-1997
2008
2011
1874
1913
1925 1999
Start-up: The
pharmacist Morten
Nyegaard started
importing drugs to
Norway. Nyegaard &
Co. changes its name
to Nycomed in 1986
Production: The
start of our own
production of
pharmaceutical
products, included the
success Globoid
Research:
Started our own
pharmaceutical
research Sales: Nycomed
acquired by
Nordic Capital
Takeda founded by
Chobei Takeda in
Japan
Research activities
begin with
establishment of a
research division
Takeda expands its
overseas operations
into Asia, the U.S.
and Europe
Takeda acquires
Millennium
Pharmaceuticals
forming Takeda‘s
wholly owned
oncology company
Takeover:
Takeda
Pharmaceutical
Company buys
Nycomed
|2017.03 | Takeda global SAP FSCM solution
5
About Takeda – Leading OTC in Norway
40 OTC-drugs and 80 commodities sold under the Nycomed-brand
|2017.03 | Takeda global SAP FSCM solution
6
SAP ERP Coverage
ROW SAP
US and JP SAP
Planned SAP
US
BR
AR
PE
VE CO
EC
MX
CA
ZA
EG IN
TR ES PT
FR
IT
DE
NO
SE FI
RU
GB IE
DK
EE LV
LT PL
CH AT SI HR
HU RO
CZ SK
AE
CN
AU
KR JP
PH
ID
MY
TH
KZ UA
|2017.03 | Takeda global SAP FSCM solution
11
IHC – Intercompany (IC) Payments
Payment
Order
Bank
Statements
1
3
2
Invoice
Bank
Statements 3
TAKEDA
Subsidiary 1
Internal Bank
|2017.03 | Takeda global SAP FSCM solution
TAKEDA
Subsidiary 2
12
IHC – IHB Concept External Payments
1 Delivery
Feedback files
& Ext. Bank Statements 5
Sub
Internal Bank/
Payment Factory
Vendor
Payment instructions
to ext. banks 4
NORDEA
7 Money is
credited
2 Invoice
Takeda
Subsidiary
Payment
instructions to
IHB
IHB Bank
Statements 6
3
|2017.03 | Takeda global SAP FSCM solution
18
SEPA - Journey
* SEPA is no longer a voluntary initiative, but a regulatory requirement. This became necessary, because migration from legacy
instruments to SEPA occured too slowly .
** Consequently , corporates need to begin their preparations immediately to ensure timely migration in the course of 2013
|2017.03 | Takeda global SAP FSCM solution
19
SEPA Phase I and Phase II Time Lines
2013 2014
3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6 7
ERP 6 EHP6
Intensive
care
Phase
II
Intensive Care
Phase I
Phase II SEPA Phase I
UPGRADE SAP ERP
SEPA
Implementation
Completion*
Milestones
Preliminary Study
Analysis & Planning
1.2.14
Migration
end date
1.12.13
Go-live
Phase I
15.11.13 15.8.13 31.5.13 1.7.14
Go-live
Phase II
Ba
nk‘s
IT
fro
ze
n z
on
e
|2017.03 | Takeda global SAP FSCM solution
21
SEPA Phase I - SDD - Overview and Deliverables
Phase I SEPA SDD - Deliverables
• XML for SEPA Direct Debit; for 5 countries (DE, AT, NL, IT(RID), ES)
• XML for ACK/NACK for SDD
• SAP SDD mandate handling
|2017.03 | Takeda global SAP FSCM solution
22
SEPA SDD Instruments (Difference between SDD core and B2B)
|2017.03 | Takeda global SAP FSCM solution
25
SEPA Phase I – ALTERNATIVES
Phase I Plan A – SEPA SDD with Inhouse Bank
To configure and use SAP standard functionality and receive direct
debits via inhouse bank.
Prerequisite: Upgrade Support Pack Level for ERP and FSCM
(financial supply chain)
Phase I Plant C – SEPA SDD with Inhouse Bank by
Programming new IDOC type.
To configure own IDOC, i.e. non-standard functionality
Prerequisites: Prototyping to verify that this would work
Phase I Plan B – SEPA SDD without InHouse
Bank
To configure and use SAP standard functionality,
but receive direct debits, ie not via inhouse bank
Prerequisite: None, it works, has been
prototyped.
Direct Debit
invoice is
created
Payment
program is run
Idoc payment
order is sent
to IHB
IHB processes
payment order
IHB reflects inbound
cash in IHB bank
statement
Idoc payment
request is sent
to Treasury
Payment program
is run and payment
file is sent to bank
Bank gets payment
from customer and
reflects transaction
in bank statement
END
Subsidiary
IHB Center
Bank
Direct Debit
invoice is created
Payment program
is run and payment
file is sent to bank
Bank gets payment
from customer and
reflects transaction
in bank statement
END
Subsidiary
IHB Center
Bank
Payment Flow Payment Flow
|2017.03 | Takeda global SAP FSCM solution
26
Creating Mandates from Customer Master Data
Configuration Payment Method in Company Code is configured to support SEPA mandates
1
Bank Master Data In the bank details of the customer an IBAN number must exist.
2
SAP Transaction FD02
Prerequisites
|2017.03 | Takeda global SAP FSCM solution
27
Creating Mandates in Mass Runs
. .
Prerequisites: SAP Transaction: FI_APAR_SEPA_CONV
The bank details have an IBAN.
The country of the bank details is participating in the SEPA procedure.
The country of the paying company code is participating in the SEPA procedure.
If the country of the bank details differs from the country of the paying company code, the customer must have a payment method that permits bank details abroad in the paying company code.
The customer has a payment method that requires bank details with direct (automatic) debit in the country of the paying company code.
The customer has a payment method that requires bank details with SEPA mandate in the country of the paying company code.
|2017.03 | Takeda global SAP FSCM solution
30
SEPA PhaSE II - SCT - Overview and Deliverables
Phase II SEPA SCT - Deliverables
• XML for DB (all currencies)
• XML for Nordea (all currencies)
• XML for ACK/NACK for SDD
• XML camt (bank statements)
|2017.03 | Takeda global SAP FSCM solution
31
SEPA Payment Formats - Advantages
|2017.03 | Takeda global SAP FSCM solution
1. Uniform payment formats for credit transfers and direct debits in the EUR payment area.
2. Reduced maintenance effort for payment formats.
3. Lower credit transfer charges (cost advantage!).
4. A central cross-company SEPA payment run is possible.
5. Standard payment formats SEPA_CT and SEPA_DD are delivered by SAP (PMW).
Advantages of SEPA payment formats
32
Master Data: IBAN Generation
Automatic IBAN generation for master data
(vendors, customers, personnel, health
insurers,
building and loan associations, and so on.)
Selection of program runs (download/upload):
1.Check existing IBAN
(checks and corrects
IBANs present in SAP)
2.Creditor master data
(determines missing IBANs for
creditor bank details)
3.Additional master data such as debtors etc. if
required
Manual postprocessing of error logs (IBANs
cannot be generated)
Business partners written to only in this case!
Supported countries/IBAN procedure (see SAP
Note 1397739) at present CH, DE, BE, AT, FI, NL
Change payment method by SAP mass change
in creditor master data
|2017.03 | Takeda global SAP FSCM solution
33
SEPA Outbound XML File
.
Payment run: F110
<?xml version="1.0" encoding="utf-8" ?>
- <Document
xmlns="urn:iso:std:iso:20022:tech:xsd:pain.008.001.01"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <pain.008.001.01>
- <GrpHdr>
<MsgId>1002176320</MsgId>
<CreDtTm>2013-04-23T12:48:24</CreDtTm>
<NbOfTxs>1</NbOfTxs>
<CtrlSum>1000.00</CtrlSum>
<Grpg>MIXD</Grpg>
- <InitgPty>
<Nm>Takeda GmbH (Germany)</Nm>
</InitgPty>
</GrpHdr>
- <PmtInf>
<PmtInfId>1002176320</PmtInfId>
<PmtMtd>DD</PmtMtd>
- <PmtTpInf>
- <SvcLvl>
<Cd>SEPA</Cd>
</SvcLvl>
- <LclInstrm>
<Cd>CORE</Cd>
</LclInstrm>
<SeqTp>RCUR</SeqTp>
</PmtTpInf>
<ReqdColltnDt>2013-04-22</ReqdColltnDt>
- <Cdtr>
<Nm>Takeda GmbH (Germany)</Nm>
- <PstlAdr>
<AdrLine>Byk Gulden Str. 3</AdrLine>
<AdrLine>Konstanz</AdrLine>
<Ctry>DE</Ctry>
</PstlAdr>
</Cdtr>
- <CdtrAcct>
- <Id>
<IBAN>DE84690700320011640000</IBAN>
</Id>
<Ccy>EUR</Ccy>
</CdtrAcct>
- <CdtrAgt>
- <FinInstnId>
<BIC>DEUTDE6F690</BIC>
</FinInstnId>
</CdtrAgt>
<ChrgBr>SLEV</ChrgBr>
- <DrctDbtTxInf>
- <DrctDbtTxInf>
- <PmtId>
<InstrId>01-801100221805722014</InstrId>
<EndToEndId>0022180572</EndToEndId>
</PmtId>
<InstdAmt Ccy="EUR">1000.00</InstdAmt>
- <DrctDbtTx>
- <MndtRltdInf>
<MndtId>000000000001</MndtId>
<DtOfSgntr>2013-04-17</DtOfSgntr>
<AmdmntInd>false</AmdmntInd>
</MndtRltdInf>
- <CdtrSchmeId>
- <Id>
- <PrvtId>
- <OthrId>
<Id>DE19ZZZ440800500359599700</Id>
<IdTp>SEPA</IdTp>
</OthrId>
</PrvtId>
</Id>
</CdtrSchmeId>
</DrctDbtTx>
- <DbtrAgt>
- <FinInstnId>
<BIC>INGDDEFF</BIC>
</FinInstnId>
</DbtrAgt>
- <Dbtr>
<Nm>Advance Pharma GmbH</Nm>
- <PstlAdr>
<AdrLine>Wallenroder Strasse 12-14</AdrLine>
<AdrLine>13435 Berlin</AdrLine>
<Ctry>DE</Ctry>
</PstlAdr>
</Dbtr>
- <DbtrAcct>
- <Id>
<IBAN>DE79500105170335535353</IBAN>
</Id>
</DbtrAcct>
- <RmtInf>
<Ustrd>/INV/ 1.4.2013</Ustrd>
</RmtInf>
</DrctDbtTxInf>
</PmtInf>
</pain.008.001.01>
</Document>
|2017.03 | Takeda global SAP FSCM solution
34
PF: External Bank Interface Flow
AR
AP
Payments /
Bank
Statements
CORE SAP
Dat
a co
nve
rter
Mo
ve IT
BCM
XML Bank Statements
(CAMT)
XML confirmations/
Rejections (Pain002)
DB
XML payments
(Pain001)
XML payments (Pain001)
XML confirmations/
Rejections (Pain002)
XML Bank Statements
(CAMT)
Nordea
Debtor Agent
(Payer Bank)
Creditor
Creditor Agent
(Payee’s Bank)
Interbank Clearing
And Settlement
|2017.03 | Takeda global SAP FSCM solution
35
Pros and Cons of implementing CAMT statements (vs MT940)
1. Must be configured (new BTCs need to be mapped and configured).
2. Must be tested.
3. Payment Factory resources must be trained.
CONS
1. Future format (European Commission might enforce it).
2. CAMT reporting statements are far richer, with additional information for reconciliation purposes that MT940 statements cannot provide.
3. CAMT reporting is capable to carry all bank account reporting with transaction hierarchies in a structured way.
4. Why not to aim for full XML choreography from pain to camt? Takeda needs to implement CAMT statements for Nordea. It is more expensive for Takeda to support dual infrastructures/formats.
5. Minimal configuration to implement CAMT statements (map the BTCs) since SAP already has the standard template after the SAP upgrade.
PROS
|2017.03 | Takeda global SAP FSCM solution
47
Disclaimer
SAP and all SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of
SAP AG. Product and service names mentioned are the trademarks
of their respective companies. Nor Adfahrer AB or any of the brands;
SBN, SDK or ADSIG is owned or controlled by SAP or any of the
other companies mentioned in this presentation.
Contact information is found on; www.adfahrer.com, www.sap-
sbn.no, www.sap-sdk.dk and www.adsig.se
or send an e-mail to [email protected]
|2017.03 | Takeda global SAP FSCM solution