1

Process Observer is a component in the SAP Business Suite Foundationlayer that can be used to monitor and analyze their built-in processes ofSAP Business Suite, like Order-to-Cash or Procure-to-Pay, Payment etc. .

2

Managing business change and business automation are importantrequirements in today‘s world.Our customers want to manage and monitor business processes along thelifecycle, and seamless across Business Networks and across SAP andnon-SAP applications.

3

The value proposition of Process Observer is to:

Gain full Process Visibility, enablingReal-time Monitoring including exception & error handlingBusiness Activity Monitoring & SLA TrackingTransparency on process quality

Insight-to-action take action as soon as issues show upon the horizon

Enhanced Process Automation

Process Optimization allow to differentiate bystrengthening operations through continuous processimprovements

4

In the Business Suite we find two kinds of processes:

Modeled Process for process extensions and built-in for SAP standard deliveredprocesses, the “applications” (Business Suite)

Modeled ProcessProcess engine executes processes according to processdefinitions

Built-in ProcessBusiness logic executed without use of an explicit processengineCollaboration treated as built-in process since activities ofdifferent actors are driving

Built-in processes make up 95% of delivered Business Suitefunctionality

The typical implemented end-to-end process is a mixture ofboth orchestration types

5

High-Level Concept of Process Observer

The execution of Business Process Activities is exposed via events‘Process Observer’correlates the events into local processes andcalculates KPIsLocal storage of local processes and their KPIs in a local “Process Log”A federated process log provides end-to-end Process Visibility,Monitoring and Analytics

A note on events: Technically events that are supported are the so-called„BOR“-events; BOR is the business object repository, which is used for SAPBusiness Workflow (BWF), but also in other areas. SAP provides a largenumber of BOR objects like „sales order“ and „business partner“ and therelated events. There are more than 7000 of these BOR events available inthe core Suite applications. Additionally many generic frameworks are BOR-enabled, i.e. they can throw BOR-events if customized accordingly. Thisincludes the change documents used in SD and related areas. See belowfor details on events and change documents.

6

- Processes are defined as a composition of process activities.- Process activities are bound to tasks which represent a reusable sets of

actions/activities executed in an application.- The application uses detectable events to inform about the execution

actions/activities on the level of the (conceptional) Business Objects.

7

- Processes are defined as aggreations of process activities. Usetransaction POC_MODEL to define processes, POC_VIEWER to viewprocess definitions.

- Process start and end activities can be marked- KPIs (counters, cycle types, classification values) and status can be

assigned to a process- Thresholds can be assigned to KPIs in order to trigger alerts and

notifications- Process definitions can be versioned- Best-practise order of execution can be attached for a graphical

representation of the process

8

- Tasks are defined as a combination of business object type and thecorresponding task type ( = action like Create, Approve, Release, …).Use transation POC_FACADE to define tasks.

- Tasks are predelivered and can be custom defined.- Tasks can be defined on header and on item level.

9

Process KPIs, also called “PPIs”, are calculated locally duringRuntime by Process Observer. Aggregated KPIs like averagesare calculated by BW, ODPs or HANA.Thresholds are used to trigger actions.

IndicatorIs a measurable quantity

EvaluationIs associated with and assesses indicator valuesIts scope will be defined depending on the business perspectiveTargets, classifications, ranges, benchmarks, thresholds

ActionViolation of objectives defined in assessments requires specificactions to be taken

10

This maps BOR events from the application to the tasks; thus a connection from application event to processdefinition is given via the task.Note: tasks do not necessarily have to be mapped to BOR events. When using the direct event interface forProcess Observer, application can directly raise events as tasks.

You can maintain the BOR instrumentation by using Transaction ‘POC_CUSTOMIZING’ and navigating to ‘GENERAL SETTINGS BUSINESS OBJECT REPOSITORY INSTRUMENTATION’Navigate to ‘Maintain BOR Instrumentation’ or use transaction POC_BOR.- Here map the Business Object with its corresponding BOR event. E.g. the Sales order business

