What is SAP Analysis for Office

SAP Analysis for Microsoft Office (Analysis for Office or AfO) is a Microsoft Office add-in that allows users to perform multidimensional analysis of OLAP (Online Analytical Processing) data sources directly within Microsoft Excel and PowerPoint. Here's a breakdown of its key features and purposes:

• Integration with SAP Data:
  • It enables users to connect to and analyze data from various SAP sources, including SAP Business Warehouse (BW), SAP Business Planning and Consolidation (BPC), and SAP S/4HANA.
• Analysis within Microsoft Office:
  • It leverages the familiar Microsoft Excel and PowerPoint environments, making it easier for users to analyze and present SAP data.
• Multidimensional Analysis:
  • It supports multidimensional analysis, allowing users to drill down into data, filter, and pivot to gain deeper insights.
• Reporting and Planning:
  • It facilitates the creation of reports and supports planning scenarios, including those involving embedded BPC.
• Key Benefits:
  • Enables efficient analysis of large data volumes.
  • Provides rapid access to various SAP data sources.
  • Offers flexible processing and storage of workbooks, including offline capabilities.

In essence, SAP Analysis for Office bridges the gap between SAP's data and the widely used Microsoft Office suite, empowering users to analyze and report on business data effectively.

SOX Reports

"SOX reports" in an SAP environment aren't a separate, built-in category but rather refer to the financial reports and audit trails that companies rely on to meet Sarbanes-Oxley (SOX) compliance requirements. In practice, organizations use several standard and sometimes custom SAP reports to provide evidence of strong internal controls over financial reporting. Key examples include:

Financial Statement Reports

• Balance Sheet & Profit & Loss Reports: These reports (often generated using Financial Statement Versions) provide the summarized financial data needed to verify the integrity of the financial statements.
• Cash Flow Statements: Essential for showing how cash moves through the organization.

Ledger and Transaction-Level Reports

• General Ledger Reports: These detail all financial transactions at the account level and are critical for verifying journal entries and ensuring accuracy.
• Trial Balance Reports: Summarize the balances of all general ledger accounts to ensure that debits and credits are in balance.

Audit and Detail Reports

• Audit Trail Reports: These track changes and document the flow of transactions, helping auditors trace how figures have been compiled.
• Sub-Ledger Reports: Reports for areas like Accounts Receivable, Accounts Payable, and Asset Accounting reconcile detailed transactions with the general ledger.

Additional Considerations

• Custom or Enhanced Reports: Many organizations build custom reports or leverage SAP's Governance, Risk, and Compliance (GRC) tools to address specific internal control and SOX requirements, such as segregation of duties and access controls.

Ultimately, while SAP does not label any report explicitly as a "SOX report," the above reports form the backbone of SOX compliance by ensuring financial data is complete, accurate, and supported by a robust audit trail. The exact set of reports considered "SOX reports" can vary by organization based on their internal control framework and compliance strategy.

Types of CDS Views in SAP

SAP Core Data Services (CDS) views are categorized based on their purpose and functionality within the SAP system. The main types of CDS views are:

1. Basic (Interface) Views

• These are the foundation of the virtual data model (VDM).
• They provide direct access to database tables and primarily focus on exposing raw data.
• Used for defining reusable, stable interfaces without applying business logic.
• Example: I_EmployeeBasicData

2. Composite Views

• Built on top of Basic Views to apply business logic, aggregations, or transformations.
• Combine multiple data sources to create meaningful analytical datasets.
• Used for reusable data sets in multiple applications.
• Example: C_SalesOrderAnalytics

3. Consumption Views

• Designed for direct consumption in analytics tools like SAP Fiori, Analysis for Office, and SAC.
• Typically exposed as OData services for UI applications.
• Include annotations for UI, analytics, and authorization.
• Example: C_ProfitabilityAnalysis

4. Transactional Views

• Support transactional processing by providing real-time operational insights.
• Often used in Fiori apps that interact with transactional data.
• Example: I_SalesOrderItem

5. Analytical Views

• Optimized for reporting and analytical scenarios.
• Used in embedded analytics and SAC reporting.
• Include measures, calculated fields, and aggregations.
• Example: C_FinancialStatement

6. Fact Views

• Represent core business data in a structured way.
• Typically contain transactional information like sales, revenue, and orders.
• Example: I_AccountingDocumentItem

7. Dimension Views

• Represent master data structures like customers, materials, or employees.
• Used to enrich transactional data with descriptive attributes.
• Example: I_Customer

8. Hierarchy Views

• Used to define hierarchical structures like cost centers, profit centers, or organizational units.
• Example: I_CostCenterHierarchy

9. Extension Views

• Allow enhancement of standard CDS views without modifying the original.
• Example: Extend View for I_SalesOrder

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.