SCM372 en Col95 FV Part Ltr Execution Steps - XSteps

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

SCM372 O n l y

Date Training Center

S A P

Instructors Education Website

P a r t n e r

Participant Handbook Course Version: 95 Course Duration: 3 Day(s) Material Number: 50099629

An SAP course - use it to learn, reference it for work

O n l y

I n t e r n a l

U s e

S A P

U s e

P a r t n

e r

SAP ERP - Production

I n t e r n a l

Execution Steps (XSteps)

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

Copyright Copyright © 2010 SAP AG. 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.

O n l y e r P a r t n S A P U s e

•

ORACLE® is a registered trademark of ORACLE Corporation.

•

INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of Informix Software Incorporated.

•

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

•

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

•

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

•

JAVA® is a registered trademark of Sun Microsystems, Inc.

•

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

•

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.

Disclaimer

g201071711410

O n l y

THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS.

e r

I n t e r n a l

IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.

P a r t n

•

S A P

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.

U s e

•

I n t e r n a l

Trademarks

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

About This Handbook Typographic Conventions

Type Style

Description

Example text

Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options.

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example SELECT and INCLUDE.

Example text

Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program.

Example text

Exact user entry. These are words and characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

I n t e r n a l

U s e

EXAMPLE TEXT

© 2010 SAP AG. All rights reserved.

O n l y

Emphasized words or phrases in body text, titles of graphics, and tables

e r

Example text

P a r t n

2010

S A P

S A P

Also used for cross-references to other documentation both internal and external.

U s e

P a r t n

e r

American English is the standard used in this handbook. The following typographic conventions are also used.

I n t e r n a l

O n l y

This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not suitable for self-study.

iii

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

About This Handbook

SCM372

Icons in Body Text The following icons are used in this handbook. Icon

Meaning

O n l y

I n t e r n a l

For more information, tips, or background

Note or further explanation of previous point

e r

Exception or caution

U s e

P a r t n

Procedures

S A P

S A P

Indicates that the item is displayed in the instructor's presentation.

e r

I n t e r n a l

U s e

P a r t n O n l y

iv


2010

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

Contents

e r P a r t n

Functions and Flow of Process Management/Process Integration .................... 2

Unit 2: Control Recipes/Control Instructions .......................................... 35 Control Recipes/Control Instructions – Settings and Processing..................... 36

Unit 3: XSteps ................................................................................. 61 XSteps – Structure, Elements, and Properties ......................................... 63 Standard XSteps............................................................................ 80 Cross-Plant and Multi-Language Standard-XStep-Repository ....................... 95 XSteps for PI Sheets/Work Instructions ................................................ 112 XSteps for Process Control Systems ................................................... 432

S A P

S A P

Unit 1: Process Management/Process Integration .....................................1

U s e

Unit 4: Appendix 1: PI Sheet/Work Instructions – Elements and Functions ..451 PI Sheet/Work Instructions – Elements and Functions ............................... 452 PI Sheet Enhancements .................................................................. 468

Unit 5: Appendix 2: Process Messages ................................................485

O n l y

I n t e r n a l

e r

Process Messages – Structure and Settings .......................................... 486 Process Messages – Processing ........................................................ 531 Process Messages in the Standard SAP System ..................................... 549

P a r t n

U s e

Course Goals.................................................................................vii Course Objectives ...........................................................................vii

I n t e r n a l

O n l y

Course Overview ............................................................................. vii

2010


v

I n t e r n a l

U s e

S A P

P a r t n e r

Contents

O n l y

SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

vi


2010

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

Course Overview This training course will enable you to apply process management/process coordination. O n l y

This course is intended for the following audiences: Project members and key users who are responsible for maintaining execution steps for production and process orders to enable data to be exchanged with shop floor control systems and the conception of work instructions and PI sheets for process operators and workers in production.

U s e

P a r t n

e r

•

Course Prerequisites Required Knowledge

S A P

SCM310 Production Orders or SCM340 Process Orders

S A P

• •

Course Goals

P a r t n

U s e

This course will prepare you to: •

Use the functions of process management/process integration

e r

I n t e r n a l

Course Objectives After completing this course, you will be able to:

2010

Set up destinations for control recipes and control instructions Develop XSteps for PI sheets/work instructions and for external systems


O n l y

• •

I n t e r n a l

Target Audience

vii

I n t e r n a l

U s e

S A P

P a r t n e r

Course Overview

O n l y

SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

viii


2010

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

Unit 1 O n l y e r

Unit Overview P a r t n

Functions and Flow of Process Management/Process Integration

U s e

Unit Objectives After completing this unit, you will be able to:

S A P U s e

Unit Contents

O n l y

I n t e r n a l

e r

Lesson: Functions and Flow of Process Management/Process Integration ... 2 Exercise 1: Process Management ............................................ 19 Exercise 2: Process Integration ............................................... 25

P a r t n

• •

Explain the functions and flow of process management/process integration Name the data structures required for process management/process integration Create and send control recipes/control instructions for process orders/production orders Maintain PI sheets/work instructions Send process messages

S A P

• • •

I n t e r n a l

Process Management/Process Integration

2010


1

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

Unit 1: Process Management/Process Integration

SCM372

Lesson: Functions and Flow of Process Management/Process Integration Lesson Overview O n l y

Lesson Objectives After completing this lesson, you will be able to:

• •

Explain the functions and flow of process management/process integration Name the data structures required for process management/process integration Create and send control recipes/control instructions for process orders/production orders Maintain PI sheets/work instructions Send process messages

S A P

S A P

Business Example •

U s e

e r

I n t e r n a l

•

At your company, you want to use the process management and process integration functions to maintain your process and production orders. You first familiarize yourself with the functions and flow of process management/process integration. You also find out about the data structures required when using process management/process integration functions.

P a r t n

•

U s e

P a r t n

e r

• • •

I n t e r n a l

This lesson describes the functions and flow of process management/process integration.

O n l y

2


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y

Lesson: Functions and Flow of Process Management/Process Integration

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 1: Planning and Production

S A P

S A P

Production control in the ECC system represents the central part of a complex process chain ranging from an independent requirement (planned or customer requirements) through to the goods issue of finished products.

e r

I n t e r n a l

U s e

P a r t n O n l y

2010


3

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y


SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 2: Production Types of the SAP ECC System

P a r t n

S A P

Correspondingly, the SAP ECC system supports various production types. The topics covered in this course refer to shop floor control with process orders and production orders.

e r

I n t e r n a l

U s e

S A P

Depending on the manufacturing process, production infrastructure, product complexity, stability of production, and further criteria, a manufacturing company has various requirements with regard to shop floor control.

O n l y

4


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 3: Process Steps of an Order

S A P

S A P

The figure shows the key activities that are carried out when a process order/production order is processed in the ECC system.

e r

I n t e r n a l

U s e

P a r t n O n l y

Figure 4: Structure of a Process Order

2010


5

I n t e r n a l

U s e

S A P

P a r t n e r


O n l y

SCM372

Operations describe the different steps required during the production process. For a more detailed description of these steps, phases are assigned to the operations. Exactly one resource is assigned to an operation. This assignment of the resource is also valid for all phases that belong to the operation. The phases' processing sequence in time is defined in relationships.

Process management enables data to be exchanged with the process control level.

S A P

O n l y S A P

A process order is usually created using a master recipe and a bill of material, whereby the operation and phase structure together with its relationships and assigned resources, as well as material components and process instructions are copied to the process order.

U s e

P a r t n

e r

In material quantity calculation, you define formulas to calculate the material quantities to be used or obtained in a production process, taking into account the mixing ratios of the ingredients, yield ratios of the products and remaining materials, as well as specific material attributes (for example, active ingredient).

I n t e r n a l

The material list is made up of components representing the materials entering and leaving the production process, as well as temporarily existing materials and their planned quantities. It also defines the assignment of these material components to the phases of the order according to their appearance in the process.

U s e

e r

I n t e r n a l

P a r t n

The data for process management is maintained as XSteps (Execution Steps). Using XSteps enables process instructions to be maintained in the form of reusable and referenceable modules. A Standard XStep Repository with version management is available.

O n l y

6


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 5: Structure of a Production Order

S A P

S A P

Operations describe the different steps required during the production process. Exactly one work center is assigned to an operation.

U s e

P a r t n

The chronological sequence in which operations are processed is defined using the operation number. The material list is made up of components representing all the materials and assemblies required in the order (including their planned quantities) and defines the assignment of these material components to the operations in the order.

Process integration enables data to be exchanged with the process control level. The data for process integration is maintained as XSteps (Execution Steps). Using XSteps enables process instructions to be maintained in the form of reusable and referenceable modules. A Standard XStep Repository with version management is available.

2010


7

O n l y

I n t e r n a l

e r

A process order is usually created using a routing and a bill of material, whereby the operation structure is copied together with assigned work centers and material components.

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y


SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 6: Synonymous Terms

S A P U s e

e r

I n t e r n a l

Process integration for production orders is available as of Release ECC 6.0 Enhancement Pack 3.

P a r t n

The figure shows the key synonyms used for both order types within this course. In the training materials, both terms are always used if possible, whereby the respective term for the process orders is used first, for example, process management/process integration.

S A P

Process orders and production orders have a similar structure and similar functions.

O n l y

8


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 7: Process Management/Process Integration in Production

S A P

S A P

Process management/process integration enables data to be exchanged with the process control level. Process management/process integration can be used in fully automated, partially automated, and manually operated plants/work centers.

e r

I n t e r n a l

U s e

P a r t n O n l y

Figure 8: Process Management/Process Integration

2010


9

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y


SCM372

Process management/process integration is the interface between SAP ECC production and the systems involved in process control. Due to its flexible structure, it can be linked to fully automated, partially automated, and manually operated lines. Process management/process integration comprises the following functions for:

•

e r

•

Data is exchanged with process control systems using the PI-PCS interface.

U s e

P a r t n

•

Receiving control recipes/control instructions with process instructions from released process/production orders. Process instructions define in detail the process steps to be executed and the process data to be reported (with process messages), for example. Sending control recipes/control instructions to the corresponding process operators/machine operators or process control systems Manual maintenance: preparing control recipes/control instructions as PI sheets/work instructions written in a natural language in the ECC system so that process/machine operators can display and maintain this data on screen. Receiving, checking, and sending process messages with actual process data from the process control system or the PI sheet/work instructions.

I n t e r n a l

O n l y

•

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

Figure 9: Data Flow

Production requirements trigger the production process. Production requirements are created in material requirements planning in the form of planned orders. Planned orders define the basic dates and planned quantities for production.

10


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


Planned orders are converted into process orders/production orders, whereby basic dates and quantities are copied and actual production dates are determined from the basic dates. Process orders/production orders are created from a master recipe/routing, which is used a template. O n l y e r P a r t n

U s e

In return, process management/process integration deals with process messages from the process control level, which are forwarded to various destinations. For example, it is possible to record confirmations for the process/production order, transfer actual values of the process to functions for process data documentation and evaluation, post material consumptions or production yields as goods movements, and transfer quality data to results recording in Quality Management.

I n t e r n a l

After a process order/production order has been released for production, the process instructions maintained in the order are merged into control recipes/control instructions as part of process management/process integration and transferred to a process control system via a specific interface or displayed in the ECC system as PI sheets/work instructions) in a natural language for process/machine operators.

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

Figure 10: Creating and Sending Control Recipes/Instructions Based on XSteps

2010


11

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y


SCM372

The data for process management/process integration is maintained as XSteps (Execution Steps). Using XSteps enables you to maintain process instructions in the form of reusable and referenceable modules. A Standard XStep Repository with version management is available. XSteps are available for process orders as of Release R/3 4.7 Extension 2.00. O n l y e r

