Na2009 enus sp_01

Chapter 1: Introduction to Microsoft Dynamics NAV 2009 / Microsoft Office SharePoint Server 2007 Integration

1-1

CHAPTER 1: INTRODUCTION TO MICROSOFT DYNAMICS NAV 2009 / MICROSOFT OFFICE SHAREPOINT SERVER 2007 INTEGRATION Objectives

The objectives are:

• Describe uses for Microsoft Office SharePoint Server 2007 and explain its Architecture.

• Describe uses for Microsoft Dynamics® NAV 2009 and explain its Architecture.

• Demonstrate integration possibilities using Microsoft Dynamics NAV 2009 Sales, Customer, and Production Date in a Web solution using Microsoft Office SharePoint Server 2007

Introduction Microsoft® Office SharePoint® Server 2007 and Microsoft Dynamics NAV 2009 are both enterprise ready business applications designed for comprehensive data collection, retrieval, and analysis. When working together they complement each other's strengths. Microsoft Dynamics NAV 2009 is the back-end repository for data collection.

This chapter takes an introductory look at each application and then demonstrates an integration application. Microsoft Dynamics NAV 2009 is the back-end repository for data collected in Microsoft Office SharePoint Server 2007.

Microsoft Official Training Materials for Microsoft Dynamics®

Your use of this content is subject to your current services agreement

Microsoft SharePoint Technologies and Microsoft Dynamics® NAV 2009

1-2

Microsoft Office SharePoint Server 2007 As an introductory look at Microsoft Office SharePoint Server 2007 you will focus on:

• What capabilities does Microsoft Office SharePoint Server 2007 provide?

• What are some Microsoft Office SharePoint Server 2007 Design Goals?

• What are some Microsoft Office SharePoint Server 2007 Components?

• What are some Microsoft Office SharePoint Server 2007 Administration considerations?

Because of time constraints, only certain aspects of Microsoft Office SharePoint Server 2007 will be covered. More information can be found in DMOC - Implementing Microsoft Office SharePoint Server 2007class 5061A.

How is Microsoft Office SharePoint Server 2007 used?

FIGURE 1.1 TYPES OF SOLUTIONS




1-3

Types of Solutions

Microsoft Office SharePoint Server 2007 is based on Microsoft Windows SharePoint Services and can be used to build the following broad types of solutions:

• Collaborative solutions, where information workers can use the latest technologies to work together as teams, regardless of their individual locations.

• Portal solutions that provide access to relevant information for users when they need it.

• Content Management solutions (including Web content management solutions, document management solutions, and records management solutions) that streamline the processes of both publishing and protecting information.

• Search solutions that information workers can use to find data that is stored in various locations in the enterprise.

• Forms solutions that gather business information in a streamlined and efficient manner.

• Business Intelligence solutions that empower decision-makers to assess business information and make informed decisions.

Additionally, Microsoft Office SharePoint Server 2007 provides many features that can be used to manage business processes across these six broad types of solutions




1-4

Microsoft Office SharePoint Server 2007 - Design Goals

FIGURE 1.2 DESIGN GOALS

Introduction

Microsoft Office SharePoint Server 2007 is designed with various goals in mind. Each goal focuses on improving the efficiency of information workers and business managers as they perform their jobs.

Design Goals

• For Collaborative Solutions, the design goals include the provision of a collaborative oriented base framework, interoperability with communication technologies, and extensibility features. This helps information workers to collaborate in intuitive and efficient ways.

• For Portal Solutions, the goals include the provision of information in a timely and context-sensitive manner. This helps ensure information workers have the tools and information they need to undertake the tasks that their roles demand.

• The goals for Content Management Solutions include the provision of robust and flexible frameworks. This helps organizations manage every aspect of their content processes and life cycles, including managing documents, records, and Web-based content.




1-5

• The Search Solution goals include ensuring information workers have access to appropriate information. This includes access to content and people that will help them perform their tasks in an efficient manner.

• The powerful Forms Solution features are designed to streamline, consolidate, and automate data capture processes, so that business processes can run smoothly and efficiently.

