4.2.2 System Packages

This topic describes about the system packages.

Main package would be generated by the Tool and should not be modified by the developer.

There is small change in the structure of the package depending on the type of the call form (Maintenance or Transaction).

Unlike normal maintenance function ids, call form packages does not have any call to the business logic within itself (similar to transaction function id). If developer wishes to uses any functions within the main package , call has to be made from the release specific package.

Main package contains functions for :

• Converting Ts to PL/SQL Composite Type
• Calling fn_main.
• Mandatory checks (fn_check_mandatory).
• Default and validation(fn_default_and_validate)
• Querying(fn_query)
• Converting the Modified Composite Type again to TS

Except the functions for type conversions, others functions calls the respective hook functions in hook packages of the call forms. Thus no processing logic within the main package is used It is to be noted that each of these functions are called from the main package of the main function id (where this call form is used) during respective stages.

But the package contains many other system generated functions for operations like

• Mandatory checks(fn_sys_check_mandatory)
• Default and validation(fn_sys_default_and_validate)
• Uploading to DB(fn_sys_upload_db)
• Query operation (fn_sys_query) etc

These functions are not called anywhere in the package. These functions if required can be called by the developer from the release specific package. Otherwise developer can write his own logic for the same in the Hook Packages