Free MB-700 Exam Dumps Preview

Background

Blue Yonder Airlines is a private airline company established in 1963 in Boston. The company completes over 2,000 flights a day with flights operating exclusively in North America. Blue Yonder Airlines is in the planning phase for replacing its current enterprise resource planning (ERP) with Dynamics 365 Finance, Supply Chain Management, and Commerce and is making solution architecture decisions prior to engaging the remainder of the implementation team.

Current environment

Technology

1. Blue Yonder Airlines operates on a custom-built ERP solution.
2. Blue Yonder Airlines uses a proprietary reporting and analytics platform that reports on data between multiple systems, including the ERP solution.
3. The ERP solution automatically pushes transactional data every five minutes to a separate database that the reporting and analytics platform uses for sales and operations planning (S&OP) activities.
4. SQL Server Reporting Services (SSRS) reports are used for several financial reports that are sent to vendors in the existing ERP solution.
5. Users utilize a third-party tool that selects alternate layouts of the reports depending on the users' requirements.
6. Blue Yonder Airlines currently uses Microsoft 365 and Office 365.

Implementation

1. The implementation of new solutions and features follows an Agile implementation strategy.
2. Blue Yonder Airlines has several highly skilled project managers.
3. Blue Yonder Airlines has a live Microsoft Dataverse instance that runs several model driven Microsoft
Power Apps apps. Several initiatives using Microsoft Power Automate and Power Virtual Agents are in the middle of implementations.

Development

1. There are five different functional groups, called pods, which fully own their development cycles for

different functionality in their ERP.
2. All code is deployed and managed by using Microsoft Visual Studio projects.
3. All development environments are currently hosted by a third-party company. The current costs are very expensive.
4. Blue Yonder Airlines plans to use the new ERP implementation to address performance and integration issues.

Licensing

1. Blue Yonder Airlines does not require licensing on its ERP solution because the system is custom.
2. Most users have more access within the ERP solution than required.

Requirements

Technology

1. The previous custom ERP data will be replaced with Dynamics 365 Finance and Operations apps in the current reporting and analytics platform.
2. Only native Dynamics 365 capabilities should be used.
3. The level of effort required from IT staff must remain the same.
4. Standard SSRS reports will be used.
5. The current third-party financial reporting tool does not integrate with Dynamics 365.
6. Blue Yonder Airlines has a highly experienced in-house team of implementation experts. It will implement Dynamic by using only internal employees. No Microsoft partner will be engaged in the implementation.

Data

1. Historical data will remain in the current system for reporting purposes.
2. Some sample data that needs to be migrated to Dynamics 365 includes:
- Data set 1 - Active airplanes - Planes that actively transport customers
- Data set 2 - Queued flights - Completed flights but not yet invoiced will be migrated
- Data set 3 - Flight consumption measurement - Units of measurement of gasoline consumed per flight
- Data set 4 - VIP customers - Customers that average $3,000 USD per flight

Development

1. Each of the pods' development teams must be able to deploy all of its code independently from one another.
2. Overlayering of base Microsoft or third-party code must be prevented.
3. Each developer must have their own environment.
4. Development environment costs should be as low as possible.
5. Developers should be able to access their development environments 24 hours a day.
6. The development team must create a performance strategy that involves the functional implementation team and the different development teams by using Microsoft recommendations.

User configuration

To save on implementation costs. Blue Yonder Airlines will determine which base security roles to assign to which users to conduct their day-to-day operations. Only base security roles will be used without modification.

Issues

Development

The development and functional teams are not taking ownership of the performance benchmark testing.
There are no functional designs, benchmark scenarios, or expectations setting created to date.

Security

Blue Yonder Airlines does not know how to configure the security of the users to enable access to complete its day-to-day operations.

Licensing

1. A licensing compliance audit has determined that the correct number of employees are added to the system but too many base and attach licenses are being used.
2. Some users will likely have to consolidate duties to maintain compliance.

A Datum CorporationOverview

A Datum Corporation is an energy copany that has office across North America and 3,000 employees.

Physical Locations
A Datum has the offices shown in the following table.

Network infrastructure
The office in Category has a 1-Gbps internet circuit. the offices in San Design and New York have 100-
Mbps internet circuits. The field site in Edmonton has a 3-Mbps internet circuit.

Departments
A Datum has the following departments:
1. Information technology (IT)
2. Project management
3. Marketing

