infor ln cloud configuration guide · configure infor ln ce. configuring infor ln ce on page 34....

Infor LN Cloud Configuration Guide

Copyright © 2021 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 LN Cloud cePublication Date: May 4, 2021Document code: lncs_ce_lncscg__en-us

Contents

About this guide.................................................................................................................................7

Contacting Infor.................................................................................................................................7

Chapter 1: Requirements...................................................................................................................8

Required applications........................................................................................................................8

Required information.........................................................................................................................8

Chapter 2: Configuration checklist...................................................................................................9

Chapter 3: Configuration overview.................................................................................................12

About Infor LN Cloud.......................................................................................................................12

Supported applications................................................................................................................12

LN Cloud tenants.............................................................................................................................13

Sequential dump of tables...........................................................................................................14

Integration with products in Infor LN Cloud.....................................................................................15

Point to point integrations.............................................................................................................16

Web services integrations............................................................................................................16

BOD integrations..........................................................................................................................16

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

Tenant ID......................................................................................................................................17

Accounting entity..........................................................................................................................17

Location.......................................................................................................................................17

Logical ID.....................................................................................................................................17

Chapter 4: Getting started...............................................................................................................18

Determining the bootstrap administrator.........................................................................................18

Accessing your cloud environment (tenant)....................................................................................18

Verifying access to your applications...............................................................................................18

Chapter 5: Post provisioning steps.................................................................................................20

Post provisioning tasks for Infor LN CE...........................................................................................20

Infor LN Cloud Configuration Guide | 3

Contents

Importing ION content..................................................................................................................20

Upgrading ION content................................................................................................................32

Configuring application companies..............................................................................................32

Post provisioning tasks for other applications..................................................................................32

Chapter 6: Configuring your web browser.....................................................................................33

Setting up compatibility for Microsoft Internet Explorer browsers....................................................33

Allowing popups for browsers..........................................................................................................33

Chapter 7: Configuring Infor LN CE................................................................................................34

Chapter 8: Configuring ERP access through Infor Ming.le..........................................................36

Single Sign On................................................................................................................................36

Users and roles...............................................................................................................................36

Roles in Infor Ming.le...................................................................................................................37

Roles in Infor LN CE....................................................................................................................37

Configuring user access to LN CE through Infor Ming.le................................................................38

ION CE.........................................................................................................................................38

LN CE tools company..................................................................................................................39

Infor Ming.le.................................................................................................................................43

LN CE application companies......................................................................................................47

Configuring additional system administrator access to applications through Infor Ming.le.............48

Verifying user access......................................................................................................................48

Setting up distribution groups..........................................................................................................49

Chapter 9: Configuring LN CE to send and receive BODs in ION................................................50

Tasks completed during provisioning and post provisioning............................................................50

Understanding how applications connect to ION............................................................................50

Publishing BODs.............................................................................................................................51

Initial data load.............................................................................................................................51

Sending the initial data load.........................................................................................................51

Publishing additional initialization data........................................................................................52

Verifying the ION configuration........................................................................................................53

Verifying that BODs are generated..............................................................................................53

Verifying that ION receives data...................................................................................................53

Verifying the data flow between applications...............................................................................54

Chapter 10: Configuring workflows and ION messages for LN CE.............................................55

ION messages.................................................................................................................................55


Contents

ION monitors, workflows and activation policies.............................................................................56

Document authorization...............................................................................................................56

Activating ION monitors, workflows, and activation policies............................................................57

Activating document authorization...............................................................................................57

Defining alarm templates.................................................................................................................58

Sample content for monitors, activation policies and workflows......................................................58

Chapter 11: Verifying drillbacks to LN CE......................................................................................59

About drillbacks...............................................................................................................................59

Available drillbacks..........................................................................................................................59

Verifying a drillback.........................................................................................................................60

Chapter 12: Configuring ION content for new LN application companies..................................61

Adding companies...........................................................................................................................61

Removing companies......................................................................................................................61

Chapter 13: Customizing ION content for LN CE...........................................................................63

Customizing BODs..........................................................................................................................63

UserArea......................................................................................................................................63

LN Studio.....................................................................................................................................63

LN Message.................................................................................................................................64

Customizing monitors, workflows, and activation policies...............................................................64

Customizing document authorization workflows.............................................................................64

Customizing drillbacks.....................................................................................................................65

Chapter 14: Configuring context apps and utility apps that are used with LN CE.....................66

Understanding in-context messages...............................................................................................66

Supported in-context messages..................................................................................................66

Context and utility applications that work with LN CE.....................................................................68

Enabling a context or utility app for LN CE..................................................................................68

Configuring the LN file attachments context app (ODM).............................................................69

Chapter 15: Configuring homepages for LN CE............................................................................71

Importing the homepage and widget content..................................................................................71

Chapter 16: Configuring Infor Document Management with LN CE............................................73

Document types..............................................................................................................................73

Specifying new document types..................................................................................................74

In-context messages.......................................................................................................................76


Contents

Related Information context app......................................................................................................77

Chapter 17: Configuring Infor Data Lake with LN CE....................................................................79

Chapter 18: Configuring BI and Analytics content for LN CE......................................................80

Chapter 19: Configuring Infor Localization Services for LN CE...................................................81

Chapter 20: Configuring and integrating other applications in the solution..............................82

Integrating with Infor Automotive Exchange....................................................................................82

Integrating with Infor CPQ...............................................................................................................82

CPQ Enterprise Configurator.......................................................................................................82

CPQ Enterprise Quoting..............................................................................................................82

Integrating with Infor d/EPM............................................................................................................83

Integrating with Infor Document Capture.........................................................................................83

Integrating with Infor EAM...............................................................................................................83

Integrating with Infor EDI Exchange................................................................................................83

Integrating with Infor Expense Management...................................................................................83

Integrating with Infor Factory Track..................................................................................................84

Configuring the Factory Track tenant...........................................................................................84

Configuring users.........................................................................................................................85

Turning on replication for BODs...................................................................................................87

Integrating with Infor HR Talent.......................................................................................................88

Integrating with Infor Governance, Risk and Compliance................................................................88

Integrating with Infor LN Mobile Apps..............................................................................................88

Integrating with Infor LN Mobile Service..........................................................................................89

Integrating with Infor PLM Discrete.................................................................................................89

Integrating with Infor Rhythm for Commerce...................................................................................89

Integrating with Infor Supplier Exchange.........................................................................................89

Integrating with Infor WMS..............................................................................................................89

Appendix A: Troubleshooting..........................................................................................................90

Data is not flowing properly.............................................................................................................90

Appendix B: Alert monitors.............................................................................................................91

LN CE monitors...............................................................................................................................91

Appendix C: Activation policies and workflows............................................................................94

Appendix D: Document authorization workflows..........................................................................96


Contents

About this guide

This guide provides information for the configuration and implementation of Infor LN Cloud in amulti-tenant cloud environment.

Note:

Because most applications that are outlined in this guide are also offered with the industry CloudSuitesfor Infor LN CE, this guide can also be used to configure and implement these multi-tenant CloudSuites:

• Infor CloudSuite Aerospace & Defense (A&D)• Infor CloudSuite Automotive• Infor CloudSuite High-Tech and Electronics• Infor CloudSuite Industrial Enterprise

Consequently, in this guide, references to LN Cloud apply equally to Infor CloudSuite Aerospace &Defense (A&D), Infor CloudSuite Automotive, Infor CloudSuite High-Tech and Electronics, and InforCloudSuite Industrial Enterprise.

Refer to the Solution Overview document of the CloudSuite to view which applications (core and add-on)are included in a specific suite.

Intended audience

This guide is intended for the system administrator or consultant who configures Infor LN Cloud foruse with Infor OS in the cloud.

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 applicationsEnsure that you have system administrator access to these applications in the cloud:

• Infor LN CE• Infor Operating Service applications• Infor Birst (Analytics Platform)• Infor LN Analytics applications• Infor Automotive Exchange (for Infor CloudSuite Automotive)• Infor Supplier Exchange (for Infor CloudSuite Automotive and Infor CloudSuite High-Tech and

Electronics)

Required informationObtain this information from the Infor Cloud team before you begin the integration:

• Administrator account and access information for your hosted Infor environment.• Name of the application instance or logical ID that is used to connect with Infor ION CE.• Tenant ID that is used to connect the application to Infor ION CE.• Enterprise organization structure, that is, accounting entities.• Location of content source files to be imported into ION CE and Infor Ming.le.


Requirements

Chapter 2: Configuration checklist

Follow this checklist to integrate the components in Infor LN Cloud:

ReferenceTaskComplete

• Configuration overview on page 12.• Infor LN Cloud Solution Overview on

the Infor Support Portal.• Infor LN Cloud Documentation List

on Documentation Central.

Understand the applications in LN Cloudand some related concepts.

□

Getting started on page 18.Perform the prerequisites to this configu-ration:

• Determine the bootstrap administra-tor.

• Perform initial sign-in and verify thatyou can access the applications.

□

Post provisioning steps on page 20.Perform post provisioning steps. Thesetasks might be completed by Infor Con-sulting:

• Import ION content for LN CE.• Upgrade ION content for LN CE.• Configure LN application companies.• Perform post provisioning tasks for

other applications in the solution.

□

Configuring your web browser on page33.

Set up compatibility for Internet Explorerbrowsers.

□

Configuring Infor LN CE on page 34.Configure Infor LN CE.□

Configuring ERP access through InforMing.le on page 36.

Configure user access and roles:

• Understand users and roles.• Configure user access to LN CE in

Infor Ming.le.• Configure additional system adminis-

tration access to applications throughInfor Ming.le.

• Optionally, set up distribution groups.

□


Configuration checklist

https://docs.infor.com/lncs/ce/en-us/lncloudbom/index.html


Configuring LN CE to send and receiveBODs in ION on page 50.

Configure LN CE to send and receiveBODs in ION:

• Understand how products connectto ION.

• Publish BODs.• Send the initial data load and addi-

tional data.• Verify the ION configuration.

□

Configuring workflows and ION mes-sages for LN CE on page 55.

Configure workflows and ION messagesfor LN CE:

• Understand ION messages.• Understand and activate ION moni-

tors, workflows, activation policies,and document authorization.

• Define alarm templates.

□

Verifying drillbacks to LN CE on page59.

Configure drillbacks to LN CE.□

Configuring ION content for new LN ap-plication companies on page 61.

Configure ION content for added andremoved LN application companies.

□

Customizing ION content for LN CE onpage 63.

Customize ION content for LN CE:

• BODs.• Monitors, workflows and activation

policies.• Document authorization workflows.• Drillbacks.

□

Configuring context apps and utility appsthat are used with LN CE on page 66.

Configure context and utility apps thatare used with your application.

□

Configuring homepages for LN CE onpage 71.

Configure homepages for your applica-tion.

□

Configuring Infor Document Managementwith LN CE on page 73.

Configure LN CE to work with Infor Doc-ument Management.

□

Configuring Infor Data Lake with LN CEon page 79.

Configure Infor Data Lake to work withLN CE.

□

Configuring BI and Analytics content forLN CE on page 80.

Configure BI and Analytics content towork with LN CE.

□

Configuring Infor Localization Servicesfor LN CE on page 81.

Configure Infor Localization Services forLN CE.

□




• Integrating with Infor AutomotiveExchange on page 82.

• Integrating with Infor CPQ on page82.

• Integrating with Infor d/EPM on page83

• Integrating with Infor DocumentCapture on page 83

• Integrating with Infor EAM on page83.

• Integrating with Infor EDI Exchangeon page 83.

• Integrating with Infor Expense Man-agement on page 83.

• Integrating with Infor Factory Trackon page 84.

• Integrating with Infor HR Talent onpage 88

• Integrating with Infor Governance,Risk and Compliance on page 88

• Integrating with Infor LN Mobile Appson page 88.

• Integrating with Infor LN Mobile Ser-vice on page 89.

• Integrating with Infor PLM Discreteon page 89

• Integrating with Infor Rhythm forCommerce on page 89

• Integrating with Infor Supplier Ex-change on page 89.

• Integrating with Infor WMS on page89.

Configure other applications in the solu-tion to work with Infor OS or the ERP.

□



Chapter 3: Configuration overview

Before you complete the configuration tasks, you must understand what is provided in Infor LN Cloudand how its components communicate. You should also be familiar with the list of related conceptsand definitions.

About Infor LN CloudThe Infor LN Cloud Solution Overview document provides a high-level explanation of this solution anda summary of the applications that are included. It also includes information about, personalization,extension, and integration options.

Supported applicationsThe core solution includes Infor LN CE, Infor Operating Service (OS), Infor Birst (Analytics Platform),and Infor LN Analytics. The other applications that are outlined in this document can also be deliveredand can be offered by Infor as an integrated solution.

These applications are offered with this solution:

• Infor LN CE• Infor Operating Service

• Infor Ming.le™• Infor ION CE• ION Messaging Service (IMS)• Infor Data Lake• Infor Document Management• Infor Localization Services

• Infor Birst• Analytics Platform• Birst Enterprise

• Infor LN Analytics• LN Analytics Foundation• LN Analytics Program Cost Ledger (PCL)


Configuration overview

• LN Analytics Quality Management (QM)

• Infor Automotive Exchange• Infor CPQ

• CPQ Enterprise Configurator• CPQ Enterprise Quoting

• Infor EAM• Infor Expense Management• Infor Document Capture• Infor Dynamic Enterprise Performance Management (d/EPM)• Infor EDI Exchange• Infor Factory Track• Infor HR Talent (GHR)• Infor Governance, Risk and Compliance (GRC)• Infor LN Mobile Apps• Infor LN Mobile Service• Infor PLM Discrete• Infor Rhythm for Commerce• Infor Supplier Exchange• Infor WMSNote: • Infor PLM Discrete must be installed on premises.• Infor Document Capture and EDI Exchange are single-tenant cloud applications.• If you use Automotive Exchange, EDI Exchange is automatically included.

LN Cloud tenantsEach LN Cloud customer is set up with a number of tenants to be used for different purposes, forexample, to fulfill training or production. For each tenant, various companies are provisioned that includeonly initialized data.