object (114) is mapped to BOR object (BUS2032)- Map the BOR events to the tasks. E.g. The SO BOR(2032) is mapped to tasks ‘CREATED’ and‘CHANGED’

- The same is supported for events that are modeled using ABAP classes rather than BOR.Note that this does not cover any ABAP event raised using the ABAP statement RAISE EVENT, butonly those events that are supported by the event runtime, similar to BOR events.

Multiple assignments are possible. This may lead to unexpected results, at least for visualization.

Note that to find out what BOR events are raised by you application during execution you can use transactionDisplay Event Trace (SWEL) to trace BOR events. You need to activate the trace in SWEL or using SwitchEvent Trace On/Off (SWELS).

Initially the main instrumentation of the process observer is through BOR events. A large number of BORevents exist, about 7.000 in the Business Suite.What we call “BOR events” are, accurately named, “BOR event types”; but since the BOR currently calls the“event types” “events” most of the time, we are using here the terminology as used in BOR and associateddocumentation; it should be clear from the content when “types” of events are referred to and when“instances”.In SAP SCM 7.0 events 548, BOR-objects with events: 165; in SAP CRM 7.0 events 1.343; BOR-objects withevents: 303; in SAP SRM 7.0 events 830; BOR-objects with events: 188; in SAP ERP EHP4 events 4.223;BOR-objects with events: 1.007.

11

The same as for BOR events applies to IF_workflow events (class-based events).Complete Guide for Events in Workflows in SAP ECC 6.0:http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e038cc2d-0cde-2a10-e28e-f50025578112

11

Create the event linkage in SWEC.

This will lead to the event being raised whenever the change document is created.

You can restrict the event raised by the change document to be raised only conditionally.Call the Field Restrictions to limit and call the Condition Editor and enter the condition. Itis possible to create complex rules looking at multiple fields and their values.

Rules may take some runtime, but since this is executed in background this will notaffect dialog performance, unless there is a large number of change documents toprocess within a given period of time.

12

The Direct Event-API for Process Observer can be called remotely via synchrounousRFC call. Internally this is a simple function module call, or method call.A table of events lt_event is created and used as input to the RFC module.A single event contains information about the event (task) type, the business object (typeand id), the callable business entity (e.g. transaction), user, execution date and time, andlogical system.For federation across systems the kernel transaction ID should be added to the event.Document flow information should be given in the form of predecessor object informationto the event. This information is used to create the process instance chain in the processlog.After the execution of the function module, the events are stored in a buffer table and areprocessed asynchronously.

The creation of events is normally done in customer exits of BAdI methods that are calledin update task where the changes of the underlying BO are posted to the system.

For using the RFC module in systems not containing process observer, see note1737693.

13

Design time:The Process Repository contains information about known events andBusiness Objects of the application, represented by the “facade“, and“process definitions“. Process definitions are simple lists of activities thatmay occur in the process, no specific ordering is required. KPIs may beassigned to the process definitions. Process definitions are required tomonitor processes in Process Observer.

Runtime:- A user executes an activity in the system. This could also be somethingcalleed from another program, e.g. a service, BAPI/RFC etc.- The application raises a BOR-event (or something similar supported byProcess Observer). This is captured by Process Observer, and mappedagains a process model. One or many activities are determined- The activity is mapped to a process instance and stored in the process log- The process log data is available for monitoring through APIs- Process log data is also available for analytics

14

- The process log is created near realtime using background jobprocessing.

- The process log contains „Processes“ as own entities with additionalinformation as futher basis for process related monitoring and analysis.

- KPIs and their evaluations are directly calculated during runtime.

15

- You can navigate from the application directly to the process manitor (via GenericObject Services)

- The process monitor gives you the log of the execution, the KPI values. Thresholdviolations are indicated.

- The process diagram shows the mapping of the process progress to the predefinedprocess definition.

16

