31 Creating Smart Fields

This chapter contains the following topics:

31.1 Understanding Smart Fields

Smart fields are data dictionary items with business functions attached. They are reusable objects that are created in the data dictionary and defined as glossary group K. The attached business function performs a specific task, such as a calculation, for the smart field.

As with all business functions, smart field business functions require a data structure to pass values. Smart field data structures include a named mapping that maps the source of each parameter included in the data structure. Named mappings are used in smart fields only.

Smart fields simplify the use of business functions because the parameters that need to be passed are held by the system. Instead of needing to know which business function to use and what parameters to pass, the user selects a smart field that inherently includes this information. Smart fields can be used for deriving column headings or populating values in a report section using Oracle's JD Edwards EnterpriseOne Report Design Aid (RDA).

For example, you can create a smart field to calculate sales by period. You can create the business function to add period 1, period 2, and period 3 to populate sales for the first quarter in a report. This calculation is performed by the business function for each row of data that is fetched by the report. Every time you use this smart field, it performs this calculation.

Without the quarterly smart field, you must write an event rule to accumulate the three periods to populate the quarterly sales column. To display a total for each quarter, you must write four event rules. Additionally, to display quarterly sales totals in multiple reports, you must duplicate these event rules in each report template.

Smart fields can be used in:

  • Columnar sections

  • Group sections

  • Tabular sections

When you select a smart field for a detail section, you must define a column heading unless you use a smart field to populate the column heading. Typically, you define data selection for each smart field column. The exception is when the section data selection is the same as the data selection for each smart field column. In this instance, you can define data selection for the section. However, if you define data selection for each smart field column, you should still define data selection for the section for processing efficiency.

Before smart fields can be used in a report, you must add them to a Smart Field template and then add the Smart Field template to a Report Director template. You can add smart fields to an existing Smart Field template, if appropriate, or create a new Smart Field template. Smart Field templates organize smart fields that use the same fields for data selection. For example, Oracle's JD Edwards EnterpriseOne existing Smart Field templates are organized by Financial Reports, Fixed Assets, and 52-Period Accounting.

When you create a new Smart Field template, you must create a new Report Director template. In the Report Director template, you can define report processing options, business views, additional properties, and the Drill Down feature. Information that is included in the Report Director template guides the report developer through the process of creating a report template using the associated smart fields. The Smart Field template and Report Director template enable you to organize and present the smart fields in RDA.

31.2 Creating Custom Smart Fields

This section provides an overview of creating custom smart field components and discusses how to:

  • Create data dictionary items.

  • Create data structures.

  • Define named mappings.

  • Perform calculations using named event rules.

  • Create data dictionary smart field items.

31.2.1 Understanding Smart Field Components

Smart fields are complex data items because they include business function logic. However, once the smart field is created, you do not have to recreate frequently used logic.

The basic components of smart fields are:

  • Data dictionary items.

    A standard data item that is defined as glossary group D.

  • Data structures.

  • Named mappings.

  • Business functions.

    Can use a C business function or a named event rule business function.

  • Smart field data items.

    A data item that is defined as glossary group K.

31.2.1.1 Data Dictionary Items

The first component of most smart fields is a data dictionary item that serves as a user prompt for the report developer. The prompt indicates how the logic should be processed if more than one option is possible. For example, a quarterly sales smart field requires input from the report developer to indicate which quarter to calculate. At least four options are possible, one for each quarter, and each option results in a different outcome. However, not all smart fields require a user prompt. A smart field used to concatenate two fields does not require input as there are no decision points.

The Report Director (Director) displays a Smart Field Parameters form to prompt the report developer. The description of the data item prompt (for example, Quarter to Display) appears on this form. The glossary that you enter when you create the data item also appears on this form. The glossary explains the purpose of the prompt and assists the report developer in determining the appropriate value to enter in the prompt.

An example glossary:

  • Enter 1 to print first quarter sales.

  • Enter 2 to print second quarter sales.

  • Enter 3 to print third quarter sales.

  • Enter 4 to print fourth quarter sales.

