Thursday, February 6, 2025

Fiori Standard App Variant

Transporting a Fiori variant depends on whether you're working with a Standard Fiori App or a Custom Fiori App. Below are the steps for each scenario:


1. Transporting a Standard Fiori App Variant (Smart Business, Analytical, or Transactional App)

If you created a variant using the "Save as Tile" or "Manage Views" feature, follow these steps:

A. Using the Fiori Launchpad (FLP) Personalization Transport

  1. Open the Fiori App where the variant is created.
  2. Go to the Variant Management option.
  3. Select the variant you want to transport.
  4. Check if the variant is stored as a "Shared Variant" (Personal variants cannot be transported).
  5. Use transaction /UIF/TRANSPORT in SAP GUI:
    • Open SAP GUI and execute /UIF/TRANSPORT.
    • Select the variant from the list.
    • Assign it to a Transport Request (TR).
    • Release the transport via SE09.

B. Using Transaction /UI5/FLPD_CUST (For Launchpad Variants)

If your variant is stored in the Fiori Launchpad configuration:

  1. Run /UI5/FLPD_CUST in SAP GUI.
  2. Locate the target variant.
  3. Assign it to a Transport Request.
  4. Release it via SE09.

2. Transporting a Custom Fiori App Variant (SAPUI5 Adaptation)

If you have made UI5 adaptations using SAP Web IDE or SAP BAS, follow these steps:

A. Transporting via Adaptation Projects

  1. Open the SAP Business Application Studio (BAS) or Web IDE.
  2. Locate the Adaptation Project in your workspace.
  3. Commit changes to Git (if applicable).
  4. Create a transport request via ADT (ABAP Development Tools):
    • In ADT, open Transport Organizer (SE09).
    • Assign the Fiori Variant (Flex changes) to the transport.
    • Release the transport.

B. Transporting Adaptations via ABAP Repository

  1. Use Transaction SUI_SUPPORT to locate the variant.
  2. Select Export and Transport.
  3. Assign the transport request.
  4. Release it via SE09.

3. Verifying the Transport in Target System

After transport, follow these steps:

  1. Execute the Fiori App in the target system.
  2. Verify the variant is available under the "Manage Views" section.
  3. If the variant is missing, check the transport logs in SE10.

Additional Notes

  • If you used Key User Adaptation (KUA) for UI changes, ensure that the changes are stored in the Customer Namespace (/UIF/ or /UI5/).
  • If you need to move only variant configurations, use transaction SCC1 to copy them across clients.
  • For Embedded Analytics (Fiori Analytical Apps), transport queries via RSRT or RSRTS_ODP_DIS.

No comments:

Post a Comment

Fiori Development - Style

Okay, here is a rewritten version incorporating the detailed information about developing preformatted layout reports, including a Table of ...