infor m3 configuration guide for infor operating service · the latest documentation is available...

Infor M3 Configuration Guide for InforOperating Service

M3 Business Engine BODs 15.5.0.0, M3 ContentPack for Infor OS and M3 Integrations 4.0, ION12.x

Release 15.5.0.0

Copyright © 2020 Infor

Important Notices

The material contained in this publication (including any supplementary information) constitutes andcontains confidential and proprietary information of Infor.

By gaining access to the attached, you acknowledge and agree that the material (including anymodification, translation or adaptation of the material) and all copyright, trade secrets and all otherright, title and interest therein, are the sole property of Infor and that you shall not gain right, title orinterest in the material (including any modification, translation or adaptation of the material) by virtueof your review thereof other than the non-exclusive right to use the material solely in connection withand the furtherance of your license and use of software made available to your company from Inforpursuant to a separate agreement, the terms of which separate agreement shall govern your use ofthis material and all supplemental related materials ("Purpose").

In addition, by accessing the enclosed material, you acknowledge and agree that you are required tomaintain such material in strict confidence and that your use of such material is limited to the Purposedescribed above. Although Infor has taken due care to ensure that the material included in this publicationis accurate and complete, Infor cannot warrant that the information contained in this publication iscomplete, does not contain typographical or other errors, or will meet your specific requirements. Assuch, Infor does not assume and hereby disclaims all liability, consequential or otherwise, for any lossor 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 youruse of this material and you will neither export or re-export, directly or indirectly, this material nor anyrelated materials or supplemental information in violation of such laws, or use such materials for anypurpose prohibited by such laws.

Trademark Acknowledgements

The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/orrelated affiliates and subsidiaries. All rights reserved. All other company, product, trade or servicenames referenced may be registered trademarks or trademarks of their respective owners.

Publication Information

Release: Infor M3 Business Engine BODs 15.5.0.0Publication Date: June 15, 2020Document code: m3bebod_15.5.0.0_m3bebodcg__en-us

Contents

About this guide.................................................................................................................................8

Related documents...........................................................................................................................8

Contacting Infor.................................................................................................................................9

Chapter 1: Requirements.................................................................................................................10

Required products...........................................................................................................................10

Application Compatibility.................................................................................................................10

Required information.......................................................................................................................11

Chapter 2: Configuration checklist.................................................................................................12

Chapter 3: Configuration overview.................................................................................................14

Infor OS...........................................................................................................................................14

Infor Ming.le.................................................................................................................................14

Infor ION......................................................................................................................................15

Infor ION Grid...............................................................................................................................16

Infor Document Management.......................................................................................................17

Infor Business Vault.....................................................................................................................17

Analytics.......................................................................................................................................17

Infor BI.........................................................................................................................................18

Concepts and definitions specific to this configuration....................................................................18

Tenant ID......................................................................................................................................18

Accounting entity..........................................................................................................................18

Location.......................................................................................................................................18

Logical ID.....................................................................................................................................19

Partner.........................................................................................................................................19

M3 Business Engine BODs..........................................................................................................19

M3 Workflow Executor.................................................................................................................20

M3 BOD architectural overview and data flow.............................................................................20

Infor M3 Configuration Guide for Infor Operating Service | 3

Contents

Chapter 4: Configuring security......................................................................................................22

Setting up M3 to use single sign-on................................................................................................22

Single sign-out.................................................................................................................................22

Chapter 5: Adding M3 applications in Infor Ming.le......................................................................23

Adding the application.....................................................................................................................23

Chapter 6: Configuring access to M3 through Infor Ming.le........................................................25

Users and roles...............................................................................................................................25

Chapter 7: Configuring M3...............................................................................................................26

Configuring BOD-specific settings...................................................................................................26

Configuring settings for catalog BODs.........................................................................................26

Configuring settings for customer master data BODs..................................................................26

Configuring settings for ProcessContactMaster...........................................................................27

Configuring settings for ProcessPurchaseOrder..........................................................................27

Configuring settings for ProcessQuote........................................................................................28

Configuring settings for ProcessRequisition................................................................................28

Configuring settings for Sync and Show SalesOrder...................................................................29

Configuring settings for Sync and Show InvoiceCustomerOrder.................................................29

Configuring settings for incoming supplier invoice BODs............................................................30

Configuring settings for incoming warehouse management BODs..............................................30

Configuring settings for LoadAdvanceShipNotice, ProcessAdvanceShipNotice, and

SyncAdvanceShipNotice..............................................................................................................31

Configuring settings for ProcessItemMaster................................................................................32

Configuring settings for inbound SyncBillOfMaterials..................................................................34

Configuring settings for ProcessWorkflow...................................................................................35

Configuring M3 application message settings.............................................................................35

Setting master data to standardized values....................................................................................37

Setting up logical IDs, tenants, accounting entities, and locations in M3.....................................37

Specifying or editing translation data..............................................................................................37

Setting up logical IDs, tenants, accounting entities, and locations in M3........................................39

Setting up the system to send initial data........................................................................................39

Chapter 8: Configuring M3 to send and receive BODs in ION.....................................................40

Installing and configuring M3 Business Engine BOD content.........................................................40

Preparing for the installation of the M3 Business Engine BOD content.......................................40

Downloading M3 Business Engine BOD content.........................................................................41


Contents

Installing M3 Business Engine BOD content...............................................................................41

Using correlation rules with BOD rules........................................................................................44

Upgrading M3 Business Engine BODs........................................................................................45

Upgrading components within an existing version.......................................................................47

Connecting M3 to Infor ION.............................................................................................................48

Understanding connection points and document flows................................................................48

Configuring a document flow between applications.....................................................................51

Publishing BODs.............................................................................................................................52

Starting applications and services...............................................................................................53

Sending the initial data load.........................................................................................................53

Verifying the ION configuration........................................................................................................55

Verifying that BODs are generated..............................................................................................55

Verifying that ION receives data...................................................................................................55

Verifying the data flow between applications...............................................................................55

Chapter 9: Configuring workflows and ION messages for M3.....................................................56

ION messages.................................................................................................................................56

Customizing M3 monitors and workflows........................................................................................57

Configuring M3 to process alerts....................................................................................................58

Example: Creating a customer invoice overdue alert...................................................................59

Configuring M3 to process workflows for tasks and notifications....................................................60

Example: Budget created.............................................................................................................61

Workflow sample content for M3.....................................................................................................62

Setup and configuration...............................................................................................................63

Distributing alerts and tasks.........................................................................................................63

Updating M3 content for ION.......................................................................................................63

Configuring the M3 workflow exit point............................................................................................64

Configuring workflow exit point properties in ION Desk...............................................................64

Chapter 10: Configuring ION APIs for M3.......................................................................................67

Creating an API suite for M3...........................................................................................................67

Chapter 11: Configuring drillbacks to M3.......................................................................................69

About drillbacks...............................................................................................................................69

Importing and configuring application drillbacks.............................................................................70

Available drillbacks.......................................................................................................................70

Translating the accounting entity..................................................................................................70


Contents

Verifying a drillback.........................................................................................................................71

Chapter 12: Configuring context apps and utility apps that are used with M3...........................72

Understanding business context messages....................................................................................72

Supported business context messages.......................................................................................72

Context and utility applications that work with M3...........................................................................73

Enabling a context or utility app for your application....................................................................73

Chapter 13: Configuring homepages for M3..................................................................................74

Importing predefined homepages...................................................................................................74

Verifying the homepage and widget content...................................................................................74

Chapter 14: Configuring Infor Document Management with M3..................................................76

Importing configurations and types.................................................................................................76

Enabling the Related Information context app.................................................................................77

Chapter 15: Configuring BI and Analytics content for M3............................................................78

Chapter 16: Configuring Infor Localization Services for use with M3.........................................79

Appendix A: Troubleshooting..........................................................................................................80

Data is not flowing properly.............................................................................................................80

No BODs reach the target system...................................................................................................81

No BODs reach the target system during the initial load.................................................................82

Some BODs do not reach the target system...................................................................................83

Appendix B: Infor ION BOD overview.............................................................................................85

BOD message structure..................................................................................................................85

System of record.............................................................................................................................86

BOD verbs.......................................................................................................................................87

Message delivery............................................................................................................................87

Data mapping..................................................................................................................................88

Classification of BODs.....................................................................................................................88

Appendix C: Ongoing maintenance................................................................................................90

Appendix D: M3 BOD overview.......................................................................................................91

Company and division in Infor Enterprise Collaborator...................................................................91

M3 API reference settings............................................................................................................91

M3 BOD agreements.......................................................................................................................91

Structure......................................................................................................................................92


Contents

Naming standard..........................................................................................................................92

Detection......................................................................................................................................92

System of Record............................................................................................................................93

M3 as System of Record..............................................................................................................93

Another external application as system of record........................................................................94

Integrations with multiple System of Records..............................................................................94

Disabling M3 BOD integration.........................................................................................................94

Appendix E: Business events that generate outbound BODs.....................................................96

Appendix F: Inbound BOD usage.................................................................................................105

Appendix G: BODs used in integrations with M3........................................................................107

Outbound BODs from M3 to integrated applications.....................................................................107

Inbound BODs to M3 from integrated applications........................................................................111

Appendix H: Master tables for initial load....................................................................................113


Contents

About this guide

This guide provides information for the configuration and implementation of Infor M3 with Infor OS.

Use this guide when M3 and Infor OS are both installed on-premises, or where some products areon-premises and some products are in the cloud.

This guide replaces Infor M3 Configuration Guide for Infor ION - M3 Business Engine BODs 15.5.0.0,ION 12.x and Infor M3 Configuration Guide for Infor Xi Platform.

Intended audience

This guide is intended for the system administrator or consultant who configures M3 for use with InforOS.

Related documentsThis table shows the types of documents that are related to ION integrations and their purpose:

PurposeDocument type

For each BOD that is supported by Infor M3in this integration, this document provides thesource and definition of the data in each BODelement that is sent from Infor M3 throughION. This document also provides detailsabout the published data.

Infor M3 Outbound BOD Mapping and Descriptions

For each BOD that Infor M3 supports, thisdocument provides the details about how eachinbound BOD receives information or requestsinformation. For example, the source mightbe an extension product, a result of a work-flow, or a drill-back function from Infor Ming.le.If a BOD updates the Infor product source ta-ble, the exceptions and handling are de-scribed.

Infor M3 Inbound BOD Mapping and Descriptions


About this guide

PurposeDocument type

This document provides end-to-end integratedBOD mapping details for BODs that are ex-changed between two Infor products or be-tween an Infor product and an Infor partnerproduct. It describes the exceptions and han-dling requirements by element.

Infor M3 Cross BOD Mapping and Descriptions

This guide describes the administration tasksto set up and maintain Infor OS.

Infor OS Administration Guide

This document provides information on howto use Infor ION Desk.

Infor ION Desk User Guide

This document covers the necessary steps toinstall the components that are common to allinstallations, including M3 BOD Processorand M3 Workflow Executor.

Infor M3 Core Installation Guide

This document provides details on the useractions and business events that send Busi-ness Object BODs to ION Connect.

M3 Business Engine BODs Rules Documentation

Not all of these documents are required to set up this integration. For a list of documents that arerequired for this integration, see the integration checklist within this document.

Contacting InforIf you have questions about Infor products, go to Infor Concierge at https://concierge.infor.com/ andcreate a support incident.

The latest documentation is available from docs.infor.com or from the Infor Support Portal. To accessdocumentation on the Infor Support Portal, select Search > Browse Documentation. We recommendthat you check this portal periodically for updated documentation.

If you have comments about Infor documentation, contact [email protected].


About this guide

https://concierge.infor.com/

https://docs.infor.com/

mailto:[email protected]

Chapter 1: Requirements

Ensure that all requirements are met.

Required productsEnsure that you have installed and configured these products:

• Infor M3 Core infrastructure and technology 13.4.0 or later.

See the Infor M3 Core Installation Guide.

• Infor M3 Business Engine 15.1.4• Infor M3 Business Engine BODs 15.5.0.0 patch 6. See KB 1895800 for the latest updates• Infor OS release 12.0.x or later.

The installation of Xi Platform includes these products: Infor Ming.le, Infor ION, Infor DocumentManagement, and ION Grid.

The server where you install Infor OS must be able to connect to the servers where you install InforM3 Business Engine and other BOD-enabled products.

See the Infor OS Installation Guide.

Application CompatibilityThis table lists the applications for Infor M3 that run in Infor Ming.le. Required software must be installedand configured before you create the application.

Related installation documen-tation

Software versionInfor Infor Ming.le application

See the M3 Core InstallationGuide for more informationabout these versions:

M3 Business Engine 15.1.4 orlater

M3 Business Engine 15.1.4 orlater

M3 Foundation 10.1.4.5 or later

Infor M3


Requirements

Related installation documen-tation

Software versionInfor Infor Ming.le application

See the M3 Core InstallationGuide

Infor M3 Metadata Publisher10.1.x

Infor M3 Metadata Publisher(MDP)

See the Infor Enterprise Searchfor M3 Installation Guide for In-for M3 LifeCycle Manager 10.x

Infor Enterprise Search for M311.x

Infor Enterprise Search

See the M3 M3 Graphical LotTracker Installation Guide

Infor M3 M3 Graphical LotTracker 10.0.x

M3 Graphical Lot Tracker

See the Infor M3 CustomerLifecycle Management Installa-tion Guide

Infor M3 Customer LifecycleManagement 15.4.2 or later

Infor M3 Customer LifecycleManagement

See the Infor Sales Hub Installa-tion Guide

Infor Sales Hub 10.2.0 or laterInfor Sales Hub

See the Infor Supplier RebateInstallation Guide

Infor M3 Business Engine15.1.4 or later

Infor Supplier Rebate

Required informationDuring the planning phase, you must provide this information:

• Name of the M3 instance (host and port) or logical ID that is used to connect with Infor ION. SeeSetting up logical IDs, tenants, accounting entities, and locations in M3 on page 37 for informationabout how to set up the logical ID for M3.

• Credentials to connect to the application interface, for example, database user, password, servername, port, or instance.

• The tenant ID that is used to connect the application to Infor OS using ION must be Infor. SeeSetting up logical IDs, tenants, accounting entities, and locations in M3 on page 37 for informationabout the tenant ID and how to set it in M3.

• Enterprise organization structure, that is, accounting entities. See Setting up logical IDs, tenants,accounting entities, and locations in M3 on page 37 for information about the accounting entityand how to set it in M3.

• Administrator account for Infor Ming.le and ION• Names and location of files to import


Requirements

Chapter 2: Configuration checklist

Follow this checklist to integrate M3 with Infor OS:

ReferenceTaskComplete

Infor OS Administration Guide

Infor ION Desk User Guide

Collect the documents that are listed inthe next column from Infor Support Portal.These documents are required for thisconfiguration.

Infor ION Desk User GuideUnderstand the concepts of ION andBODs and how these concepts relate toM3.

Integration with other applications throughION on page 16

Concepts and definitions specific to thisconfiguration on page 18

Review the description of how this productinteracts with Infor OS.

Setting up M3 to use single sign-on onpage 22

Configure security.

Adding M3 applications in Infor Ming.le onpage 23

Add M3 applications in Infor Ming.le.

• Add the application• Add accounting entities• Add locations

Configuring access to M3 through InforMing.le on page 25

Configure user access and roles.

• Configure user access to M3 in InforMing.le

• Configure additional system adminis-tration access to M3 through InforMing.le

• Set up roles in Infor Ming.le• Optionally, set up distribution groups

Configuring M3 on page 26Configure M3.


Configuration checklist

ReferenceTaskComplete

Configuring M3 to send and receive BODsin ION on page 40

See "Installing M3 BOD processor" in theM3 Core Installation Guide

Configure M3 and Infor ION to send andreceive BODs.

• Install and configure M3 BOD Proces-sor (prerequisites that are fulfilled bythe installation of Infor M3 Core Infras-tructure and Technology).

• Install Infor M3 Business Engine BODcontent (prerequisites that are fulfilledby the installation of Infor M3 BusinessEngine BOD content).

• Configure a connection point for thisproduct

• Publish BODs• Verify the ION connection

Configuring workflows and ION messagesfor M3 on page 56

Optionally, configure workflows and IONmessages for M3. If you intend to use thesample workflow content, follow thesesteps:

• Install the content• Configure drillback views for Workflow

Modeler

Configuring ION APIs for M3 on page 67Set up ION APIs for M3

Configuring drillbacks to M3 on page 69Configure drillbacks to M3.

Configuring context apps and utility appsthat are used with M3 on page 72

Configure context and utility apps that areused with M3.

Configuring homepages for M3 on page 74Configure homepages for M3.

Configuring Infor Document Managementwith M3 on page 76

Configure M3 to work with Infor DocumentManagement:

• Import configurations and types.• Enable the Related Information con-

text app for M3.


Configuration checklist

Chapter 3: Configuration overview

Before you complete the configuration tasks, you must understand how M3 is used with Infor OS. Youmust also be familiar with the related concepts and definitions.

Infor OSInfor OS is a technology platform that supports fully integrated, industry-specific solution suites withmobile-first design, a consumer-inspired user experience, and science-driven analytics. It leveragesthe convergence of information, analytics, cloud computing, mobility, and social business.

This platform includes these products:

• Infor Ming.le• Infor ION• Infor ION Grid• Infor Document Management• Infor Business Vault• M3 Analytics• Infor d/EPM Platform• Localization Services

Infor Ming.leInfor Ming.le is a web-based application framework that provides a common user interface for Inforapplications, third-party applications, and in-house developed applications that are integrated throughInfor ION. It is a centralized platform for social collaboration, business process improvement, andcontextual analytics.

Infor Ming.le provides drill-back capability so that users can navigate across the applications to tracktransactions, the transfer of data, and report updates. Additionally, Infor Ming.le provides an infrastructurefor sharing content with context applications.

Infor Ming.le uses homepages, which are configurable by users, to organize information and activitiesat a high level to focus on critical areas of concern.


Configuration overview

Within Infor Ming.le, you can use ION API, a managed API layer across all applicable Infor and non-InforAPIs, allowing existing APIs to be presented in a standardized, managed, and controllable way.

Infor Ming.le uses Infor Federation Services (IFS) for centralized authentication.

Infor Ming.le is available as a mobile app, supported on iOS, Android™, and Windows Mobile operatingsystems.

Infor IONInfor ION is a platform for business process management that integrates applications, people, andbusiness processes. The Infor ION platform converts data into the common language of standardizedXML to enable disparate business systems such as Infor products, third-party applications, and in-housedeveloped applications to share information.

Infor ION simplifies the connectivity and data sharing across the connected applications. It enablesusers to configure a routed infrastructure, set up workflows, and design and activate business eventmonitors and manage tasks and alerts.

ION componentsInfor ION has these components:

• With ION Connect, you can establish connections between applications which can either be Inforapplications or third party applications. You can configure ION Connect through ION Desk.

• ION Desk is an intuitive, browser-based interface that is used to configure and monitor ION Service.

