.Not executable subVI

Using LabView / fieldpoint with FP-1601, FP-TC-120 and FP-DO-410 I can use MAX to test the inputs and outputs, however when setting up any fieldpoint application in the labview window I get an error, of which states 'the subVI is not executable'. I've checked and re checked but cannot seem to bypass this happenning. There must be something small I'm not getting set up right. Any ideas? Thanks in advance.
Steve
Attachments:
run1.vi ‏195 KB

Hi Docbritzel
Im not sure but maby this link will help you.
regards
Manuel

Similar Messages

Tried the solutions posted for this "SubVI filter not executable. Undefined error" but not solving the problem

Hello,
I am trying to use a lowpass filter for my application but getting the error "SubVI filter not executable. Undefined error".I tried working with the solutions at this post
http://forums.ni.com/t5/LabVIEW/SubVI-filter-not-executable-Undefined-error/m-p/1996701#M657751 and results with
1. Create a blank vi, put a VI filter in the block diagram (this should not be functional as it is not wired), copy it and paste it in my other project. I believe if the filter is the first vi of a blank project, it is funcitonal and then you may copy it wherever you need to.
Result:
2.Tried to open the filter panel of the Filter but showing the same error as shown inthe below image
Don't why the solutions worked for others are not working.Can someone suggest a solution for this.
thanks in advance.

Hi PatanGova,
Very strange error. Actually, there are no required inputs on this express VI, so it should be able to run even without wires. It is not correct as you said: "this should not be functional as it is not wired". Nothing will happen, true, but the run arrow should not be broken.
For some reason, the VI with the Filter express VI fails to compile. I tried it on my computer (LV 2013) and get no error when I add it to a new VI. As was suggested in the linked forum thread, you need to open the front panel of the Filter VI and run it to see the explicit error.
If you do, do you also get the error:
"This VI claims to be part of a library that does not include the VI. The VI might have been deleted from the library. Add the VI to the library again or select File - Disconnect from the library."?
If you do, it seems that you may have a project library somewhere that has taken ownership of the express VI. The ownership prevents you from running or editing the express VI. To free the VI, you need to do one of two things. Either, you need to load the library into memory, or you need to disconnect the VI from the library. Either way, you need to find the project library that has taken the ownership of the VI. As soon as it is released, it should run for you. You release it by selecting File»Disconnect from Library on the VI.
The workaround described in your link (and also here: http://forums.ni.com/t5/LabVIEW/compatibility-problem-labview-2009-2010-2011-quot-This-VI-claims/td-... tells that you can make a copy of the VI and thereby create another instance that is free. This solution may work for you as well, but if not, you may not have created the copy properly. Maybe your copy of the VI also became part of some project library that took ownership. In either way, you should rather find the project library to release the VI before trying the workaround to copy it.
If project library ownership is not the problem, maybe the problem is connected to LV 2011, as most forum posters report that it only happens here.

Subvi is not executable error, but it has no error

Hey I hope you can help me with a weird error.
I got the error "SubVi 'name' : SubVi is not executable" but when I click on the SubVi and open it it does not show me any description of an error. If I open the main vi or the SubVi alone it shows no error. Could it be a problem of a library or something else?
I am using Labview 2012 and Labview 2012 Mindstorms NXT.
If you neew more screenshots or the rest of the SubVis please tell me so :-)
Thank you!
Jan
Attachments:
automatischer Modus - ohne Wait - ohne Array - global.vi ‏80 KB
Solar.vi ‏15 KB
project.png ‏262 KB

SmartCity-Project wrote:
Thanks for all your replies!
I found the error, the NXT does not support global variables in Target on NXT- Mode so I changed to Target on Computer - Mode and now it works.
Unfortunately the program crashes after 15 minutes more or less. Could you imagine why? Is it because of to many bluetooth connections or a bad programm structure?
After a very quick look at the code I would say that it is probably bad code. Your overuse of global variables, sequence structures and silly things like a For loop set to run once with everything inside the loop wrapped in a sequence frame is a goo dindication that you need to learn much more about data flow programming techniques. With the amount of global variables you are using your program is probably ripe with race conditions. In addition, you did not include any of the subVIs so we cannot see what is happening in them.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

SubVI not executable: many express VIs cannot be opened

When I create an icon of an express VI on the Block Diagram, "error loading National Instruments\LabVIEW 2012\resource\lvanlys.dll" appears. And when I double click the icon, it is shown on the screen "unable to view properties". I cannot run the VI, and the errors listed are like "SubVI 'simulate signal': SubVI is not executable". I do not know how to solve this problem.
Hope someone can help me. Thanks a lot!

What do you mean "create an icon of an express VI on the Block Diagram"? Give us enough steps to be able to reproduce (or test) your problem. Include:
Are you starting with a "blank" VI or a blank Project, i.e. starting from scratch?
What is on the Block Diagram before you "create the icon of an express VI"?
Which Express VI are you trying to use?
Lily092 wrote:
When I create an icon of an express VI on the Block Diagram, "error loading National Instruments\LabVIEW 2012\resource\lvanlys.dll" appears. And when I double click the icon, it is shown on the screen "unable to view properties". I cannot run the VI, and the errors listed are like "SubVI 'simulate signal': SubVI is not executable". I do not know how to solve this problem.
Hope someone can help me. Thanks a lot!

