Application Information Document

SAP Manufacturing Intelligence and Integration

MARICO Confidential Page 1 of 17

Marico Information classification: Official

 Document Control Section

Authors

Name Title/ Role Date

Srisailam Golla Team Member / SPOC 08/08/2023

Reviewers
This document requires following Reviews.

Name Title/ Role Date of Review

Murali Krishna IT Manager - Projects 10/08/2023

Approvals
This document requires following Approval.

Name Title/ Role Date of Approval

Murali Krishna IT Manager - Projects 10/08/2023

Document Location
Lotus Connection/Share point

MARICO Confidential Page 2 of 17

Marico Information classification: Official

 Revision History
Version # Description of Changes Issue Date
V1.0 Initial-Draft 07/08/2023
V1.1 Updated with more segments 08/08/2023

MARICO Confidential Page 3 of 17

Marico Information classification: Official

 Table of Contents
1. OBJECTIVES....................................................................................................................................5

2. TERMINOLOGY AND ACRONYMS............................................................................................6

2.1 OVERVIEW....................................................................................................................................7
2.2 COMPANY.....................................................................................................................................7
2.3 SAP R/3.......................................................................................................................................7
2.4 MODULES IMPLEMENTED.............................................................................................................7
3. SAP R/3 PLATFORM AND SAP MII PLATFORM.....................................................................8
3.1 R/3 LANDSCAPE...........................................................................................................................8
3.2 MII LANDSCAPE...........................................................................................................................8
3.3 DATABASE/ CLIENT SERVER........................................................................................................9
4. MII & PP/QM/QM/SHOP FLOOR INTEGRATION FLOW DIAGRAM...............................10
4.1 SAP MII & PP INTEGRATION....................................................................................................10
4.1.1 SAP PP Master data for MII/OEE application.....................................................................10
4.1.2 Business process flow............................................................................................................10
4.2 SAP MII INTEGRATION WITH SAP QM.....................................................................................12
4.3 MII & SHOPFLOOR INTEGRATION..............................................................................................13
4.4 MII & EWM INTEGRATION.......................................................................................................13
4.5 MII APPLICATION MONITORING AND DAILY SCHEDULING JOBS.................................................13
4.6 MII APPLICATIONS LANDSCAPE..................................................................................................14
4.7 EXCEPTION AND ERROR HANDING IN MII..................................................................................14
5. APPLICATION HISTORY............................................................................................................15
5.1 TYPICAL PROBLEMS...................................................................................................................15
5.2 RELEASE HISTORY.....................................................................................................................15
5.3 MAINTENANCE HISTORY............................................................................................................15
6. REFERENCE DOCUMENTS........................................................................................................16

MARICO Confidential Page 4 of 17

Marico Information classification: Official

 1. Objectives
The objective of the Application Information Document (AID) is to provide members of the delivery
team with an overview of SAP MII Module.

The AID describes overview of SAP implemented for MARICO and its different modules, components/
business flows. It also captures critical business processes/ custom transactions & its configuration/
technical details. Various critical R/3 components and its functionalities are detailed out that are
necessary from support perspective.

This document will also refer to any existing related documentations and will be used in conjunction
with the Application Support Control Plan (ASCP) to support the module.

The delivery team will keep the AID throughout the life of the SAP MII Application .

MARICO Confidential Page 5 of 17

Marico Information classification: Official

 2. Terminology and Acronyms

Acronyms and terminology specifically used in this document are described below. Other acronyms commonly
used can be found in the ASCP.

No. Terminology / Definition

Acronyms

1 AID Application Information Document

2 ASCP Application Support Control Plan

4 GDC Global delivery Center

5 RKT Remote Knowledge Transfer

6 MII Manufacturing Intelligence and Integration

7 PP Production Planning

8 QM Quality Management

9 EWM Extended Warehouse Management

10 NWA NetWeaver Administration

11 POD Production Operation Dashboard

MARICO Confidential Page 6 of 17

