MAINTAIN FUNCTIONS#
Functions are those user interface components or features which provide the business functionality of the product. As a result, they may be screen forms, processes, reports, utilities, menus, capabilities, tools, or procedures.
This section explains the Maintain Functions (IMFN) screen and its associated fields.
The Maintain Functions (IMFN) form describes each function within the system as well as defaults that are used elsewhere.
This screen allows you to control the individual functions within the application. All functions must have their execution rights defined for users or roles in order for those functions to be accessed. You can indicate whether a specific user or role may create, retrieve, update or delete data within a function.
This screen also allows you to indicate the purpose of the function, attach HTML files and control other features such as print orientation and function type.
There are two types of functions:
| Internal Function | The main purpose of an Internal Function is to allow you to create, view, edit and delete your company’s information within the application. For example, all the individuals who will be using the application are maintained as a list of users through the Maintain Users (IMUS) screen. In addition, these internal functions allow you to customize some of the structure of the application to suit your company’s needs. You can indicate how information will be presented and who will be able to access or edit this information. |
| External Function | External Functions are links to either external web pages or to documents stored outside of the application. For example, you may have a company policy that you would like to have accessible on the application. You can create a new function which points the application to that document so that users may view it online. |
The function table data is provided by High LineMcKesson, although certain options may be tailored by the system administrator, and new custom functions (e.g. procedures) may be added. Typically, there is no modification of provided functions and they should not be changed unless directed to do so by Support. Security is defined at the function level. A user must be granted execution rights to the function to be able to access it.
The definition data for the Maintain Functions screen is stored in the P2K_AM_FUNCTIONS, P2K_AM_EXECUTION_RIGHTS, P2K_AM_PREFERENCE_VALUES and P2K_CM_CHANGE_REASON_USAGES tables
- Product
- Function Name
- Description
- Description (FRE)
- Function Type
- Usage
- Computer Language
- Destination Format
- Function Style
- Subject Table
- Find LOV
- Extends
- PL/SQL Logic
- Web Address
- Implementation Name
- Where to Run
- Function Level
- PA Type
- Create Allowed
- Retrieve Allowed
- Update Allowed
- Delete Allowed
- Purpose
- Copy Function and Form
Execution Rights tab #
The Execution Rights tab allows you to grant specific users or roles access to the function and to define in what capacity.- Role or User
Preferences tab#
The Preferences tab allows you to add features to the function, such as headers or footers.- Preference
- Priority
- Value
Add OPEN IN SAFEMODE
You must create an HTML file and save that file in the document folder on your application server.
e.g. oracle/ias_903/j2ee/home/applications/selfService/HLApplication/doc/file.html
Once the file has been saved, you will indicate the folder, file name and extension; there is no need to include the path up to the application folder.
e.g. doc/file.html
Both the file name and extension must be entered with the exact spelling and case as indicated in the document folder .
`Preference' and 'Value' are mandatory fields that must be completed when you are creating a new record.
Change Reasons tab #
- Change Reason
- Description
