Bug alert re iMT Extraction tool and custom data/display fields superclasses

In the current iMT there is a Extraction tool bug whereby custom
superclass usage in NetDynamics displayFields and/or dataFields are
resulting in nodes being omitted from the
application description. Worse, this omission was not being detected
by the Extraction tool. The error would not surface until the
Translation tool ran and tried to use the incomplete application
description xml file. The translation tool would then error as it
tried to locate non-existant nodes.
This is a serious problem for those applications which make use of
custom superclasses for displayFields and/or dataFields. If the
extraction omits these nodes, then the information is not available
to be translated. The problem is so severe, that I assume no one out
there has encountered it, or they would have reported it to us. If I
am mistaken in this assumption, please contact us.
The problem was easily corrected once identified. A fix will be
included in the next general release of the iMT.
At this point we are holding off on releasing micro-patches, in
anticipation of releasing a comprehensive iMT 1.1 release in the near
future.
If you have urgent need for this fix or any others that have been
listed on these boards, since the last patch drop, please let us know
ASAP and we will see what we can do.

I, for one, appreciate your contribution to this forum.
I haven't used Ultiboard since my initial purchase of it many many years ago. (MultiSim was bad enough. I wasn't about to start fighting with UltiBoard also.) However, it's of note how may bugs you have open/unsolved. MultiSim Inc has definitely not done its homework. In my case, that's not so much of a loss, but based on what you're saying, you actually have to use this thing to make money! That stinks!
I have little grounds for filing suit, as I've taken little risk; although, I can't tell you how many hours I've burned trying to figure out MultiSim's latest burp, that's hardly grounds for benefit from a suit. But you however, you're losing money! I'm thinking that the "at your own risk" in the fine print is MultiSim's out, but this is just wrong, the way this company is. This program just doesn't work and it looks like little can be done about it.
I thought that National Instruments' involvement would get some where with this program, but thus far that's proving to be an error on my part. My latest bug is the inclusion of MultiSim's multimeter causes a circuit to stop simulating. I mean how ridiculous is that?! But at least when MultiSim burps for me I'm not losing money, just time.
Thanks again for starting this thread!

Similar Messages

Extract tool and Turbulence tool

I have recently purchased C.S.6,and find that the Extract tool has vanished as also the Turbulence tool in Liquify.Am I doing something wrong?

Hi there
With the recent update to Photoshop CS6, several tools and features were modified or removed - two of them being the Extract filter and the Turbulence tool.
The Extract filter has been replaced by the Refine Edge feature in Photoshop CS6 (source). This is a very powerful non-destructive alternative to the Extract filter in previous versions of Photoshop.
The Turbulence tool has unfortunately been elimitated in this version of Photoshop (source).
You can read more about the new Extract tool and watch a few tutorial videos here: http://feedback.photoshop.com/photoshop_family/topics/where_did_the_extract_filter_go_in_p hotoshop_cs5-12e7w3
Cheers!

Foreign trade and customs data should be picked automatically in delivery

Dear All,
Foreign trade and customs data should be picked automatically in delivery note and in the invoice once we enter it in the master data for L/C Local Sales for example country Saudi arabia to Saudi Arabia in vi95 or any other transaction you have for this particular master data entry.please help

