1 / 33

BASIC ERP ARCHITECTURE

BASIC ERP ARCHITECTURE. Skorkovský, KPH, ESF MU ,Brno. ERP-definice. Dvě různé definice systémů ERP.

sherryj
Download Presentation

BASIC ERP ARCHITECTURE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BASIC ERP ARCHITECTURE Skorkovský, KPH, ESF MU,Brno

  2. ERP-definice • Dvě různé definice systémů ERP. • V užším pojetí jsou ERP (Enterprise Resource Planning) systémy chápány jako integrované softwarové systémy, které propojují plánování a řízení všech vnitropodnikových oblastí, jako je výroba, logistika, finance a lidské zdroje. • V širším smyslu je ERP chápán jako systém, který kromě integrace interních středisek nabízí i doplňující funkce podporující propojení podniku s jeho okolím (zejména systémy Supply Chain Management a Customer Relationship Management) a manažerské doplňky, jako je Business Intelligence (BI).

  3. ERP-benefity I

  4. ERP-benefity II Zdroj (benefity I a II) : SHANG, Shari a Peter B. SEDDON. Assessing and managing the benefits of enterprise systems: the business manager's perspective, 2002, str. 296-299 , překlad DP Lenka Hladká

  5. Výhody a nevýhody různých řešení

  6. Snímek nutný k porozumění dalších snímků • ERP vytváří transakce (položky, angl. entries) • Položky hlavní knihy jak např. 112|321 a 343|321 • Položky zákazníků a dodavatelů (faktury, platby, dobropisy) • Položky zboží (nákup, prodej, výdej, příjem, spotřeba, výroba a transfer) • Každá položka představuje datovou větu (záznam, angl. record) skládají se z datových polí různého typu (čísla, texty apod.)

  7. Karta zákazníka Karta zákazníka

  8. Položky zákazníka(transakce, entries) Faktura

  9. Faktura - informace

  10. Simplified schema of ERP usage DB ERP Transaction- entries- položky Partners ERP Information (trends) Information Enterprise Reports Trends Decision Knowledge of methods applied for process management Key decisions Key knowledge 21. 10. 2019

  11. Methods Theory of constraint Critical chain Drum-Buffer-Rope Ishikawa Fishbone Diagram Boston matrix and PLC Magic Matrix (Gartner) Use of ERP analytic tools Pareto analysis SWOT MRP,MRP-II Advanced Planning and scheduling Linear programming Methods of quality management • Revenue management (Yield) • Decision trees

  12. What could be controlled…

  13. ERP The main objective of Enterprise Resource Planning, or ERP, is to integrate alldepartments and functions across a company into a single system by using acommon database, the value of which is to be able to have only one correct set ofdata.

  14. Isolated Data Islands SteelService Center Vertical Marketing & Sales Islands Accounting Island Marketing Management Production Island Customer Orders Accounting Sales Representatives Island of Deliveries Customers Production Planning Quality Management Island Quality Management Inventory and Production 14

  15. Management Marketing Customer support Internal Sales One Company Database Accounting Customers Quality management Production Planning SteelService Center Vertical One Solution One Database All Microsoft Inventory and Production Sales Representatives 15

  16. ISLAND SYSTEMS (home study) For example, recordsabout inventory levels may be found in one database, while customer informationmay be found in its own separate database. Furthermore, these databases may be"island systems" (operating independently from each other and having no integration with other databases).

  17. Architecture 2-tier (2-vrstvy) Klientská vrstva Databáze a aplikace

  18. Architecture 3-tier (3-vrstvy) Klientská vrstva Střední vrstva (servers) Databáze The second tier is the multithreadedmiddle tier. This is the servicetierthat is based on Web services.

  19. From hell to paradise –ERP (see meaning) You can change a business in order to copy rigid functions of the software ERP Programming You can change a software in order to support your business Parameter setup

  20. Technological pyramid REPORTING & ANALYTICS MICROSOFT BUSINESS SOLUTIONS - NAVISION E- COMMERCE SCM CRM FM TECHNOLOGY

  21. ISVs Development Tools Integrated homogeneous solution Customer Relationship Management Supply Chain Management Financial Management Analytics

  22. Unique architecture Integrated Development Environment Database GUI (Windows) Zaměstnanci CommercePortal Microsoft Navision Database Server Zákazníci & obchodní partneři ApplicationServer Commerce Gateway (B2B) Microsoft SQLServer 2000 Worldwide Generic Objects Country-specific Objects See live systém NAV Externí aplikace Customer-specific Objects VerticalSolutions Objects

  23. Main access form (Role Tailored Client)

  24. Main forms (card, list, form->sub-form)

  25. Main forms (card, list, form->sub-form)

  26. Main forms (card, list, form->sub-form) Partner What

  27. Relation between tables-example

  28. Relations among tables I

  29. Relations among tables II

  30. One table and its relations I

  31. One table (Sales Line) and its relations II ERP NAV

  32. Microsoft Dynamics NAV Sweet Points • Windows compatible (menu, command, mutual relations to MS Office,..) • Security (ID,passwords, roles, protocols) • Menu and basic modules • Shorthand keys and HELP • Multilanguage • Navigate and calculation (flow) fields, finding the reason why any document was created • Reports • Entries, dimensions

  33. Thanks for your attention

More Related