business process & interface monitoring - archive.sap.com · business process & interface...

94
Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix Functional Overview with ST-SER 700_2008_2 & ST-A/PI 01L*

Upload: buitu

Post on 24-Aug-2019

217 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

Business Process amp InterfaceMonitoringPart 1 ndash Keep Mission Critical BusinessProcesses Running

Part 2 ndash AppendixFunctional Overview withST-SER 700_2008_2 amp ST-API 01L

copy SAP 2009 Business Process amp interface Monitoring Page 2

Overview ndash Business Process Integration ampAutomation Management

Data ConsistencyManagement

Data VolumeManagement

Business Process ampInterface Monitoring

Job SchedulingManagement

Business ProcessPerformance Optimization

Proactively ensure reliablebusiness process flow andthroughput

Optimize business processflow and throughput

Keep data growth ampsize under control

Proactively avoid or detectharmful data inconsistencies

Automate business processwhile considering time andHW restrictions

MRP Run 1000 Billing RunArchiving

MRP Run 2000 ReorganizationBackup

MRP Run 3000Transports

Operations

copy SAP 2009 Business Process amp interface Monitoring Page 3

Business Departments

Operation concept for integration amp automation includingMonitoring objects (alert types threshold values)Error handling proceduresEscalation paths

Functional amp Technical View

Technical View(Process-independent)

Business Process Operations

Functional ViewFunctional process descriptionFunctional process operation and control

IT Infrastructure amp Technical Operations

SystemsOS admin and monitoringDB administrationDB backup und recoveryNetwork monitoringFront-end management

BasismySAP TechnologySystem log monitoringABAP dump analysisPerformance monitoringWorkload monitoring

BusinessProcess

Purpose of Business Process Integration ampAutomation Management

BusinessProcess

copy SAP 2009 Business Process amp interface Monitoring Page 4

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 5

Purpose of Business Process Monitoring

Customer

Distributor

Warehouse

Supplier

Subcontractor

Production

Headquarter

CRMSCMAPO

SRMEBP

WMS

BW

Legacy SystemLegacy System

SAP R3

CRM

Create SalesOrder

SAP ECC

Create SalesOrder

CreateDelivery

Post GoodsIssue

Create ampPrint Invoice

WMS

PerformPicking

Send PickConfirmation

Problem occurs in thesystem landscape

What part of the corebusiness process isaffected

bull Who reactsbull Howbull When is 2nd

level informedbull Who is the

escalationcontact

copy SAP 2009 Business Process amp interface Monitoring Page 6

Why Focus on Business Process Monitoring

Can you answer the following questions for yourOrder to Cash process

How many Sales Orders are open (not or only partially delivered)How many Sales Orders cannot be processed any further becausethey are incomplete have a delivery billing or credit blockHow many outbound deliveries are open (goods issue posting notcomplete)How many picking transfer orders are open (not confirmed) in yourwarehouse management systemHow many outbound deliveries have GI posted but no invoice wascreatedHow many invoices have been created but were not printedHow many sales invoices were not posted to FI

If yes how long does it take to retrieve thisinformation per sales organization plant orwarehouse

copy SAP 2009 Business Process amp interface Monitoring Page 7copy SAP 2008 Business Process amp interface Monitoring Page 7

Why Focus on Business Process MonitoringTechnical Oriented

Can you answer the following questions for yourOrder to Cash process

What is the average response time of transaction VA01 (eg last 20minutes)Did your background job for creating deliveries cancel of finishsuccessfullyHow many inbound IDocs of type DESADV exist which could notposted to an application (error status 51)How many qRFC queues of type R3A are currently blocked andhow many entries do they containDid you receive your flat files (with pricing data) from non-SAPsystems this morning Were they empty or notDid any mapping or routing errors occur in SAP PI which arerelated to your sales processHow many inconsistent objects do you have between your CRMand ERP system

If yes how timely do you get this information andhow much manual effort is needed

copy SAP 2009 Business Process amp interface Monitoring Page 8

Definition of Business Process MonitoringBusiness Process Monitoring is the proactive and process-oriented monitoring of acompanyrsquos core business processesIt includes the observation of all technical and application-related functions that arerequired for a smooth and reliable flow of the core business processes

Goals of Business Process MonitoringDetect problem situations as early as possible in order to solve them as fast aspossible - before they become critical for the businessEnable the customerrsquos Solution Support Organization to respond to and to solveproblems more proactively (ie before end-user call or open trouble tickets)

Business Process Monitoring with SAP SolutionManager

SAP Solution Manager provides the data to answer the questions aboveAutomatically amp triggers auto-reaction methods if necessaryIn a business process contextReady for BI trend analysis

Key message

copy SAP 2009 Business Process amp interface Monitoring Page 9

Why Focus on Business Process Monitoring

Two customer examples

Get Sales Order related data automaticallyOne person spends daily ~4hours collecting information about Sales Orders manually whichhave a delivery or billing block or which are open or incompleteSAP Solution Manager provides this data

Automatically amp triggers auto-reaction methods if necessaryIn a business process contextReady for BI trend analysis

Identify problem situations that stay unnoticed otherwiseSAP Solution Manager identified

Planned Orders that should have been already converted in Process Orders several daysagoConfirmation errors caused by failed goods movements (COGI) for Process Orders thatwere several weeks old

copy SAP 2009 Business Process amp interface Monitoring Page 10

Overview - Business Process Monitoring in theSAP Solution Manager

Solution ManagerService

LevelReporting

Continuous Online Alert Monitoring

BISCM CRMERPSolution Landscape

BI (ad-hoc)Reporting

People

ServiceDeskMessage

SMS

Email

copy SAP 2009 Business Process amp interface Monitoring Page 11

Example Sales Order Management

copy SAP 2009 Business Process amp interface Monitoring Page 12

Example SAP Solution Manager ndash BusinessProcess Level

copy SAP 2009 Business Process amp interface Monitoring Page 13

Example SAP Solution Manager ndash Business Process StepLevel Confirm Picking Transfer Order (TO)

copy SAP 2009 Business Process amp interface Monitoring Page 14

Business Process Step Level Confirm Picking TransferOrder (TO) Detail Report Satellite System

List of 373 openTransfer Orders onsatellite system

copy SAP 2009 Business Process amp interface Monitoring Page 15

BI Standalone Reporting (Dashboard)

Graphical AnalysisGraphical Analysis

Open Transfer Orders MUC

Open Transfer Orders FRA

Transfer Orders Munich Outbound TO items (open)

Transfer Orders Frankfurt Outbound TO items (open)

copy SAP 2009 Business Process amp interface Monitoring Page 16

BI Standalone Reporting (Dashboard)

Tabular AnalysisTabular Analysis

Open TOs MUC

Open TOs FRA

copy SAP 2009 Business Process amp interface Monitoring Page 17

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 18

Business Process AnalysisBusiness Process Monitoring Scoping

ObjectiveProvide insight amp facts about your core businessprocessesProvide scope for possible Business Process Monitoringimplementation

EffortCustomer Effort No customer involvement neededSAP Effort Only 1 manday

Delivery model 100 remote

Applications possibly in ScopeERP Logistics Order to Cash Manufacturing Procure toPay Replenishment Warehouse Management PlantMaintenance as of R3 46CERP Financials as of R3 46C

copy SAP 2009 Business Process amp interface Monitoring Page 19

Throughput and Backlog IndicatorsBenefits (12)

Throughput and Backlog Indicators can help identifyerrorsproblems of different types

Customizing errorsDesign gaps in the business process flowProcess execution in business differs from (global) business process templateErrors in transactional data not corrected in timely mannerCurrent documents not processed fast enoughPotential for data reduction of old business dataMissing end-user trainingIdentification of organizational units (eg plants or warehouses) with thehighest backlog of open business documents

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 2: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 2

Overview ndash Business Process Integration ampAutomation Management

Data ConsistencyManagement

Data VolumeManagement

Business Process ampInterface Monitoring

Job SchedulingManagement

Business ProcessPerformance Optimization

Proactively ensure reliablebusiness process flow andthroughput

Optimize business processflow and throughput

Keep data growth ampsize under control

Proactively avoid or detectharmful data inconsistencies

Automate business processwhile considering time andHW restrictions

MRP Run 1000 Billing RunArchiving

MRP Run 2000 ReorganizationBackup

MRP Run 3000Transports

Operations

copy SAP 2009 Business Process amp interface Monitoring Page 3

Business Departments

Operation concept for integration amp automation includingMonitoring objects (alert types threshold values)Error handling proceduresEscalation paths

Functional amp Technical View

Technical View(Process-independent)

Business Process Operations

Functional ViewFunctional process descriptionFunctional process operation and control

IT Infrastructure amp Technical Operations

SystemsOS admin and monitoringDB administrationDB backup und recoveryNetwork monitoringFront-end management

BasismySAP TechnologySystem log monitoringABAP dump analysisPerformance monitoringWorkload monitoring

BusinessProcess

Purpose of Business Process Integration ampAutomation Management

BusinessProcess

copy SAP 2009 Business Process amp interface Monitoring Page 4

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 5

Purpose of Business Process Monitoring

Customer

Distributor

Warehouse

Supplier

Subcontractor

Production

Headquarter

CRMSCMAPO

SRMEBP

WMS

BW

Legacy SystemLegacy System

SAP R3

CRM

Create SalesOrder

SAP ECC

Create SalesOrder

CreateDelivery

Post GoodsIssue

Create ampPrint Invoice

WMS

PerformPicking

Send PickConfirmation

Problem occurs in thesystem landscape

What part of the corebusiness process isaffected

bull Who reactsbull Howbull When is 2nd

level informedbull Who is the

escalationcontact

copy SAP 2009 Business Process amp interface Monitoring Page 6

Why Focus on Business Process Monitoring

Can you answer the following questions for yourOrder to Cash process

How many Sales Orders are open (not or only partially delivered)How many Sales Orders cannot be processed any further becausethey are incomplete have a delivery billing or credit blockHow many outbound deliveries are open (goods issue posting notcomplete)How many picking transfer orders are open (not confirmed) in yourwarehouse management systemHow many outbound deliveries have GI posted but no invoice wascreatedHow many invoices have been created but were not printedHow many sales invoices were not posted to FI

If yes how long does it take to retrieve thisinformation per sales organization plant orwarehouse

copy SAP 2009 Business Process amp interface Monitoring Page 7copy SAP 2008 Business Process amp interface Monitoring Page 7

Why Focus on Business Process MonitoringTechnical Oriented

Can you answer the following questions for yourOrder to Cash process

What is the average response time of transaction VA01 (eg last 20minutes)Did your background job for creating deliveries cancel of finishsuccessfullyHow many inbound IDocs of type DESADV exist which could notposted to an application (error status 51)How many qRFC queues of type R3A are currently blocked andhow many entries do they containDid you receive your flat files (with pricing data) from non-SAPsystems this morning Were they empty or notDid any mapping or routing errors occur in SAP PI which arerelated to your sales processHow many inconsistent objects do you have between your CRMand ERP system

If yes how timely do you get this information andhow much manual effort is needed

copy SAP 2009 Business Process amp interface Monitoring Page 8

Definition of Business Process MonitoringBusiness Process Monitoring is the proactive and process-oriented monitoring of acompanyrsquos core business processesIt includes the observation of all technical and application-related functions that arerequired for a smooth and reliable flow of the core business processes

Goals of Business Process MonitoringDetect problem situations as early as possible in order to solve them as fast aspossible - before they become critical for the businessEnable the customerrsquos Solution Support Organization to respond to and to solveproblems more proactively (ie before end-user call or open trouble tickets)

Business Process Monitoring with SAP SolutionManager

SAP Solution Manager provides the data to answer the questions aboveAutomatically amp triggers auto-reaction methods if necessaryIn a business process contextReady for BI trend analysis

Key message

copy SAP 2009 Business Process amp interface Monitoring Page 9

Why Focus on Business Process Monitoring

Two customer examples

Get Sales Order related data automaticallyOne person spends daily ~4hours collecting information about Sales Orders manually whichhave a delivery or billing block or which are open or incompleteSAP Solution Manager provides this data

Automatically amp triggers auto-reaction methods if necessaryIn a business process contextReady for BI trend analysis

Identify problem situations that stay unnoticed otherwiseSAP Solution Manager identified

Planned Orders that should have been already converted in Process Orders several daysagoConfirmation errors caused by failed goods movements (COGI) for Process Orders thatwere several weeks old

