SAP Community - SAP Manufacturing Integration and Intelligence

Start and Complete operation from external system using web service

2023-02-02T22:45:45+01:00

Hello everyone,

In this blog, let us see how to trigger the MII transaction for the start and completion of an operation from an external system to MES.

Here, in this article, I am describing the steps involved in connecting such an external system with SAP MII using SOAP Web service URL to get external data and automatically start and complete operation in SAP MII.

Instead of PCO, I have used WDSL URL. For this, I created a custom workflow to monitor the operation start and complete message status (pass/fail) in the SAP MII Queue.

High-level Steps:

Step 1. Create MII transaction

Step 2. Create custom workflow

Attach the Request XSLT

Configure service transaction (to auto-start and complete the operation)

Step 3. Build WSDL URL to pass the external data

Detailed Steps:

Step 1. Create MII transaction

Create a MII transaction to read input from external system. Inside the transaction use Enqueuer action block to call the workflow.

Step 2. Create workflow and attached Request XSLT & Service Transaction to auto start and complete the operation

Create a custom workflow. Configure the request XSLT for getting external data.

Configure service transaction to start and complete the operation.

Create a service transaction for start and complete the operation. Pass the request payload as input parameter to this transaction.

Define the input and output transaction parameters as shown below.

Inside the inputXML, pass the request payload as input parameter to this transaction properties.

In the Start & complete PAPI, map these input variables to start and complete the operation.

To get a response message, we required Success Message variable. So, we have created the variables in Local properties and map to the assignment action block.

Define the SuccessMessage given below as a local property.

When the data come from external system, the transaction will be triggered.

The transaction will call the Workflow, the workflow will trigger the service transaction.

The service transaction will get called to start and complete the operation in ME and the message will be shown in the SAP MII Queue monitor.

Step 3. Build WSDL URL to pass the external data

Build a WSDL URL using MII portal path with transaction path.

URL:http://<Hostname><Port>/XMII/WSDLGen/<TrasactionPath>?wsdl

Conclusion

Normally, for shop floor integration scenarios, where Machine data is captured from PLC / Other Third-party systems, Mostly MII will use PCo (Plant Connectivity).

This eliminates an additional integration. i.e., PCo which needs more configuration.

I hope, this article will help you how to set up the external system integration and use the MII transactions to improve the application development in SAP MII. Thank you for reading this blog post. For further questions related to the blog, please check the Q&A area and feel free to post your questions.

Steps to Configure NWDS for SAP MII

2023-08-12T02:11:26+02:00

Configuration Steps

Following setup files to be downloaded for NWDS configuration. The setup files mentioned in below are versions which used while writing this blog.

NWDS (NWCEIDE23P_3-80002366)

SAPCAR (SAPCAR_1115-70006231)

SAPJVM(SAPJVM8_31-80000211)

7ZIP setup(not required if 7ZIP is already installed in the system)

STEP 1: Place all downloaded files from 1 to 3 in single folder and install the 7ZIP if not installed in system. 7ZIP was used as standard windows unzip extracted folder had errors or missing files.

STEP 2: Extract the NWDS (NWCEIDE23P_3-80002366) using 7ZIP into the same folder where all downloaded files were placed from STEP 1 and a folder name eclipse will be the output of extraction.

STEP 3: Open command prompt. Use command CD (your folder path where download was placed)

Example: CD C:\Users\documents\NWDS (for example if all downloaded files are placed in NWDS folder in some system path)

STEP 4: Now the below command to extract SAPJVM(SAPJVM8_31-80000211) in same command prompt session of step 3.

SAPCAR.exe -xvf SAPJVM.SAR -R./SAPJVM

Below is the example as per the versions downloaded in Step 1 and wait till extraction completes.

SAPCAR_1115-70006231.exe -xvf SAPJVM8_31-80000211.SAR -R ./SAPJVM

STEP 5: Find the javaw.exe file in extracted JVM folder from Step 4 and copy the path. Replace all backward slash’s to forward slash’s

Example: C:\Users\ documents\NWDS\SAPJVM\sapjvm_8\bin\javaw.exe

STEP 6: Now open eclipse folder which was extracted from Step 2 and look for eclipse configuration file.

Paste the below command as shown in screenshot and Replace all backward slash’s (\) to forward slash’s (/) of the copied javaw path.

openFile

-vm

C:/Users/ documents/NWDS/SAPJVM/sapjvm_8/bin/javaw.exe

STEP 7: Now open (double click) eclipse application from eclipse folder.

STEP 8: When the Sap Netweaver Developer Studio is open, go to Window / Preferences. Now you’ll add the system which you want to connect with.

In the Preferences screen open Development Infrastructure and go to System Landscape Directory:

Enter after URL a SLD link and click on Ping to test the connection.

STEP 9: Go to Web Services / Enterprise Service Browser, and fill in the connection settings:

STEP 10: Go to File/Import. Then select Development Configuration as shown below and press Next

Select Import from System Landscape Directory(SLD) and Press Next

Enter the credentials for the Development Infrastructure and Press Log On.

STEP 11: Go to Window/Show View/Component Browser

Select the SLD system which was added.

Go to Window/Show View/Transport View

Transport View will be open which we will use in future steps for releasing the transport requests

Steps in SAP MII Workbench

STEP 1: Go MII Workbench and Login to Source Control

Right click on Project go to Source Control/Share

STEP 2: Any object now must be edited needs to Check Out with Activity Creation and Activity Creation is required to add new Objects as well to the shared project.

STEP 3: After completing changes in objects. Goto Source Control/Show Open Activities

Select the activity and check Activate check box then press Check In

STEP 4: Create a TR in Solman and assign it specific user and then go to NWDS Transport View all waiting and released activities will be visible in Transport View.

Right click on any waiting activity and select Release

TR created will be displayed in popup window, same to be verified and Press Release rebuilt deployable DCs

Experience SAP Digital Manufacturing via Interactive Value Journeys

2023-08-14T13:41:22+02:00

Introduction

SAP Digital Manufacturing is an enterprise-level, scalable, manufacturing solution that enables global manufacturers to manage and control manufacturing and shop floor operations and realize Industry 4.0 scenarios.

It's a cloud-based Manufacturing Execution System (MES) that supports sustainable, risk-resilient manufacturing operations through a resource-efficient Industry 4.0 approach, enabling companies to integrate and embed intelligence in manufacturing processes.

It provides coordination of planning and execution processes, covering all aspects of the manufacturing cycle from planning to the shop floor and beyond.

Experiencing SAP Digital Manufacturing

You can have a glimpse and experience several aspects of SAP Digital Manufacturing via the Interactive Value Journeys below:

Discrete within SAP Digital Manufacturing and S/4HANA Cloud

Process Industry within SAP Digital Manufacturing and S/4HANA Cloud

Tool Management within SAP Digital Manufacturing

Resource Orchestration within SAP Digital Manufacturing (Incl. Shift Planning and Tools)

Resource Orchestration within SAP Digital Manufacturing (Incl. SuccessFactors)

Production Process Design within SAP Digital Manufacturing

Shop Floor Orchestration with SAP Digital Manufacturing

Time Tracking within SAP Digital Manufacturing

SAP Digital Manufacturing for Insights

Nonconformances Processes within SAP Digital Manufacturing

Discrete Manufacturing in Private Cloud, powered by SAP

Discrete Manufacturing in Public Cloud, powered by SAP

Process Industry Manufacturing with SAP Digital Manufacturing and S/4HANA Cloud, public edition

AI-driven Visual Inspection powered by SAP

Real-Time Operations Monitoring in SAP Digital Manufacturing

Installation Points in SAP Digital Manufacturing

Nonconformances Processes within SAP Digital Manufacturing

E2E MTS for Discrete with SAP Digital Manufacturing and S/4HANA

E2E MTS for Discrete with SAP Digital Manufacturing and S/4HANA Cloud

Process Industry Manufacturing with SAP Digital Manufacturing and S/4HANA Cloud, public edition
* Better viewed in Desktop or iPad in Landscape mode

Do you like this post? Please let me know in the comments section what you think. Any feedback is highly appreciated.
Or, if you have any questions, please check SAP Community Q&A Area, or comment down below.

Thanks,
Manoel Costa

External API / Web Service integration with SAP Digital Manufacturing - Demystified!

2023-10-26T20:23:49+02:00

Hello Everyone,

Recently I learnt few things about SAP DM integration so thought of sharing what little I learnt.

This blog is about utilizing any third party API in SAP DM, to read data and post it against SFC using standard methods and SAP DM LCNC(Low-Code No-Code) options.

We have seen a few blogs around this in past but those were quite heavy and were using different technologies and tools. Here we would be checking this example without any external language knowledge or tool requirement. Let's talk about the pre-requisites first:

Data collection group with parameters maintained for data collection at relevant Operation.

Released order running on a POD with active SFC

External API to be used to capture data, in this case we would be using a simple weather API, URL example: https://api.open-meteo.com/v1/forecast?latitude=73.8567&longitude=18.5204&current=temperature_2m,windspeed_10m&hourly=temperature_2m,relativehumidity_2m,windspeed_10m

Having the system ready with above pre's, below are the steps that will guide you to complete this use case.

STEP 1: Creating a Destination in SAP DM tenant:

Go to accounts.hana.ondemand.com and open subaccount for your DM tenant. Create a destination of Type HTTP in SAP DM tenant, it should look like as shown below.

Destination created on DM Tenant for service API

Note: Here we are using "NoAuthentication" as it is not required for this open service, but you can use appropriate Authentiation depending on the service your are using. Please refer SAP DM help documentation for more on Authentication.

STEP 2: Create a webserver in SAP DM.

Open SAP DM and search for "Manage Web Server" app, click on create and provide name, description and URL ("https://api.open-meteo.com" in our case), click on save. Ref picture below:

Once webserver is created, you would see 4 tabs:

a. Server Details - Having basic server connection configuration

b. Consumed by - Showing which webserver is connected to this, it would initially show 0.

c. Destinations - Select the destination created in DM tenant here for weather api. "DM_WEATHER_SRV"