U s e

P a r t n

I n t e r n a l

XSteps are available for production orders as of Release ECC 6.0 Enhancement Pack 3.

I n t e r n a l

12


O n l y

This type of process instruction maintenance is not covered in this course.

e r

In all releases there is an older, alternative method of maintaining process instructions for process orders whereby the process instructions and control recipe destinations are assigned to the phases of the master recipe/process order.

P a r t n

U s e

S A P

S A P

Figure 11: Creating and Sending Control Recipes (II)

2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 12: Monitor for Control Instructions/Control Recipes

S A P U s e

On the basis of this information, you can execute the following functions from the monitor:

•

Send control recipes if they are not automatically sent by a background job defined in Customizing. Delete control recipes.

e r

I n t e r n a l

•

P a r t n

From the monitor, you can call different logs that provide more detailed information about the individual process steps and any errors that may have occurred.

S A P

You can obtain information about the current processing status of a control recipe/control instruction by navigating to the monitor for control instructions/control recipes.

O n l y

2010


13

I n t e r n a l

U s e

S A P

P a r t n e r


O n l y

SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 13: PI Sheet/Work Instructions

S A P

Depending on the process instructions contained in a control recipe/instruction, the PI sheet/work instructions may contain various elements and functions, for example:

U s e I n t e r n a l

14


2010

O n l y

The PI sheets/work instructions are created in HTML. The browser-based PI sheet is a further development of the original ABAP list-based PI sheet. It enables you to define your own layouts with increased flexibility and integrate different data from diverse sources, for example.

e r

Display information about the process (instructions, notes, and so on) Input fields and tables for reporting process data, input validations and signatures Batch determination and batch check Calculate process data Read and write data from internal or external applications Option of branching to QM results recording Comments for documenting and reporting process events

P a r t n

• • • • • • •

S A P

PI sheets/work instructions enable on-screen maintenance, which means that the process/machine operator can enter, confirm, report, or complete data interactively.

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 14: HTML-Based PI Sheet/Work Instructions

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

Figure 15: Flexible Data Entry with Process Messages

Process messages are data structures used to report actual process data from process control to one or more destinations.

2010


15

I n t e r n a l

U s e

S A P

P a r t n e r


O n l y

SCM372

You can define your own process messages in Customizing according to your own specific requirements. The standard SAP System contains a number of predefined message categories enabling you to transfer current data from process control to the ECC System.

O n l y

U s e

P a r t n

e r

The process messages are first sent to process management/process integration. They are then checked and passed on to predefined destinations.

I n t e r n a l

The process instructions of the control recipe/control instructions for an order define which process messages are requested by PI sheets/work instructions or a process control system.

S A P

S A P

U s e

P a r t n

I n t e r n a l

16


2010

O n l y

The standard postings for orders (goods issue, confirmation, goods receipt) can be performed using manual data entry in the ECC System or process messages from PI sheets/work instructions or a process control system.

e r

Figure 16: Standard Postings for Orders

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 17: Message Monitor

S A P

From the monitor, you can call logs that provide more detailed information on the processing of individual messages and any errors that may have occurred.

U s e

•

Complete or correct incomplete or incorrect messages Send messages if they are not automatically sent by a background job defined in Customizing Delete messages

e r

I n t e r n a l

• •

P a r t n


S A P

The message monitor provides information on the current status of process messages.

O n l y

2010


17

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y


SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 18: Order Processing with Process Management/Integration

S A P

Caution: All the exercises are offered for process orders and production orders .

O n l y

I n t e r n a l

e r

At the beginning of the course, customers must decide whether they want to carry out the exercises for master recipes and process orders or routings and production orders.

P a r t n

U s e

Alternatively, the order can be processed as described above with the help of process management/process integration.

S A P

The figure shows a detailed representation of the possible activities carried out when an order is processed.

18


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


Exercise 1: Process Management Exercise Objectives

O n l y

I n t e r n a l

After completing this exercise, you will be able to: • Create and release process orders • Create and send control recipes • Maintain PI sheets • Display and send process messages

e r

Business Example

Hint: Complete the exercises on this topic if you want to use master recipes and process orders.

S A P

S A P

Complete the exercises on the following topic, Process Integration, if you want to use routings and production orders.

1.

Create a process order PI-ORDER-## of type PI02 for material T-SCM372-PI-## in plant 1100.

2.

Choose a order quantity of 10,000 PC and a finish date in the future.

Release your process order and create the control recipe.

O n l y

I n t e r n a l

e r

Task 2:

Save your order.

Task 3: 1.

In the Process Management application menu, call the control recipe monitor and select the control recipes created for order PI-ORDER-##. Continued on next page

2010

P a r t n

U s e

Task 1:

1.

U s e

P a r t n

You are processing a process order using process management.


19

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y


2.

SCM372

Send the control recipes online from the monitor. Hint: Choose Send and not Start Send Job.

Find the PI sheets belonging to your control recipes by selecting the relevant menu item in the Process Management application menu.

2.

Access the PI sheet for the Scales operating group in change mode and maintain some of the process steps in the PI sheet.

e r

1.

1.

From the Process Management application menu, go to the process message monitor and select the process messages created during maintenance of the PI sheet.

2.

Send the process messages online from the monitor.

e r

I n t e r n a l

U s e

P a r t n

Hint: Choose Send and not Start Send Job.

S A P

S A P

Task 5:

U s e

P a r t n

Hint: Execute signatures with your ECC user and password.

I n t e r n a l

O n l y

Task 4:

O n l y

20


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


Solution 1: Process Management Task 1: Create a process order PI-ORDER-## of type PI02 for material T-SCM372-PI-## in plant 1100. Standard SAP menu: Logistics → Production - Process → Process Order → Process Order → Create → With Material Material number:

T-SCM372-PI-##

Production plant:

1100

Process order type:

PI02

Process order:

PI-ORDER-##

U s e

P a r t n

e r

a)

Enter 2.

Choose a order quantity of 10,000 PC and a finish date in the future. S A P

Total quantity:

10,000 PC

Finish:

Date in the future

P a r t n

U s e

S A P

a)

Enter

Task 2:

e r

I n t e r n a l

I n t e r n a l

O n l y

1.

1.

Release your process order and create the control recipe. O n l y

Save your order. a)

In the process order: Icon

Release

Icon

Generate Control Recipe.

Save your entries. Continued on next page

2010


21

I n t e r n a l

U s e

S A P

P a r t n e r


O n l y

SCM372

Task 3: 1.

In the Process Management application menu, call the control recipe monitor and select the control recipes created for order PI-ORDER-##. Logistics → Production – Process → Process Management → Control Recipe → Control Recipe Monitor Plant:

1100

Manufacturing order:

PI-ORDER-##

e r

Enter Send the control recipes online from the monitor. Hint: Choose Send and not Start Send Job. a)

In the control recipe monitor, select your control recipes and choose Send.

S A P

S A P

To check whether the control recipes have been sent, choose Refresh.

U s e

P a r t n

2.

I n t e r n a l

O n l y

a)

The control recipes should have Sent status.

Task 4:

U s e

Find the PI sheets belonging to your control recipes by selecting the relevant menu item in the Process Management application menu. Logistics → Production – Process → Process Management → PI Sheet → Find

e r

Plant:

1100

Process order:

PI-ORDER-## O n l y

I n t e r n a l

a)

Execute (F8) icon

Continued on next page

22


P a r t n

1.

2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


2.

Access the PI sheet for the Scales operating group in change mode and maintain some of the process steps in the PI sheet. Hint: Execute signatures with your ECC user and password. Select the PI sheet for the Scales operating group and choose Maintain PI Sheet.

Task 5: From the Process Management application menu, go to the process message monitor and select the process messages created during maintenance of the PI sheet. Logistics → Production – Process → Process Management → Message → Message Monitor Plant:

1100

Process order:

PI-ORDER-##

S A P

S A P

a)

Enter Send the process messages online from the monitor.

P a r t n

U s e

2.

Hint: Choose Send and not Start Send Job. In the message monitor, select your process messages and choose Send Message.

e r

I n t e r n a l

a)

To check whether the messages have been sent, choose Refresh.


O n l y

The messages should have Sent status.

2010

U s e

P a r t n

e r

1.

I n t e r n a l

O n l y

a)

23

I n t e r n a l

U s e

S A P

P a r t n e r


O n l y

SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

24


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


Exercise 2: Process Integration Exercise Objectives

O n l y

I n t e r n a l

After completing this exercise, you will be able to: • Create and release production orders • Create and send control instructions • Maintain work instructions • Display and send process messages

e r

Business Example

Hint: Complete the exercises on this topic if you want to use routings and production orders.

S A P

S A P

Complete the exercises on the previous topic, Process Management, if you want to use master recipes and process orders.

1.

Create a production order PP-ORDER-## of type PP02 for material T-SCM372-PP-## in plant 1000.

2.

Choose a order quantity of 10 PC and a finish date in the future.

P a r t n

U s e

Task 1:

Release your production order and create the control instructions.

O n l y

I n t e r n a l

e r

Task 2: 1.

Save your order.

Task 3: 1.

In the Process Integration application menu, call the control instructions monitor and select the control instructions created for order PP-ORDER-##. Continued on next page

2010

U s e

P a r t n

You are processing a production order using process integration.


25

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y


2.

SCM372

Send the control instructions online from the monitor. Hint: Choose Send and not Start Send Job.

Find the work instructions belonging to your control instructions by selecting the relevant menu item in the Process Integration application menu.

2.

Access the work instructions for the Work Center 1 operating group in change mode and maintain some of the process steps in the work instructions.

e r

1.

U s e

P a r t n


1.

From the Process Integration application menu, go to the process message monitor and select the process messages created during maintenance of the work instructions.

2.

Send the process messages online from the monitor.

S A P

S A P

Task 5:

P a r t n

U s e

I n t e r n a l

O n l y

Task 4:

e r

I n t e r n a l

Hint: Choose Send Message and not Start Send Job.

O n l y

26


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


Solution 2: Process Integration Task 1: Create a production order PP-ORDER-## of type PP02 for material T-SCM372-PP-## in plant 1000. a)

I n t e r n a l

O n l y

1.

Standard SAP menu:

Material number:

T-SCM372-PP-##

Production plant:

1000

Order type:

PP02

Order:

PP-ORDER-##

U s e

P a r t n

e r

Logistics → Production → Shop Floor Control → Order → Create → With Material

Enter

S A P

S A P

2.

Choose a order quantity of 10 PC and a finish date in the future.

Total quantity:

10 PC

Finish:

Date in the future

P a r t n

U s e

a)

I n t e r n a l

Enter

O n l y

1.

e r

Task 2: Release your production order and create the control instructions.


2010


27

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y


SCM372

Save your order. a)

In the production order: Choose the Release icon Choose the Generate Control Instructions icon

O n l y

Save your entries.

e r

Task 3: In the Process Integration application menu, call the control instructions monitor and select the control instructions created for order PP-ORDER-##. ECC → Logistics → Production → Shop Floor Control → Process Integration → Control Instructions → Monitor Control Instructions/Recipes Plant:

1000


PP-ORDER-##

S A P

S A P

a)

U s e

P a r t n

1.

Enter

U s e

Send the control instructions online from the monitor.

P a r t n

2.

Hint: Choose Send and not Start Send Job. In the monitor, select your control instructions and choose Send. To check whether the control instructions have been sent, choose Refresh.

e r

I n t e r n a l

a)

I n t e r n a l

(or: Choose XSteps / XSteps → Control Instructions/Recipe → Generate)

