2008 09 17 AGS Roadshow Cis BPM En

AGS Roadshow 2008, Moscow

Business Process and Interface MonitoringWaldemar Befort, Senior Support ConsultantSAP AGSeptember 17th 2008

© SAP 2008 / Business Process & interface Monitoring / Page 2

Overview – Business Process Integration &Automation Management

Data ConsistencyManagement

Data VolumeManagement

Business Process &Interface Monitoring

Job SchedulingManagement

Business ProcessPerformance Optimization

Proactively ensure reliablebusiness process flow andthroughput

Optimize business processflow and throughput

Keep data growth &size 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


Purpose of Business Process Monitoring

Customer

Distributor

Warehouse

Supplier

Subcontractor

Production

Headquarter

CRMSCM/APO

SRM/EBP

WMS

BW

Legacy SystemLegacy System

SAP R/3

CRM

Create SalesOrder

SAP ECC

Create SalesOrder

CreateDelivery

Post GoodsIssue

Create &Print Invoice

WMS

PerformPicking

Send PickConfirmation

Problem occurs in thesystem landscape

What part of the corebusiness process isaffected?

• Who reacts?• How?• When is 2nd

level informed?• Who is the

escalationcontact?


Business Departments

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

Functional & Technical View

Technical View(Process-independent)

Business Process Operations

Functional ViewFunctional process descriptionFunctional process operation and control

IT Infrastructure & Technical Operations

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

Basis/mySAP TechnologySystem log monitoringABAP dump analysisPerformance monitoringWorkload monitoring

BusinessProcess

Purpose of Business Process Integration &Automation Management

BusinessProcess


Business Process & Interface Monitoring

Key Notes


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 block?How many outbound deliveries are open (goods issue posting notcomplete)?How many picking transfer orders are open (not confirmed) in yourwarehouse management system?How many outbound deliveries have GI posted but no invoice wascreated?How many invoices have been created but were not printed?How many sales invoices were not posted to FI?

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


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 & 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


Business Process Monitoring with SAP SolutionManager

Definition of Business Process MonitoringBusiness Process Monitoring is the proactive and process-oriented monitoring of a company’score business processesIt includes the observation of all technical and application-related functions that are requiredfor a smooth and reliable flow of the core business processes

Goals of Business Process MonitoringTo detect problem situations as early as possible in order to solve them as fast as possible -before they become critical for the businessBy introducing SAP Solution Manager:

To provide defined monitoring proceduresTo enable the customer’s Solution Support Organizationto respond to and to solve problems more proactively



System Example

CRM - C00

Create SalesOrder

SAP ECC - TT5

Create SalesOrder

CheckAvailability

Run MRP

ProcurementProcess

ManufacturingProcess

CreateOutboundDelivery

Post GoodsIssue

Create BillingDocument

Warehouse - TT5

CreateOutboundDelivery

Create PickingTransfer Order

Confirm PickingTransfer Order

Post GoodsIssue

SAPENTERPRISE

PORTAL - EPP

Create SalesOrder

Example 1: Business Process “Order-to-Cash”with typical error situations

MRP run not started

Job SD_CREATE_SALES_ORDERS_2Hcancels regularly

Replication of theOutbound Delivery fails

Goods Issuesare not posted


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


Example 2:Business Process “Sales Order Management”

ERP

Create OutboundDelivery(VL10A)

Create SalesOrder

Perform Billing (VF04)

DMS

Send Urgent OrderPerform OrderRescheduling

(V_V2)

Create Shipment(VT01N)

Create PickingTransfer Order (TO)

Confirm Picking TO(LT11)

Confirm Picking TOwith difference

In case ofDiscrepancies blockDiscrepancies on Binin Storage Type 999

Post Goods Issue

• No. of outbounddeliveries created

• No. of open outbounddeliveries

• No. of overdue shipments

Job runtime

• No. of Open Picking TOs

Job runtime

• Stock Level in differencestorage type

• Unblocked stock indifference storage type

Dialog ResponseTime

• No. of deliveries with GIposted but no invoice

• No. of invoices nottransferred to FI

• No. of invoices not printedJob runtime

Dialog ResponseTime