d. Services - Shows the service using this webserver, currently this section would also be blank.

STEP 3: Linking "DMC_Cloud" to the Webserver created in step 2,

Click on "DMC_Cloud" webserver from the list of web servers under "Manage Web Server", go to connection panel, click on "Create" and select DM_WEATHER_SRV (Note: this should be the name of web server, dont confuse it to Destination name as here we are using same name at both the places which need not be the case in usual scenario).

STEP 4: Create a Service Registry using "Manage Service Registry".

Open SAP DM and search for "Manage Service Registry" app, click on create under API Services tab and provide name, ID, existing group or new group name you are willing you create, and other details for HTTP type, REST protocol and GET method.

Provide the URL suffix that is the remaining part from API url between domain.com and parameters( "/v1/forecast" in our example).
Provide parameters in parameters panel by getting the parameter query string, select the web server from value helper and provide the one created in previous step. Check the "Availability" check box and save. Ref picture below.

Service registry for Weather API.

After this step, your DMC tenant can connect to external API(weather API in our case).

STEP 5: Create a production process design by going to Production Process Designer App in SAP DM. The production process should have start, end, a service call and a script task.

Before you can add web service call to production process, you need to add the service by clicking on "Select Services" button on the left panel, find the Web Server you created in STEP 2 and select the service under that webservice, picture below for ref.

Adding service to production process.

Create the production process as shown below:

Production process design frame

Input to Service call could be automatically included due to parameters maintained while creating service, though this can be modified and parameters can be passed. We are keeping it as it is for simplicity.

Under Script Task, create input/output parameters as input: srv_result (String), Output: srv_result (String), you don't have to assign any value here.

Also, map service response('Service_Weather#httpResponse') to input parameter.

Under script, add below code:

=========================

$output.temprature=JSON.parse($input.srv_result).current.temperature_2m;

=========================

This code reads temperature value from service response JSON and assigns it to output of the script task.

Map input of Log DC control as shown below:

Input parameter mapping for DC

It is obvious the hardcoded values here can be modified with input parameter linking for dynamic values. I have kept it like this for brevity.

No output parameter mapping is required as we can see results in POD directly. Click on "Save All" and "Quick Deploy". Test the production process by clicking on Debug--> Run, check the logs of the flow completing successfully.

DC Collection successfully completed.

Verification: Open Work Center POD, select SFC/Operation and go to data collection panel, you would see the data collected by this process.

DC Collection list on POD.

The above process describes integration and utilization of external web service in SAP DM with the use of Production Process Designer. The flow you created using Production Process Designer can then be linked to Automatic Triggers or POD actions there by using data from external APIs.

The blog grew long but hope this helps you understand the use case in a simple way!!

Do like the blog if you like it.

Nice time!

Best Regards,

Swaroop

Revolutionize Your Manufacturing: KINEXON and SAP

2024-02-20T11:44:13.305000+01:00

Co-authored by Lana Lee and Hrishi Joshi of SAP.

In today’s Industry 4.0 world, where connectivity and automation are redefining our manufacturing landscape, the partnership between SAP and KINEXON stands out as an example of true innovation. This collaboration, highlighted in a recent IDC case study and to be featured in a March 7 webinar, leverages connected and automated operations to enrich SAP's Digital Supply Chain portfolio for Manufacturing and Logistics. Kinexon and SAP are focused on improving how businesses like yours approach both efficiency and sustainability.

Unlocking Efficiency through Collaboration

The goal of this partnership is to continually improve supply chain and production operations, delivering business process innovation and intelligent enterprise development outlined in RISE with SAP. This synergy leverages KINEXON's prowess in automation and IoT, significantly bolstering the SAP Digital Supply Chain portfolio with an enriched suite of tools. With Kinexon OS certified as an SAP Endorsed App and in the SAP Store, this collaboration is a significant leap towards accelerating the efficiency of your manufacturing operations.

The strategic benefits of this integration are profound, including a marked decrease in manual data entries, enhanced productivity, and considerable annual savings attributed to reduced cycle times. Insights from the IDC case study highlight these gains as essential for maintaining a competitive edge in the dynamic manufacturing sector.

Elevating Value Chains

This initiative is set to transform value chains, especially within the automotive, manufacturing, and aerospace sectors, by not only adopting but redefining the use of technology. Enhanced visibility and the link between early demand feedback and accelerated production underscore a shift towards more agile and responsive industry practices.

Embracing Industry 4.0 Innovations

Embodying the essence of Industry 4.0, this collaborative effort seamlessly merges IT and OT, enhancing data utilization to drive your business resilience and innovation. A key component of this transformation is the real-time tracking of assets and efficient management of logistics and production orders, which can provide you a competitive edge through increased automation and visibility.

Revolutionizing Shop Floor Operations

With Kinexon and SAP creating significant improvements to the shop floor, you can now integrate real-time location data, digital visualization, and advanced process management. This approach not only streamlines your operations but also promotes sustainability by transitioning your business towards a paperless production environment, while contributing to broader environmental goals.

Join the Movement: Watch our Smart Automotive Manufacturing Webinar

As we explore these groundbreaking advancements, the shift towards smart automotive manufacturing, highlighted by IDC analysts, becomes clear. 'Realizing the Promise of Smart Automotive Manufacturing,' the webinar on March 7th, offers a deep dive into this transformative era. Featuring insights from IDC and showcasing the SAP and KINEXON collaboration, this session explores the innovation forefront in automotive manufacturing. Secure your spot to discover how this synergy is revolutionizing the industry, and connect with the ideas driving the next wave of manufacturing excellence.

The Race for Semiconductor Manufacturing: How AI is Revolutionizing the Industry

2024-03-19T13:31:24.833000+01:00

In today's high-tech world, semiconductors are the lifeblood of the global economy. They power everything from electric vehicles to defense systems, making semiconductor fabs the new oil fields of our time. However, the dispersed and specialized nature of the global supply chain has raised concerns about potential threats to this crucial industry. As a result, major powers around the world are now embarking on a multidecadal effort to bring semiconductor manufacturing back onshore.

But this shift isn't just about relocating factories. It's also about embracing the power of artificial intelligence (AI) in revolutionizing the industry. Over the years, the semiconductor industry has made significant advancements in design automation and digital transformation, but never before has AI been able to learn and adapt based on best practices for new device design and manufacturing.

Enter SAP, IBM, and PDF Solutions. These industry leaders have joined forces to develop innovative solutions that leverage the Internet of Things (IoT), manufacturing solutions, and AI technologies to address the pain points of the semiconductor industry. Their collaborative efforts have resulted in a seamlessly integrated manufacturing solution that offers real-time monitoring, automated reporting, quality inspection, cognitive worker guidance, and predictive analytics.

One of the key benefits of these AI technologies is their ability to provide predictive and generative capabilities. With the help of conversational chatbots embedded with large language models and internal knowledge graphs, manufacturers can track real-time operations, identify equipment issues before they ruin batches, and trigger predictive maintenance. This level of insight and intelligence is invaluable in a complex industry where broken links in the manufacturing process can have significant impacts, such as lack of visibility, difficulty in decision-making, and safety concerns for workers.

By leveraging SAP's Conversational AI, Visual Inspection with AI, and Generative AI solutions, manufacturers can achieve real-time manufacturing execution planning, automated reporting, quality inspection, cognitive worker guidance, and end-to-end predictive analytics. These AI-powered solutions provide a comprehensive view of the production process, from planning to execution, enabling management to make informed decisions and optimize operations.

The collaboration between SAP, IBM, and PDF Solutions represents a major step forward in the race for semiconductor manufacturing dominance. With AI technology driving the industry's evolution, manufacturers can overcome the challenges of a dispersed supply chain and stay ahead in the global race for semiconductor supremacy.

To learn more about SAP's AI solutions for the semiconductor industry, visit the following pages:

SAP Conversational AI: SAP Conversational AI | SAP Community
SAP Visual Inspection with AI: Visual Inspection with AI - Detect product defects faster on the shop floor (sap.com)
SAP Generative AI: Generative AI for analytics and planning (sap.com)

2024 - Patches/fixes for SAP MII

2024-04-03T16:22:31.221000+02:00

08/30/2024:

MII_ADMIN 15.5 SP 000 Patch 25:

LogDbRowcount | Added a new MII System Job to log row count for database tables, note 3485317

XMII 15.5 SP 000 Patch 41:

LogDbRowcount | Added a new MII System Job to log row count for database tables, note 3485317

08/28/2024:

MII_ADMIN 15.4 SP 001 Patch 23:

LogDbRowcount | Added a new MII System Job to log row count for database tables, note 3485317

XMII 15.4 SP 001 Patch 51:

Added disable automatic follow redirects option to HTTP Post Action Block, note 3493822
History | Improved History Mode for the Scheduler Service, note 3442938
LogDbRowcount | Added a new MII System Job to log row count for database tables, note 3485317
PE Job inserts multiple rows when job is run several times, note 3412798

08/21/2024:

MII_ADMIN 15.5 SP 001 Patch 12:

PCo query fails in summer time skip period, note 3503051
LogDbRowcount | Added a new MII System Job to log row count for database tables, note 3485317

XMII 15.5 SP 001 Patch 20:

Security roles are not imported along with projects imported in System Management, note 3491784
MII Workbench Support using SAP Machine 17/21, note 3492652
PCo query fails in summer time skip period, note 3503051
LogDbRowcount | Added a new MII System Job to log row count for database tables, note 3485317

7/30/2024:

MII_ADMIN 15.3 SP 001 Patch 29:

System Management - Projects screen assigned roles editing Issue, note 3294426
System Warning window on MII home page for component incompatibility, note 3399037

XMII 15.3 SP 001 Patch 58:

MII Schedulers fails after Netweaver SP29 upgrade due to exception in update query on XMII_TRANSACTIONS, note 3490586
Added disable automatic follow redirects option to HTTP Post Action Block, note 3493822
System Warning window on MII home page for component incompatibility, note 3399037
GetDBTablesRowCount | Added the XMII_DBG* tables to the report, note 3486435

