Infor M3 Cloud Configuration Guide

Copyright © 2020 Infor

Important Notices
The material contained in this publication (including any supplementary information) constitutes and
contains confidential and proprietary information of Infor.
By gaining access to the attached, you acknowledge and agree that the material (including any
modification, translation or adaptation of the material) and all copyright, trade secrets and all other
right, title and interest therein, are the sole property of Infor and that you shall not gain right, title or
interest in the material (including any modification, translation or adaptation of the material) by virtue
of your review thereof other than the non-exclusive right to use the material solely in connection with
and the furtherance of your license and use of software made available to your company from Infor
pursuant to a separate agreement, the terms of which separate agreement shall govern your use of
this material and all supplemental related materials ("Purpose").
In addition, by accessing the enclosed material, you acknowledge and agree that you are required to
maintain such material in strict confidence and that your use of such material is limited to the Purpose
described above. Although Infor has taken due care to ensure that the material included in this publication
is accurate and complete, Infor cannot warrant that the information contained in this publication is
complete, does not contain typographical or other errors, or will meet your specific requirements. As
such, Infor does not assume and hereby disclaims all liability, consequential or otherwise, for any loss
or damage to any person or entity which is caused by or relates to errors or omissions in this publication
(including any supplementary information), whether such errors or omissions result from negligence,
accident or any other cause.
Without limitation, U.S. export control laws and other applicable export and import laws govern your
use of this material and you will neither export or re-export, directly or indirectly, this material nor any
related materials or supplemental information in violation of such laws, or use such materials for any
purpose prohibited by such laws.

Trademark Acknowledgements
The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or
related affiliates and subsidiaries. All rights reserved. All other company, product, trade or service
names referenced may be registered trademarks or trademarks of their respective owners.
Publication Information
Release: Infor M3 Cloud 11.x
Publication Date: November 3, 2020
Document code: m3cs_11.x_csm3cg__en-us
 Contents

Contents

About this guide.................................................................................................................................6

Contacting Infor.................................................................................................................................6
Chapter 1: Requirements...................................................................................................................7
Required applications........................................................................................................................7
Required information.........................................................................................................................7
Chapter 2: Configuration checklist...................................................................................................8

Chapter 3: Configuration overview...................................................................................................9

About the CloudSuite........................................................................................................................9
Integration with other products in the CloudSuite..............................................................................9
Point to point integrations...............................................................................................................9
Concepts and definitions specific to this configuration....................................................................10
Accounting entity..........................................................................................................................10
Location.......................................................................................................................................10
Logical ID.....................................................................................................................................10
Chapter 4: Getting started...............................................................................................................11
Determining the bootstrap administrator.........................................................................................11
Accessing your cloud environment (tenant)....................................................................................11
Verifying access to your applications...............................................................................................11
Chapter 5: Configuring security......................................................................................................13
Setting up M3 Cloud to use single sign on......................................................................................13
Users in M3 CE............................................................................................................................13
Chapter 6: Configuring access to M3 CE Core..............................................................................14
Users and roles...............................................................................................................................14
Configuring user access to M3 CE Core through Infor Ming.le....................................................15
Configuring additional system administrator access to M3 CE Core through Infor Ming.le.........18

Infor M3 Cloud Configuration Guide | 3

 Contents

Setting up roles............................................................................................................................18
Chapter 7: Configuring M3 CE Core...............................................................................................20
Configuring M3 CE Core to send and receive BODs in ION...........................................................20
Tasks completed by the Infor Cloud team....................................................................................20
Understanding how applications connect to ION.........................................................................20
Architectural overview and data flow............................................................................................21
Partner.........................................................................................................................................24
Specifying or editing translation data...........................................................................................24
Verifying the ION configuration....................................................................................................26
Chapter 8: Installing the M3 Cloud File Transfer client.................................................................28
Downloading the M3 Cloud File Transfer client package.................................................................29
Installing the grid for the M3 Cloud File Transfer client....................................................................30
Setting access rights to folders.......................................................................................................31
Installing the M3 Cloud File Transfer client on Grid.........................................................................32
Chapter 9: Configuring Infor Localization Services for M3 CE Core...........................................33
Configuring Infor Tax Authority Connector.......................................................................................33
Configuring Infor Spanish Tax Authority Connector.....................................................................33
Configuring Infor Italian Tax Authority Connector.........................................................................34
Chapter 10: Configuring the M3 Implementation Accelerator solution.......................................35

Chapter 11: Configuring Infor Data Lake........................................................................................36

Verifying the data flow between M3 Event Hub and Infor Data Lake...............................................36
Sending the initial data load for custom documents........................................................................36
Verifying the data flow to Data Lake................................................................................................37
Chapter 12: Configuring and integrating other applications in the CloudSuite.........................38
Configuring App Builder..................................................................................................................38
Configuring Infor Coleman AI Platform............................................................................................38
Configuring Coleman Digital Assistant............................................................................................38
Configuring Configure Price Quote.................................................................................................38
Configuring CRM.............................................................................................................................39
Configuring Document Capture.......................................................................................................39
Configuring Dynamic Enterprise Performance Management..........................................................39
Configuring EAM.............................................................................................................................39
Configuring Expense Management.................................................................................................39

Infor M3 Cloud Configuration Guide | 4

 Contents

Configuring Factory Track................................................................................................................40

Configuring Governance, Risk and Compliance - Authorization Insight..........................................40
Configuring Governance, Risk and Compliance - Process Insight..................................................40
Configuring M3 Customer Lifecycle Management..........................................................................40
Configuring M3 Inventory Planning Workbench..............................................................................40
Configuring Mongoose (on-premises and single tenant cloud).......................................................41
Configuring Nexus...........................................................................................................................41
Configuring PLM for Fashion...........................................................................................................41
Configuring PLM for Process..........................................................................................................41
Configuring Rhythm for Commerce.................................................................................................41
Configuring Sales Hub....................................................................................................................42
Configuring Supplier Rebate...........................................................................................................42
Configuring Supply Chain Planning.................................................................................................42
Configuring M3 Analytics, Infor Data Lake, and Birst......................................................................42
Configuring M3 Equipment Quotation Management.......................................................................42
Configuring M3 Graphical Lot Tracker.............................................................................................43
Configuring M3 Inventory Planning Workbench..............................................................................43
Configuring Making Tax Digital for VAT...........................................................................................43
Connecting to M3 Planning Workbench or M3 Scheduling Workbench..........................................43
Chapter 13: Optional post-provisioning steps for M3 CE Core....................................................45
Enabling M3 Financial Business Messages (M3 FBM) per country................................................45
Downloading the data flows for M3 FBMs....................................................................................45
Importing the custom noun data for M3 Financial Business Messages.......................................46
Importing the data flows for M3 Financial Business Messages...................................................46
Verifying the connection points and data flow for M3 and M3 FBM.............................................46
Appendix A: Troubleshooting..........................................................................................................54
Data is not flowing properly.............................................................................................................54
Issue: no BODs reaching target system......................................................................................55
Issue: no BODs reaching the target system during initial load....................................................56
Issue: one or several BODs not reaching the target system........................................................56
Issue: Divisions for a company are not displayed in the BODProcessor list................................58

Infor M3 Cloud Configuration Guide | 5

 About this guide

About this guide

This guide provides information for the configuration and implementation of Infor M3 Cloud, primarily
Infor M3 CE Core, in a multi-tenant cloud environment. This guide is also applicable for Infor CloudSuite
Chemicals, Infor CloudSuite Distribution Enterprise, Infor CloudSuite Equipment, Infor CloudSuite
Fashion, and Infor Cloudsuite Food & Beverage.

Intended audience
This guide is intended for the system administrator or consultant who configures Infor M3 Cloud,
primarily Infor M3 CE Core, for use with Infor OS in the cloud.

Contacting Infor
If you have questions about Infor products, go to Infor Concierge at https://concierge.infor.com/ and
create a support incident.
The latest documentation is available from docs.infor.com or from the Infor Support Portal. To access
documentation on the Infor Support Portal, select Search > Browse Documentation. We recommend
that you check this portal periodically for updated documentation.
If you have comments about Infor documentation, contact [email protected].

Infor M3 Cloud Configuration Guide | 6

 Requirements

Chapter 1: Requirements

Ensure that all requirements are met.

Required applications
Ensure that you have system administrator access to these applications in the cloud:
• Infor M3
• Infor OS applications

Required information
Obtain this information from the Infor Cloud team before you begin the integration:
• Administrator account and access information for your hosted Infor environment
• Name of the M3 CE Core instance or logical ID that is used to connect with Infor ION.
• Tenant ID that is used to connect the application to Infor ION.
• Enterprise organization structure, that is accounting entities.
• Location of content source files to be imported into ION and Infor Ming.le.

Infor M3 Cloud Configuration Guide | 7

 Configuration checklist

Chapter 2: Configuration checklist

Follow this checklist to integrate the components in the CloudSuite.

Complete Task Reference

□ Understanding the applications in the Integration with other products in the
CloudSuite and some related concepts. CloudSuite on page 9
Infor M3 Cloud Solution Overview
□ Getting started Getting started on page 11
□ Configuring security. Configuring security on page 13
□ Configuring user access and roles. Configuring access to M3 CE Core on page
• Configuring user access to M3 CE 14
Core in Infor Ming.le
• Configuring additional system admin-
istration access to M3 CE Core
through Infor Ming.le
• Setting up roles in Infor Ming.le
• Associating Infor Ming.le users and
roles with users in other applications
in the CloudSuite
• Optionally: Setting up distribution
groups
□ Configuring M3 CE Core. Configuring M3 CE Core on page 20
□ Configuring M3 CE Core with Infor ION to Configuring M3 CE Core to send and re-
send and receive BODs. ceive BODs in ION on page 20
□ Configuring Infor Data Lake with M3 CE Configuring Infor Data Lake with M3 CE
Core Core
□ Configuring Infor Localization Services Configuring Infor Localization Services for
with M3 CE Core M3 CE Core on page 33
□ Configuring and integrating other applica- Configuring and integrating other applica-
tions in the CloudSuite. tions in the CloudSuite on page 38

Infor M3 Cloud Configuration Guide | 8

 Configuration overview

Chapter 3: Configuration overview

Before you complete the configuration tasks, you must understand what is provided in the CloudSuite
and how the components of the CloudSuite communicate. You should also be familiar with the list of
related concepts and definitions.

About the CloudSuite

This solution overview document provides a high-level explanation of the CloudSuite and a summary
of the applications that are included. It also includes information about configuration, personalization,
extension, and integration options.

Integration with other products in the CloudSuite

The M3 CE Core application uses different integration methods to communicate with other products
in the suite.

Point to point integrations

Point to point integrations use APIs to connect to Infor M3. You may require to configure additional
parameters or master data in each of the applications to complete the integration. See the appropriate
integration guides.

Factory Track
See the Infor M3 Integration Guide for Infor Factory Track. To complete the additional master data
setup, see chapter 3.

Infor M3 Cloud Configuration Guide | 9

 Configuration overview

