Explain about xml schema with example

Hi,
Kindly anybody explain about xml schema with example?
With Regards,
L.rajesh

Maybe this is what you are looking for ??? If not give us more info...
Re: How it work?

Similar Messages

Question about xml schemas and the use of unqualified nested elements

Hello,
I have the following schema:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns="http://xml.netbeans.org/examples/targetNS"
    targetNamespace="http://xml.netbeans.org/examples/targetNS"
    elementFormDefault="unqualified">
    <xsd:element name="name" type="xsd:string"/>
    <xsd:element name="age" type="xsd:int"/>
    <xsd:element name="person">
        <xsd:complexType>
            <xsd:sequence>
                <xsd:element ref="name"/>
                <xsd:element ref="age"/>
               <xsd:element name="height" type="xsd:int"/>
            </xsd:sequence>
        </xsd:complexType>
    </xsd:element>
</xsd:schema>I am just wondering why would someone have a nested element that is unqualified? here the "height" element.
Can anyone explain this to me please?
Thanks in advance,
Julien.
here is an instance xml document
<?xml version="1.0" encoding="UTF-8"?>
<person xmlns='http://xml.netbeans.org/examples/targetNS'
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xsi:schemaLocation='http://xml.netbeans.org/examples/targetNS file:/E:/dev/java/XML/WebApplicationXML/web/newXMLSchemaThree.xsd'>
<name>toto</name>
<age>40</age>
<height>180</height>
</person>

Don't worry about it.
There are two different styles of schemas. In one style, you define the elements, attributes, etc. at the top, and then use the "ref" form to refer to them. (I call this the "global" style.) The other style is to define elements inline where they are used. ("local" style)
Within some bounds, they work the same and which you use is a choice of you and the tools that generate the schemas.
A warning about the local style. It is possible to define an element in two different locations in the schema that are different. It will get past all schema validation, but it seems wrong to my sense of esthetics. With the global style, this will not happen.
So, how did this happen? Probably one person did the schema when it only had a name and age. Then, someone else added the height element. They either used a different tool, or preferred the other style. I'm aware of no difference in the document you have described between the two styles.
Dave Patterson

How to load an XML schema with Data Integrator ?

Post Author: Kris Van Belle
CA Forum: Data Integration
Is someone having experience with loading data from a regular table into an XML schema ?
What are exactly the steps to undertake ? The DI user manual does not provide that much information...

Post Author: bhofmans
CA Forum: Data Integration
Hi Kris,
In the Designer.pdf there is a chapter called 'nested data' with more information, but you can also check this website with some detailed instructions and examples on how to build a nested relational data model (NRDM).
http://www.consulting-accounting.com/time/servlet/ShowPage?COMPANYID=43&ELEMENTID=161
(Thanks to Werner Daehn for putting this together).

Can't import XML schema with ref to external namespace

In TopLink 10.1.3 Dev Preview 3 (build 041116), I have 2 simple schema files. One defines an element as a ref to an element in the other schema, so the ref points to an element in an external namespace. TopLink won't import this schema.
First schema, imports fine:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
   xmlns:xs="http://www.w3.org/2001/XMLSchema"
   targetNamespace="http://www.oracle.com/employee"
   xmlns="http://www.oracle.com/employee"
   elementFormDefault="qualified"
   attributeFormDefault="unqualified">
     <xs:element name="employee">
       <xs:complexType>
         <xs:sequence>
                <xs:element name="name" type="xs:string"/>
         </xs:sequence>
       </xs:complexType>
     </xs:element>
</xs:schema>
Second schema, fails import with "ERROR: null. Please check to ensure the document conforms to the XML Schema specification and try again":
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
   xmlns:xs="http://www.w3.org/2001/XMLSchema"
   targetNamespace="http://www.oracle.com/department"
   xmlns="http://www.oracle.com/department"
   xmlns:employee="http://www.oracle.com/employee"
   elementFormDefault="qualified"
   attributeFormDefault="unqualified">
   <xs:import
     namespace="http://www.oracle.com/employee"
         schemaLocation="employee.xsd"/>
   <xs:element name="department">
     <xs:complexType>
       <xs:sequence>
         <xs:element ref="employee:employee"         maxOccurs="unbounded"/>
       </xs:sequence>
     </xs:complexType>
   </xs:element>
</xs:schema>
Both schemas are valid according to the W3C schema validation checker at http://www.w3.org/2001/03/webdata/xsv.
I can work around the issue by putting the employee definitions into the department schema file so that all elements are in the same namespace. But I would like the schemas to be in separate files for better modularity and maintainability.
Am I doing something wrong? I would really like to be able to use references to external namespaces in my element definitions.
Thanks,
Dave