In ION Desk, you can model document flows between applications. Such flows can represent abusiness process. In addition, further technical flows can be defined. For example, mapping datafrom a third-party application to a standard business object document as used by an Infor application.You can also use filtering or content-based routing.

From ION Desk you can integrate your models into ION Service by activating them.• ION Service then handles your documents according to your activated models. ION Desk also

provides management screens to monitor the behavior of ION Service and help troubleshootingwhen required.

• In Infor Event Management you can monitor business events and create alerts when exceptionsoccur.

The starting point for monitoring is the business object documents that are published by theapplications when business events occur. Monitors are processes that run in the Event Managementengine and evaluate these documents according to predefined business rules.

There is a predefined set of business rules that the monitoring engine can apply: comparisonconditions, value change conditions, and rules based on overdue dates. If exceptions are recognized,they are reported as alerts to the business users. The Alerts distribution list is part of the monitordefinition.

• ION Workflow is used to model and run business processes such as authorizations, work distributionor task-driven workflows across several components.



For authorizations, you can use an approval workflow to approve a purchase order or sign off anew item. Such workflows are triggered by the creation of a new item or the submission of a neworder.

In the area of work distribution, the workflow ensures that all tasks for a certain event are distributedand executed by different users. The advantage of using the ION Workflow is that you can modelhow these tasks are performed, for example sequentially or in parallel.

• ION Pulse is the component that ensures communication with the end user. ION Pulse managesalerts, tasks and notifications and distributes them to users. When users take action in Infor Ming.le,ION Pulse records these actions and returns the response to the engine that generated the useractivity. ION Pulse is also the component that sends email notifications for tasks, alerts, andnotifications.

For more information about these components, see the Infor ION User Guide.

See ION Connect concepts in the ION User Guide to understand common ION concepts such as BODnouns and verbs, document flows and workflows, listeners and connection points.

Integration with other applications through IONAn outbound operation typically begins when a user performs an action in M3 that requires a dataexchange with another ION-enabled application. A BOD XML message is generated by M3 and placedin an area designated as the M3 message outbox. At scheduled intervals, ION connects to the M3outbox and retrieves the BODs from it.

In ION, you create application connection points, which define the connections between ION and aproduct that can send and receive BODs. ION Connect routes BODs according to the document flowsbetween M3 and other ION-enabled applications.

The document flows between M3 and other applications represent the business relationship betweenthe databases. You use the the ION Document Flow Modeler page to define these document flows.

If a document flow is defined from M3 to another application for a particular BOD, then, at specifiedintervals, ION places the outbound BOD from M3 in the other application's designated message in-box.Applications are responsible for validating and incorporating the data in inbound BODs according totheir rules.

If a flow is defined from another application to M3, ION retrieves BODs from the sending application’smessage outbox and delivers them to M3's message inbox for processing. M3 retrieves, validates, andprocesses the BODs.

To understand common ION concepts such as BOD nouns and verbs, document flows and workflows,listeners and connection points, see the "ION Connect Concepts" section in the ION Desk User Guide.

Infor ION GridInfor ION Grid is a Java-based application server that provides a distributed runtime environment forother applications. Those other applications may, at any time, be added (deployed) or removed



(undeployed) from a grid. The distributed nature of a grid means that an instance of Infor ION Grid mayspan multiple server machines.

See the Infor ION Grid Administration Guide for administration tasks such as monitoring, configuring,or managing the grid.

Infor Document ManagementInfor Document Management is an integration platform that enables you to take advantage of documentsolutions that are already in use within your organization.

Document Management is used to integrate your documents with your business processes and toprovide a central repository for them. Soft links are used, based on document metadata, to provideintegration between your documents and your Infor ERP solution. You can view a document from withinthe context of M3, or click a document link to retrieve the document from the central repository.

Document Management supports the entire life cycle of your business documents, from input throughstorage, retrieval, and sharing.

Infor Business VaultInfor Business Vault is a software platform for data acquisition and enrichment. The business datarepository contains one or many data stores populated by Infor Business Vault software. The datastores are available for searching data, running reports, and synchronizing data.

AnalyticsM3 Analytics provides industry-specific content for the Infor d/EPM Platform solution for M3. M3 Analyticsuses Infor d/EPM Platform to enable access to the dashboards and widgets.

M3 Analytics contains these components:

• Business Measurement Models (BMMs)

BMMs extract and transform the source data into an analytical data model that contains fact tablesand dimension tables.

• Online Analytical Processing (OLAP) cubes

The OLAP cubes summarize data along defined dimensions and hierarchies. The cubes alsocontain dimensions for time and time-series analysis, making it easy to compare years or periodson various levels.

• Dashboards and widgets



Infor BIInfor d/EPM Platform supports all typical internal and external business intelligence requirements, withflexible ad hoc analysis and planning.

The Infor d/EPM solution suite is predominantly used where highly specific business needs must befulfilled. Usually, the solution is based on a multidimensional OLAP approach and uses dashboardsand widgets for reporting.

Concepts and definitions specific to this configurationYou must understand these terms and how they are defined in this application.

.

Tenant IDThe tenant is a container for accounting entities and locations and is required in each BOD. The valueof the tenant must be the same in all of the applications that exchange BODs. Data is not shared oraccessible between tenants.

See the information about using tenants in the ION Desk User Guide.

To ensure that the infor default value is used, leave the tenant ID for your connection point unspecified.Infor OS, single tenant version, only allows infor as the tenant ID value.

Accounting entityAn accounting entity usually represents a legal or business entity that owns its general ledger. Everytransaction belongs to only one accounting entity. An accounting entity can also be defined as theowner of certain master data within an enterprise.

In M3, accounting entity corresponds to a division within a company. Accounting entity is set accordingto the <CONO_DIVI> syntax.

LocationA location is the physical location that is associated with data or transactions. The location can be, forexample, 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 fromwhich 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 IDThe logical ID is a unique identifier used in the communication of data between the products in thetenant’s environment. Each instance of a product, for example, a site, is assigned one logical ID. InION, the logical ID is used to properly route BODs. Infor Ming.le uses the logical ID to determine whichapplication to start when you click a drillback.

For M3, you configure the logical ID in Infor Enterprise Collaborator as ionFromLogicalid. You mustprovide the logical ID when you define the ION connection point for on-premises applications.

For cloud applications, the logical ID is defined by the Infor Cloud team and is retrieved automaticallywhen the application connection point is created in ION.

In Infor Ming.le, each application is assigned only one logical ID regardless of the number of instancesof the application.

For more information, see the Infor OS Administration Guide.

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

M3 Business Engine BODsThe ION Connector component for M3 is called Infor M3 Business Engine BODs. M3 BODs use theEvent Hub to send and receive data from Infor M3 Business Engine to Infor Enterprise Collaborator.Infor Enterprise Collaborator uses event data to create BODs that are sent to ION. BODs that are sentfrom ION are detected in Infor Enterprise Collaborator and sent to Infor M3 Business Engine throughAPI transactions.



M3 Workflow ExecutorM3 Workflow Executor provides web service interfaces that enable ION workflows to interact with M3Business Engine API programs.

For more information on the usage of the M3 Workflow Executor, see M3 Workflow and Alert ContentExamples for Infor ION.

M3 BOD architectural overview and data flowThe flow diagram shows the various application components that are involved in transferring BODsfrom M3 to ION and back.

The BOD outbound data flow is based on events. An event represents predefined data. The Event Hubis the central place where all events are directed to its subscribers. M3 Foundation events can be basedon program or table operators: Start, Exit, Fail, Create, Update, Delete, Request, or Response. Eventsthat 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 alwaysplaced in a rules session. When the rule is activated and the rule session started, events get publishedby M3 Foundation and are subscribed by Event Analytics. If the criteria in the rule, such as a specificstatus or a field with matching value, are valid, a new event called M3BEBODs is published. Invalidevents 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.

M3 BOD Processor subscribes to all M3BEBOD events. All events are republished with M3 BODProcessor being the publisher and the name of the event document being the verb in BODVerb combinedwith the noun in BODNoun. Based on the value in findDIVI, the M3 BOD Processor performs one ofthese 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 theAnalyticsHubPublisherDocName target group, which contains the targets, that is publisher and eventdocument name, for the event. To trigger a BOD-specific partner agreement in Infor EnterpriseCollaborator, these requirements must be met:

• M3 BOD Processor must be 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:

DescriptionStep

The data is retrieved from M3 Business Engine through APIs and convertedinto an XML file.

XML transform

This process packs the XML data into a BOD format.Apply Envelope

This process sends the BOD to the ION ION Connector DB. ION retrieves thedata from the ION ION Connector DB and processes it.

Send

Inbound BODs are sent from ION to ION ION Connector DB, where Infor Enterprise Collaboratorcollects the BODs. Inbound BODs are detected on the EC manifest com:ionBODType, which is setfrom the IOBox metadata. After the detection, there are additional steps for an inbound ProcessBOD,which send an AcknowledgeBOD back to ION. The most common step is XML transform, whichuses APIs to add data to M3 Business Engine.



Chapter 4: Configuring security

Single sign-on allows users to use one set of credentials to log into all Infor applications.

Infor M3 is set up for single sign-on in Infor Ming.le through the use of SAML authentication, MicrosoftADFS and Integrated Windows Authentication. This requires an environment where a Windows domaintrust between the client systems and the ADFS host is configured.

See the Infor OS Installation Guide for information about the client single sign-on experience and aboutthe SAML session provider.

Setting up M3 to use single sign-onSee "Security considerations" in the M3 Core Installation Planning Guide for how to configure M3 CoreInfrastructure and Technology for single sign-on.

Single sign-outWhen a user signs out of a portal such as Infor Ming.le, the user is automatically logged out of allapplications, context applications, and widgets that were opened by the user through the portal.


Configuring security

Chapter 5: Adding M3 applications in Infor Ming.le

You must add your M3 application in Infor Ming.le.

Adding the application1 Sign in to Infor Ming.le.

Note: You must login with a MingleAdministrator security role to access the Admin Settings.

2 Select User Menu > Admin Settings.

3 On the Manage Applications tab, click Add Application.

4 In the Add New Application window, specify this information for the Infor M3 application:

Note: The available M3 applications are Infor M3, M3 Graphical Lot Tracker, MDP, Infor M3Customer Lifecycle Management, Infor Enterprise Search, Infor Sales Hub, and Infor SupplierRebate.

Application TypeSpecify Infor Application.

Application NameSpecify application name and version.

Display NameSpecify the display name for the application.

Application IconSelect an application icon.

Each application has its default icon. You can only select the color that you want to apply to theicon.

Logical IDSpecify a unique logical ID for the application.

Use HTTPSSelect this option. Ensure that you have specified the HTTPS port in the Port field.

If Infor M3 uses HTTP, do not select this option.


Adding M3 applications in Infor Ming.le

Host NameFor Infor M3, MDP, Infor M3 Customer Lifecycle Management, Infor Enterprise Search, Infor SalesHub, and Infor Supplier Rebate, specify the fully qualified domain name (FQDN) or IP address toidentify the Load Balancer (if used) or the ION Grid router that is configured for authentication withSAML Session Provider for the application that you are configuring.

For M3 Graphical Lot Tracker, specify the FQDN of the GLT server or the IP address.

Note: The specified address must correspond to a configured Login Endpoint for the SAML SessionProvider. See "Configuring Login and Logout Endpoints" in the Infor M3 Core Installation Guide.

PortSpecify the HTTPS listening port for M3 that corresponds to the address that is specified as theHost Name.

ContextAccept the default.

Note: This field is automatically populated when you select an application.

Default TenantThis field is empty by default.

5 Click OK.

6 In the Application details window, review the information under the Deployment Informationtab.

Note: Default values are populated when the application is created. Do not change the defaults.

7 Click Save.


Adding M3 applications in Infor Ming.le

Chapter 6: Configuring access to M3 through InforMing.le

Users, roles, and person IDs are defined and shared among Infor Ming.le and all of the other applicationsthat run through the Infor Ming.le portal.

User access for M3 Core is handled in Infor Ming.le. See "Admin Tasks for User Management" in theM3 Core Administration Guide.

Users and rolesBecause Infor Ming.le is the system of record for users, you must set up users in Infor Ming.le and thensynchronize them with other applications in the Infor Ming.le portal by using BODs. After the users aresynchronized with M3, you can continue the user setup in the 'User. Open' (MNS150) M3 BusinessEngine function.

You can perform these user management tasks in Infor Ming.le:

• Create users, including manual import of users• Update users (for M3, this is currently not supported)• Deactivate users (for M3, this is currently not supported)• Reset passwords• Monitor recent user activity and mobile sessions• Manage sessions

When you create or update a user in Infor Ming.le, the information that is associated with that user isused to automatically set up some user information in M3. This association is handled throughSyncSecurityUserMaster BODs that are passed through ION Desk.


Configuring access to M3 through Infor Ming.le

Chapter 7: Configuring M3

You must set up M3 so that it can generate BODs and place them in a message out-box from whichInfor ION Connect can retrieve them.

You must also set up the inbound message configuration, so that BODs that are sent to M3 can processthose messages.

Configuring BOD-specific settingsThis section describes how to configure BOD-specific settings.

Configuring settings for catalog BODsThe triggering of the catalog BOD differs from the M3 standard triggering of BODs.

When a new assortment is created in 'Assortment. Open' (CRS105), a catalog header BOD isgenerated. This event is created automatically.

Note: The catalog BOD may be large. If the assortment comprises 10000 items and 5000 customers,the size of the BOD may be about 5 MB. Processing in Infor Enterprise Collaborator can take longerthan with other BODs.

1 Create a new assortment in 'Assortment. Open' (CRS105).

2 After the assortment setup is complete, select RELATED > Publish BOD.

This option sends an event that creates the complete catalog BOD, catalog header, catalog line,and catalog customer segment (CRS 105 assortment, OIS071 assortment customer, and OIS072assortment item).

Configuring settings for customer master data BODsComplete the steps to receive and process these partner agreements:• M3_CustomerPartyMaster_Process_In• M3_ShipToPartyMaster_Process_In


Configuring M3

• M3_BillToPartyMaster_Process_In• M3_PayFromPartyMaster_Process_In

1 In Infor M3 Business Engine, create the IONCUST customer in CRS610 and specify this information:

Customer TypeSpecify 0.

2 Fill in all required fields and ensure that the status is set to 20.

Caution: Do not add an Invoice recipient (INRC) or Payer (PYNO) in the CRS610/J panel.

Configuring settings for ProcessContactMasterComplete these steps to receive and process BODs corresponding to the M3_ContactMaster_Process_Inpartner agreement.

1 In the Infor Enterprise Collaborator Partner Administration tool, go to theM3_ContactMaster_Process_In partner agreement.

2 On the Basic tab, click Control Properties and check these control properties:

• m3beContactPrefix: This optional control property can be used to set the prefix for naming anew contact that has been created with ProcessContactMaster.

• m3beContactSequenceDigits: This optional control property can be used to set the number ofdigits for the sequence following the prefix when naming a new contact that has been createdusing ProcessContactMaster. The default value is 3 if this value is not provided.

If m3beContactPrefix is set to CONTACT and m3beContactSequenceDigits is set to 3, the input tothe MI program for the Contact field will be CONTACT???, where ??? auto-generates a sequencewith 3 digits.

If the input BOD xml contains an ID for the contact, it will be used as input in the MI program.

3 Click Save.

Configuring settings for ProcessPurchaseOrderComplete these steps to receive and process BODs corresponding to theM3_PurchaseOrder_Process_In partner agreement.

1 In the Infor Enterprise Collaborator Partner Administration tool, go to theM3_PurchaseOrder_Process_In partner agreement.

2 On the Basic tab, click Control Properties and check the m3beCheckFlagCompleteExist controlproperty:

This optional control property is used to determine whetherPurchaseOrderLine\Classification\Codes\Code with the attribute listID equals "Flag Complete"must exist in the input BOD xml before PPS001MI ConfirmLine or FinishMark is called. If the valueis true, the attribute must exist in the input BOD xml, otherwise PPS001MI ConfirmLine orFinishMark will be called regardless of the existence of the attribute.


Configuring M3

3 Click Save.

Configuring settings for ProcessQuoteComplete these steps to receive and process BODs corresponding to M3_Quote_Process_In.

1 In Infor M3 Business Engine, create an order type with the order category 4 in 'CO Type. Open'(OIS010).

2 In the Infor Enterprise Collaborator Partner Administation tool, go to the M3BE_In_ProcessQuotepartner agreement.

3 On the Basic tab in Control Properties, check the m3beDefaultQuoteOrderType controlproperty.

This optional control property can be used to set the default order type when creating new salesquotations using ProcessQuote.

4 Click Save.

Configuring settings for ProcessRequisitionComplete these steps to receive and process BODs corresponding to the M3_Requisition_Process_Inpartner agreement.

1 In the Infor Enterprise Collaborator Partner Administation tool, go to the M3_Requisition_Process_Inpartner agreement.

2 On the Basic tab, click Control Properties and check these control properties:

m3beDirectPurchaseOrderTypeThis control property allows you to indicate the purchase order (PO) type for the planned purchaseorder. Through this, a PO type with Update Material = 0 may be defined for direct purchasetransaction. The hierarchy of retrieving the PO type is as follows:• Requisition/RequisitionHeader/Classification/Codes/Code@listID="Purchase Order Types"• Check if

Requisition/RequisitionLine/UserArea/Property/NameValue@name="eam.ReqLineType" isPD, then retrieve input from the m3beDirectPurchaseOrderType control property.

• Order type in 'Item. Connect Warehouse' (MMS002)

Default value for this control property is DPO. This record should be created in 'Purchase OrderType. Open' (PPS095) with 150 Material plan update = 0-No.

m3beStatusOverrideThis control property indicates the status for the requisition. If the requisition has already beenapproved by the integrating system before it is sent to M3, the record is created in M3 with status60. A requisition with status 60 automatically creates a purchase order. If changes to the requisitionare required before the purchase order is created, this control property can be used to reset therequisition status to 20. This control property is initially set to the default value.


Configuring M3

3 Click Save.

Configuring settings for Sync and Show SalesOrderComplete these steps to publish M3_SalesOrder_Sync_Out and M3_SalesOrder_Show_Out:

1 In the Infor Enterprise Collaborator Partner Administration tool, go to the M3_SalesOrder_Sync_Outor M3_SalesOrder_Show_Out partner agreement.

2 On the Basic tab, click Control Properties and check this control property:

m3beSalesOrderUnitPriceCompFlagOptionally, use this control property to set the computation of the UnitPrice/Amount andUnitPrice/BaseAmount. Permitted values are 0 or 1.

If m3beSalesOrderUnitPriceCompFlag is set to 1, the sales price or unit price that is retrievedfrom the API is multiplied by the per quantity (M3 field SACD). The same computation is used forUnitPrice/BaseAmount.

The default value of m3beSalesOrderUnitPriceCompFlag on delivery of the BOD is 0 (zero). Thecurrent functionality is retained, values are retrieved from the API.

3 Click Save.

