Creating substructures in message mapping

Hi,
I need to do a message mapping to go from
<message>
   <structure>
      field1
      field2
      fieldA
      fieldB                         
   </structure>
   <structure>
      field1
      field2
      fieldC
      fieldD                         
   </structure>
   <structure>
      field3
      field4
      fieldE
      fieldF                         
   </structure>        
   <structure>
      field3
      field4
      fieldG
      fieldH                         
   </structure>
   etc..
to
<message>
   <structure>
      field1
      field2
      <substructure>
         fieldA
         fieldB
      </substructure>
      <substructure>
         fieldC
         fieldD
      </substructure>
   </structure>
   <structure>
      field3
      field4
      <substructure>
         fieldE
         fieldF
      </substructure>
      <substructure>
         fieldG
         fieldH
      </substructure>
      etc..
I've managed to create as many target structures as there are occurences of the first field in the source structure, but i cannot find the solution to create the correct amount of substructures inside the target structures.  Can it be done with graphical mapping?
Any help appreciated.
Kr
Robert

Hi
Already found the solution:
field1(context of highest level) -> Split by value(valuechange) -> collapse context -> targetStructure
field1(context of highest level) -> Split by value(valuechange) -> collapse context -> splitbyValue(eachvalue) -> field1
field 2  same way as field one
field3 -
> }
->->->->->->->->->->->->->->->->->->}  formatByExample ---> substructure
field1(context of highest level) -> Split by value(valuechange)----->}
field 3 -> field 3
field 4 -> field 4
KR
Robert
Edited by: R. den Hoedt on Dec 1, 2011 3:54 PM

