P. 1
Chap_14_PP

Chap_14_PP

|Views: 6|Likes:
Published by Tron02

More info:

Published by: Tron02 on Nov 05, 2012
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

01/03/2015

pdf

text

original

PP Production Planning and Control

SAP R/3 Enterprise
Release 470x200

Release Notes

Inc. The information contained herein may be changed without prior notice. SAP. SAPPHIRE. RIVA. BAPI. and OS/400® are registered trademarks of IBM Corporation. MetaFrame®. Parallel Sysplex®. Word®. Massachusetts Institute of Technology. Microsoft®. SAP Logo. PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. JAVA® is a registered trademark of Sun Microsystems.com Logo and mySAP. the Citrix logo. R/2. AIX®. DB2®. SAP EarlyWatch. and Motif® are registered trademarks of the Open Group.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. Inc. DB2/6000®. All rights reserved. WebFlow. JAVASCRIPT® is a registered trademark of Sun Microsystems. XML. XHTML are trademarks or registered trademarks of W3C®. AS/400®. ORACLE® is a registered trademark of ORACLE Corporation. MVS/ESA®. VideoFrame®.© Copyright 2003 SAP AG. WinFrame®. Citrix®. Program Neighborhood®. NT®.. used under license for technology invented and implemented by Netscape. Design: SAP Communications Media . RS/6000®. WINDOWS®. X/Open®. HTML. IBM®. OS/2®. SAP Business Workflow. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. DHTML. S/390®. OSF/1®. R/3. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. TM are registered trademarks of Informix Software UNIX®. Inc. mySAP. All other products mentioned are trademarks or registered trademarks of their respective companies. INFORMIX®-OnLine for SAP and Informix® Dynamic Server Incorporated. MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems. OS/390®. Management Cockpit. World Wide Web Consortium. ICA®. EXCEL®. SAP ArchiveLink.

1.2.2.2.2 14.1 14.1.1 14.SAP System Table of Contents SAP AG ______________________________________________________________ 14 14.1 14.2 PP Production Planning and Control Execution Steps (New) PP-PI Production Plannin Industries PP-PI-PMA Process Management Change to the Structure of the IMG of Prod for Process Execution Steps (New) 1 1 4 4 4 4 ______________________________________________________________ SAP AG iii .

group and structure production steps. parameter and process instructions to an XStep. This data can be automatically processed by a process control system. XSteps now serve as modules that you can use to describe. process instructions could only be defined on the basis of a process instruction category that you had already created in Customizing. XSteps significantly simplify the maintenance of process instructions and the objects relating to them.0 (EA_APPL 2. You can assign a control recipe destination. however you no longer have to know the characteristic syntax. To do this you had to know the characteristics and take their syntax into account.1 Execution Steps (New) Use Overview As of SAP R/3 Enterprise SCM Extension 2. You can now define XSteps for PI sheets independently of the process instruction category and process instruction type. The maintenance of XSteps is no longer bound to phases. They contain process instructions that generally have specific valuations. Until now it was necessary to define this information in the form of process instruction characteristics. which enhance the key functions used in conjunction with process instructions. new developments are available in the form of execution steps (XSteps). You directly assign a destination. The maintenance of XSteps for external systems continues to be linked to process instruction types. as was the case with process instructions. application context. In the XStep editor you can define process instructions without knowledge of the characteristics. application context and scope of generation to each XStep. scope of generation. or manually processed by a process operator or employee as an interactive PI sheet. In addition. Process instructions are used to describe the execution of production processes. Application-independent standard XSteps ______________________________________________________________ SAP AG 1 . The process instructions had to be stored in the phases of a process order or master recipe and were only accessible via the phases.00).SAP System ______________________________________________________________ 14 PP Production Planning and Control 14. The following new and enhanced functions have been implemented: o o o o o o o Application-specific XSteps Application-independent standard XSteps Standard XStep repository XStep editor XStep parameter XStep generation XStep context Application-specific XSteps You create these in the process order and master recipe. Each process instruction category also had to be assigned to a certain process instruction type. Instead you have a complete view of all XSteps in a master recipe or order.

