.NET UI Program Types
On the menu, a distinct icon indicates the type of program:
• Maintenance programs
• Transactions and utilities
• Reports and inquiries
• Browses and browse collections
• Menu collections
• Process maps
Each type of program maintains a specific kind of data within the database.
The next slides illustrate the types of programs that you will encounter as you use the product during this course.
Maintenance programs create and maintain basic codes such as customers, inventory items, GL accounts, currencies, and other data. They are also used to record data that initializes business activity in a module such as sales orders and purchase orders. Most maintenance programs update static data, which is changed infrequently.
Entering data in a maintenance program creates a record in one or more tables controlled by the maintenance program. For example, item records are stored in the Item Master table controlled by Item Master Maintenance.
With non-component maintenance programs, all changes to the record are made in the same maintenance program. In component-based maintenance programs, changes are made in separate Create, Modify, or Delete functions.
Inquiry and Report Programs
Inquiries and reports retrieve and display database records.
• Inquiries are primarily used to answer specific questions and are typically viewed online, although they can be printed
• Reports usually provide more detail and are printed for a range of data records. You select data by entering a specific range of criteria, such as item number or date. Reports are often sent to a printer or file. Other output options such as e-mail are available.
Component-based reports have multiple output options, including viewer, printer, and export to PDF, XLS, and DOC standards. The report output is easy to customize, and you can create an extensive set of reports with unlimited report variants for many output types.
You can run a report immediately, or choose to schedule it to run later. In this case, a pop-up window opens to let you enter details for running the report at a later date.
Transactions express the core business activities of a company. They control and record activities related to business documents such as sales orders and invoices. Example of transaction are shipping a sales order or receipt of a shipment for a purchase order. Enterprise Financials transaction programs include Customer and Supplier Invoice Create and Journal Entry.
Most data in the database is transaction data. Every day, sales orders come in, purchase orders go out, and work orders make demands on and create material for inventory. These events result in transactions, which are stored in transaction tables. In contrast to control programs, transaction tables are constantly updated by users of the system.
When you implement a module, you enter data that the system uses later to control the interactions with users and with the database. This data is stored in control tables.
Control tables enable you to adapt QAD Enterprise Applications to your environment. The data and settings in these tables determine how certain programs are displayed, the numbers assigned to transactions, the GL accounts for particular transactions, and so on. When you can manage a typical manufacturing function in more than one way, control settings enable you to establish a preference.
This slide shows two control programs with settings that affect work order processing. To support the enhanced segregation of duties features of QAD Enterprise Edition, financial control settings are updated separately from operational controls. For example, Work Order Control (16.24) under the Work Order menu in Manufacturing has only the operational control settings for work orders. All of the financial control settings for work orders are in Work Order Accounting Control (36.9.11) under the Operational Acct Controls menu in System Administration.
Note: This is unlike QAD Standard Edition, where all control settings for a functional area are updated in one program.