We integrate with over 35 General ledger systems and often have to help our customers understand where our software ends and their ERP system begins.
Some of the packages we interface with are; Munis, Datatel, Pentamation and SCT Banner with various touch points throughout the procurement process. Our role in the cycle is to present contracts (as online catalogs), provide electronic approvals and PO Processing. Within the various models, our role is to make the overall process more efficient but still allow the business rules within the ERP system to be in effect.
As we hand off information, the rules set within the GL still apply and we wait for an acknowledgment back whether or not to move the transaction forward based on the established business rules. If the GL has an issue with the transaction, we display the message directly to the screen for the end user or approver to take action.
Some of the issues we generally see are Insufficient funds, invalid or unauthorized use of account code. Since easyPurchase is the face to the end user, it is to see why we are called upon when the transaction is not moving forward.
Part of the learning curve of the system admin is to discern whether the business rules within the GL is causing the issue or if the interface is not working properly. This is part of the education our implementation consultants provide during the project.
This post is meant to help the reader understand the role of easyPurchase and the GL and how they complement each during the procurement process. Our application does not perform any action the GL is meant to do, only to present transaction data for the current business rules to be exercised and the resulting message back allowing us to move it forward or displaying the error message to the end user.
Filed under: Ask the Experts, best practice Tagged: | GL integration, GL Interface, MUNIS interface, SCT interface
