EnterpriseOne B73.3.1 Development Standards … · B73.3.1 (6/99) 1–1 Application Design Standards Overview The Application Design Standards guide is updated monthly. To ensure

EnterpriseOne B73.3.1Development Standards Application Design PeopleBook

June 1999

J.D. Edwards World Source Company

One Technology Way

Denver, CO 80237

Portions of this document were reproduced from material prepared by J.D. Edwards.

Copyright J.D. Edwards World Source Company, 1997 - 1999

All Rights Reserved

SKU B7331CEADS

J.D. Edwards is a registered trademark of J.D. Edwards & Company. The names of all other products and services of J.D. Edwards used herein are trademarks or registered trademarks of J.D. Edwards World Source Company.

All other product names used are trademarks or registered trademarks of their respective owners.

The information in this guide is confidential and a proprietary trade secret of J.D. Edwards World Source Company. It may not be copied, distributed, or disclosed without prior written permission. This guide is subject to change without notice and does not represent a commitment on the part of J.D. Edwards & Company and/or its subsidiaries. The software described in this guide is furnished under a license agreement and may be used or copied only in accordance with the terms of the agreement. J.D. Edwards World Source Company uses automatic software disabling routines to monitor the license agreement. For more details about these routines, please refer to the technical product documentation.

B73.3.1 (6/99)

Table of Contents

Application Design Standards Overview 1–1. . . . . . . . . . . . . . . . . . . . . . .

Application Development Checklists 2–1. . . . . . . . . . . . . . . . . . . . . . . . . . Interactive Application Development Checklist 2–3. . . . . . . . . . . . . . . . . . . . . . .

All Forms Development Checklist 2–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standards That Are Set Up Automatically by the Tool Set 2–4. . . . . . . . Form Appearance 2–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Form Function 2–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Financials 2–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Human Resource/Payroll 2–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manufacturing and Distribution 2–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Localization 2–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Currency 2–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Find/Browse Development Checklist 2–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . Form Appearance 2–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Form Function 2–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Human Resource/Payroll 2–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manufacturing and Distribution 2–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Currency 2–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Selection Criteria Prior to B73.3 2–16. . . . . . . . . . . . . . . . . . . . Additional Selection Criteria for B73.3 2–17. . . . . . . . . . . . . . . . . . . . . . . Category Codes for B73.3 2–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fix/Inspect Development Checklist 2–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Form Appearance 2–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Form Function 2–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Currency 2–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Human Resource/Payroll 2–19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Header Detail and Headerless Detail Development Checklist 2–20. . . . . . . . . Form Appearance 2–21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Form Function 2–21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Currency 2–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Parent Child Form Development Checklist 2–23. . . . . . . . . . . . . . . . . . . . . . . . Form Appearance 2–23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Form Function 2–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Message Form Development Checklist 2–25. . . . . . . . . . . . . . . . . . . . . . . . . . . Form Appearance 2–25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Form Function 2–25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Search and Select Development Checklist 2–26. . . . . . . . . . . . . . . . . . . . . . . . Batch Application Development Checklist 2–29. . . . . . . . . . . . . . . . . . . . . . . . . . .

Standards That Are Set Up Automatically by the Tool Set 2–29. . . . . . . . . . . . Report Appearance 2–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing 2–31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reports to Output 2–31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Development Standards: Application Design

B73.3.1 (6/99)

Reports to File 2–32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Currency 2–32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Processing Option Tabs Checklist 2–33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Processing Option Form Tabs 2–33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Processing Option Fields 2–34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Partners in Development Considerations 3–1. . . . . . . . . . . . . . . . . . . . . . Partners in Development Administrator and System Codes 3–1. . . . . . . . . . .

OneWorld Naming Conventions 4–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding OneWorld Naming Conventions 4–3. . . . . . . . . . . . . . . . . . . . . . .

Naming Conventions for Objects 4–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Codes 4–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Data Dictionary Naming Conventions 4–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Item Alias 4–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Item Name 4–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Item Prefix 4–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Item Description 4–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Row Description 4–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Column Title 4–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Processing Option Data Item 4–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow Message Data Item 4–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error Message Data Item 4–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table I/O Data Item 4–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Object Naming Conventions for Interactive Applications 4–15. . . . . . . . . . . . . . . . Tables 4–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Indices 4–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Business Views 4–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Joined Views 4–19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applications 4–19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forms 4–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Form Interconnection Data Structures 4–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . Processing Options 4–21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Processing Option Data Structure 4–21. . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab Title 4–21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Comment 4–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Item 4–23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Event Rule Variables 4–23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Text Variables 4–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Business Function Event Rules (Named ER) 4–24. . . . . . . . . . . . . . . . . . . . . . Business Functions 4–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Business Function Data Structures 4–25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow Data Structures 4–25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Media Objects 4–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Object Naming Conventions for Batch Applications 4–27. . . . . . . . . . . . . . . . . . . Batch Applications 4–27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table Conversions 4–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Versions 4–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section Names 4–29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Batch Event Rule Variables 4–29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purge Tables 4–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents

B73.3.1 (6/99)

Hyper-Controls 5–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard Hyper-Controls 5–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Nonstandard Hyper-Controls 5–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Access Keys 6–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard Buttons 6–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu Titles 6–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Menu Titles 6–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Menu Titles 6–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Menu Items 6–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu Item Title, Long Description, and Access Keys for Menu Items 6–7. . How to Select an Access Key for User-Defined Menu Items 6–7. . . . . . . . . .

Access Keys For Specific J.D. Edwards Applications 6–9. . . . . . . . . . . . . . . . . . . Human Resources 6–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Event Rules Checklist 7–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . All Event Rules Checklist 7–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table I/O Checklist 7–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Performance Considerations 8–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance Considerations for All Forms 8–3. . . . . . . . . . . . . . . . . . . . . . . . . . . Performance Considerations for Find/Browse Forms 8–5. . . . . . . . . . . . . . . . . . . Performance Considerations for Header Detail and Headerless Detail Forms 8–7

Use of Text Strings to Name Fields 9–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . Text Strings Used in J.D. Edwards Software 9–3. . . . . . . . . . . . . . . . . . . . . . . . . . Approved Text Strings 9–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendices

Appendix A - Acronyms and Abbreviations A–1. . . . . . . . . . . . . . . . . . . . . . . . . . Appendix B - Field Sizes B–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix C - Standard Verbs C–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix D - Standard Icons D–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Glossary

Index


B73.3.1 (6/99)

B73.3.1 (6/99) 1–1

Application Design Standards Overview

The Application Design Standards guide is updated monthly. To ensure that your applicationscomply with the latest standards, request a current version of this guide. Application Design Standards include the following:

� ��

� ��

� ��

� �!��#��

� �� !�

� ��

� ��

� ��

� ��!��

� �� "��

� ��


1–2 B73.3.1 (6/99)

B73.3.1 (6/99) 2–1

Application Development Checklists

The application development checklists contain standards that J.D. Edwards developersmust follow when creating OneWorld applications. The checklists are intendedprimarily for J.D. Edwards developers and quality assurance analysts to ensure thatapplications comply with the standards. For developers external to J.D. Edwardsdevelopment, refer to the checklists as a guideline only.

The checklists provide standards for more than 500 issues, such as:

� ��

� ��

� ��

� ��

� ��

� ��

� ��

� ��

� ��

Separate checklists are provided for interactive applications and batch applications.Depending on the type of application with which you are working, refer to thefollowing chapters:

� ��

� ��

� ��


2–2 B73.3.1 (6/99)

B73.3.1 (6/99) 2–3

Interactive Application Development Checklist

The interactive application development checklist provides design standards regardingthe appearance and function of the controls used in interactive applications. Whilemany of these standards apply to all form types, separate checklists contain specificstandards for a particular form type. Where appropriate, the checklists also includespecific instructions for Manufacturing and Distribution (M&D) and Financialsapplications.

You should use the following development checklists for the appropriate designstandards:

� ��

� ��

� ��

� ��

� � ��

� ��

� ��


2–4 B73.3.1 (6/99)

All Forms Development Checklist

All standards apply to a minimized form with the exit bar turned off.

This checklist contains the following development information for all form types:

� �!�� !��! �� ! "� �"!��!��$ �$ !�� !�� !

� ��

� �� "��!��

� ��

� ��"��!"�� !��"!��

� ��%�!��

� "��$

Standards That Are Set Up Automatically by the Tool Set

When you create a new form in Forms Design Aid, certain standards are automaticallyset up for you. While you can change many of the settings, to do so violates applicationdesign standards. These standards are described in the following checklist:

� �� !�� !�� "�! ��! �� #��

� �� ! �� !�� !�#! � �&��! �� "��

� �� !�� !��

� ��!

� ��

� ��

� ��$

� ��!�

� ��

� �� !�!�� !�#! � �� !�!�� !�#! � ��$�

� �� %��

Form Appearance

Form appearance includes issues such as alignment of form controls, text properties,field size, and font characteristics. Properties for forms and form controls are definedusing the OneWorld Forms Design tool. For complete instructions on defining form andform control properties, see Forms Design in the OneWorld Development Tools guide.


B73.3.1 (6/99) 2–5

The following checklist applies to all form types:

� �# "$() ��(�( )�� #�)��! �$'" �$' �# �%%!��)�$# �( � ��#��'$,(� �$'"�

� !! �$'"(� �-��%) )�� "�((�� $'"� ��+� � ��#* ��' �#� �$$!��'�

� �� $$!��' �$#)��#( $#!. )�� ()�#��'� �*))$#(� ,�)� '�'� �-��%)�$#(�

� �)�)�� )�-) ��!�( �!!$, �$' �# �#�'��(� �# ��)�$#�! ��'��)�'( �$'

)'�#(!�)�$#� ��%�#��#� $# )�� #*"��' $� ��'��)�'(� ��#�'�!!. �# �#�'��(�

�# )�� ()�)�� )�-) ��!� (�/� $� �� %�'��#) %'$+��( �#$*�� '$$" �$'

)'�#(!�)�� )�-) �$' "�#. ��!�(� ��( "��#( )�� )�-) �$' "�#. ()�)�� )�-)

��!�( "*() #$) $��*%. "$'� )��# � %�'��#) $� )�� !�� !($� ��% �#

"�#� )��) �$*�!�0�.)� !�#�*��(� (*�� ( ��%�#�(� �#� ��#�(�� '�&*�'�

�$*' ��'��)�'( )$ )'�#(!�)� � (�#�!� #�!�(� ��'��)�'� ��(� �'� $#!.

��#�'�! �*��!�#�(�

Refer to the following table for a more accurate guide as to how much you mustincrease a static text field, based on the number of characters of English text:

Number of EnglishCharacters

Additional Space Required

1 character * 400 percent or 4 characters

2 - 10 characters 101 - 200 percent




More than 70 characters 30 percent

� ��)� )�� "%!�"�#)�)�$# $� �$'" )��(� .$* (�$*!� !�"�) �$'" �-�)(�

� �(� �'$*% �$-�( $# � �$'" )�� )$ �'$*% '�!�)�� !�(� *#!�(( )�� !�( $#

)�� )�� *(� �!! �+��!��!� (%�� #� �'� �!! '�!�)��

� �$'" )��( *(� �*!! #�!�(� )�-) )��) �( (�"%!�� ( "*�� ( %$((��!�

�,�)�$*) *(�#� ��'�+��)�$#(��

� �$'" )��( �$ #$) �$#)��# ��'�+��)�$#(�


2–6 B73.3.1 (6/99)

