Data collection, flexible upload and the Excel options

Consolidation is only as good as the reported data under it. Group Reporting offers three main ways in: the release task for units whose books are in the same SAP S/4HANA system, the flexible upload of CSV or XLSX files for units outside it, and APIs for automated feeds. Each needs its own tests, because each fails differently.

Integrated units: release the Universal Journal

For 1710 and 1810 the Release Universal Journal task in the Data Monitor reads the period's balances from ACDOCA, maps G/L accounts to FS items, derives partner units from the trading partner on each line, and writes level 00 data to ACDOCU. Nothing is re-keyed, so the usual errors are mapping errors: a new G/L account that is not mapped to an FS item, or an intercompany line posted without a trading partner, which arrives without a partner unit and cannot be eliminated later.

Non-integrated units: the flexible upload

Between the acquisition and the Wave 2 data migration, Alternadores del Norte still keeps its books in its non-SAP legacy ERP. For those quarter-ends, consolidation unit 1910 is non-integrated: its trial balance arrives as a file. The upload runs either from the Data Collection task in the Data Monitor or in the app Flexible Upload of Reported Financial Data, which can load several periods in one file.

1. Download the file template (CSV or XLSX) from the Data Collection task, so columns match the upload method assigned to the unit.
2. Map Alternadores' legacy accounts to Contoso's FS items outside SAP, with partner units for intercompany balances and subitems where the FS item needs them.
3. Check prerequisites: the period is open, the data entry task is unblocked for 1910, and the upload method is set in the consolidation unit's details in Define Consolidation Units.
4. Run a test import first: it reports errors without posting.
5. Choose the update mode: delete all resets the data block, overwrite posts only the delta for the same version, period, unit and document type, and add adds to what is there.
6. Import, then read the task log; messages should be information or success only.
7. Run net income calculation if the file does not carry the year's net income, then compare totals with the legacy trial balance.

Two details cause most upload defects. First, year-to-date versus periodic values: the file declares whether amounts are cumulative, and a periodic file loaded as year-to-date understates every month after January. Second, decimal separators: CSV files declare their separator in a parameter, while XLSX files follow the system's settings, so an MXN 1.234.567,89 written by a Mexican locale can load as a very different number. For corrections to data already released, a separate posting level (0C) is used; check which document types your configuration allows.

Excel, data entry forms and APIs

Finance teams ask for "the Excel add-in". In practice there are several Excel touchpoints, and it matters which one is meant. XLSX templates feed the flexible upload. SAP Analysis for Microsoft Office is SAP's Excel add-in for reporting on Group Reporting data. Manual data entry for units without a system has been offered through a separate data collection service with forms; its packaging and availability have changed over releases, so check the current offering and your contract before you design around it. For recurring feeds from other systems, APIs load reported data without files.

Validations are the safety net. Group Reporting's validation rules check reported data before it moves on: does the balance sheet balance, does each intercompany FS item have a partner unit, is net income consistent with retained earnings. The Data Monitor's validation task shows a traffic light per unit; a red light blocks the next task until the data is fixed or the error is explicitly accepted.

What goes wrong in testing

Testers often prove that a file loads, and stop. A load that succeeds with the wrong update mode, period type or sign convention still produces wrong group figures. Build negative tests on purpose: a file with an unmapped account, a file with a missing partner unit, a corrected file loaded twice, an XLSX with comma decimals. Each should be caught by the test import, a validation rule or the totals comparison, and the test should say which control caught it.