Error handling in ABAP proxies

Hi,
Please let me know the different ways by which error handling can be done (both at XI side and also the SAP R/3 side) in the case of ABAP inbound and outbound proxies.
Basically
1. In the case of message posting to SAP R/3 using ABAP proxy (Inbound to SAP), how errors generated in SAP can be monitored/notified and sent back to source system or XI system
2. In the case of proxy message being received by XI, from SAP, if errors are generated in SAP (before posting), how the errors can be monitored and notified.
Your early response is appreciated.
Regards
Venkat

Hi,
The error can happen due to application error, may be incorrect data or or wrong type of data.
Or system error, in case the call to SAP XI is not successful.
Youc an use fault message for the same.
If you want to catch these exceptions in SAP itself and send alert then you can either use standard FM for raising alert.
More here:
http://help.sap.com/saphelp_nw04/helpdata/en/25/a45c3cff8ca92be10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/a1/082589fc4246f09793039d5fb01a17/content.htm
First configure CCMS in XI System:-
/people/sap.user72/blog/2005/11/24/xi-configuring-ccms-monitoring-for-xi-part-i
For Monitoring in the CCMS:-
http://help.sap.com/saphelp_nw04/helpdata/en/4d/6272376d3bfa2be10000009b38f8cf/frameset.htm
Go thro' this link for configuration scenario:-
/people/aravindh.prasanna/blog/2005/12/23/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part--1
Inbound ABAP Proxy Trace and error handling
Handling Exceptions
ABAP Server Proxies - Fault Handling
Exception handling in integration processes
ABAP Proxy and fault messages
/people/bhanu.thirumala/blog/2006/02/07/abap-proxy--xml-to-abap-transformation
regards
Aashish Sinha
PS : reward points if helpful

Similar Messages

Error handling in abap proxy

Hi,
In my scenario, I have written code in the execute_synchronous method of the abap proxy in ECC. I want to capture all possible errors that might occur here and for all of them i want to capture the message id and the text and send it out. what kind of possible errors/exceptions can occur and how to handle them. My proxy class simply selects data from multiple tables in ECC and returns the same.
thks

Hi,
for outbound proxies the error handling should be done within R3 itself and there is no need to send errors to XI or receiving system for that matter. You would want someone from R3 side to take a note of it.
For Inbound proxies, you will have to implement the Fault messages
Fault message types are designed for application-specific errors that occur on the inbound side and that are reported back to the sender or persisted in monitoring.
· In the synchronous case, when an application-specific error occurs on the inbound side, instead of sending a response message back to the sender, the application can send a fault message to handle the error.
· The fault message of the application for an asynchronous ABAP server proxy is persisted for monitoring. In the case asynchronous of Java server proxies, the fault message is part of a negative application acknowledgement (see Acknowledgments).
Application-specific means that the application on the inbound side triggers the error itself because, for example, the request message did not contain sufficient information.
For more information on the same.
http://help.sap.com/saphelp_nw04s/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
In your case, since you said that you are selecting data from some tables, the possibility is that an entry is not found in the DB tables you will have to simply populate the fault message data and raise an expection CX_FM. It also depends on what error handling requirements from the Business .
regards,
Advait.

Error Handling for ABAP Proxy sender

Hello Everyone,
I am trying out a scenario of SAP R/3 to Oracle database (ABAP Proxy to JDBC).
I have the following code and it works fine.
CALL METHOD prxy->execute_asynchronous
      EXPORTING
        output = it.
     commit work
CATCH cx_ai_system_fault .
    DATA fault TYPE REF TO cx_ai_system_fault .
    CREATE OBJECT fault.
    WRITE :/ fault->errortext.
I know that the above Catch block would be used to handle system errors on the sender side.
Please tell me what kind of errors could these be and what I can do to test these errors. ie. I want to create error situations explicitely and see how they are handled.
Thanks and Regards,
Ashwin