Data dictionary items include a name, an alias, and a description. The data item name can be a maximum of 40 characters and cannot include spaces. The alias is a unique alphanumeric identifier. The software allows the alias to be a maximum of 10 characters. However, not all databases support 10 characters, so it is recommended that you limit the alias to eight characters. The description can be a maximum of 40 characters, including spaces. The description is often the same as the name, with spaces.

See JD Edwards EnterpriseOne Tools Development Tools: Data Dictionary Guide.

31.2.1.2 Data Structures

The second component that is required for a smart field is a data structure. A data structure lists the parameters that pass values between a report and the database tables. You must include all of the data items that are required to complete the function of the smart field in the data structure. For example, a quarterly amount smart field requires 12 periods for calculating each month. Another field is required for the return value, which is the result of the smart field calculation for each quarter.

All data items that are added to the data structure must reside in the same business view. If you find that you need to add data items that are not included in a single business view, you must create a custom business view that includes all of the required data items. Adding data items that reside in different business views results in a nonfunctional smart field.

You can also define the direction of the flow of data in a smart field data structure. This definition eliminates the need for the report developer to define the flow in RDA. The data flow definition is another component that simplifies the use of business functions for the report developer.

See "Creating Data Structures," "Creating Business Function Data Structures" in the JD Edwards EnterpriseOne Tools Development Tools: Data Structure Design Guide.

31.2.1.3 Named Mappings

Named mappings are a component of the data structure that is used only for smart fields. Named mappings define each of the data items that is included in the data structure. They can also hold default values for the business function so that the values do not need to be manually defined in RDA.

Named mappings are also used to map the source for each parameter (or data item) of the data structure. For example, source values are determined for the prompts, tables, and return values. This table details the sources from which data structure data items originate:

Source Description
Literal Assigns a specific value to the data item. For example, if the calculation needed to use a tax rate, you would enter the tax rate in the value field.
Prompt Indicates that the data item is the user prompt. For example, the Quarter to Display data item is the prompt. In RDA, the report developer enters the quarter to calculate, and the result appears in the smart field column of the report.
Table Indicates the data items that originate from a table. Browse to locate the table name, and then associate the data item in the data structure with the corresponding data item in the table.
Data Dictionary Item Passes values from a processing option into the data structure. Values in smart fields can be identified with a business function without requiring input. For example, the desired fiscal year or period might already be specified in a processing option that can be passed into the data structure. If this is the case, the data item must be defined as both a data dictionary item and a processing option in the named mapping.
System Value Associates the system value as the origin of the data item and browses for the appropriate system value. System values, such as system date, are used throughout the system. System values are fetched from the Table of Variables (F98VAR) table.

Named mappings begin with the letter M and use the same name as the data structure. You can add multiple named mappings to a single data structure. If you have multiple named mappings, append a sequential letter of the alphabet to the named mapping name. For example, the first named mapping for data structure D550101 would be named M550101A.

31.2.1.4 Business Functions

Business functions define the logic for the smart field. You can use either C business functions or named event rule business functions. C business functions are written in C language, while named event rule business functions are written in scripting language using the JD Edwards EnterpriseOne toolset. Named event rule business functions are also referred to as named event rules (NERs).

The advantage of using business functions is that they are reusable. The code is written once and can be used in multiple events and reports. For example, without the business function for Quarterly Amount, you would write four event rules, adding together the appropriate periods for each of the four quarters. In contrast, if you use an NER you can write the criteria once and reuse it for each of the four columns that displays a quarterly amount. You can also use this same NER in other reports that require quarterly sale figures.

The event rules scripting language used for creating NERs is platform independent. NERs are stored in a database as a JD Edwards EnterpriseOne object. When you build NERs, the system generates C code and creates .c and .h files.

A NER is a business function object. When you create a business function, you have the choice of which source language to use. The source language options are C and NER. Your selection determines which tool the system presents.

