Orbit Package Generators are the easiest and fastest way to produce the PL/SQL code for your application. Specify your settings using the Package Generator Wizard GUI interface and by the click of a button generate all your application's PL/SQL packages for transaction processing. It dynamically reads the Oracle data dictionary to generate PL/SQL packages for queries, inserts, updates, and deletes customized for your application tables. It greatly improves your staff's productivity by reducing the time programmers spend coding and debugging. It also helps to enforce coding standards and uniformity. Therefore, your IT staff can concentrate in business rules to satisfy your business needs.

 The Package Generator Wizard lets you choose which packages to generate to handle your application's transaction processing. The wizard can generate four types of packages: Public, Table API, Web API packages and User Exit Package Stubs.

 Public packages are utility read only functions for the table where you can retrieve all the common values based on the primary key ID. They also contain functions for retrieving a unique key code based on an ID and vice-versa. A PRAGMA is created for each of the functions to allow those functions to be used in SQL statements.

 Table API packages contain data types and procedures for inserting, updating, deleting, locking, and selecting to manipulate data for a specific table. They also contain procedures for denormalizing foreign key columns based on foreign key ID's. The Table API package handles the record contention for a table using optimistic record level locking.

 The Web API packages accept either single or multiple record requests from a web page and call the Table API packages to do inserts, updates, or deletes. The Web API package is the transaction controller and handles security authentication, transaction management, error display, and page redirection. Web API packages can be connected together to create Master-Detail packages. There is a separate Master-Detail package generator designed specifically for this. This enables a developer to support any presentation display requirement using 100% generated packages.

 User Exit Package Stubs support implementation of business rules and customizations in your application. The user exit procedures may be customized to support virtually any business need. User Exit packages are called from the Table API and Web API packages and handle pre and post events, such as pre-insert, post-insert, pre-update, post-update, etc. This functionality enables the Orbit presentation layer to concentrate purely on presentation, and data requirements are handled purely in the backend database in these user exit procedures. User Exit packages also concentrate all custom code to a central location for each table, allowing all of the "grunt-work" code to be 100% generated and reduce clutter in the user exit code. End result: very reusable, database-centric, and clean business rules.

 Master-Detail Packages have never been easier to generate. The wizard web-based interface collects all the necessary criteria and settings needed to generate the PL/SQL code for master-detail packages allowing you to specify up to 25 detail tables. All business rules created in the User Exit packages are still supported from the master-detail interface.