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.

SAP S4 Challenges for InfoProviders

There isn't a dedicated Fiori app specifically for listing InfoProviders in SAP S/4HANA, as the traditional concept of InfoProviders (like InfoCubes and DSOs) is mostly replaced by CDS Views, Analytical Queries, and Embedded BW objects. However, you can use the following Fiori apps to find relevant reporting data sources:

1. View Data Sources and Queries in S/4HANA

• App: View Browser (F2330)
  • Use this app to search for CDS Views and Analytical Queries available in S/4HANA.
  • You can filter by application component, data category (cube, dimension, transactional), or keywords.
  • Search for views starting with:
    • I_ (Interface Views)
    • C_ (Cube Views for reporting)
    • P_ (Projection Views)

2. Find Analytical Queries (BW-Style Reporting)

• App: Custom Analytical Queries (F2804)

  • Allows you to find and create Analytical Queries, which act as InfoProviders for reporting.
  • You can explore queries based on standard SAP S/4HANA CDS Views.

• App: Query Browser (F2580)

  • Lists available Analytical Queries and allows you to execute them.
  • These queries are based on CDS Views, replacing the need for traditional InfoProviders.

3. Find SAP BW Objects in Embedded BW

If you have Embedded BW enabled in your S/4HANA system:

• App: Data Source Browser (Available in some systems)
  • Helps identify ODP sources, ADSOs, and Composite Providers used in Embedded BW.
• Alternatively, use Transaction RSA1 in GUI to explore InfoProviders.

SAP S / InfoCubes and InfoProviders

In SAP S/4HANA, the traditional InfoProviders (such as InfoCubes and DSOs from SAP BW) are no longer used in the same way. Instead, SAP S/4HANA relies on CDS Views, HANA Calculation Views, and Embedded Analytics for reporting. However, if you are looking for reporting data structures in SAP S/4HANA, here's how you can find them:

1. Using Transaction Code RSA1 (for BW-Embedded in S/4HANA)

• If you have Embedded BW activated in SAP S/4HANA, you can use RSA1 to check the available InfoProviders.
• Navigate to Modeling > InfoProvider to find Advanced DSOs (ADSOs), CompositeProviders, and Open ODS Views.

2. Using SE11 or SE16N (For CDS-Based Reporting)

• Many reports in SAP S/4HANA are based on ABAP CDS Views. To find them:
  1. Open SE11 or SE16N.
  2. Look for tables with the prefix I_ (for interface views) or C_ (for cube-like analytical views).
  3. Example: I_GLAccountLineItemCube (General Ledger Reporting).

3. Using Eclipse ADT or GUI Transaction SDDLAR

• If you have access to Eclipse with ADT:
  1. Open Eclipse and go to ABAP Development Perspective.
  2. Search for DPC_EXT or use the Data Definition editor to explore available CDS Views.
• Alternatively, in SAP GUI, use Transaction SDDLAR to list CDS Views.

4. Checking Fiori Apps and SAP Standard Content

• Many standard Fiori apps use Analytical Queries (CDS Views).
• Use Transaction RSRT to find available analytical queries.

5. Checking HANA Views in SAP HANA Studio or Eclipse

• If you have HANA Studio or Eclipse, you can look at SAP_HANA_CALCULATION_VIEWS for predefined views used in reporting.

6. Using Transaction RSRTS_ODP_DIS (For ODP Data Sources)

• If your reporting solution is using Operational Data Provisioning (ODP), check this transaction to find available ODP providers.

How find BAPI for Technical Catelog

How to Find BAPIs Used in SAP_TC_PRC_COMMON?

Since Technical Catalogs primarily deal with Fiori applications and OData services, BAPIs are usually called via these services. Here's how you can find the BAPIs used:

1. Find Applications and OData Services in the Technical Catalog

1. Go to SAP GUI and open transaction /UI2/FLPCM_CONF (Fiori Launchpad Content Manager).
2. Search for SAP_TC_PRC_COMMON in the Technical Catalogs section.
3. Click on the catalog to see the list of apps, transactions, and OData services it contains.
4. Note the OData service names used in the apps.

2. Identify the Backend OData Service in SAP Gateway