As with any business function, you need to associate a data structure with an NER.

You create the logic for NERs using the Named Event Rules Design form. This form is similar to the Event Rules Design form used in RDA. In the Named Event Rules Design form, you can create event rule logic for each valid user prompt value. It is good practice to include a default statement. For example, the logic for quarterly amount might state that if any value other than 1, 2, 3, or 4 is entered into the user prompt, the first quarter is calculated by default.

See "Using Business Functions" in the JD Edwards EnterpriseOne Tools Development Tools: APIs and Business Functions Guide.

31.2.1.5 Smart Field Data Items

The last component that is required for a smart field is a data dictionary item that is defined as a smart field. Smart field data dictionary items differ from regular data dictionary items in two ways:

  • Glossary group.

    Regular data dictionary items are classified as glossary group D; smart field data items are classified as glossary group K. The K classification enables the Smart Field Criteria form.

  • Smart Field Criteria form.

    The Smart Field Criteria form defines the business functions and named mappings that are associated with the smart field and the event on which the logic is attached.

    If you create smart fields for use in tabular sections, you might select the Column Inclusion event. If you create smart fields for use in columnar or group sections, you might select the Do Variable event.

See Also:

  • JD Edwards EnterpriseOne Tools Development Tools: Data Access Tools Guide.

  • JD Edwards EnterpriseOne Tools Development Tools: Data Structure Design Guide.

31.2.2 Creating Data Dictionary Items

From the Tools menu in JD Edwards Solution Explorer, select Object Management Workbench (OMW).

  1. Select the project in which you want to add a new data dictionary item and click Add.

  2. On the Add EnterpriseOne Object to the Project form, select Data Item and click OK.

  3. On the Data Dictionary Item Type form, click No.

    This is a regular data dictionary item, not a glossary data item.

  4. On the Data Item Specifications form, enter the name of the data item in the Data Item field.

  5. In the Alias field, enter a unique alphanumeric identifier.

  6. In the Glossary Group field, enter D to indicate a primary data element.

  7. In the Description field, enter a brief description of the data item.

  8. In the Product Code field, enter a product code.

    Codes in the 55–59 range are reserved for clients.

  9. In the Product Code Reporting field, enter a product code that represents the system associated with this data item.

  10. In the Data Type field, use the visual assist to select a value that indicates the type of data to be entered (for example, character, string, numeric).

  11. In the Size field, enter the field size of the data item.

    This field is enabled based on the data type you selected.

  12. In the File Decimals field, enter the number of stored positions to the right of the decimal place.

    This field is enabled only if the data type is defined as numeric.

  13. In the Class field, use the visual assist to select a class that defines the attributes and characteristics of the data item (for example, CURRENCY).

    This field is only informational; it is not required.

  14. In the Display Decimals field, enter the number of decimals that you want to appear.

    This field is enabled only if the data type is defined as numeric.

  15. In the Control Type field, enter the type of control that is associated with the data item (for example, check box, push button, generic edit, and so on).

    The generic edit option is typically used when creating data items specifically for batch applications.

  16. Leave the Item Occurrences field cleared.

    The value entered in this field causes a number of identical data items to be created based on the template defined by the active data item properties. For example, if data item RDATEST is added with Item Occurrences set to 2, the system creates two copies of the data item, RDATEST1 and RDATEST2.

  17. In the Row Description field, enter the data item description as it should appear in group sections.

  18. In the Column Title fields, enter the data item description as it should appear in columnar sections.

    Split lengthy descriptions into two lines. Enter short descriptions in the top line.

  19. Select the Item Glossary tab, enter a description of all of the valid values for this prompt, and click OK.

    The item glossary appears on the Smart Field Parameters form in the Director.

    For example, for a quarterly data item prompt you might enter:

    Enter 1 to display totals for the first quarter.

    Enter 2 to display totals for the second quarter.

    Enter 3 to display totals for the third quarter.

    Enter 4 to display totals for the fourth quarter.

