Sizing Guide For SAP MII 15.4

PUBLIC
Document Version: 15.2.0 – 2018-03-25
SAP MII - Sizing Guide

© 2020 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Sizing Fundamentals and Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3 Initial Sizing for SAP MII 15.4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4 Miscellaneous. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5 Comments and Feedback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2 PUBLIC Content
1 Introduction
Use
SAP Manufacturing Integration and Intelligence (SAP MII) enables the integration of customer's plant and
enterprise systems and the displaying of integrated data to the employees. With SAP MII the customers can
view, measure, and compare the performance of plants and assets with different automation system
infrastructures.
SAP MII reduces the cost of synchronizing plant and enterprise business processes by using plant system
connectors, business logic services and integration scenarios.
Data Services
Real-time integration of data with plant floor systems, applications and legacy systems.
Visualization Services
Extensible presentation layer presented through web pages. Family of configurable UI objects provide
manufacturing views in role based dashboards or through wireless PDAs.
Business Logic Services
Flow based logic engine, enables data aggregation and transformation of disparate data. Transactions can
either be triggered or scheduled. Calculations, business rules, and alerts are easily developed and executed.
Features
1.1 Architecture of SAP MII 15.4
The SAP MII application is built in layers.
● Presentation Layer: Contains the user created web content which makes use of SAP MII display
applets/UI5 based visualization.
● UI Control Layer: Contains the user created templates. The Query Templates contain query request
parameters and the Display Templates contain the visualization properties.
● Service Layer: Exposes services such as ODATA for easy retrieval of user configured data and data from
different plant systems.
● Data Access Layer: Contains components which applies business logic on the data retrieved from the plant
system.
1.2 Functions of SAP MII 15.4
This sizing guide covers customer usages which involve SAP MII specific functionality and integration
scenarios.
Download Production Order Header List from SAP ERP
SAP MII is used as integration component at plant level and is used to download the production order Headers
from SAP ERP to the plant system. With Download Production Order List from SAP ERP scenario SAP MII

Introduction PUBLIC 3
downloads production order headers from SAP ERP using JCo communication (RFC Name (BAPI):
BAPI_PRODORD_GET_LIST) and stores in MDO.
The download is executed asynchronously using multiple parallel processes (Java threads). This is achieved by
a master transaction, triggering a dynamic transaction equal to the number of parallel processes. Transaction
output XML is restructured according to SAP MII XML format using SAP MII XML actions. The downloaded
order headers are then persisted to MDO.
XML Transformation
SAP MII is used as integration hub wherein messages are transformed using XML Transformation capabilities
and exchanged between planning and execution system. The XML transformation scenario handles the
conversion of XML message formats using XSL action block. After conversion the XML is updated to the
transaction property which can be used.
Retrieving History Data using PCo Query
SAP MII is used to create plant performance dashboard for showing the trend for a sensor data such as
temperature of boiler which can be retrieved by connecting to historian system. This scenario showcases the
above functionality with a SAP MII transaction by retrieving certain tag data from historian system using PCo
query.
PCo Notification Scenario
SAP MII is used to listen for abnormal situations such as increase of boiler temperature through a notification
from PCo on sensor value change. This scenario handles the http post call to SAP MII with the notification
message payload from PCo on sensor value change.
IDOC Integration from SAP ERP to SAP MII using JRA
SAP MII is used as integration component at plant level and to send the production orders from SAP ERP to the
plant system.
This scenario sends the production order IDOCs using POIT transaction to SAP MII using IDOC. A transaction
processes the IDOC which saves the order information to a MDO.
Report Production
Report production quantity is one of the scenario for OEE management in SAP MII.
1.3 Factors that Influence the Performance
The SAP MII Configuration options such as switching on and off the transaction, template and query caching
are major factors that influence the performance of the system.
● Transaction Caching improves the MII transaction execution. Transactions can be marked for caching in
System Properties in SAP MII administration screen.
● Template Caching ensures that template definitions are cached and loaded from the cache to ensure faster
responses.
● Query Caching is used to cache query results. Queries can be marked for caching in the query parameter
configuration in SAP MII Workbench. Additionally, the duration of the cache can be mentioned.

