Product Information
How To Copy SAP DMC POD Across Tenants, Plants
It takes lot of effort and insights to build a Production Operator Dashboard (POD) in SAP Digital Manufacturing Cloud (SAP DMC) and a lot of thoughts and inputs contribute to shape it. Many a times there are configurations and customizations that evolve over time and make way into POD. There are use cases where you have configured nice SAP DMC POD and would like to make use of it in different plants or tenants. Essentially you need to copy SAP DMC POD across plants in in the same or different tenants. While you can copy POD within the same tenant/plant using copy functionality in the POD Designer, there is no UI based method to copy SAP DMC POD across tenant/plant.
All is not lost, and help is there to copy SAP DMC POD in the above scenario. In SAP DMC, there is a released API to achieve above objective. You can have more details at public API reference here:
https://api.sap.com/api/sapdme_pod/resource
POD copying using above API is a two step process:
- In the first step you export the chosen POD from the tenant where it already exists. It is essentially downloading the already created POD.
- In the second step you can import the downloaded POD into the target tenant/plant combo.
To Export
Send a GET request to the following endpoint. Be sure to replace the parameters with whatever is correct for your system.
- {{gateway-ms}}/pod/v1/export?plant={{Plant}}&podId={POD_NAME_HERE}
In Postman when sending the request use the arrow symbol next to the send button and select “Send and Download”. See the screenshot below. Then enter the name and location of the pod configuration file you are exporting.
To Import
Send a POST request to the following endpoint. Be sure to replace the parameters with whatever is correct for your system.
- {{gateway-ms}}/pod/v1/import
The Body Form Data Parameters are as follows. In postman on the Body Tab set it to form-data and enter the following.
|
Key |
Type |
Value |
|
file |
File – You have to set this manually in postman. It defaults to “Text”. |
The location and name of the pod configuration file being imported. |
|
plant |
Text |
The name of the plant you want to import the pod to. |
|
podId |
Text |
The name of the pod after import. |
|
podDescription |
Text |
The description of the pod after import. |
Summary
As is clear, even the best of best products need enhancements, enrichments, upgrades to keep up with technology and ever changing customer requirements. In that context, I would welcome all the feedback, thoughts, comments, suggestions on product improvements/ new features from our esteemed readers, customer, partners, colleagues on this blog post of DMC, LM, OAT and related offerings.
I also would request and encourage you to follow tags and my profile to be first one to know about latest and greatest on my blogpost on DMC, OAT, LM and related offerings.
You can also look at QnA in following communities and ask questions as well. Also don’t forget to include tags of DMC, OAT, Overlay Authoring Tool, LM, and Line Monitor in your question(s). I would also encourage you to follow the tag (and/or me), so you receive notifications with upcoming content of mine and other community members:
SAP Digital Manufacturing Cloud
SAP Digital Manufacturing Cloud Insights
Again, thanks for reading this blog post and posting all the feedbacks, thoughts, comments, suggestions on product improvements/ new features.
Thank you! It is very useful
I only have a few questions:
I was able to run other APIs, but it didn't work for POD. Manoj Mishra, please share the secret of how it works for you?
BR
Hello Ruslan,
You should be able to do it using postman. Keep in mind that you should have access (and required tokens/authentications) of the source and target tenants to perform this.
TBR, Manoj