31.2.3 Creating Data Structures

Access the appropriate project in OMW.

  1. Add a data structure to the same project in which you added the data item smart field component.

  2. On the Add Object form, create a new regular data structure, name it according to the recommended naming conventions, and click OK.

    See "Understanding JD Edwards EnterpriseOne Naming Conventions" in the JD Edwards EnterpriseOne Tools Development Guidelines for Application Design Guide.

  3. On the Data Structure Design form, select the Design Tools tab and click Data Structure Design.

  4. On the Data Structure form, under Dictionary Items, enter the alias of the data item prompt on the QBE line.

  5. Double-click the data item prompt to include it in Structure Members.

  6. Double-click in the Required field of the detail area to define the data item prompt as Required.

    This field displays a check mark for the prompt data item.

  7. Under Dictionary Items, search for all of the required data items using the QBE line.

  8. Double-click the required data items individually to include them in Structure Members.

  9. Under Dictionary Items, search for a data item to serve as a return value using the QBE line.

    Use a data item that is formatted the same as you want the smart field to be formatted.

  10. Double-click the return value data item to include it in Structure Members.

    You can rename the return value data item in the Structure Member Name field.

  11. In the Input/Output field for each data item, set up the arrows to reflect the flow of the data and click OK.

    All arrows for prompts and data items should point to the right because these fields fetch data from the database. The arrow for the return value should point to the left because the data is returned to this field in the report section.

31.2.4 Defining Named Mappings

In OMW, select the smart field data structure, click the Design button, and select the Design Tools tab.

  1. Click Named Mapping.

  2. On the Named Mapping form, click Add.

    The detail area includes all data items included in the data structure.

  3. On the Add Argument List form, enter the name of the named mapping using the recommended naming conventions.

    See "Understanding JD Edwards EnterpriseOne Naming Conventions" in the JD Edwards EnterpriseOne Tools Development Guidelines for Application Design Guide.

  4. On the Named Mapping form, click the prompt data item and select the Prompt option under Origin Types.

    The prompt is already set as a required data item from the data structure definition.

  5. Click one of the data items to be fetched from a table and select the Table option under Origin Types.

  6. Click the Browse button to access the Select a Table form.

  7. Use the QBE (query by example) line to locate the table where the data item resides, and click Next.

  8. On the Select a Column form, select the field that matches the data structure data item and click Finish.

  9. On the Named Mapping form, define each of the data items that is fetched from a table using the Required option at the bottom of the form.

  10. Define the return value data item using the Return Value option at the bottom of the form.

    Note:

    When you select the Return Value option, the system automatically selects the Required option.

31.2.5 Performing Calculations Using Named Event Rules

Access the appropriate project in OMW.

  1. Add a business function to the same project in which you added the other smart field components.

  2. On the Add Object form, create a new business function, naming it according to the recommended naming conventions.

  3. Under Source Language, select NER and then click OK.

  4. On the Design Tools tab of the Business Function Design form, click Start Business Function Design Aid.

  5. On the Business Function Design form, click the visual assist in the Parent DLL field and select the DLL that your company uses to create custom business functions.

  6. In the detail area, enter a unique name in the Function Name field.

    This name cannot include any spaces and should be descriptive of the business function purpose.

  7. Enter a description in the Description field.

    This description can be the same as the name, however, you can use spaces in the description.

  8. Tab through the remaining fields.

    The system populates the F3 Code field with a 3 (Minor Business Rule).

  9. Modify the F3 Code if appropriate.

  10. Click the row header to highlight the row of data that you just entered, and select Parameters from the Row menu.

  11. Use the QBE line to locate the associated data structure, click the data structure and then click Select.

  12. On the Business Function Design form, verify that the name of the appropriate data structure appears in the Template Name field in the detail area.

  13. From the Form menu, select Edit.

  14. On the Named Event Rules Design form, create the appropriate logic using If/While statements, assignments, business functions, and system functions.

    For example, for the quarterly amount smart field that calculates sales for each quarter, this logic is appropriate:

    If <user prompt> is equal to 2
    <return value> = Sales for Period 4 + Sales for Period 5 + Sales for Period 6
    Else
    If <user prompt> is equal to 3
    <return value> = Sales for Period 7 + Sales for Period 8 + Sales for Period 9
    Else
    If <user prompt> is equal to 4
    <return value> = Sales for Period 10 + Sales for Period 11 + Sales for Period 12
    Else
    <return value> = Sales for Period 1 + Sales for Period 2 + Sales for Period 3
    End If
    End If
    End If
    

    Note:

    The first quarter sales is the default result. Therefore, if the user enters a value other than 2, 3, or 4, the business function calculates sales for the first quarter.
  15. When the logic is complete, save the event rules and click OK.

  16. On the Design Tools tab, click Build Business Function.

