Monitoring IDOC

Where to get as much as possible information about processing and monitoring IDOC processing.
I have in mind workflow for idocs with errors, monitoring in solution manager and maybe something else.
I would not like marketing material but something more.
In first line I am interesting in workflow for idocs and how to distinguish application errors from system errors (i.e how to route infos ofidocs wih error if they have application error to one agent and if there is an system error to another egent...)

Hello,
for automated IDoc monitoring you should check out "Setup Guide for Interface Monitoring" under https://service.sap.com/bpm > Media Library > Technical Information
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

Similar Messages

How can we monitor IDOCS of managed system from Solution manager .

Hello
Please tell me the steps clearly involved in monitoring IDOC's..
I have created BPM RFC till now ..
Thanku..
Dev

Hi
you need to configure interface monitoring
config guide
https://websmp104.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000258142008E
usage scenario
/people/johannes.fleig/blog/2008/05/25/new-business-process-monitoring-functionalities-in-sap-solution-manager-150-ale-idoc-monitoring
Hope it solved ur prb completely
Regards
Prakhar

Monitor IDOC in PI

Hi Gurus.
I am quite new to PI and have to advice my company on how PI can be used to "better" monitor IDOC.
Scenario is one sap system is communicating to other sap system using IDOCs currently.
We have been told by SAP that using PI, we can get better monitoring capabilities than is currently available.
But after all my searching, I could only find 2 advantages that I can get:
- One central place where we could monitor all errors - need not go into all sender/receiver system separately
- Using PI, we could send acknowledgements back to sender system.
Are there any other benefits? I still dont think that PI monitoring could be used by the end-user. Still an administrator would be required for it, just like we have for ALE monitoring. Correct?
Lets say the receiver system is down. Can I configure PI in such a way that it "automatically" sends the IDOC to the receiving system "AFTER" the receiving system is up?
Are there any other advantages of using PI as a middleware in this scenario? Any monitoring capability which it has which can get a SURE thumbs-up from all parties - something which is not at all possible in ALE, but PI can provide??
Thanks in advance.

Hi,
if you have an existing IDoc to IDoc scenario where just one system is sending IDocs without mapping to another the benefits doesnt seem to large:
- One system more to administrate and to monitor
- One place more where a message can fail (more risc)
- in case of receiver system down an IDoc message from PI would stuck in SM58 - this is the same behaviour for a SAP sender system
- WE02 monitoring at sender and receiver system is anyway required
- acknowledgements shoulnt be a challenge with or without PI
The advantages are more in bigger and more complexe environments:
- One central place for integration knowledge
- All traffic via one platform: centralized monitoring and alerting
- Quick and easy change of mapping implementation
- Implementation of more complexe business rules with BPM
Regards,
Udo

How to Monitor IDOC Adapter

Hi Frnds,
How to monitor IDOC adapter. Its resides in Integration Engine.
Regards,
Raj

hi,
Adding to above you can refer to this wiki.It has all in fo about Idoc.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/home/step%252bby%252bstep%252bprocedure%252bfor%252bcreation%252bof%252bidoc
regards,
ujjwal kumar

How to monitor idoc in PI

Hi Gurus,
how to monitor idoc and how many IDOC s come to in XI /PI ?
Regards
sreeni

Hi Sreeni,
How to monitor the idocs:
To monitor the idocs we have many transactions in R/3
we02: Gives the list of idocs based on your selection criteria
we05: Gives the list of idocs based on your selection criteria
BD87: List of idocs which are ready to be sent out of R3
SM58: If the idocs are sent out of R3 but still in the TRFC queue
Coming to XI/PI:
You can check the idoc in trnsaction IDX5 which is the idoc mionitoring tool.
How to check the count of idocs in XI/PI:
The direction of the IDOCs which are sent out of R3 is always 1. Hence if you can go to transaction we02 and give the appropriate selection parameters and select direction as 1 you would get all the IDOCs sent out of R3 to respective receivers.
Hope this helps.
Regards,
Sarvesh Desai

RWB- adapter monitoring - IDOC missing ?

Hi, I can not see IDOC adapter in adapter monitoring(RWB). when I tried to execute my scenario(File to Idoc), I got the following error.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>MI_Cremas_IA</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface MI_Cremas_IA</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
1. How do i check if IDOC adapter is running ok or not?
2. I am sure IDOC adapter is installed as I can see adapter metadata objects under http://sap.com/xi/XI/System of SAP BASIS swcv in IR. What configuration I need to do to make IDOC adapter appear in adapter monitoring(RWB) ?
3.Is above error due to problem with interface determination or receiver determination ?
Please help.

Hi,
1. File to File works fine. I just tested this.
2. File to File using BPM works fine. I just tested this.
3. File to IDOC is failing with the following error message. I have checked port and RFC destination in XI server which are working fine.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>MI_Cremas_IA</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface MI_Cremas_IA</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Does this due to any authorizations error ? Please help.
I have tested the configuration in ID which looks good except a message(sender agreement not found).
SXI_CACHE is upto date.
CPA cache refreshed successfully.
SAI_CACHE_RERESH report failed with cx_ai_cache_xms exception. How to fix this. Not sure if this is causing any cache problem.

