Interface for error handling.

Hi experts,
i have to design an interface for exception handling .there is a client system ( mainframe) linked to
sap system through webspher (ibm) .whenever ERN from the client system comes to sap system .
there will be 2 types .
1. the ERN is valid one.
2. the ERN is invalid one .
for the invalid ERN we have to inform the client system about the exception. this is through IDOC only ..
can any one sugesst the good techincal design.
regards
SV

please explain ERN , also what EDI transaction comes in and what idoc message/ idoc type is used?
Also look at EDI 864 which is a text message.
But give me more details.
BTW Welcome to SDN.
Message was edited by:
Sandeep Bhavsar

Similar Messages

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

Option for error handling for DTP, ' no updata, no reporting" and "deactiva

Hello Gurus,
     option for error handling for DTP, ' no updata, no reporting" and "deactivated" , please give some explanation and instance for them?
Many Thanks,

On the Update tab page, specify how you want the system to respond to data records with errors:
                            a.      No update, no reporting (default)
If errors occur, the system terminates the update of the entire data package. The request is not released for reporting. However, the system continues to check the records.
                            b.      Update valid records, no reporting (request red)
This option allows you to update valid data. This data is only released for reporting after the administrator checks the incorrect records that have not been updated and manually releases the request by setting the overall status on the Status tab page in the monitor (QM action).
                            c.      Update valid records, reporting possible
Valid records can be reported immediately. Automatic follow-up actions, such as adjusting the aggregates, are also carried out.
http://help.sap.com/saphelp_smehp1/helpdata/en/42/fbd598481e1a61e10000000a422035/content.htm
Hope it helps.
rgds, Ghuru

Using AIA for Error Handling. Logging and Notification Services

hi,
In our project we usie OSB and BPEL for integrating different applications.
There is a suggestion that we should use AIA to just use the Error Handling, Logging and Notification services from AIA. I am not sure about this use case, as most of these services mentioned can be replicated in BPEL. Except for the AIAAsyncExceptionHandling BPEL process, i guess all other functionalties provided by AIA can be easily developed in BPEL or OSB alone.
However, would like to hear from you guys about this particular use case. Is it advisable?

Hi,
It's an issue with 10.1.3.4 OBIEE. (whem using IBM LDAP)
References
BUG:7363517 - INTERNAL BI FAILURE ON STARTUP
They issue can be resolved by setting LD_PRELOAD=/path/libibmldap.so
Here are the steps:
. sa-init.sh
export LD_PRELOAD=/path/libibmldap.so

What is Considered Best Practice for Error Handling in Components?

What would be the best approach to handling errors in custom (possibly composite) components?
I see three different possibilities:
Having the error handling funciton within the component. The problem is that this is not adaptable to the consumers error handling setup (i.e. logging to database, redirecting to a pretty error screen, etc.).
Passing in an error function as a parameter. The problem here is how to have the externally defined error function interact with external elements that are not defined within the component, i.e. passing the error or fault object to a logging class, or something similar, of which the component knows nothing about.
Referencing the external error handling methods directly from within the component. (Of course that's shabby programming, just listing as a technical option.)
How do you solve this?
My goal is to have a versatile custom component that can utilize any given consumer's error handler.
Thanks,
Mike

or define a customized event and dispatch it when error occur, then you can just listen to it outside

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.

Java API for Error Handling

There are some common error tables storing error IDs information ( IDs like error type, project id, interface id, message id etc.) in Operational Database (is not on source or target system) which we have to update using java API. We need to call java API (java code) whenever error occurs. We have to provide all the IDs to this function and then API will take care of DB updating. We can call java API in mapping program by creating user-defined java function, this will trap all the errors which are in source file as well as in mapping and mapping lookup. Query is:
A- A- Do we have any other place after the mapping to call this java API and trap the errors through it?
B- Can we call Java API using BPM and pass error IDs to it.

Hi Anand,
You Have to write Module For that(if you wanna call Java API after Mapping)at the receiver.
To write Module Here is a link which will help you in.....
==>http://help.sap.com/saphelp_nw04s/helpdata/en/84/2e3842cd38f83ae10000000a1550b0/frameset.htm
==>http://help.sap.com/saphelp_nw04s/helpdata/en/e4/6019419efeef6fe10000000a1550b0/frameset.htm
==>http://help.sap.com/saphelp_nw04s/helpdata/en/f4/0a1640a991c742e10000000a1550b0/frameset.htm
Enjoy Coding....:)
Regards,
Sundararamaprasad.

