Sage 300 ERP Purchasing Workflow

Ernest Kruger, Conrad Roux

Features• Create Requisitions directly in CRM• Uses CRM screens and blocks• Sends data directly to Sage 300 ERP using workflow

actions• Uses a dynamically driven workflow using ASP pages

Setup• Users are set up as either Approvers or Requesters in a

hierarchical manner and the code will follow this ladder until the last Approver

• Limits are used to bring more structure into the approval process

• A Buyer is responsible for first-level approval• Cost Centres are associated with Buyers/Approvers• Cost Centres are also used for the ‘check budget’ function

Processing• User and Location fields need to be completed for the

Requisition to be created in CRM – required by Sage 300 ERP

• You then have the ability to add items to the Requisition• Promote button available on completion of Requisition• Only once the Promote button is clicked will the

Requisition be created in ERP

Buyer Approval• When a Requisition is created and there is no buyer

allocated to the specified cost centre, then no buyer approval is required

• A buyer can delete and re-price items on a Requisition• Once approved, the normal approval process will continue• Budgets can be checked from this point on by the Buyer

and Approval users

Approval• Approval users will get notified on any Requisitions

requiring their approval• An Approval user can be set up to approve ONLY, or

approve and request Requisitions• When an Approver approves a record and the amount of

the Requisition is below or equal to the amount of the Approver limit, no further approvals will take place and the request will be converted to a Purchase Order in Sage 300 ERP

• If the amount is higher than that users’ Approval limit, more approvals will need to take place

New Feature