> Continuous Process Improvement > Quality Management > SAP S/4HANA Quality Management > Data Template

Your Quality Management Data Template

SAP S/4HANA Quality Management

Quality Management Attributes (19) Quality Management Activities (15) Extraction Guides (4)

Your Quality Management Data Template

This template provides a comprehensive guide for collecting and preparing your Quality Management data. It outlines the essential attributes and activities required to create an accurate event log for process mining. Use this resource to streamline your data extraction and analysis efforts.

Recommended attributes to collect for comprehensive analysis
Key Quality Management activities to track
Guidance on extracting data from SAP S/4HANA Quality Management

New to event logs? Learn how to create a process mining event log.

Download Template

Quality Management Attributes

These are the recommended data fields to include in your event log for comprehensive quality management analysis within SAP S/4HANA.

3 Required 7 Recommended 9 Optional

	Name	Description
	Activity ActivityName	The name of the specific business event or task that occurred within the quality management process.
Description This attribute describes a single step or milestone in the quality event lifecycle, such as 'Notification Created', 'Root Cause Analysis Completed', or 'Usage Decision Made'. These activities are derived from changes in system status, creation of related documents, or specific user actions recorded in change logs. Analyzing the sequence and timing of these activities is the core of process mining. It allows for the discovery of the actual process flow, identification of bottlenecks between steps, and measurement of conformance to standard operating procedures. The granularity of activities determines the level of detail in the process analysis. Why it matters This attribute defines the steps of the process, making it possible to visualize and analyze the process flow, identify deviations, and measure performance between activities. Where to get Derived from status changes in tables JEST and JSTO, or from activity records in tables like QMSM (Tasks). Event logs can also be constructed from change document tables CDHDR and CDPOS. Examples Quality Notification CreatedInvestigation Task AssignedCorrective Action ImplementedNotification Closed
	Quality Event QualityEvent	The unique identifier for a quality notification, serving as the primary case ID for tracking a quality issue from initiation to closure.
Description The Quality Event is the central case identifier that connects all activities, tasks, and decisions related to a single quality issue. In SAP, this typically corresponds to the Quality Notification Number (QMNUM). In process mining, analyzing events by this identifier allows for the reconstruction of the end-to-end journey of each quality case. This is fundamental for visualizing process flows, calculating cycle times for the entire case, and identifying common or deviant paths in the resolution process. It serves as the backbone for almost all quality management analyses. Why it matters It is the essential key to link all related activities into a single, cohesive process instance, enabling end-to-end analysis of how quality issues are handled. Where to get This is the Quality Notification number, found in the QMEL table, field QMNUM. Examples 200000018200000019200000020
	Start Time EventTimestamp	The exact date and time when a specific activity or event occurred.
Description The Start Time, or event timestamp, records the precise moment an activity took place. This is crucial for ordering events chronologically and calculating durations between them. For example, it captures when a notification was created, when a task was completed, or when a status was changed. In process mining analysis, this attribute is fundamental for calculating all time-based metrics, such as cycle times, processing times, and waiting times. It enables the identification of bottlenecks, the analysis of throughput, and the monitoring of performance against time-based SLAs or targets. Accurate timestamps are critical for the integrity of the entire process model. Why it matters This timestamp is essential for ordering events, calculating all performance metrics like cycle times and waiting times, and understanding process dynamics. Where to get Typically sourced from date and time fields associated with status changes or document creation. Examples include ERDAT/ERZEIT (Created on/time) in QMEL or the change timestamps in CDHDR. Examples 2023-04-15T09:00:12Z2023-04-18T14:35:00Z2023-05-01T11:21:45Z
	Priority NotificationPriority	The priority level assigned to the quality notification, indicating its urgency.
Description Priority defines the urgency for addressing a quality event. It helps teams organize their work and ensures that the most critical issues are handled first. SAP allows for configuring different priority types which can influence target response times. This attribute is used to analyze if high-priority items are actually processed faster than low-priority ones. It can reveal inefficiencies where high-priority cases get stuck in the process. It is a key dimension for dashboards like 'Quality Event Throughput Analysis'. Why it matters Helps analyze if process performance aligns with business urgency, ensuring that high-priority issues are resolved faster. Where to get Located in the QMEL table, field QMPRI. The description is in table TQ05. Examples 1234
	Product MaterialNumber	The unique identifier for the product or material affected by the quality event.
Description This attribute links the quality event to a specific product or material. This connection is vital for quality assurance, as it helps identify products with recurring issues or high defect rates. In process mining, analyzing by product enables the detection of patterns, such as whether certain products have longer resolution times or are associated with specific root causes. This supports the 'Recurring Issue Pattern Detection' dashboard by correlating products with quality problems, which is crucial for targeted quality improvement initiatives. Why it matters Links quality issues to specific products, enabling analysis of product-specific defect rates, root causes, and resolution patterns. Where to get Found in the quality notification item table QMFE, field MATNR. Examples FIN-1001RAW-205ASEMI-303B
	Quality Notification Type QualityNotificationType	The classification of the quality notification, such as customer complaint, internal problem, or supplier defect.
Description This attribute categorizes the quality event based on its origin and nature. Standard SAP types include customer complaints, internal problem reports, and vendor-related defects. This categorization determines the subsequent process flow and required documentation. Analyzing the process by notification type is essential for understanding if different types of issues are handled differently or have varying levels of efficiency. It supports dashboards like 'Quality Event Throughput Analysis' by allowing filtering and comparison of cycle times and process paths for different issue categories. Why it matters It allows for segmentation of the process to see if different types of quality issues follow different paths or have different performance characteristics. Where to get Located in the QMEL table, field QMART. Examples Q1Q2F2
	Responsible Department ResponsibleDepartment	The department or functional area responsible for executing a specific task or managing the quality event.
Description This attribute indicates the organizational unit assigned to an activity or the overall quality event. This could be a quality assurance team, an engineering department, or a production unit. This is a critical dimension for analyzing cross-departmental collaboration and handoffs. It helps identify delays that occur when responsibility shifts from one department to another, supporting the 'Cross-Department Handoff Delays' dashboard. It also allows for filtering the process view to understand how specific departments operate. Why it matters Crucial for analyzing inter-departmental handoffs, identifying organizational bottlenecks, and understanding how different teams contribute to the process. Where to get Often derived from partner functions associated with the notification or task, or from the user's organizational assignment in HR master data. It may not be a direct field. Examples Quality AssuranceProduction Line 3Supplier Quality Engineering
	Root Cause RootCauseCode	A code or text identifying the determined root cause of the quality issue.
Description The Root Cause attribute captures the underlying reason for the quality defect or non-conformance. Identifying the correct root cause is a critical step in the quality management process, as it is the basis for defining effective corrective and preventive actions. This attribute is essential for the 'Root Cause Analysis Cycle Time' and 'Recurring Issue Pattern Detection' dashboards. Analyzing by root cause helps to identify systemic problems. For example, by filtering the process map for a specific root cause, one can see if it leads to unique process paths or longer resolution times. Why it matters Enables analysis of systemic issues by correlating root causes with products, departments, and process inefficiencies to guide preventive actions. Where to get Typically stored in the QMUR table (Notification Causes), field URCOD. Examples OPERATOR_ERRORDEFECTIVE_MATERIALMACHINE_MALFUNCTION
	Target Resolution Date TargetResolutionDate	The planned or required completion date for the quality event.
Description This date represents the deadline by which the quality event is expected to be fully resolved and closed. It is often used as a benchmark for measuring performance and adherence to service level agreements (SLAs). This attribute is fundamental for calculating on-time completion rates and identifying overdue cases. The 'Quality Event On-Time Completion' dashboard and the 'Quality Action On-Time Rate' KPI are directly dependent on comparing the actual completion date with this target date. It helps in prioritizing work and managing resources effectively. Why it matters Provides a baseline for measuring on-time performance, which is a critical KPI for assessing process efficiency and compliance with SLAs. Where to get Can be found in QMEL-QMDAT (Required end date) or at the task level in QMSM-PSTER. Examples 2023-05-302023-06-152023-07-01
	User ChangedBy	The user ID of the person who performed the activity or made the last change.
Description This attribute identifies the specific user responsible for executing a given process step. In SAP, this often corresponds to the 'Changed By' (AENAM) or 'Created By' (ERNAM) fields. Analyzing by user helps in understanding workload distribution, identifying training needs, and pinpointing user-specific process deviations. It is fundamental for resource-based analysis, such as investigating why certain users have longer processing times or tend to follow non-standard paths. Why it matters It enables analysis of user performance, workload distribution, and adherence to standard procedures, which is key for resource optimization. Where to get Found in header and item tables like QMEL-ERNAM (Created by) or derived from change logs (CDHDR-USERNAME). Examples SMITHJWILSONAPROCESS_AUTOMATION_BOT
	Action Effectiveness EffectivenessEvaluation	The outcome of the verification check to determine if an implemented action was effective.
Description This attribute records the result of the effectiveness check, a crucial final step in the quality management loop. It confirms whether the corrective or preventive actions taken have successfully resolved the root cause and prevented recurrence. This is the primary attribute for the 'Action Effectiveness Verification' dashboard and the 'Action Effectiveness Verification Rate' KPI. It provides direct insight into the quality of the problem-solving process itself. A high rate of ineffective actions indicates a need to improve the root cause analysis or action planning stages. Why it matters Directly measures the success of the problem-solving process, indicating whether actions are truly preventing issue recurrence. Where to get This information is often stored in follow-up actions or specific task statuses within the quality notification. It may be a custom field or based on a specific status code. Examples EffectiveNot EffectiveMonitoring Required
	Activity Processing Time ProcessingTime	The duration of time spent actively working on a single activity.