The control instructions should have Sent status. O n l y


28


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


Task 4: 1.

Find the work instructions belonging to your control instructions by selecting the relevant menu item in the Process Integration application menu. Logistics → Production → Shop Floor Control → Process Integration → Work Instructions → Find Plant:

1000


PP-ORDER-##

e r

Execute (F8) icon Access the work instructions for the Work Center 1 operating group in change mode and maintain some of the process steps in the work instructions.

U s e

P a r t n

2.


S A P

Select the work instructions for the Work Center 1 operating group and choose Change Work Instructions.

S A P

a)

From the Process Integration application menu, go to the process message monitor and select the process messages created during maintenance of the work instructions. Logistics → Production → Shop Floor Control → Process Integration → Process Messages → Message Monitor 1000

Order:

PP-ORDER-##

O n l y

Plant:

Enter


2010


e r

I n t e r n a l

a)

P a r t n

U s e

Task 5: 1.

I n t e r n a l

O n l y

a)

29

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y


2.

SCM372

Send the process messages online from the monitor. Hint: Choose Send Message and not Start Send Job. a)

In the message monitor, select your process messages and choose Send Message. I n t e r n a l

O n l y

To check whether the messages have been sent, choose Refresh.

U s e

P a r t n

e r

The messages should have Sent status.

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

30


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


Lesson Summary

O n l y e r

U s e

P a r t n

I n t e r n a l

You should now be able to: • Explain the functions and flow of process management/process integration • Name the data structures required for process management/process integration • Create and send control recipes/control instructions for process orders/production orders • Maintain PI sheets/work instructions • Send process messages

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

2010


31

I n t e r n a l

U s e

S A P

P a r t n e r

Unit Summary

O n l y

SCM372

Unit Summary

O n l y e r

U s e

P a r t n

I n t e r n a l

You should now be able to: • Explain the functions and flow of process management/process integration • Name the data structures required for process management/process integration • Create and send control recipes/control instructions for process orders/production orders • Maintain PI sheets/work instructions • Send process messages

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

32


2010

e r P a r t n S A P

P a r t n e r

O n l y

S A P P a r t n

U s e

S A P

U s e e r O n l y

I n t e r n a l

U s e

I n t e r n a l

O n l y

I n t e r n a l

e r P a r t n S A P

P a r t n e r

O n l y

S A P P a r t n

U s e

S A P

U s e e r O n l y

I n t e r n a l

U s e

I n t e r n a l

O n l y

I n t e r n a l

I n t e r n a l

U s e

S A P

P a r t n e r

Unit Summary

O n l y

SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

33


2010

I n t e r n a l

U s e

S A P

P a r t n e r

Unit Summary

O n l y

SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

34


2010

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

Unit 2 O n l y

Unit Overview

e r

This unit shows you how to set up and process control recipes/control instructions.

After completing this unit, you will be able to: •

S A P U s e

e r

I n t e r n a l

Lesson: Control Recipes/Control Instructions – Settings and Processing ... 36 Exercise 3: Control Recipes ................................................... 49 Exercise 4: Control Instructions ............................................... 53

P a r t n

Unit Contents

S A P

• • •

Explain the possible types of control recipe destinations/control instruction destinations Create a control recipe destination/control instruction destination in Customizing Describe how to process control recipes/control instructions Create, send, and monitor control recipes/control instructions for process orders/production orders

U s e

P a r t n

Unit Objectives

I n t e r n a l

Control Recipes/Control Instructions

O n l y

2010


35

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

Unit 2: Control Recipes/Control Instructions

SCM372

Lesson: Control Recipes/Control Instructions – Settings and Processing Lesson Overview O n l y

Lesson Objectives

e r

• • •

Explain the possible types of control recipe destinations/control instruction destinations Create a control recipe destination/control instruction destination in Customizing Describe how to process control recipes/control instructions Create, send, and monitor control recipes/control instructions for process orders/production orders

S A P

S A P

Business Example At your company, you want to use the functions of process management/process integration to process your process orders/production orders.

U s e

Depending on the type of destination, the control recipes/control instructions are:

I n t e r n a l

You then generate and send control recipes/control instructions for an order and monitor the status in the corresponding monitor. Finally, you familiarize yourself with the status sequence of control recipes/control instructions and the corresponding orders.

36


2010

O n l y

In Customizing, you first familiarize yourself with the structure of the destinations for control recipes/control instructions.

e r

•

Displayed in the ECC system as PI sheets/work instructions to be processed interactively Transferred to a process control system through the PI-PCS interface

P a r t n

To do this, you must transfer process instructions for the process orders/production orders to shop floor control using control recipes/control instructions.

•

U s e

•

P a r t n

After completing this lesson, you will be able to:

I n t e r n a l

This lesson describes how to process the settings for control recipes/control instructions.

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y

Lesson: Control Recipes/Control Instructions – Settings and Processing

U s e

P a r t n

e r

O n l y

I n t e r n a l

S A P U s e

• •

2010

Create control recipes/control instructions of an order at different times Create multiple control recipes/control instructions for the same destination for an order


37

O n l y

All control recipes/control instructions of an XStep tree are always generated at the same time. Control recipes/control instructions of different XStep trees can be generated separately, which means that by using multiple XStep trees, you can, for example:

e r

After the order has been released, process management/process integration generates one control recipe/control instruction for each control recipe destination/control instruction destination of an XStep tree.

P a r t n

You define XSteps for process orders/production orders in XStep trees in the underlying master recipes/routings. An XStep tree comprises XSteps and process instructions. A control recipe destination/control instruction destination is defined for each XStep.

S A P

You use XSteps to define structures with which you can describe exactly how a process order/production order is produced. You can use XSteps to control data exchange with external systems or generate interactive PI sheets/work instructions for process operators/machine operators in the production.

I n t e r n a l

Figure 19: XSteps: Generating Control Recipes/Control Instructions

I n t e r n a l

U s e

S A P

P a r t n e r


O n l y

SCM372

Depending on the destination type, the control recipes/control instructions are displayed internally in the ECC system as PI sheets/work instructions or are transferred to an external system through the PI-PCS interface.

O n l y e r

U s e

P a r t n

I n t e r n a l

A context (order, operation, or phase) is also defined for each XStep. A context object (for example, a certain phase or operation) can be assigned to any number of XSteps. As a result, the same context objects can be used more than once in different control recipes/control instructions, and therefore also in different PI sheets/work instructions of an order.

You define control recipe destinations/control instruction destinations in Customizing.

e r

I n t e r n a l

The destination types shown in the above figure are available when you use XSteps.

P a r t n

U s e

S A P

S A P

Figure 20: XSteps: Control Recipe Destinations/Control Instruction Destinations

O n l y

38


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


U s e

P a r t n

e r

O n l y

I n t e r n a l

S A P

•

•

P a r t n

Activate the digital signature and specify whether signature strategies are required for particular process steps or if deviations occur Activate a log for particular process steps

The following types of signatures are supported in PI sheets/work instructions: Signature without password check: You do not need special authorization to enter this type of signature in the PI sheet/work instructions. The system does not check the signature you entered. Digital signatures: This type of signature ensures the unique and forgery-proof identification of a user and the logging of the signed operation. There are two SAP signature methods: System Signature with Authorization by User/Password and User Signature with Ext. Security Product (for example, a card reader). If the control recipe destination/control instruction destination is an external system, you can set the Creation with XSteps indicator in the detailed data.

2010


39

O n l y

•

e r

I n t e r n a l

•

S A P

For destinations with control recipes/control instructions that are to be displayed as PI sheets/work instructions, you can also:

U s e

Figure 21: XSteps: Destination Details

I n t e r n a l

U s e

S A P

P a r t n e r


O n l y

SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 22: XSteps: "External System" Destination Type S A P

S A P

As soon as at least one control recipe/control instruction has been created for a destination, process management/process integration sends all existing control recipes/control instructions for this destination.

U s e

•

BAPIs with synchronous RFCs can also be used to enable communication between ECC and the process control systems.

40


2010

O n l y

Thanks to the RFC technology, the application is completely free of communication handling on the ECC level. The tRFC ensures that each call is executed only once. The sequence of the calls is not changed. If the target system is not active when the call takes place, the RFC is repeated according to a repetition rate and duration that can be set by the user.

e r

I n t e r n a l

•

P a r t n

From a technical point of view, ECC can communicate with the process control systems through a tRFC (transactional remote function call). The communication partners transfer data using Common Program Interface Communication (CPI-C) based on TCP/IP.

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 23: Monitor for Control Instructions/Control Recipes

S A P U s e


•

Send control recipes/control instructions if they are not automatically sent by a background job defined in Customizing Delete control recipes/control instructions: –

2010


41

O n l y

–

When using XSteps, you can only delete control recipes/control instructions if the corresponding orders have been deleted. When using process instructions maintained by phase in process orders, you can delete control recipes as soon as they have been discarded, terminated, or exited.

e r

I n t e r n a l

•

P a r t n

From the monitor, you can call different logs that provide more detailed information on the individual process steps and any errors that may have occurred.

S A P

You can obtain information about the current processing status of a control recipe/control instruction by navigating to the monitor for control instructions/control recipes.

I n t e r n a l

U s e

S A P

P a r t n e r


O n l y

SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 24: XSteps: Recipe/Instruction Status and Order Status

S A P

The PI_CRST message category is used for both process orders and production orders.

U s e

(*) An order has status XSez only if at least one control recipe/control instruction of the order has the status Created or Sent.

42


2010

O n l y

I n t e r n a l

Order status XSez: Control recipe in process Order status XSgn: XStep generated Order status XSpr: Control recipe created

e r

• • •

P a r t n

The figure above shows the status sequence of a control recipe/control instruction together with the corresponding order status when XSteps are used. Process orders and production orders can have one of the following statuses:

S A P

Process messages of category PI_CRST are used to update the statuses of control recipes/control instructions and the corresponding orders.

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


S A P U s e

(Remember: If you are using XSteps, multiple control recipes can be generated for a control recipe destination).

O n l y

A phase can be assigned to one control recipe only. (Remember: If you are using XSteps, a phase can be assigned to multiple control recipes and, therefore, also to multiple PI sheets).

2010


e r

I n t e r n a l

For each order, one control recipe is created for the control recipe destination.

P a r t n

After a process order or the relevant phases are released, the process instructions stored in the order are grouped into control recipes and transferred to process management.

S A P

In all releases there is an older, alternative method of maintaining process instructions for process orders whereby the process instructions and control recipe destinations are assigned to the phases of the master recipe/process order. One control recipe destination and any number of process instructions can be assigned to each phase. A control recipe destination can be assigned to multiple phases.

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 25: Process Instruction Maintenance by Phase: Creating Control Recipes

43

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y


SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

You define control recipe destinations in Customizing. The control recipe destination specifies:

For destinations with control recipes that are to be displayed as a PI sheet, you can also:

e r

U s e

To where a control recipe is to be transferred (for example, to an operating group that maintains PI sheets or a specific process control system) How the data is to be transferred (for example, initiated by ECC or the process control system) Which process instructions are to be generated automatically if a control recipe is created for a destination

P a r t n

• •

• •

Activate the digital signature and specify whether signature strategies are required for particular process steps Activate a log for particular process steps

If a control recipe destination is an external system, you can assign the process instruction categories defined for this system to the destination. When you maintain process instructions for a control recipe destination in the master recipe or process order, the system offers as possible entries only those process instruction categories that are assigned to the control recipe destination.


2010

O n l y

I n t e r n a l

•

44

S A P

S A P

Figure 26: Process Instruction Maintenance by Phase: Control Recipe Destinations

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


S A P

S A P

