Receiver Feedback with no Error Handling (Input Design Requested)

Hi Community,
Today we have a pretty standard integration scenario that takes in flat files and converts them to Idocs for target SAP systems. We are looking to redesign the current IDoc interface (posts a customized FIDCC1) under the principle that IDocs in errors on target are always corrected by a change in the source, so essentially we want to report errors back to the source and completely delete the IDoc. I guess this looks like a synchronous call?, but I want to remain as loosely coupled for this. Since we also process these files in batches (i.e. each file contains 1 to many invoices), we would like to return the results back to the source based on each file. For example, the message back to the source (in email so a user can act on it, not a system) could be:
a) file failed because structure is incorrect (like an XSD type check).
or of the file makes it through XI,
b) list of invoices failed because xxx is incorrect and list of invoices that processed.
We are open to using proxies, any kind of IDoc error handling that could do this, workflows, status idocs, etc. Every option is on the table.
Thanks!
Peter

peter
if u are open to proxes then u might haveone interface that will send the data to proxy and thru proxy u update the idoc....if idoc goes fpor an error u can have another interface triggered that will update/delete the soruce data...for this u might need to pass the soruce files details to proxy and back

Similar Messages

LV7.1 Strange behavior with Automatic Error Handling occuring when it shouldn't [LV 7.1 Pro on WinXP for Tablet PC's]

[LV 7.1 Pro on WinXP for Tablet PC's]
I recently let a rather large LV app of mine run in the development environment while I was out for a couple of days. Upon returning I found that the app had hung for ~22 hours waiting for an answer to an Automatic Error Handling (AEH) dialog proclaiming an Error 7 in New File without any indication of the VI hierarchy that called New File. I set about ensuring that AEH dialogs would not pop up and have not been able to discover how I could have possibly received one in the first place.
Subsequent investigation revealed:
Neither AEH option in Options>Block Diagrams were checked.
Network problems had occurred around the time that the app had hung. All file paths are network paths when running in the development environment, so the cause of the error was most likely valid, even if the AEH dialog appearance wasn't.
My app has only one instance where the New File primitive is used by me. That subVI and all others above it in the hierarchy DO NOT have the AEH property enabled. The error out cluster of New File in my subvi is wired.
My app has three instances where New File is called from a vi.lib vi (Open/Create/Replace File.vi, Open Config Data.vi, and Prompt Web Browser Path.vi), none of which have the AEH property enabled. Nor does any of their calling VI's. All three instances also have their error out cluster wired.
A utility to examine the AEH property of all VI's (with all top level and dynamic VI's loaded) in memory reported that only 1 of 308 vi's ( RGT Does File Exists.vi from the Report Generation Toolkit) had that property true. That vi has no subVI's other than the File/Directory Info primitive and no calling VI's in common with any of the vi's that call New File, except a top level VI.
As long as 'Enable automatic error handling dialogs' remains unselected in options>block diagram, I am unable to get an AEH dialog for either the New File or File/Directory Info primitives in a test VI with AEH property enabled and their error out clusters unwired no matter what invalid path I pass to the functions. As soon as the options>block diagram>Enable AEH dialogs' is selected, both primitives fire AEH dialogs with no error out wired and don't when wired. i.e. works as advertised.
In other words I can find no reason why I should have gotten the problem AEH dialog...
I cannot afford for this app to hang because of a network problem, other portions of the app that were running concurrently correctly handled the error and, had the AEH dialog not appeared, the app would have made corrections or shutdown in an orderly fashion.
Any ideas?

Very good.
Write Characters to File.vi>Open/Create/Replace File.vi>New File
New File throws the error. Open/Create/Replace strips the hierarchy from the source of the error. Write Characters passes it to the General Error Handler. I never looked above O/C/R file in the hierarchy except for enable automatic error handling property. The tip-off should have been to realize that O/C/R file was stripping the hierarchy from the error and look above that.
The real irony is that Write Characters was being used to log error cluster data to an error log file...
Save as... Copy without updating... the OEM 'Write Characters to File' is gone from this app.
Thanx (a bunch)

File receive adapter command line error handling

Hi,
This is our requirement - After the file receive adapter, we need to run a script. Based on the return code of the script, we need to handle the error handling of the interface (i.e. send an email about the error).
I have looked at the operating system command line in the file adapter. How does XI handle return codes for the command line? If the command line has a error return code, how to send an email from XI?
If anyone has ideas on this topic, please respond!!
thanks,
lasya

