Infor M3 (AWS) Early Announcement of Changes Requiring Advance Customer Action Future 20230401

Infor M3 (AWS) –
Early announcement of changes

requiring advance customer actions
Revision history
Date Version Comments

October 2022 20221001 ID M36204, M34760 added to April 2023
ID M35842 moved to April 2023
ID M35993, M35948, M35833, M35801, M35395, M34335 updated
information
November 2022 20221101 ID M36313 added to January 2023

ID M36245, M36286, M35990, M36000, M36306 added to April 2023
ID M36270, M36395, M36253, M34156 added to October 2023
ID M33316 moved to October 2023
ID M35748, M35716, M35334, M34760, M35842, M36040 updated
information
December 2022 20221201 ID M36745 added to January 2023

ID M36728 added to February 2023
ID M36394 added to April 2023
ID M36414, M36338, M36802, M36727 added to October 2023
ID M36000, M35990, M35718, M35634 updated information
January 2023 20230101 ID M36872, M36833, M36945, M36962, M36987 added to October 2023
February 2023 20230201 ID M35593, M35898, M36109, M37022, M37080, M37054 added to April 2023
ID M36081, M35351, M36177, M36297, M36311, M36330, M36334, M36337,
M36947, M37002, M37003, M37013, M37036, M37045, M37074 added to
October 2023
ID M34156, M34334, M34760, M35395, M35716, M35718, M35790, M35904,
M35990, M36204, M36245, M36306, M36728, M35842, M36872 updated
information
March 2023 20230301 ID M37094, M37181, M37024, M37250 added to April 2023
ID M37214, M35701, M37032, M37188, M37185, M36110, M35667 added to
October 2023
ID M37157, M37242, M37144, M37149 and M37182 added to April 2024
2| Updated April 2023 Copyright © 2023. Infor. All rights reserved. www.infor.com
Date Version Comments
April 2023 20230401 ID M35842, M37036, M36947, M37003, M36987, M36833, M36802, M36109,
M34156, M36395, M36872, M36727, M36177, M37242 updated information.
ID M36962, M35667 and M33316 moved to April 2024
ID M37304, M37358, M37305, M37090 and M37291 added to April 2024
Contents
Contents..................................................................................................................................................... 4
Introduction................................................................................................................................................ 5
Other recommended actions .................................................................................................................. 6
Changes requiring advance customer actions planned for April 2023 ............................................ 7
Changes requiring advance customer actions planned for October 2023 .................................... 32
Changes requiring advance customer actions planned for April 2024 .......................................... 59
Important information regarding testability of M3 functions ............................................................. 66
Important information regarding changes to Db indexes and existing table fields ...................... 67
Important information ............................................................................................................................. 68
Support information................................................................................................................................ 73
Introduction
Changes that require advance actions
Major changes and enhancements to M3 CE are planned that require your attention now as they
impact how the solution is used by end users immediately after deployment. This document contains
information about these changes and describes the mandatory actions to perform before or
immediately after the maintenance window. Infor recommends that you review the descriptions of the
included changes and prepare for them in advance of the scheduled date.
Viewing referenced KB articles
Note that referenced KB articles are not available until the month when the change is available in M3.
Always use 'Feature List. Open' (CMS975) and the KB article link in there, rather than going directly to
the KB article.
Other recommended actions
None impact features recommended to be activated as soon as possible.
M3 CE Core: Prepare Your Move from H5 Classic to H5 (Angular)

H5 (Angular) is the prerequisite for all new M3 experience innovations such as the InforOS Portal & M3
Experience Designer Applications. New capabilities in H5 will also only be added in H5 (Angular).
New tenants and on-going projects should use H5 (Angular) from start in order to avoid a future move.
The move can either be done for groups of users at different times or for all users in a single go. To move
from Classic, existing H5-Scripts must be checked for compatibility and may require some minor
adjustments. For more information about H5 scrips please see KB 1909067. H5 developer guide is also
attached in that Kb and that has a separate section in the end in how to move scripts from H5 classic to
H5 (Angular). The developer community is also a great help when you need help. It can be found here:
https://community.infor.com/infor-developers/f/m3-development.
Finally there is a recorded session at Infor Campus covering what is new in H5 (it is from 2021).
Availability:
This feature is available in M3. More information will be added to this document once available.
M3 CE Core: Export and import solution for M3 Dataset definition.

A new export and import solution for M3 dataset definition provides an efficient way of copying
datasets from one company to another or one tenant to another. Compared to the Business Engine
Data Management (copy data tool), this is more reliable as it validates the records to be imported and
handles replace and keep existing records. The solution also eliminated the manual
deactivation/activation of the dataset to create and point to the new “O-table” in the tenant. This is
now done automatically.
 
A new option 21='Export Configuration' and action F17='Export' has been added to 'Dataset. Open'
(OSS401). Up to 200 records can be exported and imported in one go. This new feature will ensure
dataset definitions are copied in an efficient way and necessary actions are done to avoid any potential
inconsistencies. The dataset table won’t be part of the import export.
Please use this capability instead of including the dataset configuration in the data management copy
tool.
 
Availability:
This feature is available as of June 2023 update of M3 and will be automatically activated as of April
2024. When available, see KB article 2284132 in the program 'Feature list. Open' (CMS975).
Changes requiring advance customer actions planned for April 2023
M3 CE Core: New setting to restrict a rental corrective invoice to contain corrected lines only
A new check box, Select all, has been added to 'Rental Invoice Proposal. Update Lines' (STS811) and
visible for corrective invoices only.
Reason for the change:
To meet statutory legislation in Russia where there is a requirement to create a corrective invoice
containing only the corrected lines.
Result of the change:
For corrective invoices, if the check box is left cleared, then only corrected rental invoice lines are
considered for the corrective invoice. If selected, all lines are included as in the previous functionality.
Actions required prior to activating the change:
All M3 customers must verify the change before April 2023.
Availability:
This feature is available in M3. For more information, see KB article 2181386 in the program 'Feature
list. Open' (CMS975).
ID: M35458
M3 CE Core: Improve tax point handling for Sales tax calculation using Vertex
The service order and leasing agreements are no longer available.
Previously available flexible fields for service order and leasing agreement have been removed since
these components are no longer available.
None.
Availability:
ID: M35606
M3 CE Core: Prevent create same alternative UM as basic UM for a conversion factor other
than 1
A stop message is now displayed in 'Item. Connect Alternate U/M' (MMS015), MMS015MI, ‘Interface
Item. Connect Alternate U/M’ (MHS015), and MHS015MI when trying to create an alternative U/M
that is the same as the basic U/M with a conversion factor other than 1:
• (MMS015): Options "Create", “Update”, "Copy"
• MMS015MI: Transactions "Add", “Upd”
• (MHS015): Options "Create" and "Copy" Option “Validate”
• MHS015MI: Transactions "AddIntItmAum", "CpyIntItmAum", "SndAddIntItmAum"
• MHS200MI: Transactions “ImpIntItm”, “ValIntItm”
In (MMS015), MMS015MI, (MHS015), and MHS015MI, it is possible to create the same alternative U/M
as the basic U/M. It is also possible to define a conversion factor that could cause problems in some
transactions where MITAUN is checked and considers the unit is the basic u/m defined in 'Item. Open'
(MMS001).
A stop message will be displayed, and it will not be possible to create an alternative U/M that is the
same as the basic U/M with a conversion factor other than 1.
Investigation of processes using this API transaction to ensure they are not affected by this change.
Availability:
This feature is available in M3 and will be activated automatically in the April 2023 update of M3
Business Engine. For more information, see KB article 2236855 in the program 'Feature list. Open'
(CMS975).
ID: M35395
M3 CE Core: Performance enhancements have been made for transactions using the API
MMS060MI
Some transactions in API MMS060MI were calling component MMS060BE to retrieve data. This has
resulted in lower performance when running the transactions with input and results in large volumes of
output since each MITLOC record requires a call to MMS060BE.
To avoid multiple calls to MMS060BE for each MITLOC record to be listed, enhancements have been
made.
These transactions in MMS060MI, Get, List, LstViaItem, SetBalIdAloc, Select, LstContainer, LstLocation,
LstLot, LstBalID, LstBalIDByOrd, have been enhanced in terms of performance. Logic has been moved
from MMS060BE into API MMS060MI to avoid an extra API call for each MITLOC record. The functional
solution is still the same as before.
These output fields have been changed to follow standard output formatting for all the listed
transactions above: REPN, PHSQ, PHAQ, AUDD, PHA2, POCY, LPCY, REOP, ATNR, ATNB, CAW2.
Example of output changes when ATNR is not used:
Old solution – field ATNR output: 00000000000000000
New solution (aligned with to the new output formatting) – field ATNR output: 0
None.
Availability:
The performance enhancement is available in M3 and will be automatically activated in the April 2023
update of M3 Business Engine. For more information, see KB article 2236890 in the program 'Feature
ID: M35548
M3 CE Core: New document number and partner media reference control

New document number for partner media reference control for 'Customer Agreement Confirmation'
(OIS631PF).
Currently, Document 231 with variant 40 can be used to setup Partner Media for Blanket Agreement
(OIS631PF). Note that the variant 40 is not supported to be generated as part of the standard
documents using ‘Standard Document. Open’ (CRS027) as it is reserved for Order Confirmation
(OIS606PF and OIS608PF). Instead of using Document 231 with variant 40, a new document '230 -
Customer Agreement Confirmation' is introduced to enable media control of OIS631PF.
Customers can no longer use Document 231 with Variant 40 to setup Partner Media for Blanket
Agreement (OIS631PF), instead the document number 230 should be applied.
If a media control set-up exists for document number 231 and variant 40, after the feature toggle is
activated, replace this with the new document number 230. Note that the new standard document is
created using ‘Standard Document. Open’ (CRS027), Use Actions Generate Standard (F14).
Availability:
This feature is available in M3 and will have an impact in the April 2023 update of M3 Business Engine.
For more information, see KB article 2185761 in the program 'Feature list. Open' (CMS975).
ID: M35515
M3 CE Core: DOP Release Validation: 'Soft allocated item not valid for auto issue level 4.'
It is no longer allowed to release a DO proposal with a dispatch policy that is 'Auto Level' (TRLV) = 4 and
'Soft Allocation Transfer Level' (SOFL) = 0-'No’ when the item has 'Allocation Method' (ALMT) = 6-'Soft
Auto 1' or 7-'Soft Auto 2'. This validation is applied in ‘Planned Distribution Order. Open' (DPS170),
DPS170MI.CrtPlannedDO, and batch job DPS914.
Release of DO proposal in (DPS170) allows the creation of a distribution order using a dispatch policy
with 'Auto Level' (TRLV) = 4 and 'Soft Allocation Transfer Level' (SOFL) = 0-'No', when the item has
'Allocation Method' (ALMT) = 6-'Soft Auto 1' or 7-'Soft Auto 2.' This should be stopped, since such an
order cannot be processed automatically. Validations are already in place when manually creating a DO
for the same scenario.
In (DPS170), the error message MM_0005, “Soft allocated item not valid for auto issue level &1.” is
returned upon release of the DO proposal.
Using the API transaction DPS170MI.CrtPlannedDO, the DO proposal cannot be created in status 60.
When autojob MMS940 is running, auto-release of DOP should not proceed, and the status should be
retained at 20. A new application message 281 was created to notify the user if the planned DO was
not released due to the conditions specified. The new application message must be generated in
'Settings - Application Messages' (CRS424) using action F14-'Crt Msg types' prior to use.
This development is controlled by feature toggle 2242559. This toggle must be active in 'Feature list.
Open' (CMS975) for the validation to take place.
Availability:
ID: M35718
M3 CE Core: (APS905) updated to configurable views

'Settings - Accounts Payable' (APS095) is modernized and changed to use configurable list standard.
The panels in (APS905) are crowded and additional panels are needed.
(APS905) will be updated to align to the latest standard for configurable views.
None.
Availability:
This feature will be available as of the April 2023 update of M3. When available, please see more
information in KB article 2267849 in the program 'Feature list. Open' (CMS975).
ID: M34334
10 | Updated April 2023 Copyright © 2023. Infor. All rights reserved. www.infor.com
M3 CE Core: Respect item status 50 at auto-connection of item to warehouse
Item status 50 needs to be respected at auto creation of item/warehouse record.
Currently, the supply model options will evaluate incorrectly when an item or warehouse is created in
other statuses, for example, status 20, which could be the normal status according to the template
item.
None.
Availability:
This feature is available in M3 and will be automatically activated in the April 2023 update of M3
(CMS975).
ID: M35662
M3 CE Core: Enhanced management of VAT capabilities, including Fiscal Representation for