• No. of open Sales Orders• No. of incomplete Sales Orders

• No. of SOs with delivery block• No. of SOs with billing block• No. of SOs with credit block


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)

Example 3: Interface Monitoring in the „Order-to-Cash“ Business Process

qRFC Monitoring - Outbound

qRFC Monitoring - Inbound

File Monitoring +Batch Input Monitoring

XI Processing

DESADV IDocs - Inbound

DESADV IDocs - Outbound

MATFET IDocs

MATMAS IDocs



Functional Overview


Cross-Application Monitoring Functionalities

Cross-Application Monitoring ObjectsBackground JobsDialog Performance (per transaction & 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)*ALE/IDoc Alert Monitoring per IDoc TypeXI Alert MonitoringBatch Input MonitoringFile Monitoring

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

tRFC Alert Monitoring*Workflow Monitoring*

*functionality with next ST-A/PI 01L


Application-Specific MonitoringFunctionalities

Application-Specific Monitoring ObjectsEnterprise Resource Planning Logistics

Sales & ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceQuality Management*

IS – UtilitiesIS – Banking

Deposits Management (FS-AM)Bank AnalyzerBanking Services

IS – InsuranceIS – Telecommunications

Enterprise Resource Planning FinancialsCustomer Relationship Management

SalesServicesCustomer Interaction Center

Advanced Planner & OptimizerDemand PlanningSupply Network PlanningProduction Planning /Detailed Schedulingglobal ATP

Extended Warehouse ManagementStrategic Enterprise Management – BCS

*functionality with next ST-A/PI 01L

© SAP 2008 / Business Process & interface Monitoring / Page 37© SAP 2007 / Business Process & interface Monitoring / Page 37

Data Consistency Monitoring Functionalities

Data Consistency Monitoring ObjectsEnterprise Resource Planning Logistics

Sales & ServicesWarehouse ManagementInventory Management

Enterprise Resource Planning FinancialsExtended Warehouse ManagementSupply Chain Management

liveCache - DatabaseCIF-Interface

GenericIntra-system CheckIntersystem CheckCustom Developed Consistency Reports

Customer Relationship ManagementCRM – ECCCRM – CDBTrade Promotion ManagementLeasing


ERP (PRD)

Example: Procurement

Create PurchaseRequisitions by MRP

Receive InboundDelivery

Run MRP

Convert Purchase Req.to Purchase Order

Post Goods Receipt

Sent/Print PurchaseOrder

Job RuntimeMRP Log

No. of Purch. Req. createdNo. of Purch. Req. open

No. of Purch. Req. overdue

No. of InboundDeliveries created

No. of Goods Receiptscreated

Create PurchaseRequisitions Manually

Create Binning TransferOrder

Confirm Binning TransferOrder

Perform InvoiceVerification

No. of Purch. Orders createdNo. of Purch. Orders open

No. of Purch. Orders overdueNo. of open Transfer

Requirements

Stock Level of criticalstock in GR area

Job Runtime

Job Runtime

Dialog ResponseTime

No. of Transfer Orders createdNo. of open Transfer Orders

Dialog ResponseTime

Job Runtime

No. of consumptionpostings

No. of Purch. Req. createdNo. of Purch. Req. open

No. of Purch. Req. overdue


Example: Manufacturing

ERP (PRD)

Create Planned Order

Confirm ProductionOrder + Backflush

Components

Run MRP

Convert Planned Orderto Production Order

Post Goods Receipt forProduction Order

Settle Work Orders

Release ProductionOrder

JobRuntime

MRP Log

No. of PlannedOrders overdue

No. of Confirmation Errors:• Goods Movements• Cost Postings• CATS/PDC Transfers

No. of consumption postings

Dialog ResponseTime/Job Runtime

Stock Level Examples:• No. of Finished Products in

quality inspection• No. of materials in GR area

with quantity >100 PCJob

Runtime

No. of ProductionOrders overdue for

release


Example: Ad Hoc Maintenance

ERP (PRD)

Update Work Orders withMaterials, Services,

Labor

Select Notifications

Capacity Planning

Create Notifications

Accept: Create WorkOrders