31.2.6 Creating Data Dictionary Smart Field Items

Access the appropriate project in OMW.

  1. Add a data item to the same project in which you added the other smart field components.

  2. On the Data Dictionary Item Type form, click No.

    This in not a glossary data item so you want to answer no to the message form.

  3. On the Data Item Specifications form, enter the name of the data item in the Data Item field.

  4. In the Alias field, enter a unique alphanumeric identifier.

  5. In the Glossary Group field, enter K to indicate that the data item is a smart field.

  6. In the Description field, enter a brief description of the smart field data item.

  7. In the Product Code field, enter a product code in the 55–59 range, codes reserved for clients.

  8. In the Product Code Reporting field, enter a product code that represents the system associated with this smart field data item.

  9. In the Data Type field, use the visual assist to select a value that indicates the type of data to be entered (for example, character, string, numeric).

  10. In the Size field, enter the field size of the smart field data item.

  11. In the File Decimals field, enter the number of stored positions to the right of the decimal place.

  12. In the Class field, use the visual assist to select a class that defines the attributes and characteristics of the smart field data item (for example, CURRENCY).

  13. In the Display Decimals field, enter the number of decimals to appear.

  14. In the Control Type field, enter the type of control that is associated with the smart field data item (for example, check box, push button, generic edit, and so on).

    The generic edit option is typically used when creating data items specifically for batch applications.

  15. Leave the Item Occurrences field cleared.

  16. In the Row Description field, enter the smart field data item description as it should appear in group sections.

  17. In the Column Title fields, enter the smart field data item description as it should appear in columnar sections.

  18. Select the Item Glossary tab and enter information that describes all of the valid results.

    For example, for a quarterly smart field, you might enter:

    • 1 returns a total value for January, February, and March.

    • 2 returns a total value for April, May, and June.

    • 3 returns a total value for July, August, and September.

    • 4 returns a total value for October, November, and December.

  19. From the Form menu, select Smart Field to launch the Smart Field Criteria form.

  20. In the Business Function field, use the visual assist to locate the appropriate business function, click the business function, and then click Select.

  21. In the Event Name field, use the visual assist to select the event from which the smart field business function will be called.

  22. In the Named Mapping field, enter the name of the named mapping that you defined for the associated data structure and click OK.

See Also:

  • JD Edwards EnterpriseOne Tools Development Tools: Data Dictionary Guide.

31.3 Creating Custom Smart Field Templates and Reports

This section provides an overview of creating custom smart field template and discusses how to:

  • Create Smart Field templates.

  • Create Report Director templates.

  • Design reports using custom smart fields.

31.3.1 Understanding Custom Smart Field Template Creation

After you create custom smart fields, you must add them to a Smart Field template and define the appropriate data selection. You must then add the smart field template to a Report Director template. The Report Director template makes the smart fields available for use in report templates.

31.3.1.1 Smart Field Templates