For more information on the tenants that are provisioned, see the Cloud Handbook.

Each tenant is a completely isolated environment, with separate users and data. If you set up data inone tenant and then want to copy it to your other tenant, you have these options:

• Use the To Excel option (on grid forms) to save data from a form to a spreadsheet and then importit into the same form in the other tenant

• Create a sequential dump of tables on one tenant, which you upload to another tenantNote: Only the initialized tenant data is copied. Further configuration of the company is yet to beperformed.



Sequential dump of tablesTo create a sequential dump of tables on one tenant and upload it to another tenant, in Infor LN CE:

1 Export data from the tenant to a dump file using the Create Sequential Dump of Table(ttaad4226m000) session.a Specify the (operational) company and a table or a range of tables for which you want to create

a dump file.b On the Files tab, specify the file name for the dump and the file name for the error log. These

two files will be written to your home directory or the directory specified in the Directory forTable Files field.

An extension will automatically be added to the file name of the dump; a dot followed by the companynumber.

2 Import the data that you exported in the previous step into the other tenant. To load the previouslycreated dump into the tenant and to create tables from the sequential dump, use the Create Tablefrom Sequential Dump (ttaad4227m000) session.a Select the Create Tables for Different Company check box and specify the company number

of the other tenant.



b Select the Ignore Referential Integrity Constraints check box. If this check box is cleared,the result could be a 606 error when you create the table from the sequential dump.

3 Repeat the previous steps for all dumps of the mandatory tables that you created.4 Run the Reorganize Tables (ttaad4225m000) session with the Reference Integrity and Repair

Reference Counter check boxes selected. The company number must be the company numberof the other tenant.

Integration with products in Infor LN CloudInfor LN CE uses different integration methods to communicate with applications in LN Cloud.



Point to point integrationsPoint to point integrations, for example Infor CPQ Enterprise Configurator with Infor CPQ EnterpriseQuoting, use direct database connections that are set up by the Infor Cloud team. You might need toconfigure additional parameters or master data in each of the applications to complete the integration.See the appropriate integration guides.

Web services integrationsWeb services integrations, for example with Infor Factory Track or Infor CPQ, use standardized webprotocols (HTTP or HTTPS) to interoperate, communicate, and exchange data messaging – usuallyXML (Extensible Markup Language) – throughout the internet.

The integrations are set up by the Infor Cloud team, but you might need to configure additionalparameters or master data in each of the applications to complete the integration. See the appropriateintegration guides.

BOD integrationsAn outbound operation typically begins when a user performs an action in Infor LN CE that requires adata exchange with another ION-enabled product. A Business Object Document (BOD) XML messageis generated and placed in an area designated as the product message outbox. At scheduled intervals,ION connects to the outbox and retrieves the BODs from it.

In ION Desk, a connection point is set up for each product or site in LN Cloud that can send or receiveBODs. If you add products later, the Infor Cloud team adds connection points for them, as needed.The connection point defines the information needed to connect to the application database. It alsoholds a list of all the BOD documents that the application can send or receive.

Document flows are defined between the connection points to represent the business flows betweenthe products. For example, a document flow is set up between Infor LN CE and Infor Ming.le to passBODs that contain user and role information. Use the Modeler in ION Desk to activate these documentflows.

ION CE routes BODs according to the document flows between BOD-enabled products. If a documentflow is defined from LN CE to another product for a particular BOD, then at specified intervals, IONplaces the outbound BOD from LN CE in the other product’s designated message in-box. Productsare responsible for validating and incorporating the data in inbound BODs according to their rules.

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



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 products that exchange BODs. Data is not shared oraccessible between tenants. The tenant ID is specified by the Infor Cloud team. This value should notbe changed.

See the information about using tenants in the Infor ION Desk User Guide - Cloud Edition.

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

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 publishedin the Location BOD. A location is required for all transactional BODs and is usually the location fromwhich a transaction or record is generated.

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 is assigned one logical ID. For example, each LNCE company has a unique logical ID. In ION CE, the logical ID is used to properly route BODs. InforMing.le uses the logical ID to determine which application to start when you click a drillback.

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

Because Infor LN CE supports multiple companies, you must use the Logical ID Fallback table in InforMing.le to associate additional companies of LN CE with company 01. Then, for example, when adrillback is sent to Infor Ming.le for company 02, Infor Ming.le uses the information in the Logical IDFallback table to determine that company 02 is related to 01.

For more information, see the online help.



Chapter 4: Getting started

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

Determining the bootstrap administratorYour tenant is delivered with a bootstrap administrator already assigned. The bootstrap administratoris the only person who can initially access the tenant. This administrator performs the initial setup ofthe tenant, including setting up access for other users.

Customers must designate one person as the bootstrap administrator. During the planning process,they must provide the email address of the designated person to their Infor representative.

For business partners who are configuring an Infor hosted CloudSuite demo environment, the bootstrapadministrator is typically the person who made the initial request for the demo environment.

Accessing your cloud environment (tenant)After the environment has been provisioned, Infor sends the bootstrap administrator an email that hasthis text in the subject line: !SECURE! Infor Provisioning Notification. This email containsinstructions for activating your Infor Ming.le user. It also includes the URLs to access the environments.

Follow the instructions in this email to complete these tasks:

• Activate and validate your access to Infor Ming.le using the instructions provided.• Validate access via the provided URLs and verify that you are able to log in to all environments.

Verifying access to your applicationsAfter you sign in to the Infor Ming.le portal for the first time, ensure that you have system administratoraccess to these applications in the cloud:


Getting started

1 Click User Menu and verify that you can access the Admin Settings and the User Managementmenu options.

2 Click App Menu and verify that you can access the applications for your solution, such as InforLN CE, Infor Ming.le, and Infor Document Management.

3 Verify that you can access the optional applications that you have licensed, such as Infor FactoryTrack.


Getting started

Chapter 5: Post provisioning steps

These are the initial steps that must be done after your tenant is provisioned by Infor.

If you engage Infor Consulting Services to perform post provisioning, they will perform the steps in thischapter for you.

Note: The Post Provisioning steps are often performed by the Bootstrap Administrator. At a minimum,the person performing these steps must have IONDeskAdmin, IONDeskSecurityAdmin, andIDM-Administrator roles assigned in Infor Ming.le, as well as be a super user in LN CE. See ConfiguringERP access through Infor Ming.le on page 36.

Post provisioning tasks for Infor LN CEThis section describes the post provisioning steps that must be done for Infor LN CE.

Importing ION contentThe cloud environment that is provisioned by the Cloud team includes:

• Infor Ming.le• Infor ION CE• Infor LN CE• LN CE tools company 0000

The cloud environment that is provisioned also meets all Infor Ming.le, ION CE and LN CE prerequisitesto use the Infor LN ION content. However, this LN ION content must first be imported and configured.

Distribution groups1 Download the DistributionGroups.csv content from KB Article 1915676 on the Infor Support Portal.2 In Infor Ming.le, select User Menu > User Management > Manage > Groups.3 Click the Import button to import the distribution groups for LN CE and select the

