A recent survey (PDF download) by Panorama Consulting Solutions compares important dimensions of IT project success and failure with respect to ERP systems from SAP, Oracle, and Microsoft Dynamics. Photo credit: "Choosing the colors of ERP" by Michael KrigsmanAccording to the report, the data set consists of over 2000 respondents from 61 countries who have selected or
implemented SAP, Oracle or Microsoft Dynamics ERP solutions between February 2006 and May 2012.
Market share. As the diagram below shows, the report indicates that SAP holds the largest market share of three vendors, with 22% share. The market share difference between SAP and everyone else is quite large. Selection rates. Given SAP's market share, it is no surprise the company often appears on procurement short lists, as indicated in this chart: Although SAP achieves the top spot in short lists, both Oracle and Microsoft are more frequently chosen than SAP. As the survey report states: the study suggests that after "assessing the available information, organizations are not easily convinced that SAP is the best option." It is possible that SAP's reputation for being expensive and complicated to implement scares potential buyers. Implementation duration. According to the survey, Oracle projects show the largest gap between planned and actual implementation durations, as the graph shows: In general, Microsoft has the smallest implementations, relative to Oracle and SAP. Overall, 61% of all implementations reported in the survey run late. This number is not surprising because it is consistent with data from other research.
The study also lists the reasons that projects run late. As listed in the table below, technical issues cause only a small percentage of projects to run late. More commonly, projects are late due organizational, business, and project management challenges. SUMMARY HIGHLIGHTS
The report presents the following overall summary information:
SAP
Largest share of the market
Highest short-listing rate
Lowest selection rate when short-listed
Longest payback period
Oracle
Highest selection rate when short-listed
Longest implementation duration
Largest delta between planned and actual implementation duration
Lowest percent of users who realized between 81- and 100-percent of benefits
Microsoft Dynamics
Smallest share of the market
Lowest short-listing rate
Shortest implementation duration
Highest percentage of users who realized between 81- and 100-percent of benefits
CIO STRATEGY CONCLUSIONS
The survey data suggests that Microsoft Dynamics is doing something right, despite its low market share. However, it is likely that Dynamics projects tend to be smaller than those from SAP or Oracle, which explains the shorter project and higher success rates.
Oracle comes off worst among the three vendors, based on the lowest benefits realization and longest gap between planned and actual project duration. SAP has the longest payback period, suggesting these projects may involve greater business process complexity than is typical from the other vendors.
Before making decisions based on this study, ERP buyers should be aware of an important deficiency in the survey reporting. Since the survey does not distinguish company size, the results are likely an average of projects of all sizes; the results might be significantly different if we were to look at breakdowns based on project and company size. For this reason, the survey is interesting and even helpful, but ultimately less useful than would otherwise be the case.
I have made a form with datasources vendtable and vendtrans. Inside vendtable_ds.executequery() looks like this: QueryBuildDataSource queryBuildDatasource ,queryBDS_VendTrans_Invoice; ; queryBuildDatasource = this.query().dataSourceTable(tablenum(vendtable)); queryBDS_VendTrans_Invoice = this.query().dataSourceTable(tablenum(vendtrans)); if (curext() == "MASTERCOMP") { this.query().allowCrossCompany(true); } else { this.query().allowCrossCompany(false); } //FilterVendorName = stringedit control on form if (FilterVendorName.text()) { queryBuildDatasource.addRange(fieldNum(VendTable,Name)).value(strfmt("*%1*", FilterVendorName.text())); } else { queryBuildDatasource.clearRange(fieldNum(VendTable,Name)); } //FilterInvoiceNumber = stringedit control on form if (FilterInvoiceNumber.valueStr() == "") { queryBDS_VendTrans_Invoice.enabled(false); } else { queryBDS_VendTrans_Invoice.enabled(true); queryBDS_VendTrans_In...
This post will help to create credit note for a sales order based on the invent lot id. All the invoices raised for a particular sales line – Lot Id will be raised back as a credit note. Information on Credit Note: A credit note or credit memorandum (memo) is a commercial document issued by a seller to a buyer. The seller usually issues a Credit Memo for the same or lower amount than the invoice, and then repays the money to the buyer or sets it off against a balance due from other transactions Below Code will help to create credit note for all the invoices raised against the sales line -lot id. Please note: This code can be customized as per your requirements. This is just a template to help creating credit note using X++ code. Please test the code before use. static void SR_CreateCreditNote_Sales(Args _args) { // Coded by Sreenath Reddy CustInvoiceTrans custInvoiceTrans; Dialog dialog = new Dialog(“Create credit note – for sales.”); DialogField dfInv...
