6. Generalized Data Input Systems (GDIS).

Includes centralized procedures to manage the data input for all of the organizations transaction processing system.

Advantages:
It improves control by having one common system perform all data validation. It measures that each AIS application applies a consistent standard for data validation. Improves systems development efficiency.

Generalized Data Input System

Five major components:

Generalized validation module (GVM)
performs standard validation routines that are common to many different applications. Validated data file. This a temporary holding file through which validated transactions flow to their respective applications.

Five major components:

Error file. Error records detected during validation are store in the file, corrected, and then resubmitted to GVM. Error reports. Standardized error reports are distributed to users to facilitate error correction. Transaction log a permanent record of all validated transactions.

PROCESSING CONTROLS

Categories:
Run-to-run controls

Operator intervention controls

Audit trail controls

Run-to-Run Controls
Use batch figures to monitor the batch as it moves from one programmed procedure to another. Ensure that each run in the system processes the batch correctly and completely. Batch control figures may be contained in either a separate control record created at the data input stage or an internal label.

Uses of Run-to-Run Controls

Recalculate control totals

Transaction codes
Sequence checks

Run-to-Run Controls

Operator Intervention Controls

Systems sometimes require operator intervention to initiate certain actions such as entering control totals for a batch of records, providing parameter values for logical operations, and activating a program from a different point when reentering semi-processed error records. Limit operator intervention, thus less prone to processing errors.

Audit Trail Controls

The preservation of an audit trail is an important objective of process control. Techniques
Transaction Logs Log of Automatic Transactions Listing of Automatic Transactions Unique Transaction Identifiers Error Listing

Transaction Logs
Serves as a journal Reasons for creating a transaction log
For permanent record of transactions Not all of the records in the validated transaction file may be successfully processed.

The system should produce a hard copy transaction listing of all successful transactions.

Transaction Log to Preserve the Audit Trail

Log of Automatic Transactions

All internally generated transactions must be placed in a transaction log. E.g. reorder point

Listing of Automatic Transactions

The responsible end user should receive a detailed listing of all internally generated transactions.

Unique Transaction Identifiers

Each transaction processed by the system must be uniquely identified with a transaction number.

Error Listing
A listing of all error records should go to the appropriate user to support error correction and resubmission.