Wiki source code of 21.1.4 User Roles

Content
Hide line numbers
  1: {{include document="zHeader"/}}
  2: 
  3: =User Roles=
  4: The User Roles section defines the system **access permissions and responsibilities** for the user.
  5: [[image:WebHome@fig 21.5.png]]
  6: 
  7: * **Requisitioner:  **the** **user** **can create a requisition by adding items from catalogues, punch-out sites, recurring requisitions and e-forms. Enables additional requisitioning roles to be selected.
  8: The following roles are conditional on ‘Requisitioner’ being selected:
  9: ** **Blanket Requisitioner:** can create blanket orders.
 10: ** **New Address Entry:** can create a //**new**//** **//Delivery Address// during the requisitioning process. (Note. All users have a default Delivery Address that they may override in the Requisition Details** **browser page from the system address book).
 11: ** **Non-Catalogue  Entry:** can order non-catalogue based services or goods. This role will make the ‘Add non-catalogue item’ button appear in the requisition screen.
 12: ** **User-Defined Supplier Entry:** this button will be available only if ‘Non-Catalogue Entry’ is selected. The User has the permission to create// “ad hoc” //suppliers in the ‘Add Non-Catalogue item’ screen.
 13: ** **Pre-Authorisation Allowance Override:** applies only to users of GECF ePCard XML (available only in the USA). The user is allowed, on a GECF ePCard, to override the allowance amount given to the supplier on a PCard transaction. Typically, this is to cover items such as tax and delivery charges; a user who has this ability is, in effect, granted permission to allow the supplier to charge extra tax and delivery.
 14: ** **Selectable Supplier Terms:** the user can select the following alternate supplier terms in the //Order Delivery and Invoicing// screen, where available, for:
 15: *** Payment Terms
 16: *** FOB terms
 17: *** Delivery Terms
 18: ** **Personal Templates Only:** when selected this will hide all Group assigned templates from the user's Templates table and ensure that they only see Private and User assigned Templates. This therefore removes Templates that are potentially irrelevant and is especially useful for Mobile users where screen size is more limited.
 19: * **VAT Override:** this permission allows a user to change the VAT Treatment default assignment on their requisitions. This would normally only be given to a user who has specific knowledge about VAT Treatment. User specified VAT will override any system generated defaults linked to either business rule group or commodity type.
 20: * **Batch Requisitioner: **The system accepts requisitions generated from internal or external processes (supporting batch feeds from materials management and inventory systems for example, or from such internal processes such as scheduled recurring requisitions). If selected, the user will be authorised to use these external requisitions and check the status of them in the Status and Order Tasks page. Typically only one user (a system login) will be granted this permission, and will possess few others.
 21: * **Receiver:** the user can access the **receiving page** for each order they have access to and update a requisition with receiving information. The receive link appears in the status search results page. A requisitioner can always receive their own orders.
 22: ** **Edit Receipts:** This button will be available only if the ‘Receiver’ role is selected. This role allows a user to edit receipts after they have been entered and saved. Note that a receipt cannot be edited once it has been included in the ReceiptReturn Export or an order has been closed.
 23: * **Invoicer:  **the user can access Invoice entry permissions: **Invoice Entry page **- for entering invoice documents against purchase orders. Access to the invoice entry page is granted through an invoice icon in the status search results page and a button in the purchase order status summary page. **Invoice Detail** – allowing access to the invoice detail screen where financial tracking code editing can be undertaken.
 24: ** **Remit Address Entry: **this option is only available for selection if the ‘invoicer’ role has first been selected. The user is allowed to select or change a remittance address in the invoice entry forms.
 25: * **Non-PO Invoice: **the user can access** Non-PO Invoice** **Entry** - allowing the posting of //ad hoc// invoice documents that are not associated to a PECOS P2P purchase order. Access to Non-PO Invoice is granted through an option on the main menu bar.
 26: * {{id name="user_roles_settlement"}}{{/id}} **Settlement:** this option gives access to all settlement activities as described below.
 27: * **Settlement Resolution screen** – where all settlement activities can be undertaken and matching results and statuses reviewed. Access is via a settlement icon in the status search results screen.
 28: ** **Invoice Deactivation** – allowing the deactivation of existing invoices that have not been sent to APExport.
 29: ** **Close Orders** – allowing the ability to manually close an order.
 30: ** **AP inquiry** – allows a user to access the ‘AP Inquiry’ screen where an order can be ‘Closed in AP’.
 31: ** **Force Settlement: **this option is only available for selection if the ‘Settlement’ role has first been selected. This allows a user to run the force settlement program for any order that is placed on a financial matching exception status.
 32: * **Administrator: **this has a number of functions:
 33: ** The user is a system administrator. Administration rights are granted in the Administrator Security screen.
 34: ** The user is granted permission to run the batch export utilities.
 35: ** Run Financial Matching – the ability to run the financial matching program. Financial matching can be performed for all orders in organisations that the user has access to through their //order access level //(see ‘groups and roles’ below). Access is granted through a button on the status search results screen (which runs matching for ALL available orders within the user’s permissions) and a button on the settlement resolution screen (which runs matching for the individual order only).
 36: ** An administrator is granted permissions to cancel any purchase order.
 37: * **Purchase Order Change Access:** The user can create __change__ orders in the Purchase Order Status Summary screen. This permission also allows users to __cancel__ order requests and purchase orders which they may have access to. See below for further information.
 38: 
 39: * **Approval Delegation:** this button allows the user to delegate their approval responsibility to any other PECOS P2P user. It enables the **approval delegation** button to be displayed in the user’s inbox which allows access to the approval delegation screen. Note that this role does //not //specify the user as an approver, nor does it validate the user as a person for whom approval can be delegated. The users who are available as delegatees will be defined by the user’s Order Access permissions: only those users who belong to these organisations will be available for selection.
 40: * **Bypass Approval Level:** use this setting to identify the user to a managerial or approval hierarchy. The numerical setting is used with the approval plan criteria: ‘Requestors Approval Level’. Principally this is used to define when an approval step is to be by-passed by requesting approval only if a user’s bypass level is greater or less than a particular value. For example you may not require certain managers, who also buy through PECOS P2P, to have their requisitions approved by themselves or a subordinate. The levels are configured by your Elcom Consultant or Elcom Support.
 41: 
 42: Bypass levels are created for the top level of your organisation only and cannot be altered for subordinate organisation levels.
 43: 
 44: * **Punch-in User:** this role is used when PECOS P2P is operated as a catalogue system and the user is an externally maintained profile setup for the purposes of punch-in from an external ordering system to create a requisition (and then punch-back to the external ordering system).
 45: * **Active User/ Inactive User: **designating an** Inactive User **deactivates the user profile and** **prevents access to PECOS P2P. An inactive user can later be reactivated. Note that a user profile cannot be deleted.
 46: 
 47: =Purchase Order Change Permission=
 48: 
 49: User permissions to purchase order **change** is altered slightly by a combination of the user profile role setting (described above) and the supplier profile contacts settings (described in an earlier chapter above). The table below summarises the change order (i.e. post order transmission) functionality granted to the user based on the different configuration options.
 50: 
 51: 
 52: 
 53: (((
 54: |(((
 55: **User**
 56: 
 57: **Permission**
 58: )))|(((
 59: **Supplier**
 60: 
 61: **Permission**
 62: )))|**Resulting User Functionality in PO Status Summary**
 63: |NO|NO|No PO Change is allowed (buttons are not displayed)
 64: |YES|NO|(((
 65: **Change** **PO** **Button** is displayed and full PO Changes are allowed.
 66: 
 67: The change order is editable by the user.
 68: 
 69: PO change transmission override is not available. Changes are sent using the supplier’s order transmission method.
 70: )))
 71: |NO|YES|(((
 72: A** Cancel** **PO** **Button** is displayed and the order can be cancelled only.
 73: 
 74: A zero value change order is created which cannot be edited by the user.
 75: 
 76: PO change transmission override is available if allowed by the supplier permission setting.
 77: )))
 78: |YES|YES|(((
 79: **Change** **PO** **Button** is displayed and full PO Changes are allowed.
 80: 
 81: The change order is editable by the user.
 82: 
 83: PO change transmission override is available if allowed by the supplier permission setting.
 84: 
 85: (A** Cancel** **PO** **Button** is also displayed allowing similar functionality)
 86: )))
 87: 
 88: Note that an administrator is also able to cancel a purchase order when the **‘Admin Order Cancellation’ **dynamic option is set for their organisation.
 89: )))
 90: 
 91: =User Cancellation Permission=
 92: 
 93: Requisitioner’s are always allowed to cancel their own requisitions and order requests prior to purchase order transmission.
 94: 
 95: Other users are able to cancel requisitions and order requests which are not their own (which they have organisation access permission to) if they have the Purchase Order Change Access permission. Requisition, order request and purchase order **cancellation** is described in full below.
 96: 
 97: __**Requisition Cancellation**__
 98: 
 99: i.e. the requisition is submitted into the approval process but no orders are transmitted.
