Journal Definition and Validation Setting
Journals allow users to make adjustments to data in the database, typically as part of the month-end or quarter-end process. During the review and analysis step, journals allow users to capture an audit trail of changes and adjustments made to the database. The purpose of validation is to prevent incorrect records being saved to the DataStore Object (advanced).
Features
Journal Template Definition
The primary requirement for journals is to track changes to data after the initial source data is input into the model. For example, the general ledger information is loaded into the model through the Data Manager. The model users can adjust this data and also track and report on the changes by, for example, amount, date, and user. Once a journal template is created, neither the dimension nor the data in the model can be deleted from the model.
For information about setting up journals and defining a journal template, see the related links below.
Validation Setting
Validations are designed to prevent incorrect DataStore Object (advanced) intersections from being saved. You cannot get data into a DataStore Object (advanced) without going through the Write-Back module. Therefore, validations are implemented in write-back, to ensure that invalid records cannot get into the DataStore Object (advanced) from any source, including journals, Data Manager packages, and manual data input. For example, a specified intercompany account with an empty Trading Partner dimension is blocked from being written into the DataStore Object (advanced).
To customize validation, in the SAP ABAP system enter the transaction code UJ_VALIDATION to configure the validation framework and customize the validation rules according to your business requirements. For more information, see Breakdown Validation.