XControl Data wiring problem - Data type is Waveform Graph (Strict)

Hi,
I created an Xcontrol for a waveform graph. The datatype (under Data 1.ctl) is a WaveformGraph reference type.
When I wire a Waveform graph reference to the Xcontrol (as an indicator), there is a wire conflict.
I checked the strict definition and the reference types are theoretically congruent but I cannot seem to wire it together. Any solutions?
Please see the attached code.
Thanks!
Attachments:
GraphDisplay XControl.7z ‏1717 KB
Tester.vi ‏15 KB

It looks like the XControl data is a waveform reference (strict). I can't open the XControl though, because I don't have a 7z compiler, but the problem is probably that the refnum will only take in a reference to an exact waveform graph because it's strict.
You can create a non-strict reference and use that for your data by:
Open your data control FP
Press Ctrl-Space
Type "Control Refnum"
Press Enter and place that on front panel
Right click it and brows to the correct data type:
James
LabVIEW Professional 2014

Similar Messages

Lost Data Minor problem data 3 ?

I Have acidently erased and installed osx 10.4 on myt audio hardisk !
I have tried nerly every type of data rescuing program on osx and p.c but the files have come back as .mpg and when I change the extentions and try to open then up in logic 7.1.1 it just doest make it ! Does any one have any experience with this type of situation as such ? And if so what can be or not be done . I have about 3 months of very hard work into the disk And going crazy to fix this up but not getting anywhere:(
And I always get this mesage minor problem in data 3?
What is this ?

Hi Prakash,
When you load data from R/3 through any infopackage the Job name is automatically taken starting with "BI". This means this a BI job running in R/3 for the ease of the understanding the processes for ourselves.
But when the Job which has been in scheduled status, which you have started, it has taken this as per the R/3 job as you have released the Job from R/3.
This might be the reasons where your Job description or name is different.
It's not the issue or problem with system. If you are getting a wrong data or not loading the data then you have to check the Job log for that particular job.
Or the another chance of the wrong job name, may be, you have released another job which is not related to BI.
Please check whether you have released the Right Job pertaining to BI.
Regards,
Ravi Kanth

How can I get extract the data between two cursors on an XY graph

How can I get extract the data between two cursors on an XY graph

Well, you say xy graph, so this might be a more complicated problem.
For a waveform graph it's trivial. Simply get the two cursor indices (property: cursor index) and apply them to array subset of the data. Is that all you need?
Here's how the above code would look like. using cursor.index instead of cursor.x elimnates the need to include scaling information.
For an xy graph, there could be multiple segments (e.g. imagine a spiral that passes the desired x range multiple times from both sides). This would neeed significantly more code for a general solution.
Message Edited by altenbach on 11-24-2009 07:53 AM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
cursorsubset.png ‏17 KB

Free memory of waveform graph

Hello,
I'm logging temperature data once a minute and display 4 plots with 1440 points (data of one day) in a waveform graph.
The data of the waveform graph is updated every 2 minutes. Over the time the application allocates continously more memory (maybe until the system crashes).
Could anyone tell me how I can free the memory used by the waveform graph or its history ?
Thanks for any help,
Ralf.

How to Clear Charts & Graphs.vi in LabVIEW help "Search Examples" demonstrates ways to clear charts before, during and after execution. This may provide you with some clues that you can apply to your vi.

Import image to waveform graph

Hello
I would like to import an waveform saved in some image format (PNG or JPEG) and display it in the waveform graph. I checked with the property node "plot images" but I am unable to specify the path of the image using this property node as in my case the image is varied with different experiments for comparing two waveforms(one waveform is in image format and the other is obtained from an oscilloscope instrument). Could someone please suggest how could I do this.
Best Regards
Pratheek
Solved!
Go to Solution.

Hi Hooovahh
Thanks for the solution. One more problem. In the waveform graph, it is displaying the labels, X-axis and Y-axis values. I woud like to have only the waveform without any labels is it possible to remove these lables from displaying in the waveform graph. could you please help. Thankyou in advance
Best Regards
pratheek
Attachments:
Capture.PNG ‏34 KB

The data type of the variant is not compatible with the data type wired to the type input.

Hello all..
Iam curently struggling with the following:
On my main(top)_VI, I have a mix-signal graph which will output several or one signals depending on the user. I also have an inner subvi which has the analisys i want to give the the data before outputing it to the main(top) VI, which has the mix-signal graph control.
Now, I created a reference from the mix-signal graph and Iam imputing this reference into the subVI (which inside has a property node type_control_mix-signal graph in which Iam connecting the refnum from the top VI to view the output data). The data consists of an array of clusters of 2 arrays of doubles each.
-- let say I create the property node type control mix-signal graph and i choose value property; it lets me put the array of clusters of 2 arrays of doubles each without problems; Now the second I connect the refnum pointing to the mix-signal graph on the Main_VI it brakes the cables and only accepts one cluster of two arrays os doubles instead.
--if on the other hand I connect the refnum to the property node type_control_mix-signal graph before connecting the imput it doesnt complain until I run the VI where it gives the error 91.
I have also notices a (strict) parenthisis at the end of the property node sometimes. [what does this (strict) means?]
FInally if instead of creating the refnum from the Main_VI, I create either a xy graph or a mix-signal praph it lets me connect the an array of clusters of 2 arrays of doubles each without any problem. The refnum connection seems to be the problematic factor, but by the same tolken I dont know any other means of sending that data from the inner to the outter VI.
I have the feeling Iam missing on one or more Labview fundamentals regarding refnums.
Any help will be apreciated

You almost found it on your own. The refnum needs to be 'strict', that means that the data type of the graph is set (2D dbl), otherwise it will use the default data type. To do this you create the refnum directly from the graph after you have wired the correct data type to the terminal. In this case the refnum wire will break if you change the data type of the graph.
Independend of this issue, I suggest you not to use the value property on the graph but directly wire the data (e.g. the 2D double) to the SubVI. The property value is by far the slowest way to get data, and 2D arrays are really some amount of data.
Felix
www.aescusoft.de
My latest community nugget on producer/consumer design
My current blog: A journey through uml

Data loading problem with Movement types

Hi Friends,
I extarcted data using the data source General Ledger : Line itemdata (0fi_gl_4) to BW side.
Problem is Movement Types for some documents missing.
But i checked in rsa3 that time showing correctly.
i restricted the data in bw side infopackage level only particular document that time data loading perfecly.
this data source having 53,460 records.among all the records 400 records doc type 'we' movement types are missing.
please give me solution for this how to loading the data with movement types.
i checked particular document of 50000313 in RSA3 it is showing movement types. then i loaded data in bw side that time that movement types are not comming to be side. then i gave the particular doc 50000313 in infopackage level loading the data that time movement types are loading correctly. this extaractor having 55000 records.
this is very urgent problem.Please give me reply urgenty. i am waiting for your's replys.
Thanks & Regards,
Guna.
Edited by: gunasekhar raya on May 8, 2008 9:40 AM

Hi,
we enhanced Mvement type field(MSEG-BWART) General ledger (0FI_GL_4) extractor.
this field populated with data all the ACC. Doc . number.
Only 50000295 to 50000615 in this range we are not getting the movement types values.
we didn't write any routines in transfer and update rules level.
just we mapped to BWART field 0MOVETYPE info object.
we restrict the particular doc no 50000313 infopackage level that time loading the the data into cube with movement types.
but we remove the restriction infopackage level then loading the data that time we missing the movement types data of particular doc no 50000295 to 50000615.
Please give mesolution for this. i need to solve this very urgently.
i am witing for your reply.
Thanks,
Guna.

Problem to create data source with OCI type of driver

Hi Experts
We are creating an XA datasource with OCI type of driver using an enterprise application with data-sources.xml, the xml is like this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE data-sources SYSTEM "data-sources.dtd" >
<data-sources>
     <data-source>
          <data-source-name>OCI_DS_XA</data-source-name>
          <driver-name>ORACLE_DRIVER</driver-name>
          <init-connections>1</init-connections>
          <max-connections>25</max-connections>
          <max-time-to-wait-connection>120</max-time-to-wait-connection>
          <expiration-control>
               <connection-lifetime>60</connection-lifetime>
               <run-cleanup-thread>300</run-cleanup-thread>
          </expiration-control>
          <sql-engine>Vendor_SQL</sql-engine>
          <jdbc-2.0>
               <xads-class-name>
                    oracle.jdbc.xa.client.OracleXADataSource
               </xads-class-name>
               <object-factory>
                    oracle.jdbc.pool.OracleDataSourceFactory
               </object-factory>
               <properties>
                    <property>
                         <property-name>serverName</property-name>
                         <property-value><SERVER_NAME></property-value>
                    </property>
                    <property>
                         <property-name>serverPort</property-name>
                         <property-value>1521</property-value>
                    </property>
                    <property>
                         <property-name>databaseName</property-name>
                         <property-value>ORCL</property-value>
                    </property>
                    <property>
                         <property-name>driverType</property-name>
                         <property-value>oci</property-value>
                    </property>
                    <property>
                         <property-name>user</property-name>
                         <property-value>username</property-value>
                    </property>
                    <property>
                         <property-name>password</property-name>
                         <property-value>password</property-value>
                    </property>
               </properties>
          </jdbc-2.0>
          </data-source>
</data-sources>
We have installed oracle client in server M/C and configured all the environment variables. While we are deploying the application from CE developer studio IDE to the CE 7.1 AS, we are getting the following error:
Description:
          1. Exception has been returned while the 'sap.com/DS_TEST_EAR' was starting. Warning/Exception :
[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 7653550:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "OCI_DS_XA".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1467)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:468)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:419)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:495)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:554)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:248)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:389)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3387)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3373)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3276)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3249)
     at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
     at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
     at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
     at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
     at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Caused by: com.sap.engine.frame.core.database.DatabaseException: Exception of type java.sql.SQLException occurred: Closed Connection.
     at com.sap.engine.core.database.impl.DataSourceAdministratorImpl.createDataSource(DataSourceAdministratorImpl.java:49)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1400)
     ... 33 more
