BPM: Idoc Monitoring

Hi Colleagues,
I'm configuring IDoc Monitoring in BPM and have an unexpected result.
System generate error alert "0 IDocs have been found since the last collector run at 01:56:56 on 18.11.2009"
I expected this message to be green since system didn't find any IDoc error, or with proper number when it has errores.
Mi configuration for IDoc Delta Monitoring is:
Direction Outbound
Partner Port ZPTA_PI
Basic Type ORDERS05
IDoc age (in hours) 336
Status Number(s): All technical for outbound:
- 29 Error in ALE service (for example, errors with field conversion, and so on)
- 26 Syntax error (for example, too many segments, wrong IDoc structure, and so on)
- 37 IDoc added incorrectly
- 02 Error passing data to port (for example, port not available, file system not available, and so on)
- 20 Error triggering EDI subsystem (for example, error during OS script processing)
Any ideas?
Regards,
Renato Petrulis

Hi Renato
I think you work with IDoc monitoring based on application monitor.
So in this case, I guess setup based on the meanining is correct way.
(You do not have to setup like IDoc Monitoring of CCMS base).
*Also at the moment IDoc monitoring based on application monitor is recommended.
Now you focus on technical error.
So it should not be occur. So I think using just "more than"
is ok. If you use less than, in case of zero "0" value,
you get some alert. So I think in that case, less than is not
necessary.
It is worth using less than alert when you monitor through put.
How many number of documents are created, then checking data
using more than (due to some error, less data created than expected)
and less than (due to some error like incorrect master data setting,
less data created than expected)
best regards
Keiji

Similar Messages

IDOC Monitoring issue - job BPM_DATA_COLLECTION* not running.

Hi all,
We are facing an issue with BPM "IDOC Monitoring" (under application monitoring), which we have setup to monitor Inbound and Outbound Idocs in 2 separate R/3 systems.
In one system it works fine, and measured values are returned each time the monitor is set to run according to the specified schedule.
However, for another R/3 system, the monitor has never run, even though the settings are identical in the monitoring setup.
From reading the Interfaces Monitoring Setup guide, I found that this monitor depends on a job called BPM_DATA_COLLECTION* which runs in the monitored system. In the system where monitoring is functioning correctly, I can see this job is completing successfully at the time the monitor is set to run. All I find is completed jobs - no scheduled or released jobs present.
However, for the system where the monitoring is not functioning, I found that this job is not running, but that the job is sitting in scheduled status instead.
When I tested manually running the job in this system, it ran successfully, and in Solution Manager the monitor brought back the measured value, so the monitor only ran successfully when I manually ran the job in the monitored system.
I read notes 1321015 & 1339657 relating to IDOC monitoring. 1321015 appears to be more relevant, yet it does not exactly describe my issue - it mentions the job BPM_DATA_COLLECTION* failing rather than just remaining in scheduled status which is what I see.
Anyone else see this issue before?
On a more general point - the standard BPM Setup guide doesn't really go into much detail on IDOC Monitoring, and makes no mention of what is happening in the background, i.e. the job BPM_DATA_COLLECTION* being created and run as per schedule. This info is found in a separate document "Interface Monitoring Setup Guide".
Is there any single document which describes fully what happens both in the Solution Manager and the Monitored systems when BPM is activated? For example, to describe which monitors require jobs to be run, which monitors require additional setup in monitored system, etc? A document such as this which describes exactly the process flow for each monitor would be very useful in troubleshooting issues going forward.
Thanks,
John

Hello John,
most probably the user assigned to the corresponding RFC READ connection that connects SolMan with the backend system doesn't have proper authorization to release a job. That's why it is only created/scheduled but not released. Verify if the RFC user on the backend has the latest CSMREG profile assigned according to SAP note 455356.
You can also check if the latest ST-PI support package is installed on your backend system as the ST-PI usualy contain the latest definition of CSMREG.
Best Regards
Volker

Idoc Monitoring - WE02

Dear Experts,
I am in the process of configuring System Monitoring in our Solution Manager system. I have to monitor Idocs coming in our ERP 6.0 system for failed messages - status 51 and status 03. Can you please provide me some info on which objects to use for monitoring this from solution manager? I am not using Interface monitoring since the Business Processes arent defined in our Solution Manager system and we dont have the luxury to do this at this stage.
Regards,
Mohammad.

