cloud integration guide for infor ion workflows and monitors · 2/14/2020 · the material...

Infor LN Cloud Integration Guide for Infor ION Workflows and Monitors

Copyright © 2020 Infor

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

Infor LN Cloud Integration Guide for Infor ION Workflows and Monitors | 3

Contents

About this guide ................................................................................................................................. 11

Intended audience ......................................................................................................................... 11

Organization ................................................................................................................................... 11

Related documents ........................................................................................................................ 11

Contacting Infor.............................................................................................................................. 12

Chapter 1 Overview ....................................................................................................................... 13

Chapter 2 Environment ................................................................................................................. 16

Chapter 3 Activation ...................................................................................................................... 17

Integration LN – Infor Ming.le user management .......................................................................... 17 ION........................................................................................................................................... 17 LN tools company .................................................................................................................... 17 Infor Ming.le ............................................................................................................................. 19 LN application companies ....................................................................................................... 21

Alerts and workflows ...................................................................................................................... 22 ION........................................................................................................................................... 22 LN ............................................................................................................................................ 23

Infor Ming.le social objects ............................................................................................................ 23

Chapter 4 Customization............................................................................................................... 24

Customize BODs ........................................................................................................................... 24 UserArea .................................................................................................................................. 24 LN Studio ................................................................................................................................. 24 LnMessage .............................................................................................................................. 24

Customize monitors, workflows, activation policies ...................................................................... 25

Customize document authorization workflows .............................................................................. 25

Customize drill backs ..................................................................................................................... 26

Contents

4 | Infor LN Cloud Integration Guide for Infor ION Workflows and Monitors

Chapter 5 Monitors ........................................................................................................................ 27

Accounting Entity added ................................................................................................................ 27

Anticipated payment due ............................................................................................................... 28

Billing cycle due ............................................................................................................................. 28

Call assigned ................................................................................................................................. 29

Call due .......................................................................................................................................... 29

Call overdue ................................................................................................................................... 30

Call unassigned ............................................................................................................................. 30

Chart of accounts addition ............................................................................................................. 31

Claim closed .................................................................................................................................. 31

Claim high amount ......................................................................................................................... 32

Contract purchase expire............................................................................................................... 33

Contract sales expire ..................................................................................................................... 33

Contract service expire .................................................................................................................. 34

Corrective action plan late ............................................................................................................. 35

Corrective action plan task late ..................................................................................................... 35

Corrective action plan task not started .......................................................................................... 36

Customer activated ........................................................................................................................ 36

Customer return with high value .................................................................................................... 37

Dimension addition ........................................................................................................................ 38

Enterprise unit addition .................................................................................................................. 39

Fiscal period closed for general ledger ......................................................................................... 39

Fiscal period open ......................................................................................................................... 40

Generate order planning aborted .................................................................................................. 40

Inspection order pending ............................................................................................................... 41

Invoice addition with high value ..................................................................................................... 41

Location addition ............................................................................................................................ 42

Maintenance notification not assigned .......................................................................................... 43

Maintenance notification not handled ............................................................................................ 43

Non-conforming material report addition ....................................................................................... 44

Non-conforming material report closure ........................................................................................ 45

Non-conforming material report late .............................................................................................. 45

Contents


Non-conforming material report waiver completed ....................................................................... 46

Opportunity activity due ................................................................................................................. 46

Opportunity due ............................................................................................................................. 47

Payable transaction blocked .......................................................................................................... 48

Planned distribution order due ....................................................................................................... 48

Planned production order due ....................................................................................................... 49

Planned purchase order due ......................................................................................................... 50

Production order blocked ............................................................................................................... 50

Production order complete ............................................................................................................ 51

Production order due ..................................................................................................................... 52

Production order projected late ..................................................................................................... 52

Production order release ............................................................................................................... 53

Project activity overdue .................................................................................................................. 53

Project activity start overdue ......................................................................................................... 54

Project bid expires ......................................................................................................................... 55

Project contract ceiling amount ..................................................................................................... 55

Project contract deliverable due .................................................................................................... 56

Project contract expires ................................................................................................................. 57

Project contract funding amount reached ...................................................................................... 57

Project contract installment amount shortage ............................................................................... 58

Project contract installment due .................................................................................................... 58

Project contract line billing due ...................................................................................................... 59

Project contract zero amount ......................................................................................................... 60

Project contract zero line amount .................................................................................................. 60

Project loss making ........................................................................................................................ 61

Project milestone overdue ............................................................................................................. 62

Purchase contract line called quantity not completely covered .................................................... 62

Purchase contract line usage does not match expected usage.................................................... 63

Purchase invoice matched ............................................................................................................ 64

Purchase invoice registered .......................................................................................................... 64

Purchase schedule line not received ............................................................................................. 65

Purchase schedule line only partially received ............................................................................. 66

Contents


Quote expires ................................................................................................................................. 66

Receivable transaction due ........................................................................................................... 67

Receive delivery due ..................................................................................................................... 68

Receive delivery quantity deviates ................................................................................................ 68

Receive delivery received late ....................................................................................................... 69

Requisition addition with high priority ............................................................................................ 70

Requisition addition with high value .............................................................................................. 70

Requisition approved ..................................................................................................................... 71

Requisition rejected ....................................................................................................................... 72

RFQ due ........................................................................................................................................ 72

RFQ expired ................................................................................................................................... 73

Sales credit memo addition with high value .................................................................................. 74

Sales order addition with high priority ........................................................................................... 74

Sales order cancelled .................................................................................................................... 75

Sales order ship to address incomplete ........................................................................................ 76

Sales order with high value ........................................................................................................... 76

Serialized item not assigned .......................................................................................................... 77

Service order activity due .............................................................................................................. 78

Service order activity overdue ....................................................................................................... 78

Service order due .......................................................................................................................... 79

Service order emergency not released ......................................................................................... 79

Service order emergency released................................................................................................ 80

Service order not costed ................................................................................................................ 81

Service order not released ............................................................................................................ 81

Shipment due ................................................................................................................................. 82

Shipment shipped late ................................................................................................................... 83

Supplier addition ............................................................................................................................ 83

Supplier credit memo addition with high value .............................................................................. 84

Supplier invoice addition with high value ....................................................................................... 85

Supplier stage payment late .......................................................................................................... 86

Transaction type addition............................................................................................................... 86

Turnaround time document due .................................................................................................... 87

Contents


Chapter 6 Workflow models ......................................................................................................... 88

Call registered ................................................................................................................................ 88

Claim close .................................................................................................................................... 89

Claim generate supplier claim ....................................................................................................... 89

Claim submit .................................................................................................................................. 90

Company addition .......................................................................................................................... 91

Contract purchase expire............................................................................................................... 91

Contract sales expire ..................................................................................................................... 92

Contract service expire .................................................................................................................. 93

Corrective action plan approved .................................................................................................... 93

Corrective action plan open ........................................................................................................... 94

Corrective action plan submitted ................................................................................................... 94

Corrective action plan task completed .......................................................................................... 95

Customer addition .......................................................................................................................... 96

Finalization error logged ................................................................................................................ 96

Global trade compliance check result ........................................................................................... 97

High value Payable transaction to be paid .................................................................................... 98

Item addition .................................................................................................................................. 98

Maintenance notification addition ................................................................................................ 100

Maintenance notification assigned .............................................................................................. 100

Maintenance notification not handled .......................................................................................... 101

Non-conforming material report assigned ................................................................................... 102

Non-conforming material report submitted .................................................................................. 102

Opportunity lost ............................................................................................................................ 103

Opportunity won ........................................................................................................................... 104

Planning signal............................................................................................................................. 104

Production order complete .......................................................................................................... 105

Production order release ............................................................................................................. 106

Production order rework .............................................................................................................. 106

Project bid convert contract ......................................................................................................... 107

Purchase invoice registered ........................................................................................................ 108

Requisition approval .................................................................................................................... 108

Contents


Requisition conversion ................................................................................................................. 109

RFQ due ...................................................................................................................................... 110

Sales order unblock ..................................................................................................................... 111

Service order release ................................................................................................................... 112

Supplier addition .......................................................................................................................... 112

Chapter 7 Document authorization ............................................................................................ 114

Adjustment line ............................................................................................................................ 114

Billable line ................................................................................................................................... 115

Customer claim line ..................................................................................................................... 115

Cycle count line............................................................................................................................ 115

Global trade compliance check result ......................................................................................... 116

Invoice .......................................................................................................................................... 116

Invoice-from business partner ..................................................................................................... 117

Invoice-to business partner.......................................................................................................... 117

Journal ......................................................................................................................................... 118

Payment batch ............................................................................................................................. 119

Pay-to business partner ............................................................................................................... 119

Pay-to business partner bank accounts ...................................................................................... 120

Physical breakdown change ........................................................................................................ 120

Project .......................................................................................................................................... 121

Project bid .................................................................................................................................... 121

Project contract ............................................................................................................................ 122

Project contract deliverable ......................................................................................................... 122

Project contract line ..................................................................................................................... 123

Project equipment costs .............................................................................................................. 123

Project interim results .................................................................................................................. 124

Project labor costs ....................................................................................................................... 124

Project material costs .................................................................................................................. 125

Project subcontracting costs ........................................................................................................ 125

Project sundry costs .................................................................................................................... 126

Purchase contract ........................................................................................................................ 126

Purchase invoice.......................................................................................................................... 127

Contents


Purchase order ............................................................................................................................ 127

Recurring journal.......................................................................................................................... 128

Register received invoice............................................................................................................. 128

Request to reuse a supplier invoice number ............................................................................... 129

Requisition ................................................................................................................................... 129

Revenue Recognition .................................................................................................................. 130

Sales contract .............................................................................................................................. 130

Sales order ................................................................................................................................... 131

Sales quotation ............................................................................................................................ 131

Service quote ............................................................................................................................... 132

Stage payment ............................................................................................................................. 132

Trade order .................................................................................................................................. 133

Appendix A Infor LN View modeler ............................................................................................ 135

Design time .................................................................................................................................. 135

Runtime ........................................................................................................................................ 136

Example ....................................................................................................................................... 137

Appendix B LnMessage ............................................................................................................... 138

Publishing .................................................................................................................................... 138 Standard content ................................................................................................................... 138 Custom content ..................................................................................................................... 140

ION Desk Modeling ...................................................................................................................... 143 Standard content ................................................................................................................... 143 Custom content ..................................................................................................................... 144

Drill back ...................................................................................................................................... 144 Standard content ................................................................................................................... 145


About this guide

This guide provides information on the event monitors and workflow models that are created specifically for BODs published by Infor LN. Recommendations are given on the process to customize the standard ION content to suit specific customer requirements.

Intended audience This guide is intended mainly for system administrators who manage and customize standard Infor LN ION content, or who must troubleshoot or trace back tasks or alerts to Infor LN.

Organization This document includes:

• Activation and customization process. • Descriptions of the monitors and workflow models, which describe why and how ION content for

Infor LN is created. • Appendices on view modeler (drill backs) and LnMessage BOD.

Related documents You can find these documents in the product documentation section of the Infor Support Portal, as described in "Contacting Infor" on page 12:

• Infor ION Desk User Guide - Cloud Edition • Infor ION Development Guide - Cloud Edition • Infor LN Cloud Integration Guide for Infor ION

About this guide


• Infor LN Cloud Configuration Guide for Infor ION Workflows and Monitors (Infor Support Portal, KB article 1915676)

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

If we update this document after the product release, we will post the new version on the Infor Support Portal. To access documentation, select Search > Browse Documentation. We recommend that you check this portal periodically for updated documentation.

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

https://concierge.infor.com/

Overview


Chapter 1 Overview 1

This chapter provides an overview of the complete integration of Infor LN with ION Process.

In ION Desk, each Infor LN company is defined as a separate Connection Point, with a unique Logical ID.

When the ION Connection Point is activated, the Infor LN Adapter of ION Connect logs on to Infor LN and populates the Administration (Subscriptions) table (tlesb300). This table contains all outbound BODs for which a document flow, activation policy or monitor exists.

Real business events, such as data added, updated or deleted in LN, results in publishing BODs with the Process/Sync Verb, when subscriptions exist.

Existing (historic) data can be published from LN through so-called initial load sessions. Each of these sessions has a setting available with the options Use Show Verb and Use Process/Sync Verb.

When ION receives a Sync BOD that meets modeled conditions, monitors create alerts and activation policies trigger workflows to create tasks and notifications.

When ION receives a Process Workflow BOD, document authorization workflows are triggered to create tasks and notifications.

Use Show Verb is for publishing BODs, if there are no real business events such as initial loading of applications, configure additional applications, system failures, failed BOD messages, change of interest, and bugs/enhancements in Infor LN. Use Show Verb requires that you specify the Logical ID(s) of the applications to which BODs must be sent. ION does not create alerts and tasks for BODs with the Show verb. It is therefore recommended that you select the default Use Show Verb option when publishing existing data. Use Process/Sync Verb results in publishing Sync BODs to active workflows and monitors in ION and to all integrated applications modeled in active ION document flows. You will get alerts and tasks for all published existing data that meets modeled conditions. Therefore, specify Use Process/Sync Verb only in exceptional situations where all connected applications must receive BODs and all active ION event monitoring and workflow must be executed.

Overview


Created alerts and 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 to persons coming from BODs.

The standard Infor LN ION Monitors and Workflow Models use distribution groups. Distribution groups are configured in Infor Ming.le where you assign users to distribution groups, without modifying the monitors or workflow models themselves. Each distribution group must include at least one user to ensure alerts, tasks and notifications are always received by someone.

The standard Infor LN ION Monitors and Workflow Models also uses persons defined in BODs.

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

The Object Configuration Management module is located in the LN menu under Tools > Integration Tools > Object Configuration Management. You use this module to model an application object. An application object is called an Object Type and consists of application tables. When an object type is activated for document authorization, changes to these tables are initially made in the draft mode. After approval, these changes are globally available. The changes to an object are classified as a certain action. For each action, you can specify whether external approval using the ION Workflow is required or whether the change can be available without approval. When a change is made for an object that requires document authorization, the user must submit the changes. When an object is submitted, a check is performed to determine whether the action is enabled. If the action is enabled, a workflow in ION is started by publishing the Process Workflow BOD from Infor LN. When the action is not enabled, the data change is available in Infor LN, without approval. The workflow results in an approval or a rejection. If approved, the changes are made available. If rejected, the user who changed the object can either revert the change to the original settings or change and resubmit the object.

See “Features” in the technical notes document for the porting set, in KB article 22923520.

For example, LN populates the AssignedPerson/IDs/ID field in the Opportunity BOD with the Assigned to field in the Opportunity (tdsmi1110m000) session in LN. Persons in BODs are Employees in the Infor LN (tccom0101m000) session.

The LN Employee is linked to the Infor Ming.le user when the Employee field from the LN Employees (tccom0101m000) session is specified in the IFS Person ID field on the Infor Ming.le user.

Overview


Alerts and tasks will show the main information about the LN entities, as published through BODs, and offer drill back to LN. Drill back is a mechanism to navigate to the LN session to see all information on the LN entity and possibly execute processes that the task or alert informed you about. Drill backs are listed in the view modeler.

View Modeler

ION invokes a URL that specifies the view name and view parameters. The view is located in the View Modeler (tlvwm0601m000) session in LN. Conditions are defined which describe, based on view parameters, the Infor LN session that must be started. Filters are defined which describe, based on view parameters, the data that must be displayed in the Infor LN session.

Standard views are loaded when the view modeler is started or when a drill-back or drill-to is executed. The delivered Infor LN ION Monitors and Workflows use the standard views to drill back to LN sessions. The standard views have already been uploaded in Infor Ming.le in the provisioned environment. You can customize views. For details see “Infor LN View modeler” on page 135.

Environment


Chapter 2 Environment 2

The cloud environment that is provisioned meets all ION and LN prerequisites to use the Infor LN ION content.

All post configuration steps must be executed as outlined in Infor LN Cloud Configuration Guide for Infor ION Workflows and Monitors.

Prerequisites for Infor LN ION Cloud Edition Content pack v13:

• Infor Ming.le 12.0 Cloud Edition. • Infor ION 12.0 Cloud Edition. • Infor LN 10.5.1 Cloud Edition. Prerequisites for Infor LN ION Cloud Edition Content pack v14: • Infor Ming.le 12.0.15 Cloud Edition. • Infor ION 12.0 Cloud Edition with ION Registry Content Pack 2.13.6. • Infor LN 10.6 Cloud Edition. Prerequisites for Infor LN ION Cloud Edition Content pack v15: • Infor Ming.le 12.0.15 Cloud Edition. • Infor ION 12.0 Cloud Edition with ION Registry Content Pack 2.13.6. • Infor LN 10.7 Cloud Edition. Prerequisites for Infor LN ION Cloud Edition Content pack v16: • Infor Ming.le 12.0.15 Cloud Edition. • Infor ION 12.0 Cloud Edition with ION Registry Content Pack 2.13.6. • Infor LN Cloud 2019.09. Prerequisites for Infor LN ION Cloud Edition Content pack v17: • Infor Ming.le 12.0 Cloud Edition • Infor ION 12.0 Cloud Edition • Infor LN Cloud 2020.03 Your environment is ready for activation and customization.

Activation


Chapter 3 Activation 3

This section describes the process to activate the content in LN, Infor Ming.le and ION. However, the section does not describe the process to connect Infor LN with other applications or to publish data to any other connected applications.

Integration LN – Infor Ming.le user management

ION Activate document flow from LN application companies to Infor Mingle:

1. In ION Desk, select Model > Connect > Connection Points.

2. Review the document flow Mingle-LNApps. Ensure that connection points are linked for the LN application companies that you want BODs to send to Infor Ming.le.

3. After review Activate the document flow Mingle-LNApps.

Activation will enable LN application companies to send AccountingEntity, Location and Person BODs to ION.

When changes are made in LN to departments, warehouses, TP Projects, companies, and employees, BODs are published when saving data. Existing data requires an initial load described in the steps below.

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

LN tools company 1 Start the job for Runtime Change Publishing

The provisioned environment comes with a job, created in LN company 0000 for the Start RT Monitor (ttrcp1205m000) session, to run at a daily basis at 20:00. This session publishes any changes with regards to users, roles, etc.

Activation


a) Select Options > Change Company.

b) Type or select company 0000.

c) Select Tools > Job Management > Job Data > Job data (session ttaad5500m000).