Print Shop Floor Papers

Post Goods Receipt

Confirm Work Orders

Update NotificationLong text

Job: Close Work Orders

Job: Settle Work Orders

Technically completeWork Orders

Reject: UpdateNotification long text

Set User Statuson Notification

Release Work Orders

No. of Notificationscreated

No. of Notificationsoverdue

No. of PM Orders createdPM Orders in phase

created

PM Orders in phasereleased

Stock Level of criticalspare parts in storagelocation of shop floor

No. of Confirmation Errors:• Goods Movements• Cost Postings• CATS/PDC Transfers

No. of PM Orderstechnically closed per day

PM Orders in phasetechnically closed

Job Runtime

Job Runtime



Setup Methodology


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 Point:Creation of Monitoring concept started during the “Technical and Integration Design” phaseof implementation project

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


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


Solution Management Optimization Service forBPM

The Solution Management Optimization (SMO) Service for BusinessProcess Management comprises:

The creation of a Business Process Management and Monitoring Concept including thedefinition of

Monitoring objectsError handling proceduresEscalation paths

Configuration of Business Process Monitoring in the SAP Solution ManagerWrap up presentation and summarizing service report

The service covers the analysis of 1 or 2 core business processes(depending on their complexity), and its delivery is planned for 2consultants for 3 to 5 days on-site/remote.

This service is exclusively available within an SAP Support Engagement(i.e. SAP MaxAttention and SAP Safeguarding).


Further Information about Business ProcessMonitoring

Further Documentation in Media Library of Quick Link BPM onSAP Service Marketplace service.sap.com/bpm

White Paper on standard process „Exception Handlings andBusiness Process & Interface Monitoring“ underservice.sap.com/supportstandards

Available class room trainings:SMO610 – Business Process Management and Monitoring (3 days)E2E300 – E2E Business Process Integration and Automation Management

(5 days including certification)

Check SAP Service Marketplace service.sap.com/education

https://websmp105.sap-ag.de/bpm

http://websmp101.sap-ag.de/supportstandards

https://websmp208.sap-ag.de/education


More than 250 Business Process Monitoring CustomersWorldwide


More than 250 Business Process Monitoring CustomersWorldwide

EMEA

AM

ERIC

AS

APJ

Caterpillar

COTY

Domtar

DuPont

Embraer

Airbus

Arla Foods

Basell Polyolefins

Benetton

BMW

Centrica

Danone

FERRERO

Gaz de France

KarstadtQuelle AG

KONE

Lekkerland

Australian Co-Operative Foods

Crystal Group

George Weston Foods

Hanson

Indofood Sukses Makmur

Ministry of Defence (Singapore)

Estee Lauder

Graybar Electric Company

Hydro Quebec

Intel

International Bank forReconstruction & Development

Nestle

Philips Lighting

RWE

Sara Lee

SPAR Österreich

T-Systems

John Deere

L’Oreal USA

Petrobras

Toyota FinancialServices

Unilever Brasil

Samsung SDS

Siemens IT Solutions &Services Thailand

Singapore Airlines

Unilever Asia

© SAP 2007 / Page 48

Thank you!


Appendix

Functions in detail

© SAP 2008 SAP Business Process and Interface Monitoring Kick-Off Page 50

© SAP 2008 / Business

Available Monitoring Objects for ERP Logistic

ERP LogisticSales & ServicesWarehouse ManagementInventory ManagementLogistics ExecutionProcurementManufacturingPlant MaintenanceMiscellaneous



Monitoring Objects/Alert types forSales & Services (1/2)

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 type,Sales organization, Distribution channel,Division, Sales group, Created by, Olderthan x days, Reference period, Data fromprevious day, Use creation date



Monitoring Objects/Alert types forSales & Services (2/2)

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 type,Sales organization, Distribution channel,Division, 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, Division,Created by, Older than x days, Referenceperiod, Data from previous day



Monitoring Objects/Alert types forWarehouse Management (1/2)


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

Warehouse number, Source storage type,Destination storage type, Older than x days,Data from previous day

