Page 805
NOTE |
You can enter any language options you want for the module options; however, the module generator only generates Oracle Forms, Oracle Reports , and PL/SQL. Any other languages you specify are for documentation purposes only. |
NOTE |
If you have already assigned business units to the business functions, the Application Design Wizard will generate one module for each business unit by placing the numbering convention 1, 2, 3 at the end of each occurrence. The wizard assumes that the different business units may use the function differently. |
Merge granularity refers to the level of information coming from the functions. The transfer can be at the attribute level or only the entity level.
Once you click the Generate button, the system generates the modules from the candidate functions. You are prompted when the generation is complete. Next, you can click the Show Results button to see a Notepad file showing what functions were generated into modules.
The module names take on the following format: the prefix (if any was given) 0010 (incrementing by tens from the initial elementary function through the last function). You can edit the name in RON. I like to rename them back to their business function names .
TIP |
To generate module names in system blocks, choose the parent at the top of each system (payroll, accounting, and so on) and give it a unique prefix. |
Functions that are elementary generate as screen, report, or manual operation modules (if there is no entity usage). Functions that are not elementary generate as menu modules.
To regenerate a module, you must first delete it.
Use the Module Structure Diagrammer to set up a hierarchy of modules that are generated into a menu.
Page 806
Start the Module Structure Diagrammer by clicking its icon under the Systems Design Layer or the Designer/2000 tool, shown in Figure 32.14.
Figure 32.14.
The Module Structure
Diagrammer.
You can enter any summary information you want to display on the top of the diagram. To edit the summary information, choose File Summary Information.
You can either use existing modules in your diagram or create new modules. If you forgot a module or realize when you are creating your Module Structure diagram that you should include a new module, you can add one. Otherwise, you are better off creating your module in the Module Data Diagrammer. For more information on using the Module Data Diagrammer, see Chapter 33, "Generating Applications."
Sometimes, a module is similar to an existing module. Rather than creating a new module, you can copy an old one and give the copy a new name. To copy a module, click the Copy Module icon, which is the fifth icon from the right on the bottom bar. Select the module to copy and then drag the cursor to the spot for the copied module. You can only copy modules of the same type. You are prompted to give the name and description information.
Page 807
To include an existing module on the diagram, choose Edit Include Network. A list of modules appears. You can pare down the list by selecting a type or by entering a string contained in the module's short name. Once you choose an item, it is added to the diagram.
You can also add a new module to the diagram. Decide what kind of item you want to put on the diagram and select its icon: Menu, Form, Report, PL/SQL, or Utility. Once you place the cursor on the diagram, you are prompted for a short name, a description, the module type, and the language the module will be generated in.
If you want to edit information about any of the modules, double-click within the confines of the diagram. You then have a set of tabs for defining module information. The first tab, Module, defines general module information. (See Figure 32.15.)
Figure 32.15.
The Module tab.
The Parameters tab lists the parameters needed to run this module, their datatypes, and whether the parameters are input, output, or both.
The Access tab lists the users or groups that can access the menu. Groups are set up in business units to determine what roles can run certain functions. When the functions create modules, these groups get passed along to the modules. You can change or add these groups here. There are also preferences that can be set to provide menu security including gray areas where access is not allowed, or to omit them entirely.
Certain tabs are only available to client modules ”or screens, reports, and menus . (See Figure 32.16.) The Client Details tab contains information specific to generating a client tool. These include the path information, method of calling, title information, and so on.
Page 808
Figure 32.16.
The Client Details tab.
If you are generating a utility or PL/SQL, you have a Server Details tab. The server details list items specific for generating a function or procedure ”type, name, database, return type, and so on.
The Program Data tab lists any defined variables that the SQL uses, such as character fields.
The Data Structure tab lists any cursors or virtual tables that the SQL creates and uses. You can copy a structure from a table structure.
Once you have added a number of modules to your diagram, you can start to place them under a menu level. To do so, click the Make Slave icon. Select the module to be at the slave level. Drag the cursor to the parent module. The slave is placed under the parent.
TIP |
If you want to create more than one slave without selecting the button each time, hold down the Shift key when you click the Make Slave button. When you are ready to move on to another activity, click another button on the icon bar. |
TIP |
Use the expand and shrink options when moving objects around the screen. |
To save the diagram, click the Save icon. You can name your diagram anything you want; it probably makes sense to name it something related to the top menu level.