Check the customizing settings under
IMG - SD - Foreign Trade/Customs - Basic Data for Foreign Trade - Define Business Transaction Types And Default Value
And the data should be picked up from Material Master record in Foreign trade export view.
They are checked as mandatory fields according to customizing under:
IMG - SD - Foreign Trade/Customs - Control Foreign Trade Data in MM and SD Documents - Incompleteness Schemas for Foreign Trade Data
Also, refer following link:
[Customizing Foreign Trade Master Data |http://wiki.sdn.sap.com/wiki/pages/viewpage.action?spaceKey=ERPLO&title=CustomizingForeignTradeMasterData&decorator=printable]
Thanks & Regards
JP

Nested routings and Custom Data

Hi,
I am working and testing different solutions with Nested Routings.
For normal operations in a routing I can add Custom Data for each routing step.
However when I add a special routing as a nested routing within my routing I can not add Custom data
for this routing step.
Are there any workarounds available? Am I doing it the wrong way?
Br,
Johan

Hi Johan,
I would suppose that nested router is not treated as a router step but rather as a link to that router because there is no actual activity done at the step-link but rather at the actual steps of the nested router. So, if you can assing Custom Data to nested NC router but can't for Special router, then it is probably a bug. Otherwise, my guess is true and you can't assign Custom Data to step-link at all.
Regards,
Sergiy

EXTRACT function and Chinese data

Hi !
I'm working with PL/SQL web applications, and I'm having trouble viewing it on a webpage when I use EXTRACT function for Chinese data.
<abccompany> <department> 凯伦·威廉斯是一家小型社区制药厂的所有者，她正考虑开始提供药方递送的服务，同时也已经就此事征求了保险专家鲍勃·布朗的意见。凯伦询问鲍勃，需要购买哪些保险、</department></abccompany>
The Chinese xml data is stored as 'xmltype' in the Oracle database.
1)
When I run the below query, the output shown on a web page is upside down question marks like this
select v.xtext.EXTRACT('/abccompany/department/text()').GetClobVal()
into text
from case_text v
where case_identifier=inIdx;
htp.print('<html><body>')
htp.print(text);
htp.print('</body></html>');
2)
However, the EXTRACT function works perfectly for English data.
3)
I also observed that, when I replace
select v.xtext.EXTRACT('/abccompany/department/text()').GetClobVal()
with
to_clob(xtext)
the web page displays the Chinese contents of the whole file and not just within the nodes <abccompany><department>.
How can I make Extract function work with Chinese data ?
Any help appreciated !
-Sara