Order Entry Interface table error handling through Form after Orderimport

Hi Gurus,
We are on Oracle Apps 11.0.3.
I'm just curious to know that is there any form available to correct error records in SO_HEADERS_INTERFACE, SO_LINES_INTERFACE, SO_LINE_DETAILS_INTERFACE, SO_PRICE_ADJUSTMENTS_INTERFACE, SO_SALES_CREDITS_INTERFACE, SO_SERVICE_DETAILS_INTERFACE, SO_LINE_ATTRIBUTES_INTERFACE, SO_HEADER_ATTRIBUTES_INTERFACE tables after running orderimport.
Most thread says that set REQUEST_ID, ERROR_FLAG and INTERFACE_STATUS columns to NULL in each interface tables. Is there any oracle standard form available to accomplish this in Oracle Apps 11.0.3 or 11i?
Thanks
-Manish

Hi Srinu,
it looks like you got the error message Schedule line &1 &2 is missing in table YVBEP while deleting the sales order.
It seems, that there are no SAP notes regarding this issue. Do you have this issue with all orders or with a single order?
If only a single order causes this issue, maybe something was wrong during an update.
If you get this error for many orders, then custom code (modification, enhancement, user exit in MV45AFZZ, ...) may be the reason for it.
If you have no custom code in module pool SAPMV45A, then contact SAP for this issue.
Regards,
Klaus

Getting Dynamic Error Text for Error Handling in BPM

Hello,
is there any way to get the error message or further details on an exception handler in BPM? I would like to pass the detailed error description of the error that has happened in BPM to an alert using a separate Alert container variable.
Is this possible or do I need to hardcode potential errors?

Hi Florian,
Check Michal's reply in : catch the exception
and Bhavesh's reply in Notify user about Exception in BPM
Regards,
ravi

How to use Fault schema in WSDL for Error Handling in ALSB

We are not able to view the fault element in our alsb flow under body variable and when we get the error in test console the error comes in bea fault schema,but we want the error in our own defined fault schema.Pls. guide.
Below are the steps we followed to create a wsdl.
Steps:
1. We created a webservice project in workspacestudio and generated a wsdl.
2. Then we have added a fault element manually in that wsdl.
3. Now we have generated a webservice from that modified wsdl.
4. Again we have generated a wsdl from webservice created in step 3.
5. step 4 wsdl is tested and running well on server.
When we try to configure that service as Proxy/Business service in ALSB and view the XPATH Expression Editor, we are not able to view Fault element under variable structures under body variable as shown below.But when we see the design view of our running wsdl in workspace studio it shows the fault element.How to get the fault element in variable body so that we can view the error in our logs in our defined Fault schema instead of BEA fault schema.WDSL is enclosed as an attachment.
Thanks in advance

Have you tried using the "Log" action in your pipeline proxy and log for $body and $fault. This will defin return the $body and $fault if these were parsed correctly

How to use fault message for error handling.

HI
Anybody has an idea about how we use fault messages to handle errors in XI
Thanks
Debraj

Hi,
Refer this link. This pdf file has descriptions about fault message types and how to use it.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4cdfc390-0201-0010-2197-da4ada09f281
Regards,
Uma

Best Practises for Error Handling

Hello
I have a PHP front end application and for now an Oracle database in the backend. User defined errors are returned back to PHP front end using RAISE_APPLICATION_ERROR(-20000,'error msg'), the PHP displays the message to the user. We have a problem where we are now going to provide a French version on the application and are stuck at what we are to do with the error messages.
What is the common practise for this?

