SAP HANA Functional Design:

MCHI – Returns Refusals and Credit Memos

GFCF Control

OTB C4.1b
Blocked returns or refusals sales orders are reviewed independently before they are released in SAP. Discrepancies
are investigated and resolved.

OTB C4.1c -
Returns or refusals sales orders below the pre-defined threshold for automatic blocking are independently reviewed
in aggregate.  Discrepancies are investigated and resolved.

BTC C1.2b
Blocked credit memo requests are reviewed independently before they are released in SAP. Discrepancies are
investigated and resolved.

BTC C1.2c
Credit memo requests below the pre-defined threshold for automatic blocking are independently reviewed in
aggregate. Discrepancies are investigated and resolved.

Page 1 of 15
Page 2 of 15
Document Control
Document Preparation
Date Version Name Role Comments
21-Sep- 1.0 Raghavendran Functional
2018 Gundurao

Document Review
Versi
Date Name Role Comments
on

Document Approval
Date Version Name Role Comments

Page 3 of 15
Table of Contents
DOCUMENT CONTROL...................................................................................................................................................2
1 OVERVIEW AND SCOPE.........................................................................................................................................5
1.1 FUNCTIONAL DESCRIPTION AND SCOPE................................................................................................................5
1.1.1. REQUIREMENTS:................................................................................................................................................5
1.2 DEPENDENCIES / CONSTRAINTS.............................................................................................................................5
1.3 ASSUMPTIONS........................................................................................................................................................5
1.4 EXTENSION USAGE................................................................................................................................................5
2 DETAILED FUNCTIONALITY................................................................................................................................6
2.1 FUNCTIONAL SPECIFICATION.................................................................................................................................6
2.2 PROCESS FLOW DIAGRAM.....................................................................................................................................7
2.3 DATA MODEL........................................................................................................................................................8
2.4 A4O AND TABLEAU DASHBOARD.........................................................................................................................8
2.5 GEOGRAPHY HIERARCHY DATA UPLOAD.............................................................................................................8
2.6 DIMENSIONS AND KEY FIGURES FOR TREND DETAILS.........................................................................................9
2.7 DATA DICTIONARY................................................................................................................................................9
2.8 MASTER TABLES..................................................................................................................................................12
2.9 INPUT AND OUTPUT.............................................................................................................................................13
2.10 REPORTING..........................................................................................................................................................13
2.11 INITIAL DATA SET-UP / CONVERSION REQUIREMENTS.......................................................................................13
2.12 NETWORK INTEGRATION.....................................................................................................................................13
2.13 EXISTING SAMPLE PROGRAMS............................................................................................................................13
2.14 SECURITY AND AUTHORISATION.........................................................................................................................13
2.14.1 Segregated Access Requirements for Users into Single Roles...................................................................13
2.14.2 Risk Assessment and Considerations for the Access Required..................................................................14
2.14.3 Users, Teams, Jobs where access is required............................................................................................14
2.14.4 Objects to be authority-checked.................................................................................................................14
2.14.5 Authorization Design:................................................................................................................................14
2.9.6 Security and Authorization for the Vendor AM Team................................................................................14
2.15 PROCESSING AND OPERATIONAL CONSIDERATIONS............................................................................................14
2.15.1 Performance...............................................................................................................................................14
2.15.2 Batch Requirements...................................................................................................................................14
2.15.3 Data Maintenance Requirements...............................................................................................................14
2.15.4 Re-Use Details...........................................................................................................................................14
2.15.5 Error Handling..........................................................................................................................................14
2.15.6 Log Output.................................................................................................................................................14
2.15.7 Purge and Archive Considerations............................................................................................................14
2.16 DESIGN ALTERNATIVES.......................................................................................................................................14
2.17 KEY TEST CONDITIONS AND CONSIDERATIONS..................................................................................................14
OPEN POINT.......................................................................................................................................................................15

Page 4 of 15
1 Overview and Scope

