Data enhancement, external definition
hi all
i m new 4 sap xi
i want some examples of data enhencement nd external definition?
nd also i have there definitions?
..thanks all
Hi,
External Defination is use to import the created data type. In SAP XI we can import
XSD, WSDL and DTD.
Example: Below is the created XSD, just save it to your desktop test<b>.xsd</b> and import in IR using the External Defination.
Go to IR>SWCV>namespace>Interface objects>External Defination.
Note: by default the category is WSDL, select the xsd for this
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
<xs:element name="ProductSKU">
<xs:complexType>
<xs:sequence minOccurs="0">
<xs:element ref="header" minOccurs="0"/>
<xs:element ref="product" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="header">
<xs:complexType>
<xs:sequence minOccurs="0">
<xs:element ref="creatorClientId" minOccurs="0"/>
<xs:element ref="migrationEnvironment" minOccurs="0"/>
<xs:element ref="origCreatorClientId" minOccurs="0"/>
<xs:element ref="replyRequested" minOccurs="0"/>
<xs:element ref="apiVersion" minOccurs="0"/>
<xs:element ref="infoMsgs" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="creatorClientId" type="xs:string"/>
<xs:element name="migrationEnvironment" type="xs:string"/>
<xs:element name="origCreatorClientId" type="xs:string"/>
<xs:element name="replyRequested" type="xs:boolean"/>
<xs:element name="apiVersion" type="xs:string"/>
<xs:element name="infoMsgs">
<xs:complexType>
<xs:sequence minOccurs="0">
<xs:element ref="level" minOccurs="0"/>
<xs:element ref="sysMsgClass" minOccurs="0"/>
<xs:element ref="sysMsgNum" minOccurs="0"/>
<xs:element ref="sysMsgText" minOccurs="0"/>
<xs:element ref="sysMsgType" minOccurs="0"/>
<xs:element ref="systemCode" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="level" type="xs:string"/>
<xs:element name="sysMsgClass" type="xs:string"/>
<xs:element name="sysMsgNum" type="xs:string"/>
<xs:element name="sysMsgText" type="xs:string"/>
<xs:element name="sysMsgType" type="xs:string"/>
<xs:element name="systemCode" type="xs:string"/>
<xs:element name="product">
<xs:complexType>
<xs:sequence minOccurs="0">
<xs:element ref="audit" minOccurs="0"/>
<xs:element ref="pKey" minOccurs="0"/>
<xs:element ref="isPackage" minOccurs="0"/>
<xs:element ref="nameCode" minOccurs="0"/>
<xs:element ref="basePrice" minOccurs="0"/>
<xs:element ref="channelCode" minOccurs="0"/>
<xs:element ref="skuNum" minOccurs="0"/>
<xs:element ref="isSaleable" minOccurs="0"/>
<xs:element ref="sapDescription" minOccurs="0"/>
<xs:element ref="version" minOccurs="0"/>
<xs:element ref="statusCode" minOccurs="0"/>
<xs:element ref="typeCode" minOccurs="0"/>
<xs:element ref="mediaCode" minOccurs="0"/>
<xs:element ref="platformCode" minOccurs="0"/>
<xs:element ref="languageCode" minOccurs="0"/>
<xs:element ref="fulfillMethodCode" minOccurs="0"/>
<xs:element ref="licenseCode" minOccurs="0"/>
<xs:element ref="licenseSeats" minOccurs="0"/>
<xs:element ref="snGenType" minOccurs="0"/>
<xs:element ref="snLegacyPrefix" minOccurs="0"/>
<xs:element ref="taxCode" minOccurs="0"/>
<xs:element ref="quantity" minOccurs="0"/>
<xs:element ref="isOrderable" minOccurs="0"/>
<xs:element ref="enigmaProtocol" minOccurs="0"/>
<xs:element ref="enigmaProductId" minOccurs="0"/>
<xs:element ref="enigmaProductCode" minOccurs="0"/>
<xs:element ref="enigmaInstallerCode" minOccurs="0"/>
<xs:element ref="enigmaSecurityCode" minOccurs="0"/>
<xs:element ref="enigmaSupportCode" minOccurs="0"/>
<xs:element ref="isForReserialization" minOccurs="0"/>
<xs:element ref="plantCode" minOccurs="0"/>
<xs:element ref="sapCategoryCode" minOccurs="0"/>
<xs:element ref="sapMaterialTypeCode" minOccurs="0"/>
<xs:element ref="isWebSellable" minOccurs="0"/>
<xs:element ref="childCount" minOccurs="0"/>
<xs:element ref="expireDate" minOccurs="0"/>
<xs:element ref="guid" minOccurs="0"/>
<xs:element ref="child" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="versionName" minOccurs="0"/>
<xs:element ref="enigmaPackingLicense" minOccurs="0"/>
<xs:element ref="isInProduction" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="audit">
<xs:complexType>
<xs:sequence minOccurs="0">
<xs:element ref="createDate" minOccurs="0"/>
<xs:element ref="createSystemCode" minOccurs="0"/>
<xs:element ref="createUserId" minOccurs="0"/>
<xs:element ref="updateDate" minOccurs="0"/>
<xs:element ref="updateUserId" minOccurs="0"/>
<xs:element ref="updateSystemCode" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="createDate" type="xs:string"/>
<xs:element name="createSystemCode" type="xs:string"/>
<xs:element name="createUserId" type="xs:string"/>
<xs:element name="updateDate" type="xs:string"/>
<xs:element name="updateUserId" type="xs:string"/>
<xs:element name="updateSystemCode" type="xs:string"/>
<xs:element name="pKey" type="xs:string"/>
<xs:element name="isPackage" type="xs:boolean"/>
<xs:element name="nameCode" type="xs:string"/>
<xs:element name="basePrice" type="xs:string"/>
<xs:element name="channelCode" type="xs:string"/>
<xs:element name="skuNum" type="xs:string"/>
<xs:element name="isSaleable" type="xs:boolean"/>
<xs:element name="sapDescription" type="xs:string"/>
<xs:element name="version" type="xs:string"/>
<xs:element name="statusCode" type="xs:string"/>
<xs:element name="typeCode" type="xs:string"/>
<xs:element name="mediaCode" type="xs:string"/>
<xs:element name="platformCode" type="xs:string"/>
<xs:element name="languageCode" type="xs:string"/>
<xs:element name="fulfillMethodCode" type="xs:string"/>
<xs:element name="licenseCode" type="xs:string"/>
<xs:element name="licenseSeats" type="xs:string"/>
<xs:element name="snGenType" type="xs:string"/>
<xs:element name="snLegacyPrefix" type="xs:string"/>
<xs:element name="taxCode" type="xs:string"/>
<xs:element name="quantity" type="xs:string"/>
<xs:element name="isOrderable" type="xs:boolean"/>
<xs:element name="enigmaProtocol" type="xs:string"/>
<xs:element name="enigmaProductId" type="xs:string"/>
<xs:element name="enigmaProductCode" type="xs:string"/>
<xs:element name="enigmaInstallerCode" type="xs:string"/>
<xs:element name="enigmaSecurityCode" type="xs:string"/>
<xs:element name="enigmaSupportCode" type="xs:string"/>
<xs:element name="isForReserialization" type="xs:boolean"/>
<xs:element name="plantCode" type="xs:string"/>
<xs:element name="sapCategoryCode" type="xs:string"/>
<xs:element name="sapMaterialTypeCode" type="xs:string"/>
<xs:element name="isWebSellable" type="xs:boolean"/>
<xs:element name="childCount" type="xs:string"/>
<xs:element name="expireDate" type="xs:string"/>
<xs:element name="guid" type="xs:string"/>
<xs:element name="child">
<xs:complexType>
<xs:sequence minOccurs="0">
<xs:element ref="childSku" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="childSku" type="xs:string"/>
<xs:element name="versionName" type="xs:string"/>
<xs:element name="enigmaPackingLicense" type="xs:string"/>
<xs:element name="isInProduction" type="xs:boolean"/>
</xs:schema>
Thanks
Farooq.
<b>*Rewards Points if you find it useful*</b>
Similar Messages
-
Can't use Data type created with External Definition
Hi,
In the repository, I would like to transport a very complexe DataType from one XI system to an other one. As I don't want to spend a week to create data types, I created a new External Definitions and loaded my XSD schema (that I exported as XSD from Source system) with Messages parameter set to "From All Available Global Elements". I don't set the "Source". I can see the "Imported Document" and "WSDL", but the Messages and External References tabs are empty. Furthermore, I can't use my new message type in a Outbound Asyncrhronous Message Interface.
Here is a very small XSD file that I use to test my scenario.
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://veilleux.1" targetNamespace="http://veilleux.1">
<xsd:complexType name="SimpleType1">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
bdfdbef1df9711daa2c9001125f86068
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Name" type="SimpleType2">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
bdfdbef0df9711daa821001125f86068
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="SimpleType2">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
0fecc852df9811da899a000f206d294f
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Name" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
ac58afc0df9711da86af001125f86068
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Any one can help me please.
Thanks, DavyHello Moorthy,
My XSD is correct since it's XI itself that generated it from real Data Type on my source System (but I tested it in Internet Explorer and it looks fine).
I tried to select my ExternalDefinition as source in MessageMapping, but XI doesn't let me specify it (Apply button is disabled when I select my ExternalDefinition).
I'm pretty sure that it is related to the fact that I should have a Data Type in "Messages" and "External References" tabs and I have nothing. My XSD is legal, but it seems that XI can't automatically create the data type from it.
Do you have any other idea?
Thanks, Davy -
External definition and used them as Data Type Templates
hi all
how to Develop external definition and used them as Data Type Templates .
Thank u
SwariHI
External Definitions: If a definition of the message structure exists in wsdl, xsd, dtd formats, we can use it in the integration repository by importing it as an external definition.
External Definations:
An external definition enables you to import a local WSDL, XSD, or DTD file to the Integration Repository and specify which parts of the schema to extract as the description for a message. You can use these extracted message schema as:
Output or input messages in message interfaces
Source or target structures for message mappings
There is a series of standard schema for describing the message structure at runtime. WSDL (Web Service Description Language), XSD (XML Schema Definition Language), or DTDs (Document Type Definitions) are often used to describe message schema. If a description of the message structure already exists in one of the above formats, you can use it in the Integration Repository by importing it as an external definition rather than re-entering it manually using the data type editor.
Have a look at
http://help.sap.com/saphelp_nw04/helpdata/en/43/ce49ef1019087ae10000000a1553f6/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ba/d4c23b95c8466ce10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm
cheers -
Possible? Using External Definitions for data type/message type definitions
Hi all,
i want to use external definitons in my own data type definitions. Is that possible? And if yes, how?
I imported many definitions via a mass import. Now I also want to use these definitions for further interfaces (than the imported ones). The most convenient would be of course to just use them as a custom created type. Can I somehow "convert" an external definition to a data type/message type?
KR
FelixHello Felix,
The External defination which you has been imported that cant use in DT and MT but yeah you can use this in Service interface.
you cant modify that External defination if you want to do that then 1st of all modify it and then reimport it as an another external defination.
and creating service interface with this ED you can use it in your message mapping .
i hope this will help to you to clear your doubt.
Monica -
Error while selecting date from external table
Hello all,
I am getting the follwing error while selecting data from external table. Any idea why?
SQL> CREATE TABLE SE2_EXT (SE_REF_NO VARCHAR2(255),
2 SE_CUST_ID NUMBER(38),
3 SE_TRAN_AMT_LCY FLOAT(126),
4 SE_REVERSAL_MARKER VARCHAR2(255))
5 ORGANIZATION EXTERNAL (
6 TYPE ORACLE_LOADER
7 DEFAULT DIRECTORY ext_tables
8 ACCESS PARAMETERS (
9 RECORDS DELIMITED BY NEWLINE
10 FIELDS TERMINATED BY ','
11 MISSING FIELD VALUES ARE NULL
12 (
13 country_code CHAR(5),
14 country_name CHAR(50),
15 country_language CHAR(50)
16 )
17 )
18 LOCATION ('SE2.csv')
19 )
20 PARALLEL 5
21 REJECT LIMIT UNLIMITED;
Table created.
SQL> select * from se2_ext;
SQL> select count(*) from se2_ext;
select count(*) from se2_ext
ERROR at line 1:
ORA-29913: error in executing ODCIEXTTABLEOPEN callout
ORA-29400: data cartridge error
KUP-04043: table column not found in external source: SE_REF_NO
ORA-06512: at "SYS.ORACLE_LOADER", line 19It would appear that you external table definition and the external data file data do not match up. Post a few input records so someone can duplicate the problem and determine the fix.
HTH -- Mark D Powell -- -
Unable to see Messages in External Definitions
I imported the WSDL below and created a Message Interface based on JobSubmitRequest but, when I come to map to it, all I see in the tree structure is node 'JobSubmitRequest' with elements 'parameter' and 'request_header'.
I also cannot see any messages in External Definitions.
Can anyone help with a solution?
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xoa="http://xoa.xpedite.com/2004/11/xoa" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://xoa.xpedite.com/2004/11/xoa">
<types>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://xoa.xpedite.com/2004/11/xoa" xmlns="http://xoa.xpedite.com/2004/11/xoa">
<!-- address type enum -->
<xs:simpleType name="AddressType">
<xs:restriction base="xs:string">
<xs:enumeration value="fax"/>
<xs:enumeration value="internet"/>
<xs:enumeration value="mbox"/>
<xs:enumeration value="x400"/>
<xs:enumeration value="telex"/>
<xs:enumeration value="cablegram"/>
<xs:enumeration value="mailgram"/>
<xs:enumeration value="ddd"/>
<xs:enumeration value="dedLine"/>
<xs:enumeration value="softswitch"/>
<xs:enumeration value="voice"/>
<xs:enumeration value="sms"/>
<xs:enumeration value="fod"/>
<xs:enumeration value="list"/>
<xs:enumeration value="smQuery"/>
</xs:restriction>
</xs:simpleType>
<!--includes for standalone validation
<xs:include schemaLocation="StatusType.xsd"/>
================ -->
<xs:element name="AuthenticateRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="Domain" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- The authenticate result (used to send back results for synchronous and asynchronous requests) -->
<xs:element name="AuthenticateResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="StatusType.xsd"/>
================ -->
<xs:element name="CFSCreateDirRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSCreateDirResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="StatusType.xsd"/>
================ -->
<xs:element name="CFSDeleteRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
<xs:element minOccurs="0" name="DeleteDir" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSDeleteResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
================ -->
<xs:element name="CFSDownloadRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSDownloadResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
<xs:element minOccurs="0" name="FileData" type="xoa:DocDataType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
================ -->
<xs:element name="CFSListRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
<xs:element minOccurs="0" name="IncludeSubDir" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:simpleType name="EntryType">
<xs:restriction base="xs:string">
<xs:enumeration value="file"/>
<xs:enumeration value="directory"/>
</xs:restriction>
</xs:simpleType>
<xs:element name="CFSListResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="DirectoryEntry" type="xoa:DirectoryEntryType">
<xs:annotation>
<xs:documentation>content of
DirectoryEntry is path relative to
the RelativePath</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="DirectoryEntryType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="type" type="xoa:EntryType" use="required"/>
<xs:attribute name="modified" type="xs:dateTime" use="optional"/>
<xs:attribute name="size" type="xs:integer" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!-- includes for standalone validation
<xs:include schemaLocation="StatusType.xsd"/>
================ -->
<xs:element name="CFSRenameRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="OldRelativePath" type="xs:string"/>
<xs:element name="NewRelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSRenameResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="OldRelativePath" type="xs:string"/>
<xs:element minOccurs="0" name="NewRelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
================ -->
<xs:element name="CFSUploadRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
<xs:element name="FileData" type="xoa:DocDataType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSUploadResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- ===============================
<xs:include schemaLocation="AddressType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
<xs:include schemaLocation="EncodableStringType.xsd"/>
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
=============================== -->
<!-- Type definitions -->
<!-- Phone element -->
<xs:element name="Phone">
<xs:simpleType>
<xs:restriction base="xs:string">
<!-- <xs:pattern value="[0-9+x\-() ]{5,20}"/> -->
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- Email element -->
<xs:element name="Email">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="2"/>
<!-- <xs:pattern value="[@]{1,64}@([@\.]{1,64}\.){1,10}[^@\.]{1,64}"/> -->
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- Eformat type -->
<xs:simpleType name="EformatType">
<xs:annotation>
<xs:documentation> Only used in messageREACH.
Indicates the preferred email format of the
message body the recipient will receive.
Leaving the field empty or setting it to
"default" will send a multipart message body
rather than just a single message body if
it would do so normally. </xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="text"/>
<xs:enumeration value="html"/>
<xs:enumeration value="htmllite"/>
<xs:enumeration value="default"/>
</xs:restriction>
</xs:simpleType>
<!-- insert list element -->
<xs:element name="InsertList">
<xs:complexType>
<xs:choice>
<xs:element maxOccurs="unbounded" name="Insert">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="number" type="xs:integer"/>
<xs:attribute name="b64charset" type="xs:string" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:choice>
</xs:complexType>
</xs:element>
<!-- extension element -->
<xs:complexType name="SegmentType">
<xs:choice>
<xs:element maxOccurs="unbounded" name="Property">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="name" type="xs:string"/>
<xs:attribute name="b64charset" type="xs:string" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:choice>
<xs:attribute name="name" type="xs:string"/>
</xs:complexType>
<xs:element name="Extension">
<xs:complexType>
<xs:choice maxOccurs="unbounded">
<xs:element name="Segment" type="xoa:SegmentType"/>
</xs:choice>
</xs:complexType>
</xs:element>
<!-- field mapping type -->
<xs:complexType name="FieldMappingType">
<xs:annotation>
<xs:documentation> Describes the correspondence
between the segment/keyword pairs in the
XDDS header file and columns in a table. Only
two table formats currently supported: CSV
(comma-separated values) and XSL (Excel
spreadsheet). The mapping may go either
from field name to the segment/keyword pair
or vice versa. In both cases, the same
structure may be used. </xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="Map">
<xs:complexType>
<xs:sequence>
<xs:element name="FieldName" type="xs:string"/>
<xs:element minOccurs="0" name="SegmentName" type="xs:string"/>
<xs:element name="PropertyName" type="xs:string"/>
<xs:element minOccurs="0" name="IsBase64Encoded" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
<!-- class definitions -->
<!-- delivery item base class -->
<xs:element abstract="true" name="DeliveryItem" type="xoa:DeliveryItemType"/>
<xs:complexType abstract="true" name="DeliveryItemType">
<xs:attribute name="ref" type="xs:string" use="optional"/>
<xs:attribute name="refb64" type="xs:string" use="optional"/>
</xs:complexType>
<!-- new branch -->
<!-- delivery item container class -->
<xs:element abstract="true" name="DeliveryItemContainer" type="xoa:DeliveryItemContainerType"/>
<xs:complexType abstract="true" name="DeliveryItemContainerType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemType"/>
</xs:complexContent>
</xs:complexType>
<!-- list delivery item class -->
<xs:element name="List" type="xoa:ListType"/>
<xs:complexType name="ListType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemContainerType">
<xs:sequence>
<xs:element name="Name" type="xs:string"/>
</xs:sequence>
<xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- SmQuery delivery item class -->
<xs:element name="SmQuery" type="xoa:SmQueryType"/>
<xs:complexType name="SmQueryType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemContainerType">
<xs:sequence>
<xs:element name="Name" type="xs:string"/>
</xs:sequence>
<xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- External table delivery item class -->
<!-- This includes CSV and XLS files -->
<xs:element name="Table" type="xoa:TableType"/>
<xs:complexType name="TableType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemContainerType">
<xs:sequence>
<xs:element minOccurs="0" name="FieldMapping" type="xoa:FieldMappingType"/>
<xs:choice>
<xs:element name="DocRef" type="xs:string"/>
<xs:element name="Document" type="xoa:DocumentType"/>
</xs:choice>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- new branch -->
<!-- delivery item simple class -->
<xs:element abstract="true" name="DeliveryItemSimple" type="xoa:DeliveryItemSimpleType"/>
<xs:complexType abstract="true" name="DeliveryItemSimpleType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemType">
<xs:sequence>
<xs:element minOccurs="0" name="Alternate">
<xs:complexType>
<xs:choice>
<xs:element ref="xoa:Fax"/>
<xs:element ref="xoa:Internet"/>
<xs:element ref="xoa:Voice"/>
<xs:element ref="xoa:Fod"/>
<xs:element ref="xoa:Mbox"/>
<xs:element ref="xoa:Sms"/>
<xs:element ref="xoa:Telex"/>
<xs:element ref="xoa:DeliveryItemGeneric"/>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- mbox delivery item class -->
<xs:element name="Mbox" type="xoa:MboxType"/>
<xs:complexType name="MboxType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element name="UserId" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- telex delivery item class -->
<xs:element name="Telex" type="xoa:TelexType"/>
<xs:complexType name="TelexType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element name="Number" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- FOD delivery item class -->
<xs:element name="Fod" type="xoa:FodType"/>
<xs:complexType name="FodType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element name="Address" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- SMS delivery item class -->
<xs:element name="Sms" type="xoa:SmsType"/>
<xs:complexType name="SmsType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element ref="xoa:Phone"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- new branch -->
<!-- Complex delivery item class -->
<xs:element abstract="true" name="DeliveryItemComplex" type="xoa:DeliveryItemComplexType"/>
<xs:complexType abstract="true" name="DeliveryItemComplexType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element minOccurs="0" ref="xoa:InsertList"/>
<xs:element minOccurs="0" ref="xoa:Extension"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- fax delivery item class -->
<xs:element name="Fax" type="xoa:FaxType"/>
<xs:complexType name="FaxType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemComplexType">
<xs:sequence>
<xs:element ref="xoa:Phone"/>
<xs:element minOccurs="0" name="Att" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="From" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="To" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="Salutation" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- voice delivery item class -->
<xs:element name="Voice" type="xoa:VoiceType"/>
<xs:complexType name="VoiceType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemComplexType">
<xs:sequence>
<xs:element ref="xoa:Phone"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- internet delivery item class -->
<xs:element name="Internet" type="xoa:InternetType"/>
<xs:complexType name="InternetType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemComplexType">
<xs:sequence>
<xs:element ref="xoa:Email"/>
<xs:element minOccurs="0" name="Subject" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="From" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="Eformat" type="xoa:EformatType"/>
<xs:element minOccurs="0" name="Password" type="xs:string">
<xs:annotation>
<xs:documentation> Only used in
messageREACH. The password used
by this recipient to retrieve
pull attachments. </xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- fax delivery item class -->
<xs:element name="DeliveryItemGeneric" type="xoa:DeliveryItemGenericType"/>
<xs:complexType name="DeliveryItemGenericType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemComplexType">
<xs:sequence>
<xs:element name="Address" type="xs:string"/>
</xs:sequence>
<xs:attribute name="type" type="xoa:AddressType" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- Finally, delivery item list -->
<!-- delivery item list type -->
<xs:complexType name="DeliveryItemListType">
<xs:choice maxOccurs="unbounded">
<xs:element ref="xoa:List"/>
<xs:element ref="xoa:SmQuery"/>
<xs:element ref="xoa:Table"/>
<xs:element ref="xoa:DeliveryItemGeneric"/>
<xs:element ref="xoa:Fax"/>
<xs:element ref="xoa:Internet"/>
<xs:element ref="xoa:Voice"/>
<xs:element ref="xoa:Fod"/>
<xs:element ref="xoa:Mbox"/>
<xs:element ref="xoa:Sms"/>
<xs:element ref="xoa:Telex"/>
</xs:choice>
</xs:complexType>
<!--remove includes later
<xs:include schemaLocation="AddressType.xsd"/>
================ -->
<xs:complexType name="DestinationType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="type" type="xoa:AddressType"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!-- ===============================
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
=============================== -->
<!-- Elementary definitions go first -->
<xs:element name="CharacterSet" type="xs:string">
<xs:annotation>
<xs:documentation>use ISO names</xs:documentation>
</xs:annotation>
</xs:element>
<!-- Document type -->
<xs:simpleType name="DocFormatType">
<xs:restriction base="xs:string">
<xs:enumeration value="text"/>
<xs:enumeration value="XMF"/>
<xs:enumeration value="TIFF"/>
<xs:enumeration value="XAR"/>
<xs:enumeration value="PS"/>
<xs:enumeration value="PCL"/>
<xs:enumeration value="PDF"/>
<xs:enumeration value="MSW"/>
<xs:enumeration value="WAV"/>
<xs:enumeration value="RTF"/>
<xs:enumeration value="XLS"/>
<xs:enumeration value="HTML"/>
<xs:enumeration value="HTMLLITE"/>
<xs:enumeration value="unspec"/>
<xs:enumeration value="GIF"/>
<xs:enumeration value="JPEG"/>
<xs:enumeration value="PPT"/>
<xs:enumeration value="BMP"/>
<xs:enumeration value="VSD"/>
<xs:enumeration value="PUB"/>
<xs:enumeration value="MPP"/>
<xs:enumeration value="empty"/>
<!-- We do not need to know the document type for the -->
<!-- email attachments. -->
</xs:restriction>
</xs:simpleType>
<!-- Document Encoding format -->
<xs:simpleType name="DocEncodingFormat">
<xs:restriction base="xs:string">
<xs:enumeration value="text"/>
<xs:enumeration value="base64"/>
</xs:restriction>
</xs:simpleType>
<!-- Document embedded into the request -->
<xs:complexType name="DocDataType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="format" type="xoa:DocEncodingFormat" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!-- All supported stored object types -->
<xs:simpleType name="SosObjectType">
<xs:restriction base="xs:string">
<xs:enumeration value="tts"/>
<xs:enumeration value="vcs"/>
</xs:restriction>
</xs:simpleType>
<!-- The types of the sos stored objects -->
<xs:complexType name="SosObjectIdType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="sosType" type="xoa:SosObjectType" use="required"/>
<xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!-- Another Document type -->
<xs:complexType name="DocumentType">
<xs:sequence>
<xs:element name="DocType" type="xoa:DocFormatType"/>
<xs:element minOccurs="0" name="Filename" type="xs:string"/>
<xs:choice>
<xs:element name="DocData" type="xoa:DocDataType"/>
<xs:element name="DocCfs" type="xs:string"/>
<xs:element name="DocUrl" type="xs:anyURI"/>
<xs:element name="SosObject" type="xoa:SosObjectIdType"/>
</xs:choice>
<xs:element minOccurs="0" ref="xoa:CharacterSet"/>
</xs:sequence>
<xs:attribute name="ref" type="xs:string" use="optional"/>
</xs:complexType>
<!-- The document set type -->
<xs:complexType name="DocumentSetType">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="Document" type="xoa:DocumentType"/>
</xs:sequence>
</xs:complexType>
<!-- The document by value or by reference -->
<xs:complexType name="DocumentOrRefType">
<xs:choice>
<xs:element name="DocRef" type="xs:string">
<xs:annotation>
<xs:documentation>must refer to a document
in document_set</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Document" type="xoa:DocumentType"/>
</xs:choice>
</xs:complexType>
<xs:complexType name="EncodableStringType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="b64charset" type="xs:string" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!--includes for standalone validation
================ -->
<xs:simpleType name="HistoryActionType">
<xs:restriction base="xs:string">
<xs:enumeration value="inserted"/>
<xs:enumeration value="updated"/>
<xs:enumeration value="deleted"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="ItemCountType">
<xs:simpleContent>
<xs:extension base="xs:integer">
<xs:attribute name="type" type="xoa:HistoryActionType"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="HistoryType">
<xs:sequence>
<xs:element name="Action" type="xs:string"/>
<xs:element name="Operator" type="xs:string"/>
<xs:element name="Agent" type="xs:string"/>
<xs:element name="Time" type="xs:dateTime"/>
<xs:element name="ItemCount" type="xoa:ItemCountType"/>
</xs:sequence>
</xs:complexType>
<!-- ================
<xs:include schemaLocation="AddressType.xsd"/>
<xs:include schemaLocation="DestinationType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
<xs:include schemaLocation="JobIdType.xsd"/>
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
<xs:include schemaLocation="RecStatusType.xsd"/>
================ -->
<xs:simpleType name="JobCancelType">
<xs:annotation>
<xs:documentation>The set of cancellation types/options</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="All"/>
<xs:enumeration value="Deliveries"/>
<xs:enumeration value="Reports"/>
<xs:enumeration value="AcceptanceReport"/>
<xs:enumeration value="CancellationNotice"/>
<xs:enumeration value="Pulls"/>
<xs:enumeration value="FriendDeliveries"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="JobCancelItemType">
<xs:sequence>
<xs:element name="JobId" type="xoa:JobIdType">
<xs:annotation>
<xs:documentation>requested JobId</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="CancelType" type="xoa:JobCancelType"/>
<xs:element minOccurs="0" name="NotificationAddress" type="xoa:DestinationType"/>
<xs:choice minOccurs="0">
<xs:element name="NotificationType" type="xs:string"/>
<xs:element name="NotificationText" type="xoa:DocDataType"/>
</xs:choice>
</xs:sequence>
</xs:complexType>
&Hi,
Not all data types from WSDL are supported during import. There is SAP Note about it.
please read it:
/people/kevin.liu/blog/2005/10/07/a-note-on-wsdl-and-xsd-imports--part-ii
regards,
wojtek
Message was edited by: Wojciech Gasiorowski -
How to remove namespaces in mapping when using External Definition
Hi,
I read in the blog (/people/sameer.shadab/blog/2005/12/05/how-to-remove-namespaces-in-mapping--xi) that you are able to remove namespaces in mapping by deleting the value from XML Namespace under the Message Type. However, is it possible to do this when you are using External Definition (xsd) ? The blog only describe how to do this if you define a Data Type.Hi ,
No ..it is not possible to remove the namespace once you imported into IR of external defintion.You can remove your namesapce from external definition before importing into IR.
Sekhar -
Not able to see "External Definitions" in Integration Repository
Hi Experts,
I am working on PI 7.1.
In the Integration Repository Menu :
SAP Basis --->SAP Basis 7.10 ->http://sap.com/xi/XI/System ->
"Service Interfaces",
"Message Types"
"Fault Message Types",
"Data Types",
"Adapter Metadata"
only are visible.
We need the "External Definitions". Is it not available in the standard SAP PI 7.1 ?
Do we have to import it explicitly?
Kindly advice.
Thanks in advance
~ SurajHey NM,
Thanks a lot for your suggestion. problem got resolved when i did what you said (checking the attributes with developers user id's)
Thanks
Sourav -
External Definitions...Need Help
could you please explain what is the main advantage of creating an External Definitions under the basic objects?
In this we have to pass one mandatory field like File... where do i get this file and what it contain exactly?
please let me know....Hi Hari,
As shekar has mentioned External definations are required to import WSDL, XSD etc, so that they can be used in the Integration scenario. They are generally provided by the Systems participating in the integration scenario.
For example if you are working in a scenario where you need to connect to a web service, then the web service people will provide you their WSDl that you need to import in external definations and use it in mapping and stuff. It saves you lot of time and hard work of creating data types and message types.
In your scenario, if you need to add an extra element in the external defination then first create a data type of FILE and then add it to Message type created using the External definations.
This should work or else provide us the whole inital and final structure that you require.
Regards,
Ashish -
Getting campaign data from external system to display campaigns/offers
Hi,
I have to find a solution for a campaign requirement for my company.
The user centric campaigns are managed by a external system provider who process billing statements (eg if you see your paper credit card statement, you see special offers, campaigns in your paper statement.)
On similar lines we have to show/build the campaign in our WLP application. The campaign data is hosted in external systems.
We have to think of a generic reciever in WLP which can get the external campaign data and based upon that it can display right campaign to logged in users.
Any ideas, leads. Has somebody implememted such a feature.
Any help will be appreciatedHi Vishnu,
OK, I see now. You don't want a pluggable user profile data source, you want a pluggable campaign rule and pluggable campaign content. I don't think there is such a thing as a framework for plugging an external campaign into Oracle WebLogic Portal.
I don't think you can plug an external campaign rule into the Oracle WebLogic Portal rules engine but you can make Oracle WebLogic Portal see external user profile data and external content. So, 2 of the 3 ingredients for the campaign are easy enough to make available to the portal. I would guess that you either need to transform the campaign definition into the proper XML document for consumption by the portal's rules engine or you need to evaluate the campaign on the external system and have the results available to the portal via a mechanism like UUP. -
Idoc - External Definitions Error
Hi,
I had to change the occurences of an exisiting idoc. I had imported the xsd,changed the occurrences and reloaded it using WSDL structure.
When i load the external definition in the mapping structure, it is giving me the following error.
Object External Message Z_INVOICE02_MULTI | INVOIC.INVOIC02.ZINVOIC02 | urn:sap-com:document:sap:idoc:messages not found
Please note that when i had imported the xsd, i had removed the target namespace.Hi Sai,
i need to add an additional field to the existing IDOC structure
Is there any specific reason for usign IDOC as external definition (are you changing the occurance of IDOC)?
what is your sender and receiver system?
Are you expecting the value for this addition field to be populated by sap along with the rest of IDOC data? if yes then ,get a custom IDOC created in SAP with the required field.
Or if you want to populate this additional field in PI usign any logic (assuming you are sending to any non sap system), then you can create a new ED for the targert , just export
the ED to desktop , open with any xml editor (xml spy or microsoft visual studio 2005) and navigate to the portion of xsd which you want to edit add the field -> reimport in PI and use it as your target strucuture.You cannot edit ED directly in ESR.
Regards,
Srinivas -
Using SAPR/3 IDOC in PI as External definition,type of communication channe
Hi,iam using IDOC Structure as an external definition in PI ,I JUST want to know the procedure for file to idoc using external defintion for idoc structure in the reciever side and what is the communication channel needed for recieving external definition at reciever side.
will be waiting for you rresponse.
bye.
regards.
VarmaHi
Use the following steps:
1. Select the software component that you want to import an IDoc type for.
Check the settings for the software component version. Make sure the
attribute Import of RFC and IDoc Interfaces from SAP Systems Permitted
is selected and that the technical connection data for importing from the
SAP system is maintained.
2. Under the Imported Objects node choose Import RFC/IDoc from the context
menu.
3. Enter a valid user and password and choose Continue.
You need to use a receive IDoc Communication Channel but in case of sender no need to create a communication channel.
Regards
Monika -
Hi Friends,
There is a requirement for external definition to import. I got one file from client text file having xml data. So i have save as to .XSD format and tested in XI while uploading into external definitions.
As per my knowledge, .XSD/wsdl/dtd file can be used for external definitions. And, it acts as Message type so create MI .
So , if we request from client , is there specific format is there for .XSD??? Is it only message type else data type possible ???
How to guide the client to get the .XSD files?
Thank you
DevaHi Deva,
first convert XML file in to XSD,for that you can use XML Editors ALTOVA XML Spy or Styalus studio to conver XML to XSD.
you can get free trail versions available.
The XML to XSD conversion process very easy , just google it.
if you have XSD then you no need to create Data type and Message Type.
Regards,
Raj -
How to see structure under schema when Create External Definition
Hi ...we have scenario like RFC<>XI<>SOAP
The request payload(SOAPIN) for SOAP is:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<AddressValidator xmlns="http://tempuri.org/geostan3/AddressValidator">
<LicenseFile>string</LicenseFile>
<Z9Path>string</Z9Path>
<House>string</House>
<Street>string</Street>
</soap:Body>
</soap:Envelope>
and we are expecting response message from SOAP:
diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1">
- <AddressCheck xmlns="">
- <Address diffgr:id="Address1" msdata:rowOrder="0" diffgr:hasChanges="inserted">
<Addline1>220 W MAIN ST</Addline1>
<Addline2 />
<URB />
<Lastline>LOUISVILLE, KY 40202-1395</Lastline>
<Location>-85754010, 38256144</Location>
<OutBlock>211110049001067</OutBlock>
<OutCBSA>31140</OutCBSA>
<MatchCode>SE0</MatchCode>
<LocationCode>AS0</LocationCode>
<DPVConfirm />
<FootNote1 />
<FootNote2 />
<FootNote3 />
<Msg>OK</Msg>
</Address>
</AddressCheck>
so when we created external definition using wsdl file into XI, it showing only schema as SOAPOUT (I couldn't see those fields in XI/under schema).
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<AddressValidatorResponse xmlns="http://tempuri.org/geostan3/AddressValidator">
<AddressValidatorResult>
<xsd:schema>schema</xsd:schema>xml</AddressValidatorResult>
</AddressValidatorResponse>
</soap:Body>
</soap:Envelope>
SXMB_MONI showing(Response):
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:AddressValidatorResponse xmlns:ns0="http://tempuri.org/geostan3/AddressValidator">
- <ns0:AddressValidatorResult>
<ns1:schema xmlns:ns1="http://www.w3.org/2001/XMLSchema" />
</ns0:AddressValidatorResult>
</ns0:AddressValidatorResponse>
So my question is how do I map response fields to RFC response? Auctully this schema is like table structure which is having all response fields.
I could see all response structure with data in sxmb_moni-->Response Msg ID > inbound message>payloads(main document). Is there any way to send this response to RFC ?
or can you suggest me any other way to send this response to RFC.
Thanks,
Edited by: PILearn on Jun 2, 2008 10:21 PMHere you go..
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://tempuri.org/geostan3/AddressValidator" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="http://tempuri.org/geostan3/AddressValidator" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
<s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/geostan3/AddressValidator">
<s:import namespace="http://www.w3.org/2001/XMLSchema" />
<s:element name="AddressValidator">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="LicenseFile" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="LicensePassword" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="SearchPath" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Z9Path" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="House" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Street" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="AddLine2" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="AddLastLine" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="URB" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Matchmode" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Datum" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="AddressValidatorResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="AddressValidatorResult">
<s:complexType>
<s:sequence>
<s:element ref="s:schema" />
<s:any />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="DataSet" nillable="true">
<s:complexType>
<s:sequence>
<s:element ref="s:schema" />
<s:any />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="AddressValidatorSoapIn">
<wsdl:part name="parameters" element="tns:AddressValidator" />
</wsdl:message>
<wsdl:message name="AddressValidatorSoapOut">
<wsdl:part name="parameters" element="tns:AddressValidatorResponse" />
</wsdl:message>
<wsdl:message name="AddressValidatorHttpGetIn">
<wsdl:part name="LicenseFile" type="s:string" />
<wsdl:part name="LicensePassword" type="s:string" />
<wsdl:part name="SearchPath" type="s:string" />
<wsdl:part name="Z9Path" type="s:string" />
<wsdl:part name="House" type="s:string" />
<wsdl:part name="Street" type="s:string" />
<wsdl:part name="AddLine2" type="s:string" />
<wsdl:part name="AddLastLine" type="s:string" />
<wsdl:part name="URB" type="s:string" />
<wsdl:part name="Matchmode" type="s:string" />
<wsdl:part name="Datum" type="s:string" />
</wsdl:message>
<wsdl:message name="AddressValidatorHttpGetOut">
<wsdl:part name="Body" element="tns:DataSet" />
</wsdl:message>
<wsdl:message name="AddressValidatorHttpPostIn">
<wsdl:part name="LicenseFile" type="s:string" />
<wsdl:part name="LicensePassword" type="s:string" />
<wsdl:part name="SearchPath" type="s:string" />
<wsdl:part name="Z9Path" type="s:string" />
<wsdl:part name="House" type="s:string" />
<wsdl:part name="Street" type="s:string" />
<wsdl:part name="AddLine2" type="s:string" />
<wsdl:part name="AddLastLine" type="s:string" />
<wsdl:part name="URB" type="s:string" />
<wsdl:part name="Matchmode" type="s:string" />
<wsdl:part name="Datum" type="s:string" />
</wsdl:message>
<wsdl:message name="AddressValidatorHttpPostOut">
<wsdl:part name="Body" element="tns:DataSet" />
</wsdl:message>
<wsdl:portType name="AddressCheckSoap">
<wsdl:operation name="AddressValidator">
<wsdl:input message="tns:AddressValidatorSoapIn" />
<wsdl:output message="tns:AddressValidatorSoapOut" />
</wsdl:operation>
</wsdl:portType>
<wsdl:portType name="AddressCheckHttpGet">
<wsdl:operation name="AddressValidator">
<wsdl:input message="tns:AddressValidatorHttpGetIn" />
<wsdl:output message="tns:AddressValidatorHttpGetOut" />
</wsdl:operation>
</wsdl:portType>
<wsdl:portType name="AddressCheckHttpPost">
<wsdl:operation name="AddressValidator">
<wsdl:input message="tns:AddressValidatorHttpPostIn" />
<wsdl:output message="tns:AddressValidatorHttpPostOut" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="AddressCheckSoap" type="tns:AddressCheckSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
<wsdl:operation name="AddressValidator">
<soap:operation soapAction="http://tempuri.org/geostan3/AddressValidator/AddressValidator" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="AddressCheckHttpGet" type="tns:AddressCheckHttpGet">
<http:binding verb="GET" />
<wsdl:operation name="AddressValidator">
<http:operation location="/AddressValidator" />
<wsdl:input>
<http:urlEncoded />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="AddressCheckHttpPost" type="tns:AddressCheckHttpPost">
<http:binding verb="POST" />
<wsdl:operation name="AddressValidator">
<http:operation location="/AddressValidator" />
<wsdl:input>
<mime:content type="application/x-www-form-urlencoded" />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="AddressCheck">
<wsdl:port name="AddressCheckSoap" binding="tns:AddressCheckSoap">
<soap:address location="http://sap-ccs-geo02/geostan3/AddressValidator.asmx" />
</wsdl:port>
<wsdl:port name="AddressCheckHttpGet" binding="tns:AddressCheckHttpGet">
<http:address location="http://sap-ccs-geo02/geostan3/AddressValidator.asmx" />
</wsdl:port>
<wsdl:port name="AddressCheckHttpPost" binding="tns:AddressCheckHttpPost">
<http:address location="http://sap-ccs-geo02/geostan3/AddressValidator.asmx" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions> -
Issue while importing the WSDL file in the External Definitions - PI 7.0
Dear all Experts
After importing the WSDL file in the external External Definitions we are not able to view the " name and namespace " in the messages tab.
Request you to advise on the issue.
We are using the PI 7.0
Regards
Machindra PatadeDear All
Got the answer"
The problem is in the namespace description LENGTH,
Note the following restrictions for XI or PI installations:
· Maximum length of repository namespaces and XML namespaces: 60 Characters. Due to this restriction, the import of XSD files and WSDL files prepares difficulties as an external definition; you can solve these difficulties using Note 901988.
· Maximum length of object names in the Integration Repository and Integration Directory: 120 characters
As of SAP NetWeaver Process Integration 7.10 Support Package 7, the enhancement of the maximum length of namespaces to 255 is supported in the configuration and runtime.
Please check the below SAP 2 notes in regards to above mail.
SAP Note 901988 - Integration Builder: Namespace of external definitions
SAP Note 870809 - Integration Builder: Length of namespaces and object names
Maybe you are looking for
-
Get all rows from a table control
Hi All, I have a table control with one column. What function should I use to retrieve all the rows ? Do I need to iterate row by row and read each row or is it possible to do it in one function ? Thanks, Kanu Solved! Go to Solution.
-
Migrating HBR Sequences into 11.1.2.x as Rule Sets
Hi, has anyone been able to migrate sequences into Calc Manager? With the method I'm trying, Calc Manager recognizes the rules and variables in the sequence(s) (will skip then when the Skip option selected), but the rule set does not appear (verifie
-
trying to update 2 ipods but when I go through the process it says "The ipod software update server could not be contacted" "Network connection could not be established". One of the ipods is locked and I don't remember password.
-
Firefox 9.0.1 with Flash player not catch keyboard event with mouse click.
In a flash application, I need select mutil items using shite key and mouse click, it is not working. looks like firefox didn't pass the keyboard even alone with the click event. This happen on Window 7, IE and Chrome have no problem. only FF
-
File opens in html editor automatically
Hi Guys, maybe one of you came across the same problem before and knows a trick how to solve it: I want to edit several html files stored in the KM but for some reason some of them are opened automatically in the html editor. I do not even get the se