Execution Steps (Xsteps) : PDF Download From SAP Help Portal: Created On September 30, 2013

EXECUTION STEPS (XSTEPS)
PDF download from SAP Help Portal: http://help.sap.com/erp2005_ehp_04/helpdata/en/7e/4cdd3e6ecb1f39e10000000a114084/content.htm Created on September 30, 2013
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.
Note This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.
2013 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see www.sap.com/corporateen/legal/copyright/index.epx#trademark for additional trademark information and notices.
PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.
Page 1 of 41
Execution Steps (XSteps)

Use
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. You can use XSteps in the process industries and in shop floor control. For more information on XSteps in manufacturing, see XSteps in Shop Floor Control. The production steps described in XSteps are grouped to form control instructions/recipes and sent to the production level. Production can then be executed either manually or automatically. In the case of manual production, the system generates interactive PI sheets/work instructions, which are then processed by the line or machine operator. In the case of automatic production, the production steps are executed by a process control system.
Prerequisites
Maintenance of XSteps in the Master Recipe To ensure that you can maintain XSteps in the master recipe, you must create a recipe profile when creating the recipe group. In the standard system supplied, the new recipe profile PI01_XS: Profile for Process Industry XSteps is available for the maintenance of XSteps. Go to Customizing for the Master Recipe and choose Settings for the Task List Type -> Define Profiles with Default Values . No profile is necessary for the maintenance of XSteps in the routing. Early Assignment of Order Number In the standard system, it is not possible to generate an XStep tree in a process order or production order unless the relevant order has already been saved. You can also set that an XStep tree is generated, even if it has not yet been saved. To do this, go to Customizing for Process Management and choose Execution Steps (XSteps) -> Set Early Assignment of Order Number.
Features
XStep Parameters 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 the master recipe, routing, production order 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 You define standard XSteps as master data in the standard XStep repository (SXS repository). You can maintain the standard XSteps in the SXS repository using versions. 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 With the aid of XSteps, you define process instructions independently of the phases of a process order or planning recipe and independently of the operations of a routing or production order. You create XStep process instructions for an XStep or standard XStep. In doing so, you must specify the destination type or concrete destination for which the XStep process instructions are to be created. For more information, see XStep Process Instructions.
XStep
Definition
A structure that you can use to describe the precise execution of production processes. Using XSteps you can control the data exchange with the process control level or generate interactive work instructions/PI sheets for process operators and production workers. An XStep can be assigned to a master recipe, process order, standard routing, or production order.
Structure
Page 2 of 41
An XStep tree consists of one or more XSteps. It can also contain XStep process instructions and references to standard XSteps (SXS reference). An XStep in an XStep tree can also be made up of further XSteps, SXS references and XStep process instructions. You can create the following components within an XStep tree.
XSteps An XStep can contain further subordinated XSteps. Properties of the higher-level XSteps, such as scope of generation, control instruction/control recipe destinations and application context are inherited by the subordinate XSteps, as long as they have not been explicitly assigned any of these values separately. If, for example, you have defined the application context Order in the superordinate XStep, this application context is valid for all subordinate XSteps until the next XStep for which a different context is defined. SXS References An XStep or a standard XStep can be referenced to versions of a standard XStep, which are maintained in the SXS repository. When creating an SXS reference, the system firstly creates a loose connection to the referenced standard XStep. Once the references are exploded, the system creates a copy of the valid version of the standard XStep in your XStep tree for the key date. See also: Standard
XSteps
XStep Process Instructions All functions that were available with the conventional process instructions are still available. When maintaining objects in the XStep editor, you no longer have to be familiar with the syntax of the process instruction characteristics. Instead, you can easily create output and input fields, as well as control functions such as function calls and process messages using the context menu. See also: XStep
Process Instructions
XStep Properties You can define specific properties for each XStep:
General Information In this dialog window, you find information about the status of the control instructions or the control recipe and administrative data about the last person to make a change and so on. Parameters and Parameter Valuations In this dialog box you create the XStep parameters and their valuations for the XStep. See also: XStep
Parameter
Scope of Generation In this dialog box you assign a scope of generation to the XStep. See also: XStep Receiver In this dialog box, you assign either a destination type (external system or PI sheet) or a concrete control instruction/recipe destination to the XStep. The destination is valid for the entire XStep tree until a new destination is found. The inheritance hierarchy then starts again from this position in the tree. Application Context In this dialog box you specify whether the XStep should be valid for a particular phase, a certain operation, or for the entire order. The system requires the XStep context during the generation and the automatic valuation. As is the case with the destination, the context is valid for the entire XStep tree until a new context is found. The inheritance hierarchy then starts again from this position in the tree.
Generation
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 creates a copy of this XStep for every phase. Every XStep copied is automatically assigned the context of the particular phase. For example, the XStep for phase 10 would be assigned the context for phase 10.
Page 3 of 41
XStep Parameters
Use
You use XStep parameters to model your data for an XStep module. The XStep parameters describe the contents of the XStep module and are valid for one XStep module only. XStep parameters also form the interface between the different XStep modules of an XStep tree and allow data to be exchanged between them. XStep parameters are therefore used as placeholders for the contents of XSteps, whose values are determined at a later point in time, or can be changed during processing. You can use XStep parameters in the following way:
As a Variable For certain contents, for example, material numbers or material descriptions, you can define XStep parameters, which you can later use as a variable within the same XStep tree. The following contains several examples of XStep parameters being used in this way:
To output individual parts of a long text: Because you can define valuation symbols for XStep parameters, it is possible to replace individual parts of a long text. You define, for example, the long text Add &PARAM1& Kg of material &PARAM2& and set the XStep parameters PARAM1 and PARAM2 as placeholders for the quantity and the material. To output default values for input fields See also: XStep: Suggested Values in Input Fields As single variables in calculation and inspection formulas, for example, for the upper and lower limit values in an inspection formula See also: XStep Calculations For assigning values to the XStep parameters of a function module in the case of dynamic function calls See also: XStep: Dynamic Function Calls XStep: Function Module Parameters To output descriptions for input or output fields See also: XStep: Outputs XStep: Inputs
To Allow the Exchange of Data Between XSteps Within an XStep Tree To transfer data between XSteps in an XStep tree, you must define reference parameters. For example, an XStep parameter at an XStep, which is located lower in the hierarchy, can be assigned the value from a higher-level XStep. Or, the XStep parameter of a higher-level XStep can be assigned the same value as a subordinated XStep (see Input and Output Parameters ). Parallel Processing of Standard XStep References You can create references to standard XSteps in the SXS repository from the master recipe or the process order. In the application, you can assign specific values to the XStep parameters at the SXS reference interface, to meet the requirements of the particular master recipe or process order. See also: SXS References
and Parameterization
Features
The data exchange is only possible between XSteps within the same XStep tree. Every XStep within an XStep tree is independent of the others, in terms of their contents. As a result of this, it is possible to use identical parameter names in different XSteps within an XStep tree without conflict.
Define XStep parameters, which should facilitate the data exchange with other XSteps within the same XStep tree, as input, output, or exchange parameters. The system writes these parameters at the parameter interface of the XSteps. You define XStep parameters, which are to be used within the same XStep or are to be transferred to the XStep located immediately below in the hierarchy, as local parameters.
Data can only be exchanged directly between a higher-level XStep and the subordinated XSteps immediately below it. If you want to transfer data between two XSteps that are located at the same level within the hierarchy, you must firstly transfer the parameter value to a local parameter of the higher-level XStep, which can then be read by an input parameter of the subordinated XStep (see diagram). Parameter Interface and Data Flow between XSteps
Definition of XStep Parameters You define an XStep parameter for the contents of every XStep. Content values can be specified or used at a later point in time. The XStep parameters are only valid for the XStep in which they were defined. That is, they are not valid for subordinated XSteps. If the values for this XStep parameter are used in a subordinated XStep, you must transfer them using references. If you want to create XStep parameters for an XStep, double-click the XStep node and maintain the tab pages Parameters and Valuation. Tab Page Parameters
Page 4 of 41
On the Parameters tab page, create the parameter names, a description, a category and a characteristic.
Category
For every XStep parameter, you must specify whether it should: Be assigned a parameter value from the higher-level XStep (category Input ) Transfer its own value to an XStep parameter in the higher-level XStep (category Output ) Be used within the same XStep, or its value be transferred to the subordinated XStep (category Local)
Category Input You define an XStep parameter with category Input, if you want to assign a value from a higher-level XStep to this XStep parameter.
In this example, the value of the XStep parameter E should be created in the PI sheet in the higher-level XStep 1 and be displayed again in the subordinated XStep 1a. The transfer of the value from E to the subordinated XStep 1a is done using the input parameter X, which is assigned values from the reference with local parameter E. Value Permitted Categories for Parameter Use in Process Instructions References
You can assign values to input parameters in the following ways: Automatically With a fixed value With a reference parameter Not at all
Input parameters of a subordinated XStep can be referenced with the XStep parameters of a higher-level XStep, which are of the following categories:
Input Local
Input parameters can output in the process instruction. To do this, define a process instruction of type Output -> Parameter Value.
Category Output You define an XStep parameter with category Output, if you want to transfer the value of this XStep parameter to the higher-level XStep, which is located directly above the XStep in the hierarchy.
In this example, the value of the XStep parameter X should be created in the PI sheet in the subordinated XStep and be displayed again in the higher-level XStep. The transfer of the value from X to the higher-level XStep is done using the output parameter X, which is assigned values from the reference with local parameter E. Value Permitted Categories for Parameter Use in Process Instructions References You can assign values to output parameters in the following ways:
With a reference parameter Not at all
Output parameters of a subordinated XStep can be referenced with the XStep parameters of a higher-level XStep, which are of the following categories:
Output Local
You can create output parameters in the process instruction. To do this, define a process instruction of type Input -> Parameter Value.
Page 5 of 41
Exchange This category is a combination of Input and Output. The XStep parameter should be assigned a value and this should then be transferred. Local You define an XStep parameter of category Local, if:
The value of an XStep parameter should be used as a variable within an XStep, for example, as a suggested value. The value of the XStep parameter should be transferred to an input parameter in the subordinated XStep The XStep parameter should be assigned values using the value of an output parameter in the subordinated XStep. Value Use in Process Instructions You can assign values to local parameters in the following ways:
Automatically Fixed Not at all
You can use local parameters in the process instruction in the following ways:
As input, if the XStep parameter has not been assigned values As output, if the XStep parameter has been assigned fixed values, or been assigned values automatically.
Characteristic You must assign a characteristic to every XStep parameter. The characteristic only specifies the data type of the XStep parameter. It can therefore be used several times. Note, that some business characteristics (for example, PPPI_MATERIAL or PPPI_BATCH) contain suggested input values and input validation. In the PI sheet, input fields which have been assigned such characteristics as data type, can only be filled with a value which is appropriate in that particular business context.
Tab Page Valuation
On the Valuation tab page, enter a valuation type for each XStep parameter and create a value and valuation symbol if required.
Depending on the chosen category, you can value XStep parameters in the following way:
None The XStep parameter should either be used at a later point in the PI sheet, or not at all. Automatically The value of the XStep parameter should be determined automatically by the system on creation of the control recipe. You must specify a valuation symbol. The application context replaces the valuation symbols with specific values depending on the application context. The number of the header material in an order can, for example, be assigned automatically. Fixed Value You define a fixed value to meet your requirements. In addition you can also define a valuation symbol. This is only appropriate, if you want to automatically assign a material description to the corresponding material in the PI sheet, for example. Reference In this case, you assign the value of one XStep parameter to another XStep parameter. In doing so, you can only use a reference to XStep parameters that you have previously defined in the higher-level XStep. You specify an XStep parameter as a valuation from the higher-level XStep, whose value should be transferred to the current XStep parameter. When doing this, you must ensure that the categories of the two XStep parameters match. For example, an XStep parameter of category Input cannot be referenced with an XStep parameter of category Output (see category Permitted Categories for Parameter References )
Note the following when working with reference parameters: The referenced XStep parameter must have been previously defined in the higher-level XStep. The characteristics of the XStep parameter in the higher-level and subordinated XStep must be the same. At the XStep tree node, you cannot assign values to the XStep parameter with valuation type Reference.
Page 6 of 41
Permitted Valuation Types for Categories Only certain valuation types are permitted depending upon which categories you have defined for an XStep parameter. The following diagram gives an overview of the permitted combinations.
Permitted Categories for Parameter References If you have defined an XStep parameter, which is to be assigned values using a reference to a different XStep parameter, then the XStep parameter categories of the higher-level XStep and the subordinated XStep must match. The following diagram gives an overview of the permitted combinations.
Live Parameters You use assign values using a live parameter, if you want to transfer data between two different PI sheets. In this case, you must set the Live Parameter indicator at the XStep parameter for both XSteps. The data exchange is done automatically using Manufacturing Data Access
Note that parameters for tabular values cannot be defined as live parameters. For further information on tabular values, see XStep Parameters for Tabular Values.
XStep Parameters for Tabular Values

