How to handle the jdbc receiver error

hi,expert:
I have a synchornous scenario:SAP/ECC(Proxy) to JDBC(SQLServer),ECC Send the message and insert data into the database,when insert sucessfully the receiver returns the count of the sucessfull inserted record . Not use store procedure.
I have a problem: When insert into the table occurs errors,like insert Duplicated record,how can i capture this exception and return to the ECC? And if it is possible to solve this problem by using fault message?
wait for reply ,thanks!

Have you identified why duplicate record error coming?? you dont want to insert duplicate records in DB?? then in this case you contraol sending data in Proxy it self,
If you want response (error message or success status from Data base you can design/develop easily, JDBC recv will support syn communication.
even you can go for fault message type to handle this error,
http://help.sap.com/erp2005_ehp_04/helpdata/EN/dd/b7623c6369f454e10000000a114084/content.htm
Regards,
Raj

Similar Messages

How to handle the 500 Internal Server Error + ADF

Hi,
How to handle the 500 Internal error ADF application? I tried with giving the error page in web.xml but it does not work
Please advice

i'm not sure if this is related, but we also have the following in the web.xml file
<filter-mapping>
<filter-name>adfFaces</filter-name>
<url-pattern>*.jsp</url-pattern>
<dispatcher>REQUEST</dispatcher>
<dispatcher>ERROR</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>adfFaces</filter-name>
<url-pattern>*.jspx</url-pattern>
<dispatcher>REQUEST</dispatcher>
<dispatcher>ERROR</dispatcher>
</filter-mapping>

Error handling at JDBC Receiver

Hi,
I am currently working on PI 7.31. This is regarding proxy to JDBC scenario using insert statement in the JDBC receiver. I would like to know is there any feature in JDBC receiver which allows the process to continue even after any data error in the insert statement by skipping the error records and finally collecting all error records and sending through alert configuration to the administrator. Currently process stops whenever any error happens in insert statement at JDBC receiver.
Regards,
Rama.

Hello,
I would suggest you to go with SP.
By default, PI will handle the transaction and in case of any errors it will rollback the entire statement. So u can allow SP to handle the transactions by asking ur DB team to create a SP with a try/catch statement and in case of any errors while performing DML operations catch those exceptions and log those erroneous records in some exception log table and continue the SQL process.
Eventually, either using SQL mailer or some windows services u can send a consolidated mail to the stakeholders. Just check with ur DB team since these are very normal stuff so i am quite sure ur DB admin would certainly help u on the same.
Thanks
Amit Srivastava

How to handle the #error in ssrs expression

hi
Please any one help me to resolve this #error ,
I have a calculated filed in that expression i given a if condition like below
data of column is coming like this 0 , 0.0
=IIF(Fields!Column1.Value=0,0,((Fields!Column2.Value - Fields!Column1.Value)/( Fields!Column1.Value)))
how to handle the #error
Please let me know any one

Hi deepuk23,
According to your description, when you use the IIF() function in the report you got some error,right?
The issue can be caused by the column1 and column2 have different datatype, I assumed that one is integer and another is float, when the Column1 is 0 or null, because IIF() function always evaluates both the true part and the false part, even
though it returns only one of them, it will throw out the error.
To resolve the issue, you should use a nested IIF() function to avoid the zero-divisor in any rate like below:
=IIF(Fields!Column1.Value=0,0,((Fields!Column2.Value - Fields!Column1.Value)/(IIF(Fields!Column1.Value=0,1,Fields!Column1.Value))))
For more information, please refer to this article:
FAQ: Why does the “Attempted to divide by zero” error still happen?
If you still have any problem, please feel free to ask.
Regards,
Vicky Liu
Vicky Liu
TechNet Community Support

How to handle the errors in transformations

Hi
I am using SOA, JDev 10.1.3.3.
How to handle the exceptions in transformations.
If any thing goes wrong in transformation then how to handle that situation.
I am not getting any kind of instances like errored out..
Please help me out
Regards
Pavankumar

I think your issue is that your process is going into manual recovery.
In the console click on the tab BPEL processes. There is a link on the left for manual recovery. Do you see your processes there?
What happens if you put your transformation into a scope. The in that scope you have a catch All. In this catch All routine just do a terminate. This will error your process but you should see it appear in the console.
cheers
James

How to handle the error handling..its urgent

hi guys...
how to handle the Exception using jsf. for example...in java program we try to connect the server...if server not connect then the exception occur like java.net.ConnectException.. i have to handle exception using jsf and display related error page...plz give me ur valuable words..its need is very urgent..
advance thanx and with regards
DJ

Hi,
1. create a new error bundle (myErrMsg) // copy from javax/faces/Messages.properties in jsf-impl.jar
2. declare this bundle in your faces-config
<application>
<message-bundle>bundle.MyErrMsg</message-bundle>
<locale-config>
<default-locale>en</default-locale>
<supported-locale>de</supported-locale>
<supported-locale>fr</supported-locale>
</locale-config>
</application>
3. handle the Exception in your backing bean
ResourceBundle bdle = ResourceBundle.getBundle("bundle.MyErrMsg",this.getLocale());
context.addMessage(clientId, new FacesMessage(severity, bdle.getString(key), null));
4. add the tag messages in your jsp
<h:messages layout="table" errorClass="TextError" infoClass="Text"/>

How to handle the errors using RSRV tcode

Hi all,
Could any one give tell me how to handle the errors,(if possible give me some example errors)and correct the errors using RSRV tcode.
Thanks & Regards,
Aswini.

Hello Aswini,
For further details on RSRV go through the link:
http://help.sap.com/saphelp_nw04/helpdata/en/92/1d733b73a8f706e10000000a11402f/frameset.htm
Hope it helps
Cheers
SRS

JDBC receiver error urgent

Hello Friends,
I am using file to JDBC scenario.
i am getting following errors in the JDBC receiver though i have set all the parameters correctly.
the same scenario is working when i used XI server but it is giving errors when i am connecting to remote server.
i used sun.jdbc.odbc.JdbcOdbcDriver driver for the same.
Error when attempting to get processing resources: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: DriverManagerException: Cannot establish connection to URL 'jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//bomwsap020/sugeet/AIP/DATABASE/Flight.mdb': SQLException: [Microsoft][ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot open the file '(unknown)'. It is already opened exclusively by another user, or you need permission to view its data.
Please help on this.
thanks in advance.
Best Regards,
Sugeet.

hi Sugeet
first check whether your user has the right to access Data base
Then check whether you have deployed the drivers correctly
You have to deploy the required JDBC drivers for the database before making connection. Ask the database provider or your vendor for the drivers That should be deployed using SDM tool
Start visual admin of XI and select service "Deploy" and then select option "Deploy and start" to select file and deploy it
Three option available:
1. Using SDM
2. Using Visual Admin
3. Using NW development studio (Not available for Production)
We will use Visual Admin u201CDeployu201D deploy service to deploy
Steps:
1. Goto VM->Deploy service
2. Select option u201CDeploy and startu201D
3. Select EAR file provided for deployment
4. Restart the service.
5. Done
follow this guide on how to install external libs for JMS/JDBC
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/how%20to%20install%20and%20configure%20external%20drivers%20for%20jdbc%20and%20jms%20adapters.doc
regards
Sandeep
If helpful reward points

Calling stored procedure multiple times in the JDBC receiver

Hi,
I am calling the stored procedure(SP) to update a DB table in the JDBC receiver.
SP has 10 input parameters, and SP can receive one value for each parameter at a time.
In my case, i will have multiple rows to insert using SP.i.e multiple values for each parameter.
Its working correctly for a single value for each parameter, but when i have multiple values i want to call the SP multiples times.
Is this possible and how?
Thanks,
Varghese.

Varghese,
I think you can have multiple statements in the JDBC Adapter's XML, as in http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm.
Here the StatementName1 node can be inserted into your JDBC XML as often as you want.
Kind regards,
Koen

How to handle the control records in case of file to idoc scenario.

Hi All,
can you please clarify me how to handle the control records in case of file to idoc scenario.

Hi,
In File to Idoc scenario even though you selected apply control record values from payload and you are not getting those correct values which you have provided in the mapping.
Also check the checkboxes Take sender from payload and Take receiver from payload along with the Apply control record values from payload checkbox
Regards
Seshagiri

How to handle the extended vo in the extended controller

Hi,
I want to know how to handle the extended vo attributes in the extended controller.
I extended CompetenceElementsVO as 'CompetenceElementsEx' with 2 transient attributes called col1 and col2.
Here i want to pass value according based on some condition. for this i want to know how to handle these attributes.
I tried by using the extended vo name in the controller, if i use means then it is throwing error after the extended controller is implemented.
Same time if i try to refer this attributes from the original vo definition, jdev itself showing error.
please tell me how to handle this?
Thanks in advance,
SAN

Hi San,
You have to extend the controller where your region is associated with,
And in that controller you get the AM(if there is more than one AM and your VO is associated with a child AM, first you have to get your required AM) and then
get the ViewObject(standard).
Then you should be able to get your newly added attributes.
Please find the below sample code to get the AM handle and VO from there, update the code according to your requirement,
     Get all the VOs under the Root AM
     writeLog(pageContext, "Room AM"+ pageContext.getRootApplicationModule());
String[] rootViewNames = pageContext.getRootApplicationModule().getViewObjectNames();
/* writeLog(pageContext," Length of the VOs from Rootm AM "+rootViewNames.length);
for (int j =0 ;j<rootViewNames.length ;j++ )
writeLog(pageContext,j +" Value "+rootViewNames[j]);
     // Get requested AM from Root am
public OAApplicationModule getRequestedAM(OAPageContext pageContext, String requestedAMName)
writeLog(pageContext,"Requested AM called to check the AM "+requestedAMName );
String amName = "";
String objectivesAMName = requestedAMName;//"ObjectivesAM";
String nestedAMArray[] = pageContext.getRootApplicationModule().getApplicationModuleNames();
pageContext.writeDiagnostics(this,"Root AM=>"+pageContext.getRootApplicationModule().getName() + " Child AMs=>"+ nestedAMArray.length,1);
OAApplicationModule currentAM = null;
currentAM = (OAApplicationModule)pageContext.getRootApplicationModule();
for(int i = 0; i < nestedAMArray.length; i++)
amName = nestedAMArray;
pageContext.writeDiagnostics(this,"Nested AM Name=>"+amName + "and amName.indexOf(objectivesAMName) "+amName.indexOf(objectivesAMName),1);
currentAM = (OAApplicationModule)pageContext.getRootApplicationModule().findApplicationModule(amName);
                    //Get the view names
               String[] viewNames = currentAM.getViewObjectNames();
for (int i =0 ;i<viewNames.length ;i++ )
writeLog(pageContext,i +" Value "+viewNames[i]);
if(!(amName.indexOf(objectivesAMName)==-1))
pageContext.writeDiagnostics(this,"Found Handle to My Nested AM " + amName ,1);
break;
return currentAM;
Get the VO from the AM
OAViewObject objAssessmentVO = (OAViewObject)yourAM.findViewObject("yourVO");
Thanks.
With Regards,
Kali.
OSSi.

How to cancel the No receiver found messages in XI

Hi Experts,
Could you please help me here, how to cancel the no receiver found error messages in XI?
I have tried to cancel it , but it is not working. Please let me know know the process?
Thanks in Advance.
Best Regards,
Madhu.

Hi,
If the error message is of red flagged, then you can cancel the message.
You can use the report 'RSXMB_CANCEL_MESSAGES' to cancel the error messages.
If the message is of synchronous, it cannot be cancelled.
Thanks,
Kanda

How to handle the Timestamp datasource while migration

Hi All
" I tried searching the forum,but didnt get the relevant one,hence posting this question".
While migration from 4.7 to ECC in R/3 system,
how to handle the Timestamp datasources( especially FI like COPA and other ) while extarcting the data from source to BW during source system migration.Since we need to empty the delta queue and should make sure that there are no delta records exists in delta queue.
Like for sales datasources using LO,we will be executing the V3 jobs for execting the LUW's from LBWQ to RSA7? In the same way is there any particular way for this also.
Anyone whi knows abt this pls share your views
Regards
Shankar

Hello Shankar.
Before the upgrade (import of a queue), all extraction queues and open
update orders in all clients must be processed. The content of the setup
tables must be deleted. To avoid problems during the upgrade or to
correct them, carry out the following steps:
1. Call transaction SMQ1 and check whether all queues in all clients
(client = '', queue name 'MCEX') have been processed. To process the
queues, start the collective run report for each application in the
displayed clients. If you no longer need the data in the BW system,
deactivate the relevant extraction queues and DataSource in the LO
cockpit (transaction LBWE) and delete the queue entries in transaction
SMQ1.
2. If you use the V3 update that is not serialized (usually only for
application 03): Start collective run report RMBWV303. Then check the
update orders in transaction SM13. If there are incorrect update orders
in transaction SM13, correct the orders and then start the collective
run report again. If you no longer require the update orders, you can
delete them. There may be inconsistencies between tables VBMOD and
VBHDR. For further information about this, see Notes 652310 and 67014.
3. Before the upgrade, delete the contents of the setup tables. Execute
report RMCEX_SETUP_ENTRIES to find out which setup tables still contain
entries. You can use transaction LBWG to delete the contents of the
setup tables for all clients.
Unfortunately the check that the system carries out during the upgrade
or when you import a Support Package does not display all affected
applications. Therefore, Note 1083709 provides a check report that you
can use to determine all affected applications and tables or queues.
More detailed information please check these following notes:
1083709-Error when you import Support Packages
1081287-Data extraction orders block the upgrade process
I hope I can be helpful.
Thanks,
Walter Oliveira.

How to handle the messages.

Hi,
I am doing interactive report. In that how to handle the error meesages.
Regards
Srinu

HI
IF YOU WANT HANDLE THE ERROE MESSAGES
*& Report ZNNR_REPORT
REPORT ZNNR_REPORT NO STANDARD PAGE HEADING <b>MESSAGE-ID ZNNR</b> LINE-SIZE 100 LINE-COUNT 65(4).
******DATA DECLARATIONS**********
DATA : BEGIN OF IT_PLANT OCCURS 0,
        MATNR LIKE MARA-MATNR,
        WERKS LIKE MARC-WERKS,
        PSTAT LIKE MARC-PSTAT,
        EKGRP LIKE MARC-EKGRP,
       END OF IT_PLANT.
DATA : BEGIN OF IT_PONO OCCURS 0,
        EBELN LIKE EKKO-EBELN,
        EBELP LIKE EKPO-EBELP,
        MATNR LIKE EKPO-MATNR,
        WERKS LIKE EKPO-WERKS,
        LGORT LIKE EKPO-LGORT,
       END OF IT_PONO.
TABLES EKKO.
********END OF DATA DECLARATIONS*********
********SELECTION SCREEN DESIGN ***********
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
PARAMETER : P_WERKS LIKE MARC-WERKS MODIF ID S1.
SELECT-OPTIONS : S_EBELN FOR EKKO-EBELN NO INTERVALS MODIF ID S2.
SELECTION-SCREEN END OF BLOCK B1.
SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-004.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS : R1 RADIOBUTTON GROUP G1 DEFAULT 'X'.
SELECTION-SCREEN COMMENT 5(20) TEXT-002 FOR FIELD R1.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS : R2 RADIOBUTTON GROUP G1.
SELECTION-SCREEN COMMENT 5(20) TEXT-003 FOR FIELD R2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK B2.
******END OF SELECTION SCREEN DESIGN****************
*********INITIALIZATION OF SELECTION SCREEN ELEMENTS.*****
INITIALIZATION.
P_WERKS = '1000'.
S_EBELN-LOW = '4500016926'.
S_EBELN-OPTION = 'EQ'.
S_EBELN-SIGN = 'I'.
APPEND S_EBELN.
CLEAR S_EBELN.
************END OF INITIALIZATION***********************
***********SCREEN MODIFICATIONS*******************
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN.
    IF R1 EQ 'X' AND SCREEN-GROUP1 EQ 'S2'.
      SCREEN-INPUT = 0.
      MODIFY SCREEN.
    ENDIF.
    IF R2 EQ 'X' AND SCREEN-GROUP1 EQ 'S1'.
      SCREEN-INPUT = 0.
      MODIFY SCREEN.
    ENDIF.
ENDLOOP.
********END OF SCREEN MODIFICATIONS*****************
***************SCREEN VALIDATIONS *****************
at selection-screen.
SELECT SINGLE *
           FROM EKKO
           INTO EKKO
           WHERE EBELN IN S_EBELN.
IF SY-SUBRC <> 0.
    SET CURSOR FIELD 'S_EBELN-LOW'.
    <b>MESSAGE E999 WITH TEXT-005</b>.
ENDIF.
********end of screen validation*****************
START-OF-SELECTION.
*set pf-status '100'.
IF R1 EQ 'X'.
    SELECT MATNR
           WERKS
           PSTAT
           EKGRP
       FROM MARC
       INTO TABLE IT_PLANT
       WHERE WERKS = P_WERKS.
    LOOP AT IT_PLANT.
      WRITE : SY-VLINE , 2 IT_PLANT-MATNR COLOR COL_KEY,
             21 SY-VLINE , 22 IT_PLANT-WERKS COLOR COL_KEY,
             27 SY-VLINE ,28 IT_PLANT-PSTAT COLOR COL_NORMAL,
             43 SY-VLINE ,44 IT_PLANT-EKGRP COLOR COL_NORMAL.
    ENDLOOP.
ENDIF.
IF R2 EQ 'X'.
    SELECT EBELN EBELP MATNR WERKS LGORT
           FROM EKPO
           INTO TABLE IT_PONO
           WHERE EBELN IN S_EBELN.
    LOOP AT IT_PONO.
      WRITE : SY-VLINE , 2 IT_PONO-EBELN COLOR COL_KEY,
             12 SY-VLINE , 13 IT_PONO-EBELP COLOR COL_KEY,
             18 SY-VLINE , 19 IT_PONO-MATNR COLOR COL_NORMAL,
             37 SY-VLINE , 38 IT_PONO-WERKS COLOR COL_NORMAL,
             44 SY-VLINE , 45 IT_PONO-LGORT COLOR COL_NORMAL, 49 SY-VLINE..
    ENDLOOP.
ENDIF.
TOP-OF-PAGE.
IF R1 EQ 'X'.
*ULINE AT /1(48).
    WRITE : SY-VLINE ,2 'MATERIAL NUMBER',
            21 SY-VLINE , 22 'PLANT',
            27 SY-VLINE , 28 'STATUS',
            43 SY-VLINE , 44 'GRUP', 48 SY-VLINE.
    ULINE AT /1(48).
ENDIF.
IF R2 EQ 'X'.
    WRITE : SY-VLINE , 2 'PO NUMBER',
           12 SY-VLINE, 13 'ITEM',
           18 SY-VLINE,19 'MATERIAL NUMBER',
           37 SY-VLINE, 38 'PLANT',
           44 SY-VLINE, 45 'GRUP',
           49 SY-VLINE.
    ULINE AT /1(50).
ENDIF.
END-OF-PAGE.
ULINE AT /1(50).
WRITE :/10 'PAGE NUMBER', SY-PAGNO.
WRITE THE CONDITION WHAT EVER YOU WANT TO CHECK AND IF THAT IS TRUE SY-SUBRC = 0 THEN NO MESS IF NE 0 THEN RAISE A ERROR MESSAGE LIKE ABOVE
REWARD IF USEFULL

How to handle the bad record while using bulk collect with limit.

Hi
How to handle the Bad record as part of the insertion/updation to avoid the transaction.
Example:
I am inserting into table with LIMIT of 1000 records and i've got error at 588th record.
i want to commit the transaction with 588 inserted record in table and log the error into
error logging table then i've to continue with transaction with 560th record.
Can anyone suggest me in this case.
Regards,
yuva

>
How to handle the Bad record as part of the insertion/updation to avoid the transaction.
>
Use the SAVE EXCEPTIONS clause of the FORALL if you are doing bulk inserts.
See SAVE EXCEPTIONS in the PL/SQL Language doc
http://docs.oracle.com/cd/B28359_01/appdev.111/b28370/tuning.htm
And then see Example 12-9 Bulk Operation that continues despite exceptions
>
Example 12-9 Bulk Operation that Continues Despite Exceptions
-- Temporary table for this example:
CREATE TABLE emp_temp AS SELECT * FROM employees;
DECLARE
TYPE empid_tab IS TABLE OF employees.employee_id%TYPE;
emp_sr empid_tab;
-- Exception handler for ORA-24381:
errors NUMBER;
dml_errors EXCEPTION;
PRAGMA EXCEPTION_INIT(dml_errors, -24381);
BEGIN
SELECT employee_id
BULK COLLECT INTO emp_sr FROM emp_temp
WHERE hire_date < '30-DEC-94';
-- Add '_SR' to job_id of most senior employees:
FORALL i IN emp_sr.FIRST..emp_sr.LAST SAVE EXCEPTIONS
UPDATE emp_temp SET job_id = job_id || '_SR'
WHERE emp_sr(i) = emp_temp.employee_id;
-- If errors occurred during FORALL SAVE EXCEPTIONS,
-- a single exception is raised when the statement completes.
EXCEPTION
-- Figure out what failed and why
WHEN dml_errors THEN
errors := SQL%BULK_EXCEPTIONS.COUNT;
DBMS_OUTPUT.PUT_LINE
('Number of statements that failed: ' || errors);
FOR i IN 1..errors LOOP
DBMS_OUTPUT.PUT_LINE('Error #' || i || ' occurred during '||
'iteration #' || SQL%BULK_EXCEPTIONS(i).ERROR_INDEX);
DBMS_OUTPUT.PUT_LINE('Error message is ' ||
SQLERRM(-SQL%BULK_EXCEPTIONS(i).ERROR_CODE));
END LOOP;
END;
DROP TABLE emp_temp;

How to handle the jdbc receiver error

Similar Messages

Maybe you are looking for