The following types of signatures are supported in the PI sheet: •

Signature without password check:

U s e

Signatures with a simple password check (for type 1 Transfer to ABAP list-based PI sheet only):

You assign plant-specific user passwords in Customizing for the control recipe destination. •

Digital signatures: This type of signature ensures the unique and forgery-proof identification of a user and the logging of the signed operation. There are two SAP signature methods: System Signature with Authorization by User/Password and User Signature with Ext. Security Product (for example, a card reader). Digital signature strategies may be requested for certain activities.

2010


45

O n l y

I n t e r n a l

e r

In this case, you must enter a user name as the signuture and an application-specific password in the PI sheet.

P a r t n

You do not need a special authorization to enter this type of signature in the PI sheet. The system does not check the signature you entered. •

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 27: Process Instruction Maintenance by Phase: "PI Sheet" Destination Type

I n t e r n a l

U s e

S A P

P a r t n e r


O n l y

SCM372

You can activate the logging of particular operations for the browser-based PI sheet.

U s e

P a r t n

e r

O n l y

I n t e r n a l

S A P

S A P

Figure 28: Process Instruction Maintenance by Phase: "External System" Destination Type

U s e

•

• •

46

Thanks to the RFC technology, the application is completely free of communication handling on the ECC level. The tRFC ensures that each call is executed only once. The sequence of the calls is not changed. If the target system is not active when the call takes place, the RFC is repeated according to a repetition rate and duration that can be set by the user.


2010

O n l y

From a technical point of view, ECC can communicate with the process control systems through a tRFC (transactional remote function call). The communication partners transfer data using Common Program Interface Communication (CPI-C) based on TCP/IP.

e r

I n t e r n a l

•

As soon as at least one control recipe has been created for a destination, process management sends all existing control recipes for this destination. Process management informs a destination about each new control recipe created. Depending on the destination, individual control recipes or all existing control recipes can be requested.

P a r t n

Depending on the destination type, control recipes can be sent to process control systems as follows:

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


BAPIs with synchronous RFCs can also be used to enable communication between ECC and the process control systems.

U s e

e r

I n t e r n a l

P a r t n

Process messages of category PI_CRST are used to update the statuses of control recipes and the corresponding orders.

S A P

S A P

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 29: Process Instruction Maintenance by Phase: Control Recipe Status and Order Status

O n l y

2010


47

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y


SCM372

The figure above shows the status sequence of a control recipe together with the corresponding order status. The statuses have the following meaning: •

Control recipe created order status, Created or Sent control recipe status: The control recipe is created. The corresponding process instructions are locked and cannot be changed.

O n l y

Order status Control recipe discarded, control recipe status Discarded: The control recipe cannot be processed. It is discarded before the start of its execution. You can change the process instructions and then generate a new control recipe.

e r

•

Control recipe finished order status, Terminated control recipe status:

P a r t n

•

Control recipe finished order status, Processed control recipe status: Execution of the control recipe has been completed. The corresponding process instructions remain locked.

U s e

The execution of the control recipe has been started but cannot be completed. You can no longer change the corresponding process instructions. If a new control recipe is required, you can maintain new process instructions.

I n t e r n a l

•

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

48


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


Exercise 3: Control Recipes Exercise Objectives

Business Example You are defining control recipe destinations in Customizing.

U s e

P a r t n

e r

Hint: Complete the exercises on this topic if you want to use master recipes and process orders. Complete the exercises on the following topic, Control Instructions, if you want to use routings and production orders.

Task: Defining and Setting Up Control Recipe Destinations

S A P U s e I n t e r n a l

00 to 09

0A to 9A

10 to 19

0B to 9B

20 to 29

0C to 9C

30

0D

00 to 09

0E to 9E

10 to 19

0F to 9F

20 to 29

0G to 9G

30

0H

Description/Address

GR## PI 1/GR## PI Sheet 1


Specify the following properties for the control recipe destinations: –

Destination type: 4 Transfer to browser-based PI sheet

–

A digital signature is required when you enter a signature in the PI sheet. Continued on next page

2010


49

O n l y

Control Recipe Destinations t  o Be Created

e r

Exercise Groups

P a r t n

Create the following control recipe destinations for PI sheets for plant 1100 in Customizing:

S A P

1.

I n t e r n a l

O n l y

After completing this exercise, you will be able to: • Define and set up control recipe destinations

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

SCM372

–

Select Log with a Digital Signature for the Activate/Deactivate operations.

–

Select No Log for the Lock/Unlock operations.

–

Select Log Without Signature for the Complete and Value Entry operations.

Copy control recipe destinations if possible.

Exercise Groups


00 to 09

0I to 9I

10 to 19

0J to 9J

20 to 29

0K to 9K

30

0L

Description/Address

GR## PCS / GR## Process Control System

As the destination type, select: 2 Download to ext. system, initiated by SAP process management.

e r

I n t e r n a l

U s e

P a r t n

Set the Creation with XSteps indicator.

S A P

S A P

Create the following control recipe destinations for an external system for plant 1100 in Customizing.

U s e

P a r t n

e r

2.

I n t e r n a l

O n l y


O n l y

50


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


Solution 3: Control Recipes Task: Defining and Setting Up Control Recipe Destinations

S A P


00 to 09

0A to 9A

10 to 19

0B to 9B

20 to 29

0C to 9C

30

0D

00 to 09

0E to 9E

10 to 19

0F to 9F

20 to 29

0G to 9G

30

0H

Description/Address



U s e

–

A digital signature is required when you enter a signature in the PI sheet.

–


–


–


O n l y

I n t e r n a l

Destination type: 4 Transfer to browser-based PI sheet

e r

–


2010


P a r t n

Specify the following properties for the control recipe destinations:

S A P

Exercise Groups

U s e

P a r t n

e r

Create the following control recipe destinations for PI sheets for plant 1100 in Customizing:

I n t e r n a l

O n l y

1.

51

I n t e r n a l

U s e

S A P

P a r t n e r


O n l y

SCM372

Copy control recipe destinations if possible. a)

SAP Customizing Implementation Guide: Production Planning for Process Industries → Process Management → Control Recipes/PI Sheets → Control Recipe Destinations → Define and Set Up Control Recipe Destinations (for plant 1100)

O n l y

Double-click a destination to maintain its details. Create the following control recipe destinations for an external system for plant 1100 in Customizing.

S A P


00 to 09

0I to 9I

10 to 19

0J to 9J

20 to 29

0K to 9K

30

0L

Description/Address



U s e

See previous exercise

e r

I n t e r n a l

a)

P a r t n


S A P

Exercise Groups

U s e

P a r t n

e r

2.

I n t e r n a l

Choose New Entries to create a control recipe destination.

O n l y

52


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


Exercise 4: Control Instructions Exercise Objectives

Business Example You are defining control instruction destinations in Customizing.

U s e

P a r t n

e r

Hint: Complete the exercises on this topic if you want to use routings and production orders. Complete the exercises on the previous topic, Control Recipes, if you want to use master recipes and process orders.

Task: Defining and Setting Up Control Instruction Destinations

S A P U s e I n t e r n a l

00 to 09

0A to 9A

10 to 19

0B to 9B

20 to 29

0C to 9C

30

0D

00 to 09

0E to 9E

10 to 19

0F to 9F

20 to 29

0G to 9G

30

0H

Description/Address

GR## WI 1/GR## Work Instruction 1



2010


53

O n l y

Control Instruction Destinations to Be Created

e r

Exercise Groups

P a r t n

Create the following control instruction destinations for work instructions for plant 1000 in Customizing:

S A P

1.

I n t e r n a l

O n l y

After completing this exercise, you will be able to: • Define and set up control instruction destinations

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y


SCM372

–

Destination type: 4 Transfer to browser-based work instruction

–

A digital signature is required when you enter a signature in the work instruction.

–


–


–


e r

Copy control instruction destinations if possible.

S A P


00 to 09

0I to 9I

10 to 19

0J to 9J

20 to 29

0K to 9K

30

0L

Description/Address



e r

I n t e r n a l


P a r t n

Exercise Groups

S A P

U s e

Create the following control instruction destinations for an external system for plant 1000 in Customizing.

U s e

P a r t n

2.

I n t e r n a l

O n l y

Specify the following properties for the control instruction destinations:

O n l y

54


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


Solution 4: Control Instructions Task: Defining and Setting Up Control Instruction Destinations

e r P a r t n S A P

00 to 09

0A to 9A

10 to 19

0B to 9B

20 to 29

0C to 9C

30

0D

00 to 09

0E to 9E

10 to 19

0F to 9F

20 to 29

0G to 9G

30

0H

Description/Address




–

A digital signature is required when you enter a signature in the work instruction.

–


–


–


O n l y

Destination type: 4 Transfer to browser-based work instruction

e r

–

P a r t n

Specify the following properties for the control instruction destinations:


2010


S A P


U s e

Exercise Groups

I n t e r n a l

Create the following control instruction destinations for work instructions for plant 1000 in Customizing:

O n l y

1.

55

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y


SCM372

Copy control instruction destinations if possible. a)

SAP Customizing Implementation Guide: Production → Shop Floor Control→ Integration → Process Integration → Control Instructions/Work Instructions→ Destination of Control Instructions → Define and Set Up Control Instruction Destinations (for plant 1000)

O n l y

Double-click a destination to maintain its details. Create the following control instruction destinations for an external system for plant 1000 in Customizing.

S A P


00 to 09

0I to 9I

10 to 19

0J to 9J

20 to 29

0K to 9K

30

0L

Description/Address



U s e

See previous exercise

e r

I n t e r n a l

a)

P a r t n


S A P

Exercise Groups

U s e

P a r t n

e r

2.

I n t e r n a l

Choose New Entries to create a control instruction destination.

O n l y

56


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


Lesson Summary

O n l y e r

U s e

P a r t n

I n t e r n a l

You should now be able to: • Explain the possible types of control recipe destinations/control instruction destinations • Create a control recipe destination/control instruction destination in Customizing • Describe how to process control recipes/control instructions • Create, send, and monitor control recipes/control instructions for process orders/production orders

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

2010


57

I n t e r n a l

U s e

S A P

P a r t n e r

Unit Summary

O n l y

SCM372

Unit Summary

O n l y e r

U s e

P a r t n

I n t e r n a l

You should now be able to: • Explain the possible types of control recipe destinations/control instruction destinations • Create a control recipe destination/control instruction destination in Customizing • Describe how to process control recipes/control instructions • Create, send, and monitor control recipes/control instructions for process orders/production orders

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

58


2010

e r P a r t n S A P

P a r t n e r

O n l y

S A P P a r t n

U s e

S A P

U s e e r O n l y

I n t e r n a l

U s e

I n t e r n a l

O n l y

I n t e r n a l

e r P a r t n S A P

P a r t n e r

O n l y

S A P P a r t n

U s e

S A P

U s e e r O n l y

I n t e r n a l

U s e

I n t e r n a l

O n l y

I n t e r n a l

I n t e r n a l

U s e

S A P

P a r t n e r

Unit Summary

O n l y

SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

59


2010

I n t e r n a l

U s e

S A P

P a r t n e r

Unit Summary

O n l y

SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

60


2010

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

Unit 3 O n l y

Unit Overview XSteps – Structure, Elements, and Properties Standard XSteps XSteps for PI Sheets/Work Instructions XSteps for External Systems

U s e

P a r t n

e r

• • • •

I n t e r n a l

XSteps

Unit Objectives After completing this unit, you will be able to:

S A P U s e

2010


61

O n l y

