Executing a Flexible Upload 

Use

You use this procedure to execute a flexible upload in the consolidation monitor.

If data is to be entered on hierarchy nodes (that is, totals items), you have selected the corresponding indicator in Customizing for Version Combinations.

Prerequisites

You have defined the upload method in customizing of data collection.

 

Procedure

Starting the upload

...

       1.      Execute the file upload by running the data collection task in the consolidation monitor.

       2.      In the data collection screen, run the upload method.

       3.      If necessary, specify the name of the upload file.

You can also execute the flexible upload method from within the consolidation workbench.

Uploading data for combinations of consolidation units

If you are modeling a matrix organization, the consolidation system makes sure that the upload method is run for all valid combinations of consolidation units when the task is executed. The system collects the data for the combinations that are currently being processed from each respective file that was specified. The following applies, for example, when processing combinations of companies and profit centers:

·        If you have selected the upload mode Delete All, and your file does not contain any data for a given combination (such as, company 1/profit center 1), then the system resets the data for this combination.

·        If data for versions, fiscal years/periods, companies or profit centers is contained in the file but has not been selected for processing, the system simply ignores this data.

For example, if the upload file contains data for the combination company 2/profit center 1, the system ignores this data record when company 1 is processed.

This logic allows the use of large files (for example, files that contain for all consolidation units or files with data for multiple periods) without the need to split up the data for processing at the consolidation unit level. When such a file is uploaded, the system only reads the desired records.

Writing of data is suppressed when errors occur

The data records are only written if no errors occur. This is necessary to prevent follow-up errors. (For example, inconsistent reported financial data can lead to erroneous results in currency translation and rounding.)

Possible errors caused by existing data records

In addition to uploaded records, the system also checks the records to be written. Thus, the system also checks existing records in prior periods which are to be changed. Consequently, the following applies:

·        If data records exist for master data that does not exist (or no longer exists), the system does not change or delete these records.

·        If data records exist which are not (or no longer are) permitted to be written, the system cannot change or delete these records. For example, this can be the case if a required breakdown (without a default) by transaction type was added.

Writing data to the BW system

When an upload method is run in update mode and does not produce any errors, the data has not been written to BW yet. This takes place when you exit the screen of the data collection task. The system shows the running status in the status line of the screen.

Result

The system generates a log of the upload run.

In the log, always check which upload method was actually used. Keep the following in mind:

§         The task hierarchy is time and version dependent.

§         The assignment of the data collection method to the task is time, version, and period category dependent.

After the records have been written to BW, you can display the uploaded data in the list of totals records. To display the cumulative values for cross-checking the upload, restrict the period to the range of 000 to the desired period.