Description Processing Time, also known as cycle time, is the time elapsed from the start to the end of a single activity. This is distinct from waiting time, which is the time spent between activities. It is calculated by taking the difference between the start and end timestamps of an activity. This metric is fundamental for identifying which specific tasks are the most time-consuming. In the 'Process Bottleneck Identification' dashboard, high processing times for certain activities can indicate complexity, lack of resources, or inefficient procedures. It helps pinpoint exactly where to focus process improvement efforts. Why it matters Measures the time spent on value-adding activities, helping to identify the most time-consuming steps in the process that are prime candidates for optimization. Where to get Calculated field derived from the start and end timestamps of each activity in the event log. (EndTime - StartTime). Examples 2 hours 15 minutes3 days 4 hours30 minutes
	Customer CustomerNumber	The identifier for the customer associated with the quality event, if applicable.
Description This attribute links a quality event to a specific customer. This is most relevant for notification types like 'Customer Complaint'. Tracking this information is vital for customer relationship management and for understanding the customer impact of quality issues. Analyzing by customer allows the business to identify if certain customers experience more quality issues than others, or if resolution times vary by customer. This supports the 'Quality Events By Severity And Impact' dashboard by adding the customer dimension to the analysis of impact. Why it matters Connects quality events to customers, enabling analysis of customer-specific issues and ensuring high-value customers receive priority support. Where to get Usually found in partner functions for the notification. Can also be in QMEL-KUNUM if it's a complaint from a sales order. Examples CUST-10045CUST-20399CUST-80110
	Is Rework IsRework	A boolean flag that indicates if an activity or sequence of activities represents rework.
Description This flag is set to true if a case repeats certain steps, indicating that the initial work was insufficient. For example, if a 'Root Cause Analysis' activity is followed later by another 'Investigation Task Assigned' for the same case, it signals a rework loop. This attribute directly supports the 'Corrective Action Rework Rate' KPI. Identifying and quantifying rework is a primary goal of process mining, as rework represents wasted effort and process inefficiency. Highlighting rework loops in the process map can reveal significant opportunities for improvement in quality and efficiency. Why it matters Quantifies process inefficiency by identifying when steps are repeated, highlighting wasted effort and opportunities to improve first-time-right rates. Where to get This is a calculated attribute. It is derived during process mining analysis by detecting repeated sequences of activities within a single case. Examples truefalse
	Last Data Update LastDataUpdate	The timestamp indicating when the data for this record was last refreshed from the source system.
Description This attribute provides a timestamp for the last data extraction or update from the source system. It informs users about the freshness of the data they are analyzing. In any analytical dashboard or report, displaying this information is key to managing user expectations about data currency. It helps distinguish between recent process changes and artifacts of stale data. Why it matters Informs users of the data's freshness, which is critical for making timely and accurate decisions based on the process mining analysis. Where to get This is a metadata field generated and populated by the data extraction tool or pipeline at the time of data refresh. Examples 2023-10-27T02:00:00Z2023-10-28T02:00:00Z
	Notification Status SystemStatus	The current processing status of the quality notification, such as 'Outstanding' or 'Completed'.
Description The system status indicates the current state of the quality event in its lifecycle. SAP uses a status management system where statuses like OSNO (Outstanding Notification), NOPR (Notification in Process), and NOCO (Notification Completed) reflect progress. This attribute is often used to derive the activities in the event log. It is also valuable as a dimension for filtering cases, for example, to analyze only open or recently closed quality events. Understanding status transitions is key to building an accurate process model. Why it matters Indicates the current state of a case, allowing for filtering of active versus closed cases and helping to derive the process activities themselves. Where to get Derived from the JEST and JSTO tables, which store status information for various SAP objects. The link is from QMEL-OBJNR. Examples OSNO NOPRNOCOTSCO
	On-Time Completion IsOnTimeCompletion	A boolean flag indicating whether the quality event was completed by its target resolution date.
Description This calculated flag compares the actual completion timestamp of a quality event with its 'Target Resolution Date'. It is true if the event was closed on or before the target date, and false otherwise. This attribute provides a simple, direct measure for performance monitoring and is the basis for the 'Quality Event On-Time Completion' dashboard and the 'Quality Action On-Time Rate' KPI. It allows for easy filtering and aggregation to understand on-time performance across different dimensions like department, product, or notification type. Why it matters Provides a clear, binary outcome for performance tracking against deadlines, making it easy to measure and report on SLA compliance. Where to get Calculated attribute derived by comparing the timestamp of the final closing activity with the 'TargetResolutionDate' attribute. Examples truefalse
	Plant Plant	The manufacturing plant or location where the quality event originated or is being managed.
Description The Plant attribute specifies the physical location, such as a factory or warehouse, associated with the quality event. It provides a geographical or organizational context for where quality issues occur. This is a powerful dimension for comparative analysis. By filtering or grouping by plant, management can compare the performance of different locations, identify site-specific problems, and share best practices from high-performing plants. It helps answer questions like 'Which plant has the longest root cause analysis cycle time?'. Why it matters Allows for performance comparison across different operational locations, helping to identify site-specific issues and best practices. Where to get The plant associated with the notification header is in QMEL-WERKS. If related to a specific material, it can also be found at the item level. Examples 100017102000
	Source System SourceSystem	Identifies the source system from which the data was extracted, such as the specific SAP S/4HANA instance.
Description This attribute specifies the origin of the quality management data. In an environment with multiple ERPs or integrated systems, this field is crucial for distinguishing data sources and ensuring data integrity. For analysis, it allows for filtering or comparing processes across different systems or organizational units. It is often a constant value for a given dataset but is mandatory for data governance and context. Why it matters Provides essential context about the data's origin, which is crucial for data governance and in environments with multiple interconnected systems. Where to get This is typically a static value added during the data extraction process to identify the SAP S/4HANA client and system ID. Examples S4H_PROD_100SAP_QM_EUS4HANA_QAS_200

Required Recommended Optional

Quality Management Activities

These are the key process steps and milestones to capture in your event log for accurate process discovery and analysis.

6 Recommended 9 Optional

	Activity	Description
	Action Effectiveness Verified	Confirms that the implemented corrective or preventive action was successful and the quality issue is resolved without recurrence. This is captured upon completion of the effectiveness check task or a final quality review.
Why it matters This is a critical milestone for validating the entire resolution process. A high rate of successful verifications indicates an effective quality management system and supports a reduction in recurring issues. Where to get Typically inferred from the completion of an 'Effectiveness Check' task in the QMSM table (using completion date ERLDT). Capture Identify the completion timestamp of the effectiveness verification task in QMSM. Event type inferred
	Corrective Action Implemented	Marks the completion of the work defined in the corrective action plan. This is typically captured when the assigned corrective action task within the quality notification is marked as complete.
Why it matters This is a key milestone indicating that steps have been taken to resolve the quality issue. It is crucial for measuring the on-time completion rate of actions and the overall efficiency of the resolution phase. Where to get Inferred from the completion of a corrective action task in the QMSM table. The completion date is recorded in the ERLDT field or via a 'Completed' status change in tables JEST/JCDS. Capture Identify the completion timestamp (ERLDT) of the corrective action task in the QMSM table. Event type inferred
	Notification Completed	Indicates the business completion of the quality notification, signifying that all required actions have been taken and the issue is resolved from an operational standpoint. This is a formal status change in the system.
Why it matters This activity serves as the primary end-point for measuring the business resolution time. It confirms that from a process owner's view, the case is finished, even if technical closure is pending. Where to get Inferred from a status change on the Quality Notification object. This is captured by identifying the timestamp when a status like 'NOCO' (Notification completed) is set in the JCDS table. Capture Identify the timestamp when the 'Notification completed' status is set in the JCDS table. Event type inferred
	Quality Notification Created	This activity marks the official start of the quality management process, where a quality-related issue, defect, or complaint is formally logged. The creation of the Quality Notification in SAP S/4HANA captures the initial details and assigns a unique identifier, initiating the case.
Why it matters As the primary start event, this activity is essential for measuring the end-to-end cycle time of the quality resolution process. It provides the baseline for tracking how long it takes to address and close quality events. Where to get This is an explicit event captured from the Quality Notification header table QMEL. The creation timestamp is typically found in the ERDAT field for the corresponding notification number QMNUM. Capture Use creation timestamp (ERDAT) from the QMEL table for the given notification. Event type explicit
	Root Cause Analysis Completed	Marks the completion of the investigation phase where the underlying cause of the quality issue has been identified. This is typically inferred from the completion of a specific 'Root Cause Analysis' task within the notification.
Why it matters This is a critical milestone for measuring the duration and efficiency of the investigation process. Identifying delays before this step helps pinpoint bottlenecks in problem analysis and decision making. Where to get Inferred from the completion of an investigation or RCA-specific task in the QMSM table. The completion is identified by a status change or the population of the task completion date field (ERLDT). Capture Identify the completion timestamp (ERLDT) of the relevant root cause analysis task in the QMSM table. Event type inferred
	Usage Decision Made	Represents the formal decision on the quality of goods from an inspection lot, such as acceptance or rejection. This is a distinct event for quality issues originating from inspections and is captured when the usage decision is saved.