Hello Mohammad,
even though you don't have the time to model business processes I would still recommend to use Interface Monitoring as part of BPMon as there the IDoc monitoring is more powerfull and flexible than a configuration via BDMO. You can create simple dummy processes which contain just one or two steps represneting the sending and recieiving of IDocs. You then use the IDoc monitor as part of the Application Monitor. A detailed description is given in "Setup Guide for Interface Monitoring" under https://service.sap.com/bpm > Media Library > Technical Information
You could then later on enhance your process models and make meaningful process models out of your dummy processes.
But only with BPMon you can specifically monitor for status 51 or 03. A configuration via BDMO monitors only in "containers" comprising several error status. Also the data collection frequency in BDMO cannot be really influenced.
So if you start from scratch rather go for BPMon and not with BDMO where you even have to transport the configured objects which is not necessary with BPMon.
Most customers that started at some point in time with BDMO changed to BPMon during the last couple months.
Also check the following Blog /people/johannes.fleig/blog/2008/05/25/new-business-process-monitoring-functionalities-in-sap-solution-manager-150-ale-idoc-monitoring
Best Regards
Volker

IDOC - BPM - IDOC Error --no sender or receiver interface definition found

I have an integration scenario, IDOC - BPM - IDOC. SAP will send ACC_GL_POSTING IDOC to XI, a BPM will start and then the BPM will send an IDOC to another SAP system.
I have read instructions on weblogs:
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
The scenario has been successfully tested in the Test Configuration Tool. However, when I try send IDOC from the source, I received the message below in the trace.
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="3" type="T">Processing mode is</Trace>
<Trace level="3" type="T">created BPE proxy for message B45CB0079DFA814BAD22CD1ED64CA6AB</Trace>
<Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING.ACC_GL_POSTING01*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING_abs*</Trace>
<Trace level="1" type="T">select interface namespace http://summaryFinancial.sap.dominofoods.com</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>
<Trace level="1" type="T">Set interface action DEL into MAST</Trace>
</Trace>
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA" />
<Trace level="3" type="T">inserted message into pipeline PE_ADAPTER</Trace>
<Trace level="1" type="Timestamp">2007-04-30T18:32:30Z EST qRFC raised on XBQO$PE_WS91000003</Trace>
</Trace>
Thanks,
Sergio

Rajeev,
The source system in the receiver determination is connected to R3. Other IDOCs are coming across the XI system.
Below is some trace information in the Receiver Determination.
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - IP_GeneralLedger</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) IP_GeneralLedger ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
Thanks,
Sergio

IDoc Monitoring in NWA: PI Perspective

Hi
I am a fresher PI Developer working on Netweaver 7.3. I came across IDoc monitoring tab in NWA, but it doesn't show the IDoc's processed within the last few days. Apart from this, there is also a IDoc metadata tab in IDoc monitoring in NWA. I couldn't understand why there is another metadata tab in NWA, while we add metadata by IDX2.Do we need to add IDoc metadata in NWA separately in order to monitor IDoc's from NWA? If not, then why IDoc monitoring in NWA is not showing any IDoc's while we had processed hundreds of IDoc's through ICO's(Java stack)? Is there a separate configuration to be done to monitor IDoc's from NWA?

Hi,
Check below link which will answer your query:
Idoc monitoring:
http://help.sap.com/saphelp_nw73/helpdata/en/de/82c727b3d94714a04a4a579663fcf5/content.htm
Idoc metadata:
http://help.sap.com/saphelp_nw73/helpdata/en/50/980951964146f1a7f189b411796bae/content.htm
Thanks
Sunny

IDOC - XI(BPM) - IDOC

Hi,
Does anybody has a documentation regarding how to set up an IDOC - XI - IDOC scenario using a BPM. Coz' currently I have an error from BPM - IDOC as the error "Unable to convert the sender service SC_PO_idoc2idoc to an ALE logical system". SC_PO_idoc2idoc is my BPM.
Thanks
Zubair

