Me and couple of my friends namely Abesh Bhattacharjee, Dipankar Saha, Tufale Ashai have written some articles based on SAP MII version 14.0 and above. Have a look at these articles. Hopefully these would be good and informative read for you.

Create Fail-Safe Composite Applications by Implementing Foolproof Error-Handling Mechanisms in SAP MII

Brief Summary: This article talks of creating fail safe transactions in SAP MII BLS. Topics covered in this article are Exception Handling, SQL Transaction Support, SAP MII Debugger and Guaranteed Delivery Concept in SAP MII.

Author: Abesh Bhattacharjee

Configuring and Monitoring Key Performance Indicators in SAP MII

Brief Summary: This article talks about the KPI framework of SAP MII and how to configure, visualize and monitor the KPIs.

Author:Tufale Ashai

How to Develop Real-Time Analytics and a Monitoring Dashboard on SAP MII SSCE

Brief Summary: This article talks about Self-Service Composition Environment (SSCE) and how to develop analytical and monitoring dashboards in SSCE.

Author:Tufale Ashai

How to Integrate Enterprise Systems and an MES Using SAP MII by

Brief Summary: This article talks about how to integrate data from ERP and MES system and consume it in SAP MII.

Author: Dipankar Saha

Enable Real-Time Integration with Manufacturing Automation Using SAP MII by

Brief Summary: This article talks about how to integrate SAP MII with manufacturing automation systems using SAP Plant Connectivity(PCo).

Author:Dipankar Saha

How to Use Manufacturing Data Objects to Develop Composite Applications in SAP MII

Brief Summary: This article talks about how to Manufacturing Data Objects (MDO) and how these can be used to integrate data from various resources and then consumed.

Author: Rohit Negi

Maintain an Asset Hierarchy Using the Plant Information Catalog in SAP MII

Brief Summary: This article talks about Plant Information Catalog (PIC) and how it can used to maintain asset hierarchy and integrate date from shop floor and enterprise system in PIC

Author: Rohit Negi

These articles are published in SAPexperts and are also released as a book(anthology) which can be bought from Sap Insider Store

Happy Reading

Many modern web development editors are now able to provide some level of autocomplete for JavaScript similar to the functionality enjoyed by java/.net developers etc. Typically some import and configuration is required for the editor to be aware of the JavaScript libraries you may be using in your project.  For UI5  Robin van het Hof  has written an excellent  blog  outlining how to get the UI5 or any JavaScript libraries into Webstorm. (note: there also appears to be a plugin available now as well ).  This is pretty straight forward as the UI5 libraries are easily available for download  via the open UI5 project. This is not the case for the MII libraries so how can we get them? This turns out to be relatively simple.

First create a new default irpt of html page in MII. Your page should only contain the script tag for the MII bootstrap.js file.  It should look similar to this:

Then simply launch or load this page in the Chrome web browser. Select 'Save page as..'  and save with a useful name like 'MII.html'  and  save as type ‘Webpage, complete’.  You should now have an html file and a directory. One is the html from your webpage and the directory contains all the JavaScript and css sources used by the page.

You may want to remove the UI5 sources and css files that were also pulled in if you plan import them separately. These are the sap-ui-core.js and library(*).css files. Now that you have the MII sources follow the instructions in Robin’s blogor for your specific development environment to import them and make them available in your preferred editor. You should then be able to enjoy autocomplete and api browsing with the MII javascript libraries.

A version of this blog was published here

As a global leading ICT solution provider, Huawei is committed to provide the innovation ICT solution, products and services for telecom carriers, enterprises, and consumers. Its eLTE broadband access solution, based on cutting-edge 4G LTE wireless technology, offers the enterprise customers highly integrated small-scale core network, distributed base station and terminal access equipment with the features of flexible networking, high reliability and so on. At the same time, the eLTE solution can be deeply adapted the industry requirements and meet the needs of the emergency network deployment and business applications in the harsh industrial environment, and will bring the brand new possibility for the future diversification applications in industry.

As a professional service supplier, Flame Company provides the integrated operation management service for engineering equipment, technical service for oil drilling engineering, and industry-scale Internet of Thing (IoT) service. In addition, it also offers the petroleum engineering services for oilfield chemistry customized, well logging, directional well, gas drilling and so on.

Nowadays, there are growing needs of wireless full coverage, connected mobile devices, real-time analysis, big data mining, predictive maintenance and so on in oil & gas industry. How to satisfy all above needs becomes a critical challenge to all the solution suppliers. As the technology of 4G communication and real-time data analysis platform becoming mature, SAP, Huawei and Flame find the cooperation opportunity: Via eLTE private broadband network, we can transfer the machine data which is fetched through Flame Data Acquisition Unit and SAP PCo (Plant Connectivity) to the SAP MII on HANA platform. In this way, we can fuse of the Flame Equipment Maintenance and Condition Based Monitor solution (OT) with SAP Enterprise Asset Management (in ERP) solution (IT). With this fusion, the base was provided to implement SAP PdMS (Predictive Maintenance Service) and big data analyst solutions on SAP HANA.

To verify the feasibility and stability of the machine data acquisition solution, SAP GPO PSC (Partner Solution Center) allied with Huawei and Flame to build a test environment in Huawei eLTE laboratory, we simulated the machine data acquisition scenario and the hardware/software included: PLC (SIEMENS SIMATIC S7-300), Flame Data Acquisition Unit (RSDA Drilling Site Data Acquisition Unit FL2000-AA), Huawei eLTE core network (eSCN230), Huawei distributed base station (DBS3900), Huawei CPE, KEPServerEX 5 (OPC Server), SAP MII 15.0 and SAP PCo 15.0.

SAP MII (Manufacturing Integration & Intelligence) is a service-based composition environment (SOA architecture) consisting of Data Services (integrating with the various data sources from shop-floor systems), Business Logic Services, Visualization Services (UI development basing on SAPUI5), Analytic Services, Web Services and so on. In addition, the environment has some pre-defined functionalities, such as OEE (Overall Equipment Efficiency) solution, KPI Framework, PIC Plant Information Catalog model self definition design and so on. The customers can rapidly develop their own solutions based on these functionalities.

SAP PCo (Plant Connectivity) is the next generation of high performance manufacturing connector software. It can connect to the industry-specific standard data sources (i.e. control systems, realtime database systems, SPC systems and so on). PCo agents support the following standardized software interfaces: OPC DA, OPC HDA, OPC A&E, OPC UA, OLE DB, ODBC, Modbus, GE Fanuc Proficy Historian, OSISoft PI, Socket, IP21, Citect, File Monitor Agent.