Concepts and definitions specific to this configuration

To configure the CloudSuite correctly, you must understand these terms and how they are defined in
this application. Together, these terms determine where inbound BOD information is processed, or the
outbound instance and location to which the BOD information should be associated.

Accounting entity
An accounting entity usually represents a legal or business entity that maintains its own general ledger.
Each transaction belongs to only one accounting entity. The accounting entity can also be defined as
the owner of certain master data within the enterprise.
For M3, the accounting entity corresponds to a division within a company. The accounting entity is set
according to the <CONO_DIVI> syntax.

Location
A location is the physical location that is associated with data or transactions. The location can be, for
example, a warehouse, a manufacturing location, a project location, or an office. Locations are published
in the Location BOD. A location is required for all transactional BODs and is usually the location from
which a transaction or record is generated.
M3 uses two types of locations, warehouse and site:
• The warehouse location type is published from 'M3 Warehouse.Open' (MMS005).
• The site location type is published from 'M3 Facility.Open' (CRS008).

Logical ID
The logical ID is a unique identifier that is used in the communication of data between products in the
tenant’s environment. A logical ID is assigned to each instance of a product, such as a site. In ION,
the logical ID is used to route BODs correctly. Infor Ming.le uses the logical ID to determine which
application to launch when you click a drillback.
In Infor Ming.le, only one logical ID is assigned to each application, regardless of the number of instances
of the application.

Infor M3 Cloud Configuration Guide | 10

 Getting started

Chapter 4: Getting started

Ensure that all of these requirements are met before you start the configuration.

Determining the bootstrap administrator

Your tenant is delivered with an already assigned bootstrap administrator. The bootstrap administrator
is the only person who can initially access the tenant. This administrator performs the initial setup of
the tenant, including setting up access for other users.
You must designate one person as the bootstrap administrator. During the planning process, you must
provide the email address of the designated person to your Infor representative.
For business partners who configure a CloudSuite demo environment that is hosted by Infor, the
bootstrap administrator is typically the person who made the initial request for the demo environment.

Accessing your cloud environment (tenant)

After the environment has been provisioned, Infor sends an email to the bootstrap administrator with
this text in the subject line: !SECURE! Infor Provisioning Notification. This email
contains instructions for activating your Infor Ming.le user. It also
includes the URLs to access the environments.
Follow the instructions in this email to complete these tasks:
1 Activate and validate your access to Infor Ming.le using the instructions provided.
2 Validate access using the provided URLs and ensure that you can sign in to all environments.

Verifying access to your applications

After you sign in to the Infor Ming.le portal for the first time, ensure that you have system administrator
access to these applications in the cloud:

Infor M3 Cloud Configuration Guide | 11

 Getting started

1 Click User Menu and verify that you can access the Admin Settings and User Management
menu options.
2 Click App Menu and verify that you can access the applications for your CloudSuite, such as Infor
M3, Infor Sales Hub, Infor Ming.le, ION Desk, and Infor Document Management.
3 Verify that you can access all optional applications that you have licensed, such as Infor Factory
Track or Infor Configure Price Quote.

Infor M3 Cloud Configuration Guide | 12

 Configuring security

Chapter 5: Configuring security

Single sign on allows users to use one set of credentials to log into all Infor applications.
M3 CE is set up for single sign on in Infor Ming.le CE through the use of SAML authentication. To
achieve single sign on, a federation must be established between Infor Ming.le CE and the customer's
identity provider.

Setting up M3 Cloud to use single sign on

Infor Ming.le CE uses the SAML 2.0 protocol and can be federated with any customer-owned SAML
2.0-compatible identity provider to achieve single sign on.
For more information on the latest technical details, contact your project manager, customer service
manager, or service delivery manager.

Users in M3 CE
This user property for M3 users must be configured in Infor Ming.le.

M3 user alias
The M3 CE user ID is limited to maximum 10 characters and cannot use the Infor Ming.le user ID
directly. This is solved by the M3 User Alias field in Infor Ming.le. The value that is specified in this
field is used as the M3 user ID.
IFS can be configured to generate an M3 user alias automatically when a user is added, or to let an
administrator set it manually. A user with the IFSApplicationAdmin role can configure this in Infor Ming.le
in User Management > Security Administration > General Settings > Application Specific Settings
by selecting the Do not auto-generate User Alias while creating users check box.
When a user is created, a GUID is assigned. The GUID is stored as identity2, and this value is used
during authentication in M3 CE.

Infor M3 Cloud Configuration Guide | 13

 Configuring access to M3 CE Core

Chapter 6: Configuring access to M3 CE Core

Users, roles, and person IDs are defined and shared between Infor Ming.le and all other applications
that run through the Infor Ming.le portal.
Configuring access to M3 CE Core through Infor Ming.le requires these IFS security roles:
• DataAdministrator
• IFSApplicationAdmin
• UserAdmin
• Infor-SystemAdministrator
The user management solution in M3 CE Core consists mainly of two entities: Infor Federation Services
(IFS), which corresponds to the user management pages in Infor Ming.le, and M3 CE Core, which is
accessed through the M3 application icon in Infor Ming.le.
IFS is the internal system of record for users in the system. This is where users are added and updated
and where security roles are configured. IFS is responsible for storing user attributes that are retrieved
as claims when a session is constructed during sign-in. Federated security and single sign on (SSO)
are also configured in the IFS user interface. For information on how to add and update users, see the
Infor Ming.le online help.
M3 CE Core is the central part of the ERP system, the application where the business logic resides.
M3 CE Core keeps its own user record in the Business Engine (BE) database. M3 CE Core maintains
a mapping between IFS users and M3 CE Core users: each M3 CE Core user is mapped to the
corresponding user in IFS. M3 CE Core also maintains additional M3-specific attributes for each user.
User information is synchronized between M3 CE Core and IFS through BODs.

Users and roles

Because Infor Ming.le is the system of record for users, you must set up users in Infor Ming.le. Then
you can use BODs to synchronize them with other applications in the Infor Ming.le portal. After the
users are synchronized with the applications, you can continue user setup in any application.
You can perform these user management tasks in Infor Ming.le:
• Create users, including manual import of users
• Update users
• Delete or deactivate users

Infor M3 Cloud Configuration Guide | 14

 Configuring access to M3 CE Core

• Reset passwords
• Monitor recent user activity and mobile sessions

Configuring user access to M3 CE Core through Infor Ming.le

The Infor Cloud team configures the initial Infor Ming.le system administration user, roles, and several
other required accounts.

Caution: We recommend that you do not change the configuration of this initial system administrator
or the other required accounts.

You must add other users in Infor Ming.le before they can access your product through Infor Ming.le.

Synchronizing security users created in Infor Ming.le

When a new user is created in Infor Ming.le, the Sync.SecurityUserMaster BOD is published. M3
subscribes to the Sync.SecurityUserMaster BOD. A security user can be created in Infor Ming.le before
it is created in M3. A security user can be created in Infor Ming.le using either of these methods:
• Through 's web-based user interface, either manual or by importing .csv or .xml files, as described
in the online help.
• Through the REST-based SCIM interface of Infor Ming.le, as described in the online help.
This user information is required to create an M3 user:

Field Description or comment

First name Mandatory in IFS.
Last Name Mandatory in IFS.
Email Address Mandatory in IFS. This is the ID to use when logging in to the
CloudSuite.
M3 User Alias This value becomes the M3 user ID. It is a string of up to 10 char-
acters that can be automatically generated by IFS or set when
manually specifying or importing .csv or .xml files. It can only be
set once and you cannot update the value.
IFS ION-Person ID This field must have the same value as 'M3 User Alias' to send
alerts, tasks, and notifications in Infor Ming.le to the correct user.
Security Role 'M3UI-User' Assign the M3UI-User security role to all users that should be
registered in 'User. Open' (MNS150) in M3.
See the Infor Ming.le online help for a description of how to assign
a security role to all new users and existing users.

1 Activate a user in Infor Ming.le to publish a Sync.SecurityUserMaster BOD. M3 then receives the
Sync.SecurityUserMaster BOD and creates or updates the user record in 'User. Open' (MNS150).

Infor M3 Cloud Configuration Guide | 15

 Configuring access to M3 CE Core

Note: A user in Draft status will not be published and not created in M3.
These M3 user properties are synchronized from Infor Ming.le:
Name
This field is populated with First Name + Last Name values from Infor Ming.le.

User Status
This field is populated with Status. Status Active from Infor Ming.le translates to the M3 status
20-Active. The Disabled status from Infor Ming.le translates to the M3 status 90-Deactivated.

Email address
The email address in 'Email Address. Open' (CRS111) is populated with the Email Address
from Infor Ming.le.

We recommend that you always use Infor Ming.le to update the M3 user details that are controlled
by Infor Ming.le. M3 displays a warning when a manual update is attempted, but you can override
it. Changing such information causes mismatch between M3 and Infor Ming.le. If these user details
are updated in M3, they will automatically be replaced with the Infor Ming.le values next time
Sync.SecurityUserMaster is consumed.
2 Some fields in (MNS150) are specific to M3 and are not sent by Sync.SecurityUserMaster. Select
Infor M3 > Administration Tools > Enterprise Collaborator Administration > Server >
Agreement Control Properties and locate M3_SecurityUserMaster_Sync_In to configure
these fields.
3 Review this information:
accountingEntity
This is the default company and division that are set in (MNS150/E) in the Company and Division
fields. The property is populated with default values when the tenant is created, but can be changed
to the relevant Accounting Entity/M3 Company and Division.
Note: Verify that the value corresponds to an existing combination of company and division in
'Company. Connect Division' (MNS100). The accounting entity must correspond to an entry in
(MNS100), otherwise no users can be created.

m3UserDateFormat
This is the user date format that is set in 'User. Open' (MNS150). It is preset to YMD, but can be
changed. Permitted values are YMD, DMY, MDY, and YWD.

m3UserDecimalFormat
This is the decimal format of the user that is set in 'User. Open' (MNS150). It is preset to comma
(","), but can be changed. Permitted values are comma (","), period ("."), or blank value.

m3UserType
This is the user type that is set in (MNS150/E) in the User type field. It is preset to MING.LE, but
can be changed to a 10-character string.

manageM3RolesPerUserFromIFS
This is a property for controlling whether the role assignments per user in IFS should be
synchronized with M3. The default value is 0, which indicates that no synchronization is made.
Set this property to 1 to synchronize the role assignments per user in IFS with M3 'Roles per User.
Connect' (MNS410). IFS is the master of record, and the values in IFS override any manual
changes made in M3.

Infor M3 Cloud Configuration Guide | 16

 Configuring access to M3 CE Core

Note: Any record of roles in M3 that has no equivalent in IFS is removed from M3 according to
this example:
Example: manageM3RolesPerUserFromIFS is set to 1. M3 has these role assignments for user
JDOE in (MNS410):
• JDOE/ROLE1
• JDOE/ROLE2
IFS has these role assignments for user JDOE:
• JDOE/ROLE1
• JDOE/ROLE3
(MNS410) will be updated accordingly:
• JDOE/ROLE1 - will be kept since it exists in IFS
• JDOE/ROLE2 - will be removed since it does not exist in IFS
• JDOE/ROLE3 - will be added since it exists in IFS

