XSteps (Execution Steps) Configuration for two different destinations (external system)
A structure for describing the precise execution of production operations. We can regulate the data interaction with the process control level and generate interactive work instructions/PI sheets for process operators and production workers using XSteps. A master recipe, process order, standard routing, or production order can all be allocated an XStep.
- Advantages of using Xstep
- Perfect building blocks for standardized procedures in production sites all over the globe.
- XML export and import of complete XStep repositories and SXS elements.
- Usage of XSteps in Process orders and Master Recipe.
- No PI Sheet simulation capabilities in process orders that use classical process instructions.
- XStep allows multiple usages of phase context in combination with multiple control recipe destinations.
- Xsteps is easy to maintain and lead time to change or maintain the Xsteps.
An XStep tree is made up of one or more XSteps. It may also include XStep process instructions and references to standard XSteps (SXS reference). In an XStep tree, an XStep can be composed of other XSteps, SXS references, and XStep process instructions.
We can create the following components within an XStep tree.
An XStep can have additional subordinated XSteps. Higher-level XStep properties such as scope of generation, control instruction/control recipe destinations, and application context are inherited by subordinate XSteps if they have not been expressly allocated any of these values individually. If, for example, the application context Order is defined in the super ordinate XStep, it is valid for all subordinate XSteps until the next XStep for which a different context is established.
- SXS References
An XStep or a standard XStep can refer to variations of a standard XStep that are kept in the SXS repository. When a SXS reference is created, the system first establishes a loose link to the referenced standard XStep. The system produces a duplicate of the valid version of the standard XStep in your XStep tree for the key date after the references are exploded.
- XStep Process Instructions
All functions that were available with the conventional process instructions are still available. It is no longer necessary to be familiar with the syntax of the process instruction characteristics while maintaining objects in the XStep editor. Instead, we may use the context menu to easily establish output and input fields, as well as control tasks like function calls and process messages.
- Objective/Case Study
Previously, the User had one external system (SAP MII) and they used to send all the information to the external system (SAP MII) through “Xsteps” for execution purposes. Recently, they have introduced/implemented a new external system for barcode printing. From now onwards need to send all information for both the system as well. So, need to configure a new Xstep under the master recipe for barcode printing system.
- Assigning XSteps to MII Master Recipes
The below steps describe how to add the xsteps necessary for the operation/phase execution (destination D1/Q1/P1). Needed on all Finished Goods.
Finally, we need the xsteps to drive the Barcode Printer Integration on all Finished. (Destination D3/Q3/P3).
Here is what the setup should look like for each type:
- Operation/Phase and Barcode Printer Needed (all finished goods):
- Detailed Instructions for Barcode Printer (P3 Destination):
Goto tr. C202 put the recipe and change number to assign XSteps and enter.
Click on the xstep icon.
The Xstep page will be opened and click on Xstep tree.
Double-click on xstep tree icon and a pop-up window will be displayed, select the “Destination” tab.
Expand “External systems” and double click “Kitchen – MES” – P3, please wait until that appears in the Current Assignment box. And Close the popup by clicking “x”.
Right-click on the xstep tree icon and click “SXS Reference”. SXS Reference will be created.
Double-click on the “New SXS Reference” and a pop-up will be displayed. Select the “context” tab.
Double-click on the header, and wait until the assignment is copied in the Current assignment box.
Select the “Reference tab” from the pop-up window. Drill down through the folder until you get the “All Phases” reference xstep. Double-click “All Phases” and wait until it appears on the current assignment box.
Select the “General” tab from the popup. Mention “All Phases” in the description box. And close the popup by clicking “x”.
Right-click on the xstep tree icon and click “SXS Reference” and a popup will be displayed. Select the “Context” tab.
Double-click on the “Good Receipt”, and wait until the assignment is copied in the Current assignment box.
Select the “Reference tab” from the pop-up window. Drill down through the folder until you get the “GR Phase” reference xstep. Double-click “GR Phase” and wait until it appears on the current assignment box.
Important Note: for destination D1/Q1P1 we specify the Bottleneck Phase. But for the Barcode Printer Integration (Destination D3/Q3/P3) it is the GR Phase that is called out. Make sure to choose the correct item and link it to the correct phase. This is how MII knows which phase to use for Goods Receipt or the Bottleneck Phase Confirmation.
Select the “General” tab from the popup. Mention “GR Phase” on the description box. And close the popup by clicking “x”.
Also, need to add another “SXS Reference” by right click on the xstep tree icon and clicking “SXS Reference” and a popup will be displayed. Select the “Reference” tab.
Double-click on the “Bottleneck Phase”, and wait until the assignment is copied in the Current assignment box.
Right click the xstep tree and click on “check”. “No errors were found” will be displayed in the information bar.
Xstep structure should look like this for all Kitchen-MES lines.
Save Master recipe.
After the above Xsteps configuration, able to send all the required information to both external systems.