We tested the connections in three different ways according to the scenarios on the customers’ side are diverse:

1. 1. To fetch data from PLCs with multiple models from different manufactures, we use KEPServerEX 5 as the OPC server to connect to all the PLCs. Then we can transfer the machine data to SAP MII with the SAP PCo OPC DA Agent as the bridge between KEPServerEX 5 and MII via Huawei eLTE private network.
2. 2.  We used SAP PCo Socket Agent connecting to Flame DAU and transferring the data to SAP MII via Huawei eLTE private network when the machine can be connected to Flame Data Acquisition Unit directly. On MII side, we built the transaction logic to parse the socket stream and filter out tag information that can be used to do business analysis.
3. 3. The developer from Flame developed the customized connector FlameAgent with data parse for their own data acquisition unit and transferred the data of tag name (i.e. rotate rate, vibration frequency etc. ) to SAP MII via Huawei eLTE private network utilizing SAP PCo SDK toolkit.  

The overall architecture is illustrated as following:

Finally, all three connection paths were verified and passed the test. Comparatively, the performance will be better (Especially, it can avoid a lot of network security related issues) if we install OPC Server and SAP PCo on the same physical server. Meanwhile, we can also install SAP PCo into Flame Data Acquisition Unit or Huawei CPE to decrease hardware investment.

This co-innovation solution by SAP, Huawei and Flame provides a wireless full coverage of production, management and operation for oil & gas industry via eLTE broadband private network. With the mobile devices, the field staff not only can use voice trunking dispatch, but also can transfer the site video and production information to the operation management center in real time to improve the efficiency of operation and management. By integrating the data from the site machines, operation management and business management, the production operation information from line of business (i.e. productions, equipment, HSE, logistics etc.) can be transferred to Headquarter to manage the multi-production sites in real time, big data analyst optimization and completely eliminate the operational risks and potential accidents before the happening.

The co-innovated solution will enhance the competitiveness and meet the actual needs of customers since SAP can supply operational management solutions for 11 lines of business in Oil&Gas E&P industry and Huawei can supply cutting-edge 4G wireless broadband network solutions.

Hi all ,

As we usually see many incidents related to the JAVA pop-ups when we open the Workbench or the applets ,

I have decided to share with you some tips that will help us to workaround it.

I have personally tried them and worked.

If you are using a build below 1.8 and above 1.7.0_11 :

Navigate to the "JAVA Control Panel" and go to the "Security" tab.

You will have 2 options :

1-Set the security level to Medium , this will allow all the Java applications to run.

2-Add the MII portal(<URL>:<PORT>/) to the Exception Site List by clicking "Edit Site List".

If you are using a build above 1.8 :

For Java version 8 , you will not see Medium option on the security level.

So , your only option is to add the MII portal (<URL>:<PORT>/) to the Exception Site List.

You need to include only URL and Port for this to work , like : Example.MII:5000/

Builds below 1.7.0_11 :

Workaround not necessary because security pop-ups were introduced on versions above 1.7.0_11.

Reminding that this is not the SAP official solution , check note number 1955567 for a concrete approach.

See also :

All these tips are available on the KBA note number 2040424.

Thanks and all the best ,

Willian.

Introduction

CORS or cross origin resource sharing is a W3C specification which allows scripts to make a request to a domain other than the one which it is hosted on.

When a browser based application sends a request to a server in a different domain it is called a "Cross domain" request.

A valid CORS request has a header called domain which is automatically added by the browser.

All browsers traditionally follow the "same origin" policy. This means if a web page say 'foo.com' wants to access data in a second web page say 'bar.com', both foo.com and bar.com should have the same origin. Origin is defined as a combination of "host name", "port number" and "URI scheme". This policy prevents a malicious script on one page from obtaining access to sensitive data on another web page through that page's Document Object Model.

Let's take the use case where in foo.com and bar.com have separate origins. The browser itself stops these requests as part of the security measure which prevents scripts from A to access sensitive data from B. However, if the server hosting bar.com has a few special headers added, bar.com can be accessed by foo.com. In that, CORS requires a co-ordination between client and server.

CORS is currently supported in the following browsers:

• Chrome 3+
• Firefox 3.5+
• Opera 12+
• Safari 4+
• Internet Explorer 8+

To query whether CORS is supported or not the following site comes in handy:

http://caniuse.com/#search=cors

Types of CORS requests

Cross-origin requests can be divided into two categories:

1. Simple requests
2. Complex requests

Simple requests are requests that meet the following criteria:

• HTTP Method matches (case-sensitive) one of:
  • HEAD
  • GET
  • POST
• HTTP Headers matches (case-insensitive):
  • Accept
  • Accept-Language
  • Content-Language
  • Last-Event-ID
  • Content-Type, but only if the value is one of:
    • application/x-www-form-urlencoded
    • multipart/form-data
    • text/plain

Simple requests are characterized as such because they can already be made from a browser without using CORS.

Understanding CORS headers

• Access-Control-Allow-Origin: Any CORS request always has an "Origin" header. Omitting this header from the request will cause the request to any server fail. A typical http request would look like:

               POST /cors HTTP/1.1
               Origin: http://foo.com


         The server receiving this request has two options here:

1. It can return the response such that the value of header "Access-Control-Allow-Origin" is foo.com. This means Origin "foo.com" is allowed                     by the server to make a CORS request.
2. The response is returned such that the value of header "Access-Control-Allow-Origin" is "*". "*" is a wild card which allows any server to make a           CORS request.

• Access-Control-Allow-Credentials (optional): This is an option header sent across by a server in case the request has the 'withCredentials' flag set to true. The only valid for this header sent across by the server is "true".  This header indicates whether cookies are allowed in CORS request. If the server does not wish to allow cookies, it omits this header from the response.

• Access-Control-Expose-Headers (optional) : This is an optional response header returned by the server. This values of this header is a comma separated list of headers exposed to the client. Any client sending a CORS request  can access the following headers of the http response:
  • Cache-Control
  • Content-Language
  • Content-Type
  • Expires
  • Last-Modified
  • Pragma

     If the server wishes to expose additional headers it should return the value of this header.

CORS Preflight Request

A CORS preflight request gets sent across before an actual http request is made. This is sent across automatically by the browser. It is a way of asking permission to make a CORS request. Typically this request gets triggered for content type "application/json". The OPTIONS http method is used for a CORS preflight.

The response to the preflight request can be cached so that it is not made repeatedly. A CORS preflight consists of the "Origin" header and one of the following:

1. Access-Control-Request-Method - The HTTP method of the actual request. This request header is always included, even if the HTTP method is a simple HTTP method as defined earlier (GET, POST, HEAD).
2. Access-Control-Request-Headers - A comma-delimited list of non-simple headers that are included in the request.

In response to the above request headers the server sends across the following in addition to Access-Control-Allow-Origin header::

Access-Control-Allow-Methods (required) - Comma-delimited list of the supported HTTP methods. Although the preflight request asks permissions for a single HTTP method, this response header can include the list of all supported HTTP methods. This is helpful because the preflight response may be cached, so a single preflight response can contain details about multiple request types.

Access-Control-Allow-Headers(required if the request has an Access-Control-Request-Headers header) - Comma-delimited list of the supported request headers. Like the Access-Control-Allow-Methods header above, this can list all the headers supported by the server (not only the headers requested in the preflight request).

Access-Control-Max-Age (optional) - Making a preflight request on 'every' request becomes expensive, since the browser is making two requests for every client request. The value of this header allows the preflight response to be cached for a specified number of seconds.

CORS support within MII

Support for CORS has been added in MII in 14.0 SP07 and MII 15.0 SP05. The headers explained above need to be added to System properties as below:

Each of these properties correspond to a header stated in section above.

If an MII server Administrator intends to allow CORS he should check Allow Cross Origin Resource Sharing.

Allowed hosts: The hosts which are allowed to make CORS requests. A "*" allows all hosts to make these requests.

Allow credentials: This flag enables MII server to add Access-Control-Allow-Credentials to the response.

Expose Headers: Comma separated list of  headers allowed by MII server.

Allow Methods:Comma separated list of http methods allowed for CORS.

Allow Headers: Which headers are allowed in response to preflight request having "Access-Control-Request-Headers"

Maximum Age: Time in seconds for which the preflight response can be cached.

All these properties should be set by MII administrator in order to allow CORS. Administrators should be careful while setting these properties as they might lead to the MII system becoming vulnerable to security threats.

This post today is for all of my Mac OS X users.

For the longest time, I couldn't get my Workbench to work correctly. Every time I would select text inside of the Workbench editor, whether it be an SQL Query or an IRPT, the Workbench would freeze up and go into 'Application Not Responding'. Oh that dreaded pinwheel of death.

No matter what version of Java I was running, or how many times I cleared my java cache, or uninstalled and reinstalled, I couldn't get it figured out. Why was this only happening to me? No one in the developer forums had any idea what I was talking about.

I was lost.

Until I just recently stumbled upon the solution.

If you're using an everyday point and click mouse, while running a mouse map editor (ex. Microsoft Intellipoint, Better Touch Tool, etc.) these problems will happen to you. For what ever reason, I'm not sure.

And the only workaround that I have for this is to uninstall those, and relaunch your Workbench.

I hope this post is able to help someone, because I know first hand how frustrating this can be.

Recently due to a project requirement, I had to integrate PCo for reading excel(.xlsx) with SAP MII. Thought of sharing the details so that if anyone has similar requirement can easily follow the steps and achieve the same.

• Tested Environment :

           SAP MII Version :  12.2 SP6 Patch 15

           SAP PCO : PCo 2.1.5.1

          Installation Package : Microsoft Access DB Engine X32-bit

           Connector Type : OLEDB

The PCo and Microsoft Access DB Engine should be installed on the same server.

• Note: SAP MII version and PCo version is independent  and this should be configurable if the required provider exists, as to read excel(.xlsx) through PCo into MII is to have the SAP recommended provider “Microsoft Office 12.0 Access Database Engine OLE DB Provider”.

        Refer the following links for details:

        http://scn.sap.com/thread/3786499

        https://www.microsoft.com/en-us/download/details.aspx?id=13255

        http://help.sap.com/saphelp_mii140sp04/helpdata/en/4e/73a42090c5455780c43287923c1022/content.htm

• Steps :
  • Install the PCo 2.1.5.1 in the Server(to be connected with MII data server) with Microsoft Access DB Engine X32 bit to get the provider to read excel file(.xlsx).
  • Configure the Source System in PCo management console by following the steps below:
    1. Create New Source System.

                   2.Select Source System Type as “OLE DB Agent” , provide a relevant name and description to it and click “OK”

                     3.Once the Source is created click on Configure and set the Data Link Properties:

• Provider Tab: Select Provider “Microsoft Office 12.0 Access Database Engine OLE DB Provider” and click on Next.

• Next takes you to Connection , put the exact file path to be read in the Data Source field, username can be put anything for the time being as this would be overridden while configuring Agent instance.

• Make sure that the File is not open in anywhere while testing the connection and click on test connection, on successful connection you will get the following pop up.

• In the Advanced tab, check on the access permissions you would like to give the user.

• In the All Tab you will see in Data Source the exact file path you provided earlier( Kept blank here for project specific confidentiality), Extended Properties should have Value “Excel 8.0;HDR=YES” and Persist Security Info should have Value False as shown below:

• Click "OK" to save the Source as shown above.

• Select the Agent you just created , and Add an Agent Instance against that.
  • Source System should have the Source Name selected, give an appropriate Agent Name and Description, and Click OK.

• Configure the Agent Instance further by giving the Service Username and relevant Password of the server.

• Check the Legacy Type, put the Port no(9000 is default port)

• Save the Agent Instance.

• Go to services.msc and provide the system username and confirm the password again, because sometimes the PCo agent is not able to recognize credential provided initially during agent instance configuration and gives error in PCo Log. The system username and password should be same as you have put in earlier step while configuring the PCo Agent.

• In the Windows Firewall with Advanced Security, check if the port 9000 is added, if not add the respective port here in Inbound Rules.

• Configure the MII Data Server to read the excel file through the Connector. Current configuration done via OLEDB Connector as:

                       In the Settings, check the Enabled box, in the Connection tab provide the IP/Server Name of the PCo installed machine and also provide the port as configured for  in the PCo[9000 in this case].

                      On enabling check status further, it should be in running mode:

• Open MII WorkBench, Open an SQL Query, select the Data server “Test Excel” and choose “Fixed Query” Mode, and go to Query, you will see all the relevant columns available in the excel sheet per worksheets available and you can apply a simple select * from [<tablename>].

   Now you are able to access all the Excel Sheet data you needed, and you can use it further as per your requirement.

   Hope this blog will be helpful to you guys.

   Also my special Thanks to Steve Stubbs for his valuable suggestions during my learning process for PCo.