07/29/2024:

XMII 15.5 SP 000 Patch 40:

XML to JSON Converter Issue, note 3478018
GetDBTablesRowCount | Added the XMII_DBG* tables to the report, note 3486435
MII Schedulers fails after Netweaver SP29 upgrade due to exception in update query on XMII_TRANSACTIONS, note 3490586
Security roles are not imported along with projects imported in System Management, note 3491784
Added disable automatic follow redirects option to HTTP Post Action Block, note 3493822

07/18/2024:

XMII 15.5 SP 001 Patch 19:

Added disable automatic follow redirects option to HTTP Post Action Block, note 3493822

07/17/2024:

MII_ADMIN 15.4 SP 001 Patch 22:

System Management - Projects screen assigned roles editing Issue, note 3294426
System Warning window on MII home page for component incompatibility, note 3399037

XMII 15.4 SP 001 Patch 50:

MII Schedulers fails after Netweaver SP29 upgrade due to exception in update query on XMII_TRANSACTIONS, note 3490586
Security roles are not imported along with projects imported in System Management, note 3491784
System Warning window on MII home page for component incompatibility, note 3399037
XML to JSON Converter Issue, note 3478018
GetDBTablesRowCount | Added the XMII_DBG* tables to the report, note 3486435

07/05/2024:

XMII 15.5 SP 001 Patch 18:

XMII_TRANSACTIONS | Increasing the length of thread name columns to 1000 characters, note 3490586
UIElementRadioButtonM | SSCE UI Element Radio Button bad styling when selected, note 3480775
Save destination folder path goes up one level after each folder export, note 3481280
New folder cancellation - appropriate message is not displayed, note 3483523
GetDBTablesRowCount | Added the XMII_DBG* tables to the report, note 3486435

6/28/2024:

XMII 15.3 SP 001 Patch 57:

Scheduler jobs disappearing, note 3476306
SAP MII - Processing rules - Export issue, note 3468097
Save destination folder path goes up one level after each folder export, note 3481280
New folder cancellation - appropriate message is not displayed, note 3483523

06/26/2024:

XMII 15.4 SP 001 Patch 49:

New folder cancellation - appropriate message is not displayed, note 3483523
Scheduler jobs disappearing, note 3476306
SAP MII - Processing rules - Export issue, note 3468097
Save destination folder path goes up one level after each folder export, note 3481280

06/25/2024:

MII_ADMIN 15.5 SP 000 Patch 23:

System Warning window on MII home page for component incompatibility, note 3399037

XMII 15.5 SP 000 Patch 39:

System Warning window on MII home page for component incompatibility, note 3399037
Scheduler jobs disappearing, note 3476306
SAP MII - Processing rules - Export issue, note 3468097
Save destination folder path goes up one level after each folder export, note 3481280
New folder cancellation - appropriate message is not displayed, note 3483523

06/14/2024:

XMII 15.5 SP 001 Patch 17:

SAP MII - Processing rules - Export issue, note 3468097
Support for X-CSRF-Token in MII HTTP POST action block, note 3429523
Scheduler jobs disappearing, note 3476306
XML to JSON Converter Issue, note 3478018

06/06/2024:

MII_ADMIN 15.3 SP 001 Patch 27:

Schedule pattern allows saving of invalid values, note 3471431

XMII 15.3 SP 001 Patch 56:

Query Number format is not working as expected, note 3443976
Support for X-CSRF-Token in MII HTTP POST action block, note 3429523
Schedule pattern allows saving of invalid values, note 3471431

06/01/2024:

MII_ADMIN 15.4 SP 001 Patch 20:

Schedule pattern allows saving of invalid values, note 3471431
Open activities with checked-out files are still visible after disabling and enabling the NWDI configuration, note 3433017

XMII 15.4 SP 001 Patch 48:

History | Improved History Mode for the Scheduler Service, note 3442938
GetDBTablesRowCountOEE | Get the total row count of all the key tables based on OEE, note 3443901
Adding Transaction Persistence as parameter in case of transaction called via SOAPRunner interface, note 3445523
Logs Addition: - Missing Order in MII due to Duplicate Message ID creation for XMII_JCOMESSAGES, note 3448342
History | adding back the columns removed by SAP Note 3442938, note 3470060
Schedule pattern allows saving of invalid values, note 3471431
Open activities with checked-out files are still visible after disabling and enabling the NWDI configuration, note 3433017
Catalog Query with formula does not give correct result, note 3324351

5/30/2024:

MII_ADMIN 15.5 SP 000 Patch 22:

Schedule pattern allows saving of invalid values, note 3471431
Open activities with checked-out files are still visible after disabling and enabling the NWDI configuration, note 3433017
NWDI configuration gives null pointer exception on save, note 3342267
Shared Memory is in read only mode even though user has all access related to Shared memory, note 3447829

XMII 15.5 SP 000 Patch 38:

Open activities with checked-out files are still visible after disabling and enabling the NWDI configuration, note 3433017
Schedule pattern allows saving of invalid values, note 3471431
Support for X-CSRF-Token in MII HTTP POST action block, note 3429523
History | adding back the columns removed by SAP Note 3442938, note 3470060
Logs Addition: - Missing Order in MII due to Duplicate Message ID creation for XMII_JCOMESSAGES, note 3448342
Shared Memory is in read only mode even though user has all access related to Shared memory, note 3447829

5/23/2024:

MII_ADMIN 15.5 SP 001 Patch 10:

Adding Transaction Persistence as parameter in case of transaction called via SOAPRunner interface, note 3445523

XMII 15.5 SP 001 Patch 16:

Query Number format is not working as expected, note 3443976
Logs Addition: - Missing Order in MII due to Duplicate Message ID creation for XMII_JCOMESSAGES, note 3448342
History | adding back the columns removed by SAP Note 3442938, note 3470060
UIElementTextFieldM TextField shows with wrong style on value change, note 3470582
Schedule pattern allows saving of invalid values, note 3471431
Catalog Query with formula does not give correct result, note 3324351
GetDBTablesRowCountOEE | Get the total row count of all the key tables based on OEE, note 3443901

5/21/2024:

MII_ADMIN 15.3 SP 001 Patch 26:

Shared Memory is in read only mode even though user has all access related to Shared memory, note 3447829
Open activities with checked-out files are still visible after disabling and enabling the NWDI configuration, note 3433017

XMII 15.3 SP 001 Patch 55:

File size not updated leading to possible Out Of Memory during blowout, note 3453485
Unused system property "Monitoring Retention Duration", note 3449627
Shared Memory is in read only mode even though user has all access related to Shared memory, note 3447829
Open activities with checked-out files are still visible after disabling and enabling the NWDI configuration, note 3433017
Catalog Query with formula does not give correct result, note 3324351
GetDBTablesRowCountOEE | Get the total row count of all the key tables based on OEE, note 3443901
Adding Transaction Persistence as parameter in case of transaction called via SOAPRunner interface, note 3445523

5/7/2024:

XMII 15.4 SP 001 Patch 47:

Catalog query with production events returns Non-PE for valid data, note 3333520
No entities displayed in OData Modeller, note 3279995

5/3/2024:

MII_ADMIN 15.5 SP 001 Patch 9:

Shared Memory is in read only mode even though user has all access related to Shared memory, note 3447829

XMII 15.5 SP 001 Patch 15:

Shared Memory is in read only mode even though user has all access related to Shared memory, note 3447829
Catalog query with production events returns Non-PE for valid data, note 3333520

4/26/2024:

MII_ADMIN 15.5 SP 000 Patch 21:

Unused system property "Monitoring Retention Duration", note 3449627
System Management - Projects screen assigned roles editing Issue, note 3294426

XMII 15.5 SP 000 Patch 37:

Unused system property "Monitoring Retention Duration", note 3449627
File size not updated leading to possible Out Of Memory during blowout, note 3453485
PE Job inserts multiple rows when job is run several times, note 3412798
Additional Logging in XMII-Module, note 3340019
Enhancing the logs for MII Start and Stop services, note 3438776
GetDBTablesRowCountOEE | Get the total row count of all the key tables based on OEE, note 3443901
Query Number format is not working as expected, note 3443976
MII show more details for PCo Connector data server creation errors, note 3449609

4/24/2024:

XMII 15.5 SP 001 Patch 14:

File size not updated leading to possible Out Of Memory during blowout, note 3453485

4/19/2024:

MII_ADMIN 15.4 SP 001 Patch 19:

System Management - Projects screen assigned roles editing Issue, note 3294426
Shared Memory is in read only mode even though user has all access related to Shared memory, note 3447829
Unused system property "Monitoring Retention Duration", note 3449627

XMII 15.4 SP 001 Patch 46:

Additional Logging in XMII-Module, note 3340019
Enhancing the logs for MII Start and Stop services, note 3438776
Query Number format is not working as expected, note 3443976
Shared Memory is in read only mode even though user has all access related to Shared memory, note 3447829
MII show more details for PCo Connector data server creation errors, note 3449609
Unused system property "Monitoring Retention Duration", note 3449627
File size not updated leading to possible Out Of Memory during blowout, note 3453485

4/12/2024:

MII_ADMIN 15.5 SP 001 Patch 8:

Unused system property "Monitoring Retention Duration", note 3449627

XMII 15.5 SP 001 Patch 13:

Adding Transaction Persistence as parameter in case of transaction called via SOAPRunner interface, note 3445523
MII show more details for PCo Connector data server creation errors, note 3449609
Unused system property "Monitoring Retention Duration", note 3449627
Event data from onChange event not propagated, note 3449926
Event Parameters do not get updated, note 3449959
UIElementCheckBoxM | SSCE UI Element CheckBox bad styling when unchecking, note 3453122
PE Job inserts multiple rows when job is run several times, note 3412798
History | Improved History Mode for the Scheduler Service, note 3442938

4/10/2024:

MII_ADMIN 15.3 SP 001 Patch 25:

Unused system property "Monitoring Retention Duration", note 3449627
System Management - Projects screen assigned roles editing Issue, note 3294426

XMII 15.3 SP 001 Patch 54:

