6 videos • 📅 2025-08-08 08:00:00 Asia/Singapore
Watch Video
2:30
2025-08-08 08:19:52
2:26:14
2025-08-08 13:05:14
21:21
2025-09-04 08:09:02
5:20:18
2025-09-04 10:36:01
23:09
2025-09-05 08:13:48
2:10:51
2025-09-05 13:50:47

Course recordings on DaDesktop for Training platform

Visit NobleProg websites for related course

Summary

Overview

This course session focuses on enabling and configuring SAP Fiori applications for warehouse management, particularly around stock transfer orders (STO) and transfer order creation via transaction codes like LT01 and LT04. It covers the gap between backend SAP transactions and frontend Fiori app exposure, emphasizing configuration steps for OData services, business catalogs, roles, and authorization management. The session also includes administrative guidance on quiz submission, system access limitations, and troubleshooting missing Fiori apps due to improper catalog assignments or system version constraints.

Topic (Timeline)

1. Quiz Submission & Attendance Verification [00:03:38 - 00:19:10]

  • Participants are instructed to complete a quiz via radio button selections, take a screenshot with their name, and submit it for scoring (perfect score = 10).
  • Trainer verifies submissions: only Jane and the participant are visible; Christian, Elisa, Maria, Giselle, and Arcillo have not shared screens.
  • Emphasis on completing the quiz as a prerequisite before proceeding.
  • Clarification that while changes can be made directly in production systems (common in BW or gateway services), using quality systems with transport management is a best practice due to authorization limitations.

2. Business Context: Warehouse Management & Stock Transfer Orders [00:19:10 - 01:04:15]

  • Transition to warehouse management enablement, focusing on accounting general entry items and project account processing.
  • Discussion of transaction codes: LT01 (primary) and LT04 (GUI-only), both related to transfer order creation.
  • Differentiation between:
    • Intercompany STO (material movement between plants)
    • Warehouse Management Transfer Order (internal logistics movement, e.g., LT01)
  • Clarification that while multiple transactions (LT0, LT10) exist, only LT01 is the correct target for Fiori enablement.
  • Observation: Most participants are viewing screens but not interacting with the full Fiori interface; system limitations are noted.

3. Fiori App Exposure & Configuration Challenges [01:04:15 - 01:39:44]

  • Explanation that Fiori apps are OData-based and require proper exposure via Fiori Launchpad.
  • Issue: Valid transactions (e.g., LT01) exist in the system but are not visible in App Finder due to missing business catalog assignments.
  • Root cause: Applications may be present but not assigned to any business or technical catalog, rendering them invisible to end users.
  • Solution path: Create or assign appropriate business catalog, technical catalog, and role to expose the app.
  • Trainer notes this is a common issue in SAP systems and requires manual reconfiguration.

4. System Limitations & Workarounds [01:39:44 - 01:57:37]

  • Trainer acknowledges system issues: some applications are damaged or non-functional.
  • Offers to demonstrate a working example from a client system in Mexico if participants provide a list of required apps.
  • Emphasizes that live demonstration on production systems is not feasible during this session due to time and access constraints.
  • Proposes to share access details via email and space for follow-up.

5. Step-by-Step Fiori App Deployment & Configuration [01:57:37 - 02:04:19]

  • Outlines 5 critical steps for enabling a Fiori app:
    1. Deploy the app – Use reference library; may require upgrading from lower (e.g., 106) to higher (e.g., 107) SAP release components.
    2. Frontend configuration – Basis team handles component download and upgrade; not participant responsibility.
    3. Activate OData services – Check activation status (gray = active); use appropriate transaction to ensure service is running.
    4. Maintain PFCG roles – Assign authorization roles via PFCG; ensure transportable objects (not temporary) are used.
    5. Testing – Optional; steps 1–4 are mandatory for initial enablement.
  • Trainer reiterates that steps 1–4 are sufficient for learners; full testing is for advanced users.
  • Final note: Document shared via Space; no time limit for follow-up questions; trainer remains available.

Appendix

Key Principles

  • Best Practice: Use quality system with transport management for changes, not direct production modifications.
  • Fiori Exposure: Apps must be assigned to a business catalog and role to appear in App Finder, even if the underlying transaction exists.
  • OData Dependency: Fiori apps are OData-based; service activation is mandatory for functionality.

Tools & Transactions

  • LT01: Primary transaction for warehouse transfer order creation (target for Fiori enablement).
  • LT04: GUI-only transaction, not suitable for Fiori.
  • PFCG: Role maintenance and authorization assignment.
  • SAP Fiori Launchpad: UI for app exposure; requires catalog and role binding.
  • OData Services: Must be activated via transaction (e.g., /IWFND/MAINT_SERVICE).

Common Pitfalls

  • Apps visible in backend but not in Fiori Launchpad → missing business catalog assignment.
  • Grayed-out or inactive apps → OData service not activated.
  • Unauthorized access → roles not assigned via PFCG or transportable objects not used.
  • System version mismatch → required app exists in higher release (e.g., 107) but system is on lower (e.g., 106).

Next Steps for Learners

  • Complete and submit quiz if not done.
  • Review shared document on Space.
  • Identify any missing Fiori apps in your system and report to basis team for catalog/role assignment.
  • For advanced exploration: Test app functionality after configuration (Step 5).