SAP MII is a well know product to provide integration and intelligence capabilities to integrate disparate system in shop floor and also to create plant performance management dashboard for different roles involved in the company. SAP MII is a manufacturing platform which provided modelling capabilities to retrieving the data, writing business logic, visualization data into different charts/controls, integrating data to any system with different standards. One of the key missing feature in MII was a modeling tool to create the dashboard quickly which can be used for IT developer and also by a business person with minimum training. MII Self Service Composition environment was added as part of MII 15.o release providing a HTML5 based design tool to create plant performance management dashboard by simply dragging and dropping different MII content object and configuring it to your need. the tool has been continuously being evolved in 15.1 release also providing a variety of use cases to cover almost all type of visualization capabilities.

Using SSCE, you could create any type of layout and drag any of the MII content i.e. Query template, design template, MDO, KPI, resource files, PIC and UI elements to create any type of dashboard.

Additionally it provides some of the key features out of box as mentioned below.

1. Authorization control on the dashboard in terms of who can modify and view the dashboard.
2. Out of box compatibility for mobile devices.
3. Ability to do where used of any MII content and PIC to find which dashboard it is being used.
4. Built in Alert Integration
5. Uniform time and PIC control from the top of the dashboard
6. Header/Footer integration
7. Configuration of events for cross cell integration
8. Ability to build custom side panel to integrate any other objects into SSCE visualization
9. Integration of PIC sensor data on a 3D image
   

Using SSCE, one can create the dashboard of different needs very quickly. Below find some detail how to documents for each of the functionality available in SSCE which could help in quick realization of your needs.

Manufacturing end to end process is generally being divided across 4 different layers where in top layer is primary dominated by planning system like PLM, ERP, SCM etc know as IT systems  and bottom layer is primarily dominated by manufacturing execution system, and Manufacturing integration system , OPC server, historian, DCS, PLC, SCADA, etc. known as Operational technology systems. To support IoT and industry 4.0, IT system and Operational systems need to convergence seamlessly to bring a great insight for action by merging data from these 2 layers. There had been significant improvement done in SAP MII over the period of 2-3 years to bring these two worlds together, helping our customer to get right information. Here are some of the key functionality providing IT/OT convergence.

1. Plant Information Catalog - Plant information catalog was introduce in MII 14.0 to organize vast variety of sensor coming from plant automation system in a logical hierarchical  format making it quite easy for the business user to find any sensor data without knowing the technical name of the sensor. Plant information catalog can be used to depict equipment structure along with measurement points associated with different equipment. Plant information catalog was enhanced to bring the PP or PM hierarchy from any of the ERP system, providing the functional context available in your planning system. The leaf of the plant information catalog on one side will point to a tag/sensor mapped to automation layer and on the other side it can be mapped to a measurement point from ERP. This is one of the great example where IT system ERP PP and PM hierarchy is linked with sensor data coming from automation layer providing greater insights. Below screen shot shows how PP/PM hierarchy with measurement point can be mapped in PIC

2. Data converse of IT and OT system - Once the PIC is maintained, user can retrieve sensor data along with the business context using catalog query e.g.  historical/current value of boiler pressure along with which functional location, equipment does it belong to. This helps conversing data from IT and OT system when retrieving data. In single query, user can get sensor data along with business context from SAP ERP system.

here is the current value of the tag returned from catalog query

the below row set is about which plant and equipment number does it belong

3. Notification events with business context - the other use case  of IT and OT convergence is brining business context along with sensor data when an event is raised for unexpected tag values. In this scenario, MII has been enhanced to create notification from MII helping to bind business context from PIC along with the tag values in the notification payload. This greatly helps in sending all relevant information in the notification enabling to make a call to core ECC system without doing any additional look up. Check the how to doc for this topic as below.

MII 15.0 -  Remote PCo Notification Management how to doc https://scn.sap.com/docs/DOC-62440

MII 15.1 - Remote PCo Notification Management how to doc - https://scn.sap.com/docs/DOC-69623

Notification creation with tags and business context together.

Browse the tags from PIC

Bind the context from PIC nodes like equipment ID

4. In the area of BigData, customer would like to bring the IT and OT data into central HANA for doing high sophisticated analysis and run predictive algorithm to find root cause. Business suite system can be replicated to central HANA using different option and for OT data MII has been enhanced to federate MII PCO queries into HANA as virtual table which can then be used in calculation views, stored procedures for detail analysis with Lumira  and also for prediction.  Additionally, using pco notification along with business context from PIC, customer can stream the data into HANA using pco ESP destination brining IT and OT data together in HANA for further analysis.

PCO query in workbench

Mapped as a separate virtual table in HANA

Query on top of virtual table, returns the data on the fly from historian.

How to Doc for HANA SDA Integration with MII - https://scn.sap.com/docs/DOC-69597

5. Energy Monitoring and Analysis - another use case of IT, OT convergence is ability to do energy analysis across your plant structure depicted as PM/PP hierarchy coming from IT system and meter data coming from OT layer. MII 15.1 has added the capability to store the equidistant meter data in KPI and link this data with Plant Information Catalog leaf node and then providing query capabilities to ask question like give hourly energy consumption for plant Houston, considering equipment of type Driller and group by line Vendor where in equipment category is a property for machine and Vendor is property of Line node. This is also a very good use case of combining IT, OT data to for managing the energy in the plant, providing greater insight for doing corrective actions.

KPI with equidistant option to store meter data

data for different meter with same equidistant option is stored in single KPI for which data is shown as below

after linking the KPI with PIC structure, queries like below can be asked.

and dashboard like below are possible using SSCE.

How to doc for Energy Monitoring with MII objects - https://scn.sap.com/docs/DOC-69627

