Monitoring of IDOC

Hello all,
I try tu have a good monitoring of IDOC.
To be clear, I will explain the problem.
We use the IDOC HRMD_ABA for the replication sap HR towards an other system CRM.
Sometimes we have some IDOC not in error but not fully posted status 52 (via transaction BD87).
The problem is : the message is not fully clear I don't know on which segment I got the error. I would like to add more information to the message, I look on customer function but I found no appropriate function => I told me why not to copy the function module [IDOC_INPUT_HRMD] for the IDOC's post into a [ZIDOC_INPUT_HRMD] function module and to manage better the message error but it looks a heavy work.
Anybody has a better idea to realise that ?
I try also to read the table EDIDS and EDID4 but the information was not helpfull.
Thank you very much in advance, Gene.

Hi Genevieve,
Yes there is a better (and much easier) way.
Go to the customer exit 002 for this specific function.
Function module = EXIT_SAPLRHA0_002.
Inside you will find: INCLUDE ZXHALU06 .
Double click on ZXHALU06 (and if it does not exist, create it by answering Yes on the create dialog).
Then simply use your coding to investigate the results and/or extend the message.
This customer exit is meant for monitoring workflow functions for this IDoc handler.
However, to copy IDOC_INPUT_HRMD to your own ZIDOC_INPUT_HRMD and extend this is not so very much work. You only need to find out with which partner the communication occurs (e.q. EDIDC-SNDPRN field).
Find this partner in transaction WE20. Indise the transaction find the message in the inbound parameters.
Double-click the partner and go to the Process code field.
Double-click the process code field and you will see that with the identification the function module IDOC_INPUT_HRMD is given.
Press the button behind the identification field and remember all fields from that screen.
Once you have copied to ZIDOC_INPUT_HRMD you can replace the identification with your function module and fill in the related fields (that you did remember).
Hope this gives you a good start.
Regards,
Rob.

Similar Messages

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

Monitoring the idoc

hi...
how can we monitor the idoc in XI.
thanks
Vishnu

Hi vishnu sreenu ,
Go thru these websites for IDoc monitoring :
Mastering IDoc Business Scenarios with SAP® XI
http://www.sap-hefte.de/download/dateien/1156/100_leseprobe.pdf
A Beginners Guide to SAP XI Settings, Part I
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/73527b2c-0501-0010-5398-c4ac372c9692
cheers!
gyanaraj
reward points if u find this helpful

Monitoring ALE/IDOC

