Managing Events Logs

Objective

After completing this lesson, you will be able to track the action in the environment.

Auditing and Traceability in Universal Models (UM)

In this lesson, we delve into the Manage Event Logs feature of the Universal Model, a pivotal tool for tracking changes and activities within the system. This feature provides a robust audit trail, ensuring transparency and accountability in your modeling environment.

The image shows the SAP Environment module interface, displaying general information about the DEMOENVM1 environment.

Step 1: Overview of Manage Event Logs

The Manage Event Logs application is designed to help users trace every action undertaken in the modeling environment. For example, if a user modifies a join configuration, deletes a function, or creates a node, these actions are meticulously logged. It ensures you can easily track who made the change and when it occurred.

Key Features:

  • Comprehensive Tracking: Logs all changes and activities within the system.​
  • User Accountability: Identifies the user responsible for actions taken.​
  • Timestamped Logs: Records the exact time when changes were made.

Step 2: Tracing Changes in Modeling

Specifically, event logs provide a detailed view of changes in your models, offering insights into:

  • User Actions: Identifying who changes specific elements (for example, joins, functions, nodes).​
  • Time Records: Documenting the precise time when changes were made.
  • Modification History: Maintaining a historical record of all modifications.

Step 3: Processing Logs

For process management within the UM, event logs offer valuable insights into various activities:

  • Process Deletion: Tracking which user deleted a process.​
  • Process Creation: Identifying who created a new process.
  • Process Execution: Understanding who executed a process.

Step 4: Data Records and Read Access

Event logs don't just track the creation and deletion of data records; they also capture read access, which is crucial for maintaining data security:

  • Access Patterns: Understanding who accessed specific data.​
  • Authorization Control: Ensuring that sensitive data is accessed by authorized users only.

Step 5: Granular Level Tracking

UM’s event logs provide an extraordinary level of detail, enabling granular tracing of all activities within the system:

  • Detailed Records: Capturing every action at a microlevel.​
  • Data Integrity: Ensuring the integrity of data by providing a complete activity picture.​
  • Security Assurance: Enhancing security through meticulous tracking.

Manage Event Logs in Modeling

The Manage Event Logs feature is essential for tracing every activity within the modeling environment of Universal Models (UM). This section delves into how this tool helps you maintain accountability, understand modification histories, and ensure the security and integrity of your models.

The image shows a diagram with three main sections: Modeling, Processing, and Data Records. Each section is highlighted with a label.

Step 1: Overview of Manage Event Logs

In the modeling environment, the Manage Event Logs tile is invaluable for tracking all user activities. Whether a user changes a rule, deletes a function, or creates a node, these actions are meticulously logged. It ensures that you can easily trace:

  • User Actions: Who made the change.​
  • Timestamp: When the change occurred.​
  • Practical Insight: Consider a situation where a critical business rule is unintentionally altered, impacting downstream data flows. Using the Manage Event Logs, you can quickly identify the responsible user and the precise time of the change, through expediting issue resolution and minimizing operational disruptions.

Step 2: Tracing Changes in Modeling

Event logs provide detailed insights into changes in the modeling environment. Specifically, they allow you to see:

  • Change Tracking: Who changed joins, functions, and nodes.​
  • Timestamp Details: The exact time when these changes were executed.

This level of detail is crucial for:

  • Maintaining Accountability: Ensuring that all actions can be traced back to a specific user.​
  • Modification History: Understanding the history of model modifications.

The Decoding of the Modeling Trace

User Actions:

As you can see on your screen, there's a fine trail that illustrates every user interaction. It showcases that an environment named Import Data was crafted by a user on April 11. The capable system captures not only the precise time of this action but also its duration.

The image shows the details of an SAP EventLog event, including general information, messages, statistics, fields, and parameters. The event details include the log ID, the event's URL, and various technical details.

The Modeling Activities

Following the same paper trail, you also note the user’s endeavors in the modeling arena. The user replicated a functionality, aptly named Importdatademo, on the same day, April 11. Once again, the time and the duration of this action are neatly recorded.​

The image displays detailed information about an SAP EventLog event, including general information, messages, statistics, and technical fields and parameters.

This glimpse gives you an insight into the remarkable detail that you can gather through Modeling Trace in SAP PaPM Cloud. Such detail not only enables you to track user activities but also equips you with the tools to audit those actions with commendable precision.​