Manufacturing companies need to keep track of some of the key cost in order to be competitive in the market. One of the most important aspect is energy cost which play a key factor in the cost of the material being produced. They need to have a complete visibility of  energy consumption by line, product etc so that it is easy to identify any leaks and hence take corrective action. Generally, customer tend to create custom applications on top of MII to do the energy analysis which are not flexible and easy to roll out to multiple plants. Keeping this in the mind, MII provided capability of energy monitoring and analysis as part of SAP MII 15.1. the main objective is collect the energy data once without any business context and provide analytic capabilities with context available in PIC and production events i.e. order history, resource status available in SAP OEE, SAP ME or any 3rd party system. Here is how you can use the energy monitoring capability in MII which is a very good use case of IT, OT convergence providing the ability to do energy analysis across your plant structure depicted as PM/PP hierarchy coming from IT system and meter data coming from OT layer.

                1. Master Data - one of the key master data for energy analysis is defining the hierarchy structure against which the analysis needs to be done i.e. facility hierarchy, organization hierarchy depicting complete structure including the meter. Plant information catalog can be used to model the different hierarchy sharing the different meter represented as tag categories i.e. Electricity, water, compressed air. The properties on each of the nodes can be used for filtering the energy data i.e. energy information only for machine type Driller or providing the grouping of the data i.e. energy information grouped by line vendor.

                2. Meter Data Collection - The next important aspect is collecting the meter data against the meter ID at a regular interval i.e. 1, 5, 10 mins etc without any functional dimension. For this purpose KPI object is being used to collect equi-distant energy data. KPI has been enhanced to support collecting equi-distant energy data and providing analysis lower than 1 hours.

                3. Linking Hierarchies with Meter Data - once the master data and transaction data is defined, it needs to be linked for the analysis. For this, Tag node in Plant Information Catalog is enhanced to map it to a KPI with appropriate dimension filter defined for that tag.

                4. Energy Analysis - Once the above data modeled is created and linked, it should be possible to ask different queries to this data model. For this a new mode in catalog query called PIC analysis is defined where you can provide following information

                                a. Tag categories i.e. electricity, water etc. for which aggregated information is required.

                                b. Granularity - Granularity at which data needs to be returned i.e. monthly, hourly etc.

                                c. Starting nodes for which the aggregated data is needed.

                                d. Any filter based on different properties on the PIC nodes.

                                e. Any group by based on different properties on the PIC nodes.

                5. Energy Dashboard - the final goal for energy monitoring is providing role based energy dashboard based on different requirements. MII SSCE has been enhanced to provide simplified energy dashboard. Some of the key improvements are as following.

                                a. Easy integration of PIC analysis query by providing overriding capability of any of the parameters.

                                b. Visualizing energy data into Chart.

                                c. Unified change of PIC node and time period at the dashboard level.

                                d. Ability to see the energy information on Map.

as you can see from above information, customer can easy do energy monitoring and analysis based on their needs primarily because there is no data model delivered by SAP for this. Everything is flexible in terms of hierarchy, the properties on each of the hierarchy nodes, queries, and dashboard creation. 

Hi Everyone,

This blog post is to inform you about the recently released patches and fixes, hope you will find it useful.

+ If you face a problem caused by a newly released patch, please report it on SCN forum, and copy the link here.

During the holiday season we released the following patches:

XMII 15.0 SP 005 Patch 8, containing the following notes:

• MII treats unspecified Spec. Limits and Control limits as '0', note 2258524

• Priority under Custom Attribute Mapping is not populating co, note 2231536

• Special characters like German umlauts appear as hex values., note 2259451

• Com sap xmii xacute core IntrospectionUtilities   cannot ini, note 2260526

MIIADMIN 15.0 SP005 Patch 5

• Priority under Custom Attribute Mapping is not populating co, note 2231536

XMII 15.0 SP 005 Patch 9

• Null pointer in Shared Property Manager on deploy, note 2261465

XMII 14.0 SP 007 Patch 13

• Null pointer in Shared Property Manager on deploy, note 2261465

Also, I would like to inform you, that the following correction is not fully present in 14.0 SP07 patch 12:

https://css.wdf.sap.corp/sap/support/notes/2235005

The following note will contain the full correction:

https://css.wdf.sap.corp/sap/support/notes/2263854

07.01.2016.:

Today we released XMII 14.0 SP 007 Patch 14, containing the following notes:

• MII OLAP query does not show dimension properties, note 2253519

• Problem with multiple updates/result sets and IDBC queries, note 2262006

• Allow Multiline property of iChart axes is not working, note 2263854

11.01.2016.:

Today we released XMII 12.2 SP 008 Patch 2, containing the following note:

• Problem with multiple updates/result sets and IDBC queries, note 2262006

14.01.2016.:

Today we released the following patches:
XMII 14.0 SP 007 Patch 15, containing the following note:

• OLAP Query - UOM not available along with Measures, note 2264978

XMII 15.0 SP 005 Patch 10, containing the following notes:

• Folder contents missing after re-deployment., note 2263268

• Help link on PIC Group does not work., note 2264891

• Limit Texts are shown multiple times in I5PSC charts, note 2261733

• MII is unable to execute BAPI_MATERIAL_GET_ALL when using JR, note 2261552

• Problem with multiple updates/result sets and IDBC queries, note 2262006

Best Regards,

Janos

Hello MII Community,

In this blog I’d like to say few words and share some hints regarding a size of MII entities and corresponding records in XMII tables.

Imagine you face some memory consumption or performance issue. It can happen because the corresponding MII file is huge and as a consequence it takes much time to process it.

In some cases you should dig to the needed record in XMII_FILES table, which has a BLOB column TEXT that can occupy a lot of space. You can judge about its size based on FILESIZE column. However, this column has been introduced since MII 12.2 SP7 and MII 14.0 SP4 only. In older versions you should use some script to evaluate the size. Below is the example from SQL Server database:

select NAME,  datalength(TEXT) as LengthOfBLOBField

from XMII_FILES

where…

The calculated length is provided in Bytes, same as in standard FILESIZE column.

In case you have other DB vendor, an equivalent datalength() function should be used.

In more rare cases you need to check for the same in other XMII tables. Very recently I have had a need to check XMII_JOBPROP table and found a property there, which value (a CLOB column PROPVALUE) occupied more than 1 Gb, and caused an issue.

Hope you find these hints useful. Your comments, ratings and Likes would be appreciated.

Best regards,

Alex.

Here in this space, we will see to make use of UI5 table control on a MII page. Here let us focus on the UI5 table with the dummy json object data. And in the upcoming section, we will see how we can bind the data from a BLS to this table.

• Go to MII workbench, WEB, right click on folder, create a new irpt page save it with “FirstPage.irpt”.
• Add the reference to the libraries.

               <script src="https://openui5.hana.ondemand.com/resources/sap-ui-core.js"

                                                            id="sap-ui-bootstrap"

                                                            data-sap-ui-libs="sap.ui.table,sap.ui.commons"

                                                            data-sap-ui-theme="sap_bluecrystal">

                              </script>

• In BODY element, create one div.

                    <div id="uiArea"></div>

• Add the script elements to define json dataobject, create table and place it on the div area.

                    <script></script>