copy SAP 2009 Business Process amp interface Monitoring Page 10

Overview - Business Process Monitoring in theSAP Solution Manager

Solution ManagerService

LevelReporting

Continuous Online Alert Monitoring

BISCM CRMERPSolution Landscape

BI (ad-hoc)Reporting

People

ServiceDeskMessage

SMS

Email

copy SAP 2009 Business Process amp interface Monitoring Page 11

Example Sales Order Management

copy SAP 2009 Business Process amp interface Monitoring Page 12

Example SAP Solution Manager ndash BusinessProcess Level

copy SAP 2009 Business Process amp interface Monitoring Page 13

Example SAP Solution Manager ndash Business Process StepLevel Confirm Picking Transfer Order (TO)

copy SAP 2009 Business Process amp interface Monitoring Page 14

Business Process Step Level Confirm Picking TransferOrder (TO) Detail Report Satellite System

List of 373 openTransfer Orders onsatellite system

copy SAP 2009 Business Process amp interface Monitoring Page 15

BI Standalone Reporting (Dashboard)

Graphical AnalysisGraphical Analysis

Open Transfer Orders MUC

Open Transfer Orders FRA

Transfer Orders Munich Outbound TO items (open)

Transfer Orders Frankfurt Outbound TO items (open)

copy SAP 2009 Business Process amp interface Monitoring Page 16

BI Standalone Reporting (Dashboard)

Tabular AnalysisTabular Analysis

Open TOs MUC

Open TOs FRA

copy SAP 2009 Business Process amp interface Monitoring Page 17

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 18

Business Process AnalysisBusiness Process Monitoring Scoping

ObjectiveProvide insight amp facts about your core businessprocessesProvide scope for possible Business Process Monitoringimplementation

EffortCustomer Effort No customer involvement neededSAP Effort Only 1 manday

Delivery model 100 remote

Applications possibly in ScopeERP Logistics Order to Cash Manufacturing Procure toPay Replenishment Warehouse Management PlantMaintenance as of R3 46CERP Financials as of R3 46C

copy SAP 2009 Business Process amp interface Monitoring Page 19

Throughput and Backlog IndicatorsBenefits (12)

Throughput and Backlog Indicators can help identifyerrorsproblems of different types

Customizing errorsDesign gaps in the business process flowProcess execution in business differs from (global) business process templateErrors in transactional data not corrected in timely mannerCurrent documents not processed fast enoughPotential for data reduction of old business dataMissing end-user trainingIdentification of organizational units (eg plants or warehouses) with thehighest backlog of open business documents

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 3: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 3

Business Departments

Operation concept for integration amp automation includingMonitoring objects (alert types threshold values)Error handling proceduresEscalation paths

Functional amp Technical View

Technical View(Process-independent)

Business Process Operations

Functional ViewFunctional process descriptionFunctional process operation and control

IT Infrastructure amp Technical Operations

SystemsOS admin and monitoringDB administrationDB backup und recoveryNetwork monitoringFront-end management

BasismySAP TechnologySystem log monitoringABAP dump analysisPerformance monitoringWorkload monitoring

BusinessProcess

Purpose of Business Process Integration ampAutomation Management

BusinessProcess

copy SAP 2009 Business Process amp interface Monitoring Page 4

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 5

Purpose of Business Process Monitoring

Customer

Distributor

Warehouse

Supplier

Subcontractor

Production

Headquarter

CRMSCMAPO

SRMEBP

WMS

BW

Legacy SystemLegacy System

SAP R3

CRM

Create SalesOrder

SAP ECC

Create SalesOrder

CreateDelivery

Post GoodsIssue

Create ampPrint Invoice

WMS

PerformPicking

Send PickConfirmation

Problem occurs in thesystem landscape

What part of the corebusiness process isaffected

bull Who reactsbull Howbull When is 2nd

level informedbull Who is the

escalationcontact

copy SAP 2009 Business Process amp interface Monitoring Page 6

Why Focus on Business Process Monitoring

Can you answer the following questions for yourOrder to Cash process

How many Sales Orders are open (not or only partially delivered)How many Sales Orders cannot be processed any further becausethey are incomplete have a delivery billing or credit blockHow many outbound deliveries are open (goods issue posting notcomplete)How many picking transfer orders are open (not confirmed) in yourwarehouse management systemHow many outbound deliveries have GI posted but no invoice wascreatedHow many invoices have been created but were not printedHow many sales invoices were not posted to FI

If yes how long does it take to retrieve thisinformation per sales organization plant orwarehouse

copy SAP 2009 Business Process amp interface Monitoring Page 7copy SAP 2008 Business Process amp interface Monitoring Page 7

Why Focus on Business Process MonitoringTechnical Oriented

Can you answer the following questions for yourOrder to Cash process

What is the average response time of transaction VA01 (eg last 20minutes)Did your background job for creating deliveries cancel of finishsuccessfullyHow many inbound IDocs of type DESADV exist which could notposted to an application (error status 51)How many qRFC queues of type R3A are currently blocked andhow many entries do they containDid you receive your flat files (with pricing data) from non-SAPsystems this morning Were they empty or notDid any mapping or routing errors occur in SAP PI which arerelated to your sales processHow many inconsistent objects do you have between your CRMand ERP system

If yes how timely do you get this information andhow much manual effort is needed

copy SAP 2009 Business Process amp interface Monitoring Page 8

Definition of Business Process MonitoringBusiness Process Monitoring is the proactive and process-oriented monitoring of acompanyrsquos core business processesIt includes the observation of all technical and application-related functions that arerequired for a smooth and reliable flow of the core business processes

Goals of Business Process MonitoringDetect problem situations as early as possible in order to solve them as fast aspossible - before they become critical for the businessEnable the customerrsquos Solution Support Organization to respond to and to solveproblems more proactively (ie before end-user call or open trouble tickets)

Business Process Monitoring with SAP SolutionManager

SAP Solution Manager provides the data to answer the questions aboveAutomatically amp triggers auto-reaction methods if necessaryIn a business process contextReady for BI trend analysis

Key message

copy SAP 2009 Business Process amp interface Monitoring Page 9

Why Focus on Business Process Monitoring

Two customer examples

Get Sales Order related data automaticallyOne person spends daily ~4hours collecting information about Sales Orders manually whichhave a delivery or billing block or which are open or incompleteSAP Solution Manager provides this data

Automatically amp triggers auto-reaction methods if necessaryIn a business process contextReady for BI trend analysis

Identify problem situations that stay unnoticed otherwiseSAP Solution Manager identified

Planned Orders that should have been already converted in Process Orders several daysagoConfirmation errors caused by failed goods movements (COGI) for Process Orders thatwere several weeks old

copy SAP 2009 Business Process amp interface Monitoring Page 10

Overview - Business Process Monitoring in theSAP Solution Manager

Solution ManagerService

LevelReporting

Continuous Online Alert Monitoring

BISCM CRMERPSolution Landscape

BI (ad-hoc)Reporting

People

ServiceDeskMessage

SMS

Email

copy SAP 2009 Business Process amp interface Monitoring Page 11

Example Sales Order Management

copy SAP 2009 Business Process amp interface Monitoring Page 12

Example SAP Solution Manager ndash BusinessProcess Level

copy SAP 2009 Business Process amp interface Monitoring Page 13

Example SAP Solution Manager ndash Business Process StepLevel Confirm Picking Transfer Order (TO)

copy SAP 2009 Business Process amp interface Monitoring Page 14

Business Process Step Level Confirm Picking TransferOrder (TO) Detail Report Satellite System

List of 373 openTransfer Orders onsatellite system

copy SAP 2009 Business Process amp interface Monitoring Page 15

BI Standalone Reporting (Dashboard)

Graphical AnalysisGraphical Analysis

Open Transfer Orders MUC

Open Transfer Orders FRA

Transfer Orders Munich Outbound TO items (open)

Transfer Orders Frankfurt Outbound TO items (open)

copy SAP 2009 Business Process amp interface Monitoring Page 16

BI Standalone Reporting (Dashboard)

Tabular AnalysisTabular Analysis

Open TOs MUC

Open TOs FRA

copy SAP 2009 Business Process amp interface Monitoring Page 17

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 18

Business Process AnalysisBusiness Process Monitoring Scoping

ObjectiveProvide insight amp facts about your core businessprocessesProvide scope for possible Business Process Monitoringimplementation

EffortCustomer Effort No customer involvement neededSAP Effort Only 1 manday

Delivery model 100 remote

Applications possibly in ScopeERP Logistics Order to Cash Manufacturing Procure toPay Replenishment Warehouse Management PlantMaintenance as of R3 46CERP Financials as of R3 46C

copy SAP 2009 Business Process amp interface Monitoring Page 19

Throughput and Backlog IndicatorsBenefits (12)

Throughput and Backlog Indicators can help identifyerrorsproblems of different types

Customizing errorsDesign gaps in the business process flowProcess execution in business differs from (global) business process templateErrors in transactional data not corrected in timely mannerCurrent documents not processed fast enoughPotential for data reduction of old business dataMissing end-user trainingIdentification of organizational units (eg plants or warehouses) with thehighest backlog of open business documents

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 4: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 4

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 5

Purpose of Business Process Monitoring

Customer

Distributor

Warehouse

Supplier

Subcontractor

Production

Headquarter

CRMSCMAPO

SRMEBP

WMS

BW

Legacy SystemLegacy System

SAP R3

CRM

Create SalesOrder

SAP ECC

Create SalesOrder

CreateDelivery

Post GoodsIssue

Create ampPrint Invoice

WMS

PerformPicking

Send PickConfirmation

Problem occurs in thesystem landscape

What part of the corebusiness process isaffected

bull Who reactsbull Howbull When is 2nd

level informedbull Who is the

escalationcontact

copy SAP 2009 Business Process amp interface Monitoring Page 6

Why Focus on Business Process Monitoring

Can you answer the following questions for yourOrder to Cash process

How many Sales Orders are open (not or only partially delivered)How many Sales Orders cannot be processed any further becausethey are incomplete have a delivery billing or credit blockHow many outbound deliveries are open (goods issue posting notcomplete)How many picking transfer orders are open (not confirmed) in yourwarehouse management systemHow many outbound deliveries have GI posted but no invoice wascreatedHow many invoices have been created but were not printedHow many sales invoices were not posted to FI

If yes how long does it take to retrieve thisinformation per sales organization plant orwarehouse

copy SAP 2009 Business Process amp interface Monitoring Page 7copy SAP 2008 Business Process amp interface Monitoring Page 7

Why Focus on Business Process MonitoringTechnical Oriented

Can you answer the following questions for yourOrder to Cash process

What is the average response time of transaction VA01 (eg last 20minutes)Did your background job for creating deliveries cancel of finishsuccessfullyHow many inbound IDocs of type DESADV exist which could notposted to an application (error status 51)How many qRFC queues of type R3A are currently blocked andhow many entries do they containDid you receive your flat files (with pricing data) from non-SAPsystems this morning Were they empty or notDid any mapping or routing errors occur in SAP PI which arerelated to your sales processHow many inconsistent objects do you have between your CRMand ERP system

If yes how timely do you get this information andhow much manual effort is needed

copy SAP 2009 Business Process amp interface Monitoring Page 8

Definition of Business Process MonitoringBusiness Process Monitoring is the proactive and process-oriented monitoring of acompanyrsquos core business processesIt includes the observation of all technical and application-related functions that arerequired for a smooth and reliable flow of the core business processes

Goals of Business Process MonitoringDetect problem situations as early as possible in order to solve them as fast aspossible - before they become critical for the businessEnable the customerrsquos Solution Support Organization to respond to and to solveproblems more proactively (ie before end-user call or open trouble tickets)

Business Process Monitoring with SAP SolutionManager

SAP Solution Manager provides the data to answer the questions aboveAutomatically amp triggers auto-reaction methods if necessaryIn a business process contextReady for BI trend analysis

Key message

copy SAP 2009 Business Process amp interface Monitoring Page 9

Why Focus on Business Process Monitoring

Two customer examples

Get Sales Order related data automaticallyOne person spends daily ~4hours collecting information about Sales Orders manually whichhave a delivery or billing block or which are open or incompleteSAP Solution Manager provides this data

Automatically amp triggers auto-reaction methods if necessaryIn a business process contextReady for BI trend analysis

Identify problem situations that stay unnoticed otherwiseSAP Solution Manager identified

Planned Orders that should have been already converted in Process Orders several daysagoConfirmation errors caused by failed goods movements (COGI) for Process Orders thatwere several weeks old