Microsoft 365 and teams Environment ADatum recently purchased a Microsoft 365 E5 subscription that has the Microsoft Teams Domestic Calling Plan add-on. All users are assigned Microsoft 365 E5 and Microsoft Teams Domestic Calling Plan licenses and Calling Plans is deployed.
Azure AD has the default Cross-tenant access settings configured.
The Teams policies settings are configured as shown in the following exhibit.

The teams client is deployed to a non-persistent Virtual Desktop infrastructure (VDI) used by the project management department.
Allow guest access in Team is set to off.
The Microsoft Viva Connections app is deployed to all users.

Problem statements
A Datum identifies the following issues: An executive at the San Diego office report that video drop during Team meetings.
The Edmonton field site has limited bandwidth, and user report poor audio during Teams calls and meetings.
Users in the project management department report that they cannot give or take during teams calls and meeting while sharing their VDI desktop.

Background

Overview

CoHo Vineyard and Winery is based in the United States. The company has a single vineyard. The company distributes full pallets of wine worldwide and sometimes sells wine by using a private label. Grape growing and wine production operations are owned and operated by a third-party company. The company uses bottles, accessories, and other disposables from a company in China.

CoHo Vineyard and Winery opens a second location. This location manages inventory for Wine Club members and includes a wine tasting room. The location also includes a warehouse and distribution center.

The wine club currently has 200 members. The company hopes to increase this number.

The company holds events for club members in the tasting room and ships both full cases and individual bottles to members. The tasting room is not treated as a retail store. All sales to club members only and purchases must be made on-account.

Company structure

The following graphic shows the company structure:

Organization

The current organizational chart and roles are as follows:

Current environment

Coho Vineyard and Winery currently uses manual processes for most of its operations. The company stores names and phone numbers for club members and prospective club members in a Microsoft Excel workbook. The sales team currently tracks club membership in a separate system. Sales team stock awards are granted on a three-year basis. The solution for the sales team cannot be replaced for three years.

1. The types of wine, such as cabernet sauvignon and red blends are tracked as separate items. Each item will have a year associated with it, such as Red Blend 2017, 2018, 2019, etc. The items are updated for the year association annually.
2. Peak times for order entry could be in the hundreds. This typically happens when first and second shift workers overlap and all users are on the system, as well as orders imported in.
3. Packaging materials, bottles, and accessories are received in the warehouse FOB Destination from the manufacturer in China.
4. Each retailer has individual item numbers, barcode placement, descriptions and other additions such as pictures and details of the wine year and flavor notes.

CoHo Vineyard and Winery has outgrown their legacy ERP system and plans to implement Dynamics 365
Finance. CoHo wants to use out-of-the-box tools which are linked to the system where possible and not create new tools.

Requirements

Licensing and organization

1. Only the President/CEO, CFO, COO, Controller and VP Operations users must be able to access finance and warehouse features.
2. Warehouse users must only have access to warehouse function. All other users must have access to finance functions.
3. The distribution center must have mobile scanners for the warehouse. The tasting room will not have mobile scanners.
4. The inventory cost must be tracked separately by distribution center or tasting room.

Club membership and events

1. You must ensure the members created in their existing system are also customers in Dynamics 365
Finance and that the customers do not exist in both systems under multiple record numbers.
2. When tasting events are planned, text notifications must be sent out to the club members.
3. Text notifications must be sent out to non-club members to encourage the non-members to join the club.
4. During tasting events, CoHo will need access to place orders during the event but will not have the need for cash registers.

Warehouse and shipping

1. The system must be able to track inventory throughout the whole warehouse process.
2. A Certificate of Origin must accompany each shipment.
3. Private label items that are shipped to retailers must be stored and costed as a single item number at CoHo.
4. The system must be able to compare year-to-year performance of a single wine type.

Implementation

1. Business processes must be documented as step-by-step processes and must align with the process flows in a visual format.
2. Data will be migrated and is a requirement for order entry.
3. Data migration must be completed prior to testing.
4. You must track each step of process validation so that the users have ownership for their individual functional areas. The tracking system used should be integrated with the system where possible.

Issues

1. Users are struggling to understand the new system's processes.
2. CoHo is concerned that the go-live will may not go smoothly.

Background

Blue Yonder Airlines is a private airline company established in 1963 in Boston. The company completes over 2,000 flights a day with flights operating exclusively in North America. Blue Yonder Airlines is in the planning phase for replacing its current enterprise resource planning (ERP) with Dynamics 365 Finance, Supply Chain Management, and Commerce and is making solution architecture decisions prior to engaging the remainder of the implementation team.