Unused system property "Monitoring Retention Duration", note 3449627
Missing Order in MII due to Duplicate Message ID creation for XMII_JCOMESSAGES, note 3448342
Incorrect Search result for fields with "_" character, note 3227452
PE Job inserts multiple rows when job is run several times, note 3412798
Enhancing the logs for MII Start and Stop services, note 3438776
MII more details for PCo Connector data server creation errors, note 3449609

03/19/2024:

XMII 15.5 SP 000 Patch 36:

Conditional | Added Conditional Action Block log entries in transaction debug output, note 3440246
History | Improved History Mode for the Scheduler Service, note 3442938
Query Number format is not working as expected, note 3443976
Adding Transaction Persistence as parameter in case of transaction called via SOAPRunner interface, note 3445523

03/14/2024:

MII_ADMIN 15.3 SP 001 Patch 24:

Job status shows as scheduled in the Scheduler screen, note 2031689

XMII 15.3 SP 001 Patch 53:

DB Object is closed error is thrown in case of sql transaction, note 3364376
Unable to read DataBufferActionInstance parameter using databuffer service, note 3395994
Usage Status Monitoring for DataServer with wrong date, note 3429629
Workbench file export generates the wrong cemd file for SSCE Dashboards, note 3430755
Additional logs for transaction action failure due to timeoutException, note 3407507
MII transaction fails with SAP DBTech JDBC: Object is closed error, note 3416130

03/11/2024:

MII_ADMIN 15.5 SP 001 Patch 7:

System Management - Projects screen assigned roles editing Issue, note 3294426
Details header not changing after selecting any tag in simulator services under data services, note 3264633
Open activities with checked-out files are still visible after disabling and enabling the NWDI configuration, note 3433017
Job status shows as scheduled in the Scheduler screen, note 2031689

XMII 15.5 SP 001 Patch 12:

Enhancing the logs for MII Start and Stop services, note 3438776
Conditional | Added Conditional Action Block log entries in transaction debug output, note 3440246
Details header not changing after selecting any tag in simulator services under data services, note 3264633
Version history missing in MII workbench, note 3418076
Additional logs and traces in message processing module of MII, note 3426125
Usage Status Monitoring for DataServer with wrong date, note 3429629
NWDI version history displays limited number of activities, note 3432814
Open activities with checked-out files are still visible after disabling and enabling the NWDI configuration, note 3433017
DependencyManager | Added dependency check for the MII_ADMIN component version, note 3308632
Additional Logging in XMII-Module, note 3340019
System Warning window on MII home page for component incompatibility, note 3399037

03/07/2024:

MII_ADMIN 15.4 SP 001 Patch 18:

Job status shows as scheduled in the Scheduler screen, note 2031689

XMII 15.4 SP 001 Patch 45:

Conditional | Added Conditional Action Block log entries in transaction debug output, note 3440246
DB Object is closed error is thrown in case of sql transaction, note 3364376
Job status shows as scheduled in the Scheduler screen, note 2031689
MII transaction fails with SAP DBTech JDBC: Object is closed error, note 3416130

03/05/2024:

MII_ADMIN 15.5 SP 000 Patch 20:

Job status shows as scheduled in the Scheduler screen, note 2031689

XMII 15.5 SP 000 Patch 35:

DB Object is closed error is thrown in case of sql transaction, note 3364376
Job status shows as scheduled in the Scheduler screen, note 2031689
JMS updates causing scheduler breakdown, note 3360558
Usage Status Monitoring for DataServer with wrong date, note 3429629
Workbench file export generates the wrong cemd file for SSCE Dashboards, note 3430755
Additional logs for transaction action failure due to timeoutException, note 3407507
MII transaction fails with SAP DBTech JDBC: Object is closed error, note 3416130

02/16/2024:

MII_ADMIN 15.4 SP 001 Patch 17:

NWDI configuration gives null pointer exception on save, note 3342267

XMII 15.4 SP 001 Patch 44:

Support for X-CSRF-Token in MII HTTP POST action block, note 3429523
Usage Status Monitoring for DataServer with wrong date, note 3429629
Workbench file export generates the wrong cemd file for SSCE Dashboards, note 3430755
SSO cookie logged and displayed in MII Log Viewer, note 3410041
Get Jar Signing related information which gets checked while opening workbench., note 3346027
NWDI configuration gives null pointer exception on save, note 3342267
Scheduler history cleanup default value changed from 24 hours to 72 hours, note 3394218
Unable to read DataBufferActionInstance parameter using databuffer service, note 3395994
Scheduler history comes blank when job is stuck or not executed in last hour, note 3396099
JMS updates causing scheduler breakdown, note 3360558

02/09/2024:

XMII 15.5 SP 001 Patch 11:

Running remote workbench with proxy for jar based workbench, note 3369660
Unable to read DataBufferActionInstance parameter using databuffer service, note 3395994
Source table is missing inside the Global setting on SSCE, note 3424542
Settings.view | Event Parameters table headers not visible, note 3426391
MII PortalContent.zip file not found under Tools and Archives, note 3427393
i5Grid getRowCount() error, note 3428910
UIElementTextFieldM | Text Field UI Element size, note 3429413
Workbench file export generates the wrong cemd file for SSCE Dashboards, note 3430755
Additional logs for transaction action failure due to timeoutException, note 3407507

02/06/2024:

MII_ADMIN 15.3 SP 001 Patch 23:

NWDI configuration gives null pointer exception on save, note 3342267

XMII 15.3 SP 001 Patch 52:

SSO cookie logged and displayed in MII Log Viewer, note 3410041
Cannot view changelist details or process a changelist, note 3336846
Get Jar Signing related information which gets checked while opening workbench., note 3346027
MII workbench login with x.509 certificate based SSO login, note 3370246
NWDI configuration gives null pointer exception on save, note 3342267
Running remote workbench with proxy for jar based workbench, note 3369660
Scheduler history cleanup default value changed from 24 hours to 72 hours, note 3394218
New Workbench launcher can not open the workbench if server url has '-' in it, note 3394368
Scheduler history comes blank when job is stuck or not executed in last hour, note 3396099
JMS updates causing scheduler breakdown, note 3360558

01/17/2024:

XMII 15.4 SP 001 Patch 43:

Cannot view changelist details or process a changelist, note 3336846
Catalog query with production events is returning Non-PE when there are records in PE table, note 3338596
Duplicate Rows inserted in PE table due to duplicate shift rows in MPM_TC37T table, note 3345988
PIC Analysis Query - Production events displaying incorrect data, note 3219251
Duplicate rows inserted in production table when PE job is run again, note 3333504
i5Chart (Gauge Chart Type) is starting from zero value for any change in Value., note 3404399

01/12/2024:

XMII 15.5 SP 001 Patch 10:

Catalog query with production events is returning Non-PE when there are records in PE table, note 3338596
Additional Logging in XMII-Module, note 3340019
MII workbench login with x.509 certificate based SSO login, note 3370246
Duplicate Rows inserted in PE table due to duplicate shift rows in MPM_TC37T table, note 3345988
Scheduler history cleanup default value changed from 24 hours to 72 hours, note 3394218
Production events job creates duplicate records in Production Events table, note 3300655
Duplicate rows inserted in production table when PE job is run again, note 3333504
i5Chart (Gauge Chart Type) is starting from zero value for any change in Value., note 3404399
SSO cookie logged and displayed in MII Log Viewer, note 3410041
Bug in SSCE text field i5ValueHelp, note 3413146

MII transaction fails with SAP DBTech JDBC: Object is closed error, note 3416130

MII configuration and content transport management

2024-04-05T09:49:58.574000+02:00

1. Introduction

SAP Manufacturing Integration and Intelligence is a manufacturing platform providing seamless integration from top floor to shop floor and vice versa, shop floor operational visibility and manufacturing performance management. customer/partner does quite of MII configuration and MII content development to cater to specific shop floor requirement customer has which needs to be transported across system e.g., development to quality to production system. This document will share what are the different options for transporting MII configuration and MII content across systems.

2. MII Configuration transport

MII has quite of configuration objects e.g. data servers, credential store etc. which needs to be transported across system for faster implementation. in MII, There are 2 ways of transporting MII configuration i.e., using export/import using Zip files and using CTS+ configuration which will be discussed further.

2.1 MII Configuration transport using zip file.

In order to transport MII configuration data using zip file, please use the following steps.

In the source system, Go to MII Menu -> System Management -> Configuration -> Export tab. Choose Export Method as File System, file format as Zip, Encryption Algorithm as one of the option mentioned in the dropdown, provide a pass phrase to protect the file and select the configuration data you would like to transport to other system.

2. It will provide an option to download the file into your file system. Save the file in your machine.

3. In the target system, Go to MII Menu -> System Management -> Configuration -> Import tab. Choose the encryption algorithm and pass phrase as what was provided during the export, provide the file location and choose Import button. This will import the content from the Zip file into target system.

2.2 MII Configuration transport using CTS+.

Export/Import using the zip file could be quite cumbersome, provide no tracking and approval process hence it is possible to use CTS+ process to transport the MII configuration data across system which internally creates an ABAP transport request, attaches the content file to the transport and on release import into target system as defined in the transport route in ABAP system. This process can be integrated with solution manager also to provide transporting content from different technologies i.e., MII and ABAP. Please check the note 3452468 - How to transport MII configuration data across system using CTS+ approach for step by step details on how to configure such transport.

3 MII Content transport

Customer/Partner creates quite of development objects in MII using MII workbench i.e. Query Template, Display template, transaction. All these objects are stored in MII DB in XML format. This content needs to be transported across system for seamless implementation and also requires proper source code management since multiple people need to work on these development object and for multiple releases. MII supports multiple options for transporting MII content with and without source code management which will be discussed now.

3.1 MII Content transport using zip file.

In order to transport MII content data using zip file, please use the following steps.

In the source system, Go to MII Menu -> System Management -> Projects and select a project and choose Export button.

It will download the project content in a zip file and store it in your machine.
In the target system, Go to MII Menu -> System Management -> Projects and select import. Provide the zip file path in the pop up screen and choose Ok. This will import the project in the target system.

