EXECUTION STEPS (XSTEPS) PDF download fro m SAP Help Help Portal: Po rtal: 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.
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 XSteps in manufacturing, see XSteps in Shop Floor Control. The The production prod uction steps described in XSteps are grouped grouped to form control instructions/recipes instructions/recipes and se nt 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 supp lied, 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. 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 for Process Management Management and and choose Execution Steps (XSteps) -> Set Early A ssignment 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 using the parameter definitions. definitions. ItIt is therefore poss ible 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. Applicati Applicationon-Speci Specific fic XSteps XSteps You define define XSteps directly in an application, for example in the master re cipe, routing, routing, production order or proces s order. They generally generally contain data that is related to the particular application. These These XSteps are generally implemented immediately. For more information, see XStep. Applicati Applicationon-IIndependen ndependentt Stan Standard dard XSte XSteps ps 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 this has been exploded, exploded , the system copies a valid version v ersion 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 the aid of XSteps, you define process instructions instructions independently independently of the phases of a process proces s order or planning 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 stru structu cture re that that you can use to describe describe the the precise precise execution execution of product production ion processes. Using Using XSteps XSteps you can control control the the data exchange exchange with the process control level or generate generate interactive work instructions/PI instructions/PI sheets for process operators and production workers. An XStep XStep can be assigned to a master recipe, proces s order, standard routing, routing, or production order.
An XStep XStep tree tree consists consists of one one or more XSteps. XSteps. It can also cont contain ain XStep XStep process process inst instruct ruction ions s and and referen references ces to standard standard XStep XSteps s (SXS (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 furth further er subordinated subordinated XSteps. Properties Properties of the higher-level higher-level XSteps, such as scope of generat generation ion,, control instruction/cont instruction/control rol recipe recipe destinations destinations and applic ation ation context are inherited inherited by the s ubordinate ubordinate XSteps, as long long as they have not been explic itly ass igned any of these these values separately. If, for example, you have defined the application context Order in 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 standard XStep can be referenced referenced to versions of a standard standard XStep, which are maintained maintained in the SXS repositor repository. y. When creating 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 Instruc tions All functions functions that were were available with the the conventiona conventionall process instructions instructions are still available. When maintaining maintaining objects objects in the XStep editor, editor, you no longer 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 s uch as function function calls and p rocess mess ages 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
Generation
● 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 the destination, destination, the the context context is valid for the the entire entire XStep tree until until a new context context is found. found. The The inheritance inheritance hierarchy then starts starts again fro from m this position in the tree.
Note that some scop scopes es of generation generation also set the context. If, for example, you have de fined fined the sco pe of generation generation For All Phases for an XStep, then then the system creates a copy of this XStep XStep for every phase. Every XStep XStep copied is automatically assigned assigned the context of the particular phase. For example, the XStep for phase 10 would be assigned the context for phase 10.
XStep Parameters Use You use XStep parameters to mod el your data for an XStep module. The The XStep parameters describe the contents 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 exchanged between them. XStep 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 defin define, e, for example, the long text “Add &PARAM1& Kg of material &PARAM2&” and set the XStep parameters PARAM1 and PARAM2 as placeholders for the quantity quantity and the material. ¡ To ou tput default values for input fields See also: XStep: Suggested Suggested Values in Input Fields single variables variables in calculation calculation and inspection formulas, formulas, for for example, for the the upper and lower lower limit limit values in an inspection formula formula ¡ As single 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 descriptions for input or output fields ¡ To ou tput descriptions See also: XStep: Outputs XStep: Inputs · To Allow the Exchange of D ata 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 lower in the hierarchy, hierarchy, can be assigned the value from from a higher-level XStep. Or, the XStep p arameter arameter of a higher-level XStep can be assigned the same value as a subordinated subordinated XStep (see Input and Output Parameters). Parameters). · Parallel Processing of Standard Standard XStep References 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 p arameters, whic h should facilitate the data exchange with other other XSteps within the same XStep tree, as inp ut, output, 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 the XStep located immediately below in the hierarchy, as local p arameters. arameters.
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
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 assi gned a parameter value from the higher-level XStep (category Input ) · Transfer its own value to an XStep parameter in the higher-level X Step (c ategory 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 You can assign v alues to input parameters in the following ways: · Automatically · With a fixed value · With a reference parameter · Not at all
Permitted Categories for Parameter References
Use in Process Instructions
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 parameters can output in the process instruction. To do this, define a process instruction of type Output -> Parameter Value.
· Input · Local
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 References
Use in Process Instructions
You can assign values to output parameters in the following ways:
Output parameters of a subordinated XStep can be referenced with the XStep parameters of a higher-level XStep, which are of the following categories:
You can create output parameters in the process instruction. To do this, define a process instruction of type Input -> Parameter Value .
· 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:
You can use local parameters in the process instruction in the following ways:
· Automatically · Fixed
· As input, if the XStep parameter has not been assigned values
· Not at all
· As output, if the XStep parameter has been ass igned fixed values, or been ass igned values automatically.
Characteristic You must assign a characteristic to every XStep parameter. The characteristic only spe cifies 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 examp le, b e ass igned 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 P arameter 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.
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, whic h can then process tabl e parameters · Outp ut 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, PA RAM1[1], PARAM1[2], PARAM1[3]. · The sum of all the row values that are c ontained 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].
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 p arameter TAB1 with category Local in the higher-level XStep and set the Table indicator. · You define XStep p arameter 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 calc ulation formula you can cal culate the average value using the parameter enhancements [ SUM] and [COUNT]. You can output the calc ulated 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.
Features Execution of the XStep Generation You can trigger the generation of XSteps in the following way: · When creating a control recip e: In this case, the system triggers the generation automatically. The XSteps that have been generated are inserted into the process order. · When process ing the XStep s 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 v aluated 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 direc t or indirect relationship to a generated control recip e destination. · You cannot insert any p arameters that have to be v aluated automaticall y or change any that already exis t. You can however change the value of the parameter. See also:
XStep Parameters
· You cannot insert any new sc opes of generation in the XStep tree. You can no longer change the contents of the templ ates. The template is inac tive. · You cannot insert new SXS references in the XStep tree or change ass ignments to the standard XSteps. · You cannot change or delete the exis ting 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 as signed values manually are deleted.
Note that some scopes of generation also set the context. If, for example, you have de fined the scope of generation For All Phases for an XStep, then the system generates an XStep for every phase. Every XStep generated is automatically assigned the context of
the particular phase. For example, the XStep for phase 10 would be assigned the context for phase 10.
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 proce ss 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 proc ess 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, s ee
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, s ee
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
○ 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 c hoose 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 S heets
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. Long T ext Editor and create your XML definition. 3. Go to the 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 below the selected XStep node. 2. Select and choose Create → Output → Long Text. The system creates the entry with the subnode < Long Text > below the node. 3. Double-click the icon. The Values Output dialog box appears. 4. In the dialog box Value Output enter a description and a long text.
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.
● 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 for integrating or referencing images: JPG, GIF, BMP). This 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 P ortal). The link is display ed in
the left half of the PI sheet. The following characteristics are available for the definition of a hyperlink:
Characteristic name
Description
PPPI_HYPERLINK
Hyperlink
PPPI_HYPERLINK_ASCII
Hyperlink to an ASCII document
PPPI_HYPERLINK_HTML
Hyperlink to an HTML document
PPPI_HYPERLINK_XML
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
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
Characteristic description
PPPI_IMAGE_AVI
Image in AVI format (video)
PPPI_IMAGE_BMP
Image in BMP format
PPPI_IMAGE_GIF
Image in GIF format
PPPI_IMAGE_JPG
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
Value
PPPI_OBJECT
\\server\ordner\dokument.doc
If you are using the standard XSL style sheet, the characteristic PPPI_OBJECT leads to the HTML element