• Inside script tags, define the json data object

               var dataObject = [{

                    "EmployeeID" : "123210",

                    "Name" : "James Ad",

                    "Designation" : "SSE",

                    "Location" : "Delhi",

                    "Hierarchy" : "6"

                     },{

                    "EmployeeID" : "123218",

                    "Name" : "Rick Hui",

                    "Designation" : "Manager",

                    "Location" : "Mumbai",

                    "Hierarchy" : "2"

                     }];

• Create a ui5 table using sap.ui.table control.

                    var oTable = new sap.ui.table.Table("oTable", {

                    visibleRowCount: 10,

                    selectionBehavior: "Row"

                    });

• Add column to this table:

                    oTable.addColumn(new sap.ui.table.Column({

                    label: new sap.ui.commons.Label({

                    text: "Employee Number",

                    wrapping: true

                    }),

                    template: new sap.ui.commons.TextField().bindProperty("value", "EmployeeID"),

                    sortProperty: "EmployeeID",

                    filterProperty: "EmployeeID",

                    width: "80px"

                    }));

               Similarly add more columns depending upon the requirement.

• Now instantiate the json data model, set it our dataobject defined earlier. Bind the data and place it on the div.

               var model = new sap.ui.model.json.JSONModel();

               model.setData(dataObject);

               sap.ui.getCore().setModel(model);

               oTable.bindRows("/");

               oTable.placeAt("uiArea");

• Save the page and test it using Chrome browser. The page will look like this:

In the previous blog, we saw how to create a ui5 table on irpt page and bind it with the dummy Json data object. Here in this space, we will see how to bind the json output data from a MII transaction into the UI5 table control on a MII page. Let's start:

• Go to MII workbench->WEB, right click on folder, create a new irpt page save it with “SecondPage.irpt”.
• Add the reference to the libraries.

               <script src="https://openui5.hana.ondemand.com/resources/sap-ui-core.js" id="sap-ui-bootstrap" data-sap-ui-libs="sap.m,                sap.ui.layout,sap.ui.table,sap.ui.commons" data-sap-ui-theme="sap_bluecrystal"></script>    

• In BODY element, create one div. <div id="uiArea"></div>
• Let us call a function fetchData() on Body onload event, and in this function, we will call the BLS, create ui5 table, and bind data and place it on the div area.

          (First develop a BLS to return the expected output data in JSON format in transaction output string parameter)

• Save the page and test it using Chrome browser. The page will look like this:

Previous Blog : MII Page with UI5 Controls 1 – Table

This blog post explains about how to Monitor a Local or a Shared Folder for a file and process the contents of the File using SAP PCo and SAP MII. It uses an SAP PCo Agent called File Monitor Agent which is available in PCo 2.2 and above. It Works in both Notification and Query Mode

In PCo you define which folder is to be monitored. If the agent finds a file that meets the configuration criteria that you specified in the PCo, then it generates, for example, a notification message and sends it to the connected destination system. In this way you can transfer file contents to the destination system. You can also define specific actions to be done like Moving, Copying, Renaming the files.

Let us see step by step procedure using an example.

Creation of Source System

• Go to SAP PCo Management Console
  
• Click on Add New Source System.

• Choose the Source System type as FileMonitorAgent and create one

• After the Source System has been created, in the Settings Tab of the new Source System, Browse the folder you need to Monitor and enter the File Mask as needed, (in our case I am giving it as ‘*.csv’ to monitor csv files). default is "*.*"

• And choose one of the File Handling Actions from the below Dropdown, (Default is DoNothing). In Case of Move, Copy or Rename, you must choose a Destination Folder using the Folder Browse button
  • You cannot choose a System Folder for Monitor and Destination,
  • You can obviously monitor a Network Folder which is shared from another system or server as well. In that case you can give the shared folder path in the Folder to monitor like (\\Servername\SharedFolderPath)
  • Check the Ignore unavailability of UNCFolders if you are using a network shared folder as, the network folder might be disconnected often which will stop the agent
    

• In case if Authentication is needed to access the Folder if it is a Shared Folder, you can give the credentials in the Authentication Tab. Click to Test the Connection

• Save the Changes

Creation of Destination System

• Add the MII System as a New Destination System

• Give SAP MII Server Details and Credentials and Save the Destination System

Creation of Agent Instance

• Create an Agent Instance and choose the Source System as the “MonitorFolder”.

• Once the Agent instance has been created, Go to Subscription Tab and add the tags to be monitored by following below steps
  • Click on Browse and a Tag Browser opens

• Click on Browse again in the Browse Pop up so as to see the available Tags

• Select them and Click “Add Selected Items” and Click OK

• Now the Subscription items have been added

• Click on the Query ports Tab and Choose SAP MII as the Port Type and type an unused port of SAP MII Server from where the File Monitor Agent can be queried

• Save the Agent Instance

Creation of Notification

• Right Click on the Agent instance and Click on “Add Notification” and create a New Notification

• In the trigger tab, Keep the Trigger Type as Always and check the Enabled checkbox.

• In the Output Tab, click the Generate Expressions to generate all the subscription items of the Agent.

• Meanwhile in SAP MII, Destination System, Create a Simple Transaction with XML Saver which can save the XML input from PCo Notification

• In the Destinations Tab, Add the Already configured SAP MII Destination System

• In the Destination Tab, Browse the already created transaction in SAP MII and map the Input Parameter Name

• Save the Changes.

Testing the Notification

• Start the Agent

• Paste a CSV File in the folder which PCo is monitoring. As we are Moving the files, in few seconds we can see that the file is disappearing

• Now the Notification should have run automatically.
• Now we can go and check the Workbench for a newly saved XML file which we received from PCo Notification

• Now MII has received the File Content through PCo File Monitor Notification, Which an MII expert can parse and use it as necessary

Query Mode

• Create a PCo Dataserver in SAP MII.
• Choose the Connector type as PCo Connector and Click Next
• Enter PCo wsdl and Click Next and give credentials.
• All the PCo Agents will appear, Choose the appropriate Agent

• Click Finish, Enable and Save the Data server.
• Make sure that you have few files in the Folder which is being monitored by SAP PCo. Which means that it should not be in Move File Handling Action mode in the Source System

• Go to the SAP MII Workbench and create a PCo Query and choose the new Data Server
• Choose “Tag Retrieve Query” mode and go to Tag Retrieve Query tab. The available Files in the Monitored folder will appear and you can select the files as needed.

• Execute the Query and check the result, as the different file contents will appear in different Rowsets.

We can use other file types as also such as .txt, .log etc using File Monitor Agent

Regards,

Austin

