EXCEL subject or not subject to Auditable practice (was Re: Commit & Logic cycle)

[Frank Kolmann <Frank.Kolmann@xxxxxxxxx>]

Yes this is borderline RPG discussion, apologies in advance if rules broken.

To assume you need an entire CRS to go change control is assuming that 
one cannot put in place procedures for change control in Excel.

I had manual procedures that recorded the Excel scripts in a wiki.
The auditors could compare the wiki with the actual SQL script.
The auditors could run the Excel script and compare the output with the 
data the users provided.
The auditors even had their own DB tools to verify the Excel data.
Yes I did not do the full Excel VBA thing,  was too hard for me, and I 
agree an audit nightmare.
The auditable Excel reports were archived into a permanent unchangeable 
repository.

What I did was auditable traceable and passed the SOX tests, you are 
limited only by your ability,

fwiw  I was suggesting SQL replace RPG not Excel.

Frank


On 18/06/2021 10:33 am, x y wrote:
> The issue with Excel is that it's a programming language but not subject to
> programming best practices, like design reviews, acceptance testing, and
> change control.   It's a great data visibility and reporting tool for both
> users and programmers...as long as that's its scope.
>
> When a spreadsheet chock-full of formulas, logic, and unknown assumptions
> is put together by one person and drives critical management decisions, I
> look for independent confirmation.
>
> Yes, HLL programs can be guilty of the same sins, but hopefully the process
> has been visible to many more people.
>
> \reeve
>
> On Thu, Jun 17, 2021 at 5:06 PM Frank Kolmann<Frank.Kolmann@xxxxxxxxx>
> wrote:

mi