which do not generally have specific valuations. when you change standardized processes you no longer have to make these changes in each individual master recipe. the new maintenance function in the XStep editor offers a view across all control recipes in addition to the phase view. In this way you can easily model complex cross-relationships between different phases and PI sheets. For example. The functions available in the XStep editor depend on the business application in which the XStep editor is called. You create standard XSteps in the standard XStep repository. Archiving Standard XSteps that are no longer used can also be archived. In other words. Whilst previously the process instructions could only be stored for phases of a master recipe or process order. You are provided with process instructions. The control recipes that were then generated had to be assigned to a particular control recipe destination.Standard XStep Repository for administration and maintenance of standard XSteps. Every standard XStep has a version and consists of one XStep tree with a given number of XSteps. in a master recipe you can only reference to standard XSteps that have the status released. In the XStep editor you can define process instructions without knowing the characteristics and their syntax. XStep Parameters XStep parameters have been introduced as the central component of XSteps. XStep parameters allow you to reuse XStep contents. Instead. The reusability of standard XSteps considerably reduces the amount of data maintenance required. These are some of the functions you can use in the SXS repository: o Versioning You can create several versions with different validity periods for a standard XStep. you make the changes centrally in the SXS repository. Several versions can exist for a standard XStep. ______________________________________________________________ SAP AG 2 . the data could only be created in the context of a particular business application and therefore was not available to any other application. You can define the contents of XSteps as parameters as you require. the system creates a copy of the standard XStep referenced in the XStep tree on the key date. For example. All master recipes that are referenced to these standard XSteps are changed automatically. process instructions could only be stored in a master recipe or process order. If the reference is exploded in an application for a standard XStep. the activities connected to the status management of standard XSteps can only be executed in the SXS repository. Standard XSteps are used as modules for master data maintenance that can be used by different applications without the data itself being modified. The XStep editor is displayed in the standard XStep repository. Using drag and drop and context menu entries you can easily configure your PI sheet and can then simulate and test it immediately. For example. Archived standard XSteps can still be viewed in the SXS repository. o o XStep Editor The XStep editor has been introduced as a unique maintenance interface for standard XSteps. process order and master recipe. however.SAP System ______________________________________________________________ Until now. Status Management You can give each standard XStep a status to document certain states. Standard XStep Repository You can use transaction CMXSV . they can no longer be referenced. The current status of a standard XStep determines which actions can be carried out with it. without these having to be given fixed values. XSteps and therefore also for process instructions.

You can now specify the scope of generation directly at the XStep or at the standard XStep. you can define value-neutral parameters in standard XSteps. The number of scopes of generation has been increased. XStep Context XSteps are no longer stored for phases of an order or master recipe. the system generates the stored process instructions for a certain scope for all control recipes for this destination. However. That is. You make this setting in Customizing for Process Management. Go to Customizing for the master recipe and choose Settings for the Task List Type -> Define Profiles for Default Values. you can also specify that an XStep tree is generated even if the order has not yet been saved. Restrictions Compared with the Conventional Process Instruction Maintenance The use of the XSteps for the following functions is either restricted or not possible: o XSteps cannot be used in the Decentralized Process Managementscenario. A new recipe profile for the maintenance of XSteps PI01_XS Profile for Process Industries XSteps is available in the standard delivery. o o Effects on Customizing Maintaining XSteps in the Master Recipe To maintain XSteps in the master recipe.SAP System ______________________________________________________________ For example. You cannot define phase sequences in process orders and master recipes. These standard XSteps can then be referenced in different applications and each be given different valuations. in which you use XSteps. You can now determine the position of the generated XSteps via the position of the XStep in the XStep tree. In conventional process instructions you could store process instructions to be generated for a particular control recipe destination in Customizing. Control recipes that you have created using XSteps can be archived in the batch record as before. in which they are used as browser-based PI sheets. XStep Generation The previous concept of generated process instructions has been converted and the functions have been enhanced. During the generation of control recipes. Individual process instructions that are sent using the PI-PCS interface to an external system. Early Issue of Order Number As default. you must create a recipe profile that allows the maintenance of XSteps when you create the recipe group. the context is important if automatic valuations or generations are to be executed. An XStep can be valid for a whole order or a phase. are not displayed explicitly in the batch record. For example. This means that you have a greater level of detail when you are generating for materials and resources. See also ______________________________________________________________ SAP AG 3 . To do this choose Execution Steps (XSteps) -> Set Early Issue of Order Number. You carry out the assignment to a phase or an operation via the application context. The process instructions generated were also valuated automatically. an XStep tree can only be generated in a process order if the corresponding order has already been saved. you cannot send control recipes that have been generated using XSteps to decentralized systems.

