Error while importing .par file into NWDS
Hi Experts,
For my query I saw a similar thread in sdn forum. the link is given below.
/thread/382306 [original link is broken]
I have unzipped the par file and inside this there is no other par file. So I have to import this par file only.
Can anybody give some alternate way to resolve this.
Thanks a lot in advance.
Edited by: Srini on Nov 22, 2010 10:46 PM
Hi Experts,
Please reply on this.
Thanks a lot in advance.
Similar Messages
-
Error after importing PAR file into NWDS
Hi Experts,
I have imported a par file into my NWDS worlspace . While building the project it's giving the following error .
import javax.servlet.http.HttpServletResponse can't be resolved .
While i am organizing the importa , the same import is getting deleted and i am getting a new error as follows .
The project was not built since its classpath is incomplete. Cannot find the class file for javax.servlet.http.HttpServletRequest. Fix the classpath then try rebuilding this project.
jdk1.5 has been configured correctly inside NWDS and i have tested it also .
Can anybody help me out regarding this .
Thanks in advance .Hi Jain,
Just right click on project to properties->java build path-> add external jars add the jar file servlet.jar.
Venkat. -
Error While uploading PAR File into NWDS
Hi Experts,
I have been to this location:
Server(D)\usr\sap\P64(SID)\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
I have copied this file com.sap.portal.runtime.logon.par.bak and pasted on my desktop.
Changed the name to com.mycompany.portal.runtime.logon.par
I tried to upload the file to NWDS(File --> Import --> Par file) and I am getting the fallowing error.
http://imageshack.us/photo/my-images/853/error1un.png/
and when i click OK on above Error
i get this errors : http://imageshack.us/photo/my-images/571/error2v.png/
I am unable to upload the Par file did i miss something?
Regards,
SivaDear Siva,
that is indeed strange.
Still don't know if this could be an issue with your NWDS or the PAR itself.
So let's do 2 tests
===============================================
TEST NR. 1
Let's try and check the NWDS first by creating a custom PAR.
Don't worry, it's easy.
Just open your NWDS and go to the top menu
File > New > Project
Inside the popup window that will open please choose
Portal Application (on the left) and Create a Portal Application Project (on the right)
Then give any name you would like (no spaces or dots, etc...)
You now have a Portal project created on NWDS ( you will see a folder on the left side with your project name)
Click on that folder with your LEFT mouse button and choose EXPORT
Choose PAR File
Choose your Project
Choose a path where you want your PAR file to be saved. (uncheck the deploy PAR file, but check the include the source code).
And click Finish.
Now delete the project you have created (by clicking on the folder with your LEFT mouse button again, but chose DELETE project)
Now you're ready to re-import the PAR file.
===============================================
TEST NR. 2
Maybe your standard PAR file that you've downloaded doesn't have the source code included or is corrupted.
Please try to open it with a ZIP program and check what type of structure/files you have there.
Have you also checked your NWDS log ?
You could also share here that log, so that I can better help you.
Kindest Regards
/Ricardo -
Error while importing PAR file from local system.
Hi Experts,
While importing PAR file into my NWDS, I am encountered by some strange error.
Please refer below screenshot for your reference.
After clicking on "OK" button of the above error popup, another popup emerge with different error, please find below the screenshot for this error.
Please let me know the reason and resolution of this error. It will be very helpful for me.
Thanks in advance.
Thanks and Regards,
sarvesh AgarwalHi ,
Are u trying to import with .bak extension ? If so please rename the file and remove .bak extension and try.
x.par is enough to import not x.par.bak.
Thanks, -
Import .par file into NWDS and Rum it without deploying ?
Hello All,
I'm new to the NWDS and the Portal.
I've many Qns on my Requirement. Hope u guys can help me out in resolving my Issues.
Is this the right forum to place my Query ?
If not then please let me know the right forum .
My Requirement is like this :-
1. I need to create a Portal Application which calls an URL.
2. But before developing this, my Client gave me one 2 options :
a. He gave me a par file and asked me to make changes in it.
b. Create a new Portal Project which calls the URL ( Predefined ).
3. I wanted to check the 1rst option i.e " a ".
4. I tried to Import the .par file into NWDS like this :
* Windows --> Open Perspective --> Enterprise Portal .
* File --> Import --> Par FIle.
* I gave the name of the Project as PortalLogon.
5. I searched in the forum on this scenario and I found that the libraries for this project are not automatically imported.
<b>A .Can any one tell me how to import the libraries and which are all the libraries to be imported ?</b>
<b>B. How to test my PortalLogon Project without deploying ?</b>
Is it possible to test this Project without deploying ?
If yes can anyone tell me hoe to do this ?
Regards,
Deepu.KHi Deepu,
Usually Server will be having all the jar files and If you want to deploy your par file using NWDS you need to give a path to your Jar file location.
So better download all the jar files from your server and keep it in your local desktop.
Create a new folder called "JarFiles" in your desktop and keep all of your jar files inside.
Download Jar finder from IBM Site ( search for "Resolving Java Classpath Issues" in SDN ,you will get a pdf and follow it.).Add it as a plugin to your NWDS path.
Restart NWDS.
Now you can resolve the jar file issues.there are many weblogs /articles/forum QAs regarding this.
If u need more clarification,please let me know.
Thank you.
Regards,
Karthick Eswaran -
Import .par file into NWDS and Run without deployment ?
Hello All,
I'm new to the NWDS and the Portal.
I've many Qns on my Requirement. Hope u guys can help me out in resolving my Issues.
My Requirement is like this :-
1. I need to create a Portal Application which calls an URL.
2. But before developing this, my Client gave me one 2 options :
a. He gave me a par file and asked me to make changes in it.
b. Create a new Portal Project which calls the URL ( Predefined ).
3. I wanted to check the 1rst option i.e " a ".
4. I tried to Import the .par file into NWDS like this :
* Windows --> Open Perspective --> Enterprise Portal .
* File --> Import --> Par FIle.
* I gave the name of the Project as PortalLogon.
5. I searched in the forum on this scenario and I found that the libraries for this project are not automatically imported.
<b>A .Can any one tell me how to import the libraries and which are all the libraries to be imported ?</b>
<b>B. How to test my PortalLogon Project without deploying ?</b>
Is it possible to test this Project without deploying ?
If yes can anyone tell me hoe to do this ?
Regards,
Deepu.Khi Deepu,
for simply displaying a URL, you can use the commonly available URL iView.
your folder->new->create iView->iView from template->URL iView and then enter your URL
for the other think.......
you can create an iView from PAR file.
your folder->new->create iView->Iview from PAR->then select your PAR and create an iView for that.
and the last one.......to see the effect without deploying it on the portal......refer the link
http://help.sap.com/saphelp_nw2004s/helpdata/en/23/c0e240beb0702ae10000000a155106/content.htm
and the usual libraries to be associated are
<b>htmlb.jar</b> and
<b>com.sap.portal.htmlbbridge.zip</b>
Cheers........ -
Error while importing par file
dear Experts,
i am facing a problem while importing par.bak file. the error message comes
"indexed store transactions did not commit properly"
Reason
sorry an error occurred creating new project
then once i click ok
i get the error
com.sap.portal.plugins.config-archiver caused exception during the "unpack" operation
any one has the solution for thisHi ,
Are u trying to import with .bak extension ? If so please rename the file and remove .bak extension and try.
x.par is enough to import not x.par.bak.
Thanks, -
Error while importing tpz file into XI Design
Hi All,
When i am trying to import latest exported tpz file from Dev system into Q system i am getting below error.
Also the tpz file i am importing , with same file name already i have imported earlier into Q system through other Dev system. Now i am importing the exported file through prod fix environment dev system. Please help me , how to import the file without this error. Also, how to avaoid duplicate file name for importing tpz files or overwrite exiting imported tpz file which is having same file name.
Batch rolled back. Caused by java.sql.BatchUpdateException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00136623) violated at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:343) at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:10698) at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeBatch(BasicPreparedStatement.java:263) at com.sap.sql.jdbc.oracle.Oracle10gPreparedStatement.executeBatch(Oracle10gPreparedStatement.java:100) at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1129) at com.sap.sql.jdbc.common.CommonPreparedStatement.executeBatch(CommonPreparedStatement.java:991) at com.sap.engine.services.dbpool.wrappers.StatementWrapper.executeBatch(StatementWrapper.java:270) at com.tssap.dtr.pvc.basics.transaction.StatementReleasingConnection.executeBatch(StatementReleasingConnection.java:297) at com.tssap.dtr.pvc.versionmg.DefaultIntegrator.fireSQLBatches(DefaultIntegrator.java:1072) at com.tssap.dtr.pvc.versionmg.DefaultIntegrator.executeDBUpdates(DefaultIntegrator.java:384) at com.tssap.dtr.pvc.versionmg.DefaultIntegrator.integrate(DefaultIntegrator.java:337) at com.tssap.dtr.pvc.versionmg.VersionSet.integrate(VersionSet.java:183) at com.sap.aii.ib.server.pvcadapt.ImmutableVersionSet.integrate(ImmutableVersionSet.java:197) at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl._integrateUnconditionally(VersionSetIntegratorImpl.java:300) at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateClosedVersionSet(VersionSetIntegratorImpl.java:119) at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateClosedVersionSet(VersionSetIntegrator.java:52) at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:261) at com.sap.aii.ib.server.propagation.Propagator.integrateObjectVersions(Propagator.java:174) at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:191) at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480) at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:546) at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716) at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362) at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151) at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75) at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730) at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Thanks in advance.
Rajesh
Edited by: rajesh amrabad on Sep 11, 2008 10:35 PMIn addition to abobe answers,
Keep this .tpz file at below mentioned location
\usr\sap\<SID>\SYS\global\xi\repository_server\import\XI7_0_SAP_BASIS_7.00_09_00.tpz
then login to the IR and peoceed as Tools -
> import design objects. Her you will get this .tpz file, just import it.
follow the steps given in this link and check if you are doing the correct thing.
http://help.sap.com/saphelp_nw04/helpdata/en/93/a3a74046033913e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/content.htm
The steps that you require are listed below,
1) You must have the role SAP_XI_ADMINISTRATOR or SAP_XI_CONTENT_ORGANIZER to be able to export and import XI content.
2)You import the XI content by first copying the provided export files into an import directory on the host of the Integration Builder and then importing the files into the Integration Repository.
3)Copy the export files into the import directory for the Integration Repository (<systemDir>\xi\repository_server\import).If the files are packed, you must unpack them before importing.The actual export files have the extension .tpz. You must not unpack these files.
4)The import directory is created the first time you call the Integration Builder.
5)Start the Integration Builder and call the Integration Repository.
To do this, perform the following steps:
a. Log on to the SAP system on which your Integration Builder has been installed.
b. Open the Integration Builder start page by calling it either from your user menu or with Transaction SXMB_IFR.
c. Choose Integration Repository.
Choose Tools u00AE Import design objects to import the XI content.
6)Only the files from the import directory are offered to be imported. The sequence in which
you import the export files is not important.
7)After a successful import, the Integration Builder moves the imported TPZ files into the directory <systemDir>/xi/repository_server/importedFiles. The support package stack of imported software component versions is displayed on the Details tab page for the relevant software component version in the Integration Builder. If an error occurs, this information is important for support.
Hope i have been of some help. -
Error while importing CIM file into target SLD
Hi
We are in the process of moving our XI objects to QA.
As a first step , we are preparing the QA SLD ( we have a separate SLD instance for XI DEV and QA environments ).
We have our standard objects loaded into the QA SLD. Now for the custom objects :
1.I export the product and the corresponding SWCV from the source SLD .
2. I import the zip file into the target SLD in that order. While importing the product into the target, I get a warning -
<b>The target namespace for the special import already contains data for one or more export lines. Continuing this import may corrupt the state of your data.</b>
I am not sure what this means - should I go ahead and import my custom product and its SWCV ( the next step ) despite this warning ? Or am I missing any step ? I checked the weblog on the SLD preparation and did not see any additional steps other than export/import from the source/target SLDs
Thank you for your time in advance.Hi Karthik,
Check out this link
==>http://help.sap.com/saphelp_nw04s/helpdata/en/b2/0aae42e5adcd6ae10000000a155106/frameset.htm
Hope this will explain you all the steps in importing...:)
Regards,
Sundararamaprasad. -
Hi Experts,
Some questions that I hope someone can verify:
1. When we download a PAR file from Portal and import into NWDS, do references to JAR files not get imported? (for e.g. I see the Portal Logon component require adding of certain jar files)
2. What are the differences between the PAR files in the following path (downloaded via System admin>support>Portal Runtime>Browse ):
-ROOT/WEB-INF/deployment/temp
-ROOT/WEB-INF/portal/portalapps
Thanks,
ZMHi,
Whenever a PAR file is imported into the NWDS the JAR files will not be imported automatically.You need to copy it in the right location manually.
Regarding the second question , ROOT/WEB-INF/deployment/temp will have the complete PAR file (also I compared the size of logon PAR file)
-ROOT/WEB-INF/deployment/temp --356234
-ROOT/WEB-INF/portal/portalapps--4096
I guess the different path are for different necessity of the same portal application. While temp folder has the PAR file of the portal application, the portalapps might contain files and reference to launch the Portal application.
When you download from the portalapps folder you will not get the PAR file.
Any information on the second question are welcome..
Regards
Karthiheyan M -
Build Error While importing standard application into NWDS
Hi all,
I am trying to Import T&E Standard Applications into NWDS.
Two components (tra & tra/tre) have to be synched to the studio. These two are interdependent..
One Component I am able synch and create project perfectly but when i try to do the second one, i am getting Generation BUILD Error...
Help me in this regard..
Thanks
Malla
Edited by: challa mallareddy on May 7, 2009 12:34 PMHi,
As per your error, I think you have already created a project with name NewParProject. Give a different name and then check.
Also check if your par file is not corrupt. Download it again and follow below steps in NWDS :
Go to File>Import > Select par file >
>Browse and select the par file>
>Give a project name i.e. ParProjectTest > Finish.
This should work.
Regards
Deepak -
Error while Importing .TPZ File into ID
Hi Experts,
While Importing the .TPZ File Into Integration Directory , It's Saying that
<b>Business system INTEGRATION_SERVER_PNW is not assigned to a business system group with the ID (XISystemGroup)</b>
Please let me Know
Regards
KhannaHi,
First, you have to start the SLD.
To transport business systems you must first of all create business system groups, then associate the business systems with the group and finally map your business systems.
To create a group, proceed as follows:
> Business Systems
> Click on the drop-down next to Group and select Edit Groups
> Create a group for each environment (eg DEV, TST, PRD). Specify for each group which Integration Server is used.
> If the group XISystemGroup (I suspect that this group has been created before via the SLD Administration / Content Maintenance Tool, isn't it?) is already present, just Remove it.
To assign business systems to a group, proceed as follows:
> Business Systems (Group = all)
> Select your Business System
> Click on the Integration tab.
> Select the related Integration Server (which is associated with a group - see step 1)
To map your DEV Business Systems to TST Business Systems etc., proceed as follows:
> Business Systems
> Select the group of your choice
> Select your Business System
> Click on Transport
> Click on Add/Change Target
> Select the Target Group and System
KR, Danny De Roovere -
Getting error while importing CRDelta file into SLD
When we are applying SAP Note 669669 - Importing delta in SLD we are getting the below mentioned error message.
"The selected aggregate import is not applicable to the current version SAP_CR2.0 of the target namespace"
We are trying to import the zip file CRDelta1511_0-10004549.ZIP.
However we were successfully able to import the cimsap1511_0-10004549.zip into the SLD successfully.
We are doing this import activity (upgrading the SLD) as we are unable to locate the ESS related mandatory Software Component EP_BUILDT in the current SLD version.
Waiting for a quick response
Regards,
NarpalHello Sihag,
No matter what product version we choose it throws the same error.
But when I give Integration process(in the same software component where the integration scenario) for the application component and then creating it works.
Afterwards I removed the integration process from application system, and its not throwing any error when i check (F7) in Integration scenario.
907897 - Check this before you import
Before you upgrade to the model version 1.5, check which version is currently imported in the SLD Web UI (Administration -> Details). If the current version is lower than 1.4.30, import model 1.4.x (x must be 30 or higher) before updating to model version 1.5. You can find this version on SAP Service marketplace under SAP MASTER DATA FOR SLD 2.0, "SAP CIM model 1.4 Support Package 08". Version Support Package 18 already contains the data for the conversion to Version 1.5.
Do let me know if your problem is getting resolved.
Thank you.
Regards,
Manomeet
- Award points if helpful - -
Error while importing .tpz file into ESR..
Hi Gurus,
I am facing one problem.
I developed one interface in XI3.0 development server.
I imported the integration directory object into quality but when importing the ESR part it got imported successfully,.But was not visible in list.when I went to change list it , and tried to activate the SWCV it gives error.
In ID I had exported whole configuration scenario and in ESR I had exported Namespace.
But first time when I exported ESR part I had checked "inlcude deleted objects". but I again exported and tried importing the ESR namespace, this time without checking "included deleted objects"
Error I am getting while activating the SWCV:
Namespace cannot be deleted since the software component version still contains objects in namespace "http://Namespacename"
Delete the objects first Originality indicator for the software component version set later. Ensure that the software component version only contains one original repositor
How can I delete it when I can even see it?
please help.
ThanksHey guys, the issue got reolved.
I did "Reject change".
Actually , when I first imported the .tpz I could not see the namespace,and tried doing it again.
But when I did reject change the namespace came in the list. -
Error while importing .xml file in Datatype
Hi SDN,
I am getting this error while importing .xml file in Datatype.
Error when parsing the XML document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8
Actually I have created datatype in my development box..
but my client doesn't want to develop in development box.
so i have exported that datatype as xsd from datatype editor.
and while importing into sandbox datatype editor i am getting this error..
Any help please......Hi Rajeev,
now i have an .xml file its not importing into datatype...
error is
Error when parsing the XML document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8))
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema targetNamespace="http://abc.com/xa" xmlns="http://abc.com/xa" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="DT_PLANNINGSCHEDULE">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">3c6ae480f2f111dbc7ac0002556ad065</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="PlanningSchedule_Output">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">c65d41c0f15b11dbb29f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PlanningScheduleHeader">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">c65d41c1f15b11dbb6ef00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ScheduleID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">6c804600f15d11dbc02400123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleIssueDate" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d0f15d11db8dd800123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="SchedulePurpose">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d1f15d11dbac4100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Purpose">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd50f15e11db9eb600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PurposeCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd51f15e11dbc47a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ScheduleTypeCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d2f15d11dbbc3900123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleTypeCodedOther" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d3f15d11dba00200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="QuantityQualifierCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d4f15d11dbc7e000123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d5f15d11db969a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BuyerParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec100f16411dba2e900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec101f16411db997a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec102f16411dbb75900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec103f16411db8fa500123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec104f16411dba93f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec105f16411dba20f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">0de2f450f16511dbaa4700123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfIdentifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d0f16711dbbdd800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d1f16711dbcd2600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d2f16711db82f800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d3f16711dbcf6e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d4f16711dbcb6200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="SellerParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e0422b80f16711dba8c100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb80f16811db82e800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb81f16811dba6ab00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb82f16811db8b4e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb83f16811dbc0ff00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb84f16811dbb8f700123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb85f16811dba46200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfIdentifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb86f16811db98c000123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb87f16811dbb25200123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb88f16811dbc7d100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e99ffa30f16811dba27100123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d30f16a11dbb29f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ShipFromParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e0422b81f16711dbbfce00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d31f16a11db9adf00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d32f16a11dbbef100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d33f16a11db9e5600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d34f16a11dbba6d00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d35f16a11db855400123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d36f16a11db877300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ShipToParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e0422b82f16711db84ec00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac0f16b11dba49600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac1f16b11db80c700123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac2f16b11db8ea300123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac3f16b11dbb5bb00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac4f16b11dbb7bc00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac5f16b11db92a300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Language">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d6f15d11db9f9a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LanguageCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd52f15e11dbc06300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfLocationGroupedPlanningDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">c65d41c2f15b11dba9fd00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocationGroupedPlanningDetail" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">89515130f17f11db98e400123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Location">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">de832980f17f11db8d4600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocationIdentifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d0f18011db8ce800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d1f18011db839900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d2f18011dba45300123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d3f18011db9ac700123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d4f18011dbc4ab00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d5f18011dbcd4400123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfLocationPlanningItemDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">de832981f17f11db856100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocationPlanningItemDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257410f18111db8b6f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BasePlanningDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257411f18111db839c00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LineItemNum">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257412f18111db847f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BuyerLineItemNum" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257413f18111dbcf7200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ItemIdentifiers">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257414f18111dba6f100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartNumbers">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257415f18111db968700123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BuyerPartNumber">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257416f18111db9f9100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartNum">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257417f18111dbc32500123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257418f18111dbcfa900123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="StandardPartNumber">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">50b67960f18211db839c00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ProductIdentifierCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">50b67961f18211dbc78900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ProductIdentifierQualifierCoded" type="xsd:integer">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">50b67962f18211dbae6e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ProductIdentifier" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">83815570f18411dbb4e800123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ItemDescription" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">83815571f18411db876f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfItemReferences">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef0f18711dbbafe00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ListOfReferenceCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef1f18711db8a7600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ReferenceCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef2f18711db935200123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ReferenceTypeCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef3f18711dba69c00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ReferenceTypeCodedOther" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef4f18711db942b00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="PrimaryReference">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef5f18711db93a800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Reference">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef6f18711dbcebc00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="RefNum" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef7f18711dbce6300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ForecastFrequencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef8f18711db937b00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfScheduleDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef9f18711dba61400123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ScheduleDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefaf18711db9d4800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="CommitmentLevelCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefbf18711dba59800123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleDates">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefcf18711db947900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ListOfDateCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefdf18711dbc43e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="DateCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefef18711dbaa5000123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Date">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefff18711dbcde600123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="DateQualifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af00f18711db87f100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="DateQualifierCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af01f18711dbc9cf00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ScheduleQuantities">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af02f18711dbc24100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ListOfQuantityCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af03f18711db842900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="QuantityCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af04f18711dbb59400123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="QuantityValue" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af05f18711dba6d900123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="UnitOfMeasurement">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a87e2580f18711dbc66f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="UOMCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a87e2581f18711db89a000123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="QuantityQualifierCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a87e2582f18711db9a1500123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Maybe you are looking for
-
Cannot print to Canon iR-ADV C2020 after updated to Mavericks!!
Very bad user experience for OSX update. Found out cannot print anymore after I updated all 3 of my Macs....
-
Sending a formatted Excel sheet as an attachment in a mail.
Hi , I have been using following code to to send formatted excel sheet as attachment in email. in the below code I want to change the format of cell from Bold to Underline. I have replaced Bold with Underline for below code but it is not working can
-
ERROR: user is not configured for keystore 'service_ssl'
hi experts: System environment: pi7.0 j2ee sp09 ECC6.0 patch level11 Here is my scenarios.. ECC6.0-->(IDOC)XI(CIDX)-- >External system. External system-->(CIDX)XI(IDOC)-- >ECC6.0 1.we have got there certificates from external system (rootCA.DER,inte
-
Can Anyone Tell Me How To Fix This?
Hi everyone, can anyone tell me what this error means: Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException at Quiz.main(Quiz.java:22) I got this error when I tried to run a quiz program, I downloaded it from the internet to see how it
-
The wireless keyboard is not working with my iPad2. I turned on bluetooth and paired the device. What other hidden step is there to do?