FAQ : Migrate to the new 360Eyes for SAP BusinessObjects Audit Job
Context
Version 2025.2 introduced changes to the behavior of 360Eyes Jobs.
Previously, we had a list of jobs consisting of:
- CMS
- Webi
- Crystal
- Universe
- IA & Other
Each job had an option to extract audit information. This could sometimes lead to the jobs extracting the information multiple times, resulting in longer overall job execution times.
We also copied the audit information from each snapshot if Delta mode was activated. Over time, this meant that more and more data was loaded into the snapshots, which could increase the copy time.
For a quick explanation of the new job, you can watch this video
Q: Do I need to change something?
The current jobs will no longer extract audit information, except for the CMS, which will continue to extract the User Sessions Audit. This means you either need to update your current 360Eyes Tasks to add the Audit Job, or create a new task for the audit job:
This action will allow you to configure the Audit Extraction.
Q: What will happen to my old data?
We won't delete any data. We will copy data from old tables to the new ones during the first job you run. The old data will still be present in the tables you have, and we will copy this data from snapshot to snapshot. This is done to keep your custom reports working and to avoid deleting data. We won't add new data to the old tables.
To provide the best data available, when performing your first audit job, we will copy your old data up to the "Number of months to audit" you choose. This way, you will have your old data, and the last few months (depending on the option you choose) will have the proper events extracted.
Rest assured that the old data will stay in the tables, even if we deprecate them.
Q: Why have a new type of job?
We created a new type of job for multiple reasons.
The first reason is that audit extraction was somewhat complicated to understand. Each type of job allowed audit extraction, and each one extracted specific audit information to specific snapshots.
This meant that to gather all audit data in one report, you had to fetch the data from different snapshots, which could be tedious.
With the new Audit job, since we aren't using snapshots, you will be able to have all your data in one place, making it easier to create reports on audit extraction.
Another reason is that including audit extraction in a job could make the job run for a long time, depending on the audit extracted.
With the new job, you will be able to extract the audit separately at any time, which will not impact the other jobs.
We also wanted to improve our audit process. Thanks to the feedback you provided, we noticed that some audit events were not being extracted. With this new job, you can now extract all audit events, including some security events that were not extracted in the previous job.
Q: What will happen to Universes and Reports
It depends on the type of universes and reports. The ones we provide will work properly with the newest data and won't have any issues.
If you have created custom reports and universes, they will still work, but only with the old audit data. This means you won't get any new data in those reports. You will need to update the dimensions to be able to use the newest data.
Your audit data will be available through our new universe called "360eyes_AUDIT".
Last updated 2 days ago