Advanced SAP Fiori for MM, SD, PP, and WM: App Development & Customization — Session 4

Overview

This course session provides a step-by-step technical walkthrough on configuring SAP Fiori Launchpad tiles, catalogs, and target mappings for purchase order-related transactions (e.g., ME21N, ME29N), while also covering workflow integration, cloud readiness, and the transition from ECC to S/4HANA. The instructor guides participants through creating custom catalogs, assigning semantic objects, configuring static tiles with transaction codes, and linking them to roles via PFCG. The session concludes with an overview of Fiori applications for warehouse management, supplier analytics, and the shift toward cloud-ready configurations using flexible workflows, BRFplus, and low-code tools.

Topic (Timeline)

1. Fiori Tile and Catalog Configuration [00:20:19.760 - 00:54:55.390]

• Instructor guides participants to create a custom catalog (e.g., zjen or z_catalog) via the SAP Fiori Launchpad Designer, emphasizing use of the plus sign in the left-bottom corner to create both group and catalog.
• Clarifies that semantic object should not be used for static tiles; instead, select App Launcher Static Tile.
• Instructions to enter meaningful tile titles (e.g., “Purchase Order Creation”) without underscores or technical prefixes.
• Emphasizes selecting Application Type: URL and Action: Display; avoids FIORI app selection.
• Configures System Alias as LOCAL under target mapping; removes unnecessary URL fields.
• Guides users to add the newly created catalog to a group and assign it to the user’s role via PFCG.
• Warns against maintaining shared catalogs; each user should create and test their own.

2. Target Mapping and Semantic Object Usage [00:54:55.390 - 01:02:35.120]

• Reiterates that semantic objects (e.g., PurchaseOrder) must be used in target mapping, not tile creation.
• Demonstrates selecting PurchaseOrder as the semantic object and choosing Manage or Create as the action.
• Specifies Application Type: Transaction and enters transaction code (e.g., ME21N).
• Confirms removal of auto-populated URL fields; only transaction code and system alias are required.
• Instructs to save and verify visibility of the tile in the Fiori Launchpad under the custom catalog (z_jen).
• Advises refreshing the launchpad and checking PFCG role assignment to ensure tile appears.

3. Role Assignment, Catalog Visibility, and Troubleshooting [01:02:35.720 - 01:15:10.290]

• Guides users to verify tile visibility in the Fiori Launchpad by searching for the tile title (e.g., “Purchase Order Creation”).
• Recommends using industry sector and material type in configuration if required for context.
• Addresses issues with missing internal names or number ranges; suggests copying from existing configuration (e.g., from 100140 to zgen).
• Notes that system errors may occur due to validation issues or external interference; recommends copying and pasting configurations to bypass.
• Instructs Marvin and others to rename their tiles with Z_ prefix (e.g., Z_PurchaseOrder) and refresh the launchpad.
• Emphasizes updating target mapping after renaming to ensure correct semantic object linkage.

4. Workflow Integration and S/4HANA Cloud Readiness [01:15:16.680 - 04:53:30.800]

• Shifts focus to purchase order workflow integration: checks for missing roles in partner maintenance (e.g., 137), release strategies, and approval workflows.
• Confirms that flexible workflow is available only in S/4HANA, not ECC; in ECC, classical workflows (SWDD) must be used.
• Explains that attachment visibility in Fiori is controlled by the workflow’s OData service, not the Fiori app itself.
• Highlights that missing attachments are a workflow configuration issue, not a Fiori UI issue.
• Discusses SAP’s cloud roadmap: transition from ECC → S/4HANA → Cloud, with deprecation of custom code in favor of Fiori apps and low-code tools.
• Introduces BRFplus for output determination and Custom Fields and Adjustments app for UI enhancements without coding.
• Notes that Fiori apps are now the standard interface, replacing traditional GUI transactions.

5. Fiori for Warehouse Management, Supplier Analytics, and SQVI [04:53:30.800 - 05:03:34.580]

• Demonstrates Fiori applications for warehouse management: transfer orders, goods receipt, goods issue, stock transfers.
• Shows supplier analytics apps: open line items, payment history, credit/debit notes, bank details, quality scores.
• Explains how SQVI (Quick View) reports can be converted into Fiori tiles: create SQVI report → assign transaction → create static tile.
• Confirms that users can access SQVI via Fiori without entering SAP GUI.
• Notes that these applications are usable on mobile devices (e.g., ITS Mobile) and support real-time data access.

6. Final Exercises and Wrap-up [05:03:37.660 - 05:19:47.450]

• Announces a set of 10 short exercises focused on navigation and configuration tasks covered in the session.
• Instructs participants to complete exercises the next day, take screenshots, and submit files with their names.
• Confirms that all exercises are based on prior steps: tile creation, catalog assignment, target mapping, and role configuration.
• Concludes with a closing remark to end the session on a positive note.

Appendix

Key Principles

• Do not use semantic objects in static tile creation — use them only in target mapping.
• Tile titles should be user-friendly (e.g., “Purchase Order Creation”) — avoid technical prefixes like underscores.
• Application Type = Transaction for standard SAP transactions (e.g., ME21N, ME29N); avoid FIORI app selection unless required.
• System Alias = LOCAL is sufficient for demo systems; no need for complex configurations.
• Attachments in Fiori workflows depend on OData service configuration — not the UI.

Tools Used

• SAP Fiori Launchpad Designer
• PFCG (Role Maintenance)
• SWDD (Classical Workflow)
• BRFplus (Output Determination)
• SQVI (Quick View)
• SICF (Internet Communication Framework)
• Fiori Explorer

Common Pitfalls

• Using semantic objects in tile configuration instead of target mapping.
• Leaving auto-populated URLs in target mapping.
• Not refreshing the launchpad after changes.
• Confusing S/4HANA flexible workflow with ECC classical workflows.
• Assuming attachment visibility is a UI issue — it’s a backend workflow/OData issue.

Practice Suggestions

• Create 3 custom tiles: one for ME21N, one for ME29N, one for SQVI.
• Assign each to a unique catalog (z_yourname) and verify visibility in Fiori.
• Test target mapping with PurchaseOrder semantic object and Create action.
• In a test system, attempt to enable an attachment in a purchase order and verify its display in the workflow task.
• Compare configuration steps between ECC and S/4HANA for the same transaction.