4 PUBLIC Introduction
Some important default values for System Properties in SAP MII are:
Property Default Value Description
Monitoring Retention Duration 30 Secs Interval between sequential message

monitor runs.
The monitor processes items received

from the message listeners.
Message Cleanup Interval 1 Hour Interval between sequential message

cleanup rules runs.
Session Timeout 60 Mins Wait time in minutes before the system

automatically closes inactive sessions
Transaction Cache Duration 2 hours Time in hours to keep transaction in the

system cache
Transaction Persistence Lifetime 8 Hours Time in hours to keep data in the trans
action manager
Expression Cache Duration 2 Hours Time in hours each to keep expression

in the cache.
To improve system performance, cache

parsed expressions.
Job History Cleanup 24 Hours Time in hours to keep the history of a

job.
Plant Information Catalog Logs Cleanup 30 Mins Interval between sequential catalog
Interval logs cleanup rules runs.
MDO Batch Processing False If this checkbox is selected, the manu

facturing data object (MDO) queries the
connection from the data source and to
see if it supports batch processing. If it
is supported, batch processing is used
for the replace and update tasks and
on-demand processing. If the checkbox
is not selected, batch processing is not
used.
Default Transaction Persistence Always The following options determine when

the system writes transaction informa
tion to the database:
● Always
● On Error
● Never

Introduction PUBLIC 5
Property Default Value Description
NetWeaver DataSource Caching False Enables the caching of data source cre
ated in NetWeaver
Usage Statistics Monitoring True Enables the monitoring of transactions

and query usage when value is set to
True.
Run Transaction Expiration Check False Enable the transaction expiration check
on startup
Transaction Caching True Enables the caching of transaction for

faster execution
Max Row Count 120000 Defines the query limit of 120,000 rows
Template Caching False Enables the caching of templates for

faster load of template definitions
WorkBench Maximum Memory Size 128 Defines the value for the WorkBench
(MB) Maximum Memory Size
For more details on System Properties, see the help document at http://help.sap.com/mii.