Sara
This normally happens when the client character set is not capable of showing chinese data. For instance on my laptop I cannot show the results of an extract() which returns chinese or japanese data in sqlplus (which cannot show chinese data on my machine) but I can in ISQL*PLUS which is web based and can show chinese data.
THis might be a result of your NLS_LANG settings. The database translates from the database character set (I'm assuming AL32UTF8 in this case, into the client character set (as defined by NLS_LANG). Again if the characters cannot be converted this can cause this issue.

Checkboxes and Custom Data Objects

I'm trying to create a form with a list of checkboxes based on customers' interests - there's 8 in all and they can select multiple options.
What I want to do is to create shared lists for each option which will serve as a segment members for future mailings.
I also need to hold the data for that individual together so if I ever need to, I can go in and say 'Well, Joe Bloggs here is interested in X, Y and Z so I'll put him into campaigns A and B'.
Are Custom Data objects the way to go? I've had a go at creating one and mapping it, but I don't know what to do with these checkboxes!!
Thanks!!

For the shared list, simply use the "Add to Shared Contact List" processing step for your form and make it conditional on the box being checked. You'll need 8 of these steps, one for each option.
For keeping the data, I would use a Custom Data Object. Create a new CDO set with a field for the email address and one for each of your checkboxes (plus whatever other info you want, of course.) And then use the "Update Custom Data Object - With Custom Values" processing step. You can set this step to add a "yes" or "on" or whatever else you'd like to the appropriate field in the CDO. Again, make this step conditional on the checkbox being checked in your form. Again, you'll need to create 8 of these steps, but once you get the first one done, the others should go quicker.
PS, I kept typing "from" instead of "form." Argh.

Use of type libraries and custom data types in TestStand 3.1

Consider the following example in CVI 7.0:
#include <cvidef.h>
typedef struct
    int                         t_err;
    unsigned int                err_flags;
    int                         err_code;
    char                        err_msg[1024];
} TEST_ERROR;
int DLLEXPORT DLLSTDCALL   NfctConnect (int iPortType, int iComPort, int iBaudRate, TEST_ERROR * tstError);
I want to call this function from TestStand 3.1 using the CVI Standard Adapter.
I created a function panel from the header file then I generated a DLL that contains the type library as an embedded resource. Using OLE/COM object viewer I can confirm that the definitions are correct. In TestStand however, all basic types are recognized but the structure is rejected as not being a TestStand type.
However, a C structure is supposed to be assimilated as a container in TestStand. Do I have to manually create a custom data type in TestStand to match my C structure or TestStand can automatically create the container based on the information in the type library (because this information is available it won't be difficult for TestStand to do this automatically)?

Hi Spoli,
At the current time the only adapter that gives you the option to
automatically create a container for a given parameter is the LabVIEW
adapter. In your case you will need to manually create the container
that matches your C struct. I apologize for the inconvenience.
One thing you can do to see this feature in future versions is make a Product Suggestion on our website. Our R&D engineers are always looking for good feedback.
Have a good one Spoli,
Dan Weiland
Applications Engineer
National Instruments
Dan Weiland

Null and no data in field value

I transferring sql from MS Access to Oracle 9i.
In Access I have this
select * from tableOne where firstname <> ''
and firstname & '' = ''The firstname field can be edited where it could have data and the data could be deleted so I am trying to select records where firstname is not null and it has no data in it.

I transferring sql from MS Access to Oracle 9i.
In Access I have this
select * from tableOne where firstname <> ''
and firstname & '' = ''
select * from tableOne where firstname IS NULL;
- or -
select * from tableOne where firstname IS NOT NULL;
as appropriate.
In Oracle there is no difference betwen being NULL and having data of length '0'

Extract parent and child data from an XML sequence?

I'm very new to XML, so please excuse me if I use incorrect terminology here. I've been given a schema definition (.xsd), and several sample xml files from which I need to extract data and insert it into relational tables. I've made some progress in that I've been able to hack enough to modify and register the schema and get the XML into the database both through the registered schema and into a separate table with an XMLType column. I've also been able to use the isSchemaValid function to validate the XML against the schema definition, and I've been able to extract some of the simple data elements via the extractValue function. My problem is with extracting some of the nested data - that is, extracting parent node elements and child node elements together where there is more than one value in the child node. BTW. I'm on Oracle 10gR2.
Following are the .xsd and and sample XML. Specifically, I need to select the NPI value from the PROVIDER node, and associate it with each of the CODE values from the SPECIALTIES node (which is part of the PROVIDER node).
Here's the .xsd (sorry, it's very long). The only modifications I've made to the schema definition are to add the xdb namespace and the "xdb:defaultTable="HMOSCHEMA" snippet:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xdb="http://xmlns.oracle.com/xdb" version="1.0">
<xsd:element name="HMO" xdb:defaultTable="HMOSCHEMA">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="HMO_GENERAL_INFORMATION" />
<xsd:element ref="PROVIDERS" />
<xsd:element ref="FACILITIES" minOccurs="0"
maxOccurs="1" />
</xsd:sequence>
<xsd:attribute name="DATE" type="xsd:string" />
</xsd:complexType>
</xsd:element>
<xsd:element name="HMO_GENERAL_INFORMATION">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="MCO_ID_LIST" minOccurs="1" maxOccurs="1" />
<xsd:element ref="HMO_WEBSITE_ADDRESS" minOccurs="1"
maxOccurs="1" />
<xsd:element ref="HMO_SPECIAL_SERVICES" minOccurs="0"
maxOccurs="1" />
<xsd:element ref="HMO_DAILY_CONTACT_EMAIL_ADDRESS"
minOccurs="1" maxOccurs="1" />
<xsd:element ref="HMO_MONTHLY_CONTACT_EMAIL_ADDRESS"
minOccurs="1" maxOccurs="1" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="PROVIDERS">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" ref="PROVIDER" />
</xsd:sequence>
<xsd:attribute name="RECORDS" type="xsd:string" />
</xsd:complexType>
</xsd:element>
<xsd:element name="PROVIDER">
<xsd:complexType>
<xsd:sequence minOccurs="1" maxOccurs="unbounded">
<xsd:element ref="NPI" minOccurs="1" maxOccurs="1" />
<xsd:element ref="FIRST_NAME" minOccurs="1"
maxOccurs="1" />
<xsd:element ref="LAST_NAME" minOccurs="1"
maxOccurs="1" />
<xsd:element ref="MIDDLE_INITIAL" minOccurs="0"
maxOccurs="1" />
<xsd:element ref="GENDER" minOccurs="1" maxOccurs="1" />
<xsd:element ref="LINE_1_ADDRESS" minOccurs="1"
maxOccurs="1" />
<xsd:element ref="LINE_2_ADDRESS" minOccurs="0"
maxOccurs="1" />
<xsd:element ref="CITY" minOccurs="1" maxOccurs="1" />
<xsd:element ref="STATE" minOccurs="1" maxOccurs="1" />
<xsd:element ref="ZIP" minOccurs="1" maxOccurs="1" />
<xsd:element ref="COUNTY" minOccurs="0" maxOccurs="1" />
<xsd:element ref="PHONE_NUMBER" minOccurs="1"
maxOccurs="1" />
<xsd:element ref="CLINIC_NAME" minOccurs="0"
maxOccurs="1" />
<xsd:element ref="CLINIC_TYPE" minOccurs="0"
maxOccurs="1" />
<xsd:element ref="CLINIC_NPI" minOccurs="0"
maxOccurs="1" />
<xsd:element ref="PROVIDER_OFFICE_HOURS_TENTHS"
minOccurs="0" maxOccurs="1" />
<xsd:element ref="MAXIMUM_PATIENTS" minOccurs="0"
maxOccurs="1" />
<xsd:element ref="ACCEPT_NEW_PATIENT" minOccurs="0"
maxOccurs="1" />
<xsd:element ref="PRIMARY_CARE_INDICATOR" minOccurs="0"
maxOccurs="1" />
<xsd:element ref="FOREIGN_LANGUAGES" minOccurs="0"
maxOccurs="1" />
<xsd:element ref="SPECIALTIES" minOccurs="1"
maxOccurs="1" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="SPECIALTIES">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="CODE"
minOccurs="1">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-9]{3}" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="FACILITIES">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" ref="FACILITY_NUM"
minOccurs="0" />
</xsd:sequence>
<xsd:attribute name="RECORDS" type="xsd:string" />
</xsd:complexType>
</xsd:element>
<xsd:element name="FOREIGN_LANGUAGES">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="CODE"
minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[A-Z]{3}" />
<xsd:pattern value="[a-z]{3}" />
<xsd:pattern value="" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="HMO_SPECIAL_SERVICES">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="CODE"
minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-9]{2}" />
<xsd:pattern value="" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="MCO_ID_LIST">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="MCO_ID" minOccurs="1" maxOccurs="unbounded">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-9]{1}" />
<xsd:pattern value="[0-9]{2}" />
<xsd:pattern value="[0-9]{3}" />
<xsd:pattern value="[0-9]{4}" />
<xsd:pattern value="[0-9]{5}" />
<xsd:pattern value="[0-9]{6}" />
<xsd:pattern value="[0-9]{7}" />
<xsd:pattern value="[0-9]{8}" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="HMO_WEBSITE_ADDRESS">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1" />
<xsd:maxLength value="100" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="HMO_DAILY_CONTACT_EMAIL_ADDRESS">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1" />
<xsd:maxLength value="50" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="HMO_MONTHLY_CONTACT_EMAIL_ADDRESS">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1" />
<xsd:maxLength value="50" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NPI">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-9]{1}" />
<xsd:pattern value="[0-9]{2}" />
<xsd:pattern value="[0-9]{3}" />
<xsd:pattern value="[0-9]{4}" />
<xsd:pattern value="[0-9]{5}" />
<xsd:pattern value="[0-9]{6}" />
<xsd:pattern value="[0-9]{7}" />
<xsd:pattern value="[0-9]{8}" />
<xsd:pattern value="[0-9]{9}" />
<xsd:pattern value="[0-9]{10}" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="FIRST_NAME">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LAST_NAME">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MIDDLE_INITIAL">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="1" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="GENDER">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="1" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LINE_1_ADDRESS">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LINE_2_ADDRESS">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CITY">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STATE">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[a-zA-Z][a-zA-Z]" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ZIP">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-9]{5}" />
<xsd:pattern value="[0-9]{9}" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="COUNTY">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-9]{1}" />
<xsd:pattern value="[0-9]{2}" />
<xsd:pattern value="[0-9]{3}" />
<xsd:pattern value="" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PHONE_NUMBER">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-9]{10}" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CLINIC_NAME">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:pattern value="" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CLINIC_TYPE">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:pattern value="" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CLINIC_NPI">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-9]{1}" />
<xsd:pattern value="[0-9]{2}" />
<xsd:pattern value="[0-9]{3}" />
<xsd:pattern value="[0-9]{4}" />
<xsd:pattern value="[0-9]{5}" />
<xsd:pattern value="[0-9]{6}" />
<xsd:pattern value="[0-9]{7}" />
<xsd:pattern value="[0-9]{8}" />
<xsd:pattern value="[0-9]{9}" />
<xsd:pattern value="[0-9]{10}" />
<xsd:pattern value="" />
<xsd:whiteSpace value="collapse"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PROVIDER_OFFICE_HOURS_TENTHS">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-9]{1}" />
<xsd:pattern value="[0-9]{2}" />
<xsd:pattern value="" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MAXIMUM_PATIENTS">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-9]{1}" />
<xsd:pattern value="[0-9]{2}" />
<xsd:pattern value="[0-9]{3}" />
<xsd:pattern value="[0-9]{4}" />
<xsd:pattern value="" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ACCEPT_NEW_PATIENT">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[A-Z]{1}" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PRIMARY_CARE_INDICATOR">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[A-Z]{1}" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="FACILITY_NUM">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-9]{1}" />
<xsd:pattern value="[0-9]{2}" />
<xsd:pattern value="[0-9]{3}" />
<xsd:pattern value="[0-9]{4}" />
<xsd:pattern value="[0-9]{5}" />
<xsd:pattern value="[0-9]{6}" />
<xsd:pattern value="[0-9]{7}" />
<xsd:pattern value="[0-9]{8}" />
<xsd:pattern value="[0-9]{9}" />
<xsd:pattern value="[0-9]{10}" />
<xsd:pattern value="" />
<xsd:whiteSpace value="collapse" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:schema>
Here's a sample of the XML (significantly shortened, and names and IDs changed to protect the innocent). BTW, the XML validates cleanly against the schema definition:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<HMO DATE="03/26/2010">
<HMO_GENERAL_INFORMATION>
<MCO_ID_LIST>
<MCO_ID>11111111</MCO_ID>
</MCO_ID_LIST>
<HMO_WEBSITE_ADDRESS>HTTP://WWW.SOMEHMONAME.COM</HMO_WEBSITE_ADDRESS>
<HMO_SPECIAL_SERVICES>
<CODE>00</CODE>
</HMO_SPECIAL_SERVICES>
<HMO_DAILY_CONTACT_EMAIL_ADDRESS>somename@someurl</HMO_DAILY_CONTACT_EMAIL_ADDRESS>
<HMO_MONTHLY_CONTACT_EMAIL_ADDRESS>somename@someurl</HMO_MONTHLY_CONTACT_EMAIL_ADDRESS>
</HMO_GENERAL_INFORMATION>
<PROVIDERS RECORDS="1011">
<PROVIDER>
<NPI>1111111111</NPI>
<FIRST_NAME>JOHN</FIRST_NAME>
<LAST_NAME>DOE</LAST_NAME>
<MIDDLE_INITIAL>A</MIDDLE_INITIAL>
<GENDER>M</GENDER>
<LINE_1_ADDRESS>1111 Some Rd</LINE_1_ADDRESS>
<LINE_2_ADDRESS> </LINE_2_ADDRESS>
<CITY>NOWHERE</CITY>
<STATE>YN</STATE>
<ZIP>12345</ZIP>
<COUNTY>13</COUNTY>
<PHONE_NUMBER>1111111111</PHONE_NUMBER>
<CLINIC_NAME>SOME CLINIC - CORPORATE OFFICE</CLINIC_NAME>
<CLINIC_NPI/>
<ACCEPT_NEW_PATIENT>Y</ACCEPT_NEW_PATIENT>
<PRIMARY_CARE_INDICATOR>N</PRIMARY_CARE_INDICATOR>
<FOREIGN_LANGUAGES>
<CODE> </CODE>
</FOREIGN_LANGUAGES>
<SPECIALTIES>
<CODE>170</CODE>
</SPECIALTIES>
</PROVIDER>
<PROVIDER>
<NPI>2222222222</NPI>
<FIRST_NAME>JANE</FIRST_NAME>
<LAST_NAME>DOE</LAST_NAME>
<MIDDLE_INITIAL>J</MIDDLE_INITIAL>
<GENDER>F</GENDER>
<LINE_1_ADDRESS>2222 SOMEOTHER ST</LINE_1_ADDRESS>
<LINE_2_ADDRESS> </LINE_2_ADDRESS>
<CITY>MYTOWN</CITY>
<STATE>YN</STATE>
<ZIP>12345</ZIP>
<COUNTY>13</COUNTY>
<PHONE_NUMBER>2222222222</PHONE_NUMBER>
<CLINIC_NAME>SOME CLINIC - MYTOWN</CLINIC_NAME>
<CLINIC_NPI/>
<ACCEPT_NEW_PATIENT>Y</ACCEPT_NEW_PATIENT>
<PRIMARY_CARE_INDICATOR>N</PRIMARY_CARE_INDICATOR>
<FOREIGN_LANGUAGES>
<CODE> </CODE>
</FOREIGN_LANGUAGES>
<SPECIALTIES>
<CODE>322</CODE>
<CODE>329</CODE>
</SPECIALTIES>
</PROVIDER>
</PROVIDERS>
<FACILITIES RECORDS="2">
<FACILITY_NUM>1000000001</FACILITY_NUM>
<FACILITY_NUM>2000000002</FACILITY_NUM>
</FACILITIES>
</HMO>
As you can see, the SPECIALTIES node can contain more than one CODE value, si I can't use extractValue to retrieve them. Again, I need to extract the NPI value from the PROVIIDER node, and associate it with each of the CODE values from the SPECIALTIES node. So, what I would need to extract from this sample XML would be:
NPI CODE
1111111111 170
2222222222 322
2222222222 329
This seems like it should be a pretty routine requirement, but I've tried everything I can think of (that is, everything I've learned to this point), and have not yet found a way............
Ideally, the solution to extracting this data would utilize SQL (not PL/SQL, or Java, or XSL, etc) with XML extraction functions (e.g. extract, extractValue, XMLSequence, XMLTable, etc).
Can anyone provide me with an example of how that iterative specialy code data could be extracted? Do I need to modify the .xsd to facilitate this extraction (so that registration of the schema results in other objects in the database)?
Any suggestions or examples would be greatly appreciated.
Thanks in advance, Dan
P.S. - I hope the XML displays OK when I post this question!