Transfer orders# of created inbound transfer orders# of open inbound transfer orders# of confirmed inbound transfer orders# of created outbound transfer orders# of open outbound transfer orders# of confirmed outbound transfer orders# of confirmed with difference outbound transfer orders# of confirmed with difference inbound transfer orders

Warehouse number, Source storage type,Destination storage type, Older than x days,Data from previous day



Monitoring Objects/Alert types forWarehouse Management (2/2)


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



Monitoring Objects/Alert types forInventory Management


Goods MovementsGoods Issue throughputGoods Receipt throughput

Data from previous day, Plant, Storage location,Movement type

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

Plant, Storage location, Material, Material type,Material group, Stock quantity, Base unit ofmaterial



Monitoring Objects/Alert types forLogistics Execution


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

User

Inbound Deliveries# of created deliveries# of open deliveries

Shipping point, Delivery type, Created by,Transaction Code, Older than x days, Data fromprevious day

Outbound Deliveries# of created deliveries# of open deliveries# of outbound deliveries with GI posted but no invoice

Shipping point, Delivery type, Created by,Transaction Code, Older than x days, Data fromprevious day

Shipments# of created shipments# of overdue shipments

Transportation planning point, Shipment type,Overdue since, Data from previous day



Monitoring Objects/Alert types forProcurement (1/2)


MRP RunKey Figures Statistics

RuntimeCanceledDumps

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

Plant

Plant, MRP controller, Exception Group

Planned OrdersOrder Start Date = Today (external)Order Start Date < Today (external)

Plant, Order Type, MRP Controller

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

Purchasing organization, Plant, Creationindicator, Item category, Document type, Olderthan x days, Outline agreement, Agreementitem, Data from previous day

Purchase Orders# of Purchase Order Items created# of open Purchase Order Items# of overdue Purchase Order Items

Purchasing organization, Plant, Documentcategory, Item category, Document type,Outline agreement, Agreement item, Data fromprevious day, Older than x days



Monitoring Objects/Alert types forProcurement (2/2)


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



Monitoring Objects/Alert types forManufacturing (1/2)


MRP RunKey Figures Statistics

RuntimeCanceledDumps

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

Plant

Plant, MRP controller, ExceptionGroup

Planned OrdersOrder Start Date = Today (internal)Order Start Date < Today (internal)

Plant, Order Type, MRPController

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

Older than x days, Plant, MRPcontroller, Storage location



Monitoring Objects/Alert types forManufacturing (2/2)


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

Older than, Plant, MRPController

Confirmation errors caused by PDC/CATS transfers forPP Production OrdersPS NetworkPM Maintenance OrdersTotal number

Older than, Plant, MRPController

Production/Process Orders# of orders overdue for release# of orders overdue for delivery completed# of orders overdue for technical closure# of orders overdue for final confirmation

Plant, Order Type, MRPController, Overdue since, Ext.status check



Monitoring Objects/Alert types forPlant Maintenance (1/2)


PM/CS 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, Data from previous day,Overdue since (days)

PM/CS 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



Monitoring Objects/Alert types forPlant Maintenance (2/2)


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 PDC/CATS transfers forPS NetworkPM Maintenance OrdersTotal number

Older than x days, Plant, MRPcontroller

Incorrect Measurement Reading Transfer


Miscellaneous Monitoring Objects/Alert types


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 type,Transmission medium,Dispatch time, Partner function,Output device, Printimmediately, User name, Olderthan x days

Reservations# of reservation items overdue

Material number, Plant,Storage location, Req. type,Overdue since



Available Monitoring Objects for ERPFinancials

Monitoring Objectsfor ERP Financials



Monitoring Objects/Alert types for Financials


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 ‘parked’ (vendor)Amount of open items FI-AP (vendor items) (optional)Amount of overdue items FI-AP (vendor items) (optional)

Company Code, Fiscal Year, CurrentFiscal Year/with x years in past, DocumentType, Created by, Vendor Account, SpecialG/L 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 ‘parked’ (customer)Amount of open items FI-AR (customer items) (optional)Amount of overdue items FI-AR (customer items) (optional)

Company Code, Fiscal Year, CurrentFiscal Year/with x years in past, DocumentType, Created by, Customer Account,Special G/L indicator, Older than x days,Overdue since x days