I've done all the necessary however still giving me the same problem, one thing I realize our XI box is currently running on SP10 this could be the problem so we've decide to upgrade it to SP11.
1. we have sp10 and the problem doesn't exist
Integration Directory and just happened that same Logical system has been used by another system then it would raised an error to my BPM saying "Check Result for Object SC_PO_idoc2idoc Logical system M01CLNT200 already exists in service | BS_JOBSKL_200" when I'm trying to SAVE the changes to my BPM.
2. but if you have 2 different systems why are you using the same name? they must be different as they represent 2 different systems
Is this a bugs in SP10 as well, do you face any problem like this before. Because if this is an issue then it will be a disaster if we have many interface coming into XI and need to be send to one same BS which the logical system is unique.
3. Like you wrote "logical system is unique" so you can't have two business systems with the same logical system name
This means that "to be send to one same BS which the logical system is unique" can be easily achived - don't worry.
regards,
michal

For IDOC monitoring, analysis and error handling in ALE & idoc

Hello...experts..can u please tell me about idoc monitoring,analysis and error handling..and can u please tell as per interview point of view in this area..if availble can u send material about this...
thx
Message was edited by:
durga kottapalli

Hi,
Reprocessing IDocs with errors
Outbound (BD88)
Once the error has been determined and corrected it is not necessary to resend the IDoc again. You simply resend the IDocs that have already been generated.
Using the IDoc overview screen you need to take note of the following for each IDoc that was not processed:
Error number: 2, 4, 5, 25, 29
Error number: 30 (Execute Check IDoc dispatch to process)
IDoc number
Using the Error number, the IDoc number and the transaction BD88 , with the required message type you can resend the IDoc. Match the error number with this transaction and execute the function for the IDocs incorrectly processed.
Just check the below link, u will get all IDOC related Interview questions
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/
http://www.sappoint.com/abap.html
http://www.sap-img.com/
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
http://www.sappoint.com/abap.html
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sap-img.com/
http://www.allsaplinks.com/
Regards,
Suresh.
Message was edited by:
SureshKumar Ramamoorthy

Queries on Business Process Monitoring (BPM) & Interface Monitoring

Dear all,
I have got a few queries on the subject and would greatly appreciate any valuable inputs.
Before I proceed, want to clarify that I have downloaded all overtly available documents (PDFs, SIMs) from the following URLs:
http://service.sap.com/rkt-solman
http://service.sap.com/solutionmanager Media Library
http://service.sap.com/bpm Media Library
I may not have read them all though since I come from a Functional angle.
Kindly reply to whatever query you can please. Not all of them are sequential.
Queries:
(1) How are Interfaces with External Systems (beyond the firewall of the enterprise) monitored ?
(2) Is it really worth listing all such External Systems as Logical Components in their own right ? I guess this makes sense if at a Process Step level, one wants to list a 'specific' Logical Component involved instead of 'generic' term like External System. However, it would benefit only if Interface Monitoring is feasible; isn't it ?
(3) There are Interfaces which are built between SAP and External System and serve various Business Processes under various Business Scenarios. In such circumstances, it is not easy to list which Process 'owns' the Interface. Therefore, under a normal Implementation Project structure (SOLAR02), choosing a particular Process Step, getting into 'Development' Tab and listing the Interface Program name may not be feasible, since there is no particular place where it belongs.
Is it therefore a good idea to create namesake Scenario for capturing all interfaces and list a library of all interfaces and store documents right there ? If so, will these namesake processes be of any use in BPM at a later date ?
(4) If my primary objective is to accomplish Interface Monitoring and not Business Process Monitoring per se, is it a good idea to create a new Solution Landscape, and manually create Business Processes that are suited to list Interfaces than to assign Template or Implementation Project to the Solution Landscape, and inherit those Processes ?
(5) What is it that a SAP Competence (Support) Centre will find as a 'major' gain in activating BPM to monitor Interfaces alone - is there something that SolMan's BPM based Interface Monitoring gives more than what PI level reporting may provide them with ?
(6) In Interfaces with Non-SAP Systems (some of them are old/ proprietary legacy systems with Credit Card companies; some of them are like 'Active Directory' servers), is it possible to define Metrics for BPM that such systems will contribute to SolMan, for reporting purposes ? Or, is it too much to hope for
Thanks again, for your patience and advance thanks for your kind responses.
Srini
Bes