Caused by: java.sql.SQLException: Closed Connection
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:227)
     at oracle.jdbc.driver.GetCharSetError.processError(T2CConnection.java:3082)
     at oracle.jdbc.driver.T2CConnection.getCharSetIds(T2CConnection.java:2811)
     at oracle.jdbc.driver.T2CConnection.logon(T2CConnection.java:300)
     at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:344)
     at oracle.jdbc.driver.T2CConnection.<init>(T2CConnection.java:136)
     at oracle.jdbc.driver.T2CDriverExtension.getConnection(T2CDriverExtension.java:79)
     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:545)
     at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:194)
     at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:121)
     at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:333)
     at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:84)
     at com.sap.sql.connect.factory.XADSPooledConnectionFactory.getPooledConnection(XADSPooledConnectionFactory.java:27)
     at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnection(DBDataSourceImpl.java:677)
     at com.sap.sql.connect.datasource.DBDataSourcePoolImpl.initConnections(DBDataSourcePoolImpl.java:1099)
     at com.sap.sql.connect.datasource.DBDataSourcePoolImpl.<init>(DBDataSourcePoolImpl.java:49)
     at com.sap.sql.connect.datasource.DataSourceManager.createDataSource(DataSourceManager.java:507)
     at com.sap.sql.connect.datasource.DataSourceManager.createDataSource(DataSourceManager.java:136)
     at com.sap.sql.manager.OpenSQLManager.createDataSource(OpenSQLManager.java:141)
     at com.sap.engine.core.database.impl.DataSourceAdministratorImpl.createDataSource(DataSourceAdministratorImpl.java:42)
     ... 34 more