As we proceed further in our exploration, you gain more insights into maximizing the power of SAP PaPM. So, let's keep the momentum going and dive even deeper into the sapient world of SAP PaPM Cloud.

Manage Event Logs application enables powerful auditability and tracking abilities. This video will help you to understand these posibilities within the Universal Model.

The Data Upload Activity

This example showcases the robust processing traceability features within SAP PaPM Cloud, providing comprehensive insights into how data processing activities are meticulously tracked and monitored. This level of traceability ensures that every step of the data processing journey is transparent and accountable, enhancing data integrity and operational efficiency.​

The image shows detailed information about an SAP EventLog event, including general information, messages, statistics, fields, and parameters.

Data Upload Activity: In this example, a user initiates a Data Upload activity. The process is tracked in real-time, capturing the successful completion of the upload. Specifically, one record was uploaded in a mere 0.23 seconds. This swift operation is logged, providing a clear and concrete record of the data ingestion process.​

Key Benefits:

Real-Time Monitoring: Instant feedback on the Data Upload process helps in identifying and resolving issues promptly.​

Performance Metrics: Tracking the time taken for uploads (for example, 0.23 seconds) allows for performance benchmarking and optimization.

The Data Processing Activity

Data Processing Activity: Following the Data Upload, the user runs a data processing activity. The traceability feature provides a detailed log of this process. The example shows that the activity began with an input of eight records. Upon completion, eight records were processed and produced as output, confirming the successful and error-free execution of the data processing task.​

The image shows detailed information about an SAP EventLog event, including general information, messages, statistics, fields, and parameters.

Key Benefits

  • Verification of Data Integrity: By matching the input and output records (eight records in, eight records out), you can verify that the data processing activity-maintained data integrity.​
  • Detailed Audits: Comprehensive logs facilitate audits by providing step-by-step records of each data processing operation.​
  • Performance Tracking: Monitoring how long each activity takes and its throughput helps in identifying bottlenecks and optimizing processes.​
  • Enhancing Data Processing Traceability: This level of traceability within SAP PaPM Cloud ensures that every step of the data processing journey is meticulously logged. By providing clear visibility into the performance and outcomes of each activity, organizations can achieve several key objectives:​
    • Operational Transparency: Full visibility into data processing activities enables organizations to understand and optimize their workflows.​
    • Error Detection and Resolution: Detailed logs allow for quick identification and correction of any errors or anomalies that occur during data processing.​
    • Compliance and Accountability: Traceability supports compliance with regulatory requirements by maintaining accurate and detailed records of all data-related activities. It creates an auditable trail that can be reviewed as needed.

In summary, the processing traceability features of SAP PaPM Cloud provide a robust framework for monitoring and logging data processing activities. This capability not only enhances operational efficiency and data integrity but also supports compliance, transparency, and accountability across the organization.

Logged Events

In the following, you will find a list of Logged Events.

Logged Events (01-20)

EvetDescription
DeactivateProcessRecords an action when user deactivates an active process
DELETERecords an action when user deletes any entity (function, field, process, data privilege,…)
eraseDataRecords an action when user erase (deletes) any data from the activity
eraseRulesRecords an action when user erase (deletes) all available rules in Dynamic Rules screen
exportDataRecords an action when user export data from Activity or from modeling (generates a CSV file)
exportEnvironmentRecords an action when user exports an environment through manage containers
exportEnvironmentDeltaRecords an action when user exports a smaller adjustment of the environment in the form of a delta container
exportRulesRecords an action when user export rules from Activity - Dynamic Rules (generates a CSV file)
importDataRecords an action when user import data from Activity or from the Show Screen (both, Activity and Modeling show screen)
importEnvironmentRecords an action when user imports the full or delta version of an environment to a tenant through Containers
importEnvironmentAsNewRecords an action when user imports an environment in the tenant with an option to update the environment ID
importRulesRecords an action when user imports rules into Activity (Dynamic Rules Screen)
LockDataRecords an action when user locks the data for editing
READRecords an action when user access any entity (function, field, process, data privilege,…)
rejectActivityRecords an action when user rejects the activity
removeDataRecords an action when user delete archived data records
removeEnvironmentRecords an action when user removes an environment
removeProcessRecords an action when user removes process
removeReportRecords an action when user removes Report

Logged Events (21-40)