Process Observer detects the violation of predefined thresholds. Thresholdscan be set for process definitions, or for individual processes using BRFplusrules. Following the violation, a BOR event is thrown indicating the violatingprocess. The BOR event can be used to trigger automated reactions likelaunching a workflow, calling a service or sending an event to NW BPM, orcontacting a person using email, SMS, etc. using the alert management(ALM, BC-SRV-GBT-ALM), which is provided as part of the SAP WebApplication Server.For more details seehttp://scn.sap.com/community/bpm/blog/2012/08/21/using-thresholds-and-alerting-in-process-observer-pob

17

Through the direct event API, systems that do not have Process Observerlocally available, here called “client systems“, can participate.This may be non-SAP systems or SAP systems of lower releases or SAPsystems where for some reason Process Observer is not set up.Also application that are not sending BOR events can use this Event APIinternally.This requires the external system to provide the events. For SAP some bestpractices how to do that exist (see MDG example).The process log is available in the Suite system and only in local (to theSuite) UIs.Limitations of this approach are obviously availability of events in the clientsystems and overall performance considerations; even though the API iscapable of bundling, volume may be a limiting factor.

18

BRFplus Integration Points:- Customer-defined Process Status additional to System Status- Binding of Task to Activity (e.g. whether the event should be logged with definition A ordefiniton B)- Calculation of Classification KPI- Threshold Calculations

The BRFplus functions are delivered with application POC_SAP_BRF_APP.Custom BRFplus rulesets are part of application POC_SAP_BRF_CUST_APP.Application POC_SAP_BRF_CUST_APP may need to be copied from client 000to the working client.For further information see note 1694459.

How to add a BRFplus Rule in transaction POC_MODEL:- Select entry in the list (if necessary create list entry first!)- Press button ‚Create BRFplus rule‘, then save first before going on. A rule ID shouldnow be visible.

- Press butten ‚Edit BRFplus rule‘

Besides using the BRFplus to create return values for Process Observer, you are alsoable to trigger side effect from BRFplus, for example by calling function modules ortriggering workflows.

As an alternative to the BAdIs you find BAdIs. (not available in all SPs)In releases < SAP_BS_FND 702 you can only use the BAdIs.

19

Exits available during execution are powerful tools. You may:- Enrich event data received from the application, and implement

individual mappings to tasks and processes.- During the logging of process data you may store additional

customer data, or trigger actions using ABAP code.

20

BAdIs for Processing of all Events (red)

BAdI: Enhance/Split Tasks (POC_MAIN_TASK)This Business Add-In (BAdI) is used in the Process Observer (CA-EPT-POC) component.You can use this BAdI to enhance/split tasks.The BAdI is executed before the determination of the process definition or instance takeplace. [Not available in all SPs.]

BAdI: Enrichment of Task Log Data (POC_MAIN_BA_LOG)You can use this BAdI to enrich process log data before it is written to the process log.You can either write additional data to fields you add to the customer includes provided inthe interface structures for the process log, or you can also trigger the update of owntables from this BAdI.

BAdI: Extend Datasources for BW Extraction (RSU5_SAPI_BADI)This Business Add-In (BAdI) is used in the SAP Business Information WarehouseExtractors (BC-BW) component. Using this BAdI you are able to either fill fields with data,or change the content of the DataSource fields that you added to the extract structure of aDataSource as an append structure.

For enhancing ODP, (BAdI BADI_RODPS_DATASOURCE_EXT), seehttp://help.sap.com/saphelp_nw70ehp3/helpdata/en/8a/4121d239094ffebac228e05771cb82/content.htm

In order to use Process Monitoring & Analytics as a solution the followingbuilding blocks are required:- Instrumentation of Applications: the application needs to provide the

required events. Check available BOR events and pre-delivered content- Process Definition: define the activities and KPIs to be observed. You

may check pre-delivered process definitions.- Monitoring & Analytics: Basic Instance Monitoring is directly available in