Configuring settings for Sync and ShowInvoiceCustomerOrderComplete these steps to publish M3_InvoiceCustomerOrder_Sync_Out andM3_InvoiceCustomerOrder_Show_Out:

1 In the Infor Enterprise Collaborator Partner Administration tool, go to theM3_InvoiceCustomerOrder_Sync_Out or M3_InvoiceCustomerOrder_Show_Out partner agreement.

2 On the Basic tab, click Control Properties and check this control property:

m3beInvoiceCOBaseAmtCompFlagOptionally, use this control property to set the computation of the UnitPrice/BaseAmount. Permittedvalues are 0 or 1.

If m3beInvoiceCOBaseAmtCompFlag is set to 1, the base amount that is retrieved from the APIis multiplied by the per quantity (M3 field SACD).

The default value of m3beInvoiceCOBaseAntCompFlag on delivery of the BOD is 0 (zero). Thecurrent functionality is retained, the value is retrieved from the API.

3 Click Save.


Configuring M3

Configuring settings for incoming supplier invoice BODsComplete these steps to receive and process BODs corresponding to M3_SupplierInvoice_Load_Inand M3_SupplierInvoice_Process_In.

1 In the Infor Enterprise Collaborator Partner Administration tool, go to theM3_SupplierInvoice_[Load][Process]_In partner agreement.

2 On the Basic tab, click Control Properties and ensure that the m3beInvoiceValidation controlproperty has one of these values. It defines whether the invoice validation routine is startedautomatically or manually in Infor M3 Business Engine.

DescriptionValue

The validation routine is started automatically immediately after the invoice has beenadded in M3 Business Engine.

*YES

The validation routine must be started manually in M3 Business Engine.*NO

3 Click Save.

Configuring settings for incoming warehouse managementBODsComplete the steps to receive and process BODs corresponding to these partner agreements:

• M3_AdvanceShipNotice_Load_In• M3_AdvanceShipNotice_Process_In• M3_AdvanceShipNotice_Sync_In• M3_InventoryAdjustment_Process_In• M3_InventoryAdjustment_Sync_In• M3_InventoryHold_Sync_In• M3_ReceiveDelivery_Process_In• M3_ReceiveDelivery_Sync_In• M3_ServiceConsumption_Sync_In• M3_Shipment_Process_In• M3_Shipment_Sync_In• M3_M3EDIAdvanceShipNotice_Load_In

1 In Infor M3 Business Engine, create a message partner in ‘M3 Stock Msg Partner.Open’(MMS865).

2 Specify this information:

WhsLeave blank.

MsgSpecify I.


Configuring M3

PartnerSpecify the application ID of the system that sends the BOD, for example, WM.

The application ID corresponds to the second element of the logical ID, that is: lid://infor.<applicationid>.<application instance>.

Msg typeSpecify BOD.

3 Select Options > Create.

4 In MMS865/E, specify a valid M3 user in 300 Partner manager and verify these values:

Msg directionI-Input

PartnerApplication ID of the system that sends the BOD

Msg typeBOD

5 In the Infor Enterprise Collaborator Partner Administration tool, go to the partner agreement forthe specific M3_Noun_Verb_In BODs.

6 Click the Basic tab. In Control Properties, verify that the m3beWarehouseInterfaceProcessFlagcontrol property has one of these values:

DescriptionValue

Message is processed in an asynchronous mode through a batch job.

This setting is recommended for high volume environments. Users can find,correct and re-run failed messages in MHS850 and can also use the mailboxfunctionality in Infor M3 Business Engine to be notified when a messagefails.

Note: Error messages are not returned by the API.

*AUT

Message is processed interactively in Infor M3 Business Engine.*EXE

Note: Control properties enable messages to be processed online or through batch jobs. Leavingthe control properties value in Infor Enterprise Collaborator empty means that the user must executethe messages through the related option 21 in MHS850/MMS850.

7 Click Save.

Configuring settings for LoadAdvanceShipNotice,ProcessAdvanceShipNotice, and SyncAdvanceShipNoticeComplete these steps to receive and process BODs corresponding to theM3_AdvanceShipNotice_Load_In partner agreement.


Configuring M3

1 In Infor M3 Business Engine, create a message partner in 'M3 Stock Msg Partner.Open'(MMS865).


WhsLeave blank.

MsgSpecify I.

PartnerSpecify the name of the system that sends the AdvanceShipNotice BOD.



4 In MMS865/E, specify a valid User in 300 Partner manager:

5 In the Infor Enterprise Collaborator Administration tool, go to the M3_AdvanceShipNotice_Load_Inpartner agreement.

6 Click the Basic tab. In Control Properties, ensure that them3beWarehouseInterfaceProcessFlag control property has one of these values:

DescriptionValue

AdvanceShipNotice is created in an asynchronous mode using a batchjob.

This setting is recommended for high volume environments. Users canfind, correct, and re-run failed messages in MHS850. They can also usethe mailbox functionality in Infor M3 Business Engine to be notified whena message fails.

Note: Error messages are not returned by the API.

*AUT

MHS850MI is run and the AdvanceShipNotice is created in M3.*EXE

Caution: Control properties enable messages to be processed online or through batch jobs inInfor M3 Business Engine. Leaving the control properties value blank means that the user mustmanually execute the messages through the related option 21 in MHS850.

7 Click Save.

Configuring settings for ProcessItemMasterComplete these steps to receive and process BODs corresponding to the M3_ItemMaster_Process_Inpartner agreement.

1 In M3 Business Engine, create an item type in 'Item Type. Open'(CRS040).


Configuring M3

2 Create a Template Item (MMS001/MMS002/MMS003) and an Item Numbering rule (MWS050 andMWS051) with valid data. The item type in CRS040/E should be assigned status 10.

Caution: The Item interface controlled field in CRS040/E must be enabled.

3 In ‘M3 Stock Msg Partner.Open’ (MMS865), specify this information:

WhsLeave blank.

MsgSpecify I.

PartnerThe value should be set, in capital letters, to the Infor application ID, which is retrieved from thelogical ID.

Example: If the logical ID is lid://infor.plmprocess.server123, the application ID isPLMPROCESS.



5 In MMS865/E, specify this information:

Partner managerSpecify the M3 user who is managing the partner settings for this record.

Default Item typeSpecify the item type that controls which data is the default for each item and how the itemnumbering is done.

6 In the Infor Enterprise Collaborator Partner Administration tool, go to the M3_ItemMaster_Process_Inpartner agreement.

7 On the Basic tab in Control Properties, ensure that the m3beItemInterfaceProcessFlag controlproperty has one of these values:

DescriptionValue

Data is only added. Validation and import to M3 is done manually.blank

Data is added and validated. Import to M3 is done manually.*VAL

Data is validated and, if there are no validation errors, imported to M3.*IMP

Same as *IMP, but the processing is done by auto job MHS250.*AUT

This property enables messages to be processed online or through batch jobs in M3 BusinessEngine.

8 Optionally, use the m3beLotControlMethod control property to set the M3 Business Engine fieldLot control method (MITMAS.MMINDI) when creating new items using ProcessItemMaster. Thecontrol property is only considered if the incoming ProcessMaster BOD has either the


Configuring M3

<SerialControlIndicator> element or the <LotControlIndicator> element set to true. On the Basictab in Control Properties, check the status of the m3beLotControlMethod control property.

a If the control property is missing, the M3 Business Engine field Lot control method is setaccording to these rules:

• If the <SerialControlIndicator> element is true, then M3 Business Engine Lotcontrol is set to 2.

• If the <SerialControlIndicator> element is false or missing and the <LotControlIndicator> element is true, then M3 Business Engine Lot control is set to 3.

b If the control property is set, the M3 Business Engine Lot control method field is set accordingto these rules:

• If m3beLotControlMethod is 1 or 3 and the <LotControlIndicator> element is trueAND <SerialControlIndicator> is set to false or missing, then M3 Business Enginelot control is set to 1 or 3 respectively.

• If m3beLotControlMethod is 2 or 5 and <SerialControlIndicator> is set to true,then M3 Business Engine lot control is set to 2 or 5 respectively.

9 Click Save.

Configuring settings for inbound SyncBillOfMaterialsComplete these steps to receive and process BODs corresponding to the M3_BillOfMaterials_Sync_Inpartner agreement:

1 In the Infor Enterprise Collaborator administration tool, go to the M3_BillOfMaterials_Sync_Inpartner agreement.

2 Click the Basic tab.

3 In Control Properties, ensure that these properties have the applicable values:

m3beSequenceNumberIntervalSpecify the numeric value to set the bill of material sequence number interval in 'Product. ConnectMaterials/Operations’ (PDS002).

m3beSetStatusToPreliminarySet to true to set the initial product status to 10-Preliminary in 'Product Structure. Open’(PDS001). Otherwise, set to false.

m3beUsedInStandardSet to true if the Used in standard check box in 'Product. Connect Materials/Operations' (PDS002)should be selected. Otherwise, set to false.

4 Click Save.


Configuring M3

Configuring settings for ProcessWorkflowM3 can publish a ProcessWorkflow BOD that can start a workflow in ION.

The ProcessWorkflow BOD publishes this information:

• WorkflowDefinitionCode: This is the name of the workflow inION that should be started.• Property/NameValue: M3 data is published in the /Property/NameValue element in the BOD, with

the M3 field name as attribute and the M3 field value as element. There are two different sets ofdata:• Data that is related to the application message (CMAILB M3 table)

• Message ID (CBMLID)• Message receiver (CBREC2)• Message text (CBMSGT): The message text from M3 may be a maximum of 180 characters

long, the NameValue element in the BOD a maximum of 64 characters. Therefore, themessage text from M3 is published in up to three different NameValue elements with theMSGT1, MSGT2 and MSGT3 attribute names.

• Data that is related to the M3 record that triggered the application message:• M3 publishes the key values for the record that triggered the application message.

Note: For this set of M3 data, the field name is published without the M3 table prefix. Forexample, the item number field name is published as ITNO and not MMITNO. This simplifiesusing the data in the Infor ION Workflow & Events to call an M3 API.

Configuring M3 application message settingsThe functionality is based on the M3 application message and is implemented for these M3 functions:

• ‘M3 Ad Hoc Report.Open’ (AHS110)• ‘M3 Event Based Alerts.Open’ (CMS047)• ‘M3 Settings - Application Messages’ (CRS424)

Configuring ad-hoc reports1 Open 'Ad Hoc Report. Open' (AHS110) and navigate to the F panel.


Ad hoc app msgSet to 2-Current User or 3-Specific receiver.

BOD enabledSelect the check box.

BOD message typeSet to 4-Workflow.


Configuring M3

Workflow nameSpecify the name of the workflow in ION that should be started by this application message.

3 Open ‘M3 Settings - Application Messages’ (CRS424). Ensure that Applicationmessage type (Appl msg type) 11 is activated.

Configuring event-based alerts1 Open ‘M3 Event Subscription.Open’ (CMS045). Set up a valid event subscription.

2 Open ‘M3 Event Based Alerts.Open’ (CMS047). Set up a valid event-based alert.


Ad hoc app msgSet to 2-Current User or 3-Specific receiver.




4 Open ‘M3 Settings - Application Messages’ (CRS424). Ensure that Applicationmessage type (Appl msg type) 12 is activated.

Configuring M3 application messages1 Open 'Settings - Application Messages' (CRS424).


Activity codeSet to 2-Current User or 3-Specific receiver.





Configuring M3

Setting master data to standardized valuesTo ensure consistent master data between integrated applications, use the ISO standard values whereapplicable, or use other standard values. M3 Business Message Data Translations is a function thattranslates soft-coded M3 Business Engine data to standards that can be understood by external systemssuch as ION.

Note: A data translation is not required when the M3 Business Engine data is specified according tointernationally acknowledged standards (ISO, X-12 EDI, etc.)

You can set M3 Business Message Data Translations in CRS881 and CRS882 in M3 Business Engine.

• CRS881 stores the header data for information that should be translated. It is generated byMBMTRNUpdate, which is available in the ION Grid management pages for the EC server.

• CRS882 stores the actual translation data. This data must be specified manually in M3 BusinessEngine.

Setting up logical IDs, tenants, accounting entities, andlocations in M3• The tenant ID is translated from the M3 company value when the BOD is generated. See Specifying

or editing translation data on page 37 for instructions on how to configure the translation. Thecompany must be translated to infor. This translation is required.

• You configure the logical ID as a group control property in Infor Enterprise Collaborator. TheionFromLogicalid follows this syntax: lid://infor.m3.environment_instance.

• For M3, accounting entity corresponds to a division within a company. The accounting entity is setaccording to the <CONO_DIVI> syntax.

Specifying or editing translation dataFollow 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 thedata in company / *blank division. If the data is different per division, enter data for a specific company/ division.

Note: The translation information must be specified for the correct company/division.

Before you start, configure the ION Grid management pages for Infor Enterprise Collaborator to connectto the MECDB. For further instructions, refer to the Infor Enterprise Collaborator Administration Guide.

1 In the ION Grid management pages for EC Server, select Utilities > MBMTRN Update.

2 Select the Cumulative or not check box.

3 Select the API reference name to update.

4 Select the mapping names and click Update.


Configuring M3

Note: If no mapping is selected, all the mappings are processed.

5 In M3, open ‘M3 Business Message Data Translation.Displ’ (CRS881) and specifyION in the Msg std field to display all possible records that have been generated from the suppliedBODs.

Note: The following steps depend on the entry that the business message has in the Data elementcolumn.

6 Right-click the business message and select Related > Translate CTRL+11.

7 In CRS882/B1, specify the M3 data and Message data for the business message:

• For business messages with the TenantID data element, add one record for each applicablecompany number (CONO).• The M3 data field should contain the company number (CONO).• The Message data field should contain infor.

• For business messages with the languageCodes data element, add one record for each ofthe 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 unitof 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 ofmeasures, data translation settings must be performed for both incoming and outgoingmessages.

• For business messages with the CountryCode data element, add one record for each countrycode 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 countrycodes, 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 currencythat 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 ISOstandards.

• For business messages with the TransportationMethodCode data element, add one recordfor 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.


Configuring M3

Note: We recommended to set up the delivery terms according to Incoterms in M3. In thatcase, no translation is required. Otherwise data translation settings must be performed for bothincoming and outgoing messages.

• For business messages with the ShippingMaterial data element, add one record for each ofthe 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 shippingmaterial, data translation settings must be performed for both incoming and outgoing messages.

8 Click Create.

9 In CRS882/E, specify a Name and a Description. Click Next.

10 Repeat the required steps for each business message for which data translation is applicable.

Setting up logical IDs, tenants, accounting entities,and locations in M3• The tenant ID is translated from the M3 company value when the BOD is generated. See Specifying

or editing translation data on page 37 for instructions on how to configure the translation. Thecompany must be translated to infor. This translation is required.

• You configure the logical ID as a group control property in Infor Enterprise Collaborator. TheionFromLogicalid follows this syntax: lid://infor.m3.environment_instance.

• For M3, accounting entity corresponds to a division within a company. The accounting entity is setaccording to the <CONO_DIVI> syntax.

Setting up the system to send initial dataInfor M3 Business Engine does not require any specific setup to send initial data. See Sending theinitial data load on page 53.

To initiate the initial load for a noun, use ‘Initial Load.Start’ (EVS005).

The ionToLogicalId control property in the Partner Administration tool must be populated with the logicalID of the target application connection point in ION Connect.

Note: The initial load of large tables takes a long time. We recommend that you run only one table pertime unit. You must ensure that sufficient resources are available in the system at the time of the initialload.


Configuring M3

Chapter 8: Configuring M3 to send and receive BODsin ION

This section describes how to configure M3 to communicate with ION. Integrations between M3 andother products use ION to send and receive BODs. For details about a specific integration, see theappropriate integration guide.

Installing and configuring M3 Business Engine BODcontentThis chapter describes the installation and configuration of Infor M3 Business Engine BOD content.For instructions detailing the installation of the M3 BOD Processor and the M3 Workflow Executor,refer to the Infor M3 Core Installation Planning Guide and the Infor M3 Core Installation Guide.

Preparing for the installation of the M3 Business Engine BODcontentUse this verification checklist before you start installing M3 BODs.

• Verify your Partner Administration tool. For further information, refer to the M3 Core InstallationGuide.

• Verify that the M3 BOD Processor LCM package is installed. The installation includes installationscripts required for the rulespack archive. For further information, refer to the M3 Core InstallationGuide.

• Verify that the SVCM3BOD M3 user is created or exists in ‘User.Open’ (MNS150) with the3-Support and Service license type and has user access to all M3 Business Engine Company,Division, Warehouse and Facilities information.

To add or update the user access for SVCM3BOD, select Related Options > Update Access allCmp/Div in ‘User.Open’(MNS150) in Infor M3 Business Engine.


Configuring M3 to send and receive BODs in ION

Downloading M3 Business Engine BOD contentThese components, which are available on the download page, are required for your installation.

Note: If an earlier version of the product is already installed, all content files in the current version areremoved during the installation.

Required components

ContainsFile nameDownload page

M3BODs_ver_IEC_data.agr

M3BODs_ver_rulespack_archive.zip

M3BODs_ver_Content.zipInfor M3 BusinessEngine BODs

See KB 1895800 for the latest updates to M3 Business Engine BOD 15.5.0.0.

In addition to the required components, download these optional components as applicable for thebusiness operations in your environment.

Optional components

ContainsFile nameDownload page

Infor Enterprise Collaborator Content for Lo-calization Services:

• M3BODs_ver_LCL_IEC_data.agr• M3BODs_ver_LCL_rulespack_

archive.zip

M3BODs_ver_ LCL_Content.zip

Installing M3 Business Engine BOD contentThis section describes how you install the rulespack archives.

Installing the rulespack archivesFollow these steps to install the rules packages in Event Analytics.

Note: Already existing rules are overwritten by this process.

1 Sign in to Infor M3 LifeCycle Manager as administrator.

2 Locate the ION Grid instance where Event Analytics is installed.

3 Right-click the Event Analytics installation and select Install Rules Packages.



https://www.inforxtreme.com/espublic/EN/AnswerLinkDotNet/SoHo/Solutions/SoHoViewSolution.aspx?SolutionID=1895800

4 In the Tasks dialog, select Upload a rules pack archive to the LifeCycle ManagerServer and click Next.

5 In the Local rules pack archive dialog, click Select and browse to the M3BODs_ver_rulespack_archive.zip file to upload it to Infor M3 LifeCycle Manager Server.

6 Click Open.

7 Click Next.8 In the Verifying package dialog, click Yes to register the rules pack archive file on the Infor M3

LifeCycle Manager Server.

9 Click OK when the Registration successful dialog appears.

10 In the Rules pack archive information dialog, select the M3BODs_ver_rulespack_archive.zip rules pack archive from the drop down list. Click Next.

11 On the Summary page, review the information and click Finish.

12 When the installation is completed successfully, click OK. Optionally, click View log to display thelog file.

13 Repeat this process for any optional rules pack archives.