d) Look up the job AUTO_RUNTIMECHANGES for the Start RT Monitor (ttrcp1205m000) session.

e) Optionally change periodical execution settings.

f) Select Queue Job.

2 Automatic convert users to runtime (optional)

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

b) Set Automatic Convert to Runtime from IFS to Yes. Set to No if you rather first review and then manually convert users to runtime in LN.

3 Publish role data in LN

a Generate RT BOD Data

Before you can publish, you first must generate data.

Select Tools > Integration Tools > Runtime Change Publishing > Publishing to start the Generate RT BOD Data (ttrcp1200m000) session.

• Select all companies, sessions, roles and users.

• Do not run in trace mode.

• Press Process button.

b Select Tools > Integration Tools > Runtime Change Publishing > Publishing to start the Publish Security Data (ttbod0200m000) session.

• Set Mode Publish.

• Set Settings Use Process/Sync Verb.

• Set Logging No.

• Set SecurityRoleMaster Yes.

• Press Process button.

This will publish provisioned roles from LN to Ming.le using the SecurityRoleMaster BOD.

4 Manually add roles (optional)

a) Select Tools > User Management > Authorization Management System > Role Data to start the Role Data (ttams4100m000) session.

The session shows the provisioned AMS roles DEFAULT, FULLDB, FULLSESS and TOOLS.

b) Add your own roles and Convert Changes to Runtime DD.

Activation


c) 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 from LN to Infor Ming.le using the SecurityRoleMaster BOD.

Important: AMS Roles can be maintained in LN or Outside LN. This can be configured in the User Data Maintenance Ownership Parameters session (ttaad2112m000). For AMS Roles, use the setting “Outside LN“, if you want to assign LN’s roles to users in Infor Ming.le user management. If the setting for AMS Roles is “LN“, then assignments made in Infor Mingle will not be processed in LN and permissions are not effective.

5 Set up User Data Defaults Sets (optional)

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

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

b) Add a new record and specify Company, Language, Use Client Language, Startup Menu and templates for User Data, Default Text Groups and Text Group Authorization.

c) Save and click Update IFS to synchronize the specified codes and descriptions with IFS through an IFS attribute service.

Infor Ming.le See the Infor Ming.le online help for supported import formats and additional information on the setup of users. Specific settings for LN users are described below.

1 Automatic activate users (optional)

Infor Ming.le’s User Management has a setting to create users in draft status.

a) Select User Menu > User Management > Security Administration > General Setting > Account Creation Status

b) Set Create Users In Draft Status to No. Set to Yes if you rather first review and then manually activate users (all at once).

2 Automatic assign User Data Defaults Set to new users (optional)

a) Select Configure > Master Data Types > LN User Data Defaults

b) Set Assign to New Users to Yes to automatically assign a User Data Defaults Set to new LN users. Set to No if you rather manually assign a LN User Data Defaults Set to all existing users or manually specify a list of users.

3 Add/import users

a) In Infor Ming.le, select User Menu > User Management > Manage > Users.

b) Add or import users and go to details of each LN user:

Activation


c) On the Details tab, in the IFS Person ID field, specify LN’s Employee Code. In the LN User field, specify LN’s User Code. Use lower case and max 8 characters. This results in sending the SyncSecurityUserMaster BOD to LN which will create users in LN.

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

• MingleIONEnabled

This role is required to receive alerts, tasks and notifications in Infor Ming.le.

• LN-Administrator

Standard role in Infor Mingle (not published by LN through the SecurityRoleMaster BOD).

Users with this role will become users of type Super User in LN, which has all permissions. Only a few users should get this role.

• LN-User

Standard role in Infor Mingle (not published by LN through the SecurityRoleMaster BOD).

Users with this role will become users of type Normal User in LN. Without further role assignments, the user has no permissions in LN. To get actual permissions, you must select either provisioned roles or manually added roles.

o The provisioned roles FULLDB, FULLSESS, DEFAULT and TOOLS

For example, to get access as a normal user to LN, assign the FULLDB and FULLSESS roles. To execute basic tasks in LN, such as change company, assign the DEFAULT role.

o The manually added roles in LN. These roles were published to Infor Ming.le through the Start RT Monitor session.

For example, you can create a Buyer role in LN with access to Procurement sessions and tables and assign that role to users in Infor Mingle.

e) On the Distribution Groups tab, click the Add new item button to add LN’s distribution groups. Each distribution group must include at least one user to ensure alerts, tasks and notifications are always received by someone.

f) On the ERP Person IDs tab, you can manually add ERP Person IDs by ERP Accounting Entity and Logical ID. However, the list will be populated automatically when you publish Person BODs from LN.

4 Additional steps (optional)

• If you configured Infor Ming.le to create users in draft status, you must manually activate users after creation:

• In Ming.le, select User Menu > User Management > Manage > Users.

• Select the user(s) and click Activate via the Action menu.

• If you configured LN to not automatically convert IFS users to runtime, you must manually convert users to runtime in LN.

Activation


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:

o Select the Users check box

o Select all users to be converted to runtime in the User From-To fields

o Select the Remote Users check box

o Clear the Roles check box

c) Click Convert to Runtime.

LN application companies 1 Create new employees

a) Select Options > Change Company:

b) Type 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 employee and specify these settings:

• Employee = IFS Person ID matching the Infor Ming.le user details

• Description = First Name and Last Name matching the Infor Ming.le user details

• Logon Code = LN User matching the Infor Ming.le user details

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

2 Publish accounting entities

a) In LN, select Common > BOD Messaging > Publish BODs > Publish Financial Master Data to start the Publish Financial Master Data (tfbia0200m000) session


• Select Publish in the Mode group.

• Specify all LN 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).

• •Clear the Logging check box.

• •Click the Clear All button.

Activation


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

d) Click the Process button.

3 Publish locations and persons

This step will publish location BODs for existing departments, warehouses, TP projects, companies, and publish Person BODs for employees from LN to Infor Ming.le.

a) In LN, select Common > BOD Messaging > Publish BODs > Publish Logistic Master Data to start the Publish Logistic Master Data (tcbod0200m000) session.


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

From-Tofields. • 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

employee records were available already before you activated the document flow Mingle-LN Apps in ION. For new employees that you specify, a Person BOD is automatically published.

c) Click the Process button.

Alerts and workflows

ION Activate ION monitors, workflows, and activation policies:

1. In ION Desk, select Model > 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 before submitting approval requests from LN.

3. Select Activation Policies, click Activate for activation policies that start or cancel activated workflows.

4. Select Monitors, review the list of monitors and click Activate for monitors that you want to generate alerts. Some monitors will require to start a related workflow first.

Activation


Activation will result in LN application companies starting to send BODs to ION for the documents listed on the activated Activation Policies and Monitors.

LN Activate LN document authorization:

In the provisioned environment, the standard model specified in the Models (ttocm0101m000) session of LN 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:

1. Select Tools > Integration Tools > Object Configuration Management > Deployments by Package Combination to start the Deployments by Package Combination (ttocm0111m000) session.

2. Navigate to Deployed Actions, review and Enable workflows for companies that you activated in ION (in the previous step).

3. Activate the deployment, this includes an automatic full convert to the runtime data dictionary. After activation, LN application companies will send Workflow BODs to ION and start the document authorization workflows (starting with DA_).

Infor Ming.le social objects Configure and activate the ION message listener (optional):

The integration between LN and Infor Ming.le user management does not require an active message listener. However, if you want to use for example Social Objects in Infor Ming.le, you must configure and activate the provisioned Infor Ming.le message listener.

Warning: Activation will result in LN application companies sending all BODs that LN can publish to Infor Ming.le. The list of BODs is defined on the LN connection point.

• In ION Desk, select Model > Connect > Message Listener.

• Open the Ming.le message listener.

• On the Documents tab, select the Sync check box.

• Activate the message listener.

Note: A new data lake connector will replace the message listener in the future, which will allow you to define specific BODs that must be published to Infor Ming.le for usage in for example Social Objects.

Customization


Chapter 4 Customization 4

This section describes the customization process for the ION content.

Customize BODs ION can create alerts or workflow tasks for any BOD that is registered.

ION comes with meta data for the standard BODs (Sales order, ItemMaster, Shipment, etc). The provisioned environment also has the LN specific BODs (LnPlanningSignal, LnClaim, LnMessage, etc).

UserArea Each BOD comes with a UserArea section that can be used to transport additional fields that are not included in the standard BODs. Additional fields can be standard fields, customer defined fields, or complete customizations.

In LN, select Tools > Application Extensibility > Extensions to model additional fields in the Extensions (ttext1500m000) session

LN Studio You can use LN Studio to customize standard BODs and LN-specific BODs, or create new custom BODs. New custom BODs must be registered in ION.

LnMessage The LnMessage BOD includes a set of generic fields and a UserArea. You can use the LnMessage when standard BODs cannot be used, you do not want to develop a new custom BOD, nor customize a standard BOD.

In LN, select Tools > Application Extensibility > Extensions to add publish triggers for the LNMessage BOD in the Extensions (ttext1500m000) session.

Customization


For details and examples see Appendix B.

Customize monitors, workflows, activation policies You can customize monitors, workflows, and activation policies in ION Desk by copying the delivered standard content and prefixing the new name with something else than “LN_”. Choosing a different prefix is required to separate standard content from custom content.

Note: Updating customized content based on new standard content is not automated. It is a manual process to compare new standard content with customized content and to make the required changes to the customized content.

Customize document authorization workflows To customize document authorization in Infor LN and ION:

1 In Infor LN, select the Models (ttocm0101m000) session. Note that the standard model is already imported, validated and deployed in the provisioned environment.

2 Review the content.

3 Select the Mappings (ttocm0105m000) session and add additional attributes as required.

4 Validate and deploy the model.

5 Select the Deployed Actions (ttocm0112m000) session and specify the required action for each object. You can start this session using the Deployments by Package Combination (ttocm0111m000) session.

6 In ION, review the content.

7 In the workflow definition, add the additional attributes you created in Step 3. Note: Root table related attributes must be added as workflow parameters. Mapping elements related to child tables must be added to the workflow structure.

8 If you require different definitions for different companies, duplicate the workflow.

9 In Infor LN, select the Deployed Actions (ttcom0112m000) session to link the non-standard workflows to the appropriate company.

10 Extend or change the workflow with additional tasks or other distributions, as required.

11 Activate the workflow.

12 In Infor LN, select the Deployments by Package Combination (ttocm0111m000) session to validate and activate the workflow in Infor LN.

See the online help in Infor LN.

Customization


Customize drill backs To customize the standard views or to create new custom views that you can link to tasks in ION, use the View Modeler (tlvwm0601m000) session in LN:

1. Create a custom view set.

2. Either copy a standard view and paste in the custom view set or create a completely new custom view.

3. Model view parameters.

4. Model sessions to drill back to.

5. Simulate the drill back in the view modeler to verify expected behavior.

6. Export the custom view set to an xml file. Select For ION in the export session.

7. Upload the custom view set xml file in Infor Ming.le. Select User Menu > Admin Settings > Manage Drillbacks. Click Upload Drillback XML to upload the custom drill backs for LN.

8. Link custom views to workflows in ION Desk.

Monitors


Chapter 5 Monitors 5

This chapter describes the monitors, which are used to create alerts.

The naming convention used for standard monitors is LN_noun_event. For example, LN_Opportunity_Due.

Do not use the LN prefix for customizations made to standard content or for customer-defined content.

Each table describes when the monitor is introduced, the Infor LN release, the required BOD schema, ION version, the purpose, monitor name, application document, conditions/rule, action, if workflow can be started from the alert, distribution, and the drill back.

Accounting Entity added Introduced in Content pack v7

Supported from Infor LN FP7

BOD schema 2.9.0 (ION 11.0)

Purpose Generate an alert when an accounting entity is created (ERPLNBD-708).

Monitor LN_ AccountingEntity_Added

Application document AccountingEntity

Conditions/rule Action code is Add.

Action Alert is sent when an accounting entity is added.

Start Workflow None

Distribution LN_Finance distribution group

Drill back Infor LN Companies (tcemm1170m000) session.

Monitors


Anticipated payment due Introduced in Content pack v3



Purpose Generate an alert when an anticipated payment of the type Check is due (ERPLNBD-337).

Monitor LN_Message_AnticipatedPayment_Due

Application document LnMessage

Conditions/rule • Message type is AnticipatedPayment. • Status is Open. • 10 days after the planned clearing date. You can customize the

threshold.

Action Alert is sent when the anticipated payment is 10 days overdue.

Start Workflow None


Drill back Infor LN Anticipated Payments/Receipts (tfcmg2504m000) session.

Billing cycle due Introduced in Content pack v8

Supported from Infor LN 10.3

BOD schema 2.9.1 (ION 11.0.1)

Purpose Generate an alert for the billing clerk when a billing cycle is due (ERPLNBD-954).

Monitor LN_Message_BillingDate_BillingDue


Conditions/rule • Message type is BillingDate. • Next billing date must be within one day. You can customize the

threshold.

Action Alert is sent when a billing cycle is due.

Start Workflow None

Distribution LN_Finance distribution group.

Monitors


Drill back Infor LN Create Aggregated Billable Cost (tppin1200m000) session.

Note: The LnMessage BOD must be published using the Publish Billing Dates (tpbod5230m000) session. Specify the By Billing Cycle in this session. The recommended publishing frequency is two times the billing frequency. To automate publishing, assign the session to a job that runs periodically.

Call assigned Introduced in Content pack v4



Purpose Calls logged must be workflow-enabled (ERPLNBD-434).

Monitor LN_CustomerCall_Assigned

Application document CustomerCall

Conditions/rule • Status is Assigned. • Support Engineer is not blank.

Action Alert is sent when a call is assigned.

Start Workflow None

Distribution Support engineer

Drill back Infor LN Call (tsclm1100m000) session.

Call due Introduced in Content pack v4



Purpose Generate an alert when a call must be transferred to service execution (ERPLNBD-859).

Monitor LN_CustomerCall_Due


Conditions/rule Status is Open, Hold, Assigned, InProcess, or Transferred.

Monitors


One day before the latest solution finish time

Action Generate an alert when a call is due in one day. You can customize the threshold.

Start Workflow None

Distribution • Support engineer. • If the value of the support engineer field is null, the LN_Service

distribution group is used.


Call overdue Introduced in Content pack v4



Purpose Generate an alert when a service call is overdue based on the agreed response time (ERPLNBD-858).

Monitor LN_CustomerCall_Overdue


Conditions/rule • Status is Open, Hold, Assigned, InProcess, or Transferred. • One minute after the latest solution finish time.

Action Alert is sent when a call is overdue.

Start Workflow None

Distribution Manager of the LN_Service distribution group.


Call unassigned Introduced in Content pack v9



Purpose Calls logged must be assigned within a specified time (ERPLNBD-1044).

Monitors


Monitor LN_CustomerCall_Unassigned


Conditions/rule • Status is Open. • One day after the reported time.

Action Alert is sent when a call is not assigned within one day.

Start Workflow None

Distribution LN_Service distribution group


Chart of accounts addition Introduced in Content pack v1



Purpose Generate an alert when a ledger account is created (ERPLNBD-334).

Monitor LN_ChartOfAccounts_Addition

Application document ChartOfAccounts

Conditions/rule Action code must be Add.

Action Alert is sent when a ledger account is added.

Start Workflow None


Drill back Infor LN Chart of Accounts (tfgld0508m000) session.

Claim closed Introduced in Content pack v13


BOD schema Infor LN 13.0 (ION 12.0)

Purpose Generate an alert when a customer claim is closed (LND2-14233).

Monitors


Monitor LN_Claim_Closed

Application document LnClaim

Conditions/rule • Agency role is Customer, which indicates that the claim is a customer claim.

• Status is Closed.

Action Alert is sent when a customer claim is closed.

Start Workflow None


Drill back Infor LN Customer Claim (tscmm1600m000) session.

Claim high amount Introduced in Content pack v13



Purpose Generate an alert when an high amount is claimed on a customer claim (LND2-14233).

Monitor LN_Claim_HighAmount



• Status is Free, Modified, or Pending Approval. • Total claimed amount in local currency must be greater than 1000. You

can customize the threshold. • Local currency is EUR.

Action Alert is sent when a customer claim is created, modified, or submitted with a total claimed amount greater than 1000 EUR.

Start Workflow None



Monitors


Contract purchase expire Introduced in Content pack v3



Purpose Generate an alert when a purchase contract is reaching the expiration date and requires a renewal (ERPLNBD-433).

Monitor LN_Contract_Purchase_Expire

Application document Contract

Conditions/rule • Agency role is Customer, which indicates that the contract is a purchase contract.

• Contract header status is Open. • Contract line status is Open. • Contract line expiry date must be within 14 days. You can customize

the threshold.

Action Alert is sent when a purchase contract is reaching the expiration date.

Start Workflow LN_Contract_Purchase_Expire

Distribution • Buyer.

• If the value of the Buyer field is null, the LN_Purchase distribution group is used.

Drill back Infor LN Purchase Contract – Lines (tdpur3600m000)

Note: Event monitoring and workflow only evaluate Sync BODs, which are published when contracts are created, modified, or deleted. Existing contracts can be published using the Publish Order Management Transactional Data (tdbod0200m000) session. To monitor existing contracts, specify Use Process/Sync Verb in this session.

Contract sales expire Introduced in Content pack v1



Purpose Generate an alert when a sales contract is reaching the expiration date and requires a renewal (ERPLNBD-432).

Monitors


Monitor LN_Contract_Expire


Conditions/rule • Agency role is Supplier, which indicates a sales contract. • Contract header status is Open. • Contract line status is Open. • Contract line expiry date is within 14 days. You can customize the

threshold.

Action Alert is sent when a sales contract is reaching the expiration date.

Start Workflow LN_Contract_Sales_Expire

Distribution LN_Sales distribution group

Drill back Infor LN Sales Contract – Lines (tdsls3600m000) session.

Note: Event monitoring and workflow only evaluate Sync BODs, which are published when contracts are created, modified, or deleted. You can use the Publish Order Management Transactional Data (tdbod0200m000) session to publish existing contracts. To monitor existing contracts, specify Use Process/Sync Verb in this session.

Contract service expire Introduced in Content pack v4



Purpose Contracts are reaching the expiration date and require renewal, and the workflow must be enabled (ERPLNBD-433).

Monitor LN_ServiceContract_Expire

Application document ServiceContract

Conditions/rule • Contract header status is Open. • Contract line expiry date must be within 14 days. You can