The transport using the zip file approach doesn’t provide any source code management for MII content and moves the whole project instead of only changed projects hence it is always recommended to use the NWDI based approach which provides central source code management, build process and deployment process.

3.2 MII Content transport using NWDI integration with CMS.

MII Content transport using NWDI approach uses SAP NetWeaver Java Development Infrastructure with following components.

Design Time Repository (DTR): DTR is a central storage of design time objects (application source code) that supports distributed versioning. Access to the central storage is through the standard WebDAV and DeltaV protocols.
Component Build Service (CBS): CBS plays a central role in the realization of the concepts of the NWDI. It offers centralized build services, storage of build results and build tools.
Change Management Service (CMS): CMS offers services to configuration of the landscape, transport software changes within the landscape and also packaging and delivery of the components being developed using NWDI.

For step-by-step details on how to do this set up, kindly check the following note 3452084 - How to setup/configure NWDI in MII for content development.

3.3 MII Content transport using NWDI integration with CM Services

CM Services is a enhanced version of CMS which provides fine granular transport of the activities. For details please check the note 1361909 - CM Services in CTS+ and following blog.

MII NWDI integration using CMS moves the all the project across system. In case much fine granular transport is needed then use NWDI integration with CM Services. Please find the step-by-step details in following note 2862116 - CM services integration with SAP MII for build process using NWDI.

4 Conclusion

SAP MII supports detailed transport management for configuration and MII Content

based on above mentioned information. In case, you have different version of MII content

development e.g., one deployed on production on which corrections are needed for

patch delivery and another version for new development then it is recommended to use

different tracks for these scenarios. Please check the following blog for more details.

How to configure NWDI in SAP MII for Content Development

2024-04-16T12:44:07.800000+02:00

This post will guide you through all steps necessary for the initial configuration of NetWeaver Development Infrastructure (NWDI) and its integration with SAP MII. After all configuration steps are done, you will be able to enable NWDI feature via SAP MII Home Page and use NWDI powered processes.

Please check the attached document in SAP Note 3452084 which guide you through the complete process.

The document describes two systems:

1) Source System: where SLD and NWDI server is configured.

2) Target System: where MII runs.

Once the configuration is completed, you should be able to enable the NWDI and use MII along with NWDI.

Usage of MDO in SAP MII & SAP Ui5 Application Development to consume the MDO Data

2024-05-20T13:57:33.657000+02:00

Hello SAPians,

In this Blog post, I would like to take you through the concept of MDOs in SAP MII where, I would like to provide the step-by-step process to create a MDO object (as a data table) and use the MDO object to perform different types of CRUD operations and also create a SAP Ui5 Application which consumes the MDO queries to manipulate the data using different functions and deploy the application in SAP MII.

So, let's start with What is a MDO and why should we use an MDO in our applications?

An MDO is a semantic layer and level of abstraction on top of SAP MII data acquisition mechanisms, such as query templates & transactions.

There are two types of MDOs that can be configured such as:

1. Persistent MDO - when the data provider for the object is executed, the system persists the data that is returned.

2. On-Demand MDO - when the data provider for the object is executed, the data is not persisted. Instead, the data is returned from the data source in the real-time.

MDO is tightly coupled with your MII content and it is even defined inside of the MII Workbench along with the rest of your MII content. It also has a lifecycle tied to it which means that the definition for the management of its data is also part of the object definition which simplifies the complexity of the data management.
The MDO object still related one to one with a table in the NetWeaver database and will scale to whatever size the underlying NetWeaver database allows you to but it will not allow you to setup primary & foreign key dependencies, triggers, sequences, or anything else that Open SQL does not support.

you can get to more about the SAP MDO from the SAP MII help portal

Now, let's see how to create a MDO object, define the attributes and develop necessary CRUD operation queries using the MDO object.

Below are the URLs to use the MDO queries as web services and consume them in different places (be it in a SAP Ui5 web applications)

1. Insert Data:
http://<server>:<port>/XMII/Illuminator?QueryTemplate=<YourInsertQueryPath>&Param.1=<value>&Param.2=<value>&Param.3=<value>&Param.4=<value>&Param.5=<value>&Param.6=<value>

2. Update Data:
http://<server>:<port>/XMII/Illuminator?QueryTemplate=<YourUpdateQueryPath>&Param.1=<value>&Param.2=<value>&Param.3=<value>

3. Delete Data:
http://<server>:<port>/XMII/Illuminator?QueryTemplate=<YourDeleteQueryPath>&Param.1=<value>

4. Retrieve Data:
http://<server>:<port>/XMII/Illuminator?QueryTemplate=<YourSelectQueryPath>

As we are ready with our requires MDOs queries, let's start creating a SAP Ui5 web application in VS code/BAS Tool(easier in VScode/BAS Tool when compared to Developing a web application in SAP MII workbench)

As we know, SAP Ui5 application follows MVC architecture, we develop application using Model, View & controller in the application. The project structure would be as follows:

In this application, we are embedding the model within the controller itself i.e where we are consuming the MDO queries as web services. Hence, there is no Model folder/File here. For full fledged SAP ui5 application, please follow the SAP Ui5 guidelines for developing the web application.

Now, let's start developing a Web application which consumes the following MDO queries and display the data in the tabular format.

The below is the ui5 web application demo using MDOs & corresponding MDO queries created in SAP MII as data source for the web application

Below is the code snippet that is responsible for achieving the above web application.

index.html

<html>
    <head>
        <script src="https://ui5.sap.com/1.122.0/resources/sap-ui-core.js"
                 data-sap-ui-libs="sap.m"
                 data-sap-ui-theme="sap_belize_plus"
                 data-sap-ui-resourceroots='{
                    "am":"./"
                 }'
                 data-sap-ui-bindingSyntax="complex">
        </script>
        <script>
            var oView=new sap.ui.view({
                id:"xmlV",
                viewName:"am.view.view1",
                type:"XML"
            });
           oView.placeAt("uiHere");
            
        </script>
    </head>
    <body class="sapUiBody">
        <div id="uiHere"></div>
    </body>
</html>

Here, in the index.html we are performing the bootstrap with SAP Ui5 libraries and creating a view objects which pulls the all the ui elements defined in the view code and places the Ui elements in the division tag of the body.

Main.view.xml

<mvc:View xmlns:mvc="sap.ui.core.mvc" 
          xmlns="sap.m"
          xmlns:f="sap.ui.layout.form"
          xmlns:t="sap.ui.table"
          xmlns:c="sap.ui.core"
          xmlns:f1="sap.f"
        controllerName="am.controller.Main">
        <Page title="Employee Data">
            <f:SimpleForm backgroundDesign="Solid"  editable="true" id="simpleForm">

                <Label text="Employee Name" labelFor="EmpName" />
                <Input id="EmpName" required="true" width="30%" />

                <Label text="Employee ID" labelFor="EmpId" />
                <Input id="EmpId" required="true" width="30%" />

                <Label text="Gender" labelFor="Gen" />
                <Input id="Gen" required="true" width="30%" />

                <Label text="Age" labelFor="Age" />
                <Input id="Age" required="true" width="30%" />

                <Label text="Salary" labelFor="sal" />
                <Input id="Sal" required="true" width="30%" />

                <Label text="Designation" labelFor="Des" />
                <Input id="Des" required="true" width="30%" />

                <Label text="Location" labelFor="Loc" />
                <Input id="Loc" required="true" width="30%" />

            </f:SimpleForm>

            <Toolbar>
                <Button text="Insert New Employee" press="insertEmp"></Button>
          
                <Button text="Update Employee Record" press="updateEmp"></Button>
          
               <Button text="Delete Employee" press="deleteEmp"></Button>

                <Button  icon="sap-icon://synchronize"  press="refresh" ></Button>
                <Button icon="sap-icon://clear-all"  press="clearAllFields" ></Button>
            </Toolbar>

            <f1:DynamicPage>
                <f1:content>
                    <t:Table id="emptab" selectionMode="Single" rows="{SEModel>/Rowsets/Rowset/0/Row}">
                        <t:extension>
                            <OverflowToolbar style="Clear">
                                <Title text="Employee Records" textAlign="Center"/>
                            </OverflowToolbar>
                        </t:extension>
                        <t:columns>
                            <t:Column width="11rem">
                                <Label text="Employee Name" />
                                <t:template>
                                    <Text text="{SEModel>EmpName}" wrapping="false" />
                                </t:template>
                            </t:Column>
                            <t:Column width="11rem">
                                <Label text="Employee ID" />
                                <t:template>
                                    <Text text="{SEModel>EmpID}" wrapping="false" />
                                </t:template>
                            </t:Column>
    
                            <t:Column width="9rem">
                                <Label text="Gender" />
                                <t:template>
                                    <Text text="{SEModel>Gender}" wrapping="false" />
                                </t:template>
                            </t:Column>
                            <t:Column width="9rem">
                                <Label text="Age" />
                                <t:template>
                                    <Text text="{SEModel>Age}" wrapping="false" />
                                </t:template>
                            </t:Column>
                            <t:Column width="7rem">
                                <Label text="Salary" />
                                <t:template>
                                    <Text text="{SEModel>Salary}" wrapping="false" />
                                </t:template>
                            </t:Column>
    
                            <t:Column width="11rem">
                                <Label text="Designation" />
                                <t:template>
                                    <Text text="{SEModel>Designation}" wrapping="false" />
                                </t:template>
                            </t:Column>
    
                            <t:Column width="11rem">
                                <Label text="Location" />
                                <t:template>
                                    <Text text="{SEModel>Location}" wrapping="false" />
                                </t:template>
                            </t:Column>
    
                        </t:columns>
                    </t:Table>
                </f1:content>
            </f1:DynamicPage>
        </Page>
</mvc:View>

In View code, we have we have placed all the necessary input fields and a table to display the data, we can bind the data using different binding modes such as

Property Binding
Expression Binding
Aggregation Binding
Element Binding

Here, i have used property binding to display the employee details in the table.