Note: The rules sessions are stopped by default. You must start a rules session when you wantto use it. In addition to the BOD-specific rules sessions, ensure to start theM3BODs_Correlation_rules session: Correlation rules are used for some of the standard M3 BODs.

Importing M3BODs to Infor Enterprise CollaboratorThe data files of the Infor Enterprise Collaborator tools include partner agreements and componentsthat are required in the Infor Enterprise Collaborator Partner Admin tool. The data files of the InforEnterprise Collaborator tools, as listed in Downloading M3 Business Engine BOD content on page 41,are imported using the Infor Enterprise Collaborator Partner Administration tool.

Note: We recommend that you import the M3BODs Infor Enterprise Collaborator Tools data files intoa clean Infor Enterprise Collaborator database, created according to the M3 Core Installation Guide.

Creating an M3 API reference1 In the Infor Enterprise Collaborator Partner Administration tool, select Manage > Communication

> M3 API and create a valid M3 API reference to the M3 Business Engine environment to getmetadata from Infor M3 Business Engine.

2 Specify the name of this M3 API reference, for example, Import Use, to indicate that this APIreference is only used during the import.

3 Select the newly created API reference and click Use. The Import Use column shows 1.

Importing M3BODs Infor Enterprise Collaborator content

You can import the M3BODs agreement files to the root or to any available folder in the AgreementView of the Infor Enterprise Collaborator Partner Administration tool.



1 From the Agreement View in the Infor Enterprise Collaborator Partner Administration tool, selector create the folder where you want to import the M3 BODs.

2 Right-click the folder and select Import agreement/group.

3 Browse to the M3BODs_ver_IEC_data.agr file in the extracted M3BODs_ver_Content folderand click Open.

4 The import file contains placeholder values that must be replaced for the applicable environmentbefore the import. In Review Suggested Items to override, replace the values to be overridden,for example, CONO, with the values that apply to your installation, and click OK.

5 In the Import Agreement dialog, review the information and click OK.

6 Repeat the procedure for optional M3BODs_ver_[xx]_IEC_data.agr files as applicable.

Updating and validating after import

Follow these steps in the Infor Enterprise Collaborator Partner Administration tool when the import ofM3BODs is completed:

1 Remove the agreements in the removeAfterImport folder, then remove the folder.

2 Update and validate the M3 API reference that is used in the XML transform process.

a Select Manage > Communications, go to the M3 API tab and select the M3 API referenceused in M3 BODs agreements (M3 API).

b Update Name, Host, Port, User, and Password.c Update the control properties on the folder level:

ValueControl propertiesname

Applicable for folders

Change the value to the lid valueof the receiving application in thelid://infor.applicationname.environment name format as defined in the connectionpoint.

Note: This value is case sensitiveand must exactly match the LogicalID value in ION Desk.

ionToLogicalIdION_InitialLoad

After the import of M3 BODs Infor Enterprise Collaborator content is finished, the detectionsare added to the bottom of the detection order.

3 To rearrange the detections in the required order, select Manage > Detection > Detection Orderin the Partner Administration tool.



Enabling the agreement changes in the Enterprise CollaboratorserverActivate the mappings and load new channels in the ION Grid management pages to activate channelsand mappings in the Infor Enterprise Collaborator (EC) server.

Activating the mappings1 Select EC Server > Management Pages > Server > Mappings.

2 Locate the imported mappings.

3 In the Action column, click Activate for the applicable mappings.

Note: You can activate multiple mappings simultaneously by clicking Activate All Inactive in thetop menu.

Loading new channels1 Select EC Server > Management Pages > Server > Overview and click Reload to reload the

agreement information.

2 Select EC Server > Management Pages > Communication3 Click Load New Channels. All new activated channels are loaded.

Using correlation rules with BOD rulesTo reduce the number of M3 BODs to be published, the BOD rules can be configured to use correlationrules. This correlates multiple M3 events that are based on common key values before the BOD ispublished.

When the correlation rule receives multiple events with the same key values, only one is kept. Thesekey values are assigned dynamically. They do not require to be the same as the full M3 key values.

There are two variants of correlation rules, EventCorrelation and TimeCorrelation rules.

DescriptionMethodCorrelation rule

A correlation ID is used tocorrelate the data eventsand the triggering event

Stores M3 events with common key values inmemory until a triggering event occurs.

Examples: A user exits an M3 program, or abatch job is finished.

EventCorrelation

The delay time is the corre-lation factor. When the timeis up, the latest event iscorrelated and released forpublishing.

Stores the M3 events in memory for a specifiedtime until either time is up or another event withthe same key values replaces the latest eventand resets the time count.

TimeCorrelation



Upgrading M3 Business Engine BODsThe requirement for upgrading M3 Business Engine BODs can be provided either by releasing updatesfor the existing version or by releasing a newer version of M3 Business BODs.

Upgrading to a new versionWe recommend that you import the M3 BODs Infor Enterprise Collaborator tools data files into a cleanInfor Enterprise Collaborator database that has been created according to the M3 Core InstallationGuide.

The reason for recommending a clean installation is that there might have been changes in bothmappings and agreements between versions. M3 APIs metadata may also have been updated.

Using new M3 BODs on earlier Infor Enterprise Collaborator tools agreements requires careful reviewon agreement level.

This section describes how to install the new version of M3 BOD parallel to an older version.

Download the deliverables according to Preparing for the installation of the M3 Business Engine BODcontent on page 40.

After downloading the deliverables and importing the Infor Enterprise Collaborator content, return tothis chapter for further upgrade instructions.

Upgrading M3 BODs Infor Enterprise Collaborator contentSee Importing M3BODs Infor Enterprise Collaborator content on page 42.

Updating and validating after importing for upgrade

Agreement files are managed in the Infor Enterprise Collaborator Partner Agreement tool.

Importing the M3 BODs agreement file a second time or more into the same Infor Enterprise Collaboratordatabase creates new Receive communication channels for EventHub Subscriber, corresponding tothe existing set. Any duplicate receive channels of the EventHub Subscriber type must be removed,otherwise Infor Enterprise Collaborator subscribes to the same M3 event multiple times and generatesunnecessary multiple BODs.

1 Remove the agreements in the removeAfterImport folder, then remove the folder.

2 Update and validate the receive channels for IONDbIn and EventHub Subscriber.

3 Select Manage > Communications > Receive.

4 Remove duplicate IONDbIn and EventHub Subscriber channels depending on the previous version:

• ION_In_Ordered• ION_In_NonOrdered• ION_In_NonOrdered2



• MBMInitiator_Subscriber• MEC-M3_In_M3BOD_NonOrdered• MEC-M3_In_M3BOD_BlncDtaFinance_Ordered• MEC-M3_In_M3BOD_MstDtaFinance_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_TrnsDtaFinance_Ordered• MEC-M3_In_M3BOD_TrnsDtaSales_Ordered• MEC-M3_In_M3BOD_TrnsDtaService_Ordered• MEC-M3_In_M3BOD_TrnsDtaSupplyChain_Ordered

5 Update and validate the M3 API reference that is used in the XML transform process:

a Select Manage > Communications, click the M3 API tab, and select the M3 API referencethat is used in M3 Business Engine BODs agreements (M3API).

b Verify Name, Host, Port, User, and Password.c Update the control properties at folder level:

ValueControl proper-ties name

Applicablefor folders

Change the value to the lid value of the receiving appli-cation in the lid://infor.application name.environment name format as defined in the connec-tion point.

Note: This value is case sensitive and must exactlymatch the Logical ID value in ION Desk.

ionToLogicalIdION_Initial-Load

When the import of the M3 BODs Infor Enterprise Collaborator content is finished, the detectionsare added to the bottom of the detection order.

6 To ensure that the agreements are detected in the required order, select Manage > Detection >Detection Order in the Infor Enterprise Collaborator Partner Administration tool and rearrange thedetections.

7 Review broken agreements. If there are broken agreements after import, this usually means thatthe detection for the agreement was incorrect. Manually correct the detection for the relevantagreements.

Connecting new mappings to existing agreementsYou can use new mappings in combination with the existing agreements.

Note: Using new M3 BOD mappings on earlier Infor Enterprise Collaborator Tools agreements requirescareful review at agreement level.



To use the existing agreements and update them with the new imported mappings, consider anydifferences between the existing agreements and the new version of the agreements based on theseaspects:

• Processes• Process steps• Control properties

Upgrading Event Analytics rulesYou can upgrade the rules in Event Analytics by installing new versions of the applicable packagesin the same location as the existing rules packages. Existing rules are overwritten.

Follow these steps to upgrade each applicable rules package in Event Analytics:

1 Extract M3BODs_ver_Content.zip to a temporary folder.

2 Extract M3BODs_ver_rulespack_archive.zip to a temporary folder. All rule sessions (fileswith the .rulespack extension) are extracted.

3 In the ION Grid management pages, select Event Analytics > Management Pages.

4 Click the Rules Package link.

5 Browse to the folder where the extracted rules packages are located. Select the rules package(with the .rulespack extension) to install and click Install selected file.

6 After the installation is complete, the installation results are displayed.

7 To install additional rules packages, navigate to the Event Analytics management pages andrepeat the installation process.

8 To verify the installation, navigate to the Event Analytics application. The installed rules packagesare displayed as individual sessions.

9 Repeat this process for any optional rules pack archives.

Upgrading components within an existing versionThis section describes how to update components within an existing version.

Upgrading individual M3 BOD mappingsYou can update individual M3 BOD mappings by installing them with the Business Document Mapper.

For more information about the installation, see "Importing Mappings, Exporting Mappings, andPublishing Mappings" in the Business Document Mapper User Guide.

The corresponding partner agreements must also be updated to use the updated BOD mappings.



Upgrading partner agreementsPatches for Infor M3 Business Engine BODs can include new partner agreements. Partner agreementsare managed in the Infor Enterprise Collaborator Partner Administration tool. The required configurationdepends on the changes required for the agreements.

Upgrading rules packagesSee Installing the rulespack archives on page 41.

You can upgrade rules packages using the Event Analytics ION Grid management pages.

Note: Existing rules with the same names in the rule session are overwritten. Any modifications to thestandard rules are lost. We therefore recommend that you keep a backup of any modified rules.

Connecting M3 to Infor IONA connection point must be set up for M3 so that it can send documents to ION.

Optionally, you can then set up and activate a document flow between connection points.

Understanding connection points and document flowsYou create connection points in ION Desk. Connection points provide the information that ION usesto connect to a product's message inbox and outbox. At least one connection point must be definedfor each product instance that integrates to ION.

For each connection point, you select the BOD documents that can be sent or received by the applicationinstance. These correspond to the BODs that are listed in BODs used in integrations with M3 on page107.

In an integration between two BOD-enabled applications, document flows are set up to define theBODs that flow between the application connection points.

A connection point can be reused multiple times in multiple document flows. You can also createconnection points during the modeling of a document flow in the details section of the document flowelements. The connection points that are created during the modeling of a flow are added to the sharedlist of connection points, and they can be reused.

Some integrations with Infor M3 use a solution XML file to set up sample connection points and documentflows. This file can be imported to ION to provide the basis for connection points and document flows.

See "ION Connect Modeling" in the Infor ION Desk User Guide for additional information aboutconnection points and document flows.



Creating a connection pointCreate a connection point for each instance of the application.

Note: Connection points are not activated separately. When you activate a document flow, the associatedconnection points are activated.

1 In ION Desk, select Model > Connect > Connection Points. A list of existing connection pointsis shown.

2 Click Add and specify Infor Application as connection type.


NameSpecify a name for this application instance.

Logical IDThe logical ID is concatenated from the values for name and logical ID type.See Setting up logical IDs, tenants, accounting entities, and locations in M3 on page 37.

TenantDo not specify a tenant. The connection point uses the default value Infor.

Logical ID TypeSpecify M3 as the type to construct the middle part of the logical ID.For example, if the logical ID type is M3 and the name is M3354_750 then the logical ID is:lid://Infor.M3.M3354_750. The logical ID type must contain alphanumeric characters, anunderscore (_) or a hyphen (-). Do not include capital letters or spaces.

Database TypeSpecify the database type, for example, SQLSERVER.

DatabaseSelect one of these configurations for the database address:• Basic: Specify properties for the database. The properties that you specify depend on the

database type that you selected. The URL to connect to the database is built automatically.• Advanced: Specify the URL to connect to the database. Use this option if you require settings

that are not available with the Basic option.

Host NameSpecify the host name of the server that hosts the database. This field is enabled if the Basiccheck box is selected.

Port NumberSpecify the number of the port that is used to connect to the database. This field is enabled if theBasic check box is selected.

Schema NameSpecify the name of the database schema. This field is enabled if the Basic check box is selectedand the Database Type is SQLSERVER, DB2 or DB2_400.



URL• If you selected the Advanced configuration for the database address, specify the URL of the

database that contains the message inbox and outbox tables. The URL depends on theconnected database type.

• If you select the Basic configuration for the database address, the URL is read-only.

User Name and PasswordSpecify the user name and password to connect to the database. If you use SQL Server withWindows authentication, specify a valid Windows domain user name instead of a SQL Serveruser name.

4 In the Polling section, set Delete Processed Messages to true to immediately delete BODs fromthe M3 message outbox area after ION processes them. Set the value to false to leave theprocessed BODs in the message outbox for the number of minutes that are specified in the OutboxCleaner Expire Time field.

5 Click Test to check if the connection is working. A message indicates whether the test wassuccessful. If the test failed, correct the connection details and try again.

6 Save the connection point.

7 Click Back to return to the list. Connection points are not activated separately. When you activatea document flow, the associated connection points are activated.

Defining application documents for the connection point1 In ION Desk, select Model > Connect > Connection points.

2 Select an M3 connection point and click Details.

3 Click the Documents tab of your M3 connection point. Select all the documents that can be sentor received by this application instance for any integration. For each document, specify whether itcan be sent, received, or both.

See the list of inbound and outbound documents in BODs used in Infor M3 integrations. The listof documents that you define for this connection point must match that list.

4 To add a document type, click Add Document. You can filter the list of documents by specifyingyour selection criteria in the Filter field or you can use these buttons:

DescriptionButton

Show standard documentsStandard

Show standard documents that are customizedExtended

Show custom documentCustom

5 To add verbs for a document type, select the document and click Add Verbs. The documents andverbs are selected from the ION registry.

6 To remove a document or verb, select the item and click Remove. When you remove a documentor verb that is used in a document flow, an error is reported in the messages pane of the documentflow.



Configuring a document flow between applicationsUsually, document flows are configured and activated in conjunction with integrations between M3 andanother application. In that case, follow the steps in the appropriate integration guide. If you want tosend BODs to another ION-enabled application and the integration is not supported by Infor, see theInfor ION Desk User Guide for the steps to create a document flow.

Defining the document flowEach document flow has a start and an end point. With a new document flow, only the start point andend points are displayed. To add items to the flow, complete these steps:

1 In ION Desk, select Connect > Data Flows.

2 Click Add to create a document flow.

3 Select the application icon in the toolbox.

4 Click the line where the application must be added. Alternatively, drag the item from the toolboxto the line where it must be added. An activity box is added.

5 Click the activity to view or change the properties in the Application Activity Properties pane.

6 Click Add to add a connection point to the activity.

7 Repeat steps 3-5 to add another application and its connection point to the flow.

8 Click the document icon between the applications to define the documents that flow from the firstapplication to the second application.

9 Save the document flow.

10 To delete an item, right-click it and click Delete.

Activating the document flowA new or changed document flow can be used in Infor ION after it is activated. This section describeshow to activate a document flow.

Note: If you encounter problems during this setup, you must stop and restart the ION service.

1 In ION Desk, select Model > Connect > Document flows.

2 Select one or more document flows.

3 Click Activate.

4 If you receive a message that the activation was successful, click OK. Your changes are effectiveimmediately.

• If you receive a warning message, the model is activated.• If you receive an error message, the model cannot be activated.

See the Infor ION Desk User Guide. for information about activation errors.



Activating the Infor Ming.le message listenerYou must activate the Infor Ming.le message listener in order to view drillbacks from your applicationin Infor Ming.le.

1 In ION Desk, select Model > Connect > Message Listeners.

2 Click Activate to activate the Infor Ming.le message listener.

See the ION Desk User Guide for information about message listeners.

Adding users and distribution groupsSet up users and distribution groups in Infor Federation Services for M3 users who require access toION to view or update information or troubleshoot errors.

See the Infor ION Desk User Guide for information about adding ION Desk users and setting ION Deskauthorization levels.

See the Infor Federation Services Administration Guide and M3 Workflow and Alert Content Examplesfor Infor ION for information about configuring distribution groups.

Setting up business events and workflowsUse the Infor ION Desk User Guide to create and configure ION events, alerts and workflows.

See the M3 Workflow and Alert Content Examples for Infor ION Desk for examples of Infor ION Deskalerts and events that are available for M3.

Publishing BODsYou publish BODs so that ION can retrieve them from your message outbox. You can publish BODsfor general use by any product that subscribes to the BODs through Infor ION. After you perform aninitial data load from M3, you verify that data is flowing out of the application into ION. For details abouta specific integration, see the appropriate integration guide.

For an ION-based integration between this application and another application, see the appropriateintegration guide for these instructions:

• Setting up the document flows• Performing any additional configuration of the applications that is required for that integration

You can then use the steps in the integration guide to publish the BODs.



Starting applications and servicesStart these applications, services, and processes:

• M3• Other applications that you communicate with through Infor ION:

• M3 BOD Processor• EC server• Event Hub• Event Analytics• Relevant BOD rule sessions and enabled rules

• ION Service. Use the ION Grid management user interface to verify that• ION Service is running. See the Infor ION Grid Administration Guide.

Sending the initial data loadDuring normal processing, BODs are published when a user changes data or completes a transaction.However, when you start a new integration with another application, you must manually generate BODsthat pass the current set of data from M3 to the other application, so that the base systems aresynchronized. The BODs are placed in the message outbox, from which Infor ION retrieves them andpasses them to the other application.

To perform the initial load of M3 data into the BODs that are placed in the message outbox:

1 Take note of the name of the master table for the applicable BOD. See Master tables for initial loadon page 113.

2 In M3, open ‘Initial Load.Start’ (EVS005).

If Smart Office is used, then specify MFORMS://EVS005, else specify EVS005. The H5 client isthe assumed user interface.

3 In Table, specify the master table name, for example MITMAS, to triggerM3BE_Out_ShowItemMaster.

4 In Division, specify the division of the events if applicable. Note that the Division parameter onlyworks if the Division field (DIVI) is a field in the primary key of the table that is specified inTable.

5 Optionally, in From date and To date, specify the registration date range for the data that is to betriggered.

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 initialload.

6 Leave the Max no. lines, Search query and Key field fields blank. They are not applicable whensending initial data. Click Next.Note: For testing purposes, you can limit the number of lines. In the live initial-load scenario, leavethe field blank to obtain the full amount of data.

The M3BE_Out_Show[Noun Mapping] BOD is triggered.



After the initial data load, M3 sends BOD updates when users change certain data or when certaintransactions occur in M3.