• For Business Iintelligence Solutions, the goals include the provision of features and technologies that business decision-makers can use to make well-informed choices based on robust data analysis.

All of these functional goals are supported by a solution framework that customers, partners, and independent software vendors can use to build specific solutions that meet the business and technical requirements of diverse organizations.

Intranet, Extranet, and Internet Single Architecture

In addition to the functional goals, Microsoft Office SharePoint Server 2007 is also designed to provide a single platform that can be used for intranets, extranets, and Internet presence sites. Organizations can now implement solutions on a single architecture to satisfy the various requirements of these different scenarios.




1-6

Microsoft Office SharePoint Server 2007 - Components

FIGURE 1.3 COMPONENTS

Introduction

Microsoft Office SharePoint Server 2007 solutions typically include many features that the underlying Windows SharePoint Services 3.0 platform provides. For example, lists, document libraries, links, contacts, events, notifications, and calendars often provide the foundation for portals, collaboration, content management, and business intelligence solutions. The ability to access all these information types through Web browsers and on mobile devices helps to ensure the usability and manageability of these solutions.

Microsoft Office SharePoint Server 2007 builds on the Windows SharePoint Services foundation by providing two key sets of components that help organizations build powerful and specific business solutions: The Microsoft Office SharePoint Server 2007 Shared Service Provider, and Microsoft Office SharePoint Server 2007 Features.




1-7

Microsoft Office SharePoint Server 2007 Shared Service Provider

The Shared Service Provider performs intensive tasks that can be shared among different sites and site collections, even across members of a server farm. The Shared Service Provider is independent of any particular solution or Web site, although the functionality can be configured differently for specific Web applications. The Microsoft Office SharePoint Server 2007 Shared Service Provider includes:

• Enterprise-level search capabilities that: o Crawl content sources, including SharePoint sites, Business Data

Catalogs (BDC), file systems, and other information stores. o Build and maintain indexes on those content sources. o Run queries on those indexes and return search results.

• Microsoft Office Excel® services that:

o Enable the configuration of trusted locations for Excel workbooks.

o Enable programmatic access to Microsoft Excel Calculation Services.

• User management capabilities that store and manage: o User profiles. o My Sites. o Membership data. o Colleague data.

Microsoft Office SharePoint Server 2007 Features

Microsoft Office SharePoint Server 2007 provides sets of features that focus on particular areas of functionality so that organizations can build specific solutions. Features can be activated to add functionality to a solution, or they can be deactivated to prevent that functionality from being used. Additionally, features can have different scopes, depending on how they are developed. Their scope can apply at the server farm level, the Web application level, the site collection level, or the site level.

Microsoft Office SharePoint Server 2007 includes features that build on the Windows SharePoint Services platform to provide functionality for different types of solutions, they include:

• BDC functionality and Web Parts: o Uses delegation to access data stores securely. o Retrieves data from those data stores. o Displays the retrieved data to information workers.




1-8

• Content publishing functionality and workflows: o Streamlines and manages authoring, editing, and publishing

processes. o Ensures information is managed in a way that conforms to

policies and regulations. o Allows multilingual publishing scenarios.

• Business intelligence functionality and Web Parts that:

o Displays charts and spreadsheet data. o Displays Key Performance Indicators (KPIs).

Microsoft Office SharePoint Server 2007 - Administration

FIGURE 1.4 MICROSOFT OFFICE SHAREPOINT SERVER 2007 ADMINISTRATIVE CONSIDERATIONS

Introduction

The basic model of developing solutions with Microsoft Office SharePoint Server 2007 is to assemble and configure features and services so that they meet the requirements of specific solutions. In some cases, additional custom development can also be included. This model makes it easier for developers to build powerful solutions. However, it also introduces considerations that system administrators and implementers must take into account. The powerful, scalable architecture of Microsoft Office SharePoint Server 2007 server farms provides many technical benefits, but it also introduces administrative tasks.




1-9

Server Farm Administration

Each member of a server farm must be kept synchronized with all the other members in terms of the Microsoft Office SharePoint Server 2007 Shared Service Provider, Microsoft Office SharePoint Server 2007 Features, and Web Parts.

Shared Service Provider Administration