Monitoring Objects/Alert types for Financials


Payment Run# of Payment Runs in status ‘proposed’# of Payment Runs in status ‘cancelled’# 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



Available Monitoring Objects for CRM

SAP CRMSales

Services

Customer Interaction Center



Monitoring Objects/Alert types for Sales


Sales Documents# of sales documents created per day# of documents in status 'To be Distributed‘# of documents in status ‘Error in Distribution‘# of documents in status ‘Error'# of documents in status ‘Open‘ or ‘In Process’

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

Business Activities/Tasks# of Activities/Tasks created# of Activities/Tasks 'Open‘ or ‘In Process’# of Activities/Tasks ‘Error’




Monitoring Objects/Alert types for Service


Service Documents# of service documents created per day# of documents in status 'To be Distributed‘# of documents in status ‘Error in Distribution‘# of documents in status ‘Error'# of documents in status ‘Open‘ or ‘In Process’

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

Business Activities/Tasks# of Activities/Tasks created# of Activities/Tasks 'Open‘ or ‘In Process’# of Activities/Tasks ‘Error’




Monitoring Objects/Alert types forCustomer Interaction Center


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 'Selected‘

Task Type, E-Mail recipient, Previous day,Older than x hours



Available Monitoring Objects for SAP APO

Monitoring Objectsfor SAP APO



Monitoring Objects/Alert types for PPDS


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



Monitoring Objects/Alert types for PPDS


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



Monitoring Objects/Alert types for Planning Runs(based on /SAPAPO/PERFMON)


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 version,Product, Location, Data from previous day

CTM RunTotal Runtime# of created ObjectsRuntime / created ObjectRuntime / Location Product

CTM Profile, Data from previous day



Monitoring Objects/Alert types for Planning Runs(based on /SAPAPO/PERFMON – cont.)


Backorder Processing RunMax. Runtime [in sec.]Max. Time in Status 'U' (in minutes)No. of Interact. BOP Runs (only prev.day)Messages dur. BOP Run (prev.+ actual day)BOP runs in Status 'B'BOP runs in Status 'I'Pos. 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 ‚U‘

Message Type (A, E, W)

Message ID

Message Number

Previous day



Available Monitoring Objects

Data Consistency CockpitERP Sales & Services

ERP Financials

SAP CRM

SAP APO

(Extended) Warehouse Management



Monitoring Objects/Alert types forERP Sales & 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 errors/checked 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-A/PI)


© SAP 2008 / Business© SAP 2007 / Business Process & interface Monitoring / Page 78

Monitoring Objects/Alert types forERP Financials


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 – Material Ledger ComparisonExistence of a differenceIncreasing number of incorrect materialsAge of stored analysis

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



Monitoring Objects/Alert types for CRM


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)





CRM Marketing: BW-SEM Consistency CheckStatistic: CRM Mkt.Elmts. (total)Statistic: BW Mkt.Elmts. (total)Statistic: BW Mkt.Elmts. (marked as existing)Statistic: BW Mkt.Elmts. (marked as deleted)Statistic: SEM Mkt.Elmts. (total)Statistic: SEM Mkt.Elmts. (non-zero plan data)Statistic: SEM Mkt.Elmts. (zeroed-out plan data)Mkt.Elmt. status: TotalMkt.Elmt. status: OK (including deleted)Mkt.Elmt. status: Not created in BWMkt.Elmt. status: Not deleted in BWMkt.Elmt. status: Not deleted in SEMMkt.Elmt. status: UnknownMkt.Elmt. status: Sum of error statusAge of last check execution

Program name

Variant name

Based on reportZRSMRM_CRM_MKT_CHECK (SAP Note 816793)





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)



Monitoring Objects/Alert types for APO


CIF Deltareport (APO-ECC) ccr# 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 – Database om17Total17 Keyfigures for specific object types1 User defined key figureAge of most recent run

User Based on OM17



Monitoring Objects/Alert types for stocks inWM/ECC


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. Díff Qty/WM stockMax. Prop. Diff. Qty/WM stockExistence of a differenceAge of last LX23 run

Used variant Based on LX23 (SAP Note1035124 required)