But when we are creating the datasource with thin type of driver, it is working fine. We have already created a driver with name ORACLE_DRIVER in server using the ojdbc14.jar using Netweaver administrator consol.
Same this is happening when we are creating the OCI type of datasource by using Netweaver administrator consol by specifying all the parameter as above and also the initial connection pool size is more than zero.
Same thing is happening for normal (JDBC 1x) datasource creation with OCI type driver.

Hello,
I ran a search on SDN, related to your error code, i found the following:
UnsupportedClassVersionError in NWDS CE
DeploymentWarning-WebService-Collection
Maybe its useful to you
Regards,
Siddhesh

Possible Problem in type Date

In the documentation about the DATE. They say, when you create a date(long), the date is create with the date 1 Jan 1970 00:00 + the parameter, so if you call the date(Long.valueOf("0")) the date isn�t 1 Jan 1970 00:00, is 1 Jan 1970 01:00. Then I think the date don�t start at this date, but at 1 Jan 1970 01:00.
the code to try:
System.out.println(new Date(Long.valueOf("0") ));
if you try with:
System.out.println(new Date(Long.valueOf("-60000") ));
you get 00:59, then there are sure something strange there.
It�s correct or there are something i don�t know?
I�m using JDK 1.5+eclipse.
thank
Edited by: cookie_monster on Jul 21, 2008 5:12 AM