1. Open transaction /IWFND/MAINT_SERVICE in SAP Gateway.
2. Search for the OData service(s) you found in step 1.
3. Select the service and navigate to the Service Implementation tab.
4. Look for the Entity Sets and their associated ABAP Class/Methods.

3. Find the BAPIs in the Backend Implementation

1. Once you find the ABAP class in the OData Service, go to transaction SE24.
2. Enter the class name and check the methods.
3. Look for CALL FUNCTION statements in the method implementations to find the BAPIs used.
4. You can also check the CDS views that might be exposed through OData.

4. Alternative: Search for Standard BAPIs in SE37

If you are unsure which BAPIs are used, try:

1. Transaction SE37 – Search with BAPI_* keywords related to procurement.
2. Transaction SE80 or SE93 – Find the backend transactions used and check their associated function modules.

---

Summary

• SAP_TC_PRC_COMMON is a Procurement Technical Catalog in S/4HANA.
• It contains Fiori apps, OData services, and transactions.
• Use /UI2/FLPCM_CONF to explore its contents.
• Identify OData services in /IWFND/MAINT_SERVICE.
• Find the corresponding ABAP class in SE24 and check for BAPI calls.
• Use SE37 to look for procurement-related BAPIs.

Fiori Infrastructure and Related Basis Activities

Introduction

SAP Fiori is a modern, role-based UX solution designed to provide a seamless and intuitive experience across various devices. Implementing Fiori in an enterprise landscape requires a well-planned infrastructure setup and effective Basis administration. This article covers key aspects of Fiori infrastructure, including Web Dispatcher setup in an embedded architecture, Web Dispatcher upgrade, and Fiori server sizing considerations.

---

1. Fiori Infrastructure Overview

Fiori infrastructure involves multiple layers and components, including:

• Frontend Server (FES): Hosts SAP Fiori applications and acts as a gateway for users.

• Backend Server (BES): Houses business logic and data services.

• SAP Gateway (ODATA Services): Facilitates communication between frontend and backend.

• SAP Web Dispatcher: Acts as a reverse proxy to route traffic efficiently.

• SAP Cloud Connector (if applicable): Used for hybrid cloud scenarios.

Two main deployment approaches exist:

• Embedded Deployment: FES and BES are on the same system (e.g., S/4HANA system).

• Hub Deployment: FES is on a separate system, connecting to multiple BES.

---

2. Web Dispatcher Setup in Embedded Architecture

SAP Web Dispatcher plays a crucial role in Fiori's embedded architecture by load balancing and routing incoming HTTP(S) requests.

2.1 Prerequisites

• Ensure Web Dispatcher is installed on a dedicated server or as part of the SAP landscape.

• Obtain SSL/TLS certificates for secure communication.

• Maintain an appropriate network firewall configuration.

2.2 Configuration Steps

1. Install SAP Web Dispatcher

   • Download from SAP Software Download Center.

   • Install using sapwebdisp executable.

2. Modify Profile Parameters (sapwebdisp.pfl)

   • Define backend target systems:

     wdisp/system_0 = SID=EBS, EXTSRV=http://backendhost:8000, SRCSRV=*  wdisp/system_1 = SID=FES, EXTSRV=http://fiorihost:443, SRCSRV=*

   • Enable SSL if required:

     ssl/server_pse=webdisp.pse

   • Define URL filtering to restrict direct backend access.

3. Start and Validate Web Dispatcher

   • Use command:

     sapwebdisp -checkconfig

   • Restart Web Dispatcher:

     sapwebdisp -restart

   • Test with:

     https://webdispatcher.domain.com/sap/bc/ui5_ui5/sap/...

---

3. Web Dispatcher Upgrade

Regular upgrades ensure security, performance, and compatibility with newer SAP releases.

3.1 Pre-Upgrade Activities

• Check current Web Dispatcher version:

  sapwebdisp -version

• Review SAP Note recommendations.

• Backup sapwebdisp.pfl and SSL certificates.

3.2 Upgrade Process

1. Download Latest Version from SAP Support Portal.

2. Stop Web Dispatcher:

   sapwebdisp -stop