Lesson: XSteps – Structure, Elements, and Properties ........................ 63 Lesson: Standard XSteps........................................................... 80 Lesson: Cross-Plant and Multi-Language Standard-XStep-Repository ...... 95 Exercise 5: Cross-plant and Multi-language Standard-Xstep-Repository (optional)......................................................................... 103 Lesson: XSteps for PI Sheets/Work Instructions ............................... 112 Exercise 6: Outputs in PI Sheets ............................................. 147 Exercise 7: Outputs in Work Instructions.................................... 211 Exercise 8: Entries and Calculations in PI Sheets ......................... 275 Exercise 9: Entries and Calculations in Work Instructions ................ 315 Exercise 10: Entries and Process Messages in PI Sheets ............... 355 Exercise 11: Entries and Process Messages in Work Instructions ...... 377 Exercise 12: Function Calls in PI Sheets.................................... 399

e r

I n t e r n a l

Unit Contents

P a r t n

• •

Explain the structure, elements, and properties of XSteps Describe how to use standard XSteps from the standard XStep repository Maintain standard XSteps in the cross-plant standard-XStep-repository and in multiple languages Create XSteps for PI sheets/work instructions Create XSteps for process control systems

S A P

• • •

I n t e r n a l

U s e

S A P

P a r t n e r

Unit 3: XSteps

O n l y

SCM372

Exercise 13: Function Calls in Work Instructions .......................... 415 Lesson: XSteps for Process Control Systems .................................. 432

U s e

P a r t n

e r

O n l y

I n t e r n a l

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

62


2010

I n t e r n a l

U s e

S A P

SCM372

P a r t n e r

O n l y

Lesson: XSteps – Structure, Elements, and Properties

Lesson: XSteps – Structure, Elements, and Properties Lesson Overview

O n l y e r

At your company, you want to use the functions of process management/process integration to process your process/production orders.

After completing this lesson, you will be able to: •

Explain the structure, elements, and properties of XSteps

In XSteps (execution steps), you therefore specify the data structures for defining the structure of control recipes/control instructions and PI sheets/work instructions along with the related process message requests.

S A P U s e

e r

I n t e r n a l

Finally, you familiarize yourself with XStep maintenance for PI sheets/work instructions and external systems.

P a r t n

You then familiarize yourself with the structure, elements, and properties of XSteps and the application of standard XSteps from the standard XStep repository.

S A P

First, you familiarize yourself with the elements and functions of PI sheets/work instructions.

U s e

Business Example

I n t e r n a l

Lesson Objectives

P a r t n

This lesson provides information about the structure, elements, and properties of XSteps.

O n l y

2010


63

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

Unit 3: XSteps

SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

U s e

You define XSteps for process orders/production orders in XStep trees in the underlying master recipes/routings.

I n t e r n a l

64


2010

O n l y

You can create multiple XStep trees in a master recipe/routing and use them in a process order/production order (for more information, see the Control Recipes/Control Instructions unit).

e r

An XStep tree can comprise XSteps, process instructions, and standard XStep references. An XStep in an XStep tree can, in turn, comprise further XSteps, SXS references, and XStep process instructions.

P a r t n

You use XSteps to define structures with which you can describe exactly how a process order/production order is produced. You can use XSteps to control data exchange with external systems or create interactive PI sheets/work instructions for process operators/machine operators in the production.

S A P

S A P

Figure 30: XSteps - Definition and Structure

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 31: Elements of an XStep Tree

S A P

2010


65

O n l y

•

e r

I n t e r n a l

•

XSteps: An XStep can contain additional, subordinate XSteps. Properties of the superordinate XSteps, such as scope of generation, control recipe destination, and XStep context, are inherited by the subordinate XSteps as long as the properties specified are not explicitly defined in these subordinate XSteps. For example, if you have defined the Order XStep context in the superordinate XStep, this also applies to all subordinate XSteps until an XStep is reached for which a different XStep context has been defined. SXS references: An XStep can reference versions of a standard XStep. Standard XSteps are managed in the SXS repository. If you explode the reference, the system creates a copy of the valid version of the standard XStep in your XStep tree for the key date. XStep process instructions: You use process instructions to define outputs, entries, and control functions such as function calls and process messages for an XStep.

P a r t n

U s e

•

S A P

You can create the following elements under an XStep tree:

I n t e r n a l

U s e

S A P

P a r t n e r

Unit 3: XSteps

O n l y

SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 32: Elements of an XStep Tree (Example)

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

Figure 33: Properties of an XStep - General

For each XStep, you can specify properties that define the XStep in more detail.

66


2010

I n t e r n a l

U s e

SCM372

S A P

P a r t n e r

O n l y


General tab page: This tab page displays information about the properties, the status of the control recipe/control instruction, and administration data.

S A P

S A P

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 34: Properties of an XStep - Parameters

For every XStep parameter, you must specify whether it should:

e r

• • • • •

2010

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) Exchange a value with a higher-level XStep (category Exchange) Exchange a value with a subordinate XStep (category Exchange, Local)


67

O n l y

I n t e r n a l

For each XStep, you define parameters for contents with values that are not yet known or changeable. The XStep parameters are only valid for the XStep in which they have been defined, that is, they do not apply to subordinate or superordinate XSteps. If you want to use the values of these XStep parameters in a subordinate or superordinate XStep, you must forward them using a reference.

P a r t n

U s e

Parameters tab page:

I n t e r n a l

U s e

S A P

P a r t n e r

Unit 3: XSteps

O n l y

SCM372

You define the data type of a parameter by assigning a characteristic with the required format. The characteristic only defines the data type of the XStep parameter. It can, therefore, be used multiple times.

O n l y e r

U s e

P a r t n

I n t e r n a l

Caution: Note that some business characteristics (such as PPPI_MATERIAL or PPPI_BATCH) contain input help and input validation. In the PI sheet/work instruction, input fields for which such characteristics are assigned as the data type can only be filled with a permitted value.

P a r t n

U s e

S A P

S A P

Figure 35: Properties of an XStep - Valuation

O n l y

I n t e r n a l

e r

On the Valuation tab page, you specify a valuation type for each XStep parameter and, if necessary, you enter a value and a valuation symbol.

68


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


Depending on the category selected, you can valuate XStep parameters as follows: •

P a r t n

S A P

LIVE Parameter: You valuate using a live parameter when you want to exchange data between two different PI sheets/work instructions. In this case, you must set the LIVE Parameter indicator in the XStep parameter of both XSteps.

U s e

•

S A P

e r

•

I n t e r n a l

O n l y

•

None: The XStep parameter is not to be valuated, or is not to be valuated until a later processing stage. Automatically: The value of the XStep parameter is to be determined automatically by the system when a control recipe/control instruction is generated. Here, you must specify a valuation symbol. Depending on the current XStep context, the application automatically replaces the valuation symbols with concrete values. You can specify, for example, that the number of the header material is to be valuated automatically. Fixed Value: You define a fixed value. In addition, you can also specify a valuation symbol. This is useful, for example, if you want the system to automatically valuate a material number with the corresponding material description in the PI sheet/work instructions. Reference: You valuate an XStep parameter with the value of a different XStep parameter. When doing so, you can only reference XStep parameters that you have already defined in the subordinate or superordinate XStep. As a valuation, you specify an XStep parameter from the subordinate or superordinate XStep whose value is to be copied over into the current XStep parameter. Note that the categories of the two XStep parameters must be identical.

e r

I n t e r n a l

U s e

P a r t n O n l y

Figure 36: Data Flow Between XSteps (Reference Valuation)

2010


69

I n t e r n a l

U s e

S A P

P a r t n e r

Unit 3: XSteps

O n l y

SCM372

Data exchange is only possible between XSteps of the same XStep tree. Within an XStep tree, the context of one XStep is not dependent on another. This means, for example, that identical parameter names can be used in different XSteps of an XStep tree without causing conflicts.

•

You define XStep parameters as input parameters, output parameters, or exchange parameters if you want to exchange with other XSteps of the same XStep tree. The system writes these XStep parameters to the parameter interface of the XStep. You define XStep parameters as local parameters if you want to use them within the same XStep or forward them to the XStep directly below in the hierarchy.

e r P a r t n

Parameter values are exchanged through a reference valuation.

U s e

You can exchange data directly between XSteps only if one is directly above or below the other in the hierarchy. If you want to exchange data between two XSteps that are on the same hierarchy level, you must first transfer the parameter value to a local parameter of the superordinate XStep, so that it can then be read by an input parameter of the subordinate XStep (see figure).

I n t e r n a l

O n l y

•

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

Figure 37: Permitted Valuation Types and Categories

Permitted valuation types for categories: Depending on the category you have defined for an XStep parameter, only certain valuation types are permitted. The figure above provides an overview of which combinations can be used.

70


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


Permitted categories for parameter references: If you have defined an XStep parameter to be assigned a value through a reference to another XStep parameter, the categories of the XStep parameters (subordinate and superordinate) must match. The figure above provides an overview of which combinations can be used.

S A P

S A P

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 38: Properties of an XStep - Generation

U s e

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.

e r O n l y

I n t e r n a l

•

P a r t n

Generation tab page: On this tab page, you assign a scope of generation (for example, For All Reservation Items) to the XStep.

2010


71

I n t e r n a l

U s e

S A P

P a r t n e r

Unit 3: XSteps

O n l y

SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 39: XStep Generation: Example 1

Example

e r

S A P U s e

O n l y

I n t e r n a l

•

P a r t n

•

The control recipe/control instruction is to contain information about the material components used. These are entered in the material list for the order. The system can, therefore, automatically create the corresponding XSteps and fill them with all the material data. To do this, you define an XStep with scope of generation For all Ingredients, which is used as the template for the XSteps to be created. For this XStep, you maintain all required parameters (for example, a parameter to output the material description) and the context in which the generation is to be executed. During the generation process, the system creates a copy of the template automatically for each material component and valuates the parameters using the data of the respective material that is contained in the material list.

S A P

•

72


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 40: XStep Generation: Example 2

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

2010


73

I n t e r n a l

U s e

S A P

P a r t n e r

Unit 3: XSteps

O n l y

SCM372

Features •

Execution of XStep generation You can trigger the generation of XSteps as follows:

e r P a r t n

–

S A P

•

As soon as the generation has been executed, manual maintenance is restricted, which means that you can no longer maintain data that requires the XStep tree to be generated again. These restrictions also apply when new XSteps are inserted. System activities after the generation has been deleted If a control recipe/control instruction in an XStep tree is not productive, you can delete the generation for the XStep tree. In doing so, the system: 1. Resets all exploded SXS references 2. Deletes all copies 3. Deletes all valuations for parameters that are to be valuated automatically

e r O n l y

I n t e r n a l

–

P a r t n

U s e

–

S A P

•

The system carries out the following activities during the generation process: 1. SXS references that have not yet been exploded are exploded 2. Templates are copied 3. Parameters that are to be valuated automatically are assigned values Restrictions after the generation process

U s e

•

When creating a control recipe/control instruction: In this case, the system triggers the generation automatically. The generated XSteps are inserted into the order. – When maintaining the XSteps in the XStep editor: If you want to check and, if necessary, change the generated XSteps before creating the control recipe/control instruction, you can trigger the generation in the process order manually. During this process, repetitions and parameter valuations are fixed, which means that subsequent changes to the order data are not taken into account in the XStep tree. To refresh the data, you must execute the Delete Generation function and repeat the generation. System activities during the generation process

I n t e r n a l

O n l y

–

74


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 41: Properties of an XStep - Destination

S A P

S A P

Destination tab page: On this tab page, you assign the XStep a destination type (external system or PI sheet/work instructions) or a concrete control recipe destination/control instruction destination. The destination is inherited down the XStep tree until a new concrete destination is found. The inheritance hierarchy then starts again from this concrete destination.