copy SAP 2009 Business Process amp interface Monitoring Page 10

Overview - Business Process Monitoring in theSAP Solution Manager

Solution ManagerService

LevelReporting

Continuous Online Alert Monitoring

BISCM CRMERPSolution Landscape

BI (ad-hoc)Reporting

People

ServiceDeskMessage

SMS

Email

copy SAP 2009 Business Process amp interface Monitoring Page 11

Example Sales Order Management

copy SAP 2009 Business Process amp interface Monitoring Page 12

Example SAP Solution Manager ndash BusinessProcess Level

copy SAP 2009 Business Process amp interface Monitoring Page 13

Example SAP Solution Manager ndash Business Process StepLevel Confirm Picking Transfer Order (TO)

copy SAP 2009 Business Process amp interface Monitoring Page 14

Business Process Step Level Confirm Picking TransferOrder (TO) Detail Report Satellite System

List of 373 openTransfer Orders onsatellite system

copy SAP 2009 Business Process amp interface Monitoring Page 15

BI Standalone Reporting (Dashboard)

Graphical AnalysisGraphical Analysis

Open Transfer Orders MUC

Open Transfer Orders FRA

Transfer Orders Munich Outbound TO items (open)

Transfer Orders Frankfurt Outbound TO items (open)

copy SAP 2009 Business Process amp interface Monitoring Page 16

BI Standalone Reporting (Dashboard)

Tabular AnalysisTabular Analysis

Open TOs MUC

Open TOs FRA

copy SAP 2009 Business Process amp interface Monitoring Page 17

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 18

Business Process AnalysisBusiness Process Monitoring Scoping

ObjectiveProvide insight amp facts about your core businessprocessesProvide scope for possible Business Process Monitoringimplementation

EffortCustomer Effort No customer involvement neededSAP Effort Only 1 manday

Delivery model 100 remote

Applications possibly in ScopeERP Logistics Order to Cash Manufacturing Procure toPay Replenishment Warehouse Management PlantMaintenance as of R3 46CERP Financials as of R3 46C

copy SAP 2009 Business Process amp interface Monitoring Page 19

Throughput and Backlog IndicatorsBenefits (12)

Throughput and Backlog Indicators can help identifyerrorsproblems of different types

Customizing errorsDesign gaps in the business process flowProcess execution in business differs from (global) business process templateErrors in transactional data not corrected in timely mannerCurrent documents not processed fast enoughPotential for data reduction of old business dataMissing end-user trainingIdentification of organizational units (eg plants or warehouses) with thehighest backlog of open business documents

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 5: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 5

Purpose of Business Process Monitoring

Customer

Distributor

Warehouse

Supplier

Subcontractor

Production

Headquarter

CRMSCMAPO

SRMEBP

WMS

BW

Legacy SystemLegacy System

SAP R3

CRM

Create SalesOrder

SAP ECC

Create SalesOrder

CreateDelivery

Post GoodsIssue

Create ampPrint Invoice

WMS

PerformPicking

Send PickConfirmation

Problem occurs in thesystem landscape

What part of the corebusiness process isaffected

bull Who reactsbull Howbull When is 2nd

level informedbull Who is the

escalationcontact

copy SAP 2009 Business Process amp interface Monitoring Page 6

Why Focus on Business Process Monitoring

Can you answer the following questions for yourOrder to Cash process

How many Sales Orders are open (not or only partially delivered)How many Sales Orders cannot be processed any further becausethey are incomplete have a delivery billing or credit blockHow many outbound deliveries are open (goods issue posting notcomplete)How many picking transfer orders are open (not confirmed) in yourwarehouse management systemHow many outbound deliveries have GI posted but no invoice wascreatedHow many invoices have been created but were not printedHow many sales invoices were not posted to FI

If yes how long does it take to retrieve thisinformation per sales organization plant orwarehouse

copy SAP 2009 Business Process amp interface Monitoring Page 7copy SAP 2008 Business Process amp interface Monitoring Page 7

Why Focus on Business Process MonitoringTechnical Oriented

Can you answer the following questions for yourOrder to Cash process

What is the average response time of transaction VA01 (eg last 20minutes)Did your background job for creating deliveries cancel of finishsuccessfullyHow many inbound IDocs of type DESADV exist which could notposted to an application (error status 51)How many qRFC queues of type R3A are currently blocked andhow many entries do they containDid you receive your flat files (with pricing data) from non-SAPsystems this morning Were they empty or notDid any mapping or routing errors occur in SAP PI which arerelated to your sales processHow many inconsistent objects do you have between your CRMand ERP system

If yes how timely do you get this information andhow much manual effort is needed

copy SAP 2009 Business Process amp interface Monitoring Page 8

Definition of Business Process MonitoringBusiness Process Monitoring is the proactive and process-oriented monitoring of acompanyrsquos core business processesIt includes the observation of all technical and application-related functions that arerequired for a smooth and reliable flow of the core business processes

Goals of Business Process MonitoringDetect problem situations as early as possible in order to solve them as fast aspossible - before they become critical for the businessEnable the customerrsquos Solution Support Organization to respond to and to solveproblems more proactively (ie before end-user call or open trouble tickets)

Business Process Monitoring with SAP SolutionManager

SAP Solution Manager provides the data to answer the questions aboveAutomatically amp triggers auto-reaction methods if necessaryIn a business process contextReady for BI trend analysis

Key message

copy SAP 2009 Business Process amp interface Monitoring Page 9

Why Focus on Business Process Monitoring

Two customer examples

Get Sales Order related data automaticallyOne person spends daily ~4hours collecting information about Sales Orders manually whichhave a delivery or billing block or which are open or incompleteSAP Solution Manager provides this data

Automatically amp triggers auto-reaction methods if necessaryIn a business process contextReady for BI trend analysis

Identify problem situations that stay unnoticed otherwiseSAP Solution Manager identified

Planned Orders that should have been already converted in Process Orders several daysagoConfirmation errors caused by failed goods movements (COGI) for Process Orders thatwere several weeks old

copy SAP 2009 Business Process amp interface Monitoring Page 10

Overview - Business Process Monitoring in theSAP Solution Manager

Solution ManagerService

LevelReporting

Continuous Online Alert Monitoring

BISCM CRMERPSolution Landscape

BI (ad-hoc)Reporting

People

ServiceDeskMessage

SMS

Email

copy SAP 2009 Business Process amp interface Monitoring Page 11

Example Sales Order Management

copy SAP 2009 Business Process amp interface Monitoring Page 12

Example SAP Solution Manager ndash BusinessProcess Level

copy SAP 2009 Business Process amp interface Monitoring Page 13

Example SAP Solution Manager ndash Business Process StepLevel Confirm Picking Transfer Order (TO)

copy SAP 2009 Business Process amp interface Monitoring Page 14

Business Process Step Level Confirm Picking TransferOrder (TO) Detail Report Satellite System

List of 373 openTransfer Orders onsatellite system

copy SAP 2009 Business Process amp interface Monitoring Page 15

BI Standalone Reporting (Dashboard)

Graphical AnalysisGraphical Analysis

Open Transfer Orders MUC

Open Transfer Orders FRA

Transfer Orders Munich Outbound TO items (open)

Transfer Orders Frankfurt Outbound TO items (open)

copy SAP 2009 Business Process amp interface Monitoring Page 16

BI Standalone Reporting (Dashboard)

Tabular AnalysisTabular Analysis

Open TOs MUC

Open TOs FRA

copy SAP 2009 Business Process amp interface Monitoring Page 17

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 18

Business Process AnalysisBusiness Process Monitoring Scoping

ObjectiveProvide insight amp facts about your core businessprocessesProvide scope for possible Business Process Monitoringimplementation

EffortCustomer Effort No customer involvement neededSAP Effort Only 1 manday

Delivery model 100 remote

Applications possibly in ScopeERP Logistics Order to Cash Manufacturing Procure toPay Replenishment Warehouse Management PlantMaintenance as of R3 46CERP Financials as of R3 46C

copy SAP 2009 Business Process amp interface Monitoring Page 19

Throughput and Backlog IndicatorsBenefits (12)

Throughput and Backlog Indicators can help identifyerrorsproblems of different types

Customizing errorsDesign gaps in the business process flowProcess execution in business differs from (global) business process templateErrors in transactional data not corrected in timely mannerCurrent documents not processed fast enoughPotential for data reduction of old business dataMissing end-user trainingIdentification of organizational units (eg plants or warehouses) with thehighest backlog of open business documents

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 6: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 6

Why Focus on Business Process Monitoring

Can you answer the following questions for yourOrder to Cash process

How many Sales Orders are open (not or only partially delivered)How many Sales Orders cannot be processed any further becausethey are incomplete have a delivery billing or credit blockHow many outbound deliveries are open (goods issue posting notcomplete)How many picking transfer orders are open (not confirmed) in yourwarehouse management systemHow many outbound deliveries have GI posted but no invoice wascreatedHow many invoices have been created but were not printedHow many sales invoices were not posted to FI

If yes how long does it take to retrieve thisinformation per sales organization plant orwarehouse

copy SAP 2009 Business Process amp interface Monitoring Page 7copy SAP 2008 Business Process amp interface Monitoring Page 7

Why Focus on Business Process MonitoringTechnical Oriented

Can you answer the following questions for yourOrder to Cash process

What is the average response time of transaction VA01 (eg last 20minutes)Did your background job for creating deliveries cancel of finishsuccessfullyHow many inbound IDocs of type DESADV exist which could notposted to an application (error status 51)How many qRFC queues of type R3A are currently blocked andhow many entries do they containDid you receive your flat files (with pricing data) from non-SAPsystems this morning Were they empty or notDid any mapping or routing errors occur in SAP PI which arerelated to your sales processHow many inconsistent objects do you have between your CRMand ERP system

If yes how timely do you get this information andhow much manual effort is needed

copy SAP 2009 Business Process amp interface Monitoring Page 8

Definition of Business Process MonitoringBusiness Process Monitoring is the proactive and process-oriented monitoring of acompanyrsquos core business processesIt includes the observation of all technical and application-related functions that arerequired for a smooth and reliable flow of the core business processes

Goals of Business Process MonitoringDetect problem situations as early as possible in order to solve them as fast aspossible - before they become critical for the businessEnable the customerrsquos Solution Support Organization to respond to and to solveproblems more proactively (ie before end-user call or open trouble tickets)

Business Process Monitoring with SAP SolutionManager

SAP Solution Manager provides the data to answer the questions aboveAutomatically amp triggers auto-reaction methods if necessaryIn a business process contextReady for BI trend analysis

Key message

copy SAP 2009 Business Process amp interface Monitoring Page 9

Why Focus on Business Process Monitoring

Two customer examples

Get Sales Order related data automaticallyOne person spends daily ~4hours collecting information about Sales Orders manually whichhave a delivery or billing block or which are open or incompleteSAP Solution Manager provides this data

Automatically amp triggers auto-reaction methods if necessaryIn a business process contextReady for BI trend analysis

Identify problem situations that stay unnoticed otherwiseSAP Solution Manager identified

Planned Orders that should have been already converted in Process Orders several daysagoConfirmation errors caused by failed goods movements (COGI) for Process Orders thatwere several weeks old

copy SAP 2009 Business Process amp interface Monitoring Page 10

Overview - Business Process Monitoring in theSAP Solution Manager

Solution ManagerService

LevelReporting

Continuous Online Alert Monitoring

BISCM CRMERPSolution Landscape

BI (ad-hoc)Reporting

People

ServiceDeskMessage

SMS

Email

copy SAP 2009 Business Process amp interface Monitoring Page 11

Example Sales Order Management

copy SAP 2009 Business Process amp interface Monitoring Page 12

Example SAP Solution Manager ndash BusinessProcess Level

copy SAP 2009 Business Process amp interface Monitoring Page 13

Example SAP Solution Manager ndash Business Process StepLevel Confirm Picking Transfer Order (TO)

copy SAP 2009 Business Process amp interface Monitoring Page 14

Business Process Step Level Confirm Picking TransferOrder (TO) Detail Report Satellite System

List of 373 openTransfer Orders onsatellite system

copy SAP 2009 Business Process amp interface Monitoring Page 15

BI Standalone Reporting (Dashboard)

Graphical AnalysisGraphical Analysis

Open Transfer Orders MUC

Open Transfer Orders FRA

Transfer Orders Munich Outbound TO items (open)

Transfer Orders Frankfurt Outbound TO items (open)

