0% found this document useful (0 votes)
8 views6 pages

Building Enterprise Digital Application

Uploaded by

albert garcia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
8 views6 pages

Building Enterprise Digital Application

Uploaded by

albert garcia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Building Enterprise Digital Application

ShoppingFresh Application
SCENARIO

Supermarkets are facing digital disruption by the new online business retail business models. Consumer
expects these days features like same day delivery, ability to order groceries and shipment status online.
Shopping Fresh application guides shipment delivery team to optimize their routes, deliver more items on
time to maximize profit and improve customer index.

DETAILS
We will be building the structure of a business scenario, in which, a fictitious company that sells fresh grocery
items has been struggling with Digital Transformation to compete in the new economy and is searching for
new ways to increase its exposure. This company is a global player with several subsidiaries and locations
world-wide selling its products through direct distribution channels.
To make it easier to onboard new partners and channels, they want to open their legacy landscape, ERP, for
Secure, Controlled Access as an API, allowing for the creation of applications by partners (imagine Amazon)
and independent developers (imagine Price Comparison websites), in a self-service manner. To achieve this,
they need to decouple the complexity of their backend systems, from what the Developers will be using to
develop their applications. The answer is to place API Management on top of their SAP system, to give
governed access to the outside world to be able to search their Catalog, and have consumers make
purchases directly. They also would like to create a digital application for their local supply and distribution
team with shows the exact shipment delivery location maintained in their legacy ERP systems with Geo
Maps co-ordinates coming from their third-party map provider.
In this Mission we would be showing you how to build an Enterprise digital application which we call as
ShoppingFresh using SAP Integration Suite API Management. We will be building the API Proxy and
Application focusing on the direct consumer scenario. See below for illustration of Company architecture,
and which part we will be working on.

2
LET’S BEGIN THE EUREKA JOURNEY
To make this Eureka series fun and interactive, we have broken this session into the following hands on
exercises.
Exercise 0: Set up Integration Suite API Management capability
Exercise 1: Create connection to a Demo SAP Gateway system (Create API Provider)
Exercise 2: Discover OData API from Demo SAP Gateway system and create API proxy
Exercise 3: Secure and Manage OData APIs
Exercise 4: Create a Product - a unit of API Exposure
Exercise 5: Get a glimpse of usage statistics on your digital asset
Exercise 6: Monetize your APIs by charging the callers of this API
Exercise 7: Debug

3
4
www.sap.com/contactsap

© 2018 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject
to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material,
code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance
on these forward-looking statements, and they should not be relied upon in making purchasing decisions.
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. See http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark
information and notices.

You might also like