Creating Datatype!
Hi All,
Can anyone help me in creating the Target Datatype in PI, based on the SOAP UI Code below
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:hris="http://trm.test.com/HRIS">
<soapenv:Header/>
<soapenv:Body>
<hris:Dispatch>
<!Optional:>
<hris:HRXML><![CDATA[<Envelope version="01.00">
<Sender>
<Id>HRXMLUSER</Id>
<Credential>11111</Credential>
</Sender>
<Recipient>
<Id />
</Recipient>
<TransactInfo transactType="data">
<TransactId>15747</TransactId>
<TimeStamp>2011-11-22 04:00 PM</TimeStamp>
</TransactInfo>
<Packet>
<PacketInfo packetType="data">
<PacketId>1</PacketId>
<Action>SET</Action>
<Manifest>JOBCODE_POSITIONDATA</Manifest>
</PacketInfo>
<Payload><?xml version="1.0"?>
<JOBCODE_POSITIONDATA language="EN" AutoFilerNotification="No">
<JOBCODE>01123</JOBCODE>
<JOBCODEDESC>ANALYST-CNTRCT MGT-II-NONC-SLR</JOBCODEDESC>
<JOBCODESTATUS>A</JOBCODESTATUS>
<JOBTITLE></JOBTITLE>
<PAYGRADEMANAGE></PAYGRADEMANAGE>
<PAYGRADEREP></PAYGRADEREP>
</JOBCODE_POSITIONDATA>
</Payload>
</Packet>
</Envelope>]]></hris:HRXML>
</hris:Dispatch>
</soapenv:Body>
</soapenv:Envelope>
If I take the entire message in SOAP UI and send it, I am getting a response back from my third party. Now the question I have is How to create the Target Datatype in XI to get a response from my third party??
Can you please help me with this issue.?
Thanks,
Harsh
Edited by: Moderator on Nov 29, 2011 4:02 PM
Karna,
Thank you very much for your reply. Sorry below is the code I pasted in SOAP UI which gives me a response
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:hris="http://trm.brassring.com/HRIS">
<soapenv:Header/>
<soapenv:Body>
<hris:Dispatch>
<!Optional:>
<hris:HRXML><![CDATA[<Envelope version="01.00">
<Sender>
<Id>HRXMLUSER</Id>
<Credential>25426</Credential>
</Sender>
<Recipient>
<Id />
</Recipient>
<TransactInfo transactType="data">
<TransactId>15747</TransactId>
<TimeStamp>2011-11-22 04:00 PM</TimeStamp>
</TransactInfo>
<Packet>
<PacketInfo packetType="data">
<PacketId>1</PacketId>
<Action>SET</Action>
<Manifest>WEENERGIES_JOBCODE_POSITIONDATA</Manifest>
</PacketInfo>
<Payload><?xml version="1.0"?>
<WEENERGIES_JOBCODE_POSITIONDATA language="EN" AutoFilerNotification="No">
<JOBCODE>01122</JOBCODE>
<JOBCODEDESC>ANALYST-CNTRCT MGT-II-NONC-SLR</JOBCODEDESC>
<JOBCODESTATUS>A</JOBCODESTATUS>
<JOBTITLE></JOBTITLE>
<PAYGRADEMANAGE></PAYGRADEMANAGE>
<PAYGRADEREP></PAYGRADEREP>
</WEENERGIES_JOBCODE_POSITIONDATA>
</Payload>
</Packet>
</Envelope>]]></hris:HRXML>
</hris:Dispatch>
</soapenv:Body>
</soapenv:Envelope>
And I will create my datatype as you said exactly. Now Can you see the "Payload" tag below. It has <, > for each field.
Can you help me how to create the Payload section in my Datatype in PI?
Sorry for the confusion.
Below is the response that I get in SOAP UI
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<DispatchResponse xmlns="http://trm.brassring.com/HRIS">
<DispatchResult><![CDATA[<?xml version="1.0" encoding="utf-8"?><Envelope version="01.00"><Sender><Id>HRXMLUSER</Id><Credential>25426</Credential></Sender><Recipient><Id></Id></Recipient><TransactInfo transactType="response"><TransactId>15747</TransactId><TimeStamp>2011-11-22 04:00 PM</TimeStamp><Status><Code>200</Code><ShortDescription>Success</ShortDescription><LongDescription>POSITIONDATA Data transfer was a success</LongDescription></Status></TransactInfo><Packet><PacketInfo packetType="response"><PacketId>1</PacketId><Action>SET</Action><Manifest>WEENERGIES_JOBCODE_POSITIONDATA</Manifest><Status><Code>200</Code><ShortDescription>Success</ShortDescription><LongDescription>POSITION Data transfer was a success</LongDescription></Status></PacketInfo><Payload /></Packet></Envelope>]]></DispatchResult>
</DispatchResponse>
</soap:Body>
</soap:Envelope>
Thanks,
Harsh
Edited by: HarshK on Nov 30, 2011 5:22 PM
Similar Messages
-
Import XSD to create datatypes
Hello Everybody-
I want to create a datatype that is specific for my outbound message,i have the xsd of that structure,i was trying to import the xsd to form a XI structure.Here is what i have done.
1.Right clicked datatypes and clicked on new
2.It asked me for a name and i gave a name "venkat".
3.Then from menu-tools, i clicked import xsd and selected my xsd. Then i got a message that Schema to be handled does not contain a definition of type venkat.
4.So what i did this time i gave the name as OrderRelease instead of venkat(as stated in step 2) and still i get the error.
I am pasting a snippet of my xsd.
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="OrderRelease">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="MergeNode" minOccurs="0" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ShipNodePersonInfo" minOccurs="0">
<xsd:complexType>
<xsd:attribute name="Suffix" type="xsd:string"/>hi,
1. you need to import it as an external definition
2. you need to close the tags
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="OrderRelease">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="MergeNode" minOccurs="0" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ShipNodePersonInfo" minOccurs="0">
<xsd:complexType>
<xsd:attribute name="Suffix" type="xsd:string"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a> -
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> -
Hi,
do you know if I can change the format of the Date and Time (i.e from yyyy/mm/dd to yyyymmdd) when creating DataType? I know that I can do it in the mapping but I'm not gonna make any mapping for this so that's why I want to do it in DataType.
Maybe in the detail column in "pattern" or "enumeration"?
Thanks> when I choose Type: Decimal. Do I put the total of the lenght in Totaldigits and the number of decimals in FractionDigits?
Can you elaborate your question with example. If you are thinking by mentioning the type and length in Data type then in any case it will not work. You have to use mapping for doing formatting.
Otherwise just using the Data Type as "String" will take care of everything. Eg. if your value comes like 1234.99 then it will be taken care by type string. -
Datatype creation error (namespace error)
Hello everybody,
while creating datatype, i am getting an error like
"namespace is not defined in the SWCV "
I have created my own software product and component.
Can anyone tell me the reason why i am getting this error and how to go about it?Yes, As soon you create a NameSpace you have to activate it. Other if you active the namespace after creating Data Types or message types or other objects. system gives some time error.
So active a namespace as soon you create it.
Regards
Shankar -
Error while installing the named instance SQL 2012 Sp1
Hi,
I am getting below error while installing the named instance with features Data base engine. on same server box 2 named instance already installed and working...please suggest. i have done a lot of troubleshooting..(configure local system for Db engines
during installation, tried to install after another domain ID., repair and uninstalled existing and retried.) .. please s if i need to do anything else to resolve the issue.. installation account is domain admin account...
Can i rename the installation domain account profile from sql server that used for 2 named instance and for 3 rd named instance i am trying... is any impact after profile rename from the local sql server on any instance already configured...
Shailendra Devthanks alberto.
here is
2015-03-24 19:48:49.42 Server Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64)
Oct 19 2012 13:38:57
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
2015-03-24 19:48:49.42 Server (c) Microsoft Corporation.
2015-03-24 19:48:49.42 Server All rights reserved.
2015-03-24 19:48:49.42 Server Server process ID is 3460.
2015-03-24 19:48:49.42 Server System Manufacturer: 'Xen', System Model: 'HVM domU'.
2015-03-24 19:48:49.42 Server Authentication mode is WINDOWS-ONLY.
2015-03-24 19:48:49.42 Server Logging SQL Server messages in file 'D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\Log\ERRORLOG'.
2015-03-24 19:48:49.42 Server The service account is 'AIRWORKS\scadmin'. This is an informational message; no user action is required.
2015-03-24 19:48:49.42 Server Registry startup parameters:
-d D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\DATA\master.mdf
-e D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\Log\ERRORLOG
-l D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\DATA\mastlog.ldf
2015-03-24 19:48:49.42 Server Command Line Startup Parameters:
-s "SCSMDB"
-m "SqlSetup"
-T 4022
-T 4010
-T 1905
-T 3701
-T 8015
2015-03-24 19:48:49.69 Server SQL Server detected 1 sockets with 1 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2015-03-24 19:48:49.69 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-03-24 19:48:49.69 Server Detected 15624 MB of RAM. This is an informational message; no user action is required.
2015-03-24 19:48:49.69 Server Using conventional memory in the memory manager.
2015-03-24 19:48:49.98 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2015-03-24 19:48:50.01 Server This instance of SQL Server last reported using a process ID of 5124 at 3/24/2015 7:48:48 PM (local) 3/24/2015 2:18:48 PM (UTC). This is an informational message only; no user action is required.
2015-03-24 19:48:50.03 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2015-03-24 19:48:50.07 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2015-03-24 19:48:50.30 Server Database Mirroring Transport is disabled in the endpoint configuration.
2015-03-24 19:48:50.58 spid5s Warning ******************
2015-03-24 19:48:50.65 spid5s SQL Server started in single-user mode. This an informational message only. No user action is required.
2015-03-24 19:48:50.66 spid5s Starting up database 'master'.
2015-03-24 19:48:50.90 spid5s 9 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2015-03-24 19:48:51.04 Server CLR version v4.0.30319 loaded.
2015-03-24 19:48:51.17 spid5s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2015-03-24 19:48:51.17 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2015-03-24 19:48:51.39 Server Software Usage Metrics is enabled.
2015-03-24 19:48:51.81 spid5s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-03-24 19:48:51.83 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-03-24 19:48:51.86 spid5s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-03-24 19:48:52.02 spid5s SQL Trace ID 1 was started by login "sa".
2015-03-24 19:48:52.16 spid5s Server name is 'AWISCDB\SCSMDB'. This is an informational message only. No user action is required.
2015-03-24 19:48:52.35 spid12s The certificate [Cert Hash(sha1) "151C8B90A9A8AF12F5EFAE3439F691E2C01A7355"] was successfully loaded for encryption.
2015-03-24 19:48:52.35 spid12s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SCSMDB ].
2015-03-24 19:48:52.40 spid12s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806.
This is an informational message only. No user action is required.
2015-03-24 19:48:52.43 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Windows return code: 0x490, state: 16. Failure to register a SPN might cause integrated
authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2015-03-24 19:48:52.45 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational
message. No user action is required.
2015-03-24 19:48:54.03 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/AWISCDB.AIRWORKS.IN:SCSMDB ] for the SQL Server service.
2015-03-24 19:48:54.03 spid14s A new instance of the full-text filter daemon host process has been successfully started.
2015-03-24 19:48:54.86 spid6s Starting up database 'mssqlsystemresource'.
2015-03-24 19:48:54.86 spid5s Starting up database 'msdb'.
2015-03-24 19:48:54.87 spid6s The resource database build version is 11.00.3000. This is an informational message only. No user action is required.
2015-03-24 19:48:55.21 spid5s 12 transactions rolled forward in database 'msdb' (4:0). This is an informational message only. No user action is required.
2015-03-24 19:48:55.32 spid5s 0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
2015-03-24 19:48:55.32 spid6s Starting up database 'model'.
2015-03-24 19:48:55.32 spid5s Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
2015-03-24 19:48:55.72 spid6s Clearing tempdb database.
2015-03-24 19:48:57.22 spid6s Starting up database 'tempdb'.
2015-03-24 19:48:59.04 spid5s Database 'master' is upgrading script 'msdb110_upgrade.sql' from level 184551476 to level 184552376.
2015-03-24 19:48:59.04 spid5s ----------------------------------
2015-03-24 19:48:59.04 spid5s Starting execution of PRE_MSDB.SQL
2015-03-24 19:48:59.04 spid5s ----------------------------------
2015-03-24 19:49:00.23 spid5s Setting database option COMPATIBILITY_LEVEL to 100 for database 'msdb'.
2015-03-24 19:49:00.57 spid5s -----------------------------------------
2015-03-24 19:49:00.57 spid5s Starting execution of PRE_SQLAGENT100.SQL
2015-03-24 19:49:00.57 spid5s -----------------------------------------
2015-03-24 19:49:00.61 spid5s Setting database option COMPATIBILITY_LEVEL to 110 for database 'msdb'.
2015-03-24 19:49:00.73 spid5s Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install.
2015-03-24 19:49:00.73 spid5s Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install.
2015-03-24 19:49:01.78 spid5s Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2015-03-24 19:49:01.79 spid5s Using 'xpstar.dll' version '2011.110.3000' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2015-03-24 19:49:01.80 spid5s DBCC TRACEOFF 1717, server process ID (SPID) 5. This is an informational message only; no user action is required.
2015-03-24 19:49:01.80 spid5s DBCC execution completed. If DBCC printed error messages, contact your system administrator.
2015-03-24 19:49:01.81 spid5s
2015-03-24 19:49:01.81 spid5s Creating table temp_sysjobschedules
2015-03-24 19:49:01.91 spid5s
2015-03-24 19:49:01.91 spid5s Alter table sysdownloadlist...
2015-03-24 19:49:01.92 spid5s
2015-03-24 19:49:01.92 spid5s Alter table sysjobhistory...
2015-03-24 19:49:01.92 spid5s
2015-03-24 19:49:01.92 spid5s Alter table systargetservers...
2015-03-24 19:49:01.92 spid5s
2015-03-24 19:49:01.92 spid5s Alter table sysjobsteps...
2015-03-24 19:49:01.99 spid5s Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
2015-03-24 19:49:01.99 spid5s Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
2015-03-24 19:49:01.99 spid5s
2015-03-24 19:49:01.99 spid5s -----------------------------------------
2015-03-24 19:49:01.99 spid5s Execution of PRE_SQLAGENT100.SQL complete
2015-03-24 19:49:01.99 spid5s -----------------------------------------
2015-03-24 19:49:02.01 spid5s DMF pre-upgrade steps...
2015-03-24 19:49:02.13 spid5s DC pre-upgrade steps...
2015-03-24 19:49:02.13 spid5s Check if Data collector config table exists...
2015-03-24 19:49:02.13 spid5s Data Collector state before upgrade: 0
2015-03-24 19:49:02.13 spid5s pre_dc100::Check if syscollector_collection_sets_internal table exists...
2015-03-24 19:49:02.13 spid5s pre_dc100::Capturing Collection set status in temp table...
2015-03-24 19:49:02.19 spid5s Deleting cached auto-generated T-SQL Data Collection packages from msdb...
2015-03-24 19:49:02.19 spid5s End of DC pre-upgrade steps.
2015-03-24 19:49:02.19 spid5s DAC pre-upgrade steps...
2015-03-24 19:49:02.19 spid5s Starting DAC pre-upgrade steps ...
2015-03-24 19:49:02.19 spid5s End of DAC pre-upgrade steps.
2015-03-24 19:49:02.19 spid5s ----------------------------------
2015-03-24 19:49:02.19 spid5s Starting execution of MSDB.SQL
2015-03-24 19:49:02.19 spid5s ----------------------------------
2015-03-24 19:49:02.23 spid5s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-03-24 19:49:02.23 spid5s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-03-24 19:49:02.27 spid5s Checking the size of MSDB...
2015-03-24 19:49:02.53 spid5s
2015-03-24 19:49:02.53 spid5s Setting database option TRUSTWORTHY to ON for database 'msdb'.
2015-03-24 19:49:02.53 spid5s Setting database option RECOVERY to SIMPLE for database 'msdb'.
2015-03-24 19:49:02.64 spid5s ----------------------------------
2015-03-24 19:49:02.64 spid5s Finished execution of MSDB.SQL
2015-03-24 19:49:02.64 spid5s ----------------------------------
2015-03-24 19:49:02.64 spid5s -----------------------------------------
2015-03-24 19:49:02.64 spid5s Starting execution of MSDB_VERSIONING.SQL
2015-03-24 19:49:02.64 spid5s -----------------------------------------
2015-03-24 19:49:02.64 spid5s -----------------------------------------
2015-03-24 19:49:02.64 spid5s Finished execution of MSDB_VERSIONING.SQL
2015-03-24 19:49:02.64 spid5s -----------------------------------------
2015-03-24 19:49:02.64 spid5s Dropping view MSdatatype_mappings...
2015-03-24 19:49:02.65 spid5s Dropping view sysdatatypemappings...
2015-03-24 19:49:02.65 spid5s Dropping table MSdbms_datatype_mapping...
2015-03-24 19:49:02.66 spid5s Dropping table MSdbms_map...
2015-03-24 19:49:02.67 spid5s Dropping table MSdbms_datatype...
2015-03-24 19:49:02.67 spid5s Dropping table MSdbms...
2015-03-24 19:49:02.73 spid5s Creating table MSdbms
2015-03-24 19:49:02.75 spid5s Creating table MSdbms_datatype
2015-03-24 19:49:03.01 spid5s Creating table MSdbms_map
2015-03-24 19:49:03.02 spid5s Creating table MSdbms_datatype_mapping
2015-03-24 19:49:03.03 spid5s Definining default datatype mappings
2015-03-24 19:49:03.04 spid5s Creating datatype mappings for MSSQLSERVER to ORACLE8
2015-03-24 19:49:03.21 spid5s Creating datatype mappings for MSSQLSERVER to ORACLE9
2015-03-24 19:49:03.29 spid5s Creating datatype mappings for MSSQLSERVER to ORACLE10
2015-03-24 19:49:03.37 spid5s Creating datatype mappings for MSSQLSERVER to ORACLE11
2015-03-24 19:49:03.46 spid5s Creating datatype mappings for MSSQLSERVER to DB2
2015-03-24 19:49:03.54 spid5s Creating datatype mappings for MSSQLSERVER to SYBASE
2015-03-24 19:49:03.62 spid5s Creating datatype mappings for ORACLE8 to MSSQLSERVER
2015-03-24 19:49:03.71 spid5s Creating datatype mappings for ORACLE9 to MSSQLSERVER
2015-03-24 19:49:03.83 spid5s Creating datatype mappings for ORACLE10 to MSSQLServer
2015-03-24 19:49:03.95 spid5s Creating datatype mappings for ORACLE11 to MSSQLServer
2015-03-24 19:49:04.08 spid5s Creating view MSdatatype_mappings
2015-03-24 19:49:04.08 spid5s Creating view sysdatatypemappings
2015-03-24 19:49:05.08 spid5s
2015-03-24 19:49:05.08 spid5s Creating table syssubsystems...
2015-03-24 19:49:05.09 spid5s
2015-03-24 19:49:05.09 spid5s Creating view sysproxyloginsubsystem_view...
2015-03-24 19:49:05.11 spid5s
2015-03-24 19:49:05.11 spid5s Creating trigger trig_sysoriginatingservers_delete...
2015-03-24 19:49:05.11 spid5s
2015-03-24 19:49:05.11 spid5s Creating view sysoriginatingservers_view...
2015-03-24 19:49:05.12 spid5s
2015-03-24 19:49:05.12 spid5s Creating trigger trig_sysjobs_insert_update...
2015-03-24 19:49:05.13 spid5s
2015-03-24 19:49:05.13 spid5s Creating view sysjobs_view...
2015-03-24 19:49:05.15 spid5s
2015-03-24 19:49:05.15 spid5s Creating trigger trig_sysschedules_insert_update...
2015-03-24 19:49:05.16 spid5s
2015-03-24 19:49:05.16 spid5s Creating view sysschedules_localserver_view...
2015-03-24 19:49:05.21 spid5s
2015-03-24 19:49:05.21 spid5s Creating view systargetservers_view...
2015-03-24 19:49:05.23 spid5s
2015-03-24 19:49:05.23 spid5s Creating view sysalerts_performance_counters_view...
2015-03-24 19:49:05.25 spid5s
2015-03-24 19:49:05.25 spid5s Creating function SQLAGENT_SUSER_SNAME ...
2015-03-24 19:49:05.25 spid5s
2015-03-24 19:49:05.25 spid5s Creating function SQLAGENT_SUSER_SID ...
2015-03-24 19:49:05.26 spid5s
2015-03-24 19:49:05.26 spid5s Creating procedure SP_SQLAGENT_IS_SRVROLEMEMBER...
2015-03-24 19:49:05.27 spid5s
2015-03-24 19:49:05.27 spid5s Creating procedure sp_verify_category_identifiers...
2015-03-24 19:49:05.27 spid5s
2015-03-24 19:49:05.27 spid5s Creating function agent_datetime...
2015-03-24 19:49:05.27 spid5s
2015-03-24 19:49:05.27 spid5s Creating procedure sp_verify_proxy_identifiers...
2015-03-24 19:49:05.28 spid5s
2015-03-24 19:49:05.28 spid5s Creating procedure sp_verify_credential_identifiers...
2015-03-24 19:49:05.29 spid5s
2015-03-24 19:49:05.29 spid5s Creating procedure sp_verify_subsystems...
2015-03-24 19:49:05.30 spid5s
2015-03-24 19:49:05.30 spid5s Creating procedure sp_verify_subsystem_identifiers...
2015-03-24 19:49:05.30 spid5s
2015-03-24 19:49:05.30 spid5s Creating procedure sp_verify_login_identifiers...
2015-03-24 19:49:05.31 spid5s
2015-03-24 19:49:05.31 spid5s Creating procedure sp_verify_proxy...
2015-03-24 19:49:05.31 spid5s
2015-03-24 19:49:05.31 spid5s Creating procedure sp_add_proxy...
2015-03-24 19:49:05.32 spid5s
2015-03-24 19:49:05.32 spid5s Creating procedure sp_delete_proxy...
2015-03-24 19:49:05.32 spid5s
2015-03-24 19:49:05.32 spid5s Creating procedure sp_update_proxy...
2015-03-24 19:49:05.33 spid5s
2015-03-24 19:49:05.33 spid5s Creating procedure sp_sqlagent_is_member...
2015-03-24 19:49:05.33 spid5s
2015-03-24 19:49:05.33 spid5s Creating procedure sp_verify_proxy_permissions...
2015-03-24 19:49:05.34 spid5s
2015-03-24 19:49:05.34 spid5s Creating procedure sp_help_proxy...
2015-03-24 19:49:05.35 spid5s
2015-03-24 19:49:05.35 spid5s Creating procedure sp_get_proxy_properties...
2015-03-24 19:49:05.36 spid5s
2015-03-24 19:49:05.36 spid5s Creating procedure sp_grant_proxy_to_subsystem...
2015-03-24 19:49:05.36 spid5s
2015-03-24 19:49:05.36 spid5s Creating procedure sp_grant_login_to_proxy...
2015-03-24 19:49:05.37 spid5s
2015-03-24 19:49:05.37 spid5s Creating procedure sp_revoke_login_from_proxy...
2015-03-24 19:49:05.37 spid5s
2015-03-24 19:49:05.37 spid5s Creating procedure sp_revoke_proxy_from_subsystem...
2015-03-24 19:49:05.38 spid5s
2015-03-24 19:49:05.38 spid5s Creating procedure sp_enum_proxy_for_subsystem...
2015-03-24 19:49:05.38 spid5s
2015-03-24 19:49:05.38 spid5s Creating procedure sp_enum_login_for_proxy...
2015-03-24 19:49:05.39 spid5s
2015-03-24 19:49:05.39 spid5s Creating procedure sp_reassign_proxy...
2015-03-24 19:49:05.40 spid5s
2015-03-24 19:49:05.40 spid5s Creating procedure sp_sqlagent_get_startup_info...
2015-03-24 19:49:05.41 spid5s
2015-03-24 19:49:05.41 spid5s Creating procedure sp_sqlagent_update_agent_xps...
2015-03-24 19:49:05.42 spid5s
2015-03-24 19:49:05.42 spid5s Creating procedure sp_sqlagent_has_server_access...
2015-03-24 19:49:05.45 spid5s
2015-03-24 19:49:05.45 spid5s Creating procedure sp_sqlagent_get_perf_counters...
2015-03-24 19:49:05.46 spid5s
2015-03-24 19:49:05.46 spid5s Creating procedure sp_sqlagent_notify...
2015-03-24 19:49:05.47 spid5s
2015-03-24 19:49:05.47 spid5s Creating procedure sp_is_sqlagent_starting...
2015-03-24 19:49:05.47 spid5s
2015-03-24 19:49:05.47 spid5s Creating procedure sp_verify_job_identifiers...
2015-03-24 19:49:05.48 spid5s
2015-03-24 19:49:05.48 spid5s Creating procedure sp_verify_schedule_identifiers...
2015-03-24 19:49:05.49 spid5s
2015-03-24 19:49:05.49 spid5s Creating procedure sp_verify_jobproc_caller...
2015-03-24 19:49:05.50 spid5s
2015-03-24 19:49:05.50 spid5s Creating procedure sp_downloaded_row_limiter...
2015-03-24 19:49:05.51 spid5s
2015-03-24 19:49:05.51 spid5s Creating procedure sp_post_msx_operation...
2015-03-24 19:49:05.54 spid5s
2015-03-24 19:49:05.54 spid5s Creating procedure sp_verify_performance_condition...
2015-03-24 19:49:05.58 spid5s
2015-03-24 19:49:05.58 spid5s Creating procedure sp_verify_job_date...
2015-03-24 19:49:05.59 spid5s
2015-03-24 19:49:05.59 spid5s Creating procedure sp_verify_job_time...
2015-03-24 19:49:05.61 spid5s
2015-03-24 19:49:05.61 spid5s Creating procedure sp_verify_alert...
2015-03-24 19:49:05.62 spid5s
2015-03-24 19:49:05.62 spid5s Creating procedure sp_update_alert...
2015-03-24 19:49:05.63 spid5s
2015-03-24 19:49:05.63 spid5s Creating procedure sp_delete_job_references...
2015-03-24 19:49:05.65 spid5s
2015-03-24 19:49:05.65 spid5s Creating procedure sp_delete_all_msx_jobs...
2015-03-24 19:49:05.66 spid5s
2015-03-24 19:49:05.66 spid5s Creating procedure sp_generate_target_server_job_assignment_sql...
2015-03-24 19:49:05.66 spid5s
2015-03-24 19:49:05.66 spid5s Creating procedure sp_generate_server_description...
2015-03-24 19:49:05.67 spid5s
2015-03-24 19:49:05.67 spid5s Creating procedure sp_msx_set_account...
2015-03-24 19:49:05.68 spid5s
2015-03-24 19:49:05.68 spid5s Creating procedure sp_msx_get_account...
2015-03-24 19:49:05.69 spid5s
2015-03-24 19:49:05.69 spid5s Creating procedure sp_delete_operator...
2015-03-24 19:49:05.70 spid5s
2015-03-24 19:49:05.70 spid5s Creating procedure sp_msx_defect...
2015-03-24 19:49:05.71 spid5s
2015-03-24 19:49:05.71 spid5s Creating procedure sp_msx_enlist...
2015-03-24 19:49:05.72 spid5s
2015-03-24 19:49:05.72 spid5s Creating procedure sp_delete_targetserver...
2015-03-24 19:49:05.73 spid5s
2015-03-24 19:49:05.73 spid5s Creating procedure sp_enlist_tsx
2015-03-24 19:49:05.74 spid5s
2015-03-24 19:49:05.74 spid5s Creating procedure sp_get_sqlagent_properties...
2015-03-24 19:49:05.76 spid5s
2015-03-24 19:49:05.76 spid5s Create procedure sp_set_sqlagent_properties...
2015-03-24 19:49:05.76 spid5s
2015-03-24 19:49:05.76 spid5s Creating procedure sp_add_targetservergroup...
2015-03-24 19:49:05.77 spid5s
2015-03-24 19:49:05.77 spid5s Creating procedure sp_update_targetservergroup...
2015-03-24 19:49:05.78 spid5s
2015-03-24 19:49:05.78 spid5s Creating procedure sp_delete_targetservergroup...
2015-03-24 19:49:05.78 spid5s
2015-03-24 19:49:05.78 spid5s Creating procedure sp_help_targetservergroup...
2015-03-24 19:49:05.79 spid5s
2015-03-24 19:49:05.79 spid5s Creating procedure sp_add_targetsvgrp_member...
2015-03-24 19:49:05.80 spid5s
2015-03-24 19:49:05.80 spid5s Creating procedure sp_delete_targetsvrgrp_member...
2015-03-24 19:49:05.81 spid5s
2015-03-24 19:49:05.81 spid5s Creating procedure sp_verify_category...
2015-03-24 19:49:05.81 spid5s
2015-03-24 19:49:05.81 spid5s Creating procedure sp_add_category...
2015-03-24 19:49:05.82 spid5s
2015-03-24 19:49:05.82 spid5s Creating procedure sp_update_category...
2015-03-24 19:49:05.83 spid5s
2015-03-24 19:49:05.83 spid5s Creating procedure sp_delete_category...
2015-03-24 19:49:05.83 spid5s
2015-03-24 19:49:05.84 spid5s Creating procedure sp_help_category...
2015-03-24 19:49:05.84 spid5s
2015-03-24 19:49:05.84 spid5s Creating procedure sp_help_targetserver...
2015-03-24 19:49:05.85 spid5s
2015-03-24 19:49:05.85 spid5s Creating procedure sp_resync_targetserver...
2015-03-24 19:49:06.06 spid5s
2015-03-24 19:49:06.06 spid5s Creating procedure sp_purge_jobhistory...
2015-03-24 19:49:06.09 spid5s
2015-03-24 19:49:06.09 spid5s Creating procedure sp_help_jobhistory...
2015-03-24 19:49:06.10 spid5s
2015-03-24 19:49:06.10 spid5s Creating procedure sp_add_jobserver...
2015-03-24 19:49:06.11 spid5s
2015-03-24 19:49:06.11 spid5s Creating procedure sp_delete_jobserver...
2015-03-24 19:49:06.11 spid5s Error: 10011, Severity: 16, State: 1.
2015-03-24 19:49:06.11 spid5s Access denied.
2015-03-24 19:49:06.11 spid5s Error: 917, Severity: 15, State: 1.
2015-03-24 19:49:06.11 spid5s An upgrade script batch failed to execute for database 'master' due to compilation error. Check the previous error message for the line which caused compilation to fail.
2015-03-24 19:49:06.11 spid5s Error: 912, Severity: 21, State: 2.
2015-03-24 19:49:06.11 spid5s Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 917, state 1, severity 15. This is a serious error condition which might interfere with regular
operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective
actions and re-start the database so that the script upgrade steps run to completion.
2015-03-24 19:49:06.11 spid5s Error: 3417, Severity: 21, State: 3.
2015-03-24 19:49:06.11 spid5s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books
Online.
2015-03-24 19:49:06.12 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2015-03-24 19:49:06.50 spid12s The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/AWISCDB.AIRWORKS.IN:SCSMDB ] for the SQL Server service.
Shailendra Dev -
File to SOAP scenario in PI 7.1
Hi
I am developing file to SOAP in 7.1 version and have the web service Url to call, Do I need upload the WSDL file of the SOAP into ESR under the external objects
Please let me know
Thank
PRHi,
it is not mandatory to upload the WSDLs of your webservice. You can create similar structure and call your webservice . But, using the WSDLs imported in your ESR you can save time spent in creating datatypes and message types. Even if you import WSDL under external definition, you need to create your service interfaces using WSDL.
Regards,
Reyaz -
Error in Soap_RFC_File scenario
Hi Experts,
I have done sceanrio like Soap to RFC to File with BPM.
The input will be taken by RFC. the response of RFC will be checked. If the response contains the feild available quantity material, then based on the response of bapi ,i calculated the cost of the material.For this
I have created
DataTypes:2 datatypes input and output
Message Types: 2 message types input and output
MessageInterfaces: 7 (input_mi,input_abs_mi,output_mi,output_abs_mi,bapi_sync_abs,bapi_req_abs,bapi_res_abs_
Mesage mapping:2 (Request and response)
interface mapping: 2 (bapi mapping and cost mapping)
and one integration process.
while generating the wsdl file in ID, i am giving the sender interface as input_mi (outbound,Asynchronous)and generated the wsdl file. while executing the sceanrio, i am getting the following below error.
Could please suggest what is the problem?
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">SYNCHONOUS_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>The process does not support the given synchronous interface or does not support synchronous messages Exception CX_WAPI_DEF_PROPERTY_NOT_FOUND occurred (program: SAPMHTTP, include: , line: 0).</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Thanks
LeelaHi Leela,
How did u get it solved.i hav same scenario and same error. -
Data Type creation in PI 7.1
Hi,
I have createda data type of Classification - "Aggreageted Type" , structure is as follows : -
GoodsMvmt_Enhance Complex Type l
COMMODITY_ITEM_NO Element xsd:string 1 false
OBLIGATION_ID Element xsd:string 1 false
REFERENCE_MATERIAL Element xsd:string 1 false
DEST_PLANT Element xsd:string 1 false
DEST_SLOC Element xsd:string 1 false
WEIGHTS_GRADES_ID Element xsd:string 1 false
while activating it , it gives me error -
Use of an XSD type in element COMMODITY_ITEM_NO is not permitted when modeling an aggregated type
Use of an XSD type in element OBLIGATION_ID is not permitted when modeling an aggregated type
Use of an XSD type in element REFERENCE_MATERIAL is not permitted when modeling an aggregated type
Use of an XSD type in element DEST_PLANT is not permitted when modeling an aggregated type
Use of an XSD type in element DEST_SLOC is not permitted when modeling an aggregated type
Use of an XSD type in element WEIGHTS_GRADES_ID is not permitted when modeling an aggregated type
Any idea how I can use XSD type rather creating datatype for every field ?
Note : If I change the Classification - "Freely Modelled Type" , it gives error while activatin that it has to ve aggreagated type.
Regards,
PranshuAny idea how I can use XSD type rather creating datatype for every field ?
You mean to say you used xsd:string while creating Aggregated Dataype?
If yes, then please note that Aggregated DT cannot refer any of the xsd elements......it can either refer an Aggregated DT or a Core DT....even if you make use of the Input help (under the Type column) it wont show you XSD Type option.....di you create an XSD outside and then imported it into the DT?
For more clarification/ examples refer --> ESR --> SAP BASIS --> SAP BASIS 7.10 --> http://sap.com/xi/BASIS/Global --> Aggregated DT.......none of the example is using xsd element....it is against the definition of this DT.
Regards,
Abhishek. -
How to configure the Http sender adapter
Now i have look through the sap lib about the http sender adapter
and i know the url is
http://hostname:port/path?namespace=<...>
&interface=<...>&service=<...>&cmd=T&loaderXML=< message object >&end=yes
My questions are:
1)the path in the URL is "/sap/xi/adapter_plain", if not, what is it?
2)the message payload is right?
any reply is appreciated
Thank you very muchHi Leo,
For a HHTP Scenario:
DESIGN:
1. Create DataTypes for source and Destinations. Create elements for all the text fields of your HTTP Client so that they can all be mapped into the destination file
2. Create MessageTypes for the two datatypes.
3. Create Message Interfaces. The One for HTTP is the sender, Asynchronous ( as no response is expected) and one for File is receiver, asynchronous.
4. Do the mapping. It will be mostly a one to one mapping of the fields.
5. Create the Interface Mapping.
Configuration:
1. Import your Business System under your Configuration Scenario.
2. Create 2 communication channels. One for Http as a sender and one for your receiver say IDoc.
Check these links for the configuration part.
http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
3. Do the Receiver Agreement for Idoc. HTTP doesnt need a sender agreement.
4. DO the Receiver Determination and Interface Determination.
Weblog which talk about the same scenario:-
/people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi - although this weblog is
aimed at explaining the sync-async bridge.. Sriram has taken http-to-file scenario as the example
(use case) and explained it...
Check this SDN tv demo, it has detail of HTTP adapter setup.
https://media.sdn.sap.com/SDNTV/main.asp?mediaId=107
Refer to this link for adapter settings.
http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
You should also have a HTTP client to send message to XI. In the connecting parameters to XI u have to use the URL in the pattern mentioned . U have to give all the configuration details in the URL.
If you give me your mail id or if you can mail me at [email protected], i can send you a HTTP CLIENT.....In which you need to view the source code and change the username and password to send message to XI.
Regards,
Abhy -
Synchronus file to jdbc Adapter configuration.
Hi ,
I want to configure for Synchronus File to Jdbc Adapter.
Can anyone tell me how to do it.
hemantHi,
In this case you would definitely need one file sender and one jdbc receiver adapter.
Create data taype and message type for file sender ,then create message interface for this message type.
Then create datatype for receiver i.e. jdbc.
For jdbc receiver there is one standard format as below:
<root>
<StatementName1>
<dbTableName action=UPDATE | UPDATE_INSERT>
<table>realDbTableName</table>
<access>
<col1>val1</col1>
<col2>val2new</col2>
</access>
<key1>
<col2>val2old</col2>
<col4>val4</col4>
</key1>
</dbTableName>
</StatementName1>
Then create message type and message interface for this message type.This interface will be inbound and synchronous.
Map your file message to jdbc receiver message.
Then map interfaces.
In ID create configuration scenario,assign file sending and jdbc receiver business system to this scenario.
Then create file sender and jdbc receiver communication channel.Create receiver determination,sender agreement and receiver agreement.
But if you want file synchronous scenario then,you need to use BPM for this.
Thanks. -
HTTP POST from ECC 6.0 to XI
On ECC 6.0, I have an XMLstring that I need to post to an external URL. I need this to go through XI. It is actually an HTTPS post. How can this be accomplished? Can anyone point me in the right direction as far as how this would work in XI? Here is a smippet of code on ECC
CALL METHOD cl_http_client=>create
EXPORTING
host = POST_HOST
service = '443'
scheme = '2'
ssl_id = 'ANONYM'
proxy_host = wf_proxy
proxy_service = wf_port
IMPORTING
client = http_client.
http_client->propertytype_logon_popup = http_client->co_disabled.
wf_user = '' .
wf_password = '' .
proxy server authentication
CALL METHOD http_client->authenticate
EXPORTING
proxy_authentication = 'X'
username = wf_user
password = wf_password.
CALL METHOD http_client->request->set_header_field
EXPORTING
name = '~request_method'
value = 'POST'.
CALL METHOD http_client->request->set_header_field
EXPORTING
name = '~request_protocol'
value = 'HTTPS/1.0'.
CALL METHOD http_client->request->set_header_field
EXPORTING
name = 'HOST'
value = POST_HOST.
CALL METHOD http_client->request->set_header_field
EXPORTING
name = '~request_uri'
value = L_POST_URI.
CALL METHOD http_client->request->set_header_field
EXPORTING
name = 'Content-Type'
value = 'text/xml; charset=utf-8'.
CALL METHOD http_client->request->set_header_field
EXPORTING
name = 'Content-Length'
value = txlen.Hi Tony,
You need to go through multiple steps.
1) Creation of Scenario in XI ( Integration Repository)
First create datatype which will represent the data that is to be passed to URL. Then message type, message interface, message mapping, Interface mapping.
2) Creation of Directory scenario ( Integration Directory)
Need to create Communication channel using either SOAP adapter or HTTP adapter as you need to pass the data to url.
3) Proxy:
Once you create first step then structure will be available in proxy ( SPROXY transaction) . There you will need to call method for outbound proxy.
For above mentioned steps you can search in SDN which will guide you to multiple helping thread. -
hi
i want to work send the data from mail to rfc...how can i do it...
whether i want to create datatype and mapping is needed...plz give me the step by step process of it...
thx in advance...Hi PP,
You may use the predefined external definition for your sender mail. Do a search in SDN or you can download in service market place.
Then you import your RFC and then you need to do mapping.
Regards,
---Satish -
can some clear me the message mapping posted in the blog by pooja pandey
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
i didn't get message mapping done with idoc on sender side and what is on the other side?
this is wat mentioned by pooja pandey:
Create three Message Mapping to convert Outbound type of IDOC into Abstract type so that we can collect it in our BPM. Message Mapping for conversion of three different types of IDOCs to their Abstract type are as follows:
MM_ISU_UKGAS_NOM1_to_NOM1_ABS
(ii) MM_ISU_UKGAS_NOM2_to_NOM2_ABS
(iii) MM_ISU_UKGAS_NOM3_to_NOM3_ABS
Below mapping is for N:1 transformation. (Here input will be having three different types of Abstract IDOCs and target will be having Abstract Target File type)
(iv) MM_ISU_UKGAS_NOM_to_NOM_ABSAnoop,
The target used in the blog was a File. For a file target you need to create Datatype and Message Type using graphical editors provided in XI.
See the first 2 steps in the blog. A file format data type and msg types are created. Follow that.
Regards,
Jai Shankar -
Reg: Seeburger BIC Mapping Designer
We are using BIC to resolve hierarchy issue.. <u>As you know we can not pasre more than 2 hierarchy levels in XI.</u>
we have a text file which contains all the records in one row..
<Recordset>
<Record00> 1-unbounded
<Field>
<Field>
<Record01>1-unbounded
<Filed>
<Field>
<b>I did following steps in BIC...</b>
Created Datatype in INHOUSE to user project
Edit structure and save
Export structure (msg_....xml)
Run CreateXMLmessage, source file msg_....xml, target file XML_....xml)
Import XML .xml to User Project
Run CreateMappingXMLToEdi source file msg_....xml, target file X2E_....xml
Import X2E .xml to user project..
Run X2E Map by giving our source text file and output will be in xml.
<u><b>Problems:</b></u>
<b> In 5th Step. while importing XML to user project i am getting auto correction window which is changing field occurances and false to true etc.
In 8th Step i am getting errors with conversion and i got the output xml file but with default values which i have given while creating datatype.</b>
I have gone thorugh all the links related to seeburger.
I would really appreciate if anyone thorw some light on the same.
Thanks in Advance...
Regards,
Mansoor.Hi
the steps to generatt the file using the BIC is
1.create the structure in inhouse
2.select the structure you have created , right click then go to the Export, give the destination, the file will be saved at that location.
3.now create the XML message using the create XML Message
4.After creating the XML Message import the XML file .
5. After importing the file the file can be see in the XML node in the BIC mapper for the inhouse structure you have created.
in this way you can create the XML file.
and the created xml file you cam export as XSD,as XML. or as DTD
if you still face the problem please reply me back
Thanks
Rinku
Maybe you are looking for
-
BSP Terminating event not triggering
Hello Friends, We have a scenario, where a BSP application is triggered from a Workflow, for a certain approval, and after the user clicks on Approve button on the BSP Page, the BSP would write to the workflow container using SAP_WAPI_WRITE_CONTAINER
-
Getting short dump while executing a background job
Hi , I have a issue in which i am executing the report in background and the while the job executes it is going into dump stating that the error "TSV_TNEW_PAGE_ALLOC_FAILED" it is happening as the internal table where all the data is getting appended
-
I-Pod not recognized by laptop
Dear All, I use my i-pod as an archive flash disk. I tried to plug it yesterday to different computers, and none have recognized it. I have checked USB ports and all are fine. While not recognized the i-Pod is still charging (using power from lap top
-
How do i repair my disk if disk utility is giving me a sandbox_cashe.db error?
I installed a new hard drive in my mid 2010 macbook pro with Mavericks and about 24 hours after all my files had been transferred over i encountered the spinning beachball of death, after 10 minutes of spinning i powered down and then when i rebooted
-
I just updated my iPhone to the 5 iOS and everything seemed to be ok i still have my contacts but when I plug in to iTunes the page which normally had all the info for the phone is blocked and nothing comes up and I can't put my music back on it or m