customize the threshold.

Action Alert is sent when a service contract is reaching the expiration date.

Start Workflow LN_ServiceContract_Expire

Distribution Sales representative

Drill back Infor LN Service Contracts (tsctm3100m000) session.

Monitors


Note: The distribution is for the sales representative, but the sales representative on the service contract in Infor LN is optional.

Corrective action plan late Introduced in Content pack v6

Supported from Infor LN 10.2.1


Purpose Generate an alert when the planned due date on the corrective action plan has passed (ERPLNBD-1012).

Monitor LN_CorrectiveActionPlan_Late

Application document CorrectiveActionPlan

Conditions/rule • Status is not Closed. • One day after the due date. You can customize the threshold.

Action Alert is sent when the corrective action plan is late.

Start Workflow None

Distribution Approver and Owner.

Drill back Infor LN Corrective Action Plan (qmcpl1100m900) session.

Corrective action plan task late Introduced in Content pack v6



Purpose Generate an alert when the due date on the corrective action plan task has passed (ERPLNBD-1012).

Monitor LN_CorrectiveActionPlan_TaskLate


Conditions/rule • Task status is Unapproved, Open, or Active. • One day after the due date of the task. You can customize the

threshold.

Monitors


Action Alert is sent when the corrective actions for one or more tasks are delayed.

Start Workflow None

Distribution Corrective action plan owner and task owner.


Corrective action plan task not started Introduced in Content pack v6



Purpose Generate an alert when the corrective action plan task status is not In progress and the task start date has passed (ERPLNBD-1012).

Monitor LN_CorrectiveActionPlan_TaskNotStarted


Conditions/rule • Task status is Unapproved or Open. • One day after the start date of the task. You can customize the

threshold.

Action Alert is sent when the corrective action for one or more tasks did not start on time.

Start Workflow None

Distribution Corrective action plan owner and task owner.


Customer activated Introduced in Content pack v2



Purpose Generate an alert when a customer is created (ERPLNBD-355).

Monitor LN_Customer_Activated

Monitors


Application document CustomerPartyMaster

Conditions/rule Customer status changes from Prospect to Open.

Action Alert is sent when a customer (sold-to business partner) is activated.

Start Workflow None


Drill back Infor LN Sold-to Business Partner (tccom4110s000) session.

Note:

• Each Infor LN company has a single company currency, also called the local currency. Amounts are published in both the transaction currency and the company currency. The company currency is published.

• The monitor does not send an alert for new customers. The LN_CustomerPartyMaster_Addition workflow sends an alert when a customer is added.

Customer return with high value Introduced in Content pack v1



Purpose Generate an alert when a high-value sales credit memo is created with conditions, for example, over amount threshold (ERPLNBD-354).

Monitor LN_CustomerReturn_HighValueEUR

Application document CustomerReturn

Conditions/rule • Status is not Closed. • BaseCurrencyAmount of type ExtendedAmount must be greater than

1000. You can customize the threshold. • BaseCurrency is EUR.

Action • A sales credit memo is created for a returned sales order. When a returned sales order is confirmed, a CustomerReturn BOD is generated.

• Manual creation of sales credit memos is not monitored. • The customer return BOD is published before the (sales) invoice BOD.

Start Workflow None

Distribution • LN_Sales distribution group. • As the return is a credit on revenue that is already recognized. This

group usually includes the accounting manager and the sales manager.

Monitors


Drill back Infor LN Sales Order – Lines (tdsls4100m900) session.

Note:

• Each Infor LN company has a single company currency, also called local currency. Amounts are published in both the transaction currency and the company currency. The company currency is published in the base currency section of the BOD and is monitored.

• Multiple company currencies are used only in complex environments. A single company currency is commonly used across all Infor LN companies, and a single monitor with a threshold in the company currency can be used to monitor all companies.

• The limitation is that CustomerReturn BODs from Infor LN companies with a company currency, other than EUR, do not generate alerts. This monitor does not convert amounts into EUR. For example, to monitor other currencies, you can customize this monitor to use USD.

• In ION you can create a model to alert the “manager of”, for example, the manager of the internal sales representative. You can set up managers for the users in the “Active Directory” application that IFS reads from.

Dimension addition Introduced in Content pack v2



Purpose Generate an alert when an analysis dimension is created (ERPLNBD-347).

Monitor LN_CodeDefinition_DimensionAddition

Application document CodeDefinition

Conditions/rule • Action code is Add. • ReportingSlot is not blank. • ListID is not DIMENSIONS.

Action Alert is sent when a general ledger dimension is added.

Start Workflow None


Drill back None

Note:

• The ReportingSlot field value is specified for general ledger dimension types and dimensions, as defined in the Dimensions (tfgld0510m000) session.

• ListID is DIMENSIONS for dimension types.

Monitors


Enterprise unit addition Introduced in Content pack v3



Purpose Generate an alert when an enterprise unit is created (ERPLNBD-709).

Monitor LN_Message_EnterpriseUnit_Addition


Conditions/rule • Message type is EnterpriseUnit. • Action code is Add.

Action Alert is sent when an enterprise unit is added.

Start Workflow None

Distribution LN_MasterData distribution group

Drill back Infor LN Enterprise Unit (tcemm0630m000) session.

Fiscal period closed for general ledger Introduced in Content pack v3



Purpose Generate an alert when a general ledger is closed (ERPLNBD-360).

Monitor LN_Message_FiscalPeriod_GeneralLedgerClosed


Conditions/rule • Message type is FiscalPeriod. • General ledger status changes into Closed.

Action Alert is sent when the fiscal period is closed for the General Ledger module.

Start Workflow None


Drill back Infor LN Period Status (tfgld0107m000) session.

Monitors


Fiscal period open Introduced in Content pack v3



Purpose Generate an alert when a fiscal period is not closed after X-days, when compared to the specified period end date. (ERPLNBD-343)

Monitor LN_Message_FiscalPeriod_Open


Conditions/rule • Message type is FiscalPeriod. • Status of AccountsPayable, AccountsReceivable, CashManagement,

Integrations, or GeneralLedger is Open. • 30 days after the period end date. You can customize the threshold.

Action Alert is sent when the fiscal period is not closed for 30 days after the period end date, for all modules.

Start Workflow None


Drill back Infor LN Period Status (tfgld0107m000) session.

Generate order planning aborted Introduced in Content pack v14



Purpose Generate an alert when generate order planning is aborted.

Monitor LN_Message_GenerateOrderPlanning_Aborted


Conditions/rule Message Type is GenerateOrderPlanningAborted.

Action Alert is sent when an order planning run is aborted.

Start Workflow None

Distribution • Planner of plan item causing abort

Monitors


• If the value of planner field is null, the LN_Planning distribution group is used.

Drill back Infor LN Statistics Generate Order Planning (cprrp8100m000) session.

Inspection order pending Introduced in Content pack v8



Purpose Generate an alert when an inspection order is not completed after X-days, from the date of creation (ERPLNBD-1024).

Monitor LN_InspectionOrder_Pending

Application document InspectionOrder

Conditions/rule • Status is Draft, Printed, or Open. • 7 days after the order date. You can customize the threshold.

Action Alert is sent when an inspection order requires follow up, when the order is not executed for 7 days.

Start Workflow None

Distribution LN_Quality distribution group

Drill back Infor LN Order Inspection (qmptc1620m000) or Storage Inspection (qmptc2120m100) sessions.

Invoice addition with high value Introduced in Content pack v2



Purpose Generate an alert when a sales invoice is created with conditions, for example, over $xxx. (ERPLNBD-351).

Monitor LN_Invoice_AdditionHighValueEUR

Application document Invoice

Monitors


Conditions/rule • BaseCurrencyAmount of TotalAmount type is greater than 1000. You can customize the threshold.

• BaseCurrency is EUR. • Status is not Proforma.

Action Alert is sent if an invoice amount is greater than 1000 EUR.

Start Workflow None


Drill back Infor LN Open Entry Details (tfacr2525s000) session.

Note:

• Proforma invoices are published for shipments but are excluded in this monitor. Only commercial invoices are monitored.

• Each Infor LN company has a single company currency, also called local currency. Amounts are published in both the transaction and the company currency. The company currency is published in the base currency section of the BOD and is monitored.

Multiple company currencies are only used in complex environments. A single company currency is commonly used across all Infor LN companies, and a single monitor with a threshold in the company currency can be used to monitor all companies.

The limitation is that Invoice BODs from Infor LN companies, with a company currency other than EUR, do not generate alerts. This monitor does not convert amounts to EUR. To monitor other currencies, you can customize this monitor to use a different currency, for example, USD.

Location addition Introduced in Content pack v1



Purpose Generate an alert when a new location is created (ERPLNBD-363).

Monitor LN_Location_Addition

Application document Location

Conditions/rule • Action code is Add. • Type is not Site or Manufacturing.

Action Alert is sent when a department (location of type Office) or warehouse (location of type Warehouse) is added.

Start Workflow None

Monitors



Drill back Infor LN Departments (tcmcs0165s000) or Warehouses (tcmcs0103s000) sessions.

Note: Work centers are published as the Location of the type Site, and also the department for the work center is published as the Location of the type Office. However, the type Site is excluded to prevent two alerts for a new work center.

Maintenance notification not assigned Introduced in Content pack v5



Purpose Generate an alert when a maintenance notification is not assigned (ERPLNBD-936).

Monitor LN_Message_MaintenanceNotification_NotAssigned


Conditions/rule • MessageType is MaintenanceNotification. • Status is Free. • Seven days after the maintenance notification was created. You can

customize the threshold. • The value of the Assigned To field is null.

Action Alert is sent when, fora maintenance notification created seven days ago, no person is assigned for the maintenance activity.

Start Workflow LN_Message_MaintenanceNotification_NotHandled


Drill back Infor LN session tscfg3110m000 Maintenance Notifications

Maintenance notification not handled Introduced in Content pack v5



Monitors


Purpose Generate an alert when a maintenance notification is not handled (ERPLNBD-936).

Monitor LN_Message_MaintenanceNotification_NotHandled


Conditions/rule • MessageType is MaintenanceNotification. • Status is Free. • Seven days after the maintenance notification is created. You can

customize the threshold. • The value of the Assigned To field is specified.

Action Alert is sent when a maintenance notification that is assigned requires follow up because no action is initiated for seven days.

Start Workflow LN_Message_MaintenanceNotification_NotHandled

Distribution Assigned To

Drill back Infor LN Maintenance Notifications (tscfg3110m000) session.

Non-conforming material report addition Introduced in Content pack v6



Purpose Generate an alert when non-conforming material report is closed (ERPLNBD-1011).

Monitor LN_DefectiveMaterialNotice_Addition

Application document DefectiveMaterialNotice


Action Alert is sent when a non-conforming material report is added.

Start Workflow None

Distribution • Owner. • Material Review Board Owner when Owner is blank. • If the values of the Owner and Material Review Board Owner field are

null, the LN_Quality distribution group is used.

Drill back Infor LN Non-Conforming Material Reports (NCMR) (qmncm1100m000) session.

Monitors


Non-conforming material report closure Introduced in Content pack v6



Purpose Generate an alert when a non-conforming material report is closed (ERPLNBD-1011).

Monitor LN_DefectiveMaterialNotice_Closure


Conditions/rule • Status is Dispositioned, Closed, or Canceled. • Status changes.

Action Alert is sent when a non-conforming material report is dispositioned, closed, or canceled.

Start Workflow None

Distribution • Reporter. • If the value of the Reporter field is null, the LN_Quality



Note: Distribution is linked to the employee, for a user that is listed in the Reported By field.

Non-conforming material report late Introduced in Content pack v6



Purpose Generate an alert when non-conforming material report is delayed (ERPLNBD-1011).

Monitor LN_DefectiveMaterialNotice_Late


Conditions/rule • Status is Open, Submitted, or Assigned. • One day after the planned review date.

Action Alert is sent when the planned review date has passed.

Monitors


Start Workflow None

Distribution • Owner and Reporter. • If the values of the Owner and Reporter field are null, the

LN_Quality distribution group is used.


Note: Distribution is linked to the employee, for the user listed in the Reported By field.

Non-conforming material report waiver completed Introduced in Content pack v6



Purpose Generate when an alert when the waiver receipt field is completed for non-conforming material report (ERPLNBD-1011).

Monitor LN_DefectiveMaterialNotice_WaiverCompleted


Conditions/rule • Status is Assigned or Dispositioned. • Receipt date exists.

Action Alert is sent when the waiver receipt date is completed on the non-conforming material report.

Start Workflow None

Distribution Owner


Opportunity activity due Introduced in Content pack v10



Monitors


Purpose Generate an alert when an opportunity activity is overdue or almost due (LND2-217).

Monitor LN_Opportunity_Activity_Due

Application document Opportunity

Conditions/rule • Opportunity status is In Process. • Due date must be within three days. You can customize the

threshold. If due date is not specified, the start date is used. • Status of the Activity of type Task is Not Started, In Process,

Waiting, or Deferred or status of activity of type Appointment or Call is Planned.

Action When an opportunity activity is overdue or almost due, action by the sales person is required.

Start Workflow None

Distribution Assigned to person

Drill back Infor LN Opportunity (tdsmi1610m000) session.

Note:

• Infor LN publishes the Opportunity BOD when activities are added, changed, or deleted only when staging is switched on for OpportunityBOD (bosmi010) in the BOD Implementation Registration (bobod1100m000) session and when you subsequently run the Publish Staged BODs (bobod2200m000) session.

• Activity type is not included as an attribute because the BOD field Opportunity\OpportunityHeader\SalesTask@type is added in BOD schema 2.12.1.

Opportunity due Introduced in Content pack v1



Purpose Generate an alert when an opportunity is overdue or almost due (ERPLNBD-488).

Monitor LN_Opportunity_Due


Conditions/rule • Decision date must be within three days. You can customize the threshold.

• Status is Open.

Monitors


Action When an opportunity is logged and overdue or almost due, a follow up by the sales person may be required.

Start Workflow None


Drill back Infor LN Opportunity (tdsmi1610m000) session.

Note: The Opportunity BOD field DecisionDateTime is populated using the Infor LN field Expected Close Date, which is displayed in the Opportunity (tdsmi1610m000) session.

Payable transaction blocked Introduced in Content pack v9



Purpose Generate an alert when a purchase invoice is blocked for x amount of time (ERPLNBD-955).

Monitor LN_PayableTransaction_Blocked

Application document PayableTransaction

Conditions/rule • Status must be Hold. • Ten days after the invoice date. You can customize the threshold.

Action Alert is sent when an invoice is blocked for ten days, to avoid escalation with the vendor.

Start Workflow None


Drill back Infor LN Open Entry (tfacp2100s000) session.

Planned distribution order due Introduced in Content pack v3



Monitors


Purpose Generate an alert when a planned distribution order is due to start (ERPLNBD-406).

Monitor LN_PlannedTransfer_Due

Application document PlannedTransfer

Conditions/rule • Status must be Planned or FirmPlanned. • Planned start date must be within five days. Threshold can be

customized.

Action Alert is raised when a planned distribution order is scheduled to start in five days, but the order is not confirmed or transferred.

Start Workflow None

Distribution LN_Planning distribution group

Drill back Infor LN Planned Order (cprrp1600m000) session.

Note: In Infor LN, if the Order Release field on the planned order is set to Not to be released, the Hold status is published and no alert is sent.

Planned production order due Introduced in Content pack v3



Purpose Generate an alert when a planned production order is due to start (ERPLNBD-405).

Monitor LN_PlannedProductionOrder_Due

Application document PlannedProductionOrder

Conditions/rule • Status must be Planned or FirmPlanned. • Planned start date must be within five days (threshold can be

customized)

Action Alert is sent when a planned production order is scheduled to start in five days, but order is not confirmed or transferred.

Start Workflow None

Distribution Planner


Note:

Monitors


• Distribution is linked to the planner, however for the planned order this is optional. • In Infor LN, if the Order Release field on the planned order is set to Not to be released, the

Hold status is published and no alert is sent.

Planned purchase order due Introduced in Content pack v3



Purpose Generate an alert when a planned purchase order is due to start (ERPLNBD-216).

Monitor LN_PlannedPurchaseOrder_Due

Application document PlannedPurchaseOrder

Conditions/rule • Status must be Planned or FirmPlanned. • Planned start date must be within five days. Threshold can be

customized.

Action Alert is sent when a planned purchase order is scheduled to start in five days, but order is not confirmed or transferred.

Start Workflow None

Distribution • Planner.

• If the value of the planner field is null, the LN_Planning distribution group is used.


Note: In Infor LN, if the Order Release field on the planned order is set to Not to be released, the Hold status is published and no alert is sent.

Production order blocked Introduced in Content pack v5



Purpose Generate an alert when production order is blocked (ERPLNBD-441).

Monitors


Monitor LN_ProductionOrder_Blocked

Application document ProductionOrder

Conditions/rule • Type must not be Maintenance. • Status is modified to Stopped. • Must be linked to an item of the item type Product.

Action Alert is sent when production order is blocked.

Start Workflow None

Distribution LN_Manufacturing distribution group

Drill back Infor LN Assembly Order (tiasc2100s000) or Production Order (tisfc0101m100) sessions.

Production order complete Introduced in Content pack v5



Purpose Generate an alert when a production order is not completed (ERPLNBD-441).

Monitor LN_ProductionOrder_Complete


Conditions/rule • Type must not be Maintenance. • Status must be Released or Active. • One day after the planned delivery date. Threshold can be customized.

Action Alert is sent to complete the production order

Start Workflow LN_ProductionOrder_Complete



Monitors


Production order due Introduced in Content pack v5



Purpose Generate an alert when a production order is due (ERPLNBD-441).

Monitor LN_ProductionOrder_Due


Conditions/rule • Type must not be Maintenance. • Status must be Planned, Released, or Active. • Planned delivery date or requested delivery date must be within one

day. Thresholds can be customized. • Must have an item of item type Product.

Action Alert is sent when a production order is due.

Start Workflow None



Production order projected late Introduced in Content pack v5



Purpose Generate an alert when the production order is planned later than the requested date, and the specified date is nearby (ERPLNBD-441).

Monitor LN_ProductionOrder_ProjectedLate


Conditions/rule • Type must not be Maintenance. • Status must be Planned, Released, or Active. • Planned delivery date is more than one day after the requested

delivery date. Threshold can be customized. • Requested delivery date must be within one day. Threshold can

be customized.

Monitors


• Must have item of item type Product.