Thanks guys, this was useful.
My scenario is for Asynchronous communication.
I guess Fault messages are used in case of Synchronous communication for handling application errors. So if there was something wrong at the JDBC end then I could use the fault messages.
Have i got this right?
I also came across this piece on Acknowledgements. But is says that they can be used with the following Receivers:
The following receivers support acknowledgments:
ABAP and Java proxies (XI 3.0 SP1 for the latter)
Integration processes
IDocs (note that IDocs only return acknowledgments when they have been configured using the ALE audit)
Receiver adapters support system acknowledgments but not application acknowledgments
My Receiver is JDBC. So I guess I cannot use acknowledgements either.
Hence, I need to know what I can do to replicate the system errors eg. failed server etc...so that I can get catch these errors during sending.
I'll tell you abt what happened earlier.
My XI server was down. I executed the code for the sender ABAP Proxy and it did not catch the error. In SXMB_MONI in the R/3 system, I could see the messages queued up. When the XI server started, the messages were transferred to XI.
I need to handle such errors...ie. If the server is down or message did not reach XI then my ABAP program that sends data via ABAP proxy needs to know that something went wrong.
Thanks and Regards,
Ashwin

Error Handling in ABAP

Dear All,
How to handle errors in ABAP.
Thanks in Advance
Arun

REPORT ZTEST
PARAMETERS number TYPE i.
DATA: result TYPE p DECIMALS 2,
      oref TYPE REF TO cx_root,
      text TYPE string.
TRY.
    IF ABS( number ) > 100.
      RAISE EXCEPTION TYPE cx_demo_abs_too_large.
    ENDIF.
    PERFORM calculation USING    number
                      CHANGING result
                               text.
CATCH cx_sy_arithmetic_error INTO oref.
    text = oref->get_text( ).
CATCH cx_root INTO oref.
    text = oref->get_text( ).
ENDTRY.
IF NOT text IS INITIAL.
WRITE / text.
ENDIF.
WRITE: / 'Final result:', result.
FORM calculation USING    p_number LIKE number
                 CHANGING p_result LIKE result
                          p_text   LIKE text
                          RAISING cx_sy_arithmetic_error.
DATA l_oref TYPE REF TO cx_root.
TRY.
      p_result = 1 / p_number.
      WRITE: / 'Result of division:', p_result.
      p_result = SQRT( p_number ).
      WRITE: / 'Result of square root:', p_result.
    CATCH cx_sy_zerodivide INTO l_oref.
      p_text = l_oref->get_text( ).
    CLEANUP.
      CLEAR p_result.
ENDTRY.
ENDFORM.

Error handling in Abap Class for SAP Workflow

Hi Experts,
I would like to know if we have an option in abap classes used in workflows to send errors to the workflow log. We can achieve this in BOR Object methods by using the EXIT_RETURN <CODE> var 1 var 2 to send the errors back to the workflow, but how is this achieved through methods from classes used in workflows.
Appreciate your quick responses,
Chaitanya

Just raise exceptions in the normal OO way. Any exception that is a subclass of CX_BO_ERROR should be automatically available in workflow. Use subclasses of CX_BO_TEMPORARY for temporary errors.

ABAP Mapping for Error handling in Proxy to JDBC

Hi All,
I am working on a proxy to jdbc scenario in which we have to throw validation errors to NWPM(Net Weaver Process Monitor Tool)
I am following the below steps,
step 1 - In message mapping a UDF is created to catch errors and store them in a variable using dynamic configuration
step 2 - writing abap mapping for handling this thrown exception and im reading the dynamic configuration in the abap class and raising exception. The exception format expected is
SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1>ZPI_THROW_EXCEPTION</SAP:P1>
<SAP:P2>001</SAP:P2/>
<SAP:P3>Mandatory field is missing[BUKRS] </SAP:P3>
 <SAP:AdditionalText />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have written the following ABAP code to achieve this:
method IF_MAPPING~EXECUTE.
DATA l_record type mpp_dynamic.
DATA error type String.
getting dynamic configuration value
filled in by any previous mapping
CALL METHOD DYNAMIC_CONFIGURATION->GET_RECORD
EXPORTING
 NAMESPACE = 'http://sap.com/xi/XI/System/ERROR'
 NAME = 'ERROR'
