It is very easy to create and manage standard XSteps (SXS) in the repository. However if you want to use the same function in different plants you have to maintain the SXS in every plant separately since the repository is plant dependent. You can export and import for an initial creation but then you have to do multiple maintenance in case of changes. Luckily there is an OSS pilot note available that fixes this problem.<\/p>\n
Installation Leading Plant When\u00a0you specify one of these objects in the new repository the system will look in the\u00a0leading plant to give you a choice. However you must make sure that these objects exist in every plant where you intend to use those cross-plant SXS. \u00a0There can be some slight variations though. For example a process message XYZ must have the same name and the same characteristics in every plant (because these are the elements you see in the repository) but the process message destination(s) could be different in every plant. It is very easy to create and manage standard XSteps (SXS) in the repository. However if you want to use the same function in different plants you have to maintain the SXS in every plant separately since the repository is plant dependent. You can export and import for an initial creation but then you have […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_links_to":"","_links_to_target":""},"categories":[16],"tags":[69],"_links":{"self":[{"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/posts\/704"}],"collection":[{"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/comments?post=704"}],"version-history":[{"count":16,"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/posts\/704\/revisions"}],"predecessor-version":[{"id":2165,"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/posts\/704\/revisions\/2165"}],"wp:attachment":[{"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/media?parent=704"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/categories?post=704"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/websha.de\/xstepcafe\/wp-json\/wp\/v2\/tags?post=704"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n<\/strong>
\nThe number of the pilot note is 1124677 and it depends on note 1101266 (included in SP1 of EhP3 or in later EhP’s). To be able to download the pilot note itself you have to create an OSS message and request this. Once you have activated these note you can use two new reports:<\/p>\n\n
\n<\/strong>
\nSince there are some plant-dependent objects when handling XSteps in the repository you need to specify which plant to use as the leading plant:<\/p>\n\n
\nUsage
\n<\/strong>
\nOnce you have installed the notes you have to use the cross-plant repository (using report RCMXXSR_CROSS_PLANT_REPOSITORY). In the recipe\/routing maintenance you will only find the cross-plant SXS now. However your old plant-specific SXS will still work. You can move your old content from the plant-specific repositories by using the folder export\/import functionality. It would also be a good idea to organize your new cross-plant repository in general folders and plant-specific folders.<\/p>\n","protected":false},"excerpt":{"rendered":"