the most related is this.No it isn't. 'This forum is for discussion of the proposed extension of the Java Programming Language with generic type declarations and methods, and for discussion of the prototype implementation provided by Sun.' Nothing to do with your question.
Do you know where i can send it?No.

Can't get a dynamic data type and wire (waveform double) to both display on a waveform graph

Hi,
I'm teaching myself LabVIEW. I wish to delay a wave form and display it with the non delayed wave form. I used a delay from the examples. The output of the delay is wire (waveform double). The Simulate signal output is dynamic data. My conversion from wire (waveform double) to dynamic does not display on the waveform graph. The VI is attached. Can anyone offer any comment.
Solved!
Go to Solution.
Attachments:
Three input graph.vi ‏92 KB

It is displaying just fine. The display is hidden behind the display of the second signal. Expand the Plot Legend to show all three plots. Then toggle the plot visible property of the second and third plots.
Lynn

Open data set problem with binary mode

Hi everyone,
I am trying to read into a buffer the content of a binary file (like Excel) and to write that content file using open data set into a folder destination.
The file destination has a size diferent than from the original one and cannot be open.
Here is the code.
DATA: lv_file_name(100),
         lt_content LIKE sdokcntbin OCCURS 0 WITH HEADER LINE.
MOVE '\computerTestA1.xls' TO lv_file_name.
OPEN DATASET lv_file_name FOR INPUT IN BINARY MODE.
IF sy-subrc NE 0.
    EXIT.
ENDIF.
DO.
    READ DATASET lv_file_name INTO lt_content-line.
    IF sy-subrc NE 0.
      EXIT.
    ENDIF.
    APPEND lt_content.
ENDDO.
CLOSE DATASET lv_file_name.
* DELETE DATASET lv_file_name.
CLEAR: lv_file_name.
MOVE '\computerTestB2.xls' TO lv_file_name.
OPEN DATASET lv_file_name FOR OUTPUT IN BINARY MODE.
IF sy-subrc NE 0.
    EXIT.
ENDIF.
LOOP AT lt_content.
    TRANSFER lt_content-line TO lv_file_name.
ENDLOOP.
CLOSE DATASET lv_file_name.
THanks in advance.
Regards.
Message was edited by:
        David Fryda

Hi,
I solve the problem.
In fact, when I try to write the last line of lt_content, it does write all the line even if this line is not full of data.
Solution :
DATA: lv_file_name(100),
         lt_content LIKE sdokcntbin OCCURS 0 WITH HEADER LINE,
         alen TYPE i,
         pos TYPE i.
MOVE '\mr0221TestA1.xls' TO lv_file_name.
OPEN DATASET lv_file_name FOR INPUT IN BINARY MODE.
IF sy-subrc NE 0.
    EXIT.
ENDIF.
SET DATASET lv_file_name POSITION END OF FILE.
GET DATASET lv_file_name POSITION pos.
SET DATASET lv_file_name POSITION 0.
DO.
    CLEAR lt_content.
    READ DATASET lv_file_name INTO lt_content-line ACTUAL LENGTH alen .
    IF sy-subrc NE 0.
      APPEND lt_content.
      EXIT.
    ENDIF.
    APPEND lt_content.
ENDDO.
CLOSE DATASET lv_file_name.
* DELETE DATASET lv_file_name.
CLEAR: lv_file_name.
MOVE '\mr0221TestB2.xls' TO lv_file_name.
OPEN DATASET lv_file_name FOR OUTPUT IN BINARY MODE.
IF sy-subrc NE 0.
    EXIT.
ENDIF.
LOOP AT lt_content.
    AT LAST.
      TRANSFER lt_content-line TO lv_file_name LENGTH alen.
      EXIT.
    ENDAT.
    TRANSFER lt_content-line TO lv_file_name.