Action Alert is sent when the planned delivery date is after the requested delivery date and the requested delivery date is near.

Start Workflow None



Production order release Introduced in Content pack v5



Purpose Generate an alert when a production order must be released (ERPLNBD-441).

Monitor LN_ProductionOrder_Release


Conditions/rule • Type must not be Maintenance. • Status must be Planned. • Production start date must be within one day. Threshold can be

customized.

Action Alert is sent when a production order must be released.

Start Workflow LN_ProductionOrder_Release



Project activity overdue Introduced in Content pack v5


Monitors



Purpose Generate an alert when the project activity of TP project or PCS project is not finished on the scheduled date (ERPLNBD-450).

Monitor LN_ProjectMaster_ActivityOverdue

Application document ProjectMaster

Conditions/rule • Project status must be Open. • Milestone indicator does not exist or must be False. • The value of the Actual finish date field is not specified. • After the scheduled finish date of the activity.

Action Alert is sent when the activity is overdue.

Start Workflow None

Distribution • For TP projects, Project manager, or LN_Project distribution group.

• For PCS projects, Project Employee, or LN_Project distribution group.

Drill back • For TP projects, Infor LN Project 360 (tppdm6500m100) session. • For PCS projects, Infor LN Project 360 (tipcs0320m000) session.

Project activity start overdue Introduced in Content pack v11.2



Purpose Generate an alert when the project activity of TP project or PCS project is not started on the scheduled date (LND2-9975).

Monitor LN_ProjectMaster_ActivityStartOverdue


Conditions/rule • Project status must be Open. • Milestone indicator does not exist or must be False. • The value of the Actual start date field is not specified. • After the scheduled start date of the activity.

Action Alert is sent when the activity start is overdue.

Start Workflow None

Monitors


Distribution • For TP projects, Project manager, or LN_Project distribution group.

• For PCS projects, Project Employee, or LN_Project distribution group.

Drill back • For TP projects, Infor LN Project 360 (tppdm6500m100) session. • For PCS projects, Infor LN Project 360 (tipcs0320m000) session.

Project bid expires Introduced in Content pack v13



Purpose Generate an alert when a project bid expires (LND2-9987).

Monitor LN_ProjectBid_Expire

Application document ProjectBid

Conditions/rule • Bid status must be Free • Approved for Proposal must be true • Expiry date must be within 5 days (threshold can be customized)

Action Alert is sent when a project bid expires within 5 days.

Start Workflow None

Distribution • Internal and external sales representatives • If the external sales and the internal sales representatives are

not specified, the LN_Sales distribution group is used.

Drill back Infor LN Bid (tpest3600m000) session

Project contract ceiling amount Introduced in Content pack v6



Purpose Generate an alert when the ceiling amount is almost reached for a project contract (ERPLNBD-953).

Monitors


Monitor LN_ProjectContract_CeilingAmount

Application document ProjectContract

Conditions/rule • On the project contract line: • Approved for invoicing amount is greater than 90% of the ceiling

amount. • Ceiling amount is greater than zero.

Action Alert is sent when the invoiced amount is close to the ceiling amount for the project contract line.

Start Workflow None

Distribution • Internal and external sales representatives on header and line. • Contract managers on header and line.

• If the values are null, the LN_Project distribution group is used.

Drill back Infor LN Contract (tpctm1600m000) session.

Project contract deliverable due Introduced in Content pack v6



Purpose Generate an alert when the project contract deliverable is due (ERPLNBD-949).

Monitor LN_ProjectContractDeliverable_Due

Application document ProjectContractDeliverable

Conditions/rule • Line status is Free, Active, or Released to Warehousing. • The deliverable is seven days before the confirmed delivery date.

Action Alert is sent when the project contract deliverable is due within 7 days.

Start Workflow None

Distribution LN_Project distribution group


Monitors


Project contract expires Introduced in Content pack v6



Purpose Generate an alert when the project contract expires (ERPLNBD-952).

Monitor LN_ProjectContract_Expire


Conditions/rule • Project contract header status must be Open. • Project contract line status must be Open. • Project contract line expiry date must be within 14 days

(threshold can be customized).

Action Alert is sent to when the project contract expires within 14 days.

Start Workflow None


• If all the values are null, the LN_Project distribution group is used.


Project contract funding amount reached Introduced in Content pack v9



Purpose Generate an alert when the billing for the project contract line funded amount is almost complete (ERPLNBD-1026).

Monitor LN_ProjectContract_FundingAmountReached


Conditions/rule • Project contract line status must be Open. • 90% of project contract funded amount must be billed (threshold

can be customized).

Action Alert is sent when the funded amount on project contract line is mostly billed.

Monitors


Start Workflow None


• If the values of all the fields are null, the LN_Project distribution group is used.


Note: The Funded Amount field is available in BOD schema 2.10.2 and later. Update the ION registry with the 2.10.2 BOD schema patch to use this monitor.

Project contract installment amount shortage Introduced in Content pack v7



Purpose Generate an alert when the installment schema is incomplete (ERPLNBD-999).

Monitor LN_ProjectContractInstallment_AmountShortage

Application document ProjectContract and ProjectContractInstallment

Conditions/rule • Seven days before the contract line delivery date. • Contract line status is Open. • Installment amount is less than the contract line amount.

Action Alert is sent when the total amount of installments is less than the contract amount.

Start Workflow None

Distribution Contract Manager or LN_Project distribution group.

Drill back • Infor LN Contract (tpctm1600m000) session. • Infor LN Installments (tppin4151m000) session.

Project contract installment due Introduced in Content pack v6

Monitors




Purpose Generate an alert when the project contract installment is due (ERPLNBD-452).

Monitor LN_ProjectContractInstallment_Due

Application document ProjectContractInstallment

Conditions/rule • Invoice does not exist. • Three days before the planned billing date.

Action Alert is sent when the project contract installment is not invoiced.

Start Workflow None


Drill back Infor LN Installments (tppin4151m000) session.

Project contract line billing due Introduced in Content pack v8



Purpose Generate an alert for the billing clerk, who is responsible for a number of project contracts, when billing is due (ERPLNBD-1022).

Monitor LN_ContractLineBillingDate_BillingDue

Application document LnContractLineBillingDate

Conditions/rule Next billing date must be within one day. You can customize the threshold.

Action Alert is sent when a billing is due for project contract line.

Start Workflow None

Distribution • Contract manager.

• If the value of the Contract Manager field is not specified, the LN_Project distribution group is used.

Drill back Infor LN Contract Lines (tpctm1110m000) session

Note: The LnContractLineBillingDate BOD must be published using the Publish Billing Dates (tpbod5230m000) session. Specify By Contract Line in this session. The recommended publishing

Monitors


frequency is 2 times the billing frequency. To automate publishing, you must assign the session to a job that runs periodically.

Project contract zero amount Introduced in Content pack v6



Purpose Generate an alert when contract amount is zero on a fixed price project contract (ERPLNBD-1001).

Monitor LN_ProjectContract_ZeroContractAmount


Conditions/rule • Contract amount is zero. • Contract type is Fixed Price. • Status changes to Open.

Action Alert is sent when a fixed price project is activated that has a contract amount of zero.

Start Workflow None

Distribution • Internal sales representative. • External sales representative if internal sales representative is

blank. • Contract manager.

• If the value of the field is not specified, the LN_Project distribution group is used.


Project contract zero line amount Introduced in Content pack v6



Purpose Generate an alert when contract line amount is zero on fixed price project contract (ERPLNBD-1001).

Monitors


Monitor LN_ProjectContract_ZeroContractLineAmount


Conditions/rule • Line contract amount is zero. • Line contract type is Fixed Price. • Line status is Open. • Header status changes to Open.

Action Alert is sent when a fixed price project is activated with a contract line amount of zero.

Start Workflow None

Distribution • Internal sales representative. • If internal sales representative is blank, then external sales

representative is used. • Contract manager. • If the values of all the fields are not specified, the LN_Project



Project loss making Introduced in Content pack v5



Purpose Generate an alert when project balance is negative (ERPLNBD-453).

Monitor LN_ProjectBalance_LossMaking

Application document ProjectBalance

Conditions/rule • Cost type is blank. • Variance at completion must be less than zero. You can

customize the threshold. • You can customize the condition to estimate during project rather

than at project completion.

Action Alert is sent when project balance is negative.

Start Workflow None


Monitors


Drill back Infor LN Control by Project (tpppc4850m000) session (using the ProjectMonitoring View).

Project milestone overdue Introduced in Content pack v5



Purpose Generate an alert when project milestone is overdue (ERPLNBD-451).

Monitor LN_ProjectMaster_MilestoneOverdue


Conditions/rule • Project status must be Open. • Milestone indicator must be True. • Actual finish date is not specified. • After scheduled finish date.

Action Alert is sent when milestone is overdue.

Start Workflow None

Distribution Project manager

Drill back Infor LN Project 360 (tppdm6500m100) session.

Purchase contract line called quantity not completely covered Introduced in Content pack v9



Purpose Generate an alert when the sum of the called quantities of the corporate purchase contract detail lines deviates more than n% from the total called quantity on the total line (LND-8043).

Monitor LN_Message_PurchaseContractLine_CalledQuantityMismatch


Monitors


Conditions/rule • Message type must be PurchaseContractLine. • "Use Corporate Purchase Contracts" parameter set. • Current date and time past effective date and time. • Line status equal to Active.

Action Alert is sent when a corporate purchase contract total line status is set to Active, and the current date/time is past the effective date/time, and the total line called quantity deviates by 5% or more from the sum of the called quantities of the detail lines.

Start Workflow None

Distribution • Buyer (Contract), Buyer (Contract Line). • If buyers are not defined, the LN_Purchase distribution group is

used.

Drill back Infor LN Purchase Contract Line (tdpur3601m000) session.

Purchase contract line usage does not match expected usage Introduced in Content pack v9



Purpose Generate an alert when the result of the corporate purchase contract line deviates more than n% from the expected result (LND-8043).

Monitor LN_Message_PurchaseContractLine_UsageVersusExpectedUsage


Conditions/rule • Message type must be PurchaseContractLine. • "Use Corporate Purchase Contracts" parameter set. • Current date and time past effective date and time. • Line status equal to either Free or Active.

Action Alert is sent when a corporate purchase contract total line with a status equal to one of the statuses listed under the Conditions/rule, and the current date/time is past the effective date/time, and either the total line result deviates by 50% or more from expected result, or the difference is more than 5% and the expiry date is less than 30 days.

Start Workflow None

Monitors


Distribution • Buyer (Contract), Buyer (Contract Line). • If buyers are not defined, the LN_Purchase distribution group is

used.

Drill back Infor LN Purchase Contract Line (tdpur3601m000) session.

Purchase invoice matched Introduced in Content pack v3



Purpose Generate an alert when invoices are matched but not approved (ERPLNBD-424).

Monitor LN_Message_PurchaseInvoice_Matched


Conditions/rule • Message type must be PurchaseInvoice. • Status must be Matched. • Three days after the invoice was matched. Threshold can be

customized.

Action Alert is sent when the invoices matched three days ago must be approved.

Start Workflow None


Drill back Infor LN Authorize Purchase Invoices (tfacp1142m000) session.

Purchase invoice registered Introduced in Content pack v3



Purpose Generate an alert when invoices are registered, but not matched or approved (ERPLNBD-423).

Monitors


Monitor LN_Message_PurchaseInvoice_Registered


Conditions/rule • Message type must be PurchaseInvoice. • Status must be Registered (also published for transactions

entered). • Three days after the invoice was registered. Threshold can be

customized.

Action Alert is sent when invoices registered three days ago must be matched.

Start Workflow LN_Message_PurchaseInvoice_Registered



Purchase schedule line not received Introduced in Content pack v9



Purpose Generate an alert when purchase schedule line is not received on the planned receipt date (LND-8044).

Monitor LN_Message_PurchaseScheduleLine_NotReceived


Conditions/rule • Message type must be PurchaseScheduleLine. • Current date and time past planned receipt date and time. • Line status is set to either: Created, Approved, Disapproved,

Order Generated, or ASN Received.

Action Alert is sent when a schedule line with a status equal to one of the statuses listed under Conditions/rule, and the current date/time is past the planned receipt date/time.

Start Workflow None

Distribution • Buyer. • If the value of the buyer field is not defined, the LN_Purchase


Drill back Infor LN Purchase Schedule Lines (tdpur3111m000) session.

Monitors


Purchase schedule line only partially received Introduced in Content pack v9



Purpose Generate an alert when purchase schedule line has only been partially received on the planned receipt date (LND-8044).

Monitor LN_Message_PurchaseScheduleLine_PartiallyReceived


Conditions/rule • Message type must be PurchaseScheduleLine. • Current date and time past planned receipt date and time. • Line status equal to Partial Receipt.

Action Alert is sent when a schedule line with a status Partial Receipt, and the current date/time is past the planned receipt date/time.

Start Workflow None

Distribution • Buyer. • If the value of the buyer field is not defined, the LN_Purchase


Drill back Infor LN Purchase Schedule Lines (tdpur3111m000) session.

Quote expires Introduced in Content pack v9



Purpose Generate an alert when a quote expires (ERPLNBD-1041).

Monitor LN_Quote_Expire

Application document Quote

Conditions/rule • CanceledBaseAmount must be greater than 1000 (threshold can be customized).

• BaseCurrency is EUR. • Quote status must be Open. • Quote expiry date must be within 5 days (threshold can be

customized).

Monitors


Action Alert is sent when a quote expires within 5 days.

Start Workflow None

Distribution If the values of the external sales representative and the internal sales representative fields are null, the LN_Sales distribution group is used.

Drill back Infor LN Sales Quotation (tdsls1600m000) session.

Receivable transaction due Introduced in Content pack v4



Purpose Generate an alert when an AR open item is reaching the specified number of days overdue, for example, 60 days (ERPLNBD-346).

Monitor LN_ReceivableTransaction_Due

Application document ReceivableTransaction

Conditions/rule • 30 days after DueDateTime. Threshold can be customized. • Status must be Open, PartialPaid, or Dispute. • Receipt Base Amount must be greater than 100. Threshold can

be customized. • Base Currency must be EUR.

Action Alert user when invoice is 30 days overdue.

Start Workflow None



Note: Each Infor LN company has a single company currency, also called local currency. Amounts are published in both the transaction currency and the company currency. The company currency is published in the base currency section of the BOD and is monitored.

Multiple company currencies are only used in complex environments. Often a single company currency is used across all Infor LN companies and a single monitor with a threshold in the company currency can be used to monitor all companies.

Monitors


Receive delivery due Introduced in Content pack v4



Purpose Genrerate an alert notifying the PO Agent, when a PO is not received on the planned and committed ship date (ERPLNBD-336).

Monitor LN_ReceiveDelivery_Due

Application document PurchaseOrder and ReceiveDelivery

Conditions/rule • Purchase order status must be Open. • Receipts with the status Received that are three days overdue

since the Required Delivery Date.

Action Alert is sent when the receipts for purchase order are three days overdue.

Start Workflow None


• If the value of the Buyer field is null, the LN_Purchase distribution group is used,

Drill back Infor LN Purchase Order – Lines (tdpur4100m900) session.

Receive delivery quantity deviates Introduced in Content pack v5



Purpose Generate an alert when a received quantity deviates from the ordered quantity (ERPLNBD-957).

Monitor LN_ReceiveDelivery_QuantityDeviates


Conditions/rule • Purchase order status must be Open. • Receipts status must be Received. • Received quantity deviates more than 5% from the ordered

quantity. Threshold can be customized.

Action Alert is sent when quantity received deviates from quantity ordered.

Monitors


Start Workflow None




Note: The monitor detects if a single receipt line deviates from the purchase order line by 5% (over received or under received). The monitor does not total the received receipts.

Receive delivery received late Introduced in Content pack v4



Purpose Genrerate an alert notifying the PO Agent, when a PO is not received on the planned and committed ship date (ERPLNBD-336).

Monitor LN_ReceiveDelivery_ReceivedLate


Conditions/rule • Purchase order status must be Open. • Receipt status must be Received. • Actual delivery date must be three days after the required

delivery date.

Action Alert is sent when a receipt for the purchase order is received three or more days late.

Start Workflow None



Drill back • Infor LN Purchase Order – Lines (tdpur4100m900) session. • Infor LN Warehouse Receipts (whinh3512m000) session.

Monitors


Requisition addition with high priority Introduced in Content pack v2



Purpose Genrerate an alert when a new requisition must be delivered and the delivery date is within 14 days (ERPLNBD-401).

Monitor LN_Requisition_AdditionHighPriority

Application document Requisition

Conditions/rule • Required delivery date on the requisition header must be within 14 days. Threshold can be customized.

• Action code must be Add.

Action Alert is sent when a requisition with a requested date within 14 days is added.

Start Workflow None

Distribution • Buyer


Drill back Infor LN Purchase Requisition – Lines (tdpur2600m000) session.

Note: The Required Delivery Date field in the Requisition BOD is populated from the Requested Date field in Infor LN.

Requisition addition with high value Introduced in Content pack v2



Purpose Generate an alert when a requisition, with a high value, is created (ERPLNBD-401).

Monitor LN_Requisition_Addition_HighValueEUR


Conditions/rule • Action code is Add.

Monitors


• BaseCurrencyAmount of type ExtendedAmount must be greater than 1000. You can customize the threshold.

• BaseCurrency is EUR.

Action Alert is sent when a requisition with a value greater than 1000 EUR is added.

Start Workflow None

Distribution • Buyer. • If the value of the Buyer field is not specified, the LN_Purchase





A limitation is that Requisition BODs from Infor LN companies with a company currency other than EUR do not generate alerts. This monitor does not convert amounts to EUR. To monitor other currencies, you can customize this monitor, for example, to use USD.

Requisition approved Introduced in Content pack v1



Purpose Generate an alert notifying the requestor that the requisition is approved (ERPLNBD-691).

Monitor LN_Requisition_Approved


Conditions/rule Status must be Approved.

Action Alert is sent when the requisition is approved.

Start Workflow None

Distribution Requestor of the requisition.


Monitors


Requisition rejected Introduced in Content pack v3



Purpose Generate an alert notifying the requestor that the requisition is rejected (ERPLNBD-691).

Monitor LN_Requisition_Rejected


Conditions/rule Status is Rejected.

Action Alert is sent when the requisition is rejected.

Start Workflow None

Distribution Requestor of the requisition.


RFQ due Introduced in Content pack v1