Manual Customer Invoices
New functionality to create a manual customer invoice (ARS120) using another base country and issuing
VAT registration number than the one from the current division.
The invoice issuing base country code and VAT reg. no. of the invoice gets indicated by the new
warehouse field. The tax point defined in the Delivery Terms used and in case settings for Fiscal
Representation get used for the VAT decision and the receiving country (BSCD).
In 'Manual Customer Invoice. Open' (ARS120), the flexibility to cope with several VAT situations is
limited. To add more flexibility, the fields warehouse and delivery terms will be introduced to determine
the tax point and the fiscal representative rule.
The user must indicate the warehouse in (ARS120). The proposed warehouse will be the default
warehouse from 'Company. Connect Division' (MNS100).
None.
Availability:
ID: M35246
M3 CE Core: Empty dataset records will no longer be automatically deleted
When all accumulator field values of a record in a dataset are updated to zero, the record is no longer
deleted.
Before, when all accumulator field values of a record in a dataset were updated to zero, the record was
automatically deleted. This was a problem to external systems that used dataset data, such as demand
planner.
Since it is not feasible to always perform a full dataset import, such systems often import the latest
updated records based on last update timestamp (LMTS). If a record in a dataset is completely deleted,
it is not possible for the external system to know if the record has values and is unchanged, has never
existed or has been deleted.
When all accumulator field values of a record in a dataset are updated to zero, the record is no longer
deleted. Now the record will remain, and its update timestamp (LMTS) will have information on when
the update occurred.
None.
Availability:
This change is available in M3 Business Engine with automatic activation as part of April 2023 release.
ID: M35392
M3 CE Core: Russia: Implement Russian special routine for "amount in words" for XML out
Conversion of amounts to Russian language was insufficient.
Users can now use CRS180MI-GetAmtInWords to translate amount to words based on the Russian
language.
None.
Availability:
This feature is available in M3 and will be enabled as part of April 2023 release. For more information,
see KB article 2221697 in the program 'Feature list. Open' (CMS975).
ID: M35862
M3 CE Core: Enhancing configurable text blocks for external documents functionality.
To reduce administration and complexity in the configurable text blocks setup, the Text ID has been
removed from ‘XML Custom Text Section Control. Open’ (CMS033). All Text IDs connected to the Key
group will be valid for the XML section created in (CMS033).
The complexity and administration proved too complex and time consuming when needing to connect
each Text ID and Key group to a Custom Text Block XML section. The connection between the Text ID
and Key group already exists in the setup, so removing the need for the Text ID in (CMS033) is logical
and simplifies the configuration.
Text ID is removed from (CMS033), and all Text IDs connected to the Key group for the Configurable Text
Block section are valid to be printed if the conditions in ‘XML Custom Text. Open Key Field’ (CMS038) are
fulfilled.
If multiple Text IDs with the same Key Group is connected to the same base section in ‘XML Structure.
Open Section’ (CMS007), remove all except one. Test and verify the functionality after activating the
feature toggle.
Availability:
This feature is available in M3 and will be automatically activated in the April 2023 update of M3 Business
Engine. When available, see KB article 2184390 in the program 'Feature list. Open' (CMS975).
ID: M35790
M3 CE Core: (OIS390) no longer shows customer returns that the user is not authorized to
access
In 'Customer Return. Open' (OIS390), it was possible to see customer returns for warehouses that the
user was not authorized to access.
Customer returns for warehouses with an object access group or belonging to a facility with an object
access group, that the user is not authorized to access are no longer displayed in (OIS390).
This change will have an impact on the customer returns displayed to the user in (OIS390). Existing object
access group and user group setup must be validated so that the user is authorized to see the correct
customer returns.
Availability:
This feature is available in M3 and will be automatically activated in April 2023. For more information,
see KB 2238253 in the program 'Feature list. Open' (CMS975).
ID: M35806
M3 CE Core: Expected receipt on DO should retain delivery number after full pick correction
When a picking list on distribution is corrected and delivery is deleted, expected receipts are not updated
correctly in ‘Expected Receipt. Display Lines’ (MHS801). The delivery number is cleared, breaking the
synchronization to an external system.
When pick correction is performed on a DO resulting in a deletion of the delivery, the expected receipts
are correctly updated to reflect this change.
(MHS801) is updated with *DLT, Quantity 0, and the delivery number is not cleared. That way, the
external system can synchronize information and be informed that this delivery is no longer expected.
Ensure that expected receipt integrations using MHS800MI work as expected when a delivery on
distribution order is deleted after a complete reverse of a picking list. Make sure that the integration and
external system recognize how to manage records flagged *DLT and referring to a delivery (DLIX) which
is deleted from M3. Those records are returned by transactions like GetExpRecDetail, LstExpRecDetail.
Availability:
This feature is available in M3 and will be automatically activated as part of the April 2023 update of M3
Business Engine. For more information, see KB Article 2252269 in the program 'Feature list. Open'
(CMS975).
ID: M35953
M3 CE Core: Users with restricted characters disallowed to be created via MNS150MI

