SAP ERP Implementation
Before implementing SAP ERP sd, the management must evaluate the feasibility of the project. Generally, most organizations have criteria that are used to justify new systems like SAP ERP sd. Typically, the evaluation requires answers to the following questions: Do the expected benefits exceed the costs? Can the system be completed within a reasonable time? Do we have, or can we obtain, people with the appropriate skills to complete and operate the system?
The systems analyst next works with future users of the SAP ERP sd system in order to identify key data needed to make decisions. The analyst also learns how the users will analyze the data. Based on this information, the analyst develops a model, or blueprint, of how the data will be stored in the repository. The analyst designs this model to make access more efficient for the users' intended analyses. When the model optimizes one type of analysis, other types of analyses may be less efficient. In other words, a data repository designed for OLAP may not efficiently support data mining. Systems analysis is an iterative process requiring communication between the end users and the technicians responsible for the project's creation.
Once the data and its intended use are known, the systems analyst must tackle several technical questions: What software will be used to manage the data and conduct the analyses? What hardware will run the software? What network infrastructure is required to deliver the information to end users?
Typically, the SAP ERP sd software is selected first. Initially, the systems analyst compares the proposed system's requirements to software created by third parties. Many vendors provide products for creation of data repositories and analysis of data. There are many advantages to using a third party's products. The software is debugged and technical support is readily available. It can usually be installed in less time than it takes to write a custom program. The major concern is that the product may not exactly fit the specified requirements. If a compromise cannot be reached between the software's capabilities and the project's needs, the project must be reevaluated to see if the benefits still justify a more costly custom development path. After selecting the hardware and software, data is copied from the legacy systems and external sources, cleansed, and loaded into the repository. Typically, the data is initially stored in its raw, detailed form. When it is known in advance that a particular summary will be used frequently, the system can be programmed to automatically calculate and save it. This will be more efficient than recalculating the summary each time it is requested. The SAP ERP sd system should be tested prior to going live to ensure that dirty data has been eradicated. Nothing will bring a project to an end faster than delivering incorrect information to decision makers. Several techniques are available. Queries can be run against the data and compared to predetermined results. Unexplained differences may indicate data problems. Additionally, statistical summaries may spot unusual items. For example, if the repository should contain the post office's two-digit state code for each address, the data can be sorted by state. If both New York and NY are found, the data has not been property cleansed.
ERP SAP
|