Articulate Word Output - exl-edu.comexl-edu.com/.../Acquisition_Workflow_Rules_New_UI.doc · Web...

Acquisition Workflow Rules (New UI)

1. Acquisition Workflow Rules

1.1 Welcome

Notes:

Welcome to this session of the Alma Administration Fundamentals Training. In this session, we will discuss optional rules you can use in your Acquisitions workflows if you want less automation and more staff mediation.

1.2 Agenda

Published by Articulate® Storyline www.articulate.com

Notes:

Alma supports a highly automated acquisitions workflow. Creation of purchase order lines, packaging of PO Lines into Purchase Orders, sending orders to vendors, receiving physical material, activating electronic resources, and creating, approving and paying invoices can all be automated. By configuring optional rules, you can mandate staff intervention at several points in the workflow either conditionally or unconditionally.

Alma supports three different types of rules: Purchasing Review Rules, Invoice Review Rules and Invoice Approval Rules. You can use one type or all three. Each type of rule corresponds to a different stage of the acquisitions workflow, as we will discuss shortly. But first, a few words about acquisition rules in general.

1.3 PO Validation Types

Notes:

When a PO line or invoice is created, Alma performs two types of validation checks: one check for mandatory information and another validation check according to any rules you have configured.


1.4 Mandatory Validation

Notes:

The first validation check is not configurable. PO lines and Invoices contain some mandatory information, indicated by a red asterisk, without which the PO line or Invoice is invalid. Alma automatically checks each PO line and Invoice to ensure that mandatory information is not missing or erroneous. For example, Alma checks that a PO line has a vendor, a Fund and a list price; or that an Invoice has an invoice number and date. If any mandatory information is missing or erroneous, Alma stops the automatic processing for that PO line or Invoice and sends it to the manual review workbench for staff intervention.

1.5 Optional Validation: Rules

Notes:

The second type of validation check is optional and depends on any rules that you configure.


1.6 Rules: General

Notes:

Rules consist of two parts: input parameters and output parameters.The input parameters define when the rule should be applied. That is, the scenario or conditions under which you want the rule to take effect. For example, a Purchase Order Line for more than a specified amount of money.The output parameters define what action should be taken when the rule applies. For example, remove the PO Line from the automated purchasing workflow and move it to the manual review workbench.

1.7 Multiple Rules

Notes:


You may configure multiple rules of each type. Alma will check them according to their order, beginning from the top, and apply the first rule whose input parameters fit the PO Line or Invoice.

1.8 General Acquisition Rules

Notes:

Rules are applied only one time per PO Line or invoice, namely, when the PO Line or invoice is created. Once the PO Line or Invoice has been moved to the manual review workbench, Alma will no longer check the rules.If, however, mandatory information is missing or erroneous, the PO Line or Invoice stays in review until the missing information is provided, regardless of any rule.

1.9 Agenda


Notes:

Purchasing Review Rules are relevant when creating a new Purchase Order Line and are used to require staff intervention before a purchase order line is packaged into a Purchase Order and then sent to the vendor.

1.10 Purchasing Review Rules

Notes:

Purchasing Review Rules are relevant when creating a new purchase order line and are used to require staff intervention before a purchase order line is packaged into a Purchase Order and then sent to the vendor.

1.11 Input Parameters


Notes:

The input parameters for Purchasing Review Rules define the conditions under which you want the rules to take effect. Purchasing Review Rules input parameters include the following:As part of the validation process for po lines, Alma automatically generates certain informational alerts, or ‘Assertions’. You can select to use any of these assertions as part of the rule.Alerts can include, for example, checking for duplicate orders, checking for existing inventory and checking for a high price. Another input parameter is the Acquisition Method - What is the method used for acquiring the PO line? For example: Approval Plan or Purchase at Vendor System. Another parameter is Vendor Code. You can check purchase order lines for a particular vendor or vendors.Another input parameter is PO line Type - What is the type of purchase order line - print or electronic?, one time or continuous?, etc.The last input parameter is Source Type - How was the PO line created? Only PO lines created via the New Order Import Profile (that is, Import EOD) or via the API will be checked by the rules. You may select more than one value in any of these parameters and more than one parameter in any rule.

1.12 Output Parameters

Notes:

If the PO line matches the input parameters defined in the rule, Alma will apply the output parameter of that rule to the PO line - either True: moving it to Review, or False: allowing it to continue automatically to the packaging stage.


1.13 Agenda

Notes:

Invoice Review Rules are relevant when creating a new invoice and are used to require staff intervention before an invoice moves to the Approval stage of the workflow. If no rules are configured, invoices will continue to the Approval stage automatically (assuming no mandatory information is missing or erroneous).

1.14 Invoice Review Rules

Notes:

Invoice Review Rules are relevant when creating a new invoice and are used to require staff intervention before an invoice moves to the Approval stage of the workflow. If no rules are configured, invoices will continue to the Approval stage automatically (assuming no mandatory information is missing or erroneous).


1.15 Invoice Review Rules

Notes:

The Invoice Review Rules can check for the following conditions…Assertion Code - As in the case of PO lines, Alma also automatically generates certain informational alerts, or ‘assertions’ for Invoices. You can use any of these assertions as part of the rule.Alerts include, for example, checking the invoice for cancelled PO lines, PO lines already associated with another invoice or linked to a different vendor account.Another input parameter is Vendor Code. You can include one or more vendors as part of the input parameters.If you know the invoice line number or numbers, you can use that as one of the input parameters in the rule. Otherwise use an asterisk (*) to designate any invoice line numbers.The last input parameter is the Invoice Creation Form. How was the invoice created? Invoice Review rules are functionally relevant only for invoices created via EDI, or via upload of an Excel or EDI file.



Notes:

The output parameter is either True: moving the invoice to Review, or False: allowing the invoice to continue automatically to the approval stage.

1.17 Agenda

Notes:

Invoice Approval Rules are used to require staff intervention before an invoice can be sent for payment. If no Invoice Approval Rules are configured, invoices will be approved automatically and continue to the next stage of the workflow which is either payment handling or closed.


1.18 Invoice Approval Rules

Notes:

Invoice Approval Rules are used to require staff intervention before an invoice can be sent for payment. If no Invoice Approval Rules are configured, invoices will be approved automatically and continue to the next stage of the workflow which is either payment handling or closed.

1.19 Input Parameters

Notes:

The input parameters available for the Invoice Approval Rules are the same as those available for the Invoice Review Rules.



Notes:

The only output of an Invoice Approval Rule is to move the invoice to the manual approval workbench.

1.21 Agenda

Notes:

In this session, we discussed three types of rules which can be used to require staff intervention in the otherwise-automated purchasing and invoicing workflows: Purchasing review rules, which are used to require staff intervention before a purchase

order line is packaged into a Purchase Order and sent to the vendor. Purchasing Review Rules are functionally relevant only for PO lines created via import of an EOD file or via the API.

Invoice review rules, which are used to require staff intervention before an invoice can be


approved. Invoice Review rules are functionally relevant for invoices created via EDI, or via upload of an Excel or EDI file.

Invoice approval rules, which are used to require staff approval before an invoice can be sent for payment.

To summarize, all rules have similar input parameters and behave in similar fashion: Rules are checked in order, starting from the top. When Alma finds a rule which fits the

scenario, the outcome of the rule is applied (i.e. to move the PO line or invoice, as the case may be, to the review or approval workbench) and no further rules are checked. If no rule fits, Alma applies the Default rule.

Rules are not checked for PO lines and invoices already in review. In other words, if the PO line or invoice was sent to review or approval because of a rule, and the operator clicks ‘save and continue’ (or clicks ‘set back to review’ in the case of an invoice in approval) without having resolved the issue for which the rule sent the PO line or invoice to review or approval, Alma treats this as though the operator has chosen to override the rule.

If mandatory information is missing, the PO line or invoice stays in review until the missing information is provided, regardless of any rule.

1.22 Session Review

Notes:

In this session, we discussed three types of rules which can be used to require staff intervention in the otherwise-automated purchasing and invoicing workflows: Purchasing review rules, which are used to require staff intervention before a purchase

order line is packaged into a Purchase Order and sent to the vendor. Purchasing Review Rules are functionally relevant only for PO lines created via import of an EOD file or via the API.

Invoice review rules, which are used to require staff intervention before an invoice can be approved. Invoice Review rules are functionally relevant for invoices created via EDI, or via upload of an Excel or EDI file.

Invoice approval rules, which are used to require staff approval before an invoice can be sent for payment.


1.23 Session Review

Notes:

All rules have similar input parameters and behave in similar fashion: Rules are checked in order, starting from the top. When Alma finds a rule which fits the

scenario, the outcome of the rule is applied (i.e. to move the PO line or invoice, as the case may be, to the review or approval workbench) and no further rules are checked. If no rule fits, Alma applies the Default rule.

Rules are not checked for PO lines and invoices already in review. In other words, if the PO line or invoice was sent to review or approval because of a rule, and the operator clicks ‘save and continue’ (or clicks ‘set back to review’ in the case of an invoice in approval) without having resolved the issue for which the rule sent the PO line or invoice to review or approval, Alma treats this as though the operator has chosen to override the rule.

If mandatory information is missing, the PO line or invoice stays in review until the missing information is provided, regardless of any rule.

1.24 Additional Resources


Notes:

Thank you for taking this lesson.If you have any questions concerning the topics discussed after viewing this session, please refer them to your Ex Libris project team.Also, you may want to search the Alma OLH to see if you can find answers to your questions there.

1.25 About this Training

Notes:

1 (Slide Layer)


2 (Slide Layer)

3 (Slide Layer)


4 (Slide Layer)


Articulate Word Output - exl-edu.comexl-edu.com/.../Acquisition_Workflow_Rules_New_UI.doc · Web...

Documents

Transcript of Articulate Word Output - exl-edu.comexl-edu.com/.../Acquisition_Workflow_Rules_New_UI.doc · Web...