Implementing Manufacturing and Materials Management: From Empty Plant to Costed Work Order · Module 2 · Security and Data Access
Security contexts explained
Lesson 15 of 188 · 3 min
The mechanism: you grant a user or a role access to specific values of a security context. "This supervisor, on this plant." "This cost accountant, on this cost organization." That is it; the rest of the lesson is which context governs what. Inventory organization governs inventory transactions, on-hand, and item organization data. Manufacturing plant governs work orders, work definitions, dispatch lists and shop floor execution. Cost organization governs cost setup, cost planning and cost processing. Now the overlap that confuses everybody. A manufacturing plant is an inventory organization with manufacturing enabled. Which means a production supervisor usually needs both contexts granted, and granting only one produces partial visibility that looks like a bug. Partial visibility, not an error: they can see their work orders and not the material. They will report that as a defect on day one, and they will be right that something is wrong and wrong about…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Implementing Manufacturing and Materials Management: From Empty Plant to Costed Work Order, with a certificate on completion and a fourteen-day refund window.
In this module: Module 2 · Security and Data Access
- 1Why this is a third security model
- 2The roles a manufacturing project needs
- 3Provisioning implementation and business users
- 4Security contexts explained
- 5Granting inventory organization access
- 6Granting plant and cost organization access
- 7Segregation of duties on the shop floor
- 8What breaks
- 9Lab: build the access grid for two plants