Hi to all,
Can anybody please tell me some examples on monitoring ALE/IDOC.
Thanks in advance.
Regards
Monalisa

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).
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.
The final section explains Active Monitoring.
If you receive IDocs by qRFC, this function can monitor the inbound queue and react to any errors which occur.
Prerequisites
You post inbound IDocs with qRFC.
Features
This monitoring function displays the elements in the inbound queue:
·         Display sender
·         Selected queues
·         IDoc number
·         IDoc status
·         Link to IDoc display
You can make the following changes to a queue:
·         Flag IDocs for deletion
·         Delete IDocs from the queue
·         Start a queue
Activities
Choose Tools ® IDoc Interface/ALE ® Administration ® Monitoring ® Troubleshooting ® Monitor IDoc Inbound Queue (transaction WEINQUEUE), to go to the inbound queue monitoring.
Select the IDocs or queues which you want to monitor, using the specified selection parameters.
If an IDoc in a queue has an error status, select it and go to its detail view with the Display IDoc button, to determine the cause of the error, and resolve it.
If you cannot correct an IDoc with error status, you can delete it from the queue with the Delete IDoc from Queue button.
To edit a queue, select the queue name and choose Start Queue.
If you send IDocs by qRFC, this function can monitor the outbound queue and react to any errors which occur.
Prerequisites
You send IDocs with qRFC.
Features
This monitoring function displays the elements in the outbound queue:
·         Recipient port
·         Selected queues
·         IDoc number
·         Link to IDoc display
You can make the following changes to a queue:
·         Flag IDocs for deletion
·         Delete IDocs from the queue
·         Start a queue
Activities
Choose Tools ® IDoc Interface/ALE ® Administration ® Monitoring ® Troubleshooting ® Monitor IDoc Outbound Queue (transaction WEOUTQUEUE), to go to the outbound queue monitoring.
Select the IDocs or queues which you want to monitor, using the specified selection parameters.
If queue problems occurred in transmission, you can select IDocs and go to their detail view with the Display IDoc button, to determine their status.
You can remove IDocs from the queue with the Delete IDoc from Queue button.
To send a queue, select the queue name and choose Start Queue.
In the IDoc Administration, you can assign a procedure to a workflow task error or status code.
With the Error and Status Processing function, you can check the assignment of the error procedure codes tothe standardtasks, if you have used EDI communication in an earlierversion.
You must also maintain this assignment for your user developments.
Example
Code Type ID                    Description
EDIX   2     TS0008070        ALE/EDI: Syntax error (Outgoing)
Activities
Check whether the assignment matches the table listed below.
1. Choose SAP Menu -> Tools -> IDoc Interface/ALE -> Administration -> Runtime Settings -> Error and Status Processing (transaction WE46).
2. Perform the function. The table must contain the ALE error handling entries listed below:
Code
Task
Description
Type
EDII
TS00008068
ErrorProcInb
2
EDIO
TS00007989
ErrorMessage
2
EDIP
TS60001307
idocpaket
2
EDIX
TS00008070
SynErrorOut
2
EDIY
TS00008074
SynErrorInb
2
EDIM
TS00007988
ErrorMessage
2
The table contains the assignment of the error procedure codes (e.g. EDII) forstandardtasks (e.g. TS00008068).
The procedure type is 2 (work item).
Notes
If you used EDI in an earlier version, standard tasks ofthe old versions are still assigned here for the procedure codes EDII and EDIO. If the new tasks are not entered here, there may be ALE Processing problems.
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.
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)
Schedule Monitoring Job (Example)
Prerequisites
The following refers to the example in the section Active monitoring . The active monitoring report is to be started as a background job every morning at 8am, to evaluate the IDocs which were received between 8am and 6pm on the previous day.
Procedure
Enter the RSEIDOCA report in the BAP Editor, select Variants, and choose Display.
Give your variant a name and choose Create.
Enter the following parameters:
Recipient type: US (user)
Recipient of notification, for example SMITH
Start time or End time before batch run: 1 Day and 0 Days 14:00:00h
Critical number of IDocs: 0
Status: 51 , 56 and 64
Logical message type: ORDERS
Partner parameter (here sender):
Choose Continue to enter a short text for your variant. Save your entries.
To schedule your job as a background job, choose System ® Services ® Jobs ® Job Definition and enter B (medium priority for periodic jobs) as the job class.
Select Start condition and enter a date and 08:00 as the start time.
Choose Execute job periodically.
Choose Period values ® Daily and save your entries.
Enter the scheduled report again when saving (RSEIDOCA) and the variant that you maintained.
Result
IDocs selected during the daily run of the background job will now be:
Those which were received between 8 am and 6 pm on the previous day
Those which have the logical message type ORDERS
Those received from the relevant customer
An IDoc from status 51 , 56 or 64 must be assigned now to ensure that a notification is sent to the user SMITH.
REWARD POINTS IF HELPFUL

BPM Monitoring of IDOCs

Hello all,
I have a scenario with 100 IDOCs and I map the IDOCs in ccBPM. But if somehow a mapping process for one of the IDOCs in ccBPM goes wrong you get an error (a red flag) for all of the other 99 IDOCs.
My question is then how can we monitor which and why the IDOC went wrong without opening all of the IDOCs?
I have tried SXMB_MONI --> Process --> PE --> Technical details
But I havent found my solution.
Has anyone any suggestion?
Kind Regards,
Kamran Vakili