Process Observer with the Process Monitor. More advanced monitoringand analytics requires the usage of SAP BI or SAP HANA and thecreation of specific dashboards and reports on top using BI Tools likeSAP Dashboards and SAP Lumira.Generic content packages for Process Observer are available for SAPBI with BI Content > 7.x6 and for SAP HANA with SAP Hana Live 1.0SP03 for SAP ERP 6.0 EhP 4.

21

Reuse Views for HANA-based real-time analytics with Process Observerdata are delivered with Suite HANA Live for EhP4 for ERP 1.0 SP03. Thevirtual data models (VDMs) are contained in package sap.hba.eccfnd701.Find the documentationat:http://help.sap.com/saphelp_hba/helpdata/en/51/6ba91eb92a4f4ee10000000a421bc1/content.htm?frameset=/en/D5/BF8F06004C4AA1B26C3B45002F9AD4/frameset.htm

22

Example for the usage of field level changes: Reporting on field changes ofsome key fields of the sales order with Bex Web Analyzer.

23

SAP Dashboards (aka Xcelsius) based on BW, ODP and on HANA allowobservation of processes over time, and the drilldown/filtering of criticalprocesses.Process Observer data can be combined with application data (see lab-preview dashboard on the right side).A sample dashboard is delivered (left side).

24

This diagram shows how Process Observer is integrated into otherbusiness suite components:

The Process Log is the central component to give insight into yourprocesses, but also to trigger follow-up actions.Events about process execution are thrown by SAP or – through an API –by non-SAP applications and stored in the process log. Process loginformation can by accessing through the Process Monitor directly or byquerying via Enterprise Search. From the process monitor you can navigateto the process-related business objects.Light-weight consumption is possible via ODATA/Gateway.Datasources allow the extration to and direct access from BusinessWarehouse. Real-time data access (RDA) is available. Analytics Data isalso available through ODPs. The existing datasources can be used toreplicate process log information to HANA via ETL. Alternatively the processlog tables can be replicated directly using SLT. The report-report interfaceallows navigation between reports, and to backend applications.Additionally, process log content be made available for applications throughsidepanels.

25

Once Process Observer is activated in the system, the Generic ObjectServices (GOS) provide access to the „Process Monitor“ showing allprocess instances related to the business object. Thus the „process“becomes available for the users executing the process.

26

The Process Instance diagram allows quickly monitoring the progress of aprocess with respect to the process definition.

It is available from Business Suite Foundation 7.31 SP08 (ERP 6.0 EhP6SP08) or Business Suite Foundation 7.47 (EhP EhP7)It can also be set up as sidepanel in SAP Business Client, and so be linkedto the Process Monitor, or the normal business applications (e.g. VA03).

Technically this requires the installation of the SAP jNet frontend componenton the display client.

27

Current versions of SAP NWBC support sidepanels for applications. AProcess Observer sidepanel can be attached to the applications, to displayimportant process information (like KPI values and status, related businessobjects and process participants) and to navigate to the process monitor.

28

Current versions of SAP NWBC support sidepanels for applications. Jamintegration, as well as notes & attachment sidepanels work on processinstance level within the process monitor, and with process definitions in theprocess definition viewer.

29

The general idea of the Concept Gateway is to enable the developer, whichusually doesn‘t have the SAP Application expertise, to consume Information fromSAP Backend SystemsThe Concept Gateway builds on standards like ODATA, meaning SAP BackendData are exposed as REST based Services.Consumption Tools supporting the ODATA open standard and the concept of a„service meta document“ can help the developer to understand the Data serviceand support him in building a first skeleton of code that he can refine. Actuallythis concept is available as a product called NW Gateway.

So, we have applied these concepts to build a new Data Service called „ProcessGateway“ as part of the NW Gateway SP04.

