Show TOC

  SXS References and Parameterization Locate this document in the navigation structure

Use

You can reference standard XSteps that you have created in the SXS repository in the following objects:

  • The master recipe

  • The process order

  • The standard routing

  • The production order

  • Another standard XStep

In the case of SXS references within another standard XStep, you can model nested standard XSteps in this way.

In the case of SXS references in the master recipe, standard routing, production order, and process order, you can parameterize the referenced standard XSteps in accordance with the relevant requirements in each case.

Example Example

The IT employee defines a standard XStep containing an input field with input validation. The system uses XStep parameters to ensure that the values for the upper and lower limits in the input validation remain value-neutral. The master data maintainer later uses this standard XStep in several master recipes. The master data maintainer assigns different values to the parameters for the upper and lower limits.

This graphic is explained in the accompanying text.

End of the example.

Features

XStep Parameter at the Standard XStep Interface

If a standard XStep version is Released or Released for Test, the system automatically copies all XStep parameters that are of type Input , Output , and Exchange that have been defined at the uppermost node in the XStep tree ( ) < XStep Tree > into the parameter interface of the standard XStep ( ) . Local XStep parameters remain unchanged. In the case of a standard XStep that has not been referenced, these XStep parameters cannot be seen at the node ( ) . The XStep parameters remain at the interface for the standard XStep, even if they are deleted again after they are released or if the version is no longer released. You should make no further changes to these XStep parameters. If, however, you need to make changes, then these changes must not change such things as the categories of the XStep parameters.

If the standard XStep is referenced, the XStep parameters at the uppermost node in the XStep tree are also copied to the interface of the SXS reference, and – in comparison to non-referenced XSteps – are visible at the node ( ) . These XStep parameters are also still visible in the XStep tree. You should, however, make no further changes to these.

Explosion of the SXS References

As soon as the SXS references in the process order, production order, routing, or master recipe are exploded, you can also specify further data (for example, specific fixed values) for the XStep parameters from the version, which is valid at that point in time.

In the case of SXS references within the SXS repository, fixed values for the XStep parameters are not displayed, because these can vary depending on the version. In this case, the XStep parameter is not regarded to have values assigned to it.

You can change XStep parameters in the subordinated XSteps of a standard XStep without restriction, as these are not transferred to the interface.

Where-Used List

You can perform a where-used function for referenced standard XSteps in the repository (see Standard XSteps ).

Export and Import of Standard XSteps with Reference Nodes

See Export and Import with Reference Nodes

Example

The following example describes how you can parameterize a standard XStep in a master recipe. You can also proceed accordingly in the standard routing. In the PI sheet, an input field for which input validation has been defined is to be outputted in the PI sheet. The input validation contains a minimum value in the form of an XStep parameter, which is derived from the total quantity in the master recipe, and a maximum value that you specify in the master recipe.

  1. You create a ( ) standard XStep in the SXS repository.

    The system automatically creates a ( ) version and an ( ) XStep tree for the standard XStep.

    See also: Create Standard XStep for PI Sheet

  2. You create the following XStep parameters for the XStep tree:

    ( )

  3. You assign values to the XStep parameters in the following way:

    ( )

    • Parameter LABEL should be automatically assigned values by the primary product in the master recipe.

    • Parameter MAX should be automatically assigned values by the total quantity in the master recipe.

    • Parameter MIN should be assigned fixed values in the master recipe.

    • Parameter VALUE is the parameter into which the entered value should be written.

      See also: XStep Parameter

  4. Assign a ( ) Destination to the XStep tree.

  5. You create a ( ) Process Instruction for the XStep tree.

  6. You create the XStep process instruction Input Parameter Value for parameter VALUE for the ( ) Process Instruction node. Create the following text “Create Quantity of &LABEL&” as a description.

    See also: XStep: Inputs

  7. You define input validation for the input field.

    1. To do this, double-click the process instruction and choose the Input Validation tab page.

    2. Specify the check type Formula and create the following calculation formula:

      X>MIN AND X<MAX

      See also: XStep: Input Validation in Input Fields

  8. Check and simulate the XStep tree.

  9. Release the SXS version, by selecting the version, Change Status and choosing Release .

    See also: Standard XSteps

  10. You create a master recipe with XSteps and switch to the XStep editor ( ) XSteps.

  11. You create an ( ) XStep tree .

  12. You create an SXS reference for the XStep tree, by selecting the XStep tree and then choosing Create and SXS Reference.

    The system creates a ( ) < New SXS Reference > node.

  13. In the properties dialog box from the ( ) < New SXS Reference >, choose the Reference tab page and create the standard XStep that you have defined before, by choosing it from the list of available standard XSteps.

  14. In the ( ) <New SXS Reference> properties window, choose the Valuation tab page. You can then see that the input parameters were transferred to the SXS reference interface.

  15. You explode the SXS reference by selecting XSteps -> References -> Explode

    After exploding the SXS reference, the system creates a copy of the version, which is valid for the key date and inserts this in your XStep tree.

    Note Note

    In general, you should explode the SXS references in the process order. Otherwise the standard XStep in the process order is not adjusted, if the standard XStep in the SXS repository was changed

    End of the note.

  16. You assign values to parameter MIN at the XStep node ( ) with a fixed value of your choice.

    After the explosion of the SXS reference and the generation, your XSteps in the master recipe will look like those shown in the diagram below:

    ( )

  17. You save the XSteps.

  18. Check and simulate the XSteps.