on 04-19-2007 5:13 AM
Hi SDN,
I have given by a sample structure which is in XML format...
I need to create datatype by seeing that structure...
Do i need to follow any steps ...while creating datatype.
Regards,
Reehan
If u have XML structure with you...
1) Convert it into WSDL or XSD using any XML Conversion tool..
2) Import the converted WSDL/XSD of step 1 in External definition of interface objects
3) External definition acts as Datatype and Messagetype, so you can use directly in message mapping..
Regards,
Chand.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Reehan,
The method for implementing an XML data type the process is very simple. As suggested by the other members, I do agree that the following steps to do the work.
1. Analysis of the data type given to you. judging the elements its nature (datatype, occurance of the element )
2. Using of Softwares like XML SPY / Stylus Studio to generate the XSD depending on the step 1.
3. Importing the XSD created and importing it to the Integration Repository.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
U can manually create fromt he structure taking into consideration the occurences and the header line item hierarchy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi Reehan
If you have XML structure with you then it is not difficult to create data type
XML is easy to understand .
Looking at the structure of XML you can create Elements,Sub Elements in Data Type.
The no of times the element is repeating in XML document you can assign Occurance in DT.
And you can roughly make out the data type for every element
Hope this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Reehan,
U can take the help of XMLSpy for the same and also just try to visualise the structure ,concentrate on the hierachy and elements in a particular hierarchy this will help to decide on the design.
Each hierarchy can be used to describe a datatype starting from innnermost to outermost
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
You dont need the XMLspy,
you can directly import it under the external deifinitions , there you can select the given xml file , automatically it will import , not you can have the structure , use this in mapping , if possible , if not create it MT with that and use in mapping..i am sure it will be useful in mapping directly..
If you want to create a data type with given xml file , first create the data type and click on xsd and click on import and select the given xml file it will import the structure..
Regards
Chilla
Hi,
Also refer thsi lonk to create data type http://help.sap.com/saphelp_nw2004s/helpdata/en/2d/c0633c3a892251e10000000a114084/frameset.htm
Satish,
This is my sample structure..
could you plz help me...
<?xml version="1.0" encoding="iso-8859-1" ?>
- <PlanningSchedule>
- <PlanningScheduleHeader>
<ScheduleID></ScheduleID>
<ScheduleIssueDate></ScheduleIssueDate>
- <SchedulePurpose>
- <Purpose>
<PurposeCoded></PurposeCoded>
</Purpose>
</SchedulePurpose>
<ScheduleTypeCoded> </ScheduleTypeCoded>
<ScheduleTypeCodedOther></ScheduleTypeCodedOther>
<QuantityQualifierCoded></QuantityQualifierCoded>
- <ScheduleParty>
- <BuyerParty>
- <Party>
- <PartyID>
- <Identifier>
- <Agency>
<AgencyCoded></AgencyCoded>
</Agency>
<Ident />
</Identifier>
</PartyID>
- <ListOfIdentifier>
- <Identifier>
- <Agency>
<AgencyCoded></AgencyCoded>
</Agency>
<Ident></Ident>
</Identifier>
- <Identifier>
- <Agency>
<AgencyCoded></AgencyCoded>
</Agency>
<Ident></Ident>
</Identifier>
</ListOfIdentifier>
</Party>
</BuyerParty>
- <SellerParty>
- <Party>
- <PartyID>
- <Identifier>
- <Agency>
<AgencyCoded></AgencyCoded>
</Agency>
<Ident />
</Identifier>
</PartyID>
- <ListOfIdentifier>
- <Identifier>
- <Agency>
<AgencyCoded></AgencyCoded>
</Agency>
<Ident></Ident>
</Identifier>
- <Identifier>
- <Agency>
<AgencyCoded></AgencyCoded>
</Agency>
<Ident></Ident>
</Identifier>
</ListOfIdentifier>
</Party>
</SellerParty>
- <ShipFromParty>
- <Party>
- <PartyID>
- <Identifier>
- <Agency>
<AgencyCoded></AgencyCoded>
</Agency>
<Ident />
</Identifier>
</PartyID>
</Party>
</ShipFromParty>
- <ShipToParty>
- <Party>
- <PartyID>
- <Identifier>
- <Agency>
<AgencyCoded></AgencyCoded>
</Agency>
<Ident />
</Identifier>
</PartyID>
</Party>
</ShipToParty>
</ScheduleParty>
- <Language>
<LanguageCoded></LanguageCoded>
</Language>
</PlanningScheduleHeader>
- <ListOfLocationGroupedPlanningDetail>
- <LocationGroupedPlanningDetail>
- <Location>
- <LocationIdentifier>
- <LocID>
- <Identifier>
- <Agency>
<AgencyCoded></AgencyCoded>
</Agency>
<Ident></Ident>
</Identifier>
</LocID>
</LocationIdentifier>
</Location>
- <ListOfLocationPlanningItemDetail>
- <LocationPlanningItemDetail>
- <BasePlanningDetail>
- <LineItemNum>
<BuyerLineItemNum></BuyerLineItemNum>
</LineItemNum>
- <ItemIdentifiers>
- <PartNumbers>
- <BuyerPartNumber>
- <PartNum>
<PartID></PartID>
</PartNum>
</BuyerPartNumber>
- <StandardPartNumber>
- <ProductIdentifierCoded>
<ProductIdentifierQualifierCoded></ProductIdentifierQualifierCoded>
<ProductIdentifier></ProductIdentifier>
</ProductIdentifierCoded>
</StandardPartNumber>
</PartNumbers>
<ItemDescription>Material text************************************</ItemDescription>
</ItemIdentifiers>
- <ListOfItemReferences>
- <ListOfReferenceCoded>
- <ReferenceCoded>
<ReferenceTypeCoded></ReferenceTypeCoded>
<ReferenceTypeCodedOther></ReferenceTypeCodedOther>
- <PrimaryReference>
- <Reference>
<RefNum></RefNum>
</Reference>
</PrimaryReference>
</ReferenceCoded>
</ListOfReferenceCoded>
</ListOfItemReferences>
<ForecastFrequencyCoded></ForecastFrequencyCoded>
</BasePlanningDetail>
- <ListOfScheduleDetail>
- <ScheduleDetail>
<CommitmentLevelCoded></CommitmentLevelCoded>
- <ScheduleDates>
- <ListOfDateCoded>
- <DateCoded>
<Date></Date>
- <DateQualifier>
<DateQualifierCoded></DateQualifierCoded>
</DateQualifier>
</DateCoded>
</ListOfDateCoded>
</ScheduleDates>
- <ScheduleQuantities>
- <ListOfQuantityCoded>
- <QuantityCoded>
<QuantityValue></QuantityValue>
- <UnitOfMeasurement>
<UOMCoded></UOMCoded>
</UnitOfMeasurement>
<QuantityQualifierCoded></QuantityQualifierCoded>
</QuantityCoded>
</ListOfQuantityCoded>
</ScheduleQuantities>
</ScheduleDetail>
</ListOfScheduleDetail>
</LocationPlanningItemDetail>
</ListOfLocationPlanningItemDetail>
</LocationGroupedPlanningDetail>
- <LocationGroupedPlanningDetail>
- <Location>
- <LocationIdentifier>
- <LocID>
- <Identifier>
- <Agency>
<AgencyCoded></AgencyCoded>
</Agency>
<Ident></Ident>
</Identifier>
</LocID>
</LocationIdentifier>
</Location>
- <ListOfLocationPlanningItemDetail>
- <LocationPlanningItemDetail>
- <BasePlanningDetail>
- <LineItemNum>
<BuyerLineItemNum></BuyerLineItemNum>
</LineItemNum>
- <ItemIdentifiers>
- <PartNumbers>
- <BuyerPartNumber>
- <PartNum>
<PartID></PartID>
</PartNum>
</BuyerPartNumber>
Regards,
Rehaan
Hi ,
U can make out an XSD out of the input XML using xmlspy and upload the same in the external definition
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.