e r

I n t e r n a l

U s e

P a r t n O n l y

2010


75

I n t e r n a l

U s e

S A P

P a r t n e r

Unit 3: XSteps

O n l y

SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 42: Properties of an XStep - Context

S A P

S A P

Context tab page: On this tab page, you specify whether the XStep is to apply to the entire order, a certain operation, or a certain phase. The system requires the XStep context, for example, when generating XSteps and assigning values automatically. As with the destination, the context is inherited down the XStep tree until a new context is found. The inheritance hierarchy then starts again from this new context.

e r

I n t e r n a l

U s e

P a r t n O n l y

76


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 43: XStep Process Instructions

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

Figure 44: XStep Process Instructions for PI Sheets/Work Instructions

2010


77

I n t e r n a l

U s e

S A P

P a r t n e r

Unit 3: XSteps

O n l y

SCM372

For destination type PI Sheet/Work Instructions, you define XStep process instructions for PI sheets/work instructions that are to be processed by process operators/machine operators. You maintain the elements of a process instruction using the context menu.

S A P

S A P

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 45: XStep Process Instructions for External Systems

U s e

•

e r

•

78

If the “Creation with XSteps” indicator is set for the destination, do not maintain any process instructions. In this case, the control recipes/control instructions are generated from the XStep parameters. If the “Creation with XSteps” indicator is not set, maintain the information for the external system in the characteristic overview of process instructions. For some external systems, you may also need to specify a process instruction type and a process instruction category.


2010

O n l y

I n t e r n a l

(*) Whether you have to maintain process instructions for the XStep depends on the Customizing settings for the destination:

P a r t n

You create XStep process instructions for external systems for destination type External System (type 2: Download to ext. system, initiated by SAP process management).

I n t e r n a l

U s e

SCM372

S A P

P a r t n e r

O n l y


Lesson Summary You should now be able to: • Explain the structure, elements, and properties of XSteps

U s e

P a r t n

e r

O n l y

I n t e r n a l

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

2010


79

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

Unit 3: XSteps

SCM372

Lesson: Standard XSteps Lesson Overview O n l y

I n t e r n a l

This lesson provides information about using standard XSteps.

Lesson Objectives After completing this lesson, you will be able to:

e r

•

Describe how to use standard XSteps from the standard XStep repository

At your company, you want to use the functions of process management/process integration to process your process/production orders.

S A P


U s e

e r

I n t e r n a l

Finally, you familiarize yourself with XStep maintenance for PI sheets/work instructions and for external systems.

P a r t n

You then familiarize yourself with the structure, elements, and properties of XSteps and the application of standard XSteps from the standard XStep repository.

S A P

In XSteps (execution steps), you therefore specify the data structures for defining the structure of control recipes/control instructions and PI sheets/work instructions along with the related process message requests.

U s e

P a r t n

Business Example

O n l y

80


2010

I n t e r n a l

U s e

S A P

P a r t n e r

SCM372

O n l y

Lesson: Standard XSteps

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 46: Standard XSteps: Use and Structure

e r

S A P I n t e r n a l

•

Standard XSteps are XSteps that you create as master data in the standard XStep repository (SXS repository). You can reuse standard XSteps by creating a reference to them in the SXS repository from an application (master recipe, routing, process order, production order, or standard XStep). Using references to standard XSteps (SXS references) considerably reduces the effort required to maintain data. If standardized process flows change, for example, these changes do not have to be made in each individual master recipe. Instead, you make the changes centrally in the SXS repository. All master recipes that contain references to these standard XSteps are changed automatically.

P a r t n

U s e

•

S A P

Use

Structure of a Standard XStep

2010

A standard XStep can comprise multiple versions. Each version contains an XStep tree. You create XSteps within the XStep tree, which describe the exact contents of the standard XStep.


81

O n l y

•

I n t e r n a l

U s e

S A P

P a r t n e r

Unit 3: XSteps

O n l y

SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 47: Standard XSteps: Versioning

S A P

•

e r

U s e

O n l y

I n t e r n a l

P a r t n

• •

You can create multiple versions of a standard XStep with different validity periods. Only one version of a standard XStep can be valid at any one time. If you explode an SXS reference from an application (for example, in the order when generating a control recipe/control instructions) or in the SXS repository itself, the system searches for the SXS version that is valid and released on the key date (that is, with the status Released or Released for Test). You can then choose any name for the version. The version names are only unique within a standard XStep.

S A P

Use

82


2010

I n t e r n a l

U s e

S A P

P a r t n e r

SCM372

O n l y


Automatic Number Assignment •

U s e

P a r t n

e r

•

I n t e r n a l

O n l y

•

In Customizing, you can specify that numbers are to be assigned automatically to the versions of a standard XStep. The first new version of a standard XStep is assigned the number 0001. If multiple versions of a standard XStep already exist, the system selects the newest version. If the key of the newest version comprises numbers, the system increases the number by one. If the system does not find any valid preceding numbers, it assigns the number 0001. If you have activated the automatic number assignment function, you cannot change the version numbers manually. If you want to change the version numbers manually, you must first undo the Customizing setting.

S A P

S A P e r

I n t e r n a l

U s e

P a r t n

Figure 48: Automatic Calculation of the Validity Period

O n l y

2010


83

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

Unit 3: XSteps

SCM372

Automatic Calculation of the Validity Period •

•

e r

–

• The valid-to date of the earlier version is changed to one day before the valid-from date of the new version. • The valid-to date of the new version is changed to one day before the valid-from date of the later version.

S A P

S A P

– –

U s e

P a r t n

–

If the valid-from date of the new version lies before the valid-from date of the old version, the valid-to date of the new version is changed to one day before the valid-from date of the new version. If a new version is released with a validity period that lies between those of two released versions, the above rule also applies:

I n t e r n a l

O n l y

•

In Customizing, you can specify that the system is to determine the valid-to date of a version. You cannot then enter the valid-to date manually. Only one version of a standard XStep can be valid at any one time. 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 already existed previously, the validity period of this version is limited to the valid-from date of the new version. Note the following points:

The date of the new version cannot not lie before the current date. The new and old versions cannot have the same valid-from date.

e r

I n t e r n a l

U s e

P a r t n O n l y

Figure 49: SXS Version: Simple Status Management

84


2010

I n t e r n a l

U s e

S A P

P a r t n e r

SCM372

O n l y


Use •

e r

U s e

P a r t n

I n t e r n a l

O n l y

•

Each version of a standard XStep (SXS version) is assigned a status. The current status of an SXS version determines which business activities can be carried out for the version. In addition to the official approval procedure for standard XStep versions described later, a simple status management procedure also exists, which is described here first. You can use this status management procedure only if you are not working in an environment in which approvals are mandatory, since status changes cannot be fully documented and restricted to authorized persons.

P a r t n

U s e

S A P

S A P

The table above shows which operations can be performed depending on the status of an SXS version. For more detailed information, see the current version of the documentation at help.sap.com.

•

Status Released for Test: The version 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. Status Released: Limited changes are permitted (for example, a parameter description). The XStep tree of a version can still be changed, but you can no longer change the category of an XStep parameter, for example.

You can check and simulate all XSteps in the standard XStep repository regardless of their status.

2010


85

O n l y

•

e r

I n t e r n a l

Figure 50: SXS Version: Simple Status Management II

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

Unit 3: XSteps

SCM372

An archived version is still displayed in the standard XStep repository.

U s e

P a r t n

e r

O n l y

I n t e r n a l S A P

S A P

Figure 51: SXS Version: Approval Procedure

Use

U s e

•

•

86

In Customizing, you have made the settings for the digital signature, set the SXS Version: Approval Procedure Active indicator, and specified whether a simple signature or a signature strategy for which multiple persons have signature authorization is to be used to set the Released, Approved, or Obsolete, Discarded statuses.


2010

O n l y

Prerequisites

e r

I n t e r n a l

•

The approval procedure for standard XSteps includes the monitored status management procedure and the digital signature for certain statuses so that changes to a version can be documented comprehensively. You can specify that a digital signature is required to set the Released, Approved and Obsolete, Discarded statuses. These statuses can then only be assigned by persons with signature authorization. In production, you can only use released and approved standard XStep versions. You cannot make any changes to released and approved standard XStep versions. If you need to make changes, you must create a copy of this standard XStep version and discard the original version.

P a r t n

•

I n t e r n a l

U s e

S A P

P a r t n e r

SCM372

O n l y


Approval Procedure with Signature Strategy • •

O n l y

U s e

P a r t n

e r

•

I n t e r n a l

•

If you use signature strategies, the Running Signature Process status is used to show that the approval procedure is in process. The Running Signature Process status only allows you to continue the process that has started, that is, either the approval and release of an XStep or the discarding of an XStep. You can terminate the signature process. The XStep is then assigned the status it had before the signature process started. Once the last required signature has been provided, the Released, Approved or Obsolete, Discarded status is set.

S A P

S A P e r

The figure above shows which operations are allowed during the approval procedure depending on the status of an SXS version. For more detailed information, see the current version of the documentation at help.sap.com. The way this procedure differs from simple status management is highlighted in the figure above. (*) If you want to change released, approved XStep versions, you must copy these versions and use them as a template. Discard the old version and assign the Released, Approved status to the new version.

2010


87

O n l y

I n t e r n a l

U s e

P a r t n

Figure 52: SXS Version: Approval Procedure II

I n t e r n a l

U s e

S A P

P a r t n e r

Unit 3: XSteps

O n l y

SCM372

P a r t n

At the standard XStep level, you can generate a where-used list using the context menu. The where-used list checks whether the standard XStep is referenced in process orders, production orders, recipes, standard routings, or in the XStep repository.

U s e

S A P

e r

O n l y

I n t e r n a l

Figure 53: Standard XSteps: Where-Used List

U s e

88


2010

O n l y

•

You can display the routing or order by double-clicking the symbol in the Application column. If you double-click a referenced standard XStep, the system navigates to the position in the standard XStep repository where the standard XStep is used. You can display the details for an order status by double-clicking the entry in the Order Status column.

e r

I n t e r n a l

•

P a r t n

Navigating to applications:

S A P

The result of the where-used list is shown as a table in the lower screen area of the XStep repository.

I n t e r n a l

U s e

S A P

P a r t n e r

SCM372

O n l y


U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 54: SXS References and Parameterization

S A P U s e

XStep parameters on the interface of the standard XStep:

•

2010


89

O n l y

•

If the version of a standard XStep is released or released for testing, the system automatically copies all XStep parameters of type Input, Output, and Exchange that are defined at the highest node in the XStep tree to the parameter interface of the standard XStep. Local XStep parameters are not affected by this. The XStep parameters remain at the interface of the standard XStep even if they are deleted after the version is released, or if the version no longer has status Released. After releasing an XStep, you must not make any further changes to these XStep parameters. If you have to make changes, these must be compatible, that is, the categories of the XStep parameters must stay the same. If the standard XStep is referenced, the parameters appear at the parameter interface of the SXS reference and can be valuated.

e r

I n t e r n a l

•

P a r t n

You can parameterize the referenced standard XSteps according to the respective requirements and assign relevant values to the parameters in the different routings/orders.

S A P

You can reference standard XSteps that you have created in the SXS repository in the master recipe, process order, routing, production order, and within another standard XStep.

I n t e r n a l

U s e

S A P

P a r t n e r

Unit 3: XSteps

O n l y

SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 55: Explosion of a Standard SXS Reference

S A P

•

e r O n l y

I n t e r n a l

•

