Hi,
Look in to this...
(/people/abesh.bhattacharjee/blog/2006/12/19/harnessing-the-power-of-xmii-using-yahoo-widgets)
This page contains a link to the previously raised blog by the same author. The link is as follows.
How to pass data dynamically between pages in xMII 11.5
(/people/abesh.bhattacharjee/blog/2006/11/29/how-to-pass-data-dynamically-between-pages-in-xmii-115)
From this blog we came to know about the new technology called xMII.
How to Work on Report generation using xMII :
http://help.sap.com/saphelp_xmii115/helpdata/en/Advanced_Topics/Report_Generation.htm
Installation Procedure for XMII:
Information on XMII:-
As far as xMII and XI is concerned - The SAP supported and recommended model for XI connecting to shop floor systems is through SAP xMII. SAP xMII includes a extensive set of connectors and data transformation components specifically targeted at manufacturing applications, and provides the complete "chain of custody" of information from SAP ERP (order/demand data, master data) and to SAP ERP (production results and other related reporting data), eliminating the need for another EAI solution on the plant floor.
XI is typically deployed in the data center, xMII in a distributed manner at each manufacturing site. This provides for optimal availability, reliability, and lowest possible TCO. SAP xMII can also use other mechanisms besides XI to interface with SAP ERP, depending on the customer's technical landscape and SAP component version(s).
KPI's are Key Performance Indicators. It could be any graph or a grid or chart or a dial showing real time information from the plant which one would like to see to maintain/improve performance. For example OEE (Overall Equipment Effectiveness).
A Dashboard is a screen which captures a set of KPI's which he would like to see.
xmii and xi compliment each other to deliver a good overview of the status of your business. With xi information can be sourced from any part of the ERP and now from the plant floor as well. This makes conditional maintenance a "breeze" for example as one can compare logistical data to realtime data. Furthermore the other good stuff can be used to create some valuable info. Imagine a composite app on the fly that can give you the KPI for the cost of production (HR module information vs XMII information - production).
The reason why SAP suggests the kind of architecture that the Best Practices Guide talks about is -
1. xMII talks about Intelligence - Real Time Dashboards for the Plant Users (Operators/Supervisors). This is a very common scenario where xMII adds value . Here it makes sense to have a xMII server @ the plant layer to make a very real time view possible for the user. So its mainly a bandwidth issue.
2. Another very good point the guide talks about is in case of absence of the Corporate network the plants can go on with there business as usual with xMII acting as a buffer. As soon as the corporate network's up the buffer can then be sent across to the corporate (read SAP ERP). There have been many instances where customers have come up with these kind of requirements; This kind of a scenario becomes very relevant when one is upgrading their ERP.
The Best Practices have evolved based upon the kind of requirements xMII has seen over the years and hence it reflects what is best from an architecture perspective.
XMII is more efficient when it is plant specific.
When you have one xMII server speaking to multiple plant databases the intelligence part of xMII gets complicated. When you have xMII configured for each and every plant, it is possible that you can configure your dashboards specific to that plant for the specific plant manager or other roles. It is also possible that you can stage all the process orders to a local database during ERP downtime using xMII you can then roll all the changes into ERP once it is up.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.