Project - Nestle - FCL Stream - Fi Sub-Stream - Implementation of NDG 3.0

Project Title:
NDG 3.0 Program
FICO - reconciliation
Status: Premilinary
IBM CONSULTING
Nestlé Dolce Gusto 3.0 Program Version: 1.0
The official version of this document is stored : Yet to decide
Table of Contents
1 Document Information...................................................................................................... 4
1.1 About this Document.................................................................................................... 4
1.2 Who should use this Document...................................................................................4
1.3 Revision/Approval History............................................................................................4
1.4 References................................................................................................................... 4
1.5 Document Control Information.....................................................................................4
2 Overview.......................................................................................................................... 5
2.1 History/Background of the Project................................................................................5
2.2 Purpose/Goal of the Project.........................................................................................5
3 Roles & Responsibilities including Governance...............................................................5
3.1 Description................................................................................................................... 5
3.2 Project Governance..................................................................................................... 5
4 Project Status / Details..................................................................................................... 6
4.1 Project/Infrastructure Landscape :...............................................................................6
4.2 Current Status............................................................................................................ 10
5 Project Status / Details................................................................................................... 10
5.1 Lessons Learned....................................................................................................... 10
Page 2 of 20
IBM CONSULTING
Page 3 of 20
IBM CONSULTING
1 Document Information
1.1 About this Document
This document describes the project background and purpose as well as status in scope of work as part
of signed Service Agreement and it’s associated contract hierarchy. The process is agreed between the
Client and IBM.
1.2 Who should use this Document

The document will be used by IBM Deutschland GmbH as well as the client, which is defined in this
document as Nestlé GLOBE Center Europe
1.3 Revision/Approval History
Version Effective Date Summary of Author Reviewer Approver

number Changes <Name and <Name and Role> <Name and
Role> Role>
1.0 01.10.2022 Rajesh Pillai Mariana Hospodinova
1.4 References
Service Agreement
Assembly Factory Contract
General Service Agreement Nestlé
1.5 Document Control Information
At the end of this document is a labeled box indicating the end of text.
END OF DOCUMENT.
Page 4 of 20
IBM CONSULTING
2 Overview
2.1 History/Background of the Project

Nestlé Dolce Gusto products such as coffee capsules, coffee machines and accessories (cups, spoons, etc.) are sold
where in Consumer Orders are placed in the Web shops (Magento) and the fulfilment provider (3rd Party Logistics
providers) is processing these consumer orders, providing warehousing and is responsible for delivery to the
consumer. These sales are Direct sales to Consumer (D2C), meaning the consumer pays e.g. by credit card or debit
card.
The Dolce Gusto Direct to Consumer E2E then needs to reflect these Consumer sales into the SAP ERP system.
To that end, the (3rd Party) fulfilment provider is already providing, (by electronic message), every single
consumer’s order, which is posted in SAP via the so-called “after-the-fact” order-to-cash process (also called
“O2C Replay”).
2.2 Purpose/Goal of the Project
The aim of the current project is, as part of the NDG 3.0 Digital Transformation program, is to improve the E2E
process and achieve the resolution of a number of pain points and therefore a more seamless integration between
Magento, the 3PL, the Payment Service Provider (PSP) and the SAP-ERP back-end.
Two variations to implement are foreseen, and we align per market which finally will be taken
Variation1: The confirmation of orders delivered/despatched would continue to come from the 3PL
Variation2: The confirmation of orders delivered/despatched would come from Magento directly to SAP & no
longer from the 3PL
Variation 2 is the preferred model & is assumed to be one adopted, exceptions will be noted
3 Roles & Responsibilities including Governance
3.1 Description
Role Responsibility
Presentation of the FI Reconciliation
RBS FCL team
demo to the market
Address the queries, Guide the FI
reconciliation process to be followed.
RBS FCL team
Coordinate with local IT, and support
partners like IBM etc.
3.2 Project Governance
As a part of Project governance, meetings like Status on open items and closure updates, pre go live status, Go no-
go meeting, Post go live issue address and weekly combined status/ update for all countries (meeting by Cormac )
Page 5 of 20
IBM CONSULTING
Some details are below

