scm380

This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)

SCM380SAP Manufacturing Integration

and Intelligence (SAP MII): BasicsSAP Manufacturing Integration and Intelligence

Date

Training Center

Instructors

Education Website

Participant HandbookCourse Version: 96 Revision ACourse Duration: 5 Day(s)Material Number: 50106170

An SAP course - use it to learn, reference it for work

This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)CopyrightCopyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Trademarks

Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server areregistered trademarks of Microsoft Corporation.

IBM, DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX,S/390, AS/400, OS/390, and OS/400 are registered trademarks of IBM Corporation.

ORACLE is a registered trademark of ORACLE Corporation. INFORMIX-OnLine for SAP and INFORMIX Dynamic ServerTM are registered

trademarks of Informix Software Incorporated. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, MultiWin and other Citrix product names referenced herein are trademarksof Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, WorldWide Web Consortium, Massachusetts Institute of Technology.

JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for

technology invented and implemented by Netscape. SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP

EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.comare trademarks or registered trademarks of SAP AG in Germany and in several other countriesall over the world. All other products mentioned are trademarks or registered trademarks oftheir respective companies.

Disclaimer

THESEMATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLYDISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDINGWITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE,INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTSCONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANYKIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOSTPROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDEDSOFTWARE COMPONENTS.

g20121311273

This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)About This HandbookThis handbook is intended to complement the instructor-led presentation of thiscourse, and serve as a source of reference. It is not suitable for self-study.

Typographic ConventionsAmerican English is the standard used in this handbook. The followingtypographic conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as wellas menu names, paths, and options.

Also used for cross-references to other documentationboth internal and external.

Example text Emphasized words or phrases in body text, titles ofgraphics, and tables

EXAMPLE TEXT Names of elements in the system. These includereport names, program names, transaction codes, tablenames, and individual key words of a programminglanguage, when surrounded by body text, for exampleSELECT and INCLUDE.

Example text Screen output. This includes file and directory namesand their paths, messages, names of variables andparameters, and passages of the source text of aprogram.

Example text Exact user entry. These are words and characters thatyou enter in the system exactly as they appear in thedocumentation.

Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

2012 2011 SAP AG. All rights reserved. iii

This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)

About This Handbook SCM380

Icons in Body TextThe following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in the instructor'spresentation.

iv 2011 SAP AG. All rights reserved. 2012

This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)ContentsCourse Overview ......................................................... vii

Course Goals .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiCourse Objectives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

Unit 1: SAP MII Introduction............................................. 1SAP MII Manufacturing Integration and Intelligence Overview .2SAP MII Architecture .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15SAP MII Positioning ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Unit 2: Data and Visualization Services: Introduction .......... 35SAP MII Workbench Overview ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37SAP MII Data Servers and Connectors .. . . . . . . . . . . . . . . . . . . . . . . . . . . 47Introduction to Query Templates ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Introduction to Display Templates ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Unit 3: Data and Visualization Services: Additional Features 91The SAP MII Time Engine ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93The iChart and Applet Generation ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108Scaling, Data Mapping, and SQL Queries.. . . . . . . . . . . . . . . . . . . . . . .123Introduction to the iGrid and Color Contexting ... . . . . . . . . . . . . . . . .135XML Queries, the iTicker, and the iBrowser .. . . . . . . . . . . . . . . . . . . . .150The iSPCChart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169

Unit 4: Navigation and Personalization............................ 199Personalization: Customizing the Navigation ... . . . . . . . . . . . . . . . . .200Personalization: Customizing the Home Page Style .. . . . . . . . . . .212

Unit 5: Web Scripting .................................................. 223Applet Events and JavaScript . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225SAP MII Report Pages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247Localization ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277

Unit 6: Business Logic Services: Introduction .................. 297Business Logic Services Terminology and Environment .. . . . . .299Action Configuration and Linking ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .322Properties, Data Types, and the Xacute Query .. . . . . . . . . . . . . . . . .336

2012 2011 SAP AG. All rights reserved. v

This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)

Contents SCM380

Unit 7: Business Logic Services: Additional Features andIntegration with SAP ................................................... 383

XML Functions ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385Document Building... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .398SAP Integration ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .418Error Handling, Transaction Calls, and Reference Documents 438

Glossary................................................................... 465

Index ....................................................................... 469

vi 2011 SAP AG. All rights reserved. 2012

This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)Course OverviewThis course introduces you to SAP Manufacturing Integration and Intelligence(SAP MII). Along with providing an overview of the product, this course enablesyou to use the scope of functions provided by SAP MII.

Target AudienceThis course is intended for the following audiences:

Members of project teams and consultants who use SAP ManufacturingIntegration and Intelligence (SAP MII) to extract, aggregate, and transformdata from existing systems

Course PrerequisitesRequired Knowledge

Basic knowledge of the manufacturing industry Basic knowledge of web technologies such as HTML, JavaScript, XML,

XSL, CSS, Path, web services, and so on Basic knowledge of database query development Basic knowledge of SAP NetWeaver Basic knowledge of the SAP ERP system

Course GoalsThis course will prepare you to:

Gain a conceptual understanding of the features, functions, and options ofSAP MII 12.1, so that you can successfully design and implement MIIapplications in a company

Use SAP MII 12.1 to connect the manufacturing shop floor system and theSAP ERP system

Course ObjectivesAfter completing this course, you will be able to:

Use the different SAP MII services to support companies in the areas ofmanufacturing with the integration of data (manufacturing integration)and process optimization (performance management and manufacturingintelligence)

2012 2011 SAP AG. All rights reserved. vii

This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)

Course Overview SCM380

viii 2011 SAP AG. All rights reserved. 2012

This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)

Unit 1SAP MII Introduction

Unit OverviewIn this unit, you will learn about the architecture of SAP MII and its maincomponents and functions. You will also see where SAP MII fits in the overallSAP Manufacturing solution.

Unit ObjectivesAfter completing this unit, you will be able to:

Describe the purpose of SAP MII Explain where SAP MII fits in the manufacturing domain List the services SAP MII provides Describe the SAP MII integration landscape Explain how SAP MII integrates with SAP ECC Explain the typical single plant SAP MII installation Explain the typical multi-plant SAP MII installation Explain the SAP MII deployment strategies Describe the application, network, and lifecycle considerations Explain the physical position of SAP MII in a single plant Explain how SAP MII fits in the SAP Manufacturing solution List the typical application areas of SAP MII Enumerate the business benefits of SAP MII Recount a brief history of the SAP MII application

Unit ContentsLesson: SAP MII Manufacturing Integration and Intelligence Overview..2Lesson: SAP MII Architecture .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Lesson: SAP MII Positioning ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2012 2011 SAP AG. All rights reserved. 1

