XSD in syndicator
Dear Experts,
I would like to know which standard xsd schema to use when we want to syndicate at once material master data. Because with CLFMAS I can map taxonomy but not the main table fields and when I try the MATMAS05 it does not include the taxonomy attributes?
Thanks,
NL
Hi,
You have to Use MATMAS05, when ever you are sending back the material master records to the remote syestems.
If you want to send attributes back to the remote systems then you have to use CLFMAS.
hope this may help you,
Regards,
Srinivas
Similar Messages
-
Root column disabled while Assigning XSD- In Syndicator
Hi,
I am not able to assign the XSD against the Remote system in the Syndicator.
While assigning the XSD through
Syndicator==> File==>
Destination Properties
While assigning the XSD against the Remotesystem,Root Textbox is disabled and OK button alsio disabled...
Please provide your suggestions
Best Regards
Devaraj PKHi Devraj,
Root column dissabled when your XSD is not proper.
In Syndicator go to file->Destination Properties
Here select XML Schema if you have made an entry of an XSD in XML Schema table in Console or you can select XML Schema File if you want to pick your XSD from a particular location.Now if the XSD is proper then only the Root Column will be enabled which contains the root node available in
XSD so please check for the Same.
Reward if Helpful,
Regards,
Vinay Yadav -
Hi SDN,
Can anybody guide me to solve this problem.
I have created a custom repository as per the requirement(repository has text fields, taxonomy fields etc). I have created a XSD structure using xomLite from the XML(by exporting from Console).
Now if I open the XSD I am finding only a Category field but the attributes that were created in Datamanager are not present.
I want an XSD with attrbutes , please help me out.
Very urgent.
Regrads,
PramodCreating XSD with attributes:
since attributes are created in Data mgr they are not part of data structure which we define in console hence the xsd from console will not have attributes. you can create an xml file from MDM syndicator with all the attributes and from that xml file convert to XSD using the software.
I want to syndicate all the attributes
since we dont have the xsd while syndicating we need to add all attributes first then do the mapping.how to add fields in the xsd in syndicator Manager pls refer the ref guide for MDM Syndicator.
hope it helps.reward points if suitable
Regards-
Ravi -
Update of XML syndication map when XSD is changed
All,
So we recently upgraded to MDM 7.1 SP 06 and found a new feature which we were waiting for quiet some time. Thought i'll share with the community as well.
Update of XML syndication map when XSD is changed in Console
In earlier SP's of MDM, if we had to update an XML syndication map, we had to upload the new XSD in Console, go to syndicator and basically re-create the whole map. there was no way for syndicator to preserve the old mapping.
Well with this new feature, the old mapping is preserved, we only need to re-map the new fields.
The process is as below:
1. Upload the new XSD in Console.
2. Go to syndicator and open the syndication map which you want to update(File->Open).
3. Click File -> Update XML Schema. (this is the new option)
4. It will give a pop-up, select the new schema you have uploaded in console and hit OK.
5. You will get a prompt saying that syndication map is being changed, hit OK.
6. Now you will see the new XSD in syndicator, the older fields are still mapped, you only need to map the new fields.
It a nice feature which will definitely save lot of time. Thanks SAP
Regards
AamirIf this post answered your question or helped, please mark it as such.
This works.
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">
<mx:Script>
<![CDATA[
import mx.events.DataGridEvent;
import mx.collections.ArrayCollection;
[Bindable] private var ac:ArrayCollection = new ArrayCollection([
{bgColor: "0xFF0000", num: 100, name: "Test1"},
{bgColor: "0xFF0000", num: 200, name: "Test2"},
{bgColor: "0xFF0000", num: 300, name: "Test3"},
private function changeBK(evt:DataGridEvent):void{
var row:uint = evt.rowIndex;
var data:Object = ac.getItemAt(row);
data.bgColor = "0x00FF00";
]]>
</mx:Script>
<mx:DataGrid id="dg" dataProvider="{ac}" itemEditEnd="changeBK(event);"
editable="true">
<mx:columns>
<mx:DataGridColumn dataField="num">
<mx:itemRenderer>
<mx:Component>
<mx:TextArea backgroundColor="{data.bgColor}" text="{data.num}"/>
</mx:Component>
</mx:itemRenderer>
</mx:DataGridColumn>
<mx:DataGridColumn dataField="name"/>
</mx:columns>
</mx:DataGrid>
</mx:Application> -
XSD for the inbound/outbound file
MDMers,
We have customized Material repository supplied with business content of MDM. We have added a few tables/fields and deleted few.
How do we create XSD from the repository which can be used in Import process and syndication process?
Thanking you in advance,
Dan.Hi Dan,
Agreed you have customized your repository by adding and deleting certain fields.
But the point is from where are you importing your source file.Because the XSD that you use in importinga nd syndicating must match with the input and output XML file.It need not be the Schema of your MDM rep.
Eg: If you are importing an XML matmas file from ECC having material master record data you will have to upload and use the matmas XSD in MDM console similarly...
If you are exporting your master data to an ECC system you will need the same matmas XSD in syndicator as well.As while syndicating your Source XSD will be your repository structure any ways it sthe destination xsd which is decided based on wats your target system.
If are jsut trying and doing an R n D with the tool then you can use the xomlite to create your xsd of the MDM repository forimporting mdm data and syndicating MDM data.
Hope It Helped
Thanks & Regards
Simona Pinto -
I created an XSD using the xomLite45. I defined the XSD in the console (in the Admin>XML schemas). After that I tryed to use it in the syndicator but I am not able to open it when I defined it in the destination properties.
What can be the problem?
Thanks, TalHi Tal,
Following could be the possibilities of XML schema not opening
1) If you are using standard Repository then it could be that it has was not correctly archived due to which the Schema generated in incorect,if you are using customized repository then check and verfiy the rep in console before exporting the Schema.
2) The XML schema generated from xomlite may not be comletely generated.Is it showing the .XSD ext and is the file in the correct format ie xsd not xml?
3) While giving the Schema name in Console could be you have given the XML file name instead of XSD.Check that
4) In the Syndicator the Root may not have been populated properly.Just check whether whether the root is getting populated.
Your problem could be due to one of these reason.
Hope it helps
Reward points if found useful
Thanks
Simona -
XSD from PI in Syndicator - no root element selectable
Hello
I have created a message type in PI and exported the XSD. However when I want to use that XSD in the syndicator no root element is available. Why is that?
I have searched the forums and found that MDM won't show a root element if the XSD is not sane. What part of the XSD is not sane? I have validated it in Liquid XML and it works in the import manager.
Has anyone had the same problem?
BR
/AlexanderHi,
I also faced same problem. We removed namespace from XSD manually. When u create file from PI it contains namespace.
It worked then !!!!
if still not solved tell me in detail i will give eg ..
Regards
Himanshu
reward if helpful -
Bonjour
I have created a message type in PI and exported the XSD. However when I want to use that XSD in the syndicator no root element is available.
Any with similar issues.
FVHeard this in the past try removing namespace from XSD manually or do post more details if this does not work !
Regards,
Raj -
XSD from PI does not works in Syndicator.
Hey Guys
I created a data type in PI then made a XSD out of It ,when i try to import that in Syndicator i don't get any root element for it. but if i tweak the XSD just a little bit. it works perfectly in syndicator.
I understand MDM has some limitations in terms of XSD attributes it uses.
The XSD which is imported from PI and does not gives root element is below
<?xml version="1.0" encoding="UTF-8" ?>
- <xsd:schema xmlns="http://mc.com/MDM/CustomerMaster" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <xsd:complexType name="DT_Sender">
- <xsd:sequence>
- <xsd:element name="Name" type="xsd:string" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">56635e00e5a911deaefc0012f0e979b0</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="Description" type="xsd:string" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">56635e01e5a911de8eac0012f0e979b0</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
XSD which works is as below
<?xml version="1.0" encoding="UTF-8" ?>
- <xsd:schema xmlns="http://millercoors.com/MDM/CustomerMaster" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <xsd:element name="DT_Sender">
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="Name" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">56635e00e5a911deaefc0012f0e979b0</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="Description" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">56635e01e5a911de8eac0012f0e979b0</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
The only difference between the 2 XSD's is that in the first one i have element defined as
<xsd:complexType name="DT_Sender">
whereas in the second one i have defined it as
<xsd:element name="DT_Sender">
<xsd:complexType>
Is there some kind of restriction for element definition in XSD for MDM?
Thanks
SaifHello Saif,
have a detailed look at your XSDs.
The first one does not define any root element. It contains the definition of a complex type only. But there is no element that is using the complex type "DT_Sender". That is the reason why Syndicator does not show any root element for selection.
The second one is different. This one defines an element "DT_Sender" that consists of a complex type. Now Syndicator is able to show the element.
If you want to use the first definition you have to add an element using the complex type. It could look like:
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns="http://mc.com/MDM/CustomerMaster" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="DT_Sender" type="DT_Sender" />
<xsd:complexType name="DT_Sender">
<xsd:sequence>
<xsd:element name="Name" type="xsd:string" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">56635e00e5a911deaefc0012f0e979b0</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Description" type="xsd:string" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">56635e01e5a911de8eac0012f0e979b0</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Some further tipps and tricks:
1) If you need the xmlns="http://mc.com/MDM/CustomerMaster" in your XML, it makes more sense to add this in the Syndication map properties. There is a field for the namespace where you should paste the http://mc.com/MDM/CustomerMaster part.
2) xmlns:xsd definitions don't have to be mentioned for each element. If you do this in the schema, it's ok.
3) MDM does not handle annotations in the XSD. You can remove them.
So a perfect XSD could look like
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="DT_Sender" type="DT_Sender" />
<xsd:complexType name="DT_Sender">
<xsd:sequence>
<xsd:element name="Name" type="xsd:string" minOccurs="0" />
<xsd:element name="Description" type="xsd:string" minOccurs="0" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Best regards
Michael -
Syndicator : Root identification for XSD (schema) file
Dear MDM Pals,
Scenario :XSD file (DEBMDM06) customization and Syndication set up in MDM Syndicator.
Details: There is a need to customise xsd file at one segment level. Only the names of elements in a segment are changed - XSD structure is untouched.When this is done , and used in syndicator , the root of xsd schema file is not getting recognized.As a result, not able to proceed with Syndication set up process.
Please advise -
a) What needs to be taken care in XSD schema file modification ?
b) MDM syndicator set up (if any) to handle custom XSDs.
Awaiting quick help on this please.
Regards,
Vinay M.SHi Vinay,
Make sure that the root element name as in the XSD exactly matches with the Repository Schema main table name.
This name should be exactly same in all respects.
Also make sure you save and upload this newly customized schema in your MDM console correctly with a new name,and then try using this schema in your MDM syndicator.
Hope It Helped
Thanks & Regards
Simona Pinto -
Generic Vendor XSD in MDM syndicator
Hi All,
I downloaded Generic Vendor XSD file from XI Content and trying to use in MDM syndication.
But,When I select Generic Vendor XSD in syndication,root element is not coming and ok button is in disable mode.
please look into my xsd file here...
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://sap.com/xi/BICONTENT" targetNamespace="http://sap.com/xi/BICONTENT">
<xsd:simpleType name="PartnerLocalId">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c2fdd4507b2a11dcbf3a0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="60" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="TextShort">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c2fb63517b2a11dcb5250013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="LanguageCode">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c3001e407b2a11dc87310013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2" />
<xsd:minLength value="2" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="MarketTradePartner">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c3028f407b2a11dcc4cb0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="36" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="TransportZone">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c30500407b2a11dc8be70013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="GroupID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c3074a307b2a11dca5530013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="32" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="GenericVendorId">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c309bb307b2a11dc9d150013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="60" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="CountryKey">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c30c05207b2a11dc9e9d0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="SourceSystemName">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c31331137b2a11dc830f0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="60" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="TextLong">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c31331107b2a11dc82d80013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="GeoSourceID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c315a2127b2a11dccda20013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="TextMedium">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c31cce007b2a11dc9d7e0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="GeoPrcisionLocation">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c31f17f07b2a11dc9fbb0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:integer">
<xsd:totalDigits value="4" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="Street60">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c32188f07b2a11dcb5cf0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="60" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="PostalCode">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c323f9f07b2a11dcae280013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="Region">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c32643e07b2a11dcc0c80013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="TimeZone">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c328b4e07b2a11dcc11a0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="6" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="CompanyCode">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c328b4e37b2a11dcabfd0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="City">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c32b25e27b2a11dccc770013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
<xsd:minLength value="1" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="BackEndType">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c32d6fd27b2a11dc993f0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="NationCode">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c32fe0d17b2a11dc895c0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="GeoLatitude">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c3322ac07b2a11dca37e0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:decimal">
<xsd:totalDigits value="27" />
<xsd:fractionDigits value="12" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="GeoAltitude">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c3349bc07b2a11dc9f6e0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:decimal">
<xsd:totalDigits value="20" />
<xsd:fractionDigits value="3" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="Gender">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c3370cc07b2a11dcbc340013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="TelNumber">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c3370cc37b2a11dcac2e0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="30" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="BusinessPartner">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c33956b27b2a11dc85200013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="PartnerSourceSystemID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c33bc7b27b2a11dc896f0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="LegalForm">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c33e38b17b2a11dcb0bb0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="OrgUnit">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c34082a07b2a11dc83200013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:integer">
<xsd:totalDigits value="8" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="FaxNumber">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c342f3a07b2a11dc8c6d0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="30" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="LocalVendor">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c3453d907b2a11dccc3f0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="GeoPostalCode">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c3453d937b2a11dc921f0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="HouseNumber">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c347ae927b2a11dcb78d0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="TaxJurisCode">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c34a1f927b2a11dc84640013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="GeoLongitude">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c34c69807b2a11dca0070013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:decimal">
<xsd:totalDigits value="27" />
<xsd:fractionDigits value="12" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="GlobalUltimateDuns">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c34eda807b2a11dc9ff90013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:integer">
<xsd:totalDigits value="9" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="DunsNumber">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c3514b807b2a11dcc48a0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:integer">
<xsd:totalDigits value="9" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="ClientObjectType">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c35395737b2a11dcb5ea0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="32" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="DeletionFlag">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c35395707b2a11dca4df0013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:length value="1" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="ApoLocno">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c35606727b2a11dc8ff40013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
<xsd:minLength value="1" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="CountryCode">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c35850627b2a11dccde30013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="SourceInfoObject">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c35ac1617b2a11dca0230013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="30" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="EmailAddress">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c35d32607b2a11dc80c90013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="60" />
<xsd:minLength value="0" />
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="GenericVendor">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
5d21eea07b2a11dcc8b80013725d3a37
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="GenericVendorID" type="GenericVendorId" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
a1cd2d00f46611d9ad8dd7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="APOLocation" type="ApoLocno" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
a1cd2d01f46611d993e0d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="BusinessPartner" type="BusinessPartner" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
cb1ab990f46911d9ca58d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="GroupID" type="GroupID" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
cb1ab991f46911d9c008d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="CompanyCode" type="CompanyCode" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
e16b4f70f46911d9ac0cd7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Country" type="CountryKey" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
4b41e260f46a11d980b3d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="DunsNumber" type="DunsNumber" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
4b41e261f46a11d9b6acd7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="BackEndType" type="BackEndType" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
4b41e262f46a11d99c2fd7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="LocalPartnerID" type="PartnerLocalId" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9ec56e70f46a11d9a572d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="SourceSystemID" type="PartnerSourceSystemID" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9ec56e71f46a11d9bbbbd7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="SourceSystemName" type="SourceSystemName" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
33efe2a0fe9d11d9b2ebc5a20a12cf18
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="SourceInfoObject" type="SourceInfoObject" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
cc2ca950f46a11d9c5edd7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ClientSystemObjectType" type="ClientObjectType">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
33efe2a1fe9d11d9c169c5a20a12cf18
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="MarketTradePartner" type="MarketTradePartner" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
f0780b10f46a11d9b9f7d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="PostalCode" type="PostalCode" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
41ac4ff0f46b11d990dad7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Region" type="Region" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
a1cce870f47211d981d6d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="LocalVendorID" type="LocalVendor" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
a1cce871f47211d9a2e1d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="GlobalUltimateDunsID" type="GlobalUltimateDuns" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
e110fc30f9d411d9959fc42c0a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="CountryCode" type="CountryCode" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
870a26c0f9d511d992b7c42c0a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Altitude" type="GeoAltitude" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
496718d0f47311d9851dd7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="City" type="City" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
496718d1f47311d998b1d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="EmailAddress" type="EmailAddress" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
496718d2f47311d999e9d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="FaxNumber" type="FaxNumber" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
496718d3f47311d99a31d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Gender" type="Gender" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
26ecd820f47411d98ffdd7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="HouseNumber" type="HouseNumber" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
26ecd821f47411d9c6e6d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="LanguageCode" type="LanguageCode" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
26ecd822f47411d9ba96d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Latitude" type="GeoLatitude" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
26ecd823f47411d9b1aad7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="LegalForm" type="LegalForm" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
26ecd824f47411d9ac3dd7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Longitude" type="GeoLongitude" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
17aa7d70f91c11d9b9a8c3c70a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Nation" type="NationCode" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
26ecd825f47411d9c6d5d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="OrganizationalUnit" type="OrgUnit" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
505fe380f47611d9ce02d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="GeoPostalCode" type="GeoPostalCode" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
505fe381f47611d99a89d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="PrecisionLocation" type="GeoPrcisionLocation" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
505fe382f47611d9c360d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="GeoSourceID" type="GeoSourceID" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
628b1d30f47711d9a05bd7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Street60" type="Street60" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c835b9b0f47711d98906d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="TaxJurisdictionCode" type="TaxJurisCode" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c835b9b1f47711d9c9c3d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="TelNumber" type="TelNumber" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9af28c20f47811d9a820d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="TimeZone" type="TimeZone" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9af28c21f47811d9a064d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="TransportZone" type="TransportZone" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9af28c22f47811d98414d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="DeletionFlag" type="DeletionFlag" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
870a26c1f9d511d98cd2c42c0a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="TextShort" type="TextShort" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
cce01270f47811d9b0c9d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="TextMedium" type="TextMedium" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
cce01271f47811d9b274d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="TextLong" type="TextLong" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
fc8667e0f47811d9b851d7990a12cf0d
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>Hi JJ,
most propably the cause for your issur is the namespace definition within the XSD:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://sap.com/xi/BICONTENT" targetNamespace="http://sap.com/xi/BICONTENT">
Solution:
1. Add the namespace information to the URI field when adding the XSD to your repository in MDM Console
OR
2. Remove the namespace information within the XSD as it is not really mandatory.
This should help.
BR Michael -
Hi,
Recently we upgraded our MDM repo schema with new fields. Accordingly, outbound XSD was modified to include new elements. What we are finding is that we cannot apply existing map onto this new schema it screws up most of the mappings - we are having to re-create maps.
Is there a better of way of doing this? My expectation was if I apply existing map onto the new schema it should at least map common elements and discard the remainder but thats not happening.
Regards,
Dev.Hi Devashish
This is how syndication map works. The schema used for preparing the map is also part of the map.
So if data model has changed we need to extend the schema and recreate a map with the new schema.
There is a workaround though, not very clean, but you can give this a try. You can export the syndication map as .syn and open it using xml editor and the delta changes done in data model can be manually updated along with the field mapping details.
Before doing this you need to study the xml file(map) and see how the fields mapped are presented.
Best regards
Ravi -
Need to add a new field to the Schema for MDM Syndicator
We are running MDM 5.5 SP6.
We have a requirement to add a new field and syndicate the new field to the our Procurement System.
I was able to add the new field to the repository and schema in SAP MDM Console. However, when I went into the Syndicator to map the new field (which I do see) to the new Schema field, I don't see the new field to map in the Schema.
How can I change the existing syndication jobs (11 of them) to use the new Schema? Or do I have to recreate all of them?
Thank you in advance!!!Hi Janynne,
I hope you have modify the Syndication XSD(add new field) and then load it in XML Schema table of MDM Console, right ?
If you have done it, now open MDM Syndicator>Go to File>Open, select the required Remote system and Available map.
Now your existing map will be loaded which has not the required added field, Now again, go to file-->Export.
Give file name and save this syndication map on your Desktop. Once you have done this.
Go to File>New>Select respective remote system and Type as XML Schema if you have loaded this XSD in Console else select Type as XML Schema file and select the modified XSD (added new field XSD) from Desktop. Once it is loaded, import the existing syndication map(which you have exported as said above) which should have all the fields mapped, now in target side you will have here new added field too, map it with required source field in Item Mapping and then go to file>Save as>select the required Remote system and give new map name. Use this map for exporting files for future reference.
Also, if your are using Port Concept, you need to change the Properties Map and XML Schema in Port of MDM Console.
Regards,
Mandeep Saini -
We are tring to syndicate the vendor numbers only from vendor repository in xml format. I created an XSD for the same. See the XSD below :
<?xml version="1.0" encoding="utf-8"?>
<xs:schema id="Vendor" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="Vendors">
<xs:complexType>
<xs:sequence>
<xs:element name="LIFNR" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
XSD validates fine and generates an output from syndicator, but the problem that we face is that this is creating 1 file for each vendor record. We want a consolidated file. I know I am missing something but cannot make it to work.
I tried to put the unbounded parameter in <xs:element name="Vendors"> but that makes the XSD invalid.
Need urgent help on this.
Thanks<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="Vendors">
<xs:complexType>
<xs:sequence>
<xs:element name="Vendor" type="Vendor" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="Vendor">
<xs:sequence>
<xs:element name="LIFNR" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:schema> -
hi All,
I am currently working with MDM Syndicator.
My problem is about Root element
when i am opening in the syndicator file-->destination properties
it will open dialog box with the following options, (i.e. type,Remote system,port,xml schema,xml file name,Root.
when i am selecting type as xml schema , romote system(i.e which i have declared in console for that repository). but when i click on OK button.
it is asking for the Root element required.
can any one help me about:
1)what is root element?
2)where we can declare root element and where we can use it in syndicator?
3)what actually Root element holds in it?
can any please provide answers to this questions
thanks in Advance
Bharat.chinthapatlaHi Michael,
Thanks for your reply for the pervious question Michael.
But.................?
My Problem is..........
Under Admin in console i have selected XML Schema table and i have created one record with Name as "xml schema file one" and in the filename field i have clicked on the browse button and selected one .xsd file in the repository.
(i have tried with .xml schema file also but not....)
I have opened the syndicator on that particular repository and in the source item i am able to see the table and fields of that particular repository and i have clicked on the file option and i have choosen "Destination properties" it has opened dialog box with different input fields, there i have selected type as "xml schema" and Remote system " MDM "(default). when i selected type as xml schema automatically xml schema input field is enabled and it as shown all the xml schema files or record which i have created in the XML schema table under Admin of the console.
But Root element is not enabled, what i have to do?
In the previous question you have said like this " <b>you have to add an XML Schema to your repository using the <u>corresponding branch</u> in the Console Admin menu</b>.
what is the corresponding branch in the console Admin menu, can you please explain me in details...
if there is any other procedure to come out of this problem, can you please explain me in details ?
Thanks in advance
bharat.chinthapatla
Maybe you are looking for
-
I have two help files running on both the intranet and the Web server at my office. When doing a search in either help file on the intranet, I get successful search results. However, when I conduct a search in the help files published to Web server,
-
Route pattern with called party transformations
HI All, i wanto to add route pattern with transformation i want to add RP with 9.001! predot and want to convert to 9.01017! with called party transformations. How we replace ! ? i've tried and it's error with message Called Party Transform Mask - al
-
Hi All, I am new to OOPs.I have a dought.can we use events in interfaces?
-
It is up-to-date ... can I upgrade directly to Mountain Lion 10.8.1 ? Will this upgrade also fix my iPhoto's inability to stay in the foreground and be usable? Thanks ps- was thinking of buying Aperture also ... but, apparently I cannot use Aperture
-
Spring + weblogic. NamedQuery not found
I've posted this at the [Spring forum|http://forum.springframework.org/showthread.php?t=67389] as well(, just wanted to try here too... We're new to about all of the technology we're working with, and we're having a hard time to get it all right. Ple