For a list of the events that generate BODs, see Business events that generate outbound BODson page 96.

M3 BOD dependenciesThe outbound initial load for Customer-, BillTo-, PayFrom- and ShipToPartyMaster must be carried outin a certain sequence. This is because the BODs refer to each other:

• BillToPartyMaster refers to CustomerPartyMaster• PayFromPartyMaster refers to BillToPartyMaster• ShipToPartyMaster refers to CustomerPartyMaster

This is the correct sequence for sending the initial load:

1 CustomerPartyMaster (table OCUSMA)2 BillToPartyMaster (table OCUSMA)3 PayFromPartyMaster (table OCUSMA)4 ShipToPartyMaster (table OCUSAD)

Sending the initial load of M3 BODs with dependenciesSend the initial load of the M3 BODs that has dependencies according to these steps:

1 Enable only the OCUSMA_REQUEST_CustomerPartyMaster rule in the M3BEBODs_InitialLoadrules session in EventAnalytics. Ensure to disable the other OCUSMA_REQUEST andOCUSAD_REQUEST rules.

2 Run EVS005 for OCUSMA and verify that all ShowCustomerPartyMaster rules have been receivedin the Send to-system as required.

3 Enable only the OCUSMA_REQUEST_BillToPartyMaster rule in the M3BEBODs_InitialLoad rulessession in EventAnalytics. Ensure to disable the other OCUSMA_REQUEST andOCUSAD_REQUEST rules.

4 Run EVS005 for OCUSMA and verify that all ShowBillToPartyMaster BODs have been receivedin the Send to-system as required.

5 Enable only the OCUSMA_REQUEST_PayFromPartyMaster rule in the M3BEBODs_InitialLoadrules session in EventAnalytics. Disable the other OCUSMA_REQUEST and OCUSAD_REQUESTrules.

6 Run EVS005 for OCUSMA and verify that all ShowPayFromPartyMaster BODs have been receivedin the Send to-system as required.

7 Enable only the OCUSMA_REQUEST_ShipToPartyMaster rule in the M3BEBODs_InitialLoadrules session in EventAnalytics. Disable the other OCUSMA_REQUEST and OCUSAD_REQUESTrules.

8 Run EVS005 for OCUSMA and verify that all ShowShipToPartyMaster BODs have been receivedin the Send to-system as required.



9 Enable only the OCUSAD_REQUEST_CustomerPartyMaster rule in the M3BEBODs_InitialLoadrules session in EventAnalytics. Disable the OCUSMA_REQUEST rules.

10 Run EVS005 for OCUSAD and verify that all ShowShipToPartyMaster BODs have been receivedin the Send to-system as required.

Note: This only applies to integrations that use one or more of the Customer-, BillTo-, PayFrom-and ShipToPartyMaster. See the details in the specific integration guides.

Verifying the ION configurationVerify that the connections are set up correctly.

Verifying that BODs are generated1 Determine what user actions generate certain BODs. See Business events that generate outbound

BODs on page 96.

2 Perform those user actions in M3.

3 In ION Desk, review the messages by using OneView or other ION Desk functions.

If messages are not displayed in ION Desk, check the message outbox in M3 to see if the BODshave been generated but not retrieved by ION.

4 If messages are not flowing, review the XML data for the BOD.

Verifying that ION receives dataTo verify that ION receives BODs from M3, perform these actions in ION Desk:

• Select Manage > Connect > Active Connection Points to show the message queue counts.• Select Manage > OneView to show individual messages when they are enabled.• Select Manage > Connect > Error BODs to see if any errors were reported.

If you encounter problems, see Data is not flowing properly on page 80.

Verifying the data flow between applicationsAfter you have created and activated document flows to other applications, check the message inboxarea of the other applications to ensure that data is flowing between the applications.



Chapter 9: Configuring workflows and ION messagesfor M3

You can configure workflows and ION messages for M3. Example workflows are provided.

ION messagesThis table shows the types of ION messages:

DescriptionType

BODs are published by applications when business events occur. In Infor ION DeskEvent Management, you can monitor business events and create alerts when ex-ceptions occur. BODs are published by applications when business events occur.Monitors are processes that run in the Event Management engine and evaluatethese BODs by applying predefined business rules: comparison conditions, valuechange conditions, and document overdue timer based rules.

When exceptions are detected, these are reported as alerts to the business users.The distribution list of alerts is included in the monitor definition. Users can receivealerts on their homepages or by email.

Alert

A task is a workflow step that creates an entry in a user's task list. The workflowstops until the user has completed the task, and then the next step in the workflowbegins.

Task

A notification is a workflow step that creates a notification in the user’s task list. Theworkflow continues after the notification is sent to a user. You can configure notifi-cations to perform these actions:

• Send a message to inform the user that a certain point in the workflow has beenreached.

• Optionally, include notes from previous steps.• Display workflow parameters and structures.

You can define a distribution list for notifications.

Notification


Configuring workflows and ION messages for M3

DescriptionType

An alarm is a monitor that is used in the ION Alarms mobile application.

M3 provides predefined alarm templates. In Infor ION Desk, the business adminis-trator can also create alarm templates.

After the templates are activated, mobile users can use the templates to createalarms in the ION Alarms mobile application for Android devices. The alarm creatorcan specify the distribution list for the resulting alert. See the Infor ION Desk AlarmsMobile Application User Guide.

The users receive the alert on their Infor Ming.le page, in the Infor Ming.le mobileapplication, or by email.

Alarm

Customizing M3 monitors and workflowsThe content pack includes standard definitions of content that is already available in the Ming.le registry.To install the M3 content pack for Infor OS deliverables, complete these steps:

1 Download M3 content pack for Infor OS from the download center and extract the files in M3 contentpack for ION [version].zip.

2 Create distribution groups in IFS and assign users to the groups.

You can either create them manually or use the file m3be_distribution_groups.csv to upload standarddistribution groups to IFS.

Caution: If you decide to use m3be_distribution_groups.csv, you must manually add this headerline in the .csv file before uploading it:

Name,Description

For a list of the required distribution groups, see Distributing alerts and tasks on page 63.

For more information about setting up distribution groups, see the Infor OS Administration Guide.

3 Customize and upload monitors to ION Desk:

a Edit each applicable monitor in m3be_monitors.xml to customize the conditions, alertsettings and messages for your business operations. Modify Conditions to specify the conditionsthat enable this monitor, modify Alert settings to specify the user or user group that should getthis notification and the message that should be displayed in the notification.

b Open ION Desk. Select Model > Monitors & Workflows > Monitors.c Click Import. Browse and open the m3be_monitors.xml file to import the customized

monitors.d Activate the required monitors.

4 Customize and upload workflows to ION Desk:

a Edit each applicable workflow in m3be_workflows.xml to customize the task message andthe distribution for your business operations. Modify Task settings to specify the user or usergroup that should get this notification, and the task message that should be sent.

b Open ION Desk. Select Model > Monitors & Workflows > Workflows.



c Click Import. Browse and open the 3be_workflows.xml file to import the customizedworkflows.

d Activate the required workflows.

5 Customize and upload activation policies to ION Desk:

a Edit each applicable activation policy in m3be_activationpolicies.xml to customize theconditions for enabling the activation policy for your business operations.

b Open ION Desk. SelectModel > Monitors & Workflows > Activation Policies.c Click Import. Browse and open the be_activationpolicies.xml file to import the

customized activation policies.d Activate the required activation policies.

6 Check the logical ID in Infor Ming.le.

a Select Admin settings from the user menu.b In Manage Applications, double-click Infor M3.c Select Application Details > Deployment Method. Verify that the logical ID corresponds to

the logical ID that has been specified in ION Desk > Manage > Connect > Active ConnectionPoints.

Configuring M3 to process alertsTo configure business rules, monitors are defined in ION Desk. A monitor contains a business rule,which consists of one or more conditions. After activation, at runtime, a monitor verifies incomingdocuments against its business rule.

1 Configure monitors to send alerts.

a Ensure that there is a valid event subscription in the event hub that is corresponding to eachalert.

b For each event-based alert, ensure that these settings are configured in 'Event Based Alerts.Open' (CMS047):

Event publisherSpecify M3.

Event name

Specify the table as the event name if it does not exist in the subscription.

Event operatorSpecify C (Create) or U (Update).

Alert rule IDAn alert rule ID only must be defined if more than one event name is used.

StatusSpecify 20 (Approved).




Logical formulaAs specified in the conditions.

If an alert is created or modified in 'Event Based Alerts. Open' (CMS047), the CMS911 autojobmust be restarted in 'Subsystem. Open' (MNS050). For more information, see NCR 6073.

c Configure the tenant.

Monitors, activation policies, and workflows can be configured to be filtered by tenant. M3standard monitors, activation policies, and workflows require you to use a tenant, and the M3content pack for Infor OS comes with a default tenant that is set to infor.

The tenant value in monitors, activation policies, and workflows must match the tenant that isused in your integration, that is the tenant that is used in the BODs and the connection pointof the M3 application.

d Configure the accounting entity.

M3 Business Engine stores part of its master data at the enterprise level. When publishing thismaster data through BODs, the data must be generated at the accounting entity level, whichis equivalent to the M3 Business Engine division. Changes to master data on enterprise levelwill generate one BOD per division in this enterprise. To prevent an alert or task from beingreceived for the same master data for each division, you can configure monitors and workflowmodels so that they are only triggered for a particular accounting unit.

Open a monitor or an activation policy. It must be deactivated to allow changes.

e On the Conditions tab, add or change an expression that uses AccountingEntityID and set theappropriate value.

Example: AccountingEntityID = 001_AAA

2 Configure ION to process alerts from M3. In ION Desk, import m3_monitors.xml.

See the ION Desk User Guide.

3 Configure Infor Infor Ming.le to display alerts for M3. Set up Infor Ming.le users with the appropriateroles to access tasks and alerts.

See the information about configuring user access for tasks and alerts in the ION Desk User Guide.

Example: Creating a customer invoice overdue alertThis example describes an alert configuration in 'Event Based Alerts. Open' (CMS047). These settingsare required to create a customer invoice overdue warning, in addition to the general settings, underConfiguring M3 to process alerts on page 58. The purpose of this configuration is to alert a user whena customer invoice is already due.

For the full set of alert-specific descriptions, see M3 Workflow and Alert Content Examples for InforOperating Service.

1 Open CMS047.



2 Speficy FSLEDG as Event name and click Create.


Alert rule IDDue date

DescriptionM3 Customer Invoice Due Date.

NameCustomerInvoice

Condition[LMDT] is greater than [DUDT]

Alert messageCustomer Invoice number <CINO> is overdue

FieldRESP

Option5

Opening panelE

Configuring M3 to process workflows for tasks andnotifications1 Configure M3 to send tasks and notifications.

a Ensure that there are valid event subscriptions in Event Hub that are corresponding to eachworkflow. See "Event Handling" in the User Documentation Infocenter (UDI) documentation.

b For each event-based workflow, configure these settings in 'Event Based Alerts.Open'(CMS047).

Event publisherSpecify M3.

Event name

Specify the table as the event name if it does not exist in the subscription.

Event operationSpecify C-Create or U-Update.

Alert rule IDIf applicable, specify only when more than one event name is used.



StatusSpecify 20-Approved.

BOD enabledSelect the checkbox.

Logical formulaAs specified in the conditions.

Each workflow configuration also describes the purpose of the workflow, the event name, alertrule ID, description, logical formula, alert message, and field or receiver. See Example: Budgetcreated on page 61 for an example of a workflow description.

If a workflow is created or modified in 'Event Based Alerts. Open' (CMS047), the CMS911autojob must be restarted in 'Subsystem. Open' (MNS050). For more information, see NCR6073.

c Configure the tenant.

Monitors, activation policies, and workflows can be configured to be filtered by tenant. M3standard monitors, activation policies, and workflows require you to use a tenant, and the M3content pack for Infor OS comes with a default tenant that is set to infor.

The tenant value in monitors, activation policies, and workflows must match the tenant that isused in your integration, that is the tenant that is used in the BODs and the connection pointof the M3 application.

d Configure the accounting entity.

M3 Business Engine stores part of its master data at the enterprise level. When publishing thismaster data through BODs, the data must be generated at the accounting entity level, whichis equivalent to the M3 Business Engine division. Changes to master data on enterprise levelwill generate one BOD per division in this enterprise. To prevent an alert or task from beingreceived for the same master data for each division, you can configure monitors and workflowmodels so that they are only triggered for a particular accounting unit.

Open a monitor or an activation policy. It must be deactivated to allow changes.

e On the Conditions tab, add or change an expression that uses AccountingEntityID and set theappropriate value.

Example: AccountingEntityID = 001_AAA

2 Configure ION to process tasks and notifications from M3.

See the ION Desk User Guide.

3 Configure Infor Ming.le to display tasks and notifications for M3.

Example: Budget createdThis example describes a workflow configuration in 'Event Based Alerts. Open' (CMS047). Thesesettings, in addition to the general settings in Configuring M3 to process alerts on page 58, are requiredto create a task when a budget is created. The purpose of this configuration is to alert a user when acustomer invoice is already due.



For the full set of workflow-specific descriptions, see theM3 Workflow and Alert Content Examples forInfor OS.

1 Open CMS047.

2 Speficy FBUDEF as Event name and click Create.


Event operationSpecify C-Create.

Alert rule IDNone.

DescriptionM3BE Budget is created.

NameBudget

ConditionNumeric field NPAM is less than or equals 12.

Alert message

Budget number <BUNO> Budget version <BVER> is created.

FieldRESP

Option5

Opening panelE

Workflow sample content for M3This section provides information about the event monitors and workflow models that have been createdfor BODs that are published by M3. It is intended mainly for system administrators who manage andcustomize standard ERP ION content, or who must troubleshoot or trace back tasks or alerts to theERP.

Recommendations are given on how to customize the standard ION content to suit your businessneeds. We recommend that you discuss the process and results of your planning decisions with InforConsulting Services prior to implementation.

If you plan to create custom tasks, workflows, or alerts that are generated from M3 to run in Infor IONDesk and Infor Ming.le, see the Infor ION Desk Development Guide.



Setup and configurationThis section describes how to install the M3 ION workflow example content. It also describes thecustomization process.

See "Event Handling" in the User Documentation Infocenter (UDI) documentation for information aboutusing the workflow examples after they are installed and configured.

RequirementsTo use the M3 ION workflow example content, at least one document flow must be activated for theM3 connection point. The solution XMLs that are provided for specific integrations of other productswith M3 contain a document flow with a single application for the M3 connection point. You can selectmultiple connection points in the document flow. If a monitor or activation policy is activated, subscriptionsare created for each active M3 connection point. See the Infor ION Desk User Guide for more information.

Distributing alerts and tasksMonitors in ION create alerts, and workflow models create tasks. These alerts and tasks can bedistributed to individual users, groups of users, or to persons who are defined in the BODs. The standardM3 ION monitors and workflow models use distribution groups and persons who are defined in theBODs, whereas event-based alerts and workflow tasks are distributed to the field or receiver that isspecified in the M3 Business Engine settings.

The distribution groups are configured in Infor Ming.le, and you can change the distribution groupswithout having to change monitors or workflow models. These distribution groups are used in thestandard M3 content:

• M3BE_Finance• M3BE_Maintenance• M3BE_Purchase• M3BE_Sales• M3BE_Warehousing

Each distribution group should include at least one user.

For the distribution of alerts and tasks to work, the user ID of the M3 Business Engine in MNS150 mustmatch the IFS ION-Person ID value that is specified in Infor Ming. le > User Management.

Updating M3 content for IONUse ION Desk to copy and adjust standard content. Updates do not overwrite imported content. Whenyou import a monitor, workflow, or activation policy that already exists, you can either select Skip orCopy:



• If you select Skip, the import does not take place.• If you select Copy, the import takes place but the imported object is renamed and the existing

object is preserved.

To replace content, delete the standard content before importing a new M3 content pack.

Configuring the M3 workflow exit pointThis section describes how you configure M3 WorkFlow Ex. M3 WorkFlowEx is a grid applicationdelivered with M3 Business Engine BODs. See the M3 Configuration Guide for ION for installationinstructions.

The purpose of M3WorkFlowEx is to offer an interface to M3 API functions for access from the IONworkflow. The interface can be used to retrieve information and add or change information in M3. Dueto restrictions in the workflow engine, only single record information can be retrieved. It is not possibleto retrieve a list of records.

Configuring workflow exit point properties in ION DeskTo interact with M3 Business Engine, you must define a workflow exit point in the ION Desk WorkFlowModeler. M3 WorkFlowEx is based on a web service. You must therefore specify a URL to the webservice description file. You must also specify the API and the transaction to be processed in the exitpoint properties.

Specifying the web service URLThe URL for M3WorkFlowEx consists of the host name and the port of the installed application:http://<hostname>:<port>/M3WF/ExternalLogicExecuter?wsdl

You can copy the URL from the topology view in the grid management pages:

1 Open the grid management pages for the grid in which your M3 Business Engine is running.

2 Expand the default router node.

3 Click the port for the applicable protocol, SYSTEM.HTTP:[PORT] or SYSTEM.HTTPS:[PORT].

Note: Click the port number to access the context roots list. The protocol parts link points to theconnection dispatchers.

4 From the Context Roots table, select M3FWorkFlowEx and click the Web Service link.

5 Copy the link and paste it into the ION Desk Exit Point properties.

6 Click Validate to ensure that the communication is working.



Specifying API transactions1 In Command, specify an API transaction, for example CRS111MI.Get.

2 Specify parameters, such as EMTP for E-mail type or EMKY for email key value.

The API transactions usually require one or more parameters. These are defined in the ION workflowas variables that are mapped to fields in the transactions. The API transactions return data in theform of fields, and they are also mapped to corresponding variable names in ION. API transactionfield names are four letters long and must be specified in uppercase.

A field name can be used in both an inbound and outbound transaction. You must define thevariable only once in the workflow properties.

Handling errorsThe interaction with M3 Business Engine can fail for various reasons. To report an error to Infor IONWorkflow & Events, you must define a specific variable.

1 Define a variable called FAIL that returns an empty value if everything was successful or returnsan error message in plain text.

2 To check whether the interaction with the M3 Business Engine was successful, create a Decisionworkflow that checks the FAIL variable and reacts to the result.

3 In Decision Properties, specify: this information:

User ConditionIncaseofproblem

NameIncaseofproblem

Expression[FAIL] <> "

Configuring the M3 default settings for usersM3 Business Engine interaction requires that a user profile is specified. The settings for this userdetermine which databases are accessible, which company and division are used, etc.

M3WorkFlowEx can work in two different modes:

• A single, common user is defined. The settings for this user determine the interaction. The user isregistered for operations that update the database.

• Alternatively, M3WorkFlowEx can be configured to require a sign-in. In this case, the settings ofthe user apply.

This M3WorkFlowEx property is named ForceLogon and can be true, false, or undefined, that isfalse.



If M3WorkFlowEx is configured to require a sign-in, basic sign-in information must be set up forthe exit point on the Connection Settings tab.