This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)

Unit 1: SAP MII Introduction SCM380

Lesson: SAP MII Manufacturing Integration andIntelligence Overview

Lesson OverviewIn this lesson you will learn how SAP MII helps manufacturers effectively managethe challenge of data disparity.

Lesson ObjectivesAfter completing this lesson, you will be able to:

Describe the purpose of SAP MII Explain where SAP MII fits in the manufacturing domain List the services SAP MII provides Describe the SAP MII integration landscape Explain how SAP MII integrates with SAP ECC

Business ExampleYou are asked to describe what SAP MII is and for what purposes it can be used.

The Challenge: Manufacturing DisparityA typical manufacturing plant has between 10 and 50 shop floor automationsystems, while a multi-site manufacturer has between 80 and 800 shop floorautomation systems across its enterprise. These systems are most likely fromdifferent vendors with different architecture and connectivity mechanisms.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)

SCM380 Lesson: SAP MII Manufacturing Integration and Intelligence Overview

Figure 1: Data Disparity

Over the years, manufacturing companies have invested in a diverse set ofapplications managing plant floor controls and operations. At the lowestlevel are sensors and controls, including programmable logic controllers anddistributed control systems. Because of the changes in technology, price points,competition and growth through acquisition, companies infrastructures oftenlack standardization.

At the next level, we find applications that orchestrate and manage plant flooroperations. This includes production operations, manufacturing execution systems(MES), data collection, asset management, scheduling, inventory management,quality analysis, and process optimization. Some of these systems are providedby software and automation vendors; others are home grown, based on SQLdatabases with custom front ends.

Each of these applications has their own data structures (tag, time series, text,SQL, XML, and so on), schemas, separate interfaces, and graphical user interfaces(GUI). Additionally, these applications embody specific shop floor businessprocesses that shop floor workers are accustomed to.

This has created significant disparity and islands of information within the plantwalls. The problem of disparity on the shop floor expands tremendously in amulti-site manufacturer. While companies have attempted to standardize on acommon set of vendors for these solutions, the evolution of these organizations(and impact of mergers and acquisitions) has created a very complex matrix ofapplications. It is not uncommon for a large multi-site manufacturer to havehundreds of different applications on the shop floor.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


These applications act as silos of rich information, if they could be broughttogether, create high-value composite applications, which provide tremendousvalue to manufacturers. Composite applications are apps on apps, leveragingexisting investments in software and applications to rapidly create newapplications with extraordinary value.

An additional gap in the manufacturing information puzzle is the gap between theshop floor and the enterprise. Linking the shop floor to enterprise applications forsynchronizing activities and assuring accurate real time views of the supply chainpresents other significant benefits to manufacturers.

This system disparity creates the fundamental problem facing manufacturers today:lack of visibility to information and synchronization across their manufacturingoperations. Very few manufacturers automatically integrate their plant data intotheir ERP system. Furthermore, plant floor workers usually are not engaged withERP data and business processes. The disconnect between the shop floor and theenterprise costs millions of dollars through waste, rejects, and reorders.

The Solution: SAP MII Composite ApplicationFramework for ManufacturingSAP MII Manufacturing Integration and Intelligence is a framework forrapid delivery of composite applications for manufacturing. Running on a Webserver, this unique product leverages the manufacturers existing investmentin shop floor applications. SAP MII leverages a service-oriented architecture,streamlining application integration and speeding deployment.

Figure 2: The Solution SAP MII


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


SAP MII is a Web-server-based application with a zero-client design; hence,no application software needs to be installed on the client machine. Clientsshould use their Web browser with the appropriate version of the Java RuntimeEnvironment (JRE). While Microsoft Internet Explorer 7.0 is recommended forthe client machine, SAP MII can deliver content to non-Java browsers if thecontent is prepared properly. This is the typical approach for mobile or handhelddevice support. Presentation of real-time plant information to Pocket PC wirelessdevices, Internet phones, and rugged-ized plant handheld devices and scannersdrives efficiencies through a mobile workforce. Data consumption and data entryare supported by SAP MII.

SAP MII runs on the SAP NetWeaver platform, leveraging SAP NetWeaverApplication Server (SAP NetWeaver AS), the Java stack, and the database. Thislighter-weight approach is more suited to a distributed environment than thefull NetWeaver stack. Optionally, the SAP MII framework can be run with theABAP stack as well as other NetWeaver components, like the portal or ProcessIntegration. One significant benefit of running under NetWeaver is platformindependence; it can be hosted on many operating systems and run with a numberof different databases. Additionally, SAP MII becomes more integrated with SAPBusiness Suite. Finally, the NetWeaver platform provides enhanced supportabilityfrom SAP through the Computing Center Management System (CCMS) andsoftware management through Solution Manager. MII also leverages NWDI fortransport. Projects can be catalogued, version controlled, and deployed froma central point through NetWeaver. And SAP MII integrates through the usermanagement engine (UME) in NetWeaver, supporting single sign-on.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Connectors

Figure 3: SAP MII Services

A family of connectors, which are delivered with the product, provide instantaccess to data from these applications without any requirement for data replicationinto another data store. These connectors use industry standard protocols forintegrating to shop floor and business applications. Connector protocols include:

ODBC/JDBC OLEDB OPC-DA OPC-HDA OPC-UA

Connectors also include application programming interfaces (APIs) for manycommonly found plant-floor applications, including vendor-specific APIs forSCADA/ HMI and process historians.

Data ServicesThe data services provide bidirectional (read write) access to data in plantsystems through rapid configuration of query templates that create named viewsof data (for example, Machine_Cycle_Time, or Line1_Conveyor_Speed). Theseare extracted from underlying systems that can be catalogued for use in SAP MII


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


applications. Templates can be parameterized, that is, you can use placeholders forquery values at run time to meet the needs of a user (start date / end date), or tochain queries and use results from one query to filter or impact another.

SAP MII normalizes all data, regardless of its source, into a standard XMLstructure. This happens behind the scenes, and is used to integrate unstructureddata together. Furthermore, results from query templates can be cached to a server,stored as an XML document, or persisted in a database.

Data service queries eliminate the need to replicate data into a data cube or centralrepository. One of the key reasons for SAP MIIs success and fast time to value isthat data can be extracted from the source in real time managed by templates.

Business Logic ServicesBusiness logic services in SAP MII are based on a graphical logic engine fororchestrating transactions in within SAP MII. Action blocks are placed insequences that are wired together to form a transaction. The wiring can leverageBoolean logic to allow for gates and loops. Transactions are executed via thetime-based scheduler in SAP MII or external triggers (Web service call, Web pageevent, and so on). Transactions are solved left to right and top to bottom.