Purpose Generate an alert when a Request for Quotation (RFQ) is overdue (ERPLNBD-403).

Monitor LN_RFQ_Due

Application document RFQ

Conditions/rule • Return date must be within three days. You can customize the threshold.

• Status is Open or Printed.

Action • The Request for Quotation is due on or before the header return date.

• Three days before the return date, an alert is sent if the RFQ status is not processed in Infor LN.

Start Workflow LN_RFQ_Due


Monitors


• If the value of the Buyer field is null LN_Purchase distribution group is used.

Drill back Infor LN Purchase Request for Quotation – Lines (tdpur1600m000) session.

Note:

• Infor LN publishes one RFQ BOD per supplier. You receive an alert for each supplier. • Alerts are also sent for RFQs with return dates in the past.

RFQ expired Introduced in Content pack v6



Purpose Generate an alert when a Request for Quotation expires (RFQ) (ERPLNBD-1013).

Monitor LN_RFQ_Due


Conditions/rule • Return date must be within three days. You can customize the threshold.

• Status is Open or Printed.


• One day after the return date, an alert is sent if the RFQ status is not processed in Infor LN.

Start Workflow None

Distribution • Buyer. • If the value of the Buyer field is null, the LN_Purchase distribution

group is used.


Note:

• Infor LN publishes one RFQ BOD per supplier. You receive an alert for each supplier. • RFQs with a return date in the past are not excluded and alerts are sent.

Monitors


Sales credit memo addition with high value Introduced in Content pack v2



Purpose Generate an alert when a sales credit memo is created with certain conditions, for example, over $xxx (ERPLNBD-351).

Monitor LN_Invoice_AdditionCreditMemoHighValueEUR

Application document Invoice

Conditions/rule • BaseCurrencyAmount of type TotalAmount must be less than -1000 (threshold can be customized).

• BaseCurrency is EUR. • Status must not be Proforma.

Action Alert is sent when an invoice with an amount less than 1000 EUR is added.

Start Workflow None



Notes:

• Proforma invoices are published for shipments but are excluded in this monitor. Only commercial invoices are monitored.

• Each Infor LN company has a single company currency, also called local currency. Amounts are published in both the transaction currency and the company currency. The company currency is published in the base currency section of the BOD and is monitored.

Multiple company currencies are only used in complex environments. Often, a single company currency is used across all Infor LN companies and a single monitor with a threshold in the company currency can be used to monitor all companies.

A limitation is that Invoice BODs from Infor LN companies with a company currency other than EUR never result in alerts. This monitor does not convert amounts into EUR. To monitor other currencies, you can customize this monitor, for example, to use USD,

Sales order addition with high priority Introduced in Content pack v2

Monitors




Purpose Generate an alert when a new sales order must be delivered soon (ERPLNBD-689).

Monitor LN_SalesOrder_AdditionHighPriority

Application document SalesOrder

Conditions/rule • Required delivery date on the sales order line must be within 14 days. Threshold can be customized.

• Action code must be Add.

Action Alert is sent when a sales order is added with a line that is planned to be received within 14 days.

Start Workflow None



Note: The Required Delivery Date field in the Sales Order BOD is populated from the Requested Date field in Infor LN.

Sales order cancelled Introduced in Content pack v9



Purpose Generate an alert when a sales order is canceled with certain conditions, for example, over $xxx (ERPLNBD-1042).

Monitor LN_SalesOrder_Canceled


Conditions/rule • CanceledBaseAmount must be greater than 1000 (threshold can be customized).

• BaseCurrency is EUR. • Status must be Canceled.

Action Alert is sent when a sales order with an amount greater than 1000 EUR is canceled.

Start Workflow None

Monitors


Distribution If the value of the External sales representative and internal sales representative fields is null, the LN_Sales distribution group is used,


Sales order ship to address incomplete Introduced in Content pack v14

Supported in Infor LN 10.5


Purpose Generate an alert when a sales order is created but ship to address is missing country or city (LND2-18054).

Monitor LN_Message_SalesOrder_ShipToAddress_Incomplete


Conditions/rule MessageType = 'SalesOrderShipToAddress'

Action Alert is sent when sales order is created but ship-to address is incomplete. Default ship-to address was used and user should correct address.

Start Workflow None

Distribution Distribution Group LN_Sales

Drill back None

Sales order with high value Introduced in Content pack v2



Purpose Generate an alert when a sales order is approved with certain conditions, for example, over amount threshold. (ERPLNBD-73).

Monitor LN_SalesOrder_HighValueEUR


Conditions/rule • Status is Open.

Monitors


• BaseCurrencyAmount of type ExtendedAmount must be greater than 1000. You can customize the threshold.

• BaseCurrency is EUR.

Action Alert is sent when the sales order, with an amount greater than 1000 EUR, is approved.

Start Workflow None





A limitation is SalesOrder BODs from Infor LN companies with a company currency other than EUR never result in alerts. This monitor does not convert amounts into EUR. To monitor other currencies, you can customize this monitor for example, to use USD.

Serialized item not assigned Introduced in Content pack v4



Purpose Generate an alert when a preferred engineer is not assigned for the serialized item (ERPLNBD-849).

Monitor LN_ConfiguredAssetMaster_NotAssigned

Application document ConfiguredAssetMaster

Conditions/rule • AssetType is Serial. • AssignedToPerson must be null. • Item is filled.

Action Alert is sent when a preferred engineer is not assigned.

Start Workflow None


Drill back Infor LN Serialized Items (tscfg2100m000) session.

Monitors


Note: Preferred engineer cannot be entered in Infor LN if value of the item is null.

Service order activity due Introduced in Content pack v4, revised in content pack v14

Supported from Infor LN FP7, revision Infor LN 10.6


Purpose Generate an alert on service order and service activity that is scheduled to be finished but not yet completed (ERPLNBD-856).

Monitor LN_ServiceOrder_ActivityDue

Application document ServiceOrder

Conditions/rule • Type is FieldService. • Status is Hold or Approved. • Activity Status is Open or Planned or Approved. • One day before the Planned Finish Time of the activity.

Action Alert is sent one day before the service order activity is due.

Start Workflow None


Drill back Infor LN Service Order – Lines (tssoc2100m100) session.

Service order activity overdue Introduced in Content pack v4, revised in content pack v14



Purpose Generate an alert on overdue service activity (ERPLNBD-851).

Monitor LN_ServiceOrder_ActivityOverdue


Conditions/rule • Type is FieldService. • Status is Hold or Approved.

Monitors


• Activity Status is Open or Planned or Approved. • One minute after the Planned Finish Time of the activity.

Action Alert is sent when service order activity is overdue.

Start Workflow None



Service order due Introduced in Content pack v4, revised in content pack v14



Purpose Generate an alert on Overdue Service Order (ERPLNBD-853).

Monitor LN_ServiceOrder_Due


Conditions/rule • Type is FieldService. • Status is Open or Planned or Approved or Hold. • Three days after the Planned Finish Time.

Action Alert is sent when a service order is not complete three days after the planned finish time.

Start Workflow None



Service order emergency not released Introduced in Content pack v14



Purpose Alert on high priority service order (ERPLNBD-368).

Monitors


Monitor LN_ServiceOrder_EmergencyNotReleased


Conditions/rule • Type is FieldService. • Status is Open or Planned or Hold. • Emergency is True.

Action Alert is sent when an emergency service order is not released.

Start Workflow LN_ServiceOrder_Release

Distribution • Service engineer.

• If the value of service engineer field is null, the LN_Service distribution group is used.


Note: Replaces LN_Message_ServiceOrder_EmergencyNotReleased that was based on LnMessage.

Service order emergency released Introduced in Content pack v14



Purpose Generate an alert on high priority service order (ERPLNBD-368).

Monitor LN_ServiceOrder_EmergencyReleased


Conditions/rule • Type is FieldService. • Emergency must be True. • Status must be Approved.

Action Alert is sent when an emergency service order is released.

Start Workflow None




Note: Replaces LN_Message_ServiceOrder_EmergencyReleased that was based on LnMessage.

Monitors


Service order not costed Introduced in Content pack v4, revised in content pack v14



Purpose Generate an alert on orders completed but not yet invoiced within x number of days (ERPLNBD-857).

Monitor LN_ServiceOrder_NotCosted


Conditions/rule • Type is FieldService. • Status not changed from Completed to Invoiced within three

days.

Action Alert is sent when a service order is completed three days ago, but is not costed.

Start Workflow None



Service order not released Introduced in Content pack v14



Purpose Generate an alert on a service order that is not release yet on the planned start date (ERPLNBD-855).

Monitor LN_ServiceOrder_NotReleased


Conditions/rule • Type is FieldService. • Status is Open, Planned or Hold. • Emergency is False. • Planned Finish Time is within three days. You can customize the

threshold.

Monitors


Action Alert is sent when a service order is not released, but is planned to start in three days.

Start Workflow LN_ServiceOrder_Release


• If the value of service engineer field is not specified, the LN_Service distribution group is used.


Notes:

• Replaces LN_Message_ServiceOrder_NotReleased that was based on LnMessage.

• Emergency service orders are excluded in this monitor because another monitor, the LN_ServiceOrder_EmergencyNotReleased monitor, sends alerts for emergency service orders.

Shipment due Introduced in Content pack v4



Purpose Generate an alert on overdue shipment with threshold (ERPLNBD-417).

Monitor LN_Shipment_Due

Application document Shipment and SalesOrder

Conditions/rule • Sales order status is Approved, Modified, Open, or Hold. • Shipments with Shipped status that are three days after the

Required Delivery Date.

Action Alert is sent when shipments for sales order are three days overdue.

Start Workflow None

Distribution • Internal sales representative. • If the value of the internal sales representative field is null, the

External sales representative is used.

Drill back Infor LN Sales Order - Lines (tdsls4100m900) session.

Note: Distribution is linked to the sales representatives, but the sales representatives on the sales orders in Infor LN are optional.

Monitors


Shipment shipped late Introduced in Content pack v4



Purpose Generate an alert on overdue shipment with threshold (ERPLNBD-417).

Monitor LN_Shipment_ShippedLate

Application document Shipment and SalesOrder

Conditions/rule • Sales order status is Approved, Modified, Open, or Hold. • Shipment status is Shipped. • Actual ship date is three days after the required delivery date.

Action Alert is sent when shipment for sales order is shipped three or more days late.

Start Workflow None

Distribution • Internal sales representative. • If the value of the Internal sales representative field is null, the

External sales representative is used.

Drill back • Infor LN Sales Order - Lines (tdsls4100m900) session. • Infor LN Shipment (whinh4630m000) session.

Note: Distribution is linked to the sales representatives. Sales representatives on sales orders in Infor LN are optional.

Supplier addition Introduced in Content pack v2



Purpose Generate an alert when a supplier is created (ERPLNBD-355).

Monitor LN_Supplier_Addition

Application document SupplierPartyMaster

Conditions/rule Action code must be Add.

Action Alert is sent when a supplier (buy-from business partner) is added.

Monitors


Start Workflow None

Distribution LN_Purchase distribution group

Drill back Infor LN Buy-from Business Partner (tccom4120s000) session.

Supplier credit memo addition with high value Introduced in Content pack v2



Purpose Generate an alert when an AP credit memo is created with certain conditions, for example, over $xxx (ERPLNBD-344).

Monitor LN_SupplierInvoice_AdditionCreditMemoHighValueEUR

Application document SupplierInvoice

Conditions/rule • BaseCurrencyAmount of type TotalAmount is less than 1000. You can customize the threshold.

• BaseCurrency is EUR. • Status is Open.

Action Alert is sent when a supplier invoice with an amount less than 1000 EUR is created.

Start Workflow None


Drill back Infor LN Invoice (cisli2505s000) session.

Notes:

• The TotalAmount (includes Tax Amounts) is used and the ExtendedAmount (without Tax Amounts) is not used.

• SupplierInvoice is published when approved in Infor LN. • Each Infor LN company has a single company currency, also called local currency. Amounts are

published in both the transaction currency and the company currency. The company currency is published in the base currency section of the BOD and is monitored.


Monitors


A limitation is SupplierInvoice BODs from Infor LN companies with a company currency other than EUR never result in alerts. This monitor does not convert amounts into EUR. To monitor other currencies, you can customize this monitor, for example, to use USD.

Supplier invoice addition with high value Introduced in Content pack v2



Purpose Generate an alert when an AP invoice or voucher is created with certain conditions (ERPLNBD-338).

Monitor LN_SupplierInvoice_AdditionHighValueEUR

Application document SupplierInvoice

Conditions/rule • BaseCurrencyAmount of type TotalAmount is greater than 1000. You can customize the threshold.

• BaseCurrency must be EUR. • Status must be Open.

Action Alert is sent when a supplier invoice has an amount greater than 1000 EUR.

Start Workflow None


Drill back Infor LN Invoice (cisli2505s000) session.

Notes:

• TotalAmount (includes Tax Amounts) is used. ExtendedAmount (without Tax Amounts) is not used.

• SupplierInvoice is published when approved in Infor LN. • Each Infor LN company has a single company currency, also called local currency. Amounts are

published in both the transaction currency and the company currency. The company currency is published in the base currency section of the BOD and is monitored.

• Multiple company currencies are only used in complex environments. Often a single company currency is used across all Infor LN companies and a single monitor with a threshold in the company currency can be used to monitor all companies.

• Unless the company currency is EUR, alerts are not created because of the SupplierInvoice BODs from Infor LN companies. This monitor does not convert amounts to EUR. To monitor other currencies, you can customize this monitor to use a different currency, for example, USD.

Monitors


Supplier stage payment late Introduced in Content pack v9



Purpose Generate an alert when supplier stage payment is overdue (ERPLNBD-1038).

Monitor LN_PurchaseOrder_SupplierStagePaymentLate

Application document PurchaseOrder

Conditions/rule • Purchase order status is not Closed. • Supplier stage payment exists. • It is after the due date. • Payment was not released or the released date is after the due

date.

Action Alert is sent when supplier stage payment is not released on time.

Start Workflow None

Distribution Buyer

Drill back Infor LN Purchase Order (tdpur4100m900) session.

Note: Supplier stage payments are published in the PurchaseOrder BOD. To trigger BOD publishing on an insert, update, or delete of supplier stage payments, you must enable staging for the PurchaseOrder BOD and execute the Infor LN session bobod2200m000 Publish Staged BODs.

Transaction type addition Introduced in Content pack v3



Purpose Generate an alert when a new transaction type is added (ERPLNBD-68).

Monitor LN_Message_TransactionType_Addition


Conditions/rule • Message type is TransactionType. • Action code is Add.

Action Alert is sent when a transaction type is created.

Monitors


Start Workflow None


Drill back Infor LN Transaction Types (tfgld0511m000) session.

Turnaround time document due Introduced in Content pack v14



Purpose Generate an alert when a turn around time document is due (LND2-17302).

Monitor LN_Message_TurnaroundTimeDocument_Due


Conditions/rule Message type is TAT Document.

Action Alert is sent when a TAT finish date is near.

Start Workflow None


Drill back Infor LN Turnaround Time Document (tcttm01600m000) session.

Note: In the Turnaround Time Parameters session (tcttm0100m000), the Warn when Remaining TAT is less than parameter is available to specify the number of days.

Workflow models


Chapter 6 Workflow models 6

This chapter describes the activation policies and workflow models.

An activation policy describes the conditions for the BODs and the workflow model that is started or canceled. Workflow models describe when to create task(s) and to whom these tasks must be distributed.

The naming convention used for standard activation policies and standard workflow models is LN_noun_event. For example: LN_Opportunity_Won.

By default, names of the activation policies and workflow models are similar.

Activation policies can be used to start or cancel workflows. Activation policies that cancel a workflow contains the _Cancel postfix. For example, LN_Requisition_Conversion_Cancel.

Do not use the LN prefix for customized standard content or customer-defined content.

The tables describe when the workflow and activation policy are introduced, the Infor LN release, the required BOD schema and ION version, the purpose, workflow and activation policy name, application document, conditions/rule, action, distribution, and drill back.

Call registered Introduced in Content pack v4



Purpose Start workflow when a call is logged (ERPLNBD-434).

Workflow LN_CustomerCall_Registered


Conditions/rule Status is Open.

Action Task is created to notify the user when a call is registered and must be assigned to a support engineer.


Workflow models



Note: The LN_CustomerCall_Registered_Cancel activation policy cancels the workflow when the status is not Open. Therefore, distributed tasks are canceled.

Claim close Introduced in Content pack v13



Purpose Start the workflow when a customer claim must be closed (LND2-14233).

Workflow/Activation Policy

LN_Claim_Close



• Status is not Closed. • Last finish time is within 5 days. You can customize the threshold.

Action Task is created to notify the user when a customer claim must be closed.



Note: The LN_Claim_Close_Cancel activation policy cancels the workflow when the customer claim is Closed. Therefore, distributed tasks are canceled.

Claim generate supplier claim Introduced in Content pack v13



Purpose Start the workflow when a supplier claim must be generated for the customer claim (LND2-14233).


LN_Claim_GenerateSupplierClaim

Workflow models




• Generate supplier claim is True • No supplier claim is generated • It is 5 days after the creation date. You can customize the threshold.

Action Task is created to notify the user when a supplier claim must be generated for the customer claim.



Note: The LN_Claim_GenerateSupplierClaim_Cancel activation policy cancels the workflow when a supplier claim is generated or is no longer required. Therefore, distributed tasks are canceled.

Claim submit Introduced in Content pack v13



Purpose Start the workflow when a customer claim must be submitted (LND2-14233).


LN_Claim_Submit



• Status is Free or Modified. • It is 5 days after the creation date. You can customize the threshold.

Action Task is created to notify the user when a customer claim must be submitted.



Note: The LN_Claim_Submit_Cancel activation policy cancels the workflow when the customer claim status is not Free or Modified. Therefore, distributed tasks are canceled.

Workflow models


Company addition Introduced in Content pack v3



Purpose Start the workflow when a new company is added (ERPLNBD-80).


LN_Message_Company_Addition


Conditions/rule • Message type is Company. • Action code is Add.

Action Task is created to notify the user when a company is added.


Drill back Infor LN Companies (tcemm1170m000) session.

Note: The LN_Message_Company_Addition_Cancel activation policy cancels the workflow when the company is Deleted. Therefore, distributed tasks are canceled.

Contract purchase expire Introduced in Content pack v3



Purpose An alert is generated when the workflow specified on the purchase contract is reaching expiration and must be renewed (ERPLNBD-433).