Hi,
I don't think so, it is possible directly. You can not get the Response back to XI pipeline from the shell script.
But you can think, if you are able to call this from Mapping.
And one more option is using Transport Acknowledgement ( with BPM) if the file is not able to write into the target directory you can raise an alert-
Blog on this-
/people/michal.krawczyk2/blog/2006/06/22/xi-playing-with-the-file-adapters-acknowledgments
Regards,
moorthy

Issue with SRDemo error handling

Hi All,
Glad the forums are back up and running. In debugging some error-handling issues in our own application, I found an issue in the error handling code of SRDemo. I thought I'd post the issue here, as many of us (myself included) use some SRDemo code as the basis for our own applications.
The issue can be found in the oracle.srdemo.view.frameworkExt.SRDemoPageLifecycle class, specifically in the translateExceptionToFacesErrors method. I'll show the code that has the issue first, and explain the issue afterwards:
        if (numAttr > 0) {
            Iterator i = attributeErrors.keySet().iterator();
            while (i.hasNext()) {
                String attrNameKey = (String)i.next();
                 * Only add the error to show to the user if it was related
                 * to a field they can see on the screen. We accomplish this
                 * by checking whether there is a control binding in the current
                 * binding container by the same name as the attribute with
                 * the related exception that was reported.
                ControlBinding cb =
                    ADFUtils.findControlBinding(bc, attrNameKey);
                if (cb != null) {
                    String msg = (String)attributeErrors.get(attrNameKey);
                    if (cb instanceof JUCtrlAttrsBinding) {
                        attrNameKey = ((JUCtrlAttrsBinding)cb).getLabel();
                    JSFUtils.addFacesErrorMessage(attrNameKey, msg);
            }Now, this bit of code attempts to be "smart" and only show error messages relating to attributes if those attributes are in fact displayed on the screen. It does so by using a utility method to find a control binding for the attribute name. There are two issues with this code, one obvious, and one that is a bit more subtle.
The obvious issue: if there is a binding in the page definition, it doesn't necessarily mean that the attribute is shown on the screen. It's a good approximation, but not exact.
The other issue is more subtle, and led to errors being "eaten," or not shown, in our application. The issue comes if you are using an af:table to display and update your data. In that case, the findControlBinding will not find anything for that attribute, since the attribute is contained within a table binding.
Just posting this as a word to the wary.
Best,
john

somehow, this message got in the wrong thread....
Hi Frank,
Yes, I simply scripted it out this way to contrast the behaviour if the first attribute was read-only vs not read-only. I found the issue on a page in our app that was simply drag-and-drop the VO from the data control on the page.
It's quite annoying, because our particular use case that hit this error is a "save" button on the page. If the commit operation doesn't return any errors (and it doesn't in this use case!), we add a JSF message saying "save successful" - then the attribute errors are further added later in the page lifecycle, so we get 3 messages: "Save successful" and "Fix this error" and "Tried to set read-only attribute" - quite confusing to the end-user when the only message they should see is "fix this error."
At any rate, the fix is to simply re-order the attributes in the page definition - that doesn't affect the UI at all, other than to fix this issue.
John
it was supposed to be something like:
Hi Frank,
Thanks for the reply. I was simply posting this here so that people who use the SRDemo application techniques as a basis for developing the same functionality in their own apps (like me) can be aware of the issue, and avoid lots of head-scratching to figure out "what happened to the error message?"
John

How does BPEL Fault Management Framework gel with ESB Error Handling ?

I see that BPEL 10.1.3.3 has pretty neat Fault Management Framework (although I have to admit it is not very well advertised).
The next logical question is: what about ESB ? Would that help in ESB error handling ? I understand that ESB has its own Error Hospital etc.; however, we have to constantly grapple with two distinct paths for any piece of integration functionality (1. ESB 2. BPEL). I guess, all of this will be moot in the 11g timeframe. Still wondering if anyone out there has somehow unified error handling for these two distinct offerings ?

It's not available in ESB, you have to implement/extend that by your self. Off course in the next release everthing will be better :-)
But, if you are able to use Oracle AIA (http://edelivery.oracle.com) You could use Oracle AIA Foundation, that has a fault 'hospital' implemented both for BPEL and ESB.
Marc
http://orasoa.blogspot.com

IE / Spry Bug with custom error handler

Ok, as I was looking through SpryData.js I noticed these
wonderful lines:
Spry.Utils.loadURL.callback = function(req)
if (!req || req.xhRequest.readyState != 4)
return;
if (req.successCallback && (req.xhRequest.status ==
200 || req.xhRequest.status == 0))
req.successCallback(req);
else if (req.errorCallback)
req.errorCallback(req);
In particular the "errorCallback()" method interested me as I
wanted to introduce my own error handler. As I went about testing
this I came up with a quick try of:
var url = "/cfcs/mycfc.cfc?method=IsValidPath&path=" +
encodeURIComponent(sl.value + sd.value);
var optionsObj = new Object();
optionsObj.errorCallback = ShowError;
Spry.Utils.loadURL("GET", url, false, ValidateForm,
optionsObj);
And this works great in FF, but not IE. When I cause an error
to occur from ColdFusion I pass a status code of "500". In FF the
error code causes my "ShowError" function to fire, but not in IE. I
tracked it to this bit of code in SpryData.js:
Spry.Utils.loadURL = function(method, url, async, callback,
opts)
var req = new Spry.Utils.loadURL.Request();
req.method = method;
req.url = url;
req.async = async;
req.successCallback = callback;
Spry.Utils.setOptions(req, opts);
try
req.xhRequest = Spry.Utils.createXMLHttpRequest();
if (!req.xhRequest)
return null;
if (req.async)
req.xhRequest.onreadystatechange = function() {
Spry.Utils.loadURL.callback(req); };
req.xhRequest.open(req.method, req.url, req.async,
req.username, req.password);
if (req.headers)
for (var name in req.headers)
req.xhRequest.setRequestHeader(name, req.headers[name]);
req.xhRequest.send(req.postData);
if (!req.async)
Spry.Utils.loadURL.callback(req);
catch(e) { req = null; Spry.Debug.reportError("Exception
caught while loading " + url + ": " + e.message); }
return req;
Apparently running (req.xhRequest.send(req.postData);) in IE
will throw an error if the requested page throws an error status
code. This causes the try/catch in the Spry function to catch the
IE error and never allows my own error handler to run. Hopefully a
fix for this will be in the works because I really like the idea of
being able to use my own error handler.
--------Edited after initial post.--------
Ok, I figured out another item of interest. My requests
earlier were set to "async = false". If I set "async = true" then
it does work. I realized that because I was using sychronous mode
and IE was throwing the error, it was preventing the call to the
"Spry.Utils.loadURL.callback" method from occuring, while asynch
mode uses the onreadystatechange to call the function and thus
causes my own error handler to function. I am still interested to
know if there is a bug here somewhere and if it is just IE or Spry
or both. Looking forward to reading any posts.

Hi WraithBudde,
Thanks for all the details. In my opinion this is indeed a
bug in Spry for the synchronous case. I'll file a bug and fix it.
> You know you love me.
Heh, yeah, I love anybody who takes the time to report bugs
... especially when they've narrowed it down to the exact set of
lines in the source.
Once again ... THANKS!
--== Kin ==--

File Sender with CC Error handling

When using the file sender with content conversion we often receive
Parsing errors in the AFW monitoring due to bad messages.
Q: how can we monitor and e-mail this errors from the AFW,does the CCMS covers everything? Alert monitoring?.
another Q: In higher SPs of XI there is the option to archive error messages,is it possible to raise an alert for the parsing problem even though the file was removed by the Comm. channel to the archive folder.
points will be rewarded.
Regards,
Nimrod.G

hi,
Q: how can we monitor and e-mail this errors from the AFW,does the CCMS covers everything? Alert monitoring?.
yes it is possible thru CCMS
check the below links
Configuring scenario specific E-mail alerts in XI-CCMS: Part - 1,2,3
/people/aravindh.prasanna/blog
XI : Configuring CCMS Monitoring for XI- Part I
/people/sap.user72/blog/2005/11/24/xi-configuring-ccms-monitoring-for-xi-part-i
XI : GRMG Customizing for XI CCMS Heartbeat Monitoring Part II
/people/sap.user72/blog/2005/12/05/xi-grmg-customizing-for-xi-ccms-heartbeat-monitoring-part-ii
regards'
chandrakanth

Report and Alert don't executed in the error handler with a JMS proxy service

Hi,
I'm working with OSB 11.1.1.4.0 and I'm facing a problem with the error handler of my JMS proxy service.
My error handler contains two main elements :
- a Report action
- an Alert with a JMS destination defined
When the business service failed the message remain in the queue. It's the expected behavior.
The problem is :
- the report is missing
- the alert is raised but missing in the JMS destination defined in the Alert setting.
I've noticed if I add a Reply with Failure or Success, Report and Alert are successfully executed.
Unfortunately the message don't remain in the JMS queue.
What can I do in order to have my report/alert done and the JMS transaction rollback in order to keep the message in the queue ?
I've already met this problem in the past with alsb v3 and my solution was to add Service Callout in the error handler in order to externalize these actions.
This solution is not convenient and I hope another solution is possible.

Inventorying workgroups can be difficult, especially when it comes to remote access and network security. Because workgroups are not centrally managed, some of the items discussed in this
wiki article on preparing your workgroup environment may require you to visit each machine individually.
For non-domain credentials, you do not use the <systemname>\<user> format, you simply enter the user name. Regarding how to enter the credentials, if you have an account that uses the same username and password on all machines and is an administrator
on all of those machines, then you can enter that in the All computers credentials page of the wizard. You can also do this if they are different user names. However, if some machines have an account with the same user name, such as Administrator,
but different passwords on each machine, you will need to use the Manually enter computer names discovery method, and then enter the information for each group or each machine.
As you can tell, workgroup environments can quickly negate any benefit that the agentless inventory nature of MAP provides.
Please remember to click "Mark as Answer" on the post that helps you, and to click
"Unmark as Answer" if a marked post does not actually answer your question. Please
VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

SOA 11g- Error handling of Asynchronous composites

Hi,
We are working on Error Handling framework design for both synchronous, asynchrounous composites of SOA 11g.
Any pointers on the same will be helpfull as how to capture errors occuring during asynchronous services calls.
Thanks,
Sowmya

Thanks Naresh.
Can you help me if the below is possbile.
I have a process which takes an input and splits the inputs into multiple requests to some external system in a flow-N activity. There is an invoke activity with-in the flow N activity. And this invoke is an asynchrnous call. If at runtime we have 5 flows for flow-N, with 5 calls to external system, and out of these 4 are successful and one errors out. Can we have an error handler to just resubmit the failed request to the external system. Once we get the response from the resubmission, we want to continue with merging the output of all 5 and sending it back.
Also, let me know if there will be any issue with the call back operation due to resubmission of the invoke. This is an asynchronous invoke with call back mechanism for response.
Thank you so much.
PK

Error handler for event based messaging framework

I've been very interested in using the event based messaging framework (described here http://forums.ni.com/t5/LabVIEW/Community-Nugget-2009-03-13-An-Event-based-messageing-framework/td-p...) for my next large application.
My main concern is the fact that it seems like typos would be very difficult to debug since you need to ignore unknown commands to make this system work.
To solve this problem I've been considering the idea of having a single message error handler VI which will store all valid commands and check all sent commands to see if they are valid. Each VI would send out a register message on startup with their name and all messages they can send and receive. The message error handler would store these and then check all future messages to be sure it is a valid message, throwing an error if it is not.
My basic problem is this: for this to work the message error handler VI would have to be started before any messages are sent so that it can capture all the register events. If this is a VI that will be continuously running the entire application how can I ensure it starts first since I cannot wait for it to complete? (I.e. the usual method of running an error out wire or using a sequence structure will not work since everything will then wait for it to complete which will not happen until the program is ready to shut down)
I'm assuming the answer might be to use an asynchronous call but I'm not very familiar with this method.
Any help is appreciated. Thanks.

Could you just use the error handler as a subVI inside a case structure that is only called when you have new message to be checked? I'm not sure I understood the exact functionality you are looking for, so sorry if this does not apply.
Zach P.
Product Support Engineer | LabVIEW R&D | National Instruments

WSN 9791, 3202 error handling

I have setup a 9791with 3202 and attached a 250ohm resistor to measure a 4-20mA signal at AI0 of the 3202. I am continously measing the input voltage and I am also checking battery voltage, link quality, external power and error messages with simple error handling. Everything seems to work fine. Now I disconnect power from the 3202 and remove the batteries. Surprisingly the input voltage at AI0 remains its value, the battery voltages remains the same, it show that external power is present and the error handling shows no error. After 3 minutes MAX will indicate that the signal has been lost. The VI shows that the external power has been disconnected. All other values remain the same
I am using LabVIEW 2009FDS and I do not have Pioneer or any other additional software.I have updated the firmware of the 9791 and 3202 to the latest revision.
How can I show in my VI that the signal has been lost? MAX seems to be able to do it, but only after 3 minutes.Why does the error handling never show anything? Why does the link quality remain the same when signal is lost?
Thanks
Solved!
Go to Solution.

I am not very impressed by this. I have always been with any NI hardware that I have purchased in the past. I am not sure why there is an error in/out, it does not do anything. The time server as an indicator if the data is old or not would be great IF I had access to a time server. This application will be setup where I have only power and no internet available. Even if I did it would not work because I have to turn off any other network connection to make it work. I have treid the Meinberg time server. It worked once and now I get 12/31/1903 again. As a minimum I would think that the Link Quality would go to 0 and not retain its value. This seems like a firmware issue that NI should fix asap. This seems not reliable for a stand alone executable.I should be able to select time server or OS system clock. I realize OS system clock may not be very accurate but at least it is something to use for time stamp. NI should also fix that in a future firmware rev. At this time I am leaning towards dumping the NI-WSN and look for something else. I guess I could buy the additional software like RT/pioneer that might allow me to do what I want but the added cost will not be appreciated by my boss. For that money I might be able to purchase something else.

Radio Frequency - Error handling

Hello ,
I have a problem with the error handling in a radio frequency program, because here is not allowed to
show the error messages as a popup or in the status line.
I make a function call of 'L_TO_CREATE_TR'. The raised errors i get back in the exceptions are not a problem to handle. But in this function call, they put normal
success or error messages in,
for example
Programm: SAPLL03A
Include: LL03AF8C
Line : 65 - 76
These messages I can t catch.
Is there any way to cut off the output of the messages??
I would appreciate a feedback very much!!!
Jasmin Söllner

Hi,
We are using the function module in one of our RF developments and here is how it is called:
CALL FUNCTION 'L_TO_CREATE_TR'
    EXPORTING
      i_lgnum                              = p_lgnum
      i_tbnum                              = p_tbnum
      i_squit                              = p_l_squit
      i_tbeli                              = p_l_squit
      i_commit_work                        = c_x
      i_bname                              = sy-uname
      it_trite                             = it_trite
IMPORTING
      e_tanum                              = p_v_tanum
   EXCEPTIONS
     foreign_lock                         = 1
     qm_relevant                          = 2
     tr_completed                         = 3
     xfeld_wrong                          = 4
     ldest_wrong                          = 5
     drukz_wrong                          = 6
     tr_wrong                             = 7
     squit_forbidden                      = 8
     no_to_created                        = 9
     update_without_commit                = 10
     no_authority                         = 11
     preallocated_stock                   = 12
     partial_transfer_req_forbidden       = 13
     input_error                          = 14
     OTHERS                               = 15
We have not faced any issues with the development yet.
regards
Aveek

Error Handling in WebUtil CLIENT_OLE2.get_obj_property

Hello,
we have a problem with the error handling in WebUtil's CLIENT_OLE2.get_obj_property function. The WebUtil version is 1.0.2 and the problem can be reproduced on the 9iAS, 9iDS and 10gAS as well.
Problem description:
The get_obj_property function does not throw a PL/SQL exception when it is given an invalid object as first argument (i.e. an object handle to an application that has intermittently been closed by the user). Instead, the function returns a NULL value and the control flow of our application code continues as if the function had succeeded. So the problem is that the get_obj_property function neither throws an exception nor can the failure be caught by calling WEBUTIL_CORE.IsError as this returns that no error occurred.
Example:
PACKAGE BODY word IS
OBJ_HND CLIENT_OLE2.OBJ_TYPE := NULL;
mydocs CLIENT_ole2.obj_type;
-- Start Word97
PROCEDURE wordopen is
BEGIN
obj_hnd := null;
obj_hnd := CLIENT_OLE2.create_obj ('Word.Application');
CLIENT_OLE2.Set_property(obj_hnd,'Visible',1);
END;
PROCEDURE test is
BEGIN
IF obj_hnd IS NULL THEN
wordopen;
END IF;
BEGIN
mydocs := CLIENT_OLE2.get_obj_property(obj_hnd,'Documents');
EXCEPTION WHEN OTHERS THEN
-- Word has probably been closed by the user
-- so just start it again and retry...
wordopen;
mydocs := CLIENT_OLE2.get_obj_property(obj_hnd,'Documents');
END;
END;
END;
If the procedure test is called once then the Word application is started and the procedure performs some work. The procedure could be called several times on the same Word instance but fails in case the user closes the Word application because the procedure does not get an exception or error from WebUtil's get_obj_property function. Only a JACOB Java exception is logged in the Java console of the user's computer - the PL/SQL code has no way of knowing that an error has occurred.
Possible solution / patch for webutil.pll:
The webutil.pll can be patched to throw an exception if it is given an invalid object handle. In webutil.pll version 1.0.2 in get_object_property, line 1205, just add the condition "(v_javaHandle IS NULL) or " at the beginning of the if-statement in that line so that an OLE_ERROR will be raised if v_javaHandle is NULL:
if (v_javaHandle IS NULL) or (v_javaHandle = 0) or (v_javaHandle='') or (v_javaHandle=-1) then
raise OLE_ERROR;
end if;
Can you confirm the error and re-release a patched webutil.pll at a later time?
Regards,
Andreas Leidner
infoteam GmbH Berlin

Hi
It is mentioned in webutil doc that, you must regenerate webutil.pll before using it; otherwise you’ll encounter error ORA-06508 when running a form with the attached library.
Hope this helps...
Regards,
Amatu Allah

'Structured' error handling and reentrancy

The parentheses in the subject are due to the fact that I'm not using the Structured Error Handler reference library, but have rolled my own to do something similar but in the manner I want it to. I don't actually use the SEH (haven't even got it installed at the moment on this PC) so am not sure exactly how it works under the hood.
I have a reasonably large application with a number of distinct parallel modules (GUI, state module, communication, motion control). The final parallel module is an error handling module. This consists of two queues - one for incoming errors, and one for outgoing actions. Errors are dequeued and their codes checked for their category (critical, warning, ignore or unclassified, for instance) and the appropriate category is returned to a local error handler via the action queue. When an error is passed to a local error handler VI, it enqueues the error to the main handler and waits for a response to that particular error.
This all works nicely, in much the same way the SEH would do. However, with either the SEH or my local error handler method, I find myself wondering how often to place these down and the consequences of doing so. If they're non-reentrant, I imagine I may end up with lots of parallel processes sitting patiently to access the VI as it's blocked by another, causing jitter. If I go pre-allocated clone, I could potentially have many many callers using this function, which strikes me as a bit of a waste of resources. My gut feel is to go with shared-allocation clones, as the vast majority of the time it'll be no error passed through an empty case, and not to place them in absolutely every subVI - just perhaps after a state executes in the state handler, in all the parallel loops of the submodules etc.
Just wondering what anyone else does with their error handling solution, and whether my thoughts make sense.
CLD

Having chatted to my friendly neighbourhood Spiderman Architect, he suggested I should probably just stop being a wimp and just use pre-allocated clones to avoid the jitter and to stop worrying about the resource hit, as you suggest
I'll use the same code on both PC host and RT host, hence the jitter concerns on the RT.
Thanks for the thoughts!
CLD

RAPOST2000 error handling depreciation test run

I have a problem with the error handling in ECC 6.0 (RAPOST2000). when I run a test run in foreground, the error list is diplayed nicely and i can doble click to see the problem for each asset. But as we have more than 1000 assets we have to run the test run in background, resulting that the error list is placed in the spool without the possibility to drill down to the problem per asset (only the error no displayed in the list). How to proceed to get a smooth way of handling errors without to use two lists ( first the errors per asset, and then the list explaining the error).

Yes, the "Error Analaysis" indicator was ticked when starting the depreciation test run. So, that does not solve the problem having to match 2 different list/reports to analyze/correct the errors.
Regards

Receiver Feedback with no Error Handling (Input Design Requested)

Similar Messages

Maybe you are looking for