Connecting Barcode Scanners with MII

          This blog is about to explain how to connect Barcode scanners to MII via PCo. This type of process is used to connect devices to MII and ERP without using web pages. In this blog, I am explaining about types of Barcode scanners and their advantages and how to connect with MII.

• Connecting Barcode scanner to MII via web page

• Any Serial port / TCP-IP port enabled devices can be connect with MII by using web pages or PCo.

• In Connection thru web pages, all barcode scanners has pre-defined scripts which send data to web pages.

• In web pages, the cursor should be positioned on any controls which will capture the incoming data.

• The controls may be text-box or any input types. Once MII page captures the data, it will proceed it with transaction.

• For this, we need to create page and disadvantage is by this method each system will connect with single scanner only         

• Currently three types of Barcode scanners are available.
  • Keyboard Wedge Output
  • RS232 (serial) Output
  • USB Output

• Keyboard Wedge Output

• The "Keyboard Wedge" output option is the most common option.

• To interface a keyboard wedge barcode scanner to a PC, we need to connect keyboard along with scanner input cable.

• The main advantage of the keyboard wedge interface is that it works just like a keyboard. We can set the cursor in text field where we want the barcode data to   go and then scan the barcode and the data pops in just as  if we typed it on the keyboard.

• The disadvantage of the keyboard wedge interface is that it works just like a keyboard. If the cursor is not in the correct input field in the correct application program, then, when we need to scan a barcode again, the data still gets entered into the PC as if it is being typed in on the keyboard.

• RS232 Output

• In RS232 option, we can connect the barcode scanner directly to an available RS232 serial port on the back of PC. In these RS232 output scanner, we can connect barcode scanner to PCo connectors or any other software.

• If we want to connect multiple scanners to single PC or server, RS 232 is best option and we can use RS232 to USB port to connect multiple scanners.

• We can plug RS 232 cable directly into the system or we can add USB to Serial converter and plug in the system.

• USB Type output

• Barcode scanners that have a USB output can work one of two ways.
  The first is that they can work exactly like a Keyboard Wedge scanner and the second is that they can work exactly like a RS232 serial output scanner.

• A USB Keyboard Wedge barcode scanner works exactly like a "Keyboard Wedge" barcode scanner except that instead of connecting the barcode scanner to the keyboard port on the PC, plug it into a USB port. Then it will be recognized by the PC as a second keyboard device and when we scan a barcode, all barcode data goes into the PC.

• Just like a standard keyboard wedge scanner, no additional software is needed. Windows will automatically recognize the scanner and treat it as if it were a second keyboard connected to PC.

• A scanner that has a USB RS232 serial interface will come with a special "Driver" program that we will need to install in the PC that you connect the scanner to. The purpose of the driver is to create a "Virtual RS232 serial port" that works exactly like a physical RS232 port.

• After we install the driver that comes with the scanner and connect the scanner to a USB port on PC, Windows will think that it has a new RS232 serial port and PCo will be able to access this port.

• Connection thru PCo

• PCo can access multiple barcode scanners thru Socket Agent interface. In these we need to add configuration details for each scanners.

• A single PCo Socket Agent can define multiple connections, each identified by a unique combination of IP address and Port, and each connection has a unique             name. 

• WiFi is fine as long as the IP address is routable from PCo Socket Agent to WiFi device, and the WiFi device is a Server, not a client. 

• If we have multiple barcode scanners connected to a single IP/Port connection, then we will have to place identifying information (i.e., a unique detectable Prefix that is NOT part of the barcode data, like A1, A2, B01, etc.) in the scanner  to be transmitted with the barcode.  Then the PCo Agent Instance Notification can use string logic in the Trigger logic to detect a particular scanner and process  its barcode data.

• Once data scanned from these devices, data will be received in PCo thru these settings. After receiving the data, it will trigger the MII transaction via PCo – MII connections.

• MII Transaction will process the received data

• Structure of Connection Flow:

• Configuration in MII and PCo.

We will see how to configure PCo with socket agent. Plug the barcode scanner into corresponding ports depends on the type. Get the port no and address of socket.

     1. In MII create a transaction to receive the Barcode message.

     2. In PCo, Select Source system as Socket Agent

     3. Choose the socket type.

• It might be Ipv4 or IPv6.
  • IPv4: Internet protocol version 4
  • IPv6: Internet protocol version 6
• Then give name for this connection and IP address of socket.

• Enter the port no on which Barcode scanner is going to connect.

• Then enter terminator to identify the end of message in data stream and give length of message in data stream. This terminator may be any char usually we will use #.

• We can give either terminator or length of message to identify the messages in data stream.

• In reliable connection tab, set interval and no of retries if connection fails.

     4. Once Source system added, create Destination system.

• In destination, choose MII Destination and give name for this.

• Give server name, port and user information like username and password

     5. Once destination added, create agent instance.

• Choose the barcode source system as source and give agent name and description.

• In subscription items tab, select browse at bottom and select Bar.Message as selected item. This is the input parameter name for Bar. Scanned barcode value will be retrieved on this parameter.

• In Query ports, select SAP MII and give new port no. This port no should not be used in any other agents. Check other agent instances before assign it.

• Once created, save the agent instance. Now we need to create notification for this.

     6. Create Notification

• Right click on agent instance and select add notification

• In trigger tab, set to trigger always.

• In output tab, click Generate expressions. Then it will add Bar.Message which we selected in agent as expression. If we want to modify, we can add expressions.

• In destination, click add destination and select the destination MII system and browse to the target transaction.

• In transaction, select the input parameter to receive this Barcode message.

• Once selected, save and start the agent instance. Once barcode is scanned, PCo will get it and send it to MII transaction. In MII transaction, we will process the input data.

SAP MII has the capability to connect to a number of JMS providers. The below blog post focuses on steps to connect to ActiveMQ JMS server. However, the steps to connect to any JMS provider remain the same.

Setup ActiveMQ server

The steps to set up the server are documented on the URL::

http://activemq.apache.org/installation.html

After the setup completes the user needs to create a queue to which he needs to send messages using MII JMS action block. The following details are required to configure JMS connection factory at Netweaver level:

1) Hostname(or IP) and port at which ActiveMQ JMS server is deloyed. The default port for ActiveMQ server is 61616.

2) The credentials to connect to the server. The default user id and password are admin.

Setup JMS Connection Factory at J2EE engine

