Fiori Deployment Part 1: Deploying to the ABAP Repository and Transports

📌 KEY POINTS
✅ Apps are deployed to the ABAP UI5 repository as BSP applications in a package with a transport.
✅ SAP Fiori tools provide a deploy configuration (ui5-deploy.yaml) and command.
✅ After deployment, the UI5 app index must be up to date for the launchpad.
✅ Transports move the app with launchpad content and service activation steps to QA and PROD.
⚠️ Deploying directly to QA or PROD bypasses transport control and versioning.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
This series covers deployment. Part 1 targets on-premise ABAP front-end servers.

━━━━━━━━━━━━━━━━━━━━
▶ 1. WHAT DEPLOYMENT CREATES
Deploying a UI5 app to ABAP uploads its built files to the UI5 ABAP repository as a BSP application with a name and package. The app is then served from the system and can be referenced by target mappings in the launchpad.

━━━━━━━━━━━━━━━━━━━━
▶ 2. DEPLOY CONFIGURATION
SAP Fiori tools add a deploy configuration with target system, BSP name, package and transport request. Running the deploy script builds the app and uploads it. Credentials are entered securely or come from destinations, not stored in the repository.

━━━━━━━━━━━━━━━━━━━━
▶ 3. APP INDEX AND CACHES
The launchpad finds apps through the UI5 app index. Deployment usually triggers index recalculation; if not, /UI5/APP_INDEX_CALCULATE updates it. Cache-busting tokens ensure browsers load new versions.

━━━━━━━━━━━━━━━━━━━━
▶ 4. TRANSPORTS
Deploying in the development system records the app in a transport. Launchpad content (catalogs, target mappings) and other objects go in transports too. Service activations, if not transportable, are part of a deployment checklist.

━━━━━━━━━━━━━━━━━━━━
▶ 5. CI/CD
Many teams build and deploy from a pipeline, for example SAP Continuous Integration and Delivery, which runs lint and tests, builds the app and deploys to development with a transport. Release to QA and PROD then follows the transport process.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. Add a deploy configuration to an app with Fiori tools.
2. Deploy to a development system with a transport.
3. Check the BSP application and app index.
4. Release the transport and verify in QA.

✅ CHECKPOINT: the app moves from development to QA through transports and appears in the launchpad.

Developers deployed fixes directly to QA to save time. Within weeks, QA had versions that existed nowhere else, and production deployments broke features. Deployment was restricted to development via a pipeline, with transports as the only path forward.

• Deploying directly to QA/PROD.
• Credentials stored in deploy configs.
• Forgetting launchpad content transports.
• App index not updated.

• Deploy only to development.
• Pipeline with lint and tests.
• Transport app and content together.
• Verify app index and cache busting.

Interviewers ask how UI5 apps are deployed to ABAP systems, what the app index is and how transports and CI/CD fit together.