EvetDescription
deactivateProcessRecords an action when user deactivates an active process
DELETERecords an action when user deletes any entity (function, field, process, data privilege,…)
eraseDataRecords an action when user erase (deletes) any data from the activity
eraseRulesRecords an action when user erase (deletes) all available rules in Dynamic Rules screen
exportDataRecords an action when user export data from Activity or from modeling (generates a CSV file)
exportEnvironmentRecords an action when user exports an environment through manage containers
exportEnvironmentDeltaRecords an action when user exports a smaller adjustment of the environment in the form of a delta container
exportRulesRecords an action when user export rules from Activity - Dynamic Rules (generates a CSV file)
importDataRecords an action when user import data from Activity or from the Show Screen (both, Activity and Modeling show screen)
importEnvironmentRecords an action when user imports the full or delta version of an environment to a tenant through Containers
importEnvironmentAsNewRecords an action when user imports an environment in the tenant with an option to update the environment ID
importRulesRecords an action when user imports rules into Activity (Dynamic Rules Screen)
lockDataRecords an action when user locks the data for editing
READRecords an action when user access any entity (function, field, process, data privilege,…)
rejectActivityRecords an action when user rejects the activity
removeDataRecords an action when user delete archived data records
removeEnvironmentRecords an action when user removes an environment
removeProcessRecords an action when user removes process
removeReportRecords an action when user removes Report

Logged Events (41-51)

EvetDescription
restoreArchiveRecords an action when user restores an archive entries
restoreDemoDataRecords an action when user restores demo data
runActivityRecords an action when user executes an activity
runFunctionRecords an action when user executes the function
setProtectionRecords when user puts protection to an environment/process
syncConnectionRecords when user syncs Connection in Manage Connection
syncModelsRecords when user syncs Model in Manage Connection
undeleteRecords an action when user restore deleted functions
undeployAllRecords an action when user undeploy (perform mass deactivation) for runtime objects
unlockDataRecords an action when user unlocks the data for editing in Activity
UPDATERecords an action when user perform any change in any entity (function, field, process, data privilege,…)

The Data Record Traceability

In SAP PaPM Cloud, data record traceability ensures that any changes to data are meticulously tracked, providing transparency and accountability.

The image shows a diagram with three main sections: Modeling, Processing, and Data Records

Understanding Data Record Traceability

  • Change Tracking: When a user changes any data records, the system logs these modifications. It includes who made the change, what was changed, and when the change occurred.​
  • Visibility: Every alteration is visible, allowing you to trace the history of data records. It ensures that any updates, deletions, or additions are fully auditable.​

With this level of traceability, you can confidently manage your data, knowing that all changes are recorded and can be reviewed when needed.

Example of Single Record Traceability

In SAP PaPM Cloud, traceability extends beyond merely tracking changes to data records. The platform provides comprehensive insights into who accessed specific data records, ensuring complete visibility and transparency into all interactions with your data. This level of single record traceability is vital for maintaining data integrity, security, and auditability.

Screenshot of SAP Show Emissions DPI app displaying a table of location-based emission records with columns for measure and gas type. The event log panel is open on the right, showing user activity history and changes for a selected entry.

Example of Single Record Traceability

Data Access: The system logs every instance of data access, recording details about who read a specific data record and the exact time when it occurred. For instance, one user accessed a particular data record on a designated day, and the trace also shows an attempted access by another user. This meticulous logging ensures that every read action is accounted for, providing a clear audit trail.​

Key Benefits: ​

Security Monitoring: Track unauthorized access attempts and ensure that sensitive information is safeguarded.​

User Accountability: Hold users accountable for their actions by maintaining a detailed access history.​

Audit Preparedness: Enhance your organization’s audit readiness by providing precise access logs.

Data Update: In addition to access logs, the system also provides detailed traces for data updates. For example, an activity team member updated a record where the original value was 10, changing it to 11. This traceability includes information about who made the update, what the original value was, what the new value is, and when the change occurred. It ensures that all modifications are fully documented and accountable.​

Key Benefits:​

Change Management: Easily identify who made specific changes to ensure data accuracy and accountability.​

Error Rectification: Quickly pinpoint and rectify any incorrect modifications by reviewing detailed update logs.​

Regulatory Compliance: Maintain compliance with industry regulations that require rigorous data tracking and auditability.​

Ensuring Full Auditability: This detailed level of traceability within SAP PaPM Cloud allows you to monitor not just data modifications but also data access within the system. Comprehensive audit trails help ensure that all interactions with data are fully traceable and transparent.

Learning

SAP FacebookSAP YoutubeSAP LinkedIn