In SAP S/4HANA Fiori apps—whether standard or extended—public views play a key role in tailoring user experiences. These views can be created with a transport request (TR) and mapped to user-specific roles, ensuring that only authorized users with the appropriate roles can access them.
Controlled Creation via Development System
To maintain governance and consistency, public views should be created in the Development system by the AMS team, based on a Ticket raised by the business key user. This ensures:
- Proper testing and validation
- Adherence to naming conventions
- Controlled deployment through the landscape
Direct Creation in Production: Proceed with Caution
While SAP allows business users -including key users -to create public views directly in the Production environment, this flexibility comes with limitations and risks:
- Role-specific views cannot be created in Production
- Untested changes may be introduced without oversight
- Naming conventions are often ignored
- Hundreds of views per app can accumulate rapidly
- App loading times may suffer due to excessive views
- User confusion grows as more views clutter the interface
- Monitoring overhead increases significantly
Recommendation
To avoid these pitfalls, organizations should:
- Centralize public view creation in the Development system
- Use structured service requests to initiate changes
- Limit direct creation in Production to specific, well-trained users
- Regularly audit and clean up unused or redundant views
By following these practices, you can ensure a clean, performant, and user-friendly Fiori experience across your S/4HANA landscape. Stay tuned to learn the Approach for S/4 Custom Fiori Apps/Reports deployed on BTP.