Hi,
Thanks for your detailed sample, it's very helpful.
This seems like it should be a pretty routine requirementIndeed, that's a classic (once you've got the method).
So, here's how you can do it :
SELECT x1.npi, x2.code
FROM t,
     XMLTable(
      '/HMO/PROVIDERS/PROVIDER'
      passing t.doc
      columns
        npi number path 'NPI',
        specialties xmltype path 'SPECIALTIES'
     ) x1,
     XMLTable(
      'SPECIALTIES/CODE'
      passing x1.specialties
      columns
        code number path '.'
     ) x2
;Assuming the XML is stored in column T.DOC.
As you see, for each NPI, the trick is to pass the entire SPECIALTIES node (kind of a join) to another nested XMLTable so that each CODE could be extracted as well.
There's another method using only one XMLTable and a little more complex XQuery. I'll try to post it soon.
HTH.
Edit : 2nd method
SELECT x.*
FROM t,
     XMLTable(
      'for $i in /HMO/PROVIDERS/PROVIDER/SPECIALTIES/CODE
       return element e
        attribute npi { $i/../../NPI },
        $i/text()
      passing t.doc
      columns
        npi number path '@npi',
        code number path '.'
     ) x
;Edited by: odie_63 on 27 mai 2010 18:43

Extracting FI and CO data (COEP and BKPF)