Current environment

Technology

1. Blue Yonder Airlines operates on a custom-built ERP solution.
2. Blue Yonder Airlines uses a proprietary reporting and analytics platform that reports on data between multiple systems, including the ERP solution.
3. The ERP solution automatically pushes transactional data every five minutes to a separate database that the reporting and analytics platform uses for sales and operations planning (S&OP) activities.
4. SQL Server Reporting Services (SSRS) reports are used for several financial reports that are sent to vendors in the existing ERP solution.
5. Users utilize a third-party tool that selects alternate layouts of the reports depending on the users' requirements.
6. Blue Yonder Airlines currently uses Microsoft 365 and Office 365.

Implementation

1. The implementation of new solutions and features follows an Agile implementation strategy.
2. Blue Yonder Airlines has several highly skilled project managers.
3. Blue Yonder Airlines has a live Microsoft Dataverse instance that runs several model driven Microsoft
Power Apps apps. Several initiatives using Microsoft Power Automate and Power Virtual Agents are in the middle of implementations.

Development

1. There are five different functional groups, called pods, which fully own their development cycles for

different functionality in their ERP.
2. All code is deployed and managed by using Microsoft Visual Studio projects.
3. All development environments are currently hosted by a third-party company. The current costs are very expensive.
4. Blue Yonder Airlines plans to use the new ERP implementation to address performance and integration issues.

Licensing

1. Blue Yonder Airlines does not require licensing on its ERP solution because the system is custom.
2. Most users have more access within the ERP solution than required.

Requirements

Technology

1. The previous custom ERP data will be replaced with Dynamics 365 Finance and Operations apps in the current reporting and analytics platform.
2. Only native Dynamics 365 capabilities should be used.
3. The level of effort required from IT staff must remain the same.
4. Standard SSRS reports will be used.
5. The current third-party financial reporting tool does not integrate with Dynamics 365.
6. Blue Yonder Airlines has a highly experienced in-house team of implementation experts. It will implement Dynamic by using only internal employees. No Microsoft partner will be engaged in the implementation.

Data

1. Historical data will remain in the current system for reporting purposes.
2. Some sample data that needs to be migrated to Dynamics 365 includes:
- Data set 1 - Active airplanes - Planes that actively transport customers
- Data set 2 - Queued flights - Completed flights but not yet invoiced will be migrated
- Data set 3 - Flight consumption measurement - Units of measurement of gasoline consumed per flight
- Data set 4 - VIP customers - Customers that average $3,000 USD per flight

Development

1. Each of the pods' development teams must be able to deploy all of its code independently from one another.
2. Overlayering of base Microsoft or third-party code must be prevented.
3. Each developer must have their own environment.
4. Development environment costs should be as low as possible.
5. Developers should be able to access their development environments 24 hours a day.
6. The development team must create a performance strategy that involves the functional implementation team and the different development teams by using Microsoft recommendations.

User configuration

To save on implementation costs. Blue Yonder Airlines will determine which base security roles to assign to which users to conduct their day-to-day operations. Only base security roles will be used without modification.

Issues

Development

The development and functional teams are not taking ownership of the performance benchmark testing.
There are no functional designs, benchmark scenarios, or expectations setting created to date.

Security

Blue Yonder Airlines does not know how to configure the security of the users to enable access to complete its day-to-day operations.

Licensing

1. A licensing compliance audit has determined that the correct number of employees are added to the system but too many base and attach licenses are being used.
2. Some users will likely have to consolidate duties to maintain compliance.

Background

VanArsdel, Ltd. is a company that uses Microsoft Dynamics AX 2012 R3 in the United States, Canada, Mexico, and Brazil in an on-premises environment. The company implemented the solution by using Sure Step 2012. VanArsdel, Ltd. plans to upgrade to Dynamics 365 Finance, Dynamics 365 Supply Chain Management, and Dynamics 365 Commerce using Proseware, Inc. as the implementation partner.

VanArsdel, Ltd. has implemented 13 other software systems for customer management and sales.

Current Environment

Methodology

VanArsdel, Ltd. deploys a proprietary methodology named VanPMP. The company plans to use VanPMP for all software implementations. The company uses a standard project template for all new implementations.

Solution

Microsoft Power Apps is used by the sales team to enter sales orders. The orders are then integrated with the current Dynamics AX 2012 R3 instance asynchronously once every hour. All sales orders are invoiced through the invoicing batch process at the end of the day. Sales are used for all business-critical scenarios.