Added validation for special characters in MNS150MI-Add and MNS150MI-CopyUser.
Special characters cannot be added in the interactive program ‘User. Open’ (MNS150) but possible in
MNS150MI.
Input for users now have validation for special characters and if detected, error message will be
presented. This validation does not accept these characters:
• *
• %
• /
• \
• ?
• <
• >
• :
• |
• “
• ^
• )
• (

None.
Availability:
This feature is available in M3 and will be activated automatically in the April 2023 update of M3
(CMS975).
ID: M35923
M3 CE Core: Several transactions within Manufacturing Order APIs, PMS100MI and

PMS170MI will be removed
The reason for decommissioning of the transactions is because they are not stateless in all situations.
The existing API transactions will no longer be available.
Any integrations or extensions using these API transactions should be reviewed and adjusted prior to
the change:
• PMS100MI Select should be replaced by PMS100MI SelOrderHead
• PMS100MI SelOperation should be replaced by PMS100MI SelOpeByHead
• PMS100MI SelMaterial should be replaced by PMS100MI SelMatByHead
• PMS170MI Select should be replaced by PMS170MI SelOrderHead
• PMS170MI SelOperation should be replaced by PMS170MI SelOpeByHead
• PMS170MI SelMaterial should be replaced by PMS170MI SelMatByHead
Availability:
The new API transactions have been available since M3 13.1 and are already active. The listed
transactions will be automatically removed in the April 2023 update of M3 Business Engine. For more
information, see KB article 2235293 in the program 'Feature list. Open' (CMS975).
ID: M34817
M3 CE Core: A new panel is added to (CRS434)
A new panel is added to ‘Credit Card Interface Settings. Open’ (CRS434).
There is no room on panel E, thus new parameters are introduced on a new panel F.
The new panel F will be mandatory when creating new records in (CRS434).
None.
Availability:
This change has been implemented and will be activated automatically in the April 2023 update of M3
Business Engine. For more information, see KB article 2237820 in the program ‘Feature List. Open'
(CMS975).
ID: M35903
M3 CE Core: Replacement of the API transaction GetBasicData in PPS001MI

The API transaction GetBasicData in PPS001MI (Purchase Order Entry) should not be used and it has
already been replaced with GetBasicData2. The latter has been there for number of years and need to
be removed.
The API transaction GetBasicData in PPS001MI (Purchase Order Entry) should return a single line but it
displays a multi-line instead, which results in mismatching records for consuming system.
The API will be deprecated.
Remove the transaction GetBasicData from PPS001MI, instead use PS001MI/GetBasicData2 to get and
display a purchase order subline record.
Availability:
This feature is available in M3. The API will be deprecated in the April 2023 release of the M3 Business
Engine. For more information, see KB article 2236933 in the program ‘Feature List. Open' (CMS975).
ID: M35944
M3 CE Core: Display all purchase price decimals in PPS100MI - LstStgPrice

All purchase price decimals stored in the database are now displayed when running API PPS100MI,
transaction LstStgPrice.
Issues were observed when using staggered pricing along with a purchase price quantity. API PPS100MI,
transaction LstStgPrice displays the purchase price per unit, and previously the purchase price was
displayed in the number of decimals defined for the item (maximum 4). This meant that if the purchase
price quantity was large enough, one or more decimals could be cut from the API output.
When running API PPS100MI, transaction LstStgPrice, all 6 decimals of the purchase price stored in the
database are displayed in the output.
Availability:
This feature is available in M3 and will be automatically updated as part of the April 2023 release of M3
Business Engine. For more information, see KB article 2255608 in the program ‘Feature List. Open'
(CMS975).
ID: M36009
M3 CE Core: Add stop message in FCS350MI UpdForQty when entering negative forecast
quantity
A stop message is returned in API FCS305MI, transaction UpdForQty when trying to update the forecast
quantity with a negative value.
A negative value should not be allowed when updating forecast quantity in FCS305MI UpdForQty. This
is the same behavior as interactive program 'Manual Forecast/MDS. Open' (FCS350).
Processing API FCS305MI, transaction UpdForQty with negative forecast quantity will not continue to
update the forecast as it will be stopped by an error in message: "Negative value is not permitted."
Investigation of processes using this API transaction to ensure that they are not affected by the change.
Availability:
This feature is available in M3. For more information, see KB article 2252868 in the program ‘Feature
List. Open' (CMS975).
ID: M36040
M3 CE Core: Implement consistent code dropdown formats

As part of the M3 CLM and MFS UI enhancements, several small changes will impact the display of
information to the user.
The change has been requested by customers to provide consistency on how the dropdown values are
displayed across different platforms.
The information displayed on the user code dropdown fields can now be customized based on the
business need and used across the different platforms. These are the detailed changes:
• In the Mobility Core Toolbox, the customer can set the format to be displayed on the code
dropdown components.
• By default, these are displayed on the platforms:
o CLM Web: Most of the code dropdowns are set to 'Description' only. There are some
selected code columns with the setting of 'GlobalCodeID' only or 'GlobalCodeID' and
'Description'.
o CLM Mobile: As per CLM Web. Most of the code dropdowns are set to 'Description' only.
There are some selected code columns with the setting of 'GlobalCodeID' only or
'GlobalCodeID' and 'Description'. This is to provide consistency across platforms.
o MFS: Common codes are set to 'Description' only, except for MFS specific codes, where
'GlobalCodeID' and 'Description' formats are retained.

All new Infor M3 CLM and MFS customers must implement the new process for managing code and code
description display. Existing customers must investigate the new process and ensure that the review and
planning for the code and code description display is completed before April 2023.
Availability:
This change is already implemented in M3 CLM and MFS and will become mandatory in the April 2023
update.
ID: M34997
M3 CE Core: Account information will be displayed as a header in all CLM dialogs

The account number will be added to the entity being worked on to supplement the existing account
name.
To provide more information to the user.
The account number will be shown alongside the account name.
All M3 CLM customers must verify the change before April 2023.
Availability:
The layout is available in CLM. For more information, see KB article 2186691.
ID: M35594
M3 CE Core: Changes to time transaction message handling in MFS
A new message will be displayed when reallocating or declining an order in MFS, if draft time records
exist.
To make the user aware that pending labor transactions exist and give them the opportunity to send
them.
A new message is displayed.
All MFS customers must verify the change before April 2023.
Availability:
The new message is available. For more information, see KB article 2248641.
ID: M35634
M3 CE Core: EDI Payment Proposal SyncM3EDIRemittanceAdvice BOD to include Break by

Payee
SyncM3EDIRemittanceAdvice has been enhanced to be sent per payee, triggered by document number
520.
Previously, M3EDIRemittanceAdvice for payment proposals was triggered in 'Suppl Payment Proposal.
Open' (APS130) using document number 500 and could contain invoices for all payees of the payment
proposal. The TradingPartnerID element in the BOD was set to the bank account ID, that is, the
company's bank account used for the payment.
Since the purpose of this BOD is to notify the payee of incoming payments, a payee should only receive
information about their own invoices and should not be able to see invoices from other payees.
This change is implemented with a feature toggle in 'Feature list. Open' (CMS975), Feature ID = 2243983.
When the toggle is active, a SyncM3EDIRemittanceAdvice is sent per payee in the payment proposal with
document number 520, the TradingPartnerID element in the BOD is set to Payee, DocumentID/ID is set
to the supplier payment proposal number concatenated with the payment order and payee
(PRPN+PYON+SPYN), and the TotalAmount element in the BOD is set to the total of the included invoices.
The standard event analysis rule
M3EDI_M3EDIRemittanceAdvice/MBMInitiator_REQUEST_M3EDIRemittanceAdvice has been updated
to accept events from both document number 500 and 520. When the toggle is inactive, only events
for document number 500 result in a BOD sent to ION. When the toggle is active, only events for
document number 520 result in a BOD sent to ION.
Configuration for each payee is done in (CRS945) for document number 520 and in (CRS949) for
MBMEVENT (Rcvr ref data 3=M3EDIBOD).
Only payment methods with payment class = 3-Bank transfer/credit card are supported. In 'M3
Document. Open' (CRS928), document number 520 is connected to Printer file=APS162PF.
On the receiving side, impact of the change in the TradingPartnerID element from Bank account ID to
Payee, change in DocumentID/ID element from supplier payment proposal number concatenated with
the payment order to supplier payment proposal number concatenated with the payment order and
payee, must be evaluated.
Availability:
This feature is available in M3 and will be activated automatically in the April 2023 release. For more
information, see KB article 2243983 in the program ‘Feature List. Open' (CMS975).
ID: M35716
M3 CE Core: Additional panel to select PO category type when creating PO type record in
(PPS095)
‘Purchase Order Type. Open’ (PPS095) configurable views can be managed including Purchase order
category (POTC).
The Purchase order category (POTC) field is not a primary key in (PPS095), but it controls some of the
fields on the other panels in (PPS095) when creating a PO type record.
The PO order category (POTC) is no longer an input field in panel B1. A new E panel is required to select
the PO category when creating the PO type in (PPS095) interactive. The POTC is controlling some fields
on the other panels, and therefore it is needed to be created in this way.
None.
Availability:
ID: M35748
M3 CE Core: MCO Invoice spec item number field populated with misc. cost type
The item number field on the MCO invoice specification will be updated with the cost type for
miscellaneous cost transactions.
The previous logic populated the item number field on the invoice specification with the product
number. This was incorrect as it had no relationship to the miscellaneous cost transaction.
When the setting ‘Miscellaneous cost defined as item’ is selected in ‘Setting - Maintenance 1’
(CRS788), parameter 49, the item number field on the MCO invoice specification in ‘Maint CO. Check
Preliminary Invoice Spec’ (COS170) will be updated with the Miscellaneous cost types field (AMTY).
Availability:
The new capabilities are available in M3. For more information, see KB articles 2245252 and 2246192
in the program ‘Feature List. Open' (CMS975).
ID: M35904
M3 CE Core: Accounting events now retrieved from the equipment on the WO operation
Accounting events MO10 and MO20 are now retrieved from the equipment defined on the work order
operation.
The assignment of accounting events is more accurate when the equipment on the work order operation
is different than the one defined on the work order header.
If an equipment number is specified on the work order operation, then the accounting events MO10 and
MO20 will be retrieved from that equipment, rather than the equipment defined on the work order
header. Only these two events are affected.
Availability:
The new capabilities are available in M3. For more information, see KB article 2246191 in the program
‘Feature List. Open’ (CMS975).
ID: M35905
M3 CE Core: Change to the validation in the labor sell rate API (COS024MI)
The validation of fields in API COS024MI/Add have changed.
The validation of fields in API COS024MI/Add were nor aligned with the validation used within the
interactive function in 'Labor Sell Rate. Open' (COS024).
The API transaction will require that fields 'Start value 2' to 'Start value 5' are populated in the same way
as the interactive function.
Availability:
‘Feature List. Open' (CMS975).
ID: M35907
M3 CE Core: Changes in WO screens for time zone handling

Changes to time zone handling and display in work order functions.
To make time zone information more visible to avoid confusion.
In 'Work Order. Close' (MOS050), the time zone setting field can either be a time zone defined in 'Time
Zone. Open' (DRS045), or the value *USER if the time zone should be retrieved from the user. The user
time zone is retrieved from these programs:
• 'User. Access per Company & Division' (MNS151)

• 'User. Open' (MNS150)
• Division. Open' (MNS100)
If the setting field is blank, the time zone is retrieved from the place of load of the warehouse. The dates
and times are displayed in the selected time zone but are converted back to &SYS time before related
data is validated and tables are updated.
The time zone field has been added in 'Work Order Operation. Report' (MOS070) and 'Report Single
Timesheet Transaction' (MOS077). If you report a work order that has a different time zone compared
to the ones displayed in (MOS077), a warning message is displayed emphasizing that it is now a different
time zone than the one you are currently about to report.
Availability:
‘Feature List. Open' (CMS975).
ID: M35908
M3 CE Core: (TXS030) updated to support configurable views
'Fiscal Representation. Open' (TXS030) has been updated to support configurable views. API support will
also be introduced.
Configurable views have been added, and API support will be introduced.
None.
Availability:
This feature is available as of the April 2023 update of M3. When available, see KB article 2282540 in the
program ‘Feature List. Open' (CMS975).
ID: M35842
M3 CE Core: Change in logic for location selection for a material on a WO operation

In response to feedback received from customers, the location stated on the WO operation in 'Work
Order. Open Line' (MOS101) should be used when using a pick list and the dispatch policy is defined on
the order type in 'Work Order Type. Open' (MOS120).
To provide a solution that is consistent with the existing process for requisition orders.
The location from (MOS101) will now be used in the scenario described.
All existing customers should test the new logic before April 2023.
Availability:
The feature is available in M3. For more information, see KB article 2252834 in the program ‘Feature
ID: M36105
M3 CE Core: Validation added when deleting a virtual field in (CMS012)

Deletion of a virtual field that was in use in the XML structure was previously possible and could cause
issues in the XML structure.
A validation in 'Virtual Fields. Connect' (CMS012) and CMS012MI/DelVirtualField has been added to
ensure that the virtual field is not used. If it is, the deletion will not work, and an error message is
displayed.
If CMS012MI/DelVirtualField is used, ensure the validation does not affect the current functionality in a
negative way.
Availability:
This feature is available in M3 with automatic activation as part of the April 2023 update. For more
information, see KB 2257140 in the program ‘Feature List. Open' (CMS975).
ID: M36204
M3 CE Core: H5 Export to Google Sheets migration to newer Google Identity Services

H5 Export to Google Sheets migration to newer Google Identity Services as Google Sign-In JavaScript
platform library will no longer be supported after March 2023.
Google Sign-In JavaScript platform library will no longer be supported after March 31, 2023. The changes
must take place so that the Google Sheets feature continue to function.
Google Identity Services will be stateless, and the transaction will be token based rather than session
based. Thus, an M3 user will now be required to choose a Google account to use every time the export
to Google Sheet is performed.
None.
Availability:
ID: M36000
M3 CE Core: Decommission low level transactions from EVS001MI

These EVS001MI transactions have been removed:
• StartFineTrace
• StopFineTrace
• GetLogFile
• RtvLogFile
• LstLogFiles
• LstVariables
• LstCallStack
• LstConcepts
• StartConceptLog
• StopConceptLog
• StartDynaTrace
• StopDynaTrace
• StartTraceUser
• StopTraceUser
• LstTraceUsers
• GetVariable
There is business case for these low-level API calls.
The concerned EVS001MI transaction will no longer be available.
None.
Availability:
This change is available as of the April 2023 update of M3 Business Engine with automatic activation as
part of April 2023 release. When available, see KB article 2261395 in the program 'Feature list. Open'
(CMS975).
ID: M36286
M3 CE Core: GCM – Deviation between agreement and costing model on purchase orders
A deviation between agreement and costing model can emerge on a purchase order line when running
the grower contract management flow. Each line in a grower contract agreement is required to have a
costing model in 'Purchase Agreement. Open Lines' (PPS101), which is set and displayed in 'Purchase
Order. Open Lines' (PPS201) during PO creation. The development is divided in two different scenarios.
It should be possible to change the agreement number or origin address from (PPS201) and
PPS200MI.AddLine when creating a new purchase order line. Origin address could be used as an object
in (PPS101) for different agreement lines, which could lead to different costing models. Changing any of
these parameters could affect which costing model to use and should therefore automatically be
updated when required. The same logic should be applied when creating or updating agreement number
or origin address from the PO batch line ('Purchase Order Batch. Open Lines' (PPS371) and
PPS370MI.AddLine). This is because creation of the purchase order is done after it has been validated in
'Purchase Order Batch. Open' (PPS370). MPOEXP (Charges) is created based on the costing model picked
from the agreement line.
Once the purchase order has been created, it should not be possible to update the agreement number
or origin address from (PPS201) and PPS200MI.UpdLine. This is because MPOEXP (Charges) connected
to the purchase order line has been created. A stop message should be displayed when trying to change
the agreement number or origin address on an existing purchase order, (PPS201) and
PPS200MI.UpdLine. The stop message: "Change is not allowed on a Grower Contract Order" is displayed.
Also, it should not be possible to release a PO batch order in (PPS370) if there is an inconsistency
between agreement number or origin address and the costing model on the batch order line. An error
message should be displayed during validation of the order. The validation message: “Costing Model &1
is invalid” should be displayed.
None.
Availability:
ID: M35990
M3 CE Core: Status cannot be set to 2 or 3 when receiving inspected by- or co-products via
API
When reporting inspected (QACD = 1) co- and by- products via interactive, the status field is not visible
and cannot be set. However, when reporting via API, it is possible to set the status to 2 or 3 and the
balance ID is created with the specified status.
User should not be allowed to change status for inspected by- and co-products via PMS080MI and
PMS090MI.
The error message "Status 2/3 is invalid" is displayed when Status 2 or 3 is specified in
PMS080MI.RptByProduct and PMS090MI.UpdCoProdReport.
None.
Availability:
This feature is available in M3. The feature will be automatically updated as part of the April 2023
release. For more information, see KB article 2263788 in the program 'Feature list. Open' (CMS975).
ID: M36306
M3 CE Core: The following Features are now toggled on

Feature toggles which are displayed in M3 function (CMS975) within action month of April 2023 will
now be enforced activated. After this, it is not possible to deactivate the toggles.
The testing period for toggles are limited.
Feature toggles are enforced activated.
Validate that all changes to features are managed.
Availability:
This feature is available as of April 2023 update of M3 CE and will be automatically activated as of the
April 2023 CE. When available, see KB article 2288360 in the program 'Feature list. Open' (CMS975).
ID: M37250
M3 CE Core: Order costing status removed from primary key and added as a separate field
The order costing table (CPOHED) had the order costing status as part of the primary key. Sometimes,
dumps are encountered since the status has changed, or another job wrote the record in the database.
The existing order costing status stored in the PCAS field will always be set to 0 and the actual value of
the status will be stored in the OCST field.
No action required before. But after activation of this change, some actions must be performed.
The XML structures for CAS320 (CAS321PF), CAS170 (CAS171PF), and CAS550 (CAS551PF) must be reset
to standard to incorporate the new fields in the structure or manually updated. The PCAS field should
be removed and OCST should be added. If user-defined reports have been added or if the reports have
been modified, updates may be required. For additional information, see KB 2123349.
The views for 'Order Costing. Display' (CAS310) can also be reset by starting 'View. Open' (CRS020). Click
Actions and select F13 - Settings, then click Actions again and select F15 - Gen Metadata.
Availability:
This feature is available as of the April 2023 update of M3. For more information, see KB article 2241285
in the program 'Feature list. Open' (CMS975).
ID: M36394
M3 CE Core: Authority check for Facility has been added in (PPS283)

A stop message is now displayed in 'Recalculation selection' (PPS283) when trying to perform
recalculation for a facility that the user is not authorized to work in.
An authority check for facility was missing in (PPS283). Users were able to run the recalculation for an
incorrect range of orders, for example, for facilities the users were not authorized to work in.
A stop message has been added in (PPS283) if the user is not authorized to work in the facility
specified.
None.
Availability:
This feature is available in M3 and will take effect as part of the April 2023 update. For more
ID: M35898
M3 CE Core: PDS001MI should not allow version management for Family and Variant items
Version Management in the M3 Product Structure is not allowed for Family and Variant items. This
means that it will not be allowed to set Version Managed (VRNF) to 1 anymore in PDS001MI.
During the development of Version Managed, a limitation was set for Family and Variant Items. In
PDS001 interactive, it is not possible to set items with Configuration Code set to 2 or 3 as version
managed. However, PDS001MI Add and Update transactions has no checking of this and allows to set
them as variant items resulting to unexplored issues such as phantom explosion.
PDS001MI.Add and Update transactions now displays an error message 'Version Managed 1 is invalid.'
when item has Configuration Code 2 or 3.
None.
Availability:
This feature is available in M3 and will be activated as part of the April 2023 update. For more
ID: M35593
M3 CE Core: Deactivating or setting the license type to 4 for an autojob user is disabled
The option to deactivate a user or change the license type of a user maintained in 'Subsystem. Open'
(MNS050) or 'Subsystem Job. Open' (MNS051) for an auto job user is now disabled.
Changing the user status to "Preliminary" or setting the license type to "Non-licensed user" for an auto
job user will stop the auto jobs from working properly.
A user that exists in an auto job in (MNS050) or (MNS051) is not allowed to be set as License type 4 nor
set to Status 10 that is, set as a non-licensed user or deactivated.
None.
Availability:
This feature is available in M3 and will be activated as part of the April 2023 update. For more
ID: M37022
M3 CE Core: Indexes changes on table OCUSCH to enable customer order changes per
customer or division
Custom lists and user-defined sorting options for the table OCUSCH related to 'Customer. Connect
Charge' (OIS003) must be regenerated following an index change where Division has been added as a
00-key (view STD01-01) and a new index is added to support a new view (STD01-02) in (OIS003).
The index change has been made to enable new functionality within in (OIS003), which will allow the
user to add and maintain charges per division as customer local exceptions.
The user must regenerate custom views, sorting orders, and sorting options for the MX-tables using
'View. Open' (CRS020), 'Sorting Order. Open' (CRS022), and 'M3 File. Create Sorting Options' (CRS021).
If this is not done, sorting by the division will not work as expected.
Modify possible scripting in ETL tools and clear Data Lake Compass data objects to handle the new
column in the unique key. See KB 2180699.
Availability:
This change will be made as part of the April 2023 update of M3 and will have an immediate effect
without toggle changes. When available, see KB article 2283020 in the program 'Feature list. Open'
(CMS975).
ID: M37080
M3 CE Core: Enhancement Day types in Job Scheduler

'Job Schedule Calendar. Open' (SHS060) will now consider 'Day type' when generating a job schedule
calendar when 'Every month' is used together with 'On day' 98 and 99. If the date at the end of the
month or period does not fulfill the day type criteria, it will retrieve the latest date that does fulfill it.
The field help for 'On day' has also been updated to reflect this new behavior.
In 'Job Schedule Calendar. Open' (SHS060), when using 'On day' = 98 or 99, the 'Day type' wasn't
considered when generating the job schedule calendar, hence it was not possible to set up a schedule
for example last bank day of the month.
Day type is now considered also for 'On day' = 98 and 99.
If the old behavior is preferred in 'Job Schedule Calendar. Open' (SHS060), you need to make sure that
'Day type' = Calendar days.
Availability:
This feature is available as of March 2023 update of M3 and will be automatically activated as of the
April 2023. For more information, see KB article 2231465 in the program 'Feature list. Open' (CMS975).
ID: M37024
M3 CE Core: IEC Message ID Duplicate Detection

Duplicate detection on Message ID in IEC will be enabled for all.
IMS communication does not guarantee single message delivery, which introduces a small risk for
inbound messages to be processed several times. IMS communication provides a Message ID for all
messages. This Message ID is set by ION and is unique per message. It is recommended to perform
duplicate checking on this Message ID to avoid duplicate message processing.
Duplicate detection for inbound messages through IMS communication will be performed using Message
ID.
If you have gotten exceptions from the currently implemented duplicate checking on message payload,
enable duplicate checking on Message ID on the Enterprise Collaborator Administration > Settings >
Feature Toggle Setting page and retry your messages. If you do not have this problem, you do not need
to do anything.
Availability:
This feature toggle for Message ID validation is available in M3 and will be automatically activated as
default as of the April 2023 update of M3. For more information, see KB article 2285955 in the program
'Feature list. Open' (CMS975).
ID: M37054
M3 CE Core: Information browser categories (IBCA) starting with 'M3' will be blocked from being
created, changed, or deleted.
The API transactions CMS010MI.AddInfoCat and ImportInfoCat will not allow information browser
categories (IBCA) starting with 'M3' to be created, changed, nor deleted.
In 'Information Browser Category. Open' (CMS010), it's not allowed to create information browser
categories starting with 'M3'. An error message is displayed: 'The first two characters, M3, are reserved
for the standard version of M3 Business Engine.'. The same behavior should also apply in the API
CMS010MI, since only standard content delivered by Infor M3 should start with 'M3'. Now, when we
start delivering standard lists in CMS010 which starts with 'M3', used by M3 Experience Designer
template applications delivered by Infor M3, we want to correct this to ensure that duplicates cannot be
created. The standard lists that start with 'M3' cannot be changed or deleted, as the template
applications may otherwise stop working, instead they can be copied.
Information browser categories (CMS010-lists) starting with 'M3' cannot be created via the API
transactions CMS010MI.AddInfoCat and ImportInfoCat. CMS010-lists starting with 'M3' cannot be
changed or modified via CMS010 or via API.
If you have a custom integration where lists starting with 'M3' may have been created via API
transactions CMS010MI.AddInfoCat or ImportInfoCat this can be checked in 'Information Browser
Category. Open' (CMS010). If you have any CMS010-lists starting with 'M3', copy the list and give the
copied list a name without 'M3' as the two first characters. Then delete the list starting with 'M3'. If the
list starting with 'M3' is used anywhere, replace it with the copied list.
Availability:
This feature is available as of the April 2023 update of M3 CE and will be automatically activated as of
the April 2023 update of M3 CE. For more information, see KB article 2284472 in the program 'Feature
ID: M37181
M3 CE Core: Sales Hub CE - Support for user personalization in customer search list
(Filtering, sorting, hiding, and reorganizing columns)
Infor Sales Hub is extended with new functionality to personalize, filter and sort columns in customer
lists.
To improve the user flexibility in forms of personalization, filter and selection capabilities when searching
for customers and finding customer specific information.
New grid list layouts for Customer Search and customer subtabs Delivery Addresses, Order History,
Quotations, Invoices and Deliveries.
In all these lists, personalization, filter, and selection capabilities were improved.
None
Availability:
ID: M37094
Changes requiring advance customer actions planned for October 2023
M3 CE Core: Introduce multiple reconciliation dimensions in the Internal Reconciliation

The automatic internal reconciliation must be possible to run based on multiple reconciliation
dimensions and a new field for reconciliation reference must be possible to use.
A new program suite has been added to work with internal reconciliation. The reconciliation rules for
and account needs to be added in 'Accounting ID. Enter Reconciliation Rule' (CRS634). The automatic
reconciliation is performed in ‘Reconciliation. Create’ (GLS380). The reconciliation result is displayed in
‘Account. Reconcile Internally’ (GLS385) and ‘Reconcile Internally. Display Details’ (GLS386). Manual
reconciliation is started from (GLS385) and the manual selection of records to be included in the
reconciliation is done in ‘Reconcile Internally. Create Manual’ (GLS387). The current internal
reconciliation performed in ‘Account. Reconcile Internally’ (GLS185), ‘GL Account. Reconcile
Automatically’ (GLS190), and ‘GL Account. Display Trans for Reconcil’ (GLS195) will not be possible to
use anymore.
The rule for internal reconciliation must be setup in (CRS634). The users should use (GLS380), (GLS385),
(GLS386), and (GLS387) instead when performing manual and automatic reconciliation.
Availability:
This feature is available in M3. For more information, see KB articles 2173273 and 2173274 in the
program 'Feature list. Open' (CMS975).
ID: M35948
M3 CE Core: Change to the injury-free setting in MFS

The injury-free check box, displayed when reporting labor time, will change format from being a check
box to a dropdown.
To make the MFS process consistent with injury-free reporting within Infor M3.
A drop-down field will be displayed instead of a check box.
All MFS customers must verify the change before April 2023.
Availability:
The new dropdown field is available in M3. For more information, see KB article 2246190.
ID: M35538
M3 CE Core: Change leasing price index update process
The leasing price index will be calculated in a different way.
Customers have requested that the leasing price index calculation should be more accurate and use
similar logic as the legacy M3 leasing solution.
The leasing price index calculation will consider more variables and utilize new fields that will be visible
in the leasing functions.
This action is only needed if using leasing functionality with price index update. If this is the case, all
leasing lines with an additional charge having record type L and a price index set on ‘Rental Agreement.
Connect Additional Charge’ (STS103/E) must be updated with a value in the new field Orig idx value
(IXVO). The value in Orig idx value will be used in the calculation of the new price for the additional
charge. If no value is found in this field, price index update will not be done.
Note: This change must be done after activating the toggle, for the field to be visible in ‘Rental
Agreement. Connect Additional Charge’ (STS103/E), but before the next price index update takes place
in ‘Leasing Price Index. Enter Value’ (LTS401). The update can be done in two ways:
• By manually setting Orig idx value (IXVO) and Curr idx value (IXVA) on ‘Rental Agreement. Connect
Additional Charge’ (STS103/E);
• By removing and resetting Price index (IXCD) in ‘Rental Agreement. Connect Additional Charge’
(STS103/E) to get Orig idx value and Curr idx value defaulted from Leasing Price Index. Enter
Value’ (LTS401).
For more information on how the periods in ‘Rental Charge Curve. Open’ (STS111) are affected by these
fields, see the KB article 2242205.
All M3 customers must verify the change before October 2023.
Availability:
ID: M35833
M3 CE Core: Harvest date validation changed at MO receipt

It makes it hard to report receipt if there are harvest managed materials which do not have harvest date
in the Bill of Material, especially if issue method 3 or 5 is used.
No stop message is given if materials, which are not harvest managed, are not reported at the time of
the MO receipt.
None.
Availability:
This feature is available as of the April update of M3. For more information, see KB article 2280337 in
the program 'Feature list. Open' (CMS975).
ID: M37013
M3 CE Core: New warning messages added to (CMS041)

New warning messages have been added to 'Event Based API Calls. Open' (CMS041).
Currently, there is no message warning the user that either the lack of filters or faulty filters can cause
performance issues or even a loop when the event-based API calls listens to its own updates.
New warning messages have been added.
Ensure that the users are aware of the change and the strong recommendation to use relevant filters
when creating event-based API calls.
Availability:
This feature is available in M3 and will be activated as part of the October 2023 release. For more
information, see KB article 2270099 in the program ‘Feature list. Open’ (CMS975).
ID: M36395
M3 CE Core: Configurable browse capabilities added for Chart of Accounts in (MNS175)

Records from Accounting identities table (FCHACC) will now be shown in custom list or configurable
browse in the same way as in 'Accounting Identity. Open' (CRS630). When logged in current division,
records are shown for the division if it exists. Otherwise, it shows blank division. When logged in blank
division, records for both blank and non-blank division are shown.
Increased search functions for accounting identities.
Records from FCHACC table that will be shown will depend on the logged in division.
None.
Availability:
This feature is available M3. For more information, see KB article 2259562 in the program 'Feature list.
Open' (CMS975).
ID: M36253
M3 CE Core: Status on (OIS010) customer order types
Enhanced control at customer order (CO) entry to avoid the use of certain CO types.
A new setting, CO type status, has been introduced in 'CO Type. Open' (OIS010/E).
Upon implementation, the new CO types at time of creation in (OIS010) will be set in a preliminary status
to avoid being used at CO entry until finalized and defined with a definite status.
This is controlled by defaulting the new setting, CO type status, to 10 = “Preliminary” at time of CO type
creation in (OIS010). This implies a new mandatory step to update the status to 20 = “Definite” to enable
the use of the CO type at customer order entry.
The new field will also be included as input field for OIS010MI.Add and Upd transactions and as output
field for OIS010MI.Get and Lst transactions.
Review the existing integration and testability scripts that includes creating CO types to consider the new
CO type status.
Availability:
This feature is available in M3 Business Engine. For more information, see KB article 2266229 in the
ID: M36270
M3 CE Core: OIS100MI Confirm to only allow batch submission

Running the Confirm action in interactive mode provides a user experience which is not appropriate to
the solution. Batch mode is a more appropriate method for Batch Order Entry Processing.
The process for OIS100MI Confirm will only be available to run in batch mode. Interactive submissions
will not be allowed.
Any integrations or extensions using this API should be reviewed and adjusted to ensure batch mode is
used. If you run OIS100MI.Confirm with 'Y' as input in the Confirmation type (CTYP) field, the transaction
is run in batch and a reserved customer order number is returned.
Availability:
The mandatory change from interactive mode to batch mode can be made immediately as both are
already supported. For more information, see KB article 2263472 in the program 'Feature list. Open'
(CMS975).
ID: M34760
M3 CE Core: M3 Streaming to Infor Data Lake by default
M3 Streaming ingestion to Infor Data Fabric enables a direct channel to Data Fabric Pipelines and will
not use ION to feed Data Lake.
To support direct ingestion to Data Fabric for further pipeline to a destination database or similar data
receiver at the customer, M3 is now supporting Streaming ingestion to Data Fabric.
Data Fabric will pass streamed data into pipelines defined by the customer, and Data Lake will get the
stream into files every 10 minutes or after 5MB of size.
ION is not part of this architecture which means that ION Data Flows will not transport M3 data.
There is a switch in M3 Data Lake Publisher that changes the publication method from ION to streaming.
After switching to Streaming, it is not possible to go back to ION ingestion method.
Availability:
This feature is available as of the April 2023 release planned to be synched with Data Fabric Pipeline
general availability. For more information, see KB article 2290669
From October 2023, new tenants will have streaming as the default ingestion method for M3 publishing
to Data Lake. The toggle in Data Lake Publisher, will still be visible but in the disabled 'streaming state'
for those customers that may have been promised by Sales to still use ION for a while.
ID: M34156
M3 CE Core: Get correct cost price in KIT components when unpacking KIT with an Alt U/M
When transferring or unpacking a KIT mother item from one warehouse to another, we can set the KIT
to be split into the individual components at the receiving division.
If the KIT has an alternate unit of measure available, the average cost of the individual components in
the receiving facility is incorrect as it is not applying the alternate unit of measure in the average cost
calculation.
A new method that permits to calculate the cost price for the KIT components in the unpack process
has been introduced. In this new calculation, we retrieve the U/M for the KIT item and for the KIT
components in two different variables. If the basic U/M used for the KIT component exists in MITAUN
(MMS015) as an alternative unit of measure for the KIT item, then the cost price is calculated using
'conversion factor' and 'conversion form' from MITAUN.
Calculation of cost prices for KIT components, after unpacking kit at goods receipt for distribution
orders, were incorrect in the transaction history.
Accounting numbers are also affected and updated with wrong amounts.
Calculation of cost prices in the transaction history during the unpack kit at goods receipt process are
now correct using the conversion form in the alternative U/M.
Amounts in the accounting numbers are also well calculated.
Investigation of the unpack KIT process using different flows with and without alternative U/M in KIT
fashion items.
Availability:
This feature is available in M3 and will be automatically activated in the October 2023 update of M3
Business Engine. For more information, see KB article 2270796 in the program ‘Feature list. Open’
(CMS975).
ID: M36414
M3 CE Core: Tax calculated at invoice recipient location

Three geographical codes are defined for a customer invoice when sales tax is calculated: administrative
origin code, the deliver-from code, and the deliver-to code. The deliver-to geographical code is retrieved
from the customer or the delivery address of the customer, but for India this is now replaced since the
tax decision for India should be based on the address of the payer or invoice recipient instead of the
delivery address.
The tax rates for the deliver-to geographical code are retrieved as follows:
•For manual customer invoices, from the payer on ‘Customer Invoice. Enter Manual’ (ARS120/F)
•For internal customer invoices, from the payer connected to the customer on the internal
customer invoice
• For customer order invoices, from the invoice recipient
• For maintenance customer order invoices, from the payer connected to the order and for a split
payer invoice, from the split payer
• For rental management invoices, from the payer address (address type 3) and if no address, from
the payer
• For project order invoices, from the payer address (address type 3) and if no address from the
payer
Ensure that M3 is set up to comply to the tax rules required when this update takes effect.
Availability:
list. Open’ (CMS975).
ID: M36338
M3 CE Core: Decimal field formatting has been changed for initial load through (EVS006)
Decimal field formatting has been changed for Initial load through 'Initial Load. Open' (EVS006) to be in
sync with M3's formatting standard for events.
The decimal format in the generated initial load events did not adhere to M3 standard.
Decimal field formatting has been changed. For example, for a field with two decimals, it has changed
from '000000000075845' to '758.45', leading zeros are removed, and a decimal point is added.
Customers must review their use of numeric fields from Event Data from Initial Load (EVS006/EVS007)
in Custom BOD usage and other mappings in IEC. No action needed for standard BODs and mappings.
Availability:
This feature is available in M3 and will be activated automatically as part of the October 2023 release.
For more information, see KB article 2269348 in the program ‘Feature list. Open’ (CMS975).
ID: M36802
M3 CE Core: Performance improvement for MMS850MI to create stock transaction history in

batch mode
Location movements using API MMS850MI should not create stock transactions interactively. Exceptions
exist for example sublot items. This also applies to package movements using 'Packages in Stock. Open'
(MMS470). These API transactions and package movement should rely on autojob MMS901 to create
stock transaction history records. These scenarios have incorrectly been using interactive update
because of an error.
MMS850MI transactions are expected to respond quicker because the creation of MITTRA records has
been moved to an autojob process. Note that delay is expected before transactions are visible in 'Stock
Transaction. Display History' (MWS070).
Any interface that expects an immediate creation of the stock transaction history must be reviewed and
adjusted.
Availability:
This feature is available in M3, where it will be automatically activated in October 2023. For more
information, see KB article 2271374 in the program ‘Feature list. Open’ (CMS975).
ID: M36872
M3 CE Core: ION API credentials file regeneration required for MFS and M3 CLM
The redirect URL string contained within the ION API credentials file will be changed.
Enhanced security.
Existing ION API will no longer work.
A new credentials file must be created containing the new redirect URL. Existing M3 CLM and MFS
Mobile app users need to use a new QR code. The new QR code must be distributed to your mobile
application users. This action can be started at any time, but must be completed before October
2023. See KB article 2197202.
To perform the action, In Mingle go to Infor ION API page, go to Authorized Apps and Add a new
application. Keep the defaults and add the following information for M3 CLM and MFS:
M3 CLM
• Name: M3 CLM Mobile
• Description: M3 CLM Mobile
• Type: Mobile – Others
• Redirect URL: https://clm.infor.com
• Download URL: https://clm.infor.com/download
MFS
• Name: MFS Mobile
• Description: MFS Mobile
• Type: Mobile – Others
• Redirect URL: https://mfs.infor.com
• Download URL: https://mfs.infor.com/download
For more information on adding new Authorized applications in Infor ION API, refer to Infor ION
Administration Guide: https://docs.infor.com/ionapi/2021-x/en-
us/ionapiag_cloud/default.html?helpcontent=fad1489670437409.html
Availability:
This feature is available in M3. For more information, see KB article 2197202.
ID: M36109
M3 CE Core: Pick deviation: Backorder management in API MHS850
When partial reporting a picking list line with a deviating balance ID, the end flag can now be activated
to close the remaining quantity. It is also possible to control the quantity to backorder.
When reporting picking, users are not aware if they use a normal pick process or a pick deviation process.
The latter did not have support of the completion flag and did not allow control of backorder quantity.
This new functionality impacts the pick deviation process, which is when picking a different balance ID
than the one allocated on the picking list line. Pick deviation is usually executed with MHS850MI pick
transactions.
When picking less quantity from a deviating balance ID and activating the end flag (OEND), the picking
list line will now be automatically flagged as complete.
When picking less than the picking list line quantity and without the 'completion flag' (OEND), quantity
picked (QTYP) and quantity to be picked (QTYO) are now used to control the quantity to backorder.
Pick deviation is now aligned to the normal pick process. If you have specific instructions when picking a
deviating balance ID, consider the new impact of the completion flag (OEND), quantity picked (QTYP),
and quantity to be picked (QTYO).
Availability:
This feature is available in M3 and will be automatically activated as part of the October 2023 update of
M3 Business Engine. For more information, see KB article 2266401 in the program ‘Feature list. Open’
(CMS975).
ID: M36727
M3 CE Core: Block the possibility to perform overpayments in (ARS118)

M3 does not support overpayment management in a proper manner. This is blocked when bank
statements are managed, and when payments are received in 'Payment Received. Record' (ARS112) but
due to incorrect controls in 'Payment Received. Record' (ARS118) overpayments can be performed.
Overpayment will no longer be allowed. Differences must be managed with on-account payments or
other accounting options.
Customers must be informed on the changed process.
Availability:
ID: M36987
M3 CE Core: Changes in WO permit reporting for time zone handling
Changes to time zone handling when reporting work order operation permits.
To make the time zone information more visible and to avoid confusion.
In 'WO Operation. Report Permits' (MOS087), the time zone setting field can be a time zone defined in
'Time Zone. Open' (DRS045) or the value *USER if the time zone should be retrieved from the user. The
user time zone is retrieved from these programs:
• 'User. Access per Company & Division' (MNS151)
• 'User. Open' (MNS150)
• 'Company. Connect Division' (MNS100)
If the setting field is blank, the time zone is retrieved from the place of load of the warehouse. The dates
and times are displayed in the selected time zone but are converted back to &SYS time before the related
data is validated and the tables are updated.
The time zone field has been added in (MOS087). The dates and times are displayed in the selected time
zone but are converted back to &SYS time before the related data is validated and the tables are
updated.
Note that the date and time in the transactions history of (MOS087) is not converted to time zone.
Availability:
‘Feature list. Open’ (CMS975).
ID: M36833
M3 CE Core: Call Vertex for rental credits

All rental credit types are now sent to Vertex.
Previously, a rental full credit invoice created using 'Credit and reinvoice' did not call Vertex, only partial
credits were sent.
All rental credit types are now sent to Vertex. This development does not include any changes in M3.
Availability:
ID: M36311
M3 CE Core: Refactor storage of purchase order information for customer order lines
Due to an important refactoring of customer order entry, we need to refactor the storage of purchase
order information for customer order lines.
Currently when creating an order-initiated customer order line that creates a purchase order, the
purchase order information managed through ‘Customer Order. Acquire Sales Item’ (OIS145) is stored
on the customer order line in OOLINE or customer batch order line in OXLINE.
The change implies that the purchase order information stored in OOLINE and OXLINE will be
deprecated, that is, the fields will no longer be updated with any value. Instead, the PO information will
be stored in a new database as we must keep the information temporarily until the firm customer order
is created. Once the PO is created, this information is obsolete.
These fields in OXLINE and OOLINE are affected:
• SUNO – Supplier
• CUCD – Currency
• PPUN - Purchase price U/M
• BUYE – Buyer
• PUCD - Purchase price quantity
• PUPR - Purchase price
• ODI1 - Discount 1
• OURR - Our reference number
• OURT - Reference type
• ORTY - Order type
Review existing integrations, views, and testability scripts that include the purchase order information
fields in OXLINE and OOLINE. The values for the fields should instead be retrieved from the purchase
order proposal or firm purchase order.
Views created for 'Customer Order. Open Line' (OIS101), 'Customer Order. Open Line Toolbox' (OIS301),
and 'Customer Order. Open Line Workbench' (OIS302) containing any of the affected fields with an OB-
prefix, for example, OBSUNO, must be changed to use the corresponding fields with an &-prefix, for
example, &SUNO.
Availability:
This feature is available in M3 Business Engine. For more information, see KB article 2270787 in the
ID: M36945
M3 CE Core: Planned internal CO issue date no longer use supply lead time
In the internal sales process, the planning date for the planned CO demand is now calculated from the
supply lead time, but rather transportation lead time from 'Supplier. Connect Transp Lead Times'
(PPS010).
In the internal sales process, the planning date in the material plan for the planned CO demand (order
category 310) has been calculated by subtracting the supply lead time from the requested delivery date
of the PO/POP.
The supply lead time (LEA1) in 'Item. Connect Warehouse' (MMS002) for internally purchased items was
meant to match the transportation time on the supplier's side before the delivery point, since the
transportation lead time set up in (PPS010) was only the transportation lead time on the buying side
after the delivery point. This meant that the supply lead time (LEA1) could not include the lead time for
supplier to supply the goods.
This design was difficult to explain, and in situations where the buying side must take the internal
supplier's own lead time into account, the planner must set the master scheduled = 1 and a planning
time fence (PTF) that includes both transportation and the lead time in the selling warehouse.
This change will only have an impact if the Internal sales process is used, that is, items purchased from
suppliers with supplier type 7-'Internal supplier', shipped by a CO from another warehouse.
The field Supply lead time (LEA1) no longer affects the planning date in the material plan for the planned
CO demand (order category 310).
The planning date in the material plan for the planned CO demand (order category 310) is now calculated
by subtracting the internal supplier's transportation lead time from the requested delivery date of the
PO/POP. The internal supplier's transportation lead time is defined in (PPS010).
1. Identify internal suppliers that use delivery terms with goods responsibility 2 or 3, where some
transportation time is under the liability of the supplier/selling warehouse.
2. In (PPS010), define the transportation lead time in fields TLE1 (if goods responsibility = 2) or both
TLE1 and TLE2 (if goods responsibility 3).
Availability:
ID: M36081
M3 CE Core: New error message is added in (PPS917) and displayed in (PPS171)
A new error message 'K1' is added in (PPS917) and displayed in ‘Planned Purchase Order. Open’ (PPS171)
if the price is manually changed in 'Purchase Requisition. Open' (PPS180) and the used 'Purchase Order
Type. Open' (PPS095) parameter 161- agreement check is active and 320- representative price is set to
2- Price according to agreement.
In 'Purchase Order Requisition. Open' (PPS180), the user is allowed to change the price of an item with
an existing active purchase agreement. The created planned purchase order from (PPS180) is
automatically created in 'Planned Purchase Order. Open' (PPS170) and it is possible to release with price
different from the referenced purchase agreement even though the used PO type 'Purchase Order Type.
Open' (PPS095) parameter 161- agreement check is active.
When the price for item with an existing active purchase agreement has been changed in (PPS180), the
field representative price in (PPS180/F) is automatically set to 1-manually-entered price. In (PPS171), the
error message 'K1- The purchase price is manually entered and different from the agreement number'
is displayed for the created planned purchase order from (PPS180) if used (PPS095) parameter 161-
agreement check is active and 320-representative price is set to 2-Price according to agreement.
Therefore, this prevents the release of the planned purchase order from (PPS170).
None.
Availability:
ID: M36337
M3 CE Core: New button and workflow change in M3 CLM

A new button has been added to the opportunity dialog to permit an activity to be created.
To simplify the process of creating an activity from an existing opportunity.
A new button will be displayed in the opportunity dialog.
All M3 CLM customers must verify the change before October 2023.
Availability:
The layout is available in M3. For more information, see KB article 2189079.
ID: M35701
M3 CE Core: Facility Authorization check in (MMS350) when Warehouse field is blank
A stop message is returned if the user has no authorization to a facility when Warehouse To and From
fields are blank in ‘’ (MMS350).
Facility Authorization check should be performed for the user when warehouse fields are blank. This is
the same behavior when the Warehouse To and From fields contain values.
Processing (MMS350) will not continue if To and From Warehouse fields are blank and the user has no
authorization in a facility as it will be stopped by an error with the message "You do not have
authorization for Facility."
Investigation of processes using (MMS350) to ensure that users are not affected by the change.
Availability:
This feature is available in M3 and will be activated automatically as part of the April 2023 update of
M3. For more information, see KB article 2274014 in the program 'Feature list. Open' (CMS975).
ID: M36947
M3 CE Core: Add stop message in (RPS102) and (RPS002) when specifying invalid planned
order status
A stop message is returned in 'Material Plan. Rescheduling' (RPS102) and 'Action Message. Open per
Item' (RPS002) when trying to update the planned order status with an invalid value.
Invalid planned order status should not be allowed in (RPS102) and (RPS002). It should have the same
status validation in the planned order programs 'Planned MO. Open' (PMS170), 'Planned Purchase
Order. Open' (PPS170), and 'Planned Distribution Order. Open' (DPS170).
Updating planned order status in (RPS102) and (RPS002) with invalid value will not continue to update
the status as it will be stopped by an error message "Status &1 is invalid."
Investigation of processes using the programs to ensure that they are not affected by the change.
Availability:
ID: M37003
M3 CE Core: Change in calculation for MCO sales statistics
The line amount is now deducted with the discount amount, for invoice line types 31 (labor), 32
(material), 34 (subcon), and 36 (miscellaneous), when creating the sales statistics.
The line amount in the sales statistics table, UCSAAM in OSBSTD, was updated with gross amount,
which was incorrect.
The discount amount, UCOFRA, is now converted to and saved in local currency. The foreign currency
amount, UCCUAM, is deducted with the discount in foreign currency.
Validation against status on the MCO line to negate discounts and quantities is removed and the
discounts and quantities are retrieved from the invoice line table, ACUIVR.
31 = Amount per labor line
32 = Amount per material line
34 = Amount per subcontracting line
36 = Amount per miscellaneous line
Availability:
This change is planned to be available from April 2023. When available, see KB article 2274173 in the
ID: M37045
M3 CE Core: Change the way in which operations are added to WO’s in MFS
Adding a new operation from the main dialog screen in MFS will no longer be possible.
To remove the possibility of users linking the operation to the wrong work order.
The option to create a new operation from the main dialog screen will be removed. Users must use the
existing capability to create a new operation from within an existing order.
All MFS customers must verify the change before October 2023.
Availability:
The option to create a new operation from the main dialog screen has been removed. The option to
create an operation from within an existing order is already available. For more information, see KB
article 2247810.
ID: M35351
M3 CE Core: MWS435PF and MMS480PF to display Warehouse time not System time when
generated from event-based printing
Event-based delivery documents and picking lists should use warehouse time zone for Start date and
Start time elements in the XML printout.
The generic Start date and Start time elements in XML printouts show the current date and time in time
zone for the job running the printout, that is the user's time zone. This solution is good for normal
printouts that are explicitly requested by a user. However, for printouts such as event-based delivery
documents and picking lists, which are triggered automatically and run on a generic user, this is not a
good solution as the same user could be processing printouts connected to different warehouses, etc.
Event-based delivery documents and picking lists will override the time zone, being used for current date
and time, with the time zone for the warehouse. This impacts the generic XML elements Start date and
Start time in these printouts, which earlier have displayed current date and time in the time zone for the
auto start jobs. This logic also applies to custom fields added with 'Source of data' equal to '50-Current
date/time'.
The solution also secures that 'Display UTC offset' in 'XML Structure. Open' (CMS006) shows the correct
offset in the XML for these elements and includes daylight saving time (DST) in the offset when
applicable.
These document numbers are affected by this enhancement:
• 120 - Picking list
• 900 - Delivery note
• 901 - Dispatch advice
• 909 - Loading/unloading list
• 912 - Transport/package label
• 913 - Address label
Delivery documents are only impacted by this feature when printed using the event-based delivery
documents functionality. All other printing of delivery documents will display the current date and time
in Start date and Start time elements in the user's time zone.
Inform users about the change in the elements in XML printouts affected by this feature.
Availability:
This feature is available as of the April 2023 update of M3 and will be automatically activated as of the
October 2023 update of M3. When available, see KB article 2269176 in the program 'Feature list. Open'
(CMS975).
ID: M37074
M3 CE Core: Use customer time zone when creating rental DOs
Change in time zone logic for rental distribution orders.
The current logic, using the user's time zone for DOs is incorrect and is inconsistent with other processes
within M3.
The time zone for rental DOs will come from the customer's site address and not the user record.
Availability:
This feature is available in M3 and will be automatically activated as of the October 2023 update of M3.
ID: M36177
M3 CE Core: Change CO number validation during rental agreement entry

A check is now made during rental agreement entry to validate that the customer order number is
unique.
To bring the rental process validation of the CO number in line with other processes within M3, including
sales.
Creating or maintaining a rental agreement ag ainst a customer in ‘Customer Master. Open’
(CRS610/F) with the setting 'CO no mandatory' will now trigger a message if the CO number has already
been used
The duplicate checks are made in 'Rental Agreement. Open' (STS100/A) and (STS100/E) and 'Rental
Agreement. Create' (STS085).
To continue with the previous process, you must change the customer master setting to the new
alternative 2, 'Yes, without duplicate check'. Alternatively, confirm the new process with the new
warning message.
Availability:
ID: M36334
M3 CE Core: Change CO number validation during MCO entry
A check is now made during MCO entry to validate that the customer order number is unique.
To bring the MCO validation of the CO number in line with other processes within M3 including sales.
Creating a new MCO record against a customer in ‘Customer Master. Open’ (CRS610/F) with the setting
'CO no mandatory' will now trigger a message if the CO number has already been used.
The duplicate check is made in 'Maintenance Customer Order. Quick Entry' (COS130) and 'Maintenance
Customer Order. Open' (COS100/A).
To continue with the previous process, you should change the customer master setting to the new
alternative 2, 'Yes, without duplicate check'. Alternatively, confirm the new process with the new
warning message.
Availability:
ID: M36297
M3 CE Core: Consider currency for MCO invoice decimal rounding

The logic for rounding if the currency used is defined with zero decimal places has changed.
For currencies with zero decimals, the decimals are still saved in the MCO invoice table (ACUINV). This
causes the calculation of the sales price to create a difference, resulting in an imbalanced voucher at
invoicing.
The MCO invoice can process records for currencies with zero decimal places.
Customers working with currencies with zero decimal places must verify the change before October
2023.
Availability:
ID: M36330
M3 CE Core: Prevent creation of MCO using a service having a WO type with update material
plan equal to one
Creating a maintenance customer order (MCO) using a service or a WO connected to a work order type
'Work Order Type. Open' (MOS120) with the parameter 'Should maintenance object update material
plan' set to one will no longer be possible.
This combination of settings can lead to financial errors.
A check has been introduced in these programs to stop the possibility to connect a maintenance
customer order to a work order where the work order type has Update Material plan equal to one:
• 'Work Request. Open' (MOS170)
• 'Work Order. Enter' (MOS001)
• 'Work Request. Quick Entry' (MOS185)
• 'API: Maintenance Order Proposals' (MOS170MI, transaction addProposal)
• 'Maint CO' (COS130)
• 'Maintenance Customer Orders. Open Line (COS101)
• 'API: List Maint MCO' (COS100MI, transactions add and addLine)
Availability:
ID: M37002
M3 CE Core: Populate the responsible for reporting field

The responsible for reporting (RPRE) field is now populated when you report inspections using
MOS085MI for work order categories other than 50.
To be consistent with the behavior when carrying out the same process within M3 using 'WO Operation.
Report Inspection Result' (MOS085).
The RPRE field is populated.
Availability:
The new checkbox is available in M3. For more information, see KB article 2275893 in the program
ID: M37036
M3 CE Core: Period type for rental utilization added to rental agreement settings (STS699)
A new field, 'Period type rental' has been added to 'Settings - Rental Agreements' (STS699).
Period type (PETR) has been added rental utilization table (STUTIL). If a default value isn’t available, then
running the rental utilization display and print programs will not display any records.
A new field, 'Period type rental' (PETR) has been added to 'Settings - Rental Agreements' (STS699). When
running ‘Rental Statistics. Update’ (STS655), the field PETR in table STUTIL is set to the new 'Period type
rental' field from (STS699). If customers wish to retain the previous processing, then they should set the
period type parameter in STS699 to "1". For old records, customers should re-run STS655 for the
previous periods using the selected period type in STS699.
Availability:
The change is planned to be available from April 2023. For more information, see KB article 2277439.
ID: M37214
M3 CE Core: Harvest date functionality enabled in MHS850MI/AddMOReceipt

When reporting MO receipt via (MHS850MI), harvest date is not inherited from issued material.
MO receipt should work the same way when reporting from (MHS850MI) as in (PMS050MI) and
'Manufact Order. Report Receipt' (PMS050).
Harvest date is inherited from issued material if the product has harvest method = 2-Inherit. We also
check that harvest date managed items are issued before allowing reporting receipt.
This can add extra stop messages when using MHS850MI/AddMOReceipt.
None.
Availability:
ID: M37188
M3 CE Core: Changes to validation rules in (MOS070MI)
Labor reporting via MOS070MI ‘ReportStartStop’ and ‘ReportTravel’ should consider time zones.
Error messages appear if the API does not consider time zones.
The API will carry out more validation and take into account times zones.
Before the change:
The API checked if the exact same transaction already existed, same WO, operation start
date/time, Finish date/time.
Next, the API considered other transactions on other orders - the UTC mode input flag is not
considered correctly.
Finally, deleted transactions in status 99 were considered, and a stop message is issued, based
on those transactions.
After the change:
Time zone conversion is carried out before any validations.
Status 99 transactions are no longer considered.
A check is made to consider if there is exactly the same transaction as before. In addition, it also
checks if the reported time is within another transaction for the same WO or other orders.
Availability:
The enhanced API validation is planned to be available from April 2023. For more information, please
see KB 2278344 in the program 'Feature list. Open' (CMS975).
ID: M37185
M3 CE Core: Decommission of API CRS990MI in favor of new BROWSEMI

The old API, CRS990MI, that was used to perform a browse on M3 data from outside M3, has been
decommissioned and is now replaced by the newer API BROWSEMI.
The API CRS990MI has not been updated with the latest changes and is built on an old standard.
BROWSEMI is a newer API that has replaced the old one.
API calls to CRS990MI can no longer be performed.
Investigate any browsing performed using the old API CRS990MI. If used, replace it with the already
existing API BROWSEMI.
Availability:
The new API is available in M3 and the old API will be removed by October 2023. For more information,
see KB article 2256619 in the program ‘Feature List. Open' (CMS975).
ID: M35334
M3 CE Core: Enforce duplicate submitted block and count pop-up at batch job requests
By mistake, users have made very large selections as printouts which blocked printers for a long time.
Users have also submitted several identical jobs resulting to duplicate jobs in queue. This enhancement
will reduce these behaviors.
It will be impossible to submit duplicate jobs multiple times while the previous job is still active or in job
queue. Duplicate means identical selections and settings at the start of the job. A pop-up will also appear
for all users when the selection made for a batch job results in a large number of selected records. The
user needs to confirm the selection or re-enter the made selections.
Inform the users about these changes.
Availability:
Will be filled in once details are final.
ID: M35667
M3 CE Core: Assign MO-lot number at MO-receipt for non QMS item

In the QMS module, for a manufactured item with quality inspection with quality request, a setting on
the MO Order Type can decide whether the QI request should be created at MO release or MO receipt.
For the first scenario, a lot number will be created in Lot Master at MO release since it is needed for the
QI request to be created properly.
However, the lot number is also created in Lot Master at MO release when the quality request
functionality is not used. Furthermore, there exists another parameter 'Create lot number at MO release'
on the MO Order Type which provides the user the capability to decide when the lot number should be
generated in Lot Master or not. As such, it may be difficult to maintain the lot management in the MO
process for lot managed item without quality request.
When using the QMS module and using 'QI Request Timing' set to 1 - "Create req on MO release" on
PMS120/F, the lot number will be generated in Lot Master only when the item is quality inspected with
quality request.
If the existing functionality 'QI Request Timing' set to 1 on PMS120/F is used to create lot number in Lot
Master at MO release, the user is advised to use instead the parameter 'Create Lot Number at MO
release' set to either 1 or 2 on PMS120/G.
Availability:
This feature is available in M3 CE. For more information, see KB article 2251500 in the program 'Feature
ID: M36110
M3 CE Core: M3EDISalesOrderAcknowledge BOD has some changes related to fields and

formatting
‘M3EDISalesOrderAcknowledgement’ has been enhanced to correct a number for elements.
It has been discovered that some elements in the BOD need corrections because of either wrong field
used or wrong formatting of the fields.
This change is implemented with a feature toggle in 'Feature list. Open' (CMS975), Feature ID = 2275202.
Following fixes are implemented:
1
M3EDISalesOrder/SalesOrderHeader/RequiredDeliveryDateTime
M3: OIS101/I, Req delivery dt; Requested Delivery Date and Time when the customer wants the
delivery to arrive at the final destination.
Feature ID = "2275202" OFF: OOHEAD.RLDT+RLHM; OIS100MI/GetOrderHead; time is always
T12:00:00.000Z
Feature ID = "2275202" ON: OOHEAD.RLDZ+RLHZ; OIS100MI/GetOrderHead; fields are changed,
correct date and time;
2
M3EDISalesOrder/SalesOrderLine/RequiredDeliveryDateTime
M3: OIS101/F, Req delivery dt;
Feature ID = "2275202" OFF: OOLINE.DWDZ+DWHZ; OIS100MI/LstLineBOD; time is always
T12:00:00.000Z
Feature ID = "2275202" ON: OOLINE.DWDZ+DWHZ; OIS100MI/LstLineBOD; time is corrected;
3
M3EDISalesOrder/SalesOrderLine/PromisedShipDateTime
M3: OIS101/I, Departure date; the planned departure date + time (not the same as Planning date)
Feature ID = "2275202" OFF: OOLINE.CODT+COHM; OIS100MI.GetLine; incorrect fields; time is always
T12:00:00.000Z
Feature ID = "2275202" ON: OOLINE.DSDT+DSHM; OIS100MI.LstLineBOD; fields are changed, correct
date and time;
4
M3EDISalesOrder/SalesOrderLine/PromisedDeliveryDateTime
M3: OIS101/I; Conf dely dt; Confirmed delivery date + time at the final destination
Feature ID = "2275202" OFF: OOLINE.CODZ+COHZ; OIS100MI/LstLineBOD; time is always
T12:00:00.000Z
Feature ID = "2275202" ON: OOLINE.CODZ+COHZ; OIS100MI/LstLineBOD; time is corrected;
5
M3EDISalesOrder/SalesOrderLine/PurchaseOrderReference/DocumentID/ID
M3: OIS101/F; Ref order no; the reference to the purchase order number
Feature ID = "2275202" OFF: OOOREF.OORIDN; OIS100MI/GetLine2; incorrect field - the batch order
number from 'Batch CustomerOrder. Open' (OIS275)
Feature ID = "2275202" ON: OOLINE.OBRORN; OIS100MI/LstLineBOD; correct field - the reference to
the purchase order number, when a purchase order is created for the order line;
M3EDISalesOrder/SalesOrderLine/PurchaseOrderReference/LineNumber
M3: OIS101/F; Ref order line; the reference to the purchase order line
Feature ID = "2275202" OFF: not published
Feature ID = "2275202" ON: OOLINE.OBRORL; OIS100MI/LstLineBOD;
6
M3EDISalesOrder/SalesOrderHeader/PaymentMethodCode
M3: OIS100/H; Payment mtd AR
Feature ID = "2275202" OFF: OOHEAD.OAPYCD; OIS100MI/GetOrderHead; not translated in CRS881 or
otherwise
Feature ID = "2275202" ON: OOHEAD.OAPYCD; OIS100MI/GetOrderHead; translated in CRS881 and has
extra translation logic after that, see Specification
M3EDISalesOrder/SalesOrderHeader/Classification/Codes/Code
Feature ID = "2275202" ON: OOHEAD.OAPYCD; OIS100MI/GetOrderHead; not translated in CRS881 or
otherwise, to keep the value available in the BOD;
M3EDISalesOrder/SalesOrderHeader/Classification/Codes/Code@listID
Feature ID = "2275202" ON: Set to "Payment Methods"
M3EDISalesOrder/SalesOrderHeader/Classification/Codes/Code@sequence
Feature ID = "2275202" ON: Set to 1
7
M3EDISalesOrder/SalesOrderHeader/CustomerParty/Contact/Name
M3EDISalesOrder/SalesOrderHeader/ShipToParty/Contact/Name
M3EDISalesOrder/SalesOrderHeader/BillToParty/Contact/Name
M3EDISalesOrder/SalesOrderHeader/PayFromParty/Contact/Name
M3EDISalesOrder/SalesOrderLine/ShipToParty/Contact/Name
The field indicates the contact persons Name
Feature ID = "2275202" OFF: OCUSCO.CCCNPE; CMSO55MI/LstByCustomer; Contact persons ID is
published instead of Name
Feature ID = "2275202" ON: CCUCON.CCTX50; CRS618MI/Get; Contact persons Name is published;
M3EDISalesOrder/SalesOrderHeader/CustomerParty/Contact/ID
M3EDISalesOrder/SalesOrderHeader/ShipToParty/Contact/ID
M3EDISalesOrder/SalesOrderHeader/BillToParty/Contact/ID
M3EDISalesOrder/SalesOrderHeader/PayFromParty/Contact/ID
M3EDISalesOrder/SalesOrderLine/ShipToParty/Contact/ID
The field indicates the contact persons ID
Feature ID = "2275202" ON: OCUSCO.CCCNPE; CMSO55MI/LstByCustomer; Contact persons ID is
published;
M3EDISalesOrder/SalesOrderHeader/CustomerParty/Contact/ID@accountingEntity
M3EDISalesOrder/SalesOrderHeader/ShipToParty/Contact/ID@accountingEntity
M3EDISalesOrder/SalesOrderHeader/BillToParty/Contact/ID@accountingEntity
M3EDISalesOrder/SalesOrderHeader/PayFromParty/Contact/ID@accountingEntity
M3EDISalesOrder/SalesOrderLine/ShipToParty/Contact/ID@accountingEntity
Feature ID = "2275202" ON: OOHEAD.OACONO+OADIVI;
8
M3EDISalesOrder/SalesOrderHeader/CustomerParty/Location/Address/CountrySubDivisionCode@listI
D
M3EDISalesOrder/SalesOrderHeader/ShipToParty/Location/Address/CountrySubDivisionCode@listID
M3EDISalesOrder/SalesOrderHeader/ShipFromParty/Location/Address/CountrySubDivisionCode@listI
D
M3EDISalesOrder/SalesOrderHeader/BillToParty/Location/Address/CountrySubDivisionCode@listID
M3EDISalesOrder/SalesOrderHeader/PayFromParty/Location/Address/CountrySubDivisionCode@listID
M3EDISalesOrder/SalesOrderLine/ShipToParty/Location/Address/CountrySubDivisionCode@listID
M3EDISalesOrder/SalesOrderLine/ShipFromParty/Location/Address/CountrySubDivisionCode@listID
The field indicates listID attribute for the state
*Canada has list ID "Canadian Provinces"
*France has list ID "France - Departements"
*United States has list ID "US States"
Feature ID = "2275202" OFF: Other countries have list ID "Country Sub-divisions", hardcoded value
Feature ID = "2275202" ON: OCUSMA.CSCD; CRS610MI/GetBasicData; Other countries have list ID
"SubDivisions - [country code]"
9
M3EDISalesOrder/SalesOrderHeader/EarliestDeliveryDateTime
M3: OIS100/E, First/last date (the first part)
Feature ID = "2275202" ON: OOHEAD.FDED; OIS100MI/GetOrderHead; the Earliest Delivery Date, the
first valid delivery date for a customer order.
Usage of the M3EDISalesOrderAcknowledgement BOD must be reviewed and impact of the change must
be evaluated and addressed.
Availability:
This feature is available as of the April 2023 release and will be activated automatically in October 2023
release. For more information, see KB 2275202 in the program 'Feature list. Open' (CMS975).>
ID: M37032
M3 CE Core: New stop messages in (PPS215) and PPS215MI

New stop messages will be introduced in 'Purchase Order. Connect Charges' (PPS215) and PPS215MI.
The new stop messages will provide more details as to why changes or different options are unavailable
depending on different circumstances for the Purchase Order Charges.
Currently, the stop messages only details that an option is invalid. For example, "Option 2 is invalid", but
the messages do not detail why the option is invalid. In conjunction with an enhancement for (PPS215)
and PPS215MI, we identified a need to clarify why options are invalid. Invalid options could be because
of charge type, PO line status conditions, or other circumstances, which will be added to the stop
message.
The new stop messages will indicate why the option is invalid. The user will know if change is not
available due to goods being received, the status of the PO Lines, and if it is because of the charge type
(Internal or External), or if it is because of an Operator that does not allow changing.
None.
Availability:
ID: M36245
Changes requiring advance customer actions planned for April 2024
M3 CE Core: Use a work center with flow order to split the material reservations in the material
plan
Material reservations should only be divided into several days in the material plan if the material is
flow order enabled in 'Item. Connect Facility' (MMS003) F-panel, and if the connected work center in
the product structure has flow order (KYRE) enabled in 'Work Center. Open' (PDS010). Today, the
material is also divided if the work center is not flow order enabled - which is wrong.
Material reservations should not be divided if they are connected to a work center that are not flow
order enabled.
It will no longer work to get the material reservations divided into several days by only setting the
material to "flow order plan" in 'Item. Connect Facility'. Users also need to enable flow order for the
connected work center.
Users need to enable flow order in the connected work center.
Availability:
This feature is available as of the April 2023 update of M3 and will be automatically activated as of the
April 2024 update of M3. When available, see KB article 2283024 in the program 'Feature list. Open'
(CMS975).
ID: M37157
M3 CE Core: Updated VAT Registration Number management validation

An updated validation of Swiss VAT registration number is required. The validation is done when a new
basic data transaction is entered or edited for example customer, customer address or supplier.
VAT Registration numbers in Switzerland is now validated using CHE as the prefix instead of CH. A suffix
is also supported. The numeric part of the VAT registration number is controlled using Modulo 11.
None
Availability:
This feature is available as of the May 2023 update of M3 CE and will be automatically activated as of
ID: M37242
M3 CE Core: Removal of hard coded pickup address mapped in LoadM3EDIAdvanceShipNotice
Hardcoded value for pickup address of ASN will be removed in the mapping of
LoadM3EDIAdvanceShipNotice as this is not relevant for EDI transactions.

The hardcoded value is not relevant for EDI transactions. Initially, the mapping of hardcoded value of
pickup address was intended to bypass the parameter 56 in M3 program (CRS780) Settings - Purchasing.
When the parameter is activated, pickup address is required as input in MHS850MI. The hardcoded value
was introduced in the standard LoadAdvanceShipNotice so that the integration flow would not be
interrupted regardless of the parameter setup in (CRS780). When LoadM3EDIAdvanceShipNotice was
created, the mapping of hardcoded value was copied from the standard BOD.
After further investigation, it was decided to remove the hardcoded value for the EDI BOD as the external
trading partners will not know the hardcoded pickup address in the mapping, and to honor the validation
of inbound delivery data done by the parameter 56 in M3 program CRS780 Settings - Purchasing.
When parameter 56 in M3 program CRS780 Settings - Purchasing is activated, and the integrating party
sends LoadM3EDIAdvanceShipNotice BOD without any pickup address ID (ADID), MHS850MI error will
be encountered, requiring a pickup address ID as input.
Check the parameter 56 in M3 program CRS780 Settings - Purchasing if activated. If activated, ensure
that the LoadM3EDIAdvanceShipNotice BOD contains a valid M3 pickup address in
AdvanceShipNoticeHeader/UserArea/Property/NameValue with attribute name set to
"AddressNumber".
ID: M37144
M3 CE Core: Additional feature for custom text block functionality

All valid custom text blocks in (CMS036) were not showing in the XML file.
All customers should validate their current configuration before April 2024. If there are several active
text blocks in CMS036 that have a valid date interval, confirm that they should be printed, otherwise,
remove or change the valid date interval for the text blocks that should not be printed.
Availability:
This feature is planned to be available in April 2023. When available, see KB article 2271118 in the
ID: M37149
M3 CE Core: Corrupted records in MTEINF caused by CMS474MI.AddUdefContent
Using API transaction CMS474MI.AddUdefContent prior to this change, it is possible to add values to a
custom field for an item or supplier whose item group or supplier group respectively is not connected to
a custom field group. It causes corrupted records which are written in file 'Custom field Information
value' (MTEINF). These records cannot be displayed in program 'Update Custom fields' (CMS474) and
cannot be either deleted, with the addition that it could be moved from one item to another (or from
one supplier to another) if option 'copy' is used. This could also cause problems with DTID duplicities.
Unable to generate corrupted data in file 'Custom field Information value' (MTEINF) using API transaction
CMS474MI.AddUdefContent
Two new stop messages when using API transaction CMS474MI.AddUdefContent will be displayed:
MSGID=S_02398 Custom field group &1 is not connected to item group &2.
MSGID=S_02399 Custom field group &1 is not connected to supplier group &2.
Investigation of processes using this API transaction to make sure they are not affected by this change.
Availability:
This feature will be available from April 2023 and will be automatically activated as part of the April 2024
update. When available, see KB article 2289394 in the program 'Feature list. Open' (CMS975).
ID: M37304
M3 CE Core: E-Invoice, print invoice after government approval, submit printout job with the user
ID that created the invoice
The invoice printout job was submitted with the API user ID that updated the record with the
government approval, which is considered to be an incorrect behavior.
For E-Invoice and print invoice after government approval, the printout job is submitted with the user ID
of the user who created the invoice, thus applying the printout settings for that user.
If you don't agree with the changed behavior, please let us know as soon as possible so that we can
develop configurability for this functionality.
Availability:
This feature is available as of the October 2023 Feature Release update of M3 and will be automatically
activated as of the April 2024 update of M3. When available, see KB article 2264145 in the program
ID: M37358
M3 CE Core: MMS850MI.AddAdjust could previously adjust stock even when item has status
90
It was possible to add stock for an item which had status set to 90 using this API Transaction.
Programs like 'Quick inventory counting' (MMS310) or API MMS310MI are showing the message
'XIT0107 Item number is not permitted - status is &1'.
But program 'Received Messages - headers' (MMS850) or API transaction MMS850MI.AddAdjust do not
show the message permitting to create on hand balance for a non-stocked item.
To avoid this error a check will be added in program 'Validations batch entry' (MMS870) when using
program 'Received Messages - headers' (MMS850) or API transaction MMS850MI.AddAdjust that will
return the message 'XIT0107 Item number is not permitted - status is &1
It is currently possible to add stock for a non-stocked item (status 90) using program 'Received Messages
- headers' (MMS850) or API transaction MMS850MI.AddAdjust.
New check is added in program 'Validations batch entry' (MMS870) when using program 'Received
Messages - headers' (MMS850) or API transaction MMS850MI.AddAdjust.
The message 'XIT0107 Item number is not permitted - status is &1' will be returned for the system.
Investigation of processes using this API transaction to make sure they are not affected by this change.
Availability:
This feature is available as of the October 2023 update of M3 and will be automatically activated as of
the April 2024 update of M3.
When available, see KB article 2289553 in the program 'Feature list. Open' (CMS975).
ID: M37305
M3 CE Core: Sales Hub - Make Item Search results a configurable panel

For improved configuration, the Item Search panel will become configurable.
Some features of the panel will become optional. There will be small visual variations. Fit and function
from the old layout will be used as a basis for the standard configuration, which may be adjusted in line
with other feature capabilities. There will be a visual change to the screen.
None.
Availability:
Further details will be provided closer to the time via a KB Article.
ID: M36962
M3 CE Core: New validations for full balance ID controlled or sublot-managed items in API
program 'Package Interface' (MWS423MI)
New validations are added to the 'PackLine' and 'PackLineInNew' transactions in API program 'Package
Interface' (MWS423MI), for items setup with full balance ID control (FUBA) or for sublot-managed
items.
It was allowed to pack part of a balance ID using MWS423MI PackLine and PackLineInNew even if full
balance ID parameter is activated for the item.
It was allowed to use the API transactions on a sublot-managed items, resulting in data corruption since
sublot ID cannot be specified.
The following new validations are added in API transactions MWS423MI.PackLine and
MWS423MI.PackLineInNew:
(1) For an item setup with full balance ID control:
-When packing a complete balance ID, the transactions process successfully.
-When attempting to pack part of a balance ID, the transactions is stopped.
(2) For a sublot-managed item, packing is not allowed using API transactions MWS423MI.PackLine and
MWS423MI.PackLineInNew. Dedicated sublot transactions must be used when packing a sublot-
managed item (MWS423MI.PackSublot and MWS423MI.PackSublotInNew)
This development is implemented with a feature toggle. Feature toggle 2281470 must be enabled in
'Feature List. Open' (CMS975). Before activating, check if those API transactions are used in some
interface, and be prepared to be stopped to prevent data corruption.
Availability:
the April 2024 update of M3. When available, see KB article 2281470 in the program 'Feature list. Open'
(CMS975).
ID: M37090
M3 CE Core: Tab spacing to be added to list of restricted characters
Some programs might dump when managing records with a tab spacing.
If activated in 'system settings' (MNS090) some characters are restricted and now the tab spacing
character is also considered as restricted.
Control that no process intend to create records that include a tab spacing.
Availability:
the April 2024 update of M3 CE. When available, see KB article 2287648 in the program 'Feature list.
Open' (CMS975).
ID: M37291
M3 CE Core: Restrict setup of customer-defined fields to master data tables

A functional restriction is added to enforce that customer-defined fields (CDF) are only used on master
data tables.
CDFs are targeted towards master data only and are not meant to be used with transactional data. This
is clearly stated in the documentation and help text, but no formal restrictions have been implemented
into the setup of CDFs in program 'Customer-Defined Fields. Open' (CMS080). To avoid customers
running into issues by mistake, a stop has been added to (CMS080) for new entries, and a warning
message is added when editing existing records. This is part two of this restriction and adds remaining
transactional tables not stopped in April 2021.
CDFs have always been targeted for master data. The use of CDFs on top of transaction tables can cause
performance problems.
New CDF setup can only be performed on master data. For existing CDFs, a warning is displayed and
should be reconfigured to XtendM3 or other valid solutions.
Reconfigure any existing CDFs that are connected to transactional tables to Dynamic tables (XtendM3)
instead. They will continue to work, but are not supported, and should be avoided.
ID: M33316
M3 CE Core: MHS855 Autojob - Missing qualifiers
Some transaction types executed with MHS850MI were not routed to a task autojob and were executed
in the dispatcher autojob MHS855.
All messages executed with MHS850MI with *AUT are routed to a task autojob MHS855T1 - MHS855TA.
Review how autojobs MHS855Tx are split into several instances in MNS051.
Review how many instances of each task autojob is appropriate to cater its load.
Consult UDI for the list of qualifiers and assigned autojobs.
Availability:
the 2024.04 update of M3 CE. When available, see KB article 2284133 in the program 'Feature list. Open'
(CMS975).
ID: M37182
Important information regarding testability of M3 functions
This section lists changes that may have an impact on customer unique test scripts. Note that these are
changes to M3 functions that do not result in a change to the processes or workflow used by the end
users.
The listed programs have been re-written and test scripts can be affected by the changes. Note that
unless also included in the Impact section above, these create no visible change for the end user.
These changes are connected to a toggle:
• Customer order types (OIS014) – Rewritten to new programming standard and some
fieldnames on the B-panel has been changed. UI changes are not visible to users but possible
bookmarks (with filters) and test scripts using this function can be affected.
• Setting Product configuration (CRS585) – New panel is added (with toggle) to support additional
settings used together with Infor CPQ
Important information regarding changes to Db indexes and existing table fields
This section lists the changes that may have an impact on customer external usage of M3 data,
XtendM3 extensions that reads directly from the M3 Db as well as user-defined APIs such as
CMS100MI, EXPORTMI, and MDBREADMI. Note that these changes to M3 database are also
documented through the normal development NCDs etc. Also note that changes implemented in the
M3 Db cannot be toggled and are immediately implemented once delivered.
These changes are currently planned:
Changes to existing Db indexes
•
April 2023 update:
o OCUSCH00
▪ The fields have been changed in order where DIVI is moved. The new primary
key is: CONO, CUNO, CRID, DIVI. The old order was CONO, CUNO, DIVI, CRID.
Changes to existing fields:
• None planned.
Important information
This section includes information about best practices and other information that a user of M3 CE must
be aware of and act upon if required. Note that this information is not associated with a specific date
or M3 update.
M3 CE Core: Restrictions on data download through M3 API

M3 APIs and infrastructure used by M3 are designed for retrieval of limited sets of data and reasonable
frequency in their access.
They are NOT designed for:
• Massive data downloads
• To continuously replicate M3 Database tables to on-premises or other solutions
Best practice includes a maximum execution time of 5 minutes per API call as well as a reasonable
number of calls per time unit.
Note: Extraction of larger M3 data sets must follow best practices and be downloaded through Data
Lake or synchronized via trickle feed through M3 events. As Data Lake is part of Infor OS, see Infor OS
User Guide in this location referencing Compass functions and Data Lake ETL capabilities.
A best practices document will be published in Knowledge Base and will include instructions about how
to use Data Lake and Events, as well as further details on the directions to what is allowed regarding
M3 API usage.
Note: The earlier communicated code change to enforce best practice has been postponed to a later
date. The recommendations and enforcement of best practices through cloud monitoring is still
applicable and is published in the early announcement document as important information. Also note
that, even though restrictions are not enforced by code they can still be enforced through monitoring
and manual blockage or throttling on a tenant level. This is required in order to ensure the overall
performance and stability of the system.
M3 CE Core: Usage of filters and selection fields in Ad Hoc reporting, EXPORTMI, and
CMS100MI
The API CMS100MI, EXPORTMI, and Ad Hoc Reporting functions can currently cause excess and
unwanted load on the M3 database server. This primarily relates to the usage of field selections
without corresponding filters having been used in combination with the field selection or that there is
no suitable index in the M3 database. To execute this on top of very large tables can result in a full
table scan to find a few records. This results in bad performance in the API/Ad Hoc call as well as a very
high load on the database server, that can in turn affect other processes in M3. Similar problems also
occur for smaller tables when the call frequency of the API transaction or Ad Hoc reports are high.
The best practice is to always base needed filtering on the existing database indexes. If no standard
database index exists, new ones can be created through the M3 sorting options in 'M3 File. Create
Sorting Option' (CRS021). To help achieve suitable filtering, an enhancement is in progress where the
last filter can be defined as an interval rather than a single value.
A recommended alternative solution to retrieve M3 data is to use Data Lake data retrieval capabilities.
See Infor OS User Guide in this location referencing Compass functions and Data Lake ETL capabilities.
M3 CE Core: Restrictions on data volume indexed in M3 function search

The M3 search program is a heavily used tool to help finding the relevant information in M3 BE. The
best practice for search is to index only the M3 tables where users perform searches as well as add a
date limit (so called incremental crawl) to larger transactional tables to limit the search indexing to
more recent data, such as the last two years.
Note: The from date for incremental crawls are normally set centrally, and not by the tenant, while the
actual activation of date limited indexing is done per tenant.
Also note that the search crawl functionality found in the search admin page is an initial load
functionality only used after a migration or data refresh of a test tenant. It is not intended to be
repeatably used. M3 search indexes are kept in synch through the M3 events and crawls are not
needed after the first initial load.
The available data size per tenant in function search is limited and usage is monitored per tenant. Note
that date limits will be enforced.
The limit is set to a maximum of 2 years of index data for these tables:
• MTRSUB • FBAKEY
• MOATTH • MITSUG
• MCBOMS • OPSALE
• FBAVAL • OXSCTR
• CINACC • FGLEDB
• MCCMAT • MIATTR
• MREALO • OSASTD
• FGLEDX • OPRBAS
• MITSUB • OPRICL
• MITTRA • OINVOL
• MOATTR • OINACC
• FGLEDG
M3 CE Core: Mashup SDK will no longer be updated. H5 SDK should be used instead
Mashup SDK is a development framework to build client-side UIs that can be used in M3 H5. It does
not contain any runtime but has helper code that make the development quicker and more
standardized.
There is a newer SDK for creating M3 UI solutions that is called M3 H5 SDK.
As there is a newer version of the SDK available the existing SDK will not be developed any longer.
Existing solutions created with Mashup SDK will continue to work but we are encouraging customers to
move over to H5 SDK over time to get the latest security codes and latest UI design.
M3 CE Core: Production Tenants are strongly recommended to only utilize one M3 CONO
Please note that this announcement is to clarify the current functionality in M3 solutions eco system
and is not a result of any changes made to the M3 CE Functional code.
This announcement is to clarify the strong recommendation to utilize only one single M3 CONO for
M3CE production tenants. This due to that multiple M3 CONO is not compliant with Infor go-forward
two-level strategy:
• M3 CONO: M3 Environment in which we work; acting as the segregation layer between
different ERP data such as Items, Suppliers and Customers, as well as Configuration Data such
as Settings and Order Types.
• M3 Division: Legal Trading Company, the company name and tax ID that is legally registered
with the local authorities. Other Infor products call this Company or Accounting Entity
M3 has a legacy coding standard where it is possible to support multiple, completely data-separated,
entities using multiple M3 CONOs within the same Installation and Database. This can be considered as
an ERP-centric/on-premises solution that has been carried over into multi-tenant Cloud.
As Infor continues to move towards Industry-based CloudSuites – this legacy capability is causing some
concerns when it comes to the CloudSuite-wide user experience.
To provide an exceptional CloudSuite Experience; the ERP is complimented with additional
components that make up the enhanced ecosystem. As the M3 CONO is a legacy M3-only capability,
many elements of the CloudSuite do not support this philosophy and the user experience and
capability can be adversely affected if the configuration uses multiple CONOs.
To ensure the end user is delighted with their Infor subscription, it is strongly recommended that M3
CE customers should NOT use the M3 CONO to model separate Legal Companies within in a production
tenant.
They should utilise the M3 Division capability or consider using separate Production Tenants – each
with a single M3 CONO within.
Even without using M3 CONO, M3 Cloud Edition is a multi-company solution supporting multiple legal
companies within same CONO, using M3 divisions (field DIVI) to enable Multiple legal entities (Legal
Trading Companies). This structure is the basis of Multiple Unit Coordination (MUC) and other
functionality to handle cross-divisional trading. By using this technique, the user experience and
capability is not detrimentally affected.
The advice has always been that for Production Tenants, only one M3 CONO should be used to ensure
that the full Infor OS experience is flawless, without workarounds or additional administration efforts.
This recommendation ensures that M3 CE is used in line with the "two level strategy" used by all other
Infor products (Tenant ID & Accounting Entity) rather than the three level historically used by M3 On
premise (Tenant ID, M3 CONO, M3 Division/Accounting Entity), and aligns to the global Infor practice
of tenant management.
Warning: The use of multiple M3 CONOs in a Production tenant works from an M3 core ERP
perspective but comes with several limitations across the whole CloudSuite from Infor OS to add-on
products. Using multiple CONOs in production requires the M3 CE customer have accepted all current
and future limitations as the CloudSuite Strategy is to continue to use the "two level strategy" to
deliver a truly exceptional user experience.
Within non-production tenants, the CONO option may be used for the purpose of segregation as it is
assumed that within the Training and Test environments the user experience is slightly compromised.
More information (including a list of some known restrictions) can be found within KB article 2119569
on the Infor Support Portal.
ID: M33497
M3 CE Core: Over-usage of M3 attributes

M3 attributes are a great solution in many cases to further describe the characteristics of an item.
Depending on the industry the number of used attributes per item or lot varies. In high volume
industries like Distribution, Fashion, or Food & Beverage best practice is to only use a few attributes
per item while in low volume industries like Equipment the best practice for the number of attributes
are significantly higher.
Customer in high volume industries need to be aware that an extensive usage of attributes will affect
the overall performance of M3. This is noticeable in processes like order entry, stock receipt etc. If
there is a requirement of high performance the number of attributes used, must be minimized.
M3 CE Core: Methodology for handling Infor OS Content such as Homepages & Widgets
Methodology for handling Infor OS Content such as Homepages & Widgets. This notification is being
made to clarify the existing policy and procedure rather than any change being made.
As part of the Cloud Deployment, Infor provides content such as role-based Homepages, Homepage
Widgets, In-context applications as well as other example templates.
This content is updated each month with new or revised versions and due to the nature of the
deployment - the changes are updated automatically outside of the normal maintenance window.
The update happens for all regions on the Tuesday immediately after the Third Saturday of the Month.
Homepage content is made available as published versions which can also be used as a template for
your own development. Please note that there is no toggle for activating updated content.
If there is a wish to not have changes made immediately for users, then these pages can be used to
create Tenant-specific versions.
Support information
For questions regarding this communication, entitlements, or software features, go to Infor Concierge
at concierge.infor.com and create a support incident.

Infor M3 (AWS) Early Announcement of Changes Requiring Advance Customer Action Future 20230401

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Infor M3 (AWS) Early Announcement of Changes Requiring Advance Customer Action Future 20230401

Uploaded by

Copyright:

Available Formats

Infor M3 (AWS) –

Early announcement of changes

Date Version Comments

November 2022 20221101 ID M36313 added to January 2023

December 2022 20221201 ID M36745 added to January 2023

Viewing referenced KB articles

M3 CE Core: Prepare Your Move from H5 Classic to H5 (Angular)

M3 CE Core: Export and import solution for M3 Dataset definition.

M3 CE Core: New document number and partner media reference control

M3 CE Core: (APS905) updated to configurable views

M3 CE Core: Enhanced management of VAT capabilities, including Fiscal Representation for

M3 CE Core: Users with restricted characters disallowed to be created via MNS150MI

Actions required prior to activating the change:

M3 CE Core: Several transactions within Manufacturing Order APIs, PMS100MI and

M3 CE Core: Replacement of the API transaction GetBasicData in PPS001MI

M3 CE Core: Display all purchase price decimals in PPS100MI - LstStgPrice

M3 CE Core: Implement consistent code dropdown formats

Actions required prior to activating the change:

M3 CE Core: Account information will be displayed as a header in all CLM dialogs

M3 CE Core: EDI Payment Proposal SyncM3EDIRemittanceAdvice BOD to include Break by

M3 CE Core: Changes in WO screens for time zone handling

• 'User. Access per Company & Division' (MNS151)

M3 CE Core: Change in logic for location selection for a material on a WO operation

M3 CE Core: Validation added when deleting a virtual field in (CMS012)

M3 CE Core: H5 Export to Google Sheets migration to newer Google Identity Services

M3 CE Core: Decommission low level transactions from EVS001MI

M3 CE Core: The following Features are now toggled on

M3 CE Core: Authority check for Facility has been added in (PPS283)

M3 CE Core: Enhancement Day types in Job Scheduler

M3 CE Core: IEC Message ID Duplicate Detection

M3 CE Core: Introduce multiple reconciliation dimensions in the Internal Reconciliation

M3 CE Core: Change to the injury-free setting in MFS

M3 CE Core: Harvest date validation changed at MO receipt

M3 CE Core: New warning messages added to (CMS041)

M3 CE Core: Configurable browse capabilities added for Chart of Accounts in (MNS175)

M3 CE Core: OIS100MI Confirm to only allow batch submission

M3 CE Core: Tax calculated at invoice recipient location

M3 CE Core: Performance improvement for MMS850MI to create stock transaction history in

M3 CE Core: Block the possibility to perform overpayments in (ARS118)

M3 CE Core: Call Vertex for rental credits

M3 CE Core: New button and workflow change in M3 CLM

M3 CE Core: Change CO number validation during rental agreement entry

M3 CE Core: Consider currency for MCO invoice decimal rounding

M3 CE Core: Populate the responsible for reporting field

M3 CE Core: Harvest date functionality enabled in MHS850MI/AddMOReceipt

M3 CE Core: Decommission of API CRS990MI in favor of new BROWSEMI

M3 CE Core: Assign MO-lot number at MO-receipt for non QMS item

M3 CE Core: M3EDISalesOrderAcknowledge BOD has some changes related to fields and

M3 CE Core: New stop messages in (PPS215) and PPS215MI

M3 CE Core: Updated VAT Registration Number management validation

Reason for the change:

M3 CE Core: Additional feature for custom text block functionality

M3 CE Core: Sales Hub - Make Item Search results a configurable panel

M3 CE Core: Restrict setup of customer-defined fields to master data tables

M3 CE Core: Restrictions on data download through M3 API

M3 CE Core: Restrictions on data volume indexed in M3 function search

M3 CE Core: Over-usage of M3 attributes

You might also like