RECEIVING
 RECORD = l_record.
error = l_record-value.
*raising exception with our message
RAISE EXCEPTION TYPE CX_MAPPING_FAULT
EXPORTING
 TEXTID =
 PREVIOUS =
 ERROR_CODE = '001'
 ERROR_TEXT = error .
RAISE EXCEPTION TYPE CX_MAPPING_FAULT
EXPORTING
 TEXTID =
 PREVIOUS =
 ERROR_CODE = '003'
 ERROR_TEXT = error .
endmethod.
I am gettign the following message for our code:
SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Could you please help in finding the solution for getting currect error message from ABAP class?
Edited by: SwethaC on Jan 21, 2011 8:18 AM

The error is due to RFC Call fail from PI system to your ECC Application System.
Check your RFC Destination for ECC System type 3 in PI System.
When you are receiving data from ECC System using Proxies & again you are going to ECC System for Validation.
Why you are not doing this validation on ECC System only in your proxy code ?
In your proxy code, it will be much better for performance to check your data there on same system.

Client ABAP proxy error handling. Please help!

Hi Experts,
   I have following scenario:
   SAP ECC (ABAP Client Proxy) -> PI(XI)-->(SOAP) Third party web service System
   This is Asynchronous.
   What will happen when ABAP client Proxy in ECC sends data to PI but PI is down?
   Will the message be queued in ECC? Can the queued message be processed automatically when PI is UP later?
   Please help.
Thanks & Regards
Gopal

Hello Gopal,
Correct, it should be an automatic entry into the queue!
refer below for a detailed understanding!
/people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies     XI: Reliable Messaging u2013 EOIO in ABAP Proxies
/people/krishna.moorthyp/blog/2005/12/23/monitoring-for-processed-xml-messages-in-abap-proxy     Monitoring for Processed XML messages in ABAP Proxy
Weblog to send Response from RFC to File in Asyn Mode Using Proxy [original link is broken]     Weblog to send Response from RFC to File in Asyn Mode Using Proxy
/people/michal.krawczyk2/blog/2009/06/20/pixi-abap-proxies-say-goodbye-to-executeasynchronous-method     PI/XI: ABAP Proxies say goodbye to Execute_Asynchronous method
/people/krishnakumar.ramamoorthy3/blog/2008/11/02/error-handling-framework-for-abap-proxies--part-1     Error handling framework for ABAP proxies - Part 1
/people/krishnakumar.ramamoorthy3/blog/2008/12/19/error-handling-framework-for-abap-proxies--part-2     Error handling framework for ABAP proxies - Part 2
Regards,
Jilan

Proxies - Queueing and Error handling features ???

My understanding is that you can have synchronous and asynchronous proxies. Do proxies have a queueing mechanism, and do they provide reprocessing and error handling features ???
Thanks in advance.

Hi,
The error can happen due to application error, may be incorrect data or or wrong type of data.
Or system error, in case the call to SAP XI is not successful.
Youc an use fault message for the same.
If you want to catch these exceptions in SAP itself and send alert then you can either use standard FM for raising alert.
More here:
http://help.sap.com/saphelp_nw04/helpdata/en/25/a45c3cff8ca92be10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/a1/082589fc4246f09793039d5fb01a17/content.htm
First configure CCMS in XI System:-
/people/sap.user72/blog/2005/11/24/xi-configuring-ccms-monitoring-for-xi-part-i
For Monitoring in the CCMS:-
http://help.sap.com/saphelp_nw04/helpdata/en/4d/6272376d3bfa2be10000009b38f8cf/frameset.htm
Go thro' this link for configuration scenario:-
/people/aravindh.prasanna/blog/2005/12/23/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part--1
Inbound ABAP Proxy Trace and error handling
Handling Exceptions
ABAP Server Proxies - Fault Handling
Exception handling in integration processes
ABAP Proxy and fault messages
/people/bhanu.thirumala/blog/2006/02/07/abap-proxy--xml-to-abap-transformation
regards
Aashish Sinha
PS : reward points if helpful