ION workflow does not currently support dynamic user interaction, that is, when the current userexecutes the workflow or displaying a sign-in screen. It can be used, however, as a means to supportdifferent users running different workflows.

Note: When ForceLogon is enabled (true) in M3WorkFlowEx, a basic authentication must be specifiedin the connection settings. Error messages can be accessed in the ION Desk log file ProcessWorkflow.log.



Chapter 10: Configuring ION APIs for M3

To enable Infor Ming.le functionality such as homepages, the M3 API metadata is provided as an APISuite.

Creating an API suite for M3You must meet these conditions:

• Ensure that the user who creates the M3 API suite in ION API has the IONAPI-AdministratorIFS Security Role.

• Create a P12 client keystore with the grid-run-as-user role.• Identify the applicable router host name and HTTPS port by opening the Topology view in the ION

Grid Management Pages and locate a router that publishes an M3 Business Engine application.• Ensure that impersonation and an applicable HTTPS authentication type is enabled for the applicable

router:• Navigate to Grid Management Pages > Configuration Manager > Communication > Routers.• Verify that Enable impersonation is selected for the applicable router.• Ensure that HTTPS Authentication Type is set to either Clients may authenticate

with certificate or Clients must authenticate with certificate for theapplicable router.

1 Open the ION API administration interface in Infor Ming.le.

2 Click Add New API Suite.

3 Specify these values:

Infor Non-provisioned

Select this option.

Application Name

Specify Infor M3.

Version

Select the applicable M3 version.

Suite NameSpecify M3.


Configuring ION APIs for M3

API ContextAccept the default value.

Use HTTPSSelect this option.

Host NameSpecify the applicable router host name.

PortSpecify the HTTPS port according to SYSTEM.HTTPS:[PORT].

ContextLeave this field as is.

4 In Target Endpoint Security, specify this information:

User Mutal SSL

Select this option.

Key Password

Specify the password for the client keystore and click Load Certificate.

Navigate to the applicable keystore and click Open.

Authentication Type

Select Anonymous.

5 Click Save.


Configuring ION APIs for M3

Chapter 11: Configuring drillbacks to M3

The standard drillback definitions for M3 BODs are located in the Infor Ming.le registry. The drillbackdefinition xml is also included in the content pack. It can be used as a template for modifications. Asan administrator, you can modify or add drillbacks to replace the standard definition by editing anduploading the drillback definition xml that is provided in the M3 content pack for Infor OS.

About drillbacksInfor Ming.le users can share screens and business data in some ION-enabled applications that areintegrated with M3. The screens and business data can include embedded drillback links to M3. If ascreen or business data is associated with a Business Object Document (BOD) that was sent fromM3, and the screen or data has an associated drillback link, then users can click the link to view thescreen that has the supporting information for the source transactions.

A drillback link can be defined for each type of BOD noun, for example SalesOrder or ItemMaster. Thelink is configured to open a specific screen for that noun. Not every BOD noun has an associateddrillback view in M3.

Applications can also drill to M3 Business Engine without receiving a BOD before. For example, anapplication can drill to a function in M3 Business Engine to view detailed item data. The M3 H5 clientsupports Drill to both through Infor Ming.le and, when running the H5 client, in standalone mode.

The drill-to format that is used when running the H5 client in Infor Ming.le must match the format thatis used for drillbacks in Infor Ming.le. If a drill-to scenario is used for a standalone H5 client, the M3bookmark format must be used. For examples of the format of drillbacks used in Infor Ming.le, see thedrillback definition in the M3 content. For information about the M3 bookmark format, refer to the InforSmart Office or H5 client documentation.

Drill back and Drill to consideration

The user profile in M3 Business Engine specifies a default company and division. When a user signsin to M3 Business Engine, they sign in to their default company/division. After a user has signed in tohis default company/division, they can switch to any company/division they have access to.

Both Drill back and Drill to, however, require that the user is signed in to M3 Business Engine with thesame company and division that the Drill back/Drill to operation is opening. If this is not the case, anerror message is displayed in the M3 UI, asking the user to sign in to the correct company and division.A similar situation occurs if the user is not authorized to access the requested function, screen, or


Configuring drillbacks to M3

record that the Drill back or Drill to is trying to open. If the user is not authorized, an error message isdisplayed.

Importing and configuring application drillbacksTo enable Infor Ming.le users to open applicable screens in M3 directly from an Infor Ming.le object,you must import an XML document to create the mapping from the object type to the appropriate M3form.

1 Download the the m3be_drillback_definition.xml.xml file, which is included in the M3Content Pack for Infor OS, from the Infor product download center.

2 In Infor Ming.le, go to the Manage Drillbacks page.

See the Infor OS Administration Guide.

3 Click Upload Drillback XML to open a file browser and select the m3be_drillback_definition.xml file, which contains the drillback views.

Note: The M3 connection point must be included in an activated ION document flow. The datafrom the documents in the activated flow is available to Infor Ming.le for use in drillbacks to M3.

Available drillbacks"Drillback" refers to the ability of starting an M3 page in Infor Ming.le through a link that is based onthe document ID or other relevant information for the respective BOD.

The drillback is displayed as a link in an task, alert or social object. This link can be used to start anM3 program from the Infor Ming.le feed.

Not all nouns have a drillback view available.

Translating the accounting entityBy default, the accounting entity is set to CONO_DIVI, for example 780_AAA. To support drillbacks inInfor Ming.le, the accounting entity must be formatted according to the default setting, that is as acompany number, followed by an underscore followed by the division.

The accounting entity in M3 Business Engine can be translated using 'Business Message DataTranslation. Display' (CRS881).

Caution: If you translate the accounting entity to anything other than CONO_DIVI, for example780_AAA, the drillback links will be corrupted.



See Specifying or editing translation data on page 37 for information on managing translations ofaccounting entities.

Verifying a drillbackDrillbacks are displayed in Infor Ming.le as links. Each link opens a specific screen, filtered for specificresults. For example, an Infor Ming.le search result, alert, or share can include a link to the form witha reference to specific M3 data.

To verify that the drillbacks are working:

1 In Infor Ming.le, click Infor M3.

2 Press Ctrl+R and specify, for example, CRS610 to open the 'Customer. Open' (CRS610)form.

Note: The user interface does not indicate whether a screen has a drillback. For a screen to receivea drillback, a drillback must be configured and a business context message sent.

3 Click the Share icon in Infor M3 and verify that the message is populated with the appropriatemetadata.

4 In the Share window, verify that the drillback icon is displayed, add a comment, and click Share.

5 In the Infor Ming.le feed, find the message that contains the drillback icon, and click the drillbackto verify that it is working.



Chapter 12: Configuring context apps and utility appsthat are used with M3

On the right side of the Infor Ming.le page is a collapsible panel that hosts several Infor Infor Ming.lecontext and utility applications.

Context apps are lightweight applications that communicate with the application frame to presentcontextual information to the user. These applications subscribe to information that is published by theapplication frame and display relevant content only when it is available. The values and content of theapplication depend on the current context that is shown in the product application panel in Infor InforMing.le.

Utility apps are lightweight applications that show information unrelated to content in the application.They do not communicate with the application frame and, if activated, are shown when the applicationis open.

Understanding business context messagesA business context message is a JSON message that is sent from an M3 screen, field, or anotherinterface object to establish the current context. These messages can be used for many contextualpurposes within Infor Ming.le, as well as for drillbacks.

M3 uses business context messages to display online help and to determine the metrics and reportsthat are displayed in the In-Context Infor d/EPM application when a certain M3 screen is displayed.For more information about the available metrics and reports, see the M3 Analytics documentation.

To find the business context message that is sent by a specific object, use the Infor Ming. le ContextViewer application. See the Infor Ming.le User Guide.

Supported business context messagesM3 supports business context messages as described in "M3 H5 and Infor Ming.le" in the Infor M3 H5User Guide:

• Posting on feed page• Infor Business Context


Configuring context apps and utility apps that are used with M3

• Mashup context

Context and utility applications that work with M3The standard context and utility apps page lists all of the default context and utility apps and othercontext and utility apps that you have added. From this page, you can add and view context and utilityapp details. These standard context and utility apps are available by default for use with M3:

• Tasks utility application and homepages widget• Alerts utility application and homepages widget• Posts• Paparazzi• Share from the Infor Ming.le shell• Social objects• Drillbacks• Metrics• Infor Federation Services - Single Sign On• In-Context Business Intelligence• Documentation• Related Information

For information about how to use the standard apps, see the Infor Ming.le online help.

M3 does not include any additional context applications.

Enabling a context or utility app for your applicationYou can add a context or utility app to M3 if it is not set up as a default. See the information aboutadding context apps or utility apps in the Infor OS Administration Guide. Either select Grant accessto all users or click Add new users and/or IFS security roles to specify certain users or roles in M3that can access this context app.


Configuring context apps and utility apps that are used with M3

Chapter 13: Configuring homepages for M3

Homepages are a flexible and configurable way to present information and activities to users.Administrators can build pages for various groups of users, roles, departments, or business functions.You can select from the library of available Infor widgets or build your own widgets.

For homepages administration tasks, see the Infor OS Administration Guide.

Importing predefined homepagesThe M3 Homepage templates provide a framework for various roles and scenarios by presenting acollection of information from various systems through configured M3 widgets. In addition to M3 BusinessEngine data, M3 widgets also use information from applications such as Infor Enterprise Search andInfor M3 Analytics.

1 Download the M3 content pack for Infor OS from the download center to a local drive and locateM3_Homepages_Templates_v[x.x].zip.

2 Import M3_Homepages_Templates_v[x.x].zip. See "Importing homepages data" in the InforOS Administration Guide.

3 Copy the template homepage that best suites your requirements.

4 Rename the file.

Caution: The content of the M3 Homepage templates is updated automatically without notice.Therefore, you must create, rename and modify a copy of the template instead of using the originalhomepage template.

5 Configure the M3 widgets to customize your homepage to your current business operations.

6 Publish the new homepage according to the instructions in the Infor OS Administration Guide.

Verifying the homepage and widget contentTo verify the homepage and widget content:

1 Sign in to Infor Ming.le as a non-administrative user who has access to both Infor Ming.le and M3.

2 Complete these steps:


Configuring homepages for M3

a Create a homepage.b Ensure that you can use the widget catalog to add and view an M3 widget on the homepage.c Verify if you can use the page catalog to add and open an M3 homepage. You must be

authorized to open the homepage in the M3 application.d Drill down to M3 forms from the appropriate widgets.


Configuring homepages for M3

Chapter 14: Configuring Infor Document Managementwith M3

Infor Document Management (IDM) and M3 are integrated through these methods:

• ION API (REST enabled)• Context Business Messages• BOD nouns

The SyncCaptureDocument BOD is an outbound BOD that is sent by IDM when capturing differenttypes of documents, for example, scanned documents.

M3 creates documents in IDM by sending a ProcessContentDocument BOD. M3 receives updates todocuments within IDM by receiving SyncContentDocument BODs.

M3 delivers its own document models and set of links to the UI applications, if applicable.

Document models and links can be configured for a tenant.

Importing configurations and typesYou can import the default configuration and document types by using the Infor Document ManagementControl Center:

To obtain the M3-specific configurations and types, download the M3 content pack for Infor OS fromthe product download center and extract the IDM-specific files. In addition to the default M3-specificconfigurations and types, the package also contains folders for corresponding content to be importedto Microsoft Sharepoint (SP) or IBM DB2 Content Manager (CM) for Infor Document Managementinstallations using these products.

• To import the default M3 Business Engine-specific document types, use the Configuration Importer.• To enable the Related Information context app to show Infor Document Management documents,

import the M3 Business Context Model configurations. See the information about the businesscontext model in the Infor OS Administration Guide.

• To import the ION configuration, use the ION option. The ION configuration enables communicationbetween IDM and ION. You can also configure a specific ION workflow for a particular documenttype.

See the instructions in the Infor OS Administration Guide.


Configuring Infor Document Management with M3

Enabling the Related Information context appWhen you set up the Related Information context app in Infor Ming.le, use the Applications tab to addthe M3 application and set it to Enabled.


Configuring Infor Document Management with M3

Chapter 15: Configuring BI and Analytics content forM3

See the M3 Analytics documentation.


Configuring BI and Analytics content for M3

Chapter 16: Configuring Infor Localization Servicesfor use with M3

Localization Services Spanish Tax Authority Connector enables online VAT reporting for M3 CountryVersion Spain. See the M3 Country Version Spain Configuration Guide and the Localization ServicesSpanish Tax Authority Connector Installation Guide for details.


Configuring Infor Localization Services for use with M3

Appendix A: Troubleshooting

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

See M3 BOD architectural overview and data flow on page 20 for a flow diagram that shows the variousapplication components that are involved in handling BODs from M3 to ION and back.

Data is not flowing properlySolution: After you complete the configuration setup, if BOD data is not flowing to ION, use IONOneView to identify the problem.

ION OneView can be found under the Manage menu in Infor ION Desk. You can perform these actionsin ION OneView.

• Track business documents from a single consolidated view; search for documents using differentsearch criteria

• View all ION components that were triggered by the incoming document: ,; mappings; ION enginesfor example, Monitor, Workflow, and Pulse; monitors; activation policies and workflows.• Connection Points• Document flow filters and content-based routing• Mappings• ION engines, for example, Monitor, Workflow• Monitors• Activation policies and workflows

• View more details about these ION components:• Detailed 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 and correlation of the different messages sent or generated• Original BOD messages that triggered the whole list of components displayed:

• Confirmed BOD messages that were generated due to any error while processing theoriginal BOD message

• Mapped/Updated BOD messages that were created during the processing of the originalBOD message


Troubleshooting

• View content of BOD messages. This information is only available to authorized users, basedon the roles and permissions that are configured

For more information, see the section on ION OneView in the Infor ION Desk User Guide.

To avoid business discrepancies between M3 and integrated applications, correct any errors as soonpossible.

No BODs reach the target systemSolution: Complete these steps to verify the configuration.

1 In the Grid management pages for M3BODProcessor, verify that the applicable M3 company anddivisions are selected for BOD publishing.

2 Ensure that the system is installed correctly:

a Verify that all components and prerequisites described in Installing and configuring M3 BusinessEngine BOD content on page 40 have been installed and are running.

b Verify that the post installation tasks and configuration have been performed. In the InforEnterprise Collaborator Partner Administration tool, check whether the specified api-referenceis a valid user, and whether the user has the required access to companies and divisions inM3. See Importing M3BODs to Infor Enterprise Collaborator on page 42.

3 Check the Grid management pages for EventHub for those subscribers and publishers that arerequired for outbound BODs. You can also click Visualization to display a graphical representationof 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 tothe Grid management page for EventAnalytics and start the M3BEBODs_GenericCorrelationrules session.

b Click Event Hub > Subscriber > M3BODProcessor and verify that EventAnalytics is listedas a publisher.

c Click the subscribers value in Publishers > M3BODProcessor > Subscribers. Verify thatthese eleven receive channels for Infor Enterprise Collaborator are listed as subscribers toM3BODProcessor:

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


Troubleshooting

MEC-M3_In_M3BOD_TrnsDtaService_Ordered

MEC-M3_In_M3BOD_TrnsDtaSupplyChain_Ordered

d If these channels are missing from the subscriber list, open the Infor Enterprise CollaboratorPartner Administration tool. Go to Manage > Communication > Receive and ensure that thechannels 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 Collaborator Partner Administrationtool, but there are no subscriptions, open the management pages for EC_Server. Go toCommunication > Channel Control and click Reload All Channels to refresh the Event Hubsubscriptions.

4 In the Grid management pages for EventHub, check if any of the subscribers and publishers in theprevious step have an excessive amount of queued events.

If there is an unusually large amount of queued events, the subscriber of these events cannot keepup with the current workload that may result from a BOD publishing peak. If the queue does notdecrease over time, this may be due to the size of the component's hardware or a system error.

5 Open ION Desk.

a Review the settings of the application connection points. Click Test to verify the connectivityof the application connection point.

b Verify that the correct accounting entity is used by the sending system. This applies to inboundBODs.

c If the BOD is visible in OneView, but cannot be routed:• Verify that CRS881 contains a translation for tenantID to infor.• 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 pointcorresponds to the ionFromLogicalId group control property as displayed in EC_ServerGrid Management Pages > EC_Server > Group Control Properties.

No BODs reach the target system during the initialloadSolution: In addition to the actions described in No BODs reach the target system on page 81, usethis procedure to verify that the ionToLogicalId group control property is configured for the agreementgroup.

1 Open EC_Server Grid Management Pages > EC_Server > Group Control Properties.

2 Verify that the ionToLogicalId group control property is set on the initial load agreement group.


Troubleshooting

Some BODs do not reach the target systemSolution: 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. Checkif 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 document flow is configured correctly.

b If the BOD uses a custom noun, that is, an xsd not listed on schema.infor.com, verify that thecustom noun is uploaded to the ION registry by opening Settings > Registry > CustomDocuments.

c Verify the settings of the application connection point. Ensure that the connection point isconfigured to publish or consume the required BOD documents.

2 In Grid management pages:

a Verify that the EC_Server, EventAnalytics, EventHub, M3BE and M3BODProcessor applicationsare running and that their status is OK. Assess any errors or warnings.

b Verify that all the M3BE subsystems are running and that their status is OK. If applicable, assessthe logs for relevant errors and warnings.

3 In the Grid management pages of Event Analytics:

a Verify that the rules session for the BOD is started.b Verify that the M3BEBODs_GenericCorrelation rules session is started.

4 In the Grid management pages for EventHub, verify these subscribers and publishers, requiredfor outbound BODs. You can also click Visualization to display a graphical representation of thecurrent 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 tothe Grid management page for Eventanalytics and start the M3BEBODs_GenericCorrelationrules session.

b Click Event Hub > Subscriber > M3BODProcessor, and verify that EventAnalytics is listedas a publisher.

c Click the subscribers value in Publishers > M3BODProcessor > Subscribers. Verify thatthese eleven receive channels for Infor Enterprise Collaborator are listed as subscribers toM3BODProcessor:

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


Troubleshooting

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 the Infor Enterprise CollaboratorPartner Administration tool. Go to Manage > Communication > Receive and verify that thechannels 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 Administrationtool, but there are no subscriptions, open to the management pages for EC_Server. Go toCommunication > Channel Control and click Reload All Channels to refresh the Event Hubsubscriptions.

5 In the Grid management pages for EventHub, check if any of the subscribers and publishers in theprevious step have an excessive amount of queued events.

If there is an unusually large amount of queued events, the subscriber of these events cannot keepup with the current workload, which may result from a BOD publishing peak. If the queue does notdecrease over time, this may be due to the size of the component's hardware or a system error..

6 In the Grid management pages for EC_Server:

a Go to Server > Mappings and ensure that the BOD mapping exists and is in the Activestate.

b Go to Message > 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 twoqueues is unexpectedly large.If so, go to EC_Server > Messages and check for messages that are currently in the XMLTransform or Pending status. Investigate whether the messages are processed slowly or notat all. Examine the messages that stay active in more detail.