useMingleLanguage
This is a property for controlling whether the Infor Ming.le user language should be synchronized
with M3. The Infor Ming.le user language is set in User Menu > User Settings > Localization
Settings > Language.
The default value for the property is 0, which indicates that no synchronization is performed. Set
this property to 1 to synchronize the Infor Ming.le user language with 'User. Open' (MNS150).
Only Infor Ming.le languages that are also valid M3 languages are considered. If the Infor Ming.le
language is not a valid M3 language, new users are assigned the language of the service user
MECSVC (GB), existing users are not changed.

Assigning users to an accounting entity in Infor Ming.le

When M3 accounting entities are available in Infor Ming.le, they can be mapped to users, either by
mapping the accounting entities per user, or by mapping the users per accounting entity.
1 To assign users to a specific Accounting Entity, click User Menu and selectUser Management >
Configure > Master Data Types > Accounting Entities
a Click the Details button to open the accounting entity.
b Click Add new item, search for users and click ADD to add a user.
c Select the Assign to New Users and Assign to all existing users check box for any
accounting entity, or M3 division, that should apply to all users.
2 To assign an accounting entity to a specific user, select User Management > Manage > Users
and select the user.
a Click User Details.
b Click the Accounting Entities tab.
c Click Add and select the applicable check boxes.
d Click Add & Close, and Save.
Infor Ming.le publishes Sync.SecurityUserMaster and M3 adds, updates, or removes corresponding
records in 'User. Access per Company Division'(MNS151). This function defines the
user's access to companies and divisions in M3.

Infor M3 Cloud Configuration Guide | 17

 Configuring access to M3 CE Core

Configuring additional system administrator access to M3

CE Core through Infor Ming.le
The Infor Cloud team initially configures the system administrator's access for a user between Infor
Ming.le and M3 CE Core.
Infor Ming.le provides a default Infor-SystemAdministrator role that enables full access to all products
that are linked to Infor Ming.le. M3 CE Core has the M3BE-SystemAdministrator role that allows access
to all M3 CE Core screens. When a user who has the Infor-SystemAdministrator or the
M3BE-SystemAdministrator role in Infor Ming.le is synchronized to M3 CE Core, that user automatically
has access to all M3 CE Core forms.

Setting up roles
This section covers user synchronization and security between M3 CE and Infor Ming.le.
The Cloud edition expects users to be managed in Infor Ming.le. When users are created and updated
in Infor Ming.le, the corresponding information must be passed to M3. M3 maintains a local copy of
the user information. Synchronization requires these BODs:
• SecurityUserMaster
• SecurityRoleMaster
• Person
• AccountingEntity
This synchronization is enabled by the M3-Mingle_security_BODs_integration data flow that is managed
in ION Desk.

Updates not covered by synchronization

M3 CE supports only a selection of the synchronization flows that are available for Infor OS:
• Synchronizing security users that are created in Infor Ming.le
• Synchronizing the accounting entities that are created in M3 to Infor Ming.le
• Assigning users to a security role in Infor Ming.le
Caution: These actions are not synchronized to the other system. These updates will be overruled
if a synchronization is initiated by the other system:
• Creating a security user in M3
• Updating a security user in M3
• Creating a location in M3
• Creating a security role in Infor Ming.le
• Updating a user-to-security role mapping in M3
• Updating a user-to-accounting entity mapping in M3
• Updating a user-to-location mapping in Infor Ming.le

Infor M3 Cloud Configuration Guide | 18

 Configuring access to M3 CE Core

• Updating a user-to-location mapping in M3

Managing security roles created in M3

Roles that are created in M3 in 'Roles. Open' (MNS405) are published to Infor Ming.le through
Sync.SecurityRoleMaster. The role is added in Infor Ming.le as a local M3 security role with the value
of the logical ID as Application Type.
If the role is updated in or removed from M3, the changes are synchronized to Infor Ming.le. If a role
that is removed from M3 has connected users in Infor Ming.le, the role is not removed from Infor Ming.le.
Note: Roles that are synchronized to IFS can be filtered using the M3 logical ID.
Click User Menu and select User Management > Configure > Master Data Types > Security Roles
to display all IFS security roles.

Assigning users to a security role in Infor Ming.le

You can associate a local M3 role with a user in Infor Ming.le.
1 To assign a role to a specific user, click User Menu, select User Management > Manage > Users.
2 Click User Details.
a Click the Security Roles tab.
b Click Add and select the applicable check boxes.
c Click Add & Close, and Save.

A Sync.SecurityUserMaster is published by Infor Ming.le, and depending on the setting for the
manageM3RolesperUserFromIFS control property, role and user mapping are stored in 'Roles per
User. Connect' (MNS410) in M3. You can also remove the user mapping in Infor Ming.le, and it
is synchronized with M3. If the M3 user status is 90-Deactivated, the user or role mapping is not
added in M3.
Note: Always maintain the relationship between users and roles in Infor Ming.le. If the
Sync.SecurityUserMaster control property manageM3RolesPerUserFromIFS is set to 1, any updates
that are performed in 'Roles per User. Connect' (MNS410) in M3 result in a mismatch between
M3 and Infor Ming.le. M3 is automatically updated with the information from Infor Ming.le the next time
a Sync.SecurityUserMaster is received.

Infor M3 Cloud Configuration Guide | 19

 Configuring M3 CE Core

Chapter 7: Configuring M3 CE Core

The applicable Implementation Accelerator is applied for the initial configuration of M3 CE Core.
For administration tasks, see the M3 CE Core Administration Guide.

Configuring M3 CE Core to send and receive BODs

in ION
This section describes how to configure M3 CE Core to communicate with ION. Integrations between
this product and other products use ION to send and receive BODs. For details about a specific
integration, see the appropriate integration guide.

Tasks completed by the Infor Cloud team

The Infor Cloud team has already set up M3 CE Core so that it can generate BODs and place them in
a message outbox from which Infor ION Connect can retrieve them. The team also has set up the
inbound message configuration, so that BODs sent to this application can process those messages.

Understanding how applications connect to ION

The Infor Cloud team has created connection points in ION Desk for each of your Infor cloud applications
that use ION. You cannot modify these connection points, but you can add to the list of documents
that can be sent or received by the connection point.
In an integration between two BOD-enabled products, data flows are set up to define the BODs that
flow between the application connection points.
A connection point can be reused in one or more data flows. See the section on ION Connect Modeling
in the Infor ION Desk User Guide - Cloud Edition for additional information about connection points
and data flows.

Infor M3 Cloud Configuration Guide | 20

 Configuring M3 CE Core

If you remove a document that is used in a data flow from a connection point, an error is shown in the
area of the data flow messages.
You cannot activate connection points separately. When you activate a data flow, the associated
connection points are activated.

Architectural overview and data flow

The diagram shows the application components that are involved in transferring BODs from Infor M3
Business Engine to ION and back.

Infor M3 Cloud Configuration Guide | 21

 Configuring M3 CE Core

The BOD outbound data flow is based on events. An event represents predefined data. The Event Hub
is the central place where all events are directed to its subscribers. The events from M3 Foundation
can be based on program or table operators (Start, Exit, Fail, Create, Update, Delete, Request or
Response). Events that trigger M3 BODs are based on table changes.
To trigger events from a specific database table, a rule is created in Event Analytics. A rule is always
placed in a rules session. When the rule is activated and the rule session started, events get published
by M3 Foundation and are subscribed by Event Analytics.

Infor M3 Cloud Configuration Guide | 22

 Configuring M3 CE Core

M3 BODs has its own set of standard rules as content in Event Analytics. These are predefined to
listen to changes for specific tables, fields, and values in Infor M3 Business Engine, and will publish a
new event called M3BEBODs. Invalid events are deleted.
The M3BEBOD event contains data from the M3 DB event and these additional fields:
• BODNoun: contains the name of the noun
• BODVerb: contains the name of the verb
• findDIVI: contains information for the M3 BOD Processor on how to handle the event. The available
values are NOLOOKUP, ALL, FACI, and WHLO.
The purpose of the M3BODProcessor is twofold:
• Enabling and disabling publishing of M3 BODs per company and division and BOD.
• Multiplying events where required to ensure that published M3 BODs are connected to the correct
AccountingEntity (CONO_DIVI) according to BOD standards.
The M3 BOD Processor is the subscriber of all M3BEBOD events. The events will be republished with
M3BODProcessor as publisher, and BODVerb combined with the BODNoun as event document name.
Based on the value in findDIVI, the M3BODProcessor will perform one of these steps:
• NOLOOKUP: do nothing
• ALL: one event is created per activated DIVI for the CONO in the event
• FACI: the DIVI value is added based on the FACI value in the event
• WHLO: the DIVI value is added based on the WHLO value in the event
The subscriber of the VerbNoun events from the M3 BOD Processor is Infor Enterprise Collaborator.
The standard BOD detection in Infor Enterprise Collaborator is based on the
AnalyticsHubPublisherDocName target group, which contains the targets, publisher and event document
name, for the event. To trigger a specific M3 Business Engine BOD Partner Agreement in Infor Enterprise
Collaborator, these requirements must be met:
• The M3 BOD Processor must be the publisher
• The event document name must match the specific BOD name in the agreement.
After subscribing to the VerbNoun events, several process steps must be performed in the agreement.
These common steps are available for all outbound BODs: The event document name must match the
specific BOD name in the agreement

Step Description
XML transform The data is retrieved from M3 Business Engine through APIs and compiled
into an XML file.
Apply Envelope This process packs the XML data in a BOD format.
Send This process sends the BOD to the ION Connector DB. ION retrieves the data
from the ION Connector DB and processes it.

Inbound BODs are sent from ION to ION Connector DB, where Infor Enterprise Collaborator collects
the BODs. Inbound BODs are detected on (identified by) the EC manifest com:ionBODType, which is
set from the IOBox metadata. After the detection, there are additional steps for an inbound Process

Infor M3 Cloud Configuration Guide | 23

 Configuring M3 CE Core

BOD, which send an Acknowledge BOD back to ION. The most common step is XML transform,
which uses APIs to add data to M3 Business Engine.
Inbound BODs are sent from ION to Infor Enterprise Collaborator through the IOBox. Infor Enterprise
Collaborator process the BOD and updates data to Infor M3 Business Engine through M3 APIs.
Both M3 BOD Processor and Infor Enterprise Collaborator connect to Infor M3 Business Engine using
API calls. Their connection to the API is performed using service users BODSVC and MECSVC
respectively.
Because these 2 service users must have access to all companies and divisions, these checks must
be performed to verify the required setup exists:
1 In Infor M3 Business Engine, 'User. Open' (MNS150), go to the BODSVC user.
2 Use related option 11='User Permissions to Cmp/Div' to open 'User. Access per Company Division'
(MNS151).
3 Verify that the user has access to all companies and divisions.
4 If required, grant access to all companies and divisions using related option 21='Update User
Access all Cmp/Div' in 'User. Open' (MNS150).
5 Repeat steps 1 to 4 for the MECSVC user.
Note: When creating new companies or divisions, permissions must be granted for both BODSVC
and MECSVC. If not, M3 Business Engine BOD Processor and Infor Enterprise Collaborator cannot
access Infor M3 Business Engine and the dependent API will fail.