Action blocks can call a query template - results are processed from the SAPMII Data Services. Complex calculations and Key Performance Indicators canbe run from other Action Blocks. E-mail based alerts can be generated based onrules configured in the logic engine. Reports can be generated in HTML or PDFformat from business logic services.

Other action blocks have a variety of data transformation capabilities, handlingvalues, strings, dates, etc. The results in any action block are available tosubsequent action blocks.

Business logic services also provides transactional integration to SAP enterpriseapplications. Action blocks take advantage of numerous mechanisms to consumeor post data from SAP core applications. Business logic services can use SAPBusiness Connector, JCo, SOAP or basic IDoc exchanges to provide integration.Mapping functions in the Business Logic Service enable easy integration of plantdata and processes to SAP ECC. Once the JCo block is in place, the developercan browse all the available RFCs, BAPIs and IDocs in ECC for applicationcomposition.

Analytic ServicesAnalytic services are another key component in SAP MII. A full-featuredStatistical Process Control (SPC) engine, with full Western Electric Rules, allowsdata analysis in real time of data sets from any application. SPC analysis can alsobe run in the background as a business logic service action block and customrules can be quickly deployed to trigger alerts or reports, based on violations.SAP MII provides dozens of SPC analysis results that can be delivered through arich set of views.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Visualization ServicesSAP MII provides a variety of methods to display information through itsvisualization services. SAP MII is delivered with a family of rich appletsthat provide the means to deliver views of data in numerous forms. Charts,grids, tickers, and browsers enable users to view and gather data from disparatesystems in a very intuitive manner. These UI components are configured in theSAP MII environment, are high performance leveraging high speed binarycommunications and are integrated with SAP security and logging.

An additional library of SVG objects provides another level of data delivery.Custom objects can be created through the toolkit as well.

Once the data is defined via the query template, transformed (if necessary) throughbusiness logic services, and linked to a display template or SVG object; theresulting visual object can be delivered to a Web page for presentation purposes.SAP MII is fully extensible in the Web environment, and leverages JavaScript todrive events from the page to the applets at run time. The applet events are exposedby a script assistant. Web page dialog boxes, dropdowns, and events can triggerdata filters, updates, and so on without refreshing the entire page. Additionalcontent can be developed using standard Web techniques via Dynamic HTML andXSLT, which is very useful for reporting views and more comprehensive views.

Security ServicesThe resulting SAP MII content can be delivered through the SAP MII lightweightportal, which manages users, roles, and security and delivers content to usersbased on their privilege. Security services can be hosted within the SAP MIImodel on a standalone basis, or SAP MII can leverage an external LDAP directoryor integrate to SAP single sign-on for user authentication through the UME. Thesecurity services include all functions for authorization management. Besides readand write access to data, you can also administer authorizations for individualSAP MII functions.

Message ServicesThe message services include all functions for sending and receiving messagesfrom other systems. Message services can:

Enable communication between systems Transfer data using IDocs, Remote Function Calls (RFC), and Web services Copy data from another system in the form of a buffer Queue data

Navigation ServicesNavigation services include all functions for setting up the SAP-MII-integratedWeb portal with a user and role-specific menu structure.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


SAP MII can also prepare content for consumption in external portals, mostnotably SAP Enterprise Portal (EP). Manufacturing data can now be easilyaccessed with enterprise data though a single common information deliveryenvironment.

Source Control ServiceThe Source control service allows you to configure a link to the NetWeaverDevelopment Infrastructure (NWDI) to centrally manage your SAP MII content.NWDI provides an infrastructure for developing Java-based applications on SAPNetWeaver and is responsible for the versioning, build, and lifecycle managementof applications. The workbench serves as an interface to NWDI.

Note: For more information, refer to the SAP MII 12.1 Ramp-UpKnowledge materials on the SAP Service Marketplace.

Report ServicesReports can be automated and printed, stored, or e-mailed based on time, event,or demand. The format for these documents can be text, XML, HTML, or PDF.Reports can include summary data, charts, grids, and analysis data. Productionsummaries, quality results, shift performance, certificate of conformance,environmental reports and others can all be generated through SAP MII.

SummaryThe SAP MII capabilities are an Enterprise Application Integration (EAI) enablerfor the plant environment. By leveraging the business logic service, SAP MII Webservice components, and broad manufacturing connectivity, coupled with a rangeof integration alternatives to ERP, you can achieve a integrated make portionof your supply chain.

SAP MII was designed for ease of use. The transformation tools require no XMLor programming expertise. These simple to learn tools allow the plant personnel tomanage the data transformations required for ERP integration at their local sites where they have the domain and system expertise. This approach not only yieldsvalue in a short time, but also lowers total cost of ownership.

The SAP MII Integration LandscapeIn this section we discuss how SAP MII integrates with the shop floor, with SAPECC, and with third-party applications.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Figure 4: The SAP MII Integration Landscape

Shop Floor IntegrationSAP MII connectors to the shop floor are shown in the diagram in two blocks. TheUniversal Data Servers (UDS) are the original connector designs for MII. Theycan run on the MII server or at the data source but require a Microsoft operatingsystem to run as a service. Plant Connectivity (PCo) is the latest connectivityoption from SAP offering a service oriented connection technology that canbind to a data source and provide unsolicited events back to MII based on a ruleviolation. Both of these technologies are the mechanism for communicating toshop floor systems.

SAP ECC IntegrationSAP MII has a number of connection technologies built in, that make it easy tointegrate with shop floor systems, but also with enterprise systems, especially SAPBusiness Suite. The SAP MII integration touch points are highlighted in thisdiagram with MII in the center gray box, ECC at the top, and the plant systemsat the bottom.

SAP MII has the ability to integrate to any function in ECC that uses BAPIs,RFC, or IDocs both standard and custom. From a technology standpoint,transactional integration to ERP can be accomplished directly to ERP through JavaConnector (JCo) or SAP Java Resource Adapter (SAP JRA). JCo provides thehighest performance. Both JCo and SAP JRA utilize mechanisms in NetWeaverfor reliable messaging using built-in queues and logs, should a transaction fail.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Automatic retries can be configured to assure payloads are delivered. SAP MII canalso integrate to enterprise systems using straight Web service calls. Informationcan also be pushed from SAP ECC to SAP MII using IDocs or RFCs.

Instead of direct communications to SAP ECC, SAP MII can process messagesthrough SAP PI or third-party EAI. Special function blocks are available inbusiness logic services to move messages to and from PI. Also, SAP MII can lookup enterprise services that are published in the Enterprise Services Repository(ESR) in PI and consume them in business logic services.

