Related topics
On this panel you enter necessary attributes to start the import of transactions to be brought into the open batch environment. You can decide if the transfer process should be interrupted when open batch transactions are created or if it should be continued until the transaction journal is finally updated. Currently A/R payments, A/R cash book payments and their related settlement transactions can be imported.
To select mandatory transfer attributes, you can either enter an already defined Batch import option code or manually enter all the required information.
| Step | Description |
|---|---|
| Preloading | Payment transactions from the A/R payment interface file are selected by the origin code values and then the selected interface transactions are automatically organized (preloaded) into dedicated files, i.e. Open batch native files. This is done in order to enable the maintenance of interface data in a similar manner as that of manual registration. During the preloading process the interface data is not validated. Transferred transactions are then grouped into batches (represented by batch headers), preloaded into native voucher files (represented by interface voucher headers) and preloaded into the payment native files (represented by interface payments). |
| Loading | During this step, the preloaded data is validated and if the data is valid, the corresponding batch transaction is created. The validation process starts at batch header level and if no errors are found, then the lower levels, e.g. the voucher, cash book header, payment and settlement levels are validated. If an error is found, the loading process is interrupted and the next level will not be validated. Erroneous interface and batch transactions are marked with dedicated error codes. |
| Batch update | If no errors exist for the batch transactions and all the batch related interface data are either successfully loaded/created or set to status Deleted, then the batch is submitted for update. |
You also have the possibility to determine if the data should be loaded all the way through until they are updated in the system or stopped after reaching a certain processing status. You can also decide to stop the import process at any of the above steps. See detailed information for the Stop after loading field.
- Batch import option
- Enter a code from Work with batch import options. The rest of the fields on this panel are automatically completed according to the code definition, but can be changed. If you do not enter a code in this field, then the other fields must be completed manually.
- Description
- Mandatory entry if a batch import code was not entered. Enter a description for the import. The description entered here will become the default Batch text that will be written to all the batch headers created by this import.
- Origin code
- Mandatory entry if a batch import code was not entered. Enter the origin code to identify the transactions that should be imported.
- Batch list profile
- Mandatory entry if a batch import code was not entered. Enter the batch list profile for the import. The batch list profile determines the lists that should be produced for the journal.
- Template
- Mandatory entry if a batch import code was not entered. Enter a template which is to be applied during transfer. During the loading process, the transferred data is completed based on the applied template definition. The template is also applied to display interface data on the entry panels.
Note: Only one template code can be selected for the import, the code you enter here identifies the template that should be used for all the relevant panels, i.e. for the batch/voucher header, cash book header and for the payment panels. Make sure that a template with the template name selected for this field exists for each of these panels.
- Stop after loading
- Mandatory entry if a batch import code was not entered. Indicate if the transaction transfer process should be stopped before batch update.