This action might not be possible to undo. Are you sure you want to continue?
Minimum Configuration of Process Management in SAP PPPI Following are the steps to configure process management in SAP PPPI. The below bullet points are configuration steps carried out the sequence in which it is arranged. A) Copying Process Management Characteristics and Process Message Categories to your Client It is always recommended to run the following 3 transaction code before you start the configuration for the Process management. Firstly Run transaction code O23c - Transport Predefined characteristics, to transfer process instruction characteristics or process message characteristics from the SAP reference client (000) to your client. Secondly you have to run transaction code O22c - Transport Predefined Message Categories – to transfer or copy all the process message characteristics from the SAP plant to your plant; when you carry out this configuration, you need to enter the plant and press execute button and then press the copy button in the next screen to copy the process messages. Thirdly you have to run transaction code CO60_VM to transport the display variants for PI Sheets predefined by SAP from the SAP reference client to your logon client. Press the save button while exiting.
the process message characteristics are grouped under a group called “PPPI_01” and process instruction characteristics are grouped under a group called “PPPI_02”. the process instruction characteristics should carry a characteristics group called “PPPI_02”. in Process management. though you need to release them for use as process messages and process instructions. When you configure you need to configure release for the following groups: PPPI_01 PPPI_03 PPPI_04 Process Message Characteristics Char.These groups are already defined by SAP in your SAP client. similarly for use of characteristics as process instruction characteristics. for Material Flow between Orders Special Applications 2 . is used to release process message characteristics group for use in process messages or process management. the process message characteristics should carry characteristics group “PPPI_01”. For use of characteristics as process message characteristics. for a given plant. Releasing the Characteristics Groups for Use . Transaction code O08C.B) Releasing Characteristics Groups for Process Managements Characteristic groups are defined by SAP to group a certain set of characteristics according to functions or areas in which the characteristics are used.
and process instruction characteristics (it doesn’t copy the process instruction categories to your respective plants and you would need to create them manually with reference to those in 0001 plant). is used to release process instruction characteristics group for use in process instructions or process management. which contains you enter information of reference tables-fields used for automatic population of characteristics values or function modules which would populate the data automatically. Along with this configuration. There are predominantly 2 types of destinations. Display is O27C). D) Creating Control Recipe Destinations Once you are done with the above 3 configuration steps. process message categories. Similarly you can create the process instruction categories using the same set of transaction codes. When you carry out the transport of predefined characteristics and transport of predefined process message categories. the system brings all the process message characteristics. for Material Flow between Orders Special Applications . you need to create the control recipe destinations using the transaction code O10c and if you are using an external control system then you need to also configure the RFC destination for the control recipe destination. Process message or process instruction characteristics created using O25C has process management button on the header screen. the transaction code to create the process message characteristics is O25C (Change is O26C. one should also configure QDR system for the resources when you are using an external process control system. one is an operator group inside of 3 Process Message Characteristics Process Instruction Characteristics Char.Transaction code O09C. Though you cannot make any changes in SAP defined standard characteristics. A control Recipe destination contains the following: a) The type of control recipe destination – Destination to which the process instructions are transferred to. When you configure you need to configure release for the following groups: PPPI_01 PPPI_02 PPPI_03 PPPI_04 C) Creating Custom Process Message Characteristics & Process Instruction Characteristics SAP offers a bunch of process message characteristics and process instruction characteristics along with another big bunch of process messages categories and process instructions categories in a SAP plant 0001. but you may need to create a few characteristics manually when you design project specific process instruction categories and message categories.
Figure 46 4 . You can also assign process instructions as a part of “automatically generated process instructions”. Type 1 is a shop floor destination in SAP to which the process instructions arranged on an ABAP based PI sheet are transferred. the Address can be name of the destination. digital signature etc. these process instructions are generated when the control recipe is created. the user name. b) Address of the destination – When the destination is an internal SAP based destination like type 1 and type 4.SAP and the other is an external process control system. similarly type 4 is an shop floor destination to which a browser based PI sheet is transferred. but when the destination is an external process control system then the address is the RFC destination of the external system. d) Assignment of instructions – You can assign process instructions to the destinations rather than having them assigned to each and every material recipe. type 2 is an external process control system which receives the process instructions as transferred by SAP and type 3 is an external process control system which triggers the transfer of process instructions towards them. c) Signature – You can include the signature details. password.
The destinations or recipients of the process instructions can be SAP destinations or external process control system destinations. If the destination is in SAP itself. the address is the RFC destination of the process control systems). Control Recipe SAP External Control System 5 . The definition of the control recipe destination needs configuring the destination type. which means that every phase in a master recipe can carry different control recipe destinations. address of the destination (in external system. where as if the destination is an external process control system outside of SAP. The control recipe destinations are assigned to the individual phases of an operation. then the process instructions & process messages are interfaced with that external system. executing the phase. One control recipe is created for a given destination and order combination. then it can be a shop floor operator/operator group at a plant or a production line or shop floor operator/operator group for a specific activity.Figure 47 Control recipe Destinations Standard SAP has control recipe destinations which receive the process instructions and using which the destination carries out the manufacturing and at the end of which they send back the process messages to confirm their production activities or production status on a real time basis.
there is a provision to assign the process instructions in a sequence (making a list of suitable instructions) which are generated in the process order control recipe and subsequently downloaded to the SAP operator/operator group.Destination 1&4 Destination lies in SAP ERP system Destinations lies outside of SAP ERP system and is called as an External Control System 2&3 Control Recipe Destinations Type 1 & 4 . Note: In configuration for the destinations of type 2 and 3. well arranged on a web based sheet browser based PI-Sheet is sent to the internal operator/operator group. for a destination). Whereas for destinations of type 1 and 4. a sheet containing all the process instructions and requesting process messages. if the same is set for a destination type 4 – browser based PI-Sheet. Note: An ABAP based PISHEET is shown below.Destination located in SAP ECC System For shop floor destinations which are in SAP itself. then the sheet with the information would appear in a browser in HTML format. The destination operator group of type 1 receives all the process instructions & requested process messages well arranged on an ABAP based sheet or screen called as a PI-Sheet (one for an order. With Destination type there are standard BAPI’s and connections working. Note: Transaction to create the Control Recipe destination is O10C. Whereas for a destination of type 4. there are 2 different types of destinations called “1” and “4”. which would process the messages once sent back to SAP by the respective destinations. ABAP Based PISHEET Order Information 6 . you can assign process instructions which would be automatically become a part of control recipe and would be downloaded to the external control system. to represent them.
Process order number Process order type Plant Process order Quantity Control Recipe number Reservation Number Destination Date/Time 10002569 PI01 0002 10 100000000029823 561543 01 – Shop Plant 0002 25th Dec 2010 Operation/Phase Information Operation Phase Description Phase Relationships Start Date & Time Finish Date Destination & Time 01 01 01 01 0010 0010 0020 0020 0011 0012 0014 0015 Component Information Operation 0010 0010 0020 0020 Phase 0011 0012 0014 0015 Component C1 C2 C3 C3 Description C1 C2 C3 C4 Qty 10 20 10 15 UOM SLOC Batch Requesting Phase Confirmations Operation Phase Yield Scrap Set up Time Machine Time Text Reason Requesting Goods Issues Component Qty UOM SLOC Batch Component Text Reason 7 .
code Control Recipe Destinations Type 2 & 3 . external process control systems or manufacturing execution systems lying outside of SAP. Note – For external control systems. namely “2” and “3”.e. There are majorly two control recipe destinations interacting with external process control systems. whereas “3” is used when the transfer or download of control recipe is triggered by the external control system (Pull case). so as to define the connections to the control system and enable SAP to communicate with the system. Note: In configuration for the destinations of type 2 and 3. you can assign process instructions which would be automatically become a part of control recipe and would be downloaded to the external control system. Destination type “2” is used when the SAP initiates the transfer or download of control recipe to the external process control system (Push case).. 8 . The transaction code to create is SM59. i.Description C1 C2 C3 C4 C1 C2 C3 C3 Requesting Goods Receipts Dynamic Function Call for MIGO_GR Transaction Code – Press here to access MB31 T . there is a provision to assign the process instructions in a sequence (making a list of suitable instructions) which are generated in the process order control recipe and subsequently downloaded to the SAP operator/operator group. you can assign the process instruction categories and have the system generate control recipes automatically. Whereas for destinations of type 1 and 4. the process instructions are sent their through a standard designed interface. Note . it is required to define a RFC destination.Destination outside of SAP (External Systems) For control recipe destinations lying outside of the SAP system.When the process control system is an external system.
Figure 2 9 .
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.