DistributionGroups.csv from the zipped Infor LN ION content file.


Post provisioning steps

https://support.infor.com/espublic/EN/AnswerLinkDotNet/SoHo/Solutions/SoHoViewSolution.aspx?SolutionID=1915676&kb_accessed_from=KBViews

Connection pointsConnection points provide the information that ION CE uses to connect to an application’s messageinbox and outbox. At least one connection point is defined for each application instance that integratesto ION CE.

Import and update the LN CE connection points to include the BODs that can be sent from, or receivedinto LN CE:

1 Download the IONLNCE.zip content from KB Article 1915676 on the Infor Support Portal.2 In ION Desk, select Connect > Connection Points.3 The delivered ConnectionPoint_LNApps.xml file contains a connection point with the documents

that LN CE supports. To import this file:

a Click Import to import the 9999 company.b Select file ConnectionPoint_LNApps.xml from the zipped Infor LN ION content file.



https://support.infor.com/espublic/EN/AnswerLinkDotNet/SoHo/Solutions/SoHoViewSolution.aspx?SolutionID=1915676&kb_accessed_from=KBViews

If the farm is not called ln01, change the file name of ConnectionPoint_LNApps.xml before theimport. Company 0000 shows the farm that is used.



4 Select connection point ln01_9999 and click Duplicate. Go to the details and change 9999 intoyour own company. Click Save.The created connection point must be duplicated and changed for each LN CE application company.



5 After connection points are created for each LN CE application company, select connection pointln01_9999 and click Delete.Note: The connection point only shows connection property LN Company. The user name is hiddenin ION Desk. Navigate to LN > Tools > User Management > Active Users (ttaad2560m000) toverify that super user ion_ln is used to handle the ION integration process.

Verifying BODs for the ERP connection points

After the Infor LN CE connection points have been set up, verify that they contain the correct documents:

1 In ION Desk, select Connect > Connection Points.2 Select one of the created LN CE connection points. Click the Documents tab of your connection

point to view all of the documents that can be sent or received by this application instance for anyintegration. For each document, you can view whether it can be sent, received, or both.The list of documents for this connection point must match the list of BODs used in integrationswith the application.

Document flowsDocument flows define which BODs flow between the application connection points. These documentflows must be imported for Infor LN CE.



To import the document flows:

1 In ION Desk, select Connect > Data Flows.2 Add the document flow between Infor Ming.le and LN CE application companies:

a Click Import and select the DocumentFlow_LNApps_Mingle.xml from the zipped Infor LNION content file.

b A message will be displayed that the import contains duplicate items. Select the option Mergeadditional documents.

c Open the details of the document flow Mingle-LNApps and select the LN CE application.d Click Add to add the LN CE apps connection point to the document flow, repeat for each

company. Do not add the LN CE connection point company 0000. Do not activate the documentflow Mingle-LNApps.



3 Add the document flow between Infor Ming.le and LN CE tools company 0000:a Click Import and select the DocumentFlow_LN0000_Mingle.xml from the zipped Infor LN

ION content file.

In case the farm is not called ln01, change the file DocumentFlow_LN0000_Mingle.xmlaccordingly before the import. Company 0000 shows the farm that is used. Modify the Mingleconnection point to the one that exists on your environment. Use the Mingle connection pointfor reference.



b A message will be displayed that the import contains duplicate items. Select the option Mergeadditional documents.



c Click Activate to activate the document flow Mingle_LN0000.

Note: To pass BODs between applications, document flows must be activated. When youactivate a document flow, the associated connection points are activated. You cannot activateconnection points individually.

Verifying the document flow Mingle_LN0000

The document flow Mingle_LN0000 is used to pass security user account and role information betweenthe LN CE tools company and Infor Ming.le.

To verify that the flow is activated and that it contains the correct connection points and documents:

1 In ION Desk, select Connect > Data Flows.2 Find the document flow Mingle_LN0000 and verify that it is marked as Active.

3 Select the document flow to open it.

4 Select the document icon between LN-OUT and Mingle and verify that it lists these documents:• Process.SecurityUserMaster• Sync.SecurityRoleMaster

5 Select the document icon between Mingle and LN_IN and verify that it lists this document:• Sync.SecurityUserMaster

Verifying the document flow Mingle_LNApps

The document flow Mingle_LNApps is used to pass accounting entities, locations, and persons betweenthe LN CE application companies and Infor Ming.le.



To verify that the flow is activated and that it contains the correct connection points and documents:

1 In ION Desk, select Connect > Data Flows.2 Find the document flow Mingle_LNApps and verify that it is marked as Active.

3 Select the document flow to open it.

4 Select the document icon between LN and Mingle and verify that it lists these documents:• Sync.AccountingEntity• Sync.Location• Sync.Person

Upgrading ION contentNew versions of content packs (LN ION content) may be released. The new Infor LN ION contentusually includes new features for ION CE and LN CE and new or extended BODs.

To use this new content, the existing Infor LN ION content must be upgraded to a new version. Seethe information about upgrading ION content in the Infor LN Cloud Configuration Guide for Infor IONWorkflows and Monitors for the upgrade steps that you must perform.

Configuring application companiesFor the application companies that you use, specific LN data must be configured before BODs can begenerated from or to Infor LN CE. See Configuring Infor LN CE on page 34.

Post provisioning tasks for other applicationsFor any post provisioning steps that must be done for the other applications in this solution, seeConfiguring and integrating other applications in the solution on page 82.



Chapter 6: Configuring your web browser

Configure your browser for use with Infor Ming.le.

Setting up compatibility for Microsoft Internet ExplorerbrowsersNote: Follow these steps only if you are using Internet Explorer as your browser.

Some Infor Ming.le and LN Cloud versions might be incompatible with Internet Explorer. If so, a messageis displayed to indicate that your browser is not supported. In that case, before you can run applicationsin Infor Ming.le, you must change your compatibility view settings in Internet Explorer.

1 In the browser, click Tools > Compatibility View Settings.2 Clear the Display intranet sites in compatibility view option.

Allowing popups for browsersEnsure that any browser that is used within Infor Ming.le allows pop-ups. If pop-ups are disabled, thehelp will not work properly.


Configuring your web browser

Chapter 7: Configuring Infor LN CE

The Infor Cloud team has provisioned one or more application companies and tools company 0000.

Note: Consider using an Infor Implementation Accelerator to speed up your implementation.Implementation Accelerators provide overviews, key capabilities, definitions, and configuration of codesand parameters for specific business processes. For more information, contact your Infor representative.

This section assumes that you have already set up the users and roles.

For the application companies that you use, verify that this data has been configured to generate BODs:

• The parameters for BOD messaging in the BOD Parameters (tcbod0100m000) session, such asthe Tenant and Accounting Entity.

• Mappings between the LN codes and the ISO codes in these sessions:• Currencies (tcmcs0102m000). An ISO 4217 code must be specified in the ISO Code field.• Countries (tcmcs0510m000). An ISO 3166 code must be specified in the ISO Code alpha-2

field.• Languages (tcmcs0146m000). An ISO 639 code must be specified in the ISO Code field.• Units (tcmcs0101m000). The ISO mapping is optional.