Link to Jira: https://dsu-jira.nestle.biz/browse/NDGECERO-11860
Link Sharepoin:https://nestle.sharepoint.com/teams/DSUPPM/NDG30/SitePages/Home.aspx?
e=1%3Ac28ec854635a46548a72beb01e001ae2
Governance meetings:
NDG weekly catch up meeting for all countries: Conducted by Cormac. OHara
Attendee’s are:
Verma,Shraddha,DE-Frankfurt am Main,External;
Hospodinova,Mariana,PL-Warszawa, FCL
Ryfka,Rafal,PL-Warszawa, IT Supply Chain &Procurement;
Mallela,Shashank,DE-Frankfurt am Main,External, from messaging team.
Rajesh Pillai, FCL
NDG-Hungary-
IonelaVidrascuionela.vidrascu@mrm.comsoor@xs.nestle.com,László,Balázs,Balazs.Laszlo@hu.nestle.com
NDG-CZ/SK - Ales Homolka,Ales.Homolka@cz.nestle.com
NDG-Italy and Switzerland - Vladimir Ioan Purge,Vladimir.Purge@mrm.com
4 Project Status / Details

4.1 Project/Infrastructure Landscape:
Assumptions:
o No Development of the SAP-ERP, re-use of existing functionality & Interfaces.
o Master & Slave – Web-Ordering solution (Magento) ànd SAP-ERP

The main change in the project is the decision that the Web system is ‘Master’ and SAP-ERP, is the ‘Slave’ when
it comes to:
 Actual Demand (i.e. consumer places order)
 Pricing & discounting
 Order Tracking for the Consumer
 Managing Payments for the order via PSP Integration
 Registering & managing any forms of cancellations, payment deferrals or cancellations, claims etc
Features of the Project: Focus on standardization
 All pricing, discounting & VAT calculations need to be performed accurately in the Web system
 No re-calculations of any consumer-impacting values should be performed in SAP or in a 3P system.
This is to avoid any (rounding) differences or inconsistencies in the pricing which has been agreed with
the consumer
 3PL should not perform any other data transformations to ensure that SAP-ERP receives the correct data,
this should all be handled in the Web system in the future
 The SAP-ERP should therefore be set up in such a way that all values coming from the Web system can
be received into Manual Condition Types in the SAP Price Procedure of the sales order
 The logistics provider is not to be treated as the ‘customer’. Sales/Deliveries performed through the
logistics providers will be recognized against generic “Online Sales Customers” (One-time Customers).
 The Web Order # will be captured with each confirmed consumer order & will be the key transactional
identifier & link between the Web Ordering solution & other systems in the landscape
 Nestlé’s SAP-ERP receives information on the sales 1-to-1 on a daily basis with agreed level of detail
(consumer, country, item...).
 In addition to that the Inbound Movement, Quality Status Change, Master Data, etc... will be exchanged
at Physical Logistics (PLOG) level as they are already currently. No changes are expected in this area.
Page 6 of 20
IBM CONSULTING
Page 7 of 20
IBM CONSULTING
To activate the Credit Card tab (functionality) on the Sales order which ensures that as soon as the invoice is saved
an accounting document is created with the One-time customer account for that Payment Card showing as cleared.
This is the main difference in accounting in credit card processing, we are sure collect the fund as we have already
blocked it during authorization. Therefore, the customer account is cleared and an interim credit card settlement
account 1046200 is debited.
Dummy Example:
Table /GLB/OGTT_B2CCC: The aim of this config is to receive the credit card information from the web.
Page 8 of 20
IBM CONSULTING
Map IDOC segment fields

/GLB/E1EDK01_MKTFIELDS-FNAME = ""AUTH_REFNO""
/GLB/E1EDK01_MKTFIELDS-FVALUE = XXXXXXX à PAYID field value
Map segment field E1EDK36-EXDATBI = "209912"
Mapping the PAYID therefore automatically triggers the activation of the Credit card functionality and needs to be
planned accordingly with the config and the readiness of the business
4.1.1 Payment terms
The Payment term is maintained on the One time Customer master record and will therefore be copied into the
Sales order as provided by the Customer master.
For the One-time Customer with Credit Card payment method there can be payment term with a certain percentage
of accrual for the Credit card fee (Merchant Service fee depending on the payments processing provider). This fee
will be transferred into the Z915 Merchant Service Fee Pricing Condition type in the Sales Document as accrual.
Using a Payment Term with the correct % is instrumental to facilitate Payment reconciliation. Therefore, we
recommend to create a One-time customer for each % fee. New Payment terms will need to be added via
CONFWR.
B2C payment terms already existing in GLOBE are:
PayT Own explanation

