Function security is the mechanism by which user access to applications functionality is controlled. System administrators
administer function security.
Access to Work in Process functionality is controlled either by menus and form functions/subfunctions or by form function parameters.

Form Function Parameters
Some Work in Process forms are coded to accept particular parameters.
Parameters can be used to limit access to form elements such as:

•  Window options
•  Tools menu options
•  Buttons

The syntax for entering form function parameters is:
PARAMETER = VALUE
For example, to enter a negative Boolean parameter value for the WIP_WIPDJMDF_CLOSE function, you would enter the following in the Parameters field in the Form Functions window:
UNCLOSE = N
The following table describes the Work in Process form function parameters. All values are either Y (Yes) or N (No). A detailed description of each form function parameter follows the table:

 

Move Transactions: Allow Skipping Over No Move Statuses
Determines whether you can override ‘no move’ shop floor statuses when performing a move transaction. If the WIP Allow Moves Over No Move Shop Floor Statuses parameter is set to N and this function security parameter (OVERRIDE_NO_MOVE_NO_SKIP) is set to Y, you can move assemblies over no move shop floor statuses.
The default for this option is N.

Move Transactions: No Completion Transactions
Determines whether you can perform assembly completion and return move transactions using the Move Transactions window. When this function security parameter (ALLOW_CMP) is set to N, the Complete and Return options do not appear in the Transaction Type region of the Move Transactions window.

Move Transactions: No Resource Transactions
Determines whether you can initiate a manual resource transaction from the Move Transactions window. When this function security parameter (RESOURCE_TXNS) is set to N, the Resources button does not appear in the Move Transactions window. The default for this option is Y.

Completion Transactions: No Final Completions
Determines whether you can perform WIP final completions in an average costing organization. When this function security parameter (ALLOW_FINAL_ COMPLETIONS) is set to N, the Final Complete check box does not appear in the Completion Transactions window.

Function Security
A form function invokes an Oracle Forms form. A non–form function (subfunction) is a securable subset of a form’s functionality: in other words, a function executed from within a form. When the subfunction associated with a certain functionality is included in a menu, that functionality is enabled.

The following table describes the subfunction used in Work in Process. A detailed description of each function (subfunction) follows the table:

Allow Overcompletions
You can complete more assemblies than have been defined for discrete jobs and repetitive schedule.