How to Use Manufacturing Data Objects to Develop Composite Applications in SAP MII
- by Rohit Negi, Senior Consultant, Cibersites India
- January 26, 2015
Organizations often come across situations while implementing a solution using SAP Manufacturing Integration and Intelligence (SAP MII) in which they want to store the relevant data and persist it locally in the SAP MII system. One reason is that data comes from many systems, and you can save this combined data in SAP MII and then create relations or calculations using the data. Another advantage is performance enhancement. Performing calculations based on data stored locally is better than fetching the data from another system. Follow a use case to learn how to persist or store data in manufacturing data objects (MDOs) that come as an in-the-box feature of SAP MII. Find out how to define MDOs and how to consume them.
Reading this article, you will learn how to:
- Create manufacturing data objects (MDOs) using the SAP Manufacturing Integration and Intelligence (SAP MII) workbench and know when to create which type of MDO
- Acquire data and persist it inside MDOs
- Consume the persisted data in SAP MII applications
Manufacturing data objects (MDOs) are data objects that can hold data in local SAP Manufacturing Integration and Intelligence (SAP MII) storage. The data objects receive the data from various sources that are configured and integrated with SAP MII.
SAP Manufacturing Integration and Intelligence (SAP MII) can act as middleware that integrates shop floor data and data from enterprise systems such as SAP ERP. It provides integration capabilities to multiple shop floor systems, such as supervisory control and data acquisition (SCADA) systems and programmable logic controllers (PLCs). It also can integrate with data storage systems, such as relational databases using various built-in data connectors and SAP Plant Connectivity (SAP PCo).
However, on some occasions, it may not be permissible when using external database systems to store and retrieve the processed transactional data. This could be because of security reasons or tight coupling in the system landscape of the shop floor. In these cases, SAP MII’s data storage capabilities can be employed. They can store and retrieve the data that might be needed to build transactional user interfaces in applications built in SAP MII that would then consume this data coming from various sources.
I explore one of these data persistency options in SAP MII called manufacturing data objects (MDOs) and explain when to use this data storage concept. Most of the applications built in SAP MII integrate data from various systems such as enterprise systems (SAP ERP) and shop floor systems (SCADA or data historians). There often is a requirement to store or persist the data coming from various systems.
In this article, the terms persist and store are synonymous.
Following are some of the use cases in which an application needs to store the data locally in SAP MII:
• Applications take data as input from users and then perform some business transactions based on that data
• The data is fetched from other systems and the communication time is very long
• There are requirements to mash or combine data from various systems and you don’t want to work on live data from other systems
• There is a need to store the metadata for applications and a persistence mechanism is required
Would you like to see this full item?