ERROR HANDLING FOR CLIENT_OLE2 FUNCTIONS

We have added spell checking to our application using the Client_OLE2 WebUtil function using the example in the knowledge base. Unfortunately the example does not check for errors. Can someone direct me to documentation that shows return codes for the Client_OLE2 functions?
Thanks

Some of the OLE2 functions return a stack of error messages. These can be obtained and processed in a loop using the tool_err package.
If you still have a 6i form builder available, the on-line help in there may give you more information and examples than that in 10g. Unfortunately when 9i removed OLE2, they also removed the help, and it did not come back when webutil reintroduced CLIENT_OLE2.

Similar Messages

Error handling for inbound function module

Dear all,
I have written my custom function module for matmas idoc extention.In the begining of function module i have used IDOC_INPUT_MATMAS01 and then have coded my BDC.For handling errors in caese BDC fails i am filling table idoc_status. wih status 51.
But this gives eror as-
Status records with status 51 after status 53
Message no. B1357
Diagnosis
The application function module controlling the ALE inbound processing has passed several status records to ALE. The status of the last of these was '51'. Before this, a status of '53' was passed.
Procedure
If you have written the application function module yourself, you need to change the program.
Can anybody guide me how to get the exact application errors in Application log.
Thank you.

Hi,
You are using BDC after the FM 'IDOC_INPUT_MATMAS01'. Right??.... The problem is, The function Module IDOC_INPUT_MATMAS01 itself posts the material and set the status '53' i.e. document posted. You can not have any error status '51' after that.
I don't understand the need of BDC in spite of the FM 'IDOC_INPUT_MATMAS01'. But if whatever the reason, you still want to use the BDC and set the status to 51, After the FM 'IDOC_INPUT_MATMAS01' call, Delete status table where status = '53'. and then proceed for the BDC...

3.2 to 4.1 Upgrade - Error Handling for Unavailable Database Links

Hi,
I'm having a 3.2 -> 4.1 upgrade issue related to error handling for failed database links.
I have a conditional Exists button on a page that has a SQL query to linked tables. However, for the 10 minutes every day where the target of the database link is getting a cold backup, the query fails. In the old 3.2 apex I simply got an error inside the region where the button is located but otherwise the page was still visible:
"Invalid exists/not exists condition: ORA-02068: following severe error from MYDBLINK ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist"
However, in apex 4.1.0.00.32 I get the following unhandled error, and clicking "OK" takes me to the edit page when logged in as developer.
i.e., the page can't be run at all while the database links are failing in this one region.
Error Error processing condition.
ORA-12518: TNS:listener could not hand off client connection
Technical Info (only visible for developers):
is_internal_error: true
apex_error_code: APEX.CONDITION.UNHANDLED_ERROR
ora_sqlcode: -12518
ora_sqlerrm: ORA-12518: TNS:listener could not hand off client connection
component.type: APEX_APPLICATION_PAGE_REGIONS
component.id: 4
component.name: Current Alerts
error_backtrace:
ORA-06512: at "SYS.WWV_DBMS_SQL", line 1041
ORA-06512: at "APEX_040100.WWV_FLOW_DYNAMIC_EXEC", line 687
ORA-06512: at "APEX_040100.WWV_FLOW_CONDITIONS", line 272
General users see this:
Error Error processing condition.
ORA-01034: ORACLE not available ORA-02063: preceding line from MYDBLINK
clicking "OK" takes user to another page, not sure how apex decides which, but not a concern at the moment.
I've done a search and read the page http://www.inside-oracle-apex.com/apex-4-1-error-handling-improvements-part-1/ but the new apex error handling isn't clear to me, and I don't know if the apex_error_handling_example provided on that page would be applicable to this situation.

Thanks Patrick.
The PL/SQL Function Body returning boolean condition with:
begin
    for l_check in (
      SELECT 1
       FROM myview@MYDBLINK
      WHERE ... ) loop
        return true;
    end loop;
    return false;
exception when others then
    sys.htp.p('Invalid exists/not exists condition: ' || sys.htf.escape_sc(sqlerrm));
    return false;