Why it matters For inspection-driven processes, this is a major milestone that dictates subsequent actions like material blocking or release. Analyzing its timing and outcomes is key to understanding product quality control efficiency. Where to get This is an explicit event recorded in the usage decision table QAVE. The creation timestamp of the record associated with the inspection lot (PRUEFLOS) signifies this activity. Capture Use the creation timestamp for the relevant inspection lot in the QAVE table. Event type explicit
	Action Plan Approved	Signifies that a proposed corrective or preventive action plan has been reviewed and approved to proceed with implementation. This step is often not a distinct event and may be inferred from the release of a task for processing.
Why it matters Long delays at this approval stage can significantly slow down the entire resolution process. Analyzing this duration helps identify administrative bottlenecks and opportunities to streamline governance. Where to get This is typically inferred from a status change on a task in table QMSM, such as 'Released'. The timestamp for this status change would be found in the JCDS table, linked to the task object. Capture Identify the timestamp when the 'Released' status is set for the corrective or preventive action task. Event type inferred
	Corrective Action Proposed	This activity represents the point where a plan to correct the identified issue is formally documented. In SAP, this is often captured through the creation of a 'Corrective Action' task within the quality notification.
Why it matters This event initiates the resolution phase of the process. Measuring the time from root cause analysis to this step can reveal delays in action planning. Where to get This event is captured when a task with a 'Corrective Action' code is created in the QMSM table for the relevant Quality Notification. Capture Use the creation timestamp (ERDAT) from the QMSM table for tasks with a corrective action type. Event type explicit
	Effectiveness Check Required	Indicates that a follow-up verification is needed to confirm that the implemented actions have successfully resolved the issue. This is often represented by a specific status on the notification or the creation of a dedicated verification task.
Why it matters This activity ensures that the quality management process includes a crucial validation loop. It separates the implementation of an action from the confirmation of its success. Where to get Can be inferred from a status change on the Quality Notification (via JEST/JCDS) or the creation of a specific 'Effectiveness Check' task in the QMSM table. Capture Identify timestamp of status change or creation of a verification task in QMSM. Event type inferred
	Investigation Task Assigned	This event occurs when a specific task, such as investigating the root cause, is formally created and assigned to a person or department. This is captured when a task record is created within the Quality Notification.
Why it matters Tracking task assignment is crucial for understanding workload distribution and identifying bottlenecks in resource allocation. It marks the start of the investigation phase, a key input for measuring root cause analysis cycle time. Where to get Captured from the task management table QMSM, linked to the Quality Notification. The creation date (ERDAT) of a task with a relevant code, e.g., for investigation, marks this event. Capture Use creation timestamp (ERDAT) from the QMSM table for tasks related to investigation. Event type explicit
	Notification Closed	Represents the final, technical closure of the quality notification in the system. After this point, no further changes can be made to the notification, marking the absolute end of the record's lifecycle.
Why it matters This activity provides the final end event for the process. Analyzing the time between 'Notification Completed' and 'Notification Closed' can reveal delays in administrative closing procedures. Where to get Inferred from a status change on the Quality Notification, specifically when an archival or final closing status is set. This change is logged with a timestamp in the JCDS table. Capture Identify the timestamp when the final 'Closed' status is set for the notification in the JCDS table. Event type inferred
	Notification Put In Process	Represents the moment a newly created notification is actively picked up for processing by the quality team. This is typically an inferred event, derived from a system status change indicating that work has commenced.
Why it matters This activity helps distinguish between the mere logging of an issue and the actual start of work. Analyzing the time lag between creation and this step reveals potential delays in issue acknowledgement and resource assignment. Where to get Inferred from a status change on the Quality Notification object. This can be tracked by analyzing status change logs in tables JEST and JCDS for a status like 'NOPO' (Notification in process). Capture Identify the timestamp when the 'in process' status is set for the notification in the JCDS table. Event type inferred
	Preventive Action Implemented	Marks the successful execution of the planned preventive action. This is captured by recording the completion of the corresponding preventive action task in the system.
Why it matters The completion of preventive actions is a vital step in mature quality processes. Tracking this activity helps measure the commitment to preventing future issues and reducing recurring problems. Where to get Inferred from the completion of a preventive action task in the QMSM table, indicated by the ERLDT field or a 'Completed' status change. Capture Identify the completion timestamp (ERLDT) of the preventive action task in the QMSM table. Event type inferred
	Preventive Action Proposed	This activity occurs when a plan is created to prevent the recurrence of a quality issue. Similar to corrective actions, it is often captured through the creation of a 'Preventive Action' task.
Why it matters This event is critical for assessing the organization's focus on proactive quality improvement rather than just reactive fixes. It marks the start of long-term resolution efforts. Where to get This event is captured upon the creation of a task with a 'Preventive Action' code in the QMSM table for the specific Quality Notification. Capture Use the creation timestamp (ERDAT) from the QMSM table for tasks with a preventive action type. Event type explicit
	Stakeholders Notified	Represents the communication of the resolution to relevant stakeholders, such as customers or internal departments. This is rarely an automated system event and is often a manual step.
Why it matters Timely stakeholder communication is critical for customer satisfaction and transparency. Measuring the delay between closure and notification can highlight gaps in communication processes. Where to get This activity is difficult to capture directly from SAP. It may be inferred from the completion of a manual task in QMSM labeled 'Notify Stakeholder' or would require analysis of external systems like email logs. Capture Identify completion of a manual communication task, if one is used. Otherwise, this is not typically available. Event type inferred

Recommended Optional

Extraction Guides

How to get your data from SAP S/4HANA Quality Management

Steps

Identify and Expose CDS Views: Confirm that the necessary Core Data Services (CDS) views are active in your SAP S/4HANA system. The primary views for this extraction are I_QualityNotification, I_QualityNotificationTask, and I_InspectionLotUsageDecision. Other views for status or text may also be relevant.
Activate OData Services: Navigate to the SAP Gateway Service Activation transaction /IWFND/MAINT_SERVICE. Add and activate the OData services corresponding to the CDS views you identified. For example, the service for I_QualityNotification is typically named API_QUALITYNOTIFICATION_SRV.
Grant Authorizations: Ensure the system user account designated for data extraction has the necessary authorizations to call the OData APIs and read from the underlying Quality Management tables. This includes authorizations for quality notifications, tasks, and inspection lots.
Establish OData Connection: Configure your data extraction or process mining tool to connect to the SAP S/4HANA OData endpoint. You will need the service URL, which can be found in /IWFND/MAINT_SERVICE, and the credentials for the authorized system user.
Structure Data Extraction Logic: The provided query represents the complete logic for building the event log. In practice, using OData, you will likely make separate API calls for each entity set (e.g., one call for notifications, one for tasks). The logic within each SELECT block in the query should be translated into OData URI parameters, such as $filter, $select, and $expand.
Fetch Notification Header Data: Execute an OData call to the I_QualityNotification service to retrieve the base events, such as 'Quality Notification Created', 'Notification Put In Process', 'Notification Completed', and 'Notification Closed'. Apply date and other filters to limit the data volume.
Fetch Notification Task Data: Execute a separate OData call to the I_QualityNotificationTask service. This will provide the data for task related activities, including 'Investigation Task Assigned', 'Root Cause Analysis Completed', 'Corrective Action Proposed', and others. You will need to filter this data by date and join it to the notification data later.
Fetch Usage Decision Data: If relevant, execute an OData call to the I_InspectionLotUsageDecision service to extract the 'Usage Decision Made' events. These records will need to be linked back to their corresponding quality notifications.
Combine and Transform Data: In your client tool or staging environment, combine the data retrieved from the different OData calls. Use the Quality Notification number as the common key. This step unifies the separate datasets into a single event log format, where each row represents one activity.
Map Columns for ProcessMind: Ensure the final output table has the required columns: QualityEvent, ActivityName, and EventTimestamp. Map the corresponding source fields from your combined dataset to these target columns.
Export and Upload: Export the final, transformed event log to a CSV file. Upload the file to your process mining tool for analysis.

Configuration

Key CDS Views: The primary views to expose as OData services are I_QualityNotification for header and status data, and I_QualityNotificationTask for detailed activities. I_InspectionLotUsageDecision is needed for events related to inspections.
Date Range Filtering: Always apply a date range filter on a creation or change date field, such as CreationDate in I_QualityNotification. We recommend starting with a recent period of 3 to 6 months to ensure manageable data volumes and faster extraction times.
Attribute Filtering: Use OData $filter parameters to narrow the scope of the extraction. Common filters include Plant, QualityNotificationType (e.g., 'Q1' for Customer Complaint, 'Q2' for Complaint against Vendor), and CompanyCode.
Task Code Configuration: The query logic for identifying specific tasks like 'Root Cause Analysis' or 'Corrective Action' relies on task codes (QualityNotificationTaskCode). These codes must be adjusted in the query's WHERE clauses to match the specific configuration of your SAP system.
Prerequisites: SAP Gateway must be configured, and the relevant OData services must be active. The user account for the connection requires appropriate S_SERVICE and QM authorizations.
Performance Considerations: OData performance depends heavily on efficient filtering. Avoid extracting all columns by using the $select parameter to specify only the required fields. For very large datasets, implement a paging strategy using $top and $skip to retrieve data in manageable chunks.

a Sample Query sql

SELECT
  noti.QualityNotification AS "QualityEvent",
  'Quality Notification Created' AS "ActivityName",
  noti.CreationDateTime AS "EventTimestamp",
  noti.CreatedByUser AS "ChangedBy",
  loc.WorkCenterInternalID AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotification AS noti