Marico Information classification: Official

 2.1 Overview
Marico is an Indian consumer goods company providing consumer products and services in the areas of
Health and Beauty based in Mumbai.

During 2015, the company generated a turnover of Rs. 5,733 crore. Marico has 8 factories in India
located at Pondicherry, Perundurai, Kanjikode, Jalgaon, Paldhi, Dehradun, Baddi and Paonta Sahib.

In Bangladesh, Marico operates through Marico Bangladesh Limited, a wholly owned subsidiary. Its
manufacturing facility is located at Shirirchala, near Gazipur
2.2 Company
Marico has a significant presence in Bangladesh, South East Asia, Middle East, Egypt and South Africa
The organization holds a number of brands including Kaya Limited, Parachute, Saffola, Hair & Care,
Nihar, Mediker, Revive, Manjal, Livon, Set Wet, Zatak, Fiancee, HairCode, Eclipse, X-Men, Hercules,
Caivil, Code 78 and Black Chic etc.

2.3 SAP R/3

Marico has implemented SAP long back around in 2001 and recently in 2015 they have
migrated to SAP HANA. They have implemented below modules in SAP.

2.4 Modules Implemented

 Finance (FI)
 Controlling (CO)
 Material Management (MM)
 Production and Planning (PP)
 Sales and Distribution (SD)
 Quality Management (QM)
 Warehouse Management (WM)
 Manufacturing Integration and Intelligence (MII)

MARICO Confidential Page 7 of 17

Marico Information classification: Official

 3. SAP R/3 Platform and SAP MII Platform
Marico uses ECC 6.0 version with EHP 7.

3.1 R/3 Landscape

Landscape – It has 3 systems which includes Development, Quality & Production system. Below
details show the system with its IP

MIP- client 400-Production system

MIA -client 400—Quality system
MIT-client 200— Development system
MIT-client 400- Test server

MIP- client 300-Production system MIP 113.2.8.1 00

MIP- APP1 client 300-Production system MIP 113.2.8.3 00
MIA -client 400—Quality system MIA 10.135.10.46 00
MIT-client 200—Test Server MIT 10.135.10.36 00
MIT –Client 400-Development system MIT 10.135.10.36 00
3.2 MII Landscape

MII 10.142.37.20
HANA 10.142.37.21:31015
DEV PCO 10.142.37.24
EWM 10.142.37.18/400/00
ECC 10.136.10.7/580
SANAND
MII 10.142.37.22
HANA 10.142.37.23:31215
PROD PCO 10.142.37.24
EWM 10.142.37.16/400/00
ECC 10.121.26.22/580
MII 10.136.10.9
HANA 10.121.23.16:30615
DEV
PCO 10.142.13.99
ECC 10.136.10.7/580
PDRI
MII 10.121.26.29
HANA 10.136.10.72:30415
PROD
PCO 10.142.13.99
ECC 10.121.26.22/580

MARICO Confidential Page 8 of 17

Marico Information classification: Official

 3.3 Database/ Client Server
Recently they have migrated to SAP HANA database.

MARICO Confidential Page 9 of 17

Marico Information classification: Official

 4. MII & PP/QM/QM/Shop Floor Integration flow diagram
SAP MII integration with SAP PP/QM and SAP EWM.

4.1 SAP MII & PP Integration

4.1.1 SAP PP Master data for MII/OEE application
 Material Master – MATMAS IDOC
 Work Center Master-LOIWCS
 Plant Hierarchy - /OEE/PLANT_HIERARCHY
 Production Order LOIPRO01
4.1.2 Business process flow
 On order release in ECC, LOIPRO idoc reaches to SAP MII message monitor.
 Based on message type MII/OEE workflow will trigger and store order data to HANA DB
 Based on planned date and shift order details will be visible in the Production order dashboard.
 Operator can Start/Hold/Complete Orders in OEE POD
 OEE is calculated based on execution or production orders in OEE POD

MARICO Confidential Page 10 of 17

