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
- Open the Fiori App where the variant is created.
- Go to the Variant Management option.
- Select the variant you want to transport.
- Check if the variant is stored as a "Shared Variant" (Personal variants cannot be transported).
- 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
.
- Open SAP GUI and execute
B. Using Transaction /UI5/FLPD_CUST
(For Launchpad Variants)
If your variant is stored in the Fiori Launchpad configuration:
- Run
/UI5/FLPD_CUST
in SAP GUI. - Locate the target variant.
- Assign it to a Transport Request.
- 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
- Open the SAP Business Application Studio (BAS) or Web IDE.
- Locate the Adaptation Project in your workspace.
- Commit changes to Git (if applicable).
- 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.
- In
B. Transporting Adaptations via ABAP Repository
- Use Transaction
SUI_SUPPORT
to locate the variant. - Select Export and Transport.
- Assign the transport request.
- Release it via
SE09
.
3. Verifying the Transport in Target System
After transport, follow these steps:
- Execute the Fiori App in the target system.
- Verify the variant is available under the "Manage Views" section.
- 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
orRSRTS_ODP_DIS
.
No comments:
Post a Comment