JD Edwards EnterpriseOne includes predefined Smart Field templates. Smart Field templates group smart fields that use the same data selection criteria so that you can include them collectively in a Report Director template. For example, the S09001 - Financial Reporting smart field template contains all of the smart fields for financial reporting. Through the Oracle's JD Edwards EnterpriseOne Smart Field Templates (P91420) application, you can add new smart field templates or modify existing smart field templates to meet your reporting needs. You can access the JD Edwards EnterpriseOne Smart Field Template application from both the Microsoft Windows client and the web client.

You must add smart fields to a smart field template before they can be used in reports. Then you must attach the smart field template to a Report Director template. When you use the Report Director template to create a report, the smart fields in the attached smart field template appear in the Available Smart Fields list on the Select Columns form of the Director. From this form, you can select any of the available smart fields to include in the report.

When you select a smart field to include in the section layout, you are typically prompted for data selection values. Data selection fields are defined within the smart field template. These fields appear on the Smart Field Data Selection form of the Director.

Custom smart field template names should begin with SFT. The next two characters should be one of the product codes that is reserved for clients (55–59), and the next characters should reflect the system that uses the smart field template, as recommended for JD Edwards EnterpriseOne objects.

When you define a smart field template, you can select multiple smart fields to include in the template as long as they all use the same data selection. When defining data selection, you must select from fields that reside in the business view that is associated with the smart fields. Only five data items can be included in the smart field data selection criteria.

You can define a data selection field as requiring a range of values, but the field must be counted as two items. A range of values takes up two lines on the Smart Field Data Selection form in RDA. For example, if you include business unit as a data selection item, you might want the report developer to be able to include a range of values. This option presents two fields on the Smart Field Data Selection form in the Director, one for the beginning business unit value and one for the ending business unit value.

31.3.1.2 Report Director Templates

Report Director templates define a set of parameters to guide the report developer through the creation of a batch application. Report Director templates are typically created to use smart fields. However, you can use Report Director templates to define parameters for the development of batch applications without the use of smart fields.

When you create a Report Director template, you define the appropriate business view to attach to the report section. The business view that you select must include all of the data items included in the smart field data structure. It is this business view that is used when the report developer selects the option I'll use the predefined business view from the Director.

Custom Report Director templates should begin with DT. The next two characters should be one of the product codes that is reserved for clients (55–59), and the next characters should reflect the system that uses the Report Director template.

The Report Director template description appears in the Application Report drop-down list box on the Director Welcome form and on the Business View Selection Options form when you create the report in RDA.

31.3.1.3 Report Templates

As the final step in the smart field creation process, you should test the smart field. It is helpful to review the Director and see how all of the information you defined is presented to the report developer. This review helps you understand the origin of each option presented in the Director and how your selections in defining the objects affect what the report developer sees.

31.3.1.4 Smart Field Logic

You can review the event rules that are created by the smart fields to understand how the smart field components are implemented in the report. In the RDA workspace, click the variable portion of a smart field column. From the Edit menu, select Event Rules. Select the event that you defined on the Smart Field Criteria form when you created the smart field data item.

The description of the business function that you created for the smart field appears on the event. Double-click the business function to review the data structure parameters. The business function information appears in the upper-left corner of the Business Functions form and includes the business function name, description, and the name of the attached data structure. The data structure displays the parameters as you defined them in the named mapping.

Notice that the data structure includes the directional arrows you defined in the data structure. The directional arrows for all data items except the return value data item point to the right. This is because each of these fields is fetched from a source, such as the database or a user prompt. The system then processes the logic using these fields and returns the result to the return value field to appear on the report. The directional arrow in this field points to the left. Without the use of this smart field, the report developer would have to know which business function to use and how to pass each of these values.

For example, if you select the first quarter variable that was created using the quarterly sales smart field, you can see in the data structure the 1 that you entered on the Smart Field Parameters form when you created the report.

See "Understanding JD Edwards EnterpriseOne Naming Conventions" in the JD Edwards EnterpriseOne Tools Development Guidelines for Application Design Guide.

31.3.2 Forms Used to Create Smart Field Templates and Reports