Hello friends,
I need to enhance the 0CO_OM_WBS_6 to add the invoice number. Kindly please, let me know, what is the connection between the table COEP and BKPF.
I would like to add the invoice number to the data extracted by 0CO_OM_WBS_6.
Thank you in advance,
K

In that case (while entries are on while doing data load) please use -
Early Delta Initialization
With early delta initialization, you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the updating of data in the source system. You can only execute an early delta initialization if the DataSource extractor called in the source system with this data request supports this.
http://help.sap.com/saphelp_nw70/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/content.htm
Hope it helps
Vikash

Russian Government and Customer Data--Privacy Legislation, what are you doing about this?

Apparently the Russian government recently accelerated legislation that will require personal data on Russian citizens to be stored in Russia. What is Oracle Eloqua or your company's feedback on how your are planning to respond to this or how other customers are responding. As SaaS, I don’t believe we have a way to store Russian contacts in Eloqua in Russia. See the basics of the legislation below.
Federal Law No. 242-FZ "On Amendments to Certain Legislative Acts of the Russian Federation for Clarification of the Procedure of Personal Data Processing in Information and Telecommunication Networks" (the "Federal Law No. 242") was adopted on 21 July 2014.
Federal Law No. 242 introduces the following changes:
to Federal Law No. 152-FZ "On personal data" dated 27 July 2006 (as amended) by establishing localization requirement for personal data processing; and
to Federal Law No. 149-FZ "On information, information technologies and protection of information" dated 27 July 2006 (as amended) by establishing procedure for blocking access to information resources on which unlawful processing of personal data takes place.
Federal Law No. 242 comes into force on 1 September 2016. The acceleration of the entry into force and change of the effective date of the Federal Law No. 242 to 1 January 2015 is however proposed by a draft law which was submitted to the State Duma (lower chamber of the Russian Parliament) on 1 September 2014. In order to become a law, the draft amendments shall be adopted through the usual law-making procedure, which duration is difficult to predict (it involves adoption by the State Duma in three readings, approval by the Federation Council (upper chamber of the Russian Parliament), signing by the President of the Russian Federation and official publication).
Localization requirement for personal data processing
Under Federal Law No. 242 so called "operators" or "personal data operators" are required to carry out certain types of "processing" of Russian citizens' "personal data" by using "databases", located in Russia. In this context:
Personal data means any information directly or indirectly related to any identified or potentially identifiable person. It includes, among other things, first name and family name, date and place of birth, address, information about family status, education, profession, income;
Personal data operator means a state or municipal authority, legal entity or individual that solely or jointly organize(s)and/or perform(s) the processing of personal data and determine(s) the purposes and scope of such processing;
Localization requirement applies not to all but only to the following types of personal data processing: recording, systematization, accumulation, storage, specification (updating and amending), and extracting; [1]
Personal data processing means any action or combination of actions performed with regard to / with any personal data, including collection, recording, systematization, accumulation, storage, use, transfer (distributing, providing or authorizing access to), blocking, deleting and destroying of any personal data;
Database means set of independent materials systematized in such a way that these materials can be retrieved and processed using the computer; and
Before starting personal data processing operators are required to notify the Federal Service for Supervision in the Area of Telecoms, Information Technologies and Mass Communications, which is the state authority responsible for the enforcement of the Personal Data Law ("Roskomnadzor") on the location of the database(s) containing personal data of Russian citizens.
The requirement of using databases "located in Russia" is not entirely clear, especially given that location of certain databases (e.g. clouds) is difficult to ascertain, but most likely this requirement implies that personal data operators are required to use local facilities (server(s) / data center(s)) located in Russia either owned or provided by third parties; each potential option requires proper legal and tax consideration.
It is not yet clear from Federal Law No. 242 whether Russian citizens' personal data may be processed with the use of the databases located outside of Russia in addition to being processed using databases located in Russia (e.g. for the purposes of back-up or duplicate storage).
Procedure for blocking access to infringing information resources
Procedure for blocking information resources on which unlawful processing of personal data takes place, introduced by Federal Law No. 242, includes the following stages:
Stage 1: The "personal data subject" (any individual identified or potentially identifiable on the basis of the personal data) whose personal data is being processed unlawfully shall obtain the relevant court decision acknowledging the unlawful processing of his/her personal data.
Stage 2: After entry of the relevant court decision into force the personal data subject may apply to Roskomnadzor with the request to limit access to his/her personal data.
Stage 3: Roskomnadzor within 3 (three) business days from the date of the relevant court decision's entry to force shall determine the hosting provider or any other person ensuring the processing of the personal data (the "Hosting Provider"), serve the Hosting Provider with a notification requesting the Hosting Provider to take measures to terminate unlawful processing of personal data and include information on the unlawful processing of personal data (including domain name, webpage, web address identifying websites on which personal data has been unlawfully processed, etc.) into the Register of Infringers of Rights of the Personal Data Subjects.
Stage 4: The Hosting Provider within 1 (one) business day from the date of receipt by the Hosting Provider of Roskomnadzor's notification shall liaise with the operator of the information resource, serviced by the Hosting Operator, requesting the operator of the information resource to terminate unlawful processing of personal data or restrict access to unlawfully processed information.
Stage 5: The operator of the information resource shall terminate unlawful processing of personal data within 1 (one) business day from the date of receipt of the request from the Hosting Operator. If the unlawful processing of personal data is not terminated by the operator of the information resource, the Hosting Provider, must restrict access to the information resource on which that personal data has been unlawfully processed not later than within 3 (three) business days from the date of receipt by the Hosting Provider of Roskomnadzor's notification.
Stage 6: Failure of the Hosting Provider or the operator of the information resource to undertake measures, described in Stages 4 and 5 above, entails submission of the information about unlawful processing of personal data to the telecommunication companies, which shall restrict access to the information resource on which that personal data has been unlawfully processed (including blocking of the relevant domain name or website). If the measures described in Stages 4 and 5 above are properly undertaken or if the court decision acknowledging the unlawful processing of personal data is overruled, Roskomnadzor or the entity keeping and maintaining the Register of Infringers of Rights of the Personal Data Subjects removes the information on the unlawful processing of personal data from such register.
1 - Excluding personal data processing: to achieve objectives stipulated by the international treaties of the Russian Federation or law, and for the performance of functions, powers or obligations of the personal data operators, imposed by law; (ii) for the performance of justice, enforcement of a judicial act, act of another authority or official, as provided by the laws on enforcement of judicial decisions; (iii) for the performance of powers imposed on the federal and municipal authorities, non-budgetary funds and organizations rendering state and municipal services, including registration in the unified and regional portals of state and municipal services; or (iv) for the professional activities of a journalist or mass media or for scientific, literature or other artistic activities, provided that rights and legal interests of the personal data subjects are not breached.