end; Resulted in a similar issue:
Error Error processing condition.
ORA-04052: error occurred when looking up remote object MYLINKUSER.myview@MYDBLINK
ORA-00604: error occurred at recursive SQL level 3
ORA-01033: ORACLE initialization or shutdown in progress
ORA-02063: preceding line from MYDBLINK
Technical Info (only visible for developers)
is_internal_error: true
apex_error_code: APEX.CONDITION.UNHANDLED_ERROR
ora_sqlcode: -4052
ora_sqlerrm: ORA-04052: error occurred when looking up remote object MYLINKUSER.myview@MYDBLINK
ORA-00604: error occurred at recursive SQL level 3
ORA-01033: ORACLE initialization or shutdown in progress
ORA-02063: preceding line from MYDBLINK
component.type: APEX_APPLICATION_PAGE_REGIONS
component.id: 4
component.name: Current Alerts
error_backtrace:
ORA-06512: at "SYS.WWV_DBMS_SQL", line 904
ORA-06512: at "APEX_040100.WWV_FLOW_DYNAMIC_EXEC", line 588
ORA-06512: at "APEX_040100.WWV_FLOW_CONDITIONS", line 148However, I created a view with the same query:
CREATE OR REPLACE VIEW v_localview (ALERT_1)
AS
SELECT 1
FROM myview@MYDBLINK ...then change the condition to look at the local view:
begin
    for l_check in (
      select alert_1 from v_localview ) loop
        return true;
    end loop;
    return false;
exception when others then
    sys.htp.p('Invalid exists/not exists condition: ' || sys.htf.escape_sc(sqlerrm));
    return false;
end;As a view is simply a query I'm surprised this should make any difference but it now looks similar to the 3.2 error, inside the region, when the linked database gets its morning cold backup, and this is fine:
Invalid exists/not exists condition: ORA-12518: TNS:listener could not hand off client connection

Found no handler for remote function module SPC_GET_PRICING_PROCEDURE_INFO

Hi
We are on CRM 7.0 with ECC 6.0 as backend system.
I have maintained all the settings that are required to create a sales order.
But i am getting one error in header area::
Found no handler for remote function module SPC_GET_PRICING_PROCEDURE_INFO
Could any one provide me information on this.
Thanks in advance

Hi,
Check this note.
884991
Your problem is related to VMC
Feel free to revert back.
-=-Ragu

Error handling for work item

Dear All,
     When I trigger my workflow from SWUE,the workflow containers must be populated with agent name.But it is populated only with 'US'.Please suggest.
     On the other hand, when I trigger my workflow from ME21N,the workflow goes into error.The error statement is "Exception occurred - Error handling for work item 000000954797".What is the problem?
    Please suggest the solution for which I will be grateful.
Thanks and regards,
S.Suresh

Dear ,
I use bus2012 as BOR and event as created.
When I create purchase order from ME21N,bus2012 is not triggering.Instead FREBUS2012 gets triggered which is a subtype of bus2012.
At SWETYPV,event linkage is activated only for BUS2012 and there is no entry at SWETYPV for FREBUS2012.
Though I configured the workflow with start events:BUS2012->created,why FREBUS2012 should trigger my workflow which is not seen in SWETYPV?How to override it?Please suggest.
There is no start conditions for my workflow.Whenever purchase order is created,this workflow should trigger.
So,the parameters passed between even to workflow are
&_EVT_OBJECT&    ->        &BUS2012&
&_EVT_CREATOR&   ->     & WFINITIATOR&
Thanks and regards,
S.Suresh

Error handling for a save button

hi. how do i get error handling say in a button, and then to give an error to the user, without crashing the whole application. can any one point me to any articles, tried searching , and not finding wxactly what i am looking for. thanks.
http://startrekcafe.stevesdomain.net http://groups.yahoo.com/groups/JawsOz

hi. maybe i did not make my self clear. okay, here's how this button works, you have a open dialog button, and a open dialog box, you click the file, and it loads in the data grid. now you click on the save button, and a message says file was saved, need
try / catch code, to catch this, if the file was not saved, or other errors, then a error friendly message, any code for this. read the article, but need a specific error handler for the save button, like i had for the open dialog file dialog box. any suggestions,
or links, to look at sample code. thanks.
http://startrekcafe.stevesdomain.net http://groups.yahoo.com/groups/JawsOz

Error handling for RGB values

Hi
I am having problems doing error handling for RGB values. I have a Java applet with 3 JTextFields whose values are parsed as int variables and stored as ints. If a value is entered that is not a value between 0 and 255 is entered, the appropriate field/s should be set to an empty string.
The problem I am having is that I am using try/catch block to try to parse as an int but then it breaks out of execution completely.
I hope this makes sense and that someone can help.
Thanks!

this is because your code is probably inside one giant try catch block, what you need to do is have small ones in places where you do the parsing.
post code and i can show you how to modify it

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

Error Handling for Outbound IDOC - COSMAS (Cost Center Master)

Hi,
I need to trigger a mail to SAP inbox whenever a outbound idoc fails for any reason.
I know how to do it for inbound or outbound transaction data, but not sure how to do error handling for outbound master data.
Could one of you help me understand the same.
Thanks in Advance,
Vinoth

Hey Vinoth,
Do you want decide the recipient of the mail dynamically? am asking because if you give the USER NAME in the partner profile and when ever a IDOC fails a mail will automatically reach the user inbox automatically
let me know if i answered ur question.
Thanks,
Santhosh

Latest Error Handling for Dynamic Actions