One important aspect of that Data service was to build an easy to consumeResource Model that also supports the usual ODATA capabilities like navigatingbetween entities and filtering information.The other important capability of such a Process Gateway Data Service is to beable to connect to different SAP Process Orchestration Infrastructures like a NWBPM or Process Observer enabeld Suite System. That means that the ProcessGateway Data Service not only provide easy access to process information butalso a uniform access.

Resources are part of NW gateway (SP 04).The appropriate backend release to support this is required nevertheless (701SP12, 702 SP 10, 731 SP04).

30

To adopt Process Observer follow these steps:

• Check available application content or RDS provided• Enhance or create Process Definition in the POB Repository• Add missing Events to the application, if necessary• Enhance the Process Log, if necessary• Create spcific analytics content and dashboards for your processes, asrequired

31

The sample process definitions can be reviewed, copied etc. in transactionPOC_MODEL.By default customizing is only available in client 000. Therefore it may berequired to copy it into your working client.You can use the SAP Customizing tools to copy entries from client 000 intoyour working client, see:http://wiki.scn.sap.com/wiki/display/ABAP/SAP+Customizing+Tools+-+frequently+asked+questions

Find more details on the sample process definitions online:- SALES ORDER PROCESS:

http://scn.sap.com/community/bpm/blog/2011/10/07/monitor-sales-order-processing-with-business-process-monitoring-analytics-for-business-suite-processes-pma

- PROCURE_TO_PAY:http://scn.sap.com/community/bpm/blog/2013/07/08/instrumentation-for-procure-to-pay-process-on-item-level-in-process-observer

Further content is planned

32

Procure-to-Pay Instumentation for Process Observer in SCNhttp://scn.sap.com/community/bpm/blog/2013/07/08/instrumentation-for-procure-to-pay-process-on-item-level-in-process-observer

33

34

35

Paul Vahle GmbH & Co KG (The VAHLE Group) is a mid-sized companybased in Kamen, Germany that has specialized in mobile power and datatransmission since 1912.They are active in 52 countries and have 13 subsidiaries worldwide. VAHLEdevelops, manufactures, and installs customized power and datatransmission systems for various material handling applications.

VAHLE implemented the Business Suite Foundation component ProcessObserver together with SAP consulting partner Cubeserv in order to identifybottlenecks and streamline their order-to-cash process run on SAP ERP.The overall deployment time of the Process Observer component took only10 days. The monitoring setup, on top of Process Observer, allowed themto identify gaps in material planning and in stocking processes that wereslowing down product delivery. Appropriate training of business users andconstant evaluation now enables them to deliver faster and make theircustomers happier.

The complete success story is published at:http://www.sap.com/bin/sapcom/en_us/downloadasset.2014-01-jan-07-17.vahle-accelerating-the-order-to-cash-cycle-and-improving-customer-satisfaction-with-sap-erp-and-process-observer-pdf.html

36

Design & AnalysisIdentification of business processesExplicit documentation with process landscapes and business process modelsDesign of performance metricsValidation of models using reviews, discussions, and simulationVerification of formal properties

ConfigurationImplementation of business process models and performance metricsAssignment of responsibilities, Organizational Change ManagementConfiguration of business process management systemsEnrichment of process models with technical aspectsIntegration of applications, data and services, coding

EnactmentPerformance of process instancesand collection of execution dataObservation of progress by process instancesIdentification of exceptions and deviationsProvision of information about conducted tasks, execution time, and resources involvedVerification that process instances run in presence of system modifications

EvaluationIdentification of weaknesses and potentials for improvement by using execution data and comparingwith performance indicatorsAdoption of process mining techniquesInput for succeeding phases

37

Application integration: Ready-to-run integrations of Process Observer into SAP standard processes and applications are provided:The following content for Process Observer (configuration and BAdI), delivered via standard support (SP and note), is currently available:

Basic O2C process instrumentation (see Monitor Sales Order Processing with Process Observer for Built-In Processes (POB))P2P tracking on item level (see Instrumentation for Procure-to-pay process on item level in Process Observer)