� �� !$� &��% �$� (�%��

� �� &��% �� !(�$��+ !&��$ &��%� ��& &�� '��$ !� &��% � +!'$

�""��&�! � �� %%�$+� �! %��$ $��$!'"� � &�� !$��&�! ! �!$�%�

� �%� �'�� %� &�*& ! �� !$� &��%�

� �� %"�� % �!$$��&�

� �� !$� �! &�� % ! �+ �""$!(�� $�(��&�! %� ��$! +�% � � (�$�%� ��

��

� �� !*�% � � $��! �'&&! % �� &! &�� & !� &�*& ��%� )�&� $�$�

�*��"&�! %�

� �! $�"$�%� & � $�(�$%� �� !$ �!$�� !�&)�$�� '%� �!�� $��&�$% � �

! �!�!$�

� � �&% !$ #'� &�&��% �!�� & ��%& �� &%�

� �� !�'�� & �'��$��+"��!�"� + �""��$ ! &�� %�� &!��&��$

�&��& �%� �� !�'�� & � �!$��&�! �""��$% ! &�� %��

� �� ! & �!$ �$�� &!&��% �% ��'�� ,"!� & �!�� $�� &!&�� % ��%�� &�� )�&�

&�� %+��!� Σ � &�� $!) ��$�

� �� % ��%�� &! '%�$ � "'&� &�� %&�&�� &�*& �%%!��&�� )�&� &��

�� % ��%! ��%��

� %%!��&�� &�*& �% !& ��%��

The following example shows static text that is not disabled:


B73.3.1 (6/99) 2–7

Example: Enabled Static Text

� �'�'�� '�+' �$$��%& �" ($$�%��&� �"� #*�%��&� ��%��'�%&� ��)�% (&� �

($$�% ��&��

� �)#�� '�� (&� #� "#(" &'%�"�&� *��%� $#&&�� '�� &��'�#" �� " '��& �(��

� �� %&' ��%��'�% #� � $%#$�% "#(" �& ��$�'� �-��

� � �#"'%# & '��' ��)� �&&#��'�� &�% ��"�� #�� '�� & ��)�

�&&#��'�� '�+'� *��%� &$�� #*&�

� � �%�� (&�& � �)�� &$�� #% ��&'��'�� %��&#"&� ��%� �%� "# $�%'��

�# (!"& #% �+'%� &$�� #" '�� "�'�� %�� ,#(% �#%! ��& !�", '��"�& �"

'�� "�� (' #" , '*# #% '�%�� # (!"&� '��" $ �� '�� %�� " � �#+

'��' �& '�� &�!� &�-� #� '�� #%! ��"� �"� ��"'�% '�� %�� *�'��" '��'

�#+�

� �� "�& #� '�� %�� %� �(&'#! �%�� "�&� '��" '�� (�%, �, �+�!$ �

�� "� �& %�!#)��

� ��%� �$$ �� (&� � �%�� )�%�� '# %�"�!� � �# (!" ��"� %�'��%

'��" �($ ��'�"� � �# (!" �"� ��"��"� '�� &�#* $%#$�%'��&�

� ��%� �%� "# (""��&&�%, )#��( �%, #)�%%��&�

� ��%�"��& '# !�� #��'&� &(�� & "#'�&� �!��&� �"� � � #��'&� �%�

��"'�� & �''��!�"'&�


2–8 B73.3.1 (6/99)

Form Function

Form function includes issues such as, fiscal year filter, summing data, displayingmessages, sequencing tabs, accessing help, and using visual assist. Form function canapply to the form itself or a form control. Depending on the particular issue, formfunction can be set up using Data Dictionary, Forms Design, and Event Rules Design.For complete instructions on defining various form functionality, see Data Dictionary,Forms Design, and Event Rules Design in the OneWorld Development Tools guide.

� �( '(- )+�%(�� '�1- '.&��+�

� �,� �'2 ( -"� (%%(0#'! -( )+�/�'- � .,�+ +(& ��,,#'! � (+& (+ +(0

�1#-

� �#,��%� -"� �1#-

� ,�- �' �++(+

� �#,)%�2 � &�,,�!� (+&

� � #,��% 2��+ #%-�+ .,�, -"� 4�#!#- ��-� #-�&� �� #,��% ��+�� , ,"(0' #'

-"� (%%(0#'! �1�&)%�

� �"�' .,#'! � �.�%��!�+ �'� �.�%��!�+ �2)�, �, #%-�+ #�%�,� -"� (+&

,"(.%� �� .%- �.�%��!�+ 0#-" �' �,-�+#,$ �� '� �.�%��!�+ �2)� �, �%�'$

.)(' �'-+2 -( -"� (+&�

� �( '(- .,� � "�+�4�(�� -�1- ,-+#'!� (+ �1�&)%� #' �� -( %(�� #�%� (+

/�+#��%�� ,� � -�1- /�+#��%� #',-��

� �+#� -(-�%, ,.& ('%2 ��-� -"�- #, -"� ,�&� ��-� -2)�� (+ �1�&)%�� ,.& �# �+�'- �.++�'�#�, (+ /�%.�, 0#-" �# �+�'- ��#&�% )%��,�

� �(-�%, (+ � (+& %�/�% �+� !�'�+�%%2 0#-"#' -"� !+(.) �(1 -"�- ,.++(.'�,

-"� !+#��

� �#!"-4�%#�$#'! (' � #�%� �#,)%�2, -"� ��-� #-�& �%#�, 0"�' -"� �"(0�%#�,

()-#(' #, �*.�% -( � #' -"� � /�+�,-� ,��-#(' ( -"� ��

� �(0 ()-#(', �#,)%�2 -"� �++(+ &�,,�!�� 3�( +��(+�, ,�%��-�� 0"�' 2(.

�--�&)- -( -�$� � +(0 ()-#(' �'� '( !+#� +��(+� #, ,�%��-��


B73.3.1 (6/99) 2–9

� �� !�� $��" �!� �� #&�� "��(�� $��"� �� #�"# #��"�

�� #� �� "$!� #��# #�� !�)��#�� "�!�� ! �� %� �� #�� &�( #� #��

��# �� #� #�� !��#�

� � �� " �%�� $#*�� "�

� ��"$�� ""�"# �" �%�� "��!�� "�

� ��#�� #�� !� #��" �!� �!��!�� "� $�� "$!�

#�� ("�� !��! �� #�� #��" �" #�� "�� " #�� #�� "� $�� "� #�� #��

��( ��" ��# �$�� !�$��

� ��#�� !�� #�� #�� "� $�� " &�#�� #�� !�$� ��'� �� #�� !�$� ��'

��#��" #&� �! ��!� ��$��"� #�� &� #�� #*��"# ��$�� #!��"

�� #�� &� #�� $�� #� #�� !��#�

Exception: If related controls appear side-by-side in different columns, then tabacross the row, or use an alternative order that makes more sense for theapplication.

The following example illustrates the desired tab sequence for this exception:

Example: Tab Sequence

� �� !�� " � #�� "#��

� �� #�� "� $�� " &�#� #�� "�

� �� #�� "� $�� " &�#� #�� !"# � ��


2–10 B73.3.1 (6/99)

Financials

This checklist contains design standards that apply to all form types used within afinancials application.

� �** !-,20-*1 $-0 �""0#11 �--) �3+ #0 : �� 2&�2 �0# ',.32:!�.� *# +312

�!!#.2 �, �*2#0,�2# ,3+ #0 �1 ',.32� �&# "#$�3*2 �""0#11 --) ,3+ #0 '1

"#2#0+',#" 7 2&# 17+ -*1 31#" ', 2&# �""0#11 �--) �-,12�,21� �1# 2&#

31',#11 $3,!2'-,� �� : �!03 �""0#11 �3+ #0� 2- �!!-+.*'1& 2&'1�

� �$ 7-3 )#7 ', �, �11#2 ,3+ #0 ', �, 3,),-5, $-0+�2� 13!& �1 �� 2&#

,3+ #0 '1 0#230,#" �1 2&# .0'+�07 �11#2 ,3+ #0 �1#" -, 2&# �'6#" �11#2

�-,12�,21� �1# 2&# 31',#11 $3,!2'-,� ��:�� : ��*'"�2# �11#2

�3+ #0� 2- �!!-+.*'1& 2&'1�

Human Resource/Payroll

This checklist contains design standards that apply to all form types used within ahuman resource/payroll application.

� �""0#11 --) ,3+ #0 �� '1 0#,�+#" 2- �+.*-7## �3+ #0 -0

�+.*-7## �-�

� �11-!'�2#" "#1!0'.2'-,1 $-0 27.# �," (- 12#. 1&-3*" ,-2 # 31#"�

�#1!0'.2'-, $-0 (- 27.#�12#. 1&-3*" # 0#20'#4#" $0-+ �- �,$-0+�2'-,

��

Manufacturing and Distribution

This checklist contains design standards that apply to all form types used within amanufacturing and development application.

� �&# �0�,!&��*�,2 '1 .*�!#" ', 2&# 3..#0 0'%&2 !-0,#0�

� �&# �0�,!&��*�,2 '1 2&# 12�2'! 2#62 $-0 �� -0 �� 5&#0# �..0-.0'�2#�

� �$ 7-3 )#7 �, �2#+ �3+ #0 ', �, 3,),-5, $-0+�2� 13!& �1 �� 2&#,

2&# ,3+ #0 '1 0#230,#" ', 2&# 1�+# $-0+�2 ', 5&'!& '2 5�1 #,2#0#"�

Localization

This checklist contains localization design standards that apply to all form types.

� �-0+ �," 0-5 #6'21 $0-+ 2&# �1# �..*'!�2'-, $-0 *-!�*'8�2'-, 0#/3'0#+#,21

�0# *� #*#" �#�%'-,�* �,$-�

� �&# +#11�%# -6 "'1.*�71 2&# 2#62� 9�#%'-,�* �,$-0+�2'-, ,-2 �4�'*� *# $-0

�1#0 �0#$#0#,!#1�� 5&#, 2&# �-3,207 �712#+ '1 *�,)�


B73.3.1 (6/99) 2–11

Currency

This checklist contains currency design standards that apply to all form types.

� ��

��

Currency CRDC Exchange Rate CRR Base CRCD Foreign

� ��


2–12 B73.3.1 (6/99)

Find/Browse Development Checklist

Find/Browse is usually the entry point to an application. It contains an optional QBEline so you can search on any database field in the grid. QBE columns that are grayedout are not in the business view and do not have QBE capability (for example, Sold ToName in the example above).

This checklist applies to find/browse forms and is categorized by the following:

� ��!� � ��!��

� ��!� �$��#��

� ��$��#$!�� "#!��$#��

� $!!��(

� ��#�� "��#�� !�#�!�� !��! #� ��

� ��#�� "��#�� !�#�!�� ! ��

� �#��!( ��" ��! ��

Form Appearance

Form appearance includes issues such as use of group boxes, field labels, row lines inthe grid, and form name. These issues are defined using the OneWorld Forms Designtool. For complete instructions on form appearance issues, see Forms Design in theOneWorld Development Tools guide.

This checklist contains design standards for form appearance that apply to Find/Browseforms.

� ��!� �" �� )��!� ��#� ��

� ��#� #�� #�#�� !� #��" �� #�� "��#�� !�#�!��

�� #��!( ��" �!� ��""�� !� #�� #�� #�#��" "��$�� !��

��#�� #�� #��!( ��"� !�" ��#�%��(�

� ��( ��" �!� %�"�� #�� !�

� �� " �!� ��#�� &�#�� !�$ ��'�

� �� !�$ ��' �!�$�� #�� ! ��" ��" �� #�#��

� �� )"�� #�� " �" ��&"�

� ��! � !�� #�� " �� !�� !�$��

� ��! � "�� "�� #� �#�� #��

� �� !�� " ��(" � !�& �� !!�!� ��! &�� (�$ &��# #� ��# �! ��

�##��#�� #� �� !�(�


B73.3.1 (6/99) 2–13

� ��! �� $��

Example: Disabled Row Lines on Find/Browse

� ��

� �� " �� $� ��

�� "� � �� "� ��

�� " �� $� ��

��"� !��

Form Function

Function for a find/browse form includes issues such as preloading the grid, exitingrows, and using filters. Depending on the particular issue, form function can be set upusing Forms Design and Event Rules Design. For complete instructions on setting upform functionality, see Forms Design and Event Rules Design in the OneWorldDevelopment Tools guide.

This checklist contains design standards for form function that apply to find/browseforms.

� �� # ��

��!�� # ��

��!�� #�

� �� !��

��

� ��


2–14 B73.3.1 (6/99)

� �, &)��$(" 0�&/ - !), - & �.$)( �-/�# �- �,�(�#��&�(. ), �)'*�(3�

� � +/$, � �)(.,)& !), - & �.$)(

� ��(" - & �.$)( �-/�# �- ��. -�

� && ,)14& 0 & 2$.- �$(�&/�$(" � & �. �(� #3* ,4�)(.,)& 2$.-� �&&)1 '/&.$*&

- & �.-� ��, 2� *.$)(- .) .#$- '�3 2$-.� �! � ,)1 2$. * ,!),'- �

')� & -- ��&& .) �().# , !),'� , * �. �� -#)/&� (). � '�,% � !), .#�.

2$.�


This checklist contains design standards that apply to find/browse forms used within ahuman resource/payroll application.

� �! ��, -- �))% (/'� , �� $- � !$&. , !$ &�� $. $- #$�� ( �(� .# ��.�

�$�.$)(�,3 $. ' �� $- /- � �- �( �,.$!$�$�& !$&. , !$ &�� , -- �))%

(/'� , $- *)*/&�. � �3 .# �/-$( -- !/(�.$)( �� 1#$�# $- ��&& �

!,)' .# �� 0 (. )( .# �� !),'

�)(.,)&� �� &&)1- '*&)3 (/'� ,� -)�$�& - �/,$.3 (/'� ,�

�&. ,(�. '*&)3 (/'� ,� ), �( �&*#� (�' - �,�# -.,$(" .) � (. , �

$(.) .# !),' �)(.,)&�

� �! ��, -- �))% (/'� , �� $- � !$&. , !$ &�� .# ( '*&)3 (/'� ,

�� -)�$�& - �/,$.3 (/'� , �� (� �&. ,(�. '*&)3 (/'� ,

�� , �&& �$-*&�3 � $( .# ",$��


The following issue applies to find/browse forms used within a manufacturing anddevelopment application.

� �), $. '4, &�. � !),'-� .# - �)(� $. ' �� ** �,- $( .# '�$( ",$�

�, �� # .#$,� �� (� -#),. �� $. '- �** �, $( .# -�,)&&4.) ",$�

�, ��

Currency

The following checklist contains currency design standards that apply to find/browseforms.

� �).# �)' -.$� �(� !), $"( �')/(.- �, $(�&/� � $( .# ",$�� 1# , �).#

�')/(.- �, �0�$&��& �

� �! �&& .# , �),�- $( .# ",$� , !& �. .# -�' �/,, (�3� .# ( .# �/,, (�3

�)� � 2�#�(" ,�. � �(� ��- �/,, (�3 �, �$-*&�3 � $( .# # �� ,

*),.$)( )! .# !),'� � .# � �� ,& -- .�$& 2�'*& !), !),'�.�


B73.3.1 (6/99) 2–15

� � �� % ��"� �� !��% �� $��

�� !�� %�� #��

� �� !�� !��%

��!�� %��

� �� !��%(�� !��

�� &�� #�� !��% �� !��

�%� �� "��!� �� !��% �� !��%(��

��

� �!��% �� #� �� #�� !��

�� !��

� � ��!� � ��

�� !� �� !��% �� !� � ��

�$�� '��( ��

If the Base Currency (currency defined at the Company level) is needed in QBE or as afilter field, then consider joining the transaction file to the Company Constants file(F0010). This provides direct database access to the Base Currency that can be used inQBE.

Example: The following form handles different currencies across many transactions.

Example: Difference Currencies for Transactions


2–16 B73.3.1 (6/99)

Additional Selection Criteria Prior to B73.3

From a find/browse form, use additional selection criteria for extra searchingcapabilities that the QBE cannot handle on a find/browse form. Use a headerless detailform to display additional selection criteria from the initial find/browse form, ifnecessary. For more information on headerless detail forms, see Header Detail andHeaderless Detail Development Checklist in this chapter.

Initially, additional selection forms were find/browse forms that included a nonstandardOK button. These forms may still exist, but the OK button has been removed and a newReturn exit has been added to the Form menu that performs the OK button event rule.The Select button on the Toolbar is not visible.

If you are developing a new form for additional selection criteria, use a headerlessdetail form rather than a find/browse form. Because the headerless detail form includesan OK button, you do not need to add a Return exit to the Form menu.

Initial Find/Browse Form

The checklist that follows applies only to initial find/browse forms that requireadditional searching capabilities prior to release B73.3.

� �(�(�� (�,( .��(�$#�! &�(�&�� ,�'('� �%%��&' �# (�� )%%�& !��(/��#� �$&#�&

$� (�� $&" +��#�*�& (�� *�!)�' $� (�� (�$#�! '�!��(�$# �&�(�&�� &� #$(

'�( ($ '�!��( �!! ��

� �!! ��(�$#�! '�!��(�$# �&�(�&�� &� ��# $# (�� &$+'� �$&"�

Additional Selection Criteria Headerless Detail Form

The checklist that follows applies to headerless detail forms that are called from aninitial find/browse forms to provide additional searching capabilities. For moreinformation on headerless detail forms, see Header Detail and Headerless DetailDevelopment Checklist in this chapter.

� ��(� (�� "%!�"�#(�(�$# $� �$&" (��' �# �� (�$#�! '�!��(�$# �&�(�&��

�#� ��(��$&- �$��' �&� ��''�� $# � �$&" (�� (�� (�(!�' '�$)!� &��

��(�$#�! ��!��(�$# �#� �(��$&- $��'� &�'%��(�*�!-�

� �&�$& ($ �� (�$#�! '�!��(�$# �&�(�&�� &� ��''�� $# � '�%�&�(� �$&"

�#(�(!�� .��(�$#�! ��!��(�$# &�(�&��

� � ��&!�'' ��(��! �$&" �' )'�� $& (�� (�$#�! '�!��(�$# �&�(�&�� (��

'�!��(�$# $� �!! ��'%!�-' �# �'(�&�' �� $&" )'�' (�� '�"� �)'�#�''

*��+ �' (�� !!�#� �&$+'� �$&"�

� �# (�� )(($#� �*�#( &)!� !$�� ' (�� #)"��& $� �&&$&' (��( $��)&

)'�#� (�� )'�#�'' �)#�(�$# ��(�&&$& $)#(� �� #$ �&&$&' $��)&� (��# (��

*�!)�' $� (�� (�$#�! '�!��(�$# �&�(�&�� &� %�''�� ($ (�� !!�#�


B73.3.1 (6/99) 2–17

�� !�� !��

�� " ��

� �� !��

��

� �� "��$��

�� !� �� #��

��

Additional Selection Criteria for B73.3

Implementation of additional selection criteria differs between release B73.2 andB73.3. Release B73.3 introduces form tabs and is the standard for additional selectioncriteria.

Category Codes for B73.3

As with additional selection criteria, form tabs is the standard for category codes.

Fix/Inspect Development Checklist

The fix/inspect form allows you to add a new record to a table or to update an existingrecord. The fix/inspect form includes OK and Cancel buttons. When you click OK,updates or additions are written to the table. When you click Cancel, any changes youhave made are lost and no database changes are made. Because the fix/inspect formonly allows you to add or update one record at a time, the form does not contain a grid.

The following checklist applies to fix/inspect forms and is categorized by thefollowing:

� ��

� ��

� ��"

Form Appearance

Form appearance includes issues regarding the form name and use of group boxes.Property definitions are defined in the OneWorld Forms Design tool. For completeinstructions on defining properties that affect form appearance, see Forms Design in theOneWorld Development Tools guide.

This checklist contains design standards for form appearance that apply to fix/inspectforms.


2–18 B73.3.1 (6/99)

� ��)�� $"��% �!#� %��% �$ �� #!� � ,�!#� ��%�� !#� ��##��$ %��

$�� !& �$ %�� ,�!#� ��%�� !#�� !��!(�� * � (!#� %��% ��$�#��$

%�� & �%�! !� %�� !#�� !# �)��"�� )�� $"��% �!#� %��% �$ ��

�#!� �!#� ��%� %�� $%�# (!&�� %�%�� %�� $%�# ��'�$�! $�

� �� !#��%�! �$ � � �#!&" �!)� %��% �$� ! ��$ �#� !&%$�� !� � �!)�

� ��#� �#� ! �!#� %�� '� �#!&" �!)�$ ! %�� !#��

Form Function

Form function includes issues such as blank and default values in form controls,preloading of form controls, returning to the browse form, and disabling key fields.Form function can apply to the form itself or a form control. Depending on theparticular issue, form function can be set up using Data Dictionary, Forms Design, andEvent Rules Design. For complete instructions on defining various form functionality,see Data Dictionary, Forms Design, and Event Rules Design in the OneWorldDevelopment Tools guide.

This checklist contains design standards for form function that apply to fix/inspectforms.

� �� !�� !#� �! %#!�$ �#� �� )��"% �!# ��&�% '��&�$��

Exception: For usability of the form, key data can be populated. An example ofthis is the Unit of Measure form that is populated from Item Master.

� �� !�� %�� )�� $"��% �!#� �!�$ !% #�%&# %! %�� #!($� �!#�

(�� $ "&$��

� � %�� !#� �$ &$�� !# ��$"��* "&#"!$�$ ! �*� ! ��$ �#� � "&% ��"��

�� ! %#!�$ �#� ��$�� $ �� #��!'�� #!� %�� !!��#�

� �� !�� !#� �! %#!�$ �#� "#��!�� #!� %�� #��!#� $��%�� !

%�� !#��

� �� !�� %�� )�� $"��% �!#� #�%&# $ %! %�� #!($� �!#� (��

�� $ "&$�� %�� !#� (�$ !% �� $ � �!��$$ �!#��

� �� !�� * ��$ � %�� # �#� ��$��

Currency

The following checklist contains currency design standards that apply to fix/inspectforms.

� �� %�� &##� �* "#!��$$� � �� $ !�� %�� &##� �* �! %#!�$ �#� ��

�&#� � %�� !� �$ �%��+�� '� %�


B73.3.1 (6/99) 2–19

� � � �&(�!�% � ��" �&- !) %&* � *�� )*&'�

� � � -� �%�� *� )!/� !) �� '!-�#)�

� � � �)� �+((�%�. &%#. �!)'#�.) * � ,�#+� �!* !) %&* !%'+*0��'��#�� )� �

�+)!%�)) �+%�*!&% *& (�*(!�,� * � �)� �&$'�%. �+((�%�. �&��

� � �% �&* * � �(�%)��*!&% �+((�%�. �%� * � �)� �+((�%�. �(� * � )�$��

* � �&(�!�% � ��" �&- !) �!)��#��

� �&( ��(*�!% *(�%)��*!&%)� )+� �) ��#�) �(��()� * � �+((�%�. �&�� %�

-� �%�� (�*� �(� '(&*��*�� !% � �%�� $&��

The following fix/inspect form complies with the standards in this checklist.

Example: A Fix/Inspect Form


This checklist contains design standards that apply to fix/inspect forms used within ahuman resource/payroll application.

� ��(�)) �&&" %+$��( �� ) &+#� �� !��% �%� �$'#&.��

!��%*!�!��*!&% � �� ) &+#� �� +)�� !% !*) '#�� '�%�!%� +'&%

* � ,�#+� !% �&$'�%. �&%)*�%*)� �!)'#�. �!* �( * � �$'#&.�� %+$��(

�� )&�!�# )��+(!*. %+$��( �� &( �#*�(%�*� �$'#&.�� %+$��(

�� !% * � �� !�#�� %�� * � ��)�(!'*!&% �&( �� *&

�''(&'(!�*�#. (�'(�)�%* * � ,�#+��


2–20 B73.3.1 (6/99)

� � �� ! �� !��

�� !� ��

Header Detail and Headerless Detail Development Checklist

Header detail and headerless detail forms both use the same development checklist.Descriptions of each form type are provided below:

Header Detail

The Header Detail form includes an input-capable grid so you can add or update detailrecords. Click OK to perform updates or adds to both tables on the form. When the userclicks Cancel, any changes are lost and no database changes are made.

The Header Detail form allows you to work with data from two separate tables. Youcan use this form to add or update a single header record. You can also add, update, ordelete multiple detail records from the same form.

Because the Header Detail form allows you to update or add records from two differenttables, you can attach two business views to a Header Detail form. Attach one businessview to the grid and the other to the form, updating both tables from a single form.

Headerless Detail

The Headerless Detail form is used to display multiple records from a single table thatis not normalized. Because this form is used to update only one table, you can attachonly one business view to the form.

The Headerless Detail form contains an input-capable grid, where you can add orupdate detail information. The header portion of the form displays data common to allthe detail records in the grid. Both header and detail information come from the samebusiness view.

Click OK to perform updates or additions to the table. When the user clicks cancel, anychanges you have made are lost, and no database changes are made.

Combined Checklist

The following checklist applies to header detail and headerless detail forms and iscategorized by the following:

� ��

� ��

� ��!


B73.3.1 (6/99) 2–21

Form Appearance

Form appearance issues for header detail and headerless detail forms include the formname, vertical and horizontal grid lines, and grid column requirements. Formappearance issues are controlled through form control properties that are defined in theOneWorld Forms Design tool. For complete instructions on defining properties, seeForms Design in the OneWorld Development Tools guide.

� ��$ ��&�� !$ ��$��%% ��&�� !$� &��& �% �� $!� � -�!$�

��&�� !$� ��$$��% &�� %�� !' �% &�� -�!$� ��&�� !$�� !��!)��

�+ � )!$� &��& ��%�$��% &�� ' �&�! !� &�� !$�� !$ �*��"�� $

��&�� !$ ��$��%% ��&�� !$� &��& �% �� $!� �!$� ��&� &�� %&�$

)!'�� &�&�� &�� %&�$ ��&��

� �!$ ��$��%% ��&�� !$�%� )�&� &�� "�� &�&�! !� �!$� &��% �

�� &�! �� %��&�! �$�&�$�� $� ��%%�� ! � �!$� &�� &�� &�&��

%�!'�� $�� &�! �� &�! �

� ��+ ��% �$� (�%�� &�� $ )�� !$� &�� % '%��

� � � ��&�� !$� �*�%&%� �� !�'� % � ��'�� &�� $�� ""��$ ! � ��&��

��*� %"��& �!$��

� �� "$!"�$&��% !"&�! �!$ $!) ��$ �% �� &! ��!) �!$ ��&��"

��%"��+�

� !&� (�$&�� !$�,! &�� $�� % �$� $�#'�$��

� �� -%��" &!� ��% �% �!��!)%�

� �!$ � $� �� &�� % ��" �$!� � � ��" ��$!'��

� �!$ � %� �� %��" &! �&�� &�� " �!�

Form Function

Form function issues for header detail and headerless detail forms include issues suchas allowing blank values, loading default values, allowing multiple grid selections,preloading form controls, and disabling key fields. Form function can apply to the formitself or a form control. Depending on the particular issue, form function can be set upusing Data Dictionary, Forms Design, and Event Rules Design. For completeinstructions on defining various form functionality, see Data Dictionary, Forms Design,and Event Rules Design in the OneWorld Development Tools guide.

This checklist contains design standards for form function that apply to header detailand headerless detail forms.

� �� &�� $�� % %�& '" &! ��!) �!$ �'�&�"�� %��&�! � � � $!) �*�&

"�$�!$�% � �!��%% �� &! � !&��$ �!$�� &�� (� & $'�� %�!'�� !& ��

��$�� &! $�"��& �!$ &��& �*�&�


2–22 B73.3.1 (6/99)

� �! ��! #!��"��#�� !��!��"� ��!#��# ��" �� #�� ! �!�

�!�#��#�� #�! ��#��! �� ! ��# �� " �'��$#�� "$��""�$��( #��

��!"# #�� %��# �� $��#�� #�� "�� #�� #��

��!#��# ��" �!� ��("� � ��#� �� $!!��( ��!��#��

� �� ! �� " ��! � ��! #!��"��#�� !��!�� "#�!

�$"��"" �$��#�� $��#�" #�� #�� !��

� �� #�� !� �" �� '��# ��! ��( ��$�# %��$�" �� !��

��!� ��#�!��#�

� �� #�� !� �" �!�� !�� #�� !��!� "��#�� #��

�� !��

� �� ( ��" �� #�� ! �!� ��"��

Currency

The following checklist contains currency design standards that apply to header detailand headerless detail forms.

� �� #�� $!!��( �!��""�� " �� #�� $!!��( ��#!��" �!� ��

�$!�� #�� " ��#��)�� %��#�

� �� #�� !�� ' �" "��#�� #�� $!!��( �� "�

�$!!��( �!� ��!��#� �# �" ��# "��#�� #� �$!!��" �!� #�� "��

� �� #�� !�� ' �� $�"��#�� ! � ��!��

#!��"��#�� ! ��#�!�� #�� "#�� $�%��# �� #�� #!��"��#��

� �� #�� !�� ' ��!" &�#� #�� %��$� �� #��

#!��"��#�� " �!��( ��#�!��

The following form complies with the standards in this checklist.


B73.3.1 (6/99) 2–23

Example: A Header Detail Form

Parent Child Form Development Checklist

You can use the parent/child form to represent parent/child relationships in anapplication. The form has a parent/child control placed where the grid resides in aFind/Browse form. The composite control presents a tree view in the left portion of theform which displays a visual representation of the parent/child relationship. The rightportion of the composite control displays a grid in browse mode. The grid displays thedetail records for the child node of the tree.

The parent/child form is created with the composite control, and Select and Closebuttons.

This checklist contains the following development information, which applies toparent/child forms:

� ��

� ��

Form Appearance

This checklist contains design standards for form appearance that apply to parent childforms.

� ��

��

��


2–24 B73.3.1 (6/99)

� ��

Form Function

This checklist contains design standards for form function that apply to find/browseforms.

� ��

��

� ��

��

All other find/browse rules apply.

The following is an example of a parent/child form.

Example: A Parent/Child Form


B73.3.1 (6/99) 2–25

Message Form Development Checklist

Use the Message form to display messages or request action from the user. The form ismodal and is also not sizable. You can add only static text and push buttons to thisform. This form is the only one that allows standard push buttons, including OK,Cancel, Yes, and No buttons.

A delete confirmation is a good example of how you can use the Message form.

There is no business view for this form type.

This checklist contains the following development information, which applies tomessage or confirmation forms:

� ��

� �� "��!��

Form Appearance

This checklist contains design standards for form appearance that apply to message orconfirmation forms.

� �� ! � !�� & �� !&�� $�� "!!��

" ��

� �� "!!��

� �� "�� !�!�� !�%! �� $��

� �� !�%! �� "�� $�!�� "� ��%�

Form Function

This checklist contains design standards for form function that apply to message orconfirmation forms.

� �� " �� &� �� !�� "��!� �� "��

��$��

� � ��!� !�"�!"�� !!�� "�! �� "! �� !��

� �� (��#�� #��! �"�� !��'�� !�� & �#��!

"��!��

� �� " �(�"!!�� #��! �"�� " � !�� #��! �"!!��

� ! �"!!�� #��! �"��


2–26 B73.3.1 (6/99)

� ��

��

The following is an example of a message form.

Example: A Message Form

Search and Select Development Checklist

Use this form to locate a value and return it to the calling field. The Search and Selectform is called using a visual assist (flashlight) or hyper-control.

After you create a Search and Select application, you must attach the Search and Selectform to the specific data item for which it was created. You do this using the visualassist trigger in the Data Dictionary or the overrides in the property sheet for thecontrol.

This form only displays information; you cannot edit fields. Therefore, the formcontains Select and Close options.

The data structure for this form should contain only one element. This data item will bepopulated automatically by the tool from the control or grid column that has this searchand select form attached. The Search and Select forms are attached to a control or gridthrough the data dictionary visual assist trigger. An example is the UDC Visual Assist.When a control has a UDC visual assist trigger, the control’s value will automaticallybe passed to the data structure of the UDC Search and Select form.


B73.3.1 (6/99) 2–27

The Search and Select form includes a grid where you can view multiple records in onetable. The grid displays valid values. When a user chooses a value from the grid andclicks Select, that value is automatically returned to the calling field.

Because this form is used to view records from only one table, you can attach only onebusiness view to a Search and Select form.

Use the following checklist when creating a search and select form:

� ��

� ��

��

� ��

��

� ��

��

��

� ��

� � � ��! ��

All other find/browse rules apply.


2–28 B73.3.1 (6/99)

B73.3.1 (6/99) 2–29

Batch Application Development Checklist

The batch application checklist contains guidelines you should follow when creating anew report or batch application. This checklist assists you with various issues such aspresentation of totals and grand totals, use of error messages and job status messages,placement of and required content for report headers, and use of cover pages.

This checklist applies to all OneWorld batch applications for the following types ofinformation:

� �� !� �! �� % �% ��

� ��

� ��#��

� �� ! �!

� ��

� !��%

Standards That Are Set Up Automatically by the Tool Set

When you create a new report or other batch application, certain standards areautomatically set up for you. While you can change many of the settings, to do soviolates design standards for batch applications. These standards are described in thefollowing checklist:

� �� $ �� &�� (��!��

� �� !�� !�� (��

� �� !�� !� �� !� �� "��!��

��

� �� '�� #�� % �� !�� !��

�� (��

� ��

� �� % ��


2–30 B73.3.1 (6/99)

Report Appearance

� �##�$ �!� �")�$ ��%� ��$��&�$% �+ �� '%��

� �%� "!�+ �##$"(�� $�(��&�"!%� �� '%� "� ��$�(��&�"!% �% �"!%�%&�!&

&�$"'��"'& &�� $�#"$& %�&� ��

� �("�� &�� '%� "� �"!%&�!& &�*& �!� &�*& "(�$$��%� )��$� #"%%��

� �%� "!�+ ��&��%� �&� % �!� �%%"��&�� %�$�#&�"!%� )��$� #"%%��

� ��'�& %#�� &)��! �"�' !% �% ��(� ��$��&�$%�

� �'%&��&�"! "� ��&� �! �"�' !% "! $�#"$&% �% �% �"��")%�

Numbers - right

Strings - left

Characters - centered

Dates - centered

Note: You can accept the default justification for numbers, strings, and datesbecause OneWorld already matches the standard for justifying column data.However, for character data you must set the default justification to centered.

� ��#"$& $��&% � ��!�%��#� "$��!&�&�"!�

� ��#"$& $'!% "! ��%�$ #$�!&�$%�

� ��#�$ %�,� �% �� * �� %&�!��$� �! &�� '!��%% +"' �$� #$"��%%�!� �

%#�� "$ �

� �!��$��!� �!� ��!&�$ �"�' ! ��!�% "(�$ &�� )��&� "� &�� "�' !�

� �(�$��!� &"&�� "'!&% )�&� � %�!�� !��

� � �$�!� &"&�� %�"'�� $��& � %�!�� "(�$��!� �!� � �"'�� '!��$��!��

� �"&�� "'!&% �$� ��!�� $��&�+ ��!��&� &�� "'!& ��% &" )��

&��+ �##�+�

� ��$� �$� !" #�� ""&�$% !"$ $�#"$& �""&�$% �! � %&�!��$� �� )�$�%

$�#"$&�

Batch Application Development Checklist

B73.3.1 (6/99) 2–31

Viewing

� �� #�,�# � )��* &% &� *�� (�'&(* )�&+#� �� )�� &% � �+) %�)) , �- *��*

�&%*� %) �## �&#+$%) &� *�� *��#� *& �##&- �&( ��*� )�#��* &% &,�( �%/

�&#+$% �(&$ *�� *��#��

� � ��,�# � )��* &% �%� �## &� *) �))&� �*�� )��* &%) �(� �(&+'�� *&��*��( %

(�'&(* , �- %��

� &%� * &%�# )��* &%) *��* �(� %&* ��##�� (� #&��*�� * *�� &**&$ % (�'&(*

, �- %��

� &%� * &%�# )��* &%) *��* �(� �))&� �*�� - *� $&(� *��% &%� ��,�# �

)��* &% �(� #&��*�� * *�� &**&$�

� ��% %�� %� *& '�(�&($ '(&��)) %� *��* �&�) %&* '(&�+�� '( %*��#�

&+*'+*� +)� � �(&+' )��* &% �%� �� %� )��* &% '(&'�(* �) �) � %&%, ) �#�

�%� �&%� * &%�# )��* &%�

� �)� �,�%* (+#� ,�( ��#�) %)*�� &� �#&��# ,�( ��#�) -��(�,�( '&)) �#��

/&+ $+)* +)� �#&��# ,�( ��#�)� +)� � �(&+' )��* &% $�("�� ) �&%� * &%�#�

� &%)*�%*) �(� +)�� *& '#�� &$$�%*) % )��* &%) *��* �(� %&* , ) �#� &( %

�&%� * &%�# )��* &%) *��* �(� %&* ��##�� )� �&$$�%*) ��% �� )'#�/��

% (�'&(* , �- %�� &%)*�%* *��* �&%*� %) *�� )��* &% %�$� �%�

��)�( '* &% ) � )*�%��(� �&$$�%* % *��)� )��* &%)�

� �� (�'&(* ,�( ��#�) % � %&%, ) �#� )��* &% �(� � )'#�/�� % (�'&(*

, �- %�� )��* &% �&�) %&* � )'#�/ % *�� (�'&(* &+*'+* -��% *�� ) �#�

��"�&. ) +%��"�� &% ��* &% �(&'�(* �)��

Reports to Output

� �� '�� ( ) #&��*�� * *�� *&'�

� � �&$$&% (�'&(* �&%*� %) � ��,�# � )��* &%� � �&*�# )��* &%� �%� � ��,�#

(��" ��( )��* &%� �� ,�# � )��* &% �''��() � ()*� �&##&-�� / *��

�&*�# �%� ��,�# (��" ��( )��* &%)�

� ��$& ,�() &%) &� � (�'&(* )�&+#� %&* �� )�* *& '( %* � �&,�( '��

� &( �% �((&( (�'&(* *��* ) ��) �%�� *& &%#/ '( %* �((&() �%� *��(� �(� %&

�((&()� *�� (�'&(* ��( '( %*)� �&##&-�� / � �&%� ($�* &% # %� *��* (��)�

0�& �((&()��

� &( (�'&(*) *��* �& %&* ��%�(�*� �%/ &+*'+*� %&*�)� &( �((&( $�))��)� *��

)�%� $�))�� )/)*�$ �+%�* &% )�&+#� �� +)�� *& )�%� *�� &( � %�*&( &� *��

��*�� !&� � $�))�� %� ��* %� -��*��( *�� *�� !&� �&$'#�*��


2–32 B73.3.1 (6/99)

��

��

� ��

Reports to File

� ��

Currency

� ��

��

� ��

B73.3.1 (6/99) 2–33

Processing Option Tabs Checklist

Processing option tabs prompt the user for information required to run an application.At runtime, the user indicates the desired processing option value in an entry field thatappears on the form tab. If a user requires additional information to enter processingoptions, the user can access field help and form tab help.

The following is an example of the processing options form tab from the Issues(P4112) application on the Inventory Master/Transactions (G4111) menu.

This checklist contains guidelines for the following:

� ��

� ��

Processing Option Form Tabs

� ��

��

��


2–34 B73.3.1 (6/99)

� �%� �""��&�! .%"�� &��% )�� & ��% %� %� &! �! %!� �% ��&�$��

)�&� +!'$ �$!%%.�' �&�! �� &��

� �� &��+ �� !$� )�&� � �!$� '��$ &��& �% '%�� &! $�&$��(� �!$� ��"�

Processing Option Fields

Most processing options consist of a single field; however, a processing option mayhave multiple fields. In any case a processing option field contains the following:

� � �� &�&�� &�� &! ! � ��

� �� &$+ �� ! &�� $��& !� &�� &�&��

� ��!)�� (��'�%� �� ""�� %&�� ' ��$ &�� &�&��

Refer to the following checklist when adding processing option fields to the form tab:

� ��& &�� &�*& �!$ � "$!��%%� � !"&�! &! ! � �� )�&�!'& )$�""� �� +!'

�'%& ��!) �!$ &$� %��&�! !� &�� &�*& �+ '%� � ! �+ � "�$�� & !� &��

��!)�� $��&�$ %"�� % )�� !) �!$ '" &! �� *"� %�! �

&$� %��&�! �

� ��&.�� &�� &�&��

� ��&.�� (�� (��'�%�

� �!��!) %&� ��$� ��"�&��,�&�! $'��% �!$ �� %� �% %�!) � &��

�*��"��

� �� )$�&� � (�� (��'�%� &+"� &�� (��'� � '��$ !$ &�*&�� !��!)�� +

! � %"�� #'�� %�� %"�� &�� %�$�"&�! !� &�� (��'��

� �! � ��&� � %"�� &$+ �% � (�� (��'�� %'�� % � %"�� %'��$

&+"� !$ �'%� �%% ' �&� � ��'�� $&�� &�� !$ �*��"�� &+"� -�

%"�� %'��$��

� �"�&��,� &�� $%& )!$� !� &�� (��'� � � &�� $%& )!$� � &�� %�$�"&�! �

Do not include additional information for valid values, such as dependencies ordetailed descriptions of entries. For example, do not type “Applies only to aspecific ledger type” or directions that are lengthy. Place this information in thefield helps for the processing options.

B73.3.1 (6/99) 3–1

Partners in Development Considerations

This section contains critical information for development of products and applicationsoutside of J.D. Edwards. These modules and applications can be categorized as follows,according to the intended distribution:

� ��

� ��

��

This section addresses important guidelines for Partners in Development, includingJ.D. Edwards consultants and third party application developers. These considerationsare necessary to prevent collision between J.D. Edwards objects and externallydeveloped objects.

Partners in Development Administrator and System Codes

Depending on the object type, you must follow the naming conventions defined in thefollowing sections. Regardless of the object type, the system code is contained in thenaming format and allows for classification of objects across all systems.

Where it is anticipated that objects will be distributed beyond the enterprise, developersshould coordinate with the Partners in Development Administrator. Your Partners inDevelopment Administrator assigns system codes for your specific set of objects toensure that externally created objects are unique and do not collide with J.D. Edwardsobjects. These system codes begin with Y or Z.

For enterprise-level development, developers should use system codes 55xx through59xx.


3–2 B73.3.1 (6/99)

B73.3.1 (6/99) 4–1

OneWorld Naming Conventions

Imagine if there were no OneWorld naming conventions. It would be chaos for you andthe database. You could not look at a table name and know it is a table. A user orupgrade could overwrite a data dictionary item, table or application with another datadictionary item, table or application with the same name.

It is important to have a standardized naming convention for OneWorld objects. Eachobject, such as a table, report, interactive application, or menu must have a uniquename.

This section includes the following information:

� ��

� ��

� ��

� ��


4–2 B73.3.1 (6/99)

B73.3.1 (6/99) 4–3

Understanding OneWorld Naming Conventions

A OneWorld application is composed of multiple objects. Additionally, you mayfurther define characteristics within an object. For example, when you create a table,you may designate a key that consists of more than one field within that table. Whenyou create the index, you should follow the standard for naming that index.

When you create a new object in the Object Librarian, you must name the object andprovide a description. Naming conventions provide a standard for each object type youcan create.

Before you create a new OneWorld object, you should understand the following:

� ��

� ��


4–4 B73.3.1 (6/99)

Naming Conventions for Objects

Use the following chart as your guide when naming objects.

x xx xxFirst digits — Object Type

B Business viewD Data structureF TableN Event rule business functionP ApplicationR Batch applicationS Section nameT Processing options data structureV Business viewW FormGT Media objectWF Workflow data structureR89 Table conversion

Second and third digits — System Code00 World Foundation Environment01 Address Book02 Balance03 Accounts Receivable55 Reserved for clients

For acomplete listof systemcodes, seeUser DefinedCodes,system 98,record typeSY

The fourthand fifthdigits onlyapply tointeractiveand batchapplications.

Fourth and fifth digits* — Group Type01 Master02 Balance1X Transaction

*Fourt and fifth digits only apply to applications.

See Also

� � ��

Understanding OneWorld Naming Conventions

B73.3.1 (6/99) 4–5

System Codes

The system code is included in an object name. For a complete list of J.D. Edwardssystem codes, see User Defined Codes, system 98, record type SY.

If you are an external developer creating objects for use in a OneWorld application, youmust contact the Partners In Development Administrator for a unique system code.System codes for external objects begin with Y or Z.

If you are performing JDE custom work, use system codes 60-69.

See Also

� ��


4–6 B73.3.1 (6/99)

Example: Program and File Names

The following chart shows examples of the naming conventions for tables, forms, andapplications:

Tables

Account Master Table F 09 01

Object Type TBLE

System Code (General Accounting)

Object Group Type (Master)

Account Master Alternate Logical F 09 01 LA

Object Type TBLE


Object Group Type (Master)

Version Identification (Logical)

Forms

W 09 01

Object Prefix W is automatically

assigned for forms


Object Group Type (File Maintenance)

Applications

P 09 01

Object Type APPL


Object Group Type (File Maintenance)

B73.3.1 (6/99) 4–7

Data Dictionary Naming Conventions

This chapter is devoted entirely to OneWorld data dictionary item conventions.Whether you are an internal J.D. Edwards developer or a developer external to J.D.Edwards, such as a Partner in Development, you must refer to the data item namingconventions. Adhering to these conventions ensures database integrity and preventsdata items from being overwritten or colliding with other data items.

If you are creating a data item for use in WorldSoftware and OneWorld, separatelimitations and considerations are required that are not addressed in detail in this guide.For OneWorld only data dictionary, refer to this chapter for information on:

� ��

� ��

� ��

� ��

� ��

� ��

� ��

� ��

� ��

� � ��

See Also

� ��

Data Item Alias

The data item alias is an 8-character alpha code. If the data dictionary item is exclusiveto OneWorld applications, the alias is five or more characters in length. When adding adata item that will be used in a table by an RPG program, the alias must not exceedfour characters.


4–8 B73.3.1 (6/99)

The data item alias is used when searching, within database routines (applicationprogram interfaces used in business functions), and within Table Design when creatinga table. For each table, a prefix is added to the alias, which makes it unique to thistable. For example, ABMCU indicates that MCU is within the Address Book.

When assigning an alias, do not begin the alias with TIP nor TERM. Aliases that beginwith TIP are reserved for OneWorld tips information; aliases that begin with TERM arereserved for use by J.D. Edwards Publications to provide term glossaries in OneWorldguides.

Blanks and the characters % & , . + are not allowed as part of the data item alias inOneWorld.

You can also identify a data item by the data item name or alpha description.

Once added, you cannot change the data item name or alias.

Alias for an External Data Dictionary Item

An external data dictionary item is one that is created by a developer outside of J.D.Edwards for use in OneWorld. For external data items, the data dictionary alias can be amaximum of eight alphanumeric characters and uses the following format:

Ysssdddd, where:

Y or Z = designates external data dictionary item and is the first digit ofany JDE-assign external system code.

sss = the system code number assigned by the Partners in Developmentsystem administrator, or 55xx-59xx for enterprise-level development ofnew modules, or 60xx-69xx for JDE custom development

dddd = the name of the data dictionary item

Data Item Name

The data item name is a 32-character, alphabetical field that identifies and defines adata item. You must allow enough room in the field name for a 30 percent expansion ofthe English text for translation.

The data item name forms the C-code data name (for example AddressNumber) that isused in business functions, data structures, and event rules.

When creating a J.D. Edwards data dictionary item, do not use a Y or Z in the firstcharacter of the data item name. Y and Z are reserved for Partners in Developmentbusiness partners. (J.D. Edwards data items beginning with Y or Z may exist prior theB73.2 release of OneWorld. These items will remain J.D. Edwards items.)


B73.3.1 (6/99) 4–9

Blanks and the characters % & , . + are not allowed as part of the data item name inOneWorld.

You can also identify a data item by the alias or alpha description.

Once added the data item name cannot be changed.

Data Item Name for an External Data Dictionary Item

When creating an external data item, you must use a Y or Z in the first character of thedata item name to distinguish an external data dictionary item from a J.D. Edwards datadictionary item.

The data item name can be a maximum of 32 alphanumeric characters and uses thefollowing format:

Ysssdddddddddddddddddddddddddddd, where:

Y or Z = designates an external data dictionary item and is the first digitof any JDE-assigned external system code

sss = the system code number assigned by the Partners in Developmentsystem administrator, or 55xx-59xx for enterprise-level development ofnew modules, or 60xx-69xx for JDE custom development

ddddddddddddddddddddddddddddd = the name of the data item name

Data Item Prefix

In a OneWorld table, a column table represents a data item. The Table Design Aid toolassigns a table column prefix to each column or data item. If a table is used exclusivelyin OneWorld, the column prefix assigned to the table does not have to be uniquebecause OneWorld qualifies the column with the table name. For example, table F0101has a column prefix AB and Address Number is data item AB in that table. OneWorldreferences AN8 as F0101_ABAN8. If another table F740101 uses the same prefix ABand AN8, OneWorld references that column as F740101_ABAN8, making it unique aswell.

If a Development Business Partner or customer wants to use Address Number (AN8) ina new table that will be part of a coexistence environment, the Business Partner orcustomer must use “Q” as the first column prefix character in order to make it unique.The second column prefix character needs to be unique only if the column willinterface with another “Q” prefixed table.

See the following example:


4–10 B73.3.1 (6/99)

No change is necessary

because the table qualifier

will make the data item

unique.

Partner Table 1

Co-existence?(AS400)

J.D. Edwards Table Partner Table 2

F0101_ABAN8Column Prefix: AB



No change is necessary

because the table qualifier

will make the data item

unique.

No

Yes

Change the Column Prefix to

make data item unique.

Column Prefix: Qx

QxAN8

QxAN8Column Prefix: Qx

QxAN8Column Prefix: Qy

No

Yes

No change is necessary.

Change the Column Prefix to QY

to make data item unique.

Interface with other QxColumn Prefix tables?


B73.3.1 (6/99) 4–11

Data Item Description

The data item description categorizes a data item on which you can search in theOneWorld Data Dictionary. When you create a new data item, provide a descriptionusing the following conventions, depending on the data item type:

Address Number Begin all address numbers, such as employee, customer, owner,with Address Number.

Amount Begin all unit, quantity, and volume fields with Units.

Code Begin all code fields with Code.

Date Begin all date fields with Date.

Factor Begin all code fields with Factor.

Name Begin all 30-byte description fields with Name.

Prompt Begin any Y/N prompting field with Prompt.

Units Begin all units, quantity, and volume fields with Units.

Row Description

Provide a description that appears for the field description on forms and reports. Therow description can be a maximum of 40 characters after translation. This meansEnglish text must allow for an expansion of 30 percent for translation. Use approvedabbreviations whenever possible.

Column Title

You can provide a one- or two-line description that will appear in column headings onforms and reports. The description should be no larger than the data item size, ifpossible. If the column heading requires only a single line, enter the description in theColumn Heading 1 field. Use the Column Heading 2 field when a single linedescription is unclear.

Also, the English text for column title must allow for an expansion of 30 percent fortranslation.


4–12 B73.3.1 (6/99)

Processing Option Data Item

Processing options for fields are accomplished using the data dictionary. Eachprocessing option field must be associated with an alternate data item (help item) inaddition to the alias data dictionary item.

Use the H glossary group when adding the data dictionary item. The namingconvention for a processing option should be formatted as follows: Sxxyyyyzz

S = processing option

xx = a 2-digit system code

yyyy = the program number

zz = a sequential number

Provide an alpha name that is usable, preferably the name of the processing option, forexample:

this: “Disable or Hide Status Codes”

not this: “Ship Confirmation Processing Option 1”

Enter the name of the entry field to which the item is to be attached. This name shouldbe the same as the field title shown on the tab form.

Note: Do not enter a ‘.’ (period) in the Description field because this will prevent yourwriter from updating the glossary portion of the data dictionary item.

Use the following guidelines when entering the glossary text for the processing optionitem:

� ��

��

��

��

� ��

��

��

Workflow Message Data Item

The naming convention for a workflow/send message should be formatted as follows:LMxxxx

LM = workflow/send message


B73.3.1 (6/99) 4–13

xxxx = any 4-digit number

System codes 5000-9999 are reserved for clients.

Error Message Data Item

Create error messages in World software and let the system assign the default alias anddata item name. This automatically enforces the standard for data items that arereserved for clients, that is error messages 5000-9999.

Development partners must preface an error message data dictionary item with thesystem code assigned by the Partners in Development system administrator, using thesame naming standard for the data item alias as discussed in �� .

Table I/O Data Item

B73.3 implements the table I/O enhancement whereby a data item for a table is used asa handle to manipulate table records. A data item is created that is specific to the table.The data item name can be a maximum of eight characters and should be formatted asfollows: HFxxxxxx

HF = designates a table I/O data item

xxxxxx = system code and group type used in the table name

For example, the table I/O data item name for table F4211 would be HF4211.


4–14 B73.3.1 (6/99)

B73.3.1 (6/99) 4–15

Object Naming Conventions for Interactive Applications

Object naming conventions provide a methodology for identifying object file namesused in interactive applications. An interactive application consists of multiple objects,such as a table, business view, form, and event rules. Thus, before you can begin tocreate an application, you must add the objects required for your application.

This chapter provides detailed instructions for naming an object. When you add newobjects, refer to the naming conventions for the following object types:

� ��

� ��

� �!�� "��#�

� �� "��#�

� ��

� ��

� �� !� !��

� ��

� �"�� !�� "��

� �$ "��

� �!�� !�� "�� !��

� �!�� !��

� �!�� !�� !� !��

� ��# �� !� !��

� ��


4–16 B73.3.1 (6/99)

Tables

The Object Librarian name for a table can be a maximum of eight characters andshould be formatted as follows: Fxxxxyyy

F = data table

xx (second and third digits) = the system code, such as

00 - OneWorld Foundation environment

01 - Address Book

03 - Accounts Receivable

xx (fourth and fifth digits) = the group type, such as

01 - Master

02 - Balance

1X - Transaction

yyy (sixth through eighth digits) = object version, such as programs that performsimilar functions but vary distinctly in specific processing

JA through JZ - Table join

Provide up to a 60-character description for a table.

The table description is the topic of the table. If it came from the AS/400, it should bethe same name as the file it represents, such as Address Book Master (F0101) and ItemMaster (F4101).

External Developer Considerations for Tables

External development refers to creation of applications by developers outside of J.D.Edwards, such as Partners in Development and J.D. Edwards consultants that maycreate custom applications for a specific clients. You must use caution when naming atable to prevent collisions between J.D. Edwards and non-J.D. Edwards objects. Whencreating a new table, format the table as follows: Fxxxxyyy, where

F = a data table

xxxx = the system code applicable to the enterprise

yyy = a unique next number or character pattern unique within the enterprise


B73.3.1 (6/99) 4–17

See Also

� ��

Indices

List the field as the index name, such as Address Number, if there is only one field inthe index.

For coexistence, it is critical that OneWorld indices match logicals on the AS/400.When you run the Generate Table command in Table Design, OneWorld automaticallylooks to the AS400 and checks to see if a matching AS/400 file exists. If a matchingAS/400 file does not exist, then OneWorld creates logical files on the AS/400. If amatching AS/400 file exists, OneWorld does not create any logicals on the AS/400.

If there are two fields in the index, list them consecutively, such as Address Number,Line Number ID.

List the first two fields followed by an alpha character (A), such as Address Number,Line Number, A if there are more than two fields in the index and the first two fieldsare the same as the first two fields of another index. Otherwise list the fields followedby a (+), such as Item Number, Branch, +.

Place a comma ( , ) and space between each index field and between the last index fieldand the plus sign.

Do not include more than 10 fields in an index.

The total length of the index name cannot exceed 19 characters if the index has two ormore fields. If you exceed 19 characters, the compiler will give you a warning of“Re-definition is not identical...”. This will impact fetches using the wrong index ID inbusiness functions.

The following example shows multiple indices that have been defined for the ShopFloor Control Parts List table (F3111).


4–18 B73.3.1 (6/99)

Example: Multiple Indices

See Also

� ��

Business Views

The Object Librarian name for a business view can be a maximum of 10 characters andshould be formatted as follows: VzzzzzzzzA

V = business view

zzzzzzzz = should be the characters of the primary table

A = letter to designate which view. For example V0101A is the first view overthe table F0101; V0101B is the second view over the same table.

Provide up to a 60-character description for a business view. It should reflect theapplication description followed by the form type, such as Item Master Browse andItem Master Revisions.

Primary unique key fields should remain in the business view. Do not reorganize theprimary unique key fields.

There should be one business view for each table that includes all columns. Use thisbusiness view for the level 01 section in all reports upon which the file is based.


B73.3.1 (6/99) 4–19

Also, only one business view is allowed for each form type, except in the case of aheader/detail form. In this instance, two business views may be selected, one for theheader portion of the form and one for the detail portion of the form.

External Developer Considerations for Business Views

External development refers to creation of applications by developers outside of J.D.Edwards, such as Partners in Development and J.D. Edwards consultants that maycreate custom applications for a specific clients. You must use caution when naming abusiness view to prevent collisions between J.D. Edwards and non-J.D. Edwardsobjects. When creating a new business view over a standard J.D. Edwards table, formatthe business view name as follows: Vssss9999, where

V = business view

ssss = the system code applicable to the enterprise

9999 = a unique next number or character pattern unique within the enterprise

See Also

� ��

� ��

Joined Views

Format the name for joined views using the names of the two tables being joined,separated by a forward slash. Place the primary table first.

For example, where F4101 is the primary table in the join view between F4101 andF4102, use the following naming standard: F4101/F4102.

Applications

The Object Librarian name for an application can be a maximum of eight charactersformatted as follows: Pxxxxyyy

The name field accepts up to 10 characters. However, if you enter more than eightcharacters, the entry will be truncated.

P = application

xxxx = the system code

yyy = a next number, such as 001 and 002


4–20 B73.3.1 (6/99)

Provide up to a 60-character description. It should reflect the subject of the formswithin the application, such as Companies and Constants.

See Also

� ��

Forms

Forms Design automatically assigns a name using the following format: WzzzzzzzzA

W = form

zzzzzzzz = is the application name

A = the first form created in the application. It is usually, but not always, theentry point to the application; subsequent forms are assigned sequential letters,such as B for the second form, C for the third and so on.

For example, the application P0101 has two forms. The first form, Work withAddresses, is the entry point and is assigned the name, W0101A. The secondform, Address Book Revisions, is assigned the name W0101B.

� ��

Find/Browse - Work With followed by the subject of the application, such asWork With Companies, Work With Constants.

Fix/Inspect, Header/Detail and Headerless/Detail - should reflect the topic theycover, such as Supplier Information, Item Master Revisions, Purchase OrderEntry.

For lower level windows, identify the window that called the form by appendingthe calling form’s title, such as Enter Voucher - G/L Distribution.

When the title of a window includes a verb, use an active verb instead of anominalization, such as Work With Vouchers.

See Also

� ��

Form Interconnection Data Structures

Form interconnection data structures are automatically created by the OneWorld toolset using the key fields in the business view.


B73.3.1 (6/99) 4–21

You should change the data item name and description to describe the item beingpassed between forms.

Because Message forms do not have data structures, you must add at least the onemember.

Processing Options

A processing option includes the following four elements:

� �'%��(( $� %&) %$ ��)� ()'*�)*'�

� �� ) )"�

� �%##�$)

� �)� )�#

Processing Option Data Structure

The Object Librarian name for a data structure can be a maximum of 10 or 9 characters(depending on whether you begin with T) and may be formatted as follows:Txxxxxyyyy

T = processing option data structure

xxxxxyyyy = the program number for the application or report

For example, the data structure name for the P0101 application is T0101.

Tab Title

Use the following guidelines when you define a tab title for a processing option:

� �+% � ��'�+ �) $� )�� ) )"�( ,��'�+�' &%(( �"��

� �*)*'� &'%��(( $� %&) %$( �$� ��)� )�%(� &'%��(( $� %&) %$( )��) �'�

�*''�$)". *$�+� "��"� , )� )�� ,%'� /�� )�� $) '� )�� (

*$�+� "��"�� &"�� /�� $� )�� -)�$�� (�' &) %$ �%' )�� )��

�� ( $�"� &'%��(( $� %&) %$ ( $%) �+� "��"�� &"�� /�� $� )��

��)� )�# ��(�' &) %$�

� �� )�� - ()( %$". %$�� $� ( $%) (&" ) $)% #*") &"� )��(� �%' �-�#&"��

*(� �'%��(( $()�� %� �'%��(( �� '%��(( ��

� �� &&" ��) %$ $�#�� (*�� ( �� ",�.( �&&��'( $ )�� )�-) ,��$

'��'�$� $� +�'( %$( )��) �'� )% �� *(�� '( %$ )�� (�%*"� �",�.(

�� $ , )� )�� %##�$) �"%�!� /�$)�' )�� +�'( %$ )% �� *(�� %' ��

&'%�'�#� �� "��) �"�$!� �� , "" �� *(��


4–22 B73.3.1 (6/99)

� ��$�� # �� # !��

�� # �� $��

�� ! ��

� �� !�� "��

�� # �� !��

Display: Display Options, determines whether or not a field is displayedor which format of a form is displayed on entry

Defaults: Default Values, assigns a default value to a field

Edits: Data Edits, indicates whether or not a validation is to be performed

Process: Process Control, controls the process flow of the application

Application-specific tabs are:

Currency: Currency Options, contains processing options that arespecific to currency

Categories: Category Codes, indicates default category codes

Print : Print Options, controls the output of a report

Versions: Versions to Execute, contains versions of the application thatare called from this application

The following are standard application-specific tab titles. Group processingoptions under these tab titles when they apply to the type of processing specifiedin the tab.


Equipment Mgt - Equipment Management

Financials

Taxes: Tax Processing, contains processing options that are specific to taxes

Comment

When entering a comment for a processing option, use the following guidelines:

� �� # ��

��


B73.3.1 (6/99) 4–23

Note: When you have several processing options grouped together, you maychoose to number the processing options or the comments. Choose whateverworks best for the situation.

� � � ��!��)��!�� "�� !�� "�� (�!�� !��

��

� �� !�� !�%! (��"�� !� !�� !�� !��

��!�� "��

� � � � ��! �� $�� "�!�� !�� !� !��

!�� ! �� #� � � !�!�� !�� "� ��

�� !��

Data Item

When selecting a data item for a processing option, use the following guidelines:

� �� &� �� !�� !�� !� �!�� !� �� !�#��

� �� !�� !� �!�� !� !�� ! ��"�� &

$�!� !�� !�� #��! �"�� #�� $�!� !��

�� "�� '��!��&��

See Also

� �� !��

Event Rule Variables

ER variables are named similar to C variables and should be formatted as follows:xxx_yyzzzzzz_AAAA

xxx = Depending on the scope, OneWorld automatically assigns the prefix, suchas:

frm_ (form scope)

evt_ (event scope)

yy = Hungarian Notation for C variables:

c - Character

h - handle request

mn - Math Numeric

sz - String


4–24 B73.3.1 (6/99)

jd - Julian Date

id - Pointer

zzzzzz = programmer-supplied variable name; capitalize each word

AAAA = Data Dictionary alias (all upper case)

For example, a Branch/Plant event rule variable would be evt_szBranchPlant_MCU.Do not include any spaces.

Text Variables

OneWorld automatically assigns a name using the following format: TBzzzzzzzz

Business Function Event Rules (Named ER)

The source code for event rule business functions should be formatted as follows:Nxxxxyyy, such as N0400121.

N = event rule function


yyy = a next number (the numbering assignments follow current procedures inthe respective application groups.)

See Also

� ��

Business Functions

The source code for business functions should be formatted as follows: Bxxxxyyyy

B = business function


yyyy = a next number (the numbering assignments follow current procedures inthe respective application groups.)

The next numbering for business functions and named event rules should not be sharedto preserve the data structure or “D” names.


B73.3.1 (6/99) 4–25

See Also

� ��

� ��

� ��

Business Function Data Structures

The data structure for business function event rules and business functions should beformatted as follows: DxxxxyyyyA

D = data structure


yyyy = a next number (the numbering assignments follow current procedures inthe respective application groups.)

A = If there are multiple data structures for a function, place an alphabeticalcharacter, such as A, B, C, and so on, at the end of the data structure name.

The data element in the data structure should use Hungarian Notation, with the dataitem alias appended. For example, if a data structure element is using LANO for thealias, the name would be mnSite_LANO.

See Also

� ��

Workflow Data Structures

A workflow process can have two data structures. One represents the keys and theother the additional data for the workflow. Name the key and additional structure thesame, except for the last character. Begin both structures with WF, formatted asfollows: WFxxxxyyyA or WFxxxxyyyB

WF = workflow data structure


yyy = a next number (the numbering assignments follow current procedures inthe respective application groups.)

A = Designates the key data structure


4–26 B73.3.1 (6/99)

B = Designates the additional data structure

Media Objects

The Object Librarian name for a media object can be a maximum of eight charactersand is formatted as follows: GTxxxxyyA

GT = media object

xxxx = the file name excluding the letter F

yy = a next number

A = If there are multiple media objects for a file, place an alphabetical character,such as A, B, C, and so on at the end of the media object name.

Provide up to a 60-character description. It should reflect the subject of the mediaobject.

See Also

� ��

B73.3.1 (6/99) 4–27

Object Naming Conventions for Batch Applications

Object naming conventions ensure a consistent approach to designing batchapplications and make it easier to identify and locate the following:

� ��

� ��

� ��

� ��

� ��

� ��

Batch Applications

For batch applications, the name can be a maximum of eight characters and should beformatted as follows: Rxxyyyyy, such as R09800, R30440.

R = batch (report) application

xx = system code

yyyyy = follow the same naming convention as on the AS/400 to fill in these lastdigits.

The Function Use field should follow the same naming standards as the AS/400, suchas:

130-139 = Batch Processes

160-169 = Reports

Report Category Codes should follow the same standards as the Forms Designstandards.

See Also

� ��


4–28 B73.3.1 (6/99)

� ��

Table Conversions

For table conversions the name can be a maximum of 10 characters and should beformatted as follows: R89xxxxxyyy

R89 = conversion program


yyy = file (table) name

Provide up to a 60-character description for a table conversion. The description shouldread as follows: [File name] Conversion From yyy To zzz where:

yyy = the release that is being converted

zzz = the “to” release

See Also

� ��

Versions

Provide up to a 60-character description that indicates the purpose of the version. Thedescription indicates what the report does with a reference for setting processingoptions for that version.

XJDE versions are used for demo purposes and are typically batch applications.

When called from a menu, batch applications display the versions list to allowfor creation of production versions by the client.

During an installation, XJDE versions are considered as owned by J.D. Edwards.J.D. Edwards may be overwrite these versions.

ZJDE versions are used for default purposes and are typically interactive applicationsor called from another application. You usually attach these versions to a menu. Clientscan set these.

When called from a menu, interactive applications with a version are called witha blind execution based on predetermined processing option values.

Object Naming Conventions for Batch Applications

B73.3.1 (6/99) 4–29

Prior to release B73.3, during an installation, ZJDE versions are considered asowned by J.D. Edwards. Effective with release B73.3, ZJDE versions areconsidered as owned by the client and are not overwritten during an installation.

The installation replaces existing versions with the versions for Masters.

See Also

� ��

Section Names

Section names are automatically named by the tool set using a next number method,such as S1, S2, S3, and so on.

The Section Description should include the section type, such as “Batch Total Section,Payment Level Break Header Section.”

Sections should be logically arranged in report rendering.

Batch Event Rule Variables

An event rule variable name within a report should be formatted as follows::xxx_yyzzzzzz_AAAA

xxx = Depending on the scope, OneWorld automatically assigns the prefix, suchas:

evt_ (event scope)

rpt_ (report scope)

sec_ (section)

yy = Hungarian Notation for C variables:

c - character

mn - math numeric

sz - string

jd - Julian date

id - pointer

zzzzzz = programmer-supplied variable name; capitalize each word


4–30 B73.3.1 (6/99)

AAAA = Data Dictionary alias (all upper case)

For example, an Item event rule variable would be rpt_mnItemNumber_ITM. Do notinclude any spaces.

If report global variables are used, global variables are defined in a conditional groupsection that is never called. This section is named Defined Global Variables. Globalvariables are placed in the section in logical groupings. Use constants to comment onthe use of the global variables.

See Also

� ��

Purge Tables

Table Conversion-Batch Delete is the generic P00purge program in OneWorld thatremoves selected records from a table and stores the data in a backup file. To use thisbatch job you must first create a table conversion, rather than a new version, for thetable you want to purge.

The purge table name can be a maximum of eight characters and should be formatted asfollows: Pxxxxxxp

P = purge table

xxxxxxp = the file (table) name

Note: In WorldSoftware, the purge program removes selected records and stores themin a designated backup. For each file that is purged, a new version is created with thenew based-on table. OneWorld does not create a new version; rather you must create atable conversion.

B73.3.1 (6/99) 5–1

Hyper-Controls

In OneWorld application development, there are two types of hyper-controls: standardand nonstandard. Both types appear on a drop down menu.

Standard hyper-controls are menu options that are currently used in OneWorldapplications. Standard hyper-controls enforce the use of a single menu option wheretwo or more similar hyper-controls might exist, such as Account Ledger and A/L. Inthis example, the standard is Account Ledger. A standard hyper-control prevents a userfrom having to learn multiple commands to accomplish the same task. When you set upa standard hyper-control on a form, use the predetermined menu text and status bardescription.

Nonstandard hyper-controls are also menu options that you must set up on a form.However, you must define the menu text and status bar description.

This section contains information on:

� ��

� ��


5–2 B73.3.1 (6/99)

B73.3.1 (6/99) 5–3

Standard Hyper-Controls

Use the following assignments when you create a hyper-control. The purpose of thislist is to ensure consistency across all J. D. Edwards applications with respect tohyper-controls. If you want to include a new hyper-control in this list, you must contactyour application design standards committee representative.

To ensure that developers are complying with standard hyper-controls, a report isroutinely generated that identifies two or more hyper-controls that appear to be similarand therefore, might accommodate a single hyper-control.

Short Descriptionthat appears on the Drop Down

Menu

Long Descriptionthat appears in the Status Bar on the Bottom of

the Form

Access Key

A/R Accounts Receivable �

A/P Accounts Payable �

AAIs Automatic Accounting Instructions �

Account Ledger Account Ledger �

Account Master Account Master Sequence �

Additional Information Application Specific �

Address Book Address Book �

Approval Application Specific

Asset Master Asset Master �

Attachments Media Objects and Attachments �

Availability Application Specific

Bank Account Application Specific �

Bank Information Application Specific �

Batches Batches �

Bill of Material Bill of Material �

BOM Inquiry Bill of Material Inquiry �

Branch/Plant Branch Plant �

Budget Application Specific �

Budget Original Application Specific �

Budget Revisions Application Specific �

Business Units Business Units �


5–4 B73.3.1 (6/99)


Menu

Access KeyLong Descriptionthat appears in the Status Bar on the Bottom of

the Form

Cancel Line Cancel Line �

Catalogs Catalogs �

Category Codes Category Codes �

Category Codes 1-20 Category Codes �

Category Codes 21-30 Category Codes �

Change History Change History �

Check Price Check Price �

Clear Clear �

Co/By Products Co/By Products �

Columns Columns �

Components Components �

Controls Controls �

Copy Copy �

Cost Analysis Cost Analysis �

Cost Components Cost Components �

Cost Details Cost Details �

Cost Revisions Cost Revisions �

Credit Check Credit Check �

Customer Rules Customer Rules �

Customer Service Customer Service �

Date Patterns Date Patterns �

Dates Dates �

Delete Application Specific �

Delete All Application Specific �

Delivery Analysis Delivery Analysis �

Delivery Details Delivery Details �

Details Application Specific �

Disposition Disposition �

Document Selection Document Selection �

Document Type Exception Document Type Exception �

Drawing Drawing �

ECO Master ECO Master �

ECO Workbench ECO Workbench �

EDI Application Specific �

Edit Application Specific �


B73.3.1 (6/99) 5–5


Menu


the Form

Equipment Search Application Specific �

Factors Factors �

Features Features �

File File �

Find Find

Forecast Forecast �

Form Form exits �

Frozen Application Specific �

G/L Distribution Application Specific �

Generate Application Specific �

Help Application Specific �

Hours Application Specific �

Image Application Specific

Ingredients Application Specific

Intermediates Application Specific

Inventory Inventory

Item Availability Application Specific �

Item Branch Item Branch �

Item Cost Item Cost �

Item Detail Item Detail �

Item Inquiry Item Inquiry

Item Ledger Item Ledger �

Item Master Item Master �

Item Notes Item Notes

Item Revisions Item Revisions �

Item Search Item Search �

Job Revisions Application Specific

Job Revisions by Co Application Specific �

Job Status Inquiry Job Status Inquiry

Journal Entries Journal Entries

Location Location �

Location Revisions Location Revisions �

Location Search Location Search �

Locators Component Locators �

Lot Master Application Specific �


5–6 B73.3.1 (6/99)


Menu


the Form

Mfg Data Application Specific �

Multi-Level Application Specific

Open Application Specific

Order Application Specific

Parts List Application Specific �

Payments Application Specific �

Pegging Application Specific �

Pending Application Specific �

PO Detail Browse PO Detail Browse �

PO Detail Revision PO Detail Revision

PO Entry PO Entry �

PO Inquiry PO Inquiry �

PO Summary PO Summary �

Print Application Specific �

Purchase Ledger Purchase Ledger �

Quality Application Specific �

Quantity Application Specific �

Rates Application Specific

Receipt Application Specific

Related Application Specific

Remove Application Specific

Reports Application Specific

Revisions Application Specific �

Routing Application Specific

Row Row Exits

Scheduling Workbench Application Specific �

Select Select �

Ship Ship to Customer �

Shortage Application Specific �

Simulated Application Specific �

Single Level Application Specific �

SO Detail Revisions SO Detail Revisions �

SO Header Revisions SO Header Revisions �

Sold Sold to Customer

Supplier Supplier Master �


B73.3.1 (6/99) 5–7


Menu


the Form

Supply/Demand Supply/Demand �

Tax Application Specific �

Time Series Application Specific �

Update Application Specific �

Update Redisplay Update with Redisplay �

View Application Specific �

Who’s who Who’s who �

WO Entry Application Specific �

Workbench Application Specific �

See Also

� ��


5–8 B73.3.1 (6/99)

B73.3.1 (6/99) 5–9

Nonstandard Hyper-Controls

Use the following guidelines for nonstandard hyper-controls:

� ��

� ��

� ��

� ��

� ��

��


5–10 B73.3.1 (6/99)

B73.3.1 (6/99) 6–1

Access Keys

An access key executes a button, menu title, or menu item using a combination of theAlt key and another key that is unique to the particular command. Access key standardshave already been defined in the Hyper-controls section of this guide. When you definean access key, you must check this list first to ensure that you are assigning the standardaccess key.

This section discusses access key standards for:

� ��

� � ��

� � ��

� ��


6–2 B73.3.1 (6/99)

B73.3.1 (6/99) 6–3

Standard Buttons

Depending on the form type that you create, standard buttons automatically appear onthe toolbar. There are seven standard toolbar buttons that may appear: OK, Select, Find,Add, Copy, Delete, and Close/Cancel. The following list presents standard buttons andcorresponding access keys, in the standard order of appearance on the toolbar.

OK alt + O

Select alt + S

Find alt + I

Add alt + A

Copy alt + Y

Delete alt + D

Close or Cancel alt + C


6–4 B73.3.1 (6/99)

B73.3.1 (6/99) 6–5

Menu Titles

Menu titles are the options that appear on the menu bar across the top of an applicationwindow. A menu title displays a list of menu items, or commands. For example, theFile menu title might contain several menu items that can be executed.

There are two types of menu titles: system and user.

System Menu Titles

There are five system-defined menu titles that appear on the menu bar within anapplication. The following list presents the standard menu title and correspondingaccess keys, in the order of appearance;

File alt + F

Edit alt + E

Preferences alt + P

Tools alt + T

Help alt + H

User Menu Titles

In addition to system menu titles, you can use system menu titles within an application.The following list presents system menu titles and the corresponding access keys foreach:

Form Form Exits, alt + M

Row Row Exits, alt + R

Reports Reports, alt + O


6–6 B73.3.1 (6/99)

View View, alt + V

See Also

� ��

B73.3.1 (6/99) 6–7

Menu Items

A menu item is a command that appears within a list for a menu title. For example,Attachments is a menu item on the Form menu title. As with standard buttons andmenu titles, a menu item can have an access key.

A menu item might contain additional menu items. If so, an ellipsis is appended to themenu item. Adhere to the Windows standard in the use of the ellipsis (...) in menu itemlabels:

‘‘If the menu item is a command that requires additional information to complete its

execution, follow the command with an ellipsis (...). The ellipsis informs the user that

the information is incomplete.”

Windows Interface Guidelines for Software Design, Microsoft Press 1995

Menu Item Title, Long Description, and Access Keys for MenuItems

When you set up a menu item on a form, you define the menu title, long description,and access keys.

See the chapter, Standard Hyper-Controls, for a complete listing of predeterminedmenu item titles, long descriptions, and access keys.

How to Select an Access Key for User-Defined Menu Items

Use the following guidelines to select an access key for user-defined menu items.

� ��

��

� ��

��

� � � ��

��

��

� � ��

��

��


6–8 B73.3.1 (6/99)

See Also

� ��

B73.3.1 (6/99) 6–9

Access Keys For Specific J.D. Edwards Applications

This chapter provides access keys defined for the following J.D. Edwards applications:

� ��

Human Resources

For Human Resources applications, refer to the following list when assigning accesskeys for the corresponding commands:

Attachments alt + A

UD date 1-10 alt + D

UD category 1-10 alt + C

Nat’l/Fiscal Data alt + F

Employee DBA Instruction alt + I

Job Information alt+ J

Eligibility/NDT alt + L

Basic Compensation alt + M

Organizational Assg alt + N

Organizational Structure alt + O

Employee alt + P

Labor Distribution alt + R

Personal alt + S


6–10 B73.3.1 (6/99)

Supp Data Entry alt + T

Supp Data Inquiry alt + U

Future Value alt + V

Payroll alt + Y

B73.3.1 (6/99) 7–1

Event Rules Checklist

The event rules checklist provides design standards regarding the use of event rules inapplications.

The following checklists are presented:

� � ��

� ��


7–2 B73.3.1 (6/99)

B73.3.1 (6/99) 7–3

All Event Rules Checklist

This checklist contains standards that apply to all event rules.

� �(*$ �#�%�+ ��!#' /(*$ #�%�+ /#," ,"� �%#�+� (%%(/�� 1 ,"� '�&�� '�

�/ �� +-�" �+ ��"(*, �,�& �-&��* �/ ��

� �%�! �'1 %�!+ ,"�, �*� )�++�� $ *(& ,"� �-+#'�++ -'�,#(' &-+,

��), � '-&�*#� .�%-� *�,"�* ,"�' � �"�*��,�*� ��"#+ #+ &(*� ��),��%�

#',�*'�,#('�%%1�� (* �0�&)%�� #' ,"� ��+� ( ,*-�� %+�� -+� (* ,*-� �'� �

(* �%+� *�,"�* ,"�' � (* � �'� � (* ��

� (&&�', �%�� %�'$ %#'� �� (*� �'� � ,�* ,"� �(&&�',� ��)�*�,�

%(!#��% +��,#('+ ( �.�', *-%�+ /#," � ��+"�� %#'��

� � ,"� /(*$ #�%� #+ � !*#� �(%-&'� -+� � !*#� .�*#��%��

� �( '(, -+� � "�*�4�(�� ,�0, +,*#'!� (* �0�&)%� #' �� ,( %(�� #�%� (*

.�*#��%�� +� � ,�0, .�*#��%� #'+,��

� �*(& �' #',�*��,#.� �))%#��,#('� )*�� ,"� �*(!*�& �� -+�� ,(

-)��,� ,"� ��,��+� /#," ,"� %�,,�* �� +-�" �+ �� (* �' ��*�++ �(($

�.�', *-%��

� �*(& � ��,�" �))%#��,#('� -)��,� ,"� )*(!*�& �� /#," �00000�

� �%/�1+ -+� ,"� �#*��,#('�% �**(/+ ,( �,,��" �-+#'�++ -'�,#('+� � �

)�*�&�,�* #+ '(, -+�� ,"�' -+� ,"� 3 +1&�(%� �"#+ +1&�(% #��',# #�+ �

)�*�&�,�* ,"�, #+ '(, -+�� 1 ,"� �))%#��,#(' ��%%#'! ,"� �-+#'�++ -'�,#('�

��#,#('�%%1� #, +�*.�+ �+ �(�-&�',�,#(' ,( (,"�* *��*+ ( ,"� �(��

� �"�' �"��$#'! )*(��++#'! (),#('+ (* (*& #',�*�(''��,#('+ (* � .�%-�

�� 1(- &-+, �%+( �"��$ (* � .�%-� ��

� �'�%-�� *�.#+#('+ %(! �, ,"� ,() ( �#�%(!�+�'#,#�%#2�� (* ,"� �',*1 )(#',

(*& (* #',�*��,#.� �))%#��,#('+ �'� �'#,#�%#2��,#(' (* ��,�"

�))%#��,#('+� �"� *�.#+#('+ %(! �(',�#'+ ,"� ��,�� -+�*� �'� �� '-&��* (

&(�# #��,#('+ &�� ,( ,"� �))%#��,#('�

See Also

� �� #' ,"� ��

� �� #' ,"� ��


7–4 B73.3.1 (6/99)

� ��

� ��

B73.3.1 (6/99) 7–5

Table I/O Checklist

Use this checklist for standards on creating event rules that use table I/O.

� �� #��"�� "�� "�� "� �� "�� #!" �� #��"��

� �� #!" �� $��" #�� #!��!!

�#��"�� " �� "�' � �� "��

� �!� "�� $��" �#��! ��!�� !�� " ��$��!� ��# �#!" � ��"�

� �#!��!! �#��"�� "�� "� � �$�� "� �" ��$� ��"� � ��

"�� "��

� �$�� #��"�� "�� %�"� � �#!��!! �#��"�� " $� "��

"�� "�� "�� #!��!! �#��"�� !!�! �#�"�� "��!� ��" "��

"�� "� "�� "��! %�"�� !�� $� "�� ! "�� #!��!! �#��"��

� �#!��!! �#��"�� !��#�� "�� #��"��! "� �" ��$� ��"� � ��

�"�� $� "��!�

� � � "�� ! � ��!"� �#!��!! �#��"�� ! "� "��" "�� #!" ��

"� �#�� "�� !"� �#!��!! �#��"��

� �� #!�� #�"�� !� �" ��$� �� $�� #��"�� ! #!��

�#!��!! �#��"�� &�� #��"�� ! #!�� #�"��

��!� #!� � �#!��!! �#��"�� "� �" ��$� "�� #��"�� $��#��

� �!� "�� $��" �#��! ��!�� "� #��"� � �" ��$� ��"� � ��

%� � ��

� �!� � ��"� �� "�� !"�� ! ��


7–6 B73.3.1 (6/99)

B73.3.1 (6/99) 8–1

Performance Considerations

This section contains guidelines for optimal performance for the following:

� ��

� ��

� ��


8–2 B73.3.1 (6/99)

B73.3.1 (6/99) 8–3

Performance Considerations for All Forms

This checklist contains standards for increased performance across all form types.

� ��% %�� &��# � � �&��$ �� %�� #�� % %�� &� #�"&�#�� * %��

�!!��%� ��

� ��! %�� &��# � � �&��$ �� %�� &$��$$ '��( % %�� &�

#�"&�#�� * %�� !!��%� ��

� ��% %�� &��# � � #� � �%# �$� (��%��# �� # '�$�� % %��

��&� #�"&�#�� * %�� !!��%� ��

� �'��% #&�� '�#��$ $� &�� &$�� $ ( #� ��$ �� !�� #�

� �%# �$�

� ��$�� %� ��%� ��#* �&��%� �$ � � #� �� #�� %# �$ %��% �#� � %

#�"&�#�� $&�� $ ��%$ �� &�% '��&�$� (��%��# �� # '�$��

� ��! %�� &�% � ��!&% �� &%!&% !�#� #�� # �� #�� # ( % %��

��&� #�"&�#�� # %�� !!��%� �� # �)��!�� ' �� $$ ��%��

��$�#�!%� �$ (��#�'�# ! $$��

� �$� %�� % ! # ��$$�� $*$%�� &��%� � (��'�# ��$�� % $��! %��

!# ��$$�� &��$$�#* �'��% #&��$�

� � �$��# %�� $�� # %�� $% ��% ��%� � � %��! #�#* ��%�

$% #�� '�� % %�� %�� $&�� $ �� '�#$&$ �� $% '�#$&$ ( #�

��$�

� �$� �� % $*$%�� &��%� �$ % ��% �� $!��* �%%��%$ ��$%��

� �� &% ��%�� % �&��%� ��%* �� !�#� #�� $

��$�� &� % � �� %� ��% � � #�� $ �� ($ * & %

��%� %�� $%�! % �� # %�� )�$%�� %%��% $ %��% �

��%��! �� $!��*�� * & &$� �&% ��%�� %

�&��%� ��%*� %��$ $%�! �� % �� %�� (�� (�*$ �� !�#� #��


8–4 B73.3.1 (6/99)

B73.3.1 (6/99) 8–5

Performance Considerations for Find/Browse Forms

This checklist contains standards for increased performance on find/browse forms.

� # "#( )'� �� ''��"!�"(' ��)'� (��, "��(�*� , �!$��(

$�&�#&!�"��

� �� '#&( #&��& #" (�� &�� '�#) � !�(�� #(� �" �"��+ ��"�� "

�"��#& � �"� � #�� "�� #" (�� (��& $�&(�� , #&

�#!$ �(� ,� �� #�� "� �"��+ !)'( �#"(��" �( ��'( � �� ' (��( �&�

�" (�� &�� '#&(� �"� (�� ' '� ��(�� #& (�� &�� '#&( !)'( �� " (��

'�!� '�%)�"�� ' (�� #�� "��+ �� '� ��&� !�, �� (�#"� �� '

�" (�� "��+ #& #�� (��( �&� "#( �"� )�� " (�� &�� '#&(� �#& �+�!$ ��

�" � $�&(�� !�(�� (�� &�� '#&( ��" �� "� (�� #�� "�

�"��+ ��" �"� )��

See Also

� � �� " (��


8–6 B73.3.1 (6/99)

B73.3.1 (6/99) 8–7

Performance Considerations for Header Detail andHeaderless Detail Forms

This checklist contains standards for increased performance on header detail andheaderless detail forms.

� �� '#&( #&��& #" �&�� '�#) � !�(�� #(� �" �"��, ��"�� " �"��#& �

�"� � #�� "�� #" (�� (��& $�&(�� - #& �#!$ �(� -� ��

#�� "� �"��, !)'( �#"(��" �( ��'( � �� ' (��( �&� �" (�� &�� '#&(�

�"� (�� ' '� ��(�� #& (�� &�� '#&( !)'( �� " (�� '�!� '�%)�"�� '

(�� #�� "��, �� '� ��&� !�- �� (�#"� �� ' �" (�� "��, #&

#�� (��( �&� "#( �"� )�� " (�� &�� '#&(� �#& �,�!$ �� " � $�&(��

!�(�� (�� &�� '#&( ��" �� "� (�� #�� "� �"��, ��"

�"� )��

� � �# )!"' �" (�� )'�"�'' *��+ !)'( �� " (�� &�� +��(��& ��" #&

*�'�� (� *� )�' �#& �# )!"' (��( �&� �" (�� )'�"�'' *��+ �)( "#( �"

(�� &�� +� �� (�� +��" �" )$��(� �' $�&�#&!��

See Also

� ��


8–8 B73.3.1 (6/99)

B73.3.1 (6/99) 9–1

Use of Text Strings to Name Fields

A noun string is a series of nouns. Noun strings are confusing, because the user ortranslator cannot tell which noun is modifying another noun. Avoid noun strings eitherby:

� ��

� ��

For example, depending on the intent, consider rewording “Install System Code” to:

� ��

� ��

� ��

� ��

� ��

� ��

The above example is particularly confusing because both install and code could beverbs. This phrase could be one very long noun, a request for action, or an actionalready taken.

Translators often require more information to effectively translate text than Englishreaders. The English language is flexible. To effectively translate, a translator mustknow who or what is performing an action.

Translators also face gender issues. Depending on how the words are strung together, aword may be feminine or masculine.

If you are in doubt about how to separate a long string of nouns, ask yourself if one ofthe nouns is a verb. If so, then insert a verb helper like “to”, “the”, “of”, “for”, orchange the tense of the verb as in “Installed System Code.” Consider shortening a longnoun string. Ask yourself if every word is really necessary. For the noun string InstallSystem Code, either Install Code or System Code is easier to translate.


9–2 B73.3.1 (6/99)

A list of approved text strings, along with a brief explanation of each follows. To usetext strings effectively when you name fields, familiarize yourself with the following:

� ��

� ��

B73.3.1 (6/99) 9–3

Text Strings Used in J.D. Edwards Software

The text strings listed below are currently used within J.D. Edwards software. Thesestrings present translation challenges because the translator must first determinewhether a word is a noun or a verb. Consider the field name, “Install System.” Is theword “install” a verb or a noun? In this instance, “install system” is a compound nounstring. For many developers, this is understood because they are familiar with the J.D.Edwards use of the text string, “install system.” For a translator or international user, itis unclear.

The following are examples of text strings that are currently used in J.D. Edwardssoftware:

Field Name Question asked by a translator

Log File Name Does this mean to log the filename or the name of the logfile?

Setup Function Does this mean to set up the function or the function forthe setup?

Setup Menu Does this mean to set up the menu or the menucontaining setup options?

Install Data Does this mean to install data or data referring to theinstallation?

Install Data Sources Does this mean to install data sources or data sourcesreferring to the installation?

Install Environments Does this mean to install environments or environmentsreferring to the installation?

Install Hosts Does this mean to install hosts or hosts referring to theinstallation?

Add Following Add the word, “following?” or add after?


9–4 B73.3.1 (6/99)

LineNumber Why are the words attached? Is this a parameter or doesit mean the number of lines?

B73.3.1 (6/99) 9–5

Approved Text Strings

The following is a list of approved, standard text strings. Refer to this list as you namefields for better understanding, easier translation, and consistent usage across J.D.Edwards software.

Text String Usage

Data Structure Data structure is a noun string. Data structure means thestructure of the data. There are different types of structures inthe OneWorld tool set. Any text that precedes the text “datastructure” refers to the type of the data structure and functionsas an adjective.

Examples:

� ��

� ��

� ��

� ��

� ��

[noun] Design The OneWorld tool set is made up of many design tools, each adifferent type of tool for creating a specific object type. Forexample, the Table Design tool creates a table.

Examples:

� ��

� ��

� ��

� ��

� ��

� ��

� � ��


9–6 B73.3.1 (6/99)

[noun or verb] Event There are numerous events or activities in OneWorld. The textthat precedes the type of an event can be a string of nouns,verbs, or combination of nouns and verbs. In any case, the textstring preceding the word, event, is an adjective and describesthe purpose of the event.

Examples:

� ��

� ��

High-level Default Trigger High-level is an adjective for the noun string “default trigger.”A high-level default trigger is criteria that is automaticallyevaluated for data in a field.

Install [noun] Install is an adjective, not a verb.

Examples:

� ��

� ��

� ��

� ��

� ��

Line Number The number of the line.

Menu Revisions Menu Revisions is a noun string. This OneWorld toolmaintains interactive and batch application menus.

Object Librarian Object Librarian is a noun string. This OneWorld toolmaintains objects or building blocks that make up applications.

Object Type Object type is a noun string. Object type means the type ofobject.

Process Function A function of the process. On a form, process function is anoun string, where process describes the function.

Process Usage A usage of the process. On a form, process usage is a nounstring, where process describes the usage.

Set Up The space between the words, set and up, indicates this is averb string.

Approved Text Strings

B73.3.1 (6/99) 9–7

Setup [noun] Setup is an adjective, not a verb.

Examples:

� ��

� ��


9–8 B73.3.1 (6/99)

Appendices


B73.3.1 (6/99)9–10

B73.3.1 (6/99) A–1

Appendix A - Acronyms and Abbreviations

This chapter contains acronyms and abbreviations you can use in OneWorldapplications. You must refer to this list before using an acronym or abbreviation. If aspecific acronym or abbreviation is not in this list, you must contact your applicationdevelopment manager to add it.

The list also includes the space required for translation of double-byte and single-bytelanguages. Where possible, enlarge the fields to accommodate translation.

In many languages, there is no equivalent for an English acronym or abbreviation.Where there is no equivalent for an English acronym or abbreviation, the description istranslated instead. Consider the following French and German translations of theacronym, A/P, for accounts payable:

��

�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�� !�� !��

Double-byte languages, such as Chinese and Japanese, commonly require the mostspace because the Chinese and Japanese languages do not have acronyms andabbreviations.

Several acronyms or abbreviations contain the “&” symbol. If you use an acronym orabbreviation with the & symbol when defining a form control or menu, you must entertwo && rather than a single &. Otherwise the runtime engine interprets the & as anunderscore ( _ ).

��

��

��

��

��

��

��

��

��

��

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ��!� � ��#�� ÑÑÑÑÑÑ

ÑÑÑÑÑÑ ÑÑÑÑÑÑ

ÑÑÑÑÑÑ��


��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��!� � ��"��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��



�� !� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99)A–2

��

��

��

��

��

��

��

��

��

��

ÑÑÑÑÑÑÑÑÑÑÑÑ

� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

.-(&�-"� ��(.'-"' �',-+.�-"('ÑÑÑÑÑÑÑÑÑÑÑÑ

� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��"+&�-"/� �-"(' �%�''"' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��


� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

$-"��(%� ��0��'� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

'( -+�',%�-"('ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�-"/"-13��,�� (,-"' ÑÑÑÑÑÑÑÑÑÑÑÑ




))%"��-"(' �"'�+1 �'-�+�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�-"/"-13��,�� '� �&�'- ÑÑÑÑÑÑÑÑÑÑÑÑ

�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�#.,-�� .++�'- ��+'"' ,ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




.-(&�-�� %��+"' �(.,� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�-.�% �('-+"�.-"(' ��+��'-� � ÑÑÑÑÑÑÑÑÑÑÑÑ




/�+� � �('-+"�.-"(' ��+��'-� �ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




��%�+�-�� (,- ��(/�+1 �1,-�&ÑÑÑÑÑÑÑÑÑÑÑÑ


ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��"��'-�% ��-! �'� �",&�&3

��+&�'-


��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



&�+"��', 0"-! �",��"%"-"�, �- ÑÑÑÑÑÑÑÑÑÑÑÑ



ADDLÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

AdditionalÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

10ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

3



�-.�% ��++�% ��+��'-� � ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




,,�-, ��)+��"�-"(' ��' �ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



+�!"-��-.+�� ' "'��+"' � �'�

�(',-+.�-"('





�/�'�� (+��,-"' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



.-!(+"2�-"(' �(+ ��*.�,- ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




/�+� � �+�" !- ��-� ,,�,,&�'-ÑÑÑÑÑÑÑÑÑÑÑÑ




/�"%��%� �(+ ��%� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




$-"�' �,�%%,�!��- ��+&�'1� ÑÑÑÑÑÑÑÑÑÑÑÑ

'( -+�',%�-"('ÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�



�#.,-�� +(,, �'�(&�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99) A–3

��

��

��

��

��

��

��

��

��

��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�651 �(0(3$5( �$45(3 ÑÑÑÑÑÑ

ÑÑÑÑÑÑ� ÑÑÑÑÑÑ

ÑÑÑÑÑÑ�

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��"�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�651/$5(' �6,'(' "(+,&.( �:4;

5(/



�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�/(3,&$0 �045,565( 1) �3&+,5(&54 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�


��#ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�'7$0&(' �05(3$&5,7( �9(&65,7(

��4 23123,(5$3: 7(34,10 1)

!��#�


�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�


�� 13 $-$ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�.41 �0180 �4ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�/5 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�/1605 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�



�.5(30$5,7( �,0,/6/ $9 ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�''3(44 �6/%(3ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�/(3,&$0 �$5,10$. �5$0'$3'4

�045,565(ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�7(3$*( �65*1,0* �6$.,5: �(7(. ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�&&16054 �$:$%.( ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�*3,&6.563$. �31'6&54� �3124ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�'7$0&(' �3,&( �0$.:4,4 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�22.,&$5,10 �31*3$/ �3,7(3 ÑÑÑÑÑÑÑÑÑÑÑÑ

� ÑÑÑÑÑÑÑÑÑÑÑÑ

�



�,3 �14,5,10 �0',&$513 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�/(3,&$0 �(531.(6/ �045,565( ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�22.,&$5,10 �31*3$/ �05(3)$&(ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�/(3,&$0 �31'6&5,10 $0' �07(0;

513: �10531. �1&,(5:� �0&�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�006$. �(3&(05$*( �$5(ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�&&(25$%.( �6$.,5: �(7(. ÑÑÑÑÑÑ


ÑÑÑÑÑÑ



�&&16054 �(&(,7$%.(ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99)A–4

��

��

��

��

��

��

��

��

��

��



",$�/'./,�' � ,0$� - ÑÑÑÑÑÑÑÑÑÑÑÑ


�



++'$��.$*) �2-. (ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



/.*(�.$� �.*,�" �� .,$ 0�' �2-3

. (



��


� �ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

- �**) - �*--$�' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



( ,$��) �.�)��,� �*� !*, �)3

!*,(�.$*) �). ,�#�)"



�



++'$��.$*) �+ �$!$� �)-.,/�.$*)-ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



++'$��.$*) �+ �$!$� �)-.,/( ). ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�0�)� � �#$+ �*.$� ÑÑÑÑÑÑÑÑÑÑÑÑ


�



/1$'$�,2 �.*,�" �**' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



( ,$��) �*�$ .2 !*, � -.$)" �)�

��. ,$�'-ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



/.*(�. � � '' , ��#$) ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



-- (�'2 .* �,� , ÑÑÑÑÑÑÑÑÑÑÑÑ




--*�$�. � � 1. �/.+/. ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



0�$'��' .* �,*($- ÑÑÑÑÑÑÑÑÑÑÑÑ


�



0�$'��' .* �,*($- �)��%/-. �ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



( ,$��) ��)& , ��. ��# �/' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�./�' �)$.- ÑÑÑÑÑÑÑÑÑÑÑÑ


�


0' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

0�$'��$'$.2 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�- ). �$.#*/. � �0 *,

�- ). �$.#*/. �!!$�$�' � �0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��,, '- + , ��2 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�$'' *! ��$)" ÑÑÑÑÑÑÑÑÑÑÑÑ


�



� "$))$)" 0�$'��' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99) A–5

��

��

��

��

��

��

��

��

��

��


� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�.� �- &(.'- ÑÑÑÑÑÑ

ÑÑÑÑÑÑ�� ÑÑÑÑÑÑ

ÑÑÑÑÑÑ�


� ��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��'$ .-(&�-�� %��+"' �1,-�&ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


� �� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�.,"'�,, ))%"��-"(' �(�-0�+�

�'-+(�.�-"(' �%�,,



�



�� "''"' /�"%��%� �'��#.,-��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�"%%"' �('-+(% ��'-"�"��-"(' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��% "�' �+�'�, ÑÑÑÑÑÑÑÑÑÑÑÑ

�� ÑÑÑÑÑÑÑÑÑÑÑÑ

�



�+��$2�/�'- �("'- ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ��++�%, (� �.�% �"% �*."/�%�'- ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�"%%"(' �',-+.�-"(', )�+ ��('�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�%$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�%�'$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�"'�+1 ��+ � ��#��- ÑÑÑÑÑÑÑÑÑÑÑÑ


�


�' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�"%%"(' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ��$ �+��+ ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�."%�"' �)�+�-"' �(,-,ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�"%% (� ��"' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�"%% (� ��-�+"�%,ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.,"'�,, ��+-'�+ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�"-, )�+ �'�! ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�"-, )�+ ��('�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�.%$ �+(�.�- �+�',��-"(' ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�


�+ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�+�'�!ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�+' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�+�'�! ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�+'��%- ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�+�'�!��%�'- ÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99)A–6

��

��

��

��

��

��

��

��

��

��



(,,(& � �$& ', �'� ��, * ÑÑÑÑÑÑÑÑÑÑÑÑ




*$,$+# �# *&�% �'$,ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



'1 ' � �(%- ' � �'� �0% ' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



-�" , �'$,+ ÑÑÑÑÑÑÑÑÑÑÑÑ


�



-+$' ++ �'$, ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


� � � ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�(+, �'� �* $"#, ÑÑÑÑÑÑÑÑÑÑÑÑ


��


�� (* ��(ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��* (!ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




��+# � � $),+ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�%$ ',�� *. * ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�(',*��, ��&$'$+,*�,$(' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�(&)-, * �++$+, � � +$"' ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�(&&(' �))%$��,$('+ �'.$*('2

& ',



�



�(&)-, *2�$� � �'"$' *$'" ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�(&)-, *2�$� � �'+) �,$(' �'�

� +,


�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�



�(&&(' �* � ��$', '�'� ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�(&)-, *2�$� � ��'-!��,-*$'"ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�(&)-, * �++$+, � �*("*�&&$'"ÑÑÑÑÑÑÑÑÑÑÑÑ


�



��, "(*0ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�(&)-, *2�$� � �*(� ++ �%�'2

'$'"





�(&)-, *2�$� � �(!,/�* �'"$2

' *$'"





�-&-%�,$. �.�$%��% ,( �*(&$+ ÑÑÑÑÑÑÑÑÑÑÑÑ




��+# !(* � %$. *0ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


B73.3.1 (6/99) A–7

��

��

��

��

��

��

��

��

��

��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ��,# ��,$, �(&2 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�)'*.- + ��, � �+�$($("ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�),- � (- + ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�2�& �).(- �)� ÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�)(,.&-�-$/ �)''$-- !)+ �(3

- +(�-$)(�& � & *#)(2 �(� � & "3

+�*#2


� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�!!$� � &� �)(,-+.�-$)( �. �. 3

� �


() -+�(,&�-$)(ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�



�)� ÑÑÑÑÑÑÑÑÑÑÑÑ




� +-$!$��- )! � *),$-ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


��3�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�)'*��- �$,�3� �� (&2 � ')+2ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�#$ ! �1 �.-$/ �!!$� +ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�#$ ! �$(�(�$�& �!!$� + ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� +-$!$ � �, � � &&)0 $( �+)�.�3

-$)( �(� �(/ (-)+2 ��(�" ' (-ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�#" ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�#�(" ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�#% ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�# �% ÑÑÑÑÑÑÑÑÑÑÑÑ




�)'*.- +3�(- "+�- � �$,-+$�.-$)( ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�)'*�"($ ��+�(� � ÑÑÑÑÑÑ


ÑÑÑÑÑÑ



� (-+�& �(!)+'�-$)( �$& ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�)'*.- +3�(- "+�- � ��1 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�),-� �(,.+�(� � �(� �+ $"#- ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�)'*.- +3�(- "+�- � ��(.!��-.+3

$("



�



�.,-)' + �(!)+'�-$)( �2,- 'ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99)A–8

��

��

��

��

��

��

��

��

��

��



&$'#�. �%)*(+�* &% ��* &$'+*1

�(ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



&%*(&# ��%�+�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��%�� %��$�%* ÑÑÑÑÑÑÑÑÑÑÑÑ


�



&((��* ,� �� %*�%�%��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



&$'+*�( 0�� %*�%�%�� %1

��$�%* �/)*�$)



�


CmpÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

CompensationÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



&)* ��%��$�%* �/)*�$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



&$'+*�( �+$�( � &%*(&# ÑÑÑÑÑÑÑÑÑÑÑÑ


�


& ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

&$'�%/ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�(* � ��*� &� �%�#/) ) ÑÑÑÑÑÑÑÑÑÑÑÑ


�



&%)&# ��*�� $% �+) ��&%� # 1

�* &% ��*



�



&$$&% �+) %�)) �( �%*�� %1

�+��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�)� &% ��# ,�(/ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



&%*� %�( &% � �� #(&�� #�*��( ÑÑÑÑÑÑÑÑÑÑÑÑ


�



&)* &� �&&�) �&#� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



&)*1&�1� , %� ��!+)*$�%* ÑÑÑÑÑÑÑÑÑÑÑÑ


�



&)*1&�1� , %� �##&-�%��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



&$'+*�( �+*'+* *& ��)�( � )" ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



&$'+*�( �+*'+* *& � �(&�&($ ÑÑÑÑÑÑÑÑÑÑÑÑ


�



+)*&$�( �( �%*�� %+��*+( %�

��%��$�%* �/)*�$)



�



� �� '�(�* %� �� (ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



B73.3.1 (6/99) A–9

��

��

��

��

��

��

��

��

��

��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�+/0 +# �1�(&05 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�+((&/&+* �",�&.ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�+." ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�%" "*0.�( �*! #+1*!�0&+*�( /5/6

0")/ +# �� /+#03�." ��&*�* &�(/�




�+.,ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�+.,+.�0&+*ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�+.,+.�0&+* #+. �,"* �5/0")/ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�+*#&$1.�0+. �.+ "//&*$ ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�".0&#&"! �1�(& +1*0�*0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


�� +. ,& ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�%�.� 0"./ ,". �* % ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�+*/1)". �.& " �*!"4ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�+*0&*1+1/ �.+ "// �),.+2")"*0ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�".0&#&"! &* �.+!1 0&+* �*! �*6

2"*0+.5 ��*�$")"*0ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�.&0& �( ��0% �"0%+! ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�"*0.�( �.+ "//&*$ �*&0ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� +. �. ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�."!&0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�� ."!&0 �",+.0&*$

$"* 5�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��,� &05 �"-1&.")"*0/ �(�**&*$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�+*#"."* " �++) �&(+0 ÑÑÑÑÑÑÑÑÑÑÑÑ


�



��0%+!& ��5 �1�" ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�(&"*0��".2". ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�(&"*0 �".2& " �++.!&*�0+.ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�1/0+)". �".2& " �",."/"*0�0&2" ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�1/0+)". �".2& " �+.'/0�0&+* ÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99)A–10

��

��

��

��

��

��

��

��

��

��

ÑÑÑÑÑÑÑÑÑÑÑÑ�� ÑÑÑÑÑÑÑÑÑÑÑ

ÑÑÑÑÑÑÑÑÑÑÑ�2+2*!1)3% �/!2+! �)0-/$%/ ÑÑÑÑÑÑ

ÑÑÑÑÑÑ� ÑÑÑÑÑÑÑ

ÑÑÑÑÑÑÑ



�-+.21%/71-7�%*%.(-,% �,1%'/!7

1)-,




ÑÑÑÑÑÑÑÑÑÑÑ�()%& �%#(,)#!* �&&)#%/ ÑÑÑÑÑÑ

ÑÑÑÑÑÑ�� ÑÑÑÑÑÑÑ

ÑÑÑÑÑÑÑ


�� -/ �1/*ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�-,1/-*ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�%,12/6 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�-++-, �0%/ �##%00 ÑÑÑÑÑÑÑÑÑÑÑÑ



�2+ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�2+2*!1)3% �.$!1% ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


ÑÑÑÑÑÑÑÑÑÑÑ�2")# �%1%/ ÑÑÑÑÑÑ


ÑÑÑÑÑÑÑ


CURÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Currency CodeÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


13


�2// ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�2//%,1 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�-01��-*2+%��/-&)1 ÑÑÑÑÑÑÑÑÑÑÑÑ



� � � ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�2, !,$ �/!$01/%%1 ��/%$)1 �%7

.-/1),' �'%,#6�



�



�!6ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�)/%#1 �##%00 �1-/!'% �%3)#% ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�%$2#1)-,0� �%,%&)10� !,$ �##/27

!*0ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�-),' �20),%00 �0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�!1! �!0% �!,!'%+%,1 �601%+ ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�)01/)"21%$ �-+.21),' �,3)/-,7

+%,1


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�)0#-2,1%$ �!0( �*-4 ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�!1! �)#1)-,!/6 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



ÑÑÑÑÑÑÑÑÑÑÑ�6,!+)# �!1! �5#(!,'% ÑÑÑÑÑÑ


ÑÑÑÑÑÑÑ�



�)01/)"21%$ �!1! �/-#%00),'ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99) A–11

��

��

��

��

��

��

��

��

��

��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ��.� � -�,$*.$)( �* �$!$��.$)(- ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



� -$"( �("$( ,$("ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� ')(-.,�.$)( ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� *)-$. �$(�(�$�& �(-.$./.$)( ÑÑÑÑÑÑÑÑÑÑÑÑ


�



��.� �$& �.$&$.2 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ��.� �(. ,�#�(" �),'�. ÑÑÑÑÑÑ


ÑÑÑÑÑÑ��



��.� �'*),. ��("/�" ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� /.-�# �(�/-.,$ �),' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

() .,�(-&�.$)( ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�



�$-.,$�/. � �!!$� �/**),. �2-. 'ÑÑÑÑÑÑÑÑÑÑÑÑ


�


DIST ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Distribution ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

8 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

8


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�2(�'$� �$(% �$�,�,2 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�


�&.ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

� & . ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�$, �. �/' ,$��& )(.,)& ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�) �). �*, �� ÑÑÑÑÑÑÑÑÑÑÑÑ


�


�) �2 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�)�/' (. �2* ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ��. 3)!3�$,.# ÑÑÑÑÑÑ


ÑÑÑÑÑÑ



�$0$-$)( )! �(. , -.ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ), �*$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�).- * , �(�# ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�*. ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

� *�,.' (. ÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ), �, ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

� �$. ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ,$. , ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��.� � �),� �1.,��.$)( �(� ��(3

�" ' (. �,$. ,ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�$-.,$�/.$)( � +/$, ' (.- �&�(3

($("



�



�$-.,$�/.$)( � -)/,� �&�(($("ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99)A–12

��

��

��

��

��

��

��

��

��

��



��1, ��&!, �.-,-�( %(# ÑÑÑÑÑÑÑÑÑÑÑÑ



�,*ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�%,*&�1ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�!�%,%)( �.**)+- �1,-!' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�)�.'!(- �1*! ÑÑÑÑÑÑÑÑÑÑÑÑ



�-� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��-� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�!'�( �%'! �!(�! ÑÑÑÑÑÑÑÑÑÑÑÑ



�.*ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�.*&%��-%)(ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�� +%-!+ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�)2!( ÑÑÑÑÑÑÑÑÑÑÑÑ


�



��+(%(#, �( �+)"%-, ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�0*!(,!, �( �-$!+, ÑÑÑÑÑÑÑÑÑÑÑÑ




�0*!(,! ��+-%�%*�-%)(ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�3��%& ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�&!�-+)(%� ��%& ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�++)+, �( �'%,,%)(, �0�!*-! ÑÑÑÑÑÑÑÑÑÑÑÑ




��$ ��(%- )" �!�,.+!� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�( %(# �/�%&��%&%-1 ÑÑÑÑÑÑÑÑÑÑÑÑ



EACÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Estimate at CompletionÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


3



�/!+!,- �**&%��-%)( �!/!&)*'!(-

�))&ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�'*&)1!! �,,%,-�(�! �+)#+�'ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�&!�-+)(%� �.+,- �( �%( ÑÑÑÑÑÑÑÑÑÑÑÑ




� %- �) !ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�.+)*!�( �)''.(%-1 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�(#%(!!+%(# �$�(#! ��(�#!'!(-ÑÑÑÑÑÑÑÑÑÑÑÑ



B73.3.1 (6/99) A–13

��

��

��

��

��

��

��

��

��

��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�% "%��)"% �!�% � �&+"�� ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�% "%��)"% �!�% � �)��)ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��"�"�%+ �&%*,$�) ��*'&%*� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�#��+)&%"� �,*+&$�) �,''&)+ ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�%�) / �%� �!�$"��# �/*+�$* ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�*+"$�+�� +� -�"#��#� ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�-�)�*+ ��-�#&'$�%+ ��%+�)ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�#��+)&%"� ��+� �%+�)�!�% � ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�#��+)&%"� ��+� �)&��**"% ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�$'#&/�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�(,�# �$'#&/$�%+ �''&)+,%"+/ ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�(,�# �$'#&/$�%+ �''&)+,%"+/

�&$$"**"&%


��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�%+�)')"*� ��"#"+/ �#�%%"% ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�#��+)&%"� �,%�* �)�%*��)ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�#��+)&%"� �,%�* �)�%*��) �/*+�$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�$'#&/�� %-&#-�$�%+ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��)%�� %�&$� �)��"+ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�$'#&/�)�* ��%+"�"��+"&% �,$��) ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�%+�)')"*� �%�&)$�+"&% �/*+�$*ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�.��,+"-� �%�&)$�+"&% �/*+�$ ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�(,"'$�%+ ��%� �$�%+ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�,)&'�� "��#� ��*+� �%� *"� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�%-")&%$�%+�# ��%� �$�%+ �/*0

+�$ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



B73.3.1 (6/99)A–14

��

��

��

��

��

��

��

��

��

��



�0$� (� )! �(-/,��$&$.3 ÑÑÑÑÑÑÑÑÑÑÑÑ


��



�(� )! �)�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�(� )! �)(.# ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��)()'$� �,� , �/�(.$.3 ÑÑÑÑÑÑÑÑÑÑÑÑ


��



�2* (- ��,.$�$*�.$)( ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ), *)- ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�& �.,)($� �)$(. )! ��& ÑÑÑÑÑÑÑÑÑÑÑÑ


�



��,($("- � , �#�, ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�2* ,. � ,!),'�(� �/**),. �3-4

. '



�



�+/�& �)ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


EQP ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Equipment ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

6 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

3



�'*&)3 , ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�'*&)3 � .$, ' (. �(�)' � 4

�/,$.3 �.



�


��2ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�(. ,*,$- � +/$, ' (.- �&�(($("

�2 �/.$)(



�



�,,), ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�'*&)3 �.)�% �1( ,-#$* �&�(ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


ETC ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Estimate to Complete ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

10 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

3



�("$( , .) �,� , ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�2 �/.$0 �$� 4�, -$� (. ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�(/' ,�.$)( � ,$!$��.$)( �3-. 'ÑÑÑÑÑÑÑÑÑÑÑÑ


�


�2�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�2�&/� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�2 �),%- ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



� � � ), ! � ! ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�$2./, - �(� �$..$("- ÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99) A–15

��

��

��

��

��

��

��

��

��

��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�(5%$ �00%1 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�2,#1(-,!* �#),-4*%$&%+%,1ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�(,!* �3%/!&% �!6 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�(,!* �00%+"*6 �#'%$2*% ÑÑÑÑÑÑÑÑÑÑÑÑ


��



�/%% �*-,&0($% �'(. ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�(,!,#(!* �##-2,1(,& �1!,$!/$0

�-!/$ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�(,!,#(!* �,!*60(0 �./%!$0'%%1

�--* !,$ �%.-/1 /(1%/





�-/%#!01 ÑÑÑÑÑÑÑÑÑÑÑÑ




�!5 �-,1/-* �,(1 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�-/+0 �%0(&, �($ ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�-/+ �%0(&, �($ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�(0#!* �!1% �!11%/, ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�%$%/!* �!5ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�%$%/!* �-20(,& �$+(,(01/!1(-, ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�/%(&'1 �!,$*(,& �-$% ÑÑÑÑÑÑÑÑÑÑÑÑ


��



�%$%/!* �,02/!,#% �-,1/("21(-,

�#1



�



�(/01 �,� �(/01 �21 ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�/%,#'� �1!*(!,� �%/+!,� �.!,(0' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�%$%/!* �,#-+% �!5 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ



�2,#1(-, �%60ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�!(/ �!"-/ �1!,$!/$ �#1 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�*%5("*% �!#'(,% �%,1%/ ÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99)A–16

��

��

��

��

��

��

��

��

��

��



��)&(4 �"!& �( �"�2" � 0 ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�("3&�(" ��*1#� 01.&*$ �4/0")ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�."" +* +�.! ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�&3"! �.!". �1�*0&04 ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�&.) �(�**"! �.!". ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�&*�* &�( �",+.0&*$ ÑÑÑÑÑÑÑÑÑÑÑÑ



FREQÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

FrequencyÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


8



�."* % �.�* / ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�"!".�( �"/".2" �4/0") ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�("3&�(" �,"*!&*$ � +1*0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


#0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�++0 ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�"!".�( �.�!" �+))&//&+*ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�"!".�( ��3 �*0.4 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�1((5�&)" �),(+4"" ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�1((5�&)" �-1&2�("*0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�&*&/%50+5�.!". ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�&(" �.�*/#". �.+0+ +(ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�+."&$* �.�!" �+*"/ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�"!".�( �*"),(+4)"*0 �*/1.�* "ÑÑÑÑÑÑÑÑÑÑÑÑ


��



�"!".�( �*"),(+4)"*0 ��3 � 0ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�&.) �+.' �.!". ÑÑÑÑÑÑÑÑÑÑÑÑ




�&/ �( �"�.ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�+. �+1. �*#+.)�0&+* ÑÑÑÑÑÑÑÑÑÑÑÑ



B73.3.1 (6/99) A–17

��

��

��

��

��

��

��

��

��

��



�$,$0 * ,# �#+(,(120 2(4$ �58

.$,1$1ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�$,$0 * �""-3,2(,& ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�$,$0 * �$#&$0 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�$,$0 **6 �""$.2$# �""-3,2(,&

�0(,"(.*$1




�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�$,$0 * �""-3,2(,& �%%("$ ÑÑÑÑÑÑ


ÑÑÑÑÑÑ



�$,$0 * �3(*#(,& �-,20 "2-0ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�0(2(1' �-3,#1 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�0$ 2$0 �' , -0 �/3 * �- ÑÑÑÑÑÑÑÑÑÑÑÑ



&(& ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�(& !62$ ��,$ !(**(-, !62$1� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�0 .'("1 �,2$0"' ,&$ �-0+ 2 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ



�*-11 06ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�+!� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�$1$**1"' %2 +(2 !$1"'07,)2$0

� %23,& ��$0+ ,6�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

,- 20 ,1* 2(-, ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�-4$0,+$,2 �.$, �612$+1 �,2$08

"-,,$"2 �0-%(*$



�



�--#1 ,# �$04("$1 � 5 �� , # �ÑÑÑÑÑÑÑÑÑÑÑÑ




�0$ 2$0 �' , ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�0-11 � 5 �5"*31(-, ÑÑÑÑÑÑ


ÑÑÑÑÑÑ



�0 .'(" * �1$0 �,2$0% "$ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�$ *2' ,# � %$26 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�(&'*6 �-+.$,1 2$# �+.*-6$$ ÑÑÑÑÑÑÑÑÑÑÑÑ




�$5 #$"(+ * ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�(&'8�$4$* � ,&3 &$ ÑÑÑÑÑÑ


ÑÑÑÑÑÑ��



�$ #/3 02$01ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99)A–18

��

��

��

��

��

��

��

��

��

��



�0)�* �".+0- ". ÑÑÑÑÑÑÑÑÑÑÑÑ


��



�0)�* �".+0- ". ��*�$")"*/ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�&!!"* �"(" /&+* ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�4,"-/"3/ ÑÑÑÑÑÑÑÑÑÑÑÑ




�4,"-/"3/ ��-'0, ��*$0�$" ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�4,"-/"3/ �-�*.#"- �-+/+ +( ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�"�/&*$� �"*/&(�/&+*� �*! �&-

�+*!&/&+*&*$



�



�*,0/ ��0/,0/ �+*/-+( ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�*/"- �+),�*4 �+./ �"*/"-ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�!"*/&#& �/&+* �+!" �".&$*�/+- ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�*/"- �+),�*4 �0� ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�!"*/&#& �/&+* ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�*/"-5�(�*/ �")�*! ÑÑÑÑÑÑÑÑÑÑÑÑ


��



�*/�*$&�(" �",("/&+* �+./ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�*./&/0/" +# �(" /-& �( �*! �(" 5

/-+*& �*$&*""-.ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�*1"*/+-4 ��*�$")"*/ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


�* ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�* % ÑÑÑÑÑÑÑÑÑÑÑÑ


�


�* ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�* (0!"ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�* +-,+-�/"! ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� �2" �+0 ÑÑÑÑÑÑÑÑÑÑÑÑ




�*/"-*"/ �-+/+ +( ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�*&/&�( �-+$-�) �+�! ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�),(")"*/�/&+* �(�**&*$ �"..&+*ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99) A–19

��

��

��

��

��

��

��

��

��

��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�+ �$"$(-0 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�+#(2(#1 ) �$0(.$*$+0 �"",1+0ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�+0$.+ ) �$2$+1$ �$.2("$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�+0$.+ 0(,+ ) �0 +# .#/ �.& +(6 7

0(,+ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�+0$.+ 0(,+ ) �0 +# .# �$.( )

�1*!$.



�



�+%,.* 0(,+ �$"'+,),&5ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�+",*$ � 4 �.$#(0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�+2$/0*$+0 � 4 �.$#(0 ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�+"$-0(,+70,7� 0$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�0* ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�0* ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�,1.+ ) �+0.5ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�,(+0 �--)(" 0(,+ �$2$),-*$+0 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�,! �,/0ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,! �,/0 �"",1+0(+& ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,! �,/0 �())(+& ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�� #3 .#/ � �,*- +5ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�,1.+ ) �+0.5 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ



�,(+ �()$ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�1/07(+7�(*$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,1.+ ) �5-$ ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,(+0 �$+01.$ �+0$.$/0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�',1/ +# ÑÑÑÑÑÑ


ÑÑÑÑÑÑ


�!ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�(),!50$ �� !50$/�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



B73.3.1 (6/99)A–20

��

��

��

��

��

��

��

��

��

��



�+,4)#"%#7��0#" �#+#/�1,/ ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�� 20&'('7��'0&�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�#11#/ ,$ �/#"'1 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�'+#��/"#/ ÑÑÑÑÑÑÑÑÑÑÑÑ




�,!�) �/#� �#14,/( ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


) ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�,2+" ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�#3#/�%#" �25,21ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



��+"#" �,01 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�#00 1&�+ � ��/),�" ÑÑÑÑÑÑÑÑÑÑÑÑ




�#3#) ,$ �#1�') ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,!�) ��1� �/#� ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�#00 �&�+ ,/ �.2�) �,ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,%'!�) �')# ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



��01 �+� �'/01 �21 ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,17�'6# �+3#+1,/5 ��+�%#*#+1

�+1#/-,)�1',+ �#!&+'.2#


� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�'!#+0# �)�1#ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�#�3# ,$ � 0#+!# ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�'+# ,$ �20'+#00 ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�#3#) ,$ �#1�')ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�'.2'" �#1/,)#2* ��0 ÑÑÑÑÑÑÑÑÑÑÑÑ



�� ,/ )-'ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�'+#0 -#/ �+!&ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,+% ��+%# �)�++'+% ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�,�"'+% ��!( �501#* ÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99) A–21

��

��

��

��

��

��

��

��

��

��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�+/ �!-%�( �0)�!- ÑÑÑÑÑÑ


ÑÑÑÑÑÑ��



�! #!- �4,!ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�!.. �$�* ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�%*! �4,! ÑÑÑÑÑÑÑÑÑÑÑÑ


�


�/ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�%)%/! ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�%"!5/+5��/! ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�+*# �!-) �!�/ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�+*# �!-) �%.��%(%/4 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�!.. /$�* � �-0�'(+� ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�+ %"%! ��!(!-�/! �+./ �!�+15

!-4 �4./!)


� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�!�* ��.+(0/! �!1%�/%+* ÑÑÑÑÑÑÑÑÑÑÑÑ


�



��*0"��/0-%*# �0/+)�/%+* �-+/+5

�+(



�



�!..�#%*# �,,(%��/%+* �-+#-�)

�*/!-"��!




�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ��*�#!)!*/ � 1%.+-4 �!-1%�!. ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�


��3ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��3%)0)ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�!#��4/! ��*! )%((%+* �4/!.� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�!�$�*%��( �-!�' +2* ÑÑÑÑÑÑÑÑÑÑÑÑ


�



��*�#!)!*/ �4 ��&!�/%1!. ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


MC ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑMethod of Computation ÑÑÑÑÑÑ

ÑÑÑÑÑÑ10 ÑÑÑÑÑÑ

ÑÑÑÑÑÑ10



�! %� �+*/-+( �*/!-"��!ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��/!-%�(5�+)%*�/! ��$! 0(%*# ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�+*/$� ��4� �!�- ÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99)A–22

��

��

��

��

��

��

��

��

��

��



��(.!��-.+$(" �("$( +$(" ÑÑÑÑÑÑÑÑÑÑÑÑ


�


' " )+ ' "�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

� "��1- ��( '$&&$)( �1- ,�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�!" ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��(.!��-.+$(" ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��#$( �(,-+.�-$)( ÑÑÑÑÑÑÑÑÑÑÑÑ


��



��(.!��-.+$(" �(,-+.�-$)( ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��"( -$� �(% �#�+��- + � �)"($2

-$)(ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


��2�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�$&$-�+1 �(,* �-$)( �-�(��+� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�$( ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�$($'.' ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�$&&$)(, )! �(,-+.�-$)(, * + � 2

�)(�


�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�



��(�" ' (- �(!)+'�-$)( �1,- 'ÑÑÑÑÑÑÑÑÑÑÑÑ


�


�$,�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�$,� &&�( ).,ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



��*� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�$&&$)( �++ &, * + ��1 ÑÑÑÑÑÑÑÑÑÑÑÑ


�



��(.!��-.+$(" ��(�" ' (- �1,2

- ',



�



�$( +�&, ��(�" ' (- � +/$� ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.&-$(�-$)(�& �)'*�(1ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.&-$(�-$)(�& �+)�.�-, ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�)(-# ÑÑÑÑÑÑÑÑÑÑÑÑ


�



� -#)� )! � &$/ +1 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


�)"�, ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�)-)+ ��,)&$( ÑÑÑÑÑÑÑÑÑÑÑÑ


��



��0$'.' �+� + �.�(-$-1ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�)� )! �+�(,*)+-�-$)( ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��,- + �+)�.�-$)( ��# �.& ÑÑÑÑÑÑÑÑÑÑÑÑ


��


B73.3.1 (6/99) A–23

��

��

��

��

��

��

��

��

��

��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ� 2$0( * �$4($5 �- 0# ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



� "'(,$ �$ # !*$ �,1203"2(-,1ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



� (,2$, ,"$� �$. (0� ,# �.$0 8

2(-, �3..*($1



�



� 2$0( * �$/3(0$+$,21 �* ,,(,&ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� ,3% "230(,& �$1-30"$ �* ,,(,& ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


��6 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

� 2$0( *1� �$1-30"$� �* ,,(,&�

,# �6$"32(-,ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



� 2$0( * � %$27 � 2 �'$$2 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�1& ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�$11 &$ ÑÑÑÑÑÑÑÑÑÑÑÑ




�-,2'82-8� 2$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�$2'-#18�(+$ �$ 130$+$,2 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



� )$82-8�0#$0ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ� )$82-8�0#$0 �0-#3"2 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ��



� )$82-8�2-")ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




� )$82-8�2-") �0-#3"2 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�3*2(.*$ �,(2 �$1(#$,2( * �3(*#(,&ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�-#$* �-0) �0#$0ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


� � � ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ� +$ ,# �##0$11 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ��



�-2 �4 (* !*$ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



� +$ �$ 0"' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�-2 �..*(" !*$ ÑÑÑÑÑÑÑÑÑÑÑÑ


��



� 2(-, * �32-+ 2$# �*$ 0(,&

�-31$





� 2(-, * �11-"( 2(-, -% �$"30(2($1

�$ *$01 �32-+ 2$# �3-2 2(-,1ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99)A–24

��

��

��

��

��

��

��

��

��

��



� . �))% ��&/ ÑÑÑÑÑÑÑÑÑÑÑÑ


��



�/' ,$��& )(.,)&ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


� �� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��.$)(�& (. , !), �/* ,�)'*/.3

$(" �**&$��.$)(-



�



�)(�$-�,$'$(�.$)( � -.ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�). �+/�& �) ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� .0),% �$& �2-. ' ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�). �, �. , �#�( ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



� .0�, �&)��& � --�"$(" ÑÑÑÑÑÑÑÑÑÑÑÑ


�



� 1. �(� �$,-. �/.ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��.$)(�& �(-.$./. !), �.�(��,�-

�(� � �#()&)"2



�



�). � -- �#�(ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



� .0�, �)��& �)�/& ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,$*& � .ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�) ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�/'� , ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� . �* ,�.$(" �-- .- ÑÑÑÑÑÑÑÑÑÑÑÑ


�



� . �* ,�.$(" �)--ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�).$� )! � ��$( -- ÑÑÑÑÑÑÑÑÑÑÑÑ


�



� . �,)!$. � !), ��1 -ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�)(3�/!!$�$ (. �/(�- ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



� 0 � �#()&)"2 ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�). .) �1� � ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�) �)/�# �1�#�(" )! �$ - ÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99) A–25

��

��

��

��

��

��

��

��

��

��



��+*-8# �#,,--21!&�. ��-*9

*�,"�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

,- 20�,1*�2'-, ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�



�#5 �-0) �2-!) �6!&�,%# ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�.2'-, ÑÑÑÑÑÑ


ÑÑÑÑÑÑ



�4#02'+#ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� (#!2 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.#, �-**� -0�2'-, �,4'0-,+#,2 ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�4#0 �0#"'2 �'+'2 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ� (#!2 �-,$'%30�2'-, ��,�%#0 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�.2'!�* �&�0�!2#0 �#!-%,'2'-,ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�0%�,'8�2'-,�* �#4#*-.+#,2 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.#, ��2� ��1# �-,,#!2'4'27 ÑÑÑÑÑÑÑÑÑÑÑÑ




�4#0�** �/3'.+#,2 �$$#!2'4#,#11 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�0'%',�* �/3'.+#,2 ��,3$�!230#0 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�4#0&#�"ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�,92&#9�- �0�',',% ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



� (#!2 �',)',% �," �+ #""',%ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�,*',# �0�,1�!2'-, �0-!#11',% ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




� (#!2 ��. ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�$$'!# -$ ��,�%#+#,2 �," �3"9

%#2



�



�.#, �#11�%',% �,2#0$�!# ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�329-$9�-!)#2 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�.2'-, ÑÑÑÑÑÑ


ÑÑÑÑÑÑ



�0"#0 �0-!#11',%ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99)A–26

��

��

��

��

��

��

��

��

��

��


�* �0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�*��* �0(� ÑÑÑÑÑÑÑÑÑÑÑÑ


��



�* �&"1�,"'&ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


4



�(�& �0+,�%+ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�(�*�,"& �0+,�% ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.�*� �!'*,� �&� ��%� �� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�(�& �0+,�%+ �'-&��,"'& ÑÑÑÑÑÑÑÑÑÑÑÑ


�



��-(�,"'&�$ ��,0 �&� ��$,!

�,





�(�& �0+,�%+ �&,�*�'&&��,"'& ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.�*,"%�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.�*2,!�2�'-&,�* ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�&� �'-�! �/�!�& � '� �"�+ ÑÑÑÑÑÑÑÑÑÑÑÑ



'1 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�-&�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


� � � '*

( � (ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�'+,� � �&� ��#"& ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�*'�", �&� �'++ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�*'(�*,0 �&� �)-"(%�&, ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�$�&&"& ��-� �,"& � $$'��,"'&+ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�*"��*&"& + ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�-*�!�+� �*��*ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�*'�",��'$-%� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


(� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��* &&-% ÑÑÑÑÑÑÑÑÑÑÑÑ


�


� � ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�*'�-�,"'& �,".",0 �'&,*'$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


� �� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�'+,"& �,�* �-,'�� ÑÑÑÑÑÑÑÑÑÑÑÑ




�'+,"& ��'*� �-,'��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



B73.3.1 (6/99) A–27

��

��

��

��

��

��

��

��

��

��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�,01&+$ �"#,/" �"�/ �+! ÑÑÑÑÑÑ


ÑÑÑÑÑÑ



�"/0,+�) �,*-21"/ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�"/0,+�) �,*-21"/ �2--,/1 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��5*"+10� �"!2 1&,+0� �"+"#&10

�+! /2�)0ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�)�+6�,6�%" (6 1&,+ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�/,$/�* �"0&$+ ��+$2�$" ÑÑÑÑÑÑÑÑÑÑÑÑ


��


�!� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�/"!& 1&3" ��&+1"+�+ " ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�/,!2 1 ��1� ��+�$"*"+1 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�/, "00,/6�,*&+�1"! � %"!2)&+$ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,01&+$ �!&1 �,!" ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�/,$/�* �3�)2�1&,+ �+! �"32"

�" %+&.2"ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�%50& �) �&)" ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�/,'" 1"! �&+�) �,01ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�/,'" 1"! �&+�) �/,#&1 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�/,'" 1"! �&+�) �"3"+2" ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�/, "00 �),4 � %"!2)&+$ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ��5*"+1 �+01/2*"+1 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�/,$/�* �+#,/*�1&,+ �&)"ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�/,$/�**��)" �,$& �,+1/,))"/ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�2�)& �&*&1"! �,*-�+5 ��+&1"!

�&+$!,*�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�)�++"! �/!"/ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�)1 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�)�+1 ÑÑÑÑÑÑÑÑÑÑÑÑ



B73.3.1 (6/99)A–28

��

��

��

��

��

��

��

��

��

��



�*�.�&,#.� ��#&,�&�&�� ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�*'(�*,/ ��&�!�%�&,ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��*#'� �-%��* ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�*'��++#&! �(,#'& ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�-*�"�+� �*��* ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�'+, �-, ' ��$�&�� ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�-*�"�+� �*��* �&,*/ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�-*�"�+� �*��* �*'��++#&! ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�'#&,1' 1��$� ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�'*,��$� �(�*�,#&! �/+,�% �&,�*1

�� '* '%(-,�* �&.#*'&%�&,+



�



��'($�� $��+� �&� �"#&!+ ÑÑÑÑÑÑÑÑÑÑÑÑ




��*, ��*#'� ��$�&�#&! ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�*'!*�%1�$�&&#&!1�-�!�,#&! �/+1

,�%ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�*��**�&!�� /%�&,+ �&� ��1

('+#,+



�



��/ ��*#'� �&�#&! ��,�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��*,+ (�* �#$$#'& ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�*� �**�� *'.#��* �*!�&#0�,#'&ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�-*�"�+� �*#�� *#�&�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��/*'$$ ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�-�$#� ��$�,#'&+ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��/ �,�,-+ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��* �)-�*� �'', ÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99) A–29

��

��

��

��

��

��

��

��

��

��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�,2+!0 -"/ �.2�/" �+ % ÑÑÑÑÑÑ


ÑÑÑÑÑÑ��



�,2+!0 -"/ �.2�/" �+ % �0,)21"ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�,2+!0 -"/ �.2�/" �+ % ��2$" ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�/,3&+ &�) ��)"0 ��5 ��+�!�� ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�/,'" 1 �1/�1"$6 �,/(0%,- ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�"/&,!71,7��1" ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



��/17�&*" �*-),6""ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�/,$/�* �"*-,/�/6 �&5 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��6/,)) ��5 ��+�$"*"+1 ÑÑÑÑÑÑÑÑÑÑÑÑ


�


�16 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�/&,/&16 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�)�+ �,/( �/!"/ ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�/"3&,20 �"�/7�+!ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�/&,/ �"�/7�+! ��)�+ " ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�/&,/ �"�/7�+! �2*2)�1&3" ÑÑÑÑÑÑÑÑÑÑÑÑ




�/&,/ �"�/7�+! �"1 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



� � ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�2"01&,+0 �+! +04"/0 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�2�)&16 002/�+ "ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�2�)&#&"! �"+"#& &�/6 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�2"/6 �6 �5�*-)" ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�2�)&#6&+$ �3"+1 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�2�)&16 �2+ 1&,+ �"-),6*"+1 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�2�)&16 ��+�$"*"+1ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�2,1" �/!"/ ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�


�/6ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�2"/6ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



B73.3.1 (6/99)A–30

��

��

��

��

��

��

��

��

��

��



�-�*,�*0,'0��,� ÑÑÑÑÑÑÑÑÑÑÑÑ


�


�,/ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�-�&,#,/ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��+��*�" �&� ��.�$'(%�&, ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�#!",�� , ÑÑÑÑÑÑÑÑÑÑÑÑ




��)-#*��(,#'&�$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



��.�*+��'#� ÑÑÑÑÑÑÑÑÑÑÑÑ


�



��.#+�� %'-&,ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


� � ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��(#� (($#��,#'& ��.�$'(%�&,ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


� � ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��&�'% ��++ ��%'*/ ÑÑÑÑÑÑÑÑÑÑÑÑ


�


��&� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��&�'% ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�'-!" �-, ��(��#,/ �$�&&#&! ÑÑÑÑÑÑÑÑÑÑÑÑ




��('*, ��+#!& #�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�-&&#&! �'$$�*+ ��$�&�� '*%�,ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




��$�,#'&�$ ��,��+� ��&�!�%�&,ÑÑÑÑÑÑÑÑÑÑÑÑ


�



��$�,#'&�$ �'�-%�&, ��&�!�0

%�&,



�



��$ �+,�,�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��'*� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��.�*+� �&,*/ �'&,*'$ ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�� *�&��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



��$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��$�,#'&+"#( ÑÑÑÑÑÑÑÑÑÑÑÑ




��(#�$/� ��'&'%#��$$/� �&� �*�0

�#�,��$/



�



��#' �*�)-�&�/ ÑÑÑÑÑÑÑÑÑÑÑÑ


�



��)-�+, '* �*'('+�$ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99) A–31

��

��

��

��

��

��

��

��

��

��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ� *. ,- !(+ �.(- ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



� ,#�.�% �'�(& ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�#�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�#� /.-� ��'��+#� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� �.� � �',-+.�-#(' � - (&).-2

+ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� ,)(', �#' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� ,)(', �#' ��(!-0�+ �)��- ÑÑÑÑÑÑÑÑÑÑÑÑ


�


�&$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

� &�+$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ� -.+' (' �,, -, ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



� �(+� (! �&)%(1& '-ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� -.+' (' �'/ ,-& '- ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



� �� '%1 � &(+1 ÑÑÑÑÑÑÑÑÑÑÑÑ


��



� (+� + �(#'- ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ� (+� + �.�'-#-1 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



� &(- �+(� �.+ �%%ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� )(+- �+("+�& � ' +�-(+ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� ,#� '-#�% �+() +-1 ��'�" & '-ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� *.#+ & '-, �%�''#'" �1,- & ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.''#'" �.�'-#-1 ��%�'� �(+&�-ÑÑÑÑÑÑÑÑÑÑÑÑ


�



� , +/ � �("'#-#(' ��(.'-#'"ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ� %�-#/ � �(+� �.&� + ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



� ,(.+� � *.#+ & '-, �%�''#'"ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�� 1,- & ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� �(+� �1) ÑÑÑÑÑÑÑÑÑÑÑÑ



B73.3.1 (6/99)A–32

��

��

��

��

��

��

��

��

��

��



�$12/+ 1, �/,#2"1(,+ ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�$3(0$# �+(10ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




� ()/, # �+$*-),6*$+1 �+02/9

+"$ �"1



�


� � � ,/ 0 � 'ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�'(--(+& +# � +#)(+&ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�$/( ) �2*!$/ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� )$0 �/#$/ ÑÑÑÑÑÑÑÑÑÑÑÑ




� )$0 �/#$/ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�,"(818 �+,+6*$ ��/ +"$� ÑÑÑÑÑÑÑÑÑÑÑÑ

+, 1/ +0) 1(,+ÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�1 +# �),+$ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�601$*0 �--)(" 1(,+ �/"'(1$"12/$ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,%14 /$ �"1(,+ �$.2$01 ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�2-$/%2+# �*$+#*$+1 �$ 21',9

/(7 1(,+ �"1



�



�$/3("$ �())(+&ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�2!)$#&$/ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�1 +# /# � 1"' �2 +1(16 ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�1 120 �,#$ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�$/3("$ �) 00 �,#$ ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�* )) �,*-21$/ �601$*0 �+1$/% "$ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�"/$$+ �$0(&+ �(# ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�1 1$ �(0 !()(16 �+02/ +"$ ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�'(--(+&� �$01(+ 1(,+� +# �2 +9

1(16



�



�$"2/(1($0 +# �5"' +&$ �,**(09

0(,+ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99) A–33

��

��

��

��

��

��

��

��

��

��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�,�&��*� �&,*1 �$�++ ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�


��)ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��)-�&��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�'-*�� &,*1 �,!$!,1 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,�,�%�&, '� �!&�&�!�$ ��'-&,!&�

�,�&��*�+ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� '( �$''* �'&,*'$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�-��!$� ÑÑÑÑÑÑÑÑÑÑÑÑ



��0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�-��!0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�!&�$� �,�% �-, '*!2�,!'& ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�,�&��*� �&�-+,*1 �$�++!�!��,!'&ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�(��!�$ �&,�*�+, �*'-( ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�'�!�$ �&+-*�&�� -%��* ÑÑÑÑÑÑÑÑÑÑÑÑ


��



�,�,� �&�'%� ��0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�,'�#!&� ��(!&� �&!, ÑÑÑÑÑÑ


ÑÑÑÑÑÑ



�,'�##��(!&� �&!,ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�$+ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��$�+ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,�&��*� ��!&,�&�&�� *��%�&,

�'&,*��,


�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�-�"��, ��,,�* �0(�*, ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�!&�$� �!&-,� �0� �&�� '� !�+ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,�&��*� ��++�� '*%�, ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



� !((�* ��&��%�&, �1+,�% ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�1+,�%+ ��,/'*# �*� !,��,-*� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�1+,�%+ ��,/'*# �*� !,��,-*�

!+,*!�-,!'& ��*.!��+ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99)A–34

��

��

��

��

��

��

��

��

��

��


ÑÑÑÑÑÑÑÑÑÑÑ�!+%2 �1$%1 ÑÑÑÑÑÑ


ÑÑÑÑÑÑÑ�



�!+%2 �1$%1 �-317ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�!+%2 �1$%1 �1.#%22)-' ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�3!3%,%-3 .& �.2)3).- ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�4''%23%$ �1$%1 �4!-3)37 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


SP ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Service Provider ÑÑÑÑÑÑÑÑÑÑÑÑ

13 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

14


�/ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�.#)%3: /%1 8).-) ��3!+7�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

-. 31!-2+!3).-ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�



�3!3)23)#!+ �1.#%22 �.-31.+ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�723%, �1.5)$%$ �-3%1&!#% ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.#);3; $% �%12.--%2 9 �%2/.-2)<

")+)3; �),)3;% ��%+')4,�


-. 31!-2+!3).-ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�(.13%23 �1.#%22 �),% �4+% ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�3!3)23)#!+ �4!+)37 �.-31.+ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�

ÑÑÑÑÑÑÑÑÑÑÑÑ�� %04%+� ÑÑÑÑÑÑÑÑÑÑÑ

ÑÑÑÑÑÑÑÑÑÑÑ�314#341%$ �4%17 �!-'4!'% ÑÑÑÑÑÑ


ÑÑÑÑÑÑÑ�



�#(%$4+%$ �.43)-% �!)-3%-!-#%ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.+43).-2� �%+!3).-2()/2� �!+4% ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.#)!+ �%#41)37 �4,"%1ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�/1%!$2(%%3 �..+ �.1 22%3 �%<

/.13)-' ��)6%$ 22%3 �%/.13 1)3<

%1�




�3$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�3!-$!1$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



ÑÑÑÑÑÑÑÑÑÑÑ�(.13<�%1, �)2!")+)37 ÑÑÑÑÑÑ


ÑÑÑÑÑÑÑ�



�3!3% �-%,/+.7,%-3 �-241!-#%ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�)#* �!72� �!#!3).-� �.+)$!72 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


SVO ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Service Order ÑÑÑÑÑÑÑÑÑÑÑÑ

10 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

3


B73.3.1 (6/99) A–35

��

��

��

��

��

��

��

��

��

��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�,$03�.# �#./',+/ �#-,/'0,.4 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�,!'#04 $,. �,.)"3'"# �+0#. �+(

�'+�+!'�) �#)#!,**1+'!�0',+/




�4 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�4/0#* ÑÑÑÑÑÑ


ÑÑÑÑÑÑ



�1*5,$50&#5�#�./�5�'%'0/ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�'*# �+" ��0#.'�)/ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.'�) ��)�+!# ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�'*# �+0.4 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�'*# !!,1+0'+% ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�#!&+'!�) �,**'00## ,+ �-#.�05

'+% �4/0#*/





�.�+/*'//',+ �,+0.,) �.,0,!,)��+5

0#.+#0 �.,0,!,)ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�'*# �+0.4 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,0�) �*-),4## �+2,)2#*#+0 ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�4-# ,$ �+-10 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�.1!(),�" ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�.�+/)�0',+ ��+�%#.ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�� )# ,$ �,+0#+0/ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�#!&+'!�)��$$'!# �.,0,!,) ÑÑÑÑÑÑÑÑÑÑÑÑ




�.�+/�!0',+ �.,!#//'+% �,1+!') ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�,0�) �.,"1!0'2# ��'+0#+�+!# ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�'*#5�&�/#" �."#. �,'+0ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�,0�) �1�)'04 �,+0.,) ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,0�) �1�)'04 �+%'+##.'+% ÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99)A–36

��

��

��

��

��

��

��

��

��

��


ÑÑÑÑÑÑÑÑÑÑÑ�/3!, �4!,)38 �!.!'%-%.3 ÑÑÑÑÑÑ


ÑÑÑÑÑÑÑ�



�� 1%$)3 �%0/13).' '%.#8�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�1!.2,!3)/. �//,2 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�.)3 /& �%!241% ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.)5%12!, �!3#( �.').% ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�3),)38 /& �423/-%1 �.&/1-!3)/.

�823%-ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�2%1 �%&).%$ �/$% ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


ÑÑÑÑÑÑÑÑÑÑÑ�2%1 �%&).%$ �%01%#)!3)/. ÑÑÑÑÑÑ


ÑÑÑÑÑÑÑ�



�.)5%12!, �),% �/.5%13%1ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.)$%.3)&)%$ �/1%)'. �"*%#3 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.)3%$ �).'$/- ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�1"!. �!.$ �.$42318 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�

ÑÑÑÑÑÑÑÑÑÑÑÑ�- ÑÑÑÑÑÑÑÑÑÑÑ

ÑÑÑÑÑÑÑÑÑÑÑ�.)3 /& �%!241% ÑÑÑÑÑÑ


ÑÑÑÑÑÑÑ�



�.)3 /& �%!241%ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.)3 /& �%!241% ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.)5%12!, �1/$4#3 �/$%ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�0$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�0$!3% ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�0$!3% ÑÑÑÑÑÑÑÑÑÑÑÑ




�.).3%114-03%$ �/6%1 �400,8ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


ÑÑÑÑÑÑÑÑÑÑÑ�.3%23%$ �4)#+ �)7 ÑÑÑÑÑÑ


ÑÑÑÑÑÑÑ�



�.)&/1- �%2/41#% �/#!3/12ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.)3%$ �3!3%2 �/,,!12 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


� � ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�!,4% $$%$ �%36/1+ ÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99) A–37

��

��

��

��

��

��

��

��

��

��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ��)1# �""#" ��4 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ



�,)1*# ,..#!0',+ ��!0,.ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�'"#, �'/-)�5 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�'"#, �'/-)�5 �#.*'+�) ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�'"#, �'/-)�5 �+'0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


��6�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�#0#.�+/ �*-),5*#+0 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�'/!,/'05 �+"#4ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�#&'!)# �"#+0'$'!�0',+ �1* #. ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�#.5 ��.%# .1"# �..'#. ÑÑÑÑÑÑÑÑÑÑÑÑ




�#+",. ��+�%#" �+2#+0,.5 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�,!� 1)�.5 �2#..'"#/ ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�


�� ,. 2,)ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�,)1*#ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�'!#6�.#/'"#+0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�#+",. �#)#�/# �!&#"1)'+% ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,'!# �#!,%+'0',+ �+'0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�#+",. �!&#"1)'+% ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�'"#, �#40ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ,. 3� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�'0& ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�#'%&0/ �+" �#�/1.#/ ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,.( #+0#. ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


�� ,. 3�& ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�'0&&,)"'+% ÑÑÑÑÑÑ


ÑÑÑÑÑÑ��


�� ,. 3�'ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�'0&'+ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


�� ,. 3�, ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�'0&,10 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�,.( �."#.ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


B73.3.1 (6/99)A–38

��

��

��

��

��

��

��

��

��

��


��3 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�'0&&,)"'+% ��3 ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,.)" �.'0#.ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��


�5� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��%# �+" ��3 �0�0#*#+0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�5 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�*-),4##�/ �'0&&,)"'+% �)),25

�+!# �#.0'$'!�0#ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�5� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�3!#-0',+ �#-,.0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��4 �$0#. �10,$$ ÑÑÑÑÑÑÑÑÑÑÑÑ




�'"# �.#� �#02,.( ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��.+'+% ÑÑÑÑÑÑÑÑÑÑÑÑ




�,.( #+!&ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,.( �.#�(",2+ �0.1!01.# ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,.(*#+�/ �,*-#+/�0',+ �!0 ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,.( �')# ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,.(5'+5�.,!#// ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,.(5'+5�.,%.#//ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�( ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�##( ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��.#&,1/#� �,!�0',+� �,/0 �#+0#.ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��.#&,1/# ��+�%#*#+0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



��.#&,1/# ��+�%#*#+0 �4/0#*ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,.( �."#.ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�,.( �."#. �.,!#//'+% ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.'0# �+!#� �#�" ��+4ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�'+"$�)) �.,$'0 ��3 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�#'%&0 -#. �+'0 ,$ �#�/1.# ÑÑÑÑÑÑÑÑÑÑÑÑ



B73.3.1 (6/99) A–39

��

��

��

��

��

��

��

��

��

��


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�!0-)-' ÑÑÑÑÑÑ


ÑÑÑÑÑÑ�



�0)2%ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�%%*92.9$!2% ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



�(.�1 �(.� ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�.0+$ �0)2%0 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�.0+$ �)$% �%" ÑÑÑÑÑÑ


ÑÑÑÑÑÑ



�(!2 7.3 1%% )1 5(!2 7.3 '%2

��)887 �)'�




� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�0.11 ÑÑÑÑÑÑ


ÑÑÑÑÑÑ



�(.-% �62%-1).-ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



�9�%& ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�0.119�%&%0%-#% ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�0.11.4%0 ÑÑÑÑÑÑÑÑÑÑÑÑ


�



�%1��. ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


7$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�!0$ ÑÑÑÑÑÑ


ÑÑÑÑÑÑ



�%!09�-$ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�


�� .0 7+$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�)%+$ ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ




�%!0ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


�



�%!092.9�!2% ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


��



.-% �,/0.4%,%-2 �+!- ��.12!+

�.$%�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ



B73.3.1 (6/99)A–40

B73.3.1 (6/99) B–1

Appendix B - Field Sizes

The following list of field names and corresponding alias examples representscommonly used data types that appear in a form. The B’s represent the number ofcharacters you can have in alphabetical fields. For example, the field MCU (CostCenter) allows you to enter ‘ABCDEFGHIJKL’. The number of 8’s means the samething for numeric fields. For example, the field ICU (Batch Number) allows you toenter ‘12345678’.

The size column next to the B and 8 columns refers to the size the field should be indesign so you have enough room to enter and display the data correctly. For example,133 is the correct size for allowing you to enter the Cost Center details. Use thefollowing list as a guideline for placing and sizing controls.

Category Alias Description Application Field LocationÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�2#/%*��-#/4 ÁÁÁÁÁÁÁÁÁÁ

�� ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�/7 �2#/%*��-#/4 �+'-& ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�01 2+)*4 �02/'2 Á

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�&&2'33 �5.$'2ÁÁÁÁÁÁÁÁÁÁ

�� ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�/7 �&&2'33 �5.$'2 �+'-& +/%-5&+/) +/4'2/#-�'64'2/#- /5.$'23ÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�#4'ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

��ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�/7 �#4' �+'-&ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁ


�5#/4+47ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

��"ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�/7 �5#/4+47 �+'-&ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


ÁÁÁÁÁÁÁ�+.' ÁÁÁÁÁ

ÁÁÁÁÁ�� ÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁ�/7 �+.' �+'-& ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁ �� ÁÁÁÁÁ

ÁÁÁÁÁ �� ÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁ� � �*#2#%4'2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ




ÁÁÁÁÁÁÁÁÁÁÁ�� *#2#%4'2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ




ÁÁÁÁÁÁÁÁÁÁÁ� � �*#2#%4'2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


ÁÁÁÁÁÁÁ ��


��ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

� �*#2#%4'2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁ ��ÁÁÁÁÁÁÁÁÁÁ ��

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ � �*#2#%4'2

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁ


��ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


� �*#2#%4'2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


ÁÁÁÁÁÁÁ�.05/4 ÁÁÁÁÁ

ÁÁÁÁÁ��!� ÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁ�64'/&'& �034 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�(4'2 /+4 �034 Á


�0.1#/7 ÁÁÁÁÁÁÁÁÁÁ


�0.1#/7 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁ�.05/4 ÁÁÁÁÁ


ÁÁÁÁÁÁÁÁÁÁÁ�522'/%7 �6%*#/)' �#4' ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


ÁÁÁÁÁÁÁ�0%5.'/4 ÁÁÁÁÁ


ÁÁÁÁÁÁÁÁÁÁÁ�0%5.'/4 �5.$'2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


ÁÁÁÁÁÁÁ�0%5.'/4


��ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�0%5.'/4 �71'ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�(4'2 �0% �5.$'2��0 &'3%�

ÁÁÁÁÁÁÁÁÁ


�0%5.'/4ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


�'7 �0.1#/7ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�(4'2 �0% �71'��0 &'3%�ÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁ�0%#4+0/ ÁÁÁÁÁ


ÁÁÁÁÁÁÁÁÁÁÁ�0%#4+0/ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


ÁÁÁÁÁÁÁ�0%#4+0/ ÁÁÁÁÁ


ÁÁÁÁÁÁÁÁÁÁÁ�04 �5.$'2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�(4'2 �� Á


�0%#4+0/ ÁÁÁÁÁÁÁÁÁÁ


�5-, � �#/, �� ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁ


B73.3.1 (6/99)B–2

SizeApplication Field LocationDescriptionAliasCategoryÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�8%17-7;ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

!��!ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�8%17-7;ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

�


�7)0 �80&)5 ÁÁÁÁÁÁÁÁÁÁ"�!� ÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁ�7)0 �80&)5 � "1.1291 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�)*7 9-7, ()6'� %*7)5 ÁÁ

ÁÁ�


�02817 ÁÁÁÁÁÁÁÁÁÁ"�� ÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁ"1-7 �267 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�)*25) �:7)1()( �02817 ÁÁ

ÁÁ�


�)16-7; ÁÁÁÁÁÁÁÁÁÁ�� ÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁ�)16-7; ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�*7)5 !�� ÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�)16-7; !;3) ÁÁÁÁÁÁÁÁÁÁ��!� ÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁ�)16-7; !;3) ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�*7)5 ��2 ()6'� ÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�5)6685)ÁÁÁÁÁÁÁÁÁÁ#��

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

#%325 �5)6685)ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�*7)5 ��!�

ÁÁÁÁ

�ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ"1-7 2* �)%685)

ÁÁÁÁÁÁÁÁÁÁ��"

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�5)6685) "��

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�*7)5 #��2 ()6'�

ÁÁÁÁÁÁÁÁÁÁÁ


!)03)5%785)ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

��!�ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�)16-7; !)03)5%785)ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�*7)5 ��ÁÁÁÁÁÁÁÁÁÁÁÁÁ


!)03)5%785)

!;3)ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�!�" ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�)16-7; !)03)5%785) !;3) ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�*7)5 ��!��2 ()6'� ÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁ!)03)5%785) ÁÁÁÁÁ

ÁÁÁÁÁ��# ÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁ�� #%325 !)03)5%785) ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�*7)5 #�� ÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

!)03)5%785)

!;3)


!�"� ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

!)03)5%785) !;3) ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�*7)5 ��#��2 ()6'� ÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁ!)03)5%785) ÁÁÁÁÁ

ÁÁÁÁÁ!�� ÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁ!)03)5%785) ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


!)03)5%785)

!;3)


!�" ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

!)03)5%785) !;3) ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�*7)5 !��2 ()6'� ÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁ#2/80) ÁÁÁÁÁ

ÁÁÁÁÁ��# ÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁ�-48-( #2/80) ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�


"1-7 2* �)%685)ÁÁÁÁÁÁÁÁÁÁ�"�: ÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁ"�� ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�*7)5 #2/� �2 ()6'� ÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�255)'7-21 �%'<

725


#��ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

#2/80) �255)'7-21 �%'725ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁ$)-+,7

ÁÁÁÁÁÁÁÁÁÁ��$


�-48-( $)-+,7ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁ

�ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ#2/80)

ÁÁÁÁÁÁÁÁÁÁ��

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�0&-)17 #2/80)

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁ�ÁÁÁÁÁÁÁ


#2/80)ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

#��#ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

#%325 #2/80)ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁ

�


#2/80) ÁÁÁÁÁÁÁÁÁÁ�#�� ÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁ�7,)5 #2/80) ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


�


�8%17-7; ÁÁÁÁÁÁÁÁÁÁ !"� ÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁ 72'. !27%/ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�27 1250%//; 21 *250 ÁÁ

ÁÁ�


�8%17-7; ÁÁÁÁÁÁÁÁÁÁ !�� ÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁ 72'. #2/80) ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�*7)5 �� ÁÁ

ÁÁ�


$)-+,7 ÁÁÁÁÁÁÁÁÁÁ$�!� ÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁ$)-+,7 �)68/7 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�*7)5 !�� ÁÁ

ÁÁ�


�-1) �80&)5ÁÁÁÁÁÁÁÁÁÁ��


�2851%/ �175; �-1) �80&)5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁ


�%7', �80&)5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

��"ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�%7', �80&)5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁ"6)5 �� ÁÁÁÁÁ

ÁÁÁÁÁ" �� ÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁ"6)5 �� ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


�


�52+5%0 �� ÁÁÁÁÁÁÁÁÁÁ�� ÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁ�52+5%0 �� ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


�

B73.3.1 (6/99) C–1

Appendix C - Standard Verbs

Refer to this list for clarification and appropriate usage of verbs in business functions.If you want to submit a verb for approval, contact your application developmentmanager.

Accumulate - adds multiple lines, amounts that are displayed or updated to afile.

Add - sums numeric amounts (usually two values).

Calculate - evaluates more complex math expressions on MATH_NUMERICvariables.

Change - modifies the value of a variable or table.

Clear - erases the value of non-numeric fields so that they are blank.

Close - shuts down a particular function or table.

Compare - evaluates a variable against another variable or a variable to a tablevalue. Use this verb to return results on the compare condition without changingany of the variables.

Convert - changes an item from alpha to numeric and visa versa, and switchesbetween upper- and lower-case characters.

Copy - duplicates the contents of a variable into another variable.

Delete - removes the contents of a variable or field.

Edit - validates variable information or data for correctness, such as date ranges.

Format - formats a field for display, such as the Location field display.

Get - retrieves a value from a table to display or calculate.

Increment - increases the value of variable by a specified number, such as 1.This is useful for numbering lines.

Initialize - specifies the first value of a variable that does not contain blanks orNULL. You may hard code the value or retrieve it from another table orvariable. Also, use this to set MATH_NUMERIC values to zero.


B73.3.1 (6/99)C–2

Merge - used for string operations and to combine strings.

Replace - overwrites the value of a variable with another variable or tableelement.

Scrub - removes unnecessary or unwanted characters from a string.

Select - chooses a variable from a string of variables, based on screening rules.From a table, select chooses a record based on key values.

Set - updates the value of a table element to a certain value; used to set defaultvalues.

Start - calls a new application.

Update - modifies table data.

Verify - ensures that a specific variable conforms to system parameters, such asto verify that the GL period is open, or that an item is a stocked item.

Write - stores data in a table.

B73.3.1 (6/99) D–1

Appendix D - Standard Icons

Refer to this list for clarification and appropriate usage of icons in your applications.

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Bitmap Name

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Bitmap


Application(s)Present

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Represents

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Activity.bmp ÑÑÑÑÑÑÑÑÑÑÑÑ

P98800 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

An Activity in WorkflowÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

ACTIVITY_ESCALATION.BMPÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

P98800ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

An Activity with escalation inWorkflow

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

APPLICATION.BMP ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

P988820P98887

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Place holder in ActivEra


Archived.bmpÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

P012501ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Archived in Work Center


ATTPRIORITY.BMP ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

P012501 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

High priority message with an at-tachment in Work Center


BLUEPHONE.BMPÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Call in Work Center


BLUEPHONERINGING.BMP ÑÑÑÑÑÑÑÑÑÑÑÑ


Call back in Work Cneter


Bluetask.bmpÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Task in Work Center


BUILDOPTIONS.BMP ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


The build options set for the pack-age build


Company.bmpÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

P98616P98887


Where used in printer application.Place holder in ActivEra


COMPOSERAPPLICATION-SUITES_TREE.BMP



Application Suite in ActivEra


COMPOSERINDUSTRY_TREE.BMP ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Industries in ActivEra


COMPOSERPRODUCT_TREE.BMP ÑÑÑÑÑÑÑÑÑÑÑÑ


Products in ActivEra


DELETED ITEMS.BMPÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


(Looking at external mail) Mes-sages in Recycle bin in Work Cen-ter


B73.3.1 (6/99)D–2


Represents




Bitmap


Bitmap NameÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Emptycan.bmp


P012501


(Looking at external mail)EmptyRecycle bin in Work Center


EMPTYTRASH.BMP ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


(Looking at internal mail)EmptyRecycle bin in Work Center


Envelope.bmpÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Message in Work Center


Fini_att.bmp ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

P98CMP01 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Selected item with attachment inActivEra

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Finished.bmpÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

P98800P988820P98887P98CMP01

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Selected item


FULLTRASH.BMPÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


(Looking at internal mail)Full Re-cycle bin in Work Center


GREYPHONE.BMPÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Call in Work Center


GREYPHONERINGING.BMPÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Call back in Work Center


Greytask.bmp ÑÑÑÑÑÑÑÑÑÑÑÑ


Task in Work Center


Group.bmpÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


User groups in Work Center


HIGHPRIORITY.BMP ÑÑÑÑÑÑÑÑÑÑÑÑ


High priority mail in Work CenterÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Host.bmpÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Host


Hotmail.bmpÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Hot mail box in Work Center


Inbox.bmp ÑÑÑÑÑÑÑÑÑÑÑÑ


Inbox Work CenterÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

LIGHTNING.BMPÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

P012501P98CMP01


Active Mail Message in Work Cen-ter


LOWPRIORITY.BMP ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Low priority message in Work Cen-ter


Not_att.bmpÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

P98CMP01ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Not selected item with attachmentin ActivEra


Notapp.bmpÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

P98800P988820P98CMP01


Not selected item in ActivEra

Appendix D - Standard Icons

B73.3.1 (6/99) D–3


Represents




Bitmap


Bitmap NameÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Paper.bmp

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

P9601P98616P9621

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Paper Type in printer application


PARENTPRINTER.BMP ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


First level tree node in printer ap-plication


Pend_att.bmpÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Pending item with attachment inActivEra


Personal.bmpÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Pending item in ActivEra


Printer.bmp ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Printer in Printer application


Priority.bmp ÑÑÑÑÑÑÑÑÑÑÑÑ


Priority mailbox in Work Center


Process1.bmpÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Process in Workflow


Process2.bmp ÑÑÑÑÑÑÑÑÑÑÑÑ


Process in WorkflwoÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Prog_att.bmpÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

P98CMP01ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Progress item in ActivEra with at-tachment.


Progress.bmp ÑÑÑÑÑÑÑÑÑÑÑÑ

P98CMP01 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Progress item in ActivEraÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Promises.bmpÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Mailbox in Work Center


QUESTION2.BMPÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Place holder in ActivEra


Receipt.bmp ÑÑÑÑÑÑÑÑÑÑÑÑ


Receipt message in Work Center


Redphone.bmpÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Call in Work Center


REDPHONERINGING.BMP ÑÑÑÑÑÑÑÑÑÑÑÑ


Call back in Work CenterÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Redtask.bmp


P012501


Task in Work Center


SENT ITEMS.BMPÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Sent mailbox in Work Center


Start.bmp ÑÑÑÑÑÑÑÑÑÑÑÑ


Start Activity in WorkflowÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

SUBPROCESS.BMPÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Sub–process activity in Workflow


Todo.bmpÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


To do mailbox in Work Center


TREECLOSEPACKAGE.BMP ÑÑÑÑÑÑÑÑÑÑÑÑ


Package assembly is complete.


B73.3.1 (6/99)D–4


Represents




Bitmap


Bitmap NameÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

TREEDATABASE.BMP


P9601


The database items to be includedin the package build.


TREEFOUNDATION.BMP ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


The foundation system to be in-cluded in the package build


TREEHELPS.BMPÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


The Helps to be included in thepackage build


TREELANGUAGE.BMP ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


The language to be included in thepackage build


TREEOBJECTS.BMP ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


The objects to be included in thepackage build.


TREEOPENPACKAGE.BMPÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


The package assembly is still beingworked on.


TREEPROPERTIES.BMP ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

P9601P9621


The properties of the assembledpackage


Unop_att.bmp ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

P98CMP01 ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Unopened task in ActivEra with at-tachment


Unopen.bmpÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Unopened task in ActivEra


YELLOWPHONE.BMP ÑÑÑÑÑÑÑÑÑÑÑÑ


Call in Work CenterÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

YELLOWPHONERINGING.BMP


P012501


Call back in Work Center


YELLOWTASK.BMPÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


Task in Work Center

Glossary


B73.3.1 (6/99)

B73.3.1 (6/99)

Glossary

action message. With OneWorld, users can receivemessages (system-generated or user-generated) thathave shortcuts to OneWorld forms, applications,and appropriate data. For example, if the generalledger post sends an action error message to a user,that user can access the journal entry (or entries) inerror directly from the message. This is a centralfeature of the OneWorld workflow strategy. Actionmessages can originate either from OneWorld orfrom a third-party e-mail system.

alphabetic characters. Characters on the keyboardincluding letters of the alphabet and all othersymbols (such as *, &, #), but excluding numerals0 through 9. For example, “ABC*” is a string ofalphabetic characters, but “ABC123” is not. Alsoreferred to as an alpha character. Contrast withalphanumeric characters and numeric characters.

alphanumeric characters. The complete set ofcharacters on the keyboard including letters of thealphabet, symbols, and numerals. For example,“ABC*123” is a string of alphanumeric characters.Contrast with alphabetic characters and numericcharacters.

alternate language. A language other thanEnglish, which is designated in the user profile. Alanguage preference code is used to set thepreferred language for each user to display data foronline and printed output.

applet. A small application, such as a utilityprogram or a limited-function spreadsheet. It isgenerally associated with the programminglanguage Java, and in this context refers toInternet-enabled applications that can be passedfrom a Web browser residing on a workstation.

application. A computer program or set ofprograms used to accomplish a task. In OneWorld,there are interactive applications and batchapplications. Interactive applications are made upof a set of forms through which the user interactswith OneWorld. Interactive application identifiersbegin with “P.” For example, Address BookRevisions (P01012) is an interactive application.Batch applications run without user interaction.Reports and table conversions are examples of

batch applications. Batch application identifiersbegin with “R.” For example, the Print MailingLabels report (R01401) is a batch application.

application programming interface (API). Asoftware function call that can be made from aprogram to access functionality provided byanother program.

application server. A server in a local areanetwork (LAN) that contains applications used bynetwork clients.

application workspace. The area on a workstationdisplay in which all related forms within anapplication appear.

architecture. The underlying design of a computerthat defines data storage methods, operations, andcompatibility requirements with other systems andsoftware. It also refers to specific components of acomputer system, the way they interact with eachother, and the type of CPU chip that is used as thebasis of a computer system.

AS/400 common. The AS/400 library that typicallycontains WorldSoftware control files. Can alsorefer to as an AS/400 Common data source used inOneWorld.

AS/400 COMMON. A data source that resides onan AS/400 and holds data that is common to thecoexistent library allowing OneWorld to shareinformation with World.

asynchronous. A method of running tableconversions in which starting one conversion doesnot rely on another conversion’s successfulcompletion.

audit trail. The detailed, verifiable history of aprocessed transaction. The history consists of theoriginal documents, transaction entries, and postingof records and usually concludes with a report.

automatic accounting instruction (AAI). A codethat refers to an account in the chart of accounts.AAIs define rules for programs that automaticallygenerate journal entries, including interfacesbetween the Accounts Payable, AccountsReceivable, Financial Reporting, and General


B73.3.1 (6/99)

Accounting systems. Each system that interfaceswith the General Accounting system has AAIs. Forexample, AAIs can direct the General Ledger Postprogram to post a debit to a specific expenseaccount and a credit to a specific accounts payableaccount.

base release. The first generally available softwarefor a OneWorld release. See also release, releaselevel.

batch. A group of similar records or transactionsthat the computer treats as a single unit duringprocessing. For identification purposes, the systemusually assigns each batch a unique identifierknown as a batch number.

batch application. A single task or groups of tasksthat the system treats as a single unit duringprocessing. The computer performs batchapplications (jobs) with little or no user interaction.Printing reports and purging files are examples.

batch control. A feature that verifies the numberof transactions and the total amount in each batchthat you enter into the system.

batch input. A group of transactions loaded froman external source.

batch job. A task or group of tasks you submit forprocessing that the system treats as a single unitduring processing, for example, printing reportsand purging files. The system performs a batch jobwith little or no user interaction.

batch processing. A method by which the systemselects jobs from the job queue, processes them,and sends output to the outqueue. Contrast withinteractive processing.

batch server. A server on which OneWorld batchprocessing requests (also called UBEs) are runinstead of on a client, an application server, or anenterprise server. A batch server typically does notcontain a database nor does it run interactiveapplications.

batch type. A code assigned to a batch job thatdesignates to which system the associatedtransactions pertain, thus controlling which recordsare selected for processing. For example, the PostGeneral Journal program selects for posting onlyunposted transaction batches with a batch type ofO.

batch-of-one immediate. A transaction methodthat allows a client application to perform work ona client workstation, then submit the work all at

once to a server application for further processing.As a batch process is running on the server, theclient application can continue performing othertasks. See also direct connect, store-and-forward.

binary large object (BLOB). A database field thathas no maximum size limit and holds any digitizedinformation. This field is often used to storeobjects, such as graphical representations or datastructures, rather than standard alphanumeric data.

binary string (BSTR). A length prefixed stringused by OLE automation data manipulationfunctions. Binary strings are wide, double-byte(Unicode) strings on 32-bit Windows platforms.

broadcast message. 1) An e-mail message that yousend to multiple recipients. 2) A message thatappears on a form instead of in your mailbox.

browser. A client application that translatesinformation sent by the Worldwide Web. A clientmust use a browser to receive, manipulate, anddisplay Worldwide Web information on thedesktop. Also known as a Web browser.

business function. An encapsulated set of businessrules and logic that can normally be reused bymultiple applications. Business functions canexecute a transaction or a subset of a transaction(check inventory, issue work orders, and so on).Business functions also contain the APIs that allowthem to be called from a form, a database trigger,or a non-OneWorld application. Business functionscan be combined with other business functions,forms, event rules, and other components to makeup an application. Business functions can becreated through event rules or third-generationlanguages, such as C. Examples of businessfunctions include Credit Check and ItemAvailability.

business function event rule. Encapsulated,reusable business logic created using through eventrules rather than C programming. Contrast withembedded event rule. See also event rule.

business view. Used by OneWorld applications toaccess data from database tables. A business viewis a means for selecting specific columns from oneor more tables whose data will be used in anapplication or report. It does not select specificrows and does not contain any physical data. It isstrictly a view through which data can be handled.

Business View Design Aid (BDA). A OneWorldGUI tool for creating, modifying, copying, and

B73.3.1 (6/99)

printing business views. The tool uses a graphicaluser interface.

category code. A type of user defined code forwhich you can provide the title. For example, ifyou were adding a code that designated differentsales regions, you could change category code 4 toSales Region, and define E (East), W (West), N(North), and S (South) as the valid codes.Sometimes referred to as reporting codes. See alsouser defined code.

central objects. Objects that reside in a centrallocation and consist of two parts: the centralobjects data source and central C components. Thecentral objects data source contains OneWorldspecifications, which are stored in a relationaldatabase. Central C components contain businessfunction source, header, object, library, and DLLfiles and are usually stored in directories on thedeployment server. Together they make up centralobjects.

Central Objects merge. A process that blends acustomer’s modifications to the objects in a currentrelease with objects in a new release.

central processing unit (CPU). Computercomponent which carries out the logic, calculationand decision–making functions. Interprets andexecutes instructions upon receipt.

character conversion. The process of convertingcharacters of the same language from one encodingscheme to another while sending and receiving datain a heterogeneous environment.

character set. An ordered set of charactersrepresenting any particular language.

chart. OneWorld term for tables of informationthat appear on forms in the software. See forms.

chart of accounts. The structure for general ledgeraccounts. The chart of accounts lists types ofaccounts, describes each account, and includesaccount numbers and posting edit codes.

check-in location. The directory structure locationfor the package and its set of replicated objects.This is usually\\deploymentserver\release\path_code\package\packagename. The subdirectories underthis path are where the central C components(source, include, object, library, and DLL file) forbusiness functions are stored.

child. See parent/child form.

client. 1) A workstation or PC in a client/serverenvironment. 2) The receiving end of the spectrumin a request/supply relationship between programs.

client workstation. The computer on which a useroperates OneWorld software applications.

client/server. A relationship between processesrunning on separate machines. The server processis a provider of software services. The client is aconsumer of those services. In essence,client/server provides a clean separation of functionbased on the idea of service. A server can servicemany clients at the same time and regulate theiraccess to shared resources. There is a many-to-onerelationship between clients and a server,respectively. Clients always initiate the dialog byrequesting a service. Servers passively wait forrequests from clients.

cluster. A group of two or more servers withidentical configurations used to provide protectionagainst failure. If one server fails, the other cancontinue processing.

code page. An ordered set of characters in whichan alphanumeric value (code point) is associatedwith each character set.

code point. The numeric identifier assigned to acharacter. Its value is usually expressed in ahexadecimal notation.

coexistence. An AS/400 configuration of J.D.Edwards software that allows shared data interfaceoperation to occur between OneWorld andWorldSoftware.

commit. A process that ensures that all databasechanges for a single transaction occursimultaneously. The changes are treated as a singleunit; either all changes occur or none of thechanges occur, thereby maintaining the integrity ofthe database.

common object request broker architecture. Anobject request broker standard endorsed by theObject Management Group.

component object model (COM). A specificationdeveloped by Microsoft for building softwarecomponents that can be assembled into programs oradd functionality to existing programs running onMicrosoft Windows platforms. COM componentscan be written in a variety of languages, althoughmost are written in C++, and can be unpluggedfrom a program at runtime without having torecompile the program.


B73.3.1 (6/99)

Conference Room Pilot environment. AOneWorld environment used as a stagingenvironment for production data, which includesconstants and masters tables, such as companyconstants, fiscal date patterns, and item master. Usethis environment along with the test environment tomake sure your configuration works before yourelease changes to end–users.

configurable client engine. Allows user flexibilityat the interface level. Users can easily movecolumns, set tabs for different data views, and sizegrids according to their needs. The configurableclient engine also enables the incorporation of Webbrowsers in addition to the Windows 95- andWindows NT-based interfaces.

Configurable Network Computing (CNC). Anapplication architecture that allows interactive andbatch applications, composed of a single code base,to run across a TCP/IP network of multiple serverplatforms and SQL databases. The applicationsconsist of reusable business functions andassociated data that can be configured across thenetwork dynamically. The overall objective forbusinesses is to provide a future-proof environmentthat enables them to change organizationalstructures, business processes, and technologiesindependently of each other.

constants. Parameters or codes that you set andthat the system uses to standardize the processingof information by associated programs.

control. Any data entry point allowing the user tointeract with an application. For example, checkboxes, pull-down lists, hyper-buttons, entry fields,and similar features are controls.

Control Table Workbench. During the InstallationWorkbench process, Control Table Workbench runsthe batch applications for the planned merges thatupdate the data dictionary, user defined codes,menus, and user overrides tables.

Control Tables merge. A process that blends acustomer’s modifications to the control tables withthe data that accompanies a new release.

cumulative update. A version of OneWorldsoftware that includes fixes and enhancementsmade since the last release or update.

custom gridlines. A grid row that does not comefrom the database, for example, totals. To display atotal in a grid, sum the values and insert a customgridline to display the total. Use the systemfunction Insert Grid Row Buffer to accomplish this.

custom installation. One of the two types ofinstallations you can set up in the InstallationPlanner application. A custom installation gives thecustomer flexibility in creating a plan with Javaand Windows terminal servers, customenvironments, and custom data sources. See alsotypical installation.

custom modifications. Changes customers make toOneWorld to make the software run moreefficiently for them or to meet their particularrequirements.

customer. The company that purchases and usesOneWorld. A customer contains individual users.

data dictionary. A database table that OneWorlduses to manage the definitions, structures, andguidelines for the usage of fields, messages, andhelp text. J.D. Edwards has an active datadictionary, which means that it is accessed atruntime.

Data Dictionary merge. A process that updates acustomer’s data dictionary tables with the data thataccompanies a new release.

data mart. Department-level decision supportdatabases. They usually draw their data from anenterprise data warehouse that serves as a source ofconsolidated and reconciled data from around theorganization. Data marts can be either relational ormultidimensional databases.

data only upgrade. A process that preservescustomer business data when moving from aprevious release of OneWorld to a new release.This shortens the upgrade process by eliminatingthe need to perform the merges and tableconversions that incorporate J.D. Edwards data intoa customer’s existing data.

data replication. In a replicated environment,multiple copies of data are maintained on multiplemachines. There must be a single source that“owns” the data. This ensures that the latest copyof data can be applied to a primary place and thenreplicated as appropriate. This is in contrast to asimple copying of data, where the copy is notmaintained from a central location, but existsindependently of the source.

data server. A machine required for AS/400 userswho need to put central objects in SQL Server orOracle. Putting central objects on a data server tellsOneWorld they are not on the enterprise server.

B73.3.1 (6/99)

data source. A specific instance of a databasemanagement system running on a computer. Datasource management is accomplished throughObject Configuration Manager (OCM) and ObjectMap (OM).

Data Source Workbench. During the InstallationWorkbench process, Data Source Workbenchcopies all data sources that are defined in theinstallation plan from the Data Source Master andTable and Data Source Sizing tables in the Plannerdata source to the System – release number datasource. It also updates the Data Source Plan detailrecord to reflect completion.

data structure. A group of data items that can beused for passing information between objects, forexample, between two forms, between forms andbusiness functions, or between reports and businessfunctions.

data warehouse. A database used for reconcilingand consolidating data from multiple databasesbefore it is distributed to data marts fordepartment-level decision support queries andreports. The data warehouse is generally a largerelational database residing on a dedicated serverbetween operational databases and the data marts.

database. A continuously updated collection of allinformation that a system uses and stores.Databases make it possible to create, store, index,and cross-reference information online.

database administrator. The person who hasspecial skills or training in one or more types ofdatabase software, for example, SQL Server orOracle.

database driver. Software that connects anapplication to a specific database managementsystem.

database management system (DBMS). Acomputer program that manages data by providingcentralized control, data independence, andcomplex physical structures for efficient access,integrity, recovery, concurrence, control, privacy,and security.

database server. A server that stores data. Adatabase server does not have OneWorld logic.

default. A code, number, or parameter that thesystem supplies when the user does not specify one.

default. A value that the system assigns when theuser does not enter a value. For example, if thedefault value for an input is N and nothing is

entered in that field, the system assumes the defaultis an N value.

deployment environment. A OneWorldenvironment used to run OneWorld on thedeployment server. This environment administersinformation for the system data source, such as userprofiles, packages, and environments.

deployment server. The computer used to install,maintain, and distribute OneWorld software to oneor more enterprise servers and client workstations.

detail. The specific information that makes up arecord or transaction. Contrast with summary.

detail area. An area of a form that displaysdetailed information associated with the records ordata items displayed on the form. See also grid.

development environment. A OneWorldenvironment used to test modified developmentobjects before transferring them to the conferenceroom pilot environment.

direct connect. A transaction method in which aclient application communicates interactively anddirectly with a server application. See alsobatch-of-one immediate, store-and-forward.

director. A OneWorld user interface that guides auser interactively through a OneWorld process.

disk. A direct access storage device.

distributed computing environment (DCE). A setof integrated software services that allows softwarerunning on multiple computers to perform in amanner that is seamless and transparent to theend-users. DCE provides security, directory, time,remote procedure calls, and files across computersrunning on a network.

distributed database management system(DDBMS). A system for distributing a databaseand its control system across many geographicallydispersed machines.

Do Not Translate (DNT). A type of data sourcethat must exist on the AS/400 because of BLOBrestrictions.

double–byte character set (DBCS). A method ofrepresenting some characters using one byte andother characters using two bytes. Double-bytecharacter sets are necessary to represent somecharacters in the a Japanese, Korean, and Chineselanguages.


B73.3.1 (6/99)

double–byte enabled. A data storage feature thatallows a computer to store ideographic charactersfrom Asian languages. J.D. Edwards codingtechniques accommodate both ideographic andalphabetic characters, making it easier to translatean application into another language.

driver. A program or portion of a program thatcontrols the transfer of data from an input or outputdevice.

duplicated database. A decision support databasethat contains a straightforward copy of operationaldata. The advantages involve improvedperformance for both operational and reportingenvironments. See also enhanced analysis database,enterprise data warehouse.

dynamic link library (DLL). A set of programmodules that are designed to be invoked fromexecutable files when the executable files are run,without having to be linked to the executable files.They typically contain commonly used functions.

dynamic partitioning. The ability to dynamicallydistribute logic or data to multiple tiers in aclient/server architecture.

Electronic Data Interchange (EDI). Thepaperless, computer-to-computer exchange ofbusiness transactions, such as purchase orders andinvoices, in a standard format with standardcontent.

embedded event rule. An event rule that isspecific to a particular table or application.Examples include form-to-form calls, hiding a fieldbased on a processing option value, and calling abusiness function. Contrast with business functionevent rule. See also event rule.

Employee Work Center. This is a central locationfor sending and receiving all OneWorld messages(system and user generated) regardless of theoriginating application or user. Each user has amailbox that contains workflow and othermessages, including Active Messages. With respectto workflow, the Message Center is MAPIcompliant and supports drag and drop workreassignment, escalation, forward and reply, andworkflow monitoring. All messages from themessage center can be viewed through OneWorldmessages or Microsoft Exchange.

encapsulation. The ability to confine access to andmanipulation of data within an object to theprocedures that contribute to the definition of thatobject.

end user. An individual who uses OneWorldsoftware.

enhanced analysis database. A databasecontaining a subset of operational data. The data onthe enhanced analysis database performscalculations and provides summary data to speedgeneration of reports and query response times.This solution is appropriate when external datamust be added to source data, or when historicaldata is necessary for trend analysis or regulatoryreporting. See also duplicated database, enterprisedata warehouse.

enterprise. Every server, PC, and database that ison an organization’s network.

enterprise data warehouse. A complex solutionthat involves data from many areas of theenterprise. This environment requires a largerelational database (the data warehouse) that is acentral repository of enterprise data, which is clean,reconciled, and consolidated. From this repository,data marts retrieve data to providedepartment-level decisions. See also duplicateddatabase, enhanced analysis database.

enterprise server. A database server and logicserver. See database server. Also referred to as host.

Enterprise Workflow Management. A OneWorldsystem that provides a way of automating tasks,such as notifying a manager that a requisition iswaiting for approval, using an e-mail-based processflow across a network.

environment. A path code with a set of ObjectConfiguration Manager (OCM) mappings thatallow a user to locate data and a specific set ofobjects. Examples include Conference Room Pilot(CRP), development, production, and pristine.

Environment Checker. An application you can runbefore installing or upgrading OneWorld todiagnose configuration and setup issues that mayexist at the operating system level.

Environment Workbench. During the InstallationWorkbench process, Environment Workbenchcopies the environment information and ObjectConfiguration Manager tables for eachenvironment from the Planner data source to theSystem release number data source. It also updatesthe Environment Plan detail record to reflectcompletion.

Ethernet. A commonly used, shared media LANtechnology, which broadcasts messages to all nodes

B73.3.1 (6/99)

on the network segment. Ethernet connects up to1,024 nodes at 10MB per second over twisted paircable, coaxial cable, and optical fiber.

event. An action that occurs when an interactive orbatch application is running. Example events aretabbing out of an edit control, clicking a pushbutton, initializing a form, or performing a pagebreak on a report. The GUI operating system usesminiprograms to manage user activities within aform. Additional logic can be attached to theseminiprograms and used to give greaterfunctionality to any event within a OneWorldapplication or report using event rules.

event rule. Used to create complex business logicwithout the difficult syntax that comes with manyprogramming languages. These logic statementscan be attached to applications or database eventsand are executed when the defined event occurs,such as entering a form, selecting a menu baroption, page breaking on a report, or selecting arecord. An event rule can validate data, send amessage to a user, call a business function, as wellas many other actions. There are two types of eventrules:

1 Embedded event rules.2 Business function event rules.

executable file.

A computer program that can be run from thecomputer’s operating system. Equivalent terms are“application” and “program.”.

facility. An entity within a business for which youwant to track costs. For example, a facility mightbe a warehouse location, job, project, work center,or branch/plant. Sometimes referred to as abusiness unit.

field. 1) An area on a form that represents aparticular type of information, such as name,document type, or amount. 2) A defined areawithin a record that contains a specific piece ofinformation. For example, a supplier recordconsists of the fields Supplier Name, Address, andTelephone Number.

file. A set of information stored under one name.See also table.

file transfer protocol (FTP). A set of TCP/IPcommands used to log on to a network, listdirectories, and copy files. FTP is also acommunications protocol used to transmit fileswithout data loss.

find/browse. A type of form used to:1 Search, view, and select multiple records

in a detail area.2 Delete records.3 Exit to another form.4 Serve as an entry point for most

applications.

firewall.

A set of technologies that allows an enterprise totest, filter, and route all incoming messages.Firewalls are used to keep an enterprise secure.

fix/inspect. A type of form used to view, add, ormodify existing records. A fix/inspect form has nodetail area.

form. The element of the OneWorld graphical userinterface by which the user exchanges data withinteractive applications. Forms are made up ofcontrols, such as fields, options, and the grid. Thesecontrols allow the user to retrieve information, addand revise information, and navigate through anapplication to accomplish a task.

Form Design Aid (FDA). The OneWorld GUIdevelopment tool for building interactiveapplications and forms.

form interconnection. Allows one form to accessand pass data to another form. Forminterconnections can be attached to any event;however, they are normally used when a button isclicked.

form type. The following form types are availablein OneWorld:

1 Find/browse.2 Fix/inspect.3 Header detail.4 Headerless detail.5 Message.6 Parent/child.7 Search/select.

fourth generation language (4GL).

A programming language that focuses on what youneed to do and then determines how to do it.Structured Query Language is an example of a4GL.

general release. See release.

generic text structures. See Media StorageObjects.

graphical user interface (GUI). A computerinterface that is graphically based as opposed to


B73.3.1 (6/99)

being character-based. An example of acharacter-based interface is that of the AS/400. Anexample of a GUI is Microsoft Windows.Graphically based interfaces allow pictures andother graphic images to be used in order to givepeople clues on how to operate the computer.

grid. A control that displays detail information ona form. The grid is arranged into rows, whichgenerally represent records of data, and columns,which generally represent fields of the record. Seealso detail area.

header. Information at the beginning of a table orform. Header information is used to identify orprovide control information for the group ofrecords that follows.

header detail. A type of form used to add, modify,or delete records from two different tables. Thetables usually have a parent/child relationship.

headerless detail. A type of form used to workwith multiple records in a detail area. The detailarea is capable of of receiving input.

host. In the centralized computer model, a largetimesharing computer system that terminalscommunicate with and rely on for processing. Itcontrasts with client/server in that those users workat computers that perform much of their ownprocessing and access servers that provide servicessuch as file management, security, and printermanagement.

hypertext markup language (HTML). A markuplanguage used to specify the logical structure of adocument rather than the physical layout.Specifying logical structure makes any HTMLdocument platform independent. You can view anHTML document on any desktop capable ofsupporting a browser. HTML can include activelinks to other HTML documents anywhere on theInternet or on intranet sites.

index. Represents both an ordering of values and auniqueness of values that provide efficient accessto data in rows of a table. An index is made up ofone or more columns in the table.

inheritance. The ability of a class to recieve all orparts of the data and procedure definitions from aparent class. Inheritance enhances developementthrough the reuse of classes and their related code.

install. To load a full or partial set of OneWorldsoftware on a machine that has existing ornonexisting OneWorld software, such as install

OneWorld for the 0first time, install an upgrade, orinstall an update.

installation. The process of putting OneWorldsoftware on your computer for the first time. Anexample of an installation is B73.2. As inOneWorld Installation Guide.

Installation Planner. OneWorld program that runson the deployment server as a systemadministration tool. Installation Planner guides youthrough the installation setup process, includingdefining the enterprise server and deploymentplatform information, setting up environments, anddefining data sources.

Installation Workbench. OneWorld systemadministration program that allocates andconfigures software and resources on servers andworkstations according to the plan you created inInstallation Planner.

installer. The person who can perform most tasksand processes during a OneWorld installation,upgrade, or update.

integrated toolset. Unique to OneWorld is anindustrial-strength toolset embedded in the alreadycomprehensive business applications. This toolsetis the same toolset used by J.D. Edwards to buildOneWorld interactive and batch applications. Muchmore than a development environment, however,the OneWorld integrated toolset handles reportingand other batch processes, change management,and basic data warehousing facilities.

integration. A situation in which J.D. Edwardssoftware and the software of another companyaccess the same database.

integrity test. A process used to supplement acompany’s internal balancing procedures bylocating and reporting balancing problems and datainconsistencies.

interactive processing. Processing actions thatoccur in response to commands that you enterdirectly into the system. During interactiveprocessing, you are in direct communication withthe system, and it might prompt you for additionalinformation while processing your request.Contrast with batch processing.

interactive processing. A job the computerperforms in response to a command. Duringinteractive processing, the user communicatesdirectly with the computer, which may prompt the

B73.3.1 (6/99)

user to input additional information during theprocessing of a request.

Internet. The worldwide constellation of servers,applications, and information available to a desktopclient through a phone line or other type of remoteaccess.

Internet address. A specified path used to sendand receive messages on the Internet. The parts ofthe address identify the contact, company, and typeof business.

interoperability. The ability of different computersystems, networks, operating systems, andapplications to work together and shareinformation.

intranet. A small version of the Internet usuallyconfined to one company or organization. Anintranet uses the functionality of the Internet andplaces it at the disposal of a single enterprise.

IP. A connectionless communication protocol thatby itself provides a datagram service. Datagramsare self-contained packets of information that areforwarded by routers based on their address and therouting table information contained in the routers.Every node on a TCP/IP network requires anaddress that identifies both a network and a localhost or node on the network. In most cases thenetwork administrator sets up these addresses wheninstalling new workstations. In some cases,however, it is possible for a workstation, whenbooting up, to query a server for a dynamicallyassigned address.

IServer Service. Developed by J.D. Edwards, thisInternet server service resides on the Web server,and is used to speed up delivery of the Java classfiles from the database to the client.

J.D. Edwards Database. See JDEBASE DatabaseMiddleware.

Java. An Internet executable language that, like C,is designed to be highly portable across platforms.This programming language was developed by SunMicrosystems. Applets, or Java applications, can beaccessed from a Web browser and executed at theclient, provided that the operating system orbrowser is Java-enabled. (Java is often described asa scaled-down C++). Java applications are platformindependent.

Java application server. A server through which auser can interact with OneWorld applications usinga Web browser.

Java Database Connectivity (JDBC). Thestandard way to access Java databases, set by SunMicrosystems. This standard allows you to use anyJDBC driver database.

JDBNET. A database driver that allowsheterogeneous servers to access each other’s data.

jde.ini. J.D. Edwards file (or member for AS/400)that provides the runtime settings required forOneWorld initialization. Specific versions of thefile/member must reside on every machine runningOneWorld. This includes workstations and servers.

JDE.LOG. The main diagnostic log file ofOneWorld. Always located in the root directory onthe primary drive. Contains status and errormessages from the startup and operation ofOneWorld.

JDEBASE Database Middleware. J.D. Edwardsproprietary database middleware package thatprovides two primary benefits:

1. Platform-independent APIs formultidatabase access. These APIs areused in two ways:

a. By the interactive and batch engines todynamically generate platform-specificSQL, depending on the data sourcerequest.

b. As open APIs for advanced C businessfunction writing. These APIs are thenused by the engines to dynamicallygenerate platform-specific SQL.

2. Client-to-server and server-to-serverdatabase access. To accomplish thisOneWorld is integrated with a variety ofthird-party database drivers, such asClient Access 400 and open databaseconnectivity (ODBC).

JDECallObject. An application programminginterface used by business functions to invoke otherbusiness functions.

JDEIPC. Communications programming toolsused by server code to regulate access to the samedata in multiprocess environments, communicateand coordinate between processes, and create newprocesses.

JDENET communications middleware. J.D.Edwards proprietary communications middlewarepackage for OneWorld. It is a peer-to-peer,message-based, socket based, multiprocesscommunications middleware solution. It handlesclient-to-server and server-to-server


B73.3.1 (6/99)

communications for all OneWorld supportedplatforms.

job. A single identifiable set of processing actionsthat user directs the computer to perform. Jobs areinitiated by selecting menu options, enteringcommands, or pressing designated function keys.

job queue. A group of jobs waiting to be batchprocessed. See also batch processing.

just in time installation (JITI). OneWorld’smethod of dynamically replicating objects from thecentral object location to a workstation.

just in time replication (JITR). OneWorld’smethod of replicating data to individualworkstations. OneWorld replicates new records(inserts) only at the time the user needs the data.Changes, deletes, and updates must be replicatedusing Pull Replication.

landscape. A printer orientation for a page withgreater width than height. Contrast with portrait.

language preference code. An abbreviation thatidentifies the preferred language to be used for thetext for online and printed output. This code is usedin the user profile to designate the user’s preferredlanguage(s).

local area network (LAN). A short distancenetwork consisting of workstations, servers, a NOS,and a communications link. It is distinguished bythe absence of telecommunications service.

location. The method by which OneWorld managesthe organizational entities within an enterprise. Thedifferentiation between locations can be physical(for example, New York and Tokyo) or virtual (forexample, Headquarters and Accounting). Alocation is identified by a three-character locationcode, which is set up during OneWorld installation.

Location Workbench. During the InstallationWorkbench process, Location Workbench copiesall locations that are defined in the installation planfrom the Location Master table in the Planner datasource to the System data source.

log files. Files that track operations for a process orapplication. Reviewing log files is helpful fortroubleshooting problems. The file extension forlog files is .LOG.

master table. A database table used to store dataand information that is permanent and necessary tothe system’s operation. Master tables might containdata, such as paid tax amounts, supplier names,

addresses, employee information, and jobinformation.

media storage objects. Files that use one of thefollowing naming conventions that are notorganized into table format: Gxxx, xxxGT orGTxxx.

menu masking. A security feature that lets youprevent individual users from accessing specifiedmenus or menu selections.

menu merge. A process that blends a customer’smodifications to the menu tables with the data thataccompanies a new release.

merge. A OneWorld process that takes acustomer’s custom modifications and blends theminto the data that accompanies a new release.

Messaging Application Programming Interface(MAPI). An architecture that defines thecomponents of a messaging system and how theybehave. It also defines the interface between themessaging system and the components.

middleware. A general term that covers all thedistributed software needed to support interactionsbetween clients and servers. Think of it as thesoftware that’s in the middle of the client/serversystem or the “glue” that lets the client obtain aservice from a server.

modal. A restrictive or limiting interaction createdby a given condition of operation. Modal oftendescribes a secondary window that restricts a user’sinteraction with other windows. A secondarywindow can be modal with respect to it’s primarywindow or to the entire system. A modal dialogbox must be closed by the user before theapplication continues.

modeless. Not restricting or limiting interaction.Modeless often describes a secondary window thatdoes not restrict a user’s interaction with otherwindows. A modeless dialog box stays on thescreen and is available for use at any time but alsopermits other user activities.

multitier architecture. A client/server architecturethat allows multiple levels of processing. A tierdefines the number of computers that can be usedto complete some defined task.

named event rules (NER). Also called businessfunction event rules. Encapsulated, reusablebusiness logic created using event rules, rather thanC programming.

B73.3.1 (6/99)

National Language Support (NLS). Mechanismsprovided to facilitate internationalization of bothsystem and application user interfaces.

network addresses. A unique position assigned toa node operating in a network that other nodes usewhen communicating with it. For Ethernet andToken Ring network adapters, unique addresses areassigned at the factory and consist of a 6-byteaddress. Half of this address identifies the board’smanufacturer, while the last half is unique to theboard and is assigned when the board ismanufactured. Communication errors areprevented, because no two Ethernet or Token RingNICs will have identical addresses.

network computer. As opposed to the personalcomputer, the network computer offers (in theory)lower cost of purchase and ownership and lesscomplexity. Basically, it is a scaled-down PC (verylittle memory or disk space) that can be used toaccess network-based applications (Java applets,ActiveX controls) via a network browser.

network computing. Often referred to as the nextphase of computing after client/server. While itsexact definition remains obscure, it generallyencompasses issues such as transparent access tocomputing resources, browser-style front-ends,platform independence, and other similar concepts.

next numbers. A feature used to control theautomatic numbering of items such as new G/Laccounts, vouchers, and addresses. Next numbersprovides a method of incrementing numbers.

node. A termination point for two or morecommunications links. A node can serve as thecontrol location for forwarding data among theelements of a network or multiple networks, as wellas perform other networking and, in some cases,local processing.

normalized. In database management,normalization applies a body of techniques to arelational database in order to minimize theinclusion of duplicate information. Normalizationsignificantly simplifies query and updatemanagement, including security and integrityconsiderations.

numeric characters. Digits 0 through 9 that areused to represent data. Contrast with alphanumericcharacters.

object. A self-sufficient entity that contains data aswell as the structures and functions used tomanipulate the data. For OneWorld purposes, an

object is a reusable entity that is based on softwarespecifications created by the OneWorld toolset. Seealso Object Librarian.

Object Configuration Manager (OCM).OneWorld’s object request broker and the controlcenter for the runtime environment. It keeps trackof the runtime locations for business functions,data, and batch applications. When one of theseobjects is called, the Object Configuration Managerdirects access to it using defaults and overrides fora given environment and user.

object embedding. When an object is embedded inanother document, an association is maintainedbetween the object and the application that createdit; however, any changes made to the object arealso only kept in the compound document. See alsoobject linking.

Object Librarian. A repository of all versions,applications, and business functions reusable inbuilding applications. It provides check-out andcheck-in capabilities for developers, and it controlsthe creation, modification, and use of OneWorldobjects. The Object Librarian supports multipleenvironments (such as production anddevelopment) and allows objects to be easilymoved from one environment to another.

Object Librarian merge. A process that blendsany modifications to the Object Librarian in aprevious release into the Object Librarian in a newrelease.

object linking. When an object is linked to anotherdocument, a reference is created with the file theobject is stored in, as well as with the applicationthat created it. When the object is modified, eitherfrom the compound document or directly throughthe file it is saved in, the change is reflected in thatapplication as well as anywhere it has been linked.See also object embedding.

object linking and embedding (OLE). A way tointegrate objects from diverse applications, such asgraphics, charts, spreadsheets, text, or an audio clipfrom a sound program. See also object embedding,object linking.

object-based technology (OBT). A technologythat supports some of the main principles ofobject-oriented technology: classes, polymorphism,inheritance, or encapsulation.

object-oriented technology (OOT). Bringssoftware development past proceduralprogramming into a world of reusable


B73.3.1 (6/99)

programming that simplifies development ofapplications. Object orientation is based on thefollowing principles: classes, polymorphism,inheritance, and encapsulation.

OneWorld. A combined suite of comprehensive,mission-critical business applications and anembedded toolset for configuring thoseapplications to unique business and technologyrequirements. OneWorld is built on theConfigurable Network Computing technology, J.D.Edwards’ own application architecture, whichextends client/server functionality to new levels ofconfigurability, adaptability, and stability.

OneWorld application. Interactive or batchprocesses that execute the business functionality ofOneWorld. They consist of reusable businessfunctions and associated data that are platformindependent and can be dynamically configuredacross a TCP/IP network.

OneWorld object. A reusable piece of code that isused to build applications. Object types includetables, forms, business functions, data dictionaryitems, batch processes, business views, event rules,versions, data structures, and media objects. Seealso object.

OneWorld process. Allows OneWorld clients andservers to handle processing requests and executetransactions. A client runs one process, and serverscan have multiple instances of a process. OneWorldprocesses can also be dedicated to specific tasks(for example, workflow messages and datareplication) to ensure that critical processes don’thave to wait if the server is particularly busy.

OneWorld Web development computer. Astandard OneWorld Windows developer computerwith the additional components installed:

� �("�& ��

� ��

� ��"�%�'#% �� *�'� ��"�%�'#%��)�

�"� ��

� � *�'� �"'�%$%�'�)� �"� �$ ��'�#"

�#"'%# &��#%!�

open database connectivity (ODBC). Defines astandard interface for different technologies toprocess data between applications and differentdata sources. The ODBC interface is made up of aset of function calls, methods of connectivity, andrepresentation of data types that define access todata sources.

Open Systems Interconnection (OSI). The OSImodel was developed by the International

Standards Organization (ISO) in the early 1980s. Itdefines protocols and standards for theinterconnection of computers and networkequipment.

operating system (OS). The software that runs onthe hardware. For example, AIX 4.1 is a version ofan operating system.

Oracle. A relational DBMS from Oracle. Runs ona broad variety of computers, which allows data tobe entered and maintained on multiple hardwareplatforms.

output queue. See print queue.

package. OneWorld objects are installed toworkstations in packages from the deploymentserver. A package can be compared to a bill ofmaterial or kit that indicates the necessary objectsfor that workstation and where on the deploymentserver the installation program can find them. It isa point-in-time “snap shot” of the central objects onthe deployment server.

package location. The directory structure locationfor the package and its set of replicated objects.This is usually \\deploymentserver\release\path_code\package\ package name.The subdirectories under this path are where thereplicated objects for the package will be placed.This is also referred to as where the package isbuilt or stored.

Package Workbench. During the InstallationWorkbench process, Package Workbench transfersthe package information tables from the Plannerdata source to the System - release number datasource. It also updates the Package Plan detailrecord to reflect completion.

parallel release. A configuration of OneWorldsoftware that lets multiple release or update levelsrun in separate environments on the same machinefor testing, training, or development purposes. Forrelease levels running in parallel, no tables or dataare shared. For cumulative update levels running inparallel, system and server map data are shared.

parameter. A number, code, or character stringyou specify in association with a command orprogram. The computer uses parameters asadditional input or to control the actions of thecommand or program.

parent/child form. A type of form that presentsparent/child relationships in an application on oneform. The left portion of the form presents a tree

B73.3.1 (6/99)

view that displays a visual representation of aparent/child relationship. The right portion of theform displays a detail area in browse mode. Thedetail area displays the records for the child item inthe tree. The parent/child form supports drag anddrop functionality.

partitioning. A technique for distributing data tolocal and remote sites to place data closer to theusers who access. Portions of data can be copied todifferent database management systems.

path code. A pointer to a specific set of objects. Apath code is used to locate:

1. Central objects.2. Replicated objects.

plan. Refers to an installation plan. A plan is thestandard means for installing, upgrading, orupdating a OneWorld configuration. Plans, whichare used in various phases of installation, containinformation about data sources you will use,environments you will install, and packages.

planner environment. A OneWorld environmentin which you prepare the main components of aOneWorld configuration.

platform. The hardware, operating system, anddatabase on which your software is operating, forexample, an HP 9000 processor using HP-UX asthe operating system and Oracle as the database.

platform independence. A benefit of open systemsand Configurable Network Computing.Applications that are composed of a single codebase can be run across a TCP/IP network consistingof various server platforms and SQL databases.

polymorphism. A principle of object-orientedtechnology in which a single mnemonic name canbe used to perform similar operations on softwareobjects of different types.

port number. A numeric code that identifies aunique process for which a service can be providedon a machine.

portability. Allows the same application to run ondifferent operating systems and hardwareplatforms.

portrait. The default printer orientation for a pagewith greater height than width. Contrast withlandscape.

primary key. A column or combination of columnsthat uniquely identifies each row in a table.

print queue. A list of tables, such as reports, thatyou have submitted to be written to an outputdevice, such as a printer. The computer spools thetables until it writes them. After the computerwrites the table, the system removes the tableidentifier from the print queue.

pristine environment. A OneWorld environmentused to test unaltered objects with J.D. Edwardsdemonstration data or for training classes. Youmust have this environment so you can comparepristine objects that you modify.

process. A complete unit of work with a definedstart and end, which a computer performs. Someoperating systems, such as Windows NT, HP-UX,and AIX, track processes by assigning identifiers tothem. In Windows NT, a process is a runninginstance of an executable file.

processing option. A feature that allows you todirect the functions of a program. For example,processing options allow you to specify defaults forcertain forms, control the format in whichinformation prints on reports, and change howinformation appears on a form or in a report.

production environment. A OneWorldenvironment in which users operate OneWorldsoftware.

protocol. A set of formalized rules specifying howhardware and software on a network should interactwhen transmitting and receiving information.

published table. Also called a “Master” table, thisis the central copy to be replicated to othermachines. Resides on the “publisher” machine. theData Replication Publisher Table (F98DRPUB)identifies all of the published tables and theirassociated publishers in the enterprise.

publisher. The server that is responsible for thepublished table. The Data Replication PublisherTable (F98DRPUB) identifies all of the publishedtables and their associated publishers in theenterprise.

pull replication. One of the OneWorld methods forreplicating data to individual workstations. Suchmachines are set up as pull subscribers usingOneWorld’s data replication tools. The only timepull subscribers are notified of changes, updates,and deletions is when they request suchinformation. The request is in the form of amessage that is sent, usually at startup, from thepull subscriber to the server machine that stores the


B73.3.1 (6/99)

Data Replication Pending Change Notificationtable (F98DRPCN).

purge. The process of removing records or datafrom a system table.

push. Technology used to force information from acentralized server to another server or client.

push installation. A process that allows a systemadministrator to schedule the automatic installationof OneWorld on workstations.

push replication. A server-to-server method ofdata replication that notifies subscriber machineswhen a change is made to the publisher table. If thesubscriber machine is not running when thenotification is sent, the subscriber receives themessage at startup.

query by example (QBE). Located at the top of adetail area, it is used to search for data to bedisplayed in the detail area.

queue. A stored arrangement of computer data orprogram waiting to be processed in the order inwhich they were submitted. A queue may refer to aprint queue, job queue, or message queue.

record. A collection of related, consecutive fieldsof data that the system treats as a single unit ofinformation.

redundancy. Storing exact copies of data inmultiple databases.

referential integrity. Ensures that a parent recordcannot be deleted from the database when a childrecord for exists.

refresh. To modify OneWorld software, or subsetof it, such as a table or business data, so that itfunctions at a new release or cumulative updatelevel, such as B73.2 or B73.2.1.

regenerable. Source code for OneWorld businessfunctions can be regenerated from specifications(business function names). Regeneration occurswhenever an application is recompiled, either for anew platform or when new functionality is added.

relationship. Links tables together and facilitatesjoining business views for use in an application orreport. Relationships are created based on indexes.

release. A release of OneWorld regardless of anyupdates that might be applied. For example, theterm Release B73.2 refers generically to B73.2,B73.2.1, and B73.2.2. Sometimes referred to as ageneral release. See also base release, release level.

release level. A specific level of OneWorldsoftware. A release level is achieved by installing abase release and applying one or more updates. Arelease level also can be installed directly. See alsobase release, release.

release/release update. A “release” contains majornew functionality, and a “release update” containsan accumulation of fixes and performanceenhancements, but no new functionality.

replicated object. A copy or replicated set of thecentral objects must reside on each client andserver that run OneWorld. The path code indicatesthe directory where these objects are located.

replication. A copy of an object, usually a table ina relational database, which is placed in anotherlocation. As part of replication, the object mayundergo a transformation from one type of table,such as an Oracle table, to another, such as a TAMfile on a client machine.

Report Design Aid (RDA). The OneWorld GUItool for operating, modifying and copying reportbatch applications.

retrofitting. The process of integrating acustomer’s modifications into a new release ofOneWorld.

rollback. A process which changes data back to aprevious state after it has been committed to adatabase.

runtime objects. Packages of objects that aredeployed to any machine that will run OneWorld.

scalability. Allows software, architecture, network,or hardware growth that will support software as itgrows in size or resource requirements. The abilityto reach higher levels of performance by addingmicroprocessors.

scripts. A collection of SQL statements thatperform a specific task.

search/select. A type of form used to search for avalue and return it to the calling field.

security server. A dispatched kernel processrunning on a server for security validation. Asecurity server protects computer resources usingsecurity applications and redundant functionality.

server. Provides the essential functions forfurnishings services to network users (or clients)and provides management functions for networkadministrators. Some of these functions are storageof user programs and data and management

B73.3.1 (6/99)

functions for the file systems. It may not bepossible for one server to support all users with therequired services. Some examples of dedicatedservers that handle specific tasks are backup andarchive servers, application and database servers.

Server Administration Workbench. A OneWorldapplication that provides the server administratorwith vital statistics about the internal functions ofOneWorld.

Server Workbench. During the InstallationWorkbench process, Server Workbench copies theserver configuration files from the Planner datasource to the System release number data source. Italso updates the Server Plan detail record to reflectcompletion.

service. A type of Microsoft Windows NT processthat does not require anyone to be logged on to theoperating system. Examples are jdesnet.exe andjdesque.exe.

servlet. Servlets provide a Java-based solution usedto address the problems currently associated withdoing server-side programming, includinginextensible scripting solutions. Servlets are objectsthat conform to a specific interface that can beplugged into a Java-based server. Servlets are to theserver what applets are to the client.

single–byte character set (SBCS). An encodingscheme in which each alphabetic character isrepresented by one byte. Most Western languages,such as English can be represented using asingle-byte character set.

socket. A communications end point through whichan application sends or receives packets of dataacross a network. Also known as Berkley Socket,developed by the University of California atBerkley.

software action request (SAR). An entry in theAS/400 database used for requesting modificationsto J.D. Edwards software.

Specification merge. The Specification merge iscomprised of three merges: Object Librarianmerge, Versions List merge, and Central Objectsmerge. The merges blend customer modificationswith data that accompanies a new release.

Specification Table Merge Workbench. Duringthe Installation Workbench process, SpecificationTable Merge Workbench runs the batchapplications that update the specification tables.

specifications. A complete description of aOneWorld object. Each object has its ownspecification, or name, which is used to buildapplications.

specifications. A description of a OneWorld object,such as a table’s width and depth, placement offields, and fonts used.

spool. The function by which the system storesgenerated output to await processing.

static text. Short, descriptive text that appears nextto a control variable or field. When the variable orfield is enabled, the static text is black; when thevariable or field is disabled, the static text is gray.

store-and-forward. A transaction method thatallows a client application to perform work and, ata later time, complete that work by connecting to aserver application. This often involves uploadingdata residing on a client to a server. See alsobatch-of-one immediate, direct connect.

structured query language (SQL). A fourthgeneration language used as an industry standardfor relational database access. It can be used tocreate databases and to retrieve, add, modify, ordeleta data from databases. SQL is not a completeprogramming language because it does not containcontrol flow logic.

subscriber. The server that is responsible for thereplicated copy of a published table. Such serversare identified in the Subscriber Table.

subscriber table. The Subscriber table(F98DRSUB), which is stored on the PublisherServer with the Data Replication Publisher table(F98DRPUB) identifies all of the subscribermachines for each published table.

summary. The presentation of data or informationin a cumulative or totaled manner in which most ofthe details have been removed. Many systems offerforms and reports that summarize informationstored in certain tables. Contrast with detail.

synchronous. A method of running processes inwhich one process must finish before the next onecan begin.

system. A group of related applications identifiedby a name and a system code. For example, theAddress Book system code is 01. All applications,tables, and menus within a system can be identifiedby the system code.


B73.3.1 (6/99)

system administrator. The person who has accessto perform tasks such as issue signon names ormaintain security.

system code. A code that identifies a system, forexample, 01 for the Address Book system and 31for the Shop Floor Management system.

system function. A program module, provided byOneWorld, available to applications and reports forfurther processing.

table. In database environments, a two-dimensionalentity made up of rows and columns. All physicaldata in a database are stored in tables. See also file.

table. A two-dimensional entity made up of rowsand columns. All physical data in a database arestored in tables. A row in a table contains a recordof related information. An example would be arecord in an Employee table containing the Name,Address, Phone Number, Age, and Salary of anemployee. Name is an example of a column in theemployee table.

table. A file in OneWorld software.

table access management (TAM). The OneWorldcomponent that handles the storage and retrieval ofuser defined data. TAM stores information such asdata dictionary definitions; application and reportspecifications; event rules; table definitions;business function input parameters and libraryinformation; and data structure definitions forrunning applications, reports, and businessfunctions.

table conversion. During an upgrade or update,this process changes OneWorld technical andapplication tables to the format for the new release.

Table Conversion Workbench. During theInstallation Workbench process, Table ConversionWorkbench runs the table conversions that changethe technical and application tables to the formatfor the new release of OneWorld. It also updatesthe Table Conversions and Controls detail recordsto reflect completion.

Table Design Aid (TDA). A OneWorld GUI toolfor creating, modifying, copying, and printingdatabase tables.

table event rules. Use table event rules to attachdatabase triggers (or programs) that automaticallyrun whenever an action occurs against the table. Anaction against a table is referred to as an event.When you create a OneWorld database trigger, youmust first determine which event will activate the

trigger. Then, use Event Rules Design to create thetrigger. Although OneWorld allows event rules tobe attached to application events, this functionalityis application specific. Table event rules provideembedded logic at the table level.

TCP/IP. Transmission Control Protocol/InternetProtocol. The original TCP protocol was developedas a way to interconnect networks using manydifferent types of transmission methods. TCPprovides a way to establish a connection betweenend systems for the reliable delivery of messagesand data.

TCP/IP services port. Used by a particular serverapplication to provide whatever service the serveris designed to provide. The port number must bereadily known so that an application programmercan request it by name.

technical data. A type of OneWorld data sourcethat contains information about how OneWorldoperates.

technical tables. Tables used for technicalprocesses such as installation and upgrade ofOneWorld, in contrast with tables used byapplications.

Telnet. A terminal emulation protocol frequentlyused on the Internet that allows a user to log onand run a program from a remote computer. Telnetis part of the TCP/IP communications.

test environment. A OneWorld environment usedalong with the Conference Room Pilot environmentto test OneWorld software or the modificationsmade in the development path code before yourelease changes to the end user.

third generation language (3GL). A programminglanguage that requires detailed information abouthow to complete a task. Examples of 3GLs areCOBOL, C, Pascal and FORTRAN.

third–party. Describes other software that is usedin conjunction with J.D. Edwards software.

token. A bit configuration circulated amongworkstations, which lets workstation send data tothe network.

token ring. A LAN access mechanism in which allstations attached to a bus wait for a broadcast tokento be passed to them before they are able totransmit. However, though token-passingtechnology is in a physical ring, the next receivingstation might not be the next physical station.

B73.3.1 (6/99)

TP monitor. Transaction Processing monitor. Amonitor that controls data transfer between localand remote terminals and the applications thatoriginated them. TP monitors also protect dataintegrity in the distributed environment and mayinclude programs that validate data and formatterminal screens.

trace. A process that helps the user troubleshootproblems.

trigger. Allow you to attach default processing to adata item in the data dictionary. When that dataitem is used on an application or report, the triggeris invoked by an event associated with the dataitem. OneWorld also has three visual assist triggers:calculator, calendar and search form.

typical installation. One of the two types ofinstallations you can set up in the InstallationPlanner application. A typical installation is thequickest way to create an installation plan, becauseit uses all of the J.D. Edwards default informationfor environment and data sources. See also custominstallation.

uniform resource locator (URL). Names theaddress of a document on the Internet or anintranet. The following is an example ofURL:http://www.jdedwards.com. This is J.D.Edwards Internet address.

unnormalized. Data that is a random collection ofdata elements with repeating record groupsscattered throughout. Also see Normalized.

update. The process of refreshing OneWorldsoftware to a new release level, such as from B73.2to B73.3.

upgrade. The process of refreshing OneWorldsoftware to a new release level, such as from B73.2to B73.3.

user. An individual who uses OneWorld software.

user defined code (UDC). A code that users candefine, assign code descriptions, and assign validvalues. Examples of such codes areunit-of-measure codes, state names, and employeetype codes.

user defined code type. The identifier for a tableof codes with a meaning that you define for thesystem, such as ST for the Search Type codes tablein Address Book. OneWorld provides a number ofthese tables and allows you to create and definetables of your own.

User Defined Codes merge. The User DefinedCodes merge blends a customer’s modifications tothe user defined code tables with the data thataccompanies a new release.

user display preferences. A set of values thatrepresents a user’s preferred language, date format,decimal format, and other country specificconventions.

User Overrides merge. The User Overrides mergeadds new user override records into a customer’suser override table.

user profile. The predefined characteristicsrequired for each user. The user profile includes alibrary list, default print queue, and default jobqueue, as well as several other characteristics.

Versions List merge. The Versions List mergepreserves any non-XJDE and non-ZJDE versionspecifications for objects that are valid in the newrelease as well as their processing options data.

visual assist. Forms that can be invoked from acontrol to assist the user in determining what databelongs in the control.

vocabulary overrides. A feature that you can useto override field, row, or column title text on formsand reports.

wchar_t. Internal type of a wide character. Usedfor writing portable programs for internationalmarkets.

Web client. Any workstation that contains aninternet browser. The Web client communicateswith the web server for OneWorld data.

Web server. Any workstation that contains theIServer service, SQL server, Java menus andapplications, and Internet middleware. The Webserver receives data from the web client, and passesthe request to the enterprise server. When theenterprise server processes the information, it sendsit back to the Web server, and the Web server sendsit back to the Web client.

wide area network (WAN). A network thatextends beyond an area served by the dedicatedcommunication lines of a LAN and is capable ofcovering long distance. It is distinguished by therequirement that a phone company ortelecommunications provider be part of thetransmission.

workflow. According to the WorkflowManagement Coalition, worlflow means “the


B73.3.1 (6/99)

automation of a business process, in whole or part,during which documents, information, or tasks arepassed from one participant to another for action,according to a set of procedural rules.”.

workgroup server. A remote database serverusually containing subsets of data replicated from amaster database server. This server does notperformance an application or batch processing. Itmay or may not have OneWorld running (in orderto replicate data).

WorldSoftware Architecture. The broad spectrumof application design and programming technologythat J.D. Edwards uses to achieve uniformity,consistency, and complete integration throughoutits software.

Worldwide Web. A part of the Internet that cantransmit text, graphics, audio, and video. TheWorldwide Web allows clients to launch local orremote applications.

z file. For store and forward (networkdisconnected) user, OneWorld store-and-forwardapplications perform edits on static data and othercritical information that must be valid to process anorder. After the initial edits are complete,OneWorld stores the transactions in work tables onthe workstation. These work table are called Zfiles. When a network connection is established, Zfiles are uploaded to the enterprise server and thetransactions are edited again by a master businessfunction. The master business function will thenupdate the records in your transaction files.

Index


B73.3.1 (6/99)

B73.3.1 (6/99)

Index

Symbols

& symbol, use of when defining controls, A–1

A

Abbreviationsin reports, 2–30listed, A–1

About object naming conventions, 4–3Acronyms, list of, A–1Add mode

on fix/inspect form, 2–18on header detail, on headerless detail, 2–22tab sequence, 2–9

Additional selection criteriaform appearance, 2–16form tab, 2–12headerless detail form type, 2–16in B73.3, 2–17indicating on initial find/browse, 2–16initial find/browse form, 2–16nonstandard buttons, 2–17prior to B73.3, 2–16when to use, 2–16

Aliasdisplayed using mouse, 2–8used in an RPG program, 4–7

Applications, naming conventions, 4–19Associated text, for UDC controls, 2–7

B

Business functionnaming conventions, 4–24standard verbs, C–1

Business function data structures, namingconventions, 4–25Business view columns, for maximumperformance, 8–3

Business views, naming conventions, 4–18Buttons, standard, 6–3

C

Capitalize text, when to, 2–7Category codes

form tab, 2–12in B73.3, 2–17

Change modefix/inspect form, 2–18on header detail, on headerless detail, 2–22tab sequence, 2–9

Check box, placement of text, 2–6Checklist, application development, 2–3Coexistence

data item used in RPG program, 4–7indices and logicals, 4–17issues addressed in this guide, 4–7

Column space, between report columns, 2–30Column title, data item, 4–11Columns, limitation, 8–3Conditional sections, location of, 2–31Constant text, in reports, 2–30Constants, use of in report viewing, 2–31Control limitations, for maximum performance,8–3Cover page, report, 2–31Currency

applicable to all forms, 2–11code, exchange rate, base, 2–14controls, 2–18, 2–22currency mode, CRRM, 2–15displayed in grid, 2–14multiple currencies, 2–15on find/browse, 2–14on fix/inspect, 2–18on header detail, 2–22on headerless detail, 2–22single currency, 2–14when currency processing is OFF, 2–15when to hide fields, 2–15


B73.3.1 (6/99)

Currency fieldscurrency, exchange rate, base, foreign, 2–11in reports, 2–32

D

Data dictionary items, naming conventions,4–7Data Item, alias, 4–7Data item

column title, 4–11error message, 4–13name, 4–8processing option, 4–12row description, 4–11table I/O, 4–13workflow message, 4–12

Data item description, defined, 4–11Data item name, displayed using mouse, 2–8Data item prefix

and Business Partners, 4–9coexistence, 4–9used in OneWorld, 4–9

DialogIsInitialized, revisions log, 7–3Document information, how displayed, 2–6

E

ENDYOW, used as artificial filter field, 2–14Error message data item, naming conventions,4–13Event rule business functions, namingconventions, 4–24Event rule variables

naming conventions, 4–23used as work fields, 8–3

External data dictionary items, namingconventions, 4–8

F

Field, default size, 2–4Fields, currency, 2–11Filter, fiscal year, 2–8Filter controls, use of, 2–13

Filter fieldsdisplayed in grid, 2–13ledger and sub–ledger type, 2–8

Fiscal year filter, example of use, 2–8Font

size, 2–4standard for reports, 2–29

Form appearanceapplicable to all forms, 2–4find/browse, 2–12fix/inspect, 2–17header detail, 2–21headerless detail, 2–21message, 2–25parent/child, 2–23

Form functionapplicable to all forms, 2–8find/browse, 2–13fix/inspect, 2–18header detail, 2–21headerless detail, 2–21message, 2–25parent/child, 2–24

Form interconnections, naming conventions,4–20Form tabs

additional selections, 2–12category codes, 2–12form exits, 2–5presentation of, 2–6text, 2–5

Formsnaming conventions, 4–20resize, 2–4

G

Global variables, how defined, 4–30Grid

custom grid lines, 2–7filter fields, 2–13hidden columns, 2–9on a header detail, 2–21on a headerless detail, 2–21use of available space, 2–7when summing totals, 2–8when to preload, 2–13

Index

B73.3.1 (6/99)

Grid totals, font, color, size, use of symbol toindicate total, 2–6Grid variable, work field, 7–3Group box

around grid, 2–13around header fields, 2–12on fix/inspect form, 2–18use of, 2–12

H

Handle request, event rule variable, 4–23Header detail

currency, 2–22form appearance, 2–21form function, 2–21

Header fields, use of group box, 2–12Headerless detail

currency, 2–22form appearance, 2–21form function, 2–21

Help, F1, What’s this?, 2–9Hidden columns, placement of, 2–9Horizontal scroll bar, movement of, 2–9HRM

filter ENDYOW hidden AN8, 2–14when AN8 is filter, 2–14

Hungarian notation, example of, 4–23

I

Icons, standard, D–1Indices, naming conventions, 4–17Indices and logicals, coexistence, 4–17InitializeSection, revisions log, 7–3Input/Output, for maximum performance, 8–3Inquiry mode, fix/inspect form, 2–18

J

JDE custom system codes, 4–5Joined views, naming conventions, 4–19

K

Key fieldsdisabled in header, 2–18visible in header, 2–12, 2–21

L

Ledger and sub–ledger type, used as filterfields, 2–8Localization, applicable to all forms, 2–10

M

M&Ddisplaying LITM, AITM, ITM, 2–14placement of Branch/Plant, 2–10static text for MCU, MMCU, 2–10

Media objects, references to, 2–7Menu bar, 2–5

N

Named ER, naming conventions, 4–24Naming conventions

applications, 4–19business functions, 4–24business views, 4–18data dictionary items, 4–7data structures, 4–25error message data item, 4–13event rule business functions, 4–24event rule variables, 4–23external data dictionary items, 4–8for objects, 4–4form interconnections, 4–20forms, 4–20graphic, 4–4indices, 4–17joined views, 4–19named ER, 4–24object, 4–3OneWorld, 4–1processing option, 4–12processing option data structure, 4–21


B73.3.1 (6/99)

processing options, 4–21purge table, 4–30report event rule variables, 4–30table conversions, 4–28table I/O data item, 4–13tables, 4–16templates, versions, sections, globalvariables, 4–27text variables, 4–24workflow data item, 4–12workflow data structures, 4–25

Next number, do not preload, 2–8Nonvisible report sections

group section, 2–31report variables, 2–31

O

Object naming conventions, 4–3Overview, Application Design Standards, 1–1

P

Partners in development system codes, 3–1Performance considerations

all forms, 8–3find/browse, 8–5header detail, 8–7headerless detail, 8–7

Preload grid, when to, 2–13Preloading form

in add mode, 2–22in change mode, 2–22

Preloading next number, 2–8Processing option, naming conventions, 4–12Program and file names, 4–6

graphic, 4–6Purge table, naming conventions, 4–30

R

Radio button, placement of text, 2–6Report, cover page, 2–31Report appearance, checklist, 2–30

Report columnsappearance of, 2–30space between, 2–30

Report event rule variable, namingconventions, 4–30Report variables, displayed in report rendering,2–31Report viewing

checklist, 2–31reports to file, 2–32reports to output, 2–31

Reportscompany name, 2–29grand total, 2–30orientation, 2–30page information, 2–29paper size, 2–30printer, 2–30run time, 2–29titles, 2–29total amounts, 2–30use of page footers, 2–30use of report footers, 2–30versions description, 2–29

Reports to outputpage header, 2–31what a common report contains, 2–31

Resize, forms, 2–4Revisions log, use of, 7–3Row description, data item, 4–11Row exit, to a modeless form, 2–14, 2–21Row level browse exits, in a find/browse grid,2–14Row lines, on find/browse, 2–13

S

Section namesarranging for report rendering, 4–29description, 4–29

Size of alias, for use in an RPG program, 4–7Skip To, label for range or single item, 2–12,2–21Standard, icons, D–1Static text

font, color, point size, 2–4presenting reverse image, 2–6size for translation, 2–5

Index

B73.3.1 (6/99)

Stop Processing system function, for maximumperformance, 8–3System codes

for client objects, 3–1for JDE Custom work, 4–5J.D. Edwards, 4–5

T

Tab sequenceassigning, example, 2–9for a grid, 2–9

Table conversions, name, 4–28Table I/O

data item, 4–13event rule variable, 4–23

Tables, naming conventions, 4–16Templates

category codes, 4–27function use, 4–27name, 4–27

Temporary data storage, for maximumperformance, 8–3Text, standard for reports, 2–29Text variable, use of, 2–8, 7–3The J.D. Edwards system codes, 4–5The naming conventions for objects, 4–4Toolbar

on forms, icons, 2–5standard buttons, 6–3standard icons, D–1standard options, 2–4

Totals, use of group box, on a form, 2–8

U

UDC controls, associated text, 2–7Unit fields, minimum number of digits, 2–6Upper and lower case

for static text, for proper nouns, 2–7use of in reports, 2–30

V

Verbs, used in business functions, C–1

Versions, name, 4–28Versions naming conventions

called from menu, during install, masterversions, 4–28report, 4–28XJDE, 4–28ZJDE, 4–28

Viewing report sections, comment, 2–31Viewing reports

conditional sections, 2–31nonvisible report sections, 2–31

Visual assist, on search fields, on UDC fields,2–9Vocabulary overrides, use of, 2–7

W

Work field, using grid variable, 7–3Workflow data structures, naming conventions,4–25Workflow message, naming conventions, 4–12

X

XJDE, use of, 4–28

Z

ZJDE, use of, 4–28


B73.3.1 (6/99)

Documents

EnterpriseOne B73.3.1 Development Standards … · B73.3.1 (6/99) 1–1 Application Design Standards Overview The Application Design Standards guide is updated monthly. To ensure