Hi,
Welcome to BPM
You have asked too many questions in a single Post, Please read rules of engagement before posting
You can monitor the following without any trouble.
● ALE/EDI
● qRFC
1) Its obvious, if your firewall blocks all your request to external enterprise, it is not possible to monitor.
3) These interfaces are not the one related to development tab in SOLAR02, you have to map them from BPM.
4) Yes, you don't have to depend on any project for your processes, you can add it in your Solution Landscape.
5) Post a Separate Thread!!!
6) Post a Separate Thread!!!
Hope this gives a better idea.
Feel free to revert back.
--Ragu

Idoc monitoring tool .

Guys , Is there any tool to monitor the Inbound and the outbound IDoc s from one server to another server . ? I know there are transactions to view the Idoc , reprocess it , But i need to know is there any tool kinda thing which monotors all of the inbound and outbound idocs ?

Hi,
I have no idea if there exist such a tool..
But when i had a similar requirement for IDoc monitoring i couldn't find any such tool so i developed a tool on my own similar to WE05 transaction but with additional functionality which will monitor the idocs and email the list of error idocs and complete idoc lists seperately. This tool was scheduled according to the client requirement daily and its working fine now.
Regards,
-Sandeep

IDOC Monitoring WE06 - RSEIDOCA

Hi Guys,
We want to monitos IDOCs for error in our ERP system. I have tried to use WE06 but I am not getting any notification apart from just "ALARM Message from Active IDoc Monitoring" which is very generic and doesnt give any details. Could someone please help in this regard? I am not sure how to setup correct tasks to this report
Thanks,
SK

Santosh, report RSEIDOCA is triggering a very specific single task workflow TS74508518 you need to make sure to have defined it as general task (either via SWU3 features or directly at the task level)
There is a OSS note specifically referring to this pre-requisite.

Idoc monitoring (may be ALEAUD)

Hi Guru's
In our project, there is a lot of idoc monitoring done, which requires manual work
To keep an eye on the queue, one person is required everytime,
But after searching I have found that we can have this process automatic, ie when idoc will fail
a mail can be sent regarding this to a particular user.
I have found that ALEAUD message type can be used to implement this if I am not wrong.
Please guide me if someone has implemented this in his/her project.
Please don't copy links, as I have all done the search work.
Now I need your support.
Thanks a lot
Manu