Partner
A partner is defined in M3 as an external party or as an application that requires specific settings for
integration with M3. The partner settings are managed in ‘M3 Stock Msg Partner.Open’
(MMS865).

Specifying or editing translation data

Follow these steps to set up the data translation in 'Business Message Data. Translate' (CRS882). For
data that is valid for the entire M3 Business Engine company, you must specify the data in company /
*blank division. If the data is different per division, enter data for a specific company / division.
This task requires the M3EC-Administrator IFS Security Role.
Note: The translation information must be specified for the correct company/division.
1 In Administration Tools > Enterprise Collaborator Administration, select Utilities > MBMTRN
Update.
a Select the Cumulative or not check box.
b Select the M3 Client Keystore check box.
c Select the check boxes corresponding to the relevant mapping names, and click Update .
Note: This step is only required in these cases:

Infor M3 Cloud Configuration Guide | 24

 Configuring M3 CE Core

• A new standard BOD has been delivered.

• Data translations for an updated standard BOD have been altered.
• You have created a new custom BOD containing data translations.
• You have customized a standard BOD and altered the data translations.
If no mapping is selected, all the mappings are processed.
2 In M3, open 'M3 Business Message Data Translation.Displ' (CRS881) and specify
ION in the Msg std field to display all possible records that have been generated from the supplied
BODs.
Note: The next steps depend on the entry that the business message has in the Data element
column.
3 Right-click the business message and select Related > Translate CTRL+11.
4 In (CRS882/B1), specify the M3 data and Message data for the business message:
• For business messages with the languageCodes data element, add one record for each of
the languages that you want to translate in the CRS882 panel for Company / *blank division.
• The M3 data field should contain the M3 language code.
• The Message data field should contain the corresponding language code according to
the RFC 1766 standard, for example, en-US.
• For business messages with the UOMCode data element, add one record for each of the unit
of measures that you want to translate in the CRS882 panel for Company / *blank division.
• The M3 data field should contain the M3 unit of measure.
• The Message data field should contain the corresponding unit of measure code according
to X-12 EDI standard.
Note: Unless all applicable integrated systems are configured to use the same set of unit of
measures, data translation settings must be performed for both incoming and outgoing
messages.
• For business messages with the CountryCode data element, add one record for each country
code that you want to translate in the CRS882 panel for Company / *blank division.
• The M3 data field should contain the M3 country code.
• The Message data field should contain the corresponding country code according to ISO
3166-1 standard.
Note: Unless all applicable integrated systems are configured to use the same set of country
codes, data translation settings must be performed for both incoming and outgoing messages.
• For business messages with the Currency data element, add one record for each currency
that you want to translate in the CRS882 panel for Company / *blank division.
• The M3 data field should contain the M3 currency defined in CRS055.
• The Message data field should contain the corresponding currency code according to the
ISO 4217 standard.
Note: Currency translation is required if the currency notation in M3 deviates from ISO
standards.
• For business messages with the TransportationMethodCode data element, add one record
for each of the Transportation Methods you want to translate in the CRS882 panel for Company
/ *blank division.
• The M3 data field should contain the M3 Delivery Term defined in CRS065.
• The Message data field should contain the corresponding transportation method according
to Incoterm standard.

Infor M3 Cloud Configuration Guide | 25

 Configuring M3 CE Core

Note: We recommended to set up the delivery terms according to Incoterms in M3. In that
case, no translation is required. Otherwise data translation settings must be performed for both
incoming and outgoing messages.
• For business messages with the ShippingMaterial data element, add one record for each of
the shipping materials you want to translate in the CRS882 panel for Company / *blank division.
• The M3 data field should contain the M3 packaging type defined in MMS050.
• The Message data field should contain the corresponding packaging type that should be
used when communicating with integrated systems.
Note: Unless all applicable integrated systems are configured to use the same set of shipping
material, data translation settings must be performed for both incoming and outgoing messages.
5 Click Create.
6 In CRS882/E, specify a Name and a Description. Click Next.
7 Repeat the required steps for each business message for which data translation is applicable.

Verifying the ION configuration

Verify that the connections are set up correctly.

Verifying that BODs are generated

1 Determine what user actions generate certain BODs. See outbound bods and event rules in M3
CE Core Administration Guide..
2 Perform those user actions in M3 CE Core.
3 In ION Desk use OneView or other ION Desk functions to review the messages.
If messages are not displayed in ION Desk, check Administration Tools > Enterprise Collaborator
Administration > Messages to see if BODs were generated but were not retrieved by ION.
4 If messages are not flowing, review the XML data for the BOD.

Verifying that ION receives data

To verify that ION is receiving BODs from M3 CE Core, perform these actions in Infor ION Desk:
• Select Connect > Active Connection Points to show the message queue counts.
• Select OneView to show individual messages, if they are enabled.
• Select Connect > Error BODs to see if any errors were reported.
If you encounter problems, see Data is not flowing properly on page 54.

Infor M3 Cloud Configuration Guide | 26

 Configuring M3 CE Core

Verifying the data flow between applications

After you create and activate data flows to other applications, you can check the message inbox area
of the other applications, to ensure that data is flowing between the applications.

Infor M3 Cloud Configuration Guide | 27

 Installing the M3 Cloud File Transfer client

Chapter 8: Installing the M3 Cloud File Transfer client

Infor M3 Cloud File Transfer Agent (CFT) is a client-server component for transferring files between
Infor M3 CE Core and a tenant's private area. The Infor M3 Cloud Transfer client should be installed
on the local server.
Print files, M3-exported and imported files, configuration data, and private content files from tenants
are transferred by CFT.
See Infor M3 Cloud Technical Requirements for the technical requirements for Windows Server and
SQL server.
One client should be installed per tenant. The size of the file storage area must consider the number
of files that are expected to be stored in that area.
Before you can install the required components on premises, you must perform these pre-installation
tasks:
• Sign in as a system administrator on your local Windows server that hosts the SQL Server.
• Take note of the tenant administrator's user name and password that are required for installing the
Cloud File Transfer client on premises.
• Take note of the SQL Server administrator (sa) password that is required during installation.
These folders are created during installation. These default folder names are used in this guide:

Folder name Description

C:\Infor\M3FILES The root folder for M3 file storage of M3 Business
Engine-generated files and reports
C:\Infor\M3PRINTS The default folder for stream files

C:\Infor\FILES The root folder for non-M3 file storage

Your user in Infor Ming.le must belong to these IFS security roles:
• GRID-Administrator: required to view Download Client
• M3BE-FndAdmin: required to access the Infor M3 Cloud File Transfer Agent Administration
page
See the Infor Operating Service documentation for information about Infor Ming.le role administration.

Infor M3 Cloud Configuration Guide | 28

 Installing the M3 Cloud File Transfer client

Downloading the M3 Cloud File Transfer client package

1 Sign in to Infor Ming.le as tenant administrator.
2 Click Infor M3.
3 Select Administration Tools > Cloud File Transfer Agent Administration.
4 Select Download Client.
5 Click Download Client Package to create the grid certificate and download the .zip file containing
the file transfer agent client.
The certificate and the transfer agent are used for all file transfers between the CloudSuite and
the local systems, for example local printers.
6 Locate the downloaded files on your server.
7 Extract the files in the .zip file cftinstaller.zip.
These files are extracted:
cftinstaller.jar
clientcert_FileTransferClient.ks
FileTransferClient.properties
gridinstaller.jar
FileTransferClient.gar
8 Double-click cftinstaller.jar to start the installation.
9 In the User Account Control window, click Yes to allow the program to make changes to this
computer.
10 Click Next.
11 Accept the default installation location.
12 To configure client settings, specify this information:
Note: The values for server and port are automatically added to the form when you download the
client package. These values are obtained from the location of the client package.
Server for Grid on Cloud
Specify the fully qualified domain name (FQDN) of the server.

Port of Grid on Cloud

Verify the HTTPS port number for this server.

M3PRINTS
The folder to contain the temporary stream files will be created in this location: C:\Infor\
M3PRINTS.

M3FILES
The root folder where the M3-generated files should be stored will be created in this location: C:
\Infor\M3FILES.

FILES
The default folder for other downloaded files.
Note: If you change any of the default folder names, use your specified folders when setting the
access rights.

Infor M3 Cloud Configuration Guide | 29

 Installing the M3 Cloud File Transfer client

13 Click Generate Properties File. A message is displayed when the file is created.
14 Click Next. The installation begins.

Installing the grid for the M3 Cloud File Transfer client

1 Select the installation location and click Next.
The default location is C:\Infor\InforIONGrid and will be used in references to administration
tasks and groups.
2 Select the applicable JDK location and click Next.
3 Configure the Grid settings.
Host FQDN or IP
Specify the Fully Qualified Domain Name (FQDN) or IP address of the grid.
Note: In the port fields, specify a port range with unused ports. We recommend using 26000 or
higher.

Host Router https port

Specify a port number, for example 26000.

Host Router port

Specify a port number, for example 26001.

Bootstrap http port

Specify a port number, for example 26002.

4 Click Next.
5 Select SQL Server as the Database Type and click Next.
6 Configure the SQL Server settings.
Specify this information:
Database name
The appropriate database is automatically selected.

Host
The server hosting the SQL Server. The default value is the current host name.

Database user
Specify a user that has CREATE TABLE and CONTROL permissions in the database. If the user
only has a schema-specific CONTROL permission, the name of the schema must be specified in
the Schema field.

Database password
Specify the password of the user.

7 Click Test Connection.

Infor M3 Cloud Configuration Guide | 30

 Installing the M3 Cloud File Transfer client

Verify that the connection is working. If the connection is not working, verify that a valid user and
password are used.
8 Click Close.
9 Click Next.
10 Configure the Service user by selecting Virtual Service account (the default value), and click Next.
11 Review the installation summary information and click Next.
The progress can now be monitored.
12 When the installation process is finished, click Next.
The configuration is now processed.
13 When the configuration process is finished, click Next.
14 Click Done.
15 Click Next.
16 Click Done.

Setting access rights to folders

These folders are created during installation. These default folder names are used in this guide:

Folder name Description

C:\Infor\M3FILES The root folder for M3 file storage of M3 Business
Engine-generated files and reports

C:\Infor\M3PRINTS The default folder for stream files

C:\Infor\FILES The root folder for non-M3 file storage