copy SAP 2009 Business Process amp interface Monitoring Page 16

BI Standalone Reporting (Dashboard)

Tabular AnalysisTabular Analysis

Open TOs MUC

Open TOs FRA

copy SAP 2009 Business Process amp interface Monitoring Page 17

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 18

Business Process AnalysisBusiness Process Monitoring Scoping

ObjectiveProvide insight amp facts about your core businessprocessesProvide scope for possible Business Process Monitoringimplementation

EffortCustomer Effort No customer involvement neededSAP Effort Only 1 manday

Delivery model 100 remote

Applications possibly in ScopeERP Logistics Order to Cash Manufacturing Procure toPay Replenishment Warehouse Management PlantMaintenance as of R3 46CERP Financials as of R3 46C

copy SAP 2009 Business Process amp interface Monitoring Page 19

Throughput and Backlog IndicatorsBenefits (12)

Throughput and Backlog Indicators can help identifyerrorsproblems of different types

Customizing errorsDesign gaps in the business process flowProcess execution in business differs from (global) business process templateErrors in transactional data not corrected in timely mannerCurrent documents not processed fast enoughPotential for data reduction of old business dataMissing end-user trainingIdentification of organizational units (eg plants or warehouses) with thehighest backlog of open business documents

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 7: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 7copy SAP 2008 Business Process amp interface Monitoring Page 7

Why Focus on Business Process MonitoringTechnical Oriented

Can you answer the following questions for yourOrder to Cash process

What is the average response time of transaction VA01 (eg last 20minutes)Did your background job for creating deliveries cancel of finishsuccessfullyHow many inbound IDocs of type DESADV exist which could notposted to an application (error status 51)How many qRFC queues of type R3A are currently blocked andhow many entries do they containDid you receive your flat files (with pricing data) from non-SAPsystems this morning Were they empty or notDid any mapping or routing errors occur in SAP PI which arerelated to your sales processHow many inconsistent objects do you have between your CRMand ERP system

If yes how timely do you get this information andhow much manual effort is needed

copy SAP 2009 Business Process amp interface Monitoring Page 8

Definition of Business Process MonitoringBusiness Process Monitoring is the proactive and process-oriented monitoring of acompanyrsquos core business processesIt includes the observation of all technical and application-related functions that arerequired for a smooth and reliable flow of the core business processes

Goals of Business Process MonitoringDetect problem situations as early as possible in order to solve them as fast aspossible - before they become critical for the businessEnable the customerrsquos Solution Support Organization to respond to and to solveproblems more proactively (ie before end-user call or open trouble tickets)

Business Process Monitoring with SAP SolutionManager

SAP Solution Manager provides the data to answer the questions aboveAutomatically amp triggers auto-reaction methods if necessaryIn a business process contextReady for BI trend analysis

Key message

copy SAP 2009 Business Process amp interface Monitoring Page 9

Why Focus on Business Process Monitoring

Two customer examples

Get Sales Order related data automaticallyOne person spends daily ~4hours collecting information about Sales Orders manually whichhave a delivery or billing block or which are open or incompleteSAP Solution Manager provides this data

Automatically amp triggers auto-reaction methods if necessaryIn a business process contextReady for BI trend analysis

Identify problem situations that stay unnoticed otherwiseSAP Solution Manager identified

Planned Orders that should have been already converted in Process Orders several daysagoConfirmation errors caused by failed goods movements (COGI) for Process Orders thatwere several weeks old

copy SAP 2009 Business Process amp interface Monitoring Page 10

Overview - Business Process Monitoring in theSAP Solution Manager

Solution ManagerService

LevelReporting

Continuous Online Alert Monitoring

BISCM CRMERPSolution Landscape

BI (ad-hoc)Reporting

People

ServiceDeskMessage

SMS

Email

copy SAP 2009 Business Process amp interface Monitoring Page 11

Example Sales Order Management

copy SAP 2009 Business Process amp interface Monitoring Page 12

Example SAP Solution Manager ndash BusinessProcess Level

copy SAP 2009 Business Process amp interface Monitoring Page 13

Example SAP Solution Manager ndash Business Process StepLevel Confirm Picking Transfer Order (TO)

copy SAP 2009 Business Process amp interface Monitoring Page 14

Business Process Step Level Confirm Picking TransferOrder (TO) Detail Report Satellite System

List of 373 openTransfer Orders onsatellite system

copy SAP 2009 Business Process amp interface Monitoring Page 15

BI Standalone Reporting (Dashboard)

Graphical AnalysisGraphical Analysis

Open Transfer Orders MUC

Open Transfer Orders FRA

Transfer Orders Munich Outbound TO items (open)

Transfer Orders Frankfurt Outbound TO items (open)

copy SAP 2009 Business Process amp interface Monitoring Page 16

BI Standalone Reporting (Dashboard)

Tabular AnalysisTabular Analysis

Open TOs MUC

Open TOs FRA

copy SAP 2009 Business Process amp interface Monitoring Page 17

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 18

Business Process AnalysisBusiness Process Monitoring Scoping

ObjectiveProvide insight amp facts about your core businessprocessesProvide scope for possible Business Process Monitoringimplementation

EffortCustomer Effort No customer involvement neededSAP Effort Only 1 manday

Delivery model 100 remote

Applications possibly in ScopeERP Logistics Order to Cash Manufacturing Procure toPay Replenishment Warehouse Management PlantMaintenance as of R3 46CERP Financials as of R3 46C

copy SAP 2009 Business Process amp interface Monitoring Page 19

Throughput and Backlog IndicatorsBenefits (12)

Throughput and Backlog Indicators can help identifyerrorsproblems of different types

Customizing errorsDesign gaps in the business process flowProcess execution in business differs from (global) business process templateErrors in transactional data not corrected in timely mannerCurrent documents not processed fast enoughPotential for data reduction of old business dataMissing end-user trainingIdentification of organizational units (eg plants or warehouses) with thehighest backlog of open business documents

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 8: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 8

Definition of Business Process MonitoringBusiness Process Monitoring is the proactive and process-oriented monitoring of acompanyrsquos core business processesIt includes the observation of all technical and application-related functions that arerequired for a smooth and reliable flow of the core business processes

Goals of Business Process MonitoringDetect problem situations as early as possible in order to solve them as fast aspossible - before they become critical for the businessEnable the customerrsquos Solution Support Organization to respond to and to solveproblems more proactively (ie before end-user call or open trouble tickets)

Business Process Monitoring with SAP SolutionManager

SAP Solution Manager provides the data to answer the questions aboveAutomatically amp triggers auto-reaction methods if necessaryIn a business process contextReady for BI trend analysis

Key message

copy SAP 2009 Business Process amp interface Monitoring Page 9

Why Focus on Business Process Monitoring

Two customer examples

Get Sales Order related data automaticallyOne person spends daily ~4hours collecting information about Sales Orders manually whichhave a delivery or billing block or which are open or incompleteSAP Solution Manager provides this data

Automatically amp triggers auto-reaction methods if necessaryIn a business process contextReady for BI trend analysis

Identify problem situations that stay unnoticed otherwiseSAP Solution Manager identified

Planned Orders that should have been already converted in Process Orders several daysagoConfirmation errors caused by failed goods movements (COGI) for Process Orders thatwere several weeks old

copy SAP 2009 Business Process amp interface Monitoring Page 10

Overview - Business Process Monitoring in theSAP Solution Manager

Solution ManagerService

LevelReporting

Continuous Online Alert Monitoring

BISCM CRMERPSolution Landscape

BI (ad-hoc)Reporting

People

ServiceDeskMessage

SMS

Email

copy SAP 2009 Business Process amp interface Monitoring Page 11

Example Sales Order Management

copy SAP 2009 Business Process amp interface Monitoring Page 12

Example SAP Solution Manager ndash BusinessProcess Level

copy SAP 2009 Business Process amp interface Monitoring Page 13

Example SAP Solution Manager ndash Business Process StepLevel Confirm Picking Transfer Order (TO)

copy SAP 2009 Business Process amp interface Monitoring Page 14

Business Process Step Level Confirm Picking TransferOrder (TO) Detail Report Satellite System

List of 373 openTransfer Orders onsatellite system

copy SAP 2009 Business Process amp interface Monitoring Page 15

BI Standalone Reporting (Dashboard)

Graphical AnalysisGraphical Analysis

Open Transfer Orders MUC

Open Transfer Orders FRA

Transfer Orders Munich Outbound TO items (open)

Transfer Orders Frankfurt Outbound TO items (open)

copy SAP 2009 Business Process amp interface Monitoring Page 16

BI Standalone Reporting (Dashboard)

Tabular AnalysisTabular Analysis

Open TOs MUC

Open TOs FRA

copy SAP 2009 Business Process amp interface Monitoring Page 17

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 18

Business Process AnalysisBusiness Process Monitoring Scoping

ObjectiveProvide insight amp facts about your core businessprocessesProvide scope for possible Business Process Monitoringimplementation

EffortCustomer Effort No customer involvement neededSAP Effort Only 1 manday

Delivery model 100 remote

Applications possibly in ScopeERP Logistics Order to Cash Manufacturing Procure toPay Replenishment Warehouse Management PlantMaintenance as of R3 46CERP Financials as of R3 46C

copy SAP 2009 Business Process amp interface Monitoring Page 19

Throughput and Backlog IndicatorsBenefits (12)

Throughput and Backlog Indicators can help identifyerrorsproblems of different types

Customizing errorsDesign gaps in the business process flowProcess execution in business differs from (global) business process templateErrors in transactional data not corrected in timely mannerCurrent documents not processed fast enoughPotential for data reduction of old business dataMissing end-user trainingIdentification of organizational units (eg plants or warehouses) with thehighest backlog of open business documents

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 9: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 9

Why Focus on Business Process Monitoring

Two customer examples

Get Sales Order related data automaticallyOne person spends daily ~4hours collecting information about Sales Orders manually whichhave a delivery or billing block or which are open or incompleteSAP Solution Manager provides this data

Automatically amp triggers auto-reaction methods if necessaryIn a business process contextReady for BI trend analysis

Identify problem situations that stay unnoticed otherwiseSAP Solution Manager identified

Planned Orders that should have been already converted in Process Orders several daysagoConfirmation errors caused by failed goods movements (COGI) for Process Orders thatwere several weeks old

copy SAP 2009 Business Process amp interface Monitoring Page 10

Overview - Business Process Monitoring in theSAP Solution Manager

Solution ManagerService

LevelReporting

Continuous Online Alert Monitoring

BISCM CRMERPSolution Landscape

BI (ad-hoc)Reporting

People

ServiceDeskMessage

SMS

Email

copy SAP 2009 Business Process amp interface Monitoring Page 11

Example Sales Order Management

copy SAP 2009 Business Process amp interface Monitoring Page 12

Example SAP Solution Manager ndash BusinessProcess Level

copy SAP 2009 Business Process amp interface Monitoring Page 13

Example SAP Solution Manager ndash Business Process StepLevel Confirm Picking Transfer Order (TO)

copy SAP 2009 Business Process amp interface Monitoring Page 14

Business Process Step Level Confirm Picking TransferOrder (TO) Detail Report Satellite System

List of 373 openTransfer Orders onsatellite system

copy SAP 2009 Business Process amp interface Monitoring Page 15

BI Standalone Reporting (Dashboard)

Graphical AnalysisGraphical Analysis

Open Transfer Orders MUC

Open Transfer Orders FRA

Transfer Orders Munich Outbound TO items (open)

Transfer Orders Frankfurt Outbound TO items (open)

copy SAP 2009 Business Process amp interface Monitoring Page 16

BI Standalone Reporting (Dashboard)

Tabular AnalysisTabular Analysis

Open TOs MUC

Open TOs FRA

copy SAP 2009 Business Process amp interface Monitoring Page 17

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 18

Business Process AnalysisBusiness Process Monitoring Scoping

ObjectiveProvide insight amp facts about your core businessprocessesProvide scope for possible Business Process Monitoringimplementation

EffortCustomer Effort No customer involvement neededSAP Effort Only 1 manday

Delivery model 100 remote

Applications possibly in ScopeERP Logistics Order to Cash Manufacturing Procure toPay Replenishment Warehouse Management PlantMaintenance as of R3 46CERP Financials as of R3 46C

copy SAP 2009 Business Process amp interface Monitoring Page 19

Throughput and Backlog IndicatorsBenefits (12)

Throughput and Backlog Indicators can help identifyerrorsproblems of different types