Í would like to know too! Some of our Eloqua customers are doing business in Russia.

Extract time and compare dates

I would like to know if hh:mm:ss have following value : "00:00:00" but I can't extract those values from the date. I'm not interested in dd/mm/yy but they are included in the string I receive.
set serveroutput on;
declare
str varchar2(30);
dat date;
begin
str := '19/01/2008 00:00:00';
dat := to_date(pepe,'HH24:MI:SS'); -- can't do this because mask do not fit with input string
if dat = '00:00:00' then ....

Sorry there was a copypaste error. This is the problem:
set serveroutput on;
declare
str varchar2(30);
dat date;
begin
str := '19/01/2008 00:00:00';
dat := to_date(str,'HH24:MI:SS'); -- can't do this because mask do not fit with input string
if dat = '00:00:00' then ...
I only want to know how can I detect that hh:mm:ss, coming from a varchar, is equal to "00:00:00".

Efficient optimized way to read from serial port and GPS data display using map

Hi,
I have a custom h/w which reads the data from GPS Rx and after parsing send it to PC over RS232.
Each second it sends 201 bytes to PC. I have developed a VI to read the GPS data and display it. Project file is attached.
Fulctionality of different loops are as following:
1. LOOP 1: 1.1 Reads the serial data from com port.
               1.2 Synclonize the frame using start bytes "a" and "z".
               1.3 Reads next 4 bytes containg receiving error information.
               1.4 Reads next 195 bytes. in which initial 80 byes are GPS data. rest are others.
