Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Purchase Requests

    Translatable
    The following roles are required to perform purchase request tasks:
    • Create request from Alma/Primo with the user as the requester: Any role
    • Create request from Alma on behalf of another user: Purchase Request Operator/Manager
    • Create request from reading list: Course Reserves Operator/Manager (when enabled by Ex Libris for your institution)
    • Manage requests: Selector, Purchase Request Operator, Purchase Request Manager
    • Delete rejected requests: Selector + Selector Extended, Purchase Request Operator + Purchase Request Operator Extended or Purchase Request Manager + Purchase Request Operator Extended
    • Assign requests: Purchase Request Manager
    Purchase requests enables librarians using Alma and instructors or patrons using Primo or Leganto to request that a library purchase an item. The requester can request an item for any reason, for example: the library does not have a copy (there is no bibliographic record, or there is a bibliographic record but no inventory), or the library does not have enough copies or in the right format or edition, or the existing copy is damaged. The requester (or a librarian on behalf of a requester) fills in as many details of the item as possible and then sends the request to Alma for review.
    An Alma user with the Purchase Request Operator role can only see requests assigned to them or that are unassigned. If their role is defined for a specific library they can create and see only those requests that belong to their library or those that don't belong to any specific library (the owning library field is empty). An operator that does not have Purchase Request Operator access will not have access to edit the requester in the purchase request form. The operator can reassign purchase requests to other purchase request operators. For customers that went live prior to the October 2018 release, this privilege is disabled by default. For all others, this privilege is enabled by default. To change this setting, contact Ex Libris support.
    An Alma user with the Purchase Request Manager role can see and assign purchase requests for all operators and managers. If the role is defined in a library scope, they may only see and assign requests in that library or that do not belong to a specific library (the owning library field is empty). At the time that the purchase request manager assigns a request, it is checked to verify that the assignee is either an operator or manager for this scope or in the institution scope. An operator or manager that needs to delete purchase requests must also have the Purchase Request Operator Extended to do so.

    When a user with one of these roles creates a purchase request, if the user is in the scope of a library, the library is added to the request as the Owning Library. If the user is in the institution scope, a pop-up will be presented to ask the user to select the owning library. If the user is not a purchase request operator or manager, the owning library will be empty. In this case, only the purchase request operator or manager can select an owning library when editing. The list of available libraries to assign will be determined by the editing user's scope.

    An Alma user with the Selector role (Selectors) can view the list of requests and assign each one to users. Selectors can edit a request, email a requester for more information, and approve or reject requests. Approved requests become PO lines. 
    To support this feature, two letters are used:
    • Purchase Request Status Letter (letter code: PurchaseRequestStatus) – Sent to requester when the request is approved or rejected.
    • Query to Requester (letter code: QueryToRequesterLetter) – Sent to the requester when the librarian queries him or her for more information.
    Bibliographic records created using purchase requests use the Default bibliographic template (see Working with Bibliographic Record Templates) and are subject to normalization processes (see Working with Normalization Processes).
    For more information, watch the Patron Purchase Requests video (3:46) Also see the purchase request presentation [PPT].
    Purchase requests is a service exposed from Alma to Primo. Like any other service, it can be hidden from groups of users using Alma’s Display Logic Rules. This service is initially hidden from users by default with the rule Hide Service Purchase Request.

     

    patron_purchase_request_link_in_primo.png

     

    Purchase Request Link in Primo
    • To enable the service for all Primo users, remove this rule.
    • To hide the service only for specific groups, remove this rule and then add a rule/rules to hide the service for those groups.
    • You can also configure all labels used for this feature.
    • To create a direct link to the purchase request form from Primo, see Direct Linking to the Purchase Request Form.
    For more information about configuring display logic rules and configuring labels, see Discovery Interface Display Logic.

    Creating a Purchase Request

    A patron can create a purchase request in Primo. Requests made by patrons in Primo are submitted to Alma with the status In Review. A brief bibliographic record is created for the requested item, if required (and if the metadata is added manually, as stated in the note below).
    You can also create a purchase request on behalf of a user in Alma. You can do this:
    • When managing citations in a reading list (see Managing Citations), if the Submit Purchase Request privilege has been added by Ex Libris Support to the Course Reserves Operator/Manager roles. Note that simply adding or editing a citation may automatically trigger a purchase request; see Configuring Automatic Purchasing Requests from Citations.
    • On the Purchase Request page (see below).
    To create a purchase request on the Purchase Request page:
    1. On the Purchase Request page (Acquisitions > Purchase Requests > Create Purchase Request), fill in as much information as you can.
      Alma: Purchase Request Page
      Select either Create new record or Use existing record on the Bibliographic Information field. When selecting Use existing record, a quick pick list is available for the Title field while the other item fields are restricted. Once you select an existing record, you can create the purchase request from this record. Alternatively, if you want to create an item from an existing similar item, you can search on the title of the existing record to populate the item's fields, then change the Bibliographic Information radio button to Create new record. The remaining item fields are not restricted while creating a new record, so the values can then be changed.
      For a description of the fields in the Resource Information area, see Adding a New Book or Journal Article. The fields in the Request Attributes area are as follows:
      • Requested Format – Whether the item should be acquired in electronic or physical format
      • Requester – The user who is making the request
      • Request Status – The initial status of the request, which is always In Review
      • Owning Library – The library that should receive the item
      • Estimated Cost – An estimated cost for the item, including the currency
      • Fund – The fund from which to purchase the item. This field is only active after a library is selected. Note that it is recommended that you add the fund immediately before the purchase request is approved.
      • Vendor/Account – The vendor and vendor account from which to purchase the item
      • Approved By – This field is initially empty. It will later contain the name of the user who approved the item, if any.
      • Requester Note – Any note to send to the user who will be approving or rejecting the request.
      • Rejection Reason – This field is initially empty. This field will later contain the reason the request was rejected, if any.
      The fields Title and Requester are mandatory.
      When a purchase request is created using Create new record, Alma looks for a potential match to the record. The matching routine first looks for an import profile to determine the matching process. The import profile can be type Repository or New Order, must be active, and its profile name stored in the purchase_request_import_profile parameter (see Configuring Other Settings (Acquisitions)). The import profile can define which match routine will be used for books and which match routine will be used for journals. If no profile is specified in the parameter, the matching is based on the ISBN/ISSN in the purchase request (using a hard-coded matching routine that cannot be modified). If a matching record is found in the repository, the purchase request is linked to this bibliographic record. If no match is found, a new bibliographic record is created. Note that the bibliographic details of the matching or new record can be edited using the MD Editor. They cannot be edited by editing the purchase request (only request attributes, such as requester and owning library can be edited this way). When editing the purchase request, the bibliographic information can be changed by selecting the Create New Record radio button. When changing the radio button, the user will be prompted with the following confirmation message: You are about to change the linked bibliographic record. The existing bibliographic record data will be replaced. Are you sure you want to continue?
      For more information, see the Configure a Preferred Match Method for Purchase Requests video (3:28 min.)
    2. The citation type for a searched item comes from the ISBN or ISSN. If there is an ISBN number, the citation type is Book. If there is an ISSN number, the citation type is Journal. If neither number exists, the citation type is the type that was chosen when the purchase request was created. As an example of how this is applied, if the MD Editor is used to add an ISSN number to a bibliographic record, and the purchase request is then edited and saved, after the purchase request is saved, the citation type of the purchase request becomes Journal.
    3. Instead of entering the information manually, you can search for and select an item in the repository, and select Select. The item’s information is pre-filled in the page’s fields. See Searching in Alma.
      When creating a purchase request associated with a bibliographic record, the bibliographic metadata cannot be edited on the purchase request page. This is to avoid either changing the existing record or creating a new one from this page. A new record is created from this page only when you enter the information manually.
    4. (When editing a request only) If you entered a Library, you can add locations and the number of requested copies for each location; select Add Location. If you do not specify quantities and locations, one copy in the default Acquisitions location is assumed.
    5. Add any notes in the Notes tab, as required.
    6. When you are done, select Save.
      The request is submitted with the status In Review. A brief bibliographic record is created for the requested item, if required.

    Managing Purchase Requests

    Viewing Pending Purchase Requests

    To view pending purchase requests, select Acquisitions > Purchase Requests > Manage Purchase Requests from the Alma Main Menu. Alternately, if there are any unassigned requests, or there are any requests assigned to you, select one of the following tasks from the Tasks List in the persistent menu (see Tasks in the Task List):
    • Purchase requests - assigned to you
    • Purchase requests - unassigned
    Manage Purchase Requests Page
    Use the tabs to see requests assigned to you or to others, or to view unassigned requests. Use the facets and the Find tool to filter the list of requests on the page.
    For information on searching using special characters/diacritics, see Searching for Special Characters.
    To view more details about the requested item:
    • Select a request title to view the request in the MARC Record Simple View page.
    • In the Unassigned or Assigned to Other tab, select View beneath a request to view the request details. The View link only appears in the Unassigned tab if the request was ordered or rejected.

    Assigning a Purchase Request

    You can assign a purchase request to a user or release an assignment. The user to which the request is assigned should approve or reject the request.
    To assign requests to a user:
    1. Select Assign to in the row actions list. A dialog box appears.
      Assign To Dialog Box
    2. Select the user to whom to assign the request. Only users with the relevant role appear in the drop-down list.
    3. Optionally add a note and select whether to send an email to the user.
    4. Select Assign To.
      The request is assigned to the selected user.
    To move a request back to unassigned:
    In the Assigned to Me or Assigned to Others tab, select Release Assignment in the row actions list. The request is moved back to the Unassigned tab.

    Editing a Purchase Request

    You can edit a purchase request.
    To edit a request:
    1. In the Assigned to Me or Unassigned tab, select Edit in the row actions list. The Purchase Request page appears. For more information, see Creating a Purchase Request.
    2. Change any non-metadata fields as required.
    3. You can select the Relink button to change the bibliographic record for this purchase request.
      For more information, see the Relink a Purchase Request to Another Bibliographic Record video (1:41 min.)
    4. When you are done, select Save.
      If the request was not already assigned to you, it is now assigned to you.

    Emailing a Purchase Requester

    You can email the requester for more information about a purchase request.
    To send email to the requester:
    1. Select Send Query to Requester in the row actions list. An Email Message dialog box appears.
      E-Mail Message Dialog Box
    2. Enter information in the fields. The From, To, and Subject fields are mandatory. Note that if the requester’s email is not prefilled, you must enter it manually.
    3. When you are done, select Send E-Mail. A Query to Requester letter (letter code: QueryToRequesterLetter) is sent to the requester. For information about configuring the letter, see Configuring Alma Letters.

    Approving or Rejecting a Purchase Request

    Approving a purchase request creates a purchase order line. Whether you approve or reject the request, Alma sends an email to the requester.
    To create a purchase order line for (approve) the request:
    Before ordering the item, ensure that a library and/or location is selected in the request. If one is not selected, edit the request; see Editing a Purchase Request.
    Select Approve and Order in the row actions list. A PO line is created with the status In Review; it then proceeds through the purchasing process, as usual. The PO line number appears in the confirmation message at the top of the page. Alma sends the requester a confirmation letter, the Purchase Request Status letter (letter code: PurchaseRequestStatus).
    To reject a request:
    1. Select Reject in the row actions list. A confirmation dialog box appears.
      Alternately, you can reject multiple requests at once: Select the check boxes next to the requests that you want to reject and select Reject Selected at the top or bottom of the page. You can select all the requests on the page by selecting Select All at the top of the list of requests. Note that you cannot reject requests that were already approved.
    2. Select Confirm in the confirmation dialog box. A reject reason dialog box appears.
      Reject Reason Dialog Box
      This list of reasons can be configured by an administrator.
    3. Select the reason for the rejection and select Reject. The request is rejected. If the request created a brief bibliographic record, it is also deleted. Alma sends the requester a Purchase Request Status letter (letter code: PurchaseRequestStatus) to inform him/her of the request rejection. For information about configuring the letter, see Configuring Alma Letters.
      An administrator can configure the reasons for rejecting a request; see Configuring Purchase Request Reject Reasons.
    After a request is rejected or approved, it appears in the list of requests with the option to delete the request. To delete the request, select Delete in the row actions list.
    To delete a purchase request, you must have the Selector Extended role.