On your Windows server, perform these steps for each of the folders:
1 Right-click the folder and select Properties.
2 Open the Security tab.
3 Click Edit... to view the permissions.
4 Click Add....
5 Verify that the list in Select this object type contains Groups.
If not, click Object Types..., select the Groups check box and click OK.
6 Click Locations..., select the current server, and click OK.
7 Click Advanced....
8 Click Find Now to view a list of all Users and Groups.
9 Select the group with the name grid installation folder_full. This name is based on the last segment
of the installation location path of the installed grid client.
10 Click OK and OK.

Infor M3 Cloud Configuration Guide | 31

 Installing the M3 Cloud File Transfer client

11 Set the permissions for the group to Allow Full control.

12 Click OK.
13 Click OK.

Installing the M3 Cloud File Transfer client on Grid

1 Start the Grid Admin UI by running C:\Infor\InforIONGrid\bin\AdminUI.cmd as
administrator.
If you receive any warning that the site is not secure, ignore it and go to the page.
2 Click Applications > Install New.
3 In Install Application, click Upload Gar and specify the CFT application location. If you installed
it in the default location, specify the path C:\Infor\CFT\FileTransferClient.gar.
4 Click Upload.
5 Select CloudFileTransferClient and the version you uploaded.
6 Click Next.
7 Use the default value for Name and Profile.
8 Specify the path of the configuration data. If you installed it in the default location, specify C:\
Infor\CFT\FileTransferClient.properties.
9 Select host name of this server.
10 Click Install.
Note: If the installation or automatic upgrade of the CFT application requires troubleshooting:
Download the latest FileTransferClient.gar from the Cloud File Transfer Agent
Administrator page from which the client package was downloaded by clicking Download Client
Application.

Infor M3 Cloud Configuration Guide | 32

 Configuring Infor Localization Services for M3 CE Core

Chapter 9: Configuring Infor Localization Services for

M3 CE Core

M3 CE Core includes support for a selection of the functionality that is enabled by the Infor Localization
Services Platform and the Global Electronic Messaging Services (GEMS).
See these documents for information about configuring and integrating these with your application:
• Infor M3 CE Core Integration Guide for Infor Localization Services GEMS 12.0 for a list of the
messages that are validated by M3 CE Core, and information about how to set up M3 CE Core
and GEMS to work together.
• Infor M3 CE Core Integration Guide for Infor Localization Services Platform for a list of the countries
and reports validated by M3 CE Core, and information about how to set up M3 CE Core and Infor
Localization Services Platform to work together.
• Infor Localization Services Release Notes.
Note: See KB 2111332 for details of the release month - the first and last internal validation performed
- and the external validation, that is, the validation at the bank or authority by the customer.

Configuring Infor Tax Authority Connector

Configuring Infor Spanish Tax Authority Connector

This connector delivers on-premise functionality to support the communication between ERP and Sii.
The web service connector software caters for these categories of registration.
• Register of issued invoices
• Register of purchase invoices
• Register of sales invoices
• Register of invoices for intra-community operations
• Register of asset acquisitions or capital goods
• Register of cash settlements
These items all have a similar process.
There are three types of request per category:

Infor M3 Cloud Configuration Guide | 33

 Configuring Infor Localization Services for M3 CE Core

• Register of invoice
• Cancellation of invoice registration
• Inquiry on the status of invoice registration
If you are running the M3 country version for Spain, you must install Infor Spanish Tax Authority
Connector on premises, for example on the server where the Infor M3 Cloud File Transfer client is
installed.
1 Navigate to Infor Support Portal > Downloads > Products and download Infor Spanish Tax
Authority Connector version 1.1.0.
2 Identify a suitable server and install the Infor Spanish Tax Authority Connector according to the
installation guide.
3 Configure an enterprise location and file connector point. The enterprise location and file connector
point can be reused for the FBMs delivered for M3 Country Version for Spain. See Verifying the
connection points and data flow for M3 and M3 FBM on page 46.

Configuring Infor Italian Tax Authority Connector

This connector delivers on-premise functionality to support the communication between ERP and SDI.
The web service connector software caters for these categories of registration:
• Register of issued invoices, along with feedback from SDI
If you are running the M3 country version for Italy, you must install Infor Italian Tax Authority Connector
on premises, for example on the server where the Infor M3 Cloud File Transfer client is installed.
1 Navigate to Infor Support Portal > Downloads > Products and download Infor Italian Tax Authority
Connector version 1.1.0.
2 Identify a suitable server and install the Infor Italian Tax Authority Connector according to the
installation guide.
3 Configure an enterprise location and file connector point. The enterprise location and file connector
point can be reused for the FBMs delivered for M3 Country Version for Italy. See Verifying the
connection points and data flow for M3 and M3 FBM on page 46.

Infor M3 Cloud Configuration Guide | 34

 Configuring the M3 Implementation Accelerator solution

Chapter 10: Configuring the M3 Implementation

Accelerator solution

Customers and partners access the Implementation Accelerator (IA) documentation from their licensed
app using the Infor Concierge app switcher. Internal Infor users can access through their employee
Infor Ming.le. The first page that is presented is called Navigation Map. The preconfigured IA database
has been installed as part of the provisioning tasks, but there are still additional actions to be carried
out to prepare the solution for the customer.
On the navigation map, click Infor Application Configuration to access personalizations, mashups
and Infor Ming.le homepages, each with their own installation instructions. Click Supporting Materials
to view other supporting content. You can click Activation Instructions to open a .pdf file. This
document is intended to draw attention to some areas of M3 functionality that should be considered
after the technical installation exercises have been completed, but before starting to configure customer
data. The installed database contains a few data elements and sorting sequences that might need to
be activated or at least considered, before attempting to test any new new processes when generating
an initial prototype.

Infor M3 Cloud Configuration Guide | 35

 Configuring Infor Data Lake

Chapter 11: Configuring Infor Data Lake

Your Concept

Verifying the data flow between M3 Event Hub and

Infor Data Lake
1 In ION Desk, select Connect > Data Flows.
2 On the Data Flows page, click the data flow corresponding to
M3_Eventhub-Data_Lake_integration.
3 Refresh the data flow.
4 Click the Event Hub application activity in the data flow.
5 In the application activity properties, verify that the application references the active connection
point.
6 Select the data flow. Click the document icon between the Event Hub application and Data Lake.
7 Ensure that all documents are displayed in the list:
a Click the Add icon.
b If applicable, add all documents and click OK. Otherwise, click Cancel.

Sending the initial data load for custom documents

During normal processing, events carrying data are generated when a user makes a data change or
completes a transaction in M3. The initial load function in M3 generates events without creating
corresponding transactions. The events are received by Event Hub and sent to ION and Infor Data
Lake.
To perform the initial load of M3 data into custom documents that are sent to ION through Infor
Messaging Services:
1 Take note of the name of the master tables to send to Infor Data Lake.
2 In M3, select Administration Tools > M3 Metadata Publisher > M3 API Repository > TEST
API.

Infor M3 Cloud Configuration Guide | 36

 Configuring Infor Data Lake

3 Click the Settings icon.

a In Company (cono), specify the company number that is assigned to your tenant.
b Click OK.
4 Specify this information:
Program
EVS002MI

Transaction
Initiate

Input Data FILE

Specify the master table name, for example MITMAS, to trigger item master documents.

Input Data DIVI

If applicable, specify the division of the events.
Note: The Division parameter works only if the Division field (DIVI) is a field in the primary key of
the table that is specified in FILE.

FRDT, TODT
In From date (FRDT) and To date (TODT), specify the registration date range for the data that is
to be triggered, if applicable.
Note: The initial loading for large tables takes a long time. You should run only one table a time.
You must ensure that there are sufficient resources available in the system at the time of the initial
load.

DLTK
Specify 1.

5 Leave the remaining fields blank, because they are not applicable when sending initial data, and
click Run.
Note: For testing purposes, you can limit the number of lines. In the live initial-load scenario, leave
the field blank to obtain the full amount of data.
After the initial data load, M3 sends updates when users change certain data or when certain
transactions are executed in M3.

Verifying the data flow to Data Lake

To verify whether the initial data is flowing between the products, check ION OneView to see if the
application data arrives in Data Lake. If data is not flowing from Infor M3 CE Core, see the
troubleshooting section.

Infor M3 Cloud Configuration Guide | 37

 Configuring and integrating other applications in the CloudSuite

Chapter 12: Configuring and integrating other

applications in the CloudSuite

Configuring App Builder

Access Infor App Builder in the Infor Mongoose application in Infor Ming.le, or through the Infor App
Builder application in Infor Ming.le.

Configuring Infor Coleman AI Platform

See "Requirements and Prerequisites" in the Infor M3 Cloud Administration Guide for Infor Coleman
AI Platform .
See "Content Deployment and Configuration" in the Infor Coleman AI Platform User Guide for how to
configure Infor Coleman AI Platform.

Configuring Coleman Digital Assistant

See the Infor M3 Cloud Administration Guide for Infor Coleman Digital Assistant and "Administrative
Settings" in the Infor Coleman Digital Assistant User Guide for how to configure Infor Coleman Digital
Assistant.
Note: The AWS features that are required for Infor Coleman Digital Assistant are available in all regions
(except Tokyo and Canada). Customers will be informed in case of changes.

Configuring Configure Price Quote

Access Infor Configure Price Quote in Infor Ming.le.
Configure the integration as described in the Infor M3 CE Core Integration Guide for Infor Configure
Price Quote.

Infor M3 Cloud Configuration Guide | 38

 Configuring and integrating other applications in the CloudSuite

Configuring CRM
Note: This information is only valid for existing Infor CRM customers.
Access Infor CRM in Infor Ming.le.
Configure the integration as described in the Infor M3 CE Core Integration Guide for Infor CRM .

Configuring Document Capture

Access Infor Document Capture (Ephesoft) in Infor Ming.le.
Configure the integration as described in the Infor M3 CE Core Integration Guide for Infor Document
Capture - Supplier Invoices.

Configuring Dynamic Enterprise Performance

Management
Access d/EPM Administration and d/EPM Business Application in Infor Ming.le.
Configure the integration as described in the Infor M3 CE Core Integration Guide for Infor Dynamic
Enterprise Performance Management.

Configuring EAM
Access Infor EAM in Infor Ming.le.
Configure the integration as described in the Infor M3 CE Core Integration Guide for Infor EAM.

Configuring Expense Management

Access Infor Expense Management in Infor Ming.le.
Configure the integration as described in the Infor M3 CE Core Integration Guide for Infor Expense
Management.

Infor M3 Cloud Configuration Guide | 39

 Configuring and integrating other applications in the CloudSuite

Configuring Factory Track

Access Infor Factory Track in Infor Ming.le.
Configure the user access as described in the User Administration topics in the Infor Factory Track
(M3) online help.
Configure the integration as described in the Infor M3 Integration Guide for Infor Factory Track.

Configuring Governance, Risk and Compliance -

Authorization Insight
Configure the integration as described in the Infor M3 CE Core Integration Guide for Infor Governance,
Risk and Compliance - Authorization Insight.

Configuring Governance, Risk and Compliance -

Process Insight
Configure the integration as described in the Infor M3 CE Core Integration Guide for Infor Governance,
Risk and Compliance - Process Insight.

