Hide Recommended (Export) ROP, Recommended (Export) ROQ fields for MTC/OPS User Role

• As part of Item request feature roll out, end users (maintenance planners) will now need to submit item requests (stock level change requests) in MRO IO. More than 500 end users will now have read only access to MRO IO. • As we all know material codes in MRO IO always have a recommendation either to increase or decrease reorder levels. However, we set up rules to identify the valid increases or decreases based on usage, criticality code, target service levels etc and divert them to work queues for Inventory Controllers to review and export changes. • Now when an end user (maintenance planner) reviews a material code in MRO IO which has recommendation to increase Reorder levels, they might misunderstand that item request needs to be submitted. Also end user might perform a simulation by modifying parameters to get required recommendation and submit item request accordingly. • This could result in numerous invalid item requests at all regions and can increase in inventory drastically. Also, it will be a big challenge for Inventory controllers to manage item requests, educate end users instead of focusing on work queues. • As there are many potential ways to misuse the MRO IO functionality, we request to build a feature to hide Recommended (Export) ROP, Recommended (Export) ROQ fields for MTC/OPS User Role.