Workflow LN_Contract_Purchase_Expire


Conditions/rule • Agency role is Customer, which indicates that the contract is a purchase contract.

• Contract header status is Open. • Contract line status is Open. • Contract line expiry date is within 14 days. You can customize the

threshold.

Action Task is created to notify the user when a purchase contract must be renewed.

Workflow models



• If a value for the Buyer field is not specified, the LN_Purchase distribution group is used.

Drill back Infor LN Purchase Contract – Lines (tdpur3600m000) session.

Notes:

• Workflow can be started using an alert that is sent by the LN_Contract_Purchase_Expire monitor.

• Event monitoring and workflow only evaluate Sync BODs, which are published when contracts are entered, modified, or deleted. You can use the Publish Order Management Transactional Data (tdbod0200m000) session to publish existing contracts. To monitor contracts, specify Use Process/Sync Verb in this session.

Contract sales expire Introduced in Content pack v3



Purpose Workflow on the sales contract is set to expire and require renewal (ERPLNBD-433).

Workflow LN_Contract_Sales_Expire


Conditions/rule • Agency role is Supplier, which indicates that contract is a sales contract.

• Contract header status is Open. • Contract line status is Open. • Contract line expiry date is within 14 days. You can customize

the threshold.

Action Task is created to inform the user that a sales contract must be renewed.


Drill back Infor LN Sales Contract – Lines (tdsls3600m000) session.

Note:

• Workflow can be started using an alert that is sent by the LN_Contract_Expire monitor. • Event monitoring and workflow only evaluate Sync BODs, which are published when contracts

are entered, modified, or deleted. You can use the Publish Order Management Transactional

Workflow models


Data (tdbod0200m000) session to publish existing contracts. To monitor contracts, specify Use Process/Sync Verb in this session.

Contract service expire Introduced in Content pack v4



Purpose The contracts are to expire and require renewal, and must be workflow- enabled (ERPLNBD-433).

Workflow LN_ServiceContract_Expire

Application document ServiceContract

Conditions/rule • Contract header status is Open. • Contract line expiry date is within 14 days. You can customize

the threshold.

Action Task is created to inform that a service contract must be renewed.


Drill back Infor LN Service Contracts (tsctm3100m000) session.

Note: Workflow can be started using an alert sent by monitor LN_ServiceContract_Expire.

Corrective action plan approved Introduced in Content pack v6



Purpose Corrective action plan status is changed to Approved, so that the corrective action plan tasks can be started (ERPLNBD-1012).

Workflow LN_CorrectiveActionPlan_Approved


Conditions/rule • Status changes to Approved. • At least one task has the Open or Approved status.

Workflow models


Action Task is created to inform user that the corrective action plan is approved and the corrective action plan tasks can be started.

Distribution Owner


Note: The LN_CorrectiveActionPlan_Approved_Cancel activation policy cancels the workflow when the status is not Approved. Therefore, distributed tasks are canceled.

Corrective action plan open Introduced in Content pack v6



Purpose Corrective action plan can be submitted after details are reviewed, tasks created and relevant non-conformance material reports are linked (ERPLNBD-1012).

Workflow LN_CorrectiveActionPlan_Open


Conditions/rule Status changes to Unapproved.

Action Task is created to inform user that the corrective action plan must be submitted.

Distribution • Owner.

• If the value of the Owner field is null, the LN_Quality distribution group is used..


Note: The LN_CorrectiveActionPlan_Open_Cancel activation policy cancels the workflow when the status is not Unapproved. Therefore, distributed tasks are canceled.

Corrective action plan submitted Introduced in Content pack v6



Workflow models


Purpose Corrective action plan status is set to Ssubmitted so the review and approval process can start (ERPLNBD-1012).

Workflow LN_CorrectiveActionPlan_Submitted


Conditions/rule Status changes to Submitted.

Action Task is created to inform that the corrective action plan must be approved.

Distribution Approver


Note: The LN_CorrectiveActionPlan_ Submitted_Cancel activation policy cancels the workflow when the status is not Submitted. Therefore, distributed tasks are canceled.

Corrective action plan task completed Introduced in Content pack v6



Purpose When a corrective action plan task status is set to Completed, the corrective action plan approver verifies the task, updates the corrective action plan task verification date and changes the relevant corrective action plan task status to Closed. (ERPLNBD-1012).

Workflow LN_CorrectiveActionPlan_TaskCompleted


Conditions/rule Corrective action plan with at least one task with the status Completed.

Action Task is created to inform the user that a corrective action plan task is complete and can be closed.

Distribution Approver


Note: The LN_CorrectiveActionPlan_ TaskCompleted_Cancel activation policy cancels the workflow when the corrective action plan status is Closed. Therefore, distributed tasks are canceled.

Workflow models


Customer addition Introduced in Content pack v1



Purpose Route the screens to the people assigned to add the sold-to data, shipping data, and invoice-to data (ERPLNBD-62 and ERPLNBD-78).


LN_CustomerPartyMaster_Addition

Application document CustomerPartyMaster


Action • Task 1: The sales person reviews the sold-to data can send a notification about the new customer.

• Task 2: The shipping department adds the shipping data. The AR department adds the invoice-to data such as payment terms.

• Task 3: If all tasks are complete, optionally a notification is sent.

Distribution • Task 1:If the value of the external sales representative and the Internal sales representative is null, the LN_Sales distribution group is used.

• Task 2: LN_Warehousing distribution group.

• Task 3: LN_Finance distribution group.

Notification: LN_Sales distribution group.

Drill back • Infor LN Sold-to Business Partner (tccom4110s000) session. • Infor LN Business Partner (tccom4100s000) session (task 2 and

3).

Note: The LN_CustomerPartyMaster_Addition_Cancel activation policy cancels the workflow when the status of the Customer is Deleted. Therefore, distributed tasks are canceled.

Finalization error logged Introduced in Content pack v3



Workflow models


Purpose Start the workflow when the finalization errors must be resolved (ERPLNBD-429).


LN_Message_FinalizationError_Logged


Conditions/rule • Message type must be FinalizationError. • Status is Open if one or more errors exist.

Action Task is created to inform the user that finalization errors occurred for a batch and fiscal year.


Drill back Infor LN Error Log (tfgld1106m000) session.

Note: The LN_Message_Company_Addition_Cancel activation policy cancels the workflow when the status is Deleted, which indicates that all errors are resolved. Distributed tasks are canceled.

Global trade compliance check result Introduced in Content pack v12



Purpose Start the workflow when the global trade compliance check result is set to Failure (LND2-7837).


LN_Message_GlobalTradeCompliance


Conditions/rule • Message type must be GlobalTradeCompliance. • Action code is Add. • Compliance check result must be Failure.

Action Task is created to inform the user that document failed the global trade compliance check.

Distribution Employee linked to user that created check result, else LN_Sales distribution group.

Drill back Infor LN Document Compliance Check Results (tcgtc1510m000) session.

Workflow models


Note: The LN_Message_GlobalTradeCompliance_Cancel activation policy cancels the workflow when the status is Deleted or when the compliance check result is set to Success. Therefore, distributed tasks are canceled.

High value Payable transaction to be paid Introduced in Content pack v2



Purpose Start workflow when invoice can be paid (ERPLNBD-426).


LN_PayableTransaction_HighValueToBePaid

Application document PayableTransaction

Conditions/rule • BaseCurrencyAmount of type TotalAmount must be greater than 1000 (threshold can be customized).

• BaseCurrency must be EUR. • Status is Vouchered or Approved.

Action After invoices are matched and approved, they must be assigned to a user who can pay the invoice.


Drill back Infor LN Open Entry (tfacp2100s000) session.

Notes:

• The LN_PayableTransaction_HighValueToBePaid_Cancel activation policy cancels the workflow, when the status of the Payable Transaction is Hold, Paid, Unapproved, or Deleted. Distributed tasks are canceled.

• PayableTransaction is published when an invoice transaction is finalized.

Item addition Introduced in Content pack v1 (extended in content pack v9)



Purpose Start the workflow for the new product (ERPLNBD-70).

Workflow models



LN_ItemMaster_Addition

Application document ItemMaster

Conditions/rule • Action code is Add. • Revision does not exist.

Action When a new item is specified in general item data, a workflow task is distributed to create the associated sub items. The Workflow is started when a new item is entered. These tasks are created:

• Task 1: When a new item is specified, this task is created: “Check if all required sub items are created.” The user can create tasks to review each of the sub items such as sales data and purchase data. A task to review item sales is created only when the value of the SalesIndicator in the UserArea of the ItemMaster BOD is True. Similar tasks exist for Costing, Freight, Ordering, Planning, Production, Project, Purchase, Service, and Warehousing.

• Task 2: After ordering data is reviewed, a task to review planning data is created.

• Task 3: When all tasks are complete, a task is created to review the item costing data.

Distribution Based on the sub item, tasks are distributed to these distribution groups: LN_Freight, LN_Manufacturing, LN_MasterData, LN_Planning, LN_Project, LN_Purchase, LN_Sales, LN_Service or LN_Warehousing

Drill back • First task: Infor LN Item – General (tcibd0101s000) session. • Next tasks: Infor LN session for the related sub item

Notes:

• The LN_ItemMaster_Addition_Cancel activation policy cancels the workflow when the status of the Item is Deleted. Therefore, distributed tasks are canceled.

• The newly entered items are immediately available for transactions in Infor LN such as sales order entry and production. This workflow creates and distributes tasks to review and complete settings for the new item. The workflow does not prevent the new item from being used in Infor LN.

• Workflow is only activated for new items and not for updates to existing items. When you insert an item without default values and then create sub items, the workflow is not activated.

Workflow models


Maintenance notification addition Introduced in Content pack v5



Purpose Start the workflow when a maintenance notification is added (ERPLNBD-935).


LN_Message_MaintenanceNotification_Addition


Conditions/rule • MessageType is MaintenanceNotification. • Action code is Add. • Status is Free.

Action • Notify customer and service contact that maintenance notification was added.

• Create a task for the preferred engineer to handle the new maintenance notification.

Distribution Notifications: customer contact and serialized item contact. Task: Preferred engineer or LN_Service distribution group when the value for the preferred engineer field is null.


Note: The LN_Message_MaintenanceNotification_Addition_Cancel activation policy cancels the workflow when the status of the maintenance notification is Deleted. Therefore, distributed tasks are canceled.

Maintenance notification assigned Introduced in Content pack v5



Purpose Start the workflow when a maintenance notification is assigned (ERPLNBD-934).


LN_Message_MaintenanceNotification_Assigned


Workflow models


Conditions/rule • MessageType is MaintenanceNotification. • Status is Free. • Assigned to value is specified.

Action Task is created to handle the maintenance notification that is assigned to the user.

Distribution Assigned to


Note: The LN_Message_MaintenanceNotification_ Assigned_Cancel activation policy cancels the workflow when the status of the maintenance notification is not set to Free or when the assigned to field is null. Distributed tasks are canceled.

Maintenance notification not handled Introduced in Content pack v5



Purpose Start the workflow when a maintenance notification is not handled (ERPLNBD-936).

Workflow LN_Message_MaintenanceNotification_NotHandled


Conditions/rule • MessageType is MaintenanceNotification. • Status is Free. • Seven days after the maintenance notification is created. You

can customize the threshold.

Action • If not assigned, the task is created to assign a maintenance notification.

• If assigned, a task is created to handle the maintenance notification.

Distribution If the maintenance notification is not assigned, the LN_Service distribution group is used. If the maintenance notification is assigned, the assigned to person is used.


Workflow models


Note: Workflow can be started from an alert sent by the LN_Message_MaintenanceNotification_NotAssigned and LN_Message_MaintenanceNotification_NotHandled monitors.

Non-conforming material report assigned Introduced in Content pack v6



Purpose Start the workflow when the non-conforming material report is submitted for an assignment (ERPLNBD-1011).


LN_DefectiveMaterialNotice_Assigned


Conditions/rule Status is set to Assigned.

Action • Create a task to generate a disposition for the assigned non-conforming material report.

• Create a task to seek a waiver, from the customer, for the non-conforming material report.

Distribution Owner

Drill back Infor LN Non-Conforming Material Reports (qmncm1100m000) session (NCMR).

Note: The LN_DefectiveMaterialNotice_Assigned_Cancel activation policy cancels the workflow when the status of the defective material notice is not Assigned. Therefore, distributed tasks are canceled.

Non-conforming material report submitted Introduced in Content pack v6



Purpose Start the workflow when the non-conforming material report is submitted for an assignment (ERPLNBD-1011).

Workflow models



LN_DefectiveMaterialNotice_Submitted


Conditions/rule Status changes to Submitted.

Action Create a task to assign the submitted non-conforming material report.

Distribution • Owner and Reporter.

• If the values of the Owner and Reporter field are null, the LN_Quality distribution group is used .

Drill back Infor LN Non-Conforming Material Reports (qmncm1100m000) session (NCMR).

Note: Distribution is to the employee for the user listed in the Reported By field.

The LN_DefectiveMaterialNotice_Submitted_Cancel activation policy cancels the workflow when the status of the defective material notice is not Submitted. Therefore, distributed tasks are canceled.

Opportunity lost Introduced in Content pack v1



Purpose Start the workflow when a lost opportunity is closed (ERPLNBD-486).


LN_Opportunity_Lost


Conditions/rule Status changes to Lost.

Action Workflow for lost opportunity, for example, must be sent to back-office clerk to perform a loss analysis.


Drill back • Infor LN Opportunity (tdsmi1610m000) session. • Infor LN Sold-to Business Partner (tccom4110s000) session.

Notes:

• The LN_Opportunity_Lost_Cancel activation policy cancels the workflow, when the status of the Opportunity is not set to Lost. Distributed tasks are canceled.

Workflow models


• With Infor LN FP7 or later, if the Infor LN status is Dead or Lost, the status Lost is published in the BOD.

Opportunity won Introduced in Content pack v1



Purpose Start a workflow when a won opportunity is closed (ERPLNBD-485)


LN_Opportunity_Won


Conditions/rule Status changes to Won.

Action Workflow for opportunity that is won, for example, route the opportunity to an order administrator to perform the order capture and fulfillment, and to a different user to perform the commissions or win analysis.


Drill back • Infor LN Opportunity (tdsmi1610m000) session. • Infor LN Sold-to Business Partner (tccom4110s000) session.

Note: The LN_Opportunity_Won_Cancel activation policy cancels the workflow, when the status of the Opportunity is not set to Won. The distributed tasks are canceled.

Planning signal Introduced in Content pack v1



Purpose Start workflow for exception messages (planning signals) (ERPLNBD-404).


LN_PlanningSignal

Application document LnPlanningSignal

Workflow models


Conditions/rule • Planner is filled. • Accepted indicator is False. • Obsolete indicator is False. • Signal code is <= 60. This constant value excludes signals on

pegging and confirmed quantity. You can customize this value.

Action • Workflow is started when a planning signal is created. • Buttons to accept or decline the planning signal, which publishes

the Process.LnPlanningSignal BOD and updates the Accepted flag in Infor LN.

Distribution • Planner.

• If the value of the planner field is null, the LN_Planning distribution group is used .

Drill back Infor LN Exception Messages by Planner and Item (cprao1125m000) session.

Caution: If multiple planning signals are created in Infor LN, the volume of tasks is high. It is recommended that you customize the activation policy or do not activate the workflow.

Notes:

• LnPlanningSignal is a custom BOD. See “Error! Reference source not found.” on page Error! Bookmark not defined. for information on how to register custom BODs in ION.

• LN_PlanningSignal_Cancel activation policy cancels the workflow, when the planning signal is accepted or deleted. The Accepted indicator must be True or the Obsolete indicator must be True. The distributed tasks are canceled.

Production order complete Introduced in Content pack v5



Purpose Start the workflow when a production order must be completed (ERPLNBD-441).

Workflow LN_ProductionOrder_Complete


Conditions/rule • Type is not Maintenance. • Status is Released or Active.

Workflow models


• One day after the planned delivery date. Threshold can be customized.

Action Task is created to complete the production order.



Note: Workflow can be started from an alert sent by the LN_ProductionOrder_Complete monitor.

Production order release Introduced in Content pack v5



Purpose Start workflow when production order needs to be released (ERPLNBD-441).

Workflow LN_ProductionOrder_Release


Conditions/rule • Type is not Maintenance. • Status is Planned. • Production start date is within one day. You can customize the

threshold.

Action Task is created to release the production order.



Note: Workflow can be started using an alert that is sent by the LN_ProductionOrder_Release monitor.

Production order rework Introduced in Content pack v5


Workflow models



Purpose Start workflow when a production order must be reworked (ERPLNBD-441).


LN_ProductionOrder_Rework


Conditions/rule • Type is ShopFloor. • Status is Planned, Released, or Active. • Rework indicator is True.

Action Task is created to rework the shop floor production order.


Drill back Infor LN Production Order (tisfc0101m100) session.

Notes:

• The LN_ProductionOrder_Rework_Cancel activation policy cancels the workflow, when the ReworkIndicator is False or if the status of the ProductionOrder is not Planned, Released, or Active. Therefore, the distributed tasks are canceled.

• Only shop floor orders can be reworked.

Project bid convert contract Introduced in Content pack v13.1



Purpose Start the workflow when project bids are accepted and must be converted to contracts (LND2-16652).


LN_ProjectBid_ConvertContract

Application document ProjectBid

Conditions/rule • Bid status must be Accepted

Action Task is created to convert the project bid.

Distribution • Internal and external sales representatives • If the external sales and the internal sales representatives are

not specified, the LN_Project distribution group is used.

Workflow models


Drill back Infor LN Bid (tpest3600m000) session

Note: The LN_ProjectBid_ConvertContract_Cancel activation policy cancels the workflow, when the bid status is not Accepted. Therefore, the distributed tasks are canceled.

Purchase invoice registered Introduced in Content pack v3



Purpose Start the workflow when purchase invoices are registered and must be matched (ERPLNBD-425).


LN_Message_PurchaseInvoice_Registered


Conditions/rule • Message type is PurchaseInvoice. • Status is Registered (also published for transactions entered).

Action Task is created to match the registered purchase invoice.



Notes:

• Workflow is started using the LN_Message_PurchaseInvoice_Registered activation policy. • Workflow can also be started using an alert that is sent by the

LN_Message_PurchaseInvoice_Registered monitor. The alert is sent three days after the invoice is registered.

