The process operator can process the PI sheet interactively. That is, the process operator is provided with the instructions for his work at the production line and he then enters data into the system accordingly, which is then further processed in the SAP system. This example relates to the PI sheets of the process industries. However, you can also use XSteps in shop floor control for work instructions, where you have the same options as described here for the PI sheet. In order to create process instructions for an XStep, you must first assign a destination type to the XStep or a specific control recipe destination.
|Published (Last):||27 August 2004|
|PDF File Size:||11.96 Mb|
|ePub File Size:||20.59 Mb|
|Price:||Free* [*Free Regsitration Required]|
Using XSteps you can describe the precise execution of production processes and can group and structure this information in the form of modules. XSteps can be structured in hierarchical form. These form XStep trees.
The production steps described in XSteps are grouped for each control recipe and sent to the production execution level. Production can then be executed either manually or automatically. In the case of manual production, the system creates interactive PI sheets, which are then processed by process operators on the production line. In the case of automatic production, the production steps are executed by a process control system.
To ensure that you can maintain XSteps in the master recipe, you must create a recipe profile when creating the recipe group. As default, it is only possible to generate an XStep tree in a process order once the order in question has been saved. You can also set that an XStep tree is generated, even if it has not yet been saved.
XStep parameters are central elements of XSteps. You use XStep parameters to model your data for an XStep module. The parameters describe the contents of the XStep module and are valid for one XStep module only.
The data exchange between the XStep modules is also controlled using the parameter definitions. It is therefore possible to use identical variable names or inspection formulas in different XSteps within an XStep tree without conflict. Automatic valuations and generations are executed on the basis of XStep parameters. For more information, see XStep Parameters. Application-specific XSteps. You define XSteps directly in an application, for example in a master recipe or process order.
They generally contain data that is related to the particular application. These XSteps are generally implemented immediately. For more information, see XStep. Application-independent Standard XSteps. If a version is correct and has been tested, you can release it for production. If an application has created a reference to a standard XStep SXS reference and this has been exploded, the system copies a valid version of the referenced standard XStep to the application.
The originals in the standard XStep repository remain unchanged. For more information, see Standard XSteps. XStep Process Instructions. Using XSteps, you define process instructions independent of the phases of a process order and master recipe. In doing so, you must specify for which destination type or precise destination the XStep process instructions should be created.
For more information, see XStep Process Instructions. Application-specific XSteps You define XSteps directly in an application, for example in a master recipe or process order. XStep Process Instructions Using XSteps, you define process instructions independent of the phases of a process order and master recipe.
Create and Test a Basic Xstep in Standard Xstep Repository
If you have selected a master recipe during order creation that contains XSteps, then you can process the transferred XSteps in the XStep editor. See also: XSteps Execution Steps. If a master recipe has been selected that contains characteristic-based process instructions, edit this in the process instruction overview. As default, it is only possible to generate an XStep tree in a process order once the order in question has been saved. You can also set that an XStep tree is generated, even if it has not yet been saved.
Directly dependent business function that you must additionally activate. This business function enables you to use execution steps XSteps that you previously used only in production planning for process industries in discrete manufacturing as well. Execution steps are modules that you can use to describe the individual steps in production. In production plants in discrete industries parts manufacturing and assembly industries it is very often necessary to achieve a timely and close exchange of manufacturing-relevant data between an ERP system and the independent level of the manufacturing process machines, individuals, manufacturing control station, machine control computer, etc. For a production order to be executed at this level and controlled, settled, and also changed in the ERP system, data such as product data, input materials, standard manufacturing and setup times, setting parameters, recipe data, and target quantities must be passed on by the planning level in the ERP system and data such as the quantities actually produced, actual manufacturing times, scrap quantities, and possibly much more data reported to the ERP system as promptly as possible.