An increasing queue length can be caused by incorrect configuration or a lack of processingresources.


Troubleshooting

Appendix B: Infor ION BOD overview

This section provides an overview of the BODs. It explains how to define BODs and how to use someof the most common XML tags. This section also describes the BOD types that are used in Inforapplications.

BOD message structureInfor ION messages are called Business Object Documents (BODs). These messages are based onstandards that are developed by the Open Applications Group, Inc. (OAGi). BODs are XML documentsthat consist of a verb component and a noun component. The BOD name consists of a verb and anoun, for example, SyncPayableTransaction and ProcessLocation. A BOD XML includes these areas:

• Verbs specify the action performed on the noun, for example, Process or Sync.• Nouns specify the business-specific data, for example, PayableTransaction or Location.• Elements are the XML tags within the BOD that describe the data. They can be hierarchical, as

shown in this example:

<PaymentTerm><Description languageID="EN">2% in 10, Net Due in 30</Description><Term><ID>2/10N30</ID></Term></PaymentTerm>

• Attributes describe the elements. For example, UnitCode is the attribute in this element:

<Quantity UnitCode="EA">

• When a value in a BOD is constructed by concatenation of multiple values, an underscore (_)character is used to separate the values.

• Data that is not defined for a noun can be passed in the UserArea of a BOD. With Infor applications,the only element that can be placed in the UserArea is Property. Multiple instances of Propertywithin the UserArea can exist. Only the UserArea fields in the header, detail, and root of a nounare supported by Infor. If you require additional fields, you must define them in the UserArea.• Each Property element contains a NameValue element that holds the value being passed.

The NameValue element also contains these attributes:


Infor ION BOD overview

• @name holds the custom field name• @type specifies the data type of the value, for example, StringType and DateType• This example shows a UserArea:

<UserArea> <Property> <NameValue name=”MyField” type=”StringType”>Sample Data</NameValue> </Property></UserArea>

• The Document ID element is a unique identification of the represented business object. The ID isused in a BOD to reference other BODs. For the SalesOrder, PurchaseOrder, and CustomerReturnnouns, the ID is the order number. For other nouns, a naming convention is defined that makesthe ID unique.

• Party ID elements identify an external entity, such as a Customer, Supplier, and ShipTo. LocationID elements identify sites within the enterprise. Within a transactional BOD such as a Shipment,if the ShipToParty/PartyIDs/ID is populated, the ID points to a ShipToPartyMaster record. If theShipToParty/Location/ID is populated, the ID points to a warehouse or other site within the enterprise.

• Date and time elements within a BOD can be presented in different ways.• Dates and times that are system-defined, for example document dates, must always be

represented in UTC time format.

Example: 2011-08-13T15:30Z

• Dates and times that are specified by an operator for a single location, internal or external,should always be represented with a time zone offset.

Example: 2011-08-13T15:30+02:00

• Non-specific times are represented without a time zone indicator, for example 2011-08-13T15:30• Dates without time, for example 2011-08-13

System of recordA piece of information, for example a customer address, is maintained by only one system, which isthe system of record (SOR). The SOR publishes all changes for that piece of information to Infor IONthrough a Sync message. Other applications that want to add or update that piece of information mustmake a request to the system of record using a Process message.

The system of record does not necessarily know which applications require the information. The entirecontents of the document are published in the Sync message. All applications that subscribe to themessage receive a copy of the message from ION.



BOD verbsInfor uses these verbs:

• A Process message is a point-to-point message that is used to request a service from anotherapplication. The Process message is usually sent from a non-system of record to the system ofrecord (SOR). These action codes are supported:• Add: Requests that the other application create new document or record.• Change: Requests that the other application update an existing document or record. The

elements that have a change are required.

• An Acknowledge message is a response to the Process message. The Acknowledge messagenotifies the requesting system whether the request was accepted or rejected. In many cases, theAcknowledge verb has additional information, such as the document ID that is assigned by thesystem of record.

• A Sync message is a broadcast message that is published by the system of record. The Syncmessage is used to inform other applications about the latest information for the noun. It is publishedafter a business event causes a change in the data. These action codes are supported:• Add: Notifies other applications that a document or record has been created.• Replace: Notifies other applications that an existing document or record has been updated.

The entire document or record is included in the BOD. The current state of the document orrecord is also shown.

• A Get message is a point-to-point message that requests information about one or more documentsor records. When the GetInventoryCount BOD is sent, the inventory balance is requested for onlyone item. For all other Get requests, the application requests a copy of all documents from thesystem of record. A Get request for all documents is useful for an initial data load or a disasterrecovery.

• A Show message is a message that is sent directly to another application by the system of recordas a response to a Get message. A Show message can contain multiple records or documentswithin one message. Show messages are typically used to reinitialize an application and not forgeneral initialization.

• A Confirm message is used to notify users of an error condition. The ConfirmBOD is sent to InforION and can be viewed in ION Desk.

Note: The OAGIS Delete verb is supported by Infor for special tenant-level master data only. Otherwise,this verb is not supported. For auditing purposes, you should cancel documents and records and notdelete them.

Message deliveryWith the exception of the Show message, which is used for the initial data load process, Infor IONmessages are delivered asynchronously. Applications send only one document per message.



Data mappingInformation about how M3 database elements or calculations are mapped to specific BOD elementsis provided in these guides:

• M3 Outbound BOD Mappings and Descriptions: For each BOD that is supported by M3, thisdocument provides the source and definition of the data in each element that is sent or receivedthrough the integration. If the source that is used differs based on specific criteria within M3, thedocument also provides the details about the data that is published.

• M3 Inbound BOD Mappings and Descriptions: For each BOD that is supported by M3, this documentprovides the details about how each inbound BOD receives information or requests information.For example, the source might be an extension product, a result of a workflow, or a drillback functionfrom Infor Ming.le. If a BOD updates a M3 source table, the document defines the exceptions andhandling.

These guides are organized according to the elements in each BOD.

Note: Infor reserves the right to change BOD structures. Although Infor attempts to provide backwardcompatibility, custom integrations that are built on a specific version of a BOD might require modificationto be compatible with newer versions of Infor components.

Classification of BODsM3 BODs are classified according to two dimensions, data type and business area.

Data type:

• Balance data• Master data• Transaction data

Business area:

• Finance• Sales• Service• Supply chain• General

Currently this classification is only used in the naming of ordered Event Hub subscriber channels inInfor Enterprise Collaborator.

• MEC-M3_In_M3BOD_MstDtaFinance_Ordered MEC-M3_In_M3BOD_BlncDtaFinance_Ordered• MEC-M3_In_M3BOD_BlncDtaFinance_OrderedMEC-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



Appendix C: Ongoing maintenance

See the M3 Core Administration Guide.


Ongoing maintenance

Appendix D: M3 BOD overview

This section provides an overview of the M3 BOD solution.

Company and division in Infor Enterprise CollaboratorM3 BODs have a transparent handling of M3 company and division. The M3 BOD agreements in InforEnterprise Collaborator are independent of M3 company and division or accounting entity.

Generic agreements are applied for Outbound BODs, and the company and division are given in theevent that triggers the publishing of the BOD.

Inbound BODs also share generic agreements, as company and division is given by the accountingentity in the received BOD.

The BOD mappings and M3 API handling for M3 BOD agreements are set up to adapt to the M3company and division, or the accounting entity, which is given by the received message data.

M3 API reference settingsThe M3 settings function in BOD mappings is used to dynamically set the correct M3 company anddivision for the M3 API calls. Because only one API reference is used for all M3 companies and divisions,only one M3 user is used for M3 API calls for all M3 companies and divisions.

Note: Ensure that the user for the API reference is granted access to all companies and divisions thatare used in the BOD integrations.

M3 BOD agreementsThe M3 BOD agreement structure in Infor Enterprise Collaborator has been simplified. The agreementsare now valid for all M3 companies and divisions by default.


M3 BOD overview

StructureThe agreement structure contains the M3 root folder with the ION and ION_InitialLoad subfolders.ION_InitialLoad contains all outbound Show BOD agreements, whereas the ION folder contains therest of the BOD agreements. Process BODs use implicit routing. There is no requirement to keep theseagreements in a specific folder, which was previously used to specify the ionToLogicalID property forthese agreements.

Naming standardThe BOD agreement names use this naming standard:

• Noun is the BOD noun.• Variant is a variant of the noun in M3 Business Engine. There are, for example, many variants of

the CodeDefinition noun, since this noun is used for many different code types in M3 BusinessEngine. Although each variant requires its own BOD mapping and agreement, the same noun isused for the BODs. Variant is optional in the name.

• Verb is the BOD verb.• In or Out is the direction of the M3 BOD, In for inbound M3 BODs, Out for outbound M3 BODs.

The BOD agreements are sorted by the noun.

Examples:

• M3_BillOfMaterials_Process_Out• M3_CodeDefinitionAccountingDimension_Sync_Out• M3_CodeDefinitionItemTypes_Sync_Out• M3_ItemMaster_Process_In• M3_ItemMaster_Sync_Out

DetectionBecause all BOD agreements are M3 company- and division-independent, we only need to detect themessage based on the BOD type.

Outbound BOD agreements use the AnalyticsHubPublisherDocName XML detection, using Publisherand Document from the received event. The publisher is normally M3BODProcessor, and the documentis the BOD verb + noun + variant (optional), for example, SyncItemMaster.

Inbound BOD agreements use the IONInboxHeaderBODType manifest detection. on thecom:ionBODType manifest item,, which is set by the ION in-box header table. Example:Process.ItemMaster.

Note: The detection order in Infor Enterprise CollaboratorOutbound BOD agreements use the XMLdetection is managed in the Partner Admin tool, Manage > Detections > Detection Order tab. Werecommend to move the most specific detection groups higher up in the tree structure of the detection


M3 BOD overview

order. Keep the less specific groups at the end of the list. This allows Infor Enterprise Collaborator tocheck the more specific detections first.Note: If you decide to keep your existing BOD agreements from version M3BOD 15.4.0.0 or earlier,you might receive inbound BODs where the element TenantID is missing in the BOD.

The detections for inbound BODs in the agreement structure for M3BOD 15.4.0.0 were made usingthe TenantID element in the BODs. Because the TenantID element is now deprecated in BODs, youmight receive BODs without the TenantID element from other applications. In these cases, the detectionin Infor Enterprise Collaborator fails.

Take one of these actions to correct the detection:

• Change to manifest detection and use the BOD Type as Target (com:ionBODType)or• Use XML detection on the AccountingEntityID element. For XML detection on AccountingEntityID,

use one of these target XPaths:• /[noun][verb]/DataArea/[noun]/[document id...][@accountingEntity]In this case, one BOD

agreement handles all accounting entities for the inbound BOD.• /[noun][verb]/DataArea/[verb]/AccountingEntityID. In this case, you must set up one BOD

agreement per accounting entity.

Note: When using one BOD agreement per M3 company and division or accounting entity, the newBOD mappings still get M3 company and division or accounting entity from the received message data.This M3 company and division overrides the M3 user setting in MNS150, M3 company and divisionsettings for the API reference. It also overrides M3 company and division settings by agreement controlproperties.

System of RecordFor some nouns, the M3 BOD solution contains BOD agreements and Event Analytics rules for bothkind of integrations:

• where M3 is System of Record (SOR)• where M3 is not SOR

Because only one application can be SOR per noun and accounting entity, you must configure the M3BOD solution for this purpose.

M3 as System of RecordIf M3 is the system of record (SOR), you must disable the outbound Process BOD. The outbound SyncBOD must be enabled. If both the outbound Sync BOD and the outbound Process BOD are enabled,M3 publishes both the Sync BOD and the Process BOD when data for the noun is altered in M3. Thisis an invalid setup.


M3 BOD overview

To disable outbound BODs, you must stop the corresponding session in Event Analytics. If, for example,M3 is the SOR for the BillOfMaterials noun, the M3BEBODs_Out_ProcessBillOfMaterials session mustbe stopped and the M3BEBODs_BillOfMaterials session must be started.

Note: If M3 is the SOR, you must set up external applications and ION to only send Process BODs toM3. Sync BODs must not be sent to M3.

Another external application as system of recordIf M3 is not the system of record, you must disable the outbound Sync BOD and enable the outboundProcess BOD. If both the outbound Process BOD and the outbound Sync BOD are enabled, M3publishes both a Process BOD and a Sync BOD when data for the noun is altered in M3. This is aninvalid setup.

To disable outbound BODs, you must stop the corresponding session in Event Analytics. If for exampleM3 is not the SOR for BillOfMaterials, the M3BEBODs_BillOfMaterials session must be stopped, andthe M3BEBODs_Out_ProcessBillOfMaterials session must be started.

Note: If M3 is not SOR you must set up external applications and ION to only send Sync BODs to M3.Process BODs must not be sent to M3. This should not be configured in Infor Enterprise Collaborator.

Integrations with multiple System of RecordsWithin an M3 installation, different integrations can be applicable for different M3 companies anddivisions, using the same BOD definitions. If the system of record for a specific BOD is M3 in oneintegration and the external application in another integration, a separate configuration is required.Then you must either configure the BOD rules in Event Analytics accordingly or set up the BODagreements in Infor Enterprise Collaborator to ensure that different verbs are used for the noun asapplicable.

You can achieve this in one of these ways:

• Change the BOD rules for the noun in Event Analytics, so that they are only valid for the correctcompanies and divisions.

• Use different BOD agreements in Infor Enterprise Collaborator for the noun for different companiesand divisions.

Disabling M3 BOD integrationIf you must disable the BOD integration for an M3 company, division, or both, you can disable alloutbound BODs for that M3 company and division in the M3 BOD Processor. For inbound BODs, youmust set up other applications in the integration and in ION. Thus, BODs are not sent to M3 for theaccounting entity that corresponds to the M3 company and division.


M3 BOD overview

Note: When using the new BOD agreements without any changes, Infor Enterprise Collaborator alwaysprocesses received messages. Received messages can be events from the Event Hub for outboundBODs or inbound BODs from ION. The only way to avoid processing a BOD using the new BODagreements is to not send the event or BOD to Infor Enterprise Collaborator.


M3 BOD overview

Appendix E: Business events that generate outboundBODs

This list details the outbound BODs that M3 publishes. The user actions that results in events whichgenerate an outbound BOD from M3 are determined by the event rules set that is delivered with theM3 BODs. The list of events that trigger BODs in M3 is too extensive to be detailed in this document.See the Infor M3 Business Engine BODs Rules Documentation.

Noun/variantVerb

AccountingBookDefinitionShow

AccountingBookDefinitionSync

AccountingChartShow

AccountingChartSync

AccountingEntityShow

AccountingEntitySync

AccountingJournalShow

AccountingJournalSync

AdvanceShipNoticeAcknowledge

AdvanceShipNoticeProcess

AdvanceShipNoticeShow

AdvanceShipNoticeSync

AssetMasterAcknowledge

AssetMasterShow

AssetMasterSync

BillOfMaterialsProcess

BillOfMaterialsShow

BillOfMaterialsSync

BillOfResourcesShow

BillOfResourcesSync


Business events that generate outbound BODs

Noun/variantVerb

BillToPartyMasterAcknowledge

BillToPartyMasterShow

BillToPartyMasterSync

CalendarSync

CarrierPartyShow

CarrierPartySync

CarrierRouteSync

CatalogShow

CatalogSync

ChartOfAccountsShow

ChartOfAccountsSync

CodeDefinition for Accounting DimensionsShow

CodeDefinition for Accounting DimensionsSync

CodeDefinition for AP Payment MethodsShow

CodeDefinition for AP Payment MethodsSync

CodeDefinition for AR Payment MethodsShow

CodeDefinition for AR Payment MethodsSync

CodeDefinition for CapabilitiesShow

CodeDefinition for CapabilitiesSync

CodeDefinition for Cost CentersShow

CodeDefinition for Cost CentersSync

CodeDefinition for Customer Discount GroupsSync

CodeDefinition for Customer Discount GroupsShow

CodeDefinition for Customer GroupsSync

CodeDefinition for Customer GroupsShow

CodeDefinition for Delivery TermsShow

CodeDefinition for Delivery TermsSync

CodeDefinition for Dynamic DimensionShow

CodeDefinition for Dynamic DimensionSync

CodeDefinition for Equipment ClassesShow

CodeDefinition for Equipment ClassesSync



Noun/variantVerb

CodeDefinition for Equipment GroupsShow

CodeDefinition for Equipment GroupsSync

CodeDefinition for Equipment MeterShow

CodeDefinition for Equipment MeterSync

CodeDefinition for Error Code 1sShow

CodeDefinition for Error Code 1sSync





CodeDefinition for Feature OptionsAcknowledge

CodeDefinition for Feature OptionsShow

CodeDefinition for Feature OptionsSync

CodeDefinition for Freight TermsShow

CodeDefinition for Freight TermsSync

CodeDefinition for General CodeShow

CodeDefinition for General CodeSync

CodeDefinition for Harbor & AirportsShow

CodeDefinition for Harbor & AirportsSync

CodeDefinition for Individual Item GroupsShow

CodeDefinition for Individual Item GroupsSync

CodeDefinition for Inspection Result ValuesShow

CodeDefinition for Inspection Result ValuesSync

CodeDefinition for Item Discount GroupsShow

CodeDefinition for Item Discount GroupsSync

CodeDefinition for Item TypesShow

CodeDefinition for Item TypesSync

CodeDefinition for Misc Cost TypesShow

CodeDefinition for Misc Cost TypesSync

CodeDefinition for OptionsShow

CodeDefinition for OptionsSync



Noun/variantVerb

CodeDefinition for Payment TermsShow

CodeDefinition for Payment TermsSync

CodeDefinition for Points of ShipmentShow

CodeDefinition for Points of ShipmentSync

CodeDefinition for Price List TablesSync

CodeDefinition for Price List TablesShow

CodeDefinition for Product LinesShow

CodeDefinition for Product LinesSync

CodeDefinition for Product Service ExtendShow

CodeDefinition for Product Service ExtendSync

CodeDefinition for Product Structure ClassesShow

CodeDefinition for Product Structure ClassesSync

CodeDefinition for Product Structure TypesShow

CodeDefinition for Product Structure TypesSync

CodeDefinition for Purchase Order TypesShow

CodeDefinition for Purchase Order TypesSync

CodeDefinition for RoutesShow

CodeDefinition for RoutesSync

CodeDefinition for Sales Order ChargesShow

CodeDefinition for Sales Order ChargesSync

CodeDefinition for Service ActionShow

CodeDefinition for Service ActionSync

CodeDefinition for Service Action TextShow

CodeDefinition for Service Action TextSync

CodeDefinition for Service Assignment TypesShow

CodeDefinition for Service Assignment TypesSync

CodeDefinition for Service CentersShow

CodeDefinition for Service CentersSync

CodeDefinition for Service Error CauseShow

CodeDefinition for Service Error CauseSync

CodeDefinition for Service Error SymptomShow



Noun/variantVerb

CodeDefinition for Service Error SymptomSync