Marico Information classification: Official

 Production
order Production Operator Start Order Order
Hold/Complete
create,release order stored in choose work produciton for a Completion in confirmation in
Order in POD
and EWM MII center order MII OEE POD ECC
stagging

POD layout looks like below – Operator POD

POD – Manage Orders

Select Start/ Operator

Open Select
work Hold start
Operator required
center and /Complete working
Dashboard order
shift Order on Order

List of BAPI/RFC call in SAP ECC,

MARICO Confidential Page 11 of 17

Marico Information classification: Official

 Outbound from MII to ECC - RFC
BAPI BAPI Desc
BAPI_PRODORDCONF_CREATE_HDR Enter Order Confirmation
BAPI_ALM_ORDER_GET_DETAIL Reading of detail data for an Order
BAPI_ALM_NOTIF_DATA_MODIFY PM/CS Notification Change data
BAPI_ALM_NOTIF_SAVE Save PM/CS Notification
ZZQPL1_INITIALIZE Initialize the function group
Automatic Generation of Inspection lots from
ZZQPL1_INSPECTION_LOT_CREATE
goods movement, delivery notes
ZZQPL1_UPDATE_MEMORY Writing Inspection Lot data to memory
ZZQPL1_INSPECTION_LOTS_POSTING Posting of all inspection lots in memory
QIRF_SEND_CATALOG_DATA2 Transfer of catalog entries
Transfer of catalog entries
QIRF_SEND_CATALOG_DATA2
Load Detail Data and Usage Decision for
BAPI_INSPLOT_GETDETAIL
Inspection Lot
ZZREAD_TEXT SAPscript: Read text RFC Enabled
BAPI_INSPOPER_GETDETAIL Read Detail Data for Inspection Operation
RFC_READ_TABLE External access to R/3 tables via RFC
Transfer of Charac. Specifications and Catalog
QIRF_SEND_INSP_DATA_FOR_WL2
Entries to the Worklist
BAPI_VENDOR_GETDETAIL Vendor Detail Information
BAPI_EQUI_GETLIST BAPI PM: Selection of Equipment List
BAPI_EQUI_GETDETAIL PM BAPI: Read Equipment
MPLAN_READ Read Maintenance Plan

4.2 SAP MII integration with SAP QM

Quality Tiles in Marico MES home page

1. QM
2. Inspection lot redownload
3. Inspection Char Details
4. User Details

MARICO Confidential Page 12 of 17

Marico Information classification: Official

 i) Raw material Packing Material - Each 89 inspection will have only one 17 Inspection lot
1:1
(1) On TU activation, Quality inspection document number is generated, 89 inspection lot
will trigger in ECC and MII receives 89 inspection lot.
(2) MII workflow process inbound IDOC message and stores in custom schema.
(3) Quality user open QM tile as shown in above diagram with inspection lot details where
operator can do results recording and usage decision.
(4) User selects required Inspection lot and start doing results recording and usage decision.
(5) When GR is completed in EWM, 17 series inspection lot triggers in ECC and downloads
to MII.
(6) Auto link 89 lot results to linked 17 series inspection lots and usage decision copy to 17
series inspection lot.
(7) Auto update 17 series inspection lot Results and usage decision in ECC.
ii) SFG - Each 89 inspection will have only one 17 Inspection lot 1:1
(1) 89 inspection Lot creation at GR SFC Batch Stop (Production & Batch/Cycle wise a 89
manual inspection lot)
(2) RR/UD for 89 inspection lot
(3) SPGR value update in SPGR screen based on UD done for inspection char of 89
inspection.
(4) Post GR in SPGR screen - Automatic backed job in MII
(5) 17 inspection lot creation after GR from SPGR screen
(6) Auto UD for 17 serial inspection lot, with background job
(7) UD status update for 17 inspection lot
(8) Stock changes from Quality to Unrestricted in ECC
iii) FG/Bottles 75 ml - Each 89 inspection can sync with multiple 17 Inspection lot 1:N
(1) 1st Pallet GR in EWM - 89 & 17 series generates and flows to MII (100 Pallets in shift
wise/Batch 89 lot)
(2) 89 lot Result recording and UD
(3) 2nd time onwards only 17 series will get generate
(4) 2nd time pallet 17 Lot sync with 1st time pallet 89 lot