How ABAP proxies will be able to handle attachements

how ABAP proxies will be able to handle attachements.
my attachment in byte array format

thax abhishek ,
the like lets about sending the message as an attachment, can u help me out, after receiving an attachment in abap proxy, what are steps need to be done in abap proxy.
is there necessary that the receiver transport protocol should be HTTPS 1.0

Error Handling in XI3

Hi all,
I am new to XI. Can anyone guide me how to handle error in XI. To elaborate more, if we use asynchronous or syncronous scenarios and if there are any problems or errors during execution of those scenarios, how to handle that?
thanks,
KP

Hi,
first you have to distinguish between error handling in the applications and monitoring. As writen before, there is the CCMS and the alerting functions of the XI Runtime Workbench for the monitoring.
The error handling differs in synchronous and asynchronous scenarios and by the adapters you use. If you are using proxies (ABAP or JAVA) the receiver application can raise an exception. In a synchronous scenario the exception is transported by XI to the sender and a exception is raised there too. You can define different exceptions in the XI repository and add datatypes for specific error data. These fault messages are assigned to an interface and exception classes are generated for the proxies. Unfortunately most adapters don't make it that easy. In RFCs you can use the message structure sy-msgid, sy-msgty, sy-msgno and sy-msgv1 to sy-msgv4. It depends on the adapters what is possible.
If you are in an asynchronous world, there is no return message to the sender. If a receiver proxy raises an exception, you can see the exception in the inbound monitoring (SXMB_MONI or MessagingSystem) of the receiver system. Then you can use the error monitoring via ccms or alerting, to monitor and report the errors to the operating.
Another way is to use Acknowlegments to send back the status of the process. In this case you don't handle errors, but send back success messages. If the success messages is not coming back, you know there is a problem. but you need to keep track of your outgoing messages.
Notice, that if you use the XI messsaging (standard functionality) for error messages, you can not report errors, if the messaging system is broken down. CCMS is working parallel, and low level, to the messaging functionality of XI and can operate, even if XI is not working. It may be good to have a seperate monitoring server like SAP Solution Manager.
Regards,
Christian

Forward Error Handling - File interfaces?

Hello Experts,
Can we use Forward Error Handling (FEH) for implementing error handling in File Interfaces ?
Like for simple Application Server file interfaces, if something goes wrong during the process of writing/reading a file on App Server, can we use FEH for showing the log?
I know it is a concept used for PI...so we want to know if it can be used for file interfaces as well? Just want to keep similar approach for error handling and logging (for both PI and File Interfaces).
Thanks.

Edit 1 May 2015: Added inbound
Just a slight correction.
FEH is used in the ABAP backend systems and are only for asynchronous inbound proxy interfaces. It is not available for sync proxies, IDocs, BAPIs. Neither is it available for any error handling on the PI system itself.
PI/XI: Forward Error Handling (FEH) for asynchronous proxy calls with the use of Error and Conflict Handler (ECH)
Message was edited by: Eng Swee Yeoh

Problem in creation of ABAP proxies

Hi,
I am trying to create proxies of Message Interfaces that are built from External Definitions(XSDs). In the scenario, we use two XSDs, one for structure of BAPI and one as Document Envelope containing header level information of the document. Message Interface is created for Document Envelope and internally it references XSD of structure of BAPI.
For e.g. For request message of BAPI_COMPANY_GETDETAIL, we have two XSDs:
1. BAPI_COMPANY_GETDETAIL
2. BAPI_COMPANY_GETDETAIL_Document_Envelope
I create interface for document envelope; interface internally references XSD BAPI_COMPANY_GETDETAIL.
When I try to create proxy for such an Interface I get following error:
Cannot generate proxy (object <element name="BAPI_ACC_DOCUMENT_POST"> missing in WSDL, see long text)
Message no. SPRX084
and diagnosis provided in long text is as follows:
Diagnosis
In the WSDL document, the object
 "<element name="Documents"> <complex/simpleType ..."
