1. SAPSYSTEM ANALYZE AND PROGRAM DEVELOPMENT

5. It eventually became known as the R/1 system. The "R" stands for real-time data processing. It was launched in 1973.

6. The second iteration of the R system (R/2) launched in 1979, accommodated different languages and currencies.

8. A sizing and blueprinting phase where the solution stack is created and training is being performed.

9. Afunctional development phase and finally a final preparation phase.

13. INVOLVEMENT 2. SAP R/3 implementation is not an IT project, in fact is an Organization Project impacting all levels of a company. So it is very important to get the support from all the people that are involved in implementing SAP, but more important the participation and commitment of all levels, specially managers, of the company.

14. BLUE PRINT 3.The Blueprint is the keystone used as the lighthouse who must guide the whole project. A blueprint should never be a merely mapping of IT systems. In fact a blueprint is bringing the strategy of a company into execution through defining its processes across all business areas. Many projects have failed because the focus was on having people with SAP knowledge, but with no business skills and so defining something that works...wrongly. Just remember, processes must change across time, and a manual error automated could be repeated infinitely.

15. CHANGING THE WAY 4.Always consider changing the way things have been done before implementing SAP. "This has always been done like this and the Consultant should replicate it on SAP" is the start of a big problem. SAP many times could save you time and money as it allows your organization to automate many processes.

16. TESTING 5.Test the SAP hardware and software rigorously by testing your business processes, and to ensure that the end-users are ready to use SAP before going live, because there are many known projects that failed because of a lack of support and SAP knowledge.

17. MANAGEMENT PROGRAM 6) Design and execute a Change Management Program by communicating as early as needed all the information that end users should have to accept the new technology and designing and executing a training plan in order to reassure a knowledge base within the organization. SAP as a Change Enabler.

19. Application Server: An application server is a set of executables that collectively interpret the ABAP/4 programs and manage the input and output for them.

21. Tables Programs DB SAP UNIQUE ARCHITECTURE Presentation SAPGUI Terminal process R/3 Application Dispatcher Work process Work process Buffer Database

23. SAP ERP systems effectively implemented can have cost benefits.

24. Integration is the key in this process.

25. SAP's ERP solution includes several modules that support key functional areas - some of them are:

26. SAP ERP Financials

27. SAP ERP Logistics

29. Provides the development and runtime environment for SAP applications.

31. Offers good understanding of current situation of company

32. Offers high security and info consistency to choose best marketing strategy

33. Offers co ordination across the company

35. Incorrect application Of software.

36. Poor analysis of cost and benefits.

37. Lack of trained personnel .

38. Not enough systems or probably computers to handle.

39. SYSTEM FAILURE

40. Localization of software.

41. Customization for different accounting systems and tax systems which changes from country to country.

42. EXPENSIVE

44. Human Resource

45. Customer Relationship Management

46. Supplier Relationship Management.

47. Product life Cycle Management

48. Business Intelligence