Infor M3 (AWS) - Changes Requiring Advance Customer Actions April 2023

Infor M3 (AWS) –
Early announcement of changes

requiring advance customer actions April 2023
Revision history
Date Version Comments

May 2023 202304 Summary of Updates for April 2023 created
2| Updated April 2023 Copyright © 2023. Infor. All rights reserved. www.infor.com
Contents
Contents..................................................................................................................................................... 3
Introduction................................................................................................................................................ 4
Other recommended actions .................................................................................................................. 5
Changes requiring advance customer actions planned for April 2023 ............................................ 6
Important information regarding testability of M3 functions ............................................................. 31
Important information regarding changes to Db indexes and existing table fields ...................... 32
Important information ............................................................................................................................. 33
Support information................................................................................................................................ 38
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 and 2260274 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
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
10 | Updated April 2023 Copyright © 2023. Infor. All rights reserved. www.infor.com
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.
For more information, see KB article 2213831 in the program 'Feature list. Open' (CMS975).
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:
This feature is available in M3. For more information, see KB article 2243985 in the program ‘Feature
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:
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 2282656 in the program 'Feature
ID: M37094
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) - Changes Requiring Advance Customer Actions April 2023

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) - Changes Requiring Advance Customer Actions April 2023

Uploaded by

Copyright:

Available Formats

Infor M3 (AWS) –

Early announcement of changes

Date Version Comments

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: 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