Note: If you know the Web Service Definition Language (WSDL) of theservice, SAP MII can consume an SAP ECC service without the ESRpresent.

The SAP MII framework is also well-equipped to directly consume and publishto ERP enterprise services. Numerous enterprise services are published on theSAP Developer Network (SDN) and additional services will be made availableas they are published.

Typically, SAP MII is connected directly to SAP ECC for synchronousapplications, where speed is important and quick feedback to the user is desired.In addition, a multi-transactional function, where a number of transactions aregrouped together, is better served through direct integration. An additional benefitof SAP MII direct integration is that the transaction payload, business processstatus, and success are all carried on the same thread.

With integration through PI, SAP MII is exchanging messages only, and notgetting the benefits of the synchronous approach. This is preferred whenthe enterprise strategy is to monitor all messages centrally and asynchronousexchanges are appropriate.

BI IntegrationBusiness intelligence (BI) from SAP includes the SAP NetWeaver BusinessWarehouse cube where enterprise data is often stored. SAP MII can read datafrom the cube using its OLAP connector, which uses XML for Analysis (XMLA)protocols (other third-party cubes support XMLA). Writing data from SAP MII toBI can occur through a JCo call. Users can take data sets, reduce and compressresults, and deliver them to BI for applications like a certificate of conformance orother quality record from the shop floor.

JMS IntegrationSAP MII supports Java Messaging Service (JMS), which can be used forintegration to other third-party applications using this new standard. The JMSAPI is a messaging standard that allows application components based on theJava 2 Platform, Enterprise Edition (J2EE) to create, send, receive, and readmessages. It enables distributed communication that is loosely coupled, reliable,and asynchronous.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Shop Floor Integration with SAP ECCMany of our customers use SAP MII for simplifying the operator experiencein receiving or sending data to SAP ECC in context to their job function in theplant. The ability to relate enterprise data to plant data in one view, and providesimple tools for inputting data have been very popular with plant personnel. Thiseliminates the need for a plant floor worker to log into multiple applications,including SAP GUI, and manually bring together all the data required to completethe business process underway. In the past, many customers have relied onclipboards and Microsoft Excel for gathering plant information, and later use anSAP ECC administrator to enter data into the various transactions through SAPGUI.

To speed application development, SAP has authored many of the commontransactions that manufacturing companies use for shop floor integration andmade these available on the SAP Developer Network (SDN). These transactionsare run in business logic services, and can be modified or extended to suit thelocal requirements of the plant.

Figure 5: Information and Process Integration

Downloaded Transaction ResultsOn the left side of the diagram above, you can see some of the typical data thatplant workers use from SAP ECC, including customer details, order management,material management, master data delivery (including recipes and specifications),and maintenance details. The power of SAP MII allows the execution of multipletransactions from one view and the integration of results with plant information toallow intelligent operations in the plant.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Writing Transaction ResultsOnce armed with intelligence from SAP ECC and the plant, the operator can nowfeed back results to SAP ECC. On the right side of the diagram, typical data entrytransactions are shown. These can occur based on an operator input into a Webobject selection box, dropdown, or data entry field or can occur automatically.For example, SAP MII could read plant values from a production system and postthe results into quality management (QM), plant maintenance (PM), or anothermodule to feed back work in process (WIP) status or quality status, or deliverexceptions to SAP ECC.

Templates and CompositesBeyond these templates, SAP is also developing complete composite applications.These are out-of-the-box applications that include the query template examples,transaction templates, and GUIs that make up a complete application. Some ofthese are already available on SDN and others are in development. Our partnerecosystem is also developing and delivering pre-built composites that meetindustry-specific requirements.

Content DeliveryContent can be delivered through the SAP MII lightweight portal, which managesusers, roles, and security and delivers content to users based on their privilege.Security services can be hosted within the SAP MII model on a standalone basis,or SAP MII can leverage an external LDAP directory or integrate to SAP singlesign-on for user authentication through the UME.

SAP MII can also prepare content for consumption in external portals, mostnotably SAP Enterprise Portal. Manufacturing data can now be easily accessedwith enterprise data though a single common information delivery environment.With the Enterprise Portal, SAP MII can delivered role based iViews forpublishing in the portal with user security. SAP MII can also deliver KPIs andalerts to the role-based dashboard in EP. Additionally, SAP MII results can bepresented through Visual Composer (VC), as the query templates can be linkedin the VC development environment.

Benefits Summary Connectors provide instant integration to plant systems. Leverages existing investments; data replication is not required Provides integration and intelligence in one framework Applications are developed very quickly; time to benefit in weeks. Pre-built templates are available for integration with SAP Business Suite. Designed for real-time manufacturing applications Delivers transactional integration for simplifying user interaction with ERP


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Lesson Summary

You should now be able to: Describe the purpose of SAP MII Explain where SAP MII fits in the manufacturing domain List the services SAP MII provides Describe the SAP MII integration landscape Explain how SAP MII integrates with SAP ECC


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)

SCM380 Lesson: SAP MII Architecture

Lesson: SAP MII Architecture

Lesson OverviewThis lesson will help you understand the factors that should be consider whendeveloping an SAP MII deployment strategy.


Explain the typical single plant SAP MII installation Explain the typical multi-plant SAP MII installation Explain the SAP MII deployment strategies Describe the application, network, and lifecycle considerations Explain the physical position of SAP MII in a single plant

Business ExampleProper SAP MII architectures vary from company to company, based on theapplication requirements of that company, required service levels for the users,and the understanding of total cost of ownership. Balancing the three architecturalpillars is critical in deciding the proper server architectures. If a companydecides to design their architecture solely on the basis of cost, they may find theapplication environment too slow to meet the user requirements, or it may lackappropriate availability.

Architecture OverviewThere are numerous factors that should be considered in developing a SAPMII deployment architecture. SAP MII is often used for operations-centeredapplications. Availability and speed of response are often critical to the usersof these applications.

Single PlantIn a single-plant installation, SAP MII should be installed at the plant close tothe data sources that change quickly. This enables real-time views of informationand faster screen response for the users. Slower-moving ERP data can be accessedvia transactions, and are less time-critical to the users.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Figure 6: SAP MII Single-Plant Installation


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Multiple PlantsFor multi-plant SAP MII installations, SAP recommends a distributed architecture.A distributed architecture is recommended to facilitate some of the followingconcepts:

Assure the speed of response at the plant level.

Implement technology close to the high volume data sources, whichchange quickly.

Reduce WAN traffic. Preprocess data close to the source. Scale applications through parallel processing. Create an environment that withstands ERP downtime or network issues

for disconnected operations.

SAP MII caching of plant transactions for example, capturing a goodsmovement, or inspection result