Similar Messages

  • Message Mapping - External Definitions

    My Scenario
    1) File1(Request with Employee Number) - Sent to XI (Async)
    2) XI will send the Request over HTTP and will Receive the Response(Employee Details) (Synchronous)
    3) The HTTP Response will be sent to File2(Employee Details) (Async)
    The Request and Responses are XSD Messages. I have Imported them into External Definition in my Repository.
    Created a File Request - Abstract - Asynchronous - Message interface
    Created a HTTP Request-Response - Abstract - Synch - Message interface
    Created a File Response - Abstract - Asynchronous - Message interface
    Message Mapping: (I am stuck here)
    I need to Map the File Request to HTTP Request
    I need to Map the HTTP Response to File2Response
    How can I creat the Message Mapping for the above situation?
    Thanks.

    Hi,
    You will need to create the following message mapping:
    1. File Request - HTTP Request
    2. HTTP Response - File Response
    you can map Message Types to External Definitions and vice versa.
    They should appear in the list for the relevant software component.
    Or am I missimng something here ?
    Cheers
    colin.

  • Message mapping not generating target fields

    hi
    iam doing jdbc--->rfc (bpm) created a one2one message mapping to import rfc table.
    thanks in advance
    sri

    Hi Sri Rao,
    Since you have created a one to one mapping, it would be required to map all the fields in your target message to ur source fields. In case there r some target fields which do not relate to your source field, map it onto a constant. This is all that is required to be done from what i understand from your query. In case there r further problems send the source n target data structure n i will be able to help you out better.
    Cheers,
    Christina

  • Message mapping - Duplicate subtree

    Hi Experts,
    I am working on 7.0 server.
    In the existing message mapping I found that target nodes are duplicated.
    For example
    /ns0:FiletoFile_ib_mt/Record/Emp[1]
    /ns0:FiletoFile_ib_mt/Record/Emp
    And the order for the node in the target message structure is same as above.
    And in the output, the order is reversed as below
    /ns0:FiletoFile_ib_mt/Record/Emp
    /ns0:FiletoFile_ib_mt/Record/Emp[1]
    But when am duplicating one more node in the existsing mapping the order is
    /ns0:FiletoFile_ib_mt/Record/Emp[2]
    /ns0:FiletoFile_ib_mt/Record/Emp[1]
    /ns0:FiletoFile_ib_mt/Record/Emp
    And now the output is
    /ns0:FiletoFile_ib_mt/Record/Emp[2]
    /ns0:FiletoFile_ib_mt/Record/Emp[1]
    /ns0:FiletoFile_ib_mt/Record/Emp
    But I need the output as
    /ns0:FiletoFile_ib_mt/Record/Emp
    /ns0:FiletoFile_ib_mt/Record/Emp[1]
    /ns0:FiletoFile_ib_mt/Record/Emp[2]
    Please let me know if you have faced similar issue.
    If am creating a new message mapping and duplicating the subtrees the order is given below
    /ns0:FiletoFile_ib_mt/Record/Emp
    /ns0:FiletoFile_ib_mt/Record/Emp[1]
    Why in the existing mapping duplicate subtree is going in the top order and for new message mapping duplicate subtree is going in the bottom. Please advice
    Thanks
    Suma S

    Hi Lucas
    I checked this sap note but I used PI 7.0.
    This happens from 7.10 onwards and this is primarily due to the reason that the occurence of the duplicated node was not remembered when the mapping program gets executed. So, the mapping program was expecting data from the payload for the duplicated node and hence the error

  • Unable to edit Message Mapping

    Hi Experts,
    I have an issue where SAP has created some graphical message mapping in XI systems.I have to edit the messages
    but it doesn't allow me to edit as the "Switch Between Display and Edit" button is disabled.Please let me know
    the way how i can bring it to edit mode (or) if basis can do it please let me the procedure (or) if the prior
    is not possible have to contact sap.
    Thanks,
    Sudhansu

    Sudhansu,
    DO not edit or change the SAP standard SWC. I experimented it like this once and I had to re import it to roll back changes.
    You are correct the warning is not usual for normal objects and do not change it under any circumstances
    After changes are made and activated, if you try to roll back the history also, this symbol will not go
    SAP will not support your product after these changes if you are endorsed or partnered with SAP
    Do the following.
    1. Make this as a dependent SWC in SLD.  THen it will appeare under your local SWC
    2. Here you can use to edit or change it.
    Venkat.

  • Problem in 1toN message mapping,payload not populated but file created

    I am doing 1:N multimapping From Proxy  to File scenario .Proxy send three types of data all having same stucture but depending on the value of First field we split the whole stucture in 3 parts on target side and generating three files on taget side.During testing values get Passed from the SXMB_MONI(processed) and we get whole payload data upto
    "Message Branch Acording to Reciever List" .But when i check payload data in 'Request Message Mapping" we donot get any data in Payload.Taget File is generated but when we try to oen the file I get message " Unable to display the File".
    can any expert help me resolve this problem.

    I need to generate 3 files each having similar structures depending upon the first field 'listcode' values whose values are  'N0','MA','MY' coming in a proxy structure.The source structure is as follows::
    MT_Source
    >Detailrecord..0..unbounded
    >listcode..0.1...xsd:string
    >itemcode...0.1...xsd:string
    >description1...0.1..xsd:string
    >description2...0.1..xsd:string
    The target stuctures are:
    MT_Target_N0
    >Detailrecord..0..unbounded
    >listcode..0.1...xsd:string
    >itemcode...0.1...xsd:string
    >description1...0.1..xsd:string
    >description2...0.1..xsd:string
    MT_Target_MA
    >Detailrecord..0..unbounded
    >listcode..0.1...xsd:string
    >itemcode...0.1...xsd:string
    >description1...0.1..xsd:string
    >description2...0.1..xsd:string
    MT_Target_MY
    >Detailrecord..0..unbounded
    >listcode..0.1...xsd:string
    >itemcode...0.1...xsd:string
    >description1...0.1..xsd:string
    >description2...0.1..xsd:string
    I need to do mapping of such 1:n multimapping mapping.I have done mapping but getting error in moni "Split mapping created no messages".Please suggest me some right way to do mapping

  • PI 7.30 Message Mapping with MsgSplit error Split mapping created no messages, cannot proceed.

    Hi @all,
    I am working on a scenario to split one soruce message with several items to 0..n message for the same receiver.
    Therefore the occurrency of target message (signature in MM) have been adjusted.
    Not all items are forwarded to receiver, only if the content meets some rules the item should be forwarded.
    It could be that no item of the source message meet these rules and therefore no target message at all should be created.
    During test of this case I am facing following error in RWB, scenario is setup as integrated configuration.
    MappingException: Split mapping created no messages, cannot proceed. Review your mapping setup: splitting to 0 messages is not allowed.
    As the occurrency of the target message is 0..n, 0 should be also valid and there should be no error in this case, just stop processing like if there is no receiver in receiver determination step (mode IGNORE)
    Otherwise this will end up in lots of error messages which have to be analyzed and canceled manually which is quite time consuming.
    Maybe someone faced the same issue and found a solution to get rid of this error message.
    Best regards
    Jochen

    Hi Somil,
    hi Sriram,
    thanks for your response.
    In my scenario there also multiple receiver applications receiving data from one single sender application. We are using PI 7.30 dual stack and major goal is to setup all scenario as integrated configurations to have java only processing. One reason for this setup is that the main support user do not have extensive PI knowledge so far and we want to keep it as simple as possible and therefore do not want them to care about the abap stack as much as possible.
    Unfortunately migration to java only is not possible yet.
    In this release extended receiver determination using operation mapping is not supported in integrated configuration.
    There is quite complex rules to check if an item should be forward or not including lots of fields and also value mapping, so it would be quite difficult/impossible to write XPATH expression to have the same check during receiver determination step.
    One workaround could be creating a dummy message in case of no item to be forward and root this message to different place (local file which is always to be overwritten)
    Are there any alternatives/workarounds?
    Best regards
    Jochen
    Message was edited by: Jochen Gugel

  • PI Message Mapping One Source to create two of the same Target Nodes.

    Hi,
    I have a source node that contacts the following.
    "1234-5678".
    When there is a "-" in the source node then I need to create two target nodes.
    When there is no "-" in the source node then only create one node.
    Since the source structure is a flat structure by on the target side as you can see I am trying to achieve a diep structure.
    Please can you assist in how to do this with PI message mapping.
    Regards
    Willie Hugo

    Hi,
    "1234-5678" only occurs once in the source. There is no source xml node that will occur more that once. The whole structure only occurs once. But on the target side I need one of the node to occur more than once if a hyphen is found in the source field.
    Source Message                      - Always only one data node.
    ==============
    <root>
    <OnceOnlyNode>1234-5678</OnceOnlyNode>                   [1..1]
    </root>
    Target Message                      - Only two text node when "-" in source, else only one text node.
    =============
    <msg>
    <text>1234</text>
    <text>6789</text>
    </msg>
    How can this be done using standard PI message mapping functions. Can it be done?
    Regards
    Willie Hugo

  • Create IDoc from flat file - How to do the message mapping

    Hi everybody,
    I want to create an IDoc from a flat file.
    The file structure looks like this:
    MT_XYZ
    - Node001       0...1
      - Leaf001
    - Node002       0...unbounded
       - Node003    0...1
          - Leaf002
          - Leaf003
       - Node004    0...1
          - Leaf004
       - Node005    0...1
          - Leaf005
    I have created a mapping and all the other stuff to set up the IDoc adapter.
    Now when I try to test the interface the IDoc is created properly but obviously no information from the nodes "Node003" to "Node005" is inserted in the IDoc. Only the information kept in the elements (leafs) of "Node001" are inserted.
    All IDoc segments and their "Segment" elements are linked to the root node of the file structure "MT_XYZ". I tried to link some IDoc segments only to "Node002" but then this segment is not created.
    So how can I set up the message mapping in a way that the information from "Node003" to "Node005" is transported to the IDoc? Can anyone help me here?
    Thanks in advance for all answers!
    Regards,
    Torben
    Edited by: Torben Hönemann on Dec 14, 2009 4:26 AM

    Hi Torben,
    >>I want to create an IDoc from a flat file.
    So you are using File content Conversion on the sender side. Right?
    >>no information from the nodes "Node003" to "Node005" is inserted in the IDoc.
    Are these information available in the source XML (you can check in transaction SXMB_MONI-> Input Payload).. There is a limitation in File Content Conversion of File adapter and it is that I can make an XML structure of 3 level.. Since these nodes details are in level 4 and 5 they should be missing in Source XML structure itself (after content conversion of File adapter). check that
    >>So how can I set up the message mapping in a way that the information from "Node003" to "Node005" is transported to the IDoc? Can anyone help me here?
    So you need to take an alternate approach where you do File Content Conversion and make 3 level structure.. then using a mapping convert this three level structure to your 5 level one and then try to map with the idoc.
    Check this blog for an idea
    http://www.riyaz.net/blog/xipi-file-content-conversion-for-complex-structures/
    http://www.riyaz.net/blog/xipi-convert-flat-file-to-deeply-nested-xml-structures-using-only-graphical-mapping/
    Regards
    Suraj

  • How can i test after creating Message mapping transformations

    Hi guys,
    How can i test my transformation after creation of message mapping in Integration Repository.
    Pleae expain step by step procedure
    Thanks & Regards.,
    Pushparaju.B

    Hi,
    1. If you just want to test the mapping --In message Mapping there are three tab, the second one being hte Test tAb. So u can pu the values in the left side XML and do test.
    http://help.sap.com/saphelp_nw04/helpdata/en/c3/e3072e65f04445a010847aa970b68b/content.htm
    2. You can do the Testing from Interface mapping also. There is a Test tab there too.
    3. If you have created the whole scnerio then you can do testing from Integration directory:
    http://help.sap.com/saphelp_nw04/helpdata/en/6b/874a4273bb3830e10000000a155106/content.htm
    Regards
    Vijaya

  • Internal GUI Error when creating Message Mapping.

    Hi Experts,
    An Unexpected Exception occurs when I try to create a Message Mapping on PI 7.1 EHP1.
    After that the object is not create but is locked, if I try to create again an error message is displayed saying "Object Message Mapping: mm_efgsdjk | http://testexxxx currently being edited by user CONSULTOR".
    Can anyone help-me with this problema ?
    Thanks in advance,
    Regis Ferrato

    Hello,
    To unlock the object, please do the following.
    1. Goto Integration Builder homepage and click on "Administration" link on top right menu.
    2. Goto Repository tab >> Lock Overview.
    3. You can select and delete the required locked object.
    Please not that if you dont have the access to this screen, you need to ask basis to do this or give you the access.
    Regards,
    Vikas

  • NullPointerException encountered when creating Message Mapping

    Hi experts,
    I created 3 messages using a wsdl external definition
    - GetPatientDemographicOutput
    - GetPatientDemographicInput
    - SOAPFaultMessage
    With this, I wanted to to create a message mapping object, to map GetPatientDemographicInput to a pre-defined message format.
    However, when I try to select "GetPatientDemographicInput" as "Source Message" in the "Message Mapping" window, I encounter a NullPointerException.
    The wsdl file I used is:
    === Start wsdl file definition ====================================
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- edited with XMLSpy v2005 rel. 3 U (http://www.altova.com) by Administrator (Fujitsu) -->
    <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:y="http://new.webservice.namespace" xmlns:ns="a" xmlns:ns1="b" targetNamespace="http://new.webservice.namespace">
         <types>
              <xs:schema xmlns:ns1="b">
                   <xs:element name="GetPatientDemographicReq">
                        <xs:annotation>
                             <xs:documentation>Request Message</xs:documentation>
                        </xs:annotation>
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Header">
                                       <xs:complexType>
                                            <xs:all>
                                                 <xs:element name="Encoding" type="xs:string"/>
                                                 <xs:element name="SendingApp" type="xs:string"/>
                                                 <xs:element name="SendingFac" type="xs:string"/>
                                                 <xs:element name="ReceivingApp" type="xs:string"/>
                                                 <xs:element name="ReceivingFac" type="xs:string"/>
                                                 <xs:element name="TimeStamp" type="xs:dateTime"/>
                                                 <xs:element name="MessageType" type="xs:string" minOccurs="0"/>
                                                 <xs:element name="MessageId" type="xs:string"/>
                                                 <xs:element name="MessageDesc" type="xs:string" minOccurs="0"/>
                                            </xs:all>
                                       </xs:complexType>
                                  </xs:element>
                                  <xs:element name="PatientID" type="xs:string" minOccurs="0"/>
                                  <xs:element name="InstitutionID" type="xs:string"/>
                                  <xs:element name="SAPPatientID" type="xs:string" minOccurs="0"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="GetPatientDemographicRep">
                        <xs:annotation>
                             <xs:documentation>Reply Message</xs:documentation>
                        </xs:annotation>
                        <xs:complexType>
                             <xs:all>
                                  <xs:element name="Header">
                                       <xs:complexType>
                                            <xs:all>
                                                 <xs:element name="Encoding" type="xs:string"/>
                                                 <xs:element name="SendingApp" type="xs:string"/>
                                                 <xs:element name="SendingFac" type="xs:string"/>
                                                 <xs:element name="ReceivingApp" type="xs:string"/>
                                                 <xs:element name="ReceivingFac" type="xs:string"/>
                                                 <xs:element name="TimeStamp" type="xs:dateTime"/>
                                                 <xs:element name="MessageType" type="xs:string" minOccurs="0"/>
                                                 <xs:element name="MessageId" type="xs:string"/>
                                                 <xs:element name="MessageDesc" type="xs:string" minOccurs="0"/>
                                            </xs:all>
                                       </xs:complexType>
                                  </xs:element>
                                  <xs:element name="PatientID" minOccurs="0">
                                       <xs:simpleType>
                                            <xs:restriction base="xs:string">
                                                 <xs:length value="20"/>
                                            </xs:restriction>
                                       </xs:simpleType>
                                  </xs:element>
                                  <xs:element name="SAPPatientID" minOccurs="0">
                                       <xs:simpleType>
                                            <xs:restriction base="xs:string">
                                                 <xs:length value="10"/>
                                            </xs:restriction>
                                       </xs:simpleType>
                                  </xs:element>
                                  <xs:element name="LastName" minOccurs="0">
                                       <xs:simpleType>
                                            <xs:restriction base="xs:string">
                                                 <xs:length value="50"/>
                                            </xs:restriction>
                                       </xs:simpleType>
                                  </xs:element>
                                  <xs:element name="MiddleName" minOccurs="0">
                                       <xs:simpleType>
                                            <xs:restriction base="xs:string">
                                                 <xs:length value="50"/>
                                            </xs:restriction>
                                       </xs:simpleType>
                                  </xs:element>
                                  <xs:element name="FirstName" minOccurs="0">
                                       <xs:simpleType>
                                            <xs:restriction base="xs:string">
                                                 <xs:length value="50"/>
                                            </xs:restriction>
                                       </xs:simpleType>
                                  </xs:element>
                                  <xs:element name="DOB" type="xs:date" minOccurs="0"/>
                                  <xs:element name="Gender" minOccurs="0">
                                       <xs:simpleType>
                                            <xs:restriction base="xs:string">
                                                 <xs:length value="10"/>
                                            </xs:restriction>
                                       </xs:simpleType>
                                  </xs:element>
                                  <xs:element name="Race" type="xs:string" minOccurs="0"/>
                                  <xs:element name="Nationality" type="xs:string" minOccurs="0"/>
                                  <xs:element name="Language" type="xs:string" minOccurs="0"/>
                                  <xs:element name="HomeNumber" type="xs:string" minOccurs="0"/>
                                  <xs:element name="MobileNumber" type="xs:string" minOccurs="0"/>
                                  <xs:element name="BusinessNumber" type="xs:string" minOccurs="0"/>
                                  <xs:element name="PaymentType" type="xs:string" minOccurs="0"/>
                                  <xs:element name="CancelInd" type="xs:string" minOccurs="0"/>
                                  <xs:element name="PatientRef" type="xs:string" minOccurs="0"/>
                                  <xs:element name="VIPInd" type="xs:string" minOccurs="0"/>
                             </xs:all>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="SOAPFaultMessage">
                        <xs:annotation>
                             <xs:documentation>Fault Message</xs:documentation>
                        </xs:annotation>
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="FaultMessage" type="xs:string"/>
                                  <xs:element name="FaultCode" type="xs:string"/>
                                  <xs:element name="FaultDesc" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
              </xs:schema>
         </types>
         <message name="messageName"/>
         <message name="GetPatientDemographicInput">
              <part name="GetPatientDemographicReq" element="ns1:GetPatientDemographicReq"/>
         </message>
         <message name="GetPatientDemographicOutput">
              <part name="GetPatientDemographicRep" element="ns1:GetPatientDemographicRep"/>
         </message>
         <message name="SOAPFaultMessage">
              <part name="SOAPFaultMessage" element="ns1:SOAPFaultMessage"/>
         </message>
         <portType name="SOAPPort">
              <operation name="GetPatientDemographic">
                   <input message="y:GetPatientDemographicInput"/>
                   <output message="y:GetPatientDemographicOutput"/>
                   <fault name="FaultName" message="y:SOAPFaultMessage"/>
              </operation>
         </portType>
         <binding name="PatientDemoQuerySOAP" type="y:SOAPPort">
              <soap:binding style="rpc" transport="http://schemas.xmlsoap.org"/>
              <operation name="GetPatientDemographic">
                   <soap:operation/>
                   <input>
                        <soap:body use="literal"/>
                   </input>
                   <output>
                        <soap:body use="literal"/>
                   </output>
                   <fault name="FaultName"/>
              </operation>
         </binding>
         <service name="RetrievePatientDemographics">
              <port name="QueryPort" binding="y:PatientDemoQuerySOAP">
                   <soap:address location="http://www.xmlspy.com"/>
              </port>
         </service>
    </definitions>
    === End wsdl file definition ====================================
    The exception stack trace I got is:
    === Start stack trace ====================================
    #19 11:55:30 [AWT-EventQueue-0] ERROR com.sap.aii.utilxi.swing.toolkit.ExceptionDialog: Throwable
    Thrown:
    MESSAGE ID: com.sap.aii.utilxi.misc.api.BaseException
    com.sap.aii.utilxi.misc.api.BaseException: java.lang.NullPointerException
         at com.sap.aii.ib.gui.xmleditor.docview.views.XsdSchemaTextable.setSchema(XsdSchemaTextable.java:86)
         at com.sap.aii.ib.gui.xmleditor.docview.views.XsdContainerTextView.setSchema(XsdContainerTextView.java:46)
         at com.sap.aii.ib.gui.xmleditor.docview.views.XsdContainerTextView.<init>(XsdContainerTextView.java:36)
         at com.sap.aii.ib.gui.xmleditor.docview.MultiViewEditor.makeFromTreeDoc(MultiViewEditor.java:216)
         at com.sap.aii.ib.gui.xmleditor.docview.MultiViewEditor.<init>(MultiViewEditor.java:64)
         at com.sap.aii.mappingtool.mf.TransformationPanel.createSourceView(TransformationPanel.java:248)
         at com.sap.aii.mappingtool.mf.TransformationPanel.<init>(TransformationPanel.java:99)
         at com.sap.aii.mappingtool.mf.MappingTool.<init>(MappingTool.java:32)
         at com.sap.aii.mappingtool.api.MappingToolFactory.getInstance(MappingToolFactory.java:96)
         at com.sap.aii.mappingtool.fwutil.util.ToolUtil.restartTool(ToolUtil.java:315)
         at com.sap.aii.ibrep.gui.mapping.xitrafo.XiTransformationView.loadIfrSchema(XiTransformationView.java:274)
         at com.sap.aii.ibrep.gui.mapping.xitrafo.XiMappingView.searchForRepositoryObject(XiMappingView.java:245)
         at com.sap.aii.ibrep.gui.mapping.xitrafo.RepObjSearchHelpAction.actionPerformed(RepObjSearchHelpAction.java:90)
         at com.sap.aii.utilxi.swing.framework.mtaction.MTActionGroup.actionPerformed(MTActionGroup.java:44)
         at com.sap.aii.utilxi.swing.framework.mtaction.IBToolButton.performDefaultAction(IBToolButton.java:326)
         at com.sap.aii.utilxi.swing.framework.mtaction.IBToolButton.fire(IBToolButton.java:220)
         at com.sap.aii.utilxi.swing.framework.mtaction.IBToolButton.access$200(IBToolButton.java:49)
         at com.sap.aii.utilxi.swing.framework.mtaction.IBToolButton$4.actionPerformed(IBToolButton.java:340)
         at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
         at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
         at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
         at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
         at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.Component.processMouseEvent(Unknown Source)
         at javax.swing.JComponent.processMouseEvent(Unknown Source)
         at java.awt.Component.processEvent(Unknown Source)
         at java.awt.Container.processEvent(Unknown Source)
         at java.awt.Component.dispatchEventImpl(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Window.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)
         at java.awt.EventQueue.dispatchEvent(Unknown Source)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.run(Unknown Source)
    Root cause:
    java.lang.NullPointerException: null
         at com.sap.aii.utilxi.xsd.api.XsdHandler.saveSchemaToDocument(XsdHandler.java:61)
         at com.sap.aii.ib.gui.xmleditor.docview.views.XsdSchemaTextable.setSchema(XsdSchemaTextable.java:82)
         at com.sap.aii.ib.gui.xmleditor.docview.views.XsdContainerTextView.setSchema(XsdContainerTextView.java:46)
         at com.sap.aii.ib.gui.xmleditor.docview.views.XsdContainerTextView.<init>(XsdContainerTextView.java:36)
         at com.sap.aii.ib.gui.xmleditor.docview.MultiViewEditor.makeFromTreeDoc(MultiViewEditor.java:216)
         at com.sap.aii.ib.gui.xmleditor.docview.MultiViewEditor.<init>(MultiViewEditor.java:64)
         at com.sap.aii.mappingtool.mf.TransformationPanel.createSourceView(TransformationPanel.java:248)
         at com.sap.aii.mappingtool.mf.TransformationPanel.<init>(TransformationPanel.java:99)
         at com.sap.aii.mappingtool.mf.MappingTool.<init>(MappingTool.java:32)
         at com.sap.aii.mappingtool.api.MappingToolFactory.getInstance(MappingToolFactory.java:96)
         at com.sap.aii.mappingtool.fwutil.util.ToolUtil.restartTool(ToolUtil.java:315)
         at com.sap.aii.ibrep.gui.mapping.xitrafo.XiTransformationView.loadIfrSchema(XiTransformationView.java:274)
         at com.sap.aii.ibrep.gui.mapping.xitrafo.XiMappingView.searchForRepositoryObject(XiMappingView.java:245)
         at com.sap.aii.ibrep.gui.mapping.xitrafo.RepObjSearchHelpAction.actionPerformed(RepObjSearchHelpAction.java:90)
         at com.sap.aii.utilxi.swing.framework.mtaction.MTActionGroup.actionPerformed(MTActionGroup.java:44)
         at com.sap.aii.utilxi.swing.framework.mtaction.IBToolButton.performDefaultAction(IBToolButton.java:326)
         at com.sap.aii.utilxi.swing.framework.mtaction.IBToolButton.fire(IBToolButton.java:220)
         at com.sap.aii.utilxi.swing.framework.mtaction.IBToolButton.access$200(IBToolButton.java:49)
         at com.sap.aii.utilxi.swing.framework.mtaction.IBToolButton$4.actionPerformed(IBToolButton.java:340)
         at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
         at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
         at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
         at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
         at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.Component.processMouseEvent(Unknown Source)
         at javax.swing.JComponent.processMouseEvent(Unknown Source)
         at java.awt.Component.processEvent(Unknown Source)
         at java.awt.Container.processEvent(Unknown Source)
         at java.awt.Component.dispatchEventImpl(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Window.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)
         at java.awt.EventQueue.dispatchEvent(Unknown Source)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.run(Unknown Source)
    #18 11:55:30 [AWT-EventQueue-0] FINE AutoLog.created.com.sap.aii.utilxi.misc.api.BaseException: com.sap.aii.utilxi.misc.api.BaseException: java.lang.NullPointerException
         at com.sap.aii.ib.gui.xmleditor.docview.views.XsdSchemaTextable.setSchema(XsdSchemaTextable.java:86)
         at com.sap.aii.ib.gui.xmleditor.docview.views.XsdContainerTextView.setSchema(XsdContainerTextView.java:46)
         at com.sap.aii.ib.gui.xmleditor.docview.views.XsdContainerTextView.<init>(XsdContainerTextView.java:36)
         at com.sap.aii.ib.gui.xmleditor.docview.MultiViewEditor.makeFromTreeDoc(MultiViewEditor.java:216)
         at com.sap.aii.ib.gui.xmleditor.docview.MultiViewEditor.<init>(MultiViewEditor.java:64)
         at com.sap.aii.mappingtool.mf.TransformationPanel.createSourceView(TransformationPanel.java:248)
         at com.sap.aii.mappingtool.mf.TransformationPanel.<init>(TransformationPanel.java:99)
         at com.sap.aii.mappingtool.mf.MappingTool.<init>(MappingTool.java:32)
         at com.sap.aii.mappingtool.api.MappingToolFactory.getInstance(MappingToolFactory.java:96)
         at com.sap.aii.mappingtool.fwutil.util.ToolUtil.restartTool(ToolUtil.java:315)
         at com.sap.aii.ibrep.gui.mapping.xitrafo.XiTransformationView.loadIfrSchema(XiTransformationView.java:274)
         at com.sap.aii.ibrep.gui.mapping.xitrafo.XiMappingView.searchForRepositoryObject(XiMappingView.java:245)
         at com.sap.aii.ibrep.gui.mapping.xitrafo.RepObjSearchHelpAction.actionPerformed(RepObjSearchHelpAction.java:90)
         at com.sap.aii.utilxi.swing.framework.mtaction.MTActionGroup.actionPerformed(MTActionGroup.java:44)
         at com.sap.aii.utilxi.swing.framework.mtaction.IBToolButton.performDefaultAction(IBToolButton.java:326)
         at com.sap.aii.utilxi.swing.framework.mtaction.IBToolButton.fire(IBToolButton.java:220)
         at com.sap.aii.utilxi.swing.framework.mtaction.IBToolButton.access$200(IBToolButton.java:49)
         at com.sap.aii.utilxi.swing.framework.mtaction.IBToolButton$4.actionPerformed(IBToolButton.java:340)
         at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
         at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
         at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
         at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
         at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.Component.processMouseEvent(Unknown Source)
         at javax.swing.JComponent.processMouseEvent(Unknown Source)
         at java.awt.Component.processEvent(Unknown Source)
         at java.awt.Container.processEvent(Unknown Source)
         at java.awt.Component.dispatchEventImpl(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Window.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)
         at java.awt.EventQueue.dispatchEvent(Unknown Source)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.run(Unknown Source)
    #17 11:55:30 [AWT-EventQueue-0] DEBUG AutoLog.created.com.sap.aii.utilxi.misc.api.BaseException: java.lang.NullPointerException
    #16 11:55:30 [AWT-EventQueue-0] FINE AutoLog.created.java.lang.NullPointerException: java.lang.NullPointerException
         at com.sap.aii.utilxi.xsd.api.XsdHandler.saveSchemaToDocument(XsdHandler.java:61)
         at com.sap.aii.ib.gui.xmleditor.docview.views.XsdSchemaTextable.setSchema(XsdSchemaTextable.java:82)
         at com.sap.aii.ib.gui.xmleditor.docview.views.XsdContainerTextView.setSchema(XsdContainerTextView.java:46)
         at com.sap.aii.ib.gui.xmleditor.docview.views.XsdContainerTextView.<init>(XsdContainerTextView.java:36)
         at com.sap.aii.ib.gui.xmleditor.docview.MultiViewEditor.makeFromTreeDoc(MultiViewEditor.java:216)
         at com.sap.aii.ib.gui.xmleditor.docview.MultiViewEditor.<init>(MultiViewEditor.java:64)
         at com.sap.aii.mappingtool.mf.TransformationPanel.createSourceView(TransformationPanel.java:248)
         at com.sap.aii.mappingtool.mf.TransformationPanel.<init>(TransformationPanel.java:99)
         at com.sap.aii.mappingtool.mf.MappingTool.<init>(MappingTool.java:32)
         at com.sap.aii.mappingtool.api.MappingToolFactory.getInstance(MappingToolFactory.java:96)
         at com.sap.aii.mappingtool.fwutil.util.ToolUtil.restartTool(ToolUtil.java:315)
         at com.sap.aii.ibrep.gui.mapping.xitrafo.XiTransformationView.loadIfrSchema(XiTransformationView.java:274)
         at com.sap.aii.ibrep.gui.mapping.xitrafo.XiMappingView.searchForRepositoryObject(XiMappingView.java:245)
         at com.sap.aii.ibrep.gui.mapping.xitrafo.RepObjSearchHelpAction.actionPerformed(RepObjSearchHelpAction.java:90)
         at com.sap.aii.utilxi.swing.framework.mtaction.MTActionGroup.actionPerformed(MTActionGroup.java:44)
         at com.sap.aii.utilxi.swing.framework.mtaction.IBToolButton.performDefaultAction(IBToolButton.java:326)
         at com.sap.aii.utilxi.swing.framework.mtaction.IBToolButton.fire(IBToolButton.java:220)
         at com.sap.aii.utilxi.swing.framework.mtaction.IBToolButton.access$200(IBToolButton.java:49)
         at com.sap.aii.utilxi.swing.framework.mtaction.IBToolButton$4.actionPerformed(IBToolButton.java:340)
         at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
         at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
         at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
         at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
         at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.Component.processMouseEvent(Unknown Source)
         at javax.swing.JComponent.processMouseEvent(Unknown Source)
         at java.awt.Component.processEvent(Unknown Source)
         at java.awt.Container.processEvent(Unknown Source)
         at java.awt.Component.dispatchEventImpl(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Window.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)
         at java.awt.EventQueue.dispatchEvent(Unknown Source)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.run(Unknown Source)
    #15 11:55:30 [AWT-EventQueue-0] DEBUG AutoLog.created.java.lang.NullPointerException: null
    === End stack trace ====================================
    Please help.
    I am running PI7.0.
    Thanks.
    Ron

    I've managed to get around this problem.
    The problem is with the namespace definition.
    Apparently, a more correct definition looks like this:
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
    xmlns:y="http://new.webservice.namespace"
    xmlns:ns="http://new.webservice.namespace"
    targetNamespace="http://new.webservice.namespace"
    >
         <types>
              <xs:schema <b>targetNamespace="http://new.webservice.namespace" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns="http://new.webservice.namespace" xmlns:y="http://new.webservice.namespace" xmlns="http://schemas.xmlsoap.org/wsdl/"</b>>
                   <xs:element name="GetPatientDemographicReq">
                        <xs:annotation>
                             <xs:documentation>Request Message</xs:documentation>
                        </xs:annotation>
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Header">
                                       <xs:complexType>
                                            <xs:all>
                                                 <xs:element name="Encoding" type="xs:string"/>
                                                 <xs:element name="SendingApp" type="xs:string"/>
                                                 <xs:element name="SendingFac" type="xs:string"/>
                                                 <xs:element name="ReceivingApp" type="xs:string"/>
                                                 <xs:element name="ReceivingFac" type="xs:string"/>
                                                 <xs:element name="TimeStamp" type="xs:dateTime"/>
                                                 <xs:element name="MessageType" type="xs:string" minOccurs="0"/>
                                                 <xs:element name="MessageId" type="xs:string"/>
                                                 <xs:element name="MessageDesc" type="xs:string" minOccurs="0"/>
                                            </xs:all>
                                       </xs:complexType>
                                  </xs:element>
                                  <xs:element name="PatientID" type="xs:string" minOccurs="0"/>
                                  <xs:element name="InstitutionID" type="xs:string"/>
                                  <xs:element name="SAPPatientID" type="xs:string" minOccurs="0"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="GetPatientDemographicRep">
                        <xs:annotation>
                             <xs:documentation>Reply Message</xs:documentation>
                        </xs:annotation>
                        <xs:complexType>
                             <xs:all>
                                  <xs:element name="Header">
                                       <xs:complexType>
                                            <xs:all>
                                                 <xs:element name="Encoding" type="xs:string"/>
                                                 <xs:element name="SendingApp" type="xs:string"/>
                                                 <xs:element name="SendingFac" type="xs:string"/>
                                                 <xs:element name="ReceivingApp" type="xs:string"/>
                                                 <xs:element name="ReceivingFac" type="xs:string"/>
                                                 <xs:element name="TimeStamp" type="xs:dateTime"/>
                                                 <xs:element name="MessageType" type="xs:string" minOccurs="0"/>
                                                 <xs:element name="MessageId" type="xs:string"/>
                                                 <xs:element name="MessageDesc" type="xs:string" minOccurs="0"/>
                                            </xs:all>
                                       </xs:complexType>
                                  </xs:element>
                                  <xs:element name="PatientID" minOccurs="0">
                                       <xs:simpleType>
                                            <xs:restriction base="xs:string">
                                                 <xs:length value="20"/>
                                            </xs:restriction>
                                       </xs:simpleType>
                                  </xs:element>
                                  <xs:element name="SAPPatientID" minOccurs="0">
                                       <xs:simpleType>
                                            <xs:restriction base="xs:string">
                                                 <xs:length value="10"/>
                                            </xs:restriction>
                                       </xs:simpleType>
                                  </xs:element>
                                  <xs:element name="LastName" minOccurs="0">
                                       <xs:simpleType>
                                            <xs:restriction base="xs:string">
                                                 <xs:length value="50"/>
                                            </xs:restriction>
                                       </xs:simpleType>
                                  </xs:element>
                                  <xs:element name="MiddleName" minOccurs="0">
                                       <xs:simpleType>
                                            <xs:restriction base="xs:string">
                                                 <xs:length value="50"/>
                                            </xs:restriction>
                                       </xs:simpleType>
                                  </xs:element>
                                  <xs:element name="FirstName" minOccurs="0">
                                       <xs:simpleType>
                                            <xs:restriction base="xs:string">
                                                 <xs:length value="50"/>
                                            </xs:restriction>
                                       </xs:simpleType>
                                  </xs:element>
                                  <xs:element name="DOB" type="xs:date" minOccurs="0"/>
                                  <xs:element name="Gender" minOccurs="0">
                                       <xs:simpleType>
                                            <xs:restriction base="xs:string">
                                                 <xs:length value="10"/>
                                            </xs:restriction>
                                       </xs:simpleType>
                                  </xs:element>
                                  <xs:element name="Race" type="xs:string" minOccurs="0"/>
                                  <xs:element name="Nationality" type="xs:string" minOccurs="0"/>
                                  <xs:element name="Language" type="xs:string" minOccurs="0"/>
                                  <xs:element name="HomeNumber" type="xs:string" minOccurs="0"/>
                                  <xs:element name="MobileNumber" type="xs:string" minOccurs="0"/>
                                  <xs:element name="BusinessNumber" type="xs:string" minOccurs="0"/>
                                  <xs:element name="PaymentType" type="xs:string" minOccurs="0"/>
                                  <xs:element name="CancelInd" type="xs:string" minOccurs="0"/>
                                  <xs:element name="PatientRef" type="xs:string" minOccurs="0"/>
                                  <xs:element name="VIPInd" type="xs:string" minOccurs="0"/>
                             </xs:all>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="SOAPFaultMessage">
                        <xs:annotation>
                             <xs:documentation>Fault Message</xs:documentation>
                        </xs:annotation>
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="FaultMessage" type="xs:string"/>
                                  <xs:element name="FaultCode" type="xs:string"/>
                                  <xs:element name="FaultDesc" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
              </xs:schema>
         </types>
         <message name="messageName"/>
         <message name="GetPatientDemographicInput">
              <part name="GetPatientDemographicReq" element="ns:GetPatientDemographicReq"/>
         </message>
         <message name="GetPatientDemographicOutput">
              <part name="GetPatientDemographicRep" element="ns:GetPatientDemographicRep"/>
         </message>
         <message name="SOAPFaultMessage">
              <part name="SOAPFaultMessage" element="ns:SOAPFaultMessage"/>
         </message>
         <portType name="SOAPPort">
              <operation name="GetPatientDemographic">
                   <input message="y:GetPatientDemographicInput"/>
                   <output message="y:GetPatientDemographicOutput"/>
                   <fault name="FaultName" message="y:SOAPFaultMessage"/>
              </operation>
         </portType>
         <binding name="PatientDemoQuerySOAP" type="y:SOAPPort">
              <soap:binding style="rpc" transport="http://schemas.xmlsoap.org"/>
              <operation name="GetPatientDemographic">
                   <soap:operation/>
                   <input>
                        <soap:body use="literal"/>
                   </input>
                   <output>
                        <soap:body use="literal"/>
                   </output>
                   <fault name="FaultName"/>
              </operation>
         </binding>
         <service name="RetrievePatientDemographics">
              <port name="QueryPort" binding="y:PatientDemoQuerySOAP">
                   <soap:address location="http://www.xmlspy.com"/>
              </port>
         </service>
    </definitions>
    Thanks!

  • How to Transport only Message mapping in already created transport.

    Hi All,
    I have changed message mapping object in ESR and now need to transport the new version to Q enivroment using CTS.
    Can somebody tell me the detailed steps for doing this.???
    Thanks in advance!!!!

    hi,
    you refer from 33 page on words below in doc :
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20ccd0ec-2839-2b10-0097-828fcd8ed809?QuickLink=index&overridelayout=true
    becuase i dont know are u release the transport /not.
    if ur release and everything fine, then simply go to QUAlity Sys -> tools-> impoted desig time obj.

  • Create a Support Message in Production system showing up in Solution Manage

    Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
    I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
    Thanks
    Paul

    Hi Paul
    The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
    Make sure your RFC's are trusted and that you have SAP ALL during config.
    I hope this will help:
    Setup Service Desk
    Steps to follow while configuring support desk.
    1) Implement the note 903587 .
    2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
    3) Check all the objects in the table BCOS_CUST using transaction SM30.
    Appl : OSS_MSG
    + :W
    DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
    + :CUST 620
    + :1.0.
    *4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
    4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
    4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
    4.3) Activation of the following components has to be done by replicating the previous steps
    3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
    3.2) SOLMAN40_SDESK_ACTIONLOG_001
    3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
    3.4) SOLMAN40_SDESK_TEXTTYPES_001
    *Depends upon the number of inactive BC set objects that we have after the upgrade.
    4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
    5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
    Number ranges for ABA notifications
    5.1) create an internal and external number range using transaction DNO_NOTIF.
    5.2) assign number range intervals to groups internal and external.
    5.3) SLF1 is the internal number range group
    5.4) SLF2 and SLF3 is the external number range interval
    5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
    5.51) Go to transaction DNO_CUST01
    5.52) From the GOTO menu select the menu item DETAILS
    5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
    The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
    Number ranges for Support Desk notification
    5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
    5.6) Then assign both the external and internal numbering
    5.61) Go to SPRO and then to SAP Solution Manager
    5.62) Then select General Settings and then select Transaction types
    5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
    5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
    5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
    6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
    6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
    6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
    7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
    8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
    8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
    8.2) Select the item Service Desk and then to general settings.
    8.3) Execute the category u2018Define Transaction Typesu2019.
    8.4) Select the transaction type as SLFN
    8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
    9) Activate the partner/ Organization
    9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
    9.2)Find the entries starting with HRALX
    HRALX-HRAC WITH VALUE 'X'.
    HRALX-OBPON WITH VALUE 'ON'.
    HRALX-PBPON u2018ONu2019.
    HRALX-MSGRE u2013 u20180u2019.
    9.3) If entries are not found create it.
    10) Generate Business partner screens
    10.1) Go to transaction BUSP.
    10.2) Execute the report with the following parameters
    CLIENT - Client in which business partners should be created (solution manager client)
    APPLICATION OBJECT-
    SCREEN - *
    Generate all/ selected screens - All screens.
    delete sub screen containers -
    11) implement SAP note 450640.
    11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
    11.2) Execute it with test mode box unchecked.
    If a new relationship is to be created then steps 12 and 13 has to be followed
    12) To create a relationship category
    12.1) Go to transaction BUBA
    12.2) Select the entry CRMH00: Undefined relationship
    12.3) click on copy
    12.4) Rename CRMH00 to ZCRMH00.
    12.5) CREATE A RELATIONSHIP CATEGORY.
    IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
    ' FROM BP2 : IS A PART OF ATTUNE
    13) Add the relationship category to the support team partner function
    13.1)Use SPRO
    IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
    -> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
    13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
    13.3) In the field relation ship category, Select the newly created relationship category and save.
    14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
    15) Create a new access sequence for the support team determination
    15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
    SAP Solution Manager -> Configuration ->
    -> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
    ->Define Access Sequence
    15.2) Click on New Entries
    15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
    15.4) Create an new Individual Access with the following value:
    u2022 Batch Seq: 10
    u2022 Dialog Seq : 10
    u2022 Source : Business Partner Relationship.
    u2022 Detail on the source:
    u2022 Partner Function : Reported By (CRM)
    u2022 Mapping/restrictions
    u2022 Flag Mapping/definition for partner being Searched
    u2022 Partner Function in Source: Support Team (CRM).
    Save it.
    This Access Sequence will give us the Partner which has the relationship assigned
    to the Support Team in the Reported By partner data.
    16) Adapt the partner determination schema/Function
    16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
    SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
    -> Partner Determination Procedure -> Define Partner Determination Procedure.
    16.2) The two options to adapt partner determination schema are
    16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
    16.22) select the line starting with SLFN0001 or the newly created procedure.
    16.23) Double Click on Partner Function in Procedure.
    16.24) Select the Partner Function "Support Team", and click Details.
    16.25) in the detail view only change the Partner Determination/access Sequence to
    the one we've just created. Save your entry.
    17) Create a root organizational model.
    17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
    17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
    17.3) enter the organizational unit, the description and save it.
    18) Create the support team organization
    18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
    19) Create the business Partners.
    19. 1) Key users- End user (Business Partner General) ,Address should be specified.
    19.2) go to the transaction BP.
    19.3) create a new Person, Select the role: Business Partner (Gen).
    For Identification of the key user
    19.31) click on the identification tab
    19.32) enter a line in the identification number formatted as follows
    IDTYPE : CRM001.
    Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
    eg: USER NAME : USER1.
    CLIENT : 100.
    SID : ER1.
    INSTALL NUMBER : 123456789.
    IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
    20) Message Processors- Support Team members .
    20.1) they should be created first as the users in the corresponding client of the solution manager.
    20.2) As business partners they will have the role 'EMPLOYEE'.
    20.3) Go to transaction BP .
    20.4) Create New Person with the role employee.
    20.5) In the Identification tab you should enter the user name in the employee data/User Name.
    eg: username: proc1
    enter proc1 in the field User name.
    21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
    22) Assign the business partners (Message Processors) to the previously created support team.
    22.1) Go to transaction PPOMA_CRM.
    22.2) Select the support team 1.
    22.3) Click on create
    22.4) select position
    22.5) call it 'MPROC_T1/Message Processors for team 1
    22.6) Replicate it for the other support teams.
    22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
    choose owner/Business Partner find and select the business partner
    22.8) Validate and Save it.
    22.9) If the assignment of business partner is not possible then implement the note 1008656
    Or 997009
    23) Create the iBase component
    23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
    23.2) or use the transaction IB51 to create the installed base.
    23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
    24)Assign Business Partners to iBase Components
    IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
    -> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
    *--optional--
    If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
    Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
    Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
    Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
    now to assign the partner Function "System Administrator".
    25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
    26)Define the transaction variant for the message processors
    Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
    Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
    27) Go to transaction PFCG
    27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
    27.2) Give a description Message Processor role and save it.
    27.3) Go to the menu tab and choose add report
    27.4) select the report type : ABAP Report
    27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
    27.6) Enter the previously created variant.
    27.7) flag the skip initial screen box.
    27.8) flag the SAPGUI for windows.
    27.9) Create a new transaction with tcode starting with Y or Z.
    27.10)Display this transaction and check the values at the bottom of the screen
    in the subscreen Default Values, you should have the following parameters:
    u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
    u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
    u2022 D_SREPOVARI-NOSELSCRN = X
    And also all the user should have the correct role.

  • To get exception value in Message Mapping

    Hi folks,
    I would like catch bpm step exception in one message mapping, for example:
    I have create on ccBPM using one block, in block i have createad "ex" exception variable and set ex in all step (send and transformation), i have created one exception branch in block using "ex" exception.
    How can i get "ex" value and pass for one message mapping ?
    In MM how can i get text values from excpetion ocurred in ccBPM ?
    Im am trying using Global Variables but not found any parameter of exceptions.
    Can anybody help me, please?

    hi,
    >>In MM how can i get text values from excpetion ocurred in ccBPM ?
    this is not possible
    Regards,
    Michal Krawczyk