ENDLOOP.
CLOSE DATASET lv_file_name.
Thanks.

Problem when sorting data based on date

I am trying to sort the following data based on the Transaction Receipt date column,unable to do it usi g the following syntax:
<?sort:TRANSACTION_RECEIPT_DATE;'ascending';data-type='date'?>
I have problem in converting the date in report to canonical date ,is there any other way to achieve the output without converting the date format.
<?xml version="1.0"?>

<RECDTREP>
<LIST_G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO104</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>24636</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863063</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO107</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>24641</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863068</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO123</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>24658</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863086</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO75</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>31-MAR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>22190</OBJECT_ID>
<INITIALIZATION_DATE>14-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510860842</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>31-Mar-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>971515</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO116</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>25-JUN-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>64271</OBJECT_ID>
<INITIALIZATION_DATE>30-JUN-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863077</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>25-Jun-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO92</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>31-MAR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>22253</OBJECT_ID>
<INITIALIZATION_DATE>14-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510860890</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>31-Mar-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>971515</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO99</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>31-MAR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>22263</OBJECT_ID>
<INITIALIZATION_DATE>14-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510860899</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>31-Mar-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>971515</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO109</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>25-JUN-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>64204</OBJECT_ID>
<INITIALIZATION_DATE>30-JUN-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863070</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>25-Jun-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO135</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>25-JUN-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/18 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>64296</OBJECT_ID>
<INITIALIZATION_DATE>30-JUN-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510875546</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>25-Jun-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO101</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>24618</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863046</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO120</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>24653</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863081</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO122</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>24657</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863085</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO127</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>24662</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863090</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO100</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>24585</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863033</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO110</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>25-JUN-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>64265</OBJECT_ID>
<INITIALIZATION_DATE>30-JUN-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863071</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>25-Jun-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO130</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>25-JUN-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/13 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>64275</OBJECT_ID>
<INITIALIZATION_DATE>30-JUN-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510875487</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>25-Jun-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
</LIST_G_ASW_REC_DATE>
<CF_SORT_BY>Manufacture,Receipt Date,Organization,Item Code</CF_SORT_BY>
<CF_SERIAL_WHERE></CF_SERIAL_WHERE>
</RECDTREP>

HI Mahesh,
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
this is not a date,
so you should change the query to get you the format in xsd format : YYYY-MM-DDThh:mm:ss+HH:MM
otherwise, you have to write a custom sort function to decode and order it it.
if you dont do the custom order and use
<?sort:TRANSACTION_RECEIPT_DATE;'ascending';data-type='date'?>
the data will be treated as string and you will see the row is sorted on string.

Date popup problem in APEX 3.1

Hi
I have a date picker (DD-MM-YYYY HH24:MI) and after upgrading to APEX 3.1 from APEX 3.0.1 the popup window height is too small.
The end user is having to resize the window to click on the OK button.
Is there a file I can edit to increase the height, couldnt find it in templates/themes.
Regards
Adam

Hi Adam,
This is a bug in APEX 3.1. It was discussed here:
Apex 3.1 Upgrade Issue - dba_lock and date picker display
and here:
Date Picker problem in Apex 3.1
I'll let Carl investigate and provide an official response and recommendation. Although I know where this problem is occurring.
The size of the popup calendar window is hard-wired in the file apex/images/javascript/apex_3_1.js. In APEX 3.0, the size of the popup window was determined programatically at runtime and was a function of the date format, if it included a time component or not.
The uncompressed, readable version of this same file is in apex/images/javascript/uncompressed/apex_3_1.js. Look for p_DatePicker and you'll see what I'm talking about. You'll see the height is hard-wired to 210 and width to 258. In APEX 3.0, the height was set to 255 if the date format contained a time component.
So my suggestion, until Carl provides an official response, is to look for '210' in apex/images/javascript/apex_3_1.js and change this to 255. Granted, all calendar popup windows will be this big, but it won't put as great a burden on the end-user.
I hope this helps.
Joel

Use a Mathscript code which has both x and y data and produce it in a waveform

