Execution properties, Enable automatic error handling

Hi
I am writing real-time code for standalone execution on a cRIO-9074.
If I untick the "Enable automatic error handling" option in VI properties (Execution), what is the consequence if I have an application with no error handling case structures to detect the occurrence of errors elsewhere and within subVI's ? Does the error just go undetected and the application continue regardless? If ticked, could a standalone application hang as there is no user-interface for the error to get reported automatically to? Can I configure the LabVIEW RTE to automatically handle errors in a certain way regardless of individual VI settings of the "Enable automatic error handling" option?
I am a bit confused by the usefulness of "Enable automatic error handling" within RT/FPGA code, and where in the development process it is best enabled then disabled (if necessary).
Thanks

If I untick the "Enable automatic error handling" option in VI properties (Execution), what is the consequence if I have an application with no error handling case structures to detect the occurrence of errors elsewhere and within subVI's ? Does the error just go undetected and the application continue regardless?
That's the case: the error is lost (i.e. it's not handled), and the application goes on.
If ticked, could a standalone application hang as there is no user-interface for the error to get reported automatically to?
The property "Enable automatic error handling" is not availabe in the run-time engine, so there's no automatic error handling in a built application,
Can I configure the LabVIEW RTE to automatically handle errors in a certain way regardless of individual VI settings of the "Enable automatic error handling" option?
No, for the reason stated above.
I am a bit confused by the usefulness of "Enable automatic error handling" within RT/FPGA code, and where in the development process it is best enabled then disabled (if necessary).
There's no "Enable automatic error handling" property in Labview RT either.
Regards,
Marco

Similar Messages

Displaying errors when Enable automatic error handling option is on

In order to display error messages do I need general or simple error handler to implement if I have Enable automatic error handling on?
Solved!
Go to Solution.

Both will (optionally) display a popup when an error occurs. The general error handler just has more options for special cases. The simple error handler is typically sufficient.
If you havce automatic error handing enabled, you'll get a popup whenever a function generates an error AND the error output is not wired. Once you wire an error handler, the automatic error handling will no longer occur.
To display an error, you can also just place a plain error indicator on the front panel. This avoids annoying popup messages.
LabVIEW Champion . Do more with less code and in less time .

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)

How to disable the LV error handler?

I want to disable the LV error handler, im my application if an error happens i use a case structure to handle it.
how can i do?

青风细雨楼 wrote:
I want to disable the LV error handler, im my application if an error happens i use a case structure to handle it.
how can i do?
Once you wire the error output of your function, automatic error handling is no longer relevant. That setting only matters for subVIs where you don't wire the error output.
Just take the error output and wire it to the selector terminal of the case structure. You'll get an "error" and a "no error" case. Place appropriate code in each case so it act like you want it to.
LabVIEW Champion . Do more with less code and in less time .

How to stop execution after generating error message in an error handler?

I am working on ALSB 3.0.I have a proxy consisting of 2 stages in a pipeline pair. I have error handlers for each of the stages. The first stage contains schema validation action. Whenever the schema validation fails,control should transfer to error handler.
The error handler has a publish action and in request action I am calling an xquery transformation to generate error message.Publish action should publish message to a jms based business service configured. My questions are:
1. After getting into the error handler, the first alert msg configured inside request action (of publish action) is generated.Subsequent actions to generate error xml message and to replace the contents of errorXml in $body are not executed.And so no error message is generated or published.
2. I have also configured a reply with failure. Inspite of that,the control shifts to next stage in request pipeline and execution continues.
Can anyone tell me where I need to do the corrections.
Cheers.
Edited by: arrajago on Jun 15, 2009 11:55 PM

Got the answer.Generate error xml outside publish action.Replace action has to placed inside Publish's request action.To stop execution,use Reply action after Publish.

Break execution after custom run-time error handler callback