6 PUBLIC Introduction
2 Sizing Fundamentals and Terminology
Use
This section explains the most important sizing terms, as these terms are used extensively in this document.
Features
Sizing
Sizing means determining the hardware requirements of an SAP application, such as the network bandwidth,
physical memory, CPU processing power, and I/O capacity. The size of the hardware and database is
influenced by both business aspects and technological aspects. This means that the number of users using the
various application components and the data load they put on the server must be taken into account.
Benchmarking
Sizing information can be determined using SAP Standard Application Benchmarks and scalability tests
(http://www.sap.com /benchmark). Released for technology partners, benchmarks provide basic sizing
recommendations to customers by placing a substantial load upon a system during the testing of new
hardware, system software components, and relational database management systems (RDBMS). All
performance data relevant to the system, user, and business applications are monitored during a benchmark
run and can be used to compare platforms.
SAPS
The SAP Application Performance Standard (SAPS) is a hardware-independent unit that describes the
performance of a system configuration in the SAP environment. It is derived from the Sales and Distribution
(SD) Benchmark, where 100 SAPS is defined as the computing power to handle 2,000 fully business processed
order line items per hour. (For more information about SAPS, see http://www.sap.com/benchmark
Measuring in SAPS).
Initial Sizing
Initial sizing refers to the sizing approach that provides statements about platform-independent requirements
of the hardware resources necessary for representative, standard delivery SAP applications. The initial sizing
guidelines assume optimal system parameter settings, standard business scenarios, and so on.
Expert Sizing
This term refers to a sizing exercise where customer-specific data is being analyzed and used to put more
detail on the sizing result. The main objective is to determine the resource consumption of customized content
and applications (not SAP standard delivery) by comprehensive measurements.
Configuration and System Landscaping
Hardware resource and optimal system configuration greatly depend on the requirements of the customer-
specific project. This includes the implementation of distribution, security, and high availability solutions by

Sizing Fundamentals and Terminology PUBLIC 7
different approaches using various third-party tools. In the case of high availability through redundant
resources, for example, the final resource requirements must be adjusted accordingly.

8 PUBLIC Sizing Fundamentals and Terminology
3 Initial Sizing for SAP MII 15.4
Use
Ensure that:
SAP MII scenarios are executed in scheduled mode, where overlapping occurs in execution time slot of different
scenarios or same scenario with different data.
The sizing is provided separately for each MII scenario. The final sizing result is the sum of the results for the
scenarios that run in parallel. For multiple combinations of parallel running scenarios, the maximum
requirement (peak overlapping interval) of all combinations should be considered as final.
Features
3.2 Sizing Download Production Order Header List from SAP ERP
The processing time of download Production Order Headers (PO) scenario for given "number of PO" depends
heavily on the transaction modelling which the customer designs.
If the customer has a requirement for target processing time, the number of asynchronous thread is calculated
in the following way:
Number of asynchronous thread = (0.03 * Number of PO) / Target processing time[s]
 Example
If "number of PO" is 10.000 and target processing time [s] is 30 seconds, then the value of parameter
"number of asynchronous thread" should be set to 10. With the same "number of PO", if the target
processing time [s] is increased to 5 minutes (300 seconds), then no parallelization is required and number
of asynchronous thread can be set to 1.
 Note
Target processing time[s] below 20-30 seconds is hard to achieve because the overhead of splitting work in
packages can be quite significant if multiple packages are to be defined. The minimum target time
requirement is 20-30 seconds.
The configuration of SAP NW ABAP server and SAP NW Java server should support the selected number of
asynchronous thread. For example, if the selected value for number of loops is 20 then there must be at least
20 work processes at the SAP NW ABAP server side and 20 worker threads on SAP NW Java server side. Else
the parallelization will be limited by the actual number of available work processes and Java threads.
The higher the parallelization the more hardware resources are required.
The table below refers to SAPS and memory requirements for downloading POs with different configuration of
number of asynchronous thread.

Initial Sizing for SAP MII 15.4 PUBLIC 9
Configuration: " number of SAPS Java Server SAPS Java Server Database Physical memory [GB] for
asynchronous thread " Java Server
1 800 200 0.2
5 4000 1000 1
10 8000 2000 2
20 16000 4000 4
 Recommendation
For optimal performance LAN network is recommended between SAP NW Java Server and SAP ERP.
3.3 Sizing XML Transformation
The XML transformation is executed sequentially. The processing time for a single XML document can be
increased only by a faster CPU and not with multiple CPUs.
The required SAPS for SAP NW Java Server is proportional to the number of XML transformations scheduled
to run in parallel and is independent of the size of the XML document. In other words, if one XML document is
scheduled for transformation, one processing unit (core, thread) should be available and free for the SAP NW
Java server side processing and if 10 XML documents are scheduled for transformation, 10 processing units
should be available.
The memory requirement depends on the size of the XML document, for example for each 1 MB of a XML
document, 20 MB of Java server memory is required.
 Note
To parse a single XML document of size 90MB, 1.8GB free java heap space must be available in addition to
the usual Java server initial memory allocation (normal range is 1GB). This can be set on the SAP NW Java
Server with the parameters, -Xms = -Xmx which equals to 2.8 GB.
The java parameter- Xms defines the minimum Heap Size and the java parameter - Xmx defines the
maximum Heap Size. Both parameters should be set to the same value because this improves the
performance of the system.
 Example
Suppose there are 5 XML documents scheduled for parsing at the same time by a single SAP NW Java
server node. Let 3 XML documents have size of 50 MB each and 2 XML documents have size of 90 MB
each. Then the total required heap space is calculated as follows:
1 GB + (3 * 50 MB + 2 * 90 MB) * 20 MB = 7.4 GB
The configuration of the java server node memory is rounded up to 8GB (using -Xms = -Xmx = 8GB).
Memory measurement for SAP NW Java server memory

10 PUBLIC Initial Sizing for SAP MII 15.4
Size of XML in MB Required java server memory [GB] for Required java server memory [GB] for
processing of 1 XML document processing of 10 XML documents in
parallel
10 1.2 GB 12 GB
50 2 GB 20 GB
90 2.8 GB 28 GB
The database disk space is growing proportional to the size of the XML document, e.g. with a 50 MB XML
document plan 50 MB disk space growth for the database.
Consider the retention period to calculate how much disk space would be occupied over time with
accumulation of data.
3.4 Sizing Retrieving History Data using PCo Query
Retrieval of PCo Metadata and Secondary information of the tags and PCo notification is not considered in this
sizing.
For details on sizing for Plant Connectivity (PCo), see http://service.sap.com/sizing Sizing Guidelines
Others SAP Plant Connectivity .
The processing of data in this scenario is executed sequentially on SAP NW Java server. The duration of
processing depends on the number of tags, the number of retrieved records per tag, and the speed of the
processing unit (core, thread). In other words, multiple processing units (cores, threads) are required only if the
more than one query is executed in parallel.
The SAP NW Java memory requirement for the sequential processing of a query is rounded to 1 GB. For parallel
execution of queries, the memory must proportional in size.
1 GB offset memory for SAP NW Java server initialization for each configured java server node is required.
Number of queries exe SAPS Java Server SAPS Database Physical memory [GB] for
cuted in parallel Java Server
5 3600 400 6 GB (For example, 1 server

node)
10 7200 800 12 GB (For example, 2 server

nodes)
20 14400 1600 24 GB (For example, 3server

nodes)
3.5 Sizing PCo Notification Scenario
The PCo notifications are sent by sensors or machines and are received at the SAP NW Java Server side. The
sizing table below refers to the number of received notifications per second, which usually is much lower than
the number of attached sensors or machines.

Number of notifica SAPS Java Server SAPS Database Physical memory Network require
tions per second [GB] for Java Server ments [Mbit/s]
10 400 250 1.5 GB 2.5 Mbit/s
100 4000 2500 2.2 GB 25 Mbit/s
250 10000 6250 6.5 GB 60 Mbit/s
3.6 Sizing IDoc Integration Scenario
The IDOC Scenario receives messages in MII Java Server from the ERP system (via RFC Destination) through
the IDOC Listener. It triggers a transaction in the MII system which saves the messages in MDO in the Java
database. Additionally, the scenario checks for the successful persistence of the message.
For each Production Order a message is sent from ERP and persisted in the MDO.
Messages/Production Orders are sent in different chunks of sizes, which can be configured with parameter.
 Note
IDOC scenario is executed in scheduled mode in the background and the processing of IDOC is done
sequentially .Hence, the execution time of this scenario depends on the number of IDOCs in linear way and
cannot be reduced by additional hardware.
The minimum hardware requirement for SAP MII (number of cores and memory) is sufficient to execute
individually scheduled and non-overlapping IDOC scenario. If multiple IDOC scenarios are scheduled to run in
parallel or one IDOC scenario runs in parallel to other MII scenarios, then 1 core free and up to 200 MB memory
is required along with the existing hardware for each of the parallel running IDOC processing.
3.7 Sizing Report Production Scenario
Report production quantity is a scenario in OEE on SAP MII. Production quantities are reported from the shop
floor against machine or line and orders running on these lines. This production data is sent to OEE through
MII.
For sizing exercise, the report production scenario is replicated for number of posts per second.
The scenario uses SAP MII transaction which in turn uses an OEE custom action service in the transaction. The
transaction is executed with an input parameter and the OEE custom action. Every single execution of the
custom action service reports a production quantity to OEE.
The table below refers to SAPS and memory requirements with different configuration of number of posts per
second.
The number of peak posts per second is determined by the number of configured machines and depends on
the intervals between the posts. For example, 10 posts per second are equivalent to 100 machines sending at
interval of 10 seconds or 300 machines sending at interval of 30 seconds and so on, i.e. “10*N machines”
sending at “interval of N seconds”

12 PUBLIC Initial Sizing for SAP MII 15.4
Number of posts per SAPS Java Server SAPS Database Physical memory Network require
second [GB] for Java Server ments [Mbit/s]
10 4100 1950 5 40
50 20450 9600 15 180
100 40850 19200 30 360
3.2.7 Sizing Report Downtime
Report downtime is a scenario in SAP OEE Management on SAP MII. Downtimes are reported from the shop
floor against machine or line and orders running on these lines. This downtime data is sent to OEE through MII.
For sizing exercise, the report downtime scenario is replicated for number of posts per second.
The scenario uses SAP MII transaction which in turn uses an OEE custom action service in the transaction. The
transaction is executed with an input parameter and executes the OEE custom action. Every single execution of
the custom action service reports a downtime to OEE.
The table below refers to SAPS and memory requirements with different configuration of number of posts per
second.
The number of peak posts per second is determined by the number of configured machines and depends on
the intervals between the posts. For example, 10 posts per second are equivalent to 100 machines sending at
interval of 10 seconds or 300 machines sending at interval of 30 seconds and so on, i.e. “10*N machines”
sending at “interval of N seconds”.
Number of posts per SAPS Java Server SAPS Database Physical memory Network require
second [GB] for Java Server ments [Mbit/s]
10 13300 7500 10 60
50 66400 37300 30 270
100 132800 74550 60 540

4 Miscellaneous
The MII installation guide is available on the SAP Help Portal page at http://help.sap.com/mii
For the latest supported configurations, see the SAP Product Availability Matrix or PAM at SAP Product
Availability Matrix .
4.2 Abbreviations
● MII - Manufacturing Integration and Intelligence

● ERP - Enterprise Resource Integration
● JCo - Java Connector
● MDO - Manufacturing Data Object
● PCo - Plant Connectivity
● IDOC - Intermediate Document
● PO - Production Order
● RFC - Remote Function Call
● NW - Netweaver

14 PUBLIC Miscellaneous
5 Comments and Feedback
Address your questions to CSS component MFG-MII.

Comments and Feedback PUBLIC 15
6 Appendix
Download Production Order Header List from ERP
For more details on Transaction, see SAP Note 1977429
Sample of Downloaded Production Order Header
<?xml version="1.0" encoding="UTF-8"?>

<BAPI_PRODORD_GET_LIST>
<INPUT>
<COLLECTIVE_ORDER/>
</INPUT>
<OUTPUT>
<RETURN>
<TYPE/>
<ID/>
<NUMBER>000</NUMBER>
<MESSAGE/>
<LOG_NO/>
<LOG_MSG_NO>000000</LOG_MSG_NO>
<MESSAGE_V1/>
<MESSAGE_V2/>
<MESSAGE_V3/>
<MESSAGE_V4/>
<PARAMETER/>
<ROW>0</ROW>
<FIELD/>
<SYSTEM/>
</RETURN>
</OUTPUT>
<TABLES>
<MATERIAL_RANGE/>
<MRP_CNTRL_RANGE/>
<ORDER_HEADER>
<item>
<ORDER_NUMBER>000001000250</ORDER_NUMBER>
<PRODUCTION_PLANT>1000</PRODUCTION_PLANT>
<MRP_CONTROLLER>001</MRP_CONTROLLER>
<PRODUCTION_SCHEDULER/>
<MATERIAL>ICM_CHOCOLATE</MATERIAL>
<EXPL_DATE>2012-12-13</EXPL_DATE>
<ROUTING_NO>0000000251</ROUTING_NO>
<RESERVATION_NUMBER>0000000279</RESERVATION_NUMBER>
<SCHED_RELEASE_DATE>2012-12-13</SCHED_RELEASE_DATE>
<ACTUAL_RELEASE_DATE>2012-12-13</ACTUAL_RELEASE_DATE>
<FINISH_DATE>2012-12-13</FINISH_DATE>
<START_DATE>2012-12-13</START_DATE>
<PRODUCTION_FINISH_DATE>2012-12-13</PRODUCTION_FINISH_DATE>
<PRODUCTION_START_DATE>2012-12-13</PRODUCTION_START_DATE>
<ACTUAL_START_DATE>2012-12-13</ACTUAL_START_DATE>
<ACTUAL_FINISH_DATE>0000-00-00</ACTUAL_FINISH_DATE>
<SCRAP>0</SCRAP>
<TARGET_QUANTITY>100.000</TARGET_QUANTITY>
<UNIT>KG</UNIT>
<UNIT_ISO>KGM</UNIT_ISO>
<PRIORITY/>
<ORDER_TYPE>PP01</ORDER_TYPE>
<ENTERED_BY>I064248</ENTERED_BY>
<ENTER_DATE>2012-12-13</ENTER_DATE>
<DELETION_FLAG/>

16 PUBLIC Appendix
<WBS_ELEMENT>00000000</WBS_ELEMENT>
<CONF_NO>0000000000</CONF_NO>
<CONF_CNT>00000000</CONF_CNT>
<INT_OBJ_NO>000000000000000000</INT_OBJ_NO>
<SCHED_FIN_TIME>00:00:00</SCHED_FIN_TIME>
<SCHED_START_TIME>00:00:00</SCHED_START_TIME>
<COLLECTIVE_ORDER/>
<ORDER_SEQ_NO>00000000000000</ORDER_SEQ_NO>
<FINISH_TIME>00:00:00</FINISH_TIME>
<START_TIME>00:00:00</START_TIME>
<ACTUAL_START_TIME>13:55:08</ACTUAL_START_TIME>
<LEADING_ORDER/>
<SALES_ORDER/>
<SALES_ORDER_ITEM>000000</SALES_ORDER_ITEM>
<PROD_SCHED_PROFILE/>
<MATERIAL_TEXT>CHOCOLATE ICECREAM</MATERIAL_TEXT>
<SYSTEM_STATUS>REL PCNF PRC GMPS MANC SETC</SYSTEM_STATUS>
<CONFIRMED_QUANTITY>0</CONFIRMED_QUANTITY>
<PLAN_PLANT>1000</PLAN_PLANT>
<BATCH/>
<MATERIAL_EXTERNAL/>
<MATERIAL_GUID/>
<MATERIAL_VERSION/>
<DATE_OF_EXPIRY>0000-00-00</DATE_OF_EXPIRY>
<DATE_OF_MANUFACTURE>0000-00-00</DATE_OF_MANUFACTURE>
</item>
</PRODPLANT_RANGE>
<PROD_SCHED_RANGE/>
<SALES_ORD_ITM_RANGE/>
<SALES_ORD_RANGE/>
<SEQ_NO_RANGE/>
<WBS_ELEMENT_RANGE/>
</TABLES>
</BAPI_PRODORD_GET_LIST>
XML Transformation Scenario
<?xml version="1.0" encoding="UTF-8"?>

<xsl:stylesheet version="1.0" exclude-result-prefixes="java" xmlns:xsl="http://
www.w3.org/1999/XSL/Transform" xmlns:java="http://xml.apache.org/xslt/
java"><xsl:template match="/">
<Parent>
<xsl:for-each select="/Rowsets/Rowset/Row">
<Child>
<VALUETYPE><xsl:value-of select="VALUETYPE"/></VALUETYPE>
<VERSION><xsl:value-of select="Plant"/></VERSION>
<DATAQUALITY><xsl:value-of select="VERSION"/></DATAQUALITY>
<STARTDATE><xsl:value-of select="STARTDATE"/></STARTDATE>
<ENDDATE><xsl:value-of select="ENDDATE"/></ENDDATE>
<SHIFT><xsl:value-of select="SHIFT"/></SHIFT>
<EVENTSTARTTIME><xsl:value-of select="EVENTSTARTTIME"/></EVENTSTARTTIME>
<LASTMODIFIED><xsl:value-of select="LASTMODIFIED"/></LASTMODIFIED>
<STATUS><xsl:value-of select="STATUS"/></STATUS>
<SITE><xsl:value-of select="SITE"/></SITE>
<PLANT><xsl:value-of select="PLANT"/></PLANT>
<PLANTNATIVE><xsl:value-of select="PLANTNATIVE"/></PLANTNATIVE>
<EQUIPMENT><xsl:value-of select="EQUIPMENT"/></EQUIPMENT>
<FUNCTIONALLOCATION><xsl:value-of select="FUNCTIONALLOCATION"/></
FUNCTIONALLOCATION>
<EQUIPMENTCATEGORY><xsl:value-of select="EQUIPMENTCATEGORY"/></EQUIPMENTCATEGORY>

Appendix PUBLIC 17
<PRODUCTIONWORKCENTRE><xsl:value-of select="PRODUCTIONWORKCENTRE"/></
PRODUCTIONWORKCENTRE>
<MATERIAL><xsl:value-of select="MATERIAL"/></MATERIAL>
<MATERIALNATIVE><xsl:value-of select="MATERIALNATIVE"/></MATERIALNATIVE>
<TOMATERIAL><xsl:value-of select="TOMATERIAL"/></TOMATERIAL>
<LOCATION><xsl:value-of select="LOCATION"/></LOCATION>
<LOCATIONNATIVE><xsl:value-of select="LOCATIONNATIVE"/></LOCATIONNATIVE>
<TOLOCATION><xsl:value-of select="TOLOCATION"/></TOLOCATION>
<DESTINATION><xsl:value-of select="DESTINATION"/></DESTINATION>
<PRIMARYTIMEELEMENT><xsl:value-of select="PRIMARYTIMEELEMENT"/></
PRIMARYTIMEELEMENT>
<SECONDARYTERTIARYTIMEELEMENT><xsl:value-of
select="SECONDARYTERTIARYTIMEELEMENT"/></SECONDARYTERTIARYTIMEELEMENT>
<TIMEELEMENTNATIVE><xsl:value-of select="TIMEELEMENTNATIVE"/></TIMEELEMENTNATIVE>
<PSEUDOCODE><xsl:value-of select="PSEUDOCODE"/></PSEUDOCODE>
<MEASURENAME><xsl:value-of select="MEASURENAME"/></MEASURENAME>
<QUANTITY><xsl:value-of select="QUANTITY"/></QUANTITY>
<UOM><xsl:value-of select="UOM"/></UOM>
<UOMNATIVE><xsl:value-of select="UOMNATIVE"/></UOMNATIVE>
<OPERATOR><xsl:value-of select="OPERATOR"/></OPERATOR>
<SUPPORTEQUIPMENT><xsl:value-of select="SUPPORTEQUIPMENT"/></SUPPORTEQUIPMENT>
<SUPPORTOPERATOR><xsl:value-of select="SUPPORTOPERATOR"/></SUPPORTOPERATOR>
<SUPPORTFUNCTIONALLOCATION><xsl:value-of select="SUPPORTFUNCTIONALLOCATION"/></
SUPPORTFUNCTIONALLOCATION>
<IGNOREEVENT><xsl:value-of select="IGNOREEVENT"/></IGNOREEVENT>
<DATASOURCE><xsl:value-of select="DATASOURCE"/></DATASOURCE>
<CALENDARDAY><xsl:value-of select="CALENDARDAY"/></CALENDARDAY>
<CALENDARWEEK><xsl:value-of select="CALENDARWEEK"/></CALENDARWEEK>
<CALENDARMONTH><xsl:value-of select="CALENDARMONTH"/></CALENDARMONTH>
<CALENDARQUARTER><xsl:value-of select="CALENDARQUARTER"/></CALENDARQUARTER>
<CALENDARYEAR><xsl:value-of select="CALENDARYEAR"/></CALENDARYEAR>
</Child>
</xsl:for-each>
</Parent>
</xsl:template>
</xsl:stylesheet>
Retrieving History Data using PCo Query
PCo Notification Scenario
IDOC Integration Scenario

18 PUBLIC Appendix
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Important Disclaimers and Legal Information PUBLIC 19
www.sap.com/contactsap
© 2020 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

Sizing Guide For SAP MII 15.4

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

Sizing Guide For SAP MII 15.4

Uploaded by

Copyright:

Available Formats

PUBLIC

Document Version: 15.2.0 – 2018-03-25

SAP MII - Sizing Guide

THE BEST RUN

2 Sizing Fundamentals and Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3 Initial Sizing for SAP MII 15.4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

5 Comments and Feedback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

SAP MII - Sizing Guide

Business Logic Services

1.1 Architecture of SAP MII 15.4

The SAP MII application is built in layers.

1.2 Functions of SAP MII 15.4

Download Production Order Header List from SAP ERP

SAP MII - Sizing Guide

Retrieving History Data using PCo Query

PCo Notification Scenario

IDOC Integration from SAP ERP to SAP MII using JRA

1.3 Factors that Influence the Performance

SAP MII - Sizing Guide

Property Default Value Description

Monitoring Retention Duration 30 Secs Interval between sequential message

The monitor processes items received

Message Cleanup Interval 1 Hour Interval between sequential message

Session Timeout 60 Mins Wait time in minutes before the system

Transaction Cache Duration 2 hours Time in hours to keep transaction in the

Expression Cache Duration 2 Hours Time in hours each to keep expression

To improve system performance, cache

Job History Cleanup 24 Hours Time in hours to keep the history of a

MDO Batch Processing False If this checkbox is selected, the manu­

Default Transaction Persistence Always The following options determine when

SAP MII - Sizing Guide

Usage Statistics Monitoring True Enables the monitoring of transactions

Transaction Caching True Enables the caching of transaction for

Template Caching False Enables the caching of templates for

SAP MII - Sizing Guide

Configuration and System Landscaping

SAP MII - Sizing Guide

SAP MII - Sizing Guide

Number of asynchronous thread = (0.03 * Number of PO) / Target processing time[s]

SAP MII - Sizing Guide

1 800 200 0.2

3.3 Sizing XML Transformation

Memory measurement for SAP NW Java server memory

SAP MII - Sizing Guide

3.4 Sizing Retrieving History Data using PCo Query

5 3600 400 6 GB (For example, 1 server

10 7200 800 12 GB (For example, 2 server

20 14400 1600 24 GB (For example, 3server

3.5 Sizing PCo Notification Scenario

SAP MII - Sizing Guide

10 400 250 1.5 GB 2.5 Mbit/s

100 4000 2500 2.2 GB 25 Mbit/s

250 10000 6250 6.5 GB 60 Mbit/s

3.6 Sizing IDoc Integration Scenario

3.7 Sizing Report Production Scenario

SAP MII - Sizing Guide

50 20450 9600 15 180

100 40850 19200 30 360

3.2.7 Sizing Report Downtime

50 66400 37300 30 270

100 132800 74550 60 540

SAP MII - Sizing Guide

● MII - Manufacturing Integration and Intelligence

MDO Batch Processing False If this checkbox is selected, the manu