LEFT JOIN I_QltyNfnWorkCenterLocation AS loc ON noti.QualityNotification = loc.QualityNotification
WHERE noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  noti.QualityNotification AS "QualityEvent",
  'Notification Put In Process' AS "ActivityName",
  noti.LastChangeDateTime AS "EventTimestamp",
  noti.LastChangedByUser AS "ChangedBy",
  loc.WorkCenterInternalID AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotification AS noti
LEFT JOIN I_QltyNfnWorkCenterLocation AS loc ON noti.QualityNotification = loc.QualityNotification
WHERE noti.NotificationProcessStartDate IS NOT NULL AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Investigation Task Assigned' AS "ActivityName",
  task.CreationDateTime AS "EventTimestamp",
  task.CreatedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup = '[Your Investigation Task Code Group]' AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Root Cause Analysis Completed' AS "ActivityName",
  task.CompletionDateTime AS "EventTimestamp",
  task.LastChangedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  task.QualityNotificationTaskCause AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup = '[Your Root Cause Task Code Group]' AND task.CompletionDateTime IS NOT NULL AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT 
  ud.QualityNotification AS "QualityEvent",
  'Usage Decision Made' AS "ActivityName",
  ud.UsageDecisionDateTime AS "EventTimestamp",
  ud.UsageDecisionMadeByUser AS "ChangedBy",
  noti.ExecutingWorkCenter AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_InspectionLotUsageDecision AS ud
INNER JOIN I_QualityNotification AS noti ON ud.QualityNotification = noti.QualityNotification
WHERE ud.QualityNotification IS NOT NULL AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Corrective Action Proposed' AS "ActivityName",
  task.CreationDateTime AS "EventTimestamp",
  task.CreatedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup = '[Your Corrective Action Task Code Group]' AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Action Plan Approved' AS "ActivityName",
  task.ReleaseDateTime AS "EventTimestamp",
  task.LastChangedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup IN ('[Your Corrective Action Task Code Group]', '[Your Preventive Action Task Code Group]') AND task.ReleaseDateTime IS NOT NULL AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Corrective Action Implemented' AS "ActivityName",
  task.CompletionDateTime AS "EventTimestamp",
  task.LastChangedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup = '[Your Corrective Action Task Code Group]' AND task.CompletionDateTime IS NOT NULL AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Preventive Action Proposed' AS "ActivityName",
  task.CreationDateTime AS "EventTimestamp",
  task.CreatedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup = '[Your Preventive Action Task Code Group]' AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Preventive Action Implemented' AS "ActivityName",
  task.CompletionDateTime AS "EventTimestamp",
  task.LastChangedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup = '[Your Preventive Action Task Code Group]' AND task.CompletionDateTime IS NOT NULL AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Effectiveness Check Required' AS "ActivityName",
  task.CreationDateTime AS "EventTimestamp",
  task.CreatedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup = '[Your Effectiveness Check Task Code Group]' AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Action Effectiveness Verified' AS "ActivityName",
  task.CompletionDateTime AS "EventTimestamp",
  task.LastChangedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup = '[Your Effectiveness Check Task Code Group]' AND task.CompletionDateTime IS NOT NULL AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Stakeholders Notified' AS "ActivityName",
  task.CompletionDateTime AS "EventTimestamp",
  task.LastChangedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup = '[Your Stakeholder Notification Task Code Group]' AND task.CompletionDateTime IS NOT NULL AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  noti.QualityNotification AS "QualityEvent",
  'Notification Completed' AS "ActivityName",
  noti.CompletionDate AS "EventTimestamp",
  noti.LastChangedByUser AS "ChangedBy",
  loc.WorkCenterInternalID AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotification AS noti
LEFT JOIN I_QltyNfnWorkCenterLocation AS loc ON noti.QualityNotification = loc.QualityNotification
WHERE noti.IsCompleted = 'X' AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  noti.QualityNotification AS "QualityEvent",
  'Notification Closed' AS "ActivityName",
  noti.ArchivingDate AS "EventTimestamp",
  noti.LastChangedByUser AS "ChangedBy",
  loc.WorkCenterInternalID AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotification AS noti
LEFT JOIN I_QltyNfnWorkCenterLocation AS loc ON noti.QualityNotification = loc.QualityNotification
WHERE noti.IsArchived = 'X' AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

Steps

Identify and Expose CDS Views: Confirm that the necessary Core Data Services (CDS) views are active in your SAP S/4HANA system. The primary views for this extraction are I_QualityNotification, I_QualityNotificationTask, and I_InspectionLotUsageDecision. Other views for status or text may also be relevant.
Activate OData Services: Navigate to the SAP Gateway Service Activation transaction /IWFND/MAINT_SERVICE. Add and activate the OData services corresponding to the CDS views you identified. For example, the service for I_QualityNotification is typically named API_QUALITYNOTIFICATION_SRV.
Grant Authorizations: Ensure the system user account designated for data extraction has the necessary authorizations to call the OData APIs and read from the underlying Quality Management tables. This includes authorizations for quality notifications, tasks, and inspection lots.
Establish OData Connection: Configure your data extraction or process mining tool to connect to the SAP S/4HANA OData endpoint. You will need the service URL, which can be found in /IWFND/MAINT_SERVICE, and the credentials for the authorized system user.
Structure Data Extraction Logic: The provided query represents the complete logic for building the event log. In practice, using OData, you will likely make separate API calls for each entity set (e.g., one call for notifications, one for tasks). The logic within each SELECT block in the query should be translated into OData URI parameters, such as $filter, $select, and $expand.
Fetch Notification Header Data: Execute an OData call to the I_QualityNotification service to retrieve the base events, such as 'Quality Notification Created', 'Notification Put In Process', 'Notification Completed', and 'Notification Closed'. Apply date and other filters to limit the data volume.
Fetch Notification Task Data: Execute a separate OData call to the I_QualityNotificationTask service. This will provide the data for task related activities, including 'Investigation Task Assigned', 'Root Cause Analysis Completed', 'Corrective Action Proposed', and others. You will need to filter this data by date and join it to the notification data later.
Fetch Usage Decision Data: If relevant, execute an OData call to the I_InspectionLotUsageDecision service to extract the 'Usage Decision Made' events. These records will need to be linked back to their corresponding quality notifications.
Combine and Transform Data: In your client tool or staging environment, combine the data retrieved from the different OData calls. Use the Quality Notification number as the common key. This step unifies the separate datasets into a single event log format, where each row represents one activity.
Map Columns for ProcessMind: Ensure the final output table has the required columns: QualityEvent, ActivityName, and EventTimestamp. Map the corresponding source fields from your combined dataset to these target columns.
Export and Upload: Export the final, transformed event log to a CSV file. Upload the file to your process mining tool for analysis.

Configuration

Key CDS Views: The primary views to expose as OData services are I_QualityNotification for header and status data, and I_QualityNotificationTask for detailed activities. I_InspectionLotUsageDecision is needed for events related to inspections.
Date Range Filtering: Always apply a date range filter on a creation or change date field, such as CreationDate in I_QualityNotification. We recommend starting with a recent period of 3 to 6 months to ensure manageable data volumes and faster extraction times.
Attribute Filtering: Use OData $filter parameters to narrow the scope of the extraction. Common filters include Plant, QualityNotificationType (e.g., 'Q1' for Customer Complaint, 'Q2' for Complaint against Vendor), and CompanyCode.
Task Code Configuration: The query logic for identifying specific tasks like 'Root Cause Analysis' or 'Corrective Action' relies on task codes (QualityNotificationTaskCode). These codes must be adjusted in the query's WHERE clauses to match the specific configuration of your SAP system.
Prerequisites: SAP Gateway must be configured, and the relevant OData services must be active. The user account for the connection requires appropriate S_SERVICE and QM authorizations.
Performance Considerations: OData performance depends heavily on efficient filtering. Avoid extracting all columns by using the $select parameter to specify only the required fields. For very large datasets, implement a paging strategy using $top and $skip to retrieve data in manageable chunks.

a Sample Query sql

SELECT
  noti.QualityNotification AS "QualityEvent",
  'Quality Notification Created' AS "ActivityName",
  noti.CreationDateTime AS "EventTimestamp",
  noti.CreatedByUser AS "ChangedBy",
  loc.WorkCenterInternalID AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotification AS noti
LEFT JOIN I_QltyNfnWorkCenterLocation AS loc ON noti.QualityNotification = loc.QualityNotification
WHERE noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  noti.QualityNotification AS "QualityEvent",
  'Notification Put In Process' AS "ActivityName",
  noti.LastChangeDateTime AS "EventTimestamp",
  noti.LastChangedByUser AS "ChangedBy",
  loc.WorkCenterInternalID AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotification AS noti
LEFT JOIN I_QltyNfnWorkCenterLocation AS loc ON noti.QualityNotification = loc.QualityNotification
WHERE noti.NotificationProcessStartDate IS NOT NULL AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Investigation Task Assigned' AS "ActivityName",
  task.CreationDateTime AS "EventTimestamp",
  task.CreatedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup = '[Your Investigation Task Code Group]' AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Root Cause Analysis Completed' AS "ActivityName",
  task.CompletionDateTime AS "EventTimestamp",
  task.LastChangedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  task.QualityNotificationTaskCause AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup = '[Your Root Cause Task Code Group]' AND task.CompletionDateTime IS NOT NULL AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT 
  ud.QualityNotification AS "QualityEvent",
  'Usage Decision Made' AS "ActivityName",
  ud.UsageDecisionDateTime AS "EventTimestamp",
  ud.UsageDecisionMadeByUser AS "ChangedBy",
  noti.ExecutingWorkCenter AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_InspectionLotUsageDecision AS ud
