Fraud Management Dashboard

Key Risk Indicators

KT Sessions
GL Account Balance KRI-s – Technical Overview Miguel Ferreira
Visio Diagram: Carmen Rodriguez
http://ecm.ctr.nestle.com/globelib/drl/objectId/0900f3d382155a76
GLOBE-BS-BA-D&B FC

Apr 10, 2024

Index
• GL Account Balance KRI-s
• Visio Document (Data Flow)
• Steering Information (extraction steering entries and reporting steering entries)
• Extraction
• Transformation
• Integration in KRI Repository - Aggregated KRI results
• Composite Providers for Aggregated results and Detailed Reporting
• Reporting
• Data load mechanisms: Quarter Process chains
• What to do if …?
• Additional Information

2 Apr 10, 2024

GL Account Balance KRI-s (1)
• KRI#4 – Write-off differences, deductions and bad debts is the KRI in scope. The risk captured in the KRI is
to raise abnormal levels in different types of write offs and Bad Debt related expenses for Receivable
Accounts (small differences, deduction purge, bad debt).
• Before automated Dashboard, Internal control built this KRI by manually extracting information from ERP by
means of t.code S_ARL_87012043. Value of KRI is captured via quarter snapshot.
Quarter snapshot is defined by the range of fiscal
periods & fiscal year indicated in selection criteria:
Manual execution of t.code S_ARL_87012043 Q1.2017
Fiscal year : 2017
Fiscal periods: 001 to 003

Q2.2017
Fiscal year: 2017
List of GL accounts in scope Fiscal periods: 004 to 006

Q3.2017
Fiscal year : 2017
Fiscal periods: 007 to 009

Q2.2017
Fiscal year : 2017
Fiscal periods : 010 to 0012

3 Apr 10, 2024

GL Account Balance KRI-s (2)
• For more details about KRI definition, check RDD link provided at the end of this presentation.
• KRI#4 is calculated as : [Debit – Credit]
• As part of BW Fraud dashboard, the scope for this KRI is to automate the calculation which was done
completely manually in the past, as explained in previous slide.
• Information provided by t.code S_ARL_87012043, exists already in BIM BW on multiprovider Y6FCHMC0.
• Flow FI GL Balances (Y6FCHMC0) exists only in BIM, therefore Fraud data flow to capture snapshot for this
KRI, extracts data from BIM , using query extraction approach.
 BW Fraud management flow in BIG, extracts data from Y6FCHMC0 flow, using query extraction approach.
 Infopackage for extraction performs dynamic selection on the characteristics required to filter (GL Account, Company code, fiscal
year, fiscal period and currency type). This dynamic selection is required to simulate same selection criteria used in manual
extraction.
• In next slides, it is provided full description of technical features of the data flow designed to capture
automatic quarter snapshot of this KRI.

4 Apr 10, 2024

Visio Document (Data Flow) 1
• One single flow has been built in BW BIG to produce this KRI.

• Data is extracted from BIM flow and pushed through data flow in BIG. Detailed data is pulled to Y3 layer.
From Propagation layer, information is aggregated in Y4 layer (KRI Fraud Repository)
• Same as for Overdue KRIs, in Design studio dashboard it is required to display aggregated results of the
KRI-s as well as detailed reporting. Detailed reporting is produced from Bex query Y6FC3CP0Q_001, built
on top of composite provider Y6FC3CP0, and aggregated results are produced from Bex query
Y6FC1CP0Q_002, built on top of Composite provider Y6FC1CP0. This last CP makes the union of all Y4
layers, which holds aggregated data using account model
• Full visio diagram in link below
http://ecm.ctr.nestle.com/globelib/drl/objectId/0900f3d382155a76

5 Apr 10, 2024

Visio Document (Data Flow) 2

Detailed information is extracted and pulled