SubVI filter not executable. Undefined error.

Good morning,
During the development of a bigger labview project, I came to need filtering of my waveforms at some point. I am getting a broken arrow signaling the filter assistant :
"SubVI 'Filter' : SuvVI is not executable"
I thought it could have something to see with the whole program and thus created a simple VI of acquisition from a myDAQ aparatus and had the same error.
Do you have any idea how I could at least identify the error?
Thanks in advance,
David

David Pastorino wrote:
Good morning,
During the development of a bigger labview project, I came to need filtering of my waveforms at some point. I am getting a broken arrow signaling the filter assistant :
"SubVI 'Filter' : SuvVI is not executable"
I thought it could have something to see with the whole program and thus created a simple VI of acquisition from a myDAQ aparatus and had the same error.
Do you have any idea how I could at least identify the error?
Thanks in advance,
David
If you open the SubVI Filter and hit Ctrl+R LabVIEW should tell you what you need to fix in that VI.
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Open the VI in LabVIEW using File Open and verify that it is runnable.

When trying to run a sequence on a deployment machine I get this error. When I switch the Adaptor back to the Development System the problem goes away however I do not have the luxury of keeping the full Labview development on the test machine. Is there a know fix for this problem and what is the cause of this error. Here is the software and versions I am using. It seems that the vi's that are broken are using Invoke and Property Nodes within them, I am not sure if this is just a coincidence. It appears it is more related to the invoke node than the property node. Any help is greatly appreciated. Why does it seem everything works great until you try and deploy it on a test machine. This is not the first time I have had these kinds of problems using Nation Instruments software.
Labview 8.2.1
TestStand 4.0
Solved!
Go to Solution.

I have a similar problem.
A bit of background - I had developed a test suite with a Labview front panel for manual operations, and a Teststand project which used some of the same lower level vi's, and specific test step vi's. It was developed on LV 2010 32-bit and Teststand 2010. All was fine.
Recently i had to rebuild my development machine and installed only LV 64-bit 2011 and the latest (2010) Teststand from the 2012 Dev Suite.
I knew that i wanted to run some new hardware drivers in 64-bit versions due to another problem, so i replaced the .dll in the very lowest level VI with the 64 bit version. And ran the manual interface. All ok.
But when i try the Teststand execution, i get one of two errors:
- If i set Teststand to use the LV runtime engine 11.0.1 (2011 SP1), the i get a "Unable to load VI xxxxx with the runtime engine version '11.0'" Despite the fact that each VI does run correctly in LV dev when loaded individually, and i've saved them as version 11.
- If i set it to use the development system (which shows in the config menu 'active version:32-bit' even though 32-bit LV is not installed), then i get the "The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located." error, even though i when i open each VI in the LV 2011 it runs ok.
Any ideas?
How can i set TS dev system to use the 64-bit version? Or is there a separate 64-bit deployemrnt of TS?
Labview 2010, TestStand 2010

Open Specific WorkBook.vi: subVI is not executable error

Hi,
I'm trying to programaticaly change some cells of a specific worksheet and then saving it on a new file.
But I can't run the VI because I get the error Open Specific WorkBook.vi: subVI is not executable.
I've atteched a printscreen of my VI.
Any hints?
Daniel Coelho
Daniel Coelho
VISToolkit - http://www.vistoolkit.com - Your Real Virtual Instrument Solution
Controlar - Electronica Industrial e Sistemas, Lda
Solved!
Go to Solution.
Attachments:
VI.JPG ‏16 KB

This is the Open Specific WorkBook.vi with the error.
Daniel Coelho
VISToolkit - http://www.vistoolkit.com - Your Real Virtual Instrument Solution
Controlar - Electronica Industrial e Sistemas, Lda
Attachments:
VI2.JPG ‏140 KB

MS Office Report (Report Generation toolkit) is not executable, Xnode broken?

Hi, I am trying to generate an excel report, and I figured it would be easier to use the MS Office report VI, but I am getting the broken arrow saying the SubVI is not executable and that the library that defines the xnode is broken... here is a screensot attached, I already uninstall and reinstall the report generation toolkit and still the same... this is what I found on NI: "This error occurs when the library that defines the XNode you used is broken. To correct this error, reconfigure the XNode." but no idea how to reconfigure xnode
Attachments:
Error.png ‏67 KB

What version of LabVIEW are you using?
What is the nature of your Report? What should it look like? What kind of data should it contain?
Can you show us some code that you've tried to use? If so, include the code as either a Snippet or as a VI attachment (so we can plug it into our own LabVIEW installations and experiment with it).
I generally find that the Report Generation Toolkit is a very easy way to generate Excel Workbooks. I work primarily with LabVIEW 2012 and LabVIEW 2014.
Bob Schor

ADO function error:SQL execute.vi is not executable.