1.1 Functional Description and Scope

Business needs a report that will bring information on the following documents created for the month.
 Returns – Customer returns the product that was received by him in the past
 Refusals – Customer refuses to accept the shipment and hence the products are returned to
Unilever Site
 Credit Memos – Standlone Credit Memos created to handle any price / quantity / others
discrepancies.

1.1.1. Requirements:
These reports will benefit significantly from HANA acceleration and enable business teams to perform to a
higher standard. The proposed user interface is Analysis for Office (A4O) and Tableau as this provides a
flexible user interface, giving the power to business users to obtain and interpret the data as required
without further development.

1.2 Dependencies / Constraints

N/A.

1.3 Assumptions

Data loaded into HANA through ECC tables will only be used for reporting.

1.4 Extension Usage

N/A.

Page 5 of 15
2 Detailed Functionality
2.1 Functional Specification

The report should list out all the orders information created fort the selection period. Users should have the
flexibility to run the report in A4O by

 Cluster
 Country
 Entity
 Sales Org
 Distribution channel
 Division
 Customer type

Only those order types that belong to Returns, Refusals and Credit Memos must be considered for this report.
The order types in scope for this report are :

Instance Fusion Instance U2K2

Order
Type Description Order Type Description
ZR01 HLL GT Returns Order RK Invoice Correct. Req
ZR02 HLL Manual Rtn Order YCR Credit Memo Req.
ZR03 HLL Memo Rtn Order ZRE Non-delivery returns
ZR04 HLL DSM Rtn Order ZNON Returns Order
YDR
ZR05 HLLDirDisptchRtnOrd

ZR06 HLL Institl Rtn Ord

ZR07 HLL MT Returns Order
ZR08 HLL CSD Return Order
ZR09 HLL DmgReturns Order
ZR10 HLL FRMS Rtn Order
ZR13 FRMS SubItm RtnOrder
ZR19 HLL Loose Pcs Return
ZR22 HLL RMPM Returns
ZR28 HLL Water Rtn Order
ZR33 HLL Ex Dome Ret sale
ZR51 LLPL Fr Return Order
ZRL1 SL GT Returns Order
ZRL2 SL Manual Rtn Order
ZRL3 SL Memo Rtn Order
ZRL7 SL MT Returns Order
ZRL9 SL Loose Pcs Return

Page 6 of 15
 Instance Cordillera Instance Sirius
Order
Order Type Description Type Description
Credit Memo
CR Request ZA10 Consignment Returns
RK Invoice Correct. Req ZB1 Returns /Del rel bil
Consignment
ZA10 Returns ZB3 3rd Party Return
ZB3 3rd Party Return ZB4 Refusal w/o Double
MSO Return
ZB6N Int.Order ZB5 Refusal ref to order
3rdPty Cust
ZCC Crd(PGM) ZB6M Return to intr.Order
Credit Memo
ZCR Request ZB6 MSO Return Int.Order
Credit Memo Req.
ZCRM man ZB6N MSO Return Int.Order
ZCU Unsaleables ZB9 Indirect Return
Freezer Damages
ZDCR Cred ZCR Credit Memo Request
ZRTF Returns to DC ZCRK Invoice Correct. Req
ZRTR Returns LA ZCRM Credit Memo Req. man
ZVOC Sundry Credit Req ZCRS CreditMemo Req. Shop
DR YB1 Returns/Intern.Cust
ZSPC YCR CM req./Intern. cust
ZDRM YCRM CreditMemoReq.manInt
ZVOD YDR
ZDR ZDRM
ZDRR
ZDR
ZDRK
ZDR
ZDRK

2.2 Process Flow Diagram

Data Extraction:

ECC
-Cordillera A4O
SLT Replication SAP
-U2K2 Transactional Tablea
Server HANA
-Sirius Data u
-Fusion Page 7 of 15
 2.3 Data Model

Sample Extract from CMIR is attached