MARICO Confidential Page 13 of 17

Marico Information classification: Official

 Inspection lot Auto link 17
Download series Ussage UD update in
89 series operator do 17 serieries
from ECC to inspeciton lot desicion by ECC via JCO
inpection lot result inspection lot
MII via to exisiting 89 operator with function call
download recoding download
Message series user name from SAP MII
Monitor inspection lot

4.3 MII & Shopfloor Integration

SAP MII integrated to the shopfloor systems – KepServerEx and OSIPI servers through SAP Plant
connectivity. SAP MII server reads data from this shop floor system based on tag value or user
interaction or periodically.
4.4 MII & EWM Integration

SAP MII integration with SAP EWM with Java Connectivity (JCO interface) by using BAPI/RFCs

List of Functional Modules,

# EWM - BAPI/RFC Description

1. Checks the stock which are relevant for Quality
inspection.
CHecks the batch details of the stocks.
1 ZSCWM_SFG_BATCH_INSPECTION Sends the data to MII with the details for Quality clearance.
1.Create Manufacturing Order Batch Details for the entered
Batch & Qty
2.Calculate and Save BOM details for the Batch
2 ZSCWM_F_BATCH_MNFORDER_CREATE 3.Create Staging WTs for all Staging Relevant Components
3 ZSCWM_F_BATCH_MNFORDER_CANCEL 1. Manufacturing order cancellation

4.5 MII application monitoring and daily scheduling jobs

 Check scheduled jobs status and history of jobs

 MII message monitor to check any failed IDOC received from ECC
 Transaction Manager if any failed transaction
 Log Viewer if any error occurred in complete MES application
 Data Servers connection status check
 ECC/EWM connection check
 PCO server connection check with SAP MII
 PCO server connection with shopfloor systems – OSI PI and Historian.
 Action sessions list in MII administration

MARICO Confidential Page 14 of 17

Marico Information classification: Official

 4.6 MII applications landscape

MII DEV/QA MII PROD

4.7 Exception and error handing in MII

 Custom table is created to capture all the error/exception throughout the MES application.

Table Name: PN2E.LOGT_TL_MSGS

 Email alert whenever exception or error occurs in MES application

 Email alert whenever PCO agent is struct in PCO server
 Email alert whenever inspection plan is not assigned to material.
 Restart agent instance in MII automatically with the scheduled jobs

4.8 Transport mechanism

As we don’t have CTS+ enabled for transport mechanism, move change from DEV/QA server PROD
server manually.

4.9 Change request process

Whenever is CR created for a new requirement, we follow below steps to complete CR and promote
changes to PROD server

 Will receive CR document with requirement or problem statement

 We request business user to share justify business reason and ROI
 CR will send for approval and after approval dev team will start building in DEV server
 Business user will test and do UAT with test results
 CR changes moved to PROD
 Business user will confirm in PROD server and CR closed after validation/Monitoring for a
week

MARICO Confidential Page 15 of 17

Marico Information classification: Official

 5. Application History

5.1 Typical Problems

5.2 Release History

5.3 Maintenance History

MARICO Confidential Page 16 of 17

Marico Information classification: Official

 6. Reference Documents

The Project Library consists of documents that can provide further information about the application. Documents related to
the MII includes:

Version Last Update

Document Name Document Location
Number (YY/MM/DD)

Plant Hierarchy Plant Hierarchy Template Configuration.pdf

Target KPI SAPL_[Marico]_Target_KPI_[Falcon]-

[KPI]_[2020mmdd].pdf

MARICO Confidential Page 17 of 17

Marico Information classification: Official