The external systems include 12 integrations, such as Microsoft Power Platform, Office 365, Azure, and third-party systems.

One of the automated accounts receivable import integrations, named integration 1, generates revenue in a business-to-business (B2B) scenario that is supported by sales orders. The integration runs every night and is always the first integration to be tested.

All regression testing is completed manually.

Security

The company uses Dynamics AX 2012 R3 in all the countries/regions in which they operate.

Because VanArsdel, Ltd. operates within the United States, the company must comply with government financial compliance standards. Government compliance requires that VanArsdel, Ltd. manufacturing divisions must not be able to approve purchase orders. Manufacturing managers must not be able to access data in other manufacturing sites. The manufacturing divisions belong to a single legal entity with multiple sites.

Requirements

Licensing
The implementation requires the following Dynamics 365 licenses:

1. 120 Supply Chain Management licenses
2. 60 Finance licenses
3. 50 Commerce licenses

Methodology
The implementation must use the VanArsdel, Ltd. proprietary methodology for the Dynamics 365 implementation. The methodology in the project template must use the Microsoft-recommended approach.
Progress must be tracked in a central location for VanArsdel, Ltd,, Microsoft, and Proseware, Inc. to view.

VanArsdel Ltd. requires a sample methodology in Lifecycle Services (LCS).

The project must coordinate project dates in the methodology with any required Microsoft touchpoints to ensure that the project is on track and implemented according to best practices.

Solution
The sales order entry Power Apps integration must be configured by using out-of-the-box solutions.

Integrations
The company has the following integration requirements:

1. Four integrations must run asynchronously.
2. Eight integrations must run synchronously.
3. The integrations must be able to run after applying updates to the system.

All items must have their own item pricing. Each item must have an MSRP and a selling price that is determined based on the date and location.

Testing
The user reporting test case needs to be reviewed by using the same process in the test environment.

The Regression suite automation tool (RSAT) must be used to automate every critical scenario. All other testing must be performed manually.

Integration 1 must be deployed first. All data must be created and tested in the correct sequence to ensure that pricing is applied correctly to the item.

Security
Dynamics 365 must be rolled out incrementally by country/region. The implementation must go live in the United States first, and then continue to the other countries/regions over the next 12 months.

VanArsdel, Ltd, must assign access to new users based on the site of the users.

VanArsdel, Ltd. requires that Proseware, Inc. perform the following:

1. Objective
1. Determine the software licensing costs for the system based on the contracted costs determined during the start of the project.
2. Objective
2. Audit the security roles for users in the manufacturing division.

Issues

Some users report that too many fields are displayed when the users create records in the Dynamics 365 AX 2012 R3 instance. These fields often prevent users from being productive.

Statement of work concerns Before the project kickoff, several of the VanArsdel, Ltd. IT team members had concerns after reviewing the statement of work. The primary concerns were raised by the following team members

1. An administrator named Admin1 reports a performance impact on multiple large integrations with the Dynamics 365 AX 2012 R3 implementation.
2. An administrator named Admin2 reports a concern with environment management with the global rollout.

All concerns must be reviewed and scheduled with all solution architects in workshops.

Testing

The Dynamics 365 AX 2012 R3 instance experiences frequent issues due to users running reports for an extended period of time on the same Application Object Server (AOS) service. A user named User1 reports a delay retrieving the same report in Dynamics 365.

Background

Margie's Travel company (http://www.margiestravel.com/) provides travel services to consumers. These services include package offers, special deals, and excursion add-ons such as jet ski and horseback rides in Jamaica. Margie's Travel negotiates rates with multiple vendors and secures bundled pricing for consumers, serving as a travel broker. Margie's Travel only sells services and does not have any tangible products or merchandise.

Margie's Travel began in 1994 when Margie, CEO, and president, planned group trips for her friends in the United States (US). As this grew organically, Margie's created a second company based in Jamaica, followed by the acquisition of a third company in the United Kingdom (UK). The company has grown fast challenging the current systems that support the business model. Margie has determined it is time to implement Dynamics 365 Finance.

Current environment

Application and environment

The current system has the following structure:

1. In the US, employees use SoftwareA, accounting software, which is a desktop installation package for small businesses and single users.
2. In the UK, employees use SoftwareB, ERP (enterprise resource planning) software installed on local servers. The cost of maintaining SoftwareB licensing is high, and Margie's Travel has decided against the software and associated overhead costs.
3. In Jamaica, employees use SoftwareC, a homegrown application based on spreadsheets. Local sales representatives use pen and paper in the field.
4. Margie's Travel employees use personal email addresses and chat tools and text each other directly due to the lack of corporate tools.
5. IT department resources are located in the US and are responsible for management of all software support.
6. Margie's Travel company does not have standardized processes across the organization.
7. Each country's manager is responsible for system downtime. This has proven to be a challenge due to the multiple time zones across the organization and the centralized IT department.

Vendors and purchasing

As customers purchase packages, Margie's Travel can claim rebates with the providing vendor for every package sold. The rebates are claimed quarterly, and internal workflows have been established for approval prior to vendor submission. The workflows for package offerings eligible for rebates can be complex. User2 has created Visio diagrams for the associated approval processes.

Customer relations

1. Customers exist in all three current countries/regions where Margie's Travel operates.
2. Margie's Travel offers consumers a loyalty program. Consumers can earn points per dollar spent across all in countries in which Margie's operates. The loyalty program is currently managed by using a spreadsheet.

Requirements

Applications and environment

1. All three countries must use Dynamics 365 Finance.
2. The system must allow for updates to be applied at the same time as they are periodically released.
3. Margie's Travel requires that the new business processes be standardized and follow industry best practices.
4. Margie's Travel requires implementation of Office 365 and Microsoft Teams to streamline their operations. The IT department will be responsible for troubleshooting these applications, along with Dynamics 365 Finance.
5. The infrastructure team must ensure that separate environments are created for development and build, prior to moving to test and eventually gold environments.
6. The infrastructure team must move the code for the loyalty program to test environment.
7. The CTO has directed the infrastructure team to guarantee they are on the most current version available at the time of go-live.
8. The go-live activities must be coordinated across all countries, with data validation planned for each time zone.
9. Once user acceptance testing (UAT) has been completed, the project manager must report the number of tenants for production to Microsoft.
10. A report must show seasonality and weather patterns so that Margie's Travel does not offer excursions during timeframes where severe weather is predicted.
11. Sales representatives in the field will only be licensed for Microsoft 365 and Microsoft Power Platform.

Vendor negotiations

1. Rebates must be consolidated at the vendor level.
2. A single claim must be sent to the vendor on a monthly basis for all sales.

Customer relations

1. Customers must be identified with the same customer ID across all companies and systems, and automatically update cross-references as new records are created.
2. Margie's Travel wants to enable customer self-service in the future for customers based in the US and UK. This feature is not planned for the initial system rollout; however, the CIO has asked that the roadmap be created for Dynamics 365 Customer Service and Dynamics 365 Commerce applications in the future. In addition, the CIO wants to ensure that the old customer numbers can be matched to a new standardized format.
3. New customers in Jamaica must be reviewed and approved due to frequent customer data discrepancies. The sales representatives in the field will enter information that must be routed to validate against existing data.

Issues

Applications and environment

1. The IT department needs help troubleshooting post go-live with the least costly solution.
2. The CTO has learned that there are updates to globalization features in Dynamics 365 Finance. The IT staff has been tasked with ensuring that they are the first group to receive these updates.
3. The company is unable to consolidate financials with the existing systems.
4. The current chart of accounts (COA) does not match between the companies. The chart of accounts

must have accounts manually mapped monthly because no controls can be enabled through multiple systems.
5. The CEO is considering the acquisition of additional companies in the same countries as the current companies. The consolidation structure may change within the first 90 days of go-live. Margie's does not want to finalize the consolidation structure for a hard-close at month's end until this has been finalized.
6. Due to resource constraints, the IT department only has the capacity to apply service updates to all countries at once, not as individual tasks.
7. The IT department has limited knowledge of Microsoft 365, Microsoft Teams, and Dynamics 365
Finance. The IT department will be unable to support the applications. The CTO must determine the strategy for managing the support-related risk.
8. The IT department has decided not to code for globalization issues because they are in an upcoming service update. They are closing in on go-live and need to make sure that the updates are applied in time.
9. A mock cutover was conducted. It was unsuccessful due to lack of coordination across the countries.
The lack of success created timing issues with data uploads from centralized IT and validation at the country level. User1 must use a standard template to prevent the mock cutover issue happening at go-live.

Vendor negotiations

1. The rebates cannot be claimed because disparate systems today do not allow for consolidation to ensure that thresholds are met to claim rebates.
2. The accounts receivable and accounts payable departments are unclear about the workflows associated with the rebate process. User2 must ensure that representatives from each department validate that they have tested their respective steps in the overall process. Testing feedback must be communicated to User2.