00 (EA_APPL 2.1.SAP System ______________________________________________________________ ________________________________________________________________________ 14.2 PP-PI 14.2 Execution Steps (New) Use Overview As of SAP R/3 Enterprise SCM Extension 2.1 PP-PI-PMA Production Planning for Process Industries Process Management 14.1 Change to the Structure of the IMG of Production Planning for Process Industries (PP-PI) Use As of SAP R/3 Enterprise SCM Extension 2.00) the following changes have been made to the Implementation Guide (IMG) of Production Planning for Process Industries (PP-PI): New IMG Activities o Under process management the structure node execution steps (XSteps) with the following activities.2. or manually processed by a process operator or employee as an interactive PI sheet.1. This data can be automatically processed by a process control system. Until now it was necessary to define this information in the form of ______________________________________________________________ SAP AG 4 . new developments are available in the form of execution steps (XSteps).2. which enhance the key functions used in conjunction with process instructions. has been added: o Define Name Spaces for Scopes of Generation and Valuation Symbols Release Name Spaces Assign Standard XSteps Production Scheduling Profile Set Early Issue of Order Number Define Authorization Groups for SXS Repository Under Business Add-Ins in Process Management the following new activities have been added: BAdI: Definition of Scopes of Generation for XSteps BAdI: Definition of Valuation Symbols for XSteps BAdI: Enhancements for the Standard XStep Repository 14.00). Process instructions are used to describe the execution of production processes.0 (EA_APPL 2.2.

SAP System ______________________________________________________________ process instruction characteristics. You can assign a control recipe destination. scope of generation. Standard XStep Repository You can use transaction CMXSV . Every standard XStep has a version and consists of one XStep tree with a given number of XSteps. however you no longer have to know the characteristic syntax. which do not generally have specific valuations. The reusability of standard XSteps considerably reduces the amount of data maintenance required. The control recipes that were then generated had to be assigned to a particular control recipe destination. The maintenance of XSteps for external systems continues to be linked to process instruction types. In other words. Standard XSteps are used as modules for master data maintenance that can be used by different applications without the data itself being modified. Application-independent standard XSteps Until now. the data could only be created in the context of a particular business application and therefore was not available to any other application. XSteps now serve as modules that you can use to describe. XSteps significantly simplify the maintenance of process instructions and the objects relating to them. process instructions could only be defined on the basis of a process instruction category that you had already created in Customizing. when you change standardized processes you no longer have to make these changes in each individual master recipe. You can now define XSteps for PI sheets independently of the process instruction category and process instruction type. For example. as was the case with process instructions. Several versions can exist for a standard XStep. You create standard XSteps in the standard XStep repository. The following new and enhanced functions have been implemented: o o o o o o o Application-specific XSteps Application-independent standard XSteps Standard XStep repository XStep editor XStep parameter XStep generation XStep context Application-specific XSteps You create these in the process order and master recipe. In addition. parameter and process instructions to an XStep. You are provided with process instructions. They contain process instructions that generally have specific valuations. group and structure production steps. In the XStep editor you can define process instructions without knowledge of the characteristics. The process instructions had to be stored in the phases of a process order or master recipe and were only accessible via the phases. Instead you have a complete view of all XSteps in a master recipe or order. process instructions could only be stored in a master recipe or process order. you make the changes centrally in the SXS repository. application context. To do this you had to know the characteristics and take their syntax into account. All master recipes that are referenced to these standard XSteps are changed automatically. You directly assign a destination. The maintenance of XSteps is no longer bound to phases.Standard XStep Repository for administration and maintenance of ______________________________________________________________ SAP AG 5 . application context and scope of generation to each XStep. Each process instruction category also had to be assigned to a certain process instruction type. Instead.

Archived standard XSteps can still be viewed in the SXS repository.SAP System ______________________________________________________________ standard XSteps. You carry out the assignment to a ______________________________________________________________ SAP AG 6 . These are some of the functions you can use in the SXS repository: o Versioning You can create several versions with different validity periods for a standard XStep. the activities connected to the status management of standard XSteps can only be executed in the SXS repository. During the generation of control recipes. The number of scopes of generation has been increased. the system creates a copy of the standard XStep referenced in the XStep tree on the key date. This means that you have a greater level of detail when you are generating for materials and resources. For example. You can now determine the position of the generated XSteps via the position of the XStep in the XStep tree. For example. they can no longer be referenced. You can now specify the scope of generation directly at the XStep or at the standard XStep. You can define the contents of XSteps as parameters as you require. These standard XSteps can then be referenced in different applications and each be given different valuations. The functions available in the XStep editor depend on the business application in which the XStep editor is called. If the reference is exploded in an application for a standard XStep. without these having to be given fixed values. In conventional process instructions you could store process instructions to be generated for a particular control recipe destination in Customizing. In this way you can easily model complex cross-relationships between different phases and PI sheets. o o XStep Editor The XStep editor has been introduced as a unique maintenance interface for standard XSteps. Using drag and drop and context menu entries you can easily configure your PI sheet and can then simulate and test it immediately. The process instructions generated were also valuated automatically. In the XStep editor you can define process instructions without knowing the characteristics and their syntax. the system generates the stored process instructions for a certain scope for all control recipes for this destination. process order and master recipe. The XStep editor is displayed in the standard XStep repository. XSteps and therefore also for process instructions. Archiving Standard XSteps that are no longer used can also be archived. the new maintenance function in the XStep editor offers a view across all control recipes in addition to the phase view. XStep parameters allow you to reuse XStep contents. you can define value-neutral parameters in standard XSteps. however. XStep Parameters XStep parameters have been introduced as the central component of XSteps. Status Management You can give each standard XStep a status to document certain states. XStep Context XSteps are no longer stored for phases of an order or master recipe. The current status of a standard XStep determines which actions can be carried out with it. in a master recipe you can only reference to standard XSteps that have the status released. Whilst previously the process instructions could only be stored for phases of a master recipe or process order. XStep Generation The previous concept of generated process instructions has been converted and the functions have been enhanced. For example.

an XStep tree can only be generated in a process order if the corresponding order has already been saved. A new recipe profile for the maintenance of XSteps PI01_XS Profile for Process Industries XSteps is available in the standard delivery. you must create a recipe profile that allows the maintenance of XSteps when you create the recipe group. You make this setting in Customizing for Process Management. Individual process instructions that are sent using the PI-PCS interface to an external system. you can also specify that an XStep tree is generated even if the order has not yet been saved. However. To do this choose Execution Steps (XSteps) -> Set Early Issue of Order Number. Go to Customizing for the master recipe and choose Settings for the Task List Type -> Define Profiles for Default Values.SAP System ______________________________________________________________ phase or an operation via the application context. in which you use XSteps. Control recipes that you have created using XSteps can be archived in the batch record as before. That is. o o Effects on Customizing Maintaining XSteps in the Master Recipe To maintain XSteps in the master recipe. You cannot define phase sequences in process orders and master recipes. See also ________________________________________________________________________ ______________________________________________________________ SAP AG 7 . in which they are used as browser-based PI sheets. An XStep can be valid for a whole order or a phase. Early Issue of Order Number As default. are not displayed explicitly in the batch record. Restrictions Compared with the Conventional Process Instruction Maintenance The use of the XSteps for the following functions is either restricted or not possible: o XSteps cannot be used in the Decentralized Process Managementscenario. you cannot send control recipes that have been generated using XSteps to decentralized systems. For example. the context is important if automatic valuations or generations are to be executed.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->