• Volume units in the Unit Dimensional Relationships (tcmcs1101m000) session, which are usedin the AdvanceShipNotice, ItemMaster, ReceiveDelivery and Shipment BODs. For each unit oftype Length, the required Derived Volume Unit must be specified in this session.

• Blocking reasons in the BOD Publishing group of the Inventory Handling Parameters(whinh0100m000) session, which are used as hold codes in multiple BODs. Ensure that theseblocking reasons have been specified:• Inspection Blocking in the Inbound Inspection Blocking Reason field.• Inspection Blocking in the Outbound Inspection Blocking Reason field.• Quarantine Blocking in the Quarantine Inventory Blocking Reason field.

• Financial master data, for use in financial BODs, in these sessions:• Journal Types (tfbia0119m000)• Map Journal Type to Transaction Type (tfbia0120m000)• BIA Parameters (tfbia0500m000)• Flexible Dimension Definitions (tfbia8501m000)• Fixed Dimension Definitions (tfbia8502m000)• Mapping ERP Dimensions to Reporting Dimensions (tfbia8503m000)• Chart of Accounts (tfgld0508m000)

Note: • To publish LN CE data to ION CE, an initial load of data is required from multiple initial load sessions

in LN CE. See Sending the initial data load on page 51.


Configuring Infor LN CE

• Use the Validate Publishing Data Setup (tcbod0300m000) session to check the status of thedata setup. You can run this session at the beginning and at the end of the configuration for BODpublishing. Run this session at the beginning to view the data that must be specified.

See the section on configuring LN for BOD publishing in the Infor LN Cloud Integration Guide for InforION for additional information about the configuration of Infor LN CE to generate and publish BODs.


Configuring Infor LN CE

Chapter 8: Configuring ERP access 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.

Single Sign OnAll applications in Infor LN Cloud are preconfigured to use Infor Ming.le/IFS to allow single sign on. Noadditional configuration is needed.

Users and rolesBecause Infor Ming.le is the system of record for users, you must set up users in Infor Ming.le. Theusers are then synchronized through BODs with other BOD-enabled applications in the Infor Ming.leportal. After the users are synchronized with your application, you can continue the user setup in eachapplication.

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

• Create users, including manual import of users• Update users• Delete or deactivate users• Reset passwords• Monitor recent user activity and mobile sessions• Manage sessions

Infor Ming.le and LN CE

When you create or update a user in Infor Ming.le, the information associated with that user is used toautomatically set up some user information in LN CE. This association is handled through SyncSecurityUserMaster BODs that are passed through ION CE.


Configuring ERP access through Infor Ming.le

Provisioned and manually added LN CE roles are mapped to security roles in Infor Ming.le. After theroles are set up in LN CE, they are synchronized to Infor Ming.le through the Sync SecurityRoleMasterBOD, so that Infor Ming.le is aware of all possible roles.

Infor Ming.le provides a default Infor-SystemAdministrator role that allows for full access to all applicationsthat are linked to Infor Ming.le. LN CE has an LN Administrator role that allows access to all LN CEsessions. When a user who has the Infor-SystemAdministrator role in Infor Ming.le is synchronized toLN CE, that user automatically has access to all LN CE sessions.

Roles in Infor Ming.leIf your application has security roles defined in Infor Ming.le, you can manage most role assignmentsthrough Infor Ming.le.

The security user integration between Infor Ming.le (IFS) and LN CE is role based. In IFS, you mustassign one of the predefined standard roles to a security user. This makes the user an LN user, andgrants the user access to the LN CE application through Infor Ming.le.

These are the standard roles that you can assign to a security user in IFS:

• Infor-SystemAdministrator - used for overall administrators. Users with this role are superusers in LN CE.

• LN Administrator - used for LN administrators. Users with this role are super users in LN CE.• LN-User - users with this role are normal users in LN CE. Before normal users can access the

LN CE application, additional LN-specific roles must be assigned.

See Configuring user access to LN CE through Infor Ming.le on page 38.

For instructions to set up and assign roles, see the administration information in the online help.

Roles in Infor LN CEInfor LN CE has provisioned roles and configurable roles that are set up in LN CE and then sent toInfor Ming.le through the SecurityRoleMaster BOD. This BOD is defined at the tenant level.

When a user is created in Infor Ming.le and assigned the standard LN User role, LN roles must alsobe assigned to the user to get permissions in LN CE.

For example, to get access as a standard user to LN CE, assign the provisioned FULLDB and FULLSESSroles. To execute basic tasks in LN CE such as change company, assign the DEFAULT role.

Enterprise Modeler roles can also be assigned to users and published. For details, see the Infor LNCloud Integration Guide for Infor Federation Services (IFS).



Configuring user access to LN CE through Infor Ming.leCaution: The Infor Cloud team configures the initial Infor Ming.le system administration user and itsroles, as well as several other required accounts. We recommend that you do not change theconfiguration of this initial system administrator or the other required accounts.

You must add other users in Infor Ming.le before they can access LN CE through Infor Ming.le.

Configuration of LN users happens through centralized user management in Infor Ming.le (IFS). IFSis the System of Record (SOR) for security users.

The security user integration between IFS and LN CE is role based. In IFS, you must assign one ofthe predefined standard roles to a security user. This makes the user a normal user or super user inLN CE, and grants the user access to the LN CE application through Infor Ming.le. The standard rolesthat you can assign to a security user in IFS are: Infor-SystemAdministrator, LNAdministrator, and LN-User.

The cloud environment that is provisioned meets all prerequisites for the integration between LN CEand IFS. For information about the additional data that you must specify before you can use theintegration, refer to these sections:

• ION CE• LN CE tools company• Infor Ming.le• LN CE application companies

ION CEWhen you specify or modify departments, warehouses, TP Projects, sites, companies, or employeesin LN CE, BODs can be sent to ION. To enable LN CE application companies to send AccountingEntity,Location and Person BODs to ION, you must first activate the document flow from LN CE applicationcompanies to Infor Ming.le.

To activate the document flow:

1 In ION Desk, select Connect > Data Flows.2 Review the document flow Mingle-LN Apps. Ensure that connection points have been linked for

the LN CE application companies that you want BODs to send to Infor Ming.le.

3 Activate the document flow Mingle-LN Apps.

Note: The connection point only shows the connection property LN Company. The user name is hiddenin ION Desk. In LN CE, navigate to Tools > User Management > Active Users (ttaad2560m000) toverify that super user ion_ln is used to handle the ION integration process.



LN CE tools company1 Configure a job for Runtime Change Publishing.

The provisioned environment comes with a job that is created in the Start RT Monitor(ttrcp1205m000) session for LN company 0000. The job runs at a daily basis at 20:00. This sessionpublishes any changes to entity types, such as users and roles.

To configure the job:

a In LN CE, select Options > Change Company.b Specify or select company 0000.c Select Tools > Job Management > Job Data > Job Data to start the Job Data

(ttaad5500m000) session.d Search for the job AUTO_RUNTIMECHANGES for the Start RT Monitor (ttrcp1205m000)

session.e Optionally, change periodical execution settings.f From the Actions menu, select Queue Job.