SAP MII caching of ERP master data for continuous operation forexample, download all active process orders for the coming days, andallow workers to work off the cache

Manage time zone issues.

User time versus server time versus data source time Correlating data from different time stamp sources Managing user profiles to deliver data in right time zone

Promote local innovation.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Figure 7: SAP MII Multi-Plant Installation

A corporate MII server can be installed to aggregate results across the plants andprovide plant rollups or plant-to-plant comparisons.

Virtual ConnectionSAP MII instances can operate as a federation, meaning that they talk to eachother. If a user is logged into an instance at corporate and wants a drilldown intoplant data, the SAP MII corporate instance can extract the data in a very efficientmanner from the MII plant server and deliver it to the user session at corporate.The use of parameterization in the application design allows for powerfulmechanisms to enable cross-plant data access and rollup of multiple plant data.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Figure 8: SAP MII Virtual Connection

Deployment StrategiesStrategies for MII deployment have included:

Plant-based servers: One or more servers per plant Regional approaches: Implementing SAP MII (or multiple SAP MII servers)

in data centers

One SAP MII server may serve a number of smaller plants SAP MII servers placed in geographic centers (time zone and language

requirements) Centralized approaches (one or more servers hosted in central environment)

With that said, customers have successfully implemented SAP MII using anumber of different architectures. The decision process for these architectures islargely built on the desired application suite. Summary reporting and general KPIprocessing can sometimes be supported through more centralized or regionalapproaches. Transactional processing or deep-dive analytics drive the distributedarchitecture to a more granular level to assure responsiveness and applicationavailability. Pure ERP transactions, where there is no concern for disconnectedoperations, can be managed from a centralized approach.

Note that many of our customers invite plant personnel to aid in the design anddevelopment of applications. This is the local innovation concept referencedabove. Driving innovation locally and managing the promotion of new conceptsand ideas from a central group stimulates new ideas and engages plant people inthe innovation process, and connects them to the corporate culture and businessstrategy.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Considerations

Data sources and locations Real-time performance requirements Data volumes, especially time series data Transaction volumes: Synchronous / asynchronous Application scenarios

KPI and performance applications Data entry applications Alerts: Real time / business alerts Analytics Data movement, calculations, and refresh rate Mobile applications: Connected / disconnected Mission-critical requirements

Future requirements

WAN architecture LAN structure Network bandwidth EAI infrastructure and integration strategy User distribution

Concurrent loading by location Performance considerations Interruptions

Supportability

MII can be managed remotely Test and development

MII ERP Data sources

Maintenance Application Promotion

Single-Plant ArchitectureThe next section discusses the physical position of SAP MII in a single plant.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Figure 9: Single-Plant Typical Logical Architecture

Level 1 Control LayerThe bottom or first-level network in a plant is the control layer, with programmablelogic controllers (PLCs) and distributed control systems (DCSs) that control theoperation of a machine or process and record the status of mechanical operations.

A PLC is a digital computer used for automation of electromechanical processes,such as control of machinery on factory assembly lines. Unlike general-purposecomputers, the PLC is designed for multiple inputs and output arrangements,extended temperature ranges, immunity to electrical noise, and resistance tovibration and impact. A PLC is an example of a real-time system, since outputresults must be produced in response to input conditions through complex logicwithin a bounded time; otherwise, unintended operations will result. PLCs areextensively used in the manufacturing process of many industries.

DCSs are heavily used in the process industries for controlling large processoperations. Like PLCs, they include complex control computers with specialalgorithms that tightly control the position of valves, motors, and dampers tocontrol temperatures, pressures, flows, and levels of process lines and reactors.Safety systems are sometimes included with the DCS or separately from the DCSto assure safe operations in case of an out-of-control condition in the plant.

Level 2Level-two systems provide an operator interface to the control layer and maycollect data from various controllers at a plant and for consolidation to a centralcomputer which manages the data in a high performance manner. Supervisory


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


control and data acquisition (SCADA) and Human Machine Interface (HMI)provide a window for an operator to view operations and processes and control theoperation of equipment.

SCADA and HMI can be seen as a system with many data elements called tags.Typically, each tag is a monitor or a plant sensor that has a number of associatedvariables. These points can be either hard or soft. A hard data point can bean actual monitor; a soft data point can be seen as an application or softwarecalculation. Tags include the value of the tag monitored, descriptors, and healthstatus of the value.

Plant historians are often found in level-two networks as well. These applicationsprovide high-speed data collection of plant applications, sometimes at sub-secondfrequency. Large volumes of data are collected by the historian. Specialalgorithms in the historian compress the data to reduce hard disk consumption anddeliver high performance data extraction for analysis.

Many companies also deploy OLE for Process Control (OPC) servers on thelevel-one or level-two networks. OPC servers act as a bridge for communicatingto level-one systems using an industry-standard protocol.

Level 1 and 2 SummaryLevel-one and level-two systems need a deterministic network that is, theyoperate in real time and must have a high performance communications toassure timing of operations. Plant Engineering personnel are sensitive to puttingbusiness systems on these networks as they may interfere with the performanceand security of the network.

Level 3Level-three systems leverage the data received from the level two systems. SAPMII sits among the level three systems along with manufacturing executionsystems (MES), computerized maintenance management systems (CMMS),laboratory information systems (LIMS), process modeling, and optimizationsoftware. This network often is separated from the control network throughfirewalls for security purposes. Level-three systems communicate to level-twosystems most commonly.

Here SAP MII can query the data from level two systems by interacting with themthrough a Universal Data Server (UDS) and PCo or interface with other level-threesystems that receive data from level-two systems. The UDS and PCo can beinstalled on the level-two network if desired, which enhances performance.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Lesson Summary

You should now be able to: Explain the typical single plant SAP MII installation Explain the typical multi-plant SAP MII installation Explain the SAP MII deployment strategies Describe the application, network, and lifecycle considerations Explain the physical position of SAP MII in a single plant


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Lesson: SAP MII Positioning

Lesson OverviewIn this lesson you will learn about history of MII as well as future direction.


Explain how SAP MII fits in the SAP Manufacturing solution List the typical application areas of SAP MII Enumerate the business benefits of SAP MII Recount a brief history of the SAP MII application

Business ExampleUnderstanding the position of SAP MII within the SAP technology stack is animportant concept that helps drive the investment decision in the technologyand recognizes the value areas MII can generate. Without this understanding,many customers mis-position other technologies that appear to provide similarfunctionality to SAP MII, such as portals, dashboards, or integration technologies.

