This post describes how to use the full potential of the Production Information System (transactions COOIS COHV COOISPI COHVPI).
These transactions are too often used at only 10% of their capacity. This blog shows how to transform them into a shop floor production executing system for example.
These transactions have no limits as you can display all Production and Planning information and you can manage all access to the transaction through the navigation profile.
Remember that COHV and COOIS use the same program. Only COHV permits to add mass processing.
The COHV transaction is generally known for reporting, whereas it allows access to practically ALL transactions. With the cockpit, it is possible to select / display the information needed on a single screen (a BADI allows 10 additional fields to be added if necessary). It can be used in production directly on a workstation for many actions (depending on the variants) :
▪ WM Staging
▪ Quality data entry
▪ Release/closure of production orders
▪ Mass changes
▪ KPIs, daily controls, etc.
The implementation of this solution is simple as it requires adjustments and little or no configuration. It is often done first by a consultant and then handed over to key users for adjustments.
It could sometimes avoid MES integration, avoid or simplify bespoke transactions or reports with BADI.
Call the transaction COHV or COOIS
Define a selection variant which will become the access to the cockpit.
In the initial screen, select the different screens to be displayed. You must choose the value "List of Objects" in the "List" drop-down menu : this is the gateway to the cockpit !
This function brings up another tab : "Obj.Selection"
Choose the sub-screens to display with a layout (for instance here the missing parts)
On the "Obj.Selection" tab select :
object "items" with the value "0000000001" for instance
object "components" with the value "/MISSPARTS" for the "Layout" field and the value "2" for the "item" field.
Nota Bene : The value of the field "ITEM" corresponds to the sub-screen (ALV Grid) number of the selected object which will be displayed on the result screen
On the "Selection" tab, enter values : for instance, the field "Production Plan", "Order Type" and System Status" (REL)
Select the icon "Save as Variant…"
Enter values for the fields "Variant Name" and "Description" then click on the save icon. This variant could be used as a cockpit selected by user or added to a transaction + variant
On the initial screen, click on the execute icon. The Cockpit is displayed.
Define the “Navigation Profile”
Select the "Navigation Profile" icon and choose "Change Navigation Profile"
To add a "transaction" icon, check the "application toolbar" box and click on the "new entry" icon then call a transaction
Fill in the values, in the example the Transaction MIGO and a value for the text that will be displayed on the icon. Finally, click on continue (or press enter)
The same method is used to insert a function call (add an icon Reread of Refresh in this example)
After inserting the transactions (routing, BOM, production version, Gantt) and functions (reread and refresh) save the navigation profile by clicking on the save icon. CO11N access is also used a lot. There are no limits and it is possible to add a navigation profile to each part. (production declaration, print Handling Unit, Quality information, etc.)
Here is the preview of a cockpit on COHV after adding a custom navigation profile
COHV is very powerful with the cockpit (enabled by the function : object overview and navigation profile). I have implemented this solution several times and the feedbacks from clients and users are excellent : this solution is stable and scalable. Users no longer use transactions or the SAP menu: everything can be in this production cockpit, even most of the functionality of an MES. It is the best PP transaction !
It is even possible to start the cockpit directly by creating a transaction with a variant to avoid going through the selection screen. This is possible to use it with FIORI as well.
This post refers to the COOIS/COHV transaction. The same approach can be used for PP-PI with COOISPI/COHVPI.
After reading this blog post, you should now be able to create a production cockpit and propose this solution to your clients.
As an SAP User eXperience consultant, this post will be followed by other "killer app" transactions that should be more widely known given the excellent customer feedback
Thanks a lot for your feedbacks and comments.
Enjoy SAP !
For more information :
If you want to know more about this transaction : check the following blogs which explain how to improve navigation profile and use mass processing functions :