CodeDefinition for Service ManagersShow

CodeDefinition for Service ManagersSync

CodeDefinition for Service Order TypesShow

CodeDefinition for Service Order TypesSync

CodeDefinition for Service QualificationsShow

CodeDefinition for Service QualificationsSync

CodeDefinition for Service TypesShow

CodeDefinition for Service TypesSync

CodeDefinition for Stock LocationsAcknowledge

CodeDefinition for Stock LocationsShow

CodeDefinition for Stock LocationsSync

CodeDefinition for Transportation MethodsShow

CodeDefinition for Transportation MethodsSync

CodeDefinition for Unit CodesShow

CodeDefinition for Unit CodesSync

CodeDefinition for Work Order TypesShow

CodeDefinition for Work Order TypesSync

ConfiguredAssetMaster for Maintenance OrderShow

ConfiguredAssetMaster for Maintenance OrderSync

ConfiguredAssetMaster for Service OrderShow

ConfiguredAssetMaster for Service OrderSync

ContactMasterAcknowledge

ContactMasterShow

ContactMasterSync

CreditTransferSync

CurrencyExchangeRateMasterShow

CurrencyExchangeRateMasterSync

CurrencyRateTypeShow

CurrencyRateTypeSync

CustomerPartyMasterAcknowledge



Noun/variantVerb

CustomerPartyMasterShow

CustomerPartyMasterSync

CustomerReturnShow

CustomerReturnSync

DebitTransferSync

EmployeeWorkTimeAcknowledge

FinancialCalendarShow

FinancialCalendarSync

InspectionOrder for Work OrderAcknowledge

InspectionOrder for Work OrderShow

InspectionOrder for Work OrderSync

InventoryAdjustmentAcknowledge

InventoryAdjustmentShow

InventoryAdjustmentSync

InventoryCountShow

InventoryCountSync

InventoryHoldShow

InventoryHoldSync

Invoice for BillforPrepaymentShow

Invoice for BillforPrepaymentSync

Invoice for CustomerOrderShow

Invoice for CustomerOrderSync

ItemMasterAcknowledge

ItemMasterShow

ItemMasterSync

LCLJournalEntryReportSync

LCLTradeStatisticsEUSalesPurchaseSync

LCLTradeStatisticsIntrastatExtrastatSync

Location for FacilityShow

Location for FacilitySync

Location for WarehouseShow



Noun/variantVerb

Location for WarehouseSync

PayableTransactionShow

PayableTransactionSync

PayFromPartyMasterAcknowledge

PayFromPartyMasterShow

PayFromPartyMasterSync

PersonAcknowledge

PersonShow

PersonSync

ProductionOrderShow

ProductionOrderSync

PromotionShow

PromotionSync

PulseAlertProcess

PulseNotificationProcess

PulseTaskProcess

PurchaseOrderAcknowledge

PurchaseOrderShow

PurchaseOrderSync

QualitySpecificationAcknowledge

QualitySpecification for Work OrderShow

QualitySpecification for Work OrderSync

QualityTestMasterAcknowledge

QualityTestMaster for Work OrderShow

QualityTestMaster for Work OrderSync

QuoteAcknowledge

QuoteShow

QuoteSync

ReceivableTransactionShow

ReceivableTransactionSync

ReceiveDeliveryAcknowledge



Noun/variantVerb

ReceiveDeliveryShow

ReceiveDeliverySync

ReceiveDelivery for WarehouseShow

ReceiveDelivery for WarehouseSync

RemitToPartyMasterShow

RemitToPartyMasterSync

RequisitionAcknowledge

RequisitionShow

RequisitionSync

SalesOrderAcknowledge

SalesOrderShow

SalesOrderSync

ServiceOrderAcknowledge

ServiceOrderShow

ServiceOrderSync

ServiceOrder for Work OrderAcknowledge

ServiceOrder for Work OrderShow

ServiceOrder for Work OrderSync

ShipFromPartyMasterShow

ShipFromPartyMasterSync

ShipmentAcknowledge

ShipmentProcess

ShipmentShow

ShipmentSync

Shipment for DeliveryShow

Shipment for DeliverySync

ShipToPartyMasterAcknowledge

ShipToPartyMasterShow

ShipToPartyMasterSync

SourceSystemGLMovement for ActualShow

SourceSystemGLMovement for ActualSync



Noun/variantVerb

SourceSystemGLMovement for BudgetShow

SourceSystemGLMovement for BudgetSync

SourceSystemJournalEntryShow

SourceSystemJournalEntrySync

SupplierInvoiceAcknowledge

SupplierInvoiceSync

SupplierPartyMasterShow

SupplierPartyMasterSync

TransferSync

TransferShow

WorkflowProcess



Appendix F: Inbound BOD usage

This table shows the incoming BODs that are accepted by M3. See Infor M3 inbound BOD mappingand descriptions for detailed information on the area in which the processed inbound data is displayed.

Noun/variantVerb

AdvanceShipNoticeAcknowledge

AdvanceShipNoticeLoad

AdvanceShipNoticeProcess

AdvanceShipNoticeSync

AssetMasterProcess

BankStatementLoad

BillOfMaterialsAcknowledge

BillOfMaterialsSync

BillToPartyMasterProcess

CodeDefinition for Feature OptionsProcess

CodeDefinition for Stock LocationsProcess

ContactMasterProcess

CustomerPartyMasterProcess

EmployeeWorkTimeProcess

InspectionOrder for Work OrderProcess

InventoryAdjustmentProcess

InventoryAdjustmentSync

InventoryHoldSync

ItemMasterProcess

PayFromPartyMasterProcess

PersonProcess

PulseAlertAcknowledge


Inbound BOD usage

Noun/variantVerb

PulseNotificationAcknowledge

PulseTaskAcknowledge

PurchaseOrderProcess

QualitySpecificationProcess

QualityTestMasterProcess

QuoteProcess

ReceiveDeliveryProcess

ReceiveDeliverySync

RequisitionProcess

SalesOrderProcess

SecurityUserMasterSync

ServiceConsumptionSync

ServiceOrderProcess

ServiceOrder for Work OrderProcess

ShipmentAcknowledge

ShipmentProcess

ShipmentSync

ShipToPartyMasterProcess

SourceSystemGLMovement for BudgetSync

SupplierInvoiceLoad

SupplierInvoiceProcess

WorkflowAcknowledge


Inbound BOD usage

Appendix G: BODs used in integrations with M3

This section contains the list of BODs that are available with M3.

Outbound BODs from M3 to integrated applicationsThis table shows the BODs that are available with M3. Where the product column is blank, the BODis not currently used by interfacing products, but the BOD is generated by M3 and is available to beprocessed through ION and any application that is set up to receive it.

To productsNoun/variantVerb

Supplier RebateAccountingEntitySync

Infor NexusAdvanceShipNoticeAcknowledge

CloudSuite WMSAdvanceShipNoticeProcess

Rhythm for CommerceBillOfMaterialsSync

CloudSuite PLM for ProcessBillOfMaterialsProcess

Mobility for Field ServiceBillOfResourcesSync

CloudSuite CRMBillToPartyMasterAcknowledge

Enterprise Quoting

CloudSuite CRM

Rhythm for Commerce

CloudSuite WMS

BillToPartyMasterSync

CloudSuite CRMCarrierPartySync

Rhythm for CommerceCatalogSync

Supplier RebateCodeDefinition for AP Payment MethodsSync

Enterprise Quoting

CloudSuite CRM

CodeDefinition for AR Payment MethodsSync

Mobility for Field ServiceCodeDefinition for CapabilitiesSync

Rhythm for CommerceCodeDefinition for Delivery TermsSync


BODs used in integrations with M3


Mobility for Field ServiceCodeDefinition for Error Code 1sSync



M3 Fashion PLMCodeDefinition for Feature OptionsAcknowledge

Rhythm for CommerceCodeDefinition for Feature OptionsSync

CloudSuite EAMCodeDefinition for Freight TermsSync

Enterprise Quoting

Rhythm for Commerce

CodeDefinition for General CodeSync

Rhythm for CommerceCodeDefinition for Harbor & AirportsSync

Mobility for Field ServiceCodeDefinition for Inspection Result Val-ues

Sync

M3 Fashion PLM

Rhythm for Commerce

CodeDefinition for Item TypesSync

Enterprise Quoting

CloudSuite CRM

Rhythm for Commerce

Supplier Rebate

CodeDefinition for Payment TermsSync

CloudSuite PLM for ProcessCodeDefinition for Product StructureClasses

Sync

Rhythm for CommerceCodeDefinition for RoutesSync

Mobility for Field ServiceCodeDefinition for Service CentersSync

Mobility for Field ServiceCodeDefinition for Service TypesSync

CloudSuite EAMCodeDefinition for Stock LocationsAcknowledge

CloudSuite EAMCodeDefinition for Stock LocationsSync

Enterprise Quoting

CloudSuite CRM

Rhythm for Commerce

CodeDefinition for Transportation MethodsSync

CloudSuite EAM

Rhythm for Commerce

Supplier Rebate

CodeDefinition for Unit CodesSync

Mobility for Field ServiceCodeDefinition for Work Order TypesSync

CloudSuite CRMContactMasterAcknowledge

CloudSuite CRMContactMasterSync




Enterprise Quoting

Supplier Rebate

CurrencyExchangeRateMasterSync

CloudSuite CRMCustomerPartyMasterAcknowledge

Enterprise Quoting

CloudSuite CRM

CloudSuite PLM for Process

Rhythm for Commerce

CloudSuite WMS

CustomerPartyMasterSync

CloudSuite CRMCustomerReturnSync

Mobility for Field ServiceInspectionOrderAcknowledge

Mobility for Field ServiceInspectionOrderSync

CloudSuite EAMInventoryAdjustmentAcknowledge

CloudSuite CRM

Rhythm for Commerce

Invoice for Customer OrderSync

M3 Fashion PLM


ItemMasterAcknowledge

Enterprise Quoting

CloudSuite CRM

CloudSuite EAM

M3 Fashion PLM


Rhythm for Commerce

Enterprise Quoting

CloudSuite WMS

Supplier Rebate

ItemMasterSync

CloudSuite CRM

Rhythm for Commerce

Supplier Rebate

Location for WarehouseSync

CloudSuite CRMPayFromPartyMasterAcknowledge

CloudSuite CRMPayFromPartyMasterSync

CloudSuite CRMPersonSync

Rhythm for CommercePromotionSync

Infor NexusPurchaseOrderAcknowledge




CloudSuite EAM

Infor Nexus

CloudSuite WMS

Supplier Rebate

PurchaseOrderSync

Mobility for Field ServiceQualityTestMaster for Work OrderSync

CloudSuite PLM for ProcessQualitySpecificationAcknowledge

Mobility for Field ServiceQualitySpecification for Work OrderSync

CloudSuite CRMQuoteAcknowledge

CloudSuite CRMQuoteSync

CloudSuite CRM

Rhythm for Commerce

ReceivableTransactionSync

CloudSuite EAMReceiveDeliveryAcknowledge

CloudSuite EAMReceiveDeliverySync

CloudSuite EAMRequisitionAcknowledge

Enterprise Quoting

CloudSuite CRM

Rhythm for Commerce

SalesOrderAcknowledge

Enterprise Quoting

CloudSuite CRM

Rhythm for Commerce

SalesOrderSync

Mobility for Field ServiceServiceOrder for Work OrderAcknowledge

Mobility for Field ServiceServiceOrder for Work OrderSync

CloudSuite WMSShipFromPartyMasterSync

CloudSuite EAMShipmentAcknowledge

CloudSuite WMSShipmentProcess

CloudSuite CRM

Mobility for Field Service

Rhythm for Commerce

Shipment for DeliverySync

CloudSuite CRMShipToPartyMasterAcknowledge

Enterprise Quoting

CloudSuite CRM

Rhythm for Commerce

CloudSuite WMS

ShipToPartyMasterSync




Supplier RebateSupplierInvoiceAcknowledge

CloudSuite EAM

M3 Fashion PLM


CloudSuite WMS

Supplier Rebate

SupplierPartyMasterSync

Inbound BODs to M3 from integrated applicationsThis table shows the BODs that can be received and processed by M3. If the product column is empty,the BOD is not currently used by interfacing products.

From productsNoun/variantVerb

CloudSuite WMSAdvanceShipNoticeAcknowledge

Infor NexusAdvanceShipNoticeProcess

CloudSuite PLM for ProcessBillOfMaterialsAcknowledge

CloudSuite PLM for ProcessBillOfMaterialsSync

CloudSuite CRMBillToPartyMasterProcess

M3 Fashion PLMCodeDefinition for Feature Op-tions

Process

CloudSuite EAMCodeDefinition for Stock Loca-tions

Process

CloudSuite CRMContactMasterProcess

CloudSuite CRMCustomerPartyMasterProcess

Mobility for Field ServiceInspectionOrder for Work OrderProcess

CloudSuite EAMInventoryAdjustmentProcess

CloudSuite WMSInventoryAdjustmentSync

CloudSuite WMSInventoryHoldSync

M3 Fashion PLM


ItemMasterProcess

CloudSuite CRMPayFromPartyMasterProcess

Infor NexusPurchaseOrderProcess



From productsNoun/variantVerb

CloudSuite PLM for ProcessQualitySpecificationProcess

CloudSuite CRMQuoteProcess

CloudSuite EAMReceiveDeliveryProcess

CloudSuite WMSReceiveDeliverySync

CloudSuite EAMRequisitionProcess

Enterprise Quoting

CloudSuite CRM

Rhythm for Commerce

SalesOrderProcess

Mobility for Field ServiceServiceOrder for Work OrderProcess

CloudSuite WMSShipmentAcknowledge

CloudSuite EAMShipmentProcess

CloudSuite WMSShipmentSync

CloudSuite CRMShipToPartyMasterProcess

Supplier RebateSupplierInvoiceProcess



Appendix H: Master tables for initial load

This table lists the M3 master tables by Show verb for sending the initial load.

M3 master table for InitialLoad

NounVerb

CSYTABAccountingBookDefinitionShow

CSYTABAccountingChartShow

CMNDIVAccountingEntityShow

CSYTABAccountingJournalShow

MHEXRHAdvanceShipNoticeShow

FFASMAAssetMasterShow

MPDHEDBillOfMaterialsShow

MPDSRCBillOfResourcesShow

OCUSAD, OCUSMABillToPartyMasterShow

CIDMASCarrierPartyShow

CSYTABCatalogShow

FCHACCChartOfAccountsShow

FCHACCCodeDefinition for Accounting DimensionsShow

CSYTABCodeDefinition for AP Payment MethodsShow

CSYTABCodeDefinition for AR Payment MethodsShow

CCADEFCodeDefinition for CapabilitiesShow

FCHACCCodeDefinition for Cost CentersShow

CSYTABCodeDefinition for Customer Discount GroupsShow

CSYTABCodeDefinition for Customer GroupsShow

CSYTABCodeDefinition for Delivery TermsShow

FGLEDGCodeDefinition for Dynamic DimensionShow

MIEQCLCodeDefinition for Equipment ClassesShow


Master tables for initial load


NounVerb

MIEQGRCodeDefinition for Equipment GroupsShow

SINDMDCodeDefinition for Equipment MeterShow

CSYTABCodeDefinition for Error Code 1sShow



MPDFHECodeDefinition for Feature OptionsShow

CSYTABCodeDefinition for Freight TermsShow

CSYTABCodeDefinition for General CodeShow

CSYTABCodeDefinition for Harbor & AirportShow

CSYTABCodeDefinition for Individual Item GroupsShow

MPDIRVCodeDefinition for Inspection Result ValuesShow

CSYTABCodeDefinition for Item Discount GroupsShow

MITTTYCodeDefinition for Item TypesShow

ACUEXPCodeDefinition for Misc Cost TypesShow

MPDOPTCodeDefinition for OptionsShow

CSYTABCodeDefinition for Payment TermsShow

CSYTABCodeDefinition for Points of ShipmentShow

OPLTMACodeDefinition for Price List TablesShow

CRPDLNCodeDefinition for Product LinesShow

SITCOMCodeDefinition for Product Service ExtendShow

CSYTABCodeDefinition for Product Structure ClassesShow

CSYTABCodeDefinition for Product Structure TypesShow

MPORDTCodeDefinition for Purchase Order TypesShow

DROUTECodeDefinition for RoutesShow

ODCHRGCodeDefinition for Sales Order ChargesShow

SMECODCodeDefinition for Service ActionShow

SMETXTCodeDefinition for Service Action TextShow

SASSTPCodeDefinition for Service Assignment TypesShow

MPDWCTCodeDefinition for Service CentersShow

SERCODCodeDefinition for Service Error CauseShow




NounVerb

SERSYMCodeDefinition for Service Error SymptomShow

SSRESPCodeDefinition for Service ManagersShow

SSTYPECodeDefinition for Service Order TypesShow

CSYTABCodeDefinition for Service QualificationsShow

CSYTABCodeDefinition for Service TypesShow

MITPCECodeDefinition for Stock LocationsShow

CSYTABCodeDefinition for Transportation MethodsShow

CSYTABCodeDefinition for Unit CodesShow

MMORDTCodeDefinition for Work Order TypesShow

MILOINConfiguredAssetMaster for Maintenance OrderShow

SINDIVConfiguredAssetMaster for Service OrderShow

CCUCONContactMasterShow

CCURRACurrencyExchangeRateMasterShow

CSYTABCurrencyRateTypeShow

OCUSMACustomerPartyMasterShow

OCHEADCustomerReturnShow

CSYPERFinancialCalendarShow

MMOOPSInspectionOrder for Work OrderShow

MITTRAInventoryAdjustmentShow

MITTKVInventoryCountShow

MITTRAInventoryHoldShow

OOPINHInvoice for BillforPrepaymentShow

OINVOHInvoice for CustomerOrderShow

MITMASItemMasterShow

CFACILLocation for FacilityShow

MITWHLLocation for WarehouseShow

FPLEDGPayableTransactionShow

OCUSMAPayFromPartyMasterShow

CSYUSRPersonShow

MWOHEDProductionOrderShow




NounVerb

OPROMHPromotionShow

MPHEADPurchaseOrderShow

MPDIIDQualitySpecification for Work OrderShow

MPDIREQualityTestMaster for Work OrderShow

OOQUOHQuoteShow

FSLEDGReceivableTransactionShow

MPLINDReceiveDeliveryShow

MHDISHReceiveDelivery for WarehouseShow

CIDMASRemitToPartyMasterShow

MPOPLPRequisitionShow

OOHEADSalesOrderShow

SSHEADServiceOrderShow

MMOHEDServiceOrder for Work OrderShow

CIDMASShipFromPartyMasterShow

DCONSIShipmentShow

MHDISHShipment for DeliveryShow

OCUSAD, OCUSMAShipToPartyMasterShow

FBAVALSourceSystemGLMovement for ActualShow

FBUDETSourceSystemGLMovement for BudgetShow

FGLHEDSourceSystemJournalEntryShow

CIDMASSupplierPartyMasterShow

MGHEADTransferShow

