Idoc (monitoring system BSM)

Hello All,
In the process, to check if communication between SAP and WMS is operational (IDoc) we create a mail, if idoc is not ok.
We would like to connect a failure to a monitoring system BSM by sending and event.
is this possible from an ABAP program? If so, How?
Good answers will be appreciated.
Thanks in advance.
Regards
Sasidhar Reddy Matli.

Hi Vishal,
Please check and implement below notes to fix the first issue:
1570282 - Advance Corr. BPMon ST-A/PI 01N
1946940 - ST-A/PI 01Q SP2: Advance Correction BPMon (Infrastructure and
EBO)
1869678 - Advanced Corrections for BPmon/Analytics Delivered with 01Q SP1
(framework)
Thanks
Vikram

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

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

Error when posting IDoc *** in system ERP100

Hi Experts!
Can you pls help me with a goods receipt issue?
When user tries to make a good receipt on a PO, we have the msg "Error when posting IDoc *** in system ERP100" in SRM front-end application monitor.
The same msg is getting displayed in RZ20.
On the idoc itself in tcode WE02 however, I can't see any problem and unfortunately I have no access to the same t-code in R/3. Anyway, I don't see the GR on the PO.
What can be the reason for this problem please?
What is in general the way to analyse and solve this kind of issue?
Thanks a lot !!
imre

Hi,
First find out the PO number from the idoc in tx WE02 in SRM system. Then in ERP , transaction BD87 , specify the details like message type and the system information .... and find out the PO that was errored out for GR. From this we can find the cause of the error. First try to rectify the error and then run the report to clear the contents of BBP_DOCUMENT_TAB.
Hope this helps.
Regards,
Kalyan

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 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 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: Data collection not getting completed

Hi,
I have setup IDoc monitoring in Solution Manager 7.1 SP08 for managed systems which is on ST-A/PI 01Q. There are many IDoc being generated in the managed system but I am not getting any alert for it.
In the alert inbox I get the message that the data collection has not yet taken place since the last activation. and the last data collection time is shown as of 2009.
Also in the managed system the BPMon background job BPM_DATA_COLLECTION_2 get cancelled with run time error TSV_TNEW_BLOCKS_NO_ROLL_MEMMORY
What can be the issue?
Regards
Vishal

Hi Vishal,
Please check and implement below notes to fix the first issue:
1570282 - Advance Corr. BPMon ST-A/PI 01N
1946940 - ST-A/PI 01Q SP2: Advance Correction BPMon (Infrastructure and
EBO)
1869678 - Advanced Corrections for BPmon/Analytics Delivered with 01Q SP1
(framework)
Thanks
Vikram

Unable not find the monitoring object(idoc monitoring ) in BPmon

