Message mapping editor

in messgae mapping editor, what are the nodes with a "red circle" mean....and what does green colored and red colored circle means,
sometimes i encounter this problem while testing message mapping:
"Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd"
can u detail this

The nodes with a little red-lined circle are the nodes that are marked with max occurrence > 1 (for example, unbounded). That means that these fields can occur repeatedly in the target message.
Green circles mean fields that you have already mapped or that are not necessary to be mapped, they will be created automatically (for fields with 1...1 occurrence in target message).
Grey circles mean fields that you haven't mapped yet, but that are not necessary (optional fields, with min occurrence = 0). In particular, nodes which accept multiple instances (with little red circle) will have gray circle, even if they have min occurrence >= 1. You'll have to pay attention on those.
Red circles mean fields that are obrigatory in target message (for example, fields with min occurrence = 1) but are not mapped yet.
Regards,
Henrique.

Similar Messages

  • Does the message mapping editor insure that a valid target message is co

    Hi Friends
    Does the message mapping editor insure that a valid target message is constructed?
    Regards
    Sam

    Samuel,
    Message mapping editor ,will generate the output as per your logic. Hence you need to validate and check whether the target message has been created correctly.
    If you say," I'm perfect with the logic, I created the mapping I checked the target strcuture, its perfect, always the data will be populated correctly?" If the above is your question, then the answer is YES.
    raj.

  • Many Options in Message Mapping Editor Disabled

    Hello all,
    Many fields in Mapping editor are disbled. Fields like,
    ==>"Map Selected fields and Substructures, if names are identical"
    ==>"Clear Mapping"
    ==>"Data Flow Editor"
    etc, in that row, except "Edit Java sections" and "Select Message" are diabled.
    How to enable them?
    Thanks and Regards,
    Sundar

    Hi,
    Open your respective SWCV.
    Double click on SWCV and look at the bottom of it, there will be two check boxes just make sure both are checked. (I don't remember the names but you need to check both of them).
    Regards,
    Sarvesh
    Edited by: Sarvesh Singh on Jan 2, 2008 5:41 PM

  • Message Mapping : Testing at Runtime

    Hi all,
    I am doing scenario File XI IDoc...
    I was encountering error.. Runtime exception in Mapping...
    So i tried the testing step described by michal.
    if i paste the payload of the data obtained from SXMB_MONI in test tab of message mapping editor i will get error
    <i>Cannot produce target element /WGSREQ02/IDOC/E1WGRK1. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd </i>
    but for the same paylod in "src" of testing tab if i add namespace the testing is working fine.
    Kindly can anybody give me suggestion
    Regards,
    Ramesh P
    Message was edited by:
            Ramesh Parashivamurthy

    Message Mapping
    http://help.sap.com/saphelp_nw04/helpdata/en/49/1ebc6111ea2f45a9946c702b685299/frameset.htm
    User Defined Functions:
    http://help.sap.com/saphelp_erp2004/helpdata/en/22/e127f28b572243b4324879c6bf05a0/frameset.htm
    Advanced Graphical Mapping:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/b9af5e71-0701-0010-d0b8-f612fb6593dd
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/be05e290-0201-0010-e997-b6e55f9548dd

  • Hi,about message mapping

    why is always disabled the dependencies button in the message mapping editor of IR.
    it is for ever gray whether in edit mode or not?

    Hi,
    The dependency button in Message mapping is used to show the Source field mapped to which target field.
    Can u explain ur query clearly...
    Regards
    San
    Remember to set the thread to solved when you have received a solution there is a Way.

  • Parameterized Message Mapping in PI 7.1

    Hi,
    My requirement is:
    If the import parameter of type "string" equals constant "Test",
    pass the constant value "Mail1" to the target field,
    else pass the constant value "Mail2" to the target field.
    Also I have mentioned the import parameter value in Interface Determination as "Test".
    So, "Mail1" should be the output, but in a strange way i'm always getting "Mail2" as the output.
    In message mapping test tab, i'm getting the expected output as "Mail1" but when i test it end-to-end, i'm getting "Mail2" as the output.
    Does it mean that we cannot use the import parameters for checking any conditon? Or am I doing any silly mistake?
    Any help will be appreciated.
    Edited by: Geetha Jeyaprakash on Dec 24, 2008 2:25 PM

    I'm giving the condition in Message mapping editor using standard functions.
    Actual requirement is to pass a particular mail id to the target field in Development environment and some other mail id in Production environment. As we don't have any particular source field to check the condition, we tried using parameterized mapping for the same.

  • Message Maaping Editor - Buttons in Object Toolbar disabled

    In Message Mapping Editor, Object Tool bar buttons are always disabled. I can not use functions like "Data Flow Editor", "Clear Mapping", "Text Preview" etc. The only functions enabled in Object Toolbar are "Select Message" and "Edit Java Sections". All the other functions are disabled. We are working in PI 7.0 SP12 environment. Please let me know if you know how to make these enabled. Thanks in Advance.
    Srihari

    Aamir,
         Thanks for the reply. The Java Version that we are using is 1.6.0_03. Do you think that we need to change it back to 1.4.2?
    Thanks,
    Srihari

  • Message mapping (data flow editor, data dependcies  buttons not visible)

    Hi,
    In my SAP PI...IR ...in message mapping screen some buttons are not enable/visible like
    data flow editor, data dependcies,clear mapping  buttons not visible)
    any oss notes/help will be appreciated.
    Thanks

    Hi,
    This will help you
    /people/shabarish.vijayakumar/blog/2006/02/13/unable-to-open-iresrid-xipipi-71-updated-for-pi-71-support
    Go for 1.4.X version than 1.6.X The Problem will be resolved
    Regards
    Sangeetha

  • Error when saving message mapping -

    Just upgradedto PI 7.1. System details below....
    Make Release NW07_08_REL  SPS Number 08  JDK Version jdk15
    Server Version SAP J2EE Engine 7.10.3710.43701.20090416112158
    Java Runtime Java(TM) 2 Runtime Environment, Standard Edition (version=5.1.034)
    Java Virtual Machine SAP Java Server VM (version=5.1.034)
    Operating System AIX (version=5.3, arch=ppc64)
    I've been building an interface to test the developer tools and when I save my message mapping (it's a very simple graphical mapping) I get a java popup with the text 'Internal GUI error', I'm using Java WS Version 1.5.0 (build 1.5.0_19-b02) as per the PI documentation.
    I recreated the problem timing each activity and saved the exception in a text file. I'm able to identify the relevant section of the exception biut it's meaningless to me. I searched SDN & OSS and I can't find any specific hits. Those that are similar (different SAP applications - WebDynPro for example) point towards incompatible s/w components - Java Run Time environment etc.... I've cleared the Java WS cache (Edit>Preferences>Delete Files) just to make sure, but the problem still occurs. I'm looking for advice. I've pasted some of the exception details below. I can provide more information but it's a pretty long file.
    Edited by: Rob Warde on Aug 5, 2009 4:27 PM

    Thrown:
    com.sap.aii.utilxi.swing.framework.FrameworkException: Internal problem occurred
         at com.sap.aii.utilxi.swing.toolkit.ExceptionDialog.init(ExceptionDialog.java:124)
         at com.sap.aii.utilxi.swing.toolkit.ExceptionDialog.<init>(ExceptionDialog.java:96)
         at com.sap.aii.utilxi.swing.toolkit.IBMessages$1.run(IBMessages.java:319)
         at com.sap.aii.utilxi.misc.thread.ThreadPool.assureAWTEventQueueing(ThreadPool.java:84)
         at com.sap.aii.utilxi.misc.thread.ThreadPool.assureAWTEventQueueing(ThreadPool.java:67)
         at com.sap.aii.utilxi.swing.toolkit.IBMessages.showException(IBMessages.java:309)
         at com.sap.aii.utilxi.swing.toolkit.IBMessages.showException(IBMessages.java:299)
         at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor$1.run(Guitilities.java:395)
         at java.awt.event.InvocationEvent.dispatch(Unknown Source)
         at java.awt.EventQueue.dispatchEvent(Unknown Source)
         at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
         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)
    Caused by: java.lang.NoSuchMethodError: com.sap.aii.ib.bom.mt.js.JavaSource.setMode(I)V
         at com.sap.aii.mappingtool.Project.getJavaFile(Project.java:324)
         at com.sap.aii.mappingtool.mf.MappingTool.getJavaFile(MappingTool.java:107)
         at com.sap.aii.mappingtool.fwutil.api.ViewUtil.prepareSave(ViewUtil.java:118)
         at com.sap.aii.ibrep.gui.mapping.xitrafo.XiMappingView.prepareSave(XiMappingView.java:269)
         at com.sap.aii.ib.gui.editor.DefaultPersistenceHandler.save(DefaultPersistenceHandler.java:153)
         at com.sap.aii.ib.gui.editor.XiDocument.save(XiDocument.java:335)
         at com.sap.aii.utilxi.swing.framework.cmd.SaveCommand.execute(SaveCommand.java:76)
         at com.sap.aii.utilxi.swing.framework.ExecutionContext.execute(ExecutionContext.java:198)
         at com.sap.aii.utilxi.swing.framework.ExecutionContext.executeSafe(ExecutionContext.java:154)
         at com.sap.aii.utilxi.swing.framework.CommandAction.actionPerformed(CommandAction.java:82)
         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.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)

  • Error in message mapping

    I used MT_PerformRate for both sender side and receiver side in message mapping
    When I goto interface mapping and click on the mapping program it gives following error.
    The source or target structure has been changed or could not be found in the Integration Repository. The mapping definition contains elements or attributes that do not exist in the changed structure. The relevant entries will be deleted
    Target structure has no such path: /ns0:MT_PerformRate/@EmpName. Skipping mapping
    Target structure has no such path: /ns0:MT_PerformRate/@EmpNo. Skipping mapping
    Target structure has no such path: /ns0:MT_PerformRate/@PerformRating. Skipping mapping
    Target structure has no such path: /ns0:MT_PerformRate/@RatingDesc. Skipping mapping
    Target structure has no such path: /ns0:MT_PerformRate/@EffectiveDate. Skipping mapping
    In mapping editor target fileds are shown in red.
    I can see two message mappings in Change list one with target fileds in red and one with green.
    I do not know what is happening
    PLs suggest

    Thanks Amith and Ameer for your answers.
    The exact reason was because I did not used recordset in my datatype creation.
    But I did not set ignoreRecordsetName to true
    For who get similar problem please see below details and link
    A <Recordset> element is inserted in the XML structure for each recordset structure. This level is not always required, particularly if the recordset only contains one structure definition.
    If you set the parameter to true, the <Recordset> element is not inserted.
    http://help.sap.com/saphelp_nw70/helpdata/EN/2c/181077dd7d6b4ea6a8029b20bf7e55/frameset.htm
    Thanks,
    Raj

  • XI message mapping clarifications

    Dear All                                                                               
    I would like to know if XI message mapping(graphical mapping) can be         
    used for mapping based on the order of elements given in the XML source          
    message.                                                                               
    For example I have a source message as below                                                                      
    Source XML:                                                                      
    <Source>                                                                         
    <givenname>Ramesh</givenname>                                                     
    <givenname>Kumar</givenname>
    <givenname>Ganapathy</givenname>                                                                               
    </Source>                                                                               
    semantic is first instance of <givenname> needs to be mapped <firstname> in target,                      
    Second occurance of <givenname> needs to be mapped <secondname>,                                
    Third occurance of <givenname> needs to be mapped <familyname>                                                                               
    Target XML                                                                       
    <Target>                                                                         
    <firstname>Ramesh</firstname>                                                    
    <secondname>Kumar</secondname>
    <familyname>Ganapathy</familyname>                                               
    </Target>                                                                               
    As I understand graphical mapping editor works based on Xpath                    
    expressions, Is it possible to achieve such mapping schematics with              
    graphical mapping and UDF in XI.
    Please note I cannot use Java, ABAP or XSLT mapping programme.
    Can you provide me some hints on how to do this.                                                                               
    Thanks                                                                           
    Satish

    Hi Chilla
    This is how I am currently handling it. But my problem is
    The number of UDF's keeps increasing if I have a fourth, fifth element to handle. I have to create new UDF for every new level added.
    Is there a way I can do this with single UDF.
    result.addValue(givenname(X));
    X- will be the position and I can pass values as an argument to the UDF.
    Again the problem here is when I have second argument to specify which value of input to pick up say for example  givenname(1) or givenname(2)
    The second argument expects an String[] array as argument and not string(when i assign a constant its a string).
    So I cannot attach a constant to the second argument and pass the input.
    Is there any functions that can return a String[] array as an output taking sting value as input.
    Thanks
    Satish

  • Problem in Message Mapping

    Hi,
    My requirement is filter message based on the condition.
    My source structure is like below
    Root_Node
        |
      RecordSet (1..Unbounded)
          |_
          |   Header (1..1)
          |      |_ RecordType
          |_
              Detail (1.. Unbounded)
                 |_ RecordTypeDetail
    Example XSD is given below
    Now my requirement is I need to map the iterations to the same type of target structure (but only difference is all elements are non mandatory).
    if
    1) RecordType does not exists under Header, then map Detail.
    2) recordTypeDetails does not exists under Details then map Header.
    Now while doing RecordSet Mapping I have written user defined function which adds context if any of the above condition valid.
    But while doing the mapping for the Header Record we should map the iteration for which detail is not available, I am not able to associate the above context with the new resultset context.
    Any suggestions please.
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:group8" targetNamespace="urn:group8">
         <xsd:complexType name="DT_EA_COMPLETE">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   e616ab20c08c11d9bb8e001143eb68b9
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="DT_EA_HD" type="DT_EA" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             cdea8830bb8e11d98600dd930a770421
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="DT_EA">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   eab53980c08c11d9ab7d001143eb68b9
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="Header">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             9d192f70bb0e11d9afc8fdcd0a770421
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:complexType>
                             <xsd:sequence>
                                  <xsd:element name="rec_type_h" type="xsd:string">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            9d192f71bb0e11d9c902fdcd0a770421
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                                  <xsd:element name="Project_estimate_number" type="xsd:string">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            9d192f72bb0e11d998cafdcd0a770421
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                                  <xsd:element name="Revision_number" type="xsd:string">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            9d192f73bb0e11d9851bfdcd0a770421
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                                  <xsd:element name="Project_estimate_title" type="xsd:string">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            9d192f74bb0e11d99a04fdcd0a770421
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                                  <xsd:element name="Project_estimate_description" type="xsd:string">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            9d192f75bb0e11d99d6ffdcd0a770421
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                                  <xsd:element name="purchase_order" type="xsd:string">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            9d192f76bb0e11d9bf5efdcd0a770421
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                             </xsd:sequence>
                        </xsd:complexType>
                   </xsd:element>
                   <xsd:element name="DetailData" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             9d192f77bb0e11d9c8b6fdcd0a770421
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:complexType>
                             <xsd:sequence>
                                  <xsd:element name="rec_type" type="xsd:string">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            9d192f78bb0e11d9cfa4fdcd0a770421
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                                  <xsd:element name="Price" type="xsd:string">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            9d192f79bb0e11d9c487fdcd0a770421
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                                  <xsd:element name="gl_account" type="xsd:string">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            9d192f7abb0e11d99609fdcd0a770421
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                                  <xsd:element name="Internal_order" type="xsd:string">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            9d192f7bbb0e11d99b5afdcd0a770421
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                                  <xsd:element name="line_item_description" type="xsd:string">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            9d192f7cbb0e11d9bdf8fdcd0a770421
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                                  <xsd:element name="print_job_indicator" type="xsd:string">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            9d192f7dbb0e11d9cec2fdcd0a770421
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                                  <xsd:element name="impress_project_number" type="xsd:string">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            9d192f7ebb0e11d9af41fdcd0a770421
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                                  <xsd:element name="partner_vendor" type="xsd:string">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            9d192f7fbb0e11d9be5dfdcd0a770421
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                                  <xsd:element name="time_of_delivery" type="xsd:date">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            9d192f80bb0e11d9c353fdcd0a770421
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                                  <xsd:element name="Vendor_text" type="xsd:string">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            9d192f81bb0e11d9b0cdfdcd0a770421
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                             </xsd:sequence>
                        </xsd:complexType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>

    HI,
    I think there is problem with occurence here. Try to findout run time value in the mapping.. i.e Diplay queue option in the mapping editor. SO that you can check where exactly it is getting error.
    Regards,
    Moorthy

  • Writing message mapping function in Java in integration repository

    Hi XI Pundits,
    I am new to XI. I was working on Message mapping in intergration repository.
    To map the source messages to target messages, we do graphical kind of mapping like drag and drop.
    There are some functions aavilable at the bottom like concatehate, trim and etc. which we use if we need to modify the source message and map to target.
    But in case we face a situation when we don't find the function which suits our requirement, I guess we need to write a new function. We can write these new function using Java only.
    Can someone throw some light on this ?
    <b>What do we do to invoke java editor in integartion reposity to write mapping function in java ?
    Can someone give an example of snippet of code ?</b>
    Thanks.

    Hi Tushar,
    Go thro this help link. You will get all info about User defined function.
    http://help.sap.com/saphelp_nw04/helpdata/en/22/e127f28b572243b4324879c6bf05a0/frameset.htm
    To get more understanding on mapping go thro this link(PDF File)
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9202d890-0201-0010-1588-adb5e89a6638
    Hope this helps.
    regards,
    P.Venkat
    Message was edited by: Venkataramanan

  • Message Mapping of Recursive Source Structure?

    Hello,
    a mapping needs to be implemented from a custom source structure to an IDoc. An XSD has been provided for the source structures which contains recursive elements --> an element of a specific type contains another element with the same type.
    If I import the XSD then the type of the recursive element is displayed in "red", but I still can expand it. If I want to use the source structure in the message mapping I cannot expand the recursive elements anymore. Does anyone of you have an idea how to handle this? I want to avoid XSLT if possible.
    Thank you!

    Hi again Florian,
    please have a look at [Structure Overview in Message Mappings on SAP help|http://help.sap.com/saphelp_nwpi71/helpdata/en/e3/92be7c6cd34fd485c967144e302fb6/content.htm]. There is a paragraph on Recursive Structures:
    ...It is possible to map these elements in the mapping editor in a rudimentary fashion by using the context menu to expand a specific number of subnodes and then use them in target-field mappings...
    That works for both source and target message.

  • Missing closing tag in message mapping

    Hi experts,
    I have an RFC --> PI --> JDBC scenario with the following message mapping:
    SOURCE --> TRIM --> mapWithDefault [] --> DESTINATION
    If the source field doesn't come, the input XML is a follows:
    <SOURCE/>
    And after the mapping I obtain the following: <DESTINATION></DESTINATION> that is exactly what the reciever system is expecting. This was been working fine until the upgrade to ECC 6.0 of the Sender system. Actually I don't know if it has anything to do, because the RFC XML looks exactly the same, but the user claims it has stopped working since the upgrade.
    Now the same mapping, with the same <SOURCE/> input creates this output: <DESTINATION/>. This is not accepted by the reciver system and throws an error.
    What can be happening? The message mapping has not changed and the RFC XML looks exactly the same....any ideas?? Thanks! Pablo

    >
    Stefan Grube wrote:
    > >. This is not accepted by the reciver system and throws an error.
    > What is the error?
    > If you use JBDC adapter, it is no difference, whetehr you have <tag></tag> or <tag />, because this is the same.
    If  you see the payload in Internet Explorer, for example you'll see <tag />. But if you see the XML with a text editor, it should be <tag></tag>: Before this issue the receiver system was getting a "blank" value, now it's getting "null" and it can't handle it.
    Sarvesh: thanks for your advice but I'm already using that function...
    I'll try Pedro's, Srinivas' and Hetal's ideas, but the user has to setup the development box for testing.
    I'll update later, thanks for your help. More ideas are appreciated!
    Pablo

Maybe you are looking for