Hello David,
Apologies, but this is a bug in DP3 with respect to references to elements in imported namespaces. This has been fixed in current code, but until you get that, there are a couple ways to work around it:
==========================================================
1) Use an include rather than an import.
department.xsd
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
    targetNamespace="http://www.oracle.com/department"
    xmlns="http://www.oracle.com/department"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    elementFormDefault="qualified"
    attributeFormDefault="unqualified">
   <xs:include schemaLocation="employee.xsd"/>
   <xs:element name="department">
      <xs:complexType>
         <xs:sequence>
            <xs:element ref="employee" maxOccurs="unbounded"/>
         </xs:sequence>
      </xs:complexType>
   </xs:element>
</xs:schema>employee.xsd
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    targetNamespace="http://www.oracle.com/department"
    xmlns="http://www.oracle.com/department"
    elementFormDefault="qualified"
    attributeFormDefault="unqualified">
   <xs:element name="employee">
      <xs:complexType>
         <xs:sequence>
            <xs:element name="name" type="xs:string"/>
         </xs:sequence>
      </xs:complexType>
   </xs:element>
</xs:schema>You should only have to import the parent schema (i.e. department.xsd), as the included document will automatically be built in. Note that this works for imports as well, provided that there aren't nasty bugs blocking the process.
==========================================================
2. Build everything into the same document
department.xsd
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
    targetNamespace="http://www.oracle.com/department"
    xmlns="http://www.oracle.com/department"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    elementFormDefault="qualified"
    attributeFormDefault="unqualified">
   <xs:element name="department">
      <xs:complexType>
         <xs:sequence>
            <xs:element ref="employee" maxOccurs="unbounded"/>
         </xs:sequence>
      </xs:complexType>
   </xs:element>
   <xs:element name="employee">
      <xs:complexType>
         <xs:sequence>
            <xs:element name="name" type="xs:string"/>
         </xs:sequence>
      </xs:complexType>
   </xs:element>
</xs:schema>Obviously, this one won't work quite as well in some cases.
==========================================================
Until you can get to the latest code, I hope this helps some.
- Paul

Explain TO_CHAR(),TO_DATE(),TO_NUMBER() with examples

Hi All,
I have little bit confusion on TO_CHAR(),TO_DATE(),TO_NUMBER().
Can any one please explain when will use that functions with examples.
Thanks & Regards,

974825 wrote:
Hi All,
I have little bit confusion on TO_CHAR(),TO_DATE(),TO_NUMBER().
Can any one please explain when will use that functions with examples.
Thanks & Regards,
For to_date and to_char (as applied to dates) see: http://edstevensdba.wordpress.com/2011/04/07/nls_date_format/ - But I want to store my date as ...
Once you understand how it works for dates, you should have a good foundation for understanding how it works for numbers.

Error while adding XML Schemas with cyclic references

I have to use the 3rd party bunch of XML Schema files, but two of them reference each other, i.e. there are cyclic references. ESB displays a conflict in this case.
Is there any way to resolve the problem without changing source xsd-files?
My configuration is WebLogic Platform 9.2.1 + AquaLogic Service Bus 2.6

Our scenario is that the corporate data model (in UML) is transformed into XSD and delivered as several separate XSD files. Our modellers argue that cyclic references make sense in this context and are not forbidden by the standard.
We restructured the transformation so that only a single XSD file is delivered (~550K) but this is unwieldy, inflexible and ALSB is sloooooooooow when manipulating a schema of this size inside the console.

Special Problem about XML schema simpleType definition

hi, OracleTeam,
hi, Bruno,
Fiena comes again :( :p
It seems you do not use Oracle schema processor . I met a problem about schema ...
here is test1.xsd
<?xml version="1.0"?>
<schema xmlns = "http://www.w3.org/1999/XMLSchema"
targetNamespace = "http://www.sample.com"
xmlns:vs ="http://www.sample.com">
<element name = "Test" type= "vs:test" minOccurs ="1" maxOccurs="1"/>
<simpleType name= "test">
<restriction base="integer">
<minInclusive value="-1290"/>
<maxInclusive value="29035"/>
</restriction>
</simpleType>
</schema>
here is test1.xml
<?xml version="1.0"?>
<video:Video xmlns:video="http://www.sample.com"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xsi:schemaLocation="http://www.sample.com test1.xsd"
>
<Test>11</Test>
</video:Video>
but when I validate the two files with schema processor , it will said :
Validation failed, error 909 ( not parer, but schema processor)
I don't know why everytime I define "simplyType" , it will show this error...
Thank you no matter you can answer me :)
Best wishes,
fiena
null