Monitoring Objects/Alert types forMaterials Mgmt. / Extended Warehouse Mgmt.


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. Díff Qty/WM stockMax. Prop. Diff. Qty/WM stockAge of last /SCWM/ERP_STOCKCHECK run

Used variant Based on/SCWM/ERP_STOCKCHECK(SAP Notes 1097463 and1123340 required)



Available Monitoring Objects for ExtendedWarehouse Management

Monitoring Objectsfor ExtendedWarehouseManagement



Monitoring Objects/Alert types forExtended Warehouse Management


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 Type,Overdue in hours

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

Warehouse Number, Document Type,Overdue in hours



Available Monitoring Objects for Mass ActivityMonitoring

Mass Activity MonitoringIS - Utilities

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

IS - Insurance

IS - Telecommunications



Alert types for Mass Activity Monitor

Alert TypeProcessed Objects

# of Selected Objects# of Successful Objects# of ExceptionsThroughput (per hour) for all jobsThroughput (per job/per hour)Custom Counter (up to 20 different, e.g. “Payment Run”)

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



Available Monitoring Objects for SEM-BCS

SEM-BCSThroughput and Detailed Information for

SEM-BCS Tasks

SEM-BCS BI Queries



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 Read/Update Runtime per Task categoryAverage Data Read/Update Runtime per Task categoryAverage # Records Read/Updated 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



Outlook of proposed Monitoring Objects

Cross-Application MonitoringObjects & Monitoring Objectsfor InterfacesALE / IDoc monitoringqRFC monitoringSAP Batch Input monitoringFile monitoringXI / PI monitoring



Cross-Application Monitoring Functionalities(1/2)

R/3 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



Cross-Application Monitoring Functionalities(2/2)

ALE/IDoc Alert Monitoring per IDoc TypeOutbound IDocs

IDoc 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 MonitoringBlocked queuesStatus of R&R Queue Demon (CRM)Status of R&R Queues (CRM)

Customer Exit in ApplicationMonitoring Infrastructure

Interface Monitoring Objects

Customer Specific Monitoring Objects

XI Alert MonitoringMessage monitoring

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

Availability of RFC connection



Interface Monitoring – IDoc Monitoring(as of ST-A/PI 01K and SAP_BASIS 4.6C)

Alert Type Select Options

IDoc Monitoring (error and backlog monitoring)‚Delta‘ monitor: number of suitable IDocs since the last datacollection

‚Total number‘ monitor: number of suitable IDocs for the last xdays

On object level:

Direction, Port, Partner number, Partnertype, Partner function, Message type,Basic 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)



Interface Monitoring – qRFC Monitoring(as of ST-A/PI 01K and SAP_BASIS 4.6C)


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 group,Command string of SMD qRFC backlog coll.,Command string of SMD qRFC status coll.

Considered statuses:

Inbound:

ANORETRY, SYSFAIL, ARETRY, CPICERR,MODIFY, NOEXEC, RETRY, RUNNING, STOP,WAITING, WAITSTOP

Outbound:

ANORETRY, SYSFAIL, VBERROR, ARTRY,CPICERR, EXECUTED, MODIFY, NOSENDS,RETRY, RUNNING, STOP, SYSLOAD,WAITING, WAITSTOP, WAITUPDA



Interface Monitoring – Batch Input, File Monitoring(as of ST-A/PI 01K & SAP_BASIS 4.6C)


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 level:Session name, Creating program,Created by

On key-figure level:Status(es)

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

On object level:File 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 pattern/string

Select options:File name, Path, Files to be ignored,Agent scheduling (specified day andtime, specified time-window)



Interface Monitoring – XI/PI Monitoring(as of XI 6.40 (SP21), 7.0(SP13) and 7.10(SP3))


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

On SAP XI/PI per rule:Sender PartySender ServiceSender interfaceSender NamespaceReceiver partyReceiver ServiceReceiver InterfaceReceiver Namespace

On SAP Solution Manager per alert category:Threshold values for the number of alerts

Date post:	09-Dec-2015
Category:	Documents
Upload:	christopheolivier4145
View:	227 times
Download:	3 times