• No results found

Analyze Sales Orders using SAP Analytics Cloud

N/A
N/A
Protected

Academic year: 2022

Share "Analyze Sales Orders using SAP Analytics Cloud"

Copied!
24
0
0

Loading.... (view fulltext now)

Full text

(1)

Extensibility Guide | PUBLIC

Analyze Sales Orders using SAP Analytics Cloud

affiliate company. All rights reserved.

(2)

Content

1 Overview. . . . 3

1.1 Business Scenario. . . 3

2 Technical Implementation Steps. . . . 4

3 Preparation. . . . 5

3.1 Prerequisites. . . 5

4 Implementation Steps. . . . 6

4.1 Implementation Steps in SAP S/4HANA Cloud System. . . 6

Create Custom Fields. . . .6

Create Custom Analytical Query. . . .8

Publish the Query Using View Browser App. . . .10

Create Sales Orders. . . .12

View Published Applications in SAP S/4HANA Cloud. . . .15

4.2 Implementation Steps in SAP Analytics Cloud. . . .16

5 Appendix. . . .21

5.1 Issues. . . 21

5.2 Document History. . . .21

(3)

1 Overview

1.1 Business Scenario

Note

This sample scenario is for learning purposes only. It is intended to give you an understanding of the various technical aspects related to extending SAP S/4HANA Cloud. The sample scenario may not always be available in a readily consumable state due to the continuous improvements being made in the underlying products or services. If this is the case, appropriate adaptations based on the latest documentation of the respective products or services are required.

The analysis of data is an important business requirement. This example shows how to classify sales order data created in SAP S/4HANA Cloud.

A custom field assigned to the sales order in SAP S/4HANA Cloud enables the end user to classify the use of the products included in an order. In this sample, stories in SAP Analytics Cloud are used to enable an in-depth analysis of the sales order data.

Scenario Process Flow:

(4)

2 Technical Implementation Steps

This guide explains how to use a custom code list to create analytics reports for a business scenario. You need access to an SAP S/4HANA Cloud system and an SAP Analytics Cloud system. These apps are required in SAP S/4HANA Cloud: Custom Fields and Logic and Custom Analytical Queries

Step Details

1 Create custom fields with a fixed-length code list

You create a custom field with the following business context: Sales: Sales Document.

2 Enable on the UI and in the CDS view

You enable the created custom field for the data sources C_SALESORDERQUERY and SD_SALESDOC_GUI and in the relevant business scenarios (optional).

3 Create custom analyti­

cal queries

You create a custom analytical query and add it to the SAP Fiori launchpad as an app to make the new dimensions available in the functional report.

4 Publish the query using the View Browser app

You publish the query to make it available as an app in SAP S/4HANA Cloud and as a data source in SAP Analytics Cloud.

5 Create a story in SAP Analytics Cloud

While you create an analytics report, you can create a story based on a model to consume the custom fields via query.

(5)

3 Preparation

3.1 Prerequisites

To perform the steps in this document, make sure that the following prerequisites have been met:

Prerequisites Details

SAP S/4HANA Cloud system You have access to an SAP S/4HANA Cloud system with all the necessary users and authorizations.

SAP Analytics Cloud System You have access to an SAP Analytics Cloud system with all the necessary users and authorizations.

Business Roles The Administrator (SAP_BR_ADMINISTRATOR) business role

has been assigned to your user. Make sure that the Analytics Specialist (SAP_BR_ANALYTICS_SPECIALIST) and Sales Manager (SAP_BR_SALES_MANAGER) business catalogs are also assigned to your user.

SAP S/4HANA Cloud system and SAP Analytics Cloud sys­

tem integration

See this document to to find out more about connecting your SAP S/4HANA Cloud system to the SAP Analytics Cloud system.

(6)

4 Implementation Steps

4.1 Implementation Steps in SAP S/4HANA Cloud System 4.1.1 Create Custom Fields

Purpose

You want to create a custom code list with products used by customers.

Procedure

1. Log on to SAP Fiori launchpad.

2. Open the Custom Fields and Logic app under Extensibility.

3. Choose the Custom Fields tab.

4. Choose Create (+).

5. A dialog box is displayed. Enter the following details under Field Properties.

Field Name Value

Business Context Sales:Sales Document

Field Properties Label

End Use for SAC Scenario

Type Code List

Length 3

Enter the following details under List Values.

Code Value Description

101 Military

102 Building Industry

(7)

Code Value Description

103 Public Sector

6. Choose Create and Edit.

7. Go to the UI and Reports tab. This section determines the availability of this field on the UI, in the API, and in CDS views. Choose Enable Usageto enable the data source C_ SALESORDERQUERY and

SD_SALESDOC_GUI (refer to screenshot below):

8. Go to the Business Scenarios tab. This section determines the business scenarios in which this field must be enabled. Enable the entries as shown in the screenshot:

9. Choose Save and Publish. On the Custom Fields and Logic screen, you’ll see two more fields automatically created for the Sales: Billing Document and Shipping: Delivery business contexts.

(8)

10. Enable the custom field that was automatically created in the Sales: Billing Document business context for the billing-related queries. To do this, navigate to the details of the End Use for SAC Scenario custom field under the Sales: Billing Document business context.

11. Go to the UI and Reports tab. Enable the entry as shown in the screenshot:

12. Choose Save and Publish.

4.1.2 Create Custom Analytical Query

Purpose

You want to create a custom analytical query to make the report functional.

(9)

Prerequisites

To create a custom analytical query, you need the Analytics Specialist business role.

Procedure

1. Log on to SAP Fiori launchpad.

2. Open the Custom Analytical Queries app on the Query Design tab.

3. Choose New.

4. A dialog box is displayed. Enter these details:

Field Name Value