As soon as an SXS reference is exploded in the process order, production order, master recipe, or routing, the system creates a copy of the version that is valid on the key date. The entire original XStep tree of the SXS is visible and can be changed in the master recipe and routing. Whether it can be changed in the order depends on the status of the control recipe/control instruction. In the order, an SXS reference is exploded automatically when the control recipe/control instruction is generated. For SXS references within the SXS repository, fixed values of XStep parameters are not displayed because these can vary depending on the version. The XStep parameter is then classified as non-valuated.

P a r t n

U s e

•

S A P

Explosion of an SXS reference:

90


2010

I n t e r n a l

U s e

S A P

P a r t n e r

SCM372

O n l y


P a r t n

Using the XML-based export and import functions, you can transfer contents from one XStep repository to another. This can be useful, for example, if you want to import data from your test system to your validation or production system.

U s e

S A P

e r

O n l y

I n t e r n a l

Figure 56: Standard XSteps: Export and Import

U s e

Standard XStep folder Standard XStep Standard XStep version XStep tree Individual XStep nodes

e r O n l y

I n t e r n a l

P a r t n

• • • • •

S A P

You can export the following objects of a standard XStep, save them locally, and then import them again:

2010


91

I n t e r n a l

U s e

S A P

P a r t n e r

Unit 3: XSteps

O n l y

SCM372

Conditions for carrying out an import: •

O n l y e r

•

U s e

P a r t n

For more detailed information about exporting and importing standard XSteps, see the documentation at help.sap.com.

I n t e r n a l

•

When importing XML files, the system creates new SXS objects (subtree structures) for the imported XML data. The new objects are assigned, as subobjects, to the repository object you have selected. When doing so, the system checks whether the hierarchical relationship between the objects is taken into account. To be able to reconstruct the exported subtree structures in the target system, you also have to export the data from referenced standard XSteps. When importing XML files, the system checks whether the files contain all information required to reconstruct the SXS referenced in the SXS reference nodes.

S A P

S A P e r

I n t e r n a l

U s e

P a r t n

Use •

92

Sample standard XStep building blocks are available as downloads in the SAP Portal in the SAP Community Network.


2010

O n l y

Figure 57: Standard XSteps Library

I n t e r n a l

U s e

S A P

P a r t n e r

SCM372

O n l y


Activities • •

O n l y

• •

e r

–

–

For more information about this topic, see the BPX Community for Manufacturing at https://www.sdn.sap.com/irj/sdn/bpx-manufacturing.

U s e

P a r t n

–

Flexible Building Blocks for Shop Floor Instruction Sheets – Basic Standard XStep Templates Flexible Building Blocks for Shop Floor Instruction Sheets – Standard XStep Library Flexible Building Blocks for Shop Floor Instruction Sheets – Advanced Standard XStep Templates

I n t e r n a l

•

To access the SAP Community Network, choose https://www.sdn.sap.com in the SAP Portal. Choose "Downloads" from the horizontal menu bar; this takes you to the Download Catalog. Choose Templates, Plug-ins, and Samples / for Manufacturing from the list of available downloads. Choose Core Manufacturing from the list of manufacturing downloads. Finally, choose Click here for download and then the following download links:

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

2010


93

I n t e r n a l

U s e

S A P

P a r t n e r

Unit 3: XSteps

O n l y

SCM372

Lesson Summary You should now be able to: • Describe how to use standard XSteps from the standard XStep repository

U s e

P a r t n

e r

O n l y

I n t e r n a l

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

94


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y

Lesson: Cross-Plant and Multi-Language Standard-XStep-Repository

Lesson: Cross-Plant and Multi-Language Standard-XStepRepository O n l y

This lesson gives a short overview of the cross-plant and multi-language Standard-XStep-Repository available with Business Function LOG_PP_XS_01.

U s e

P a r t n

e r

Hint: The exercise of this lesson is meant to be optional and should not be done before having finished all exercises of lesson XSteps for PI Sheets/Work Instructions.

Lesson Objectives After completing this lesson, you will be able to: Maintain standard XSteps in the cross-plant standard-XStep-repository and in multiple languages

Business Example

e r

U s e

O n l y

I n t e r n a l

P a r t n

You use XSteps and maintain standard XSteps in the SXS-Repository. Previously, you had to create your own standard XSteps for each plant. You can now use a cross-plant repository as the central storage facility for your XSteps instead of the plant-dependent repository. You can create a standard XStep once centrally and then use it in any number of plants. In this way, you can reduce the effort of maintaining master data and thus ensure a standardized way of working in all plants. Furthermore, previously you could create a standard XStep in one language only. It was not possible to translate the texts of a standard XStep into other languages. Now you can translate the texts of a standard XStep into any number of languages.

S A P

S A P

•

I n t e r n a l

Lesson Overview

2010


95

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

Unit 3: XSteps

SCM372

Business Function LOG_PP_XS_01

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 58: Business Function LOG_PP_XS_01

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

Figure 59: XSteps – Cross-Plant Repository and Language Dependency

96


2010

I n t e r n a l

S A P

P a r t n e r

O n l y


I n t e r n a l

O n l y

SCM372

U s e

Figure 60: Customizing

U s e

P a r t n

e r

Cross-plant Standard-XStep-repository

S A P

S A P e r

I n t e r n a l

U s e

P a r t n

Figure 61: XSteps – Cross-Plant Repository: Old Situation

O n l y

2010


97

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

Unit 3: XSteps

SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 62: XSteps – Cross-Plant Repository: New Situation

S A P

S A P

Multi-language Standard-XStep-Repository

e r

I n t e r n a l

U s e

P a r t n O n l y

Figure 63: XSteps – Language Dependency: Translatable Text Elements

98


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 64: XSteps – Language Dependency

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

Figure 65: XSteps – Language Dependency Translation Overview

2010


99

I n t e r n a l

U s e

S A P

P a r t n e r

Unit 3: XSteps

O n l y

SCM372

e r

O n l y

I n t e r n a l

P a r t n

U s e

Figure 66: XSteps – Language Dependency: Technical Lang. vs. Preferred Stand. Language I

S A P

S A P e r

I n t e r n a l

U s e

P a r t n

100


O n l y

Figure 67: XSteps – Language Dependency: Technical Lang. vs. Preferred Stand. Language II

2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 68: XSteps – Language Dependency: Technical Lang. vs. Preferred Stand. Language III

S A P

S A P e r

I n t e r n a l

U s e

P a r t n

2010


101

O n l y

Figure 69: XSteps – Language Dependency: Technical Lang. vs. Preferred Stand. Language IV

I n t e r n a l

U s e

S A P

P a r t n e r

Unit 3: XSteps

O n l y

SCM372

U s e

P a r t n

e r

O n l y

I n t e r n a l

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

102


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


Exercise 5: Cross-plant and Multi-language Standard-Xstep-Repository (optional) Exercise Objectives O n l y

Business Example

Hint: The exercise of this lesson is meant to be optional and should not be done before having finished all exercises of lesson XSteps for PI Sheets/Work Instructions.

S A P U s e

1.

Define Reference Plant for Cross-Plant Standard XStep Repository Plant 1100 has to be defined as reference plant for the following exercises.


2010


103

O n l y

Choose the following Customizing activity (transaction CMX22): (SPRO: SAP Reference IMG: Production Planning for Process Industries → Process Management → Execution Steps (XSteps) → Standard XStep Repository → Define Reference Plant for Cross-Plant Standard XStep Repository)

e r

I n t e r n a l

In a first step you have to define a reference plant in Customizing to activate the cross-plant standard-XStep-repository. The reference plant is a technical aid that is needed only to enable the release of the necessary characteristic groups for process instructions and process messages.

P a r t n

You want to use the cross-plant standard-XStep repository to reduce the effort of maintaining your standard XSteps and thus to ensure a standardized way of working in all plants. In the cross-plant standard-XStep repository you can create standard XSteps once centrally and then use it in any number of plants.

S A P

Task 1:

U s e

P a r t n

e r

You maintain standard-XSteps in the cross-plant standard-XStep-repository and in several languages.

I n t e r n a l

After completing this exercise, you will be able to: • Maintain standard-XSteps in the cross-plant standard-XStep-repository and in several languages.

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

Unit 3: XSteps

SCM372

Task 2: In your ERP system, you find for historical reasons standard XSteps (SXS) in the plant-dependent standard-XStep-repositories (CMXSV) and in the cross-plant standard-XStep-repository (CMXSVN).

O n l y

You also check, that after having defined a reference plant in Customizing, you can only define new SXS References in the XStep editor of your plans with reference to SXS of the cross-plant repository.

To adopt constituents of a plant-dependent repository in the cross-plant repository, you must create this data in the cross-plant repository again. You can use the XML export and import functions for this purpose. Choose transaction CMXSVN (SAP menu: Logistics → Production-Process → Master Data → Cross-Plant Standard-XStep-Repository) to enter the Cross-Plant Standard-XStep-Repository. In the cross-plant repository you find for example a folder DPP65 which contains cross-plant SXS for this training course.

U s e

Choose transaction CMXSV (SAP menu: Logistics → Production-Process → Master Data → Standard XStep Repository) to enter the Standard XStep Repositories for plant 1000 and then for plant 1100.

3.

Choose transaction CA02 (SAP menu: Logistics → Production → Master Data → Routings →Routings → Standard Routings → Display) to change the standard routing for


104


2010

O n l y

You cannot find SXS that have been maintained in the cross-plant repository (CMXSV). For example, you cannot find folder DPP65.

e r

I n t e r n a l

2.

P a r t n

You cannot find SXS that have been maintained in the plant-dependent repositories (CMXSV).

S A P

S A P

1.

U s e

P a r t n

e r

But still existing SXS References which were defined with reference to a plant-dependent repository (CMXSV) before activating the cross-plant repository will remain valid.

I n t e r n a l

You check, that the cross-plant standard-XStep-repository (CMXSVN) is a separated repository. XSteps maintained in the cross-plant repository are not available in the plant-dependent repositories and vice versa.

I n t e r n a l

U s e

SCM372

S A P

P a r t n e r

O n l y


4.

Material:

T-SCM372-PP-##

Plant:

1000

Group counter:

9

Choose symbol XSteps or Goto → XSteps to enter the XStep editor.

O n l y

Choose the context menu for the XStep Tree (right mouse click) and then Create → SXS Reference. Double click the new SXS Reference and go to the Reference tab.

e r

Only SXS of the cross-plant repository can be assigned as reference.

I n t e r n a l

In the XStep editor, create a new SXS Reference:

You have production plants in several countries. Therefore you translate your standard XSteps in several languages.

S A P

You can check in a translation overview what elements of a SXS has not been translated yet

U s e

Choose the following Customizing activity: (SPRO: SAP Reference IMG: Production Planning for Process Industries → Process Management → Execution Steps (XSteps) → Standard XStep Repository → Define Preferred Default Language)

e r

Language EN is defined as preferred language. 2.

For the following exercise steps you have to logon to your ERP system three times: Logon in languages EN (English), DE (German), and FR (French).

3.

For each language: Choose transaction CMXSVN (SAP menu: Logistics → Production-Process → Master Data → Cross-Plant Standard-XStep-Repository) to enter the Cross-Plant Standard-XStep-Repository. Continued on next page

2010


105

O n l y

I n t e r n a l

Define Preferred Default Language

P a r t n

1.

S A P

You normally create SXS in language EN English. Therefore you define language EN as your preferred language in Customizing. Texts that not have been translated in all other languages yet will be displayed in English as default.

U s e

P a r t n

Task 3:

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

Unit 3: XSteps

SCM372

Display the texts of all translatable elements with respect to folder DPP65 in the translation overview. Choose the context menu for folder DPP65 (right mouse click) and then Display Translations.

