active alerts use cases presentation

24
1 Minola Technology An SAP Mobile Apps & ABAP partner Presentation SAP Mobile App Active Alerts

Upload: truongtruc

Post on 12-Feb-2017

214 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Active Alerts Use Cases Presentation

1

Minola Technology An SAP Mobile Apps & ABAP partner

Presentation

SAP Mobile App

Active Alerts

Page 2: Active Alerts Use Cases Presentation

2

Use Cases

Page 3: Active Alerts Use Cases Presentation

3

Use cases

1: A batch EDI interface of sales orders is run on a

regular basis with a need to know if it fails or if there is any missing field values. In the case of a fail then the appropriate person needs to be notified.

2: A vendor invoice is parked and then posted by the same user

alert Accounts Payable manager.

3: A change has been made to allow access SAP_ALL to an

existing user. The compliance manager needs to be aware immediately.

Page 4: Active Alerts Use Cases Presentation

4

Use cases

4: If a Purchase requisition is released by it’s requisitioner then PO manager may need to be aware.

5: Failed IDocs where incoming vendor invoices are being auto

matched against GRN’s. If there is no match possible then IDoc fails (status =51) and Accounts Payable manager needs an alert immediately.

6 GR Reminder: Sundry P/O’s where invoice was receipted

and required Goods receipt was not posted, and therefore the invoice was blocked. This is a reminder Alert. The alert is dynamically split between the users who created the original requisitions (also could be sent to the user who created the P/O or the user who released the requisition).

Page 5: Active Alerts Use Cases Presentation

5

Use cases

7: End of period: SAP transaction VFX3 reports SD Billing documents which are blocked for integration with FI. This Alert is sent to the user who created the billing document and reminds them to fix the problem well before the end of the Period.

8: Key Job Monitor : If the named job(s) is cancelled for any reason an Alert is immediately sent to the IT manager who then has time to react and fix the problem before it becomes a big issue.

9: Unprocessed EDI TXT Files: The Alert is designed to highlight any

EDI files which are not processed at a specific time. It reads the specified directory(ies) on the SAP Server(s), and an Alert is sent if any files exist. This indicates to the recipient that there was a problem processing the files listed.

Page 6: Active Alerts Use Cases Presentation

6

Summary of problem & requirements

A problem may arise or an event take place and nobody is

aware of it where action is needed quickly.

This problem may be detected on tables, jobs, directories, other.

A control description call-to-action is required to resolve the problem.

The call-to-action must be to the appropriate person/agent.

It must be “pushed” by email and/or Mobile.

Page 7: Active Alerts Use Cases Presentation

7

Minola Technology An SAP Mobile Apps & ABAP partner

Overview

Active Alerts

Page 8: Active Alerts Use Cases Presentation

8

Active Alert: Data Extraction Layer

•ABAP Classes

•SAP Infoset & Query

Alerts

8

Active Alert: Notification Layer

•ABAP Classes to dynamically determine recipients / agents

•Statically assigned recipients / agents

Tables Jobs Directories Logs

Auto email Allow Mobile App manage

the call-to-action

RFC sources Other

Sources

ECC

Page 9: Active Alerts Use Cases Presentation

9

Who could receive Alerts?

Internal IT SAP Support group

External SAP Support group(s)

Compliance group /

GRC controls

Users (who could also configure

their own)

Page 10: Active Alerts Use Cases Presentation

10

BASIS

FICO

Compliance

MM

SD

other

Alerts

Page 11: Active Alerts Use Cases Presentation

11

Data extract classes – examples used

Class Name Inputs Description

Query User Group

Query Name

Generic extract class for all ABAP Queries

Server directory name

Reads file details from a specific directory on a SAP server

/MTE/CL_EVENT_ABORTED_JOB Job Name Check whether the specified job name(s) have aborted

/MTE/CL_EVENT_INFOSET

/MTE/CL_EVENT_UNPROCESSED_FILE

Page 12: Active Alerts Use Cases Presentation

12

Key features

Can work with various Data Extract classes

Minimum number of actual scheduled jobs (via SM36 & SM37)

flexibility in deciding all alerts or net change

Control description call-to-action with alert / mitigation

Auto determine agent or recipient from transaction

Can push an alert to notify technical staff, individual

users, user groups, support companies, agents By email and/or mobile device.

Out-of-box Alerts Content

Page 13: Active Alerts Use Cases Presentation

13

Differences with SQ01

Generate Alert

Not based just tables – also with jobs, directories, other

extract classes

flexibility in deciding all alerts or net change

No need to get involved with SM36 & SM37

Less jobs via SM36 & SM37 required

Alert only if results (no blank alerts)

Out-of-box Content

Page 14: Active Alerts Use Cases Presentation

14

Differences with SQ01

Call-to-action

Also to the appropriate person from transaction

Auto-splitting alerts by appropriate receiving person

With control description call-to-action / mitigation

Pushed to email

Pushed to Mobile

Page 15: Active Alerts Use Cases Presentation

15

Pre-requisites

SAP ERP ECC (also BW,HR,CRM,SRM)

Mobile infrastructure:

SAP Gateway 2.0 SP04 and

SMP* platform or

SMP platform (run-time only)

Device requirements: Google Android OS version 4.1.2 or higher

* SMP = SAP Mobile Platform (previously named SUP)

Page 16: Active Alerts Use Cases Presentation

16

Benefits – effort & cost savings

Remove the need to remember what actions to take

Immediate directing of problems to appropriate person for call-to-action = less effort to do it manually

reduce development costs of writing own automated checks (e.g. using ABAP)

Option to now include new automated alerts where previously it would have been impractical to do so (memory, time, effort). e.g. on interfaces, IDocs, processes, compliance

Page 17: Active Alerts Use Cases Presentation

17

Benefits – pro-active support

Pro-active approach to problem resolution

Immediate directing of problems to appropriate person

Help reduce affect on the business

Ability to introduce additional automatic alerts for tighter control

Work better within Service Level Agreements

A pro-active process which can be available on a 24 x 7 basis

Page 18: Active Alerts Use Cases Presentation

18

Benefits – support during change

Better ability to support business change

Examples:

The business process has changed

In parallel with data migration

In Parallel with data cleansing

Pre go-live testing

Go-live

Introduction of new modifications involving data updates

New business entities coming on stream

New product launch

New application go-live

Migration to ERP ECC6

Any other system changes

Page 19: Active Alerts Use Cases Presentation

19

Benefits – IT dept

IT function can become more pro-active means less re-action / fire-fighting

IT can be become aware of issue before the business is aware

Ability to tackle problems earlier / sooner

Call-to-action auto routed to appropriate person – so opportunity to balance the load on individuals.

Also allows problem to be resolved faster (by having the correct person involved)

Option to increase / reduce number of checks to reflect the level of business change

Page 20: Active Alerts Use Cases Presentation

20

From this

Page 21: Active Alerts Use Cases Presentation

21

To this

Page 22: Active Alerts Use Cases Presentation

22

Another similar & popular tool

What are the benefits of having a smoke detector & alarm?

Page 23: Active Alerts Use Cases Presentation

23

In the press

Page 24: Active Alerts Use Cases Presentation

24

Minola Technology An SAP Mobile Apps & ABAP partner

Thank you

SAP Mobile App

Active Alerts