The SAP Manufacturing SolutionIn the complete SAP Manufacturing solution, SAP MII is positioned between SAPBusiness Suite and the plant floor solutions. Users can elect to use any or all of thecomponents included above for their manufacturing requirements. SAP MII canrun standalone, or in combination with any of the components shown.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)

SCM380 Lesson: SAP MII Positioning

Figure 10: The SAP Manufacturing Solution

SAP MII is delivered with SAP Manufacturing Execution as an out-of-the-boxsolution for integrating Manufacturing Execution with SAP ECC. The ERPconnector, also called VERPSI, includes pre-built integration templates thatdrive business processes between ECC and the execution environment for ordermanagement, material management, quality management, etc. ME is the SAPsolution for discrete manufacturing environments which controls productionexecution, tracking and tracing, genealogy, work instructions, quality, and otherrequirements in discrete parts manufacturing.

Some customers leverage SAP MII to extract and cleanse plant data for deliveryto the business intelligence cube. From there SAP Business Explorer can runenterprise reports on the BI Content. Additional integration scenarios with SAPBusinessObjects technologies are evolving, including SAP Crystal Reportsintegration and Xcelsius integration to SAP MII.

Application OverviewIn this section, we will discuss the typical applications areas of SAP MII.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Figure 11: Typical SAP MII Application Areas

Performance ManagementManufacturing intelligence is the right pillar in this diagram. The key applicationarea for manufacturing intelligence is performance management. The ability tomanage performance metrics and feedback real-time achievements is a significantdriver for improvement. Providing actionable intelligence around performancemanagement allows all employees to drive continuous improvement initiatives.Latent feedback, that is, receiving reports that are a week or a month old, is noteffective in driving behavioral change.

The first key to performance management is understanding the drivers that impactthe business performance and making these visible to all employees that can makean impact. Key Performance Indicators (KPIs) are generally created to allow theorganization to focus on areas they can impact. Dashboards that present these inreal time, with drill downs to underlying data, assists in root cause analysis ofissues preventing performance. Alerts that trigger e-mails or pagers to highlightproblems are another method for getting attention to problem areas.

SAP MII plays a key role in the presentation of these metrics, the gathering ofdata, the calculations (with associated business rules), and the presentation ofresults for general consumption.

Performance management applications with SAP MII can be extended to manycontinuous improvement activities including Six Sigma, Balanced Scorecard,and others. SAP MII dashboards are often used for delivery of performance forthese initiatives.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Companies armed with this capability can establish benchmarks using bestpractices to drive optimal performance across production lines and across plants.Significant return on investment has been shown when real-time performance canbe compared to real world targets achieved in other operating units.

Manufacturing SynchronizationManufacturing Iitegration is a critical part of the value chain for MII applications.System-to-system interoperability automates data presentation and data movement,significantly accelerating supply chain velocity. Synchronizing plant operations tothe enterprise in real time is a critical capability delivered by SAP MII.

With the ability to integrate systems, the execution of plant work processes isanother key capability of SAP MII. Eliminating the task of manually inputtingdata into ERP is solved with the data services and business logic services availablein SAP MII. Streamlined, real time data gathering and delivery reduces work load,improves accuracy and promotes an accelerated supply chain. Results includereduced inventories, improved customer deliveries and reduced cycle times.

SAP MII also plays a key role in linking enterprise activities to plant floor workers.Simplified user interfaces can be quickly deployed to allow plant floor workers toconsume enterprise data (production orders, bills of materials, material details,and so on) in context to their local work process. Equally important, interfacesenable shop floor works to appropriately feedback production events and valuesassociated with their work processes. Production confirmations, material transfers,quality characteristics, maintenance notifications, and other transactions can besimplified for the plant environment.

Linking plant floor activities to the enterprise presents dramatic shifts inperformance and increased value in a customer ERP investment. Extendingvisibility to the plant and automating work processes drives superior decisionsupport, increases accuracy, and drives business thinking to plant operations.

The Business Benefits of SAP MIIThe business benefits of SAP MII are numerous.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Increased Manufacturing ProductivitySAP MII collects data from different systems and provides relevant information inthe form of alarms, reports, and key figures available to manufacturing employees.A company-wide uniform display of analysis data using a role-based, configurabledashboard supports fast, sound decisions.

Speeds information flow Unified interface brings disparate data together in one place Enables shop floor workers to consume ERP business processes Improves on-time delivery Better customer satisfaction drives increased market share Increases agility Alerts provide real time notification of unplanned events Integrated views of data improve decision support Browser-based and mobile information delivery provides information to

anyone, anytime, anywhere

Continuous Optimization of Processes and PerformanceThe real-time analysis of the production processes enables you to use SAP MII toincrease production activity in the long term. The employees in manufacturing canmonitor, measure, and control initiatives for process improvement. These includeSix Sigma, lean manufacturing, and right-first-time manufacturing.

Improved quality Reduced rework Elimination of waste Reduces inventories, lowers safety stock Reduces operating costs

Better Equipment UtilizationSAP MII enables you to compare the activity of individual pieces of equipment orplants. Using the comparative values, you can optimize equipment utilization andrationalize unproductive equipment.

Benchmark and drive performance improvements Real time views of operating KPIs Line-to-line, shift-to-shift, and plant-to-plant comparisons Improves asset utilization Increases throughput Reduces cycle time


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Assures Operational ComplianceData gathering and reporting can speed information delivery to meet compliancerequirements in the areas of product quality, safety, and environmental.

Real-time reporting improves performance to targets Meet customer or agency reporting requirements Reduces labor

Low Total Cost of OwnershipSAP MII establishes a real-time link between manufacturing and ERP systems.Prefabricated connectors based on standards reduce the startup costs, complexity,and system costs.

Reduces operational costs Integration and intelligence in one framework Connectors eliminate the need for custom interfaces Prebuilt templates and composites speed application development

Short Amortization TimeSAP MII can usually be implemented in 90 to 120 days and therefore pays foritself very quickly. This includes system installation and application development,which demonstrates the value of the investment to a company.

Product HistoryThe predecessor of SAP MII was the Collaborative Manufacturing Suite (CMS)developed by Lighthammer Software Development Corp. SAP acquiredLighthammer in July of 2005 and first integrated this product into the group ofSAP xApp, or composite application, products. It was called xMII, or xAppManufacturing Integration and Intelligence, until January 1, 2008. Since then ithad been known as SAP MII.

Historically, CMS consisted of Illuminator for querying and visualizing thedata from underlying systems. This part of CMS contained the connectors tosystems and the options for visualizing the data using Java applets. Interactionwith this data was achieved using JavaScript. Illuminator became the data servicesand visualization services in SAP MII and represented the first release of theproduct in 1998.

Lighthammer added another capability to the product called the Quality Portal,which included the statistical process control (SPC) calculation and chartingfunctions to the CMS suite.