from the namespace
"http://mindef.nl/schemas/DocumentEnvelope"
links to the object
 "<element name="BAPI_ACC_DOCUMENT_POST">"
from the namespace
 "urn:sap-com:document:sap:rfc:functions"
However, this last object does not exist in the WSDL document.
System Response
ABAP proxy generation expects that all directly and indirectly referenced objects are in the WSDL document. Therefore, no proxy can be generated for this WSDL and the system displays an error message.
Procedure
This situation can have different causes:
Object "<element name="BAPI_ACC_DOCUMENT_POST">" not been defined
Object "<element name="BAPI_ACC_DOCUMENT_POST">" saved in the wrong namespace
In the reference to object "<element name="BAPI_ACC_DOCUMENT_POST">", the wrong name was specified
In the reference to object "<element name="BAPI_ACC_DOCUMENT_POST">", the wrong namespace "urn:sap-com:document:sap:rfc:functions" was specified
Internal error in the service that constructs the WSDL document
Internal error in ABAP proxy generation
I have checked all the possibilities, there is no inconsistency in WSDL.
Kindly provide some suggestions to tackle this problem.
regards,
Bhavish Bhatia

Hi Bhatia,
You cannot create ABAP proxies from external definitions, IDOC or BAPI, when your application system is based on 6.20.
This works only, when your application system is based on 6.40 or higher.
Regards,
Udo

I am getting the following error at Import ABAP phase ...

Dear All,
I am getting the following error at Import ABAP phase when performing the system copy function (Import) via ./sapinst ( OS - LINUX and DATABASE-ORACLE 10g)...
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
/usr/sap/RXT/SYS/exe/run/R3load: START OF LOG: 20090102154030
/usr/sap/RXT/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
/usr/sap/RXT/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
Compiled Apr 1 2006 00:08:29
/usr/sap/RXT/SYS/exe/run/R3load -testconnect
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: DbSlErrorMsg rc = 99
/usr/sap/RXT/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/RXT/SYS/exe/run/R3load: END OF LOG: 20090102154030
Thanx,
Amit