3. Replace Executables:

   cp NEW_VERSION/sapwebdisp /usr/sap/SAPWebDisp

4. Restart Web Dispatcher:

   sapwebdisp -start

5. Verify Functionality:

   • Ensure logs show successful startup (dev_webdisp).

   • Test URL routing and load balancing.

---

4. Fiori Server Sizing for Embedded Setup

Proper sizing ensures performance and scalability of the embedded Fiori landscape.

4.1 Key Factors Affecting Sizing

• Number of Concurrent Users: Active Fiori users in peak hours.

• Type of Fiori Apps: Transactional, Analytical, or Fact Sheets.

• SAPS Requirement: CPU processing capacity (SAP Application Performance Standard).

• Memory Consumption: Based on HANA DB footprint.

4.2 SAP Recommendations

CPU and Memory Sizing (Baseline for Embedded Fiori on S/4HANA)

Users	CPU Cores	Memory (GB)
100	4	32
500	8	64
1000	16	128

HANA Database Sizing

• Rule of Thumb:

  • 3GB per 100 active users.

  • Additional 1GB for every 50GB of transaction data.

Storage Considerations

• SSD-based storage for faster response.

• 50GB free space for logs and updates.

4.3 Performance Optimization

• Implement Caching and Compression via Web Dispatcher.

• Optimize OData Services to minimize backend load.

• Enable Lazy Loading in UI5 apps.

• Utilize CDS Views for efficient data retrieval.

---

Conclusion

A well-designed SAP Fiori infrastructure with optimized Web Dispatcher and proper server sizing ensures a robust, scalable, and high-performance environment. Regular upgrades and proactive monitoring further enhance the user experience and system stability. By following the best practices outlined in this guide, organizations can maximize the benefits of SAP Fiori in an embedded setup.

Connecting SAP Analytics Cloud (SAC) to SAP ECC Data

Connecting SAP Analytics Cloud (SAC) to SAP ECC Data

This document outlines the different methods for connecting SAP Analytics Cloud (SAC) to SAP ECC data. Since ECC doesn't directly integrate with SAC, we'll explore various intermediary tools and techniques to bridge the gap.

Table of Contents

1. Using SAP BW as a Bridge
   • Ideal Use Case
   • Pros & Cons
   • Key Considerations
2. Using SAP HANA as a Bridge
   • Ideal Use Case
   • Pros & Cons
   • Key Considerations
3. Using OData Services
   • Ideal Use Case
   • Pros & Cons
   • Key Considerations
4. Using Flat Files
   • Ideal Use Case
   • Pros & Cons
   • Key Considerations
5. Using 3rd Party ETL Tools
   • Ideal Use Case
   • Pros & Cons
   • Key Considerations
6. Connection Scenarios in SAC
   • Live Connection
   • Import Connection
7. Best Practices
   • Performance
   • Security
   • Data Modeling

1. Using SAP BW as a Bridge

• Ideal for: Organizations already leveraging SAP BW, or those requiring complex data transformations and modeling.
• Pros: Robust data warehousing capabilities, mature ETL processes, potential for historical data analysis.
• Cons: Can add complexity and overhead if BW is not already in place.
• Key Considerations:
  • BW Version: Ensure your BW system is compatible with SAC.
  • Data Extraction: Utilize appropriate extractors (e.g., FI-GL, CO-PA) to extract data from ECC.
  • Query Optimization: Design efficient BW queries for optimal performance in SAC.

2. Using SAP HANA as a Bridge

• Ideal for: ECC systems running on HANA or organizations with a separate HANA database.
• Pros: Real-time data access, powerful data modeling capabilities within HANA.
• Cons: Requires HANA expertise and infrastructure.
• Key Considerations:
  • Data Replication: Choose the appropriate replication method (SLT or SDI) based on your needs and HANA version.
  • Calculation Views: Model your data using calculation views in HANA for efficient data access in SAC.

3. Using OData Services

• Ideal for: Exposing specific datasets from ECC for analysis in SAC.
• Pros: Direct access to ECC data without a separate data warehouse.
• Cons: Can be limited in terms of data modeling and transformation capabilities.
• Key Considerations:
  • SAP Gateway: Configure SAP Gateway to enable OData services for your ECC system.
  • OData Service Creation: Develop or utilize existing OData services that expose the required ECC data.