Configuring M3 Customer Lifecycle Management

See the Infor M3 Customer Lifecycle Management Configuration Guide for Infor Operating Service -
Cloud Edition.

Configuring M3 Inventory Planning Workbench

Access Infor M3 Inventory Planning Workbench in Infor M3 > SCP - Supply Planning Workbench >
IPW - Inventory Planning Workbench in Infor Ming.le.
M3 Inventory Planning Workbench at Infor Support Portal

Infor M3 Cloud Configuration Guide | 40

 Configuring and integrating other applications in the CloudSuite

Configuring Mongoose (on-premises and single tenant

cloud)
Access Infor Mongoose in Infor Ming.le.
Download and install the Infor M3 plugin for Infor Mongoose from KB 1983653.
Infor Mongoose Framework documentation at Infor Support Portal.

Configuring Nexus
Infor Nexus is provisioned separately from M3 CE. Access Infor Nexus according to the introduction
email that is provided to the registered user.
Configure the integration as described in the Infor M3 CE Core Integration Guide for Infor Nexus.

Configuring PLM for Fashion

Access Infor PLM for Fashion in Infor Ming.le.
Configure the integration as described in the Infor M3 CE Core Integration Guide for Infor PLM for
Fashion.

Configuring PLM for Process

Access Infor PLM for Process in Infor Ming.le.
Configure the integration as described in theInfor M3 CE Core Integration Guide for Infor PLM for
Process.

Configuring Rhythm for Commerce

Access Infor Rhythm for Commerce in Infor Ming.le.
Configure the integration as described in the Infor M3 CE Core Integration Guide for Infor Rhythm for
Commerce.

Infor M3 Cloud Configuration Guide | 41

 Configuring and integrating other applications in the CloudSuite

Configuring Sales Hub

No configuration is required to get the product running.
See the Infor Sales Hub Reference Guide for conceptual and procedural information for Infor Sales
Hub administrators.

Configuring Supplier Rebate

Access Infor Supplier Portal in Infor Ming.le.
Configure the integration as described in the Infor M3 CE Core Integration Guide for Infor Supplier
Rebate.
See "Post-provisioning steps in Infor Supplier Rebate" in the Infor Supplier Rebate Configuration Guide
for Infor Operating Service Cloud Edition.

Configuring Supply Chain Planning

Access Infor Demand Planning and Infor Supply Planning in the Infor Supply Chain Planning application
in Infor Ming.le.
Configure the integrations as described in the Infor M3 CE Core Integration Guide for Infor Demand
Planning and Infor M3 CE Core Integration Guide for Infor Supply Planning.

Configuring M3 Analytics, Infor Data Lake, and Birst

M3 Analytics retrieves data from Infor Data Lake using Birst Connect 2.0 (BC2). A BC2 agent and the
shared connection to Data Lake is set up during provisioning. Access Birst according to the introduction
e-mail that is provided to each registered user.
See "Configuring Infor Data Lake with M3 CE Core" for instructions on how to send data from the
required M3 tables to Data Lake.

Configuring M3 Equipment Quotation Management

Access M3 Equipment Quotation Management in Infor M3 > Mashup Library > EQM in Infor Ming.le.

Infor M3 Cloud Configuration Guide | 42

 Configuring and integrating other applications in the CloudSuite

Users must have the EQM-User IFS security role to run M3 Equipment Quotation Management.
Administrators must have the EQM-Administrator IFS security role to access Infor M3 > Administration
Tools > EQM Administration.

Configuring M3 Graphical Lot Tracker

See "Defining the settings in M3 Graphical Lot Tracker" in the Infor M3 Graphical Lot Tracker
Administration Guide for Infor M3 Business Engine.

Configuring M3 Inventory Planning Workbench

See "M3 Business Engine settings for Inventory Planning Workbench" in the Infor M3 Inventory Planning
Workbench User Guide.

Configuring Making Tax Digital for VAT

See "UK - Making Tax Digital for Business (MTDfB)" in the M3 CE Core Configuration Guide for Infor
Localization Services Platform.

Connecting to M3 Planning Workbench or M3

Scheduling Workbench
Connect to SWB through VPN and establish a REST API connection to M3 CE Core. The M3 APIRest
URL that are provided in the deployment mail are required to connect to Infor Ming.le. Each user must
enter their own OAuth credentials in SWB or PWB to be able to retrieve data from Infor M3 Business
Engine.
1 Create an OAuth key for the SWB or PWB user. The user who performs this step must be customer
tenant administrator and must either have the have the Infor-SystemAdministrator or
M3BE-FndAdmin IFS security role.
a In Infor M3, select Administration Tools > Business Engine Authentication.
b On the M3 Business Engine Authentication tab, click the OAuth tab.
c Select the SWB or PWB user from the M3 user list.
d Click Create to create new OAuth credentials.

Infor M3 Cloud Configuration Guide | 43

 Configuring and integrating other applications in the CloudSuite

e Copy the Consumer Key and Secret Key.

f Communicate the Consumer Key and Secret Key and APIRest URL to the SWB or PWB
user.
The secret key is only visible at the moment you are creating the credentials. You must secure
a copy by writing down the secret key on a notepad.

2 Configure the REST API connection.

a Start a VPN connection to VPC (OpenVPN or SecureLink).
b Open RDWeb using https://<CustomerPrefix>-ca01.cloud.infor.com/Rdweb
(replace CustomerPrefix with unique value for the deployment), or connect using RDP to
Published APPs Server (INFORBCCA01).
c Open the M3 SWB - Scheduling Workbench or M3 PWB - Planning Workbench application.
d Open Menu > System > Parameters and click the Database tab.
e Specify the M3 APIRest URL that are provided in the deployment mail and select OAuth
authentication. Specify the Consumer Key and the Secret Key. All values are received
from the customer tenant administrator as described.
f Click Test Logon.
The expected result is the 6350I Test logon succeeded system message.
g Click OK.
h Ensure that the M3 Business Engine user and Tenant ID are as expected.
i Click OK to save the specified Consumer Key and the Secret Key in Parameters.
The application can now connect to the Infor M3 Cloud environment.

Infor M3 Cloud Configuration Guide | 44

 Optional post-provisioning steps for M3 CE Core

Chapter 13: Optional post-provisioning steps for M3

CE Core

Enabling M3 Financial Business Messages (M3 FBM)

per country
This section is only applicable if your environment includes M3 Country Versions that use M3 FBMs.
You must import the custom noun data and data flows and verify the content in ION Desk to enable
sending and receiving M3-specific financial business messages per country. The content is installed
per country.
For certain M3 divisions, FBMs for several countries can be used. For example, the FBMs for Austria
can be used for a German division. In this case, the secondary M3 country version must also be
licensed.
Note: An M3 Country Version can contain both M3 Financial Business Messages and Infor Localization
Services GEMS messages.
See the M3 Country Version for [country] for the full set of supported financial business messages for
the country.
See KB 2111332 for details of the release month - the first and last internal validation performed - and
the external validation, that is, the validation at the bank or authority by the customer.

Downloading the data flows for M3 FBMs

To download the data flow:
Note: To perform this task, you must have the M3BE-FndAdmin IFS security role.
1 In Infor M3, select Administration Tools > Cloud File Transfer Agent Administration.
2 Click Download Contents.
3 Select the applicable M3FBM_ION_Integration_to_Country_<Country> check boxes where
<Country> is represented by a two-letter abbreviation such as AT, DE, or FR, and click Download.
4 Extract M3FBM_<Country>_CustomNounData.zip and M3FBM_<Country>_DocumentFlows.
zip from M3FBM_ION_Integration_to_Country_<Country>.zip.

Infor M3 Cloud Configuration Guide | 45

 Optional post-provisioning steps for M3 CE Core

5 Extract the M3FBM_<Country>_<Direction>.xml data flow where the direction is either Inbound
or Outbound from M3FBM_<Country>_DocumentFlows.zip. Examples: M3FBM_AT_Outbound
or M3FBM_FR_Inbound.

Importing the custom noun data for M3 Financial Business

Messages
1 In ION Desk, select Data Catalog > Object Schemas.
2 Click Import.
3 Browse and select M3FBM_<Country>_CustomNounData.zip.
4 Click OK. The custom noun data is imported from the file.

Importing the data flows for M3 Financial Business Messages

1 In ION Desk, select Connect > Data Flows.
2 Click Import.
3 Browse and select M3FBM_<Country>_<Direction>.xml.
4 Click OK. The connections, data flows, and file templates are imported from the file.
This import is expected to contain duplicate items for the connection points, because the M3
connection point was created during provisioning.
5 Select Merge additional documents.
6 This import may also contain duplicate items for the data flow, because the file templates are
already imported previously. Select Skip already existing.
7 Click OK.
8 Repeat steps 2 to 7 for additional data flows as applicable.
The M3 FBM file connection point is referenced as M3FBM_FILE_CONN_POINT in the data flow. Check
the list of existing connection points if a file connection point already exists for M3 FBM with a different
name. If applicable, replace the reference to an imported file connection point with a reference to an
existing file connection point for M3 FBM.

Verifying the connection points and data flow for M3 and M3

FBM
If the connection point for M3 is not named m3 or if the connection point for M3 FBM is not named
M3FBM_FILE_CONN_POINT, you must update the existing connection points with the applicable
documents and reference the existing connection points from the data flow.
1 In ION Desk, select Connect > Connection Points.

Infor M3 Cloud Configuration Guide | 46

 Optional post-provisioning steps for M3 CE Core

a On the Connection Points page, select the M3 FBM connection point

(M3FBM_FILE_CONN_POINT) and verify that the Documents tab includes all the inbound
and outbound documents that are required for this integration:
b Select the desired document and set up the appropriate scenario (Write a file to a
folder or Read a file from a folder) as instructed in the table below.

Document Write a file to a Read a file from a

folder folder
Sync.M3FBM_AR_Out_VATReport_DigitalVATBook selected
Sync.M3FBM_AT_Out_CustomerOrderInvoice_ebIn- selected
terface
Sync.M3FBM_AT_Out_VATReport_UVA_U30 selected
Sync.M3FBM_BE_Out_AnnualVAT-Report_LK7 selected
Sync.M3FBM_BG_Out_Electronic_VAT_Purchase- selected
Books_POKUPKI
Sync.M3FBM_BG_Out_Electronic_VAT_Sales- selected
Books_PRODAGBI
Load.M3FBM_BR_In_BankConfirmation_BDB selected
Load.M3FBM_BR_In_BankConfirmation_BRADE- selected
SCO
Load.M3FBM_BR_In_BankConfirmation_HSBC selected
Load.M3FBM_BR_In_BankConfirmation_ITAU selected
Load.M3FBM_BR_In_BankConfirmation_Santander selected
Load.M3FBM_BR_In_COInvoice_NFe2_CancelRe- selected
turn
Load.M3FBM_BR_In_COInvoice_NFe2_IssueReturn selected
Load.M3FBM_BR_In_COInvoice_NFe4_Approved_Is- selected
sueReturn
Load.M3FBM_BR_In_COInvoice_NFe4_Unap- selected
proved_IssueReturn
Load.M3FBM_BR_In_COInvoice_Synchro31_Can- selected
celReturn
Load.M3FBM_BR_In_COInvoice_Synchro31_Is- selected
sueReturn
Load.M3FBM_BR_In_ItemComplementFCI selected
Sync.M3FBM_BR_Out_BankRemittance_BDB selected
Sync.M3FBM_BR_Out_BankRemittance_BRADE- selected
SCO