Use
If you want to reuse values from a table (repeated data requests) using XStep parameters, you must set the Table indicator in the parameter definition on the Parameter tab page. This XStep parameter is then valid for all values in a table column. XStep parameters for tabular values can be:
Transferred to function modules, which can then process table parameters Output in a different table in the PI sheet
Using XStep parameters for tabular values, you can also transfer the following values using the parameter enhancement:
Only the single row value of a table column In this case, you insert the supplement [1], [2], [3] and so on, after the parameter name for each table row, for example, PARAM1[1], PARAM1[2], PARAM1[3]. The sum of all the row values that are contained in the table column In this case, you insert the supplement [SUM] after the parameter name, for example, PARAM1[SUM]. The number of row values that are contained in the table column In this case, you insert the supplement [COUNT] after the parameter name, for example, PARAM1[COUNT].
Example
PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved. Page 7 of 41
You have defined a table with three rows in an XStep. The rows contain material quantities amongst other things. In the subordinated XStep you want to calculate the average quantity of the material quantities that are contained in the table. Proceed in the following way:
You define the XStep parameter TAB1 with category Local in the higher-level XStep and set the Table indicator. You define XStep parameter TAB2 in the subordinated XStep. You assign category Input and value assignment type Reference to TAB2 and set the Table indicator. You assign values to XStep parameter TAB2 using a reference to TAB1. Using a calculation formula you can calculate the average value using the parameter enhancements [SUM] and [COUNT]. You can output the calculated value in the PI sheet. You must define the corresponding process instructions. See also: XStep
Process Instructions for PI Sheets
XStep Generation
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.
Page 8 of 41
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.
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
Page 9 of 41
the particular phase. For example, the XStep for phase 10 would be assigned the context for phase 10.
XStep Process Instructions

Use
In XStep process instructions, you define the concrete content of an XStep (for example, which data is to be displayed and entered in the PI sheet/work instructions). You can confirm the processing of the actual data using process messages. You create XStep process instructions for an XStep or standard XStep. For more information, see Execution Steps (XSteps).
Features
XStep Process Instructions for PI Sheets You define XStep process instructions, which should be processed by the line or machine operator, for the destination type PI Sheet. These XStep process instructions are created automatically as universal process instructions. Via the context menu, you can store different pieces of information in the PI sheet without having to know the syntax of the characteristics. For more information, see XStep Process Instructions for PI Sheets.
XStep Process Instructions for PI Sheets

