Showing results for 
Search instead for 
Did you mean: 

IDOC TO JDBC Erroe Handling

Former Member
0 Kudos



we have to send ZIDOC To ORACLE system.


Here how we can handle if it is

1. Network failure(System Errors)

2. Business Errors

There is no BPM

we decided:

IDOC data will insert into ORACLE sys uing value mapping (which is having values in IDOC and ORACLE)

my dought is if any failure in Value mappings than it will to intimate to SENDER and reciver using ALERT or MAIL.

Is this right approach ? if yes,

How can we send alert or mail? is there any documents is there?

thnx in advance



Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Kumar,

Errors like (e.g. mapping error, no reciver) are raised from the integration server.To do the same,in the runtime workbench you define the receiver of such an error in the alert configuration.

Please look at the information provided below in doing the same and see if it helps you.......

From SP 14 on PMI-free alerting was introduced. That means before SP 14 one has to configure and activate the End-to-End Monitoring, and to schedule the report SXMSALERT_PROCESS_DATA_GET in order to extract the alerts from the PMI data. For SP 14 and higher, that's not longer necessary.

If no alerts are being delivered, please check if "Suppress multiple alerts of this rule" is checked for your rule.

For SP 14 and higher you could also have a look at the report sxmsalert_logreader. This report shows some information about alerts being created or not.

You'll find more information about trouble shooting the alerting in SAP Note 913858.

Also just check if this batch program (RSALERTPROC) is running or not.

The links below on Alert Management (ALM) will be of good help to you:

<a href="">Forwarding Alerts to Alert Management (ALM)</a>

<a href="">Alert Management</a>

<a href="/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step: Alerts - Step by step</a>

<a href="/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide: Alerts - Troubleshooting guide</a>

Meanwhile look at these forum threads also:

Also go through these...


Alert Notification Step-by-Step

Alert Configuration

2) Michal's blog: XI FAQ


XI: Alerts - Troubleshooting guide


XI: Alerts - Step by step


To send an EMAIL, assign an EMAIL ID to the corresponding user in the transaction SU01 and then set up SCOT and you can send emails when the ALERT is triggered..

Once you have configure Alerts, you will get the Alerts into ALERT INBOX in RWB of the user. To also get the email, the following needs to be done,

1. In SU01 -- Assign the Email ID for the Recipient of the ALERT.

2. In , RWB>ALERT INBOX> PERSONALIZATION--> Time Independent Delivery and Email are selected.

3. Finally, SCOT needs to be set up to send Emails. Check this for the same. You can ask your BASIS team to do this step.

Also, In ALRTCATDEF, go to SETTINGS--> CONFIGURATION. By default, the option selected is INTERNAL PROCESSING. Select the option SMTP FORWARDING AS XML and give the email id. This will enable you to send an email alert whenever an error occurs in XI.

I hope this helps....



Former Member
0 Kudos

Hi kumar,

I would decide for BPM with two exception branches

- one for mapping errors

- one for system errers (e.g. Database not available)

Regards Mario

Former Member
0 Kudos

hi Mario,

I have similar problem wherein i want to catch mapping errors separately and database errors(like primary key violation/DB server down) separately.

Could you please tell me how to go about it. I already have a exception branch which handles all errors.

Active Contributor
0 Kudos

/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step -- Alerts Step by Step

take a look at this blog for Alerts. This will trigger alerts if an error occurs in any component of XI .

So, if your network goes down ( say JDBC connection fails using JDBC adapter as DB is down ) , then XI will trigger the alerts .

To send email for alerts, apart from the blog given above,


2. in Transaction su01--> assign EMAIL ID to the recipeient of the Alert.

3. Make sure SCOT is confiured.