Dedicated RDS packages to integrate applications and processes. The following RDS package is currently available :RDS Master Data Governance (see New SAP RDS called SAP MDG Content Accelerator)

Real-time aggregation and analysis of process log information and KPIs is possible via SAP HANA. Therefore, the Process Observer logs arereplicated into SAP HANA via SLT and Virtual Data Models delivered with SAP HANA Live. This makes it possible to report and aggregate overprocess observer log information (see SAP HANA Live for EHP4 for ERP) using BI tools or SAP Smart Business. The new SAP Smart Businessallows it to create personalized and HTML5 dashboards and analyses on top of the HANA views that run on desktop computers as well as on mobiledevices.

For classical analysis using delivered BI content for Process Observer (see BI Content for Process Observer), Process Observer log data is replicatedinto SAP BI via data sources. Custom reports and UIs can be built on top of Process Observer and other application content.

In addition to SAP BI, SAP's partner, Cubeserv, also delivers process dashboards that visualize process observer data graphically and allow furtherprocess analysis (see Process Observer – a new SAP approach to analyze Business Suite processes!).

A specific form of process analysis is the analysis of Process Observer log information via Operational Data Providers (ODPs), which allow theaggregation of data as well as the creation of reports using BI tools in a specific BI client belonging to the backend system itself (see SAP OperationalAnalytics).

For a comparison of BI tools for the frontend that can be combined with SAP BI and SAP HANA to analyze date, please see:http://scn.sap.com/docs/DOC-49350

On SAP HANA, you can further extended Process Observer with SAP Operational Process Intelligence (SAP OPInt) powered by SAP HANA for animproved operational support of your solution for the business end users.

This is especially helpful in cross-system monitoring and the definition of cross-system KPIs on HANA. Operational Process Intelligences also providesan improved 3rd party integration and a number of tools for the improved monitoring and operation of your processes (such as phase and milestoneviews, dashboards, trend & prediction, task management).

Process Mining allows the detection and the analysis of Process Observer log information according to process variants. Currently this is supported byusing external Process Mining tools via the MXML export functionality. A sample report for exporting the log data as MXML is delivered (see ApplyingProcess Mining Techniques to Process Observer Data using the ProM Toolkit). ProM of the Process Mining Group or Fuxicon Disco are example of theexternal products supporting the MXML interface.

While Process Observer delivers more runtime-oriented and performance-oriented information about your processes (process execution history, cycletimes), you may also have Solution Manager-based Business Process Monitoring and Analytics (BPMon/BPA) in your landscape, which focusesmore on monitoring current backlog / issues in your system and comes with a large set of predefined KPIs. For more information about the differentcapabilities and the common usage of the tools, please see Comparison of Business Process Monitoring / Business Process Analytics (BPMon/BPA)and Process Observer (POB).

38

Find more information online:- SAP RDS MDG: http://scn.sap.com/community/mdm/master-data-

governance/blog/2012/10/09/new-sap-rds-called-sap-mdg-content-accelerator

- SAP Process Object Builder:http://help.sap.com/saphelp_pobuilder10/helpdata/en/07/9ee990aab04af9af34cbadedf27333/frameset.htm

- SAP Application Interface Framework: http://scn.sap.com/community/aif

39

MDG supports create and change requests for master data like material orbusiness partner. The initial change is done on the SAP MDG-Hub servertriggerend by a MDG change request workflow. The master data is thendistributed to client systems, where additional workflows can be triggerendand further, client specific data can be maintained.Process Observer can be used to monitor the workflow cross MDG-hub andclients.

MDG instrumentation for Process Observer will be provided with RDS„MDG Content Accelerator“.

40

