How to Change Division in Infor M3
how to change division in infor m3
Also searched as
- infor m3 change company
- m3 switch division
- m3 default division user MNS150
- m3 not authorized to division
Short answer
In M3 a user works in one company (CONO) and one division (DIVI) at a time. You switch for the current session from the company/division selector in the H5 client, and you change the default you land in through the user settings (MNS150). If the division you want is missing or rejected, the user lacks authority for it.
Applies to: Infor M3 Business Engine on-prem and CloudSuite, H5 Client and Smart Office. Menu labels vary slightly by version.
Change the active division
- 1In the H5 client, open the user or session menu in the header and look for the company/division option. Pick the target company and division from the list.
- 2If the list does not offer the division, the user is not authorized for it. Do not fight the UI, fix the authority (see below).
- 3To change the default for future logins, open MNS150 (User) and select the user. Check the default company and division fields on the panel for settings.
- 4Also review the other defaults on the same user record, such as default facility and warehouse, because they must belong to the new division or panels will reject them.
- 5Sign out and back in (or restart the session) so the new defaults are read.
- 6Verify by opening a division-specific program such as the item or customer order program and confirming the division shown in the panel header and in the data returned.
- 7For an integration or API user, change the division it connects with in the user record the service account uses, or pass the division where the API program supports it.
Company versus division in M3
M3 data is partitioned by company (CONO) and, for many tables, by division (DIVI). Company holds shared master data and the chart of accounts structure, while the division is the legal and operational unit with its own settings, currency and periods. Most transactional work, such as customer orders and purchase orders, is scoped to a division.
When you change division you are not changing a view filter. You change the context that every program reads and writes. That is why a wrong division is a real risk on write transactions, and why many sites remove the right to change division from ordinary users.
Why the division you want is missing
The common reason is authority. M3 checks the user's role and the division/company authorizations before it lets the session enter a division. If an administrator has not connected the division to the user (or to a role the user holds), the selector will not list it.
Ask the security administrator to compare the user against a colleague who can enter the division. In M3 security setup you look at the user record, the roles connected to it, and the function and data authorizations on those roles. The exact program numbers differ between versions, so search for the security programs by name in the program search rather than trusting a number from a forum post.
A second cause is a stale session. Defaults are read at sign-in, so an edited user record only takes effect in a new session.
Division changes in integrations
An M3 API call runs as the user it authenticates with, so it uses that user's default company and division unless the transaction takes the values as input. Many MI programs accept a division field, but it must still be one the service user is authorized for.
A frequent integration bug is a service account whose default division was changed for a human test and never restored. Calls then succeed but write to the wrong division. Keep service accounts separate from personal accounts and document their defaults.
Try it here, free
Infor M3 Facility and Warehouse Structure Worksheet
Design the M3 hierarchy of division, facility, warehouse and locations on one sheet, with storage capacity totals.
Common pitfalls
- !Changing the division in the middle of a half-entered transaction. Finish or cancel the work first.
- !Setting a default division but leaving a default facility or warehouse from the old division, which then fails validation.
- !Testing a fix in a person's own session and forgetting the service account has a different default.
- !Giving every user the right to change division. Restrict it to people who need it, because writes land in the active division.
- !Assuming a program number from an older version. Confirm menu names in your own release.
How an ERP-grounded AI assistant handles this
A read-only assistant such as ERPray can answer which users are authorized for which division, which default division each service account uses, and which orders were written in an unexpected division, by querying the live configuration and showing the query. It does not change authority. Netray can run this on-prem so the user and security data never leave your network.
Frequently asked questions
Can I be in two divisions at the same time in M3?
A session has one active company and division. People who work across divisions normally open a second session or switch, and reporting that spans divisions is done with reports or queries that read several divisions rather than by being in two at once.
Where is the default division stored?
On the user record, maintained in MNS150. The default company, division, facility and warehouse there are applied when the user signs in.
Why does the division selector not show my division?
Almost always authority. The user, or a role connected to the user, is not authorized for that division. A security administrator needs to connect it, then you start a new session.
Does changing division affect running jobs?
Interactive sessions only. Batch jobs and integrations run under the user and context they were scheduled with, so check the schedule's user rather than your own session.
Related
Infor M3 Security Settings: Roles, Authorization and Setup
M3 security combines who the user is, the roles they hold, which programs and options a role may use (function authority), and which companies, divisions, facilities and warehouses it may work in (data scope). You set it up by connecting users to roles and roles to authorizations, then audit with the security reports.
AdvancedHow to Call M3 API (MI Programs) Through ION API
Calling M3 from an external system today almost always means going through ION API rather than the older direct MvxAPI SOAP endpoint: you create an ION API authorized app or service account in the ION API portal, download its .ionapi credential file, obtain an OAuth 2.0 access token, and call the M3 MI program transaction through the m3api-rest execute endpoint with that token.
How-toHow to Create a New Item in M3 (MMS001)
A new item in M3 is created in two stages: item basic data in MMS001 (Item. Open), which defines company-wide attributes such as description, item group and unit of measure, then facility-level data in MMS002 (Item/Facility. Connect), which attaches the item to a specific warehouse or plant with purchasing, planning and costing parameters. An item is not usable for orders, purchasing or MRP until both stages are complete.
Error fixM3 API Error: Record already exist
Record already exist means the MI Add transaction you called is trying to insert a key that is already present in the target M3 table, most often because a prior call succeeded and was retried, or because the key fields you built do not match what you think they match. Read the errorField and errorFieldGroup attributes on the response to see exactly which key field M3 flagged, then either switch to the matching Chg (change) transaction or fix the key construction in the caller.
AdvancedPaging M3 API MI List Transactions Past the Default Record Limit
M3 List transactions (the read/browse transaction most MI programs expose, such as CRS610MI.LstByNumber or OIS100MI.LstOrderHead) cap the rows returned per call using the MaxReturnedRecords input field, and by default many clients leave it low or unset, which looks like the API silently truncating results. Set MaxReturnedRecords explicitly, then loop the call using the last key values from the previous page as the starting position until fewer rows than the limit come back.
Error fixM3 API Error: Not Authorized to Program
Not authorized to program (or the equivalent transaction-level authorization error) means the M3 user ID the integration authenticates as can log in fine but has not been granted access to that specific MI program, transaction, or company/division through its authority group. Fixing it means adding the program/transaction to the integration user's authority group in M3, not changing anything in the calling code.
AI for ERPInfor M3 AI: A Practical Path from MI Programs to a Private Assistant
Infor M3 AI explained: grounded natural-language answers over MI programs and MEC, agents for distribution and manufacturing, on-prem or EU private cloud.
Stuck on Infor M3?
Talk to engineers who work inside Infor M3 every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- Infor M3 Facility and Warehouse Structure WorksheetDesign the M3 hierarchy of division, facility, warehouse and locations on one sheet, with storage capacity totals.
- Infor M3 H5 Script Review ChecklistA review checklist for H5 Client scripts covering design, coding, security, testing and upgrade risk.
- Infor M3 User Acceptance Test Script TemplateFill-in UAT script with scenario, preconditions, step table, results and sign-off for M3 end to end process testing.
ERP fixes and how-tos
- Infor M3 Security Settings: Roles, Authorization and SetupHow Infor M3 security works: users, roles, function authority, company and division authority, and how to set them up and audit who can do what.
- M3 API Error: Not Authorized to ProgramM3 API or MvxAPI call rejected with Not authorized to program or transaction. Check the calling user's authority group and function grants, not just password.
- Infor M3 Date Format: User Setting, API and DatabaseHow dates work in Infor M3: the user display format in MNS150, the 8-digit YYYYMMDD format used by MI APIs and tables, and how to convert them.
Guides
- Infor M3 H5 Client Personalization and Scripting GuideWhat the Infor M3 H5 client is and how to tailor it: personalization layers, JavaScript scripts, bookmarks and deployment, without touching the Business Engine.
- Infor M3 Financials Configuration: Structure, Rules, and CloseInfor M3 financials configuration guide: company and division setup, accounting identities, FAM functions, accounting rules, and period close controls.
- Infor M3 Technical Architecture Explained Layer by LayerInfor M3 technical architecture explained: M3 Business Engine, Infor Grid, database tables, H5 client, and integration layers for on-prem and CloudSuite teams.
Integrations
- How to use ChatGPT with Infor M3How to use ChatGPT with Infor M3: exports, custom GPT actions over the M3 API or ION, enterprise data controls, and when a private model is the safer choice.
- How to add an AI chatbot to Infor M3How to add an AI chatbot to Infor M3 for staff and customers: grounded in M3 data via the API, embedded in a portal or Teams, and able to run fully on-prem.