INNER JOIN I_QualityNotification AS noti ON ud.QualityNotification = noti.QualityNotification
WHERE ud.QualityNotification IS NOT NULL AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Corrective Action Proposed' AS "ActivityName",
  task.CreationDateTime AS "EventTimestamp",
  task.CreatedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup = '[Your Corrective Action Task Code Group]' AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Action Plan Approved' AS "ActivityName",
  task.ReleaseDateTime AS "EventTimestamp",
  task.LastChangedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup IN ('[Your Corrective Action Task Code Group]', '[Your Preventive Action Task Code Group]') AND task.ReleaseDateTime IS NOT NULL AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Corrective Action Implemented' AS "ActivityName",
  task.CompletionDateTime AS "EventTimestamp",
  task.LastChangedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup = '[Your Corrective Action Task Code Group]' AND task.CompletionDateTime IS NOT NULL AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Preventive Action Proposed' AS "ActivityName",
  task.CreationDateTime AS "EventTimestamp",
  task.CreatedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup = '[Your Preventive Action Task Code Group]' AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Preventive Action Implemented' AS "ActivityName",
  task.CompletionDateTime AS "EventTimestamp",
  task.LastChangedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup = '[Your Preventive Action Task Code Group]' AND task.CompletionDateTime IS NOT NULL AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Effectiveness Check Required' AS "ActivityName",
  task.CreationDateTime AS "EventTimestamp",
  task.CreatedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup = '[Your Effectiveness Check Task Code Group]' AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Action Effectiveness Verified' AS "ActivityName",
  task.CompletionDateTime AS "EventTimestamp",
  task.LastChangedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup = '[Your Effectiveness Check Task Code Group]' AND task.CompletionDateTime IS NOT NULL AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  task.QualityNotification AS "QualityEvent",
  'Stakeholders Notified' AS "ActivityName",
  task.CompletionDateTime AS "EventTimestamp",
  task.LastChangedByUser AS "ChangedBy",
  task.ExecutingDepartment AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotificationTask AS task
INNER JOIN I_QualityNotification AS noti ON task.QualityNotification = noti.QualityNotification
WHERE task.QltyNotificationTaskCodeGroup = '[Your Stakeholder Notification Task Code Group]' AND task.CompletionDateTime IS NOT NULL AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  noti.QualityNotification AS "QualityEvent",
  'Notification Completed' AS "ActivityName",
  noti.CompletionDate AS "EventTimestamp",
  noti.LastChangedByUser AS "ChangedBy",
  loc.WorkCenterInternalID AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotification AS noti
LEFT JOIN I_QltyNfnWorkCenterLocation AS loc ON noti.QualityNotification = loc.QualityNotification
WHERE noti.IsCompleted = 'X' AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

UNION ALL

SELECT
  noti.QualityNotification AS "QualityEvent",
  'Notification Closed' AS "ActivityName",
  noti.ArchivingDate AS "EventTimestamp",
  noti.LastChangedByUser AS "ChangedBy",
  loc.WorkCenterInternalID AS "ResponsibleDepartment",
  noti.QualityNotificationType AS "QualityNotificationType",
  noti.Material AS "MaterialNumber",
  noti.NotificationPriority AS "NotificationPriority",
  NULL AS "RootCauseCode",
  noti.RequiredEndDate AS "TargetResolutionDate"
FROM I_QualityNotification AS noti
LEFT JOIN I_QltyNfnWorkCenterLocation AS loc ON noti.QualityNotification = loc.QualityNotification
WHERE noti.IsArchived = 'X' AND noti.CreationDate BETWEEN '[START_DATE]' AND '[END_DATE]'

Steps

Prerequisites: Ensure you have Python installed on your system. Install the required libraries, SAP PyRFC for SAP connectivity and Pandas for data manipulation, using pip: pip install pyrfc pandas. You must also download the SAP NetWeaver RFC SDK from the SAP Support Portal and place its lib folder in a location accessible by your system's library path.
SAP Connection Configuration: In the provided Python script, locate the connection parameter section. Fill in your SAP system's details, including the Application Server (ashost), System Number (sysnr), Client (client), User (user), and Password (passwd). It is highly recommended to use a secure method for storing credentials instead of hardcoding them, such as environment variables or a credential management service.
Define Extraction Scope: Set the date range for the extraction by modifying the start_date and end_date variables in the script. You can also specify other filters, such as notification_types, to narrow down the selection of quality notifications.
Execute Initial Query: The script first calls the BAPI_QUALNOT_GETLIST function to retrieve a list of all quality notification numbers that match the specified date and filter criteria. This provides the primary case identifiers for the subsequent steps.
Iterate and Fetch Details: The script then loops through each notification number obtained in the previous step. Inside the loop, it calls the BAPI_QUALNOT_GETDETAIL BAPI to fetch comprehensive information for that specific notification, including header data, status information, tasks, causes, and related activities.
Generate Event Log Activities: For each notification, the script processes the detailed data retrieved from the BAPI. It logically constructs individual rows for each of the 15 required business activities. This involves checking status changes, task creation dates, and task completion dates to generate events like 'Quality Notification Created', 'Investigation Task Assigned', and 'Notification Closed', each with a corresponding timestamp.
Map and Structure Data: As events are generated, the script maps the technical SAP field names to the user-friendly column names required for the event log, such as QualityEvent, ActivityName, and EventTimestamp. All generated event rows are collected into a single list.
Create and Export DataFrame: Once the loop finishes processing all notifications, the script converts the list of events into a Pandas DataFrame. This structured format is ideal for analysis and export.
Save the Event Log: The final step is to save the DataFrame to a CSV file. The script includes a line df.to_csv('quality_management_event_log.csv', index=False) which you can execute to create the final output file, ready for upload to ProcessMind.

Configuration

SAP Connection Credentials: The script requires a dedicated SAP user with sufficient authorizations to execute RFC calls and access Quality Management data. The required BAPIs include BAPI_QUALNOT_GETLIST and BAPI_QUALNOT_GETDETAIL.
Date Range: To manage performance and data volume, it is crucial to define a specific date range. For an initial analysis, a period of 3 to 6 months is recommended. The script uses a CREATED_FROM and CREATED_TO selection for this.
Notification Type Filter: You can filter the extraction to specific types of quality notifications (e.g., F1 for Customer Complaint, F2 for Internal Problem). This is configured via the notification_types list in the script and helps focus the analysis on a particular process variant.
Task Code Configuration: The script identifies specific activities like 'Root Cause Analysis Completed' or 'Corrective Action Implemented' by looking for specific codes associated with tasks. You MUST update the placeholder task codes, for example [Your Root Cause Task Code], in the script to match the codes configured in your SAP system's catalog for QM Tasks (Catalog type '2').
Python Environment: The script requires Python 3.6 or higher, along with the pyrfc and pandas libraries. The SAP NW RFC SDK must also be correctly installed and accessible.

a Sample Query python

import pandas as pd
from pyrfc import Connection
from datetime import datetime, timedelta

class=class="hl-string">"hl-comment"># --- 1. SAP Connection and Extraction Parameters ---
class=class="hl-string">"hl-comment"># IMPORTANT: Use a secure method like environment variables or a key vault for credentials.
SAP_CONNECTION_PARAMS = {
    class="hl-string">"user": class="hl-string">"[Your SAP User]",
    class="hl-string">"passwd": class="hl-string">"[Your Password]",
    class="hl-string">"ashost": class="hl-string">"[Your SAP Host IP/Hostname]",
    class="hl-string">"sysnr": class="hl-string">"[Your System Number]",
    class="hl-string">"client": class="hl-string">"[Your Client]",
}

class=class="hl-string">"hl-comment"># Define the extraction period
end_date = datetime.now()
start_date = end_date - timedelta(days=180) class=class="hl-string">"hl-comment"># Default to last 6 months

class=class="hl-string">"hl-comment"># Define filters (optional)
class=class="hl-string">"hl-comment"># Example: [class="hl-string">'F1', class="hl-string">'F2'] for Customer Complaint and Internal Problem
notification_types = [] class=class="hl-string">"hl-comment"># Leave empty for all types

class=class="hl-string">"hl-comment"># IMPORTANT: Configure your system's specific task codes
TASK_CODE_CONFIG = {
    class="hl-string">'INVESTIGATION': class="hl-string">'[Your Investigation Task Code]',
    class="hl-string">'ROOT_CAUSE': class="hl-string">'[Your Root Cause Task Code]',
    class="hl-string">'CORRECTIVE_ACTION': class="hl-string">'[Your Corrective Action Task Code]',
    class="hl-string">'PREVENTIVE_ACTION': class="hl-string">'[Your Preventive Action Task Code]',
    class="hl-string">'EFFECTIVENESS_CHECK': class="hl-string">'[Your Effectiveness Check Task Code]',
    class="hl-string">'STAKEHOLDER_NOTIFICATION': class="hl-string">'[Your Stakeholder Notification Task Code]'
}

def format_sap_timestamp(sap_date, sap_time):
    class="hl-string">"""Combine SAP date and time fields into a single datetime object."""
    if not sap_date or sap_date == class="hl-string">'00000000':
        return None
    if not sap_time or len(sap_time) < 6:
        sap_time = class="hl-string">'000000'
    return datetime.strptime(fclass="hl-string">"{sap_date}{sap_time}", class="hl-string">'%Y%m%d%H%M%S')