MCHI_Sales
Reversals - Aug'18_ Sample1.xlsx

2.4 A4O and Tableau Dashboard

 The interface should open to a dashboard which is excel like tool, displaying report as a tabular line
item data.First login should report at a landscape level. User should then have the option to save
default parameters when opening the dashboard.
 User will get a input prompt to execute report at
 Cluster
 Country
 Entity
 Sales Org
 Distribution Channel
 Division

Page 8 of 15
  Customer Type

2.5 Geography Hierarchy Data Upload

 Changes to Geography Hierarchy will be done by the Basis team through a service request. This will
be done by HANA team with incident assigned to HANA model group.
 A customized table for Customer types, document types will be created in HANA
 There will be option for incremental uploads or incremental deletes
 The following fields to be included in the report

Field Field Description DataType Width Validation

Should be
validated with
Sorg Sales org CHAR 4
BUKRS in T001
table

Sorg name Sales org name CHAR 30  

Country Country CHAR 20  

Country Group Country Group CHAR 20  
MCO MCO CHAR 30  
Market Cluster Market Cluster CHAR 25  

SAP Instance SAP Instance CHAR 10  

Active Active Boolean 3 Yes/No
Group Currency Group Currency CHAR 3  
BCS BCS Boolean 1  

2.6 Dimensions and Key Figures for Trend Details

N/A

2.7 Data Dictionary

The data dictionary is the catalogue that includes the data elements needed for reporting. The tables below
outline all of the data elements which will be included in each of these domains.

Selection Criteria
User can run the dashboard with standard filters provided by A4O and can apply to all views or the current
view.

Page 9 of 15
User will get a input prompt to execute report at
 Cluster
 Country
 Entity
 Sales Org
 Distribution Channel
 Division
 Customer Type

Report Output :
  SAP Table          
Field Outpu Mandator
Description Table Field t Filter Caclulated y Comments
See Geography
Cluster     Yes Yes Yes No Hierarchy Sheet
See Geography
Hierarchy Sheet.
This field is
needed only for
SU / MCO *     Yes Yes Yes No Sirius.
Reporting Date     Yes Yes Yes Yes Report run date
Standard SAP
HANA query can
Country T001 LAND1 Yes Yes No No return the info
Standard SAP
HANA query can
Country return the info
Description T005T LANDX Yes Yes No No (SPRAS=EN)
Sales
Document VBAK VBLEN Yes Yes No No  
Created on VBAK ERDAT Yes Yes No No  
Time VBAK ERZET Yes Yes No No  
Created by VBAK ERNAM Yes Yes No No  
Document
Date VBAK AUDAT Yes Yes No No  
SD document
category VBAK VBTYP Yes Yes No No  
SD document Table attached in
category Desc VBAK VBTYP Yes Yes No No Section 2.8
Sales
Document
Type VBAK AUART Yes Yes No No  
Sales TVAKT BEZEI Yes Yes No No Pass Sales org &
Document SPRAS=EN

Page 10 of 15
Type
Description
Order reason VBAK AUGRU Yes Yes No No  
Pass Order
Order reason reason and
Description TVAST VTEXT Yes Yes No No SPRAS=EN
Net value VBAK NETWR Yes Yes No No  
Absolute of Net
Value. If Net
Value is Positive,
change the sign
and display this
Net value (Abs) VBAK NETWR Yes Yes Yes No field as positive.
Net Value (Abs)
divided by a
Millions Calc Calc Yes Yes Yes No Million
Document
Currency VBAK WAERK Yes Yes No No  
Sales
Organization VBAK VKORG Yes Yes No No  
Sales Org Table attached in
Name Table Table Yes Yes No No Section 2.8
Distribution
Channel VBAK VTWEG Yes Yes No No  
Division VBAK SPART Yes Yes No No  
Pass Sales Doc
Order rel bill Type to TVAK and
type TVAK FKARA Yes Yes No No pull FKARA
Purchase order
no VBKD BSTKD Yes Yes No No  
Sold-to party VBAK KUNNR Yes Yes No No  
CustomerName KNA1 NAME1 Yes Yes No No  
CCode to be
billed VBAK BUKRS_VF Yes Yes No No  
Company Code
Description T001 BUTXT Yes Yes No No  
Month VBAK ERDAT Yes Yes No No Select Month
Year VBAK ERDAT Yes Yes No No Select Year

