In another article, we discussed how to get the capacity of a workplace. This article covers a common way to list or process the work orders of a workplace.
We will use the data from a transaction COOIS to get the work orders. Technically, we are executing the report behind the COOIS transaction. This report is called PPIO_ENTRY.
If you don’t know how to find the name of the report from the transaction name, just call the transaction and go to the menu system -> status and find the text field for program. That’s the report name. If you do this for a COOIS transaction, you will find PPIO_ENTRY.
To execute a report in Peakboard, you need to do a small installation on the SAP side to get it working. All the details are explained in this article.
Understanding COOIS
COOIS is the number one reporting transaction for getting an overview of all production data. There are options to select production data from different levels (header, material, operations, etc.).
The select options and the selection screen might vary by SAP release. This article uses the 2019 S4/HANA COOIS transaction, which might look different from your SAP system. That doesn’t matter, because the general principle explained in this article remains the same for all common SAP releases over the last few years.
Let’s assume we’re interested in the operations of a certain workplace. So we fill out the selection screen according to the given plant and workplace. We also limit the operations on “not confirmed” and “partly confirmed.”
The status values to chose here depends heavily on the customizations of the SAP production module. The values in the screenshot are only valid for this particular SAP system.
We must also take care of the layout. The layout determines which columns are selected. Under certain circumstances, it makes sense to create an individual layout only for use with Peakboard. All the columns we need later in the application should be covered.
Let’s try out the selection and check the result.
Side note: It might be necessary to apply additional filters on the result after the selection. If you want to do this, you must save these filters together with the layout. Then, you must apply the layout in the selection screen.
After having checked the result, we go back to the selection and save the selection as a variant. A good practice is to use the workplace in the selection as part of the name of the variant.
Call the report from Peakboard
In Peakboard Designer, we create another SAP data source and apply the following XQL, which executes the report PPIO_ENTRY with the just created variant PB_Z_ASM3.
EXECUTE REPORT 'PPIO_ENTRY' USING 'PB_Z_ASM3'The following screenshot shows the data source together with the preview. This should match what we checked directly in the COOIS transaction earlier.
Note: The name of the report columns are language-dependent. So if we change the login language, it will change the column names and mess up all your metadata.
Final result
If we use a regular table and adjust the column width, format, and naming of the columns, we can easily create a cool table with the workplace’s operations. These screenshots show the table in design and at runtime.
Additional hints
Here are some more things to consider:
- If for whatever reason the COOIS transaction does not fulfill your needs, you can try to build and use a query instead.
- The pattern described in this article is fully language-dependent. This is also true for the system status values. For example, when you limit the operations to “Confirmed,” the English status is “CNF” while the German status is “RÜC.” So the selection value must be changed when the login language changes.
- Using reports for data selection gives you any date value in the format of the current language. The typical SAP date format
YYYYMMDDcan’t be used here. You need to convert it in Peakboard to your desired format. - In our example, we have chosen the level of “Order Headers” for the selection. Depending on your use case, it might make more sense to choose “operations” or other levels.