100: 
101: 1. The **requisitioner** is always able to cancel their own requisitions:
102: 1*. In the Requisition Approval Summary screen (i.e. the requisitioner approves their own requisitions)
103: 1*. In the Returned Requisition Summary screen
104: 1*. In the Requisition Status Summary screen (i.e. from a status search)
105: 1. **Other Users** (e.g. Approvers) cannot cancel requisitions
106: 1. **Administrators** cannot cancel requisitions
107: 
108: __**Order Request Cancellation**__
109: 
110: i.e. the requisition is submitted and split into order requests which are in the approval process but no orders are transmitted.
111: 
112: 1. The **requisitioner** is always able to cancel their own order requests:
113: 1*. In the Order Request Approval Summary screen (i.e. the requisitioner approves their own order requests)
114: 1*. In the Returned Order Request Summary screen
115: 1*. In the Purchase Order Status Summary screen (i.e. from a status search)
116: 
117: 1. **Other Users** are able cancel if they have the** ‘Purchase Order Change Access’ **user role assigned to them:
118: 1*. In the Order Request Approval Summary screen (i.e. they are an approver)
119: 1*. In the Purchase Order Status Summary screen (i.e. from a status search)
120: 
121: 1. **Administrators** are able to cancel if they have the** ‘Admin Order Cancellation’ **dynamic option set for their organisation:
122: 1*. In the Order Request Approval Summary screen (i.e. they are an approver)
123: 1*. In the Purchase Order Status Summary screen (i.e. from a status search)
124: 
125: __**Purchase Order Cancellation**__
126: 
127: i.e. the requisition is submitted, order requests are created and approved and transmitted as Purchase Orders.
128: 
129: 1. Any user with the** ‘Purchase Order Change Access’ **user role assigned** **to them:
130: 1*. In the Purchase Order Status Summary screen (i.e. from a status search)
131: 
132: 1. Any administrator when the **‘Admin Order Cancellation’ **dynamic option is set for their organisation:
133: 1*. In the Purchase Order Status Summary screen (i.e. from a status search)