I checked this, It's not a solution when error's occur in the transformation step (mapping).
I have the same problem. I guess there is no solution for monitoring BPM when messages go wrong.
Anyone an idea? The only error you get from BPM when transformations goes wrong is:
com/sap/xi/tf/_mm_IDOC_Orders05_naar_Orderbestand~
com.sap.aii.utilxi.misc.api.BaseRuntimeExceptionRu
ntimeException in Message-Mapping transformatio~
Regards,
Luc
Found the solution:
Go to technical details -> scroll down to bottom -> double click on show container -> Double click on TRACE -> Double click on Value under Object Type (in my cause CL) -> Now you see what went wrong in the message and which message went wrong.
Message was edited by:
TPG TPG SAP CCC - Pink Roccade
Message was edited by:
TPG TPG SAP CCC - Pink Roccade

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

Delete monitor logs/ IDOC

Hello
We have refreshed BW Develpoment server (3.1c) from BW production server using system copy process. Now, BW development server has the logs and IDOC of BW production server. What would be the best way to remove these logs/IDOC from the BW development server.
Thanks
Amar

dear Amar,
in the monitor, psa requests are shown,
you have to delete old psa requests,
rsa1->psa->on the root node, right click 'delete psa',
here you can determine how many days backward to be deleted. further more, you can include the psa deletion in process chain.
hope this helps.
http://help.sap.com/saphelp_bw33/helpdata/en/b0/078f3b0e8d4762e10000000a11402f/frameset.htm
Activities
Choose the PSA tree in the Administrator Workbench under Modeling.
Use the context menu for an application component, InfoSource, or a PSA Table and choose Delete PSA Data. Choose Delete on a request level.
In the following screen, the DataSources for the previously chosen application component, InfoSource, PSA table, or for the request are displayed.
Use a simple mouse click in the DataSource overview to select the DataSource for which requests need to be deleted.
To help you do this, you can display a list of the requests.
Specify the number of days or a date, that you want to use as a cutoff point. All requests before this are deleted. You also have the option to specify whether you only want to delete successfully updated requests, and/or only incorrect requests, that are no longer updated in a data target (this is only valid for transaction data).
Specify the postprocessing, if necessary.
In BW 3.0, automatic process control has been enhanced and improved significantly with the concept of process chains. Controlling the process by using postprocessing events is no longer enhanced, but continues to be supported. We recommend that you only use process chains for schedules of connected processes that must be re-defined.
Schedule the delete job.
Including the deletion of requests from the PSA in the process chain
If you want to automate the deletion of requests from the PSA, you can include an appropriate process variant in a process chain.
In the maintenance of process variants, you specify the DataSource for which the requests need to be deleted by using the implicit selection of a PSA table or an InfoPackage.
Specify the requests that need to be deleted by determining the days or dates. You also have the option to specify whether you only want to delete successfully updated requests, and/or only incorrect requests, that are no longer updated in a data target (this is only valid for transaction data).
Save your entries and go back.
In the following screen, confirm the addition of the process variants in the process chain.
You arrive in the plan view for the process chain. The process variant for deleting requests from the PSA is included in your process chain.

Idoc monitoring

Dear Experts,
             Is there any report or a way to get the list of idocs in error into a file at SAP server level.
Also kindly let us know the best way to monitor the idocs in production system.
Regards,
Prasanna

Hello Prasanna
The class ZCL_IDOC just collects useful data of the affected IDoc (like the IDoc data itself, links of the IDoc to business objects, etc.).
Below I mention a few standard functions that I have added to this class:
METHOD constructor.
CREATE OBJECT me->mo_idoc_xml1    " TYPE REF TO cl_idoc_xml1
    EXPORTING
      docnum = id_docnum
    EXCEPTIONS
      error_loading_idoc = 1
      error_building_xml = 2
      others             = 3.
CASE syst-subrc.
    WHEN '0'.
    WHEN '1'.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
              WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4
              RAISING error_loading_idoc.
    WHEN OTHERS.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
      WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4
      RAISING error_building_xml.