Main.controller.js

sap.ui.define([
    'sap/ui/core/mvc/Controller'
,
    'sap/ui/model/json/JSONModel'
    ],function(oCon,JSONModel) {

    'use strict';
    return oCon.extend("am.controller.Main",{
            
        onInit:function(){
	var SEModel=new JSONModel("/XMII/Illuminator?QueryTemplate=<Path>/SelectEmpData&Content-Type=text/json");
            this.getView().setModel(SEModel,"SEModel");
        },
	refresh:function(){
            var SEModel=new JSONModel("/XMII/Illuminator?QueryTemplate=<Path>/SelectEmpData&Content-Type=text/json");
            var E=this.getView().setModel(SEModel,"SEModel");
            return E;
            sap.m.MessageToast.show("Data Refreshed!",{
                duration:2000,
                width:"55em",
            });
        },
        insertEmp:function(){
            var empName=this.getView().byId("EmpName").getValue();
            var empId=this.getView().byId("EmpId").getValue();
            var gen=this.getView().byId("Gen").getValue();
            var age=this.getView().byId("Age").getValue();
            var sal=this.getView().byId("Sal").getValue();
            var des=this.getView().byId("Des").getValue();
            var loc=this.getView().byId("Loc").getValue();
            
            if(empName==""||empId==""||gen==""||age==""||sal==""||des==""||loc==""){
                sap.m.MessageToast.show("please enter all the fields to create an Employee record!!",{
                    duration:2000,
                    width:"55em",
                });
            }
	else{
            	var IEModel= new JSONModel("/XMII/Illuminator?QueryTemplate=<Path>/InsertEmpData&Param.1="+empName+"&Param.2="+empId+
"&Param.3="+gen+"&Param.4="+age+"&Param.5="+sal+"&Param.6="+des+"&Param.7="+loc);
            	this.getView().setModel(IEModel,"IEModel");
		sap.m.MessageToast.show("New Employee record created successfully!!!",{
                   		 duration:2000,
                   		 width:"55em",
               	 });
	}
        },
        updateEmp:function(){

            var empId=this.getView().byId("EmpId").getValue();
            var sal=this.getView().byId("Sal").getValue();
            var des=this.getView().byId("Des").getValue();
            var loc=this.getView().byId("Loc").getValue();
            
            if(empId==""||sal==""||des==""||loc==""){
                sap.m.MessageToast.show("please enter Employee ID, Salary, Designation & Location to update a Employee record!!",{
                    duration:2000,
                    width:"55em",
                });
            }
            var UEModel= new JSONModel("/XMII/Illuminator?QueryTemplate=<Path>/UpdateEmpData&Param.1="+empId+"&Param.2="+sal+"&Param.3="+des+"&Param.4="+loc);
            this.getView().setModel(UEModel,"UEModel");
            sap.m.MessageToast.show("Employee Record Updated Successfully!!",{
                duration:2000,
                width:"55em",
            });
        },
        clearAllFields:function() {
            this.getView().byId("EmpName").setValue("");
            this.getView().byId("EmpId").setValue("");
            this.getView().byId("Gen").setValue("");
            this.getView().byId("Age").setValue("");
            this.getView().byId("Sal").setValue("");
            this.getView().byId("Des").setValue("");
            this.getView().byId("Loc").setValue("");
        },
        deleteEmp:function(){
	var empId=this.getView().byId("EmpId").getValue();
            if(empId==""){
                sap.m.MessageToast.show("please enter Employee ID to delete an Employee record!!",{
                    duration:2000,
                    width:"55em",
                });
            }
            var UEModel= new JSONModel("/XMII/Illuminator?QueryTemplate=<Path>/DeleteEmpData&Param.1="+empId);
            this.getView().setModel(UEModel,"UEModel");
            sap.m.MessageToast.show("Employee Record deleted Successfully!!",{
                duration:2000,
                width:"55em",
            });
        }
    });
});

In controller code, we have defined the functions to trigger an event whenever a button is clicked and create a named JSON model and loaded the model using the illuminator services of the MDO queries created earlier.

once the application is developed, we need to create a manifest.json file within the webapp folder, which is an application description file holds the application properties such as application type, id, etc..

Manifest.json

{
    "sap.app":{
        "id":"MDOapp",
        "type":"application"
    }
}

you can find more information on Application descriptor file here

once all the above files are developed, you can create the ui5 web project by following the below guidelines:

Note: The following commands has to be executed within the project but outside webapp folder

Initiate a node project using npm init in the terminal of VScode/BAS tool - this should create a package.json file in the project folder.
now, we initiate a ui5 project using ui5 init - this should create a ui5.yaml file
you can now test the project by using the command ui5 serve -o index.html which open the ui5 web application in the browser without any errors and your application will be displayed on the browser.

Deployment of SAP Ui5 App in SAP MII:

once the ui5 application is built using the above guidelines, export the code from VS Code/BAS Tool to a project specific location.
now open SAP MII workbench and navigate to the Web Tab of SAP MII project where you want to deploy the application.
Right click on the project --> import --> select the Ui5 project folder --> open. Now the application is deployed in the SAP MII.
For Testing, open the project --> web app folder --> right click on index.html(basically landing page of the application) copy url and open it in browser, your sap ui5 application should load without any issue.
or, you can test by opening the index.html file and click on test icon on the top-right of MII Menu bar.

I hope, this blog provides you the basic knowledge of creation of MDO objects, queries and its consumption in a SAP Ui5 application. Please do let me know if you have any queries or suggestions.

Note: Please note that this is a basic SAP Ui5 application to demonstrate the usage of MDO objects and queries in SAP MII.

Thank You!

*VSCode - Visual Studio Code
*BAS - Business Application Studio
*MDO - Manufacturing Data Objects

📅 30-Day SAP PP Module Series

2025-04-29T16:56:37.245000+02:00

Hello SAP Community!

I’m thrilled to share that I’ll be launching a 30-day educational SAP Community series focused entirely on SAP Production Planning (SAP PP) starting May 1, 2025!

This series is designed to support:

SAP consultants (functional & technical)
Production and supply chain professionals
Newcomers to SAP S/4HANA
Anyone looking to sharpen their PP knowledge

What You Can Expect

Each day, I’ll be sharing concise, visual-rich posts covering:

Core SAP PP concepts (BOM, Routings, MRP)
Discrete vs. Process vs. Repetitive manufacturing
Capacity planning, order management, and costing
Fiori apps, embedded analytics, and S/4HANA innovations
Integration with MM, SD, QM, CO, and more
Use cases, pro tips, and real-world examples

How to Join the Series

Follow me on SAP Community
Invite your team members or peers who might benefit
Engage with questions and share your own insights

This is a great opportunity to brush up on your SAP PP fundamentals or go deeper into advanced topics like MRP Live, Batch Management, or PP in the Cloud.

Looking forward to learning, sharing, and connecting with many of you during this knowledge journey! Here is the curriculum I have prepared:

Week 1: Foundations of SAP PP

Day 1: Introduction to SAP PP

Overview of SAP PP and its role in ERP
Brief history and evolution of PP
Common industry applications

Day 2: Organizational Structure in SAP PP

Plants, Storage Locations, and Work Centers
Example scenarios with visuals
Best practices for structure optimization

Day 3: Master Data Essentials

Material Master
Bill of Materials (BOM)
Work Centers and Routings

Day 4: Detailed Exploration of Bill of Materials (BOM)

Types of BOM (Material, Equipment, Functional Location)
Practical example with screenshots

Day 5: Work Center Configuration and Management

Purpose and key configurations
Capacity planning integration

Day 6: Routings and Operations Management

Detailed explanation with screenshots
How routings influence scheduling

Day 7: Weekly Recap (Carousel Format)

Summarize week's learnings with visual highlights

Week 2: Core Processes and Planning

Day 8: Material Requirements Planning (MRP)

MRP concepts and types
Configuration basics
Visual example of MRP run

Day 9: MRP Live in SAP S/4HANA

Differences from traditional MRP
Performance improvements and use-cases

Day 10: Demand Management

Planned independent requirements (PIR) and customer independent requirements (CIR)
Demand strategies explained

Day 11: Capacity Planning in SAP PP

Capacity leveling techniques
Common challenges and solutions

Day 12: Production Order Creation and Management

Creating, releasing, and monitoring production orders
Practical tips for order management

Day 13: Discrete vs. Repetitive vs. Process Manufacturing

Key differences explained
Industry-specific use-cases

Day 14: Interactive Poll

Ask your audience about their biggest challenge in SAP PP

Week 3: Advanced Features & Integration

Day 15: PP Integration with Other SAP Modules

Integration with MM, SD, QM, CO
Practical examples and benefits

Day 16: SAP PP-PI (Production Planning for Process Industries)

Special features for pharma, chemicals, and food industries

Day 17: Variant Configuration in SAP PP

Benefits, challenges, and implementation steps

Day 18: Shop Floor Control and Execution

Overview of shop floor processes
Role of SAP PP in Industry 4.0

Day 19: Batch Management and Traceability

Importance of batches in quality control
Integration with SAP QM

Day 20: Reporting and Analytics in SAP PP

Standard reports and analytics
Custom report examples

Day 21: Case Study

Share a real-world success story (anonymized)

Week 4: Optimization & Practical Tips

Day 22: Performance Optimization in SAP PP

Common performance bottlenecks
Practical solutions

Day 23: Troubleshooting Common Issues

Real-life examples of frequent errors and fixes

Day 24: Best Practices for SAP PP Implementation

Checklist for successful PP implementations

Day 25: User Training and Adoption Strategies

Tips for user training programs

Day 26: SAP PP and Cloud Solutions

Using SAP PP with SAP S/4HANA Cloud
Benefits of cloud-based solutions

Day 27: Innovations and Future Trends

AI, IoT, and their impact on SAP PP

Day 28: Expert Tips and Tricks

Share lesser-known features or shortcuts

Week 5: Community Engagement & Wrap-Up

Day 29: FAQ Session (Interactive Post)

Answer top questions collected over the month

Day 30: Summary and Key Takeaways