2 Convert users to runtime.Specify how changed user and role data is converted to the runtime data dictionary.

a Select Tools > Application Configuration > Parameters > AMS Parameters to start theAMS Parameters (ttams0100m000) session.

b Select the Automatic Convert to Runtime from IFS check box to automatically convert usersto runtime. Clear this check box if you rather first review and then manually convert users toruntime in LN CE.



3 Generate BOD data for roles.a Select Tools > Integration Tools > Runtime Change Publishing > Publishing > Generate

RT BOD Data to start the Generate RT BOD Data (ttrcp1200m000) session.b Specify all Companies, Roles and Users.c Clear the Trace Mode check box.d Click Generate.

4 Publish provisioned roles from LN CE to Infor Ming.le using the SecurityRoleMaster BOD.a Select Tools > Integration Tools > Runtime Change Publishing > Publishing > Publish

Security Data to start the Publish Security Data (ttbod0200m000) session.



b Select Publish in the Mode group.c Select Use Process/Sync Verb in the Settings group.d Do not select the Logging check box.e Select the SecurityRoleMaster check box.f Click Process.



5 Manually add and publish roles (optional).a Select Tools > User Management > Authorization Management System > Role Data to

start the Role Data (ttams4100m000) session.

The session includes these provisioned AMS roles: DEFAULT, FULLDB, FULLSESS and TOOLS.

b Add your own roles.c Click Convert… to convert the changes to runtime using the Convert Changes to Runtime

DD (ttams2200m000) session.d Either manually run the Start RT Monitor (ttrcp1205m000) session, or wait for the queued

job to be started automatically when the job daemon runs. This will publish added roles fromLN CE to Infor Ming.le using the SecurityRoleMaster BOD.

Note: In the User Data Maintenance Ownership Parameters (ttaad2112m000) session, youcan specify whether AMS Roles are maintained inside or outside LN. If you want to assign LN rolesto users in Infor Ming.le, set the Maintenance Ownership field to Outside LN for the AMS RolesUser Property. If this Maintenance Ownership field is set to LN, assignments made in InforMing.le are not processed to LN CE and permissions are not effective.



6 Set up User Data Default Sets (optional).User Data Default Sets can be assigned to new and existing security users in Infor Ming.le andare used to default several LN-specific user properties. If no LN User Data Default Set is assigned,system defaults are applied upon registration of the user.

a Select Tools > User Management > General User Data > User Data Defaults Sets to startthe User Data Defaults Sets (ttaad2111m000) session.

b Add a new User Data Default Set and specify the Company, Language, Startup Menu, UseClient Language, User Data Template, Default Text Groups Template, and Text GroupAuthorization Template fields.

c Click Save.d Click Update IFS to synchronize the specified codes and descriptions with IFS through an IFS

attribute service.

Infor Ming.le1 Specify the mode for user activation.



a Select User Menu > User Management > Security Administration > Settings > GeneralSettings > Account Creation Status.

b Clear the Create Users In Draft Status check box if you want to automatically activate users.Select the Create Users In Draft Status check box if you rather first review and then manuallyactivate users (all at once).

2 Specify the mode for assigning a user data default set to new users.a Select Configure > Master Data Types > LN User Data Defaults Sets.b Select the Assign to New Users check box if you want to automatically assign a user data

default set to new LN CE users. Clear the Assign to New Users check box if you rathermanually assign an LN user data default set to all existing users or manually specify a list ofusers.

3 Add/import users.a Select User Menu > User Management > Manage > Users.b Add or import users and go to the details of each LN CE user.



See the Infor Ming.le online help for supported import formats and additional information onthe setup of users.

c On the Details tab of a user, specify LN’s Employee Code in the IFS ION-Person ID field. Inthe LN User field, specify LN’s User Code. Use lower case and a maximum of eight characters.Consequently, the SyncSecurityUserMaster BOD is sent to LN CE, which will create users inLN CE.

d On the Security Roles tab, click the Add new item button to add these roles:



• MingleIONEnabled: Required role to receive alerts, tasks and notifications in InforMing.le.

• LN Administrator: Standard role in Infor Ming.le, which is not published by LN throughthe SecurityRoleMaster BOD. Users with this role are users of the type Super User inLN CE, which has all permissions. Only a few users should get this role.

• LN-User: Standard role in Infor Ming.le, which is not published by LN through theSecurityRoleMaster BOD. Users with this role are users of the type Normal User in LNCE. Without further role assignments, the user has no permissions in LN CE. To getpermissions, you must also add the provisioned or manually created LN roles. These LNroles are published from LN CE to Infor Ming.le with the SecurityRoleMaster BOD afterrunning the Start RT Monitor (ttrcp1205m000) session.

You can add these LN roles:

• The provisioned LN roles that are applicable for a user. You can select FULLDB,FULLSESS, DEFAULT and TOOLS. For example, to get access as a normal user to LNCE, assign the FULLDB and FULLSESS roles. To execute basic tasks in LN CE suchas change company, assign the DEFAULT role.

• Manually added roles in LN CE. For example, you can create a Buyer role in LN CEwith access to procurement sessions and tables, and assign that role to users in InforMing.le.

e On the Groups tab, click the Add new item button to add the user to a distribution group. Atleast one user must be assigned to a distribution group to ensure alerts, tasks and notificationsare always received by someone.

f On the ERP Person IDs tab, you can manually add ERP Person IDs by ERP AccountingEntity and Logical ID. However, the list is also populated automatically when you publishPerson BODs from LN CE.

4 Additional steps.• If you configured Infor Ming.le to create users in draft status, you must manually activate users

after creation:a In Infor Ming.le, select User Menu > User Management > Manage > Users.b Select the users and click Activate from the Action list.

• If you configured LN CE to not automatically convert IFS users to runtime, you must manuallyconvert users to runtime in LN CE:a Select Tools > User Management > Authorization Management System > Convert to

DD > Convert Changes to Runtime DD to start the Convert Changes to Runtime DD(ttams2200m000) session.

b Specify these settings:• Select the Users check box.• Select all users to be converted to runtime in the User From-To fields.• Select the Remote Users check box.• Clear the Roles check box.

c Click Convert to Runtime.



LN CE application companies1 Create new employees.

a Select Options > Change Company.b Specify or select an application company (not tools company 0000).c Select Common > People > Employee 360 to start the Employee 360 (bpmdm0101m100)

session.d Add a record for each new employee and specify these settings:

• The code of the employee in the Employee field. This code matches the IFS ION-PersonID in the Infor Ming.le user details.

• The description of the employee in the Description field. This description matches theFirst Name and Last Name in the Infor Ming.le user details.

• The employee’s logon code in the Logon Code field. This code matches the LN User inthe Infor Ming.le user details.

When you save a new employee, the Person BOD is automatically published to Infor Ming.le.

2 Publish accounting entities.a Select Common > BOD Messaging > Publish BODS > Publish Financial Master Data to

start the Publish Financial Master Data (tfbia0200m000) session.b Specify these settings:

• Select Publish in the Mode group.• Specify all LN CE application companies that you want BODs to send in the Company

