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 Supplement of an Individual Development for CFR


The directory S1_KFR-Erweiterung_indiv_Spiegel contains files with definitions for enhancement of an individual transaction development without carry forward (liability development e.g.) by posting keys and development columns for additional automatic transactions (carry forward, changes in current period, etc.) like it is necessary for the purpose of cash flow reporting for accounts of this development. They contain posting keys like for a fully automatic transaction development which are allocated to the new checked but not balance relevant transaction development area '1'.

The data are defined for the individual transaction development key 'S1'. If you need them for other developments you have to substitute the development key in the files for each data line. Furthermore column numbers '21' to '35' are used. Thus assure that these columns aren't used already in your installation for other purposes. The new posting keys receive alphabetical keys to be distinguishable from the real posting keys (for maturity e.g.).

The batch file KPBSLXXX.txt contains the new posting keys 'D', 'E', 'F', 'K', 'L', 'ME', 'MF', 'NE', 'NF', 'Q' and 'V' with the according usage tags. Please assure that these posting keys are not yet used with another meaning. These posting keys are allocated to existing transaction development columns. You have to define separate transaction development columns and allocate the posting keys to them if you desire a separate analysis

These definitions may be adopted into your database with the aid of import applications. For this purpose copy all contained TXT files from this directory into the directory ...\idl\batch (or another import path specified in the options dialogue) on your local computer. Modify them there, if needed (see above). Then, in IDL Konsis, call the application IMPORT per click from the menue tree or short word entry, open the branch "Import masterfiles" by mouse click on the '+' symbol, mark the lines for

  • Import transaction development areas,
  • Import transaction development columns and
  • Import posting keys

and start the action "Run import-file (.TXT)" using the right mouse key. If you have activated the file dialogue (via "Options ...") you just have to accept the proposed files, if you had copied them into the indicated directory.

The imported definitions can be viewed by the application "Transaction development definition" (short word SPIDEF) and also be modified if necessary. However, you shouldn't modifiy the usage tags of posting keys, otherwise the automatic generation of the development transactions is endangered.

For initialization of carry forwards in the first period you have to perform the carry forward into this period (in case repeated only for this development). Then current changes are refreshed automatically.

Report definitions (column options, column descriptions and formulae lines) are not contained here, since the development (liabilities e.g.) is presented without the additional columns in general.

Published:

Batch Files for Supplement of an Individual Development for CFR


The directory S1_KFR-Erweiterung_indiv_Spiegel contains files with definitions for enhancement of an individual transaction development without carry forward (liability development e.g.) by posting keys and development columns for additional automatic transactions (carry forward, changes in current period, etc.) like it is necessary for the purpose of cash flow reporting for accounts of this development. They contain posting keys like for a fully automatic transaction development which are allocated to the new checked but not balance relevant transaction development area '1'.

The data are defined for the individual transaction development key 'S1'. If you need them for other developments you have to substitute the development key in the files for each data line. Furthermore column numbers '21' to '35' are used. Thus assure that these columns aren't used already in your installation for other purposes. The new posting keys receive alphabetical keys to be distinguishable from the real posting keys (for maturity e.g.).

The batch file KPBSLXXX.txt contains the new posting keys 'D', 'E', 'F', 'K', 'L', 'ME', 'MF', 'NE', 'NF', 'Q' and 'V' with the according usage tags. Please assure that these posting keys are not yet used with another meaning. These posting keys are allocated to existing transaction development columns. You have to define separate transaction development columns and allocate the posting keys to them if you desire a separate analysis

These definitions may be adopted into your database with the aid of import applications. For this purpose copy all contained TXT files from this directory into the directory ...\idl\batch (or another import path specified in the options dialogue) on your local computer. Modify them there, if needed (see above). Then, in IDL Konsis, call the application IMPORT per click from the menue tree or short word entry, open the branch "Import masterfiles" by mouse click on the '+' symbol, mark the lines for

  • Import transaction development areas,
  • Import transaction development columns and
  • Import posting keys

and start the action "Run import-file (.TXT)" using the right mouse key. If you have activated the file dialogue (via "Options ...") you just have to accept the proposed files, if you had copied them into the indicated directory.

The imported definitions can be viewed by the application "Transaction development definition" (short word SPIDEF) and also be modified if necessary. However, you shouldn't modifiy the usage tags of posting keys, otherwise the automatic generation of the development transactions is endangered.

For initialization of carry forwards in the first period you have to perform the carry forward into this period (in case repeated only for this development). Then current changes are refreshed automatically.

Report definitions (column options, column descriptions and formulae lines) are not contained here, since the development (liabilities e.g.) is presented without the additional columns in general.

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