Lastly, Xacute was added to the CMS suite. This was the first release of atransactional development environment using a graphical flow chart style tool,that was able to use the connections from the Illuminator part to access data


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


and transform results through complex program logic, data manipulation andcalculation. Xacute was also the focus area for transactional integration to SAPBusiness Suite. Xacute became the business logic services in SAP MII.

Hint: This background knowledge about the product history can help youunderstand why you will see terms like xMII, Lighthammer, Illuminator,and Xacute in some of the older documentation and file conventions.

SAP MII VersionsThe following are the SAP MII versions released since SAP acquiredLighthammer.

MII 11.5The initial release of SAP xMII was 11.5, which only ran on a Microsoft serverunder IIS. A Java Servlet engine was included with the product, creating a verysmall footprint and extremely simple system installation. This version wassunsetted in 2008.

MII 12.0The next major release of the product was SAP MII 12.0, released in 2007. Thiswas the first release of SAP MII running on SAP NetWeaver. The movement ofSAP MII to SAP NetWeaver enabled multi-platform support and included theuse of the SAP NetWeaver database for storing and managing the application,content and users. Supportability was another key capability delivered to SAP MIIthrough SAP NetWeaver. A unified workbench brought all of the developmentfunctions of SAP MII into one environment, making the data access, businesslogic, and visualization features available in one tool.

MII 12.1SAP MII 12.1 was released in 2009, leveraging the SAP NetWeaver CompositionEnvironment (SAP NetWeaver CE) platform. The SAP NetWeaver CE platformimproved the implementation and management experience of the solution and SAPMII now leverages a number of key services in SAP NetWeaver CE to improve thecapabilities of our offering. Since SAP MII applications are stored in the database,the solution environment can now manage projects and use the NetWeaverDevelopment Infrastructure (NWDI) for transport. SAP MII also uses the queuingand logging features of SAP NetWeaver to increase transactional reliability. Userinterface improvements and accessibility features have also been included in thisversion. MII 12.1 also has broad language support including English, German,French, Spanish, Portuguese, Chinese, Japanese, Russian, Korean, and Hebrew.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


MII 12.2SAP MII 12.2 is planned for release in 2010. The most notable feature of thisrelease is a semantic modeling layer, called manufacturing data object (MDO).With MDO, the persistence of data objects can be easily stored into a canonicalmodel within the SAP MII database.

Figure 12: SAP MII Product Overview and Evolution


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Lesson Summary

You should now be able to: Explain how SAP MII fits in the SAP Manufacturing solution List the typical application areas of SAP MII Enumerate the business benefits of SAP MII Recount a brief history of the SAP MII application


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)

SCM380 Unit Summary

Unit SummaryYou should now be able to: Describe the purpose of SAP MII Explain where SAP MII fits in the manufacturing domain List the services SAP MII provides Describe the SAP MII integration landscape Explain how SAP MII integrates with SAP ECC Explain the typical single plant SAP MII installation Explain the typical multi-plant SAP MII installation Explain the SAP MII deployment strategies Describe the application, network, and lifecycle considerations Explain the physical position of SAP MII in a single plant Explain how SAP MII fits in the SAP Manufacturing solution List the typical application areas of SAP MII Enumerate the business benefits of SAP MII Recount a brief history of the SAP MII application


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)

Unit Summary SCM380


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)

This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)

Unit 2Data and Visualization Services:

Introduction

Unit OverviewIn this unit, we begin to build the foundational knowledge necessary to use SAPMII to its full potential. You will become familiar with the SAP MII Workbench,which consists of a single editor for developing SAP MII content and web content.You will learn about SAPa rs and how to create data server connections. You willgain an understanding of different types of query and display templates and howthey are created. You will also be introduced to SAP MII XML format, which isutilized across SAP MII.

Unit ObjectivesAfter completing this unit, you will be able to:

Differentiate between the Catalog, Web, and Meta-inf tabs Explain how to create an SAP MII project Describe the recommended project structure Leverage a common folder Import and export files List the ways SAP MII can connect to data sources Identify the characteristics of an SAP MII connector Explain the concept of an SAP MII data server Describe the various types of connectors and their differences List the categories of data server properties and give examples of each Explain data server permissioning Explain the concept of reusability as it applies to data servers Create data server connections Explain the concept of a query template Name the different query template types Explain the idea of query modes and methods List the screens that are common to all query types


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)

Unit 2: Data and Visualization Services: Introduction SCM380

Describe the structure and importance of an SAP MII XML formatteddocument

Explain the importance of column metadata Discuss the concept of reusability as it applies to queries Create and test a basic tag query Name the available testing content types Explain the concept of an applet Explain the concept of a display template Name the different display template types List the screens common to most display types Understand what it means to refresh a display Understand the concept of reusability as it applies to display templates Build and test a basic display template

Unit ContentsLesson: SAP MII Workbench Overview... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Exercise 1: Create a Project and Folders .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Lesson: SAP MII Data Servers and Connectors.. . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Procedure: Creating an SAP MII Data Server .. . . . . . . . . . . . . . . . . . . . . . . . . . 52Procedure: Assigning Roles to the Data Server.. . . . . . . . . . . . . . . . . . . . . . . . 53

Lesson: Introduction to Query Templates... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Procedure: Creating a Query (Basic Procedure).. . . . . . . . . . . . . . . . . . . . . . . 62Exercise 2: Create and Test a Tag Query ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Exercise 3: Understand SAP MII XML Format .. . . . . . . . . . . . . . . . . . . . . . . . . 67

Lesson: Introduction to Display Templates ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Procedure: Creating a Display Template (Basic Procedure) .. . . . . . . . . 78Exercise 4: Build a Bar Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)

SCM380 Lesson: SAP MII Workbench Overview

Lesson: SAP MII Workbench Overview

Lesson OverviewThe SAP MII Workbench is an environment that simplifies the development oftransactions, query and display templates, animated objects, reference documents,and user content by combining several user interfaces into one.


Differentiate between the Catalog, Web, and Meta-inf tabs Explain how to create an SAP MII project Describe the recommended project structure Leverage a common folder Import and export files

Business ExampleAs a member of the project team responsible for implementing SAP MIIapplications, you need to use the SAP MII Workbench to work on different SAPMII development tasks, such as database queries, data displays, and businesslogic transactions.

Opening the WorkbenchFrom the SAP MII menu, choose Data Services SAP MII Workbench. The SAPMII Workbench may take a minute or so to load.

The initial screen is divided into three parts: the project and file browsing area,the information pane, which changes dependent upon the current developmenttask, and the development area for authoring queries, displays, and transactions,and other editing other content.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Figure 13: The Initial Workbench Screen