I have this MATLAB code:
t = (0:0.0000001:0.01);
f1 = 0.0011312*cos(2*pi*49400*t);
f2 = 0.003936*cos(2*pi*100*t);
H = (f1*f2);
x = ((2.93464*10^-10)*H);
ms = 1000;
M = ms (coth(x) - (1./x));
I want to plot it on Labview 8.0 as M vs. t with 'M' being Y-axis and 't' being X-axis.
I tried using MathScript to type the MATLAB code but when i add an output to it and connected it to a waveform, it does nothing....
Thanks,
K

On Dec 9, 5:10 pm, Kris Matrix <[email protected]> wrote:
> I have this MATLAB code:
>  
> t = (0:0.0000001:0.01);f1 = 0.0011312*cos(2*pi*49400*t);f2 = 0.003936*cos(2*pi*100*t);H = (f1*f2);x = ((2.93464*10^-10)*H);ms = 1000;M = ms (coth(x) - (1./x));
>  
> I want to plot it on Labview 8.0 as M vs. t with 'M' being Y-axis and 't' being X-axis.
>  
> I tried using MathScript to type the MATLAB code but when i add an output to it and connected it to a waveform, it does nothing....
>  
> Thanks,
> K
Two suggestions.
There maybe some exceptions but most of the time with Labview's Data
flow approach to programming you need to calculate all of your output
points before you pass the data to a waveform graph. How are you
accumulating your data?
Instead of using a Labview waveform graph to plot the data use a
Matlab plot command to plot the data. Once you can successfully plot
the data with a Matlab plot command then go onto the next step and try
to plot the data with a Labview waveform graph.
Howard

Xml conversion of data refs with dynamic type

Hi Colleagues,
I have to create an XML from a TYPE REF TO DATA, where this data is created using a dynamic internal table. By dynamic internal table i mean that the internal table is created dynamically using the class method cl_alv_table_create=>create_dynamic_table.
Now the problem that i face is when i use the statement:
CALL TRANSFORMATION id
      SOURCE jsag_data = im_context_b64
      RESULT XML lv_xml
      OPTIONS data_refs = 'embedded'
              value_handling = 'move'.
to generate the XML i get a dump of type CX_XSLT_SERIALIZATION_ERROR saying "The ABAP data cannot be serialized."
I found a solution to avoid the dump by adding the additional option " TECHNICAL_TYPES = 'ignore' " to the CALL TRANSFORMATION statement, like
CALL TRANSFORMATION id
      SOURCE jsag_data = im_context_b64
      RESULT XML lv_xml
      OPTIONS data_refs = 'embedded'
              value_handling = 'move'
              TECHNICAL_TYPES = 'ignore'.
But, using this addition the dynamic type ref to data part is totally ignored from the XML generation.
If I use a specific DDIC table type to create the data, we do not face this issue and the XML is generated as desired
Does anyone have a solution to this problem as it has become a sort of blockade for our development?
Thanks and Cheers,
Gaurav.

Hello,
I reached same problem with dynamic data references, the only solution I got is to used global DDIC types (also for table types !!) when creating data which needs to be serialized.
The options technical_types = 'ignore' doesn't solve the problem - it just instructs the parser to skip data references without global ddic type. The options value_handling = 'move' is very helpful as XML serialization is very picky about values beeing serialized.
Here is summary of my observations:
- Global DDIC type has to be associated with data reference, otherwise only technical type is there and this is not supported (you can use OPTIONS TECHNICAL_TYPES = u2018IGNOREu2019 but this will just skip the data to be serialized to XML) u2026
- The above means that if you are serializing data reference to table then you have to have also global DDIC type for the table-type !! Unfortunatelly there is no default table type available for transparent tables u2026. They are treated as structures not as table-types u2026 thus:
- CREATE DATA lr_data TYPE <global_ddic_structure> - can be serialized
- CREATE DATA lr_data TYPE STANDARD TABLE OF <global_ddic_structure> - cannot be serialized
- CREATE DATA lr_data TYPE <global_ddic_table_type> - can be serialized
- !! Unfortunatelly !! CREATE DATA lr_data TYPE <type_pool_ddic_structure/ type_pool_table_type> - also cannot be serialized u2013 this is pitty u2026 this should be supported u2026.

XControl Data wiring problem - Data type is Waveform Graph (Strict)

Similar Messages

Maybe you are looking for