• The LN_Message_PurchaseInvoice_Registered_Cancel activation policy cancels the workflow, when the status is Matched, Approved, or Deleted. Therefore, the distributed tasks are canceled.

Requisition approval Introduced in Content pack v1 (LN_DA_Requisition is introduced in content pack v10

as a successor)


Workflow models



Purpose Start workflow to approve/reject requisitions (ERPLNBD-398).


LN_Requisition_Approval


Conditions/rule Status is Open.

Action • Workflow is started when a requisition is open. • Tasks offer a button to approve or reject the requisition. • Rejection results in a Process.Requisition BOD to update the

status in Infor LN to Rejected. Approval results in: • If the total amount is not above 500, Process.Requisition BOD to

update the status in Infor LN to SpendApproved. • If the total amount is above 500, a new task for another user to

approve or reject is created. The second approval results in a Process.Requisition BOD to update the status in Infor LN to SpendApproved. Rejection results in a BOD to update the status in Infor LN to Rejected.



Notes:

• LN_DA_Requisition workflow is introduced in content pack v10 for Infor LN 10.4.1. Ensure that not two workflows are used to approve and reject requisitions. Deactivate the LN_Requisition_Approval workflow, when the LN_DA_Requisition workflow is active.

• Requisition approval in ION workflow can be enforced by selecting the External Approval check box in the Infor LN Purchase Requisition Parameters (tdpur0100m200) session. If this check box is selected, purchase requisitions are approved outside Infor LN. Therefore, the purchase requisition approval process is unavailable in Infor LN.

• Infor LN 10.4.1 or later does not include the External Approval anymore; LN_DA_Requisition document authorization workflow is introduced that succeeds LN_Requisition_Approval workflow.

• The LN_Requisition_Approval_Cancel activation policy cancels the workflow, when the status of the Requisition is Approved or Rejected. Therefore, distributed tasks are canceled.

Requisition conversion Introduced in Content pack v1

Workflow models




Purpose Start the workflow to convert requisitions (ERPLNBD-398).


LN_Requisition_Conversion


Conditions/rule Status is Approved.

Action Workflow is started when a requisition is approved, a task to prepare conversion is followed by a task to convert the requisition.



Note: The LN_Requisition_Conversion_Cancel activation policy cancels the workflow, when the requisition is converted. The status must be Converted. Therefore, the distributed tasks are canceled.

RFQ due Introduced in Content pack v3



Purpose Workflow on an overdue Request for Quotation (RFQ) (ERPLNBD-400).

Workflow LN_RFQ_Due


Conditions/rule • Return date must be within three days (threshold can be customized).

• Status must be Open or Printed.


• Three days before the return date, a task is created to take action on the RFQ.


• If the value of the buyer field is null, the LN_Purchase distribution group is used.

Workflow models



Notes:

• Workflow can be started using an alert that is sent by the LN_RFQ_Due monitor. • Infor LN publishes one RFQ BOD per supplier. You receive a task for each supplier. • RFQs with a return date in the past are not excluded and tasks are created.

Sales order unblock Introduced in Content pack v7



Purpose Workflow for the Sales Order must be unblocked (ERPLNBD-1025).

Workflow LN_SalesOrder_Unblock


Conditions/rule Status must be Hold

Action Task is created to unblock the sales order. Blocking reason is mentioned.

Distribution • Internal and external sales representatives.

• If all the values of the fields are null, the LN_Sales distribution group is used.

Drill back Infor LN Blocked Sales Order (Lines) (tdsls4520m000) session.

Notes:

• Blocking can due to the various customer-defined hold reasons. The activation policy can be easily customized to start the workflows only for specific hold reasons, such as hold reasons of the type credit check, margin check, promotion check, or general.

• The LN_SalesOrder_Unblock_Cancel activation policy cancels the workflow, when the sales order is approved. The status must be not be Hold. Therefore, the distributed tasks are canceled.

Workflow models


Service order release Introduced in Content pack v14



Purpose Workflow for a Service Order must be Planned/Released (ERPLNBD-850).

Workflow LN_ServiceOrder_Release


Conditions/rule • Type is FieldService. • Status must be Open or Planned or Hold. • Emergency must be True or Planned Finish Time must be within

three days (threshold can be customized).

Action Task is created to release the service order.




Notes:

• Replaces workflow LN_Message_ServiceOrder_Release that was based on LnMessage.

• Workflow can be started from alerts that are sent using the LN_ServiceOrder_EmergencyNotReleased and LN_ServiceOrder_NotReleased monitors.

Supplier addition Introduced in Content pack v4



Purpose New Vendor/Creditor Creation must be workflow enabled (ERPLNBD-65).


LN_SupplierPartyMaster_Addition

Application document SupplierPartyMaster

Workflow models



Action • Task 1: The buyer reviews the buy-from data and can send a notification about the new supplier

• Task 2: The shipping users add the shipping data. • Task 3: The AP department adds the invoice-to data.

If all the tasks are completed, a notification can also be sent.

Distribution • Task 1: Buyer or distribution group LN_Purchase when buyer is blank

• Task 2: Distribution group LN_Warehousing • Task 3: Distribution group LN_Finance

Notification: Distribution group LN_Purchase

Drill back Infor LN Buy-from Business Partner (tccom4120s000) session. Infor LN Business Partner (tccom4100s000) session (task 2 and 3).

Note: The LN_ SupplierPartyMaster _Addition_Cancel activation policy cancels the workflow, when the status of the Supplier is Deleted. Therefore, distributed tasks are canceled.

Document authorization


Chapter 7 Document authorization 7

This chapter describes the workflows for document authorization.

The naming convention used for standard workflow models is LN_DA_object. For example: LN_DA_ProjectContract. By default, the standard model in the Object Configuration Management module uses standard workflow models.

Do not use the LN prefix for customized standard content or customer-defined content.

The tables describe when document authorization is introduced, the Infor LN release, required BOD schema and ION version, the purpose, workflow name, application document, conditions/rule, action, distribution, and drill back.

Workflows are distributed to the submit user. When first starting to work with document authorization this is a convenient default, but the distribution must be modified to the user or group of users who are responsible for approval.

Adjustment line Introduced in Content pack v9



Purpose To write off the inventory, document authorization is required (LND-9491).

Workflow LN_DA_AdjustmentLine

Application document Workflow

Conditions/rule Submit the created or modified adjustment line.

Action Task is created to accept or reject the new version of the adjustment line.

Distribution Submit user

Drill back Infor LN Adjustment Order (whinh5120m100) session.



Billable line Introduced in Content pack v9



Purpose Confirming a billable line requires document authorization (LND-9589).

Workflow LN_DA_BillableLine


Conditions/rule Confirm the billable line.

Action Task is created to accept or reject the billable line.


Drill back Infor LN Billable Lines (cisli8110m000) session.

Customer claim line Introduced in Content pack v10



Purpose Approving the customer claim line requires document authorization (LND2-291).

Workflow LN_DA_CustomerClaimLine


Conditions/rule Approve the created or changed customer claim line.

Action Task is created to accept or reject the customer claim line.



Cycle count line Introduced in Content pack v9





Purpose To count inventory, document authorization is required (LND-9491).

Workflow LN_DA_CycleCountLine


Conditions/rule Submit the changed cycle count line.

Action Task is created to accept or reject the new version of the cycle count line.


Drill back Infor LN Cycle Counting Order Lines (whinh5110m000) session.

Global trade compliance check result Introduced in Content pack v12



Purpose Global trade compliance requires document authorization.

Workflow LN_DA_GTCCheckResult


Conditions/rule Submit the global trade compliance result.

Action Task is created to accept or reject the global trade compliance result.


Drill back Infor LN Document Compliance Check Results (tcgtc1510m000) session.

Invoice Introduced in Content pack v9





Purpose Composing the invoice requires document authorization (LND-9590).

Workflow LN_DA_Invoice


Conditions/rule Compose the invoice.

Action Task is created to accept or reject the invoice.


Drill back Infor LN Invoice (cisli3605m000) session.

Invoice-from business partner Introduced in Content pack v6



Purpose Creating or changing the invoice-from business partner requires document authorization (ERPLNBD-1008).

Workflow LN_DA_InvoiceFromBP


Conditions/rule Submit the created or changed invoice-from business partner. Changes to an inactive invoice-from business partner are automatically approved. Other possible conditions are available in the workflow definition.

Action Task is created to accept or reject the new version of the invoice-from business partner.


Drill back Infor LN Invoice-from Business Partner (tccom4122s000) session.

Note: Invoice-from business partner information can be created by department. Changes to the general definition of the invoice-from business partner result in updating the department specific definitions when the approval is received. A department specific change must be approved before approving the general change.

Invoice-to business partner Introduced in Content pack v9





Purpose Creating or changing the invoice-to business partner requires document authorization. Changes to credit limit and other attributes cannot be made without the required authorization (LND-7548).

Workflow LN_DA_InvoiceToBP


Conditions/rule Submit the created or changed invoice-to business partner.

Action Task is created to accept or reject the new version of the invoice-to business partner.


Drill back Infor LN Invoice-to Business Partner (tccom4112s000) session.

Note: Invoice-to business partner information can be created by department. Changes to the general definition of the invoice-to business partner result in updating the department specific definitions when the approval is received. A department specific change must be approved before approving the general change.

Journal Introduced in Content pack v9



Purpose Approval of a journal requires document authorization (LND-9598).

Workflow LN_DA_Journal


Conditions/rule Approve the created journal.

Action Task is created to accept or reject the journal.


Drill back Infor LN Document History - Transaction Lines (tfgld0618m200) session.



Payment batch Introduced in Content pack v9



Purpose Approval of a payment batch requires document authorization (LND-9599).

Workflow LN_DA_PaymentBatch


Conditions/rule Approve the payment batch.

Action Task is created to accept or reject the payment batch.


Drill back Infor LN Payment Advice (tfcmg1609m000) session.

Pay-to business partner Introduced in Content pack v6



Purpose Creating or changing the pay-to business partner requires document authorization (ERPLNBD-1008).

Workflow LN_DA_PayToBP


Conditions/rule Submit the created or changed pay-to business partner. Changes to an inactive pay-to business partner are automatically approved. Other possible conditions are available in the workflow definition.

Action Task is created to accept or reject the new version of the pay-to business partner.


Drill back Infor LN Pay-to Business Partner (tccom4124s000) session.



Pay-to business partner bank accounts Introduced in Content pack v6



Purpose Creating or changing the bank account by pay-to business partner requires document authorization (ERPLNBD-1008).

Workflow LN_DA_PayToBPBA


Conditions/rule Submit the created or changed bank account details by pay-to business partner. Changes other than a changed bank account are automatically approved.

Action Task is created to accept or reject the new version of the pay-to business partner bank account.


Drill back Infor LN Bank Account by Pay-to Business Partner (tccom4125s000) session.

Physical breakdown change Introduced in Content pack v9



Purpose Submit the physical breakdown change. To modify the physical breakdown document authorization is required (LND-8359).

Workflow LN_DA_PhysicalBreakdownChange


Conditions/rule Submit the physical breakdown change.

Action Task is created to accept or reject the physical breakdown change.


Drill back Infor LN Physical Breakdown – Change Lines (tscfg2141m000) session.



Project Introduced in Content pack v6



Purpose To change the status of the project document authorization is required (ERPLNBD-1014).

Workflow LN_DA_Project


Conditions/rule Status change of the project.

Action Task is created to accept or reject the new version of the project.

Distribution If the value of the contract manager field is null, Project manager or submit user is used.

Drill back Infor LN Project 360 (tppdm6500m100) session.

Note: Approval tasks are created when the project status is changed to Active, Finished, or Closed. Other changes submitted in Infor LN are automatically approved.

Project bid Introduced in Content pack v13



Purpose To change the status of the project bid, document authorization is required (LND2-1793).

Workflow LN_DA_ProjectBid


Conditions/rule Status change of the project bid.

Action Task is created to accept or reject the new version of the project bid.


Drill back Infor LN Bid (tpest3600m000) session.

Note: Approval tasks are created when the Project Bid field, which is approved for proposal, is set to ‘yes’. Other changes submitted in Infor LN are automatically approved.



Project contract Introduced in Content pack v5



Purpose To change the status of the project contract header document authorization is required (ERPLNBD-950).

Workflow LN_DA_ProjectContract


Conditions/rule Status change of the project contract header.

Action Task is created to accept or reject the new version of the project contract header.

Distribution If a value for the contract manager field is not specified, Contract manager value or submit user is used.


Note: Approval tasks are created when the status of a contract header is changed. Other changes submitted in Infor LN are automatically approved.

Project contract deliverable Introduced in Content pack v6



Purpose To change the status of the project contract deliverable document authorization is required (ERPLNBD-947).

Workflow LN_DA_ProjectContractDel


Conditions/rule Status change of the project contract deliverable.

Action Task is created to accept or reject the new version of the project contract deliverable.

Distribution If a value for the contract manager field is not specified, Contract manager value or the submit user is used.




Note: Approval tasks are created when the status of the project contract deliverable is changed to Active, Released, Warehousing, or Canceled. Other changes submitted in Infor LN are automatically approved.

Project contract line Introduced in Content pack v5



Purpose To change the status of the project contract line document authorization is required (ERPLNBD-950).

Workflow LN_DA_ProjectContractLine


Conditions/rule Status change of the contract line.

Action Task is created to accept or reject the new version of the contract line.

Distribution If a value for the contract manager field is not specified, the Line contract manager value or the submit user.

Drill back Infor LN Contract Lines (tpctm1110m000) session.

Note: Approval tasks are created when the status of a contract line is changed. Other changes submitted in Infor LN are automatically approved.

Project equipment costs Introduced in Content pack v9



Purpose Approval of the project costs requires document authorization. Booking costs to a project cannot be done without the required authorization (LND-9345).

Workflow LN_DA_ProjectEquipmentCosts


Conditions/rule Approve the created cost line.



Action Task is created to accept or reject the project costs.


Drill back Infor LN Equipment Costs (tpppc2151m000) session.

Project interim results Introduced in Content pack v9



Purpose Approval of the project interim result requires document authorization. Booking results to a project cannot be done without the required authorization (LND-9342).

Workflow LN_DA_ProjectInterimResults


Conditions/rule Approve the created interim result.

Action Task is created to accept or reject the interim result.


Drill back Infor LN Interim Results (tpppc3150m000) session.

Project labor costs Introduced in Content pack v9




Workflow LN_DA_ProjectLaborCosts







Drill back Infor LN Labor Costs (tpppc2131m000) session.

Project material costs Introduced in Content pack v9




Workflow LN_DA_ProjectMaterialCosts





Drill back Infor LN Material Costs (tpppc2111m000) session.

Project subcontracting costs Introduced in Content pack v9




Workflow LN_DA_ProjectSubcontrCosts







Drill back Infor LN Subcontracting Costs (tpppc2171m000) session.

Project sundry costs Introduced in Content pack v9




Workflow LN_DA_ProjectSundryCosts





Drill back Infor LN Sundry Costs (tpppc2191m000) session.

Purchase contract Introduced in Content pack v9 (extended in content pack v13 for Infor LN 10.5.1)



Purpose Activating the purchase contract requires document authorization (LND-9526).

Workflow LN_DA_PurchaseContract


Conditions/rule Activate the purchase contract header.



Action Task is created to accept or reject the purchase contract or purchase contract change request


Drill back Infor LN Purchase Contract (tdpur3600m000) session or Infor LN Purchase Contract Change Request (tdpur3600m100) session.

Purchase invoice Introduced in Content pack v9



Purpose Creating the invoice requires document authorization (LND-4651).

Workflow LN_DA_PurchaseInvoice


Conditions/rule Approving the created purchase invoice.

Action Task is created to accept or reject the purchase invoice.


Drill back Infor LN Purchase Invoice Inquiry (tfacp2600m100) session.

Purchase order Introduced in Content pack v9 (extended in content pack v13 for Infor LN 10.5.1)



Purpose Approving the purchase order requires document authorization (LND-6709).

Workflow LN_DA_PurchaseOrder


Conditions/rule Approve the created or changed purchase order.



Action Task is created to accept or reject the purchase order or purchase order change request.


Drill back Infor LN Purchase Order (tdpur4100m900) session or Infor LN Purchase Order Change Request (tdpur4600m000) session.

Recurring journal Introduced in Content pack v6



Purpose Creating or changing a recurring journal requires document authorization (ERPLNBD-1009).

Workflow LN_DA_RecurringJournal


Conditions/rule The recurring journal is ready.

Action Task is created to accept or reject a new version of a recurring journal.


Drill back Infor LN Recurring Journal (tfgld0140m100) session.

Register received invoice Introduced in Content pack v15



Purpose Workflow gives an approval/rejection possibility before the open entry is created by Invoice Scanning.

Workflow LN_DA_RegisterReceivedInvoice


Conditions/rule Register a received invoice.



Action Task is created to accept or reject the registered invoice.


Drill back Infor LN Received Purchase Invoice (tfacp1610m000) session.

Request to reuse a supplier invoice number Introduced in Content pack v14



Purpose Request to reuse a supplier invoice number requires document authorization (LND2-18528).

Workflow LN_DA_RequestReuseSupplInvoice


Conditions/rule Submit request to reuse a supplier invoice number.

Action Task is created to accept or reject the request to reuse a supplier invoice number


Drill back Infor LN Requests to Reuse Supplier Invoice Number (tfacp2106m000) session.

Requisition Introduced in Content pack v10 (succeeds the LN_Requisition_Approval workflow that

was introduced in content pack v1)



Purpose Approving the requisition requires document authorization (LND2-710).

Workflow LN_DA_Requisition


Conditions/rule Approve the submitted or changed requisition.



Action Task is created to accept or reject the requisition.


Drill back Infor LN Purchase Requisition (tdpur2600m000) session.

Note: Prevent that two workflows execute approval and rejection of the requisitions. Deactivate workflow LN_Requisition_Approval when workflow LN_DA_Requisition is active.

Revenue Recognition Introduced in Content pack v16

Supported from Infor LN Cloud 2019.09


Purpose Workflow gives an approval/rejection possibility for revenue lines.

Workflow LN_DA_RevenueRecognition


Conditions/rule Approve a revenue line.

Action Task is created to accept or reject the revenue line.


Drill back Infor LN Revenue Line (cirrc1620m000) session.

Sales contract Introduced in Content pack v10



Purpose Activating the sales contract requires document authorization (LND2-708).

Workflow LN_DA_SalesContract