Thanks for everyone who is willing to help me out of this problem that puzzled me several days,I can't find a similar one from Google or other forum..
Problem:
When I was using LabSQL,it come an error:
Subvi "SQL execute":subvi isnot executable. and then I searched the source of the error,it was finally found to be the
"ADO Recordset GetString.vi":
"invoke node:invalid method"
"invoke node:invalid refnum class".
What I used is Windows 7 and LabVIEW7.1.
Attached is the detail of this problem that includes the vi and some error pictures,and the ADO functions I used.
ute.vi" is
Attachments:
Error.zip ‏1865 KB

Duplicate - http://forums.ni.com/t5/LabVIEW/ADO-function-error-SQL-execute-vi-is-not-executable/m-p/2397360#M742...
Try to take over the world!

VI seen as not executable from LV runtime, correct in LV development

My current problem is the following:
On the same PC, having TestStand 4.0 & LabVIEW Development 8.5, I try running a sequence with both adapters: LV development 8.5 and LV runtime 8.5.
My sequence steps call VIs that call subVIs in a full hierarchy (let's say 1500 VIs are involved in a test sequence).
The sequence runs with the development adapter, and with the runtime, I got a -18002 LabVIEW error: Vi not executable, broken, etc.
Of course, when I open the VI within the development environment, everything is correct.
As I'm testing both adapters on the same PC, the full hierarchy, including LV libraries provided with LV development are at the same location.
Due to the large amount of VIs I use, I cannot guess which LLB could be missing or not inaccessible.
Is there a way to investigate the cause, despite the fact that everything is correct under the development environment?
Is it possible to tell the LV runtime where it should search for LLBs or other required dependencies that the LV development seams able to find?
Thanks in advance for your help,
JJD
Solved!
Go to Solution.

Hello,
I've seen this error when two VIs withthe same name were loaded in memory; this VI was called from a TestStand sequence and from the user interface (very poor design of a customer that I will not mention ^^).
I'm not sure to understand youy problem: everything works fine when you are using Developpment system (Active Version 8.5) but, do you have this error when you set the adapter to LabVIEW Run-Time Engine 8.5, right? Are LabVIEW and/or VIs used in your sequence open when you run your sequence in Run-Time mode?
Cordially,
.mrLeft{float:left} .mrInfo{border-left:solid 1px #989898;font-size:x-small;color:#989898}
Mathieu R.
  CTD - Certified TestStand Developer / Développeur TestStand Certifié
  CLAD - Certified LabVIEW Associate Developer

Simulation interface toolkit: SUB VI not executable error

Hi;
I have a real-time application where I model things in Simulink and use Simulation Interface Toolkit to carry out hardware-in-the-loop simulations. As a real-time target, I am using NI-PXI8106 with NI-PXI6251 DAQ card on it. Up until now, I was able to run my code just fine. However, for some reason, my vi didn't work today and gave several errors such as:
SubVI NI_SIT_sitclient.Lvlib:RVE.vi: SubVI is not executable
Details:The SubVI is not executable. You must fix all error in the subVI before this VI can run.
SubVI NI_SIT_sit Init Model.vi: SubVI is not executable
Details:The SubVI is not executable. You must fix all error in the subVI before this VI can run.
This is just few of many error that I received...In the details section of the error list window, the error statement are usually like the following:
SUBVI not supported for current target..
Type not supported in the current target...
The only thing that changed since the last time I ran this program with success is the IP change of the target machine..However, when I use Measurement and Automation tool, I am able to access my target machine (PXI8106) without a problem...Maybe there are some certain rules for IP settings on the PXI target? ...I can provide the details of my new IP configuration numbers if necessary...
I also reinstalled the SIT 5.0 on the target machine but It didn't do the trick. I am wondering if there is anyone out there who can help me out with this problem..
Thank you so much!
Kind Regards.

Hi there,
I was just wondering if you did manage to solve this problem. I'm a new user and have recently started using the Simulation interface toolkit. I have created my model using Simulink and used the real-time workshop to convert it to a .dll file. I tried to run it on labview and it seems to build it on the realtime target, however as soon as map it to the hardware (using a NI BNC-2111,It's just a bunch of analog inputs and output which I have connected to a voltmeter), a dialog box pops up with the the following error:
Error 1003 occurred during host VI initialization: SIT_test1.vi >> NI_SIT_sitclient.lvlib:sit Init Model.vi >> NI_SIT_sitclient.lvlib:sit Connect to Target.vi
<append>=========================
Simulation Interface Toolkit: The driver VI (SIT_Test_Driver.vi) is not executable.
Check the following:
1) You have not modified the driver VI.
2) You properly installed SIT and any necessary driver software on the target.
3) The target has not been locked from Measurement and Automation Explorer.
Do you want to launch the SIT Connection Manager dialog box and reconfigure the simulation?
Please look at the JPEG picture attached below to see how the error looks on my monitor.
Thanks
Attachments:
error1.JPG ‏135 KB

BPM send step not executed in BPM (after Message split)

Hello everybody,
we use BPM:
We have a paralell Block which should send the rows of a multiline element. In SXMB_BPE_MONI the send step is not executed?
Any idea?
Thanks lot, regards Mario