ZST1 B2C Credit Card Fee 2% (Fee accrual)
ZST2 B2C Credit Card Fee 0.3% (Fee accrual)
ZST3 B2C Debit Card Fee 1.10% (Fee accrual)
ZDG1 DG Credit Card Fee 1.7% (Elavon Fee accrual)
ZDG2 DG Credit Card Fee 0.27% (BNP Fee Accrual)
ZDG3 DG Credit Card Fee 2.19% (Bank & Ogone Fee accrual
ZDG4 DG Credit Card Fee 1.55% (bank charge fee accrual)
ZDG5 DG Credit Card Fee 2.6% (Bank & Ogone Fee accrual)
ZDG6 DG Credit Card Fee 1.65% (Bank Fee accrual).
ZDG0 Payment Term - Market Place CNOVA
As all orders will be captured against 1-time customers, there will be no need to have any credit control facility. In
the case of credit card, there will be a specific Payment term to determine the Merchant Service Charge.
Page 9 of 20
IBM CONSULTING
Invoice Creation
This area also is not changing & no specific set-up is required in SAP.
An exception here can be Portugal, where the legal invoice needs to be produced out of SAP. For the rest of the
markets, where Magento will produce the invoice, SAP’s Invoice is there to complete the Replay & formally
register sales & the Open Items in Finance against which the PSP Payments will be applied
Invoice creation will be done fully automatically by the system via a batch job.
Printing of invoices is not necessary from SAP as the Invoices will be sent to the Consumer via mail / made
available in the Consumer Web shop account. Printing by the 3PL to accompany the goods is assumed not required
in most countries.
No Credit Memos will be printed or sent to the Consumers from SAP as the Invoices (Credit notes) will be sent to
the Consumer via mail / made available in the Consumer Magento account. Printing by the 3PL to accompany the
goods for the Replacement Free of Charge is assumed not required in most countries.
4.2 Current Status
Status Date Description

01.10.2022 Post April 2022
the following markets are live
Hungary,
Poland,
Switzerland
Italy
First half of 2023 Iberia, CZ and SK wil go live.
5 Project Status / Details
5.1 Lessons Learned
Once project or project phase is completed, please document the lessons learned for future references.
Project The interaction between markets is very minimal and should be increased. Since we are
Phase implementing same solutions in different markets, more frequent discussion between them
will help to deliver faster and error free solution.
Design
This is to describe and map the FICO process setup which is currently used for the B2C E2E
process flow web sales to consumers and GLOBE implementation setup.
Page 10 of 20
IBM CONSULTING
Sales will be rolled-up individually for each destination market, based on the detailed
information provided by the 3rd Party logistics fulfilment provider (3P) / payment service
provider (PSP), via existing and widely used GLOBE functionality.
Individual consumer details are not stored in GLOBE via a sold party customer but rather via
One-time-customers (Z006- Miscellaneous Customer). A dummy customer will be created for
every company code by each business unit (NDG /Special T, etc.)
For reconciliation and reporting purposes, it is important to gather all relevant information
related to each individual sale in Globe, hence all transactional sales orders will be recorded in
SAP on a daily basis.
This will mirror one by one the sales in the Web application.
To identify each sales and to reconcile individual invoices booked in 3P system a unique PO
number needs to be provided by 3P for every order IDOC and will be stored in sales order “PO
number” field in GLOBE as web order number.
Three scenarios can be defined for most of the B2C process:
Scenario: Payment by Credit card

Consumer is going to web side placing an order.
Payment is authorised immediately.
Scenario: Payment by Debit card

Payment is authorised immediately.
Scenario: Payment by paper invoice

Payment will be authorised later, but before goods are dispatched.
• Sales will be rolled-up individually for each destination market, based on the detailed
information provided by the 3rd Party logistics fulfilment provider (3P) / payment
service provider (PSP), via existing and widely used GLOBE functionality.
• Individual consumer details are not stored in GLOBE via a sold party customer but
rather via One-time-customers (Z006- Miscellaneous Customer). A dummy customer
will be created for every company code by each business unit (NDG /Special T, etc.)
• For reconciliation and reporting purposes, it is important to gather all relevant
information related to each individual sale in Globe, hence all transactional sales
orders will be recorded in SAP on a daily basis.
• This will mirror one by one the sales in the Web application.
• To identify each sales and to reconcile individual invoices booked in 3P system a
unique PO number needs to be provided by 3P for every order IDOC and will be
stored in sales order “PO number” field in GLOBE as web order number.
•
Page 11 of 20
IBM CONSULTING
Activation of Credit Card functionality in SAP-ERP
• In order to enable the automatic reconciliation of Invoices, Cash collected, and Bank
Statement in SAP-ERP the Credit Card Functionality in SAP-ERP will be activated.
• As soon as the invoice is saved an accounting document is created with the XREF3
field populated with the Web-order number and the One-time customer account for
that Payment Card shows as cleared.
• This is the main difference in accounting in credit card processing, we are sure to
collect the funds as we have already blocked it during authorization. Therefore, the
customer account is cleared and an interim credit card settlement account 1046200 is
debited.
• Balance of one-time customer line no 1 vs line no 10 will be 0. Hence the follow up
on the money will be on payment account 1046200. This is another big difference to
the process before.
Page 12 of 20
IBM CONSULTING
Testing
Page 13 of 20
IBM CONSULTING
Page 14 of 20
IBM CONSULTING
Page 15 of 20
IBM CONSULTING
Page 16 of 20
IBM CONSULTING
Page 17 of 20
IBM CONSULTING
Page 18 of 20
IBM CONSULTING
Implement A) Sales and Distribution->Billing->Payment Cards-> Authorization and