Conditions/rule Activate the sales contract header.

Action Task is created to accept or reject the sales contract.




Drill back Infor LN Sales Contract (tdsls3600m000) session.

Sales order Introduced in Content pack v9 (extended in content pack v10 for Infor LN 10.4.1,

extended in content pack v17 to handle sales order change requests)


BOD schema 2.10.0 (ION 11.1 for content pack v9, ION 11.1.9 for content pack v10)

Purpose Approving the sales order requires document authorization (LND-9525).

Workflow LN_DA_SalesOrder


Conditions/rule Approve the created or changed sales order.

Action Task is created to accept or reject the sales order.



Sales quotation Introduced in Content pack v10



Purpose Approving the sales quotation requires document authorization (LND2-1693).

Workflow LN_DA_SalesQuotation


Conditions/rule Approve the created or changed sales quotation.

Action Task is created to accept or reject the sales quotation.




Drill back Infor LN Sales Quotation (tdsls1600m000) session.

Service quote Introduced in Content pack v15



Purpose Approval of the quote request requires document authorization. (LND2-22280).

Workflow LN_DA_ServiceQuote


Conditions/rule Approve the created service quote.

Action Task is created to accept or reject the quote request.


Drill back Infor LN Quote Request (tsepp1600m000) session.

Stage payment Introduced in Content pack v9



Purpose Releasing the supplier stage payment requires document authorization (LND-9527).

Workflow LN_DA_StagePayment


Conditions/rule Release the created supplier stage payment.

Action Task is created to accept or reject the stage payment.





Trade order Introduced in Content pack v11 (extended in content pack v12 and v15)

Supported from Infor LN 10.4.2 (extended in Infor LN 10.5 and Infor LN 10.7)

BOD schema 2.10.0 (ION 11.1.9) (extended with ION 12.0 that comes with BOD schema 2.12.0)

Purpose Approve the trade order requires document authorization (LND2-7155).

Workflow LN_DA_TradeOrder


Conditions/rule Approve the trade order.

Action Task is created to accept or reject the trade order.


Drill back Infor LN Intercompany Trade Order - Purchase (tcitr3600m300) session. Infor LN Intercompany Trade Order – Sales (tcitr3600m200) session.


Appendix A Infor LN View modeler A

This appendix describes the view modeler. See “Overview” for a description of the interaction between the view modeler and ION.

You use the view modeler to model views that can be used to drill back and drill to Infor LN.

Design time The view modeler in Infor LN allows you to view the standard and customize standard views, and define your own custom views. You can export the standard content and custom content using XML files. You can also import content to the view modeler.

The Infor LN View Modeler (tlvwm0601m000) session runs within the Infor Web UI and is also available in Infor Ming.le. The view modeler session is a composite session with a navigation tree on the left and a properties pane on the right.

Overview of the view modeler:

• The view modeler has a standard set and a custom view set. A view set consists of several views.

• Views of the standard view set are loaded using Infor LN code. • Views of the custom view set are loaded using the Infor LN tables in the vwm module of the tl

package. Data is stored in company 000. View modeler tables tlvwm001 (View Sets), tlvwm002 (Views), tlvwm003 (View Parameters), tlvwm004 (View Sessions), and tlvwm020 (View Set by Package Combination) must exist in company 000.

• The standard view set is available in an Infor LN library, which means that a standard view set is applicable for a package combination. For the custom view set, you can specify a list of applicable package combinations in the View Set by package Combination (tlvwm0120m000) session.

• A view set can be exported and imported. You can export a complete view set or export a view set for ION, which means only the views and parameters are selected.

• When the view modeler session is started, the standard and the custom view sets are loaded to a single xml file, which is in the view modeler session.

• A view includes parameters and sessions. The view and parameters must be specified by applications external to Infor LN that must drill back or drill to Infor LN.

• A view can be simulated. The view parameter value must be specified. Optionally, the logical ID can be specified; if it is not specified, the current company is used. The simulate button starts the session for the specified view parameter value.

Infor LN View modeler


• View parameters can be composed and be decomposed to its elements, which are called calculated parameters.

An example of a composed parameter is AdjustmentOrderNumber of the AdjustmentOrderView. Infor LN publishes InventoryAdjustment BODs for adjustment orders and for cycle counting orders. For cycle counting orders, the order number is concatenated with the count number, order number_count number.

You can specify the decompose function tcbod.dll0003.decompose.adjustment.order.number to decompose the view parameter AdjustmentOrderNumber to the calculated parameters Source (“CycleCount” or “Adjustment”), OrderNumber, and CountNumber.

• For a session, you can specify the session code, mode, condition, and filter. o Mode is the start mode for the session and can be SINGLE_OCC, MULTI_OCC, or

MULTI_OCC+MODAL. o The condition allows you to specify the parameters values to start the session. o The filter allows you to specify which data filter to apply when the session is started. o The view modeler sets the WHERE clause extension that is used to start the

session. o A Check button is available to test the conditions and filters for the correct syntax.

• In the AdjustmentOrderView example, the condition in the Cycle Counting Order (whinh5600m000) session:

Source = "CycleCount" and filter "whinh500.orno = OrderNumber and whinh500.cntn = CountNumber."

When the AdjustmentOrderView is started and the AdjustmentOrderNumber parameter is decomposed to the Source = "CycleCount" calculated parameter, the cycle count session whinh5600m000 is started. The session displays the cycle count order and cycle count as specified in the AdjustmentOrderNumber view parameter that is decomposed to the OrderNumber and CycleNumber calculated parameters.

Runtime An application can invoke a URL that specifies the view name and view parameters.

The same xml structure that the view modeler session displays is loaded during the first drill back or drill to Infor LN.

The view is located in the view modeler xml.

Conditions and filters are evaluated to determine, based on view parameter values, which Infor LN session must be used to start the session and the data that must be displayed.

The regular session authorization is effective. If a user does not have access to a session, the sessions are not started.

Infor LN View modeler


Example An example for a purchase order drill-back:

Drill-back for a purchase order is fetched using an alert in Infor Ming.le.

Infor Ming.le is used to manage the URL:

First, the Infor Application Deployment for logical ID lid://infor.ln.nlbaudv1-422 is located.

Deployment consists of hostname, port, context, and whether or https must be used.

If the view name exists as an Infor Application View in Infor Ming.le, parameters ID1, ID2, and so on, are replaced by the specified parameters.

Infor Ming.le constructs the URL that contains the Infor Application Deployment for Infor LN.

The view modeler loads all views and searches for the view that is specified in the ViewId parameter.

The purchase order view consists of only one session and filters the data for the specified purchase order.

The session is started with a filter on the purchase order.

LnMessage


Appendix B LnMessage B

This appendix describes the LnMessage custom BOD, which is used to send messages from Infor LN to the users. The ION Desk modeling functionality is used with this custom BOD. The LNMessage BOD does not send messages to systems, such as other ERP or reporting applications.

The LnMessage BOD consists of a generic setup that you can use for events, when standard BOD cannot be used and when creation of a specific custom BOD is not required. The LnMessage BOD is used to send alerts or create workflow tasks without customizing BODs or using Business Studio.

This appendix describes the Publishing, ION Desk Modeling, and the drill back tasks.

Publishing LnMessage BOD is published from Infor LN to the ION.

Sending the LnMessage BOD to Infor LN is not implemented.

Standard content Several use cases are implemented such as the adding of enterprise units (master data) and monitoring of anticipated payments (transactions). See Infor LN BOD Mapping and Descriptions.

The trigger to publish the LnMessage for these standard use cases is implemented in the DAL scripts, which results in LnMessage BODs when a monitor or workflow is activated which utilizes the LnMessage BOD.

Company addition example

To publish fields using the Companies table, tcemm170 table, the standard DAL is changed. The tcintdlltcbod library is linked.

The handle.publish.ln.message function publishes the LnMessage and is called when the companies are added or deleted.

RETIFNOK(tcint.dlltcbod.publish.ln.message(

"ActionCode", action.code,

LnMessage


"MessageType", "Company",

"DocumentID", tcemm170.comp,

"Description", tcemm170.desc,

"Status_Code", trim$(status.code),

"Status_EffectiveDateTime", utc.to.iso(utc.num(),UTC_ISO_Z),

"Status_ArchiveIndicator", false,

"CompanyType", enum.descr$("tcemm.ctyp", tcemm170.ctyp, "2"),

"CurrencySystem", enum.descr$("tcemm.depe",tcemm170.csys, "2"),

"BaseCurrency", tcemm170.fcua,

"ReportingCurrency", tcemm170.lcur))

The following BOD is generated:

<LnMessage>

<DocumentID>

<ID accountingEntity="DV1-422" location="DV1-422"

lid="lid://infor.ln.nlbaudv3_422">Company_670_</ID>

</DocumentID>

<DisplayID>670</DisplayID>

<Description></Description>

<Status>

<Code>Open</Code>

<EffectiveDateTime>2012-01-10T14:36:44Z</EffectiveDateTime>

<ArchiveIndicator>false</ArchiveIndicator>

</Status>

<MessageType>Company</MessageType>

<MessageTypeDetails>

<CompanyGroup>

<CompanyType>Logistic</CompanyType>

<CurrencySystem>Standard</CurrencySystem>

<BaseCurrency>EUR</BaseCurrency>

<ReportingCurrency>GBP</ReportingCurrency>

</CompanyGroup>

</MessageTypeDetails>

LnMessage


</LnMessage>

Note: • The DocumentID is updated with the prefix, Company, and the separator character is appended.

The default separator is the underscore. If the DocumentID already contains the default separator, the next available separator from the list of alternate separators is used. For example, DocumentID 670 is changed to Company_670_. This convention is required to drill back from the ION Process.

• The DisplayID is the readable version of the DocumentID without the prefix and appended separator. For example, the DisplayID is 670.

Custom content You can generate your own alerts or create your own workflow tasks by using the LnMessage BOD. You can trigger the publishing of the LnMessage for custom workflows or tasks by using a User Exit DLL or by customizing the standard software (DAL.)

As the User Exit DLL is external to the standard software, no rework is required when standard scripts are updated. The User Exit DLL can be used for any table with a DAL and for scripts that use dal functions such as dal.new/dal.update/dal.destroy or dal.new.object/dal.change.object in combination with dal.save.object/dal.destroy.object.

A developer license is required to create User Exit DLLs. Before you customize standard software, contact your Infor representative for additional information.

The LnMessage contains the MessageType field that you can use to select a value. It is recommended that you use a company prefix such as CP_ so that the standard use cases are not in conflict.

Billing request example

To publish fields from the Billing Requests cisli200 table, create the User Exit DLL cisli200ue and link the tcintdlltcbod (Integration DLL for BODs) and cislidll0996 (Functions for Exceptions) libraries.

User exit dll’s include template code that you can extend.

Write a table declaration and include:

table tcisli200 |*Billing Requests

#include "itcmcs2000“

Add the code to the ue.after.after.save.object hook:

domain tcyesno exception.yn

if cisli.dll0996.exceptions.exist(cisli200.scmp,cisli200.brid,true) then

exception.yn = tcyesno.yes

else

exception.yn = tcyesno.no

LnMessage


endif

RETIFNOK(tcint.dlltcbod.publish.ln.message(

"MessageType", "BillingRequest",

"DocumentID", cisli200.scmp,

"DocumentID", cisli200.brid,

"Description", cisli200.dsca,

"Status_Code", enum.descr$("cisli.brst",cisli200.brst,"2"),

"UserAreaName", "Exceptions",

"UserAreaType", "StringType",

"UserAreaValue", enum.descr$("tcyesno",exception.yn,"2")))

This produces the following BOD:

<LnMessage>

<DocumentID>

<ID accountingEntity="DV1-422" location="DV1-422" lid="lid://infor.ln.nlbaudv3_422">BillingRequest_422_000000734_</ID>

</DocumentID>

<DisplayID>422 000000734</DisplayID>

<Description>SLO000442</Description>

<Status>

<Code>On Hold</Code>

</Status>

<MessageType>BillingRequest</MessageType>

<UserArea>

<Property>

<NameValue name="Exceptions" type="StringType">Yes</NameValue>

</Property>

</UserArea>

</LnMessage>

Global trade compliance example Another example is where LN implemented an LnMessage BOD for global trade compliance without making changes to XSD and only added the below line of code to DAL. LN included several UserAreaName, UserAreaType, UserAreaValue arguments for fields that are not part of the standard LnMessage XSD.

LnMessage


Just ensure that names are unique for extraction in ION later. For customizations, you could use a ‘user exit script’ and add a similar line to trigger BOD publication.

RETIFNOK(tcint.dlltcbod.publish.ln.message( MessageType, "GlobalTradeCompliance",

DocumentID, tcgtc110.boty, DocumentID, tcgtc110.boco, DocumentID, tcgtc110.bobj, DocumentID, tcgtc110.borf, DocumentID, tcgtc110.extc, Status_Code, enum.descr$("tcgtc.cres",tcgtc110.cres,"2"), "UserAreaName", "Document Type", "UserAreaType", "StringType", "UserAreaValue", enum.descr$("tcgtc.boty", tcgtc110.boty,"2"), "UserAreaName", "Document Company", "UserAreaType", "StringType", "UserAreaValue", tcgtc110.boco, "UserAreaName", "Document", "UserAreaType", "StringType", "UserAreaValue", tcgtc110.bobj, "UserAreaName", "Document Reference", "UserAreaType", "StringType", "UserAreaValue", tcgtc110.borf, "UserAreaName", "Kind of Check", "UserAreaType", "StringType", "UserAreaValue", enum.descr$("tcgtc.check", tcgtc110.extc,"2"), "UserAreaName", "Export / Import", "UserAreaType", "StringType", "UserAreaValue", enum.descr$("tcgtc.exp.imp", tcgtc110.exim,"2"), "UserAreaName", "Item", "UserAreaType", "StringType", "UserAreaValue", tcgtc110.item, "UserAreaName", "Business Partner", "UserAreaType", "StringType", "UserAreaValue", tcgtc110.bpid, "UserAreaName", "Address", "UserAreaType", "StringType", "UserAreaValue", tcgtc110.cadr, "UserAreaName", "License ID", "UserAreaType", "StringType", "UserAreaValue", tcgtc110.lcid, "UserAreaName", "Compliance Check Result", "UserAreaType", "StringType", "UserAreaValue", enum.descr$("tcgtc.cres", tcgtc110.cres,"2"), "UserAreaName", "Failure Reason Code", "UserAreaType", "StringType", "UserAreaValue", tcgtc110.cfrc, "UserAreaName", "Approved", "UserAreaType", "StringType", "UserAreaValue", enum.descr$("tcyesno", tcgtc110.appr,"2"), "UserAreaName", "Shipment Line Confirm", "UserAreaType", "StringType", "UserAreaValue", enum.descr$("tcyesno", tcgtc110.conf,"2"), "UserAreaName", "Note Guid", "UserAreaType", "StringType", "UserAreaValue", tcgtc110.note,

LnMessage


"UserAreaName", "Checked by", "UserAreaType", "StringType", "UserAreaValue", tcgtc110.ckby, "UserAreaName", "Check Date", "UserAreaType", "StringType", "UserAreaValue", tcgtc110.ckdt, "UserAreaName", "Overridden by", "UserAreaType", "StringType", "UserAreaValue", tcgtc110.ovby, "UserAreaName", "Override Date", "UserAreaType", "StringType", "UserAreaValue", tcgtc110.ovdt, "UserAreaName", "Contract Line", "UserAreaType", "StringType", "UserAreaValue", tcgtc110.cnln, "UserAreaName", "Line", "UserAreaType", "StringType", "UserAreaValue", tcgtc110.pono, "UserAreaName", "Sequence", "UserAreaType", "StringType", "UserAreaValue", tcgtc110.seqn, "UserAreaName", "Component Sequence", "UserAreaType", "StringType", "UserAreaValue", tcgtc110.cseq ))

ION Desk Modeling The custom BOD LnMessage must be stored in the ION registry. After registration, you can model monitors and workflows for the LnMessage BOD similar to any other BOD.

Standard content Several use cases are implemented in the Cloud Edition Content pack v13. The content pack v13 includes monitors, workflows, and activation policies that you can import and activate.

Company addition example For a description, see workflow Company Addition.

When a company is added, an LnMessage BOD is published with the MessageType field set to “Company”. The activation policy uses the MessageType field to filter out the LnMessage BODs for company additions.

DisplayID (and not DocumentID) is used in the workflow message to indicate the company that is added.

LnMessage


Custom content You can model your own monitors and workflows using the LnMessage BOD. You can copy standard monitors and workflows and customize the same.

Billing Request example

Application Document: LnMessage

This table shows the monitor attributes:

Name Path Filter

BillingRequestID LnMessage/DocumentID/ID

BillingRequest LnMessage/DisplayID

Description LnMessage/Description

Status LnMessage/Status/Code

MessageType LnMessage/MessageType

Exceptions LnMessage/UserArea/Property/NameValue@name = “Exceptions” Yes

This table shows the conditions where the Combined condition is used as the monitor rule:

Name Expression

BillingRequest [MessageType] = 'BillingRequest‘

Exceptions [Exceptions] = 'Yes‘

Combined BillingRequest AND Exceptions

Alert message: Exceptions exist for billing request [BillingRequest] with status [Status]

Distribution: LN_Finance Group

Drill back Drill backs can be modeled in the View Modeler that specify the conditions that must be used to start an Infor LN session and the records to filter. Using the View Modeler, you can add drill back sessions without modifying the imported Views_Standard.xml drill back file in ION.

LnMessage


Standard content The standard view set includes the LnMessageView and sessions for each standard use case. Content packs contain the Views_Standard.xml file. You must copy these files to the ION server; however, you are not required to update these files when use cases are added.

Company addition example

Properties

Session: Companies (tcemm1170m000)

Mode: SINGLE_OCC

Condition: MessageType = "Company"

Filter: tcemm170.comp = IDpart1

The DocumentID is decomposed to the elements. The separator is appended and is used to determine the MessageType and ID elements. For example, “Company_670_” decomposes into message type “Company” and IDpart1 = 670 and contains only one IDpart.

You can add sessions for your use cases by copying the LnMessageView from the standard view set to a custom view set and then adding a session to the LnMessageView custom.

Billing request example

Properties

Session Billing Requests (cisli2100m000)

Mode SINGLE_OCC

Condition MessageType = "BillingRequest"

Filter cisli200.scmp = IDpart1 and cisli200.brid = IDpart2