Validation rules for data loads into Financial Consolidation

After you click Load Data in the Load Data dialog box, the validation process is started and its results are provided. The results include these elements:

Number of validated entities.
Number of entities that have been loaded successfully.
Number of entities for which a warning has been logged.
A warning indicates that data has been loaded and, if any data inconsistencies exist, that they have been logged.
Number of entities for which an error has been logged.
Entities with errors are skipped during a data load.

Download a log if any warnings or errors have been detected during validation.

Note: If you have access, you can view and download error logs also in d/EPM Administration. Select Dashboards > Logs > View Application Logs and specify applicable filters. In the Events field, select Modeling > Business Modeling > Load Facts (Load facts from Integration table). After you apply the filters, a list of log entries is displayed. Double-click a log entry to view detailed information in the Message pane. You can copy the message to the clipboard, if required. There are two log entries for each data load. One is for data validation, the other for the data import process.

ExchangeRate data is loaded based on the periods that you select in the Load Data dialog box.

Validation of a financial data load

Financial data is loaded from the BudgetingMain and FactsTransactionCurrency integration tables.

Validation of a financial data load is run only for entities and periods that you select in the Load Data dialog box.

Records in the BudgetingMain and FactsTransactionCurrency tables must refer only to base records of business objects. An error is logged if data is loaded into parents.

For the purposes of validation, business object records must be available in Business Modeling and must be published. Otherwise, an error is logged.

This list shows conditions under which validation errors and warnings are logged:

The Entity field must have a valid reference to the Entities business object record. Otherwise, an error is logged.
Values in the Entity and Intercompany fields can be the same only if the Intercompany property of the referenced group account is selected in Business Modeling. Otherwise, data from the BudgetingMain table is loaded to the External element of the Intercompany dimension, and records from the FactsTransactionCurrency table are ignored. In both cases, a warning is logged.
The Intercompany field must have a valid reference to the Intercompany business object record. Otherwise, data from the BudgetingMain table is loaded to the External element of the Intercompany dimension. In this case, records from the FactsTransactionCurrency table are ignored and excluded from a data load. In both cases, a warning is logged.
Note: We recommend that you leave the Intercompany field blank for external transactions.
If the Intercompany field of a record is populated, the value of the Intercompany property of the referenced group account must be True. Otherwise, a warning is logged.
The Account field must have a valid reference to the Accounts business object record. Otherwise, an error is logged.
For accounts of types A, L, E, and R, if an ID that refers to the group account is not specified or an ID that refers to an element of the Group Account dimension is not valid, then data is loaded to the Unassigned element of the Group Account dimension. A warning is logged. Records with statistical accounts of types S, M, T, and O are skipped and a warning is logged.
If the Currency field in the BudgetingMain table is blank or the value does not match the configuration of entity parameters, then an error is logged.
If the Currency field in the FactsTransactionCurrency table is blank or the value is invalid, then an error is logged.
The currency exchange rate must exist for all currencies in both integration tables. That is, each local currency must have an exchange rate for all group currencies. A warning is logged if an exchange rate is missing in any local currency-group currency combination.
Note: In the FactsTransactionCurrency table, the Currency field can be NULL. In the BudgetingMain table, the Currency field has a NOT NULL constraint.
The Level field must be blank or have a valid reference to the corresponding element in the Level dimension. The value of the Import attribute of that corresponding element must be True. If the corresponding element does not exist in the dimension or if the value of the element's Import attribute is False, then data rows are skipped and a warning is logged.
Note: The Import attribute is configured in Business Modeling. Select Modules > Consolidation > Core and click Data Management. On the Entity Levels Entry or Import tab, select the Import attribute for the required elements.
The BudgetingMain and FactsTransactionCurrency tables must contain data for the selected entities and periods. The ExchangeRate table must contain data for the selected periods. Otherwise, a warning is logged.

Custom business objects that have been defined as Segment 1, 2, or 3 must have a valid reference to the corresponding record in a custom business object. The corresponding record must be a child business object. Otherwise, a warning is logged.

This table shows how validation is applied for available segment configurations in the Consolidation Core:


Segment 1	Segment 2	Segment 3	Validation
No	No	No	No validation
Yes	No	No	Yes, Segment 1
Yes	Yes	No	Yes, Segment 1 and 2
Yes	Yes	Yes	Yes, Segment 1, 2, and 3