Customer relations

1. Customers are frustrated because while there is an expectation of white-glove service, customer number and other lookup information is not available in all countries. A customer travelling from the US to the UK must provide multiple pieces of information for them to be re-entered into the country-specific software system. The CIO knows this problem will become worse in the future with the addition of applications to the roadmap.
2. Customer service is unable to access all customer order history because it exists across three different systems. Local installations of software prevent lookups in each system and require a single dashboard to display the information.
3. A hurricane has been predicted for an upcoming tropical destination. Customers who are impacted by the hurricane either want a refund or want to rebook for another date. A customer does not know their customer number, but provides their name, address, and phone number.
4. Margie's Travel learns that the loyalty program across multiple countries is not a standard industry process and is not a standard feature in Dynamics 365 Finance.
5. The project manager does not have a process list to use as a baseline for the project.
6. Customers who sign up for add-on Jamaica excursions bring friends who have not signed up ahead of time. The sales representatives record the customer information on paper, take payment, and then enter the information into the system later. The information is frequently inaccurate and creates discrepancies.

Background

Overview

CoHo Vineyard and Winery is based in the United States. The company has a single vineyard. The company distributes full pallets of wine worldwide and sometimes sells wine by using a private label. Grape growing and wine production operations are owned and operated by a third-party company. The company uses bottles, accessories, and other disposables from a company in China.

CoHo Vineyard and Winery opens a second location. This location manages inventory for Wine Club members and includes a wine tasting room. The location also includes a warehouse and distribution center.

The wine club currently has 200 members. The company hopes to increase this number.

The company holds events for club members in the tasting room and ships both full cases and individual bottles to members. The tasting room is not treated as a retail store. All sales to club members only and purchases must be made on-account.

Company structure

The following graphic shows the company structure:

Organization

The current organizational chart and roles are as follows:

Current environment

Coho Vineyard and Winery currently uses manual processes for most of its operations. The company stores names and phone numbers for club members and prospective club members in a Microsoft Excel workbook. The sales team currently tracks club membership in a separate system. Sales team stock awards are granted on a three-year basis. The solution for the sales team cannot be replaced for three years.

1. The types of wine, such as cabernet sauvignon and red blends are tracked as separate items. Each item will have a year associated with it, such as Red Blend 2017, 2018, 2019, etc. The items are updated for the year association annually.
2. Peak times for order entry could be in the hundreds. This typically happens when first and second shift workers overlap and all users are on the system, as well as orders imported in.
3. Packaging materials, bottles, and accessories are received in the warehouse FOB Destination from the manufacturer in China.
4. Each retailer has individual item numbers, barcode placement, descriptions and other additions such as pictures and details of the wine year and flavor notes.

CoHo Vineyard and Winery has outgrown their legacy ERP system and plans to implement Dynamics 365
Finance. CoHo wants to use out-of-the-box tools which are linked to the system where possible and not create new tools.

Requirements

Licensing and organization

1. Only the President/CEO, CFO, COO, Controller and VP Operations users must be able to access finance and warehouse features.
2. Warehouse users must only have access to warehouse function. All other users must have access to finance functions.
3. The distribution center must have mobile scanners for the warehouse. The tasting room will not have mobile scanners.
4. The inventory cost must be tracked separately by distribution center or tasting room.

Club membership and events

1. You must ensure the members created in their existing system are also customers in Dynamics 365
Finance and that the customers do not exist in both systems under multiple record numbers.
2. When tasting events are planned, text notifications must be sent out to the club members.
3. Text notifications must be sent out to non-club members to encourage the non-members to join the club.
4. During tasting events, CoHo will need access to place orders during the event but will not have the need for cash registers.

Warehouse and shipping

1. The system must be able to track inventory throughout the whole warehouse process.
2. A Certificate of Origin must accompany each shipment.
3. Private label items that are shipped to retailers must be stored and costed as a single item number at CoHo.
4. The system must be able to compare year-to-year performance of a single wine type.

Implementation

1. Business processes must be documented as step-by-step processes and must align with the process flows in a visual format.
2. Data will be migrated and is a requirement for order entry.
3. Data migration must be completed prior to testing.
4. You must track each step of process validation so that the users have ownership for their individual functional areas. The tracking system used should be integrated with the system where possible.

Issues

1. Users are struggling to understand the new system's processes.
2. CoHo is concerned that the go-live will may not go smoothly.