class=class="hl-string">"hl-comment"># --- 2. Main Extraction Logic ---
def extract_quality_events():
    event_log = []
    try:
        class=class="hl-string">"hl-comment"># Establish connection
        conn = Connection(**SAP_CONNECTION_PARAMS)
        print(class="hl-string">"Successfully connected to SAP.")

        class=class="hl-string">"hl-comment"># Get list of Quality Notifications
        print(fclass="hl-string">"Fetching notifications from {start_date.strftime('%Y%m%d')} to {end_date.strftime('%Y%m%d')}...")
        notif_list_result = conn.call(class="hl-string">'BAPI_QUALNOT_GETLIST',
                                      DATE_FROM=start_date.strftime(class="hl-string">'%Y%m%d'),
                                      DATE_TO=end_date.strftime(class="hl-string">'%Y%m%d'),
                                      NOTIF_TYPE=notification_types)

        notif_numbers = [item[class="hl-string">'NOTIF_NO'] for item in notif_list_result[class="hl-string">'NOTIF_LIST']]
        print(fclass="hl-string">"Found {len(notif_numbers)} notifications to process.")

        class=class="hl-string">"hl-comment"># Process each notification to get details
        for i, notif_no in enumerate(notif_numbers):
            print(fclass="hl-string">"Processing notification {i+1}/{len(notif_numbers)}: {notif_no}")
            try:
                detail_result = conn.call(class="hl-string">'BAPI_QUALNOT_GETDETAIL', NOTIF_NO=notif_no)
                header = detail_result.get(class="hl-string">'NOTIFHEADER_EXPORT', {})
                tasks = detail_result.get(class="hl-string">'NOTIFTASK_EXPORT', [])
                statuses = detail_result.get(class="hl-string">'NOTIFSTATUS', [])

                if not header:
                    continue

                class=class="hl-string">"hl-comment"># Common attributes for all events for this case
                common_attrs = {
                    class="hl-string">'QualityEvent': header.get(class="hl-string">'NOTIF_NO'),
                    class="hl-string">'QualityNotificationType': header.get(class="hl-string">'NOTIF_TYPE'),
                    class="hl-string">'MaterialNumber': header.get(class="hl-string">'MATERIAL'),
                    class="hl-string">'NotificationPriority': header.get(class="hl-string">'PRIORITY'),
                    class="hl-string">'TargetResolutionDate': format_sap_timestamp(header.get(class="hl-string">'REQ_END_D'), header.get(class="hl-string">'REQ_END_T')),
                    class="hl-string">'ResponsibleDepartment': header.get(class="hl-string">'DEPT_RESP'),
                    class=class="hl-string">"hl-comment"># Root Cause is often at cause level, this is a simplification
                    class="hl-string">'RootCauseCode': detail_result.get(class="hl-string">'NOTIFCAUS_EXPORT', [{}])[0].get(class="hl-string">'CAUSE_CODE')
                }

                class=class="hl-string">"hl-comment"># --- Generate events based on BAPI data ---

                class=class="hl-string">"hl-comment"># 1. Quality Notification Created
                created_ts = format_sap_timestamp(header.get(class="hl-string">'CREATE_DATE'), header.get(class="hl-string">'CREATE_TIME'))
                if created_ts:
                    event_log.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Quality Notification Created', class="hl-string">'EventTimestamp': created_ts, class="hl-string">'ChangedBy': header.get(class="hl-string">'CREATED_BY')})

                class=class="hl-string">"hl-comment"># 2. Notification Put In Process
                in_process_status = next((s for s in statuses if s[class="hl-string">'STAT'].startswith(class="hl-string">'I0002')), None)
                if in_process_status:
                    class=class="hl-string">"hl-comment"># BAPI doesn't provide easy access to status change timestamp, using header change date as approximation
                    changed_ts = format_sap_timestamp(header.get(class="hl-string">'CHANGE_DATE'), header.get(class="hl-string">'CHANGE_TIME'))
                    event_log.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Notification Put In Process', class="hl-string">'EventTimestamp': changed_ts, class="hl-string">'ChangedBy': header.get(class="hl-string">'CHANGED_BY')})

                class=class="hl-string">"hl-comment"># 3-13. Events from Tasks
                for task in tasks:
                    task_code = task.get(class="hl-string">'TASK_CODE')
                    task_created_ts = format_sap_timestamp(task.get(class="hl-string">'CREATE_DATE'), task.get(class="hl-string">'CREATE_TIME'))
                    task_completed_ts = format_sap_timestamp(task.get(class="hl-string">'COMPLETE_DATE'), task.get(class="hl-string">'COMPLETE_TIME'))
                    task_released_ts = format_sap_timestamp(task.get(class="hl-string">'RELEASE_DATE'), None) class=class="hl-string">"hl-comment"># Time not available for release
                    user = task.get(class="hl-string">'COMPLETED_BY') or task.get(class="hl-string">'CREATED_BY')

                    if task_code == TASK_CODE_CONFIG[class="hl-string">'INVESTIGATION'] and task_created_ts:
                        event_log.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Investigation Task Assigned', class="hl-string">'EventTimestamp': task_created_ts, class="hl-string">'ChangedBy': task.get(class="hl-string">'CREATED_BY')})
                    elif task_code == TASK_CODE_CONFIG[class="hl-string">'ROOT_CAUSE'] and task_completed_ts:
                        event_log.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Root Cause Analysis Completed', class="hl-string">'EventTimestamp': task_completed_ts, class="hl-string">'ChangedBy': user})
                    elif task_code == TASK_CODE_CONFIG[class="hl-string">'CORRECTIVE_ACTION']:
                        if task_created_ts:
                            event_log.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Corrective Action Proposed', class="hl-string">'EventTimestamp': task_created_ts, class="hl-string">'ChangedBy': task.get(class="hl-string">'CREATED_BY')})
                        if task_released_ts: class=class="hl-string">"hl-comment"># Approximating approval with release
                            event_log.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Action Plan Approved', class="hl-string">'EventTimestamp': task_released_ts, class="hl-string">'ChangedBy': task.get(class="hl-string">'CHANGED_BY')})
                        if task_completed_ts:
                            event_log.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Corrective Action Implemented', class="hl-string">'EventTimestamp': task_completed_ts, class="hl-string">'ChangedBy': user})
                    elif task_code == TASK_CODE_CONFIG[class="hl-string">'PREVENTIVE_ACTION']:
                        if task_created_ts:
                            event_log.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Preventive Action Proposed', class="hl-string">'EventTimestamp': task_created_ts, class="hl-string">'ChangedBy': task.get(class="hl-string">'CREATED_BY')})
                        if task_completed_ts:
                            event_log.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Preventive Action Implemented', class="hl-string">'EventTimestamp': task_completed_ts, class="hl-string">'ChangedBy': user})
                    elif task_code == TASK_CODE_CONFIG[class="hl-string">'EFFECTIVENESS_CHECK']:
                        if task_created_ts:
                            event_log.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Effectiveness Check Required', class="hl-string">'EventTimestamp': task_created_ts, class="hl-string">'ChangedBy': task.get(class="hl-string">'CREATED_BY')})
                        if task_completed_ts:
                            event_log.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Action Effectiveness Verified', class="hl-string">'EventTimestamp': task_completed_ts, class="hl-string">'ChangedBy': user})
                    elif task_code == TASK_CODE_CONFIG[class="hl-string">'STAKEHOLDER_NOTIFICATION'] and task_completed_ts:
                        event_log.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Stakeholders Notified', class="hl-string">'EventTimestamp': task_completed_ts, class="hl-string">'ChangedBy': user})
                
                class=class="hl-string">"hl-comment"># 5. Usage Decision Made (Conceptual - requires Inspection Lot logic)
                class=class="hl-string">"hl-comment"># This is a placeholder. A full implementation would check for a linked inspection lot
                class=class="hl-string">"hl-comment"># (e.g., in notification long text or object key tables) and then call another BAPI
                class=class="hl-string">"hl-comment"># like BAPI_INSPLOT_GETUSAGEDECISION to get the decision date.

                class=class="hl-string">"hl-comment"># 14. Notification Completed
                completed_status = next((s for s in statuses if s[class="hl-string">'STAT'].startswith(class="hl-string">'I0045')), None)
                if completed_status:
                    completed_ts = format_sap_timestamp(header.get(class="hl-string">'COMPLETE_DATE'), header.get(class="hl-string">'COMPLETE_TIME'))
                    if completed_ts:
                        event_log.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Notification Completed', class="hl-string">'EventTimestamp': completed_ts, class="hl-string">'ChangedBy': header.get(class="hl-string">'CHANGED_BY')})

                class=class="hl-string">"hl-comment"># 15. Notification Closed
                closed_status = next((s for s in statuses if s[class="hl-string">'STAT'].startswith(class="hl-string">'I0046')), None)
                if closed_status:
                    class=class="hl-string">"hl-comment"># Using header change date as approximation for close date
                    changed_ts = format_sap_timestamp(header.get(class="hl-string">'CHANGE_DATE'), header.get(class="hl-string">'CHANGE_TIME'))
                    event_log.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Notification Closed', class="hl-string">'EventTimestamp': changed_ts, class="hl-string">'ChangedBy': header.get(class="hl-string">'CHANGED_BY')})

            except Exception as e:
                print(fclass="hl-string">"  - Error processing notification {notif_no}: {e}")

        conn.close()
        print(class="hl-string">"Connection to SAP closed.")

    except Exception as e:
        print(fclass="hl-string">"An error occurred: {e}")
        return None

    if not event_log:
        print(class="hl-string">"No events were generated.")
        return pd.DataFrame()

    class=class="hl-string">"hl-comment"># Convert to DataFrame and sort for chronological order
    df = pd.DataFrame(event_log)
    df = df.sort_values(by=[class="hl-string">'QualityEvent', class="hl-string">'EventTimestamp']).reset_index(drop=True)
    return df