Query Name salesordercube_SAC

Date Source I_SALESORDERCUBE

5. Choose OK.

6. Go to the General tab. In the Label field, enter the name salesorder with Custom Dimension for SAC.

7. Go to the Field Selection tab to select the fields that you want to display as dimensions and measures in the query. In the Available Fields section, search for the custom field End Use for SAC Scenario that was already created and select the one or more checkboxes to select additional fields as shown in the

screenshot:

8. Choose Save Draft.

9. Choose Publish. The YY1_SALESORDERCUBE_SA C custom analytical query is now published.

(10)

4.1.3 Publish the Query Using View Browser App

Purpose

You want to publish the query and make it available as a tile in SAP S/4HANA Cloud.

Prerequisites

To view the published query as an application tile, you need the Sales Manager business role.

Procedure

1. Log on to SAP Fiori launchpad.

2. Open the View Browser app.

3. Search for the Custom Analytical Query you've already created (in this case, YY1_SALESORDERCUBE_SAC).

4. Choose Create Application.

5. Choose Multi-Dimensional Report from the drop-down list.

(11)

6. A dialog box is displayed. Enter the following details:

Field Name Value

Language English

Title YY1_SALESORDERCUBE_SAC

Subtitle I_SALESORDERCUBE_SAC

7. Choose OK.

8. Select the application you've already created.

9. Note down the Annotation Value as highlighted in the screenshot below and go to Show Application Status.

Note

The Annotation Value is used in SAP Analytics Cloud to fetch this query.

10. Choose Add.

(12)

11. Search for the Sales Analytics business context.

12. Choose OK.

13. Select the business catalog you added earlier.

14. Choose Publish.

4.1.4 Create Sales Orders

Purpose

You want to create sales orders and assign values to the code list items.

(13)

Procedure

1. Log on to SAP Fiori launchpad.

2. Open the Create Sales Order - VA01 app.

3. Fill in the following fields.

4. Choose Continue.

5. Enter the necessary information.

6. Choose the icon to display the header details.

(14)

7. Choose the Custom Fields tab.

8. Choose the relevant entries from the specific custom fields.

(15)

9. Enter the item details.

10. Choose Save.

4.1.5 View Published Applications in SAP S/4HANA Cloud

1. You can now search for the published application (in this case, YY1_SALESORDERCUBE_SAC).

2. A dialog box is displayed. Enter the following values:

Field Name Value

Exchange Rate Type M

(16)

Field Name Value

Display Currency EUR

3. You can access the following report:

4.2 Implementation Steps in SAP Analytics Cloud

Purpose

You want to consume a custom field using a query in SAP Analytics Cloud.

Prerequisites

To proceed with these steps, you must first complete the steps described in Integrating SAP Analytics Cloud.

Procedure

1. Log on to SAP Analytics Cloud with the same credentials that you used for SAP S/4HANA Cloud.

2. From the dropdown menu, select create Model .

(17)

3. Select Get data from a datasource.

4. Select Live Data connection.

5. Select the system type SAP BW.

6. Select the connection created during the prerequisites step of integrating SAP S/4HANA Cloud system with SAP Analytics Cloud system.

7. Select a data source. In this case it is the annotation value noted down previously ( YY1_ SALESORD_7).

(18)

8. Choose OK.

9. Save the model by providing the appropriate name and description.

10. From the dropdown menu, choose the options for creating a Story.

(19)

11. Choose an SAP Analytics Cloud Analytics template.

12. Select Data and choose Data acquired from an existing model.

13. Select the model created in step 9 (in this case, YY1_SALESORDER_SAC).

(20)

14. A dialog box is displayed. Enter the following values:

Field Name Value

Exchange Rate Type M

Display Currency EUR

15. Create your Story according to your needs.

(21)

5 Appendix

5.1 Issues

Please note that SAP does not offer any official support for the sample code (see the SAP SAMPLE CODE LICENSE AGREEMENT on GitHub). However, feel free to use the Issues section on GitHub if you have any problems. We recommend that you browse through the known issues section before creating a new issue

.

5.2 Document History

Revision Date Change

1.0 2020-01-10 Document created.

1.1 2020-02-05 Scenario renamed from Analyze Sales Orders with Custom Fields Created in SAP S/

4HANA Cloud using SAP Analytics Cloud to Analyze Sales Orders using SAP Analytics Cloud.

(22)

Important Disclaimers and Legal Information

Hyperlinks

Some links are classified by an icon and/or a mouseover text. These links provide additional information.

About the icons:

Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.

The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code

Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related Language

We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

(23)
(24)

www.sap.com/contactsap

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

References

Related documents

The positive and signi…cant coe¢ cient on the post shipment dummy in the fourth column implies that prices charged in post shipment term transactions are higher than those charged

Developed for middle school students, this resource, available in either English or Spanish, provides opportunities for students to examine violence and prejudice, address issues

The limit of liability shown in the Declarations for each person for Bodily Injury Liability is our maximum limit of liability for all damages arising out of bodily injury to

○ If BP elevated, think primary aldosteronism, Cushing’s, renal artery stenosis, ○ If BP normal, think hypomagnesemia, severe hypoK, Bartter’s, NaHCO3,

The PROMs questionnaire used in the national programme, contains several elements; the EQ-5D measure, which forms the basis for all individual procedure

law firm of Kohn, Kohn & Colapinto, LLP (http://www.kkc.com) served in the 1980’s as the Director of Corporate Litigation for the Government Accountability Project.. His

Abstract In this paper the well-known minimax theorems of Wald, Ville and Von Neumann are generalized under weaker topological conditions on the payoff function ƒ and/or extended

Online community: A group of people using social media tools and sites on the Internet OpenID: Is a single sign-on system that allows Internet users to log on to many different.