Help required in xml to xml Mapping

Hi guys,
While performing mapping between two message types, where my input message type looks like..
<?xml version="1.0" encoding="UTF-8"?>
<DATA>
<FNAME>
<LNAME>
<DATA>
and I'm using both the FNAME and LNAME nodes in the output file.
Here If I'm giving the input file format as...
<?xml version="1.0" encoding="UTF-8"?>
<DATA>
<FNAME>Varun</FNAME>
<DATA>
This is without the LNAME tag...
I want to know, how can I assign a blank value to my output file structure for this particular tag???
I tried using a custom mapping with the code written below, but it didn't work
public String matchFields(String a,Container container){
   //write your code here
String output;
if(a""l)
output = "";     
else
output = a;
return output;
Please help me on this guys....Plzzz
Regards
Varun

Hi,
use it like this if Fname equals constnat[space] then pass the Constant[space] to Fname else value of Fname as under
................................Constant[]------>
FNAME.............................................Then
>Equals....................................IF -
>FNAME
Constant[].........................................ELSE
.......................................FNAME---->   
Constant[]    = Constant [ Space ]
Sachin

Similar Messages

  • Node Function help required in XML message mapping !!

    Hi Brilliants,
    Source Message
        <ROOT>               0..1   
          <OUTPUT>          0..n
             <Group_N1>           0..n     <Header>
                <H02_N1_DTM>                           0..1
          DTM_Y2K_DATE     0..1
             <Group_LIN>          0..n                <Lin Item>
         <Group_ZA>          0..n
              <D02_ZA>     0..n
          </OUTPUT>
    </ROOT>
    The above Source <OUTPUT> tag comes 2 times. In this two time, Header comes once per header and more than 50 times Lin item occurs.
    Target Message
    ProductActivityNotification                                                            0..n
         ProductActivity                                                       1..1
              Item                                                       1..unbound  (Lin Item level on target side)
                 SalesTimeSeries                  0..1
                          Item                                           1..unbound
                        ValidityPeriod              1..1
                        StartDate              0..1
                        EndDate              0..1
    The above source message Lin item, whatever the times it replicates, the same number of times u201CItemu201D tag has to occur and DTM_Y2K_DATE value has to pass to StartDate.
    Could anybody please put your valuable idea on this? I suppose to deliver this interface tomorrow.
    I will highly appreciate your intellectual ability.
    Many Thanks in Advance
    Kind Regards
    San

    HI San,
    Based on your this post, i think u want like this way...
    How many times from source  DTM_Y2K_DATE  or <LinItem>(because DTM_Y2K_DATE   in LinItem ) occurs that many of <Item> in target is required rt??
    Then u map like,
    DTM_Y2K_DATE  (Change context to LineItem(right clich and choose context)) and map  to LineItem of target.
    and also now map directly from DTM_Y2K_DATE  to Start Date(Dont change any context now..)
    If still nt clear do post..
    Babu

  • Help required on XML format for Sourcing system

    Hi All,
    We are Integrating PI with SAP Sourcing and Sourcing is expecting the XML in below structure.
    XML Required by the target system:
    <?xml version="1.0" encoding="UTF-8"?>
    <sapesourcing defaultlanguage="" xsi:noNamespaceSchemaLocation="Locations.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
          <objects>
    <object classname="">
                <fields>
    Field1....n
                </fields>
            </object>
          </objects>
    </sapesourcing>
    I have converted the XML in to XSD and imported in to PI, but I have no idea how to Populate the tag as it required by Sourcing system
    tag must be required by sourcing system is:
    "<sapesourcing defaultlanguage="" xsi:noNamespaceSchemaLocation="Locations.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    Mapping generates below tag :
    <?xml version="1.0" encoding="UTF-8"?>
    <sapesourcing defaultlanguage="">  ........
    Regards,
    Mani

    Hi Mani,
    Try to add the xml tag using XSLT mapping.  Go through with the below link.
    add Namespace in message mapping | SCN
    Thanks,
    Satish.

  • I am trying to open a document I saved on a previous version of Pages, but ever since I updated, I get a message: "couldn't be opened: the required index.xml file is missing". Can anyone help me here?

    I am trying to open a document I saved on a previous version of Pages, but ever since I updated, I get a message: "couldn't be opened: the required index.xml file is missing". Can anyone help me here?

    Check this thread with possible answer from PeterBreis
    Pages & Mavericks - "The required index.xml file is missing."
    What can I do to open a pages file she I get this message"the required index.xml file is missing" ?

  • Help require to get the XML output to design template- JDE

    Hi Friends,
    I am asking this question from JDE perspective.I want to design XMLP Template for R40572 Check Printing.
    When I upload an blank template and after attaching RD, When ever I initiate a check from P04572 Application.RThe Write Row exit will lead to check printing which in turn will call a batch R04571 and this batch will call R04572(Which I require the XML output) since it is the second report and we cant direct it to local server I am not able to get the XML output..
    Another think is since its running in server i think its not taking the RD modification we done in loacl because it always fires PDF .

    Hi,
    I assume you're Using XMPOSA for generating the files locally. What I suggest is, you set the application to run with the report definition by default. That way, even when it is called, it will be called along with the report definition. You can take the resultant XML file from P95630
    hope this helps,
    -Domnic

  • Xcelsius Dashboard on SAP R/3 Table using BSP and XML Mapping

    Hi Experts,
    I have developed a simple dashboard on small data set (10 records) that I am fetching from a R/3 Table into BSP and generating XML from there and consuming it in Xcelsius (SAP R/3 + BSP + XML Mapping).
    Now I want to fetch data based on Variables values that should be passed from the dashboard at the runtime and should display the data  accordingly. Any help on how it can be achieved?
    Thanks..!!
    Sharad

    Hi,
    You could try doing this by using XML data connection. You would have to make use of Enable load to get the data from XML and Enable send to send data back to XML from dashboard.
    This would require you to write a script.
    Thanks,
    Amit

  • XSLT mapping Help Required.

    XSLT mapping Help Required.
    Hi Experts,
    I am New to XSLT Mapping. I am practising the below Example:
    InputXML File:
    <?xml version="1.0" encoding="UTF-8"?>
    <?xml-stylesheet type="text/xsl" href="Persons111.xsl"?>
    <ns0:MT_XSLT_Source xmlns:ns0="http://XYZ.com/gen">
    <Person>
    <FirstName>Anshul</FirstName>
    <LastName>Chowdhary</LastName>
    <Gender>Male</Gender>
    <Address>
    <Street>2nd Main</Street>
    <Houseno>83/b</Houseno>
    <City>Mysore</City>
    </Address> </Person>
    </ns0:MT_XSLT_Source>
    XSL StyleSheet File:
    <?xml version='1.0' encoding="UTF-8"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns0="http://XYZ.com/Gen"
    Xmlns:ns1=”http://XYZ.com/Test”>
    <xsl:template match="/">
    <ns1:MT_XSLT_Target>
    <Title> <xsl:value-of select="ns0:MT_XSLT_Source/Person/Gender"/> </Title>
    <Name> <xsl:value-of select="concat(concat(ns0:MT_XSLT_Source/Person/FirstName,' '), ns0:MT_XSLT_Source/Person/LastName)"/>
    </Name>
    <Street> <xsl:value-of select="concat(concat(ns0:Mt_XSLT_Source/Person/Address/Houseno,' '),
    ns0:Mt_XSLT_Source/Person/Address/Street)"/> </Street>
    <City> <xsl:value-of select="ns0:Mt_XSLT_Source/Person/Address/City"/> </City>
    </ns1:MT_XSLT_Target>
    </xsl:template>
    </xsl:stylesheet>
    The Desired Output shuold be:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns1:MT_XSLT_Target xmlns:ns1="http://XYZ.com/Test">
    <Title>Male</Title>
    <Name>Anshul Chowdhary</Name>
    <Street>83/b 2nd Main</Street>
    <City>Mysore</City>
    </ns1:MT_XSLT_Target>
    I have refered the xsl in xml and i am getting the below Oupt in a Single line like this:
    Anshul Chowdhary Male 2nd Main 83/b Mysore
    I am Unable to display in Target XML Fomrat as shown above. Please check and do the needful.
    Regards,
    GIRIDHAR

    Hi,
    I have used below for testing.
    Input xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <?xml-stylesheet type="text/xsl" href="Persons111.xsl"?>
    <ns0:MT_XSLT_Source xmlns:ns0="http://XYZ.com/gen">
    <Person>
    <FirstName>Anshul</FirstName>
    <LastName>Chowdhary</LastName>
    <Gender>Male</Gender>
    <Address>
    <Street>2nd Main</Street>
    <Houseno>83/b</Houseno>
    <City>Mysore</City>
    </Address> </Person>
    </ns0:MT_XSLT_Source>
    xsl code:
    <?xml version='1.0' encoding="UTF-8"?> 
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns0="http://XYZ.com/gen" 
        xmlns:ns1="http://XYZ.com/Test"> 
        <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/> 
        <xsl:template match="/"> 
            <ns1:MT_XSLT_Target> 
                <Title> <xsl:value-of select="ns0:MT_XSLT_Source/Person/Gender"/> </Title> 
                <Name> <xsl:value-of select="concat(concat(ns0:MT_XSLT_Source/Person/FirstName,' '), ns0:MT_XSLT_Source/Person/LastName)"/> 
                </Name> 
                <Street> <xsl:value-of select="concat(concat(/ns0:MT_XSLT_Source/Person/Address/Houseno,' '), 
                    /ns0:MT_XSLT_Source/Person/Address/Street)"/> </Street> 
                <City> <xsl:value-of select="/ns0:MT_XSLT_Source/Person/Address/City"/> </City> 
            </ns1:MT_XSLT_Target> 
        </xsl:template> 
    </xsl:stylesheet>
    For testing in PI ,change the extension from .txt to .xsl and zip it and upload into PI as an imported archive .
    Regards
    Venkat

  • Need Help on complex XML loading into ODI

    Hi,
    I have a requirement in which i have to create xml mapping in ODI which should load 30 to 40 million message per day with file size of 30 MB. I have created xml connection in topology manager and have provided xsd path of unix server and it's working but when I try to reverse xml structure into Designer model then it gave me error " java.sql.SQLException: No DTD found and no XML file provided: the XML schema cannot be created". I have used below xml connection detail in topology manager.
    JDBC Driver: com.sunopsis.jdbc.driver.xml.SnpsXmlDriver
    jdbc:snps:xml?f=/odi_rep/sita_meg_bi/etl_metadata/&stypex.xsd&re=TYPEX&ro=true&case_sens=true
    We are using 10.1.3.6 ODI version in this project.I have given below xsd and xml file format. FYI...we recevie multiple message with same strucutre in xml source file.
    XSD File:
    XML File :
    <tns1:MessageTraceEvent xmlns_tns1="http://www.sita.aero/csbu/tools/v1/namespace" timeStamp="2011-07-13T00:01:09Z" priority="3" envelopeMessageID="xs-atl-xs2011-07-13t00:01:09.525:519160" mes
    sageType="TYPEX" messageTotalSize="6506" systemID="bgtxjao">
         <tns1:SitaIdentifiers>
              <tns1:sitaUID>xPreg1D3RF2tGbF9iUPReA</tns1:sitaUID>
              <tns1:TransactionID>dzA5Arb0QZyOOq9NqgrQ2Q</tns1:TransactionID>
         </tns1:SitaIdentifiers>
         <tns1:previousSitaIdentifiers>
              <tns1:sitaUID>xPreg1D3RF2tGbF9iUPReA</tns1:sitaUID>
              <tns1:TransactionID>zrL7EtGpTVSYeLpb+2W1NQ</tns1:TransactionID>
         </tns1:previousSitaIdentifiers>
         <tns1:Addresses>
              <tns1:Originator>XS-ATL-XS</tns1:Originator>
              <tns1:Recipient>AF-QVI-BP</tns1:Recipient>
              <tns1:Recipient>AF-QVI-BP</tns1:Recipient>
         </tns1:Addresses>
         <tns1:RemoteSystem>
              <tns1:Source>
                   <tns1:NodeID>AF-QVI-BP</tns1:NodeID>
                   <tns1:MiscData>BadgerID: XS-ATL-XS-1310515269-9.1</tns1:MiscData>
                   <tns1:isCustomer>false</tns1:isCustomer>
              </tns1:Source>
         </tns1:RemoteSystem>
         <tns1:AdditionalData>
              <tns1:TypeXData subject="No message"/>
         </tns1:AdditionalData>
         <tns1:Payload payloadType="MessageData">PHR4bWU6VFhNX0VudmVsb3BlIHhtbG5zOnR4bWU9Imh0dHA6Ly93d3cuaWF0YS5vcmcvdHhtL2VudmVsb3BlIiB4bWxuczp0eG1zPSJodHRwOi8vd3d3LmlhdGEub3JnL3R4bS9zZXNzaW9
    uIiB4bWxuczp0eG1tPSJodHRwOi8vd3d3LmlhdGEub3JnL3R4bS9tc2doZWFkZXIiIHhtbG5zOnR4bWM9Imh0dHA6Ly93d3cuaWF0YS5vcmcvdHhtL2NvbW1hbmQiIHhtbG5zOnR4bXg9Imh0dHA6Ly93d3cuaWF0YS5vcmcvdHhtL3hhdGFwIiB4bWxucz
    p0eG1mPSJodHRwOi8vd3d3LmlhdGEub3JnL3R4bS9mYXVsdCIgeG1sbnM6dHhtcj0iaHR0cDovL3d3dy5pYXRhLm9yZy90eG0vcmVwb3J0IiB4bWxuczp0eG11PSJodHRwOi8vd3d3LmlhdGEub3JnL3R4bS9hdXRoIiB4bWxuczp0eG1hPSJodHRwOi8vd
    3d3LmlhdGEub3JnL3R4bS9hdHRh
    pc3Rvcnk+PC93dHI6QklSX0RlbGF5ZWRCYWdSZWNvcmQ+CgkJPC90eG1lOlRYTV9QYXlsb2FkPgoJPC90eG1lOlRYTV9Cb2R5Pgo8L3R4bWU6VFhNX0VudmVsb3BlPgo=</tns1:Payload>
    </tns1:MessageTraceEvent>
    Edited by: user13544580 on Jul 18, 2011 6:27 AM

    <?xml version="1.0" encoding="UTF-8"?>
    <!-- edited with XMLSpy v2010 rel. 3 sp1 (http://www.altova.com) by SITA (SITA) -->
    XSD File :
    <xs:schema xmlns:tns1="http://www.sita.aero/csbu/tools/v1/namespace" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://www.sita.aero/csbu/tools/v1" targetNamespace="http://www.sita.aero/csbu/tools/v1/namespace" elementFormDefault="qualified" attributeFormDefault="unqualified" version="version 1.0">
         <xs:element name="MessageTraceEvent">
              <xs:annotation>
                   <xs:documentation>version 1.0</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="SitaIdentifiers" type="tns1:SitaIdType">
                             <xs:annotation>
                                  <xs:documentation>Container for Sita Unique ID and Transaction ID</xs:documentation>
                             </xs:annotation>
                        </xs:element>
                        <xs:element name="previousSitaIdentifiers" type="tns1:SitaIdType" minOccurs="0" maxOccurs="unbounded">
                             <xs:annotation>
                                  <xs:documentation>Container for previous Sita Unique IDs and Transaction IDs</xs:documentation>
                             </xs:annotation>
                        </xs:element>
                        <xs:element name="relatedSitaIdentifiers" type="tns1:SitaIdType" minOccurs="0" maxOccurs="unbounded">
                             <xs:annotation>
                                  <xs:documentation>Container for related Sita Unique IDs and Transaction IDs which a delivery report is reporting</xs:documentation>
                             </xs:annotation>
                        </xs:element>
                        <xs:element name="Addresses">
                             <xs:annotation>
                                  <xs:documentation>Container for Sender and Recipient addresses</xs:documentation>
                             </xs:annotation>
                             <xs:complexType>
                                  <xs:sequence>
                                       <xs:element name="Originator" type="tns1:AddressType" minOccurs="0"/>
                                       <xs:element name="Recipient" type="tns1:AddressType" minOccurs="0" maxOccurs="unbounded"/>
                                  </xs:sequence>
                             </xs:complexType>
                        </xs:element>
                        <xs:element name="RemoteSystem">
                             <xs:annotation>
                                  <xs:documentation>Container for Source or Destination system information</xs:documentation>
                             </xs:annotation>
                             <xs:complexType>
                                  <xs:choice>
                                       <xs:element name="Source" type="tns1:HostType"/>
                                       <xs:element name="Destination" type="tns1:HostType"/>
                                  </xs:choice>
                             </xs:complexType>
                        </xs:element>
                        <xs:element name="AdditionalData" minOccurs="0">
                             <xs:annotation>
                                  <xs:documentation>Service or Billing specific information</xs:documentation>
                             </xs:annotation>
                             <xs:complexType>
                                  <xs:choice>
                                       <xs:element name="AFTNData" type="tns1:AFTNDataType" minOccurs="0">
                                            <xs:annotation>
                                                 <xs:documentation>Addintinal data gathered on NTS </xs:documentation>
                                            </xs:annotation>
                                       </xs:element>
                                       <xs:element name="TypeBData" type="tns1:TypeBDataType" minOccurs="0">
                                            <xs:annotation>
                                                 <xs:documentation>Additional data gathered on MegaSwitch, Sitex or Badgers</xs:documentation>
                                            </xs:annotation>
                                       </xs:element>
                                       <xs:element name="TypeXData" type="tns1:TypeXDataType" minOccurs="0">
                                            <xs:annotation>
                                                 <xs:documentation>Additional data gathered on Badgers</xs:documentation>
                                            </xs:annotation>
                                       </xs:element>
                                       <xs:element name="SMTPData" type="tns1:SMTPDataType" minOccurs="0">
                                            <xs:annotation>
                                                 <xs:documentation>Additional data gathered on SMTP systems</xs:documentation>
                                            </xs:annotation>
                                       </xs:element>
                                       <xs:element name="FAXData" type="tns1:FAXDataType" minOccurs="0">
                                            <xs:annotation>
                                                 <xs:documentation>Additional data gathered on Fax systems</xs:documentation>
                                            </xs:annotation>
                                       </xs:element>
                                       <xs:element name="OmhData" type="tns1:OmhDataType" minOccurs="0">
                                            <xs:annotation>
                                                 <xs:documentation>Additional data gathered on OmhData systems</xs:documentation>
                                            </xs:annotation>
                                       </xs:element>
                                  </xs:choice>
                             </xs:complexType>
                        </xs:element>
                        <xs:element name="Payload" minOccurs="0" maxOccurs="unbounded">
                             <xs:annotation>
                                  <xs:documentation>Used to save the full message as received from customer, it can help us avoid re-transforming it back to original message or be used for debugging</xs:documentation>
                             </xs:annotation>
                             <xs:complexType>
                                  <xs:simpleContent>
                                       <xs:extension base="xs:base64Binary">
                                            <xs:attribute name="payloadType">
                                                 <xs:simpleType>
                                                      <xs:restriction base="xs:string">
                                                           <xs:enumeration value="MessageData"/>
                                                           <xs:enumeration value="EnvelopeData"/>
                                                      </xs:restriction>
                                                 </xs:simpleType>
                                            </xs:attribute>
                                       </xs:extension>
                                  </xs:simpleContent>
                             </xs:complexType>
                        </xs:element>
                   </xs:sequence>
                   <xs:attribute name="timeStamp" type="xs:dateTime" use="required"/>
                   <xs:attribute name="priority" type="xs:string" use="optional">
                        <xs:annotation>
                             <xs:documentation>Priority defines precedence in sending the messages through to destination</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
                   <xs:attribute name="bodyMessageID" type="xs:string" use="optional">
                        <xs:annotation>
                             <xs:documentation>The Message ID in the body, as received from or sent to the customer.</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
                   <xs:attribute name="envelopeMessageID" type="xs:string" use="optional">
                        <xs:annotation>
                             <xs:documentation>The Message ID in the envelope, as received from or sent to the customer.</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
                   <xs:attribute name="isReport" type="xs:boolean" use="optional" default="false">
                        <xs:annotation>
                             <xs:documentation>Is it a delivery or acknowledge report? If so, set it true</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
                   <xs:attribute name="messageType" type="tns1:MessageType" use="required">
                        <xs:annotation>
                             <xs:documentation>The type of message, e.g. TYPEB, TYPEX, SMS, etc.</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
                   <xs:attribute name="previousMessageType" type="tns1:MessageType" use="optional">
                        <xs:annotation>
                             <xs:documentation>The logical message type, where this is different from the physical type. For example a TYPEB message sent to SMTP would have a messageType of SMTP, but previousMessageType of TYPEB.</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
                   <xs:attribute name="messageBodySize" type="xs:string" use="optional"/>
                   <xs:attribute name="messageHeadSize" type="xs:string" use="optional"/>
                   <xs:attribute name="messageTotalSize" type="xs:string" use="optional"/>
                   <xs:attribute name="PDM" type="xs:boolean" use="optional">
                        <xs:annotation>
                             <xs:documentation>True if it is a PDM message.</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
                   <xs:attribute name="messsageArchive" type="xs:boolean" use="optional">
                        <xs:annotation>
                             <xs:documentation>True if the message has been flagged for archiving.</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
                   <xs:attribute name="messageArchiveDays" type="xs:int" use="optional">
                        <xs:annotation>
                             <xs:documentation>The number of days to archive, if known.</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
                   <xs:attribute name="systemID" type="xs:string" use="required">
                        <xs:annotation>
                             <xs:documentation>The unique identifier for the system executing the transaction, e.g. BADGERX, JAOMSW, etc.</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
              </xs:complexType>
         </xs:element>
         <xs:simpleType name="MessageType">
              <xs:restriction base="xs:string">
                   <xs:enumeration value="AFTN"/>
                   <xs:enumeration value="FAX"/>
                   <xs:enumeration value="SMTP"/>
                   <xs:enumeration value="TYPEC"/>
                   <xs:enumeration value="TYPEB"/>
                   <xs:enumeration value="TYPEX"/>
                   <xs:enumeration value="SMS"/>
                   <xs:enumeration value="X400"/>
                   <xs:enumeration value="SKYFAX"/>
                   <xs:enumeration value="OTHER"/>
                   <xs:enumeration value="TELEX"/>
                   <xs:enumeration value="URI"/>
                   <xs:enumeration value="EDI"/>
                   <xs:enumeration value="EDI-X12"/>
                   <xs:enumeration value="EDI-EDIFACT"/>
                   <xs:enumeration value="EDI-BINARY"/>
                   <xs:enumeration value="EDI-XML"/>
                   <xs:enumeration value="SPEC2000"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="EventType">
              <xs:restriction base="xs:string">
                   <xs:enumeration value="MessageAccepted"/>
                   <xs:enumeration value="MessageDispatched"/>
                   <xs:enumeration value="MessageRejected"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="TypeBPriority">
              <xs:restriction base="xs:string">
                   <xs:enumeration value="AF"/>
                   <xs:enumeration value="NO"/>
                   <xs:enumeration value="OK"/>
                   <xs:enumeration value="QA"/>
                   <xs:enumeration value="QB"/>
                   <xs:enumeration value="QC"/>
                   <xs:enumeration value="QD"/>
                   <xs:enumeration value="QK"/>
                   <xs:enumeration value="QN"/>
                   <xs:enumeration value="QP"/>
                   <xs:enumeration value="QQ"/>
                   <xs:enumeration value="QU"/>
                   <xs:enumeration value="QX"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="FaxServiceName">
              <xs:restriction base="xs:string">
                   <xs:enumeration value="IPFax"/>
                   <xs:enumeration value="BFax"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="MessageStatusType">
              <xs:restriction base="xs:string">
                   <xs:enumeration value="failed"/>
                   <xs:enumeration value="relayed"/>
                   <xs:enumeration value="received"/>
                   <xs:enumeration value="delivered"/>
                   <xs:enumeration value="rejected"/>
                   <xs:enumeration value="re-injected"/>
                   <xs:enumeration value="intercepted"/>
                   <xs:enumeration value="drained"/>
                   <xs:enumeration value="op-dropped">
                        <xs:annotation>
                             <xs:documentation>message dropped by an operator</xs:documentation>
                        </xs:annotation>
                   </xs:enumeration>
                   <xs:enumeration value="sys-dropped">
                        <xs:annotation>
                             <xs:documentation>message dropped by the messaging system</xs:documentation>
                        </xs:annotation>
                   </xs:enumeration>
                   <xs:enumeration value="odmci">
                        <xs:annotation>
                             <xs:documentation>out of date message cancellation input</xs:documentation>
                        </xs:annotation>
                   </xs:enumeration>
                   <xs:enumeration value="odmco">
                        <xs:annotation>
                             <xs:documentation>out of date message cancellation output</xs:documentation>
                        </xs:annotation>
                   </xs:enumeration>
                   <xs:enumeration value="other"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:complexType name="AFTNDataType">
              <xs:attribute name="isDataCollect" type="xs:boolean" use="optional">
                   <xs:annotation>
                        <xs:documentation>To determine a Type B traffic chargeable</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="messageIdentifier" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="SMI" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>Standard message identifier for Type B messages</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="doubleSignature" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="BATAPSN" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The BATAPSN number of a message</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="ISN" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The ISN number of a message</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
         </xs:complexType>
         <xs:complexType name="TypeBDataType">
              <xs:attribute name="isDataCollect" type="xs:boolean" use="optional">
                   <xs:annotation>
                        <xs:documentation>To determine a Type B traffic chargeable</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="messageIdentifier" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="SMI" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>Standard message identifier for Type B messages</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="doubleSignature" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="eopt" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>eopt is 10 numeric characters long and the value is always 0000000000, Eric indicated his team does not populate any value in this field. </xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="documentConversion" type="xs:boolean" use="optional"/>
              <xs:attribute name="subject" type="xs:string" use="optional"/>
              <xs:attribute name="charSet" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The character set of a message body</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="BATAPSN" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The BATAPSN number of a message</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="ISN" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The ISN number of a message</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="cnxType" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The connection Type of a message</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="Location" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The location of a connection coming from</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
         </xs:complexType>
         <xs:complexType name="SMTPDataType">
              <xs:attribute name="subject" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="doubleSignature" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="rule" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="resend" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
         </xs:complexType>
         <xs:complexType name="TypeXDataType">
              <xs:attribute name="messageIdentifier" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="doubleSignature" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="documentConversion" type="xs:boolean" use="optional"/>
              <xs:attribute name="subject" type="xs:string" use="optional"/>
              <xs:attribute name="XATAPSN" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The XATAPSN number of a message</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="BadgerId" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The BadgerId to a Type X message is what ISN to a Type B message</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
         </xs:complexType>
         <xs:complexType name="FAXDataType">
              <xs:attribute name="errorCode" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>Error code for the request. 0=success.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="errorString" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The error message, if any.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="serviceName" type="tns1:FaxServiceName" use="optional">
                   <xs:annotation>
                        <xs:documentation>Enum value in FaxServiceType</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="channelNumber" type="xs:int" use="optional">
                   <xs:annotation>
                        <xs:documentation>The fax channel on the server.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="receivedSize" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The size of the received message, including headers.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="convertedSize" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The size of the message after conversion for fax.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="totalSentSize" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The sum of the bytes sent, including cover pages and retries.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="totalConnectTime" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The sum of time connected to a fax receiver for all attempts.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="totalDuration" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The sum of the off-hook, or network time, for all attempts.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="nbrFaxPages" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The number of pages in the message, including the cover sheet.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="totalPages" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The sum of the pages sent for all attempts.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="recvCSID" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The CSID received from the remote fax system.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="tries" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The number of fax attmpts.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="subject" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="acknow" type="xs:string" use="optional"/>
              <xs:attribute name="cod" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="referenceNumber" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The UFAX MSG_ID for the message.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="distID" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The UFAX MSG_RQ_ID for the message.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="fineResolution" type="xs:boolean" use="optional">
                   <xs:annotation>
                        <xs:documentation>True for Fine resolution, false for Coarse resolution.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="baudRate" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The connection speed for the fax.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="sitaReceiveTime" type="xs:dateTime" use="optional">
                   <xs:annotation>
                        <xs:documentation>The time when the message is received into SITA's network.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="ufaxReceiveTime" type="xs:dateTime" use="optional">
                   <xs:annotation>
                        <xs:documentation>The time when UFAX receives the message, when it is delivered to the UFAX inbox.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="startConversionTime" type="xs:dateTime" use="optional">
                   <xs:annotation>
                        <xs:documentation>The time when the Converter starts processing a message. If it takes more than one attempt to convert the message, this will be the time of the first attempt.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="endConversionTime" type="xs:dateTime" use="optional">
                   <xs:annotation>
                        <xs:documentation>The time when the Converter completes the conversion process. If it takes more than one attempt to convert the message, this will be the time of the last attempt.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="tfaTime" type="xs:dateTime" use="optional">
                   <xs:annotation>
                        <xs:documentation>The time of the first call attempt for the message. If UFAX is already calling the fax number for a different message, then this will be the time the message was queued for calling.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="completionTime" type="xs:dateTime" use="optional">
                   <xs:annotation>
                        <xs:documentation>The time when the fax has been completed, either because the fax was delivered or it reached the maximum error threshold.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="reportTime" type="xs:dateTime" use="optional">
                   <xs:annotation>
                        <xs:documentation>The time when the delivery report is sent. Not used if a report isn't sent.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="doubleSignature" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>For BFax, the Double Signature for the message if any.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="userConfigType" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>Legacy bit-mapped field for BFax.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="networkAccessPoint" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The network access point where the channel was connected.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
         </xs:complexType>
         <xs:complexType name="OmhDataType">
              <xs:attribute name="msgIdent" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="sysMsgIdent" type="xs:string" use="required">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
                        <xs:attribute name="inMsgFmt" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="outMsgFmt" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="toDirection" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="fromDirection" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="inMsgSize" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
                        <xs:attribute name="outMsgSize" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="compCode" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="applicationId" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
         </xs:complexType>
         <xs:complexType name="AddressType">
              <xs:annotation>
                   <xs:documentation>This is a generic address object</xs:documentation>
              </xs:annotation>
              <xs:simpleContent>
                   <xs:extension base="xs:string">
                        <xs:attribute name="responsible" type="xs:boolean" use="optional" default="false">
                             <xs:annotation>
                                  <xs:documentation>Used to denote whether the address should be delivered or not, is the node responsible for delivery of this address</xs:documentation>
                             </xs:annotation>
                        </xs:attribute>
                        <xs:attribute name="typeOfAddress" type="tns1:MessageType" use="optional">
                             <xs:annotation>
                                  <xs:documentation>Type of the address we are given</xs:documentation>
                             </xs:annotation>
                        </xs:attribute>
                        <xs:attribute name="mapped" type="xs:boolean" use="optional" default="false">
                             <xs:annotation>
                                  <xs:documentation>Used to denote whether the address is mapped or not</xs:documentation>
                             </xs:annotation>
                        </xs:attribute>
                        <xs:attribute name="masqueraded" type="xs:boolean" use="optional" default="false">
                             <xs:annotation>
                                  <xs:documentation>used to denote if the address is masqueraded, this happens often when messages are pushed through gateways.</xs:documentation>
                             </xs:annotation>
                        </xs:attribute>
                        <xs:attribute name="masqueradedID" type="xs:string" use="optional">
                             <xs:annotation>
                                  <xs:documentation>If the address is masqueraded than this is the place where I can carry the original address</xs:documentation>
                             </xs:annotation>
                        </xs:attribute>
                   </xs:extension>
              </xs:simpleContent>
         </xs:complexType>
         <xs:complexType name="HostType">
              <xs:annotation>
                   <xs:documentation>This is a generic host object</xs:documentation>
              </xs:annotation>
              <xs:sequence>
                   <xs:element name="HostName" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>Hostname of the server</xs:documentation>
                        </xs:annotation>
                        <xs:complexType>
                             <xs:simpleContent>
                                  <xs:extension base="xs:string">
                                       <xs:attribute name="hostType" type="tns1:MessageType" use="optional">
                                            <xs:annotation>
                                                 <xs:documentation>Type of the host such as MQ, JMS, SMTP etc</xs:documentation>
                                            </xs:annotation>
                                       </xs:attribute>
                                  </xs:extension>
                             </xs:simpleContent>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="NodeID" type="xs:string" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>Optional NODE ID goes here</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="HostIP" type="xs:string" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>Service or host IP address of the service</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="HostPort" type="xs:integer" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>Port address of the service</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="url" type="xs:string" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>URL address of the service</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="HostChannel" type="xs:string" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>Channel name of the service</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="ConnectionNumber" type="xs:string" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>the connection number that host is connecttng to.</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="CircuitNumber" type="xs:string" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>This is SITA's CNR</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="DestinationNumber" type="xs:string" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>This is SITA's DNR</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="X25DNA" minOccurs="0" maxOccurs="unbounded">
                        <xs:annotation>
                             <xs:documentation>This is SITA's X25 dan numbers</xs:documentation>
                        </xs:annotation>
                        <xs:simpleType>
                             <xs:restriction base="xs:positiveInteger"/>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="MessageStatus" type="tns1:MessageStatusType" minOccurs="0" maxOccurs="unbounded">
                        <xs:annotation>
                             <xs:documentation>Users can put anything they want here</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="MiscData" type="xs:string" minOccurs="0" maxOccurs="unbounded">
                        <xs:annotation>
                             <xs:documentation>Users can put anything they want here</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="isCustomer" type="xs:boolean">
                        <xs:annotation>
                             <xs:documentation>False if the sender/receiver is a SITA system</xs:documentation>
                        </xs:annotation>
                   </xs:element>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="SitaIdType">
              <xs:sequence>
                   <xs:element name="sitaUID" type="xs:string">
                        <xs:annotation>
                             <xs:documentation>The unique ID assigned to the message by the first receiving system. This ID must be contained in the message.</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="TransactionID" type="xs:string">
                        <xs:annotation>
                             <xs:documentation>An identifier assigned or created for this event. This must be a unique identifier for this message, i.e. the combination of the SitaUID and transaction ID must be unique. This ID must be contained in the message.</xs:documentation>
                        </xs:annotation>
                   </xs:element>
              </xs:sequence>
         </xs:complexType>
    </xs:schema>

  • PAYMUL-XML mapping

    Hi Everyone,
    Can anyone help me where i can get mapping guide for PAYMUL-XML payment file ?

    Hi Krishna,
    You must be referring to XSLT mapping.
    In XSLT, we parse XMl source message and generate outbound structure as required.
    It works based on template and Xpath.
    For that it would be good if you can use somne editors like Altova XML spy.
    You will find many blogs on XSLT mapping.
    After writing XSLT mapping , you need to zip the xsl file(XSLT file has xsl extension) then import that zip file under Imported Archives in IR.
    We normally use XSLT mapping, when graphical mapping becomes more complex.
    As XSLT can easily read, process XML source message which XI has received and produces target structure required by receiver application system.
    We will prefer XSLT when:
    Nested structure: In case of multiple nested structure especially in ccase of IDocs, we use XSLT mapping
    Maintaining the sequence of the input structure: If you want to maintain the sequence of the data fromt he incoming file.
    It would be good if you start doing and you will get better idea about it.
    Ref:
    http://www.w3schools.com/xsl/default.asp
    http://help.sap.com/saphelp_nw04/helpdata/en/83/2200cb50d345c793336d9a1683163e/frameset.htm
    H. Nested structure: In case of multiple nested structure especially in ccase of IDocs, we use XSLT mapping
    2. Maintaining the sequence of the input structure: If you want to maintain the sequence of the data fromt he incoming file.
    Hope this will help.
    Regards,
    Divyesh

  • Excel XML Maps Problem

    When I import a Excel 2003 XLS file with a Excel 2003 XML map defined I can see the data update if I use the refresh buttom on the spreadsheet pane of Xcelsius 2008 but nothing happens when I export the file as a SWF no matter what I set the refresh properties to?
    Also when I bring up the Data > Connections Menu and try to ADD <Excel XML Maps> I do not get a dialog box on the right?  The <Excel XML Maps> shows as an Existing Connection but does no show any information in the right panel?
    Hope someone can help!
    Tom Ebert

    Thanks guys for your responces.
    Here is what I learned.  Xcelsius 2008 does indeed supports Web Services.  When I was exporting my Excel spreadsheets as XML and trying to refer to it in my SWF file it seems that the Excel XML file does not have the required mapping / schema.
    Soooooooo I'm going to work with a friend who actuall understands Web Services and XML.
    Thanks again for your reply...te

  • Multiple connections via xml maps

    I am currently using Engage SP1 version of Xcelsius. (not Engage Server.)
    As noted in other posts, this version of the product does not all allow multiple connections to web services using the connectivity tools built into the Xcelsius development environment.
    However I've found there is no such limit placed on the number of web service connections if you set them up in Excel (as xml mappings) and then import that excel spreadsheet as the model for Xcelsius.
    I've tested this by connecting to three different web services using 3 xml maps in Excel and then importing that excel file as the model for Xcelsius to use.  The xcelsius model worked flawlessly displaying data from all three web services on the dashboard (swf).
    The only limitation I've found is that the excel XML mapping tool doesn't offer a way to feed a value as input for the web service.   In the example all three web services required no input values. 
    They just run when called and return data.    (no parameter required.)
    However my attempts to setup an xml mapping to a web service that requires an input parameter has failed.
    There seems to be no way to feed the web service an input value within Excel.   I realize that may be an Excel support issue, but have found no documentation in the Excel product or websites to explain how to setup the xml map to allow for the input.
    I should note, that i have connected successfully using a web service url that contains the parameter values hard coded (but no successess passing them in from excel at the time of the web service call.)
    If anyone has solved this issue any feedback would be greatly appreciated.
    Edited by: Blake  Dodds on Oct 3, 2008 5:38 PM

    Hi, when you are maping an xml file in excel you have only imported the data that contains the file but not the query, you have to update the file but i dont know if excelsius will allow to reimport the xml in the datasheet when its in a swf format. I have a similar issue because mapping its almost equal to copy the entire data base.
    I am trying to make a web service that contains more that one query and generate the xml in a schema that will be helpfull for me to make a general configuration.
    I have to make 5 or 6 drill downs whit specific information :s and i havent get any response. My limitation its that i have the same version that  you have only one conection but if i can do that web service it will be very helpfulll and i will be using like 500 rows. I dont whant to make it in diferent xcelsius templates because i havent found an alternative to conect the "filters" to each template.
    Second Xcelsius has make a point that its a waste to buy even the engage version but this is what my company whants and i have to use it.
    If you know flash you can do it in a very efficient way, also you need to have a general idea of programing an application.
    I didnt know flash but in this time 2 months have finish the project, the problem its that is not in excelsius >,>. And they what it in excelsius so they can modify the source files (.xlf).
    If i can do the web service i will post it and maybe it can help you. Good luck if you success in your idea.

  • I can't open a file on Pages'09 4.1    I get  window that says "The required index.xml file is missing."  How do I get this file open?

    I have a file that I havel been adding to for years. I opened it a week ago but today I tried and I got the window message
    "the required index.xml file is missing"  How do I get this to open?
    I have Pages '09  4.1  Not sure when that was put on or updated.
    Thanks for any help you can give
    Teacher72

    http://www.freeforum101.com/iworktipsntrick/viewtopic.php?t=308&mforum=iworktips ntrick
    Are you sure you haven't upgraded Pages on your Mac to Pages 5?
    Check your Applications folder and the Applications/iWork folder. You may have 2 versions on your Mac.
    Peter

  • Does Jabber for Mac 9.2.1 require jabber-xml.config?

    Hello,
    Does anybody know if new Jabber for Mac version 9.2.1 require a jabber-xml config file?
    Users with this new version are complaining that they can't search on the directory and that usernames are not showing correctly on the contact list (they just see the username@domain instead).
    Jabber for mac version 8.x works correctly as it has been doing for a while.
    Regards.

    Yes, the latest release along with the feature regression, requires the .xml file
    Global configuration files
    Global configuration files apply to all Cisco Jabber for Mac users. Cisco Jabber for Mac downloads the global configuration file from your TFTP server during the login sequence.
    The default name for the global configuration file is jabber-config.xml.
    http://www.cisco.com/en/US/partner/docs/voice_ip_comm/jabber/mac/9.2.1/JABM_BK_CB0ACEBC_00_cisco-jabber-for-mac-installation_chapter_010.html
    HTH
    java
    if this helps, please rate
    www.cisco.com/go/pdihelpdesk

  • HT202879 How do I fix "the required index.xml file is missing?" when opening Pages documents?

    I can't open any documents from my son's iPad.  Error message: the required index.xml file is missing.  How do I fix this error so that I can open his Pages documents?  Before I ran the latest update as prompted when I opened Pages, I WAS able to open and view the document.
    I did try restoring Pages using my Time Machine, but it still won't open the Pages document.
    I have a brand new iMac that I just set up last week. 
    Son uses iPad at school, so we update when the school asks him to update.  Will doublecheck his version of Pages but it should be pretty recent.
    In general I don't like using Pages because it lacks a lot of the backwards / forwards compatibilty of Microsoft Word. 
    However, it is what my son uses with the iPad. 
    Most of the time I have to export his files as WORD files because we never seem to have compatible versions of Pages between the iPad and the desktop iMacs. 
    Where can I recommend that Apple improve its compatibility issues with Pages?
    This week I am going to receive a new iPad at my school (I am a teacher) but I am 100% certain that it will not be compatible with the older version of Pages on my classroom iMac.  I also avoid using Keynote for the same reason.  I have 15 year old Power Points that I can still open, but I am hesitant to switch over to Keynote because I want to be able to open my files any time, any where.
    Please advise.

    Not sure what v5 is. Someone helped me and opened it through Pages 5.2, through the program, rather than the Finder. Thanks for making a suggestion!

  • Oracle XML to HSBC XML mapping for R12 AP Check Printing

    Hi,
    Our environment is Oracle APPS R12.
    We need to send an electronic payment information to HSBC bank.  So this will be generated 'like' a check from the payments process, but for payment types of WIRE, ACH, etc...and the output is an XML file in a format specified by the bank HSBC.  We need to send an XML file to HSBC per their spec.  The data that needs to go in this file is the same payment information that Oracle already provides in the standard check printing.  We need to take that data and turn it into XML matching the HSBC spec (hence the XML to XML mapping).
    I am not sure how to get the source for standard check printing prog. Any idea of how to do Oracle XML- HSBC XML Mapping? Any help is really appreciated.
    Thanks
    Valli

    Review this note, you will get source of check printing program
    R12: Master Troubleshooting Guide for Oracle Payables Check Printing issues (Doc ID 1353280.1)
    thanks

Maybe you are looking for

  • Integration with url iview

    Hi everyone, I have a web application and Portal and My aim is this two systems integration using url iview but I don't want to use Application Integrator.I want to use only URL iview with url parameters. My wish is to enter URL Parameter = uname(sta

  • How can I get rid of Euro symbol in text?

    Euro symbol show up in front of Copyright symbol when I test it in Internet Explorer but doesn't when I check it in another browser. How can I get rid of it? Thank you.

  • Convert Milliseconds into specified format

    HI, How to convert System.currentMillis() into yyyy-mm-dd HH:MM:SS:SSS format? PLease give me a solution Thanks

  • Growing nsure audit log file in sys\etc\logcache

    I have a Netware 6.5 OES2 server that suddenly had a quickly growing file in the \sys\etc\logcache folder. The file has just recently stabilized, but I would like to shrink the file. I am aware that this is part of NSure auditing and would like to le

  • BDC Selecting view in MM02

    Hi Experts,   I am doing BDC Session method for Tcode MM02.There i am getting selection View screen for different material.But if i select a material in Sales view i need to select Sales :Sales org dAta. It's coming third position. But for some mater