As a reminder, traceability logs allow you to trace generated quantities back to the source data, including the mapping rules they created. You'll see the rows from the upload files, corresponding rows from the mapping file, and the result row. When manually executing the mapping job, it was possible to select the "With traceability log" option.
GRDC also allows you to schedule mapping jobs to run automatically based on a set time and recurrence pattern.
With Release 2402 you have the ability to generate traceability logs for scheduled orders and push API. You can now activate the option in the job definition.
Then the user will not be able to start the mapping without this protocol. Automating log generation leads us to the next change. Previously you had to save the logs locally. If this didn't happen, the logs were gone.
When running a data mapping job with a traceability log, you can now use a remote folder location to save and read your traceability log file.
It is now possible to store a OneDrive or SharePoint where the protocols are stored centrally.
Now it can be ensured that EVERY change that goes into group reporting via GRDC mapping is also documented with the traceability protocol and these protocols are automatically stored for the auditor.
Would you like to know what else Release 2402 has in store? Then read the other articles:
Here Find out more about SAP Group Reporting!
