Cannot Delete, Requisition is Awaiting Approval

Often users submit a requisition in Lawson and later find an error in the order and need to re-submit. When trying to delete via RQ10, they get the error “Cannot delete, requisition is awaiting approval.” Luckily this is an easy fix.

  1. Go to RQ13 and inquire on the company and requisition number. Then click Unrelease and confirmed it released.
  2. Go back to RQ10.1 and inquire on the same requisition. You’ll now see that its status is “Unreleased”. Now press Delete.

Done! Now go ahead and resubmit a new requisition with corrections.

How to setup a temporary requisition approver user to start and end at a certain date

  1. Login into Lawson Landmark via Richclient or the cloud-based Process Server Administrator.
  2. In PSA, go to Configuration >> User Configuration >> Users
  3. Select the user we will be adding the filter to then under User Tasks, select create a new filter. (this will be a backup or temporary filter for the user)
  4. Now create the new task (a new tab may open in your browser):
  5. Type in task name and description, save:
  6. Back under user task, select the newly created filter, select the dates you want and save. For our example today is 3/20/2020, we will be setting the date in the future to activate for 3/23/2020 to 3/27/2020:
  7. Now select your new temporary filter and add your filter keys in which you want to approve for:

That’s all there is to it, this filter will enable on 3/23/2020 and disabled again on 3/27/2020 and is useful for users that take time off and need someone to cover them.

A Brief Overview into the Lawson Requisition and Approval Process

Lawson allows for requester users to submit requisition orders for their organization. To make sure the orders are valid, Lawson also supports approvers to verify and approve/reject the orders.

The core of this is done by setting up Requisition Locations (RQ01) and Requisition Strings (RQ02) and having a workflow process everything in between.

Requisition Strings can be used in many different ways, but in our example it is to have individual approvers approve for a particular location. This can also be general titles like Manager, VP, etc. or however your organization wants to set it up.

As you can see below, these are strings for Company 100, Requesting Location RQ210 with Approvers starting at Level4 and stopping at Level6. The lower limit on the left is the amount that the users approve orders for and depending on the IPA flow logic, could notify or skip them.

When users track requsitions in say RQ10 for example, they can drill around and see history log via the strings themselves:

This is only half the setup for this particular organization.


Approvers have to be setup on the Landmark side via Rich Client or Process Server Administrator web application. This is done via “Filters” and these have to be named accordingly to what your IPA Requisition flow will coincide with.

Below is an example of how we would mirror the RQ02 strings in Rich Client (custom report).

The Level 4, 5, and 6 are the “auth id” that our custom flow matches up on. It then grabs the user from Landmark and send notifications based on where the requisition is in the flow.

Some organizations simply don’t use RQ02 strings as they may find it easier to process everything on the Landmark side.  Landmark does have a set of its own reporting tools and filters (See my other article titled “Generating a simple approval level report from the Landmark database“ for a custom database report I created).

The benefits of RQ02 strings in my experience is that the frontend functional users could setup the strings for the developers to mirror in the back end (or by an automated process if done right).


Hope this was helpful in giving you a brief overview of requisitions and approvers.

Changing Prices on Reqs and POs

Can’t Change Pricing on a Requisition or a PO?

There are settings in the Buyer (PO04) or Requestor (RQ04) setup.  It allows control over defaulting in pricing from any contracts or vendor agreements that you might have in place.  If you want a buyer or a requestor to be able to change the price on a PO or a Requisition, then consider the following changes:



At the bottom of the Main tab in PO04 – you can setup a buyer to allow unit cost overrides from different costs.  In this case, the user can’t override a cost that defaults in from a vendor agreement or Strategic Sourcing (Contracts).  However they can override the cost on a PO line item if it defaults in from the last PO or Last Cost (Invoice cost or adjusted cost).



At the bottom of the Main tab in RQ04 – you have similar options.  This user does not have the ability to override any cost that might default onto a requisition.