2. LOOP 2: 2.1 Extarcts the GPS information and put them in an array.
                  2.2 Extarcts the receive error infor and counts the total error by incrimenting the variable using shift reg.
3. LOOP 3:3: 3.1 Displays the GPS data in chart and log the data in a file.
4. FLOW : Uses the GMAP .NET based API to creat a MAP and display.
Problem statement:
1. Functionality acheived.
2. However in between data set is being missed by the programm.
Quesitions:
1. Is the developed VI is efficient in terms of using queue loacl variables etc.
2. What are the improvments I can do to solve the problem.
Any other suggestions|
Thank you
jayant
jayant
Attachments:
Telemetry_Receiver_v2.zip ‏3075 KB

One of the most common problems in serial communication is the need for an adequate timing: how much time is expected your device to spend before answering? Have you put and adequate pause in your code before reading from the serial port?
Hope this helps
Roberto
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

Problem while creating with QUAN and CURR data type fields

I am trying to create a Z table. A couple of fields are of data type QUAN and CURR, which need to have reference table and reference field.
Field               DataType     Length     Decimal
TOT_QTY       QUAN            15                 3
PRICE              CURR             16                2
For reference table and fields, I found a Table HRPAD23 which has a field called N_QUANTITY (15,3) that matches my TOT_QTY field's data type and it also has a field called UN_PRICE that matches my PRICE field's data type. But when I use them as reference, and try to activate the table, I get an error "combination reference table/field does not exist". How do I fix this? Can anybody help me? Thanks in advance.
Chris
Edited by: martin99 on Aug 18, 2011 9:16 PM

Martin,
I doubt that you need to add 2 extra fields in your table as suggested in the last post by John.
Your error is very CLEAR that you seem to be use wrong combination of reference table and field.
For QTY field,
use ref table - HRPAD23.              ref field- UNIT
OR
ref table - VBAP                       ref field - VRKME
For PRICE field,
use ref table - PAD25                  ref field - KWAER
OR
ref table - T77REFDOC                                     ref field - CURRENCY
It should work.
BR,
Diwakar

Hierarchical and grouped data display

This question was posted in response to the following article: http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7bf4.html

"To display flat data as a hierarchy, you group the rows of the flat data before passing the data to the AdvancedDataGrid control"
So I have to filter and sort the data BEFORE I send it to the ADG?I have about 30,000 players, in 16 states, who either are or are not a member of an alliance. There is more data along with, but I would like to to be able to filter it by state and/or alliance, similar to the way MS Excel does.
The data comes from the server in no particular order, and the state is derived from the coordinates on demand. I plan 2 view states, one by state, sub alliance, another by alliance sub player, but if I am reading this correctly, I have to run thru the data once to assign states, then sub sort each state by alliance the send the data to the grid?

Bug alert re iMT Extraction tool and custom data/display fields superclasses

Similar Messages

Maybe you are looking for