in Y3 layer: 3 partitions of size small (Z) for 3
zones: ZA0 (EMENA), ZB0 (AOA),
ZC0(AMS). There is a forth partition (ZD0)
for the company codes in the Center, but
these comp. Codes are out of scope for
Fraud Project. It has been created just to
follow GLOBE Standards

Detailed data in Y3 layer is aggregated in Y4

layer using account model (KRI Fraud
Management Repository)

6 Apr 10, 2024

Steering Entries
• In full Fraud model we use B (Medium size) and Z (Small size) type partitions. The data flow for KRI#4 uses Z
partitions, due to small data volumes.
• In general, information for company codes belonging to the same Zone is stored in the same partition.
Therefore there are in total 4 partitions, one per zone (A0 – EMENA, B0-AOA, C0-AMS). An additional
partition is set up for the Center (D0), which is not loaded in the context of Fraud.
• There are 6 partition IDs set up:
 WFGBA – Partition type B EMENA
 WFGBB – Partition type B AOA
 WFGBC – Partition type B AMS
 WFGZA – Partition type Z EMENA (Partition used for KRI#4 structures)
 WFGZB – Partition type Z AOA (Partition used for KRI#4 structures)
 WFGZC – Partition type Z AMS (Partition used for KRI#4 structures)
 Any partition ID for the center has been set up, as any company code in the CTR is in scope for fraud management dashboard.
Steering values for company code are set up in table YEDW_STEER_VAL

• Split criteria used is 0COMP_CODE (as reflected in table YEDW_SPLIT_CRIT)

• Steering entries are maintained in table YEDW_STEER
• Steering information summarized in link below.
Load and Reporting Steering Entries Fraud Management (Vers. 1.0)
http://ecm.ctr.nestle.com/globelib/drl/objectId/0900f3d3820efbb3

7 Apr 10, 2024

Extraction (1)
• Extraction mechanism DS Y6FCHZX0 (BIM data
source)
• This DS is a BIM data source replicated into BIG.
In split environments (regression, pre-prod and
prod), the data source in BIG points to the
different BIM source systems

• This data source uses query extraction

mechanism using GLOBE class Extraction Structure
Data Source
YCL_EXTRACT_INFOPROVREAD
 Query for extraction: Y6FCHMC0Q_EXTRACT
 Function Module: Y6FCHZX0
 Extraction structure: Y6FCHZX0_EXT_STRUCT

8 Apr 10, 2024

Extraction (2)
• Function Module Y6FCHZX0 calls internally class
YCL_EXTRACT_INFOPROVREAD, which is
responsible to call the query to read, and pass
the parameters for selection.

• Query designed handles by itself steering values

for company code, via customer exit variable
YGTIPROV. This query must follow some rules:
 InfoProvider must be on the row section
 Characteristics in the row section must be set up to
«Display as key only»
 For characteristics in the row section, results row must
be supressed
 In column section we need to set the key figures to
extract This query exists only in
 In filter section all filters to be applied must be placed. BIM, same as data
The values to capture quarter snapshot will be handled source, as the extraction
by the data source (fields for selection) and will be is performed to BIG from
passed to these variables in the FM Y6FCHZX0 BIM track

9 Apr 10, 2024

Extraction (3)
• To make this extraction mechanims work it is required to maintain mapping entries in custom GLOBE table
YEDW_STEER_IREAD.
• ODSOBJECT -> Contains data source name
• INFOCUBE –> Contains multicube name
• IOBJNM_SOURCE -> Contains name of the field
to be extracted in the query.
• IOBJNM_TARGET -> Contains name of the field
in the extraction structure of data source.

Therefore this table contains the mapping between

the source objects (in the query) and the target object
(in the extraction structure).

10 Apr 10, 2024

Extraction (4)
• Calendar Year, Calendar year quarter and quarter are derived in FM
Y6FCHZX0, based on the values received in parameters fiscal year and
fiscal period:
 Fiscal period: 001.2017 TO 003.2017 & Fiscal Year 2017 -> Q1.2017
 Fiscal period: 004.2017 TO 006.2017 & Fiscal Year 2017 -> Q2.2017
 Fiscal period: 007.2017 TO 009.2017 & Fiscal Year 2017 -> Q3.2017
 Fiscal period: 010.2017 TO 012.2017 & Fiscal Year 2017 -> Q4.2017

11 Apr 10, 2024

Extraction (5)
• Custom configuration is required on InfoPackages for
dynamic selections.
 Data source replicated in BIG is linked to 3 different source systems
(EUROPE, AMS and AOA). Each DS is linked to one infopackage.
 To execute dynamic selections it is required some configuration
entries for each infopackage on YEDW_IP_ADD_SEL_TABLE
 Note that different infopackages are used for recovery purposes.

Dynamic selection via entries in YEDW_IP_ADD_SEL_TABLE

1. Fiscal Year -> Include program

YEDW_IPAC_STEERING_SEL,to derive value based on entries
in YEDW_IP_ADD_SEL table
2. Fiscal Period-> Include program YEDW_IPAC_STEERING_sEL
to derive value based on entries in YEDW_IP_ADD_SEL table.
3. GL Account -> Include program YEDW_IPAC_STEERING_sEL
to derive value based on entries in YEDW_IP_ADD_SEL table.
Only 11 GL accounts are in scope to calculat this KRI.
4. Currency Type-> Include program
YEDW_IPAC_STEERING_sEL to derive value based on entries
in YEDW_IP_ADD_SEL table.

12 Apr 10, 2024

Extraction (5)
• Entries required in YEDW_IP_ADD_SEL to
execute dynamic selection
 Function module YFC_FM_FL_ACCOUNT_IP retrives
dynamically the list of GL accounts in scope to calculate
the snapshot of this KRI. These GL accounts are
maintained in custom table YFCFM_FILTER_IP. This table
is also used to maintain GL accounts in scope for
calculation of KRIs 8-10 and 12, as explained in KT
Material for GR/IR KRIs-

 Function module YFC_FM_FISCAL_PERIOD_IP derives

the ranges of fiscal periods based on the quarter to be
loaded.

 Function module YFC_FM_FISCAL_YEAR_IP derives the

year based on the quarter to be loaded.

13 Apr 10, 2024

Transformation
Update DS -> into Y3 Layer
• Once extracted by data source
Y6FCHZX0, information mapped using 1:1
rule.
• Y3 layer -> Y3WDU
• 4 partitions have been set up, one for each
Zone and one for the CTR. This last
partition is not loaded.
 ZA0 EMENA
 ZB0 AOA
 ZC0 AMS

14 Apr 10, 2024

Integration in KRI Repository - Aggregated Results
Transformation Y3 -> Y4 Layer
• Information is transformed from Y3 to Y4 layer to keep in
Y4 only the operands (numerator and denominator)
required to calculate at query level the values of the KRIs.
• This KRI is calcuted as : [Debit – Credit]. In expert routine
YFC_Y3WDUZXX_Y4FCAZXX_TREX 0CREDIT is
mapped with target infoObject YCANUM01 and 0DEBIT
is mapped with target infoObject YCADEN01
• As explained in previous slides Y4 layer, so called Key
Risk Indicator Repository, is the layer where we
aggregate detailed information in Y3 layers from the
different flows to keep only the operands required
(numerator and denominator) required to calculate all
KRI’s in query Y6FC1CP0Q_002

15 Apr 10, 2024

Composite Providers Aggregated and Detailed Reporting
• Dashboard displays aggregated values and detailed reporting for this KRI as well .
 Aggregated results are displyed via Bex Query Y6FC1CP0Q_002, built on top of Composite Provider Y6FC1CP0
 Detailed Reporting for GL Account Balance is provided via bex query Y6FC3CP0Q_001 built on top of Composite Provider Y6FC3CP0.

Composite Provider Aggregated Results – Fraud KRI repository

Y6FC3CP0Q_001 - FCFM Write-off differences,

Composite Provider Detailed Reporting deductions and bad debts - Detailed view

16 Apr 10, 2024

Reporting Display at Zone Level
Aggregated Results
• KRI#4 – Write-off differences, deductions and bad
debts, is reported via Design Studio application
YGTSFC003.
 Values for the KRI (aggregated values) are displayed at
Zone, Market and Country level in Summary Tab in
Dashboard YGTSFC003. The source of data for this
aggregated view is Bex query Y6FC1CP0Q_002
Drill down to Market Level
Check list of Bex queries used in Dashboard in link below
Fraud Management Reporting Queries (Vers. 1.0)
http://ecm.ctr.nestle.com/globelib/drl/objectId/0900f3d3820f6500

Drill down to Country Level

17 Apr 10, 2024

Reporting
Detailed Reporting
• KRI#4 – Write-off differences, deductions and bad debts, is reported via Design Studio application YGTSFC003.
 Once at country level, user can click on any value for KRI#4 to display more detailed data at company code level.

By clicking on value for KRI#4 for any country, it will jump to Detailed
Country Level Reporting Level 2 - Query Y6FC3CP0Q_001. Debit- Credit results are
Query Y6FC1CP0Q_002 displayed for that particular country and for all GL accounts in scope

By clicking once more at country level, more granular data is displayed

at company code level.

18 Apr 10, 2024

Data Load Mechanisms: Quarter & Recovery Process Chains
Quarter Process Chains
KRI#4 data flow is loaded using metachains below. Each metachain loads one partition (EMENA, AMS, AOA).
Check in clink below scheduling details in Production NB3 and more detailed info of these chains.
Fraud Management Process Chains (Vers. 1.8)
http://ecm.ctr.nestle.com/globelib/drl/objectId/0900f3d38215500c

EUR Metachain AOA Metachain AMS Metachain

19 Apr 10, 2024

What to do if …?
Most common issues faced
• This section explains what to do in case of issues raised. This outcome is the result of most common issues
faced during hyper care period.
1. Company codes not reported in dashboard
2. Values not matching with ERP results
3. How to recover

20 Apr 10, 2024

Additional Information (1)
RDD Documents

General Document

Non-alert based KRI-s

Alert based KRI-s

21 Apr 10, 2024

Additional Information(2)
Visio Diagram
Fraud_Management_Dashboard (Vers. 1.5)
http://ecm.ctr.nestle.com/globelib/drl/objectId/0900f3d382155a76

Steering Entries and Partitioning used

Load and Reporting Steering Entries Fraud Management (Vers. 1.0)
http://ecm.ctr.nestle.com/globelib/drl/objectId/0900f3d3820efbb3

Bex Query list – List of Bex queries used in Design Studio YGTSFC003
Fraud Management Reporting Queries (Vers. 1.0)
http://ecm.ctr.nestle.com/globelib/drl/objectId/0900f3d3820f6500

Process chains and Recovery process chains

Fraud Management Process Chains (Vers. 1.8)
http://ecm.ctr.nestle.com/globelib/drl/objectId/0900f3d38215500c

KRI Classification Matrix

KRI Classification Matrix (Vers. 1.12)
http://ecm.ctr.nestle.com/globelib/drl/objectId/0900f3d3820fd74d

22 Apr 10, 2024

Additional Information(3)
KRI Calculation Matrix
KRI Definition Matrix (Calculation) (Vers. 1.9)
http://ecm.ctr.nestle.com/globelib/drl/objectId/0900f3d382119848

List of Company codes in scope

Company Codes in scope_reviewed_03.05.2017 (Vers. 1.0)
http://ecm.ctr.nestle.com/globelib/drl/objectId/0900f3d3820848e0

23 Apr 10, 2024

Q&A

24 Apr 10, 2024