Show TOC

  XStep Generation Locate this document in the navigation structure

Use

An XStep, which has been assigned a scope of generation, and its subordinated XSteps are used as a template for the XSteps that are to be generated. Using the scope of generation, you specify whether the system should copy the template automatically for the assigned scope during the generation.

Example

Information about the material components used should be available in the control recipe. These are created in the material list for the order. The associated XSteps can therefore be created automatically by the system and can be automatically enhanced with the data for the specific materials.

You define an XStep with the scope of generation For All Ingredients, which can be used as a template for the XSteps that are to be created. You maintain all required parameters for this XStep (for example, a parameter for the output of the material description) and the context in which the generation should be executed.

During the generation the system creates a copy of the template for each of the material components automatically and assigns values to the parameters with the data from the materials, which is contained within the material list.

This graphic is explained in the accompanying text.

This graphic is explained in the accompanying text.

See also: XSteps (Execution Steps)

Features

Execution of the XStep Generation

You can trigger the generation of XSteps in the following way:

  • When creating a control recipe:

    In this case, the system triggers the generation automatically. The XSteps that have been generated are inserted into the process order.

  • When processing the XSteps in the XStep Editor:

    If you want to check and, if necessary, change the generated XSteps before you create the control recipe, you can start the generation in the process order manually. By doing this, repeats and parameter valuations will be saved. That is, subsequent changes to the order data are no longer transferred to the XStep tree and the PI sheets. To update the data, you must execute function Generation -> Delete and repeat the generation.

System Activities During the Generation

During the generation the system executes the following activities:

  1. SXS references that have not yet been exploded are exploded.

    See also: Standard XSteps

  2. Templates are copied.

  3. Those parameters that are to be valuated automatically are assigned values.

Restrictions After Generation

As soon as the generation is executed, manual maintenance is restricted. That is, you can no longer maintain data that requires the XStep tree to be generated again. These restrictions are also valid when inserting new XSteps.

  • You can no longer change the XSteps that have a direct or indirect relationship to a generated control recipe destination.

  • You cannot insert any parameters that have to be valuated automatically or change any that already exist.You can however change the value of the parameter.

    See also: XStep Parameters

  • You cannot insert any new scopes of generation in the XStep tree. You can no longer change the contents of the templates. The template is inactive.

  • You cannot insert new SXS references in the XStep tree or change assignments to the standard XSteps.

  • You cannot change or delete the existing contexts.

System Activities After Deleting the Generation

As long as no productive control recipe exists for an XStep tree, you can delete the generation for an XStep tree. If you do this, the system carries out the following activities:

  1. All exploded SXS references are exploded.

  2. All copies are deleted.

  3. All valuations for the parameters that are assigned values manually are deleted.

    Caution Caution

    Note that some scopes of generation also set the context. If, for example, you have defined the scope of generation For All Phases for an XStep, then the system generates an XStep for every phase. Every XStep generated is automatically assigned the context of the particular phase. For example, the XStep for phase 10 would be assigned the context for phase 10.

    End of the caution.