Use
XStep process instructions for destination type PI Sheet are displayed as browser-based PI sheets in the SAP system. 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.
Prerequisites
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.
Features
Using XStep process instructions you can store the following contents and functions in the PI sheet:
Output You can output information such as long texts, numerical values and images in the PI sheet. For more information, see XStep: Outputs. Input Using the input fields, you can request production-relevant data, that the process operator should create in the PI sheet. For example, values and signatures can be created in the PI sheet. For more information, see XStep: Inputs. Depending upon the data type, you can also define the following functions for input fields:
Suggested Value See: XStep: Suggested Values in Input Fields Input Validation See: XStep: Input Validations in Input Fields Error Handling
Control Functions With the aid of control functions, you can enter confirmations and perform calculations for example. The following functions can be defined in the PI sheet:
Calculations See: XStep Calculations Manufacturing Data Access See: XStep: Manufacturing Data Access
Page 10 of 41
Automatic Entries See: XStep Automatic Value Assignment Tables See: Tables Function Calls See: XStep: Dynamic Function Calls Process Messages See: Process Messages Commands See: XStep: Functions that can be Executed Automatically
Data Format
A value is suggested, as standard, for the majority of XStep process instructions, which determines the data format of the value. If you want to use a different format, you have to choose a different characteristic from the input help, or create a new characteristic. You can create your own characteristics in Customizing for production planning process industries under Process Instructions Process Instruction Characteristics Define Characteristics for Process Instructions.
Layout in the PI Sheet
The SAP standard layout is defined in such a way that all input and output fields, with the exception of long texts, are displayed on the right side of the PI sheet. If you have defined input and output fields as well as long texts, the long text will be displayed on the left of the PI sheet. In parallel, the input and output fields will also be displayed at the same level.
Layout Definition for the PI Sheets
If you want to change the standard layout of the PI sheet, or you want to define it yourself, you must choose characteristic PPPI_LAYOUT, as is the case with characteristic-based process instructions. To do this, proceed as follows: 1. Double-click node and choose the tab page Characteristics. 2. Create the characteristic PPPI_LAYOUT in the characteristic overview. It must be in first position in the characteristics list. 3. Go to the Long Text Editor and create your XML definition. For more information, see Layout Definition for PI Sheets and Cockpits.
Activities
The following example illustrates how you can create an XStep process instruction: 1. Select a new XStep node and choose Create Process Instruction. The system creates the entry <New Process Instruction> below the selected XStep node. 2. Select <New Process Instruction> and choose Create Output Long Text. The system creates the entry <Grouping> with the subnode <Long Text> below the <New Process Instruction> node. 3. Double-click the <Long Text> icon. The Values Output dialog box appears. 4. In the dialog box Value Output enter a description and a long text.
Page 11 of 41
XStep: Outputs
Use
Using XStep process instructions, you can display varied information in the PI sheet. For example, you can store notes in the form of long texts to ensure that certain regulations are observed, or create internet and intranet links.
Prerequisites
If you work with output objects that use XStep parameters, you must have previously defined these parameters in the higher-level XStep of the same tree.
Features
Output Functions in the PI Sheet Output of Character String The data format of characteristic PPPI_SHORT_TEXT is proposed as a default. In this case, you can output a description and a 30 character alphanumerical value of your choice.
Output of Date The data format of characteristic PPPI_ EVENT_DATE is proposed as a default. In this case, you can output a description and a date in format DD.MM.JJJJ.
Output of Numerical Value The data format of PPPI_PARAMETER_VALUE is proposed as a default. In this case you can output a numerical value with 10 places before and 3 places after the decimal point. You can also display a unit of measure, in addition to a numerical value. If you output the unit of measure as a character string with the characteristic PPPI_UNIT_OF_MEASURE then the unit of measure is displayed to the right of the output field.
Page 12 of 41
Output of Long Text When using this function, several functions are available which allow you to format the long text. You can store any long text you require in the SAPScript Editor. The long text is displayed in the left half of the PI sheet. If you also want to format your long text using HTML fragments, you must choose the characteristic PPPI_FRAGMENT_ HTML (HTML fragment).
You can use this characteristic to integrate any HTML source code. Note that this HTML source code can represent a security risk. A security warning applies in particular to the HTML tag <IMG> for integrating or referencing images: JPG, GIF, BMP). This <IMG> makes it possible to load images with harmful source code or integrate or reference any other objects that might contain harmful source code. For this reason, make sure that the integrated or referenced files are free of viruses. Choose SAP SCM Implementation Guide (IMG) SAP Web Application Server System Administration Virus Scan Interface to check the files you wish to upload for viruses.
Output of Time The data format of PPPI_EVENT_TIME is proposed as a default. In this case, you can enter a description and a time in format HH.MM.SS.
Output of Hyperlink You enter the address of the internet or intranet page that you want to link to, for example http://help.sap.com (SAP Help Portal). The link is displayed in the left half of the PI sheet. The following characteristics are available for the definition of a hyperlink:
Characteristic name PPPI_HYPERLINK PPPI_HYPERLINK_ASCII PPPI_HYPERLINK_HTML PPPI_HYPERLINK_XML
Description Hyperlink Hyperlink to an ASCII document Hyperlink to an HTML document Hyperlink to an XML document
Because the target of the hyperlink can be external, hyperlinks represent a security risk.
If you are using the standard XSL style sheet, these characteristics lead to hyperlinks. Alternatively, you can link a different functionality than a hyperlink to
Page 13 of 41
these characteristics with an XSL style sheet of your own.
See also: Reference Information: Definition of Hyperlinks in the ERP System
Output of Image You can insert and display images that have the formats GIF, JPG, BMP, or AVI (video). You enter the URL, under which the image file is stored, for example http://help.sap.com/banner/saplogo_a.gif. The image is displayed on the left side of the PI sheet. The following characteristics are available for the definition of a hyperlink to the corresponding file:
Characteristic name PPPI_IMAGE_AVI PPPI_IMAGE_BMP PPPI_IMAGE_GIF PPPI_IMAGE_JPG
Characteristic description Image in AVI format (video) Image in BMP format Image in GIF format Image in JPG format
Because these file formats may contain harmful code, the file formats represent a security risk. For this reason, ensure that the files used are free of viruses or that there are no viruses that can execute source code in image files.
See also: Reference Information: Definition of Hyperlinks in the ERP System

Output of Object You can also include any other object of your choice, such as an MS Word document. To do this, specify the URL under which the file is stored for the characteristic PPPI_OBJECT (any object). Because any object can be loaded, the integration of objects represents a security risk. You must therefore ensure that the files used are free of viruses.
Example Characteristic PPPI_OBJECT Value \\server\ordner\dokument.doc
If you are using the standard XSL style sheet, the characteristic PPPI_OBJECT leads to the HTML element <object>. Depending on what you are inserting with it, you must find out yourself which of the possible attributes you should or must specify according to HTML standard. To include attributes, you must define an XSL style sheet.
Output of Parameter You can display the values of XStep parameters that you have defined in the XStep in the PI sheet. To do this, enter a description and the name of the XStep parameter. See also: XStep
Parameters
Examples
See also: XStep Process Instructions for PI Sheets (Section Activities ) XStep: Lists
XStep: Inputs
Use
You use XStep process instructions to add input fields to a PI sheet that the process operator then fills with values. Input fields can be used as follows:
Page 14 of 41
To enter certain actual values from production To enter signatures to sign a process step in the PI sheet To enter signatures to complete the whole PI sheet See: Completing Browser-Based
PI Sheets
In addition, you can define the following functions for the value to be entered:
Suggested Value The input field is filled with the defined suggested value at the start of the PI sheet. The suggested value is displayed in blue. Only once you have accepted the value by choosing Enter, or changed it, it is displayed in black. See: XStep: Suggested Input Validation See: XStep: Input Validation in Input Fields
Values in Input Fields
You can use a process message to report the values that the process operator has entered. See: Process Messages
Prerequisites
In order to write an input value in an XStep parameter, you must first have defined this XStep parameter in the XStep. See also: XStep Parameter
Features
Input Functions in the PI Sheet Input Character String The data format of characteristic PPPI_SHORT_TEXT is proposed as a default. The process operator, who is processing the PI sheet, can enter any alphanumerical value of up to 30 characters in the input field. Input Date The data format of characteristic PPPI_ EVENT_DATE is proposed as a default. In this case, the input field is already filled with the current system date when the process operator calls up the PI sheet. However, this date can be changed. Input Numerical Value The data format of characteristic PPPI_ PARAMETER_VALUE is proposed as a default. In the input field, the process operator can enter a numerical value with 10 places before and 3 places after the decimal point. You can also output a unit of measure, in addition to a numerical value. If you output the unit of measure with the characteristic PPPI_UNIT_OF_MEASURE as a character string then the unit of measure is displayed to the right of the input field. Input Long Text The data format of PPPI_MESSAGE_TEXT is proposed as a default. The process operator can enter a text of any length in the input field. The long text input field is displayed in the left half of the PI sheet. Input Time The data format of PPPI_EVENT_TIME is proposed as a default. In this case, the input field is already filled with the current system time when the process operator calls up the PI sheet. However, you can change the time. Input Parameter Value You can write a value entered in a PI sheet in a parameter in order to reuse this value somewhere else in the same XStep or the subordinate XStep. To do this you specify an XStep parameter of the type Local or Output, which you have previously defined for the XStep. See also: XStep Input Signature The data format of PPPI_SIGNATURE is proposed as a default. In this case you can enter a signature in the PI sheet in this input field. If you have set the indicator Digital Signature, the system checks the signature entered in the input field separately. If, in addition to the digital signature, you have defined a signature strategy for variances or for signing process steps for the control recipe destination, you must carry out the specified signature strategy for all variances and process steps in the PI sheet. However, you can also use another signature strategy in a particular XStep process instruction. To do this, enter a signature strategy on the Value Input tab page in the XStep process instruction. See also: Definition of Signatures
Parameters
in PI Sheets
Page 15 of 41
Example
See: XStep: Lists
XStep: Suggested Values in Input Fields

Use
If a planned or target value is available for an input value, you can enter the planned or target value as a suggested value in the XStep process instruction. If a suggested value is defined for an input value then the relevant input field is already filled with the suggested value when the PI sheet is called. You can, however, change this value.
Prerequisites
For suggested values that you define as parameter values in the XStep process instruction you must have already defined this parameter in the subordinate XStep of the same XStep tree.
Features
You can enter a suggested value as follows in the process instruction in one of the following forms:
As a fixed value You enter a numerical value. As a parameter value You enter a parameter, the value of which is to be accepted as a suggested value. You define parameters as suggested values if you want to accept the suggested value from the higher-level XStep of the same XStep tree.
Activities
Define Suggested Value as Parameter Value The following is an example of how you can define a suggested value for an input field with an XStep parameter: 1. In the higher-level XStep you create an XStep parameter for the value that you want to use as a suggested value in the subordinate XStep. You assign the category Local to the XStep parameter and assign values automatically or using a fixed value. 2. In the subordinate XStep you define an XStep parameter for the input value, which should contain a suggested value. You assign the category Input to this parameter and assign it with values using a reference to the XStep parameter that you defined in the higher-level XStep (step 1). 3. In the subordinate XStep you create a process of the type Input Parameter Value. See also: XStep: Inputs 4. In the subordinate XStep you define a suggested value with the value assignment type Parameter for the input field. To do this, you choose the tab page Suggested Value in the process instruction and enter the parameter that you defined in step 2.
XStep: Input Validations in Input Fields