Customizing errorsDesign gaps in the business process flowProcess execution in business differs from (global) business process templateErrors in transactional data not corrected in timely mannerCurrent documents not processed fast enoughPotential for data reduction of old business dataMissing end-user trainingIdentification of organizational units (eg plants or warehouses) with thehighest backlog of open business documents

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 10: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 10

Overview - Business Process Monitoring in theSAP Solution Manager

Solution ManagerService

LevelReporting

Continuous Online Alert Monitoring

BISCM CRMERPSolution Landscape

BI (ad-hoc)Reporting

People

ServiceDeskMessage

SMS

Email

copy SAP 2009 Business Process amp interface Monitoring Page 11

Example Sales Order Management

copy SAP 2009 Business Process amp interface Monitoring Page 12

Example SAP Solution Manager ndash BusinessProcess Level

copy SAP 2009 Business Process amp interface Monitoring Page 13

Example SAP Solution Manager ndash Business Process StepLevel Confirm Picking Transfer Order (TO)

copy SAP 2009 Business Process amp interface Monitoring Page 14

Business Process Step Level Confirm Picking TransferOrder (TO) Detail Report Satellite System

List of 373 openTransfer Orders onsatellite system

copy SAP 2009 Business Process amp interface Monitoring Page 15

BI Standalone Reporting (Dashboard)

Graphical AnalysisGraphical Analysis

Open Transfer Orders MUC

Open Transfer Orders FRA

Transfer Orders Munich Outbound TO items (open)

Transfer Orders Frankfurt Outbound TO items (open)

copy SAP 2009 Business Process amp interface Monitoring Page 16

BI Standalone Reporting (Dashboard)

Tabular AnalysisTabular Analysis

Open TOs MUC

Open TOs FRA

copy SAP 2009 Business Process amp interface Monitoring Page 17

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 18

Business Process AnalysisBusiness Process Monitoring Scoping

ObjectiveProvide insight amp facts about your core businessprocessesProvide scope for possible Business Process Monitoringimplementation

EffortCustomer Effort No customer involvement neededSAP Effort Only 1 manday

Delivery model 100 remote

Applications possibly in ScopeERP Logistics Order to Cash Manufacturing Procure toPay Replenishment Warehouse Management PlantMaintenance as of R3 46CERP Financials as of R3 46C

copy SAP 2009 Business Process amp interface Monitoring Page 19

Throughput and Backlog IndicatorsBenefits (12)

Throughput and Backlog Indicators can help identifyerrorsproblems of different types

Customizing errorsDesign gaps in the business process flowProcess execution in business differs from (global) business process templateErrors in transactional data not corrected in timely mannerCurrent documents not processed fast enoughPotential for data reduction of old business dataMissing end-user trainingIdentification of organizational units (eg plants or warehouses) with thehighest backlog of open business documents

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 11: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 11

Example Sales Order Management

copy SAP 2009 Business Process amp interface Monitoring Page 12

Example SAP Solution Manager ndash BusinessProcess Level

copy SAP 2009 Business Process amp interface Monitoring Page 13

Example SAP Solution Manager ndash Business Process StepLevel Confirm Picking Transfer Order (TO)

copy SAP 2009 Business Process amp interface Monitoring Page 14

Business Process Step Level Confirm Picking TransferOrder (TO) Detail Report Satellite System

List of 373 openTransfer Orders onsatellite system

copy SAP 2009 Business Process amp interface Monitoring Page 15

BI Standalone Reporting (Dashboard)

Graphical AnalysisGraphical Analysis

Open Transfer Orders MUC

Open Transfer Orders FRA

Transfer Orders Munich Outbound TO items (open)

Transfer Orders Frankfurt Outbound TO items (open)

copy SAP 2009 Business Process amp interface Monitoring Page 16

BI Standalone Reporting (Dashboard)

Tabular AnalysisTabular Analysis

Open TOs MUC

Open TOs FRA

copy SAP 2009 Business Process amp interface Monitoring Page 17

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 18

Business Process AnalysisBusiness Process Monitoring Scoping

ObjectiveProvide insight amp facts about your core businessprocessesProvide scope for possible Business Process Monitoringimplementation

EffortCustomer Effort No customer involvement neededSAP Effort Only 1 manday

Delivery model 100 remote

Applications possibly in ScopeERP Logistics Order to Cash Manufacturing Procure toPay Replenishment Warehouse Management PlantMaintenance as of R3 46CERP Financials as of R3 46C

copy SAP 2009 Business Process amp interface Monitoring Page 19

Throughput and Backlog IndicatorsBenefits (12)

Throughput and Backlog Indicators can help identifyerrorsproblems of different types

Customizing errorsDesign gaps in the business process flowProcess execution in business differs from (global) business process templateErrors in transactional data not corrected in timely mannerCurrent documents not processed fast enoughPotential for data reduction of old business dataMissing end-user trainingIdentification of organizational units (eg plants or warehouses) with thehighest backlog of open business documents

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 12: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 12

Example SAP Solution Manager ndash BusinessProcess Level

copy SAP 2009 Business Process amp interface Monitoring Page 13

Example SAP Solution Manager ndash Business Process StepLevel Confirm Picking Transfer Order (TO)

copy SAP 2009 Business Process amp interface Monitoring Page 14

Business Process Step Level Confirm Picking TransferOrder (TO) Detail Report Satellite System

List of 373 openTransfer Orders onsatellite system

copy SAP 2009 Business Process amp interface Monitoring Page 15

BI Standalone Reporting (Dashboard)

Graphical AnalysisGraphical Analysis

Open Transfer Orders MUC

Open Transfer Orders FRA

Transfer Orders Munich Outbound TO items (open)

Transfer Orders Frankfurt Outbound TO items (open)

copy SAP 2009 Business Process amp interface Monitoring Page 16

BI Standalone Reporting (Dashboard)

Tabular AnalysisTabular Analysis

Open TOs MUC

Open TOs FRA

copy SAP 2009 Business Process amp interface Monitoring Page 17

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 18

Business Process AnalysisBusiness Process Monitoring Scoping

ObjectiveProvide insight amp facts about your core businessprocessesProvide scope for possible Business Process Monitoringimplementation

EffortCustomer Effort No customer involvement neededSAP Effort Only 1 manday

Delivery model 100 remote

Applications possibly in ScopeERP Logistics Order to Cash Manufacturing Procure toPay Replenishment Warehouse Management PlantMaintenance as of R3 46CERP Financials as of R3 46C

copy SAP 2009 Business Process amp interface Monitoring Page 19

Throughput and Backlog IndicatorsBenefits (12)

Throughput and Backlog Indicators can help identifyerrorsproblems of different types

Customizing errorsDesign gaps in the business process flowProcess execution in business differs from (global) business process templateErrors in transactional data not corrected in timely mannerCurrent documents not processed fast enoughPotential for data reduction of old business dataMissing end-user trainingIdentification of organizational units (eg plants or warehouses) with thehighest backlog of open business documents

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 13: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 13

Example SAP Solution Manager ndash Business Process StepLevel Confirm Picking Transfer Order (TO)

copy SAP 2009 Business Process amp interface Monitoring Page 14

Business Process Step Level Confirm Picking TransferOrder (TO) Detail Report Satellite System

List of 373 openTransfer Orders onsatellite system

copy SAP 2009 Business Process amp interface Monitoring Page 15

BI Standalone Reporting (Dashboard)

Graphical AnalysisGraphical Analysis

Open Transfer Orders MUC

Open Transfer Orders FRA

Transfer Orders Munich Outbound TO items (open)

Transfer Orders Frankfurt Outbound TO items (open)

copy SAP 2009 Business Process amp interface Monitoring Page 16

BI Standalone Reporting (Dashboard)

Tabular AnalysisTabular Analysis

Open TOs MUC

Open TOs FRA

copy SAP 2009 Business Process amp interface Monitoring Page 17

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 18

Business Process AnalysisBusiness Process Monitoring Scoping

ObjectiveProvide insight amp facts about your core businessprocessesProvide scope for possible Business Process Monitoringimplementation

EffortCustomer Effort No customer involvement neededSAP Effort Only 1 manday

Delivery model 100 remote

Applications possibly in ScopeERP Logistics Order to Cash Manufacturing Procure toPay Replenishment Warehouse Management PlantMaintenance as of R3 46CERP Financials as of R3 46C

copy SAP 2009 Business Process amp interface Monitoring Page 19

Throughput and Backlog IndicatorsBenefits (12)

Throughput and Backlog Indicators can help identifyerrorsproblems of different types

Customizing errorsDesign gaps in the business process flowProcess execution in business differs from (global) business process templateErrors in transactional data not corrected in timely mannerCurrent documents not processed fast enoughPotential for data reduction of old business dataMissing end-user trainingIdentification of organizational units (eg plants or warehouses) with thehighest backlog of open business documents

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 14: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 14

Business Process Step Level Confirm Picking TransferOrder (TO) Detail Report Satellite System

List of 373 openTransfer Orders onsatellite system

copy SAP 2009 Business Process amp interface Monitoring Page 15

BI Standalone Reporting (Dashboard)

Graphical AnalysisGraphical Analysis

Open Transfer Orders MUC

Open Transfer Orders FRA

Transfer Orders Munich Outbound TO items (open)

Transfer Orders Frankfurt Outbound TO items (open)

copy SAP 2009 Business Process amp interface Monitoring Page 16

BI Standalone Reporting (Dashboard)

Tabular AnalysisTabular Analysis

Open TOs MUC

Open TOs FRA

copy SAP 2009 Business Process amp interface Monitoring Page 17

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 18

Business Process AnalysisBusiness Process Monitoring Scoping

ObjectiveProvide insight amp facts about your core businessprocessesProvide scope for possible Business Process Monitoringimplementation

EffortCustomer Effort No customer involvement neededSAP Effort Only 1 manday

Delivery model 100 remote

Applications possibly in ScopeERP Logistics Order to Cash Manufacturing Procure toPay Replenishment Warehouse Management PlantMaintenance as of R3 46CERP Financials as of R3 46C

copy SAP 2009 Business Process amp interface Monitoring Page 19

Throughput and Backlog IndicatorsBenefits (12)

Throughput and Backlog Indicators can help identifyerrorsproblems of different types

Customizing errorsDesign gaps in the business process flowProcess execution in business differs from (global) business process templateErrors in transactional data not corrected in timely mannerCurrent documents not processed fast enoughPotential for data reduction of old business dataMissing end-user trainingIdentification of organizational units (eg plants or warehouses) with thehighest backlog of open business documents

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 15: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 15

BI Standalone Reporting (Dashboard)

Graphical AnalysisGraphical Analysis

Open Transfer Orders MUC

Open Transfer Orders FRA

Transfer Orders Munich Outbound TO items (open)

Transfer Orders Frankfurt Outbound TO items (open)

copy SAP 2009 Business Process amp interface Monitoring Page 16

BI Standalone Reporting (Dashboard)

Tabular AnalysisTabular Analysis

Open TOs MUC

Open TOs FRA

copy SAP 2009 Business Process amp interface Monitoring Page 17

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 18

Business Process AnalysisBusiness Process Monitoring Scoping

ObjectiveProvide insight amp facts about your core businessprocessesProvide scope for possible Business Process Monitoringimplementation

EffortCustomer Effort No customer involvement neededSAP Effort Only 1 manday

Delivery model 100 remote

Applications possibly in ScopeERP Logistics Order to Cash Manufacturing Procure toPay Replenishment Warehouse Management PlantMaintenance as of R3 46CERP Financials as of R3 46C

copy SAP 2009 Business Process amp interface Monitoring Page 19

Throughput and Backlog IndicatorsBenefits (12)

Throughput and Backlog Indicators can help identifyerrorsproblems of different types

Customizing errorsDesign gaps in the business process flowProcess execution in business differs from (global) business process templateErrors in transactional data not corrected in timely mannerCurrent documents not processed fast enoughPotential for data reduction of old business dataMissing end-user trainingIdentification of organizational units (eg plants or warehouses) with thehighest backlog of open business documents

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 16: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 16

BI Standalone Reporting (Dashboard)

Tabular AnalysisTabular Analysis

Open TOs MUC

Open TOs FRA

copy SAP 2009 Business Process amp interface Monitoring Page 17

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 18

Business Process AnalysisBusiness Process Monitoring Scoping

ObjectiveProvide insight amp facts about your core businessprocessesProvide scope for possible Business Process Monitoringimplementation