Is there any documentation on the Latest Error Handling for Dynamic Actions?

BillC,
Interesting that I was looking around for the same thing after seeing a Foreign Key violation in my application.
I found this article by Patrick Wolf:
APEX 4.1 – Error Handling Improvements – Part 1
http://www.inside-oracle-apex.com/apex-4-1-error-handling-improvements-part-1/
I believe you need to be on 4.1 or later though.
Thanks,
Joe

Error Handling for Dynamic Actions (4.1.1)

Hello
I'm trying to create a function to handle all possible errors but the errors generated by DA are not being caught.
Is it possible to caught them? How?
My function is based in:
http://www.inside-oracle-apex.com/apex-4-1-error-handling-improvements-part-1/
http://docs.oracle.com/cd/E23903_01/doc/doc.41/e21676/apex_error.htm#autoId4
and I'm making my tests in apex.oracle.com
Thanks

Hi,
there is no APEX JS function which you could use to intercept the error display. But you might be able to overwrite the "window.alert" JS function which is used to show the error with your own implementation. This function could check the text for some patterns and then decide what to show to the user. I haven't tried this but
var originalAlert = window.alert;
window.alert = function( pMessage ) {
if ( pMessage ... some check comes here ... ) {
originalAlert( "My new message" );
} else {
originalAlert( pMessage );
};might work.
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Error Handling for Background/Update Tasks (Transfer Order creation) - How?

Hi,
I have a standard process for creating a Transfer Order and 2 user-exits that I have implemented.
The user exits are used to transfer information during Transfer Order creation.
However, the user-exits also check data in table TVARV and other. As such, error handling needs to be implemented, since the T.O. might or might not go through, depending on data validation and related.
However, the user-exits are implemented during creation, which is an update task that runs in the background. This makes it impossible to output any information or error messages.
What else can be done in regards to outputting a message, since the user will need to see some sort of message that the process failed, that the T.O. didnu2019t confirm? Can an SAP inbox message be created and how?
Please help.
Thank You,
John

Hi,
Please check the following link for all the function modules and user exits on TOs.
http://help.sap.com/saphelp_erp2005/helpdata/EN/c6/f83a294afa11d182b90000e829fbfe/content.htm
Reward points if it was helpful.
Regards
Abhishek
Edited by: Abhishek Raj on May 29, 2008 10:20 AM

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

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}

Error Handling for Bundled Updates

HI,
Runtime errors can occur during execution of bundled updates. How are they handled?

HI,
In general, COMMIT WORK processing occurs in the following order:
1. All dialog-task FORM routines logged with PERFORM ON COMMIT are executed.
2. All high-priority (V1) update-task function modules are executed.
The end of V1-update processing marks the end of the change transaction. If you used COMMIT WORK AND WAIT to trigger commit processing, control returns to the dialog-task program.
3. All low-priority (V2) update-task function modules are triggered.
All background-task function modules are triggered.
Runtime errors can occur either in the system itself, or because your program issues an termination message (MESSAGE type A). Also, the ROLLBACK WORK statement automatically signals a runtime error. The system handles errors according to where they occur:
in a FORM routine (called with PERFORM ON COMMIT)
Updates already executed for the current update transaction are rolled back.
(ii)No other FORM routines will be started.
(iii) No further update-task or background-task functions will be started.
(iv) An error message appears on the screen.
in a V1 update-task function module (requested IN UPDATE TASK)
(i)Updates already executed for V1 functions are rolled back.
(ii)All further update-task requests (V1 or V2) are thrown away.
(iii)All background-task requests are thrown away.
(iv)Updates already executed for FORM routines called with PERFORM ON COMMIT are not rolled back.
(v)An error message appears on the screen, if your system is set up to send them
in a V2 update-task function module (requested IN UPDATE TASK)
(i)Updates already executed for the current V2 function are rolled back.
(ii)All update-task requests (V2) still to be executed are discarded.
(iii) All background-task requests still to be executed are carried out.
(iv)No updates for previously executed V1 functions are rolled back.
(v)No updates previously executed for FORM routines (called with ON COMMIT) are rolled back.
(vi) An error message appears on the screen, if your system is set up to send them
in a background-task function module (requested IN BACKGROUND TASK DESTINATION)
Background-task updates already executed for the current DESTINATION are not rolled back.
(ii) All further background-task requests for the same DESTINATION are thrown away.
(iii)Other previously executed updates are rolled back.
(iv)No error message appears on the screen.
If your program detects that an error in remote processing has occurred, it can decide whether to resubmit the requests at a later time.
For further information about RFC processing, refer to the Remote Communications documentation.
Reward Points if found helpfull..
Cheers,
Chandra Sekhar.

ERROR HANDLING FOR CLIENT_OLE2 FUNCTIONS

Similar Messages

Maybe you are looking for