topic Re: monitoring ALE/IDOC in Application Development and Automation Discussions

monitoring ALE/IDOC

Former Member — Thu, 04 Oct 2007 05:43:06 GMT

Hi to all,

Can anybody please tell me some examples on monitoring ALE/IDOC.

Thanks in advance.

Regards

Monalisa

Re: monitoring ALE/IDOC

paruchuri_nagesh — Thu, 04 Oct 2007 05:51:39 GMT

status monitoring can be done by using tcode BD87

u can see status of idoc in WE05

BD84(rbdagai2)

You use this report to reprocess inbound IDocs containing errors. IDocs containing errors have one of the following statuses:

56: IDoc containing errors added

61: Continue processing despite syntax error (inbox)

63: Error passing IDoc to the application

65: Error in ALE service

When you execute this report you can specify the the IDocs to be processed according to IDoc number, creation date, time, merssage type or sender.

The 'Import in background' checkbox has the following significance:

If the checkbox is marked, the reprocessing for the selected IDocs is triggered immediately without the IDocs being displayed. A list of the IDoc status values after processing is displayed.

If the checkbox is not marked. the selected IDocs are displayed one after the other. You can then trigger the processing for each individual IDoc separately.

Output

The report outputs a list of processed IDocs containing the following information: IDoc number, message type, status after processing and a description.

BD83(rbdagain)

This report reprocesses outbound IDocs which contain errors. IDocs containing errors have one of the following statuses:

02: Error transmitting data to port

04: Error in EDI subsystem control information

05: Error in conversion

25: Continue processing despite syntax error (outbound)

29: Error in ALE service

When you execute this report you can select the IDocs for processing by specifying IDoc number, creation date, time, message type or recipient on the initial screen.

The 'Import in background' checkbox has the following significance:

If the checkbox is marked, the reprocessing of the selected IDocs is triggered immediately, without the IDocs being displayed. After processing, a list of the new IDoc status values is output.

If the checkbox is not marked. the selected IDocs are displayed one after the other. You can then trigger the processing of each individual IDoc separately.

Output

The report outputs a list of the processed IDocs containing the IDoc number, message type, status value after processing and a description.

RBDAPP01

Report for processing inbound IDocs not passed to the application immediately.

This report forwards all IDocs with:

Status 64 "ready to be passed to application"

Status 66 "IDoc is waiting for predecessor IDoc (serialization)

These match the selection criteria to be passed to the application for further processing.

Essentially there are two groups of IDocs:

IDocs to be serialized in accordance with the associated object.

All other IDocs

There are also two types of processing:

Serial processing (IDocs are processed one after each other in one process)

Parallel processing (IDocs are passed in packets to other processes for processing).

Purpose of parameter 'Packet size': For IDocs to be serialized by object and for activated parallel processing, this parameter specifies the size of a packet to be processed in a task. If applicable, independent objects are processed in a separate task as with serial processing. (Large packet sizes lowers the level of parallel processing).

For all other IDocs, as far as possible, an appropriately sized document is passed to the application. On the one hand, this supports some applications capable of mass processing. On the other hand, the number of parallel packets is less as with activated parallel processing. (Lower system load, longer runtime).

Notes on Program Terminations in Parallel Processing

In parallel processing, processes containing the IDocs to be processed are started in parallel. If there is a termination (dump/ A message), no message is issued by RBDAPP01. The best way to identify such problems is to run RBDAPP01 without parellel mode after a scheduled RBDAPP01 with parallel mode. Then a termination is logged (dialog message or message in job log).

Output

The processed IDocs are output.

RSEOUT00

Report for generation of files for EDI outbound processing.

The report processes the IDocs available in the system with the status 'to be processed'. The IDocs are selected according to the selection options and parameters specified.

It is important that you make sure that only test messages or productive messages are selected.

The IDocs are processed in various files for various output modes and for various ports. The names of the files are created according to the naming definition for the outbound file. This definition is determined in the port definition.

reward for use ful points

regards

Nagesh.Paruchuri

Re: monitoring ALE/IDOC

former_member404244 — Thu, 04 Oct 2007 05:54:19 GMT

Hi,

chek the below link..

http://help.sap.com/saphelp_nw04s/helpdata/en/dc/6b815e43d711d1893e0000e8323c4f/content.htm

reward points if helpful..

Regards,

Nagaraj

Re: monitoring ALE/IDOC

Former Member — Thu, 04 Oct 2007 06:06:36 GMT

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

EDIO

TS00007989

ErrorMessage

EDIP

TS60001307

idocpaket

EDIX

TS00008070

SynErrorOut

EDIY

TS00008074

SynErrorInb

EDIM

TS00007988

ErrorMessage

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

Re: monitoring ALE/IDOC

Former Member — Thu, 04 Oct 2007 06:08:50 GMT

HI,

here are the entire details read this

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

+reward if helpful
vivekanand
+

Re: monitoring ALE/IDOC

Former Member — Fri, 05 Oct 2007 03:08:41 GMT

Many many thanks.

Regards

Monalisa

Re: monitoring ALE/IDOC

Former Member — Fri, 05 Oct 2007 03:10:17 GMT

Many many thanks.

Regards

Monalisa

Re: monitoring ALE/IDOC

Former Member — Fri, 05 Oct 2007 03:17:34 GMT

Many many thanks.

Regards

Monalisa

Re: monitoring ALE/IDOC

Former Member — Fri, 05 Oct 2007 03:26:17 GMT

Many many thanks.

Regards

Monalisa

Re: monitoring ALE/IDOC

paruchuri_nagesh — Fri, 05 Oct 2007 03:59:36 GMT

thanks only

reward points if u find use ful

regards

Nagesh.Paruchuri