EffortCustomer Effort No customer involvement neededSAP Effort Only 1 manday

Delivery model 100 remote

Applications possibly in ScopeERP Logistics Order to Cash Manufacturing Procure toPay Replenishment Warehouse Management PlantMaintenance as of R3 46CERP Financials as of R3 46C

copy SAP 2009 Business Process amp interface Monitoring Page 19

Throughput and Backlog IndicatorsBenefits (12)

Throughput and Backlog Indicators can help identifyerrorsproblems of different types

Customizing errorsDesign gaps in the business process flowProcess execution in business differs from (global) business process templateErrors in transactional data not corrected in timely mannerCurrent documents not processed fast enoughPotential for data reduction of old business dataMissing end-user trainingIdentification of organizational units (eg plants or warehouses) with thehighest backlog of open business documents

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 17: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 17

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 18

Business Process AnalysisBusiness Process Monitoring Scoping

ObjectiveProvide insight amp facts about your core businessprocessesProvide scope for possible Business Process Monitoringimplementation

EffortCustomer Effort No customer involvement neededSAP Effort Only 1 manday

Delivery model 100 remote

Applications possibly in ScopeERP Logistics Order to Cash Manufacturing Procure toPay Replenishment Warehouse Management PlantMaintenance as of R3 46CERP Financials as of R3 46C

copy SAP 2009 Business Process amp interface Monitoring Page 19

Throughput and Backlog IndicatorsBenefits (12)

Throughput and Backlog Indicators can help identifyerrorsproblems of different types

Customizing errorsDesign gaps in the business process flowProcess execution in business differs from (global) business process templateErrors in transactional data not corrected in timely mannerCurrent documents not processed fast enoughPotential for data reduction of old business dataMissing end-user trainingIdentification of organizational units (eg plants or warehouses) with thehighest backlog of open business documents

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 18: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 18

Business Process AnalysisBusiness Process Monitoring Scoping

ObjectiveProvide insight amp facts about your core businessprocessesProvide scope for possible Business Process Monitoringimplementation

EffortCustomer Effort No customer involvement neededSAP Effort Only 1 manday

Delivery model 100 remote

Applications possibly in ScopeERP Logistics Order to Cash Manufacturing Procure toPay Replenishment Warehouse Management PlantMaintenance as of R3 46CERP Financials as of R3 46C

copy SAP 2009 Business Process amp interface Monitoring Page 19

Throughput and Backlog IndicatorsBenefits (12)

Throughput and Backlog Indicators can help identifyerrorsproblems of different types

Customizing errorsDesign gaps in the business process flowProcess execution in business differs from (global) business process templateErrors in transactional data not corrected in timely mannerCurrent documents not processed fast enoughPotential for data reduction of old business dataMissing end-user trainingIdentification of organizational units (eg plants or warehouses) with thehighest backlog of open business documents

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 19: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 19

Throughput and Backlog IndicatorsBenefits (12)

Throughput and Backlog Indicators can help identifyerrorsproblems of different types

Customizing errorsDesign gaps in the business process flowProcess execution in business differs from (global) business process templateErrors in transactional data not corrected in timely mannerCurrent documents not processed fast enoughPotential for data reduction of old business dataMissing end-user trainingIdentification of organizational units (eg plants or warehouses) with thehighest backlog of open business documents

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 20: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 20

Throughput and Backlog IndicatorsBenefits (22)

Value PropositionGain transparency about your core business processesLearn in which organizational areas you

Could speed-up amp streamline your most critical business processesCould improve service levelsMight need to train your end-users to better follow intended proceduresCould improve your daily operations

Automate your daily monitoring tasks (technical amp application related)Support the organizational interface between business amp IT departmentLower Total Cost Of Ownership (TCO)

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 21: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 21

Example Order-to-Cash

of created OutboundDeliveries

Open Outbound Deliveries

of created Sales Orders Sales Orders (GI date in the

past but not delivered)

of posted Invoices Invoices not transferred to

Accounting

OpenOverdue CustomerItems FI-AR

Open Picking TransferOrders

Goods Delivered not Invoiced

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 22: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 22

Order to Cash 873 Sales documents created on28102008

Example

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 23: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 23

Order to Cash Process 3225 Orders withdelayed Delivery

96120 France

453111 Germany

2014380 Italy

BacklogOrders

SalesOrganization

Top 3 Sales Organizations

Okay Warning Critical

Finding3225 Sales Orders with planned Goods Issue date in the past and no delivery was createdyet62 of these outstanding sales orders belong to ItalyOldest entry from April 2003

Business Risk This key figure represents real sales backlog where the expected deliverydate was not met and lies in the past As no delivery is created yet the customer will also notbe delivered within the next 1-2 days This is lost revenue and might lead to bad customersatisfaction or the sales was cancelled and the old document should not be in the system anylonger

Example

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 24: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 24

Order to Cash Process 3225 Orders withdelayed Delivery

Example

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 25: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 25

Example Manufacturing

of Planned Orders notconverted

of Confirmation Errors forGoods Movements

of ProductionProcess Ordersoverdue for release

of ProductionProcess Ordersoverdue for technical closure

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 26: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 26

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

85M001 London

148M025 Paris

2876M021 Berlin

Failed GoodsMovements

ManufacturingPlants

Top 3 Manufacturing Plants

Okay Warning Critical

Finding3244 failed goods movements during Production Order confirmation were found which areolder than 1 day88 of these confirmation problems are related to plant M021 in BerlinOldest entry from March 2006

Business Risk Failed goods movement postings represent an inconsistency between thereal world stock information and the book inventory These errors should be corrected in atimely manner

Example

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 27: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 27

Manufacturing Process 3244 Failed Goods Movementsduring Production Order Confirmation older 1 day

Example

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 28: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 28

Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction amp function code per user pattern)General Application Log (SLG1)Update Errors (Transaction- Program-specific)Document Volumes (based on SAP table statistics)

Interface Monitoring ObjectsqRFC Alert MonitoringBDoc Alert Monitoring (CRM)ALEIDoc Alert Monitoring per IDoc TypeXIPI Alert MonitoringBatch Input MonitoringFile Monitoring

Customer Specific Monitoring ObjectsCustomer Exit in Application Monitoring InfrastructureAll Alert Information available via CCMS Monitoring Infrastructure

tRFC Alert MonitoringWorkflow Monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 29: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 29

Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management

IS ndash UtilitiesIS ndash Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS ndash InsuranceIS ndash Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner amp OptimizerDemand PlanningSupply Network PlanningProduction Planning Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management ndash BCS

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 30: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 30copy SAP 2007 Business Process amp interface Monitoring Page 30

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales amp ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM ndash ECCCRM ndash CDBTrade Promotion ManagementLeasing

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 31: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 31

Starting Point for Business Process andInterface Monitoring concept

Phases of a Software Implementation Project

StrategicFramework

Technicaland IntegrationDesign

Technical andOperations

Implementation

Cutoverand Start ofProduction

Operationsand Continuous

Improvement

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Ideal Starting PointCreation of Monitoring concept started during the ldquoTechnical and Integration Designrdquo phaseof implementation project

Later Starting PointsEstablishing a Business Process and Interface Monitoring concept can be started during alater phase at any time during the productive operation of the business processes

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 32: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 32

Step 1Identify corebusinessprocesses

Step 2Identifyprocess stepsand interfaces

Step 3Identifybusinessrequirementsregardingprocessexecution

Step 4Definemonitoringobjects alertsand thresholds

Implementation Methodology for BusinessProcess and Interface Monitoring

Define andCreate

a MonitoringConcept

Implement theMonitoring

Concept

StartMonitoring

ContinuousImprovement

Step 6Definecommunicationand escalationprocedures

Step 7Assignmonitoringactivities toresponsibles

Step 8DefineReportingObjects andReportingActivities

Step 9Definecommunicationand escalationprocedures

Step 10Assignreportingactivities toresponsibles

Step 5Definemonitoringactivities

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 33: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 33

Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace BPM or on SDN under nw-processmonitoring

White Paper on standard process bdquoException Handlings andBusiness Process amp Interface Monitoringldquo undersupportstandards

Available class room trainingsSM300 ndash Business Process Management and Monitoring (3 days)E2E300 ndash E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace education

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 34: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 34

More than 350 Business Process Monitoring CustomersWorldwide

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 35: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 35

More than 350 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Apotex

Caterpillar

Colgate

COTY

Domtar

DuPont

Airbus

Arla Foods

Basell Polyolefins

Bayer Health Care AG

BMW

Carlsberg

Centrica

Eurohypo

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Nestleacute

Philips Lighting

Australian Co-Operative Foods

Crystal Group

DKSH

George Weston Foods

Hanson

Indofood Sukses Makmur

Japan Airlines

Ministry of Defence (Singapore)

Embraer

Estee Lauder

Hydro Quebec

Intel

John Deere

Petrobras

Postbank

RWE

Sara Lee

Shell

SPAR Oumlsterreich

Standard Bank SA

T-Systems

Sony Argentina

Toyota Financial Services

Unilever Brasil

Warner BrosEntertainment

YPF

Samsung SDS

Siemens IT Solutions ampServices Thailand

Singapore Airlines

Unilever Asia

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 36: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 36

End-to-End Business Process Integration andAutomation from SAP Helps Thai IT Group

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 37: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 37

SAPreg Solution Manager

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 38: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 38

Philips Lighting SAPreg MaxAttention

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 39: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 39

1 Business Process Monitoring - Overview

2 Business Process Analysis

3 Appendix - Functional Overview with ST-SER 700_2008_2 amp ST-API01L

Agenda

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 40: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 40

Appendix

Standard Process for Business Process Monitoring

Cross-Application Monitoring Functionalities

Interface Monitoring

Available Monitoring Objects forbull ERP Logisticsbull ERP Financialsbull SAP CRMbull SAP APObull Consistency Checksbull Extended Warehouse Managementbull Mass Activity Monitoringbull SEM-BCS

APPENDIX

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 41: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 41

Process Standard ldquoBusiness Process ampInterface Monitoring (including Exception Handling)rdquo

Business ProcessOperations

Key User ApplicationManagement

Business ProcessChampion

Detect Alert Situation

Execute exceptionhandling

Execute InitialAnalysis

Assign Service Deskmessage to issue

RCA process

Createaction plan

Change Requestprocess

Sign-off alertresolution

Identify ApplicationProblem

Create Service Deskmessage

Solve Service Deskmessage

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 42: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 42

Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects amp Monitoring Objectsfor InterfacesALE IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringWorkflow monitoringtRFC monitoringBDoc monitoringXI PI monitoring

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 43: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 43

Cross-Application Monitoring Functionalities(12)

R3 Background JobsStart-End delayOut of time windowNot started on timeMaximum durationCancellationParallel processingJob log messages

Dialog Performanceper transaction and SAP instance

per transaction-specific function codes(CUA internal commands)

per transaction-specific function codestransferred in HTTP requests

per HTTP request

per program function name in RFC call

per user pattern

Update Errors (Transaction- Program-specific)

V1 update errors V2 update errors

General Application Log (SLG1)total number of messages per object sub-object usercritical messages in terms of messageclass and number

Document Volumes (based on SAP tablestatistics)

Operations (inserts updates deletes)on SAP tables

Cross-Application Monitoring Objects

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 44: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 44

Cross-Application Monitoring Functionalities(22)

ALEIDoc Alert Monitoring per IDoc Type(CCMS based)

Outbound IDocsIDoc generatedIDoc ready for dispatchIDoc in external systemIDoc dispatchedError in IDoc interfaceError in external systemIDoc with delete flagIDoc processing in target system

Inbound IDocsIDoc generatedIDocs transferred to applicationIDoc transferred to dialogApplication document postedError in IDoc interfaceError in applicationIDoc with delete flag

All Alert Information available via CCMSMonitoring Infrastructure

qRFC Alert Monitoring (CCMS based)Blocked queuesStatus of RampR Queue Demon (CRM)Status of RampR Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

BDoc Alert Monitoring (CCMS based)BDoc Messages in error statusBDoc Messages waiting for response

Availability of RFC connection

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 45: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 45

Interface Monitoring ndash IDoc Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)sbquoDeltalsquo monitor number of suitable IDocs since the last datacollection

sbquoTotal numberlsquo monitor number of suitable IDocs for the last xdays

On object level

Direction Port Partner number Partnertype Partner function Message typeBasic type Message code Messagefunction IDoc age (in hours)

On key-figure level