Use
To restrict the value range for a specific input value, you define an input validation for it in the XStep process instruction. In the input validation, you determine:
The validation rule that is used to check the input value in the PI sheet Whether invalid values in the PI sheet are accepted and how this is done
If the process operator has entered an invalid value in the PI sheet the system issues a warning message, informing the process operator that the value entered does not correspond to the validation rule. The process operator can reject or accept the value. If the process operator accepts a value that does not correspond to the validation rule he or she may be requested to sign.
Page 16 of 41
Prerequisites
Check function If you want to use a check function to check the input value, a suitable function module must have been created in the system. To create or display function modules, go to Customizing for Process Management and choose Process Instructions Define PI Categories for PI Sheet Using Characteristic Overview. Assign Characteristics to Dynamic Function Calls Create Function Modules for Dynamic Function Calls. Error Handling If a signature is required when invalid input values are accepted in the PI sheet, you must specify which type of signature you want to use in Customizing for Control Recipe Destinations . You have the following options:
Signature without a password check Digital signatures If several individual signatures are to be executed, you also specify the signature strategy in the control recipe destination. For more information about digital signatures and the required settings, see Approval Using Digital Signatures.
Features
In the XStep process instruction, you can define the validation rule for the input validation as follows:
As a check formula for numerical values You write the check formula in the Editor. When doing so, refer to Check Formula As a check function for all values You specify a function module and assign the obligatory parameters of the function module with values.
Syntax for Input Validations.
Error Handling In addition to the validation rule, you can also enter the following information in the XStep process instruction to control how invalid input values are processed:
Invalid values are accepted You can choose from the following options:
Always Accept All invalid values are accepted by the system. Never Accept Invalid values are never accepted by the system. In this case, you must discard the invalid value. Only with Signature Depending on the settings made in the control recipe destination, the PI sheet requests a signature without a password, one digital signature, or several individual signatures defined in a signature strategy. You must also enter a comment for digital signatures. The input value is not automatically confirmed when the signature is entered. Once you have entered a correct value again, the system automatically accepts this value, which means you do not need to enter another signature. All deviating input values are documented in a deviation history. For more information, see Recording Actual Data in Browser-Based PI Sheets.
Signature strategy for digital signatures For digital signatures in PI sheets you can define a signature
strategy. This ensures that invalid values must be signed by several people. In the
signature strategy, you specify which individual signatures are required. You can assign a signature strategy in the control recipe destination. This strategy is then used for all input validations. If you want to use a different strategy for a particular process instruction, you assign the strategy to this process instruction. The signature strategy must be carried out synchronously in the PI sheet. This means that the individual signatures must be executed immediately after one another (see Signature mode). Authorization to execute a signature For signatures without a password check and for digital signatures, you can specify that a user requires a special maintenance authorization for the PI sheet to execute the signature. The system then checks if the activity specified in the process instruction has been included in authorization object C_CRPI_BER in the user master record. Irrespective of the settings you make here, the system checks the following authorizations for digital signatures:
Activity 73 (Archive) in authorization object C_CRPI_BER (PI sheet) For individual signatures in a signature strategy, the authorization group for the individual signature in authorization object C_SIGN_BGR (authorization groups for digital signatures)
Signature mode
Page 17 of 41
If invalid values are accepted, signatures can only be entered synchronously (synchronous See also: Definition of Signatures Warning
signature process).
in PI Sheets
If you have accepted an invalid value in the PI sheet anyway the system issues a standard message to this effect. Instead of this standard message you can also save your own message text.
Activities
Input Field with Check Function and Error Handling 1. You create an XStep process instruction of type Input -> Character String. See also: XStep: Inputs 2. You enter the name of the function module in the process instruction on the Input Validation tab page. 3. You assign values to the parameters of the function module. See also: XStep Function Module Parameters 4. On the Error Handling tab page, you define whether invalid values are accepted in the PI sheet and if so, how. 5. If invalid values can only be accepted with a signature, you can also specify a signature strategy and an authorization. 6. If applicable, you create your own warning message.
XStep: Calculations
Use
You can use this function to perform calculations based on calculation formulas in the PI sheet. You can, for example, calculate the total material quantity consumed in all phases. You can then use a process message to report the calculated value.
Prerequisites
You have already defined the following parameters for the XStep.
Parameters that you use in the calculation formulas (for example VALUE1+ VALUE2) Parameters in which the calculated values are to be written.
Features
You define the calculation formulas using XStep parameters, which are inserted as variables in the formula. Additionally, you can also write the value calculated in the PI sheet to a parameter. Carrying Out the Calculation The calculation can be carried out in the PI sheet in the following ways:
Manually If you have not specified an event in the XStep process instruction, you must trigger the calculation in the PI sheet manually by choosing icon Event-Triggered If you have specified an event in the XStep process instruction, the system carries out the calculation in the PI sheet, as soon as the specified event occurs. For more information about events, see Events .
in PI Sheets and Cockpits.
Activities
1. You create an XStep process instruction of type Control Calculation. 2. In the process instruction, you specify: A description, that is displayed in the PI sheet next to the calculated value. A parameter, if necessary, in which the calculated value is to be written An event, if necessary, that triggers the calculation automatically A calculation formula, that is used to calculate the value Refer to Syntax of Calculation Formulas
XStep: Manufacturing Data Access

Use
You can use the internal interface Manufacturing Data Access to:
Page 18 of 41
Read values of manufacturing data points in the PI sheet from another application Write values from the PI sheet to manufacturing data points of another application Subscribe to manufacturing events of another application in the PI sheet These events are then automatically reported to the PI sheet as soon as they occur. In this way, you can, for example, subscribe to value changes. In addition, events can contain parameters that you can read while processing an event.
All applications that are registered as services at the interface can provide data points and events and receive them from other services. In this way, values from one or more data points can be:
Read or written synchronously This means on demand (for example, using a pushbutton). Read or written on an event-driven basis This means that in running applications, data is automatically read or written triggered by an event without the user having to take any action.
Events can also be processed in different system logons running in parallel. User A maintains PI sheet 001. User B maintains PI sheet 002. Value changes in PI sheet 002 can be transferred automatically to PI sheet 001 although the two users are logged on at different terminals. For more information, see Manufacturing Data Access.
Prerequisites
OPC Items and OPC Events To use data points (items) of the services ODA (OPC Data Access) and OAE (OPC Alarms/Events), you must first have created a subscription in Customizing. To do so, go to Customizing for Process Management and choose SAP ODA (OPC Data Access). For more information about SAP ODA, see SAP OPC Data Access.
Features
Executing Data Access Data access with MDA can be executed as follows:
Manually A button with the description saved appears in the PI sheet. The data is not read or written until you have pushed the button. Event-driven You can specify an event that triggers data access. The system automatically reads or writes data as soon as the event is triggered. Manual and event-driven You can read and write data manually and parallel to this, the data access can be triggered by a defined event. To do this you specify an event.
Read the value of a data point If you want to the read the value of a data point, you define it with the type Read and assign it with values using an XStep parameter that you have defined beforehand at the XStep node. The value Read is transferred to the XStep parameter. To display a read value in the PI sheet, define a process instruction of the type Output -> Parameter Value. Write value to a data point If you want to transfer a value from a PI sheet as a data point to another application, you define it with the type Write and assign it with a fixed value or an XStep parameter that you have defined beforehand at the XStep node. The fixed value or the value of the XStep parameter is exported as a data point.
Activities
1. You define XStep parameters at the XStep node For all data points that are to be read in the PI sheet For all values from the PI sheet that are to be written to another application as data points See also: XStep Parameters 2. You create an XStep process instruction of type Control Data -> Manufacturing Data Access a. On the Data Access tab page, you specify whether the data access should be executed on a manual or event-driven basis or using both these options. b. On the Data Points tab page you specify the following: The data points The type of data point (read or write) The value assignment type Parameter or Fixed The XStep parameters to which the data point values should be written The XStep parameters or fixed values to which the data points should be written 3. To display read values in the PI sheet you create an XStep process instruction of the type Output -> Parameter Value and enter the corresponding XStep parameter. See also: XStep: Outputs
Page 19 of 41
XStep: Automatic Value Assignment