ation Settlement> Maintain Clearing House> Account Determination> Assign
G/L Accounts> Sales org./Currency/Type
Here card type B2C will be used.
B) Sales and Distribution /Billing/ Payment cards/ Authorization and

Settlements/ Maintain Clearing House/ Set Authorization/ Settlement
control per account
C) /GLB/RGTT_B2C Table maintenance
D) GLOBE Extension / Finance and Controlling / Accounting Operations /

Travel and Expenses / Prepare Automatic Clearing (Company level)
E) Table maintenance /GLB/OGTT_B2CCC for assignment of Sales org and

payment card
F) Maintain table /GLB/RGTT_ACC_D - The aim is to copy the fields XREF1

/ XREF3 to the line of G/L Account 1046200.
G) Financial Accounting/ Financial Accounting Global

Settings/Tools/Validation/Substitution/Substitution in Accounting
Documents- The aim of this User Exit is to active the logic to get the
contract number from the text of the bank Statement and add it into the
field XREF2.
Stabilizatio
n
There was no design showstopper during Hypercare and normal issues were
reported related to idoc failure due to master data etc or rounding off for files
from Source like Adyen etc.
Closure
Project is still in Hypercare stage.
END OF DOCUMENT.
Page 19 of 20
IBM CONSULTING
Page 20 of 20

Project - Nestle - FCL Stream - Fi Sub-Stream - Implementation of NDG 3.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project - Nestle - FCL Stream - Fi Sub-Stream - Implementation of NDG 3.0

Uploaded by

Copyright:

Available Formats

Project Title:

NDG 3.0 Program

The official version of this document is stored : Yet to decide

1.2 Who should use this Document

1.3 Revision/Approval History

Version Effective Date Summary of Author Reviewer Approver

1.0 01.10.2022 Rajesh Pillai Mariana Hospodinova

1.5 Document Control Information

2.1 History/Background of the Project

2.2 Purpose/Goal of the Project

3 Roles & Responsibilities including Governance

3.2 Project Governance

Some details are below

NDG-CZ/SK - Ales Homolka,Ales.Homolka@cz.nestle.com

NDG-Italy and Switzerland - Vladimir Ioan Purge,Vladimir.Purge@mrm.com

4 Project Status / Details

o No Development of the SAP-ERP, re-use of existing functionality & Interfaces.

o Master & Slave – Web-Ordering solution (Magento) ànd SAP-ERP

Features of the Project: Focus on standardization

Map IDOC segment fields

4.1.1 Payment terms

B2C payment terms already existing in GLOBE are:

PayT Own explanation

4.2 Current Status

Status Date Description

First half of 2023 Iberia, CZ and SK wil go live.

5 Project Status / Details

5.1 Lessons Learned

Three scenarios can be defined for most of the B2C process:

Scenario: Payment by Credit card

Scenario: Payment by Debit card

Scenario: Payment by paper invoice

Activation of Credit Card functionality in SAP-ERP

Implement A) Sales and Distribution->Billing->Payment Cards-> Authorization and

Here card type B2C will be used.

B) Sales and Distribution /Billing/ Payment cards/ Authorization and

C) /GLB/RGTT_B2C Table maintenance

D) GLOBE Extension / Finance and Controlling / Accounting Operations /

E) Table maintenance /GLB/OGTT_B2CCC for assignment of Sales org and

F) Maintain table /GLB/RGTT_ACC_D - The aim is to copy the fields XREF1

G) Financial Accounting/ Financial Accounting Global

Project is still in Hypercare stage.

You might also like