Thank you,
I do understand it,
but why or when it is necessary to have this structure ?
I ask because I found simple exsamples of XML-Datafiles without this :
like this example
<A31>
<HEADER>TEST HEADER</HEADER>
<MASSNAHME>NR_10-0009/02-A07</MASSNAHME>
<TEILMASSNAHME>
<LFDNR>1</LFDNR>
<STT3X>dies ist text 1</STT3X>
</TEILMASSNAHME>
<TEILMASSNAHME>
<LFDNR>2</LFDNR>
<STT3X>dies ist text 2</STT3X>
</TEILMASSNAHME>
</A31>
in contrast to that :
<A31>
<A31_ITEM>
<HEADER>TEST HEADER</HEADER>
<MASSNAHME>NR_10-0009/02-A07</MASSNAHME>
<TEILMASSNAHME>
<TEILMASSNAHME_ITEM>
<LFDNR>1</LFDNR>
<STT3X>dies ist text 1</STT3X>
</TEILMASSNAHME_ITEM>
<TEILMASSNAHME_ITEM>
<LFDNR>2</LFDNR>
<STT3X>dies ist text 2</STT3X>
</TEILMASSNAHME_ITEM>
</TEILMASSNAHME>
</A31_ITEM>
</A31>
this creates finally different ( incorrect ) schema-files
to import into nested tables ?
Norbert

Could anyone please explain Polymorphism to me with Example?

I am trying to learn the concept of Polymorphism in Java and I am having a tough time understanding what it is. I keep confusing it with inheritance which I am now comfortable with but I don't get what the book says about polymorphism and a lot of tutorials I have seen do not seem to explain it as to a layman. Please Help a newbie to programming understand POLYMORPHISM
Java NewBie

