Function Security defines the specific access to individual forms and the business functions of each form. A form can have several business functions associated with it, however some forms and functions may not be appropriate for each user. Purchasing provides the following basic responsibilities: Requestor, Receiver, Buyer, and PO Superuser. You can create new responsibilities or modify the existing ones. A responsibility defines an application user's current privileges while working with Oracle Applications.
You can use Function Security to control access to forms (windows) and functions within windows, thereby tailoring each responsibility to the needs of an individual user. However, if you grant a user access to a window, all the functions within that window are automatically included in the user's access. If you want the user to have access to the window but not to all the window's functions, you must exclude access to each function individually.
For example, if you want a user to be able to view the Purchase Orders Summary window but not have access to the functions associated with the New Release, New PO, and Open buttons within that window, you would grant access to the Purchase Orders Summary window but disable access to the New Release, New PO, and Open functions.
The following table lists examples of functions available in common Oracle Purchasing windows.
| Window | Function | Requestor | Receiver | Buyer | PO Superuser |
|---|---|---|---|---|---|
| Requisition Summary Tools Menu | View Lines Distributions Purchase Orders Sales Orders Action History Preferences Control | X | X | X | |
| Requisition Summary window | New | X | X | X | |
| Purchase Order Summary window | New Release New PO Open Buttons | X | X | ||
| Purchase Order Summary Inquire Menu | View Lines Shipments Distributions Action History Invoices Receipts | X | X | X | X |
| Purchase Order Summary Tools Menu | Acceptances Control Preferences Manage Global Agreements | X | X | ||
| Supplier Summary window | Open | View Only | X | ||
| Supplier Summary window | New | X | |||
| Exceeded Price Tolerances window | Accept/Reject | View Only | View Only | View Only | View Only |
Oracle Purchasing provides the following view menus for Buyer Work Center views:
View Purchasing Documents (PO_VIEW_PURCHASING_DOCUMENTS):
The submenu associated with this menu is Purchasing Buyer Home Page Read Only view. The functions associated with this menu are PO Orders Summary Page For Read Only View and PO View Agreements Summary Page For Read Only View.
This menu enables buyers to view all details of purchase orders and agreements. Purchasing administrators can assign this menu to users such as requesters or project managers who do not have access to the Purchasing responsibility to view purchasing documents. Users assigned this menu can only view documents and cannot perform any update actions.
The following view actions are available for purchase orders:
View Acknowledgments
View Acquisition Cost
View Action History
View Approval Workflow
View Change History
View Invoices
View PDF
View Payments
View Receipts
View Requisitions
View Revision History
The following view actions are available for agreements:
View Acknowledgements
View Action History
View Approval Work Flow
View Change History
View PDF
View Revision History
The view actions that appear in the Actions list in the Standard Purchase Order or Agreements page depend on the status of the purchase order or agreement. By default, this menu is associated with the Purchasing SuperUser GUI (PO_SUPERUSER_GUI) and Purchasing Buyer Work Center (PO_BUYER_WORK_CENTER) menus. If enterprises use custom Purchasing menu, then they must grant this menu to the custom responsibility to enable buyers to view purchasing documents from Buyer Work Center.
Non-CLM Views (PO_VW_FUNCTIONS): The Non-CLM Views menu groups the functions that enables access to the predefined views in the Buyer Work Center. Purchasing administrators can use this menu to control access to predefined views. For example, access to the existing predefined views such as “My In Process Orders” or “My Incomplete Orders” can be granted or revoked using this new menu. The Non-CLM Views (PO_VW_FUNCTIONS) menu is associated by default with the predefined Purchasing SuperUser GUI (PO_SUPERUSER_GUI) and Purchasing Buyer Work Center (PO_BUYER_WORK_CENTER) menus. If enterprises use the custom Purchasing responsibility, then they must grant the Non-CLM Views (PO_VW_FUNCTIONS) menu to the custom responsibility. Otherwise, views in Buyer Work Center cannot be accessed.
Depending on your business requirements, you can enable certain authorized users to delete pending or running ROI transactions from the Transaction Statuses window. For information about transaction statuses, see: Viewing Transaction Status Information
To enable users to delete pending or running ROI transactions, you must set the P_ALLOW_DELETE form parameter function to Yes for the predefined View Transactions Status GUI (RCVTXVTX) form or the custom function that you use.
Navigate to the Form Functions window.
Search for the View Transactions Status GUI (RCVTXVTX) form or the custom function that you use.
Set the form parameter as P_ALLOW_DELETE=Y in the Parameters field to enable deletion of Pending or Running transaction line rows.
When deleting a transaction record, the application deletes:
The Receiving Headers Interface (RHI) transaction data only if is not related to the Receiving Transactions Interface (RTI).
The parent RTI transaction data only if all its child transactions have been deleted. When users try to delete a parent transaction for which child transactions exist, an error message appears. This message informs users that the current transaction cannot be deleted as child transactions exist for the parent transaction.
If Oracle Yard Management System (YMS) is licensed and installed, you can enable users to split ASN lines and update ASN trailer SCAC and Equipment Number using the Split Line window. The Split Line window appears when the P_ALLOW_YMS_UPDATE form function parameter is set to Y. For more information, see: Managing Shipments
To enable the Split Line window:
Navigate to the Form Functions window.
Search for the Manage Shipments function (RCV_RCVSHESH).
Set the form parameter as P_ALLOW_YMS_UPDATE =Y in the Parameters field to enable the Split Line window.
Related Topics
Overview of Function Security, Oracle E-Business Suite Security Guide
Forms and Subfunctions, Oracle E-Business Suite Security Guide
Overview of Oracle Application Security, Oracle E-Business Suite Security Guide