class=class="hl-string">"hl-comment"># --- 3. Run Extraction and Save to CSV ---
if __name__ == class="hl-string">"__main__":
    event_log_df = extract_quality_events()

    if event_log_df is not None and not event_log_df.empty:
        print(class="hl-string">"\nExtraction complete. Event log preview:")
        print(event_log_df.head())
        print(fclass="hl-string">"\nTotal events extracted: {len(event_log_df)}")
        
        class=class="hl-string">"hl-comment"># Save to CSV
        output_filename = class="hl-string">'quality_management_event_log.csv'
        event_log_df.to_csv(output_filename, index=False, date_format=class="hl-string">'%Y-%m-%dT%H:%M:%S')
        print(fclass="hl-string">"Event log saved to {output_filename}")

Steps

Create the ABAP Program: Open the ABAP Editor using transaction code SE38. Enter a name for your new program, for example, ZQM_PROCESS_EXTRACTION, and click 'Create'. Provide a suitable title, set the Type to 'Executable Program', and save it.
Define Program Parameters: In the program, define selection screen parameters to allow users to filter the data. Key parameters should include the notification creation date range (S_ERDAT), notification type (S_QMART), and plant (S_WERKS). This makes the extraction flexible and manageable.
Declare Data Structures: Define an internal table structure that will hold the final event log data. This structure must include all required and recommended attributes: QualityEvent, ActivityName, EventTimestamp, ChangedBy, ResponsibleDepartment, QualityNotificationType, MaterialNumber, NotificationPriority, RootCauseCode, and TargetResolutionDate.
Extract 'Quality Notification Created': Select data directly from the QMEL table for the creation event. The event timestamp is a combination of QMEL-ERDAT (creation date) and QMEL-ERZEIT (creation time). Map the relevant QMEL fields to your internal table structure.
Extract Status-Driven Events: To capture events like 'Notification Put In Process', 'Notification Completed', and 'Notification Closed', read from the status change log tables JEST and JCDS. Join them with QMEL using the object number (OBJNR). The timestamp for these events comes from JCDS-UDATE and JCDS-UTIME.
Extract Task-Based Events: For activities related to tasks, such as 'Investigation Task Assigned' or 'Corrective Action Implemented', select data from the tasks table QMSM and the causes table QMUR. Each task typically generates two events: one for creation (using fields QMSM-ERDAT/ERZEIT) and one for completion (using fields QMSM-PSTER/PSTUR). You must identify the specific task codes (MNGRP, MNCOD) used in your system for different activities like root cause analysis or corrective actions.
Extract Usage Decision Events: Join the inspection lot table QALS with the usage decision table QAVE using the inspection lot number (PRUEFLOS). The inspection lot can be linked back to the quality notification via table QAMB (if the link exists). The event timestamp is QAVE-VDATUM and QAVE-VZEIT.
Combine All Events: Append the results from each distinct query (creation, status changes, tasks, usage decisions) into the single final internal table you declared in step 3. This builds the complete, unified event log.
Write to Application Server File: Use the OPEN DATASET, LOOP AT, TRANSFER, and CLOSE DATASET statements in ABAP to write the contents of the final internal table to a flat file on the SAP application server. Use a clear delimiter, such as a semicolon or tab, to separate the columns.
Download the Event Log File: Use transaction code AL11 to locate the file on the application server directory. Once found, use transaction code CG3Y to download the file from the application server to your local machine for further processing and upload to ProcessMind.

Configuration

Authorization: The user executing the program needs authorization to access the ABAP workbench (S_DEVELOP) for program creation and execution, as well as read access to QM tables (QMEL, JCDS, QMSM, QAVE, etc.) and authorization for file system operations (S_DATASET).
Selection Criteria: It is crucial to use the selection screen parameters to limit the data scope. A date range of 3 to 6 months is recommended for initial analysis to ensure manageable data volume and performance. Always filter by key organizational units like plant or company code if applicable.
Task and Cause Codes: The extraction logic for task-based activities depends heavily on your system's specific configuration. You must identify the code groups and codes used for activities like 'Root Cause Analysis' or 'Corrective Action' in table QMSM (MNGRP, MNCOD) and QMUR (URGRP, URCOD). These will need to be configured in the WHERE clause of the ABAP SELECT statements.
System Performance: Extracting large volumes of data can impact system performance. Schedule the program to run during off-peak hours as a background job. Avoid excessively wide date ranges, especially for the first run.
File Format: The output file should be a delimited flat file, for example, CSV or TSV. Ensure the delimiter character you choose does not appear within the data itself to avoid parsing issues. The program should handle the proper formatting of date and time fields into a single timestamp column.

a Sample Query abap

REPORT ZQM_PROCESS_EXTRACTION.

*&---------------------------------------------------------------------*
*&-- Data Structure for the Final Event Log
*&---------------------------------------------------------------------*
TYPES: BEGIN OF ty_event_log,
         qualityevent          TYPE qmnum,
         activityname          TYPE string,
         eventtimestamp        TYPE timestamp,
         changedby             TYPE ernam,
         responsibledepartment TYPE veran_q,
         qualitynotificationtype TYPE qmart,
         materialnumber        TYPE matnr,
         notificationpriority  TYPE qmpr,
         rootcausecode         TYPE urcod,
         targetresolutiondate  TYPE qtrdd,
       END OF ty_event_log.

DATA: lt_event_log TYPE TABLE OF ty_event_log,
      ls_event_log TYPE ty_event_log.

*&---------------------------------------------------------------------*
*&-- Selection Screen Parameters
*&---------------------------------------------------------------------*
SELECT-OPTIONS: s_erdat FOR qmel-erdat OBLIGATORY,
                s_qmart FOR qmel-qmart.
PARAMETERS: p_file TYPE string DEFAULT '/usr/sap/trans/tmp/qm_event_log.csv'.

*&---------------------------------------------------------------------*
*&-- Main Program Logic
*&---------------------------------------------------------------------*
START-OF-SELECTION.

  DATA: lv_timestamp TYPE string.

*-- 1. Quality Notification Created
  SELECT qmnum, erdat, erzeit, ernam, veran, qmart, matnr, qmpr, qtrdd
    FROM qmel
    INTO TABLE @DATA(lt_qmel)
    WHERE erdat IN @s_erdat
      AND qmart IN @s_qmart.

  IF lt_qmel IS NOT INITIAL.
    LOOP AT lt_qmel INTO DATA(ls_qmel).
      ls_event_log-qualityevent          = ls_qmel-qmnum.
      ls_event_log-activityname          = 'Quality Notification Created'.
      CONCATENATE ls_qmel-erdat ls_qmel-erzeit INTO lv_timestamp.
      CONVERT DATE ls_qmel-erdat TIME ls_qmel-erzeit INTO TIME STAMP ls_event_log-eventtimestamp TIME ZONE sy-zonlo.
      ls_event_log-changedby             = ls_qmel-ernam.
      ls_event_log-responsibledepartment = ls_qmel-veran.
      ls_event_log-qualitynotificationtype = ls_qmel-qmart.
      ls_event_log-materialnumber        = ls_qmel-matnr.
      ls_event_log-notificationpriority  = ls_qmel-qmpr.
      ls_event_log-targetresolutiondate  = ls_qmel-qtrdd.
      CLEAR ls_event_log-rootcausecode.
      APPEND ls_event_log TO lt_event_log.
    ENDLOOP.
  ENDIF.

*-- 2, 14, 15. Status Changes: Put In Process, Completed, Closed
  SELECT qmel~qmnum, qmel~veran, qmel~qmart, qmel~matnr, qmel~qmpr, qmel~qtrdd, jcds~udate, jcds~utime, jcds~usnam, jcds~stat
    FROM jcds
    INNER JOIN jhst ON jhst~objnr = jcds~objnr AND jhst~spras = sy-langu
    INNER JOIN qmel ON qmel~objnr = jcds~objnr
    INTO TABLE @DATA(lt_jcds)
    WHERE qmel~erdat IN @s_erdat
      AND qmel~qmart IN @s_qmart
      AND jcds~stat IN ('I0002', 'I0045', 'I0046') "NOIN, NOCO, NOCL
      AND jcds~chgnr > 1 " Ignore initial creation status
      AND jcds~inact = ''.

  LOOP AT lt_jcds INTO DATA(ls_jcds).
    ls_event_log-qualityevent = ls_jcds-qmnum.
    CASE ls_jcds-stat.
      WHEN 'I0002'.
        ls_event_log-activityname = 'Notification Put In Process'.
      WHEN 'I0045'.
        ls_event_log-activityname = 'Notification Completed'.
      WHEN 'I0046'.
        ls_event_log-activityname = 'Notification Closed'.
    ENDCASE.
    CONVERT DATE ls_jcds-udate TIME ls_jcds-utime INTO TIME STAMP ls_event_log-eventtimestamp TIME ZONE sy-zonlo.
    ls_event_log-changedby             = ls_jcds-usnam.
    ls_event_log-responsibledepartment = ls_jcds-veran.
    ls_event_log-qualitynotificationtype = ls_jcds-qmart.
    ls_event_log-materialnumber        = ls_jcds-matnr.
    ls_event_log-notificationpriority  = ls_jcds-qmpr.
    ls_event_log-targetresolutiondate  = ls_jcds-qtrdd.
    CLEAR ls_event_log-rootcausecode.
    APPEND ls_event_log TO lt_event_log.
  ENDLOOP.

