SAP PPPI - Process Management Execution in a Process Order 

Processing of the Control Recipe 

The creation of control recipe and the use of control recipe to carry out business functions (carrying out shop floor execution functions) as a substitute to the manual shop floor execution in SAP is a special feature available in SAP PPPI. 

Following are control recipe statuses, explained:  

a) When the control recipe is created, the process order gets the system status CRCR – control recipe created.  

b) When a control recipe is finished and completely executed, the process order gets a system status CRFI.  

c) When the control recipe is discarded before the start of the execution then process order gets a system status CRAB – Control recipe discarded (similarly the processing of the control recipe can be terminated as well, if the work on the control recipe is already started).  

d) In case of a PI sheet, if you set the PI sheet to “Completion” Status (when all the entries, calculations are fully completed in the sheet), a process message category named PI_CRST is automatically sent to SAP, this process message category would have a process message characteristics PPPI_CONTROL_RECIPE_STATUS whose value would have been set to “processed”.  The status CRFI is set on the process order.  

Similarly for setting a completion status on the control recipe, when you are working with an external system, a process message category named PI_CRST has to be sent to SAP with the control recipe status value set as “processed thereby setting the status CRFI on the process order.  

e) In case of a PI sheet, if you set the PI sheet to “technical completion” – (when you want to prematurely stop processing of the PI sheet), a process message category named PI_CRST is automatically sent to SAP, this process message category would have a process message characteristics PPPI_CONTROL_RECIPE_STATUS whose value would have been set to “terminated”.  The status CRAB – Control recipe discarded, is set on the process order.  

And similarly when you are working with an external system, and want to terminate or discard a control recipe, a process message category named PI_CRST has to be sent to SAP with control recipe status set as “terminated”.   

Downloading of the Control Recipe 

Control recipe once created needs to be downloaded to the specified control recipe destination/s. To do this, you can download it manually using the control recipe monitor (transaction code CO53) under human supervision or you can schedule a background job for the downloading program RCOCB006 (batch job name – SAP_NEW_CONTROL_RECIPE).  

The control recipe monitor shows the sent control recipes, information on all the executed control recipes and information on all the terminated and discarded control recipes with logs included. The selection criterion is plant and date ranges like any other monitor or report.  

Once is control recipe is downloaded to the destinations of type 1 and 4, it is called as a PI sheet whereas control recipes downloaded to the destinations of type 2 and 3 reach the external system or external process control system.  

Below is a Control recipe monitor screen shot that is used to send the control recipe to their respective destinations. 

If you are working with PI sheets, then the operator should enter the details for the PI sheet created for a process order using the transaction code CO58 (Display of PI sheet is transaction code CO56 and Deletion of PI sheet is The following are some important transaction code CO59) 

Once the PI sheet is completed and saved, the detailed entered in the PI sheet as process messages, for enabling execution of various business processes in SAP are to be uploaded and processed in SAP depending upon the type of the process message category. 

SAP PPPI - Process Management Execution in a Process Order

Processing of the Process Messages

After processing the control recipe at the destinations, i.e., the destination (an operator or the process control system) provides the values for the process message characteristics of a process message category. The process message category or the process messages is sent back to SAP and subsequently processed in SAP depending upon the type of the process message category.   

The process messages are sent to the destination by the process management. The messages are first sent to the process management and then transferring the process messages to the destinations i.e., updating the process messages depending upon the type of the process messages. The process message categories or the process messages (as they are called) would be checked for missing values and authenticity.  

Process messages which are created for a test are monitored and checked, though they are not  processed at the destination as normal process message would.  

The process messages are uploaded and processed into SAP, either automatically using an upload batch job – program name - RCOCB002 (for process messages existing cross plants) or RCOCB004 (for process messages existing at a plant) or done manually through the process management monitor (transaction code CO54).  

Process message categories which end up with errors or are terminated during processing can be resubmitted for processing by the use of process management monitor as seen above.  

SAP also provides an option to create the process message category manually using the transaction code CO57. Here you should enter the plant, the process message category and the values for the process message characteristics which are required or sufficient to process the process message category in SAP. The Process message category can be created for test purpose or for final execution. This process message category like any, would reach the process management monitor from where it has to be updated in SAP. 

Depending upon the type of the process message category, the process messages are processed in SAP. The following are the process message category types.  

• BAPI or Function modules are used to update the process messages in SAP. The process messages once received in SAP are processed using these function modules. You can define your own function modules or you can use the existing standard function modules. Transaction code SE37 can be used to access these function modules. 

• External Functions to coordinate with the external process control system with process messages through RFC connections (a RFC destination should be created for every external system). Transaction code SM59 can be used to define the RFC destinations to communicate with the external system. 

• SAP Office User is a destination type which is used to inform specific SAP users about the status of the control recipe and process messages (in short the status of the production run)

• The process message characteristics data can be updated in user Defined ABAP tables. One can define the ABAP tables and access them through transaction code SE11.

•  Alerts of critical situation or milestones in the production run, from the external control system or internal shop floor operator using the PI Sheets can be sent to the multiple recipients as SMS or email. You can define Alert categories using SAP transaction code ALRTCATDEF. 

All the site contents are Copyright © www.sapsword.com and the content authors. All rights reserved.

All product names are trademarks of their respective companies.  The site www.sapsword.com is in no way affiliated with SAP AG. Every effort is made to ensure the content integrity. 

Information used on this site is at your own risk.

 The content on this site may not be reproduced or redistributed without the express written permission of www.sapsword.com or the content authors. 

Sitemap