Information Systems:Auto cash not run as scheduled

From uniWIKI
Revision as of 10:48, 3 October 2017 by Norwinu (talk | contribs) (Created page with "Read more about auto-cash here. ==Problem description== Accounting_Finance:Auto_Cash-Running_Auto_Cash#Overview|Auto ca...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Read more about auto-cash here.

Problem description

Auto cash needs to run on period-end dates. Its program design currently does not allow for manual runs (i.e. for a select date range), and thus it is an issue when Auto Cash is not run on schedule. The problem is rare (happened in 2010, 2017), and will likely be very obvious - Accounting will report it and it will need to be fixed before they can run statements. The issue here is that the program uses the current date to create the entries.

Solution

The current fix involves hard-coding the date (setting date variables to a constant value) into the auto-cash program and recompiling. It requires some programming know-how - use caution.

  • Locate the source for Z1FR100 in XX2480BP (QRPGLESRC). This is the auto-cash application. Use Rational Developer.
  • Look for the lines labeled 'temp'. Fortunately, Sheila marked these when she encountered the problem in the past. These are the date variables.
  • Uncomment the line and set the date to the desired period-end date. For example, if running on Oct. 2 for Sep. 16 - Sep. 30, then use '20170930'.
  • (Optional) Comment the line above (where the variable is set to a dynamic value). Technically, it should be ok if you have two variable declarations (as a latter statement will always override the former one), but who knows, it's RPG.
  • Save the file, but do not compile.
  • On a green screen, locate the source again using WRKMBRPDM.
  • Enter 'AC' beside it and press F4. This stands for 'ASW Compile' and is a hidden option. This is important for making sure the program can access ASW files (doing a normal compile e.g. in RDi will cause issues when you run the application).
  • Ensure that you're compiling