Specifying new roles

To specify new roles in LN and make them available for assignment to users in Infor Ming.le:

In the LN menu, navigate to Tools > User Management > Authorization Management System > Role Data to specify a new role in the Role Data (ttams4100m000) session.
Define Session Authorizations in the Role Data (ttams4100m000) session. For example, add a record that gives full authorization for all sessions in a specific company. The LN37X role mentioned earlier has 6 records for Session Authorizations.
Define Table Authorizations in the Role Data (ttams4100m000) session. For example, add a record that gives authorization to delete/insert/modify/read for all tables in a specific company. The LN37X role mentioned earlier has 6 records for Table Authorizations.
Publish the LN (role) changes to Infor Ming.le. These options are available:
- Manually publish the changes through the Start RT Monitor (ttrcp1205m000) session. In the LN menu, navigate to Tools > Integration Tools > Runtime Change Publishing > Publishing to start this session.
- Automatically publish the changes through the AUTO_RUNTIMECHANGES job. This job is provided in company 0000 and can be configured to run, for example, every 15 minutes.
The SecurityRoleMaster BOD is transported to Infor Ming.le through the Mingle_LN0000 data flow, if the data flow is active.

Note: Security roles are assigned to users in Infor Ming.le. In LN, you can also assign roles to users and update the user assignments in Infor Ming.le. However, if you specify a new role and immediately assign it to a user in LN, Infor Ming.le may receive the user role assignment before it receives the new role. This results in an error and you must resubmit the SecurityUserMaster BOD. To resubmit the BOD:

After the role is known in Infor Ming.le, navigate to ION Desk > Connect > Error BODs.
Search for the Error BOD that has Sent From set to infor.ln and Document Name set to Process.SecurityUserMaster.
Select the record and click Resubmit.