Use
You can use this function to determine the point of time (date and time) at which you process the XStep process instruction in the PI sheet. The date or time is automatically updated once an entry is made in the PI sheet. This time is recorded using a process message. If you delete the entry, the system resets the date or time to the current system time.
Activities
1. You create an XStep process instruction of type Automatic Value Assignment. 2. In the Creation Date dialog box, you enter the date or time of the event. 3. If required, you specify an XStep parameter, to which the date or time is written. By doing this, it is possible to reuse the data again in the PI sheet. 4. If required, you create an XStep process instruction of type Output -> Parameter Value to display the date or time in the PI sheet.
XStep: Tables
Use
You can use this function to output control function keys, input and output fields in the PI sheet in the form of a table. In comparison to lists, in which process instructions of the same type are grouped and displayed as a list, the system copies the XStep process instructions and outputs them in the form of a table. For more information about lists, see XStep: Lists.
Activities
1. You create an XStep process instruction of type Control Data ->Table.
The system creates the node <Table> under the node .
2. In the properties dialog box of the node <Table> you enter the minimum and maximum number of rows that can be displayed in and added to the PI sheet. 3. On the <Table> node you create your inputs, outputs and control functions.
XStep: Dynamic Function Calls

Use
You can use this function to call certain SAP functions from within the PI sheet or perform certain calculations and checks in the PI sheet. ABAP function calls that have been created for the corresponding use are used for the function call.
Prerequisites
The function module to be called must exist and be active in the Function Builder (ABAP Development Workbench).
Features
The SAP system contains a number of predefined function modules that you can use in function calls. You can also create your own function modules. To create or display function modules, go to Customizing for Process Management and choose Process Instructions Define PI Categories for PI Sheet Using Characteristic Overview. -> Assign Characteristics to Dynamic Function Calls Create Function Modules for Dynamic Function Calls. The following table provides an overview of the function modules that you can define as dynamic function calls:
Page 20 of 41
Function Calling of any transaction Order confirmation for phases Displaying of material quantity calculation in the order
Function Module COPF_CALL_TRANSACTION COPF_ENTER_CONFIRMATION COPF_MATERIAL_QUANTITY_CALC
Display of documents created in the SAP document management COPF_DOCUMENT_SHOW_DIRECT system Calculation of the duration of time intervals Calculatethe start date of a time interval Calculate the end date of a time interval Create physical-sample records for quality inspections during production Processing of sample drawing (for example, release/lock physical sample) Recording of inspection results in QM Sample function module for check function
Execution of the Function
COPF_DETERMINE_DURATION COPF_DETERMINE_START_TIME COPF_DETERMINE_END_TIME QPRS_PI_NEW_SAMPLE_DRAW_XS QPRS_PI_NEW_SAMPLE_DRAW_PROC_XS COPFX_QM_INSPECTION_RESULT_REC_XS COPF_VALIDATION_FUNCTION_TEST
The function can be executed in the following ways:

Manually A button with the description saved appears in the PI sheet. The function is only executed, once you have triggered it using the pushbutton. Event-driven You can specify an event that triggers the function automatically. The system automatically executes the function as soon as the event is triggered. Manual and event-driven You can execute the function manually and parallel to this, the function can also be automatically triggered using a defined event. To do this you specify an event.
For the event PARAMETER_CHANGED, in the case of event-driven and manual execution you can specify which parameters have to have values assigned to them in order for a function module to be executed. For more information about events, see Events in PI Sheets and Cockpits. For more information on how to define the parameters of the function module in the XStep process instruction, see XStep: Function Module Parameters.
Activities
1. You create an XStep process instruction of the type Control Function Call. 2. You specify the following on the Function tab page in the process instruction: Whether the function can also be executed in display mode Whether the function should be triggered manually, event-controlled, or both manual and event-controlled.
If the function should be triggered manually, you have the option of entering a description which will appear on the pushbutton in the PI sheet.
3. You enter the name of the function module on the Parameters tab page. The function module parameters are displayed. 4. You assign values to all the mandatory parameters of the function module. 5. You assign values to all optional parameters of the function module, for which you do not want to use the default value defined in the function module.
XStep: Function Module Parameters

Use
ABAP function modules, which you use in XStep process instructions, contain import , export, changing or table parameters, according to how they have been defined. You must assign either a fixed value or an XStep parameter to these.
The Type of Function Module Parameter indicates the data flow of the parameter from the point of view of the PI sheet view and not of the function module. A parameter of the type Export means that the value of the parameter is transferred from the PI sheet to the function module. From the function module's point of view, they are import parameters.
Prerequisites
If you want to assign values to a function module parameter using an XStep parameter the XStep parameter must first be defined in the higher-level XStep. See also: XStep Parameters
Features
Export parameters You use export parameters in dynamic function calls and input validations that are carried out using a check function. You must assign either a fixed value or an XStep parameter to the export parameters (see below). Import parameters You use import parameters in dynamic function calls. You assign values to the import parameter using an XStep parameter. The value of the import parameter is written to the XStep parameter and imported from the function module to the PI sheet. You can output the value of the XStep parameter in the PI sheet. You can also use the XStep parameter to forward the value to subsequent XSteps in the same XStep tree. Changing parameters You define changing parameters in dynamic function calls. You assign values to the changing parameters using an XStep parameter. The value of the changing parameter is written to the XStep parameter and imported from the PI sheet to the function module. Once the function has been executed the value of the changing parameter is again written to the XStep parameter and re-imported to the PI sheet. You can output the value of the imported changing parameter in the PI sheet. You can also use the XStep parameter to forward the value to subsequent XSteps in the same XStep tree. When doing so you should note the following:
The function can be execute more than once in the PI sheet The value of the changing parameter may be changed by the function
Table parameters You use table parameters in dynamic function calls. You can use table parameters to export values of a table column from a PI sheet to a function module. The function module can change the contents of the table and return the result to the PI sheet. You assign values to the table parameter using an XStep parameter. The value of the table parameter is written to the XStep parameter and exported from the PI sheet to the function module. Once the function has been executed the value of the table parameter is again written to the XStep parameter and resent to the PI sheet.
You should note that the system only accepts XStep parameters that come from a table (repeated data request). Equally, you can only output an XStep parameter again within one table. The XStep parameter refers to the entire table column. If the function call is executed outside the table, all values of the table column are transferred to the function module. If you want to the display the value of an XStep parameter in the PI sheet you must have defined an output for it. For more information, see XStep: Outputs.
Assigning Values to Function Module Parameters
You assign a fixed value or an XStep parameter to a function module parameter.

Value assignment with fixed value If you want to export a parameter value from the PI sheet to the function module you can enter it as a fixed value, provided that it already exists in the process order. The data type of the fixed value must match the data type of the function module parameter. Value assignment with XStep parameter If the value is only available in the PI sheet you copy it using an XStep parameter. This must first be defined in the same XStep. The data type of the XStep parameter must match the data type of the function module parameter. Function Module Parameters of Type Table
Import, export and changing parameters can be typed with reference to a table type. In contrast, a function module can also possess concrete table parameters (see Table Parameters). If the function module parameter is typed with reference to a table type, you can export an entire table from the PI sheet to the function module and back again. If you want to output the table in the PI sheet you must define the XStep process instruction as a table (repeated data request). If you have defined a simple data request, the system only outputs the value of the first table line. The system can only process single-column tables.
XStep: Functions that can be Executed Automatically