Status number(s) Status messagequalifier Status message ID Statusmessage number Status age (in min)

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 46: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 46

Interface Monitoring ndash qRFC Monitoring(as of ST-API 01K and SAP_BASIS 46C)

Alert Type Select Options

qRFC MonitoringStatus (error) monitoringNumber of entries with critical status in groupAge of oldest critical status in groupCombination of Entries and Age in critical stateNumber of entries with interim status in groupAge of oldest interim status in groupCombination of Entries and Age in interim state

Backlog monitoringNumber of individual queues in groupTotal number of entries in all queues of groupAverage number of entries per queue in groupMaximum number of entries per queue in groupAge of oldest entry in groupCombination of Total entries and Oldest age

On object level

qRFC direction RFC destination Queue groupCommand string of SMD qRFC backlog collCommand string of SMD qRFC status coll

Considered statuses

Inbound

ANORETRY SYSFAIL ARETRY CPICERRMODIFY NOEXEC RETRY RUNNING STOPWAITING WAITSTOP

Outbound

ANORETRY SYSFAIL VBERROR ARTRYCPICERR EXECUTED MODIFY NOSENDSRETRY RUNNING STOP SYSLOADWAITING WAITSTOP WAITUPDA

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 47: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 47

Interface Monitoring ndash Batch Input File Monitoring(as of ST-API 01K amp SAP_BASIS 46C)

Alert Type Select Options

Batch Input MonitoringNumber of queues in specified status(es)Number of errors per sessionNumber of transactions processed per sessionNumber of transactions in specified status(es)Job cancellation

On object levelSession name Creating programCreated by

On key-figure levelStatus(es)

File Monitoring as of ST-API01KFile existence (at a certain time)File size (in kB)

On object levelFile path File name Pattern User(File Creator)

File Monitoring with SAPCCMSR agentFile existence (at a certain time)File age (in min)File size (in kB)Count lines in fileAlert on a specified patternstring

Select optionsFile name Path Files to be ignoredAgent scheduling (specified day andtime specified time-window)

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 48: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 48