1. The first step to configuring a JMS connection factory is to deploy the client libraries required to connect to the JMS server. A list of the jar files required by any client to connect to the JMS server should be available in the JMS server documentation. For ActiveMQ server it is activemq-all.jar which comeswith all libraries required.

         In order to deploy the libraries navigate to SAP MMC -> Java Application Server -> AS Java Process Table -> icm node

     Right Click and select Java AS Java Telnet. The java console comes up which requires Administrator access for login. Once logged in the user needs to deploy the third party JMS jars. For this run the command:

          > ADD JMSCONNECTOR

          >DEPLOY_JMS_LIBRARY <library name> <path to jar files>

          If the above command fails try changing the location of the jar files.

     The status of the libraries can be checked under Java Class Loader Viewer.

   2. Once the library jars are deployed the user needs to configure JMS Connection Factory Reference. For this navigate to:

     NWA -> Configuration -> Infrastructure -> Application Resources.

   3. Select New -> JMS Connection Factory Reference

   4. Fill the details as shown the image below:

     Library name should be the same as the one specified in (1) above.

    5.  Save the Factory Reference

    6. Few additional properties need to be specified. This can be done by clicking "Add New Property" button at the end of the page. The additional properties are shown below:

The java.naming.factory.initial in case of ActiveMQ server is org.apache.activemq.jndi.ActiveMQInitialContextFactory.The format of specifying java.naming.provider.URL  is tcp://<host ip>:<port> for the system on which ActiveMQ server is deployed.The default value of port is 61616.

    7. Save the Resource. The status of the resource should be green.

    8. Navigate to JNDI Browser in NWA.

    9. The entry for path to ActiveMQResourceApplication should be visible as shown in the image below:

     The path to the connection factory is jms_vendor_factory_local/sap.com/ActiveMQResourceApplication/AMQConnectionFactory.

     MII Configuration

1) Login to MII. Navigate to Data Services - >  Connections

2) Create a new JMS connection of type JMS.

3) Fill in the details like Name, Server URL, JNDI Context Provider and JNDI Factory Context like image shown below. Note that the JNDI factory context will be the path  noted above.

    The check-box, "Skip JNDI lookup" has been introduced so that the user can specify whether the Queue(or rather the JMS server) being used exists on the same java application server. In case a separate ActiveMQ has been setup, the box should be checked.

4) Once the configurations are complete, the transaction can be run to send the JMS message to the specified queue.

Good Day!!

After having heard a lot on flexible UIs these days and with the fact that a lot of clients are now demanding dynamic and configurable one. Sharing a solution that would help you derive quick solution in times when there's nothing relevant available that takes you through it.

My team was working on a similar solution when I found out that they are struggling with creating a dynamic table and when we say dynamic table, it's like depending on back end data, you need to render different controls for each row in same column.

My solution follows below steps:

1. Create a table

2. Define columns : The ones you intent to keep dynamic should contain empty layouts. In my case I was using a simple MatrixLayout as template to dynamic column. Let's say it was column 4 for my table i.e. index 3.

3. Bind table to model path: "/sampleRowData"

Say my data is {"sampleRowData":[

                         {"a":"val11","b":"val12","c":"val13","d":"Dropdown","e":"val5"}

                         ,{"a":"val21","b":"val22","c":"val23","d":"TextField","e":"val25"}

                         ]

                         };

4. Now I iterate through table rows, and get the cell using index 3 that belongs to dynamic column. oTable.getRows()[i].getCells()[]

5. I compare the value coming from sampleRowData and assign the controls to layout as shown below:

var bindedData = sap.ui.getCore().getModel().getProperty("/sampleRowData");

     $.each(oTable.getRows, function(i. obj){

               if(bindedData[i] == "Dropdown"){ //Index would be same for tableRow and BindedData as table is binded to same data

                    obj.getCells()[3].createRow(new sap.ui.commons.Dropdown({

  items:[

  new sap.ui.core.ListItem({key:"1", text:"a"}),

  new sap.ui.core.ListItem({key:"2", text:"b"})

  ]

  })

  );

               }

    else if (bindedData[i]=="TextField"){

  obj.getCells()[3].createRow(new sap.ui.commons.TextField({value:"sample dyn field"});

    }

    and so on....

     });

6. You need one condition for each type of control to be rendered or created dynamically.

7. Tada....your dynamic table is ready.

Hope it helps you find a solution to problems.

Thanks and Good luck!!

Best Regards,

Swaroop

SAP Integration and Certification Center (ICC) offers certification for solutions deployed/integrated with SAP Manufacturing Integration and Intelligence (MII).

SAP Manufacturing Integration and Intelligence (MII) enables you to integrate your plant and enterprise systems and display integrated data to your employees. you can use MII to 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.

This certification is for manufacturing solution built with the SAP Manufacturing Integration and Intelligence (MII) to extend SAP services to the shop floor. SAP MII is the main choice for ISV to build manufacturing solutions as more and more reusable components and services are provided using MII to link the SAP Business Suite to shop floor systems and tools. Application Developer User for Partners is pre-requisite to apply for this certification.

This certification is meant for solutions built on top of SAP MII providing following business value

• Extending the core manufacturing capabilities by integrating disparate system spanning across multiple level i.e. from shop floor control to core enterprise system
• Simplifies the overall process at plant level to some key areas/industries

Usage of any of the following is required to qualify the certification process.

• Data Services
• Business Logic Service
• VisualizationService
• Analytic Service
• Message Service
• Manufacturing Data Object (MDO), KPI and Alert Framework
• Catalog Services
• OEE services and dashboard
• Additional connector using SAP PCo(Plant Connectivity) SDK

The possible certification scenarios:

 Scenario A - Integration with Shop Floor

     Presenting shop floor control data or taking action of certain events in shop floor using data services, business logic service, visualization/analytic services

 Scenario B – Integration with SAP Business Suite system

     Receiving/sending information from/to SAP business suite system using message services, Business logic service

 Scenario C – Integration between shop floor and SAP business suite system

     Integrating shop floor and SAP business suite system using data services, message services, business logic services

 Scenario D – Performance Management

     Storing performance management data in MII from shop floor/business suite system and providing performance management dashboard using MDO, KPI, Alert, Visualization services

 Scenario E – Worker UI

     Enhancing OEE dashboard to integrate additional scenarios in OEE dashboard. Providing out of box integration scenarios using OEE services

 Scenario F – Additional Connector using Pco SDK

     Enhance the MII integration capabilities by adding vendor specific connectors using PCO SDK.

SCN page for MII-MFG certification: http://scn.sap.com/docs/DOC-65499

Benefits of certification: http://scn.sap.com/docs/DOC-25281

If interested to get it certified, please reach out to us at icc-info@sap.com