Use
You can use this function to define conditions that automatically trigger the execution of functions such as Deactivate process instruction or Lock process step in the context menu. You want to specify, for example, that the quantity recording for a certain material depends on the current pH value of the mixture in the vessel. This means that the material quantity may not be recorded until the process operator has measured a pH value of less than seven (< 7). Using this function, you define this condition in the process order or master recipe. When the PI sheet is opened, the input field for material quantity recording would first be locked. The lock for the input field for material quantities would only be removed after a pH value of less than seven was entered in the preceding input field. The material quantity field would become ready for input.
Page 22 of 41
Prerequisites
OPC Events To use events of the service OAE (OPC Alarms/Events), you must first have created a subscription in Customizing. To do so, go to Customizing for Process Management and choose SAP ODA (OPC Data Access). For more information about SAP ODA, see SAP OPC Data Access.
Features
You can define conditions to automatically execute the following functions:
- Save document - Document report data - Activate process step - Deactivate process step - Lock process step - Unlock process step - Complete process step - Activate process instruction - Deactivate process instruction - Lock process instruction - Unlock process instruction - Complete process instruction - Activate table - Deactivate table - Lock table - Unlock table - Complete table - Add table line - Activate table line - Deactivate table line - Lock table line - Unlock table line - Complete table line
Conditions You can define conditions for the automatic execution of functions as follows:
In a Formula In the calculation formula, you specify when this command should be executed. Refer to Syntax In a Function Module You enter a function module, in which the conditions for triggering the command are stored. You assign values to the parameters of the function module. See also: XStep: Function Module
of Calculation Formulas
Parameters
As a Manufacturing Event (PPPI_EVENT) You specify an event, which the PI sheet is to subscribe to. For more information on events, see:
Events in PI Sheets and Cockpits Manufacturing Data Access Manufacturing Events
Activities
1. You create an XStep process instruction of type Control Data -> Command. 2. In the process instruction on the Command tab page, you specify the following: The command that is automatically executed, displayed or hidden once the conditions have been met. An action, which specifies whether the command should be executed, displayed or hidden once the conditions have been met. 3. On the Trigger tab page, you specify a trigger type. Enter a calculation formula for trigger type Formula Specify a function module for trigger type Function Specify a manufacturing event for trigger type Event
Example
The following example shows, how it is possible to define the example described above: 1. You create a standard XStep in the SXS repository. 2. You create an XStep for the XStep tree. 3. You create the following XStep parameters for the XStep:
Page 23 of 41
4. You assign values to the XStep in the following way:
5. Assign a Control Recipe Destination to the XStep. 6. You create a process instruction. 7. You create an XStep process instruction of type Input -> Parameter Value for parameter P1 for the XStep node 8. You create additional process instructions. 9. You create the following XStep process instructions for this XStep node : Enter parameter value for parameter P2 Control Command Command: Process instruction locked Action: Execute Trigger: Formula Formula: P2>7 Control Command Command: Remove process instruction lock Action: Execute Trigger: Formula Formula: P2<7
Your standard XStep should now have the following structure:
10. You check and simulate the XSteps. 11. You release the SXS version.
XStep: Lists
Use
You use this function to output input fields, output fields and functions (that you have defined in process instructions of the type Simple Data Request) in the form of a table in the PI sheet. In this way, you can display information of the same kind in a clearly laid-out and structured way. In this function, all XStep process instructions with the same logical structure are grouped together. In comparison, in repeated data requests, a process instruction is copied and output in a table. By grouping generated XStep process instructions in which the material components are automatically adopted, you obtain a clearly laid-out material list in the PI sheet.
Page 24 of 41
Prerequisites
So that the system is able to group XStep process instructions of the same type and output them in list form in the PI sheet, the XStep process instructions must meet the following conditions:
They are of the type Simple data request They belong to the same process instruction category Their logical structure, with regard to input fields, output fields and control functions, is identical No text symbols are used in the labels Example
The following example illustrates how you can define a material list: 1. You create a standard XStep in the SXS repository.
The system automatically creates a version and an XStep tree for the standard XStep.
2. You create an XStep for the XStep tree. 3. You create the following XStep parameters for the XStep:
4. You assign values to the XStep parameters in the following way:
See also: XStep
Parameters For all Ingredients.
5. Assign a Destination to the XStep. 6. You assign the XStep to the scope of generation See also: XStep Generation
7. You create a Process Instruction for the XStep. 8. You create the following XStep process instructions for this node : Output -> Parameter Value for the parameters MATNR, QUANSO and UOM Input -> Parameter Value for the parameters QUANIS and SIGN Input -> Signature for the parameter SIGN
Your standard XStep should now have the following structure:
See also: XStep: Outputs and XStep: Inputs
9. You check the XStep tree and simulate the standard XStep.
Page 25 of 41
10. You release the SXS version. See also: Standard XSteps 11. 12. 13. 14. 15. You create a process order and go to the XStep editor ( XSteps). You create an XStep tree. You create an SXS reference <New SXS Reference> for the XStep tree. You assign a concrete SXS reference to the XStep by assigning the standard XStep version that you have already defined. You explode the SXS reference.
After you have exploded the SXS reference, the system adds the whole XStep tree to the referenced SXS version in your XStep tree.
16. If necessary, you execute the generation. 17. You generate the control recipe.
Use of XSteps to Connect Up External Systems

Use
If you want to transfer XSteps to external systems, you have specified type 2 Download to External System, Initiated by Process Management (SAP) as the control instruction/recipe destination. In the case of control instructions/recipes with this destination, the XSteps are passed on to an external system (such as a process control system) via the PI-PCS interface. There they are processed automatically. The external system then reports back actual data to the SAP system.
Prerequisites
A precondition for the use of this function is that you are using an external system that is connected to the SAP system via the PI-PCS interface. For more information, see
PI-PCS Interface.
You have set the Generation of XSteps Blocks indicator in Customizing under Define and Set Up Control Instruction/Recipe Destinations. Only if the indicator is set can you send control instructions/recipes with XSteps to external systems.
Features
If you define XSteps that are to be sent to an external system, you enter the data that you wish to send in the XStep in the form of a parameter list. The XStep contains the parameters with the characteristics for appropriate value assignment (see also XStep Parameters). It is not necessary to create process instructions for the XStep.
Standard XSteps
Use
Standard XSteps are XSteps that you create as master data in the standard XStep repository (SXS repository). Standard XSteps can be reused by creating a reference to them in the SXS repository from an application (for example, master recipe). Using the references to standard XSteps (SXS reference), you can considerably reduce the time required to maintain the data. If, for example, there are changes to the standard processes, you do not have to make these changes in each individual master recipe. Instead, you make the changes centrally in the SXS repository. All master recipes containing references to these standard XSteps are changed automatically.
Prerequisites
See also: Execution Steps (XSteps)
Features
You invoke the standard XStep repository from the SAP menu under Production - Process Master Data Standard XStep Repository. Structure of a Standard XStep A standard XStep can consist of several versions. Every version contains an XStep tree. You create XSteps within the XStep tree, which describe the precise contents of the standard XSteps. For more information about XSteps, see XStep.
Page 26 of 41
Versioning You can create several versions with different validity periods for a standard XStep. If you explode an SXS reference either in the SXS repository or in an application, the system searches for the SXS version that is valid and released for the key date and creates a copy of it. You can choose any name for the version. The version names are only unique within a standard XStep (see Standard XSteps: Versioning). Where-used list At the level of the standard XStep, you can perform the where-used function via the context menu. The where-used function checks whether the standard XStep is referenced in process orders, in recipes, in standard routings and in production orders, or in the repository. The result of the where-used analysis is shown in tabular form in the lower part of the screen of the repository.
Branching to Applications: By double-clicking on Application, you can branch to the display of the master recipe or the process order. By double-clicking on a referenced standard XStep, you cause the system to take you to the point in the standard XStep repository at which the standard XStep is used. In the case of process orders, you can double-click on the Order Status to branch to the detail view of the order status. Add New Fields
Vial Choose Layout in the button bar, you can store your own variants for the layout of the where-used list. To display your own information in the where-used list, proceed as follows: 1. Define an Append structure for the DDIC structure CMX_XSR_W_SXS_WHERE_USED_LIST 2. Create an enhancement implementation for the enhancement spot ALV_GRID_XT. Enter as filter criterion for the filter ALV_GRID_ID the value SXS_WUL_RESULTS an. 3. In the method TABLE_FOR_FIRST_DISPLAY, the fields of the customers own Append structure are populated (in CT_OUTTAB). The field catalog (CT_FIELDCATALOG) must likewise be extended by the addition of the new columns of the customers own fields.
Standard XSteps: Configurable Building Blocks

Use
You can use configurable standard XStep building blocks to cover the most important elements of the production process, such as digital signatures, confirmations, accessing of process descriptions, etc. The standard XStep building blocks are configurable and can be adjusted to suit customers' own specific needs. The standard XStep building blocks are available as downloads in the SAP portal in the SAP Community Network.
Activities
1. To access the SAP Community Network, choose https://www.sdn.sap.com in the SAP portal. 2. Choose the link Downloads from the horizontal menu bar.
You now see the Download Catalog.
3. Here choose the entry Manufacturing from the available downloads. 4. Then choose the entry Core Manufacturingfrom the list of downloads for Manufacturing.
There you will find the required files and documents for downloading.
For more information, refer to the BPX Community for Manufacturing under https://www.sdn.sap.com/irj/sdn/bpx-manufacturing.
Standard XSteps: Versioning

Use
You can create several versions with different validity periods for a standard XStep. If you explode an SXS reference either from within an application or in the SXS repository itself, the system searches for the SXS version that is valid and released as at the key date (i.e. with the status Released or Released for Test). You can choose any name for the version. The version names are only unique within the standard XStep.
Features
Automatic Number Assignment
In Customizing for Production Planning Process Industries, you can specify under Process Coordination Execution Steps Standard XStep Repository Settings for Standard XStep Repository that numbers are to be assigned automatically for the versions of a standard XStep. The first new version of a standard XStep is assigned the number 0001. If several versions already exist for a standard XStep, the system chooses the newest version. If the key of the newest version consists of numbers, the system increases the number by one. If the system does not find a valid predecessor number, the number 0001 is assigned. if you have activated automatic number assignment, you cannot then change the version number manually. If you wish to change the version number manually, you must first reverse your Customizing setting.
Automatic Calculation of the Validity Period
In Customizing for Production Planning Process Industries, you can specify under Process Coordination Execution Steps Standard XStep Repository Settings for Standard XStep Repository that the valid-to date of a version is to be determined by the system. Manual entries for the valid-to date are then not possible. At any one point in time, there can only be one valid version of a standard XStep. If you change the status of a version to Released or Released for Test, the system checks the validity of the versions. If a valid version previously existed, the time period of this version is limited to the valid-from date of the new version.
For a standard XStep, version 1 with the validity period 03.31.06 until infinite (12.31.9999) was hitherto released. If you release version 2 as at 09.30.07, the validity period of version 1 is limited to 09.29.07. There are a number of special aspects:
If the valid-to date of the new version lies before the valid-from date of the old version, the valid-to date of the new version ends one day before the valid-from date of the new version. If a new version whose period lies between two released versions is released, the same rule as above applies:
The valid-to date of the earlier version ends one day before the valid-from date of the new version. The valid-to date of the new version ends one day before the valid-from date of the later version.
The date of the new version may not lie before the current days date. The new and the old version may not have the same valid-from date.
Standard XSteps: Approval Procedure