Maybe you are looking for

  • Bluetooth soft blocked, wont unblock

    Hello, my laptop's bluetooth adapter is not working due to the hci0 interface being soft blocked. Unblocking with # rfkill unblock all doesn't have any effect at all - 'rfkill list' still shows 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no

  • Read a csv file and update sql db

    I'm a newbie to C#. I've put together the code below - see two commented lines where the for loop starts. need advise as to the correct approach. you may insert pseudo code in appropriate places. Thanks in advance. Below is my code: public class Mail

  • Executing multipule .sql files in Sequence

    Hi , I am new to oracle world . I need to execute 150 .sql files from my local machine . I am trying do something like this ... but facing many errors ... I am using oracle 10 g Please advice me . CREATE OR REPLACE PROCEDURE MYPROC AS BEGIN DECLARE C

  • Can't find a P2 driver for FCP 6.0

    Hi, We just hired a company to do a shoot and they put P2 files on my XHD. They told me I need to download the P2 driver. They sent me a link to the creative cow site with a demonstration video and the link to download the driver. I clicked on the li

  • I want to install R12 , 2node rac configuration and i have 32gb ram , can i go for 2db nodes and 2 app nodes

    i want to use VM  for this can any one please suggest what is max best combination for me to test out the R12 on RAC environment. Regards, Raj