|
|
|
|
|
|
Task Manager integration provides an ability to review, authorise or reject the following notifications from the application:
Purchase Management Related
Accounts Payable Related
Order details as displayed in Mobile Application
Order reference, Action before date, Supplier description, created by user description.
The BEM Priority is displayed as High, Medium or Low on drill into a document detail. Approve or Reject functions are available at this level. Additional information includes:
The Company description, Order number, Revision number, Owner description, Owner eMail Address, Buyer description Date, document value, Currency description and Supplier description.
Line details available are: Item code / description, Quantity, QUOM description, Price, PUOM description, Delivery location description. (Equivalents for Rate and Value type lines).
Requisition details as displayed in Mobile Application
Requisition reference, Action before date, requisition title, created by user description.
The BEM Priority is displayed as High, Medium or Low on drill into a document detail. Approve or Reject functions are available at this level. Additional information includes:
The Company description, Requisition reference, Title, Revision number, Owner description, Owner eMail Address, Date and document value.
Line details available are: Item code / description, Currency description, Quantity, QUOM description, Price, PUOM description, Supplier description, Buyer description, Delivery location description. (Equivalents for Rate and Value type lines).
Contract details as displayed in Mobile Application
Contract reference, Action before date, Supplier description, created by user description.
The BEM Priority is displayed as High, Medium or Low on drill into a document detail. Approve or Reject functions are available at this level. Additional information includes:
The e5H5 Company description, Contract reference, Revision number, Owner description, Owner eMail Address, |Buyer description, Date, value, currency description, supplier description.
Line details available are: Item code / description, Quantity, QUOM description, Price, PUOM description, price break, effective date, expiry date, delivery location description, (Equivalents for Rate and Value type lines).
AP Transaction Details as displayed in Mobile Application
Transaction reference, Action before date, created by user description.
The BEM Priority is displayed as High, Medium or Low on drill into a document detail. Approve or Reject functions are available at this level. Additional information includes:
The Company description, AP Transaction reference, Supplier description, currency description, gross amount, tax amount, date and Status.
Line details available are: Item description, Quantity, QUOM description, Price, PUOM description, total value, tax value (Equivalents for Rate and Value type lines).
The process that processes Air Approvals actions also handles events that arise from an escalation or transfer BEM message.
As, in this case, the approval action may emanate from an Approver who is not the original assigned authoriser, additional checks are performed to ensure that the user can legitimately perform the requested action.
The Authorisation Structure used for additional checks is determined as follows; if there is one on the relevant company controls then this will be used. If there is not one at this level, then if the Approving/Rejecting user exists on just one structure, then that will be used. If neither of these scenarios are valid then a structure will not be used, the Approve/Reject action will not be performed and an Error BEM notification provided.
It is assumed that if a user is not sufficiently high in the structure to authorise a document then they will also not have sufficient rights to reject the document.
Where the extra checks raise an error that will prevent the Approval process, a new BEM event will be triggered to notify the problem to an assigned User.
It is expected that the Action list entry for the new BEM events will be set up with a User, or Action Role entry to control who is notified in these circumstances of the errors. If a user is not defined at this level then if there is a Security administrator defined at system control level, they will be informed. If there is no Security Administrator, then the Batch User defined at system control level will be notified.
Examples of the Shipped BEM Diary text are below:
A. User @@@@@@@@ attempted to authorise for user @@@@@@@@ but an authorisation structure could not be found.
B. User @@@@@@@@ attempted to authorise for user @@@@@@@@ but they do not exist in authorisation structure @@.
C. User @@@@@@@@ attempted to authorise for user @@@@@@@@ but they do not have sufficient rating in authorisation structure @@.
D. User @@@@@@@@ attempted to reject for user @@@@@@@@ but an authorisation structure could not be found.
E. User @@@@@@@@ attempted to reject for user @@@@@@@@ but they do not exist in authorisation structure @@.
F. User @@@@@@@@ attempted to reject for user @@@@@@@@ but they do not have sufficient rating in authorisation structure @@.
See also
|
© Advanced, Jan 2021 |
|