Form Name FormID Navigation Usage
Work With Smart Field Templates

W91420A EnterpriseOne Life Cycle Tools, Report Management (GH9111), Advanced Report Setup, Smart Field Templates Add, modify, and delete smart field templates.
Smart Field Template Revisions W91420G Click Add on the Work With Smart Field Templates form. Enter smart field template name, description, and smart field data item.
Smart Field Template Criteria Revisions W91420B Click OK on the Smart Field Template Revisions form. Enter fields to be used for data selection.
Work With Report Director Templates W91400A EnterpriseOne Life Cycle Tools, Report Management (GH9111), Advanced Report Setup, Report Director Templates Add, modify, and delete Report Director templates.
Report Director Templates Revisions W91400B Click Add on the Work With Report Director Templates form. Enter the Report Director template name, description, section type, default business view, processing options, smart field template name (if appropriate), default data sequencing and level breaks, properties, and drill down information.

31.3.3 Creating Smart Field Templates

The smart field template includes two parts, the Smart Field Template Revisions form and the Smart Field Template Criteria Revisions form.

31.3.3.1 Smart Field Template Revisions

Access the Smart Field Template Revisions form.

Figure 31-1 Smart Field Template Revisions form

Description of Figure 31-1 follows
Description of "Figure 31-1 Smart Field Template Revisions form"

Smart Field Template

Enter the name of the Smart Field template.

Description

Enter a meaningful description of the type of smart fields that are included in the Smart Field template.

Data Item and Description

Enter the data item alias of all smart fields to be included in the Smart Field template.

Description

Describes the data item based on the alias entered. The system populates this field.

31.3.3.2 Smart Field Template Criteria Revisions

Access the Smart Field Template Criteria Revisions form.

Figure 31-2 Smart Field Template Criteria Revisions form

Description of Figure 31-2 follows
Description of "Figure 31-2 Smart Field Template Criteria Revisions form"

Smart Field Template

Displays the name of the Smart Field template as entered on the Smart Field Template Revisions form.

Description

Displays the description of the type of smart fields that are included in the Smart Field template as entered on the Smart Field Template Revisions form.

Data Item

Enter the alias of the data items to be used as data selection in the report sections created using the Smart Field template.

Description

Describes the data items to be used as data selection in the report sections created using the Smart Field template. The system populates the description field based on the alias that you enter.

Display Seq

Indicates the sequence in which the data selection fields appear on the Smart Field Data Selection form of the Director. The system populates this field when you tab out of it.

Range Values

Indicates whether a field requires a range of values or a single value. The system populates this field with a default value of 0, but you can override this value. For example, if Units-Order Transaction Quantity requires a range of values, enter 1 in the field.

31.3.4 Creating Report Director Templates

Access the Report Director Templates Revisions form.

Figure 31-3 Report Director Templates Revisions form

Description of Figure 31-3 follows
Description of "Figure 31-3 Report Director Templates Revisions form"

Report Template/Description

Enter the name of the Report Director template and a meaningful description.

The system displays the Report Template/Description information from all three tabs.

Section Type

Select a user-defined code (UDC) that represents the type of report section that the system creates when this Report Director template is selected.

Business View

Enter the business view to be used by the report. You can override this business view in the Director.

Processing Options

This field is optional. Enter the processing option template to be used by the report. You can override this business view in the Director.

Smart Field Template

Enter the smart field template to be used by the report. The smart field template is dependent on the business view defined.

Default Sequence and Level Breaks

The system displays the Default Sequence and Level Breaks information from all three tabs.

Data Item

Enter the alias of the data items to be used as data sequencing and level breaks in the report sections created using the Report Director template. The first two data items appear in Report Grouping, and the subsequent data items appear in Report Detail on the Data Sequencing Help form of the Director. You can override these fields in the Director.

Description

The description of the data items to be used as data sequencing and level breaks in the report sections created using the Report Director template. The system populates the description field based on the alias that you enter.

Display Seq