I am using Teststand 2010 SP1 and have written a custom runtime error handler based on the ErrorHandlerExample example that ships with TestStand. It has been implemented as a StationPostStepRuntimeError callback in my Station Callbacks folder. I have modified the example as follows:
(1) Added code to turn off the UUT transmitter if it was on.
(2) Added a call to an executable that sends an email to the currently logged in user.
(3) Calls the standard TestStand run-time error dialog using the Engine DisplayRunTimeErrorDialog method.
(4) Processes the user's selection, then turns on the UUT transmitter for any option other then Abort.
The callback also checks the status of the Break and "Don't Show again for this execution" options selected by the user. If the user selects Break then the only option I can find is to call the API Execution.Break() method which breaks the execution right there in my callback. The user then has to single step there way out of the callback. Is there a way of instructing TestStand to complete the callback execution and break immediately after completing the callback (i.e.at the step following the error)? I've zipped up and attached my modified sequence.
Alternatively, is there a better way of doing this?
Regards,
David
Solved!
Go to Solution.
Attachments:
StationCallbacks.7z ‏13 KB

Didn't have a chance to try it yet but maybe StepOut is your solution?
From the TS Help:
StepOut Method
Syntax
Execution.StepOut
Purpose
Resumes the execution from a suspended state and then suspends the execution again after execution of the current sequence completes.
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

Error handling -- automatic process chain

Hello Experts,
I need your suggestions.
1) I want to set up the error handling for the ILTC(Intiail load from the trusted client). Do I need to create a process chain to handle errors manually? or will the Process type 'Error handling for ILTC' collects and creates the process chain for the each object type?
2) Say some how the process chain for the error objects has started. How can the error objects be handled automatically ?
Thanks,

Dear Sweatha,
1 - You have to create a process chain with a start step, error handling step and a step to edit data and then a post step
2 - If error occurs during ILTC, the error handling chain will be started automatically. Data will be stored in the error handling step.
To process the error really you have to go to the error handling monitor and press the continue button. Data will be sent to the edit step. Here you can correct manually the errors.
Please find additional information in the SAP Help Portal: http://help.sap.com/saphelp_mdm300/helpdata/EN/88/454ba493cb43f1b74336772a7f3508/frameset.htm
Kind regards,
Markus

Enable Goods Movement Error Handling on Inventory Management

Hello gurus.
The Production department uses transaction COGI (Automatic Goods Movement Error Handling) to track what automatic goods issues were not performed due to errors like stock deficit, etc.
My question is; is it possible to use this same COGI transaction to store manual goods movements that also end up in an error?
For example, if I go to MIGO and I perform a Goods Issue with Movement Type 201; if I don't have enough stock of the material, normally I get an error and I cannot continute; instead I want the movement to fail and go to transaction COGI, where I can deal with it later.
The main goal is not to interrupt the capture of the Goods Issues, if there is not enough stock in the system, the person should not stop to correct the error. It's something that is desired to deal with later.
Any possibilities that you see?

Hi,
COGI transaction is Goods movements error status while process order or production order level.
If Goods are not avaiable in store/warehouse, how to post thru' 201 movement. In case stock is avaiable goods movements are only thru' 261 movement.
regards,
satish kumar

Bursting with JAVA APIs / MultiThreading / Errors Handling

We are trying to use the bursting JAVA APIs 10.1.3.3.1 Standalone) to burst huge XML files and generate PDF Files from RTF templates. Here are a list of our issues with this feature:
1. We have some problems catching the errors when bursting. We have tried to use the "oracle.apps.xdo.common.log.Logger" class, but it is not always reacting like we think it should. Could you please give us an exemple of a clean bursting error catching or a brief description of how we could do it. We have a lot of difficulties to find information about using the JAVA APIs of BIP.
2. Is it a clean way of catching the bursting errors to use the "oracle.apps.xdo.common.log.Logger" class?
3. When using the 10.1.3.3.1 DocumentProcessor JAVA API, the process gets killed when the RTF template is not where the control file specified it. Even when using a finally clause containing the document processor, we can't fetch the error from the "oracle.apps.xdo.common.log.Logger" class. We did not find a way to catch this error which make our program crash.
4. How can we enable multi-threading that is included in the DocumentProcessor JAVA APIs so it can take advantage of the multi-processors environnements?