For details see SCN Blog: Monitoring of cross system workflows with SAPProcess Observer (http://scn.sap.com/community/mdm/master-data-governance/blog/2012/06/11/monitoring-of-cross-system-workflows-with-sap-process-observer)

The graphical sidepanel is also available for other applications.

41

Process Object Builder 1.0 is planned for ramp-up in August 2012. ProcessObjects from Process Object Layer (POL) are instrumented to use ProcessObserver for monitoring. The target is to monitor the entire orchestratedprocess using Process Observer.

42

SAP Application Interface FrameworkA powerful framework for interface implementation, monitoring and errorhandlingA proven solution with more than seven years of development andcustomer historyA cross-industry solution with customers from 25 industries

Interface Implementation (Design Time)Interface implementation mainly through Customizing menusEasy access to relevant data or functions of underlying SAP applicationRe-use of interface components (e.g. checks, mappings, actions)Supports variants of interfaces (exceptions or additional steps)Independent implementation and testing of interface components andinterface variants

Monitoring and Error-Handling (Runtime & Operations)Business user monitoring (power user)Customizable authorizations for interface accessOverview of interface status

43

44

Process Observer provides log data as input to BP Analytics [BPMon] onSAP Solution Manager for further processing.This functionality can be achieved using customer-specific extensions.This functionality is not available in standard as of yet.

45

SAP Dashboards (aka Xcelsius) based on BW, ODP and on HANA allowobservation of processes over time, and the drilldown/filtering of criticalprocesses.Process Observer data can be combined with application data (see lab-preview dashboard on the right side).A sample dashboard is delivered (left side).

46

SAP Partner CubeServ delivers Process Observer dashboards for operational reportingbased on ODP direcly on SAP ERP and strategic reporting based on SAP BI.

47

Today as a business user in finance, sales, procurement … getting theinformation you need at the right time is tough. You have to wait (asopposed to responsive), you use old data (as opposed to real-time), youleverage generic UX (as opposed to one that is adapted to your role),information is provided in multiple places (as opposed to single source oftruth) -> The result is you struggle connecting analysis with execution (asopposed to instant insight to action)This is where Smart Business cockpits come into play. SBc are newcockpits to help you drive your business through fact-based information (vsgut feel). SAP Smart Business cockpits are new cockpits - including tailoredKPIs and graphical visualization – designed for instant insight-action in thecontext of the SAP Business Suite powered by SAP HANA. SAP SmartBusiness cockpits leverage SAP Fiori Design principles for a simplified yetbeautiful UX.

SAP Smart Business Cockpits are:

Responsive: Bringing together transactions and analytics to close thegap between insight and actionPersonalized: Offering personalized role-based tailored KPIs, actionableinsights, news feeds and tasksSeamless: Delivering the same real-time insights and user experienceacross desktops, mobiles and tabletsBeautiful: Delivering the same real-time insights and user experienceacross desktops, mobiles and tablets

48

SAP OPInt 1.0 supports the following business event provider systems• SAP Business Suite Applications (via Business Suite Foundation

Process Observer)• SAP Business Workflow (via Workflow Façade)• SAP NetWeaver Process Orchestration (via BPM Process Façade)Please see appendix for required release/SP levels

Future releases of SAP OPInt will enable you to connect to non-SAPenvironments and scenarios:• SAP NetWeaver Process Integration (Integration Visibility) for 3rd party

business application integration, message flow event integration into abusiness scenario (e.g., a start or end event of a phase) and B2Bconversation events

• SAP NetWeaver Cloud Integration (Cloud Integration Visibility)• Sybase Event Streaming Platform (ESP) for complex event pattern

consumption• SAP Operational Process Intelligence Extensibility (e.g., to build

Non-SAP integration of providers, for instance a social---media adapter)– offering a generic method to implement a non-SAP data model

49

SAP OPInt is especially helpful in cross-system monitoring and thedefinition of cross-system Process KPIs on HANA (which is currently alimitation in Process Observer).

Operational Process Intelligences also provides an improved 3rd partyintegration and a number of tools for the improved monitoring and operationof your processes (such as UI5-based phase and milestone views,dashboards, trend & prediction, task management).

When combining Process Observer with SAP OPInt, you import the processdefinitions from the Process Observer system, and connect them toscenarios in SAP OPInt. You define phases and KPIs directly in SAP OPInt.At runtime process log information is always collected by Process Observer,and – in the side-by-side scenario – replicated in real-time into the SAPOPInt HANA system.

50

Process Observer is delivered with Software Component Business SuiteFoundation (SAP_BS_FND).It is currently available for the software component versions SAP_BS_FND7.01, 7.02, 7.31, 7.46 and 7.47The Business Suite Foundation is part of almost all Business Suite productbased on Web AS ABAP.For details on your products, please consult your System LandscapeDirectory.

51

Information Resources:

Process Observer in SCN (http://scn.sap.com/docs/DOC-24983)Overview page of Process Observer in SCN that contains links torelevant articles, including blog post on how to setup process observerand create first process definitions for logging.Process Observer in SAP Help Portal(http://help.sap.com/erp2005_ehp_06/helpdata/en/33/14dd25b1964c6b8b44cf5b9d757b81/frameset.htm)Application Documentation of Process Observer in SAP Help Portal.BIT605 Process Observer(https://learningportal.wdf.sap.corp/sap(bD1lbiZjPTAwMSZkPW1pbg==)/bc/bsp/sap/z_lso_center/trainingtype.htm?plvar=01&otype=D&objid=70222065 )2-day classroom training (offered by SAP University in Germany, othercountries on request)

52

A selection of Process Observer blog postings in the SCN:

- Introduction http://scn.sap.com/community/bpm/blog/2011/09/05/introducing-new-component-business-process-monitoring-analytics-for-business-suite-processes-pma- Architecture http://scn.sap.com/community/bpm/blog/2011/09/16/architecture-of-business-process-monitoring-analytics-for-business-suite-processes-pmaSetup http://scn.sap.com/community/bpm/blog/2011/09/26/setup-of-component-business-process-monitoring-analytics-for-business-suite-processes-pma- Create Process Definition for Monitoringhttp://scn.sap.com/community/bpm/blog/2011/10/14/create-process-definition-for-business-process-monitoring-analytics-for-business-suite-processes-pma- Direct Event API http://scn.sap.com/community/bpm/blog/2013/06/17/process-observer-pob-direct-event-api-for-logging-processes-from-sap-and-non-sap-systems- Tracking field changes http://scn.sap.com/community/bpm/blog/2013/07/30/tracking-field-changes-using-the-process-observer-pob-direct-event-api- Monitor cross-system workflow http://scn.sap.com/community/mdm/master-data-governance/blog/2012/06/11/monitoring-of-cross-system-workflows-with-sap-process-observer- Thresholds, SLAs and Alerts http://scn.sap.com/community/bpm/blog/2012/08/21/using-thresholds-and-alerting-in-process-observer-pob- Process Mining http://scn.sap.com/community/bpm/blog/2013/08/20/applying-process-mining-techniques-to-process-observer-data-using-the-prom-toolkit

53

Process Observer in Help Portal

Business Function Documentationhttp://help.sap.com/erp2005_ehp_06/helpdata/en/3d/ec3aaca2264acf91e2c95d3450881d/frameset.htm

Application Documentation for Process Observerhttp://help.sap.com/erp2005_ehp_06/helpdata/en/33/14dd25b1964c6b8b44cf5b9d757b81/frameset.htm

BI Content Documentationhttp://help.sap.com/saphelp_nw70ehp2/helpdata/en/c9/3e38a2779b4fb5a6e203301f9d8145/frameset.htm

BI Content Extensionhttp://help.sap.com/saphelp_nw70ehp2/helpdata/en/6a/f247bf0ce745eab5648a309fbd784e/frameset.htm

HANA Livehttp://help.sap.com/saphelp_hba/helpdata/en/51/6ba91eb92a4f4ee10000000a421bc1/content.htm?frameset=/en/D5/BF8F06004C4AA1B26C3B45002F9AD4/frameset.htm

54

55

56

57

58