From-To fields.• Select Use Process/Sync Verb in the Settings group (ensure that no activation policies

or monitors are active in ION CE).• Clear the Logging check box.• Click the Clear All button.

c On the AccountingEntity tab, select the AccountingEntity check box. The check box isdisabled and cleared if there is no subscription for the AccountingEntity BOD. To create thesubscription, ensure that the document flow Mingle-LN Apps is active.

d Click the Process button.

3 Publish locations and persons.To publish location BODs for existing departments, warehouses, TP projects, and sites, and topublish Person BODs for employees from LN CE to Infor Ming.le:

a Select Common > BOD Messaging > Publish BODS > Publish Logistic Master Data tostart the Publish Logistic Master Data (tcbod0200m000) session.

b Specify these settings:

• Select Publish in the Mode group.• Specify all LN CE application companies that you want BODs to send in the Company

From-To fields.• Select Use Process/Sync Verb in the Settings group (ensure that no activation policies

or monitors are active in ION CE).• Clear the Logging check box.• Click the Clear All button.• On the Location tab, select all check boxes.



• On the Person tab, select the Person check box. This step is required only if employeerecords were available already before you activated the document flow Mingle-LN Appsin ION CE. For new employees that you specify, a Person BOD is automatically published.

c Click the Process button.

For details about the integration between LN CE and IFS, see the Infor LN Cloud Integration Guide forInfor Federation Services (IFS).

Configuring additional system administrator access toapplications through Infor Ming.leThe Infor Cloud team initially configures system administrator access for one user between Infor Ming.leand Infor LN Cloud.

Infor Ming.le provides a default Infor-SystemAdministrator role that enables full access to all productsthat are linked to Infor Ming.le When a user has the Infor-SystemAdministrator role in Infor Ming.le,that user automatically has access to all application screens.

You can assign the Infor-SystemAdministrator role to the appropriate users in Infor Ming.le. You canalso assign administrator roles by product to authorize a user access to all functions for a specificproduct.

Verifying user accessTo verify that users were created properly and can access the appropriate sessions in LN CE:

1 Log into Infor Ming.le as a user. The user must belong to a role that is defined as an administratorin both Infor Ming.le and LN CE.

2 From the App Menu, click the LN icon.3 Open the User Data (ttaad2500m000) session and verify this information for several users:

• User matches the First Name and Last Name in Infor Ming.le.• SSO User matches the LN User in Infor Ming.le.• Identity (UUID) matches the IFS ION-Person ID in Infor Ming.le.• Email Address matches the Email Address in Infor Ming.le.

4 Sign out of the application and Infor Ming.le. Close the browser.5 Log into Infor Ming.le and LN CE as a non-administrative user who has access.6 Ensure that you can open any session that the user has authorization to open, and that you cannot

open sessions for which the user is not authorized.



Setting up distribution groupsOptionally, you can set up distribution groups in Infor Ming.le for users who require access to ION CEin order to view or update information or to troubleshoot errors. See the online help.

Distribution groups for LN CE can be imported as part of post provisioning. See Distribution groups onpage 20.

Assign users to the groups as applicable.



Chapter 9: Configuring LN CE to send and receiveBODs in ION

This section describes how to configure Infor LN CE to communicate with ION CE. Integrations betweenthis application and other applications use ION CE to send and receive BODs. For details about aspecific integration, see the appropriate integration guide.

Tasks completed during provisioning and postprovisioningInfor LN Cloud has been set up so that it can generate BODs and place them in a message outboxfrom which Infor ION Connect can retrieve them. The inbound message configuration has also beenset up, so that BODs sent to the applications can be processed.

Understanding how applications connect to IONThe cloud environment includes connection points, which are set up in ION Desk. Connection pointsmust be available for the applications to be able to send documents to ION CE. Connection pointsprovide the information that ION CE uses to connect to an application’s message inbox and outbox.At least one connection point must be defined for each application instance that integrates to ION CE.

For each connection point, the BOD documents are selected that can be sent or received by theapplication instance.

In ION CE, each LN CE company is defined as a separate connection point, with a unique Logical ID.After the ION connection point is activated, the Infor LN Adapter of ION Connect logs on to LN CE andpopulates the Administration (Subscriptions) (tlesb300) table. This table contains all outboundBODs for which a document flow, activation policy or monitor exists.

Real business events, such as data added, updated or deleted in LN CE results in publishing BODswith the Process/Sync Verb, if subscriptions exist.


Configuring LN CE to send and receive BODs in ION

To pass BODs between applications, document flows have been set up between the applicationconnection points. You must activate these document flows. A connection point can be reused inmultiple document flows.

See the section on ION Connect Modeling in the Infor ION Desk User Guide – Cloud Edition for additionalinformation about connection points and document flows.

Publishing BODsYou publish BODs so that ION CE can retrieve them from your message outbox. You can publishBODs for general use by any product that subscribes to the BODs through Infor ION CE. After youperform an initial data load from your application, you verify that data is flowing out of the applicationinto ION CE. For details about a specific integration, see the appropriate integration guide.

For an ION-based integration between Infor LN CE 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.

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 your application to another application, so that the base systemsare synchronized. The BODs are placed in the message outbox, from which Infor ION retrieves themand passes them to the other application.

Sending the initial data loadExisting data can be published from LN CE using these initial load sessions:

• Publish Logistic Master Data (tcbod0200m000)• Publish Logistic Code Definitions A-L (tcbod0200m100)• Publish Logistic Code Definitions M-Z (tcbod0200m200)• Publish LN Message Data (tcbod0200m300)• Publish Order Management Transactional Data (tdbod0200m000)• Publish Planning Transactional Data (cpbod0200m000)• Publish Manufacturing Master Data (tibod0210m000)• Publish Manufacturing Transactional Data (tibod0200m000)



• Publish Warehouse Management Transactional Data (whbod0200m000)• Publish Quality Management Transactional Data (qmbod0200m000)• Publish Service Transactional Data (tsbod0200m000)• Publish People Transactional Data (bpbod0200m000)• Publish Financial Master Data (tfbia0200m000)• Publish Financial Transactional Data (tfbia0210m000)• Publish General Ledger Movement (tfbia8205m000)• Publish Project Data (tpbod0200m000)• Publish Billing Dates (tpbod5230m000)

In each of these initial load sessions, you can select these options in the Settings group box:

• Use Show Verb: Select this option if you want to publish BODs for no real business events. Forexample, for initial load of applications, configuration of additional applications, system failures,failed BOD messages, change of interest, and bugs/enhancements in Infor LN CE. If you selectUse Show Verb, you must also specify the Logical ID(s) of the applications to which BODs are tobe sent. Because alerts and tasks are not created for BODs with the Show verb, we recommendthat you select Use Show Verb when you publish existing data.

• Use Process/Sync Verb: Select this option if you want to publish Sync BODs to all integratedapplications modeled in active ION document flows. You do not want to get alerts and tasks for allpublished data. Therefore, deactivate activation policies, workflows and monitors in ION beforeyou use the Use Process/Sync Verb option, and reactivate after running the initial load sessions.

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