Don't reinvent the wheel. Oracle provides built-in error globalization.
http://www.morganslibrary.org/reference/pkgs/utl_lms.html
SQL> set serveroutput on
SQL> DECLARE
2   s VARCHAR2(32767);
3   i PLS_INTEGER;
4 BEGIN
5    i := utl_lms.get_message(26052,'rdbms','ora','french', s);
6
7    dbms_output.put_line('before format, message is: ' || s);
8
9    dbms_output.put_line('formatted message is: '|| utl_lms.format_message(s, 96, 'my_string'));
10 END;
11 /
before format, message is: Type %d non pris en charge pour l'expression SQL sur la colonne %s.
formatted message is: Type 96 non pris en charge pour l'expression SQL sur la colonne my_string.
PL/SQL procedure successfully completed.
SQL> ed
Wrote file afiedt.buf
1 DECLARE
2   s VARCHAR2(32767);
3   i PLS_INTEGER;
4 BEGIN
5    i := utl_lms.get_message(26052,'rdbms','ora','german', s);
6    dbms_output.put_line('before format, message is: ' || s);
7    dbms_output.put_line('formatted message is: '|| utl_lms.format_message(s, 96, 'my_string'));
8* END;
9 /
before format, message is: Nicht unterstützter Typ %d für SQL-Ausdruck in Spalte %s.
formatted message is: Nicht unterstützter Typ 96 für SQL-Ausdruck in Spalte my_string.
PL/SQL procedure successfully completed.If you are writing your own messages then Tubby's recommendation is best but I'd be inclined not to put the messages into a table but rather to put them into a package header as constants which minimizes I/O overhead.

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

Error Handling for BAPI MB_COUNT_POST_WITHOUT_INV_DOC for MI10 Transaction

Hi,
Can any one suggest me, how to handle the errors for the BAPI MB_COUNT_POST_WITHOUT_INV_DOC, because this bapi does not have any return table for errors handling? And also suggest any other BAPI which fits for MI10 transaction.
<removed by moderator>
Thanks&Regards,
Damuan.
Edited by: Thomas Zloch on Feb 2, 2012

Hi Dear,
Your answer is very helpful, thanks..!!
But when i am testing with the EIKPF structure, neither error is populating in EIKPF nor the records are posting in MI10. Could you please guess what would be the problem?
Below are the fields that i am passing through this BAPI
1)Document date 2)count date 3)plant 4)storage location 5)item number 6)material code 7) entry quantity
Thanks&Regards,
Damuan.

Best error handling for visa calls?

We are using some handlers we've devloped for power supply handling (over GPIB). The power supplies are SCPI and use SCPI/GPIB commands. The handlers use the NI visa api's Read() and Write() functions to send the commands. They work fine, for the most part, and we've been using them for a number of years.
However, we're hearing reports that there may have been a few times that commands were not executed on the power supply and our handler did not report back any error.
So, I'm trying to update these handlers to add a little error checking to make them more robust and hopefully we'll catch this error if it happens again.
For error handling, I've come up with 3 solutions and tried all 3. I find some benefits and drawbacks with each and hoped I could get your opinions about error handling as I'm not overly familiar with some of the methods.
Method 1:
Set the Event Status Enable register to catch all events (or all that I care about).
Read status byte (STB?) after each command and check the event bit and then event status bit if event bit set.
Drawback1: I have one power supply that does not implement this correctly and a second type that appears to not be working correctly either.
Drawback2: Errors are generic. I'll know if I got, for example, a DDE (Device Dependant Error), but I won't know more detail than that.
Method 2:
After each command sent, read the error queue with the System:Error? query.
Drawback: It seems I get a lot of messages back in this method that aren't real errors. It's very "noisy" and I have no way to distinguish real errors from "noise" messages like "query interrupted" and such.
Method 3:
Check the return code of the Visa Read() and Write() commands. At first I didn't think this was very robust, but after seeing the list of errors here, I'm beginning to think that these might be more robust and detailed than Method 1. However, I'm not sure.
So is method 3 as robust as it looks, or is there a combination/comprimise I can make, or another method I did not mention which is best to trap errors from Visa Reads/Writes to these GPIB power supplies? Keep in mind that the handlers work for a number of different power supplies and its likely that some things may be implemented differently between supplies....so its best to stick with somethind standard that will work on all power supplies.

Hi KingTermite,
I hope you will got answer of the question and may be implemeted something .It was really a nice discussion .I am also facing the same issue where I am communicating with different instrument using GPIB communication and RS 232 too.
Can you share and discuss about the implementation of your initiative.
Best Regards
Regards:
Vaibhav Kanchan
Sr. Engineer
NI Certified LabVIEW Developer(CLD)
NI Certified TestStand Developer(CTD}

Interface for error handling.

Similar Messages

Maybe you are looking for