Recap of series highlights
Invitation to continue conversation and collaboration

📅 Day 1/30 – Kickoff: What is SAP PP?🔧🏭📦

2025-05-05T10:30:42.886000+02:00

📌 What is SAP PP?
SAP PP (Production Planning) is a module designed to plan, schedule, and control manufacturing processes. It plays a critical role in ensuring materials and resources are available for production while aligning production with demand.

🚀 Whether you're in automotive, pharma, food, or discrete manufacturing, SAP PP helps businesses:
✅ Optimize production processes
✅ Reduce inventory costs
✅ Increase delivery reliability
✅ Align operations with business goals

🧱 Key Components include:

Material Master
Bill of Materials (BOM)
Work Centers & Routings
Production Orders
MRP (Material Requirements Planning)

🔍 In the next 30 days, I’ll walk you through core concepts, real-world use cases, advanced planning strategies, and tips from field experience 🚜🏗️

👂Let’s start a conversation!
What’s your experience with SAP PP? Are you currently using it in your projects? Drop your thoughts or questions below! 💬👇

GenAI was used to help generate this content

📅 Day 2/30 – Organizational Structure in SAP PP: The Blueprint Behind the Process

2025-05-06T13:15:56.851000+02:00

Before you plan production or run MRP, you need to build the framework that everything else relies on: the Organizational Structure in SAP PP.
This structure ensures that every material, machine, and movement happens in the right place, at the right time.

🔍 Key Elements of SAP PP Organizational Structure

🔹 Plant
The central unit for planning and execution — it can represent a factory, mill, or any production location.

🔹 Storage Location
Sub-divides the plant to help track where materials are stored — raw materials, finished goods, etc.

🔹 Work Center
Represents where operations are performed — machines, production lines, or even labor-based stations.

🔹 Routing
Defines how the product is made — the sequence of operations assigned to work centers.

🧩 How It All Connects

A product is manufactured in a Plant, using a Routing that defines tasks at different Work Centers, and the components come from Storage Locations.
The way you set this up impacts capacity planning, costing, inventory, and even reporting.

✅ Pro Tip:
Avoid future pain by standardizing your naming conventions across plants and work centers. It simplifies data maintenance and makes your reporting far more effective!

💬 How many plants or work centers are you managing in your current SAP landscape? What challenges have you faced in structuring them effectively?

📅 Day 3/30 – Master Data Essentials in SAP PP 🧩📚🏭

2025-05-07T10:37:50.938000+02:00

In SAP PP, master data is the foundation upon which all planning, execution, and control processes are built. Just like you can’t build a house without bricks, you can’t run efficient production without properly maintained master data! 🏗️💡

Here's a quick overview of the core master data objects in SAP PP:

🔹 📦 Material Master
The material master contains information on all the materials your company produces, procures, stores, or sells. It impacts everything — from production to purchasing and inventory.

🔹 📘 Bill of Materials (BOM)
The BOM is a structured list of components needed to manufacture a product. Think of it as a recipe for manufacturing — including materials, subassemblies, and quantities.

🔹 ⚙️ Work Centers
These represent the physical locations where production operations are performed (e.g. machines, assembly lines). Work centers include key data such as capacity, scheduling formulas, and cost centers.

🔹 📋 Routings
Routings define the sequence of operations required to produce a material. They are essential for planning lead times, capacity, and costing.

✅ Pro Tip:
Accurate and consistent master data is crucial for successful MRP runs, production orders, and cost calculations. Invest time in setting it up right — your downstream processes will thank you! 🔍✅

💬 Do you manage master data in SAP? What’s the most challenging part in your experience — BOM changes, routing accuracy, or material classification?

👇 Let me know in the comments!

📅 Day 4/30 – Understanding the Bill of Materials (BOM) in SAP PP📘🔩🛠️

2025-05-08T09:13:13.377000+02:00

Behind every successful product is a well-structured Bill of Materials (BOM) — the blueprint of production! 🏗️✨

In SAP PP, the BOM is an essential piece of master data that defines the components (materials, subassemblies, packaging, etc.) required to manufacture a finished product or semi-finished assembly.

🔍 Key Concepts of BOM in SAP PP:
🔹 Multi-level BOMs – Structure your production from raw material to finished product with hierarchical dependencies.
🔹 Alternative BOMs – Use when a product can be manufactured using different materials or methods.
🔹 Variant BOMs – Perfect for handling configurable products with multiple variations (think automotive or electronics).
🔹 Phantom Assemblies – For grouping components logically without creating actual production steps.
⚙️ Use Case Example:
Imagine you're manufacturing a bicycle 🚲:
The BOM would include the frame, wheels, handlebars, saddle, brake system, etc.
Each of these might also have its own sub-BOM (like spokes, tires, etc.).
💡 BOMs help ensure the right materials in the right quantities are available during production planning and MRP runs.

✅ Pro Tip:

Keep your BOMs version-controlled and collaborate closely with engineering teams to maintain accuracy across changes and releases! 🔧🗂️

💬 What’s your biggest BOM challenge — managing complexity, versioning, or integration with CAD/PLM systems? Let's exchange ideas in the comments!

📅 Day 5/30 – Work Centers in SAP PP: The Beating Heart of Production⚙️🏭💡

2025-05-09T18:20:20.650000+02:00

In SAP PP, Work Centers represent the physical or logical locations where operations are executed — machines, production lines, or even human labor stations. Without them, production is just a plan on paper!

What is a Work Center?
A Work Center contains all the data required to perform, schedule, and cost an operation, including:
🔹 Resource capacity
🔹 Available time
🔹 Cost center assignment
🔹 Activity types (e.g. machine time, labor time)
🔹 Formulas for scheduling and costing
🔹 Default control keys for how tasks should be processed

⚙️ Types of Work Centers
🛠️ Machine – For automated operations (CNC, injection molding, etc.)
👨‍🔧 Labor/Person – Human operators
🏭 Production Line – Flow-based manufacturing
📦 Storage/Packaging – End-of-line handling
📈 How It All Comes Together:
Work Centers are assigned to Routings, which define the operation steps in production. This enables:
✅ Capacity Planning
✅ Detailed Scheduling
✅ Accurate Costing
✅ Pro Tip:

Well-maintained Work Centers = better shop floor control, smoother MRP runs, and accurate production lead times! 🔄📊

💬 What types of Work Centers have you worked with most — manual or automated? Share your experiences below!👇

📅 Day 6/30 – Routings in SAP PP: Mapping the Path to Production

2025-05-12T17:46:01.263000+02:00

Once your materials are in place and Work Centers are defined, it’s time to organize the production steps — and that’s where Routings come in!

In SAP PP, Routings describe the sequence of operations required to manufacture a product. It’s the production navigation map that tells SAP how and where to make things.

🔍What Does a Routing Contain?

Each routing includes:

🔸Operation steps (e.g., cut, drill, assemble)

🔸Assigned Work Centers

🔸Standard values (e.g., setup time, processing time)

🔸Control keys (influences whether confirmation, printing, or costing is required)

🔸Inspection characteristics (optional integration with QM)

🧩 How Are Routings Used in SAP PP?

✅Basis for Production Order creation

✅Drives Scheduling and Capacity Planning

✅Supports Cost Estimation

✅Enables Process Optimization

Real-Life Example:

If you’re manufacturing a steel chair:

1️⃣Cut steel sheets

2️⃣Bend into shape

3️⃣Weld joints

4️⃣Paint

5️⃣Final assembly

Each of these is an operation in the Routing, with time, tools, and resources assigned.

✅Pro Tip:

Use Reference Operation Sets and Routing Groups to reduce duplication and standardize processes across similar materials. This is key in repetitive or discrete manufacturing!

💬Have you built or optimized Routings before? What’s your experience with managing variant-specific Routings or frequent process changes?

📅 Day 7/30 – Weekly Recap: SAP PP Week 1 Highlights!

2025-05-16T09:09:49.714000+02:00

What a week it's been! We've laid the foundation for a deep dive into SAP Production Planning (PP) with essential master data and core concepts. Here’s a quick recap if you missed any posts — or just want a refresher before we go deeper next week!

🧭 Day 1 – What is SAP PP?
The central module for managing manufacturing activities in SAP. It ensures your production processes are aligned with material availability, demand, and execution.

🏗️ Day 2 – Organizational Structure
We covered how Plant, Storage Location, Work Center, and Routing form the building blocks of a solid SAP PP framework.

📦 Day 3 – Master Data Essentials
An introduction to Material Master, BOM, Work Centers, and Routings — the critical records you need to keep production running smoothly.

🔩 Day 4 – Bill of Materials (BOM)
Think of it as the recipe for manufacturing — listing all components and quantities needed to make your product.

⚙️ Day 5 – Work Centers
Where production operations take place! Machines, people, or lines — each with capacity, cost, and scheduling info.

📋 Day 6 – Routings
The process blueprint! Defines the sequence of operations, work centers used, and estimated times.

✅ Next Week:
We’ll step into the world of MRP, Demand Management, Capacity Planning, and more!

Day 8/30 – Material Requirements Planning (MRP) in SAP PP

2025-06-13T10:15:33.130000+02:00

Time to step into the engine room of planning — MRP!
Material Requirements Planning is the core function that ensures you have the right materials, in the right quantity, at the right time — without overstocking or risking shortages.

🔍 What is MRP?
MRP analyzes demand (planned orders, sales orders, forecasts) and supply (stock, purchase orders, production orders) to create procurement or production proposals.

It answers:
➡️ What materials are needed?
➡️ How much is needed?
➡️ When is it needed?

⚙️ Types of MRP in SAP PP:
🔹 MRP Run (Classic MRP) – Transaction: MD01, MD02, MD03
🔹 MRP Live (S/4HANA) – Transaction: MD01N (real-time, in-memory)
🔹 Net Change vs. Regenerative Planning
🔹 Lot sizing, Safety stock, Procurement type — all play a role

🚀 What does MRP generate?

Planned Orders (for in-house production)
Purchase Requisitions (for external procurement)
Scheduling info for production and procurement
Exception messages (e.g. rescheduling alerts)