[ALEAUD explained here in sap library|http://help.sap.com/saphelp_nw70/helpdata/EN/0b/2a6550507d11d18ee90000e8366fc2/frameset.htm] : schedule periodically RDBSTATE program

IDOC Monitoring Procedures for error

Hi ,
Can anyone provide me the link or document for IDOC Monitoring for error?

Hey,
R3 side.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
WE42 process code
WE47 status info.
XI Side.
IDx5(Idoc check)
SU53(authorization check)
IDX2
Transaction: IDX2
There are a couple of situation where IDX2 can be useful on the XI system.
1. When we want to test connection between the XI and SAP backend system.
you can also refer to these links will surely help.
http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/frameset.htm
Troubleshooting File-to-IDOC Scenario in XI.
Note:-940313
regards,
Milan

IDOC Monitoring urgent

Hi SAPpers,
Does anybody knows what is IDOC Monitoring?
The step by step configuration for IDOC monitoring.
Was is the purpose of that?
What is the Tcode for monitoring IDOC?
Thanks will be rewarded

Hi,
Use
You can easily and effectively monitor inbound and outbound processing of IDocs using special reports and graphic displays. An agent can also be notified automatically using a workflow if an emergency occurs (active monitoring).
Features
The following tools are available for monitoring:
·        IDoc Display
All the other fields of the control record are available as selection criteria as well as partners and messages
-   IDoc numbers
-   Ports
-   IDoc types
You can display a tree structure of the IDoc directly using the IDoc number. The IDoc list is displayed again if several IDocs are selected.
·        IDoc Statistics
The IDocs are sorted and represented graphically according to predefined status groups. Lists and individual IDocs can be displayed using mouse clicks.
·        IDoc Search
You can select IDocs according to their business content, that is, according to the data contained in the segments.
·        Error and Status Processing
Error and status codes are defined for the IDoc transfer. These codes can be assigned to a workflow task, which informs the agent automatically in a procedure.
·        Monitoring the Inbound Queue
If you can receive IDocs via qRFC, you can monitor the inbound queue using a special transaction.
·        Monitoring the Outbound Queue
If you can send IDocs via qRFC, you can monitor the outbound queue using a special transaction.
·        Active Monitoring
This function provides you with a report that informs you if the number of critical IDocs exceeds a certain threshold.
Active Monitoring Locate the document in its SAP Library structure
Use
This report automatically informs the agents responsible if too many incorrect IDocs are found.
Integration
Active monitoring is not used for processing or reimporting of an incorrect IDoc. Exception handling of every incorrect IDoc is responsible for this.
Activities
You plan the report to run regularly with a variant. The variant also informs the report of the status values to be selected: If the critical status contains more IDocs than specified in the critical number of IDocs, a message is sent to a predefined recipient.
The recipient receives the notification in the form of a work item displayed in their Business Workplace. If they execute the work item, the IDoc statistics are displayed with the values determined at the time of evaluation. The agent can display the current status of these IDocs using the Refresh function. The selection criteria which led to the notification are also used for this evaluation.
Example
An important customer orders goods using EDI on working days, between 8am and 6pm. These goods are to be delivered at 4pm the next day. To ensure that the delivery is made on time, the ordered quantity must be recorded by midday on the day of delivery. The active monitoring function is to be used at 8am every morning to determine whether there are any orders which could not be processed automatically. The report, therefore, is started at the same time every day and 0 is selected as the critical number of IDocs. The agent responsible is notified if any incorrect IDocs are found and can then manually process the outstanding orders by midday.
For more information see
Schedule Monitoring Job (example)
A processing status is assigned to an IDoc during processing (e.g. Status03: Data Transfer to Port OK). These status values are in turn assigned to a higher level status group (e.g. Output: IDoc Transfer Successful). This assignment to a status group is referred to as Qualification. You can change the assignment of status values to status groups in the Edit Status Values transaction.
Procedure
       1.      To edit the status groups, choose the ALE customizing transaction SALE ® Set-Up System Monitoring ® Set-Up IDoc Status Display ® Edit IDoc Status Values (WE47).
A list of statuses which have been defined is displayed.
       2.      If necessary, choose This graphic is explained in the accompanying text. By double-clicking on the status that you wish to assign a different status group, the detail screen is displayed.
       3.      The status group is displayed in the Qualification field. Use the F4 input help for an explanation of the numbers.
       4.      Select Save.
ExampleExample
Status 25 (processing despite syntax error (outbound)) is assigned status group 1 = Outbound: IDoc generated". Replace 1 with 5 for Outbound: IDoc Interface error".
Chek Tcodes in WE02 OR WE05
Regards,
Phani,
Points If Helpful.

Idoc monitoring using WE06

Hi all,
I want to do Idoc monitoring using the tool Active Idoc Monitoring(Programm: RSEIDOCA;Transaction : WE06).
So when ever something goes wrong in an Idoc,depending on the idoc type ,I want to inform the concerned person by email using SAP mail( Business Workplace).
My questions are with regard to the 2 possibilities(I thought) stated below for achieving this.
[1]
Is it possible to directly send an email to the SAP mail inbox of the concerned person,using this program depending on the Idoc type and other conditions if they exists .Because depending on the idoc type different users need to be informed of the error.
I made a variant as said below in the link.
http://help.sap.com/saphelp_470/helpdata/En/dc/6b81b943d711d1893e0000e8323c4f/frameset.htm
Is it possible to test this case immediately by sending a error ORDERS Idoc.If yes,How?
Is the configuration said in the above link sufficient or Is there any need to make any further changes.
OR
[2]
Using transaction WE06,I want to the send the email to my sap mailBox and from there forward it to other users depending on the conditions said above.
How could I achieve it? Test it immediately
I would like to go forward with this 2nd solution,if thats better and easily configurable.
How to configure this scenario.
Any help is greatly appreciated.
Regards
K

Closing this thread.Moving it to a more appropriate forum.

IDOC Monitoring returns wrong result

Hi All
I set up IDOC Monitoring to generate Yellow alert when No. of IDOC is less than 6 and ref when it is more than 6.
However, even when the no. of IDOC is more than 6, I get a Yellow alert. I checked "Auto Notif" under Notifications and Service Desk

First of all please refer to following SDN Blog for details about the setup of
IDOC monitoring:
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/9639
You can define threshold values in both directions, for "more than" and
"less than" at the same time.
Just to confirm your threshols looks like this:
if less than 6, = yellow. if more than 6 = Red ?

BPM: Idoc Monitoring

Similar Messages

Maybe you are looking for