Difference between revisions of "Information Systems:Customizations to STM (Statements extension)"
(Created page with "=Overview= In 2008 Sheila further developed the STM - Statements extension to be able to edit EFT data and post EFT transactions to ASW. Prior to this, transactions had to be...") |
m |
||
| Line 15: | Line 15: | ||
=Known issues= |
=Known issues= |
||
| − | The commands that post transactions to ASW first write |
+ | The commands that post transactions to ASW first write records into ASW interface files and then call ASW programs to write to the <nowiki>"master"</nowiki> transaction files. This is because ASW transaction files cannot be written to directly, so intermediate interface files |
[[Category: Extensions]] |
[[Category: Extensions]] |
||
[[Category: Statements]] |
[[Category: Statements]] |
||
| + | [[Category: IT - Finance Problems]] |
||
Revision as of 15:08, 3 October 2016
Overview
In 2008 Sheila further developed the STM - Statements extension to be able to edit EFT data and post EFT transactions to ASW. Prior to this, transactions had to be manually entered in Accounting. This functionality is found in the STM menu/program View Statement Control Periods (ARRIQ400). The additional commands are :
- EG - Calculate EFT amounts
- EP - Print report of EFT amounts
- EE - Edit EFT amounts
- EC - Export credit EFT transactions to bank file
- ED - Export debit EFT transactions to bank file
- E1 - Build cash book entry for EFT credits
- E2 - Build cash book entry for EFT debits
As this was a customization made to the extension, these commands are not documented in the technical reference manuals that were produced when the extensions were written. Explore the program source for more info as Sheila comments her code well.
Known issues
The commands that post transactions to ASW first write records into ASW interface files and then call ASW programs to write to the "master" transaction files. This is because ASW transaction files cannot be written to directly, so intermediate interface files