SAP Industry Solution Oil & Gas

Mobile Ticket Data Capture App

September 2018

CUSTOMER
Disclaimer

The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the
permission of SAP. This presentation is not subject to your license agreement or any other service or subscription
agreement with SAP. SAP has 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's strategy and possible future developments, products and or platforms directions and
functionality are all subject to change and may be changed by SAP 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. This document is provided without a warranty of any kind, either express or implied, including but not
limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This
document is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility
for errors or omissions in this document, except if such damages were caused by SAP´s willful misconduct or gross
negligence.

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, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 2

Objectives

After completing this learning module, you will be able to:

• Outline the overall 1809 scope for Mobile Ticket Data Capture at terminals using the newly
developed features of the Hybrid Mobile App

• Understand the process how the TSW Ticket data is captured, transmitted and
documents are posted

• Get the details of Settings, Mapping and Configuration required for Mobile Ticketing

• Explain the value proposition to customers

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 3

SAP Oil & Gas Mobile Ticket Data Capture App
Designed for the Terminal Operator
SAP Oil & Gas Mobile Ticket Data Capture App
Loading details captured and passed to SAP Backend by Terminal Operator when a nomination is actualized

Scope: Capture the loading details for nomination item, when it is being loaded by Terminal Operator,
in a Mobile App and passing them to SAP Backend where tickets are posted.

• Define the authority for each Terminal Operator in order to restrict nomination items from being
downloaded to his/her device

• Make settings to define the date range and status of nomination items that would be downloaded
to Mobile for each location & transport system

• Download the nomination items scheduled for the location, transport systems and authorized for the
user

• Capture the loading details for the nomination item as it is being loaded, such as quantity, UoM,
dates, parameters, additional quantities as well as ticket event data*

• Send the ticket data to backend by syncing the device

* New 1809 feature

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 5
SAP Oil & Gas Mobile Ticket Data Capture App
Agenda – Deep Dive

• Download the nomination items to mobile device

• Mobile Ticket Data Capture (offline or online mode)

• Application Interface Framework (AIF)

• Settings and configuration

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 6

Download Nominations to Mobile Device
Download Nominations to Mobile Device (I)

• The App is installed on the mobile device

(Android and iOS)

user id
• Once user opens the App, it requires to be
logged in using user credentials

• Once user logs into the App, the nominations

scheduled for location & transport system are
downloaded to the device

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 8

Download Nominations to Mobile Device (II)

A nomination item can have the following status:

• Due – Nomination item that has not been ticketed yet
• Saved – Nomination item with ticket data captured and
saved in local data store when device is offline, yet to be
sent to SAP backend
• Sent – Nomination item for which captured ticket data is
sent to SAP backend but stuck with error in AIF
• Processed – Nomination item for which captured ticket
data is sent to SAP backend and a ticket is created, not
actualized
• Actualized – Nomination item for which captured ticket
data is sent to SAP backend and ticket is created and
actualized

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 9

Mobile Ticket Data Capture
Mobile Ticket Data Capture (I)

• Due Status nomination item, when clicked directly

takes to Ticket Create object page
• The Nomination Details are also displayed in first
anchor tab
• Loading/Unloading details such as Actual
Quantity, UoM, Start & End Date/Time could be
captured in the Movement Details tab
• Default Physical Parameters displayed could be
edited as required
• Additional Quantities could be keyed if available
• Additional Quantities are not calculated in the
device, instead it only captures what is entered
and sends to SAP backend

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 11

Mobile Ticket Data Capture (II)

• Multiple ticket events can be captured under the

events tab including the following information*

• Event type
(Available event types are defaulted from backend system)

• Sequence number
• Actual Start Date / Time
• Actual End Date / Time
• Optional Event Long Text

* New 1809 feature

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 12
Mobile Ticket Data Capture (III)

• If mobile device is offline, the ticket data captured gets

saved in local data store and status moves to “Saved”
• Multiple tickets for the same nomination (item) can be
created in offline mode*
• Once online, the device is synced with a pull down refresh
or by tapping on sync icon
• Upon syncing, data from mobile is flushed to SAP backend
and new data is fetched and downloaded to device
• The status then moves from “Saved” to “Sent” or
“Processed” or “Actualized”
• If mobile device is online, the status directly moved from
“Due” to “Sent” or “Processed” or “Actualized”
• Upon clicking a nomination item with status “Sent” or
“Processed” or “Actualized”, it displays the ticket object page

* New 1809 feature

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 13
Application Interface Framework (AIF)
Application Interface Framework (AIF)

• Application Interface Framework (AIF)

is a middleware embedded within SAP
backend where all activities such as
logging, validation, mapping,
monitoring, processing is executed
• Logging: The nominations downloaded
to mobile or ticket messages sent from
mobile to SAP backend are logged in
Application Interface Framework
• Mapping: Value mappings will be
executed where data is mapped from
raw to SAP structure
• Validation: Validation of message
content could be enabled in AIF such that
any message with a defective content
does not get processed

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 15

Settings, Configuration & BADIs
Settings required for Mobile Ticket Data Capture
• In O4NMTC transaction, for combination
of TSW location and transport system,
settings could be maintained for
nomination items download to mobile
device
• The Days in past and future defines the
horizon where all Nomination items with
schedule dates in this date range gets
picked up
• The status flagged would get picked to be
downloaded to mobile
• The ticket message captured in mobile
creates a ticket in SAP backend with
Ticket Type as defined in this transaction
• The Ticket Actualize column defines if
the message received from mobile device
should only create a ticket or create &
actualize the ticket
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 17
Configuration in SPRO for Mobile Ticketing

• The Ticket External Number is

assigned internally by system since
tickets are automatically created in
SAP backend with mobile ticket
messages

• The number range for the external

number could be configured in SPRO

• The External Number Range Group

could be maintained for each ticket
type in the SPRO

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 18

BADIs for Mobile Ticketing

• The Ticket External Number range

assignment could be enhanced using a
BADI OIJ07_NMT_EXTKTNUM

• The logic to fetch nomination items to

be downloaded could be enhanced
using BADI
OIJ07_NMT_NOMINATIONFETCH

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 19

SAP Oil & Gas Mobile Ticket Data Capture App
Value Proposition

Drivers & Motivation Benefits & Value

• Support terminal operator‘s daily • Ease of use, minimizing manual intervention

activities with ad hoc ticket data capture or errors

• Allow capturing relevant ticket data while • Data flow is near to real time
executing a movement
• Accelerated and efficient Order to Cash
• Enabled with offline capability for low- cycle
connectivity areas
• Offline data capture capability for areas
• Seamless flow of information between with limited connectivity
terminal and SAP back office

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 20

Summary

You should now be able to

• Outline the overall 1809 scope for Mobile Ticket data capture at terminals using the newly
developed features of the Hybrid Mobile App

• Understand the process how the TSW Ticket data is captured, transmitted and Documents
posted

• Get the details of Settings, Mapping and Configuration required for Mobile Ticketing

• Explain the value proposition to customers

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 21

© 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://global.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.