Indicates the sequence in which the data sequencing fields appear on the Data Sequencing Help form of the Director. The system populates this field when you tab out of it.

31.3.5 Designing Reports Using Custom Smart Fields

Access RDA.

  1. On the Director, under Application Reports, select the appropriate Report Director template from the pull-down menu and click Next.

    This information is derived from the description you entered when you created the Report Director template.

  2. On the Page Header Details form, accept the page header defaults and click Next.

  3. On the Business View Selection Options form, select the option I'll use the pre-defined business view and click Next.

    The predefined business view is the business view that you defined on the Building Blocks tab for the Report Director template. You can select one of the other two business view selection options to override this default.

  4. On the Select Columns form, move the appropriate smart field from the Available Smart Fields list to Columns in Report Section.

    The available smart fields are derived from the Smart Field template that you associated with the Report Director template. All smart fields in the attached Smart Field template are available to the report developer.

  5. On the Smart Field Name form, change the Variable Name to describe the smart field (for example, First Quarter).

    • Change the Report Column Headings fields to describe the field on the report.

      For example, to describe the first quarter data, enter First Quarter on line 1 and Sales on line 2.

      If you selected a Report Director template that includes a smart field that displays column headings, the Smart Column Heading option is available. Instead of changing the column heading names, select this option to enable the smart field to populate the column headings based on information that you enter in the subsequent forms.

      Subsequent forms are dependent on the selected Report Director template. For example, using the quarterly sales scenario you might see these forms:

    • Smart Field Parameters

      This form displays the user prompt data item that you created. The information that you entered in the item glossary appears in the center of the form. Enter an appropriate value in the Enter the Literal field based on the glossary information. If you created multiple user prompts, you are presented with additional forms for each prompt. For quarterly sales, enter the quarter that you want calculated and included on the report. For first quarter sales, enter 1 in this field.

    • Smart Field Data Selection

      This form displays the data items that you defined on the Smart Field Template Criteria Revisions form when adding the smart field to the smart field template. If you defined any of the data items as requiring a range of values, the data item displays a From and a To field.

      If you intend to define the same data selection for each smart field column, you can leave this form blank and just fill in the data selection for the report.

  6. When you have completed all smart field parameters, click Finish.

    Add additional smart field columns to the report. For example, for quarterly sales, you can select the smart field again and enter 2 on the Smart Field Parameter form to calculate and display sales for the second quarter.

  7. When you are finished adding smart field columns to the report, click Next.

  8. On the Data Sequencing Help form, click Next.

    The Data Sequencing Help form displays the Data Sequence and Level Break Fields that you defined in the Report Director template. The fields that appear under Report Grouping are defined as level break fields and are the first two fields you entered into the detail area in the Report Director template. You can remove these fields as level breaks by clearing the option.

    The fields that appear under Report Detail are the additional fields that you included in the Report Director template and are also used for data sequencing. Click each field that you want to include as a level break field so that they appear in the empty field directly above them.

    You can override the predefined data sequencing and level breaks by selecting the I'd like to set up the sequencing and level breaking myself option under Advanced. You can define data sequencing on the Section Data Sequencing form. The fields listed in the Available Columns section are fields from the attached business view. The subsequent Define Sort Properties form enables you to define level breaks.

  9. On the Help with Section Data Selection form, create either a balance sheet or an income statement and indicate whether you want to add to the data selection, and click Next.

    Note:

    This form only appears if you defined the associated Report Director template to display financial criteria.
  10. On the Data Selection form, define the appropriate data selection.

    This form appears if you defined the selected Report Director template to display generic criteria or if you selected the option Set up data selection manually on the Help with Section Data Selection form.

    You should define data selection on the Data Selection form to enhance system performance even if you defined data selection for each smart field.

  11. On the Additional Properties form, select the appropriate options and click Next.

    The options that appears on this form are defined on the Properties tab of the Report Director Template.

  12. On the Finish form, click Finish.

  13. Save and preview the report.