ProjectsA project is a root-level container that is used as an organizational unit for objectsrelated to queries, displays, transactions, and web content. A project can consist ofboth SAP MII and Web content. Organizing content in a project-type structure hasimportant administrative implications:

Projects can be imported and exported. Properties can be shared among transactions within a project. Content management is administered at the project level.

Hint: To learn more about content management, some resources includethe SAP MII 12.1 Help for Source Control, SAP Help Documentation forNWDI, and the SAP Developer Network (SDN).

When a project is created, it will be present across three tabbed browser areas:the Catalog, Web, and Meta-Inf areas.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Figure 14: The Tabbed Browser Areas

The Catalog TabThe Catalog tab holds all SAP MII content: query and display templates, businesslogic transactions, and animated objects, which are stored in folders inside ofprojects.

Hint: Animated objects are SVG images that you impart motion or actionto. Refer to the Help documentation for further information.

The Web TabThe Web tab holds all Web content, such as HTML and IRPT web pages, XMLfiles, and images, which are stored in projects.

Note: You will learn about IRPT pages and the functionality they providein a future lesson.

The Meta-Inf TabThe Meta-Inf tab holds all project-specific shared properties and localizationtokens. Shared properties can be utilized in any business logic transactionwithin a project. Localization enables you to make your SAP MII applicationsuser-language specific.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Creating an SAP MII ProjectA project can be created in the SAP MII Workbench by first selecting the servername at the top of the Catalog tab and then choosing File New Project fromthe top menu.. A project can also be created by right-clicking on the server nameand choosing New Project. Once the project is created, it will be visible on theWeb and Meta-Inf tabs as well.

Leveraging a Common Project or FolderIt is recommended that a common project be created for objects shared acrossprojects. These objects may include CSS stylesheets, images, company-themeddisplay templates, utility queries, and utility transactions. A common folder canbe created within a project itself for content shared at the project level. Leveraginga common project or folder promotes reuse, eliminates duplication, and savesdevelopment time.

Creating FoldersTo create a folder within the project, right-click on the project and choose NewFolder.

Note: Unlike projects, folders are created on the current in-focus tab only.Thus, if you created folders on the Catalog tab, you will need to recreatethem on the Web tab, and vice-versa.

Note: When a project is created, it will contain a default folder calledWEBon the Web tab. The mirrored folder structure is created inside this folder.

Project StructureProject files should be stored based on functional behavior and not by objecttype. For example, it is strongly recommended that you do not create a separatefolder for queries, a separate folder for charts, a separate folder for grids, and soon, but rather group related objects within the same folder. From a maintenancestandpoint, it is much easier to find the component parts of an application whenfiles are stored as a functional area, thereby eliminating the need to search throughseparate folders to find all the necessary pieces.

It is also recommended that to the extent possible, the folder structure be mirroredon the Catalog and Web tabs.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Importing and Exporting FilesFiles can be imported and exported from the SAP MII Workbench from and toavailable resources. For example, you may have a stylesheet or image you wantto retrieve from your local machine.

Note: Projects are exported or imported using the System Management Projects option of the SAP MII main menu.

You can import a file into a project folder by choosing File Import from the topmenu or by right-clicking on the desired folder and choosing Import. You can thenbrowse for and upload the file from an available resource.

Exporting files is done in a similar manner; select the file you wish to export andchoose File Export from the top menu or right-click on the file and chooseExport. You can then browse to the desired available resource location.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)



This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Exercise 1: Create a Project and Folders

Exercise ObjectivesAfter completing this exercise, you will be able to: Create a project Create folders within a project

Business ExampleAs the member of the team developing an SAP MII application, you need to knowhow to create projects and folders.

Task 1:Create a new project in the SAP MII Workbench.

1. Open the logon page to SAP MII using the URL provided by your instructor.The URL will be in the format:http://[ServerName]:[Port]/XMII

Log on to SAP MII using the username and password provided by yourinstructor. Open the SAP MII Workbench from the Data Services menuoption.

2. Create a project on the Catalog tab called SCM380_##, where ## equals theparticipant number assigned to you by your instructor.

3. Note that your project is now visible on the Catalog tab. Check the Weband Meta-Inf tabs.

Task 2:Create folders under your project.

1. Create a folder called Basics and a folder called Common under yourproject. Remember that you must create these folders on both the Catalogand Web tabs.

2. Add a Basics folder and a Common folder to your project on the Web tab.

ResultYour project should now contain a Basics folder and a Common folder.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Solution 1: Create a Project and FoldersTask 1:Create a new project in the SAP MII Workbench.

1. Open the logon page to SAP MII using the URL provided by your instructor.The URL will be in the format:http://[ServerName]:[Port]/XMII

Log on to SAP MII using the username and password provided by yourinstructor. Open the SAP MII Workbench from the Data Services menuoption.

a) Open the browser and enter the URL provided by the instructor.

b) Log on using the username and password provided by the instructor.

c) From the SAPMII menu, chooseData Services SAPMII Workbench.

Hint: The SAP MII Workbench may take a minute or two toopen.

2. Create a project on the Catalog tab called SCM380_##, where ## equals theparticipant number assigned to you by your instructor.

a) From the Catalog tab, highlight the server name. From the top menu,choose File New Project, or right-click on the server name andchoose New Project from the context menu.

b) In the Enter project name dialog, enter SCM380_##, where ## is yourparticipant number. Click OK when you are finished.

3. Note that your project is now visible on the Catalog tab. Check the Weband Meta-Inf tabs.

a) After noting that your project has been created on the Catalog, switchto theWeb andMeta-Inf tabs and observe that your project exists acrossthese tabs as well.

Continued on next page


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Task 2:Create folders under your project.

1. Create a folder called Basics and a folder called Common under yourproject. Remember that you must create these folders on both the Catalogand Web tabs.

a) From the Catalog tab, right-click on your SCM380_## project andchoose New Folder.

b) Enter the folder name as Basics, and then click OK.

c) Repeat the step above and name the folder Common.

2. Add a Basics folder and a Common folder to your project on the Web tab.

a) Switch to the Web tab, right-click on the default WEB folder in yourproject, and follow the same procedure you used to create folders onthe Catalog tab.

ResultYour project should now contain a Basics folder and a Common folder.


This

mat

eria

l is

for t

he E

xclu

sive

Use

of R

egis

tere

d S

tude

nts

in S

AP

Cou

rse

Del

iver

ies

(UK

)


Lesson Summary

You should now be able to: Differentiate between the Catalog, Web, and Meta-inf tabs Explain how to create an SAP MII project Describe the recommended project structure Leverage a common folder Import and export