RAW16 to xsd:base64Binary - Manual Overide in PI Mapping ?
Friends,
I am relatively new to PI, we have imported an RFC FM in PI and done the mapping ...
One of the fields in FM - has data type - RAW16 after importing in PI it is converted to xsd:base64Binary
Following are my questions
1. Can we manually override one of the fields in PI , like for e.g. after importing in PI from RFC FM can we convert data type xsd:base64Binary to XSDString?
2. I need the field as string in PI, what could be the alternate solution to this problem, In SAP they cannot convert the field/data Type(RAW16) to String?
Note: The FM has about 100+ fields so we cant do manual mapping in PI
Thanks in anticipation!
Hi Jitesh,
As Indrajit mentioned you can write an UDF in PI.
Also check below thread.
ABAP Proxy - BASE64 content
Regards,
Pranil.
Similar Messages
-
Xsd:base64Binary vs Datahandler
Hi There,
I was developing a webservice using top down approach( wsdl to java). So in one of my complex types, I defined an element type as xsd:base64Binary( in wsdl file)
<xsd:element minOccurs="1" maxOccurs="1" name="token" type="xsd:base64Binary"/>
When I convert this wsdl to java, a java class for this complex type will be created and the type of token is javax.activation.DataHandler.
So in serverside if I have a byte array, how will I convert that to a valid javax.activation.DataHandler object and vice versa in client side?
I hope I have provided enough info here to understand the issue. Please feel free to ask otherwise.
Thanks,
Jose Johnannoyingly, this is not as easy as it should be. basically, you need to wrap the byte[] in a ByteArrayInputStream, and wrap that in an instance of a DataSource which returns this stream from the getInputStream method (and then wrap the DataSource in a DataHandler). there may be some internal sun classes which simplify this (something like ByteArrayDataSource), but i'm not sure.
-
Hi ,
We are experiencing wierd problems with size of an element with data type xsd:base64Binary (Byte array).
Following is the scenario:
We have an element(FileDoc) of type xsd:base64Binary in a message. This message in being used in an Outbound Interface which has been exposed as a asynchronous webservice.
This webservice is being called from a .Net application. In the .Net applicaiton a byte array is created and filled with values. This byte array is set to FileDoc element.
1. When the size of the byte array is <= 1533, the webservice call finishes and we could see the message in XI(SXIMB_MONI).
2. But when the size of the byte array is > 1533, the webservice call finishes without any errors, but in XI we see no message(SXIMB_MONI / RWD).
Its looks like there is a size limit on the amount of data one can send for datatype:base64Binary.
Has any noticed this problem???
Thanks,
naveenHi,
maybe the total size of your message is too big?
try setting max_request_size_KB parameter to -1
for a few minutes
- restart your server
- test your webservice
http://help.sap.com/saphelp_nw04/helpdata/en/58/108b02102344069e4a31758bc2c810/content.htm
after the test change it to the value you had before
Regards,
michal -
Use XSD referencing other XSDs with include statement in Message mapping
Hello,
I have an XSD with include statements having reference to other 4 XSDs.One XSD out of these 4,one references one more XSD
I referred to the thread on this :
refrencing 1 xsd to another https://forums.sdn.sap.com/post!default.jspa?forumID=44#
I have created 6 External Definitions one for each XSD
Referring to the following statement in this thread:
In XI 3.0, there is a tab there called External References. You will see there a Source and a Name. When you click the Name, click Copy Object. Then you open the target object and paste it under the Source located just before the tabs.
The Name you see in the External References are the ones that are declared as include or import in the XSD.
I can see included XSD names in Source column under External References tab in External definition for main XSD.
But Name column is always blank and these columns are not editable.Also,copy doesn't work.
We have XSD names in include statements,but I wonder when I create External definitions out of these XSDs ,how would my main External definition know,which other External definitions are referenced?
If I use the External definition with main XSD as target structure in my mapping,I can only see the fields from this XSD and not the fields from the included XSDs.But I need to map these fields as well.
Can anybody please let me know how can I get a complete XSD as target structure in my mapping?
Thanks for your help.
Regards,
ShwetaPlz close other duplicate threads for the same issue first..
Regards,
Sarvesh -
Downloading maps can take a considerable length of time. Then later, when "New Maps Available" shows, we are told that clicking on the Download Now button will cause all current maps will be deleted and new ones to be installed. Is this really the case or is it just a few obsolete maps that are deleted and replaced?
It would certainly help if the OVI maps list could flag which maps have been updated. It could then be a case of simply deleting an old file from the phone and then downloading just the new one before visiting a country. That could save a lot of time.
For example, I have no idea which maps have been updated in the Europe set. All I need is the latest map for the country that I will be visiting next week. So, if I just delete and replace that one country it should be up to date. That's a few MB rather than 2.4GB. Is this a valid way to proceed or am I missing something?Pete_G wrote:
My phone is a 6730 classic running maps version 3.04.
Sorry you have no choice in the matter as v3.04 is latest version for 6730:http://europe.nokia.com/support/product-support/maps-support/compatibility-and-download#/nokia-6730-...
Happy to have helped forum with a Support Ratio = 42.5 -
Converting Base64Binary to PDF document in BSP
Hello SDN users,
I am trying to get and display a pdf document from a webservice which is provided as a base64binary.
The interface of the webservice tells me that the response type (the actual pdf document) is an xsd:base64Binary.
The webservice proxy class generates an RAWSTRING for the pdf document as the response from the webservice call.
So my first guess was to use following class method to convert the base64binary to a normal string
CALL METHOD cl_http_utility=>if_http_utility~decode_base64
EXPORTING
encoded = lv_out_char " RAWSTRING from webservice
RECEIVING
decoded = lv_out_char_decoded.
My second guess was to create an xstring from this converted string via
CALL FUNCTION 'SCMS_STRING_TO_XSTRING'
EXPORTING
text = lv_out_char_decoded"
mimetype = 'APPLICATION/PDF'
IMPORTING
buffer = lv_out_charx.
My next assumption was to create otf-data via function module so that I can send the otf data to the http server cache.
lv_pdf_len = XSTRLEN( lv_out_charx ).
call function 'CONVERT_OTF'
EXPORTING
format = 'PDF'
IMPORTING
bin_filesize = lv_pdf_len
bin_file = lv_out_charx
TABLES
OTF = LT_OUTPUT_DATA-OTFDATA
LINES = LT_LINES
EXCEPTIONS
err_max_linewidth = 1
err_format = 2
err_conv_not_possible = 3
err_bad_otf = 4
others = 5.
My Problem is, that I get back error code 4 which means bad otf.
Does anyone has a hint how I need to convert the base64binary from the webservice to a right format?
That would be great!Hello Durairaj,
thank you very much for your answer,
is it usual that the method
CALL METHOD cl_http_utility=>if_http_utility~decode_base64
EXPORTING
encoded = lv_out_char " RAWSTRING from webservice
RECEIVING
decoded = lv_out_char_decoded.
returns a string containg something like %pdf...? This was not the case with my method call.
But on friday I found out why. the string I received from the webservice was actually an XSTRING which I found out during a debugging session. The method return parameter was declared as RAWSTRING so I assumed that I had to convert from Base64 to STRING and then to XSTRING. When I aborted all the converting routines
if_http_utility~decode_base64
and
CALL FUNCTION 'SCMS_STRING_TO_XSTRING'
and passed the XSTRING to the ICM server cache I received the pdf I wanted.
But anyway If you could confirm my second question how a a decoded Base64 attribute should look like I would be very happy.
Regards,
Sebastian -
How to set a base64binary to hexBinary in BPM process
Hi all.
I'm developing using Oracle BPM Suite 11.1.1.5
I've the following scenario:
I need to insert a binary from a BPM process to database using a data access web service implemented with ADF Service Interface. In the process a binary value is treated like xsd:base64binary while the ADF web service treats binary values as xsd:hexBinary. Inside my BPM process I got a service task making a service call to the data access webservice and invoking an InsertPhoto method. During the process I obtain the image (as a binary) I want to insert in the database and, using associations, I map the image value to the binary field required as input for the insert method. There's no error during the implementation but after deploy and test the process I got the following error, asociated to the service task:
javax.xml.ws.soap.SOAPFaultException:
Exception Description: The object [<the hole binary characters>], of class [class java.lang.String], could not be converted to [class [B].
at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:197)
at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:130)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:125)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:136)
at $Proxy29.operation(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)
at $Proxy30.operation(Unknown Source)
at com.oracle.xmlns.bpmn.bpmnprocess.process.ProcessPortClient.main(ProcessPortClient.java:24)
Any suggestion will be welcome.
Regards
isabelbernellyDone. The solution was just go to the ADF web service schema definition (xsd), look for the InsertPhoto method message and change the type of Image (the binary field) from "hexBinary" to "base64Binary" and redeploy the web service application.
-
Import and Syndication maps - change in XSD
HI All,
Can any one let me know are these are correct if it is then are there any work around solutions?
We created manually Import and syndication maps.. fine..After few days we changed data type/deleted the filed/added new fields.... In all these above incidents do we need to recreate import and syndication maps????
There is no other work around for this ??
2) Even if there is no change in Repository structure but change in import or syndication XSD do we need to recreate all import and syndication maps???
Your inputs are really helpful.
Thanks
RajeevHI Rajeev,
So for any change in the MDM repository Import maps and syndication maps are not needed to recreate from scrach right?
For minor changes like field add there is no need.For changes involving deletion of mapped fields,changing types of already mapped fields,deleting mapped tables,one should first unmap the current map and then carry out structural changes.Later one can remap them again,this is to avoid maps from getting corrupt.
If there is any change in the XSD then there is a possibility to recreate the map from scrach??
Yes
Do Update XML schema option avaliable only in MDM 7.1?? not in 5.5?
Yes
A good description and usage is given by Aamir here Update of XML syndication map when XSD is changed
One more thing want to clear : I created a scheme and assigned the XSD.. Now when I created the port I am unable to assing the schema like I do for import map??? then what is the use of XSD schema for outbbound??
Seems you are not using in the way it is supposed to.the exact usage and defining what feature is available with which port is mentioned in pg no 356 of Console guide.
What is the usual method of import XSD and Outbound XSD?? Do Source and Target systems provide XSDs to MDM or MDM provides to Source and Target Systems?
For Standard contents SAP provides ready made xsds.
It is important to note that xsds are only to make MDM and other system understand the xml so they should be same.
To do this you can use Altova tool to create xsds based on your xml,also PI can help you do the same.
You can create xsd with PI for other idoc type too.
Hope this helps.
Thanks,
Ravi -
Hello PI people.
I have a problem reguarding to a XSD file (standard DSML found here: [DSMLv2|http://www.oasis-open.org/committees/dsml/docs/DSMLv2.xsd]).
When I Import it as external definition to PI Integration builder it all works fine but if I undfold the message "Filter" the there is problem with the defintions for "not" and after one more fold on "and" or "or" the same problem is shown. It looks like PI understands the XSD but it just not permit recursive nodes?
Is it the XSD that dosent meet the PI standard or is it a internal thing in PI that needs to be activated to handle recursive nodes i XSD?
(When a message is mapped with this DSML all the error prone nodes are stripped..)
// JesperHello Jesper,
You can refer to this document for supported XSD and WSDL:
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00a9a425-1769-2a10-9196-bd8eeed72e4c
Once you open this excel document go to row 94 for Recursive Data Structures, it says it is supported but there is a reference to row 143 which says
Recursive data structure must be expanded in design-time manually to the desired depth
If what you are thinking is dynamic recursion, then it is not possible. You have to use Java Mapping/XSLT for that. Now as for the nodes not displaying, right-click on the node and then select expand recursive structure.
Hope this helps,
Mark -
XML entities in xs:base64Binary
Hi there,
this is my first Post, and i hope i am at the right place in this forum.
I am integrating a third party application, that provides WSDL files for generating web services. An internal Web Service is creating an XML which is than encoded via base64 an sent as a SOAP message to the application.
So the SOAP message contains an element (type xsd:base64Binary) in wich the base64 content is transported. The problem is, that in this base64 string, there are xml entities &#xA; instead of the allowed base64 whitespace characters.
Can anyone give me a hint, if these character entities can be supressed?
Best
ThomasHi,
Sorry, but i think i cant do search and replace here.
@David: the SOAP message containing the base64Binary element is sent from SAP to the application. It is created by a consumer proxy we generated from the WSDL files provided by the third party application (namely StreamServe) . The application cant handle the character entities &#xA; the base64 string contains.
We also regenerated the proxy class, but there ist still a mapping from the xml schema type xsd:base64Binary to ABAP RAWSTRING.
This error (or these character entities) occur, since we upgraded to EHP1, so i think there might be the cause for this behaviour.
Best
Thomas -
Import XSD to create Data type in Design
hi,
I know that we can import XSD in Design and create data type,my question is:
1. Can i import an XSD thats been created in message mapping and use that to create my data type in design.
(or)
2.Should i have to write an XSD on my own and then import it to create my data type, and is there any standard format to write it.Hello Prashanth,
For your first question: i don't know exactly what you mean that the the xsd you create in the data mapping steps. So can you explain it in details?
For your 2nd question: Sure you can write your own XSD to create a data type. And i will give you an example xsd file format. Then you can import it in the XSD tab view.
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://sap.com/xi/XI/hansteel" targetNamespace="http://sap.com/xi/XI/hansteel">
<xsd:complexType name="CustomerInfo">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
a6c26c80000f11dac45e00096b1669b3
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="ID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
dfe699c0e7bc11d9c736d51c0a0013e1
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NAME">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
dfe82060e7bc11d9b2efd51c0a0013e1
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="35" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CUSTTYPE">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
dfe82061e7bc11d9c193d51c0a0013e1
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="POSTCODE">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
e93039a0e7bc11d9c7c6d51c0a0013e1
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CITY">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
f0122850e7bc11d99189d51c0a0013e1
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="35" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Hope this will be helpful.
Eric Ma -
Best practice for how to access a set of wsdl and xsd files
I've recently beeing poking around with the Oracle ESB, which requires a bunch of wsdl and xsd files from HOME/bpel/system/xmllib. What is the best practice for including these files in a BPEL project? It seems like a bad idea to copy all these files into every project that uses the ESB, especially if there are quite a few consumers of the bus. Is there a way I can reference this directory from the project so that the files can just stay in a common place for all the projects that use them?
BretHi,
I created a project (JDeveloper) with local xsd-files and tried to delete and recreate them in the structure pane with references to a version on the application server. After reopening the project I deployed it successfully to the bpel server. The process is working fine, but in the structure pane there is no information about any of the xsds anymore and the payload in the variables there is an exception (problem building schema).
How does bpel know where to look for the xsd-files and how does the mapping still work?
This cannot be the way to do it correctly. Do I have a chance to rework an existing project or do I have to rebuild it from scratch in order to have all the references right?
Thanks for any clue.
Bette -
Error during import of XSD file in message mapping
When i try to import an XSD file from desktop during message mapping I am getting a following error 'display problem'.
"Root element not found. Root Schema only describe type defintions. Cannot opent this XSD."
Is there any direct or work around way to import the file?
Any help would be appreciated.
Thanks
PremThanks Alexey
Let me specify some more detail. I got the following XSD file from a third party vendor. I am using XML spyeditor to edit the file. When i tried to add the global element it says the schema is not validated. How can it fix this?
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:include schemaLocation="http://www.ABC.com/schemas/ABCXMLlibrary.xsd"/>
<xs:complexType name="sesType">
<xs:sequence>
<xs:element name="eserviceNumber" type="xs:string">
<xs:element name="SAPPurchaseOrder" type="SAPPurchaseOrderType" minOccurs="0"/>
<xs:any namespace="##any" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
Thanks
Prem -
Source of xslt mapping and XSD/ XMT target structures for standard Idocs
Hi,
I am working on R/3 - XI - ICH scenario. I need xslt mapping and XSD/ XML target structures for standard IDoc like PROACT01,DELFOR01, DELVRY03. I tried to search it on marketplace but couldn't find it there. As per configuration document, these things are shipped with XI mapping content in live cache CD. But I don't have this CD with me. Can anybody tell me the source for these target structures and mapping program. ( Please share marketplace, site link or send me across the mail [email protected])
Thank you in advance.
Anand More.Anand the other option is to import the corresponding idocs into your integration repository and then you can view the generated XSD there.
As regards XSLT mapping, you need to basically first identify as to what form you want to transform your source idoc into.
For some help on XSLT mapping check the following threads,
https://www.sdn.sap.com/sdn/collaboration.sdn?contenttype=url&content=https%3A//forums.sdn.sap.com/topusers.jspa%3FforumID%3D44
https://www.sdn.sap.com/sdn/collaboration.sdn?node=linkFnode1-6&contenttype=url&content=https://Process Integration (PI) & SOA Middleware
Also have a look at my code samples,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-code-samples/generic xslt mapping in sap xi, part i.pdf
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9692eb84-0601-0010-5ca0-923b4fb8674a
cheers
Sameer -
Hi All,
I want to transfer data from mdm through syndicator.
I created the follwing xsd file in xi.(message mapping)
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http:
mycompany.com\mdm" targetNamespace="http:
mycompany.com\mdm">
<xsd:element name="MT_Customer" type="DT_Customer" />
<xsd:complexType name="DT_Customer">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
495dde70551e11db9e560011433286d8
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Customer_Data">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
13886a30550b11dbcb99cf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Customer" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
13886a31550b11dba3f2cf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Title" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
13886a32550b11dbcc76cf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Name1" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
13886a33550b11db9c96cf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Name2" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
13886a34550b11dbbbc7cf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Name3" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
13886a35550b11db8470cf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Name4" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
13886a36550b11dbb3bfcf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Searchterm1" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
13886a37550b11dbae35cf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Searchterm2" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
13886a38550b11dbb7c9cf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="City_Post_Code" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
13886a39550b11dba621cf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="City" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
13886a3a550b11db9287cf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Country" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
13886a3b550b11dbb137cf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Region" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
13886a3c550b11dbcc68cf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Noof_Employees" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
13886a3d550b11db8a29cf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Annual_Sales" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
13886a3e550b11dbbe2bcf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Currency_Of_Sales" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
13886a3f550b11dbb901cf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Pobox" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
13886a40550b11db97aecf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Language" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
13886a41550b11dba4becf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Salesdata" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
13886a42550b11dbae61cf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Bank_Details" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
1f101890551e11dbc760cf9a0abc902e
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
And add xml shema entry in mdm console for the above schema.
When I try to set destination properties in syndicator...
I selected XMLSchema as type,client system,schema name. but,I am not able to select any <b>root</b> for it and I am not able to go proceed in syndication.
Is there any problem in the above xsd file ?
Please help me.Hello Rama:
It happends because on your XSD you didn't define a data root tag:
<b><xsd:element name="dataroot">
</b>
I here paste an example of this. Please note how Office Access wrapped it all on the dataroot tag:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:od="urn:schemas-microsoft-com:officedata">
<xsd:element name="dataroot">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="SP1PERS" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="generated" type="xsd:dateTime"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="SP1PERS">
<xsd:annotation>
<xsd:appinfo>
<od:index index-name="PrimaryKey" index-key="SPBPERS_PIDM " primary="yes" unique="yes" clustered="no"/>
<od:index index-name="STVNATN_CODE" index-key="STVNATN_CODE " primary="no" unique="no" clustered="no"/>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="SPBPERS_PIDM" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SP1PERS_HEIGHT_x0020_" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SP1PERS_FECHA_MATRIMONIO" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ST4TTRA_TITULO_TRATO" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STVNATN_CODE" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="GTVZIPC_CODE_LUGAR_NACIMIENTO" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="GTVZIPC_CODE_LUGAR_PROCEDENCIA" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SP1PERS_CURP" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SP1PERS_ACTIVITY_DATE" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SP1PERS_USER_x0020_" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Field11" minOccurs="0" od:jetType="text" od:sqlSType="nvarchar">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
I hope that helps
Regards
Alejandro
Maybe you are looking for
-
Mid-2009 MacBook Pro 13" install and format SSD drive
I'm running OS 10.8.3 and intend to install an SSD hard drive. They recommended formatting the hard drive prior to installation??? I have a backup of my hard drive so the data is protected. I've seen some suggestions on the forum but for older vers
-
Mac Mini 5.1 External Hard drives
I am having troble with my Fantom 2TB USB 3.0 and my mac mini 5.1. My trouble doesn't have anything to do with bluetooth, but for some reason the mac becomes unstalbe with the drive attached and a lot of apps crash and sometimes the mac reboots. I a
-
New computer, but long time itunes and Ipod mini user. Downloaded itunes with no apparent difficulty. Clicked to run it, but hourglass flashed for a second, then no action. Repeated tries resulted in the same thing. Then, after disabling Norton and o
-
No organisational structure maintained for this item
I am trying to create a shopping cart in SRM 4.0 front end and i keep getting the error no organisational structure maintained for this item. the purchasing group is not being picked up.I will greatly appreciate your help in solving this issue. thank
-
I spent 2 hours working on a slideshow of my last hiking trip. Right before I went to export the slideshow, I changed the aspect ratio rom 16:10 to 16:9. Doing this rearranged ALL of the slides in my slideshow, with no way to undo it. It took the mai