✅ Pro Tip:
Fine-tune MRP parameters in the Material Master (MRP1–MRP4 views). A small mistake in lot sizing or procurement type can ripple through your entire planning process!

Generated by AI with my custom prompt

💬 Have you transitioned to MRP Live yet? Or are you still running classic batch-based MRP? Drop your insights below!

#SAP #SAPPP #MRP #MaterialPlanning #ProductionPlanning #ERP #SAPS4HANA #MRPLive #SmartManufacturing #Manufacturing #DigitalTransformation #LinkedInSeries #SupplyChain #InventoryManagement

S/4HANA Intelligent Scenario Lifecycle Management (ISLM) and Situation Handling Scenarios: Part-1

2025-10-27T13:56:35.980000+01:00

In this blog, Part-1, I will be primarily focusing on SAP Intelligent Scenario Lifecycle Management (ISLM) through a Supply Chain use case - predicting the forecast delivery date by using regression based predictive model (SAP Standard ISLM Framework). This Model provides predictions based on historical data. I will also touch base on the SAP Situation Handling Scenario for the Stock Transfer Order Process. However, I will walk you through the set-up in more detail in Part-2 of this blog series.

My Business Use Case:

My organization has to transfer an Asset: 20000000 (Equipment: 10000001-Air Compressor 1250 CFM 8KG/CM2) from our Norco Plant in Louisiana to our Robinson Plant in Illinois. To support this process and predict the forecast delivery date based on historical stock transfers, we have activated the ISLM Scenario: MATERIAL_OVERDUE_SIT (Stock In Transit Material Overdue) and a Situation Handling Scenario: MAN_MATLOVERDUESITSITN (Stock Transport Order Overdue) to monitor exceptions as well.

Let us dive in...

What Is ISLM: Intelligent Scenario Lifecycle Management is a standardized framework to build and manage AI use cases within SAP S/4HANA for both embedded and side-by-side scenarios. It can be leveraged to perform lifecycle operations, including Scheduled Training and Retraining, and deployment of the model directly within SAP S/4HANA.

ISLM framework consists of two Fiori Applications, Intelligent Scenarios (App ID F4469) and Intelligent Scenario Management (App ID F4470). These two applications provide a unified interface for creating, deploying, monitoring, and activation of the model directly within SAP S/4HANA.

Based on the ISLM association with business application, the ISLM scenarios can be categorized as Embedded and Side-by-Side.

Embedded: A business application, for example SAP S/4HANA runs in the same stack as its machine learning provider with the analytics libraries SAP HANA Automated Predictive Library (APL) or SAP HANA Predictive Analysis Library (PAL).

Side-by-Side: A business application, for example SAP S/4HANA runs in a separate stack than its machine learning infrastructure provider.

To begin with, let us take a look at the architecture of SAP Intelligent Scenario Lifecycle Management.

Architecture of Intelligent Scenario Lifecycle Management

Business User: The user who Interacts with the business application and uses the predictions from machine learning for the business purpose.
Business Administrator: A domain expert who can perform model trainings based on business context, evaluate model quality , and activate a model for production usage.
Technical Administrator: A system administrator who can perform the configurations of connectivity between different entities and maintains the technical configurations of the system.
ABAP Developer: A developer who can create ABAP artifacts required for Intelligent Scenario registration.
Intelligent Scenario Owner: An owner who creates, reviews, and publishes the Intelligent Scenario.

For instance, based on our business use case, I will walk you through the standard ISLM scenario that leverages one of the models from SAP HANA Automated Predictive Library (APL) by stepping into the roles of "Business User", "Business Administrator", and "Intelligent Scenario Owner".

The Intelligent Scenarios App is used to create, display, and configure various scenarios tailored to specific business needs. Using this App, we can view a list and activate SAP provided standard scenarios or create Embedded or Side-by-Side scenarios.

Now, let us use the SAP provided ISLM scenario "MATERIAL_OVERDUE_SIT" and take a look at the input and out put fields used by the model, and Fiori App IDs that support the business process.

The Input fields are the data points to train an ML model and to make new prediction. They represent the historical business data and other relevant information that the ML model can learn from to identify the patterns.

Output fields contain the results generated by the ML model after it is trained. These output fields provide the predictions and related metrics back to the business application.

It`s time to publish the scenario...

After successfully publishing the ISLM scenario, let us move on to the "Intelligent Scenario Management" application to train the model and schedule it.

The Intelligent Scenario Management App is used to manage, monitor, and optimize AI driven scenarios throughout their entire lifecycle. We can view the list of App IDs relevant for the ISLM scenario MATERIAL_OVERDUE_SIT.

For instance, let us retrain the model with new historical data using new filtering conditions. The system generates a new Model Version ID for every "Retrain".

Following the successful training, the system provides a statistical information on variables and performance of the model. The model version report screen provides a summary about a particular model version. The quality information details varies according to the intelligent scenario type and underlying machine learning used.

For Instance, the following filter values are used for training the model.

The tab "Debrief" in a "Model Version Report" provides a breakdown of the trained machine learning model`s characteristics and its key influencing factors. The "Debrief" helps us understand and evaluate the model by explaining the main drivers behind its prediction.

Key Influencers and their percentage of contribution in the overall prediction.

We can schedule a training for our Intelligent Scenarios. When the schedule is created for a training, the system creates a planned task, which can be viewed in "Scheduled Planned Task" tab.

Mini Note: If we try to create a new schedule without deactivating the previous one, the system prompts an error message.

We can monitor the scheduled runs that are created via ISLM in the "Monitor Planned Task Jobs" tile.

We can copy and cancel the planned task and view the logs associated with each run of the schedule.

Now, let us move on to "Situation Handling Scenarios"...

As part of our business use case, I have activated the situation handling scenario with the following conditions: "MAN_MATLOVERDUESITSITN" to notify respective business team if the the order gets delayed.

Situation Handling Scenario: ZMAN_MATLOVERDUESITSITN conditions to trigger an exception message.

Situation Handling Conditions to trigger an exception notification...

Following the successful activation and training of ISLM and Situation Handling Scenarios, let us examine the transactional data.

Norco Plant asset/equipment master:

We have Asset Master and Equipment Master synchronization functionality in place.

Following the successful movement of equipment 10000001 from its functional location to Engineering Spares Warehouse, the system updates the stock in the designated storage location, which should be transferred to the Robinson Plant. The stock movement has been completed using a Maintenance Order.

Now, let us create a Stock Transfer Order using App ID F1957 - Transfer Stock Cross - Plant

With this App, we can make transfer postings from one plant(Issuing Plant) to another plant(Receiving Plant). This app supports warehouse clerk in finding the allowed transfer postings and in personalizing the control settings of storage locations and visible columns.

For instance, I have chosen the material code "271", which is designated for Equipment 10000001.

Mini Note: If the predictive analytics model is active, the system uses the predicted delivery date as forecast delivery date. We can also select the entry "Use Predictive Model for Forecast Delivery Date" in the application settings.

I have chosen the storage location 171B , which contains the stock of Equipment 10000001. I have entered the input values in the pop-up screen. The activated ISLM scenario model determines the "Forecast Delivery Date" for the stock transfer order based on the historical data.

Now, let us create "Stock Transport Order" using the option "Create Stock Transport Order".

Following the successful creation of stock transport order, using App ID F2139: Overdue Materials - Stock In Transit, we can view the "Predicted Deviation" values for the stock transport orders.

Using this App F2139 (Overdue Materials-Stock In Transit) with an Active Predictive Model:

If the predictive analytical model is active, the system uses the predicted delivery date as forecast delivery date.
If the predictive analytics model is active, we can select the "Predicted Deviation" field in the view settings for the results list.

Mini Note: The predicted deviation field displays the difference between the planned and the predicted delivery date. With this information about the predicted deviation, we get an impression that if a goods receipt can be successfully completed in time.

How to Interpret the predicted Deviation field value:

In our case, the predicted deviation for the STO 4500000334 is negative, i.e., -1 : This means that the forecast delivery date calculated by the predictive model is one day later than the planned delivery date from the purchase order.
If the predicted deviation is 0 (Zero) : This means that the forecast delivery date and the planned delivery date from the purchase order are the same.
If the predicted deviation is positive, for example 2 : This means that the forecast delivery date calculated by the predictive model is two days ahead of the planned delivery date from the purchase order.

Using this App F2139 (Overdue Materials-Stock In Transit) without an Active Predictive Model:

If the predictive analytics model is not active, we cannot select the "Predicted Deviation" field in the view settings for the results list.
If the predictive analytics model is not active, the micro chart uses the planned delivery date from the purchase order instead.
If the predictive analytics model is not active, the forecast delivery date and the planned delivery date of the purchase order are the same.

The shipping duration micro chart illustrates the goods movement process for an Stock Transfer Order item and shows the forecast delivery date in relation to the actual delivery date.

Since we have activated the "Situation Handling Scenario" with the conditions, the system triggers the exception notification when the stock in transit days are >1.

In our use case, the STO 4500000334 was delayed and met the conditions that are part of situation handling scenario; hence, the system triggered the exception notification.

The situations are displayed at "Bell Icon", which is a gate way to the SAP Fiori notification center.

or we can use "App ID: F4154 (My Situations app) " to monitor exception notifications.

Following the successful completion of the STO 4500000334, the situation can be closed using thee option "Close Situations" in My Situations App.

😊 This brings me to the end of a detailed walkthrough of the SAP Intelligent Scenario Lifecycle Management process , along with a high-level overview on how the situation handling scenario supports business teams in monitoring exceptions. I hope this blog proves useful to the Inventory Management team to have a nuanced understanding of material movements with enhanced predictive insights and exception notifications during Stock Transfer Order Process.

A detailed walkthrough of the SAP Situation Handling scenario process flow is covered in Part-2 of this blog series...use the link below to view it.

S/4HANA Intelligent Scenario Lifecycle Management (ISLM) and Situation Handling Scenarios: Part-2

Yours Sincerely,

Pardhasaradhi Reddy. C