Interface Monitoring ndash Workflow amp tRFC Monitoring(as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

Workflow MonitoringNumber of work items in status errorNumber of work items after system crashNumber of event linkages with status errorCanceled entries in workflow RFC destinationStatus of workflow runtime environment

On key-figure level

Task Collector Mode

tRFC MonitoringNumber of tRFC entries in critical stateAge of oldest entry in critical stateCombination of Entries amp Age in critical stateNumber of tRFC entries in interim stateAge of oldest entry in interim stateCombination of Entries amp Age in interim state

On object level

Client RFC destination Functionmodule User name MinimAge(critical) MinimAge (interim)

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 49: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 49

Interface Monitoring ndash BDoc Monitoring (as of ST-API 01L amp SAP_BASIS 46C)

Alert Type Select Options

BDoc MonitoringNumber of BDoc messages in error stateAge of oldest message in error stateCombi of Messages amp Age in error stateNumber of BDoc messages in interm stateAge of oldest message in interm stateCombi of Messages amp Age in interm state

On object level

BDoc Type Flow Context SenderSite Name Minimum Age (errors)Minimum Age (intermed)

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 50: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 50

Interface Monitoring ndash XIPI Monitoring(as of XI 640 (SP21) 70(SP13) and 710(SP3))

Alert Type Select Options

SAP XIPI MonitoringIntegration of the Message-Based Alerting errormonitoring on adapter framework(s) and integrationengine

On SAP XIPI per ruleSender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert categoryThreshold values for the number of alerts

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 51: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 51

Available Monitoring Objects for ERP Logistic

ERP LogisticSales amp ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality ManagementMiscellaneous

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 52: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 52

Monitoring ObjectsAlert types forSales amp Services (12)

Alert Type Selection Options

Sales Documents of sales documents created per day of sales document line items created of open sales documents of incomplete sales documents of sales documents with delivery block of sales documents with billing block of sales documents with credit block of sales orders (planned GI date in past but not delivered) of open orders via index table of orders with delivery block via index table of orders with billing block via index table of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 53: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 53

Monitoring ObjectsAlert types forSales amp Services (22)

Alert Type Selection OptionsSales Documents

Percentage of open sales ordersPercentage of incomplete sales documentsPercentage of sales orders with delivery blockPercentage of sales orders with billing blockPercentage of sales orders with credit blockPercentage of open orders via index tablePercentage of orders with delivery block via index tablePercentage of orders with billing block via index tablePercentage of orders with credit block via index table

Document category Sales document typeSales organization Distribution channelDivision Sales group Created by Olderthan x days Reference period Data fromprevious day Use creation date

Invoices of sales invoices posted per day of sales invoices line items posted per day of invoices not posted to FIPercentage of sales invoices not posted to FI

Billing type Billing category Salesorganization Distribution channel DivisionCreated by Older than x days Referenceperiod Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 54: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 54

Monitoring ObjectsAlert types forWarehouse Management (12)

Alert Type Selection Options

Transfer requirements of created inbound transfer reqs items of open inbound transfer reqs items

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

Transfer orders of created inbound transfer order items of open inbound transfer order items of confirmed inbound transfer order items of created outbound transfer order items of open outbound transfer order items of confirmed outbound transfer order items of outbound transfer order items confirmed withdifference of inbound transfer order items confirmed with difference created inbound transfer orders created outbound transfer orders

Warehouse number Source storage typeDestination storage type Older than x daysData from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 55: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 55

Monitoring ObjectsAlert types forWarehouse Management (22)

Alert Type Selection Options

Critical deliveries Depending on Warehouse Activity Monitor settings

Negative stocks Depending on Warehouse Activity Monitor settings

Interim storage stock without movement Depending on Warehouse Activity Monitor settings

Critical stocks for production supply Depending on Warehouse Activity Monitor settings

Posting change notices of created notices of open notices

Warehouse number Movement type Older thanx days Data from previous day

Stock levelStock level in storage typeUnblocked positive stock in differences storage type

Warehouse number Storage Type

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 56: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 56

Monitoring ObjectsAlert types forInventory Management

Alert Type Selection Options

Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day Plant Storage locationMovement type

Stock Level (IM)Unrestricted stockStock in transferQuality inspection stockBlocked stock

Plant Storage location Material Material typeMaterial group Stock quantity Base unit ofmaterial

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 57: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 57

Monitoring ObjectsAlert types forLogistics Execution (12)

Alert Type Selection Options

Due List Log (for deliveries)No docs createdToo few documentsNum of messages in DL runMessages

User

Inbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 58: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 58

Monitoring ObjectsAlert types forLogistics Execution (22)

Alert Type Selection Options

Outbound Deliveries of created deliveries of created delivery items of open deliveries of items in open deliveries of outbound deliveries with GI posted but no invoice of overdue deliveries of items in overdue deliveries

Shipping point Plant (item) Delivery type ItemCategory Created by Transaction Code Olderthan x days Data from previous day

Shipments of created shipments of overdue shipments

Transportation planning point Shipment typeOverdue since Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 59: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 59

Monitoring ObjectsAlert types forProcurement (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller Exception Group

Planned OrdersOpening Order Date = Today (external procurement)Opening Order Date lt Today (external procurement)Opening Order Date in Offset Period (externalprocurement)

Plant Order Type MRP Controller OffsetPeriod

Purchase Requisition of Requisition Items created of open Requisition Items of overdue Requisition Items

Purchasing organization Plant Creationindicator Item category Account AssignmentCategory Document type Created by Olderthan x days Outline agreement Agreementitem Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 60: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 60

Monitoring ObjectsAlert types forProcurement (22)

Purchasing organization PlantDocument category Item categoryAccount assignment CategoryDocument type Created by Outlineagreement Agreement item Data fromprevious day Older than x days

Purchase Orders of Purchase Orders created of Purchase Order Items created of open Purchase Order Items of overdue Purchase Order Items of Purchase Orders not yet completed

Alert Type Selection Options

MM Invoices (AP) of blocked invoices for payment of blocked invoices for payment (cash discount endangered)

Company code Fiscal year Older thanx days due within x days

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 61: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 61

Monitoring ObjectsAlert types forManufacturing (12)

Alert Type Selection Options

MRP RunKey Figures Statistics

RuntimeCanceledDumps

Key Figures MRP List of exceptions in MRP ListNo MRP List created

Plant

Plant MRP controller ExceptionGroup

Planned OrdersOpening Order Date = Today (in-house production)Opening Order Date lt Today (in-house production)Opening Order Date in Offset Period (in-house production)

Plant Order Type MRPController Offset Period

Confirmation errors caused by failed goods movements forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than x days Plant MRPcontroller Storage location

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 62: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 62

Monitoring ObjectsAlert types forManufacturing (22)

Alert Type Selection Options

Confirmation errors caused by incorrect cost postings forPP Production OrdersPS NetworkPM Maintenance OrdersPI Process OrdersTotal number

Older than Plant MRPController

Confirmation errors caused by PDCCATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than Plant MRPController

ProductionProcess Orders of orders overdue for release of orders overdue for delivery completed of orders overdue for technical closure of orders overdue for final confirmation of orders with release in offset period

Plant Order Type MRPController Overdue since Extstatus check Offset Period

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 63: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 63

Monitoring ObjectsAlert types forPlant Maintenance (12)

Alert Type Selection Options

PMCS NotificationsTotal of notif created of notif from maint sched created of manual notif createdTotal of notif completed of notif from maint sched completed of manual notif completedTotal of notif overdue of notif from maint sched overdue of manual notif overdue

Planning plant Notificationtype Created by Data fromprevious day Overdue since(days)

PMCS Orders of Orders created of Orders tech closedOrders in phase createdOrders in phase releasedOrders in phase technically closedOrders in phase closed

Plant Order type Planningplant Older than x days Datafrom previous day

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 64: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 64

Monitoring ObjectsAlert types forPlant Maintenance (22)

Alert Type Selection Options

Confirmation errors caused by failed goods movements forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller Storage location

Confirmation errors caused by incorrect cost postings forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Confirmation errors caused by PDCCATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days Plant MRPcontroller

Incorrect Measurement Reading Transfer

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 65: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 65

Monitoring ObjectsAlert types for QualityManagement

Alert Type Selection Options

Inspection LotsInspection Lots with Outstanding QuantitiesInspection Lots without Usage DecisionInspection Lots wo Inspection Completion

Plant Inspection Lot OriginOlder than x days

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 66: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 66

Miscellaneous Monitoring ObjectsAlert types

Alert Type Selection Options

BatchesUnrestricted use stock (Quant = 0)Sales order stock (Quant = 0)Project stock (Quant = 0)

Material Plant Storagelocation Older than x days

MessagesNot processed messagesIncorrectly processed messages

Application Message typeTransmission mediumDispatch time Partner functionOutput device Printimmediately User name Olderthan x days

Reservations of reservation items overdue

Material number PlantStorage location Req typeOverdue since

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 67: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 67

Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 68: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 68

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Postings - Throughput of FI postings of FI posting line items

Company Code Document Type CreatedBy Creation time from-to Data fromprevious day

Open Items (Vendors) of open items FI-AP (vendor items) of overdue open items FI-AP (vendor items) of overdue items in FI-AP w Spec GL ind (vendor) of open items FI-AP in status lsquoparkedrsquo (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Vendor Account SpecialGL indicator Older than x days Overduesince x days

Open Items (Customers) of open items FI-AR (customer items) of overdue open items FI-AR (customer items) of overdue items in FI-AR w Spec GL ind (customer) of open items FI-AR in status lsquoparkedrsquo (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code Fiscal Year CurrentFiscal Yearwith x years in past DocumentType Created by Customer AccountSpecial GL indicator Older than x daysOverdue since x days

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 69: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 69

Monitoring ObjectsAlert types for Financials

Alert Type Selection Options

Payment Run of Payment Runs in status lsquoproposedrsquo of Payment Runs in status lsquocancelledrsquo of enqueues of cancelled Payment Runs

Payment run identification Older than xdays

Bank Statements Bank statements not completely posted Bank statement items not completely posted

Company Code House Bank AccountID Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 70: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 70

Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 71: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 71

Monitoring ObjectsAlert types for Sales

Alert Type Selection Options

Sales Documents of sales documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 72: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 72

Monitoring ObjectsAlert types for Service

Alert Type Selection Options

Service Documents of service documents created per day of documents in status To be Distributedlsquo of documents in status lsquoError in Distributionlsquo of documents in status lsquoError of documents in status lsquoOpenlsquo or lsquoIn Processrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data formPrevious Day

Business ActivitiesTasks of ActivitiesTasks created of ActivitiesTasks Openlsquo or lsquoIn Processrsquo of ActivitiesTasks lsquoErrorrsquo

Business Transaction Category BusinessTransaction Type Input Channel SalesOrganization Distribution Channel DivisionCreated by Older than x days Data fromPrevious Day

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 73: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 73

Monitoring ObjectsAlert types forCustomer Interaction Center

Alert Type Selection Options

Outbound Calls of open calls

Assigned to Overdue for x hours

E-Mail Work Items of E-Mail Work Items created of E-Mail Work Items Ready of E-Mail Work Items Selectedlsquo

Task Type E-Mail recipient Previous dayOlder than x hours

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 74: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 74

Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 75: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 75

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Planned Orders of orders with opening date today of orders with opening date in the past(both separated for in-house and external proc) of orders in offset period

Location Product ID Planned or UnplannedOrders Production Planner Start x days in thepast end x days in the future Max openingperiod x days

Purchase requisitions of Purchase Req Items created of open Purchase Requisition Items of overdue Purchase Requisition Items

Location Production Planner Data fromprevious day Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 76: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 76

Monitoring ObjectsAlert types for PPDS

Alert Type Selection Options

Change pointersConfirmation for Scheduling AgreementsExternal Procurement

Inhouse Production

Planned Independent Requirements

Sales Orders

Production Campaign

Planning File Entries (IS-Automotive)

Transports

Deliveries

Confirmations (IS-Automotive)

Confirmation of deletions (IS-Automotive)

Reporting Points (IS-Automotive)

Reservations

Location Type of Location Method used duringtransfer of an object Older than x days

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 77: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 77

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON)

Alert Type Selection Options

Demand Planning RunTotal Runtime Processed CVCs CVCs not savedRuntime CVC

Background Job Number Data from previousday

SNP Optimizer RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

SNP Optimizer Profile Data from previous day

SNP Heuristic RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

Planning book Data view Global SNP settingsprofile Selection Profile Planning versionProduct Location Data from previous day

CTM RunTotal Runtime of created ObjectsRuntime created ObjectRuntime Location Product

CTM Profile Data from previous day

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 78: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 78

Monitoring ObjectsAlert types for Planning Runs(based on SAPAPOPERFMON ndash cont)

Alert Type Selection Options

Backorder Processing RunMax Runtime [in sec]Max Time in Status U (in minutes)No of Interact BOP Runs (only prevday)Messages dur BOP Run (prev+ actual day)BOP runs in Status BBOP runs in Status IPos processed successfully (in permille max valueAvg No of saved Items per secondAvg No of processed items per sec (based on total)Avg processing time per item (based on tot runtime)Avg time for saving (per item) [msec]Avg time for ATP check (per item) [msec]

Name of BOP Run

User (create)

Filtervariant

Max Duration for Status sbquoUlsquo

Message Type (A E W)

Message ID

Message Number

Previous day

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 79: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 79

Available Monitoring Objects

Data Consistency CockpitERP Sales amp Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 80: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 80

Monitoring ObjectsAlert types forERP Sales amp Services

Alert Type Select Options Comment

Credit Management of credit customers with critical deviationsAge of stored analysis

Variant Based on reportZ_CREDIT_VALUE_COMPARE_DCC which can be found inSAP Note 1040893

Requirements of items with errorschecked itemsAge of stored analysis

Variant Based on report SDRQCR21(SAP Note 1036106 required)

Accounting documents without billingdocuments

of inconsistent objects (absolute)Age of stored result

Variant Based on Generic ConsistencyReport(available via ST-API)

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 81: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 81

Monitoring ObjectsAlert types forERP Financials

Alert Type Select Options Comment

Financial Accounting Comparative AnalysisExistence of a differenceAge of last SAPF190 run

Company Code

Relevant Period

Based on reportSAPF190

Comparison between CO totals and line itemsExistence of a differenceAge of stored analysis

Used variant Based on reportRKACOR04 (SAPNote 1121834)

FI-CO consistencyExistence of a differenceTotal value of inconsistent FI-documentsNo clear assignment possibleAge of stored analysis

Used variant Based on reportZKACOR43_DCC(SAP Note 1109289)

Material Master ndash Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

Used variant Based on reportSAPRCKMU(Transaction CKMC SAP Note 1091447 )

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 82: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 82

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

Consistency CRM-ECCPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

Consistency CRM-CDBPercentage of inconsistent objects of inconsistent objects (absolute) of objects in both systems but unequal of objects in compared system only

of objects in CRM system onlyAge of last comparison run start

DIMa instance name Based on Data IntegrityManager (DIMa)

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 83: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 83

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Marketing BW-SEM Consistency CheckStatistic CRM MktElmts (total)Statistic BW MktElmts (total)Statistic BW MktElmts (marked as existing)Statistic BW MktElmts (marked as deleted)Statistic SEM MktElmts (total)Statistic SEM MktElmts (non-zero plan data)Statistic SEM MktElmts (zeroed-out plan data)MktElmt status TotalMktElmt status OK (including deleted)MktElmt status Not created in BWMktElmt status Not deleted in BWMktElmt status Not deleted in SEMMktElmt status UnknownMktElmt status Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 84: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 84

Monitoring ObjectsAlert types for CRM

Alert Type Select Options Comment

CRM Leasing Payments vs Billing RequestItems

Existence of a differenceNumber of differencesAge of last CRM_FS_EVALUATE_PAYM_BRIS run

Used variant Based on reportCRM_FS_EVALUATE_PAYM_BRIS

SAP Note 1135291 required(pilot release)

CRM Leasing Billing Request Items in errorExistence of a differenceNumber of differencesAge of last CRM_FS_FIND_BRIS_IN_ERROR run

Used variant Based onCRM_FS_FIND_BRIS_IN_ERROR

SAP Note 1135291 required(pilot release)

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 85: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 85

Monitoring ObjectsAlert types for APO

Alert Type Select Options Comment

CIF Deltareport (APO-ECC) of inconsistencies of inconsistent planned orders of inconsistent production orders of inconsistent sales orders of inconsistent purchase orders of inconsistent purchase requisitions of inconsistent scheduling agreements of inconsistent stocks of inconsistencies in other objects

Name of save Based on Deltareport

LiveCache - DatabaseTotal17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 86: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 86

Monitoring ObjectsAlert types for stocks inWMECC

Alert Type Select Options Comment

Stock valuesAbsolute variance per company codeAge of last RM07MMFI runExistence of a difference

Used variant Based on RM07MMFI (SAP Note921161 required)

WM-IM Stock ComparisonAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 87: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 87

Monitoring ObjectsAlert types forMaterials Mgmt Extended Warehouse Mgmt

Alert Type Select Options Comment

MM Consistency CheckExistence of a difference (total and separatelyfor tables MBEW MARC MARD and MCHB)Age of last MB5K runNumber of differences (total and separately fortables MBEW MARC MARD and MCHB)

Used variant Based on transaction MB5K(SAP Notes 1076137 and1131548 required)

EWM-ERP Stock comparisonExistence of a differenceAv Prop Diacuteff QtyWM stockMax Prop Diff QtyWM stockAge of last SCWMERP_STOCKCHECK run

Used variant Based onSCWMERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 88: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 88

Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 89: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 89

Monitoring ObjectsAlert types forExtended Warehouse Management

Alert Type Selection Options

Waves of overdue waves

Warehouse Number Wave Type WaveCategory Overdue in hours

Warehouse Orders of overdue warehouse orders

Warehouse Number Queue ActivityArea Overdue in hours

Warehouse Tasks of overdue warehouse tasks of overdue replenishment tasks

Warehouse Number WarehouseProcess Type Warehouse Processcategory Overdue in hours

Inbound Deliveries of inbound deliveries overdue without Warehouse Task of inbound deliveries overdue without Goods Receipt

Warehouse Number Document TypeOverdue in hours

Outbound Deliveries of outbound deliveries overdue without Warehouse Task of outbound deliveries overdue without Goods Issue

Warehouse Number Document TypeOverdue in hours

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 90: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 90

Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

IS - BankingDeposits Management (FS-AM)Bank AnalyzerBanking Services

IS - Insurance

IS - Telecommunications

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 91: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 91

Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

of Selected Objects of Successful Objects of ExceptionsThroughput (per hour) for all jobsThroughput (per jobper hour)Custom Counter (up to 20 different eg ldquoPayment Runrdquo)

Job informationDuration (overall) of canceled jobsAverage interval processing timeJob statistics (CPU time DB time EM usage)

Hardware utilizationCPU utilization (max min average)Paging per hourUsed Memory (per server)Used Memory (per mass activity run)BTC work process utilization

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 92: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 92copy SAP 2008 Business Process amp interface Monitoring Page 92

Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 93: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 93

Alert types for SEM-BCS

Alert TypeThroughput

of processed SEM-BCS Tasks per hour (or defined time interval) of processed BI Queries per hour (or defined time interval) of BCS Task and Reporting Users per hour (or defined time interval)Peak Information All task categories

SEM-BCS Task informationAverage Total Runtime per Task categoryAverage Status ReadUpdate Runtime per Task categoryAverage Data ReadUpdate Runtime per Task categoryAverage Records ReadUpdated per Task categoryAverage Function Runtime per Task categoryAverage Log Runtime per Task categoryDrilldown functionality to single task informationDrilldown functionality to single Validation step information

BI Query informationAverage Runtime per QueryTotal of executions per QueryDetailed BI Query statistics

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten

Page 94: Business Process & Interface Monitoring - archive.sap.com · Business Process & Interface Monitoring Part 1 – Keep Mission Critical Business Processes Running Part 2 – Appendix

copy SAP 2009 Business Process amp interface Monitoring Page 94

Copyright 2009 SAP AGAll 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 AG The information contained herein may be changedwithout prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may vary

The information in this document is proprietary to SAP This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This documentcontains only intended strategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business product strategyandor development SAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphics links orother items contained within this material This document is provided without a warranty of any kind either express or implied including but not limited to the implied warranties ofmerchantability fitness for a particular purpose or non-infringement

SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This limitationshall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcher Form auch immer ohne die ausdruumlckliche schriftliche Genehmigung durchSAP AG nicht gestattet In dieser Publikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werdenEinige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte koumlnnen Softwarekomponenten umfassen die Eigentum anderer Softwarehersteller sindSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver Duet Business ByDesign ByDesign PartnerEdge und andere in diesem Dokument erwaumlhnte SAP-Produkte und Servicessowie die dazugehoumlrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Laumlndern weltweit Alle anderen in diesem Dokument erwaumlhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken Produkte koumlnnen laumlnderspezifische Unterschiede aufweisen

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP Dieses Dokument enthaumllt nur vorgesehene Strategien Entwicklungen und Funktionen des SAPreg-Produkts und ist fuumlr SAP nicht bindend einen bestimmtenGeschaumlftsweg eine Produktstrategie bzw -entwicklung einzuschlagen SAP uumlbernimmt keine Verantwortung fuumlr Fehler oder Auslassungen in diesen Materialien SAP garantiert nicht dieRichtigkeit oder Vollstaumlndigkeit der Informationen Texte Grafiken Links oder anderer in diesen Materialien enthaltenen Elemente Diese Publikation wird ohne jegliche Gewaumlhr wederausdruumlcklich noch stillschweigend bereitgestellt Dies gilt u a aber nicht ausschlieszliglich hinsichtlich der Gewaumlhrleistung der Marktgaumlngigkeit und der Eignung fuumlr einen bestimmten Zwecksowie fuumlr die Gewaumlhrleistung der Nichtverletzung geltenden Rechts

SAP uumlbernimmt keine Haftung fuumlr Schaumlden jeglicher Art einschlieszliglich und ohne Einschraumlnkung fuumlr direkte spezielle indirekte oder Folgeschaumlden im Zusammenhang mit der Verwendungdieser Unterlagen Diese Einschraumlnkung gilt nicht bei Vorsatz oder grober FahrlaumlssigkeitDie gesetzliche Haftung bei Personenschaumlden oder die Produkthaftung bleibt unberuumlhrt Die Informationen auf die Sie moumlglicherweise uumlber die in diesem Material enthaltenen Hotlinkszugreifen unterliegen nicht dem Einfluss von SAP und SAP unterstuumltzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewaumlhrleistungen oder Zusagen uumlberInternetseiten Dritter ab

Alle Rechte vorbehalten