Page 11 of 15
 . Pass Sold to
Party to KNB1
and select AKONT
. If AKONT is 133*
or 114* Print "3P
Trade "
. If third and
fourth digits are
17 Print
"InterCompany"
. For rest, Print
Customer Type KNB1 AKONT Yes Yes No No "Others"
Cordillera /
SAP SAP U2K2 / Sirius /
Instance Instance Instance Yes Yes No No Fusion
Net value Net Value (Abs)
Thousands Calc Calc Yes Yes Yes No divided by 1000
Bucket them
under these
categories based
on net value
<0.1K
>5K
0.1K-0.2K
0.2K-0.5K
0.5K-1.0K
1.0K-2.0K
2.0K-3.5K
Value Bucket Calc Calc Yes Yes Yes No 3.5K-5.0K
Refer to Section
Conv rate Calc Calc Yes Yes Yes No 2.8
Net Value (ABS) /
Conv Rate / 1
Euro(Mio) Calc Calc Yes Yes Yes No Million

2.8 Master Tables

We need below tables to be referred in A4O to pull description of elements like Sales Org, Sales Order Type
and Values in Euro etc..

 Sales Document Category Desc Table

Page 12 of 15
 Sales Doc
Category.xlsx

 Sales Org Desc Table – Refer to all 4 sheets

Sales Org
Desc,Currency Conv.xlsx

 Currency Conversion Table

Two tables need to be used for Currency Conversion.
Table 1 has mapping between Reporting Year and Currency Base Year.
Table 2 to be used for fetching relevant conversion rate based on the currency base year.

1.Rep Year-Curr 2.Curency

Base Year Mapping.xlsx
Master-Multi Year-Updated.xlsx

2.9 Input and Output

N/A

2.10 Reporting

As discussed in section 2.1.

2.11 Initial Data Set-Up / Conversion Requirements

SLT replication that is currently available for all landacapes and new replication that needs to be setup is
mentoioned in the attached file

2.12 Network Integration

N/A.

2.13 Existing Sample Programs

N/A

2.14 Security and Authorisation

To be discussed.

Page 13 of 15
2.14.1 Segregated Access Requirements for Users into Single Roles
N/A

2.14.2 Risk Assessment and Considerations for the Access Required

2.14.3 Users, Teams, Jobs where access is required

N/A

2.14.4 Objects to be authority-checked.

N/A

2.14.5 Authorization Design:

N/A

2.9.6 Security and Authorization for the Vendor AM Team

N/A

2.15 Processing and Operational Considerations

2.15.1 Performance
N/A

2.15.2 Batch Requirements

N/A

2.15.3 Data Maintenance Requirements

N/A

2.15.4 Re-Use Details

N/A

2.15.5 Error Handling

N/A

2.15.6 Log Output

N/A

2.15.7 Purge and Archive Considerations

N/A

2.16 Design Alternatives

N/A.

2.17 Key Test Conditions and Considerations

Below are the key test conditions. Detailed test conditions will be created as part of unit and product testing.

Page 14 of 15
 No. Description Expected Result
1 A4O Dashboard Dashboard should appear for the Volumes under
 Cluster each ageing bucket as on key Date
 Country
 Entity
 Sales Org
 Distribution Channel
 Division
 Customer Type
 Run the Returns, Refusals and Credit Report was run successfully.
Memos report in the Dashshboard with
ECC
 HANA Output should match with existing Report was run successfully. Data matches with
CMR report ECC.

Open point

Page 15 of 15