← Back to Recording

Summary

Overview

This course session provides a comprehensive, hands-on walkthrough of SAP system access, Fiori Launchpad configuration, role-based authorization management (via PFCG), OData service activation via SICF, and integration of SAP BTP (Business Technology Platform) with on-premise ERP systems. The instructor guides learners through setting up remote desktop access to SAP systems (ECC6 and S/4HANA), navigating Fiori apps, customizing launchpad tiles, assigning backend authorizations, and preparing for BTP connectivity via destinations and cloud connectors. The session bridges frontend user experience with backend technical configuration, emphasizing practical steps for system access, service activation, and future integration with SAP Business Application Studio.

Topic (Timeline)

1. Remote Desktop and SAP System Access [00:01:21.970 - 00:19:19.790]

  • Instructions for accessing SAP systems via Remote Desktop Connection (mstsc) using provided IP addresses.
  • Guidance on launching SAP Logon Pad to connect to both S/4HANA and ECC6 systems.
  • Emphasis on using numerical passwords (e.g., 156 for ECC6) and consistent username prefixes (e.g., AUG).
  • Clarification on avoiding direct database access via HANA Studio; directing users to use LB Station Console instead.
  • Troubleshooting tips for users encountering connection issues, including verifying login status and system availability.

2. Fiori Launchpad Navigation and Tile Customization [00:19:31.070 - 00:42:49.680]

  • Step-by-step login to Fiori Launchpad via Microsoft Edge or Google Chrome, including bypassing certificate warnings via “Advanced” > “Continue to website”.
  • Use of consistent credentials (AUGABAB16 for ECC, AUG prefix for S/4HANA).
  • Introduction to the Fiori Launchpad home page, initially empty for new users.
  • Process to enter “Edit Page” mode and use “Add Tile” to discover and add applications from the catalog (e.g., Procurement Overview).
  • Explanation of catalog structure: transactional apps (no numbers) vs. analytical apps (prefixed with numbers).
  • Performance note: Non-productive system slowness due to caching and low traffic; expected improvement with regular usage.

3. Fiori Launchpad Designer and Role Configuration [00:42:52.190 - 01:04:31.780]

  • Accessing Launchpad Designer via URL path: /sap/bc/ui5_ui5/sap/FLPD_CUST (after / and uifld).
  • Demonstration of modifying tile titles and icons (for reference only; no changes made to standard apps).
  • Introduction to PFCG (Role Maintenance) transaction for backend authorization.
  • Creation of a custom role (e.g., Z_SALES_MANAGER) and assignment of Fiori catalog entries (e.g., Manage Sales Order).
  • Use of “User Comparison” to verify role assignment to the current user (AUG).
  • Clarification that PFCG is a basis-level transaction and should be used with caution.

4. OData Service Activation and SICF Configuration [01:04:35.930 - 01:10:30.750]

  • Identification of OData services via Fiori Explorer (e.g., F1873 for Manage Sales Order).
  • Navigation to SICF transaction (/sap/bc/ui5_ui5/sap/) to locate and activate OData service nodes.
  • Explanation of SICF as the web server framework for SAP UI5, OData, BSP, and other web services.
  • Critical note: Services must be activated in SICF; otherwise, runtime errors occur due to unexposed endpoints.
  • Structure of SICF path: sap/bc/ui5_ui5/sap/ → service-specific folders (e.g., sap/bc/ui5_ui5/sap/ for Fiori apps).
  • Emphasis on service activation being mandatory for data availability in frontend apps.

5. SICF Security and Transport Management [01:10:33.120 - 01:26:57.850]

  • Configuration of authentication in SICF: default “open” access vs. restricted access via assigned roles.
  • Use of system alias (e.g., LOCAL) for on-premise systems.
  • Requirement of a transport request for SICF changes due to customization nature.
  • Linkage between Fiori app, Launchpad Designer, PFCG role, and SICF service activation as a complete authorization chain.
  • Reference to managing sales-related apps via consistent naming (e.g., “Manage Sales Order”).

6. SAP BTP Trial Account Setup and Architecture [01:26:57.850 - 01:53:33.690]

  • Step-by-step registration for SAP BTP trial account via web browser.
  • Creation of global account → subaccount → organization → space.
  • Activation of SAP Business Application Studio (pre-enabled in trial).
  • Clarification on licensing: 90-day trial, extendable by 30-day increments for active users.
  • Note on restricted access for some services; most development tools available under free trial.
  • Identification of unregistered users (Giselle, Gischen, Arcelo) and encouragement to complete setup.

7. BTP Connectivity: Destinations and Cloud Connector Overview [01:53:33.690 - 02:24:38.020]

  • Introduction to BTP connectivity options: Destinations (for publicly accessible systems) and Cloud Connector (for on-premise systems behind firewall).
  • Explanation of Cloud Connector as an on-premise agent that creates a secure tunnel to BTP.
  • Demonstration of creating an HTTP destination in BTP: name, description, URL (OData endpoint), proxy type (On-Premise), and authentication (to be configured later).
  • Note: URL and authentication details will be finalized in the next session after OData service setup.
  • Use case: Consuming OData/REST APIs from Business Application Studio to build UI5/HTML5 apps.
  • Emphasis on JavaScript/Visual Studio Code familiarity as an advantage for learners.
  • Licensing path: Free trial → paid BTP license for extended features and unrestricted access.
  • Final note: Next session will cover practical setup of destinations and cloud connector; session ends with invitation for feedback and closing remarks.

Appendix

Key Principles

  • Fiori Access Chain: Launchpad → Catalog → Role (PFCG) → OData Service (SICF) → Backend System.
  • SICF Activation is Mandatory: Unactivated services cause silent failures; always verify activation status.
  • BTP Trial Flexibility: 90-day trial extendable indefinitely for active users; sufficient for learning and prototyping.
  • Authentication Separation: Frontend (Fiori login) and backend (OData/SICF) authentication are distinct and must both be configured.

Tools Used

  • Remote Desktop Connection (mstsc)
  • SAP Logon Pad
  • Fiori Launchpad (Edge/Chrome)
  • SICF Transaction (/sicsf)
  • PFCG Transaction (/pfcg)
  • SAP Business Application Studio
  • SAP BTP Cockpit (https://account.hana.ondemand.com)

Common Pitfalls

  • Forgetting to activate OData services in SICF → “No data” or “Runtime error” in Fiori apps.
  • Using incorrect URL format for destinations (missing /sap/opu/odata/...).
  • Attempting direct HANA Studio access instead of approved interfaces (LB Station Console).
  • Ignoring browser certificate warnings without proper bypass (causing login failure).
  • Not registering BTP trial account → inability to proceed with cloud development.

Practice Suggestions

  • Recreate the Fiori tile customization process on a test system.
  • Use PFCG to create a custom role and assign 3 Fiori apps manually.
  • Locate and activate 2 OData services in SICF and verify their status.
  • Register for a BTP trial account if not already done; explore the “Destinations” section.
  • Practice copying and pasting Fiori URLs between Edge and Chrome to understand browser behavior.