1. Check tim d. blog, you can use the bursting listners to get the errors. It's also in the documentation.
First, on every exception, the Bursting APIs are dumping the error in the Logger. So I can't see how we can use the listeners to catch these. We can check the hasExceptions on the Logger but still, we have some problems with this. When we deploy our application as a MDB (Message driven bean), it seems that once the hasException flag has been raised, if we call the MDB again, it is still up. Is there documentation about that Logger class? Also, I'm worried that we won't be able to call our MDB twice to run simultaneously 2 different bursting process since it seems the Logger is something static, keeping every exception in memory... That's bad.. And show me where you have found documentation about this. All I see in documentation is how to call the DocumentProcessor in a couple of lines. I don't see anything about a clean way to catch errors.
2. Yes/No/Depends. I think it's fine. If your changing the logger options in your program that could come back to haunt you.
I guess so, I'm not changing anything and its already haunting me...
3. When using the 10.1.3.3.1 DocumentProcessor JAVA API, the process gets killed when the RTF template is not where the control file specified it. Even when using a finally clause containing the document processor, we can't fetch the error from the "oracle.apps.xdo.common.log.Logger" class. We did not find a way to catch this error which make our program crash.
Even worst, when we deploy the component has an MDB, when the error happens, it kills the whole oc4j container... please correct this quick.
4. How can we enable multi-threading that is included in the DocumentProcessor JAVA APIs so it can take advantage of the multi-processors environnements?
We got an answer from the dev team which is to add two properties to the document processor, something like:
enable-multithreading: true
thread-count: >2
We did that and what we got is that the process started and it got stuck in a dead lock at the first document processing. How nice! :)
We got a milestone in March and I'm really worried about all those problems... Not enough documentation, a pretty bad error handling, errors making crash the whole oc4j container, Logger seems not to be handling simultaneous calls/ threads, not even handling two subsequent calls... etc.
If anyone has the magic answer, it would be pretty welcomed!
Thanks

Use of "Error Handling" Tab in InfoPackage Update Tab?

Hello All
I want to know the Use of "Error Handling" Tab in InfoPackage Update Tab?
Options in this tab are like
1.No Update,no reporting
2.Valid records update,no reporting(request red)
3.Valid records update,reporting possible(request green)
Terminate After No.Errors _________
4.No Aggregation Allowed
Will anyone tell about this in detail?
Many Thanks
balaji

Hi,
No update, no reporting (default):
If errors do occur, the update of the entire data packet is canceled. The request is not released for reporting. However, the records check continues.
Updating valid records, no reporting (request red) :
This option enables you to update valid data that is released for reporting only after the administrator has checked the incorrect, not updated records, and has manually released the request (by a QM action, meaning setting the Overall status on the tabstrip Status in the monitor).
Updating valid records, reporting possible :
The valid records can be reported on immediately. Automatic follow-up actions are also carried out, such as adjusting the aggregates.
With option a) the incorrect records are marked in red in the PSA maintenance. You can display the relevant error messages amodally, edit the records, and update the request manually. If it was not possible to write into the PSA (hierarchy or transfer method IDoc), an application log is written instead.
With options b) and c) a new request that is only read into the PSA is formed from the incorrect records. Here you can edit the records of the new request in the PSA and start the update manually.
For more information please refer the URL below.
http://help.sap.com/saphelp_bw30b/helpdata/en/05/bb223905b61b0ae10000000a11402f/frameset.htm
Regards,
K.Manikandan.

General error handling operation

