Reconcile Upload
Use this command to submit changed data, including schedule data, to the Longview database.
Business processes often involve submitting files from a single source multiple times within a period. For example, month-end actuals data extracted from the general ledger (potentially large files) could be loaded into the application in several iterations to account for adjusting entries, with the differences between iterations usually very small.
The Reconcile Upload command is almost identical to the Upload command, except that DataArea contents are compared with current database contents, to submit changes only:
| Value | Description |
|---|---|
If the data does not exist in database... | it submits the data |
If the data does exist in the database, and the value is the same... | no submission occurs |
If the data does exist in the database, and the value is not the same... | it submits the new value |
If the database has a data intersection not referenced in the file... | it submits a zero |
Note: The RECONCILE UPLOAD command will only upload data to which the user has write access.
The Reconcile Upload command depends on the existence and status of the lock ID for the DataArea being uploaded as follows:
| Value | Description |
|---|---|
DataArea has a valid lock ID | Delta values will be uploaded. |
DataArea does not have a valid lock ID, and... | one or more locks exist that covers the entire DataArea: All writable data will be uploaded by reconciling the data in the DataArea with the data in the database. |
no lock exists that covers any part of the DataArea: The UPLOAD will fail. |
Note: The DataArea must be fully locked for the Reconcile Upload command to run successfully.
Syntax
RECONCILE UPLOAD DataAreaName ["Comment"] [BatchWait DisableServerRollup] [UploadBatchSize] where:
- DataAreaName is the name of the DataArea.
- Comment is an optional setting equivalent to having a BatchComment command before the UPLOAD command, enclosed in double quotation marks. If not specified, the batch has no comment.
- BatchWait is equivalent to having a BatchWait command before the UPLOAD command and can be one of the following:
- FALSE—Use this value if you want to exit without waiting for the batch to complete.
- TRUE—Use this value if you want to wait for the batch to complete.
- DisableServerRollup turns off the server rollup when set to TRUE, and has a default value of FALSE which leaves the server rollup on. This setting is the same as the ServerMath command.
- UploadBatchSize specifies how the upload batch is broken down and transferred to the Data Server. This has no effect on the submission itself, only on performance. The default value is 150000.
Note: If either BatchWait or DisableServerRollup is specified, the other must also be specified.
Syntax example
CREATE DATAAREA daMaster USING Master.lvdsp
CREATE LOCK daMaster USING Master.lvdsp
RECONCILE UPLOAD daMaster "Upload Batch" See also