Here's a real-world example: I had a large data structure (a tree, basically) whose contents aren't relevant to this discussion. I also had a variety of functionality required, a bunch of which required visiting every node of the data structure.
Now, I could write the same tree-spanning code over and over again for each separate bit of functionality that required it. Or try to create a library function that spanned the tree (although in reality, it's hard to write library functions like that without a degree of polymorphism). But these were either redundant or clumsy or both.
So the approach I took was to add a "visitAll" method to the data structure. (This is actually an example of encapsulation -- the data and the operations on the data are stuck together.) The visitAll method took an object, and for each node in the tree, it invoked a method (let's call it "absorb") on the given object.
continued...

Error while generating an XML Document from XML Schema with JAXB

Hi,
I am following this OTN tutorial to generate the XML document from Java classes got from the XSD document.
http://www.oracle.com/technology/pub/notes/technote_jaxb.html
I am able to generate all the Java classes but getting error on compiling the XMLConstructor.java class which is use for generating the XML document :
I am using JDK 1.5 and
Oracle 10g XML Developer's Kit (XDK) Production for Java. xdk_nt_10_1_0_2_0_production
(though these are warnings I am not able to run it.)
Error
C:\Prototype\classes\jaxbderived\catalog>javac -Xlint XMLConstructor.java
warning: [path] bad path element "%CLASSPATH%": no such file or directory
XMLConstructor.java:42: warning: [unchecked] unchecked call to add(E) as a member of the raw type java.util.List
journalList.add(journal);
^
XMLConstructor.java:46: warning: [unchecked] unchecked call to add(E) as a membe
r of the raw type java.util.List
articleList.add(article);
Thanks
Sanjeev ([email protected])

Use JDK 1.4.

Reading information about XML Schema.

Hi,
I receive the data structure as a Node and based on some logic I create new nodes. Now I found the root node where I need to append by newly created nodes. Since the root folder contains many children I am not sure before which node I need to insert by newly created node for the inputSource to be still schema valid. I can only find that information by reading the XSD schema. Is there some API/objects that can help me out in finding that kind of information or is the only option of parsing the schema through DOM/SAX and figuring out where the newly created node needs to be inserted.
Thanks,

You could try using XPath

Please brief Describes about error handling with example

dear
please describe about error handling and exception handling

Darryl Burke wrote:
This is the third thread you have started here, without bothering to reply to responses on the two earlier threads. Not the best way to continue to get help on a forum, that.Not to mention the fact that it's a horribly broad and vague question that is better answered by a combination of books, tutorials, and google searches.

Explain about earlydelta intialization with business senario

give me reply as early as possible

hi found on help sap here is the link
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/content.htm
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 posting of data in the source system. The option of executing an early delta initialization is only available if the DataSource extractor called in the source system with this data request supports this.
Extractors that support early delta initialization are delivered with Plug-Ins as of Plug-In (-A) 2002.1.
You cannot run an initialization simulation together with an early delta initialization.
in fact not all datasources allow this type of update check on table roosource wiht type of delta in general what i have seen is that some datasources of LO cockpit like for deliveries you can use this type of update.
hope this could help you
regards
Boujema

Problems using XML DB with Schema

Hi,
I am attempting to use Java code running on WebLogic Server 10.3 to insert some XML documents into an Oracle Database (11gr1) and have them ‘shredded’ into columns, as the documentation claims is possible.
I registered the XML Schema with Oracle using SQL*Plus, and have verified that tables and types are being built as expected. (Partial details below if needed.)
I am able to insert records into the table, using XMLType, but they do not appear to be shredded in such a way that we can perform relational queries on them. References I found on the Oracle web site and others implied that if the XMLType is created with a schema associated, the insert will perform the shredding.
When I attempt to create the XMLType with a schema in either of the two ways below, I get SQLExceptions.
xml = XMLType.createXML(conn,doc.toString(), schema, true, true);
Or
xml = xml.createSchemaBasedXML(schema); // after a successful XMLType.createXML(conn, doc.toString());
The most recent error is java.sql.SQLException: Fail to convert to internal representation (full stack trace along with the doc.toString() is below).
How can I get more insight into what is causing this problem? Is there a more appropriate way to persist XML documents into Oracle relational tables? Is there some sample code/tutorial I can use that shows how to do this?
Thank you,
-=Alan
--- Version of Oracle and validating that the schema is registered.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> describe objecthandle;
Name Null? Type
TABLE of SYS.XMLTYPE(XMLSchema "http://foo.org/mySchema" Element "ObjectHandle") STORAGE Object-relational TYPE
"OBJECTHANDLE_TYPE"
--- The XML document I am trying to persist.
<ObjectHandle objectuid="objecthandle_301" serviceURL="URL-Fri Oct 31 17:47:19 EDT 2008" xmlns="http://foo.org/mySchema"/>
--- The most recent error with full stack trace.
java.sql.SQLException: Fail to convert to internal representation
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:173)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:229)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:403)
at oracle.sql.OPAQUE.<init>(OPAQUE.java:85)
at oracle.xdb.XMLType.toDatum(XMLType.java:492)
at oracle.jdbc.driver.OraclePreparedStatement.setORADataInternal(OraclePreparedStatement.java:7437)
at oracle.jdbc.driver.OraclePreparedStatement.setObjectInternal(OraclePreparedStatement.java:8158)
at oracle.jdbc.driver.OraclePreparedStatement.setObject(OraclePreparedStatement.java:8149)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.setObject(OraclePreparedStatementWrapper.java:229)
at weblogic.jdbc.wrapper.PreparedStatement.setObject(PreparedStatement.java:314)
at org.foo.test.Test.doInsert(Test.java:76)
at org.foo.test.Test.testAddObjectHandle(Test.java:32)
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.component.pojo.JavaClassComponent.invoke(JavaClassComponent.java:112)
at weblogic.wsee.ws.dispatch.server.ComponentHandler.handleRequest(ComponentHandler.java:84)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:141)
at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:114)
at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:285)
at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:169)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Thanks - I have been fighting with another problem for the past few days, but am getting back to this now...
I think the second link you sent helped me realize that the particular error came while using the 'thin' driver; I had other problems when I used the OCI driver... I'll try it again and see, now that I'm using a container managed datasource...
I registered the schema in SQL*Plus using the command:
BEGIN
DBMS_XMLSCHEMA.registerURI(
'http://foo.org/mySchema',
'/home/foo/mySchema.xsd',
LOCAL=>TRUE, GENTYPES=>TRUE, GENBEAN=>FALSE, GENTABLES=>TRUE);
END;
Everything created, was created from that command. I did use xdb annotations, but perhaps I didn't use enough of them...
In this simple example (I have more complicated ones) there are only the two attributes; I've been hoping that I would be able to use normal sql statements, e.g.
SELECT * FROM objecthandle WHERE objectuid='objecthandle_301';
and get back either the XML or a resultset -- I'm less picky about that right now.
I've been unable to find good reference material for this query; any advice will be appreciated.

XML Schema Collection (SQL Server 2012): Complex Schema Collection with Attribute - Should xs or xsd be used in the coding?