Hi,
I did not find a comprehensive explanation how error handling works in TestStand, only bits and pieces about the callbacks (perhaps I looked at the wrong places).
Anyway, I made some experiments with SequenceFilePostStepRuntimeError and StationPostStepRuntimeError - intentionally leaving out ProcessModelPostStepRuntimeError to reduce complexity - and came up with the attached flow chart. I would like to know:
if that shows the correct operation of TestStand error handling (we are currently using 4.1, about to switch to 2010 or 2012, so it would also be interesting to know if anything changes with the new versions)
if it is always the case that the combination of ErrorReported=True und Error.Occurred=True after the error handler leads to termination of the execution? I could not find any setting governing that (the "goto cleanup immediately" setting of the sequence was off;
Best regards
Peter
Attachments:
TestStand_ErrorHandling.png ‏36 KB

Hi Peter,
1) Every step has :
error.code - to set the error code
error.occured - boolen if set true displays a popup error message to the user
error.message - the popup contains this message
when you set error.occured=true it will bring up a popup message with the error.message and error.code.
Please note that this may not be acceptable in the manufacturing environment where operators may not be trained to check for errors.
The general practice in manufacturing is to fail all important steps that errors out so that the final result is failed.Then do a offline analysis.This is done by step.results.status = "Failed".You can also populate step.results.ReportText with proper values so that your test report reflects the type of error/failure.
2) Regarding the SequenceFilePostStepRuntimeError and StationPostStepRuntimeError - they are optional error handling methods if you want to act on errors.
3)Every step has an option ( look for properties-->post actions).On Pass or On fail destinations can be set for each step.Cleanup is always executed except in cases of abort.
4) In the menu configure-->Station options-->execution there is an option for runtime errors ( one of them is run cleanup).
Hope the above information helps.

Unable to get automatic event handling for OK button.

Hello,
I have created a form using creatobject. This form contains an edit control and Search, Cancel buttons. I have set the Search buttons UID to "1" so it can handle the Enter key hit event. Instead its caption changes to Update when i start typing in the edit control and it does not respond to the Enter key hit. Cancel happens when Esc is hit.
My code looks like this -
Dim oCreationParams As SAPbouiCOM.FormCreationParams
        oCreationParams = SBO_Application.CreateObject(SAPbouiCOM.BoCreatableObjectType.cot_FormCreationParams)
        oCreationParams.UniqueID = "MySearchForm"
        oCreationParams.BorderStyle = SAPbouiCOM.BoFormBorderStyle.fbs_Sizable
                Dim oForm As SAPbouiCOM.Form = SBO_Application.Forms.AddEx(oCreationParams)
oForm.Visible = True
'// set the form properties
        oForm.Title = "Search Form"
        oForm.Left = 300
        oForm.ClientWidth = 500
        oForm.Top = 100
        oForm.ClientHeight = 240
        '// Adding Items to the form
        '// and setting their properties
        '// Adding an Ok button
        '// We get automatic event handling for
        '// the Ok and Cancel Buttons by setting
        '// their UIDs to 1 and 2 respectively
        oItem = oForm.Items.Add("1", SAPbouiCOM.BoFormItemTypes.it_BUTTON)
        oItem.Left = 5
        oItem.Width = 65
        oItem.Top = oForm.ClientHeight - 30
        oItem.Height = 19
        oButton = oItem.Specific
        oButton.Caption = "Search"
        '// Adding a Cancel button
        oItem = oForm.Items.Add("2", SAPbouiCOM.BoFormItemTypes.it_BUTTON)
        oItem.Left = 75
        oItem.Width = 65
        oItem.Top = oForm.ClientHeight - 30
        oItem.Height = 19
        oButton = oItem.Specific
        oButton.Caption = "Cancel"
oItem = oForm.Items.Add("NUM", SAPbouiCOM.BoFormItemTypes.it_EDIT)
        oItem.Left = 105
        oItem.Width = 140
        oItem.Top = 20
        oItem.Height = 16
        Dim oEditText As SAPbouiCOM.EditText = oItem.Specific
What changes do i have to make to get the enter key to work?
Thanks for your help.
Regards,
Sheetal

Hello Felipe,
Thanks for pointing me to the correct direction.
So on refering to the documentation i tried out a few things. But I am still missing something here.
I made the following changes to my code -
oForm.AutoManaged = True
oForm.SupportedModes = 1 ' afm_Ok
oItem = oForm.Items.Add("1", SAPbouiCOM.BoFormItemTypes.it_BUTTON)
        oItem.Left = 5
        oItem.Width = 65
        oItem.Top = oForm.ClientHeight - 30
        oItem.Height = 19
oItem.SetAutoManagedAttribute(SAPbouiCOM.BoAutoManagedAttr.ama_Visible, 1, SAPbouiCOM.BoModeVisualBehavior.mvb_Default)
        oButton = oItem.Specific
        oButton.Caption = "OK"