For records that contain intersegment information, these conditions must be met:

The corresponding record must exist in the corresponding Intercompany Partner Segment business object. Otherwise, a warning is logged.
The corresponding record cannot be a parent in the corresponding Intercompany Partner Segment business object. Otherwise, a warning is logged.
Segment and intercompany information must be specified in a record. Otherwise, a warning is logged.
Intersegment information must be specified in a record if segment and intercompany information is specified. Otherwise, a warning is logged.

This table shows how validation is applied for available Intercompany Partner segment configurations in the Consolidation Core:


Segment 1	Segment 2	Segment 3	Validation
No	No	No	No validation
Yes	No	No	Yes, Intercompany Partner Segment 1
Yes	Yes	No	Yes, Intercompany Partner Segment 1 and 2
Yes	Yes	Yes	Yes, Intercompany Partner Segment 1, 2, and 3

The ScheduleDetailID field from the BudgetingMain integration table must have a valid reference to the Schedule Details business object record. Otherwise, an error is logged. This does not apply if schedules are not used. That is, if schedules are not configured in the Core consolidation module and are not assigned to a Group Accounts business object record.

This table shows how validation is applied for different schedule configurations:


Account with schedule	Schedule with opening balance	Schedule with subschedules	Period	Load to schedule element	Validation
No	No	No	Any period	No load to the Schedule Details dimension.	No validation.
Yes	No	No	Any period	Load to the corresponding detail, excluding the opening balance detail.	Yes. The corresponding business object record must exist. Otherwise, an error is logged.
Yes	Yes	No	Period 0	Load to the corresponding opening balance detail. Controlled by Business Modeling.	No validation.
Yes	Yes	No	Any period other than 0	Load to the corresponding detail.	Yes. The corresponding business object record must exist. Otherwise, an error is logged.
Yes	Yes	Yes	Period 0	Load to the corresponding detail.	Yes. The corresponding business object record must exist. Otherwise, an error is logged. If no ID or incorrect ID is provided, the default subschedule for opening balances is used to detect to which opening balance element to load the opening balances.
Yes	Yes	Yes	Any period other than 0	Load to the corresponding detail.	Yes. The corresponding business object record must exist. Otherwise, an error is logged.

Data of the 0 period is loaded as opening balances to the opening balance elements of the Schedule Details dimension. Those opening balance elements are controlled by Business Modeling.

A group account can be assigned a schedule. If a schedule is not assigned, then these facts apply:

Data is not loaded to the Schedule Details dimension. Data of the 0 period is used only for the calculated YTD closing balance of the Finance cube in Financial Consolidation.
Validation is not required for any periods.

If a group account has a schedule with an opening balance assigned and no subschedule assigned, then these facts apply:

Data of the 0 period (opening balances) is loaded to the corresponding opening balance element of the Schedule Details dimension. That opening balance element is controlled by Business Modeling.
Data of any period other than period 0 (periodic data) is loaded to the corresponding schedule detail. Validation is required.

If a group account has a schedule with an opening balance and a subschedule assigned, then these facts apply:

Data of the 0 period (opening balances) is loaded to the corresponding opening balance element of the subschedules. If the schedule ID does not match the corresponding business object record in the Schedules dimension, then the default subschedule is used during a data load.
Data of any period other than period 0 (periodic data) is loaded to the corresponding schedule detail. If a schedule detail ID does not exist or is invalid, then data is not loaded and an error is logged.

If a group account has a schedule assigned without an opening balance, then data of any period is loaded to the corresponding schedule detail. If a schedule detail ID does not exist or is invalid, then data is not loaded and an error is logged.

Validation of an exchange rate load

Data from the ExchangeRate table is loaded to selected periods. These validations happen:

That entity currency and group currency columns refer to a valid and activated currency in the Currencies business object. If they do not, then rows that do not match are skipped and a warning is logged.
That, in integration, only currency exchange rates of types F (closing rates) and PA (periodic average rates) are used. Records with other rate types are skipped and a warning is logged.
That, for calculation of a rate of type A (average rate), the periodic average rates for the previous fiscal year periods are present. The previous periods must have a status of Open in Financial Consolidation. Otherwise, a warning is logged.