Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Batch Files for Update of the Old Standard of Transaction Developments

The "old" standard for transaction development definitions had been provided as LieferBatch for all customers up to release 2012.0. With release 2013.0 new standard definitions for transaction developments are provided. Therefore this LieferBatch directory no longer contains complete transaction development definitions but rather supplements to the old standard e.g. due to new posting key usage tags.

The data are provided in the Excel file SPI.xlsm with references for IDL.XLSLINK. The data are splitted into several sheets of this file, one for each database table. For the time being there are data for only one table:

  • BSL - Posting keys
  • SSP - Columns of transaction development

The first sheet of the file is titled "General" and contains some central specifications on which the formulae of the following sheets refer. These are:

  • the name of the database (default name is "IDLDB")
  • the keys of the languages of descriptions
  • a unique valid-from period for all master data (default is "12.2012")

Please replace the specifications for database and valid-from period by the values applying for you or desired by you, respectively. The language keys are fixed, however, they can be overwritten by an invald value (e.g. 'XXX' instead of 'FRA') if you do not need descriptions in the respective language.

In the same way you can replace the keys of transaction developments by other values used in your installation. An exception is the development for shares, since the key 'B' is fixed. Transaction developments can be replaced by an invalid key (e.g. '%'), too, if you do not want to use this development. In this case you receive corresponding error messages when exporting the complete workbook.

The file contains amendments from different release updates. Therefore the page <BSL>contains a column for the release in which the supplement had been provided. Thus in case you only have to export the actual extensions.

Published:

Batch Files for Update of the Old Standard of Transaction Developments

The "old" standard for transaction development definitions had been provided as LieferBatch for all customers up to release 2012.0. With release 2013.0 new standard definitions for transaction developments are provided. Therefore this LieferBatch directory no longer contains complete transaction development definitions but rather supplements to the old standard e.g. due to new posting key usage tags.

The data are provided in the Excel file SPI.xlsm with references for IDL.XLSLINK. The data are splitted into several sheets of this file, one for each database table. For the time being there are data for only one table:

  • BSL - Posting keys
  • SSP - Columns of transaction development

The first sheet of the file is titled "General" and contains some central specifications on which the formulae of the following sheets refer. These are:

  • the name of the database (default name is "IDLDB")
  • the keys of the languages of descriptions
  • a unique valid-from period for all master data (default is "12.2012")

Please replace the specifications for database and valid-from period by the values applying for you or desired by you, respectively. The language keys are fixed, however, they can be overwritten by an invald value (e.g. 'XXX' instead of 'FRA') if you do not need descriptions in the respective language.

In the same way you can replace the keys of transaction developments by other values used in your installation. An exception is the development for shares, since the key 'B' is fixed. Transaction developments can be replaced by an invalid key (e.g. '%'), too, if you do not want to use this development. In this case you receive corresponding error messages when exporting the complete workbook.

The file contains amendments from different release updates. Therefore the page <BSL>contains a column for the release in which the supplement had been provided. Thus in case you only have to export the actual extensions.

For an optimal Community experience, Please view on Desktop
Powered by Zendesk