AND
oForm.Mode = SAPbouiCOM.BoFormMode.fm_OK_MODE
oItem = oForm.Items.Add("1", SAPbouiCOM.BoFormItemTypes.it_BUTTON)
        oItem.Left = 5
        oItem.Width = 65
        oItem.Top = oForm.ClientHeight - 30
        oItem.Height = 19
oItem.AffectsFormMode = False
I get the same behaviour OK button changes to update and enter key does not work.
Could you please tell me find what is it that i am doing wrong?
Regards,
Sheetal

Error handling in File - XI - SOAP scenario without BPM

Hello!
We have a File -> XI -> SOAP scenario without BPM. The problem is that if the Web Service sends back an error XI tries to reprocess the same message again and again instead of taking the next one.
We do not want set the retry interval to NULL because most error cases are temporary connection problems and then also those messages would not automatically be reprocessed any more.
We also have to use BE instead of EO, otherwise the Web Service will not return a response. But we need the response to be sure that the processing was successful. The message volume in this scenario is quite high and we do not want to use BPM only for the error handling.
I know that from SP19 some additional adapter modules are available for async - sync scenarios without BPM. I tried to configure it like described in File - RFC - File without a BPM - Possible from SP 19. but it did not solve the problem. Does anybody have any other ideas? Thanks.
Regards, Tanja

Hi Tanja,
>>>The volume is 3000 messages/day on business days and 700 messages/day during weekends but the traffic will increase in the future
I think, you should check that out. It is assumedly only 2 days work to build a scenario:
IDoc -> BP
BP <-> SOAP/HTTP
BP -> IDoc (Acknowledgement)
In the process you need a condition branch, where you decide success or not. You need 2 Interface Mappings for filling the ALEAUD.
Just send 1000 IDocs to the Test-XI and look to performance monitoring at Runtime Workbench, to find out, how many message will be processed in one hour. Assumedly 3000 and more per day should be possible. The advantage would be to reduce number of systems (no file system) and messages (better monitoring) and using the standard (better maintenance).
>>>So you are suggesting I should use HTTP adapter and then add the SOAP header manually in a mapping?
Yes, build the SOAP envelop during the mapping. Most easy is to use XSL or, if your mapping is ready, an additionsal XSL. You can put the error into the Acknowledgement to see it in ERP transaction WE02.
Filling of ALEAUD fields:
E1ADHDR/MESTYP: original message type
E1ADHDR/E1STATE/DOCNUM: original IDoc number
E1ADHDR/E1STATE/STATUS: 68 in case of error, 53 in case of success
E1ADHDR/E1STATE/STATXT: Short description for R/3 user what has happend
I ve done such a scenario several times. That works without any problems.
Regards,
Udo

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

Is there a way to find out that a variant is of type vt_null, without using an error handler?

i am using an persistant ado-recordset. some fields may return a variant of type vt_null (sql-null value).
i want to figure out if a field contains a null or an empty string. when i checked the "view type" at a variant control, i see that labview correctly recognize a null value.
making a compare with "not a refnum/number/..." does not work. checking against a null string also don't work.
i used "variant flatten string" and "flatten string" but there is no difference between a field containing data and a null field (the type string tells me that is a reference to the variant, neither function 'flatten' the refrenced variant)
"varaint to data" results in an error, whe
n used with lv-native datatype and trying to convert a null-value. but the function has to return a variant, so using an error-handler is not an option. (converting variant-null to variant-data does not produce an error)
i also tried to get the "attribute" "value type"; it is not accessable with this function, like "attribute" "value".
is there a way to extract the variant data-type from a variant? or any other soloution to find out that a variant carries a null-value?

Hi,
sorry, i got no idea how to get the datatype of a variant, but there are properties "ActualSize" and "Type" of the ADO Field-Object. In case of an empty field the ActualSize is zero. Maybe you can use that. See VI below.
best regards
chris
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"
Attachments:
DB_Test.vi ‏67 KB

Execution properties, Enable automatic error handling

Similar Messages

Maybe you are looking for