Ansicht
Dokumentation
MDG_VC_GEN_CDSV_PROA - Generate CDS Views for Process Analytics
BAL_S_LOG - Application Log: Log header data ABAP Short ReferenceThis documentation is copyright by SAP AG.
This configuration activity enables you to generate the required CDS views for change request analytics.
Prerequisites
You must run the report
Activities
To generate the CDS views perform the following actions:
1. Enter an Analytical CDS View Name.
2. Choose a data model and main entity type.
3. Choose a local package to store the generated CDS views.
4. Choose the Analytics Target to decide which changes to analyze.
5. Choose which attributes you want to make available for analytics. You can choose from any type 1
or type 4 entities belonging to the main entity type. Additionally, if any attributes need access logging,
choose a Log Domain. The accessing of these attributes using your CDS view in any analytics report will
be logged in the central Read Access Logging tool with the channel SAP BW and domain Analytics/
6. Select the views you want to create and choose Generate.
You can change the description of the configuration at any time.
Details
From the generated analytics CDS view, you will be able to measure the following:
•,,The number of change requests
•,,The total change request processing days
•,,The change request average processing days
•,,The total change request overdue days
•,,The change request average overdue days
You can use the attributes you configure in the Fields Selection view to further analyze the objects within the change requests. The analytics report shows the final values of the master data, regardless of intermediate values during change request processing.
Example 1:
You configure the report to display information on the Product Group.
Your configured report displays the following content for your Product Group:
| Product Group | Number of Change Requests | |
|---|---|---|
| A100 | 2 |
,,,,
There could be 2 possible reasons for this result:
•,,Product P123 has the value A100 for the attribute Product Group, and two change requests have modified it.
•,,Product P123 and Product 456 both have the value A100 for the attribute Product Group, and each Product is processed by one change request.
The system ignores the initial and intermediate values for the Product Group attribute in these cases, providing data based only on the final attribute value.
Example 2:
You configure the report to display information on the MRP Type.
Your configured report displays the following content:
| MRP Type | Number of Change Requests | |
|---|---|---|
| M1 | 2 | |
| M2 | 1 |
The reason for this is might be:
The current values for the MRP Type for Product M909 are M1 (Plant 1) and M2 (Plant 2), and the product has been processed by one change request. The current value for the MRP Type for Product M1928 is M1 (Plant 3), and the product has been processed by another change request. The data modified by the change requests is not important in these cases.
In both examples above, the objects (Product) were modified, but there is not necessarily any change made to the attributes (Product Group and MRP Type).
To make it transparent to your analytics end user, you should always use a clear report name.
General Material Data CL_GUI_FRONTEND_SERVICES - Frontend Services
This documentation is copyright by SAP AG.
Length: 4545 Date: 20240523 Time: 184602 sap01-206 ( 65 ms )
