41
17-8 Oracle E-Business Suite Developer's Guide
Purchase Orders
Purchase Orders (<-Purchase Orders Gateway)
View Expiring Purchase Orders
Mass Delete Purchase Orders
Quotes
Suppliers
Setup
Reports
Reports versus Processes
If you create separate instances of the Submit Requests form to launch specific processes
(programs) or groups of processes, place that form function under the appropriate
object-based name in your menu. (A process is a program that manipulates data, rather
than a report that only sorts or displays the data.)
In the above example, the "Mass Delete Purchase Orders" menu entry might open a
specialized Submit Request window to launch the Mass Delete Purchase Order
standard request submission program. Since this process deletes data, it appears under
the Purchase Order menu entry rather than the Reports menu entry.
Multi-row and Single-row Displays
When you have both a multi-row and a single row display of data in a form (usually in
a combination block), title the multi-row window and associated menu entry using the
plural of the entity name followed by "Summary", for example: "Purchase Orders
Summary". Title the single-row window (and the associated menu entry, if there is one)
with the plural of the entity name, for example: "Purchase Orders". If you have only a
single-row version of a form, the form name and associated menu entry are simply the
plural of the entity name, for example: "Purchase Orders".
Form Function Standards
Function Names and User Function Names
The user function name (which is defined using the Form Functions form, and which is
the selection value in the LOV on the Menus form) is simply the form name, for
example: "Purchase Orders". It is important to follow these user function naming
standards, since end users see user function names in the Navigator window's Top Ten
List.
Create function names (not user function names) as:
<APPLICATION_SHORTNAME>_<FORMNAME>_<MODE>. <MODE> is optional; use
it if there are several functions that reference the same form. If you create a function that
references a form in another product, use your products shortname as the application
shortname. For example, WIP_FNDRSRUN_AUTOCREATE.
Never begin a user function name with a number, such as "2-Tier Pricing Structure",
since the number would conflict visually with the Top Ten List in the Navigator
window. Menu entry prompts should not have numbers anywhere in them, because the