HI,
Go to SXMB_MONI_BPE->and check the workflow log (technical details).and go to SXI_CACHE and check the return code of the Integration Process. It should be zero. If not try to activate the same
If there is no error then go with like this-
Also check the Syntax in Integration Repository with F7. Change the IP and activate it. If there is no syntax errors.
Then reimport the IP into Directory and then test your scenario
Regards,
Moorthy

I recieve the following error when running an executable ("This VI is not Executable. The full development version of Labview is required to fix the errors"

I recieve the following error when trying to build and run a labview executable. I am able to build the executable but when trying to run the executable, a pop up window comes up asking the user to select a dll. (please see screen shot attached). Once the DLL is selected, I get the error that This VI is not Executable. The full development version of Labview is required to fix the errors. (please see screen shot attached). I have also attached a snapshot of the project window.
I have the professional development system
I can run the main VI
all the required DLL's are in the dependencies section of the project window.
I am trying to find the root cause of this error but to no avail. can anyone give me a clue to what i am missing here. Any suggestions on where i should look to find the problem ?
Thanks in advance to all labview users for your help
Attachments:
project window.PNG ‏36 KB

other PNG
Attachments:
Broken Arrow on EXE.PNG ‏179 KB

I get a "vi is not executable" error when building an application.

I have an ongoing project that has worked fine in the past when building an application. I have recently added some report generation toolkit vis(Excel) and get an error for some of the ni vis and some of my own that call lower level excel vis. The error is that he vi is not executable, however they run fine in the development environment. I do not get this error if I save all vi's into one llb with save with options command and then build. However, when I try to run the app, this error re-appears. Also, do I have to add the dynamically loaded vi's that are part of the toolkit in my build script? Could this be the cause of the problem? If so, what's the best way to find all of them? Any suggestions?

You have hit in on the nail! You do need to add the dynamically loaded VIs when you are creating an executable from your VI. You need to add _wordsub.lib and _exclsub.lib as dynamically loaded VIs into your executable. Try this and let us know if you have any more problems with it.
J.R. Allen

PROCEDURE IS NOT EXECUTED WITH IN THE DATABASE TRIGGER

The follwing databse trigger works fine but the procedure lv_calc_pkg.p_orders_executed(:new.stock_code,:new.selling,:new.buying,:new.qty,:new.price); is not executed
please help
CREATE OR REPLACE TRIGGER SE.LV_SUMMARY_TRADE_TR
AFTER INSERT
ON SE.LV_DAILY_TRADES
REFERENCING NEW AS NEW OLD AS OLD
FOR EACH ROW
DECLARE
vstock gn_stocks.stock_code%TYPE;
CURSOR stock_cur
IS
SELECT stock_code
FROM lv_trade_summary
WHERE stock_code = :NEW.stock_code;
BEGIN
OPEN stock_cur;
FETCH stock_cur
INTO vstock;
IF stock_cur%NOTFOUND
THEN
INSERT INTO lv_trade_summary(
     the_time,
     the_date,
     stock_code,
     stock_type_id,
     market_id,
     deals,
     price,
     qty,
     trade_value,
     le_value,
     buying,
     selling,
     rec_count,
     rec_serial,
     buying_count,
     close_price,
     coupon_value,
     currency,
     dividend_yield_perc,
     eps,
     free_stocks,
     hi_offer,
     hi_req,
     hi_req_qty,
     high_date,
     high_price,
     last_offer,
     last_request,
     last_trade_date,
     less_offer,
     less_offer_qty,
     less_request,
     liquid,
     low_date,
     low_price,
     market_cap,
     off_count,
     prev_close,
     prop_avg_ofr_10,
     prop_avg_rqst_10,
     prop_avg_ofr_5,
     prop_avg_rqst_5,
     prop_avg_offers,
     prop_avg_rqst,
     req_count,
     rqst_to_offers,
     sector_desc_a,
     sector_desc_e,
     selling_count,
     simple_avg_ofrs_10,
     simple_avg_rqst_10,
     simple_avg_ofr_5,
     simple_avg_rqst_5,
     simple_avg_offers,
     simple_avg_rqst,
     stock_count,
     stock_desc_a,
     stock_desc_e,
     sum_less_ofr_10,
     sum_less_rqst_10,
     sum_less_5_rqst,
     sum_offer,
     sum_volume_traded,
     trx_count,
     sum_request,
     last_request_qty,
     last_offer_qty )
VALUES (
     :NEW.the_time,
     :NEW.the_date,
     :NEW.stock_code,
     :NEW.stock_type_id,
     :NEW.market_id,
     :NEW.deals,
     :NEW.price,
     :NEW.qty,
     :NEW.trade_value,
     :NEW.le_value,
     :NEW.buying,
     :NEW.selling,
     :NEW.rec_count,
     :NEW.rec_serial,
     lv_calc_pkg.f_buying_count (:NEW.stock_code),
     lv_calc_pkg.f_close_price (:NEW.stock_code),
     lv_calc_pkg.f_coupon_value (:NEW.stock_code),
     lv_calc_pkg.f_currency (:NEW.stock_code),
     lv_calc_pkg.f_dividend_yield_perc (:NEW.stock_code),
     lv_calc_pkg.f_eps (:NEW.stock_code),
     lv_calc_pkg.f_free_stocks (:NEW.stock_code),
     lv_calc_pkg.f_hi_offer (:NEW.stock_code),
     lv_calc_pkg.f_hi_request (:NEW.stock_code),
     lv_calc_pkg.f_hi_request_qty (:NEW.stock_code),
     lv_calc_pkg.F_HIGH_DATE (:new.stock_code),
     lv_calc_pkg.F_HIGH_price (:new.stock_code),
     lv_calc_pkg.f_last_offer (:NEW.stock_code),
     lv_calc_pkg.f_last_request (:NEW.stock_code),
     lv_calc_pkg. F_LAST_TRADE_DATE(:new.stock_code),
     lv_calc_pkg.f_less_offer (:NEW.stock_code),
     lv_calc_pkg.f_less_offer_qty (:NEW.stock_code),
     lv_calc_pkg.f_less_request (:NEW.stock_code),
     lv_calc_pkg.f_liquid (:NEW.stock_code),
     lv_calc_pkg.f_low_date(:new.stock_code),
     lv_calc_pkg.f_low_price(:new.stock_code),
     lv_calc_pkg.f_market_cap(:new.stock_code),
     lv_calc_pkg.f_off_count (:NEW.stock_code),
     lv_calc_pkg.f_prev_close (:NEW.stock_code),
     lv_calc_pkg.f_prop_avg_best_10_ofrs (:NEW.stock_code),
     lv_calc_pkg.f_prop_avg_best_10_rqst (:NEW.stock_code),
     lv_calc_pkg.f_prop_avg_best_5_ofrs (:NEW.stock_code),
     lv_calc_pkg.f_prop_avg_best_5_rqst (:NEW.stock_code),
     lv_calc_pkg.f_prop_avg_offers (:NEW.stock_code),
     lv_calc_pkg.f_prop_avg_rqst (:NEW.stock_code),
     lv_calc_pkg.f_req_count (:NEW.stock_code),
     lv_calc_pkg.f_rqst_to_offers (:NEW.stock_code),
     lv_calc_pkg.f_sector_desc_a(:new.stock_code),
     lv_calc_pkg.f_sector_desc_e(:new.stock_code),
     lv_calc_pkg.f_selling_count (:NEW.stock_code),
     lv_calc_pkg.f_simple_avg_best_10_ofrs (:NEW.stock_code),
     lv_calc_pkg.f_simple_avg_best_10_rqst (:NEW.stock_code),
     lv_calc_pkg.f_simple_avg_best_5_ofrs (:NEW.stock_code),
     lv_calc_pkg.f_simple_avg_best_5_rqst (:NEW.stock_code),
     lv_calc_pkg.f_simple_avg_offers (:NEW.stock_code),
     lv_calc_pkg.f_simple_avg_rqst (:NEW.stock_code),
     lv_calc_pkg.f_stock_count (:NEW.stock_code),
     lv_calc_pkg.f_stock_desc_a(:new.stock_code),
     lv_calc_pkg.f_stock_desc_e(:new.stock_code),
     lv_calc_pkg.f_sum_less_10_offers,
     lv_calc_pkg.f_sum_less_10_rqst,
     lv_calc_pkg.f_sum_less_5_rqst,
     lv_calc_pkg.f_sum_offerst (:NEW.stock_code),
     lv_calc_pkg.f_sum_volume_traded (:NEW.stock_code),
     lv_calc_pkg.f_trx_count (:NEW.stock_code),
     lv_calc_pkg.f_sum_request (:NEW.stock_code),
     lv_calc_pkg.f_last_request_qty (:NEW.stock_code),
     lv_calc_pkg.f_last_offer_qty (:NEW.stock_code) );
ELSIF stock_cur%FOUND THEN
     UPDATE lv_trade_summary
     SET the_time = :NEW.the_time,
     deals = :NEW.deals,
     price = :NEW.price,
     qty = :NEW.qty,
     trade_value = :NEW.trade_value,
     le_value = :NEW.le_value,
     buying = :NEW.buying,
     selling = :NEW.selling,
     rec_count = :NEW.rec_count,
     rec_serial = :NEW.rec_serial,
     buying_count = lv_calc_pkg.f_buying_count (:NEW.stock_code),
     close_price = lv_calc_pkg.f_close_price (:NEW.stock_code),
     coupon_value = lv_calc_pkg.f_coupon_value (:NEW.stock_code),
     currency = lv_calc_pkg.f_currency (:NEW.stock_code),
     dividend_yield_perc =
     lv_calc_pkg.f_dividend_yield_perc (:NEW.stock_code),
     hi_offer = lv_calc_pkg.f_hi_offer (:NEW.stock_code),
     hi_req = lv_calc_pkg.f_hi_request (:NEW.stock_code),
     hi_req_qty = lv_calc_pkg.f_hi_request_qty (:NEW.stock_code),
     last_offer = lv_calc_pkg.f_last_offer (:NEW.stock_code),
     last_request = lv_calc_pkg.f_last_request (:NEW.stock_code),
     last_trade_date = lv_calc_pkg.f_last_trade_date (:NEW.stock_code),
     less_offer = lv_calc_pkg.f_less_offer (:NEW.stock_code),
     less_offer_qty = lv_calc_pkg.f_less_offer_qty (:NEW.stock_code),
     less_request = lv_calc_pkg.f_less_request (:NEW.stock_code),
     liquid = lv_calc_pkg.f_liquid (:NEW.stock_code),
     off_count = lv_calc_pkg.f_off_count (:NEW.stock_code),
     prev_close = lv_calc_pkg.f_prev_close (:NEW.stock_code),
     prop_avg_ofr_10 =
     lv_calc_pkg.f_prop_avg_best_10_ofrs (:NEW.stock_code),
     prop_avg_rqst_10 =
     lv_calc_pkg.f_prop_avg_best_10_rqst (:NEW.stock_code),
     prop_avg_ofr_5 =
     lv_calc_pkg.f_prop_avg_best_5_ofrs (:NEW.stock_code),
     prop_avg_rqst_5 =
     lv_calc_pkg.f_prop_avg_best_5_rqst (:NEW.stock_code),
     prop_avg_offers = lv_calc_pkg.f_prop_avg_offers (:NEW.stock_code),
     prop_avg_rqst = lv_calc_pkg.f_prop_avg_rqst (:NEW.stock_code),
     req_count = lv_calc_pkg.f_req_count (:NEW.stock_code),
     rqst_to_offers = lv_calc_pkg.f_rqst_to_offers (:NEW.stock_code),
     sector_desc_a = lv_calc_pkg.f_sector_desc_a (:NEW.stock_code),
     sector_desc_e = lv_calc_pkg.f_sector_desc_e (:NEW.stock_code),
     selling_count = lv_calc_pkg.f_selling_count (:NEW.stock_code),
     simple_avg_ofrs_10 =
     lv_calc_pkg.f_simple_avg_best_10_ofrs (:NEW.stock_code),
     simple_avg_rqst_10 =
     lv_calc_pkg.f_simple_avg_best_10_rqst (:NEW.stock_code),
     simple_avg_ofr_5 =
     lv_calc_pkg.f_simple_avg_best_5_ofrs (:NEW.stock_code),
     simple_avg_rqst_5 =
     lv_calc_pkg.f_simple_avg_best_5_rqst (:NEW.stock_code),
     simple_avg_offers =
     lv_calc_pkg.f_simple_avg_offers (:NEW.stock_code),
     simple_avg_rqst = lv_calc_pkg.f_simple_avg_rqst (:NEW.stock_code),
     stock_count = lv_calc_pkg.f_stock_count (:NEW.stock_code),
     stock_desc_a = lv_calc_pkg.f_stock_desc_a (:NEW.stock_code),
     stock_desc_e = lv_calc_pkg.f_stock_desc_e (:NEW.stock_code),
     sum_less_ofr_10 = lv_calc_pkg.f_sum_less_10_offers,
     sum_less_rqst_10 = lv_calc_pkg.f_sum_less_10_rqst,
     sum_less_5_rqst = lv_calc_pkg.f_sum_less_5_rqst,
     sum_offer = lv_calc_pkg.f_sum_offerst (:NEW.stock_code),
     sum_volume_traded =
     lv_calc_pkg.f_sum_volume_traded (:NEW.stock_code),
     trx_count = lv_calc_pkg.f_trx_count (:NEW.stock_code),
     sum_request = lv_calc_pkg.f_sum_request (:NEW.stock_code),
     last_request_qty = lv_calc_pkg.f_last_request_qty (:NEW.stock_code),
     last_offer_qty = lv_calc_pkg.f_last_offer_qty (:NEW.stock_code)
     WHERE stock_code = :NEW.stock_code;
END IF;
lv_calc_pkg.p_orders_executed(:new.stock_code,:new.selling,:new.buying,:new.qty,:new.price);
CLOSE stock_cur;
END;

Well, you can use merge statement or exception :
CREATE OR REPLACE TRIGGER SE.LV_SUMMARY_TRADE_TR
AFTER INSERT
ON SE.LV_DAILY_TRADES
REFERENCING NEW AS NEW OLD AS OLD
FOR EACH ROW
BEGIN
     BEGIN
          UPDATE lv_trade_summary
          SET the_time = :NEW.the_time,
          deals = :NEW.deals,
          price = :NEW.price,
          qty = :NEW.qty,
          trade_value = :NEW.trade_value,
          le_value = :NEW.le_value,
          buying = :NEW.buying,
          selling = :NEW.selling,
          rec_count = :NEW.rec_count,
          rec_serial = :NEW.rec_serial,
          buying_count = lv_calc_pkg.f_buying_count (:NEW.stock_code),
          close_price = lv_calc_pkg.f_close_price (:NEW.stock_code),
          coupon_value = lv_calc_pkg.f_coupon_value (:NEW.stock_code),
          currency = lv_calc_pkg.f_currency (:NEW.stock_code),
          dividend_yield_perc =
          lv_calc_pkg.f_dividend_yield_perc (:NEW.stock_code),
          hi_offer = lv_calc_pkg.f_hi_offer (:NEW.stock_code),
          hi_req = lv_calc_pkg.f_hi_request (:NEW.stock_code),
          hi_req_qty = lv_calc_pkg.f_hi_request_qty (:NEW.stock_code),
          last_offer = lv_calc_pkg.f_last_offer (:NEW.stock_code),
          last_request = lv_calc_pkg.f_last_request (:NEW.stock_code),
          last_trade_date = lv_calc_pkg.f_last_trade_date (:NEW.stock_code),
          less_offer = lv_calc_pkg.f_less_offer (:NEW.stock_code),
          less_offer_qty = lv_calc_pkg.f_less_offer_qty (:NEW.stock_code),
          less_request = lv_calc_pkg.f_less_request (:NEW.stock_code),
          liquid = lv_calc_pkg.f_liquid (:NEW.stock_code),
          off_count = lv_calc_pkg.f_off_count (:NEW.stock_code),
          prev_close = lv_calc_pkg.f_prev_close (:NEW.stock_code),
          prop_avg_ofr_10 =
          lv_calc_pkg.f_prop_avg_best_10_ofrs (:NEW.stock_code),
          prop_avg_rqst_10 =
          lv_calc_pkg.f_prop_avg_best_10_rqst (:NEW.stock_code),
          prop_avg_ofr_5 =
          lv_calc_pkg.f_prop_avg_best_5_ofrs (:NEW.stock_code),
          prop_avg_rqst_5 =
          lv_calc_pkg.f_prop_avg_best_5_rqst (:NEW.stock_code),
          prop_avg_offers = lv_calc_pkg.f_prop_avg_offers (:NEW.stock_code),
          prop_avg_rqst = lv_calc_pkg.f_prop_avg_rqst (:NEW.stock_code),
          req_count = lv_calc_pkg.f_req_count (:NEW.stock_code),
          rqst_to_offers = lv_calc_pkg.f_rqst_to_offers (:NEW.stock_code),
          sector_desc_a = lv_calc_pkg.f_sector_desc_a (:NEW.stock_code),
          sector_desc_e = lv_calc_pkg.f_sector_desc_e (:NEW.stock_code),
          selling_count = lv_calc_pkg.f_selling_count (:NEW.stock_code),
          simple_avg_ofrs_10 =
          lv_calc_pkg.f_simple_avg_best_10_ofrs (:NEW.stock_code),
          simple_avg_rqst_10 =
          lv_calc_pkg.f_simple_avg_best_10_rqst (:NEW.stock_code),
          simple_avg_ofr_5 =
          lv_calc_pkg.f_simple_avg_best_5_ofrs (:NEW.stock_code),
          simple_avg_rqst_5 =
          lv_calc_pkg.f_simple_avg_best_5_rqst (:NEW.stock_code),
          simple_avg_offers =
          lv_calc_pkg.f_simple_avg_offers (:NEW.stock_code),
          simple_avg_rqst = lv_calc_pkg.f_simple_avg_rqst (:NEW.stock_code),
          stock_count = lv_calc_pkg.f_stock_count (:NEW.stock_code),
          stock_desc_a = lv_calc_pkg.f_stock_desc_a (:NEW.stock_code),
          stock_desc_e = lv_calc_pkg.f_stock_desc_e (:NEW.stock_code),
          sum_less_ofr_10 = lv_calc_pkg.f_sum_less_10_offers,
          sum_less_rqst_10 = lv_calc_pkg.f_sum_less_10_rqst,
          sum_less_5_rqst = lv_calc_pkg.f_sum_less_5_rqst,
          sum_offer = lv_calc_pkg.f_sum_offerst (:NEW.stock_code),
          sum_volume_traded =
          lv_calc_pkg.f_sum_volume_traded (:NEW.stock_code),
          trx_count = lv_calc_pkg.f_trx_count (:NEW.stock_code),
          sum_request = lv_calc_pkg.f_sum_request (:NEW.stock_code),
          last_request_qty = lv_calc_pkg.f_last_request_qty (:NEW.stock_code),
          last_offer_qty = lv_calc_pkg.f_last_offer_qty (:NEW.stock_code)
          WHERE stock_code = :NEW.stock_code;
     EXCEPTION WHEN OTHERS THEN
          INSERT INTO lv_trade_summary(
          the_time,
          the_date,
          stock_code,
          stock_type_id,
          market_id,
          deals,
          price,
          qty,
          trade_value,
          le_value,
          buying,
          selling,
          rec_count,
          rec_serial,
          buying_count,
          close_price,
          coupon_value,
          currency,
          dividend_yield_perc,
          eps,
          free_stocks,
          hi_offer,
          hi_req,
          hi_req_qty,
          high_date,
          high_price,
          last_offer,
          last_request,
          last_trade_date,
          less_offer,
          less_offer_qty,
          less_request,
          liquid,
          low_date,
          low_price,
          market_cap,
          off_count,
          prev_close,
          prop_avg_ofr_10,
          prop_avg_rqst_10,
          prop_avg_ofr_5,
          prop_avg_rqst_5,
          prop_avg_offers,
          prop_avg_rqst,
          req_count,
          rqst_to_offers,
          sector_desc_a,
          sector_desc_e,
          selling_count,
          simple_avg_ofrs_10,
          simple_avg_rqst_10,
          simple_avg_ofr_5,
          simple_avg_rqst_5,
          simple_avg_offers,
          simple_avg_rqst,
          stock_count,
          stock_desc_a,
          stock_desc_e,
          sum_less_ofr_10,
          sum_less_rqst_10,
          sum_less_5_rqst,
          sum_offer,
          sum_volume_traded,
          trx_count,
          sum_request,
          last_request_qty,
          last_offer_qty )
          VALUES (
          :NEW.the_time,
          :NEW.the_date,
          :NEW.stock_code,
          :NEW.stock_type_id,
          :NEW.market_id,
          :NEW.deals,
          :NEW.price,
          :NEW.qty,
          :NEW.trade_value,
          :NEW.le_value,
          :NEW.buying,
          :NEW.selling,
          :NEW.rec_count,
          :NEW.rec_serial,
          lv_calc_pkg.f_buying_count (:NEW.stock_code),
          lv_calc_pkg.f_close_price (:NEW.stock_code),
          lv_calc_pkg.f_coupon_value (:NEW.stock_code),
          lv_calc_pkg.f_currency (:NEW.stock_code),
          lv_calc_pkg.f_dividend_yield_perc (:NEW.stock_code),
          lv_calc_pkg.f_eps (:NEW.stock_code),
          lv_calc_pkg.f_free_stocks (:NEW.stock_code),
          lv_calc_pkg.f_hi_offer (:NEW.stock_code),
          lv_calc_pkg.f_hi_request (:NEW.stock_code),
          lv_calc_pkg.f_hi_request_qty (:NEW.stock_code),
          lv_calc_pkg.F_HIGH_DATE (:new.stock_code),
          lv_calc_pkg.F_HIGH_price (:new.stock_code),
          lv_calc_pkg.f_last_offer (:NEW.stock_code),
          lv_calc_pkg.f_last_request (:NEW.stock_code),
          lv_calc_pkg. F_LAST_TRADE_DATE(:new.stock_code),
          lv_calc_pkg.f_less_offer (:NEW.stock_code),
          lv_calc_pkg.f_less_offer_qty (:NEW.stock_code),
          lv_calc_pkg.f_less_request (:NEW.stock_code),
          lv_calc_pkg.f_liquid (:NEW.stock_code),
          lv_calc_pkg.f_low_date(:new.stock_code),
          lv_calc_pkg.f_low_price(:new.stock_code),
          lv_calc_pkg.f_market_cap(:new.stock_code),
          lv_calc_pkg.f_off_count (:NEW.stock_code),
          lv_calc_pkg.f_prev_close (:NEW.stock_code),
          lv_calc_pkg.f_prop_avg_best_10_ofrs (:NEW.stock_code),
          lv_calc_pkg.f_prop_avg_best_10_rqst (:NEW.stock_code),
          lv_calc_pkg.f_prop_avg_best_5_ofrs (:NEW.stock_code),
          lv_calc_pkg.f_prop_avg_best_5_rqst (:NEW.stock_code),
          lv_calc_pkg.f_prop_avg_offers (:NEW.stock_code),
          lv_calc_pkg.f_prop_avg_rqst (:NEW.stock_code),
          lv_calc_pkg.f_req_count (:NEW.stock_code),
          lv_calc_pkg.f_rqst_to_offers (:NEW.stock_code),
          lv_calc_pkg.f_sector_desc_a(:new.stock_code),
          lv_calc_pkg.f_sector_desc_e(:new.stock_code),
          lv_calc_pkg.f_selling_count (:NEW.stock_code),
          lv_calc_pkg.f_simple_avg_best_10_ofrs (:NEW.stock_code),
          lv_calc_pkg.f_simple_avg_best_10_rqst (:NEW.stock_code),
          lv_calc_pkg.f_simple_avg_best_5_ofrs (:NEW.stock_code),
          lv_calc_pkg.f_simple_avg_best_5_rqst (:NEW.stock_code),
          lv_calc_pkg.f_simple_avg_offers (:NEW.stock_code),
          lv_calc_pkg.f_simple_avg_rqst (:NEW.stock_code),
          lv_calc_pkg.f_stock_count (:NEW.stock_code),
          lv_calc_pkg.f_stock_desc_a(:new.stock_code),
          lv_calc_pkg.f_stock_desc_e(:new.stock_code),
          lv_calc_pkg.f_sum_less_10_offers,
          lv_calc_pkg.f_sum_less_10_rqst,
          lv_calc_pkg.f_sum_less_5_rqst,
          lv_calc_pkg.f_sum_offerst (:NEW.stock_code),
          lv_calc_pkg.f_sum_volume_traded (:NEW.stock_code),
          lv_calc_pkg.f_trx_count (:NEW.stock_code),
          lv_calc_pkg.f_sum_request (:NEW.stock_code),
          lv_calc_pkg.f_last_request_qty (:NEW.stock_code),
          lv_calc_pkg.f_last_offer_qty (:NEW.stock_code) );
     END;
     lv_calc_pkg.p_orders_executed(:new.stock_code,:new.selling,:new.buying,:new.qty,:new.price);
END;
/Nicolas.

.Not executable subVI

Similar Messages

Maybe you are looking for