Adding users to an accounting entity in Mingle vs MNS151 ?

Hi,

I have a doubt of understanding on the accounting entities present in MIngle (IFS) .

As much the security roles are synchronized, as much I finally read nothing on this subject on the accounting entities.

I have the impression that the management of user rights to accounting entities in M3 (MNS151) does not really have a link with the association Accounting Entities - Users in IFS.

Could you tell me if my understanding is correct?

And if yes, what is the interest to manage users - accounting entities associations in Mingle?

Thank your for you help for clarifying the point.

Regards

Find more posts tagged with

Infor Ming.le

Accepted answers

unknown

Hi Dens,

Hope you are well.

From my experience and knoweldge of the Accounting Entities - the Company/Division are reflected in IFS however to get them to be reflected in MNS151 and managed from IFS is something I am still workin on.

But to get the Accounting Entites reflected in IFS you need to make sure that the BOD - SyncAccountingEntities has been enabled for the Company & Divisions you want. then you need to do an Initial Load via the program EVS006.

Regarding your comment about setting the default CONO and DIVI - there is a way to set this:

M3 -> Admin Tools -> Enterprise Collaborator Admin

Server tab -> Agreement Control Properties

Agreement Name = M3_SecurityUserMaster_Sync_In

from here you can set the accounting Entity property - what this will do is that it will populate the Default CON and DIVI with whatever it populated here.

fyi - I'm still looking in how to do this dynamically, our issue is that we have multiple divisions in use and not all users have access to all. some users are only bound to 1.

hope this helps.

Qas

All comments

Denis MARETTE

I correct my statement: after exploration, the accesses to CONO and DIVI in Mingle are well reflected in M3 at MNS151.

The only oddity is that in MNS150 you can set a default CONO/DIVI for the user, but it cannot be controlled by Mingle

unknown

Hi Dens,

Hope you are well.

Regarding your comment about setting the default CONO and DIVI - there is a way to set this:

M3 -> Admin Tools -> Enterprise Collaborator Admin

Server tab -> Agreement Control Properties

Agreement Name = M3_SecurityUserMaster_Sync_In

from here you can set the accounting Entity property - what this will do is that it will populate the Default CON and DIVI with whatever it populated here.

fyi - I'm still looking in how to do this dynamically, our issue is that we have multiple divisions in use and not all users have access to all. some users are only bound to 1.

hope this helps.

Qas

Denis MARETTE

Hello Qasim,

Very pleased to read you.

Thanks for the tip to cause the initial download via EVS006 when the synchronization is done after allocations have already been made.

I did notice a strange behavior though: Before implementing the synchronization, I had a user who had by default in MNS150 access to CONO: XXX and DIVI YYY.
I activated the synchronization and then only gave this user access to CONO: XXX but to DIVI ZZZ.
In M3, he still had access to CONO YYY ?

The property in the M3_SecurityUserMaster_Sync_In contract does not really solve the problem. It allows you to set a CONO and DIVI value when the user is created in MNS150, but in my opinion it does not really control the CONO and DIVI and the default connection, which in my understanding requires that certain access management properties be administered in MNS150.

Thank you for these constructive exchanges

Copyright © 2025 Infor. All rights reserved.