Dear Juan,
Trans.log is ;
isrxi:rxtadm 7> cat trans.log
4 ETW000 R3trans version 6.13 (release 700 - 20.02.06 - 16:15:00).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 02.01.2009 - 16:45:09
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: R3trans -d
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [dev trc ,00000] Fri Jan 2 16:45:09 2009 62 0.000062
4 ETW000 [dev trc ,00000] db_con_init called 13 0.000075
4 ETW000 [dev trc ,00000] create_con (con_name=R/3) 21 0.000096
4 ETW000 [dev trc ,00000] Loading DB library '/usr/sap/RXT/SYS/exe/run/dboraslib.so' ...
4 ETW000 26 0.000122
4 ETW000 [dev trc ,00000] load shared library (/usr/sap/RXT/SYS/exe/run/dboraslib.so), hdl 0
4 ETW000 9099 0.009221
4 ETW000 [dev trc ,00000] Library '/usr/sap/RXT/SYS/exe/run/dboraslib.so' loaded
4 ETW000 16 0.009237
4 ETW000 [dev trc ,00000] function DbSlExpFuns loaded from library /usr/sap/RXT/SYS/exe/run/dboraslib.so
4 ETW000 30 0.009267
4 ETW000 [dev trc ,00000] Version of '/usr/sap/RXT/SYS/exe/run/dboraslib.so' is "700.08", patchlevel (0.46)
4 ETW000 42 0.009309
4 ETW000 [dev trc ,00000] function dsql_db_init loaded from library /usr/sap/RXT/SYS/exe/run/dboraslib.so
4 ETW000 21 0.009330
4 ETW000 [dev trc ,00000] function dbdd_exp_funs loaded from library /usr/sap/RXT/SYS/exe/run/dboraslib.so
4 ETW000 25 0.009355
4 ETW000 [dev trc ,00000] New connection 0 created 16 0.009371
4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = -000000001 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000 21 0.009392
4 ETW000 [dev trc ,00000] db_con_connect (con_name=R/3) 17 0.009409
4 ETW000 [dev trc ,00000] find_con_by_name found the following connection for reuse:
4 ETW000 15 0.009424
4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = 000000000 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000 16 0.009440
4 ETW000 [dev trc ,00000] -->oci_initialize (con_hdl=0) 195 0.009635
4 ETW000 [dev trc ,00000] Client NLS settings: AMERICAN_AMERICA.UTF8 1567 0.011202
4 ETW000 [dev trc ,00000] Logon as OPS$-user to get SAPSR3's password 14 0.011216
4 ETW000 [dev trc ,00000] Connecting as /@RXT on connection 0 (nls_hdl 0) ... (dbsl 700 240106)
4 ETW000 15 0.011231
4 ETW000 [dev trc ,00000] Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
4 ETW000 17 0.011248
4 ETW000 [dev trc ,00000] 0 UTF8 1 0x9342150 0x9349ba0 0x935a298
4 ETW000 16 0.011264
4 ETW000 [dev trc ,00000] Allocating service context handle for con_hdl=0 15 0.011279
4 ETW000 [dev trc ,00000] Allocating server context handle 11 0.011290
4 ETW000 [dev trc ,00000] Attaching to DB Server RXT (con_hdl=0,svchp=0x935a1c8,svrhp=0x935c4a8)
4 ETW000 63 0.011353
4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'OCIServerAttach' failed: rc = 12541
4 ETW000 1787 0.013140
4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error '12541'
4 ETW000 16 0.013156
4 ETW000 [dev trc ,00000] Try to connect with default password 46 0.013202
4 ETW000 [dev trc ,00000] Connecting as SAPSR3/<pwd>@RXT on connection 0 (nls_hdl 0) ... (dbsl 700 240106)
4 ETW000 15 0.013217
4 ETW000 [dev trc ,00000] Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
4 ETW000 16 0.013233
4 ETW000 [dev trc ,00000] 0 UTF8 1 0x9342150 0x9349ba0 0x935a298
4 ETW000 15 0.013248
4 ETW000 [dev trc ,00000] server_detach(con_hdl=0,stale=0,svrhp=0x935c4a8)
4 ETW000 14 0.013262
4 ETW000 [dev trc ,00000] Detaching from DB Server (con_hdl=0,svchp=0x935a1c8,srvhp=0x935c4a8)
4 ETW000 13 0.013275
4 ETW000 [dev trc ,00000] Deallocating server context handle 0x935c4a8 20 0.013295
4 ETW000 [dev trc ,00000] Allocating server context handle 20 0.013315
4 ETW000 [dev trc ,00000] Attaching to DB Server RXT (con_hdl=0,svchp=0x935a1c8,svrhp=0x935c4a8)
4 ETW000 25 0.013340
4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'OCIServerAttach' failed: rc = 12541
4 ETW000 430 0.013770
4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error '12541'
4 ETW000 16 0.013786
4 ETW000 [dblink ,00431] ***LOG BY2=>sql error 12541 performing CON [dblink#3 @ 431]
4 ETW000 85 0.013871
4 ETW000 [dblink ,00431] ***LOG BY0=>ORA-12541: TNS:no listener [dblink#3 @ 431]
4 ETW000 15 0.013886
2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'RXT'"
isrxi:rxtadm 8>
Regards,
Amit

BPM for error handling and acknowledgements

Hi,
Can any one tell me how to handle BPM for error handling and acknowledgements in one scenario.
Please send me the link if you have other wise give me the solution on the same.
Thanks,
Nagesh

Hi !
Just check out these links This might help you.
Usually Application Level Acknowledgement is considered during Sync communication. If you are using RFC, you can make use of Sync communication. So you can handle it without bpm, provided your both sender and receiver are sync interfaces.
To know about Ack-
http://help.sap.com/saphelp_nw2004s/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
you can not dirrectly access the content of the ACK, however the BPM shows different behaviours based on the ACK status. E.g. if the ACK contains a success message the BPM will continue in its normal process, if the ACK contains a permanent error, it will either stop or go through an exception branch (provided such a branch has been defined). Have a look at the documentation: http://help.sap.com/saphelp_nw04/helpdata/en/43/65ce41ae343e2be10000000a1553f6/content.htm It doesnt"t state the above mentioned behaviour in detail but says that you need to define an exception branch.
The trickiest part is always to find out, when you will get a transient vs. as permanent error ack. If you are using ACKs with Proxies refer also to this link http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/content.htm and this http://help.sap.com/saphelp_nw04/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/7b/94553b4d53273de10000000a114084/content.htm
The following link has entire configuration of Receiver XI Adapter (including acknowledgements)
http://help.sap.com/saphelp_nw04/helpdata/en/f4/0a1640a991c742e10000000a1550b0/content.htm
 eror handling in BPM.

1. CCMS monitoring
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/42fb24ff-0a01-0010-d48d-ed27a70205a8
2. BPM Monitoring
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e7bc3a5a-0501-0010-1095-eb47159e169c
3. Monitoring XML Messages http://help.sap.com/saphelp_nw04/helpdata/en/41/b715045ffc11d5b3ea0050da403d6a/frameset.htm
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
monitoring BPm https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e7bc3a5a-0501-0010-1095-eb47159e169c
Reconciliation of Messages in BPM - /people/krishna.moorthyp/blog/2006/04/08/reconciliation-of-messages-in-bpm
Also see the below BPM related links
check list for BPM https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3bf550d4-0201-0010-b2ae-8569d193124e
/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers
http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/62/dcef46dae42142911c8f14ca7a7c39/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/de/766840bf0cbf49e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/cb/15163ff8519a06e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
Many other examples can be found under the following link at help.sap.com
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
And some weblogs
https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
/people/siva.maranani/blog/2005/05/22/schedule-your-bpm *****
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
/people/michal.krawczyk2/blog/2005/06/11/xi-how-to-retrieve-messageid-from-a-bpm
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
/people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
/people/michal.krawczyk2/blog/2005/09/04/xi-do-you-realy-enjoy-clicking-and-waiting-while-tracing-bpm-steps *****
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements *****
/people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure
/people/kannan.kailas/blog/2005/12/07/posting-multiple-idocs-with-acknowledgement
Also have a look at these seminars,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/daea5871-0701-0010-12aa-c3a0c6d54e02
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/e8515171-0701-0010-be98-e37bec4706cc
Thanks !!!
Regards
Abhishek Agrahari
Questions are welcome here!!
Also mark helpful answers by rewarding points

Error Handling in File to Multiple IDOC Scenario?

Hello Experts,
My scenario is file with Multiple records and I want to send it to SAP system.If there will be 10 Records in my file I need to create 10 IDOC in Target system.
I can use below of the two options.
1) File to Multiple Idoc (1.N Mapping)
2) Using BPM
3)Directly place the file in SAP application server and process it via ABAP Program.
However I am not clear in which option error handling will be more effective.Please suggest.
Basically I want to handle If out of 10 records 9 are correct and 1 record is not correct then I should be able to report within PI without affecting 9 correct records.Is it possible 9 records will be sent to SAP system and PI will only show error for 1 incorrect record.
Also I will be doing this scenrio for transaction data with huge size (1 Million Records).Which approach will be more effective in this case.
Thanks,
Pushkar

Hi Patel,
I want to handle If out of 10 records 9 are correct and 1 record is not correct then I should be able to report within PI without affecting 9 correct records.Is it possible 9 records will be sent to SAP system and PI will only show error for 1 incorrect record.
when working on graphical mapping, the target structure is created when there are no errors in all records of source structure.
suppose if we have validation error in 9th and 10th record, then we can not process the first eight records and inturn we can not store the two error records in XI for further.
i suggest you the third option, you can directly place the file in SAP application server and process it via ABAP Program.
this is far better because you can do more customizations as you have to deal with millions of records.
Regards,
Pradeep A.

Error handling in ABAP proxies

Similar Messages

Maybe you are looking for