SAP Fiori has revolutionized the way users interact with SAP systems by providing a modern, role-based, and intuitive user experience. In the context of SAP Supplier Relationship Management (SRM), Fiori apps enable procurement professionals and suppliers to efficiently perform their tasks on any device. While SAP delivers many standard Fiori apps for SRM, businesses often require custom Fiori apps tailored to unique procurement scenarios and processes. This article explains the approach and best practices for creating SRM Fiori apps for custom scenarios.
- Address Unique Business Requirements: Standard apps may not cover all specialized procurement processes or data views.
- Simplify User Experience: Custom apps focus on specific roles or tasks, reducing complexity.
- Enhance Mobile and Cross-Platform Access: Tailor apps for on-the-go users with responsive designs.
- Integrate with Backend Processes: Connect to SAP SRM and backend ERP for real-time data and transactions.
- Leverage Latest UI5 Technologies: Utilize SAPUI5 frameworks for rich, interactive interfaces.
¶ 1. SAP Gateway and OData Services
- OData Services provide RESTful APIs to expose SAP SRM backend data and processes.
- Use SAP Gateway to create, register, and maintain custom OData services that enable data read/write.
- These services form the foundation for Fiori app communication with SAP backend.
- SAPUI5 is the UI development toolkit for building responsive web apps.
- Custom Fiori apps are developed using JavaScript, XML views, and CSS in SAPUI5.
- It supports MVC architecture, ensuring clean separation of UI and logic.
- Development environments provided by SAP for building, testing, and deploying Fiori apps.
- Facilitate rapid development with templates, wizards, and integrated tools.
- Identify the specific procurement scenario requiring a custom app (e.g., special approval process, custom reporting, supplier evaluation).
- Define user roles, key functionalities, and data requirements.
¶ Step 2: Design UI and User Experience
- Sketch wireframes and user flows.
- Ensure design aligns with SAP Fiori Design Guidelines for consistency.
- Use SEGW transaction or SAP Gateway tools to create OData services.
- Map SRM backend tables, BAPIs, or function modules to OData entities.
- Implement create, read, update, delete (CRUD) operations as needed.
- Start with a template (List Report, Object Page, Worklist) based on app requirements.
- Bind UI controls to OData service entities.
- Implement custom logic, validations, and navigation.
¶ Step 5: Test and Deploy
- Conduct unit and integration testing in development systems.
- Deploy apps to SAP Fiori Launchpad via SAP Gateway.
- Assign roles and authorizations to end-users.
- Custom Shopping Cart Approvals: Streamline approval of non-standard items with tailored UI and workflow.
- Supplier Performance Dashboard: Visualize supplier KPIs with interactive charts and alerts.
- Contract Management: Allow contract managers to view, edit, and approve contracts with enhanced filtering.
- Exception Handling: Provide a centralized app to monitor and resolve procurement exceptions.
- Adhere to SAP Fiori design principles for intuitive and consistent UX.
- Optimize performance by minimizing OData calls and implementing client-side caching.
- Ensure security by implementing proper authentication and authorization checks.
- Leverage reuse libraries and UI components provided by SAP to accelerate development.
- Maintain clear documentation and version control for ongoing maintenance.
Creating custom SAP SRM Fiori apps empowers organizations to tailor procurement processes to their unique needs while delivering a superior user experience. By leveraging SAP Gateway, SAPUI5, and SAP’s development tools, businesses can develop responsive, efficient, and scalable Fiori apps that enhance productivity, supplier collaboration, and process transparency in SRM.