Hello Guys,
     As part configuration of IDOC monitoring in BPmon configuration ,while i am creating monitoring object for IDOC monitoring (solman_workcenter->Business process operations ->setup Business process monitoring -->selected the solution --> business scenarios -->
As mentioned above i could not able to find the IDOC monitoring template in the droup down list
Components level on manage system:-
ST-PI       2008_1_710 SP 08
ST-A/PI   01Q_731 SP2
I have done the load monitoring definition by selecting respective local component and clicked on load monitoring definitions
Please help me on resolving the issue.
Regards,
Pavan

Hello Calvin van der Walt,
Please upgrade ST-PI & ST-A/PI component to latest level.I resolved my issue by doing ST-PI & ST-A/PI component upgarde.
I had raised an OSS message eith SAP on this isssue and SAP has asked us for ST-PI & ST-A/PI component upgarde.
So please go with ST-PI & ST-A/PI component upgarde it will resolve your issue.
Regards,
Pavan

Inbound idoc monitoring

Dear all
What tcode use for inbound idoc monitoring when data is transfer from one sap system to other sap system
Thanks
Amit

Hi
use the Tool (TCODE WE19) for inbound IDoc monitoring.
Also check the following Tcodes
BDM2 Monitoring: IDocs in Receiving Sys.
ELDM Monitoring of IDocs Processed
IDX5 IDoc Adapter - Monitoring
RSEIDOCA Active IDoc Monitoring with Workflow
WE06 Active IDoc monitoring
Reward points if useful
Regards
Anji
Message was edited by:
 Anji Reddy Vangala

Reg : IDOC Monitoring

Hi All,
       Could any one please let me know abt the IDOC Monitoring technique?
       What are all the things we need to take care in idoc monitoring?
      Any inputs will be of gr8 use.
Thanks in advance.
Regards
Abhilash.

Hi Abhilash,
In Idoc monitoring we monitor the idocs in MMS system. Depending upon the type of data ( Master or Transactional) we need to take action .
For master data in error status, you need to replicate the data, if it still fails then you will create a ticket and assign it to your next level support.
Fror Transactional data in error status ( for eg 51 status you will first reprocess the data through RBDMANI2 program) u need to reprocess, if it still fails then create a ticket and assignit to properresolution group which will take care of issue.
Remember For master data you should always replicate the data first and for transaction reprocess the data.
we monitor the idocs in red status and yellow status.
Red status - 02,26, 29, 51
Yellow status - 30, 64 , 52
Depending on the status of idoc and type of data ( Master or Transactional) it contains you will take action.
refer link below for more info
http://help.sap.com/search/highlightContent.jsp
Regards
Vinod

Advanced IDOC Monitoring Tool (AIM)

Dear all,
what is the Transaction of 'Advanced IDOC Monitoring Tool (AIM)' ?
It is mybe the WE02?
regards

Hi
IDOC Monitoring
WE02 IDoc display
WE05 IDoc Lists
WE06 Active IDoc monitoring
WE07 IDoc statistics
System Monitoring
SM12 Locked Entries
SM13 Update Monitoring
SM21 System Log Display
SM58 Transactional RFC Log
SM66 Debug Async Update Tasks
ST22 Dump Analysis
Regards
Gaurav

In 26.0, how do I put Download, Bookmarks, History, and Tags into separate windows? I have multi-monitor system and place these different windows . . .

Hello,
I recently, decided to upgrade from 19.0b to the current (26.0) version, as "Tab Utilities" now supports 26, but am finding one of the visual changes counter productive. My two workstations have multiple monitors. One has 2 monitors (2560x1600) and the other one has 4 monitors (2560x1600). On both workstations, I'll place the various Firefox informational windows off the "main monitor" (the one directly in front of me). This way they're available to me at a glance.
(Side note: I refer to my monitors, as 2L, 1 2R and the 4th as "auxiliary.") The one thing I miss most is being able size these Firefox windows independently and in different positions.
I mean I'm used to seeing "Download" on monitor 2R on the right side (1/8 of screen) behind Microsoft Process Explorer's System Information. While the History will be on monitor 2L on the right side at 1/4 of the screen). I'm used to glancing out my right eye at the downloads and when needing something from the past, it's right next to the main monitor #1. This way I can access history quickly.
I can see why a developer (with one monitor say 1920 x 1080) would love seeing one window, but why can't Firefox support both single and multiple monitor users at the same?
Anyway, is there a way to get 26.0 to place at least "Download" and "History" in separate sizable windows?
(I'm not jumping up and down to go back to 19.0b or to try 25, but would like to stay current.)

Hello,
Thank you for your very quick reply. Before I read your reply completely, let me see if I can answer your first concern.
> Maybe I am missing your point.
Maybe I'm not making the point properly. Honestly, I never explained the issue from how it is directly affecting me.
OK, let's do a real world example of what I'm seeing on my two monitor system. I'll first describe what I experienced with 19.0b and earlier, which is IMHO how it should work in 26 and beyond ('''''as an option'''''). Next, I'll review what I'm seeing in 26.0. Hopefully this will help you understand what changed, from a practical perspective.
In 19.0b (and how I like working) for a multiple monitor system:
On the main monitor, I'm running Firefox. It is 1920 x 1080 and is in the lower right hand corner.
On the the monitor to my right (2R), I have the Download Manager list of downloading and downloaded file. It is in the upper right hand corner and takes up about 300 x 1500 pixels.
For a two monitor system, I have the History List running beside Firefox in the lower right hand corner and it is 600 x 1080.
For a three (plus) monitor system, I have the History List running on my left (2L) monitor. It is in the lower right hand corner and is 600 x 1080 pixels big.
For 26.0: I'm seeing the following:
On the main monitor, I'm running Firefox. It is 1920 x 1080 and is in the lower right hand corner. (This is the SAME as with 19.0b.)
When I start the Download Manager and have it set up as I do for 19.0b, it looks OK. It is on monitor 2R and is 450 x 1500 pixels (because of the new navigation side bar).
'''''The problem STARTS NOW (when I start the History List).'''''
When starting the History List, it replaces the Download Manger on the 2R monitor in the 450 x 1500 pixel window. This doesn't work for me because:
1) It is too far away to see. (NOTE: I put it on the 2L monitor in the lower right hand corner. so I can see it easier for the 3+ monitor. In the case of the 2 monitor, I put it beside Firefox again to see it easier.)
Some might ask, but the Download Manager is on the 2R and right side, why can't the History List be there too? Good question, and I can only reply saying:
1) Personal choice.
2) The Download Manager is NOT as busy as the History List and I find it easy to read.
3) The History List is a lot busier and the font size looks to be smaller (might be the same, but it looks smaller to my eyes). I need it closer to me / Firefox.
What I'm saying is this . . . The Download Manager and History List have <ul>''valid reasons to be visible to the user at the same time''.</ul> They also need to be independent of one another for (at least) size and location.
Combining them together is OK for some people, but NOT for everyone. Please make it an option to combine (as in 26) and separate (25 and earlier).
I'm not sure this is the best way to put it, but here goes. Allow users to collapse or expand these various lists by using multiple windows. One window is the collapse view and multiple independent windows is the expand view.
I'll read and comment on the rest of your reply, soon. Thanks for allowing me hopefully to explain my point in a better manner. :-)

Remote Desktop Monitoring System

I am having some porblem regarding my project on Remote Desktop Monitoring System.
The project is supposed to have the following features:
1.Monitor and Control the computer in a network
2.Send Instant Message
3.File Transfer
We are having porblem on Networking ,Please supply us with the code or description on how to connect computers using Java so we can check on ours....

Remote Desktop Monitoring System is supposed to be a fully java based project. As the name suggests, the project should be able to view the computers(active screens) on the network and perform some specified tasks.
It also should have features like Instant messaging and File transferring between the connected computers.
(It is similar to the available software in Windows XP which helps us to monitor and contorl othe computers in the network)
-In order to connect to each other, the computer should have Remote
Desktop Monitoring Systems Server software or Client software installed in it.
-The main objective of this project is to build that Server and Client software with which we can perform the specified tasks.
-We are using NetBeans to develop the project and MySQL to handle some user datas.
-We have finished the Front End forms for the project and are finding difficulties in networking using java.(since we are students new to java)
I hope the above explanation clears some queries about the project.If anything is not clear please post on this forum and help us.
So if anybody has similar type of project or and concept regarding how to create the Client and Server side software as mentioned above please help us.

Idoc (monitoring system BSM)

Similar Messages

Maybe you are looking for