Use
The approval procedure for standard XSteps comprises the controlled status management and the digital signature for certain statuses, enabling comprehensive documentation of the changes made to a version. Which business actions may be performed for the standard XSteps depends on the status. You can specify that a digital signature is necessary to set the statuses Released, Approved and Obsolete, Discarded. These statuses can then only by assigned by authorized signatories (see also Approval Using Digital Signatures). In production, you can only use released and approved standard XStep versions. You may not make any further changes to released and approved standard XStep versions. If changes are necessary, you must create a copy for this version of a standard XStep and discard the original version. At any one point in time, there can only be one valid version of a standard XStep.
Prerequisites
You have made the settings for the digital signature in Customizing under Cross-Application Components General Application Functions Digital Signature. You have set the SXS Version: Approval Procedure Active indicator in Customizing for Production Planning Process Industries under Process Coordination Execution Steps (XSteps) Standard XStep Repository Settings for the Standard XStep Repository . You have also specified in this IMG activity whether an individual signature or a signature strategy with several authorized signatories is to be used to set the statuses Released, Approved, or Obsolete, Discarded.
Features
Each version of a standard XStep (SXS version) is assigned a status. The current status of a standard XStep determines which business actions can be executed with it. The following types of status can be set:
Page 29 of 41
Status In Process
Meaning This status is set automatically as soon as you have created a version. A version of a standard XStep that has the status In Process:
Can be changed (for example, new XStep parameters can be added or existing ones changed) Cannot be referenced if it has only versions with the status In Process Can be checked and simulated in the SXS repository
Business Action Release for test Reject Release and approve
Refused
You set the status Refused for an SXS version, if, for example, the check has revealed errors and you want to correct the SXS version. A version of a standard XStep that has the status Refused:
Cannot be changed (for example, the categories of an existing XStep parameter cannot be changed) Can only be changed if you have explicitly set the status to In Process Can be checked and simulated in the SXS repository Can be archived or deleted
Delete Process Flag for deletion
Released for Test
A version of a standard XStep that has the status Released for Test:
Can only be changed to a limited extent if a version exists that has been released and released for testing. For example, you can no longer change the category of a parameter Can be checked and simulated in the SXS repository Can only be exploded in test control recipes in the case of an existing reference Can be simulated in the master recipe
Process Reject Release and approve
Releasedand Approved
You set the status Released and Approved for an SXS version if it can be used in production. This status can be used only with a digital signature. At a key date, there can only ever by one released and approved version of an XStep. A version of a standard XStep that has the status Released, Approved
Can be exploded in the case of an existing reference Can no longer be changed Cannot be reset to the status In Process Can be checked and simulated in the SXS repository
Discard
If you wish to change released and approved XStep versions, you must copy them and use them as templates. Discard the old version and assign the status Released, Approved to the new version. Obsolete and Discarded You set the status Obsolete and Discarded for an SXS version if it can no longer be used in production. This status can be used only with a digital signature. A version of a standard XStep that has the status Obsolete:
Cannot be changed Can no longer be released
Delete Flag for deletion
Page 30 of 41
Can be checked and simulated in the SXS repository Can be archived or deleted
Flagged for Archiving
A version of a standard XStep that has the status Flagged for Archiving:
Can be archived Can no longer be changed Can be checked and simulated in the SXS repository
Archived
If you have archived an SXS version, it is assigned the status Archived: A version of a standard XStep that has the status Archived
Remains visible in the SXS repository Can no longer be changed Can be checked and simulated in the SXS repository
Delete
The following graphic shows the statuses and business actions of the approval procedure:
Approval Process with Multistep Signature Procedure
If you specify a multistep procedure for the digital signature, in which several persons must provide their signatures, the status Current Signature Process is used to denote that the approval procedure is running. The status Current Signature Process allows only the continuation of the process that has started as business actions (that is, either the approval and release or the discarding of an XStep. You can terminate the signature process. The XStep then acquires the status prior to the signature process. When the last necessary signature has been provided, the status Released, Approved or Obsolete, Discarded is set.
Activities
Create Standard XStep For more information, see Creating a Standard XStep for a PI Sheet.
Standard XStep Versions: Simple Status Management

Use
In addition to the official approval procedure for standard XStep versions, there is a simple status management facility. You can use this status management only if you are not working in an environment in which approvals are mandatory because status changes cannot be comprehensively documented and restricted to authorized persons. Comparison of Approval Procedure and Simple Status Management:
Page 31 of 41
Approval Procedure Two additional statuses:

Status Released and Approved: Versions with this status can no longer be changed. Status Discarded The status of these versions can no longer be changed to Released.
Simple Status Management

Status Released:: Limited changes are possible (e.g. the description of a parameter). The XStep tree of a version can still be changed. Status Obsolete The status of these versions can be changed again to Released.
Digital signature can be used to set the statuses Released and Approved and Discarded. The digital signature ensures that status changes may only be made by authorized persons.
The digital signature cannot be used.
Prerequisites
You have not set the SXS Version: Approval Procedure Active indicator in Customizing for Production Planning Process Industries under Process Coordination Execution Steps (XSteps) Standard XStep Repository Settings for the Standard XStep Repository.
Features
The following statuses are provided for the versions of a standard XStep in simple status management:
Page 32 of 41
Status In Process
Meaning This status is set automatically as soon as you have created a version. A version of a standard XStep that has the status In Process:
Can be changed (for example, new XStep parameters can be added or existing ones changed) Cannot be referenced if it has only versions with the status In Process Can be checked and simulated in the SXS repository
Refused
You set the status Refused for an SXS version, if, for example, the check has revealed errors and you want to correct the SXS version. A version of a standard XStep that has the status Refused:
Cannot be changed (for example, the categories of an existing XStep parameter cannot be changed) Can only be changed if you have explicitly set the status to In Process Can be checked and simulated in the SXS repository Can be archived or deleted
Released for Test
A version of a standard XStep that has the status Released for Test:
Can only be changed to a limited extent if a version exists that has been released and released for testing. For example, you can no longer change the category of a parameter Can be checked and simulated in the SXS repository Can only be exploded in test control recipes in the case of an existing reference Can be simulated in the master recipe
Released
Set the status Released for an SXS version, if it can be used in production. A version of a standard XStep that has the status Released:
Can be exploded in the case of an existing reference Can only be changed to a limited extent (for example, you are not allowed to change the category of an XStep parameter) Cannot be reset to the status In Process Can be checked and simulated in the SXS repository
Obsolete
You set the status Obsolete for an SXS version if it can no longer be used in production. A version of a standard XStep that has the status Obsolete:
Cannot be changed Can only be changed if you have set the status to Released Can be checked and simulated in the SXS repository Can be archived or deleted
Flagged for Archiving
A version of a standard XStep that has the status Flagged for Archiving:
Can be archived Can no longer be changed Can be checked and simulated in the SXS repository
Archived
If you have archived an SXS version, it is assigned the status Archived: A version of a standard XStep that has the status Archived
Remains visible in the SXS repository Can no longer be changed Can be checked and simulated in the SXS repository
Page 33 of 41
SXS References and Parameterization

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. 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.
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
Page 34 of 41
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 See also: Create version and an XStep tree for the standard XStep.
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 the following text Create Quantity of &LABEL& as a description. See also: XStep: Inputs 7. You define input validation for the input field. a. To do this, double-click the process instruction and choose the Input Validation tab page. b. 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
Process Instruction node. Create
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.
Page 35 of 41
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 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.
Export and Import of Standard XStep Objects

Use
You can use the XML-based export and import functions to transfer content from one XStep repository to another. This can make sense if you wish to import data from your test system to your validation or production system, for example. You can export the following objects of a standard XStep, save them locally, and import them again:
A standard XStep folder A standard XStep A standard XStep version
Features
Restrictions During Import:
During XML import, the system generates new SXS objects (subtree structures) for the imported XML data. The new objects are assigned to the repository object you selected as subobjects. In the process, the system checks whether the hierarchical relationship that objects have with each other is taken into account.
Standard XStep folders can only have standard XStep folders or standard XSteps as subnodes. Standard XSteps can only have standard XStep versions as subnodes. Only one XStep tree can ever be inserted under a standard XStep version.
If these conditions are not satisfied, the system terminates the XML import.
Check Sum Check During Import of XML Files From Folders, Standard XSteps, and SXS Versions
The XML file of the exported data can be processed and changed in the XML editor. You can use the check sum check to determine whether XML files whose content was changed after the XML export may be imported into your target system. In Customizing for Production Planning Process industries you can specify under Process Coordination Execution Steps Standard - XStep Repository Settings for Standard XStep Repositorywhich message type the system is to generate if changed XML files are to be imported. The check sum check must be activated both in the source and target system prior to export/import of the XML files.
Error Messages
Error messages during import are outputted in a separate subwindow below the repository.
Status of SXS Version
The SXS versions newly generated through the import are given the initial status In Process.
Activities
Export Standard XStep Objects
... 1. Select the desired object. 2. Choose Export in the context menu with the right-hand mouse key.
Page 36 of 41
You can control the functions that a user can perform in the context menu via the authorization concept.
The Export SXS Object dialog box appears.
3. Enter a name for the exported file and choose the desired directory.
The system converts the selected object and the subordinate hierarchy structure (XS repository) into an XML file.
4. Save your data.

The system creates an XML file with the exported standard XSteps object in the specified directory. Import Standard XStep Objects
5. Select the desired object that is to contain the new objects and choose Import from the context menu.
The Import SXS Object dialog box appears.
6. Open the XML file that is to be imported.

The system imports the data at the selected point.
Export and Import of Standard XSteps with Reference Nodes

Use
You have the option of referencing other standard XSteps within XStep trees of the standard XStep repository by generating SXS reference nodes (see SXS References and Parameterization). The SXS reference node merely contains a link to the assigned standard XStep. In order to be able to reconstruct the subtree structure you exported, during the XML export you must also export the data of the referenced standard XStep.
Features
During the XML import, the system checks whether the XML files contain all the information necessary to reconstruct the SXSs referenced in SXS reference nodes.
If all information is complete, the XML import is carried out.
SXS versions for SXSs, that are used as reference must subsequently receive the status Released for Test or Released so that the SXS reference relationship becomes valid again.
If information is missing and the reconstruction of the referenced SXSs is thus impossible, the system terminates the XML import.
Activities
Export a folder of the SXS repository containing the complete data record including the referenced standard XSteps. Otherwise the data enabling the referenced standard XStep to be completely set up is missing.
Export and Import of Subobjects of an SXS

Use
You can export the following parts of an SXS version, save them locally and import them again:
Individual XStep nodes of an SXS version The entire XStep tree of an SXS version
The contents and structure of the exported XStep trees are stored as XML documents.
Note the following during the import: The XStep tree is inserted as an XStep node and no longer as an XStep tree. Parameters that you have defined initally for the XStep tree are connected to the subordinated XStep node after importing, and no longer to the tree itself. When you export the XSteps, and then subsequently import them into another system and another plant, ensure that the control recipe destination plant is the same plant, as the one into which the XStep tree has been imported.
Page 37 of 41
Activities
Export XStep
... 1. Select an XStep tree or a subordinate XStep node and choose XSteps -> Export from the menu.
The Export XSteps dialog box appears.
2. Enter a name for the exported file and choose the desired directory. 3. Save your data.
The system creates a XML file with the exported XSteps in the specified directory. Import XStep
... 4. Create a standard XStep, in which you want to import the XStep. 5. Select an XStep node in the standard XStep and choose XSteps Import.
The Export XSteps dialog box appears.
6. Open the XML file that is to be imported.

The system creates the imported XStep below the XStep tree as an XStep node.
Creating a Standard XStep for a PI Sheet

The following example describes, how you can create a standard XStep for a PI sheet. It is important to note the following points when navigating in the standard XStep repository:
You can execute several functions for each XStep node. You access all functions for an XStep node using the context menu. You can store several different pieces of information and settings for each XStep node. You access the dialog box by doubling-click on the particular node.
Procedure
1. From the SAP Easy Access Menu, choose Production Process -> Master Data -> Standard XStep Repository. 2. Create folder
Select the Standard XSteps folder and choose Create -> Folder. The system creates the < Folder> node. Enter a description for the folder.
3. Create Standard XStep

Select the Process. < Folder> and choose Create -> Standard XStep. < Standard XStep> node with the < Version> and < XStep Tree> subnodes. The status of the version is currently In The system creates the
a. Enter a description for the standard XStep. b. Enter a description for the version and a validity period. See also: Standard XSteps
4. Create XStep
Select <XStep Tree> and choose Create -> XStep. < New XStep> node. The system creates a See also: XStep
Page 38 of 41
5. Assign Control Recipe Destination

Double-click < New XStep> and enter the destination type PI sheet or a precise destination that has type PI sheet in the Destinations dialog box.
6. Define XStep Parameter

Define, if required, XStep parameters for the contents of all XSteps, which have values that you want to reuse. Double-click parameters and their valuations in the Parameters and Valuations dialog box. See also : XStep < New XStep> and create the
Parameter and SXS Reference and Parameterization.

<New XStep> and enter a scope of generation in the scope of generation dialog box.
7. Assign Scope of Generation

Assign a scope of generation to the XStep if required. Double-click See also: XStep
Generation
8. Create Process Instructions

Select < New XStep> and choose Create -> Process Instruction. < New Process Instruction> node. Enter a description for the process instruction. The system creates a See also: XStep
Process Instructions for PI Sheets
9. Create Output of a Long Text

Select < New Process Instruction> and choose Create -> Output -> Long Text. < Group> node with the sub node < Long Text >. < Long Text > and enter a description and a long text. The system creates the Double-click
Page 39 of 41
10. Save 11. Execute Inspection

Select an XStep node in the standard XStep and choose XSteps -> Check from the menu bar. Correct any errors that may occur.
12. Execute Simulation

Select an XStep node in the standard XStep and choose XSteps -> Simulate from the menu bar. The XStep is simulated on the right of the screen. A preview of your PI sheet is displayed.
13. Release Status of the Version

To release your standard XStep for production, you must change the status of the version from In Process to Released. Select Change Status -> Release. See also: Standard < Version> and choose
XSteps
Archiving and Deleting SXS Versions

Use
You can archive and delete single versions of a standard XStep using archiving object CMX_XSTEPS for application XSV (SXS repository). The system creates an XML document for each XStep tree and every change. In order to be able to archive a SXS version, you must firstly set the version to status Flagged for Archiving. Standard XSteps, which you use in masters recipes and process orders, can be archived together with the corresponding master recipe or process order. See also: Archiving and Deleting Master Recipes and XSteps Archiving and Deleting Process Orders and XSteps
Activities
You access the archiving function via the area menu for system administration. To do this choose Tools-> Administration -> Administration-> Data Archiving. For more information, see: Archiving of XSteps
Data Archiving
XStep Editor
Use
The XSteps editor provides you with a maintenance environment for XSteps and standard XSteps and can be accessed from the following applications:
The standard XStep repository The master recipe The standard routing The production order The process order
The functions you can invoke depend on the application in question. For example, you can generate control instructions or control recipes in the process order and production order only.
Prerequisites
In order to move or copy XStep nodes and then insert them again, you must fulfill the following prerequisites independent of the application:
In the standard XStep repository, the SXS version must be in context. change mode; that is, the XStep node is displayed in blue. In the process order and production order, following generation of the XStep nodes, you can only move those nodes that no longer influence the business
Features
You can use the following functions in the XStep editor:
Check You either check the entire XStep tree, or separate XSteps in the XStep tree. During the check, the system ensures that the definition of the XSteps is correct; that is, whether the XStep parameters used have been previously defined. To do this, you select an XStep or the entire XStep tree and choose Check from the context menu. The error messages are displayed at the bottom of the screen. If you double click an error message, the XStep node containing this error will be visibly highlighted. Simulate You can simulate individual XStep trees separately. To do this, select an XStep node and choose Simulate from the context menu. On the right of the screen, you can then see how the entire XStep tree will look in the PI sheet. No interaction with the system is possible in the simulation; that is, the input fields and function buttons are not active in the simulation. Drag&Drop You can move the XStep nodes of an XStep tree in all applications using Drag&Drop. Cut, Copy and Paste You can cut and copy every XStep node of an XStep tree and insert it at a different point in the XStep tree. Functions in the Properties Dialog Box
Close This function closes the dialog box. The data entered is not saved automatically. Reset As soon as you have confirmed your entries in the properties window with Enter, these are transferred to the XStep tree. Using the Reset function, you can reset incorrect entries. This is, however, only possible before you have selected Enter. Previous Node Using this function, you can switch to the properties dialog box of the previous XStep node. Next node Using this function, you can switch to the properties dialog box of the next XStep node. See also: XStep
Page 41 of 41

Execution Steps (Xsteps) : PDF Download From SAP Help Portal: Created On September 30, 2013

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Execution Steps (Xsteps) : PDF Download From SAP Help Portal: Created On September 30, 2013

Diunggah oleh

Hak Cipta:

Format Tersedia

EXECUTION STEPS (XSTEPS)

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.