*-- 3, 4, 6, 8, 9, 10, 11, 12, 13. Task-based events
  SELECT qmel~qmnum, qmel~veran, qmel~qmart, qmel~matnr, qmel~qmpr, qmel~qtrdd,
         qmsm~erdat, qmsm~erzeit, qmsm~ernam, qmsm~pster, qmsm~pstur, qmsm~paenr, qmsm~mnkat, qmsm~mngrp, qmsm~mncod
    FROM qmsm
    INNER JOIN qmel ON qmel~qmnum = qmsm~qmnum
    INTO TABLE @DATA(lt_qmsm)
    WHERE qmel~erdat IN @s_erdat
      AND qmel~qmart IN @s_qmart.

*-- Root Cause from QMUR
  SELECT qmnum, ursac, urgrp, urcod
    FROM qmur
    INTO TABLE @DATA(lt_qmur)
    FOR ALL ENTRIES IN @lt_qmel
    WHERE qmnum = @lt_qmel-qmnum.

  LOOP AT lt_qmsm INTO DATA(ls_qmsm).
*-- Task Assigned / Action Proposed
    CLEAR ls_event_log.
    ls_event_log-qualityevent = ls_qmsm-qmnum.
    CASE ls_qmsm-mngrp.
      WHEN '[Your Investigate Task Group]'. ls_event_log-activityname = 'Investigation Task Assigned'.
      WHEN '[Your Corrective Task Group]'. ls_event_log-activityname = 'Corrective Action Proposed'.
      WHEN '[Your Preventive Task Group]'. ls_event_log-activityname = 'Preventive Action Proposed'.
      WHEN '[Your Effectiveness Task Group]'. ls_event_log-activityname = 'Effectiveness Check Required'.
      WHEN '[Your Stakeholder Notify Task Group]'. ls_event_log-activityname = 'Stakeholders Notified'.
      WHEN OTHERS. CONTINUE. " Skip tasks not relevant for process mining
    ENDCASE.
    CONVERT DATE ls_qmsm-erdat TIME ls_qmsm-erzeit INTO TIME STAMP ls_event_log-eventtimestamp TIME ZONE sy-zonlo.
    ls_event_log-changedby = ls_qmsm-ernam.
    ls_event_log-responsibledepartment = ls_qmsm-veran.
    ls_event_log-qualitynotificationtype = ls_qmsm-qmart.
    ls_event_log-materialnumber = ls_qmsm-matnr.
    ls_event_log-notificationpriority = ls_qmsm-qmpr.
    ls_event_log-targetresolutiondate = ls_qmsm-qtrdd.
    APPEND ls_event_log TO lt_event_log.

*-- Task Completed / Action Implemented / Verified
    IF ls_qmsm-pster IS NOT INITIAL AND ls_qmsm-pster <> '00000000'.
      CLEAR ls_event_log.
      ls_event_log-qualityevent = ls_qmsm-qmnum.
      CASE ls_qmsm-mngrp.
        WHEN '[Your Investigate Task Group]'. ls_event_log-activityname = 'Root Cause Analysis Completed'.
        WHEN '[Your Corrective Task Group]'. ls_event_log-activityname = 'Corrective Action Implemented'.
        WHEN '[Your Preventive Task Group]'. ls_event_log-activityname = 'Preventive Action Implemented'.
        WHEN '[Your Effectiveness Task Group]'. ls_event_log-activityname = 'Action Effectiveness Verified'.
        WHEN OTHERS. CONTINUE.
      ENDCASE.
      CONVERT DATE ls_qmsm-pster TIME ls_qmsm-pstur INTO TIME STAMP ls_event_log-eventtimestamp TIME ZONE sy-zonlo.
      ls_event_log-changedby = ls_qmsm-paenr.
      ls_event_log-responsibledepartment = ls_qmsm-veran.
      ls_event_log-qualitynotificationtype = ls_qmsm-qmart.
      ls_event_log-materialnumber = ls_qmsm-matnr.
      ls_event_log-notificationpriority = ls_qmsm-qmpr.
      ls_event_log-targetresolutiondate = ls_qmsm-qtrdd.
      READ TABLE lt_qmur INTO DATA(ls_qmur) WITH KEY qmnum = ls_qmsm-qmnum.
      IF sy-subrc = 0. ls_event_log-rootcausecode = ls_qmur-urcod. ENDIF.
      APPEND ls_event_log TO lt_event_log.
    ENDIF.
  ENDLOOP.

*-- 5. Usage Decision Made
  SELECT qmel~qmnum, qmel~veran, qmel~qmart, qmel~matnr, qmel~qmpr, qmel~qtrdd,
         qave~vdatum, qave~vzeit, qave~vaenr
    FROM qamb
    INNER JOIN qals ON qals~prueflos = qamb~prueflos
    INNER JOIN qave ON qave~prueflos = qals~prueflos
    INNER JOIN qmel ON qmel~qmnum = qamb~qmnum
    INTO TABLE @DATA(lt_qave)
    WHERE qmel~erdat IN @s_erdat
      AND qmel~qmart IN @s_qmart
      AND qave~vdatum <> '00000000'.

  LOOP AT lt_qave INTO DATA(ls_qave).
    ls_event_log-qualityevent          = ls_qave-qmnum.
    ls_event_log-activityname          = 'Usage Decision Made'.
    CONVERT DATE ls_qave-vdatum TIME ls_qave-vzeit INTO TIME STAMP ls_event_log-eventtimestamp TIME ZONE sy-zonlo.
    ls_event_log-changedby             = ls_qave-vaenr.
    ls_event_log-responsibledepartment = ls_qave-veran.
    ls_event_log-qualitynotificationtype = ls_qave-qmart.
    ls_event_log-materialnumber        = ls_qave-matnr.
    ls_event_log-notificationpriority  = ls_qave-qmpr.
    ls_event_log-targetresolutiondate  = ls_qave-qtrdd.
    CLEAR ls_event_log-rootcausecode.
    APPEND ls_event_log TO lt_event_log.
  ENDLOOP.

*-- NOTE: 'Action Plan Approved' is highly specific. It might be a task status change.
*-- This requires reading JCDS again for task object numbers (from QMSM-OBJNR)
*-- This example omits it for simplicity but it can be added here.

*-- Sort final table chronologically
  SORT lt_event_log BY qualityevent eventtimestamp.

*-- Write to file
  OPEN DATASET p_file FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
  IF sy-subrc <> 0.
    MESSAGE 'Error opening file.' TYPE 'E'.
    RETURN.
  ENDIF.

  DATA: lv_line TYPE string.
  DATA(lv_header) = 'QualityEvent;ActivityName;EventTimestamp;ChangedBy;ResponsibleDepartment;QualityNotificationType;MaterialNumber;NotificationPriority;RootCauseCode;TargetResolutionDate'.
  TRANSFER lv_header TO p_file.

  LOOP AT lt_event_log INTO ls_event_log.
    DATA(lv_ts_char) = |{ ls_event_log-eventtimestamp TIMESTAMP = ISO }|.
    CONCATENATE ls_event_log-qualityevent
                ls_event_log-activityname
                lv_ts_char
                ls_event_log-changedby
                ls_event_log-responsibledepartment
                ls_event_log-qualitynotificationtype
                ls_event_log-materialnumber
                ls_event_log-notificationpriority
                ls_event_log-rootcausecode
                ls_event_log-targetresolutiondate
      INTO lv_line SEPARATED BY ';'.
    TRANSFER lv_line TO p_file.
  ENDLOOP.

  CLOSE DATASET p_file.

  WRITE: / 'Extraction complete. File created at:', p_file.

Your Quality Management Data Template

Your Quality Management Data Template

Quality Management Attributes

Quality Management Activities

Extraction Guides

SAP S/4HANA QM CDS View Extraction via OData Service

Steps

Configuration

a Sample Query sql

Direct HANA DB Query on QM Transparent Tables

Steps

Configuration

a Sample Query sql

Python Extraction using SAP RFC and BAPI Functions

Steps

Configuration

a Sample Query python

Custom ABAP Program for Flat File Extraction

Steps

Configuration

a Sample Query abap

Ready to Get Started?

Boost Quality Management: Cut Cycle Time by 30% Instantly

Your Quality Management Data Template

Your Quality Management Data Template

Quality Management Attributes

Quality Management Activities

Extraction Guides

SAP S/4HANA QM CDS View Extraction via OData Service

Steps

Configuration

a Sample Query sql

Direct HANA DB Query on QM Transparent Tables

Steps

Configuration

a Sample Query sql

Python Extraction using SAP RFC and BAPI Functions

Steps

Configuration

a Sample Query python

Custom ABAP Program for Flat File Extraction

Steps

Configuration

a Sample Query abap

We value your privacy

Ready to Get Started?

Boost Quality Management: Cut Cycle Time by 30% Instantly