Infor M3 Cloud Configuration Guide | 47

 Optional post-provisioning steps for M3 CE Core

Document Write a file to a Read a file from a

folder folder
Sync.M3FBM_BR_Out_BankRemittance_HSBC selected
Sync.M3FBM_BR_Out_BankRemittance_ITAU selected
Sync.M3FBM_BR_Out_BankRemittance_Santander selected
Sync.M3FBM_BR_Out_COInvoice_NFe2_CancelRe- selected
quest
Sync.M3FBM_BR_Out_COInvoice_NFeXML4_Can- selected
celRequest
Sync.M3FBM_BR_Out_COInvoice_NFe4_Master- selected
saf_IssueRequest
Sync.M3FBM_BR_Out_COInvoice_NFe4_2019_Mas- selected
tersaf_IssueRequest
Sync.M3FBM_BR_Out_COInvoice_NFe4_Stan- selected
dard_IssueRequest
Sync.M3FBM_BR_Out_COInvoice_NFe4_2019_Stan- selected
dard_IssueRequest
Sync.M3FBM_BR_Out_COInvoice_Synchro31_Can- selected
celRequest
Sync.M3FBM_BR_Out_COInvoice_Synchro4_Is- selected
sueRequest
Sync.M3FBM_BR_Out_SupplierPayment_BDB selected
Sync.M3FBM_BR_Out_SupplierPayment_HSBC selected
Sync.M3FBM_CH_Out_SupplierPay- selected
ment_SEPA_113_CH02_CreditSuisse
Sync.M3FBM_CL_Out_VATReport_RegistrodeCom- selected
pras
Load.M3FBM_CN_In_GoldenTaxInvoice_IssuedIn- selected
voiceList
Sync.M3FBM_CN_Out_GoldenTaxInvoice_Rejecte- selected
dInvoiceList
Sync.M3FBM_CN_Out_GoldenTaxInvoice_SalesIn- selected
voiceList
Sync.M3FBM_CZ_Out_VAT_Report_Control_State- selected
ment_XML_2019
Sync.M3FBM_CZ_Out_VAT_Return_State- selected
ment_DPHDP3

Infor M3 Cloud Configuration Guide | 48

 Optional post-provisioning steps for M3 CE Core

Document Write a file to a Read a file from a

folder folder
Sync.M3FBM_DE_Out_VATReport_Elster_UStVA selected
Sync.M3FBM_DE_Out_VATReport_UVA18 selected
Load.M3FBM_ES_In_OnlineVATReport_SII_Respues- selected
taEmitidas_2018
Load.M3FBM_ES_In_OnlineVATReport_SII_Re- selected
spuestaRecibidas_2018
Sync.M3FBM_ES_Out_CustomerOrderInvoice_Fac- selected
turae_321
Sync.M3FBM_ES_Out_OnlineVATReport_SII_Fac- selected
turasEmitidas_2018
Sync.M3FBM_ES_Out_OnlineVATReport_SII_Fac- selected
turasRecibidas_2018
Sync.M3FBM_ES_Out_VATReport_Format340 selected
Sync.M3FBM_ES_Out_VATReport_Format347_2015 selected
Load.M3FBM_FR_In_ExternalAccountState- selected
ment_ETEBAC
Sync.M3FBM_HU_Out_AnnualVATReport_1965 selected
Sync.M3FBM_HU_Out_AnnualVATReport_2065 selected
Sync.M3FBM_IT_Out_VATReport_Esterometro_2019 selected
Sync.M3FBM_IT_Out_VATReport_Spesometro_2017 selected
Sync.M3FBM_LT_Out_ConsignmentNote_iVAZ_133 selected
Sync.M3FBM_LT_Out_VATReport_iSAF_11 selected
Sync.M3FBM_SI_Out_VATReport_DDV_O selected
Sync.M3FBM_SK_Out_InvoiceList_VATRe- selected
port_KVDPH_2017
Sync.M3FBM_SK_Out_VATReport_DPH2018 selected

c On the Connection Points page, select the M3 connection point and verify that the Documents
tab includes all the inbound and outbound documents that are required for this integration:

Document Receive in Applica- Send from Applica-

tion tion
Sync.M3FBM_AR_Out_VATReport_DigitalVATBook selected
Sync.M3FBM_AT_Out_CustomerOrderInvoice_ebIn- selected
terface

Infor M3 Cloud Configuration Guide | 49

 Optional post-provisioning steps for M3 CE Core

Document Receive in Applica- Send from Applica-

tion tion
Sync.M3FBM_AT_Out_VATReport_UVA_U30 selected
Sync.M3FBM_BE_Out_AnnualVAT-Report_LK7 selected
Sync.M3FBM_BG_Out_Electronic_VAT_Purchase- selected
Books_POKUPKI
Sync.M3FBM_BG_Out_Electronic_VAT_Sales- selected
Books_PRODAGBI
Load.M3FBM_BR_In_BankConfirmation_BDB selected
Load.M3FBM_BR_In_BankConfirmation_BRADE- selected
SCO
Load.M3FBM_BR_In_BankConfirmation_HSBC selected
Load.M3FBM_BR_In_BankConfirmation_ITAU selected
Load.M3FBM_BR_In_BankConfirmation_Santander selected
Load.M3FBM_BR_In_COInvoice_NFe2_CancelRe- selected
turn
Load.M3FBM_BR_In_COInvoice_NFe2_IssueReturn selected
Load.M3FBM_BR_In_COInvoice_NFe4_Approved_Is- selected
sueReturn
Load.M3FBM_BR_In_COInvoice_NFe4_Unap- selected
proved_IssueReturn
Load.M3FBM_BR_In_COInvoice_Synchro31_Can- selected
celReturn
Load.M3FBM_BR_In_COInvoice_Synchro31_Is- selected
sueReturn
Load.M3FBM_BR_In_ItemComplementFCI selected
Sync.M3FBM_BR_Out_BankRemittance_BDB selected
Sync.M3FBM_BR_Out_BankRemittance_BRADE- selected
SCO
Sync.M3FBM_BR_Out_BankRemittance_HSBC selected
Sync.M3FBM_BR_Out_BankRemittance_ITAU selected
Sync.M3FBM_BR_Out_BankRemittance_Santander selected
Sync.M3FBM_BR_Out_COInvoice_NFe2_CancelRe- selected
quest
Sync.M3FBM_BR_Out_COInvoice_NFeXML4_Can- selected
celRequest

Infor M3 Cloud Configuration Guide | 50

 Optional post-provisioning steps for M3 CE Core

Document Receive in Applica- Send from Applica-

tion tion
Sync.M3FBM_BR_Out_COInvoice_NFe4_Master- selected
saf_IssueRequest
Sync.M3FBM_BR_Out_COInvoice_NFe4_2019_Mas- selected
tersaf_IssueRequest
Sync.M3FBM_BR_Out_COInvoice_NFe4_Stan- selected
dard_IssueRequest
Sync.M3FBM_BR_Out_COInvoice_NFe4_2019_Stan- selected
dard_IssueRequest
Sync.M3FBM_BR_Out_COInvoice_Synchro31_Can- selected
celRequest
Sync.M3FBM_BR_Out_COInvoice_Synchro4_Is- selected
sueRequest
Sync.M3FBM_BR_Out_SupplierPayment_BDB selected
Sync.M3FBM_BR_Out_SupplierPayment_HSBC selected
Sync.M3FBM_CH_Out_SupplierPay- selected
ment_SEPA_113_CH02_CreditSuisse
Load.M3FBM_CN_In_GoldenTaxInvoice_IssuedIn- selected
voiceList
Sync.M3FBM_CL_Out_VATReport_RegistrodeCom- selected
pras
Sync.M3FBM_CN_Out_GoldenTaxInvoice_Rejecte- selected
dInvoiceList
Sync.M3FBM_CN_Out_GoldenTaxInvoice_SalesIn- selected
voiceList
Sync.M3FBM_CZ_Out_VAT_Report_Control_State- selected
ment_XML_2019
Sync.M3FBM_CZ_Out_VAT_Return_State- selected
ment_DPHDP3
Sync.M3FBM_DE_Out_VATReport_Elster_UStVA selected
Sync.M3FBM_DE_Out_VATReport_UVA18 selected
Load.M3FBM_ES_In_OnlineVATReport_SII_Respues- selected
taEmitidas_2018
Load.M3FBM_ES_In_OnlineVATReport_SII_Re- selected
spuestaRecibidas_2018
Sync.M3FBM_ES_Out_CustomerOrderInvoice_Fac- selected
turae_321

Infor M3 Cloud Configuration Guide | 51

 Optional post-provisioning steps for M3 CE Core

Document Receive in Applica- Send from Applica-

tion tion
Sync.M3FBM_ES_Out_OnlineVATReport_SII_Fac- selected
turasEmitidas_2018
Sync.M3FBM_ES_Out_OnlineVATReport_SII_Fac- selected
turasRecibidas_2018
Sync.M3FBM_ES_Out_VATReport_Format340 selected
Sync.M3FBM_ES_Out_VATReport_Format347_2015 selected
Load.M3FBM_FR_In_ExternalAccountState- selected
ment_ETEBAC
Sync.M3FBM_HU_Out_AnnualVATReport_1965 selected
Sync.M3FBM_HU_Out_AnnualVATReport_2065 selected
Sync.M3FBM_IT_Out_VATReport_Esterometro_2019 selected
Sync.M3FBM_IT_Out_VATReport_Spesometro_2017 selected
Sync.M3FBM_LT_Out_ConsignmentNote_iVAZ_133 selected
Sync.M3FBM_LT_Out_VATReport_iSAF_11 selected
Sync.M3FBM_SI_Out_VATReport_DDV_O selected
Sync.M3FBM_SK_Out_InvoiceList_VATRe- selected
port_KVDPH_2017
Sync.M3FBM_SK_Out_VATReport_DPH2018 selected

Your connection point also includes documents for other integrations.

2 In ION Desk, select Connect > Data Flows.

3 On the Data Flows page, select the data flow and use the configured connection points. If the file
connection point for M3 FBM named M3FBM_FILE_CONN_POINT is to be used, you must update
the file connection point to use the correct enterprise location and connection details.
a In ION Desk, select Connect > Connection Points and select M3FBM_FILE_CONN_POINT.
b On the Documents tab, update the Write Location, Read Location, Archive Location and Error
Location. Update the tenant with the actual tenant value.
For inbound FBM messages, update the accounting entity with the actual accounting entity
value. The placement of the accounting entity in relation to the folder structure in the read
location should be reflected in the FilePathAELevel control property of the agreement. This
can be updated in Enterprise Collaborator Administration > Server > Agreement Control
Properties.
For outbound FBM messages, [accounting_entity] will depend on the value of the accounting
entity sent in the manifest info for the FBM mapping. Therefore, it is not necessary to update
[accounting_entity] for outbound FBM messages.
c Click Save.
d Click Activate/Reactivate.

