Running manual internal transfers

An internal transfer profile allows you to transfer data from one part of a SunSystems database to another part of the same database. This type of profile exports data and then re-imports it in one process.

During the process, Transfer Desk exports the requested data, manipulates it as required, and then imports it into another part of the database. Run-time options are applied to both the export and import process.

Uwaga: The same result can be achieved by chaining two separate profiles together; one export and one import.

By default, the options for the transfer are taken from the profile to be run. The profile specifies the following:

  • the source, target and method
  • runtime parameter values
  • transformations to be applied.

The runtime values provided in the transfer profile record, are used by Transfer Desk during the export process to select, sort and/or summarize the required data, and to output it to the required file.

If a parameter is set to allow runtime override, you can amend the values when you run the profile, before the transfer starts. These amended values are used during the transfer process, but are not saved back to the profile unless you amend them using Edit.

The data is transferred within the SunSystems database, using the runtime values and transformations supplied or attached to the profile. Transformations allow the values in the data to be manipulated during the transfer process.

Uwaga: It is possible to use range control when specifying an internal transfer profile, but the functionality is different to using range control in Ledger Exports. If an import from an internal transfer profile contains rejected journals, then Journal Number From is not updated.