Publishing additional initialization dataFor LN CE, the BODs are published when the business event happens. However, for performancereasons, some financial documents and inventory counts are published in separate sessions.

Publishing financial documentsUse the Publish Financial Documents (tfbia8210m000) session to publish these documents:

• Invoice• SupplierInvoice• PayableTransaction• ReceivableTransaction• SourceSystemJournalEntry

Use the Publish General Ledger Balances (tfbia8211m000) session to publishSourceSystemGLMovement messages.

These sessions can be manually run or in a job mode.



Publishing inventory countsUsually, balance information is sent at quiet moments. Use the Publish InventoryCount Messages(whinr1448m000) session to publish InventoryCount BOD messages for combinations of warehouseand item. This session can be manually run or in a job mode.

Note: A cycle counting order in LN CE does not result in an InventoryCount BOD. The results of thecycle counting order are published with the InventoryAdjustment BOD.

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

Verifying that BODs are generated1 Determine what user actions generate certain BODs.2 Perform those user actions in Infor LN CE.3 In ION Desk, use OneView or other ION Desk functions to review the messages.

If messages are not displayed in ION Desk, check the message outbox in the application to see ifBODs were generated but were not retrieved by ION. To verify if BODs were generated, you cancheck this information in LN CE:

• If a BOD is created in the outbox, in table tlesb100. If an ION connection point is active, theBOD is immediately processed by ION and is removed from the outbox.

• If the first free number is increased for the new BOD, in table tlesb200.• If subscriptions exist in table tlesb300. Subscriptions represent the BODs that LN CE sends

to the applications. Run the Validate Publishing Data Setup (tcbod0300m000) session withthe Subscriptions check box selected to view the publishing subscriptions that are available.

• The setting of the Prevent BOD Publishing check in the BOD Parameters (tcbod0100m000)session. This check box must be cleared.

• The outcome after running the BOD Monitor (bobod1200m100) session.• The outcome after running the BOD Alerter (bobod1200m200) session.

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

Verifying that ION receives dataTo verify that ION is receiving BODs from LN CE, perform these actions in ION Desk:

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



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

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



Chapter 10: Configuring workflows and ION messagesfor LN CE

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

ION messagesThis table shows the types of ION messages:

DescriptionType

Alerts are generated by Event Management in Infor OS or by aPulseAlert BOD. An alert is a business notification or exception indicat-ing that something out of the ordinary has happened in the flow of ap-plication documents.

Alert

Tasks are generated by Workflow or by a PulseTask BOD. A task is anactivity that must be completed within a defined period of time. Whenthe task is generated by Workflow, it suspends the execution of theworkflow until the task is completed. When a task is completed, theuser's response is sent back to Workflow to resume execution of theworkflow.

Task

Notifications are generated by Workflow or by a PulseNotification BOD.A notification is similar to a task, but does not require immediate useraction. A notification does not suspend the execution of the workflow.

Notification

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

In ION Desk, the business administrator can create alarm templates.

After the templates are activated, mobile users can use the templatesto create alarms in the ION Alarms mobile application. The alarm creatorcan specify the distribution list for the resulting alert. See the applicableInfor ION Alarms Mobile Application User Guide.

Users receive the alert on their Infor Ming.le page, in the Infor Ming.lemobile application, or by email.

Alarm


Configuring workflows and ION messages for LN CE

ION monitors, workflows and activation policiesMonitors and workflow models are set up by the Infor Cloud team for BODs published by Infor LN CE.Optionally, you can customize the standard ION content to suit specific customer requirements.

When ION receives a Sync BOD from LN CE that meets the conditions modeled in the monitors, themonitors create alerts and activation policies trigger workflows to create tasks and notifications.

When ION receives a Process Workflow BOD from LN CE, document authorization workflows aretriggered to create tasks and notifications.

Created alerts, tasks, and notifications are distributed to Infor Ming.le users and can be emailed.Distribution is modeled in ION Desk and can be to specific named users, to distribution groups, or topersons coming from BODs.

The standard Infor LN ION Monitors and Workflow Models use distribution groups. Distribution groupsare configured in Infor Ming.le where you assign users to distribution groups without modifying themonitors or workflow models themselves. Each distribution group must include at least one user toensure alerts, tasks and notifications are always received by someone. See the information aboutconfiguring user access for tasks and alerts in the Infor ION Desk User Guide – Cloud Edition.

The standard Infor LN ION Monitors and Workflow Models also use persons defined in BODs. Forexample, LN CE populates the AssignedPerson/IDs/ID field in the Opportunity BOD with the Assignedto field from the Opportunity (tdsmi1110m000) session in LN CE. Persons in BODs are employeesspecified in the Employees-General (tccom0101m000) session.

The LN CE employee is linked to the Infor Ming.le user if the Employee field from theEmployees-General (tccom0101m000) session is specified in the IFS ION-Person ID field on theInfor Ming.le user.

Document authorizationDocument authorization is the process wherein changes made in Infor LN CE must be approved usingthe ION workflow, so that these changes are available for general use.

If workflow approval logic applies to a business object in LN CE, a Workflow Status field is displayedin the related LN CE session. This Workflow Status field is displayed alongside any existing statusfield. It does not replace, but it complements the usual approval, activation, or validation logic.

You can activate a business object for document authorization in the Object ConfigurationManagement module of LN CE. You use this module to model a business object. A business objectis called an Object Type and consists of application tables. When an object type is activated fordocument authorization, changes to these tables are initially made in the draft mode. After approval,these changes will be globally available.

The changes to an object are classified as a certain action. For each action, you can specify whetherexternal approval using the ION Workflow is required or whether the change can be processed withoutapproval.

When a change is made to an object that requires document authorization, the user must submit thechanges. When an object is submitted, a check is performed to determine whether the action is enabled.


Configuring workflows and ION messages for LN CE

When the action is enabled, a workflow is started in ION CE by publishing the Process Workflow BODfrom LN CE. When the action is not enabled, the data change is processed in LN CE, without approval.

The workflow results in an approval or a rejection. If approved, the changes are made available. Ifrejected, the user who changed the object can either revert the change to the original setting or changeand resubmit the object.

Activating ION monitors, workflows, and activationpoliciesTo activate the ION monitors, workflows, and activation policies:

1 In ION Desk, select Monitors & Workflows.2 Select Workflows, review the list of workflows and click Activate for workflows that you want to

generate tasks and notifications. Ensure to activate document authorization workflows beforesubmitting approval requests from LN CE.

3 Select Activation Policies and click Activate for activation policies that start or cancel activatedworkflows.

4 Select Monitors, review the list of monitors and click Activate for monitors that you want to generatealerts. For some monitors, it is required to start the related workflow first.

After activation, LN CE application companies will start sending BODs to ION CE for the documentslisted on the activated Activation Policies and the activated Monitors.

Activating document authorizationIn the provisioned environment, the standard model specified in the Models (ttocm0101m000) sessionof LN CE has already been imported, validated and deployed for the tenant's package combination.This deployment still has the Free status and must be activated.

To activate the deployment in LN CE:

1 Select Tools > Integration Tools > Object Configuration Management > Deployments byPackage Combination.The Deployments by Package Combination (ttocm0111m000) session