O n l y

Finally simulate the work instruction / PI sheet for SXS Cross-plant & multi-language example SXS.

U s e

P a r t n

e r

Choose the context menu for the XStep Tree (right mouse click) and then Simulate.

I n t e r n a l

You get an overview of all existing translations in an ALV grid view. A Missing Translation flag is set if a text is maintained for any other language but not for the current language. You can jump to an element to be translated by double click.

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

106


2010

I n t e r n a l

U s e

SCM372

S A P

P a r t n e r

O n l y


Solution 5: Cross-plant and Multi-language Standard-Xstep-Repository (optional) Task 1: O n l y e r

In a first step you have to define a reference plant in Customizing to activate the cross-plant standard-XStep-repository. The reference plant is a technical aid that is needed only to enable the release of the necessary characteristic groups for process instructions and process messages. Choose the following Customizing activity (transaction CMX22): (SPRO: SAP Reference IMG: Production Planning for Process Industries → Process Management → Execution Steps (XSteps) → Standard XStep Repository → Define Reference Plant for Cross-Plant Standard XStep Repository)

U s e

P a r t n

1.

I n t e r n a l

You want to use the cross-plant standard-XStep repository to reduce the effort of maintaining your standard XSteps and thus to ensure a standardized way of working in all plants. In the cross-plant standard-XStep repository you can create standard XSteps once centrally and then use it in any number of plants.

Define Reference Plant for Cross-Plant Standard XStep Repository S A P

S A P

Plant 1100 has to be defined as reference plant for the following exercises. a)

---

e r

I n t e r n a l

U s e

P a r t n O n l y


2010


107

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

Unit 3: XSteps

SCM372

Task 2: In your ERP system, you find for historical reasons standard XSteps (SXS) in the plant-dependent standard-XStep-repositories (CMXSV) and in the cross-plant standard-XStep-repository (CMXSVN).

O n l y

You also check, that after having defined a reference plant in Customizing, you can only define new SXS References in the XStep editor of your plans with reference to SXS of the cross-plant repository.

To adopt constituents of a plant-dependent repository in the cross-plant repository, you must create this data in the cross-plant repository again. You can use the XML export and import functions for this purpose. Choose transaction CMXSVN (SAP menu: Logistics → Production-Process → Master Data → Cross-Plant Standard-XStep-Repository) to enter the Cross-Plant Standard-XStep-Repository. In the cross-plant repository you find for example a folder DPP65 which contains cross-plant SXS for this training course.

U s e

a)

Choose transaction CMXSV (SAP menu: Logistics → Production-Process → Master Data → Standard XStep Repository) to enter the Standard XStep Repositories for plant 1000 and then for plant 1100.

a) 3.

---

Choose transaction CA02 (SAP menu: Logistics → Production → Master Data → Routings →Routings → Standard Routings → Display) to change the standard routing for Continued on next page

108


2010

O n l y

You cannot find SXS that have been maintained in the cross-plant repository (CMXSV). For example, you cannot find folder DPP65.

e r

I n t e r n a l

2.

---

P a r t n

You cannot find SXS that have been maintained in the plant-dependent repositories (CMXSV).

S A P

S A P

1.

U s e

P a r t n

e r

But still existing SXS References which were defined with reference to a plant-dependent repository (CMXSV) before activating the cross-plant repository will remain valid.

I n t e r n a l

You check, that the cross-plant standard-XStep-repository (CMXSVN) is a separated repository. XSteps maintained in the cross-plant repository are not available in the plant-dependent repositories and vice versa.

I n t e r n a l

U s e

SCM372

P a r t n e r

O n l y


Material:

T-SCM372-PP-##

Plant:

1000

Group counter:

9

a)

---

Choose symbol XSteps or Goto → XSteps to enter the XStep editor. In the XStep editor, create a new SXS Reference: Choose the context menu for the XStep Tree (right mouse click) and then Create → SXS Reference.

e r

Double click the new SXS Reference and go to the Reference tab.

a)

---

U s e

P a r t n

Only SXS of the cross-plant repository can be assigned as reference.

Task 3:

S A P

You normally create SXS in language EN English. Therefore you define language EN as your preferred language in Customizing. Texts that not have been translated in all other languages yet will be displayed in English as default.


e r

Choose the following Customizing activity: (SPRO: SAP Reference IMG: Production Planning for Process Industries → Process Management → Execution Steps (XSteps) → Standard XStep Repository → Define Preferred Default Language)

P a r t n

You can check in a translation overview what elements of a SXS has not been translated yet

S A P

You have production plants in several countries. Therefore you translate your standard XSteps in several languages.

1.

I n t e r n a l

4.

O n l y

S A P

Define Preferred Default Language

a) 2.

---

For the following exercise steps you have to logon to your ERP system three times: Logon in languages EN (English), DE (German), and FR (French). a)

--Continued on next page

2010


109

O n l y

Language EN is defined as preferred language.

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

Unit 3: XSteps

SCM372

3.

For each language: Choose transaction CMXSVN (SAP menu: Logistics → Production-Process → Master Data → Cross-Plant Standard-XStep-Repository) to enter the Cross-Plant Standard-XStep-Repository.

O n l y

Choose the context menu for folder DPP65 (right mouse click) and then Display Translations.

e r

You get an overview of all existing translations in an ALV grid view. A Missing Translation flag is set if a text is maintained for any other language but not for the current language. You can jump to an element to be translated by double click.

U s e

P a r t n

Finally simulate the work instruction / PI sheet for SXS Cross-plant & multi-language example SXS. Choose the context menu for the XStep Tree (right mouse click) and then Simulate. a)

I n t e r n a l

Display the texts of all translatable elements with respect to folder DPP65 in the translation overview.

---

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

110


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


Lesson Summary You should now be able to: • Maintain standard XSteps in the cross-plant standard-XStep-repository and in multiple languages

U s e

P a r t n

e r

O n l y

I n t e r n a l

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

2010


111

I n t e r n a l

U s e

S A P

P a r t n e r

O n l y

Unit 3: XSteps

SCM372

Lesson: XSteps for PI Sheets/Work Instructions

O n l y

Business Example

After completing this lesson, you will be able to: •

Create XSteps for PI sheets/work instructions

P a r t n

In XSteps (execution steps), you therefore specify the data structures for defining the structure of control recipes/control instructions and PI sheets/work instructions along with the connected process message requests.

S A P

You then familiarize yourself with the structure, elements, and properties of XSteps and the use of standard XSteps from the standard XStep repository.

P a r t n

Finally, you familiarize yourself with XStep maintenance for PI sheets/work instructions and external systems.

e r

I n t e r n a l

U s e

S A P


U s e

At your company, you want to use the process management and process integration functions to process your process and production orders.

I n t e r n a l

Lesson Objectives

e r

Lesson Overview

O n l y

112


2010

I n t e r n a l

SCM372

U s e

S A P

P a r t n e r

O n l y


U s e

P a r t n

e r

O n l y

I n t e r n a l

Figure 70: XStep Process Instructions for PI Sheets/Work Instructions

S A P

S A P

For destination type PI Sheet/Work Instructions, you define XStep process instructions for PI sheets/work instructions that are to be processed by process operators/machine operators. You use the context menu to maintain the elements of a process instruction.

e r

I n t e r n a l

U s e

P a r t n O n l y

Figure 71: XStep Process Instructions – Features

2010


113

I n t e r n a l

U s e

S A P

P a r t n e r

Unit 3: XSteps

O n l y

SCM372

You can use XStep process instructions in the PI sheets/work instructions to define the following contents and functions: •

•

e r

Data format

•

For most XStep process instructions, a characteristic that defines the data format of the value is suggested by default. If you want to use a different format, you can select a different characteristic from the input help or create a new one. You can create your own characteristics in Customizing for Production Planning for Process Industries under Process Instructions → Process Instruction Characteristics → Define Characteristics for Process Instructions.

U s e

P a r t n

•

I n t e r n a l

O n l y

•

Outputs: You can output information using different data types such as long texts, numeric values, and images. Inputs: You can use input fields to request production-relevant data that the process operators/machine operators are to enter in the PI sheet/work instructions. Control data: You can use control data to request process messages, make calculations, call functions, and read and write data points to and from other applications using manufacturing data access, for example.

S A P

S A P e r

I n t e r n a l

U s e

P a r t n O n l y

Figure 72: Long Text Outputs – Exercise Example

114


2010

I n t e r n a l

U s e

S A P

SCM372

P a r t n e r

O n l y


Output of Long Text •

O n l y

U s e

P a r t n

e r

•

I n t e r n a l

•

This function provides you with a selection of characteristics, such as PPPI_MESSAGE_TEXT, which support the long text format. You can define a text of your choice in the SAPscript editor. The long text is displayed in the left-hand area of the PI sheet/work instructions. If you also want to use HTML fragments to format your long text, you can choose characteristic PPPI_FRAGMENT_HTML (HTML Fragment). You can use this characteristic to include a user-defined HTML source text. You can create a note for characteristic PPPI_NOTE that can be shown and hidden in the PI sheet/work instructions.

S A P

S A P

U s e

P a r t n e r

Output a Character String •

2010

The data format of characteristic PPPI_SHORT_TEXT is suggested by default. In this case, you can output a title and a user-defined alphanumeric value of 30 characters.


115

O n l y

I n t e r n a l

Figure 73: Outputs of Different Types – Exercise Example

I n t e r n a l

U s e

S A P

P a r t n e r

Unit 3: XSteps

O n l y

SCM372

Output a Numerical Value •

Output a Date

e r

•

The data format of characteristic PPPI_EVENT_DATE is suggested by default. In this case, you can output a description and a date in the format DD.MM.YYYY.

I n t e r n a l

O n l y

•

The data format of characteristic PPPI_PARAMETER_VALUE is suggested by default. In this case, you can output a numerical value with 10 digits and 3 decimal places. You can also display a unit of measure for a numeric value. If you output the unit of measure as a character string using characteristic PPPI_UNIT_OF_MEASURE, the unit of measure is displayed to the right of the output field.

•

The data format of characteristic PPPI_EVENT_TIME is suggested by default. In this case, you can output a description and a fixed time in the format HH.MM.SS.

S A P

•

U s e

•

116


2010

O n l y

•

You can include and display images in the format GIF, JPG, BMP, or AVI (video). To do this, you specify a URL at which the image file is stored, for example, http://help.sap.com/banner/saplogo_a.gif. The image is displayed in the left-hand area of the PI sheet/work instructions. The following characteristics are provided for defining a hyperlink to the corresponding file: 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.

e r

I n t e r n a l

Output an Image

P a r t n

•

Enter the address of the Internet or intranet page that you want to reference, for example, http://help.sap.com (SAP Help Portal). The link is displayed in the left-hand area of the PI sheet/work instructions. The following characteristics are provided for defining a hyperlink: PPPI_HYPERLINK Hyperlink PPPI_HYPERLINK_ASCII Hyperlink to ASCII Document PPPI_HYPERLINK_HTML Hyperlink to HTML DocumentPPPI_HYPERLINK_XML Hyperlink to XML Document

S A P

Output a Hyperlink

U s e

P a r t n

Output a Time

I n t e r n a l

U s e

SCM372

S A P

P a r t n e r

O n l y


Output an Object •

O n l y e r

U s e

P a r t n

I n t e r n a l

•

You can also include any other object, such as an MS Word document. To do this you specify a URL at which the file is stored for characteristic PPPI_OBJECT (Any Object) If you use the standard XSL style sheet, characteristic PPPI_OBJECT leads to HTML element

SCM372 en Col95 FV Part Ltr Execution Steps - XSteps

Recommend Documents