Administrators also require knowledge on how Microsoft Office SharePoint Server 2007 Shared Service Provider functions. For example, administrators will need to configure the Shared Service Provider correctly, monitor performance and usage, and optimize the provider if necessary.

The application integration capabilities of Microsoft Office SharePoint Server 2007 also introduce administrative and design features for specific solutions. The tools Microsoft Office SharePoint Server 2007 provides are straightforward to use, however, it is important for administrators and implementers to understand best practices when integrating disparate enterprise systems.

The more powerful search facilities Microsoft Office SharePoint Server 2007 provides also need to be administered correctly. Implementing a poorly designed search-and-indexing strategy might not provide adequate or appropriate search results, or might degrade performance of Microsoft Office SharePoint Server 2007 solutions if the operations place too heavy a load on the physical servers.

Business Critical Issues

Most often Microsoft Office SharePoint Server 2007 solutions will quickly become critical systems for organizations. Because of this it is important that Office SharePoint Server 2007 solutions provide a high level of availability and are maintained to ensure information is not lost in the event of hardware failures. They must also be optimized so that solution performance is acceptable.

Microsoft Dynamics NAV 2009 This following is an introduction to Microsoft Dynamics NAV 2009 and it focuses on

• What capabilities does Microsoft Dynamics NAV 2009 provide? • What is an Enterprise Resource Planning (ERP) system? • What is the Architecture of Microsoft Dynamics NAV 2009?

Because of time constraints, only certain functionality of Microsoft Dynamics NAV 2009 will be covered. More information can be found in Introduction to Microsoft Dynamics NAV 2009 class 80043A.




1-10

How is Microsoft Dynamics NAV 2009 Used?

Microsoft Dynamics NAV 2009 is an integrated business management solution. It provides financial management, customer relationship management (CRM), and supply chain management (SCM) functionality. It has a modular design which helps people to easily use the functionality required to meet the evolving needs of their business. It also allows for business processes and information to be shared across applications. Data is gathered in a central database (Microsoft SQL Server® 2005 or 2008) that can be reported against, and used by analytical tools to generate business intelligence.

Microsoft Dynamics NAV 2009 provides a complete financial management solution, it is easy to connect financial transactions and information smoothly across affiliate companies and multi-site and international deployments. It provides the audit trails and other security measures required by mandates such as Sarbanes-Oxley, Basel II, the U.S. Health Insurance Portability and Accountability Act (HIPAA), International Financial Reporting Standards (IFRS) and local Generally Accepted Accounting Principles (GAAPs).

The modular design of Microsoft Dynamics NAV can be used to extend functionality by adding in the solutions needed to manage financial data and generate the analytics and business intelligence to help your company grow into the future.




1-11

What is ERP

The main objective of an Enterprise Resource Planning (ERP) system, is to integrate all departments and functions across a company into a single system by using a common database, and to have only one correct set of data. A challenge for many companies is access to timely and correct information, which is crucial in making appropriate business decisions. Sometimes corporate information is located in several databases. For example, inventory levels records are located in one database, while customer information is located in its own separate database. These databases might be “island systems” (they operate independently from each other and do not have any integration with other databases).

FIGURE 1.5 ISLAND SYSTEMS

The Island Systems diagram shows that information about warehousing, production, sales, and customer data are located in several databases across the enterprise. Because this information is not shared, this makes extracting relevant information difficult.

For example, John , a customer who usually buys on credit, wants to triple his standard order, and it must be delivered within the month. Jane, the sales representative, needs to verify the following to ensure she can comply with the order:

• Authorization (whether the sales representative needs his or her manager's approval to approve the order)

• Credit limit (how much the customer can order from the company based solely on credit)

• Inventory levels, production levels, and forecasts. (if there is sufficient stock to comply with the order)

• Shipping (if the items can be delivered on time)




1-12

If the sales representative cannot get this information in a timely manner, she might not be able to close the sale. If she agrees to complete this order without performing the necessary background check, she runs the risk of not meeting the order, and more importantly, losing a customer.

ERP systems do not suffer from this limitation because all information is found in one common database. For example, even though a warehouse supervisor enters information into the system using the warehousing module, that information is visible across the enterprise.

Thus, when a sales representative takes an order from a customer, all information required to fulfill that order will be readily available (for example, customer credit history, inventory levels, shipping availability).

FIGURE 1.6 AN ERP SYSTEM

Real Time

Another factor is that information entered in a legacy system might not be available in real-time. This can mean that records are only updated at certain intervals during a period (hour, day, week, or month) and are usually done as a batch job. The advantage of an ERP system is that once data is entered into the system, it becomes instantly available, with no waiting time. The disadvantage is that incorrectly entered data will also be viewed, and so it important for users to be cautious when entering data into the system. It is critical that only correct data reside within an ERP system.




1-13

ERP System Tied to Company's Business Process

In many cases, an ERP system is configured to match a company's business process. Although companies in a particular industry can share common business processes, each company can have certain business processes specific only to them. Accordingly, an ERP system will be modified and configured to meet a company's individual requirements.

Job Roles and Authorization

While information in the system is accessible, proper authorization is required. Access to data is often determined by one's job role and responsibilities within the organization. For example, an HR manager is authorized to view and modify confidential employee information (such as job description, salary, and benefits), while employees can only edit personal information. In some cases, authorization to access information in the system can be given from time to time. For example, a production supervisor can authorize a subordinate to create and release production orders on his behalf, while he or she is away on vacation. This is to ensure that data cannot be accessed by unauthorized personnel.

The ERP System

Microsoft Dynamics NAV 2009 is a fully integrated relational database system that allows you to enter and maintain financial and other business activities in one place, including:

• General ledger • Inventory • Sales and receivables • Purchases and payables • Resources • Manufacturing

As such, it is categorized as an ERP system.

The business functionality is displayed in a graphical user interface that provides the following benefits:

• All work on the screen is performed in windows. • Many windows can be open at the same time. • One key stroke or mouse click can choose, select, and execute

various functions.




1-14

The application's general functions allow you to:

• Organize daily routines • Locate information quickly • Manage business information

Microsoft Dynamics NAV 2009 design has changed from a two- to three-tier architecture and offers numerous programming features that provide for effective customization of code and execution of functions.

Selected features and characteristics will be introduced through conceptual descriptions and reinforced with a test your knowledge section and demonstrations on the subject.

Microsoft Dynamics NAV 2009 is an integrated business management solution that provides financial management, customer relationship management (CRM), and supply chain management (SCM) functionality. It has a modular design so people can easily use the functionality required to meet the evolving needs of their business. This integrated design means that business processes and information are shared across applications. Data is gathered in a central database (Microsoft SQL Server® 2005 or 2008) that can be reported against, and used by analytical tools to generate business intelligence.

Unlike previous versions, Microsoft Dynamics NAV 2009 is built on a three-tier architecture model and is the first release to introduce a new layer in the traditional two-tier architecture. This additional layer, which is often referred to as the “service tier,” is designed to host and execute all the business logic. The service tier acts as a middle tier between the server and the client tiers.

The introduction of the three-tier architecture however does not mean the end of the two-tier architecture. In Microsoft Dynamics NAV 2009, the three-tier and two-tier architectures coexist: while the Role Tailored client interacts with the Role Tailored components, the Classic client works in the traditional way. Additionally, the Classic client remains an essential component for developing and administering Microsoft Dynamics NAV 2009 applications. (For example, you must use the Classic client to upload your Microsoft Dynamics NAV 2009 license file or to create reports and pages that will be used on the Role Tailored client.

More information on the architecture can be found in the Microsoft Official Curriculum (MOC) 80040, Installation and Configuration in Microsoft Dynamics NAV 2009.

Architectural Changes in Microsoft Dynamics NAV 2009

In previous versions of Microsoft Dynamics NAV, the architecture consisted of two tiers: a client and a server where the client is responsible for displaying the presentation layer in forms and running the business logic in C/AL code.




1-15

The architecture of Microsoft Dynamics NAV 2009 includes a two-tier model, where the Classic client provides a front end to the data layer, which is either the Database Server for Microsoft Dynamics NAV Classic or Microsoft® SQL Server®.

The architecture is now extended to support a three-tier model, with:

• Role Tailored client: A client user interface that provides the front end.

• Microsoft Dynamics NAV Server: A middle-tier server that provides the business logic layer.

• SQL Server: A database server that provides the data layer.

The following figure, describes the three-tier architecture in Microsoft Dynamics NAV 2009.

FIGURE 1.7 THE THREE-TIER ARCHITECTURE

The Role Tailored client, which is a Windows Forms-based client , is designed as the front end for the new architecture. One key feature of the Role Tailored client is the new user interface. After extensive research into how customers work, what their business goals are, and how their departmental organization works,




1-16

Microsoft created a new interface with new interaction styles that support working in a role-oriented, task-focused manner.

To support this user interface, Microsoft Dynamics NAV displays data in the Role Tailored client in a model-driven way and relies on metadata to display this data. Also, business logic code is no longer run on the client. Instead, requests to run C/AL code are sent to the middle tier.

Previous versions of Microsoft Dynamics NAV and the Classic client in Microsoft Dynamics NAV 2009 display data in forms, such as card forms or list forms. This is where forms are designed in a visual design environment with precise layout information.

The new Role Tailored client now displays data in pages, and these pages are designed in Page Designer. You can use Page Designer to transform your existing forms into pages and then adjust them further. Additionally, the page elements are listed in their relative display order, and the properties that are associated with each element are used to specify special presentation features but without any size or position specifications. A page can be consumed by different types of clients without being constrained by layout limitations and each client can render the page in a different way.

Pages provide a flexible foundation for building many different types of display objects. The Classic client contains card forms and list forms. In the Role Tailored client, there are equivalent page types and several new ones that help you build pages with special layouts. Pages also contain new types of controls that enable advanced representation of system data and shortcuts to system features.

The Role Tailored client provides a single document interface (SDI) environment, which is the same type of environment used in Microsoft® Office Outlook®. Lists of e-mails, tasks, or contacts are displayed in the navigation layer, and every email that you want to read or create will open in its own window.

In the Role Tailored client, the navigation layer displays lists of work areas, called list places. Examples of list places include customers and orders. By default, one list replaces another list in the same window. You can also launch a list or card page in its own window. In addition to list places, the navigation layer shows the Role Center and Departments place.

You then open an entity, such as a specific customer or sales order, in a separate window to view or edit it. These windows are called task pages, which also fall into subcategories with different layouts, such as cards, documents, and journals.

The Role Tailored client also has a small category of dialog boxes that are different from task pages. These dialog boxes differ in layout and do not represent an entity. Instead, they prompt the user for parameters for further processing.




1-17

First Look at Both Systems To gain an understanding of Microsoft Dynamics NAV 2009, use demonstration data in Microsoft Dynamics NAV 2009 to display and navigate customer and sales data. The data is found in the VPC used for this class.

To view an example of how Microsoft Office SharePoint Server 2007 can be integrated with Microsoft Dynamics NAV 2009, navigate the same customer and sales data we reviewed in Microsoft Dynamics NAV 2009, however, this time do it through a Microsoft Office SharePoint Server 2007 portal, also found in the VPC used for this class.

Demonstration: Microsoft Dynamics NAV 2009 Customer Data

Click Departments > Sales & Marketing > Sales > Lists > Customers.

The Customer List window opens, showing a list of the existing customers

1. Locate Customer 10000 The Cannon Group PLC and double-click anywhere on the line to view the Customer Card.

2. In the Customer Card locate the Customer Statistics Fact Box on the lower right side.

3. Click Outstanding Orders to view a list of all the orders that are still waiting to be fulfilled for them.

4. Click the line with Order No. 101016 then Show Document to view the order.

Demonstration: Microsoft Dynamics NAV 2009 Sales Orders

Click Departments > Sales & Marketing > Order Processing > Sales Orders

A Sales Order List will appear

1. In the Filter box, filter for Customer 10000 in the Sell-to-Customer field.

2. Double click the line for Sales Order No. 101016 to see the Sales Order.

Review the various tabs to get an idea of the structure of Sales Orders




1-18

Demonstration: Integration of Sales and Customer Data

Open Internet Explorer with http://sharepoint/default.aspx and NAV/SharePoint integration site will open

From the left pane you can access Shared Documents, Calendar, Team Discussions.

You can also view Sales Department and Production Department tabs.

Open the Sales Department tab.

Here users can access a Customer List and a Sales Order List, from which you can further drill down to a particular entry.

1. Locate Customer No. 10000 in the Customer List Fast Tab and click Card. Notice the Customer Card Fast Tab now reflects your selection

2. In the Sales Order List Fast Tab locate Order No. 101016 and select Card. Notice the Sales Order Card tab now shows the Sales Order selected.

3. Navigate to the various tabs to view the data that was shown in the Microsoft Dynamics NAV 2009 demonstrations.

Demonstration: Integration of Inventory Data

Open Internet Explorer with http://sharepoint/default.aspx and a NAV/SharePoint integration site will open

Open the Production Department tab.

Here users can access published Production Information

1. In the Search For Item Fast Tab search for Item 1000 2. Navigate to the various tabs on the Item Card Fast Tab to view

production information for this item. 3. Click the Quantity Explosion of BOM item to see a report detailing

the components that comprise this item.




1-19

Summary Microsoft Office SharePoint Server 2007 and Microsoft Dynamics NAV 2009 can work together as a powerful team to produce solutions that allow interaction with Enterprise data from customers, employees, project team members, and management.

SharePoint collaboration is not limited to dedicated Microsoft Dynamics NAV 2009 users. It can be published on the web to be made available to anyone given access to the data through the web interface. Data can be collected in Microsoft Office SharePoint 2007and delivered to Microsoft Dynamics NAV 2009 to be used in tracking costs for any resources.




1-20

Test Your Knowledge

1. What does three-tiered Architecture mean for Microsoft Dynamics NAV?

( ) That data and business logic are separate from the presentation layer ( ) That there cannot be a direct link to the data from the presentation

layer. ( ) That the underlying data structure is not carried through to the

business layer first. ( ) That business logic is applied after the presentation layer is rendered

in most cases.

2. Why consider integrating Microsoft Dynamics NAV with Microsoft Office SharePoint

( ) To dramatically extend the capabilities of both systems ( ) Reduce the license expense ( ) To allow users not licensed for Microsoft Dynamics NAV interaction

with Microsoft Dynamics NAV data. ( ) To create a new data silo for future growth

3. What types of Projects could be considered for Microsoft Dynamics NAV and Microsoft Office SharePoint integration? (Select all that apply)

( ) Development projects ( ) Sales campaigns ( ) Supply chain integration with suppliers ( ) Inventory management

4. What feature in Microsoft Office SharePoint allows for the creation of dedicated new sites?

( ) The Presentation Layer ( ) SiteBuilder ( ) Templates ( ) Groups




1-21

Quick Interaction: Lessons Learned Take a moment and write down three key points you have learned from this chapter

1.

2.

3.




1-22

Solutions Test Your Knowledge

1. What does three-tiered Architecture mean for Microsoft Dynamics NAV?

(•) That data and business logic are separate from the presentation layer ( ) That there cannot be a direct link to the data from the presentation

layer. ( ) That the underlying data structure is not carried through to the

business layer first. ( ) That business logic is applied after the presentation layer is rendered

in most cases.

2. Why consider integrating Microsoft Dynamics NAV with Microsoft Office SharePoint

(√) To dramatically extend the capabilities of both systems (√) Reduce the license expense (√) To allow users not licensed for Microsoft Dynamics NAV interaction

with Microsoft Dynamics NAV data. ( ) To create a new data silo for future growth

3. What types of Projects could be considered for Microsoft Dynamics NAV and Microsoft Office SharePoint integration? (Select all that apply)

(√) Development projects (√) Sales campaigns (√) Supply chain integration with suppliers (√) Inventory management

4. What feature in Microsoft Office SharePoint allows for the creation of dedicated new sites?

( ) The Presentation Layer ( ) SiteBuilder (•) Templates ( ) Groups



Na2009 enus sp_01

Technology

Transcript of Na2009 enus sp_01