ENDCASE.
me->md_docnum   = id_docnum.
me->md_port     = id_port.
me->md_released = id_released.
me->md_external = id_external. " external representation of outbound
me->md_include_empty_fields = id_include_empty_fields.
me->ms_control_record = me->mo_idoc_xml1->get_controlrecord( ).
CALL METHOD me->read_idoc_completely( ). " calls fm IDOC_READ_COMPLETELY
** CALL METHOD me->get_external_view_for_outbound( ).
** CALL METHOD me->process_data_records( ).
CALL METHOD me->get_next_relations( ).
call method me->get_next_neighbors( ). " calls fm SREL_GET_NEXT_NEIGHBORS
ENDMETHOD.
Instead of having multiple functions floating around I just gathered them together into a useful class.
Regards
Uwe

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 in PI

Hi Experts,
Please Help me,
Using SAP to send an IDoc directly into Gentran system, then is it possible to monitoring the status of the IDoc through WE02/WE05.
Using XI/PI to the IDoc flow to/from SAP to/from PI and then to/from Gentran,
Then also we can still be using WE02/WE05 to monitor the status of IDoc?
I needs to be clear for the following,
1) Are we using we02/we05 to monitor PI idoc's
2) what does PI monitor and How we can monitor it?
Also please suggest me How monitoring was actually done in PI?
Thanks in Advance.
Regards,
Senthil Kumar M

Hi Senthil,
You need to understand one thing that we use both PI and Gentran are middleware tools. The data is coming from SAP.
Scenario1:
SAP is connected to Gentran directly. If you want to send EDI documents then you send idocs directly to Gentran and from there it sends to your EDI partners. Now to monitor in sap we use WE02 and 05 whether they are successfully created and processed coming in and out of sap.
Scenario2:
SAP is connected to PI. Now here pi uses Seeburger adapters to send the edi documents to its trading partners. Now still from sap we use we02 and 05 to check the idocs in sap. Now once left from sap they should be in pi and we can monitor with transaction sxmb_moni for any errors on integration engine or from the seeburger Runtime work bench communicaiton cahnnel monitoring for any errors in j2ee engine.
Now it doesnot make sense to send data from sap>pi>Gentran. Because the use of PI and Gentran are same and it makes no sense to use both of them until unless you have the requirements.
You can see the very old troubleshooting guide:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283?quicklink=index&overridelayout=true
Regards,
---Satish

IDoc scenario monitoring,,,

Hi,
I have some scnerio's in whic data flows from SAP (using idoc's) - XI - POS system (File system) and vice versa.
Indeed there are some heavy data transfer involved.
NOw I have some queries and would appreciate if anyone can help me in solving them:
1. Is there any way like creating a custom/ standard report to monitor the idoc's sent sucessfully/ unsuccessfully end to end from R/3 and XI perspective.
I understand that this can be done using certain tools in XI but this report is helpful for end user, who actually triggers the scenario from SAP and POS system.
2. At times, it happens that 1-2 messages out of 5-6 messages in SXMB_MONI have green flag ( Scheduled for outbound processing) and then I have to manually go in SMQ1/SMQ2 and execute the LUW. Is there any way to avoid such occurences.
I would really apreciate if in addition to links/blogs, anyone can provide some explaination to these issue.
Thanks....

Hi,
2. At times, it happens that 1-2 messages out of 5-6 messages in SXMB_MONI have green flag ( Scheduled for outbound processing) and then I have to manually go in SMQ1/SMQ2 and execute the LUW. Is there any way to avoid such occurences.
For this goto SMQ2--Then Delete or release that Locks and now
goto SMQR Select All QueuesSay Delete
Now goto SXMB_ADMManage Queues-Say Register Queues
Regards
Seshagiri

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

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

CCMS IDOC Monitoring

HI All,
I've configured CCMS alert monitoring for IDOCs and Batch job failures. In case of any IDOC failures, in CCMS tree it just shows that there is an alert with description "Outbound: Error in IDoc interface". But it doesn't shows the details of the IDOC failure means complete Status record of the IDOC. Is it possible to display detail level IDOC display in CCMS.
with Regards

Check it via BDMO - usually Computing Center Management System (CCMS) will have Test option which may give you the detailed view of IDOC(error).
Thanks!

Monitoring of IDOC

Similar Messages

Maybe you are looking for