Can't we monitor IDOC in SXMB_MONI ??

Hi All,
Can't we monitor in SXMB_MONI if the IDOC is Posted From R/3 to XI ???
What Could be the Reason
Regards
Vamsi

Hi Vamsi,
The IDOC will be in SXMB_Moni only when it is sucessfully posted to XI system.
So we monitor whether the IDOC have reached the XI by the Tcode IDX5.
If in case it as failed, it may got failed in R3 system in SM58.
Regards
Santhosh
Remember to set the thread to solved when you have received a solution
Message was edited by:
Santhosh Kumar V

Problem monitoring idoc for some interface

Hi all
I have implemented the "Business process Monitoring" to monitor 10 interfaces.
The communication is between SAP Pi and SAP ECC. SAP PI send idocs type acc_document to SAP ECC. I would to monitor the status of inbound-idoc in SAP ECC System for all interface so I have created 10 Customize Monitoring Object in SAP ECC with transaction BDMO using for the filed
u201CMessage Typeu201D acc_document. The problem is that all interfaces use acc_document so if the idoc of interface 1 generate the error this error is detect to all interface. So, how can I monitor those interfaces correctly?
Thanks a lot for collaboration

Hi Maurizio
Is it impossible to distinguish IDOC content by partner number ?
By the way, it seems you use old technique. In latest BPMon, you can use application monitor for IDoc monitoring.
In more detail, please download the document of IFMon from following link.
http://www.service.sap.com/bpm
=>Media Library
=>Technical Information about "Setup Guide - Interface Monitoring "
=>Customer Information "Interface Monitoring - Overview "
Best Regards
Keiji

Message monitor - IDOCs messages

Hi
I've created and sent IDOC messages from ERP to MII. However there is no single message found in MII. Any idea? The error message in MII is "Unknown error no messages" (something like that as I translated from German to English)
What I did checked
1. MII IDOC listener status - ok
2. ERP RFC connection -ok
But I saw error message under transaction SM58 "Error when opening an RFC connection"
Thanks for posting

Dear Seng,
I am working on MII12.1.5 build 91
I was also getting error in idoc receiving see below thread but now issue got resolved.
iDoc not received in MII
In my case iDoc sent successfully from SAP but not received in MII.
So i have created one more wrong RFC destination along with actual correct one.
then configured it in SAP NW as well as in SAP MII with same setting as i done for correct one it worked.
then i deleted the wrong RFC Destination and also deleted settings of wrong one in SAP NW and MII.
then my actual correct one is worked.
its strange but workes for me .
may i know on which MII version you are working.
Regards,
Manoj Bilthare

Monitoring IDoc Receiver Adapter

Dear experts,
in FILE -> XI -> IDoc scenarios erros are not shown correctly. Neither SXMB_MONI nor RWB shows errors for outbound status of the IDoc when I select for errors. If XI sends an IDoc to another System and the partner for the RFC connection is locked, I only see the error in SM58 or SXMB_MONI (but not in the first column... I have to scroll to the right to see the red flat in column "Outbound Status" and the flag in the first column shows me, that everything is ok).
Is it possible, to configure XI to change the overall status of the message or to show these errors in RWB? It's impractical to use different selections and tools to get all possible errors.
Thanks in advance,
David

Hi David,
Since your scenario is File to IDOC hence if XI has processed the message successfully then you will see the successful flag but as you said if you scroll to the right and there you see a red flag which is also correct behavior because the problem is at outbounding side. So check your configuration again in ID.
Few steps you can varify ....
Check the RFC password has not expired.
Make sure in your receiving system i.e R3, You have setup the partner profile correctly in WE20. Also the Port created in XI which contains the RFC (which connects to R3 system) is working fine.
Also make sure if you have uploaded the IDOC metadata using IDX2 transaction code.
if you are getting any specific error message please let us know.
Secondly it will be not possible to change the standard behvior of Moni to change the overall status of message.
Regards,
Sarvesh

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

Monitoring receiver idoc communication channel

Hi All
I have an idoc to idoc scenario.
I am unable to see my receiving idoc communication channel in communication channel monitoring of RWB. It is not available in the dropdown list.
I want to have a look at the audit log to see if the idoc is delivered to the receiving system.
How can i monitor receiver idoc communication channel?
How can i ensure that the idoc is delivered to the receiving system?
In sxmb_moni, status is checkered flag.
Many Thanks
Chandra Sekhar

Hi,
IDOC is on ABAP stack hence u can not monitor IDOC.
For testing purpose
1) GO to SXMB_MONI check the status of message.
2) Go to R3 and enter Tcode WE02 and check the IDOC which is send from XI. enter the idoc name and see the status of IDOC it should be in green status if it is posted successful or else see the status record for checking the error message.
chirag

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

Monitoring IDOC

Similar Messages

Maybe you are looking for