4. Using Flat Files

• Ideal for: Ad-hoc analysis or small datasets.
• Pros: Simple and straightforward approach.
• Cons: Not suitable for large datasets or frequent data refreshes.
• Key Considerations:
  • Data Preparation: Ensure data is properly formatted and cleansed before importing into SAC.
  • Data Refresh: Manually update data by importing new flat files.

5. Using 3rd Party ETL Tools

• Ideal for: Organizations with existing ETL infrastructure or complex data integration needs.
• Pros: Flexibility and powerful data transformation capabilities.
• Cons: Can introduce additional costs and complexity.
• Key Considerations:
  • Tool Selection: Choose an ETL tool that supports both ECC and SAC.
  • Data Integration: Design and implement ETL processes to extract, transform, and load data into SAC.

6. Connection Scenarios in SAC

• Live Connection: Real-time data access without data replication (possible via BW, HANA, or S/4HANA).
• Import Connection: Data is imported into SAC, allowing you to model and transform data (used with OData, flat files, or databases).

7. Best Practices

• Performance: Use live connections for real-time data analysis, but ensure the source system can handle the load.
• Security: Configure SAC connections to comply with your organization's security policies.
• Data Modeling: Prepare your data models (e.g., CDS views in HANA or SAP BW queries) for better performance and usability in SAC.

How to connect SAP SAC to ECC data , if possible a brief

Connecting SAP Analytics Cloud (SAC) to ECC data is possible, but it can be a bit involved depending on your ECC system's specifics. Here's a breakdown of the process and key considerations:

Prerequisites:

• SAP ECC 6.0 EHP 07 SPS 04 or higher: This is the minimum requirement for connecting SAC to ECC.
• Cloud Connector: This establishes a secure tunnel between your SAP Cloud Platform and your on-premise ECC system.
• SAP Agent: This facilitates communication between the Cloud Connector and your ECC system.

Connection Options:

1. Import Connection: This involves importing data from your ECC system into SAC. You can use either:
   • InfoSet Queries: These are predefined queries in ECC. However, they can be performance-intensive.
   • SAP Queries: Another type of query in ECC, offering similar functionality to InfoSet Queries.
   Limitations:
   • No Real-time Data: Import connections don't provide live data. You need to schedule data refreshes to keep your SAC data up-to-date.
   • Limited to Queries: You're restricted to using InfoSet Queries or SAP Queries as your data source.
2. Live Connection (with Embedded BW): If your ECC system runs on HANA, you can leverage the embedded BW within ECC.
   • Advantages:
     • Real-time Data: Access live data from your ECC system.
     • More Data Sources: You can utilize various BW objects and connections, offering more flexibility than import connections.
   • Process:
     • Create BW queries on your ECC system.
     • Connect SAC to these queries using a live connection.
3. Live Connection (with Separate BW): If your ECC system doesn't run on HANA or you prefer a separate BW layer, you can:
   • Set up a separate BW system: This can be a dedicated BW system or a BW system that also serves other purposes.
   • Create Virtual Providers in BW: These virtual providers connect to your ECC data.
   • Connect SAC to BW Queries: Establish a live connection between SAC and the queries built on the virtual providers in your BW system.

Important Considerations:

• Performance: For import connections, optimize your InfoSet Queries or SAP Queries for performance to avoid slow data refreshes.
• Security: Set up appropriate security measures in SAC to control access to your ECC data.
• Data Modeling: Once the data is in SAC, you can utilize SAC's modeling capabilities to transform and prepare your data for analysis and visualization.

Steps for Setting Up an Import Connection:

1. Install and configure the Cloud Connector.
2. Install and configure the SAP Agent.
3. Create an import data connection in SAC.
4. Select your ECC system and specify the InfoSet Query or SAP Query.
5. Schedule data refreshes to keep your data up-to-date.

For live connections, the process will involve additional steps related to configuring BW and creating queries.

Remember that connecting SAC to ECC can be complex, especially for live connections. If you're unsure about any part of the process, it's best to consult with an SAP expert or refer to the official SAP documentation.