Hi all,
I just got a copy of the book "Pro SQL Server 2008 XML" written by Michael Coles (published by Apress) and try to learn the XML Schema Collection in my SQL Server 2012 Management Studio (SSMS2012). I studied Chapter 4 XML Collection of the book
and executed the following code of Listing 4-8 Complex Schema with Attribute:
-- Pro SQL Server 2008 XML by Michael Coles (Apress)
-- Listing04-08.sql Complex XML Schema with Attribute
-- shcColes04-08.sql saved in C:\\Documents\XML_SQL_Server2008_code_Coles_Apress
-- 6 April 2015 8:00 PM
CREATE XML SCHEMA COLLECTION dbo.ComplexTestSchemaCollection_attribute
AS
N'<?xml version="1.0"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="item">
<xs:complexType>
<xs:sequence>
<xs:element name="name" />
<xs:element name="color" />
<xs:group ref="id-price" />
<xs:group ref="size-group" />
</xs:sequence>
<xs:attribute name="id" />
<xs:attribute name="number" />
</xs:complexType>
</xs:element>
<xs:group name="id-price">
<xs:choice>
<xs:element name="list-price" />
<xs:element name="standard-cost" />
</xs:choice>
</xs:group>
<xs:group name="size-group">
<xs:sequence>
<xs:element name="size" />
<xs:element name="unit-of-measure" />
</xs:sequence>
</xs:group>
</xs:schema>';
GO
DECLARE @x XML (dbo.ComplexTestSchemaCollection_attribute);
SET @x = N'<?xml version="1.0"?>
<item id="749" number="BK-R93R-62">
<name>Road-150 Red, 62</name>
<color>Red</color>
<list-price>3578.27</list-price>
<size>62</size>
<unit-of-measure>CM</unit-of-measure>
</item>';
SELECT @x;
GO
DROP XML SCHEMA COLLECTION dbo.ComplexTestSchemaCollection_attribute;
It worked nicely. But, I just found out the coding that was downloaded from the website of Apress and I just executed was different from the coding of Listing 4-8 listed in the book: all the <xs: ....> and </xs: ..> in my SSMS2012 are
listed as <xsd:...> and </xsd:...> respectively in the book!!?? The same thing happens in the Listing 4-3 Simple XML Schema, Listing 4-5 XML Schema and Valid XML Document with Comple Type Definition, Listion 4-6 XML Schema and XML
Document Document with Complex Type Using <sequence> and <choice>, and Listing 4-7 Complex XML Schema and XML Document with Model Group Definition (I executed last week) too. I wonder: should xs or xsd be used in the XML
Schema Collection of SSMS2012? Please kindly help, clarify this matter and explain the diffirence of using xs and xsd for me.
Thanks in advance,
Scott Chang

Hi Scott,
Using xs or xsd depends on how you declare the namespace prefix.
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="item">
I've posted a very good link in your last question, just in case you might have missed it, please see the below link.
Understanding XML Namespaces
In an XML document we use a namespace prefix to qualify the local names of both elements and attributes . A prefix is really just an abbreviation for the namespace identifier (URI), which is typically quite long. The prefix is first mapped to a namespace
identifier through a namespace declaration. The syntax for a namespace declaration is:
xmlns:<prefix>='<namespace identifier>'
If you have any question, feel free to let me know.
Eric Zhang
TechNet Community Support

Hi gurus, can any one explain me about Badi & Bapi with eg.?

Hi gurus,
Can any one explain me about Badi & Bapi with examples.
Regards
Raghu

Hi Raghu
1) Badis means:
The BAdIs of the enhancement concept are not treated as standalone objects, but are integrated in the overall concept. Thus, the tools for defining BAdIs are part of the Enhancement Builder included in the ABAP Workbench.
Transaction SE18, up to now the only entry point for defining classic BAdIs, now manages classic and new BAdIs. When an existing BAdI is displayed or changed, it analyzes whether the BAdI is a classic or a new one, and then switches to the respective tool. In the case of a new BAdI, this tool is the enhancement spot editor
2) Bapis means:
BAPIs can be called within the R/3 System from external application systems and other programs. BAPIs are the communication standard for business applications. BAPI interface technology forms the basis for the following developments:
Connecting:
New R/3 components, for example, Advanced Planner and Optimizer (APO) and Business Information Warehouse (BW).
Non-SAP software
Legacy systems
Isolating components within the R/3 System in the context of Business Framework
Distributed R/3 scenarios with asynchronous connections using Application Link Enabling (ALE)
Connecting R/3 Systems to the Internet using Internet Application Components (IACs)
PC programs as frontends to the R/3 System, for example, Visual Basic (Microsoft) or Visual Age for Java (IBM).
Workflow applications that extend beyond system boundaries
Customers' and partners' own developments
Thanks
Trinath

Explain about xml schema with example

Similar Messages

Maybe you are looking for