Infor M3 Cloud Configuration Guide | 52

 Optional post-provisioning steps for M3 CE Core

If a file connection point is to be used but does not exist, create a file connection point. Follow the
instructions in the Infor ION Technology Connectors Administration Guide–Cloud Edition.
Furthermore, if an enterprise location is not available for use in the file connection point, create an
enterprise location. Follow the instructions in the "Enterprise Connector application connection
points" section of the Infor ION Desk User Guide - Cloud Edition.

Infor M3 Cloud Configuration Guide | 53

 Troubleshooting

Appendix A: Troubleshooting

This section describes actions that you can perform to solve integration issues with Infor OS.

Data is not flowing properly

Cause: A problem is preventing the flow of BOD data to ION.
Solution: After you complete the configuration setup, if BOD data is not flowing to ION, use OneView
in ION Desk to identify the problem.
You can perform these actions in ION OneView:
• Track business documents from a single consolidated view: search for documents using different
search criteria.
• View all ION components that were triggered by the incoming document: connection points; data
flow filters and content-based routing; mappings; ION engines for example, Monitor, Workflow,
and Pulse; monitors; activation policies and workflows.
• View more details about ION components:
• Properties for each ION component.
• List of events that were logged by each ION component while processing the message.
• Drilldown views that are used to display the appropriate management pages for the selected
ION component.
• Visibility of the different messages sent or generated: Original BOD messages that triggered
the whole list of components displayed; Confirm BOD messages that were generated due to
any error while processing the Original BOD message; Mapped/Updated BOD messages that
were created during the processing of the Original BOD message.
• Content of BOD messages. This information is only available to authorized users, based on
the roles and permissions that are configured
For more information, see the section on ION OneView in the Desk User Guide – Cloud Edition.
To avoid business discrepancies between this application and integrated applications, correct any
errors as soon possible.

Infor M3 Cloud Configuration Guide | 54

 Troubleshooting

Issue: no BODs reaching target system

Complete these steps to verify the configuration.
1 In Administration Tools > BOD Processor Administration verify that the applicable M3 company
and divisions are selected for BOD publishing.
2 Ensure that the system is installed correctly:
a Verify that all components are running.
3 Check Administration Tools > Event Hub Administration for those subscribers and publishers
that are required for outbound BODs. You can also select Event Hub Visualization to display a
graphical representation of the current publisher and subscriber topology.
a Click Administration Tools > Event Hub Administration > Subscriber > EventAnalytics.
• Verify that M3 is listed as a publisher.
• Verify that EventAnalytics is listed as a publisher.
If EventAnalytics is missing from the list of publishers for the EventAnalytics subscriber, go to
Administration Tools > Event Analytics Administration and start the
M3BEBODs_GenericCorrelation rules session.
b Click Administration Tools > Event Hub Administration > Subscriber > M3BODProcessor
and verify that EventAnalytics is listed as a publisher.
c Click the subscribers value in Publishers > M3BODProcessor > Subscribers. Verify that
these eleven receive channels for Infor Enterprise Collaborator are listed as subscribers to
M3BODProcessor:
MEC-M3_In_M3BOD_BlncDtaFinance_Ordered
MEC-M3_In_M3BOD_MstDtaGeneral_Ordered
MEC-M3_In_M3BOD_MstDtaSales_Ordered
MEC-M3_In_M3BOD_MstDtaService_Ordered
MEC-M3_In_M3BOD_MstDtaSupplyChain_Ordered
MEC-M3_In_M3BOD_NonOrdered
MEC-M3_In_M3BOD_TrnsDtaFinance_Ordered
MEC-M3_In_M3BOD_TrnsDtaSales_Ordered
MEC-M3_In_M3BOD_TrnsDtaService_Ordered
MEC-M3_In_M3BOD_TrnsDtaSupplyChain_Ordered
d If these channels are missing from the subscriber list, open Administration Tools > Enterprise
Collaborator Administration. Go to Communication > Receive and ensure that the channels
are enabled.
e If the channels are missing, reinstall M3BODs_[ver]_IEC_data.agr.
f If the channels are visible and selected in Communication > Receive , but there are no
subscriptions, open Administration Tools > Enterprise Collaborator Administration. Go
to Communication > Channel Control and click Reload All Channels to refresh the Event
Hub subscriptions.
4 In Administration Tools > Event Hub Administration check if any of the subscribers and
publishers in the previous step have an excessive amount of queued events.

Infor M3 Cloud Configuration Guide | 55

 Troubleshooting

If there is an unusually large amount of queued events, the subscriber of these events cannot keep
up with the current workload that may result from a BOD publishing peak. If the queue does not
decrease over time, this may be due to the size of the component's hardware or a system error.
5 Note: For information about ION administration see Infor Operating Service documentation.
Open ION Desk.
a Review the settings of the application connection points. Click Test to verify the connectivity
of the application connection point.
b Verify that the correct accounting entity is used by the sending system. This applies to inbound
BODs.
c If the BOD is visible in OneView, but cannot be routed:
• If the M3 application is represented by a question mark instead of a reference to a valid
connection point, verify that the logical ID that has been specified for the connection point
corresponds to the ionFromLogicalId group control property as displayed in Administration
Tools > Enterprise Collaborator Administration > Groups > Control Properties.

Issue: no BODs reaching the target system during initial load

In addition to the actions for troubleshooting the issue of no BODs reaching the target system, use this
procedure to verify that the ionToLogicalId group control property is configured for the agreement group.
1 Open Administration Tools > Enterprise Collaborator Administration > Groups > Control
Properties.
2 Verify that the ionToLogicalId group control property is set on the initial load agreement group.

Issue: one or several BODs not reaching the target system

Use this procedure to investigate why specific BODs do not reach the target system.
1 In ION Desk:
a Search for the BOD in OneView. If it exists, click the document icon to view the routing. Check
if the BOD was routed to the target connection point:
• If the BOD is routed to the target point, the problem is in the receiving system.
• If the BOD is not routed, check if the integration's data flow is configured correctly.
b If the BOD uses a custom noun, that is, an xsd not listed on schema.infor.com, verify that the
custom noun is uploaded to the ION registry by opening Settings > Registry > Custom
Documents.
c Verify the settings of the application connection point. Ensure that the connection point is
configured to publish or consume the required BOD documents.
2 In the Infor M3 Administration Tools:
a Verify that the EC_Server, EventAnalytics, EventHub, M3BE and M3BODProcessor applications
are running and that their status is OK. Assess any errors or warnings.

Infor M3 Cloud Configuration Guide | 56

 Troubleshooting

b Verify that all the M3BE subsystems are running and that their status is OK. If applicable, assess
the logs for relevant errors and warnings.
3 In Administration Tools > Event Analytics Administration :
a Verify that the rules session for the BOD is started.
b Verify that the M3BEBODs_GenericCorrelation rules session is started.
4 In Administration Tools > Event Hub Administration, verify these subscribers and publishers,
required for outbound BODs. You can also click Event Hub Visualization to display a graphical
representation of the current publisher and subscriber topology.
a Click Event Hub > >Subscriber > EventAnalytics.
• Verify that M3 is listed as a publisher.
• Verify that EventAnalytics is listed as a publisher.
If EventAnalytics is missing from the list of publishers for the EventAnalytics subscriber, go to
the Grid management page for Eventanalytics and start the M3BEBODs_GenericCorrelation
rules session.
b Click Event Hub > Subscriber > M3BODProcessor, and verify that EventAnalytics is listed
as a publisher.
c Click the subscribers value in Publishers > M3BODProcessor > Subscribers. Verify that
these eleven receive channels for Infor Enterprise Collaborator are listed as subscribers to
M3BODProcessor:
MEC-M3_In_M3BOD_BlncDtaFinance_Ordered
MEC-M3_In_M3BOD_MstDtaGeneral_Ordered
MEC-M3_In_M3BOD_MstDtaSales_Ordered
MEC-M3_In_M3BOD_MstDtaService_Ordered
MEC-M3_In_M3BOD_MstDtaSupplyChain_Ordered
MEC-M3_In_M3BOD_NonOrdered
MEC-M3_In_M3BOD_TrnsDtaFinance_Ordered
MEC-M3_In_M3BOD_TrnsDtaSales_Ordered
MEC-M3_In_M3BOD_TrnsDtaService_Ordered
MEC-M3_In_M3BOD_TrnsDtaSupplyChain_Ordered
d If these channels are missing from the subscriber list, open Go to Manage > Communication
> Receive and verify that the channels are enabled.
e If the channels are missing in the Infor Enterprise Collaborator Partner Administration tool,
reinstall M3BODs_[ver]_IEC_data.agr.
f If the channels are visible and selected in the Infor Enterprise CollaboratorPartner Administration
tool, but there are no subscriptions, open to the management pages for EC_Server. Go to
Communication > Channel Control and click Reload All Channels to refresh the Event Hub
subscriptions.
5 In the Grid management pages for EventHub, check if any of the subscribers and publishers in the
previous step have an excessive amount of queued events.
If there is an unusually large amount of queued events, the subscriber of these events cannot keep
up with the current workload, which may result from a BOD publishing peak. If the queue does not
decrease over time, this may be due to the size of the component's hardware or a system error.

Infor M3 Cloud Configuration Guide | 57

 Troubleshooting

6 In Administration Tools > Event Hub Administration:

a Go to Server > Mappings and ensure that the BOD mapping exists and is in the Active
state.
b Go to Messages > Status and check if the agreement for the BOD is in force:
• If the agreement is in force, but the state indicates an error, click Show and download the
log for further analysis.
• If the state is Finished, open ION Desk and search for the BOD in OneView.
c Go to Communication > Pools, and check whether the value for Length for one of the two
queues is unexpectedly large.
If so, go to Messages and check for messages that are currently in the XML Transform or
Pending status. Investigate whether the messages are processed slowly or not at all. Examine
the messages that stay active in more detail.
An increasing queue length can be caused by incorrect configuration or a lack of processing
resources.

Issue: Divisions for a company are not displayed in the

BODProcessor list
Issue: Divisions for a company are not displayed in the BODProcessor list.
Solution: Update the access to companies and divisions for the user BODSVC.
1 In Infor M3, open 'User. Open' (MNS150).
2 Select the BODSVC user.
3 Check if the user has access to all companies and divisions that are listed in 'User. Access per
Company Division' (MNS151).
4 In (MNS150), right-click the BODSVC user and select Related > Update User Access all Cmp/Div.
Allow some time for the update to take effect.
5 In Administration Tools > BOD Processor Administration, click Reload.
When the reload is complete, the companies are updated with divisions.

Infor M3 Cloud Configuration Guide | 58