XI Configuration Design questions with multi-mapping message mapping object

Hello,
I'm having trouble designing a particular scenario for multi-mapping.  Currently i'm working with a Vendor create and change.  BPM is not being used.
This is what i need:
I need a CREMDM04 to turn into one or multiple ADRMAS/CREMAS IDocs and potentially a CLFMAS IDoc based on the values in the inbound CREMDM04 IDoc.
This is what i currently have:
A CREMDM04 inbound idoc is multi-mapped to a CREMDM03 (1...9999), another CREMDM03 (0...9999), and a CLFMAS01 (0...9999).  At a minimum only the first CREMDM03 IDoc will be created and at a maximum all three will be created.  The parameters on creating the second CREMDM03 IDoc and the CLFMAS01 IDoc are based on the values in the inbound CREMDM04 IDoc, whereas the first CREMDM03 IDoc will always be created and the values will just be converted/mapped from the inbound CREMDM04 IDoc.  This multi-mapping is currently set-up via a graphical message map and works successfully in the test-tab of the mapping object.  It has a main message and has sub-messages which are the IDocs.  I’m mapping the CREMDM04 to a CREMDM03 to then map it through an ABAP-Class and then to an XSL where the CREMDM03 inbound structure is expected to split into ADRMAS and CREMAS Outbound IDocs for Vendor Create/Change in the remote R/3 systems.
After the graphical map we have a necessary ABAP Class call that calls a BAPI to the remote system.  This ABAP Class must come after the graphical map since the parameter for the BAPI is based on a converted value from the graphical multi-map.
After the ABAP Class call there is finally an XSL message split the CREMDM IDoc into an ADRMAS and CREMAS IDoc.  There need to be two interface mappings (one per ADRMAS and CREMAS) since the ABAP classes and XSLs are specific to the ADRMAS and CREMAS.
The CLFMAS IDoc can go directly to the remote system, but since it’s within this one multi-map, I’m not sure if is possible?  I’m not sure if it will fail once it tries entering the XSL mapping (this is the standard CREMDM message split offered from SAP).
There are three interface mapping scenarios I can think of, but cannot get to work:
CREMDM04 to ADRMAS02
CREMDM04 to CREMAS03
CREMDM04 to CLFMAS01
Currently I have the Interface Mapping structured as follows:  (I cannot get this to activate as it appears it does not work)
Multi-Mapping ==> ABAP Class Call ==> Standard XSL Message Split
How should i design the interface mapping objects and the configuration objects for this scenario?
Any help is appreciated and I definitely will reward points (no need to include it in your response).

Hi,
I suggest you may use multiple steps interface mapping. It's composited with 3 message mappings as step by step.
Mapping 1: One to one mapping. For the output schema, use a composition schema which includes those 3 IDOCs you want.
Mappign 2: ABAP Mapping. I am not sure the ABAP class you mentioned is an ABAP mapping or not. If it does, That's ok. If not,
call that ABAP class in your ABAP mapping and do corresponding change for your message. Return back the same structure as output.
Mapping 3: One to multiple mapping to split the message.
So basically as interface mapping, it's one to multiple mapping. And internally, you have 3 steps to realize the mapping.
And as my experience, for both one to multiple message mapping & multiple steps interface mapping, it works well in my project. And
in ID, you have to configure it via "advance" function in receiver determination or interface determination.
Let me know if any confusion.
Thanks
Nick

Similar Messages

  • Error status code 400 with the description Message mapping failed

    Hi,
    I tried to build RFID outbound scenario using ECC 5.0, XI and AII 2.1.
    When I send IDOC message:AIDOPMSG.AIDOP01 from ecc 5.0 to XI(ouput message type is OperationalIn and message mapping is OperationalInTo), i get following error:
    <SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
      <SAP:P1>400</SAP:P1>
      <SAP:P2>Message mapping failed</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>Message mapping failed</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP response contains status code 400 with the description Message mapping failed Boundary SAP_57D7D47469E09543A1EA0002CBDA0492_END could not be found</SAP:Stack>
    I am using standard AUTO-ID 2.1 XI contents. If any of you have encountered such error message, then could you please help me understand the meaning and how to fix it.
    thanks in advance,
    Ashit

    hi Ashit,
    take a look at my weblog on how to test your mapping:
    /people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
    maybe with this you'll be able to find out the error
    Regards,
    michal

  • Architecture/Design Question with best practices ?

    Architecture/Design Question with best practices ?
    Should I have separate webserver, weblogic for application and for IAM ?
    If yes than how this both will communicate, for example should I have webgate at both the server which will communicate each other?
    Any reference which help in deciding how to design and if I have separate weblogic one for application and one for IAM than how session management will occur etc
    How is general design happens in IAM Project ?
    Help Appreciated.

    The standard answer: it depends!
    From a technical point of view, it sounds better to use the same "midleware infrastructure", BUT then the challenge is to find the lastest weblogic version that is certified by both the IAM applications and the enterprise applications. This will pull down the version of weblogic, since the IAM application stack is certified with older version of weblogic.
    From a security point of view (access, availability): do you have the same security policy for the enterprise applications and the IAM applications (component of your security architecture)?
    From a organisation point of view: who is the owner of weblogic, enterprise applications and IAM applications. In one of my customer, application and infrastructure/security are in to different departments. Having a common weblogic domain didn't feet in the organization.
    My short answer would be: keep it separated, this will save you a lot of technical and political challenges.
    Didier.

  • Problem with WCS, with an error message (Error: Object not found in device)

    I  have a problem with WCS, I can not open the window monitor /  controllers with an error message (Error: Object not found in device)  -> https: / / 10.19x.xxx.xx/webacs/switchDetailAction. do? ControllerID = 23735
    by  cons I can open the window configures / controllers -> https: / /  10.19x.xxx.xx/webacs/switchGeneralAction.do? command = detail &  ControllerID = 23735
    Is there a way to recreate the database or the object? thank you in advance

    thank you for your help
    Unfortunately, the command "refresh config from controller"  does not solve the problem because we have a negative result
    (in mode retain or in mode delete) with the following logs :
    Log file wcs-0-0.log
    10/19/10 12:07:16.333 ERROR[snmpmed] [23] Response VarBind missing for class InterfaceConfig attribute isInterfaceWired
    Log file tomcat_localhost_access_log
    10.197.xxx.xx - - [19/Oct/2010:12:07:16 +0000] "POST /webacs/switchListCommandAction.do HTTP/1.1" 200 47399
    10.197.xxx.xx- - [19/Oct/2010:12:07:16 +0000] "GET /webacs/alarmSummaryAction.do?command=summary&dojo.preventCache=1287490037130 HTTP/1.1" 200 421

  • Question with multi-mapping 1:n split scenario

    Hi
        I have a scenario with the following requirement
    R3 --> XI --> Multiple files
    I used a multi-mapping scenario  using message mapping. to get the following output
    <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
    <ns0:Message1>
    <Transaction> </Transaction>
    <Transaction> </Transaction>
    </ns0:Message1>
    <ns0:Messages>
    Each  <Transaction> </Transaction>  produces a file in runtime. So far so good.
    Now, there was a new requirement to introduce a dtd line as the first line  in each of the target files created  - that looks like follows :
    <!DOCTYPE Transaction PUBLIC \"-//XXXXX//DTD BatchReceiptAuthorization//EN\" \"http://dtd.XXXXX.com/dtds/ReceiptAuthorization.dtd\">
    How do I go about introducing this header line above the <Transaction> node in each and every target file - that is created by multi-mapping  ? This header line is not a part of the target schema and hence cannot be mapped to as an constant element in the target.
    Any suggestions/ideas as to how this can be done ?

    Hi Gautam
        I did use a java mapping , as a second step after the message mapping - so that the dtd line can be introduced as a header for each target message/file written by the muti-mapping in the first step.
         In my scenario, I sent the inputstream that is being passed to the Java execute method  - to trace and I see that the whole of the xml file - as shown below - which is the output of message mapping ( from the first mapping step ) in sent to the execute method of the java mapping a single call
    <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
    <ns0:Message1>
    <Transaction> </Transaction>
    <Transaction> </Transaction>
    </ns0:Message1>
    <ns0:Messages>
    So, I modified Java mapping program to look for multiple occurences of <Transaction> tag and prefix them with my constant DTD Literal - which is the primary reason , why I had to use Java mappings after the message mapping.
    Now, I get an error is XI- SXMB_MONI
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
    <SAP:Category>XIServer</SAP:Category>
    <SAP:Code area="MAPPING" />
    <SAP:P1>unexpected symbol; expected '<'</', entity refe</SAP:P1>
    <SAP:P2>rence, character data, CDATA section, processing i</SAP:P2>
    <SAP:P3>0</SAP:P3>
    <SAP:P4>113</SAP:P4>
    <SAP:AdditionalText />
    <SAP:ApplicationFaultMessage namespace="" />
    <SAP:Stack>The exception occurred (program: CL_XMS_MAIN===================CP, include CL_XMS_MAIN===================CM00A, line: 609)</SAP:Stack>
    <SAP:Retry>M</SAP:Retry>
    </SAP:Error>
    Can you help me out here ?

  • 1: N multi mapping -----Message Mapping Error

    Hi,
    I am doing this scenario
    Various multi-mappings and Optimizing their Implementation in Integration Processes (BPM) in XI.
    In the design part of the mapping.
    How can I perform the message mapping
    Step 1. We are controlling occurrence of Output Piyush_msg_out_3 by mapping it with element2 with message context.
    Step 2.
    We are using u201CUseOneAsManyu201D under category node functions (SP14). It has three inputs ;
       1. Element which is going to be used for multiple times. In our case it is Element1 with message context.
       2. The element which is going to define how many times it will be replicated. Important thing, context should be same.
       3. Same as second input but with its own context in our case it is Element2.
    For Step 1,
    I have mapped piyush_msg_out_3 with Element2 (context is root)
    For Step 2,
    I have mapped
    Element1(context root)----
    |
    Element2(context root)----
    |   useOneAsMany -
    >Element1
    Element2(context root)----
    |
    subelement------> subelement
    I did not do root mapping.
    when do the test I am getting the following error
    Start of test
    Compilation of MM_multimappingandoptimizing successful Cannot produce target element
    /ns0:Messages/ns0:Message1/ns1:piyush_msg_out_3[2]/root/Element1. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd Cannot produce target element
    /ns0:Messages/ns0:Message1/ns1:piyush_msg_out_3[2]/root/Element1. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
    End of test
    I thought error generated due to Parent Node condition fails, How do I map the Top node,
    even though I mapped root------->root, I am  getting the same error in the instance test
    Please give me some suggestions
    my message mapping is correct or do I need to change the context of the node  or what should I have to do ?
    thanks
    manian

    Hi Praveen,
    I have checked the XSD tab of Source and Target message types. I can see the complete XSD.
    Source Message Type XSD:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:mlr:multimappingandoptimizing" targetNamespace="urn:mlr:multimappingandoptimizing">
         <xsd:element name="piyush_msg_in_1" type="piyush_msg_in_1" />
         <xsd:complexType name="piyush_msg_in_1">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   f1fd03a0cddd11ddc1c4001cc01cef0d
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="root">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             99ffb9e0cd1a11ddc6b0001cc01cef0d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:complexType>
                             <xsd:sequence>
                                  <xsd:element name="Element1" type="xsd:string">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            99ffb9e1cd1a11dd8843001cc01cef0d
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                                  <xsd:element name="Element2" maxOccurs="unbounded">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            99ffb9e2cd1a11dd8f7a001cc01cef0d
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element name="subelement" type="xsd:string">
                                                      <xsd:annotation>
                                                           <xsd:appinfo source="http://sap.com/xi/TextID">
                                                           99ffb9e3cd1a11dd8ff2001cc01cef0d
                                                           </xsd:appinfo>
                                                      </xsd:annotation>
                                                 </xsd:element>
                                            </xsd:sequence>
                                       </xsd:complexType>
                                  </xsd:element>
                             </xsd:sequence>
                        </xsd:complexType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>
    Target Message Type XSD:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:mlr:multimappingandoptimizing" targetNamespace="urn:mlr:multimappingandoptimizing">
         <xsd:element name="piyush_msg_out_3" type="piyush_msg_out_3" />
         <xsd:complexType name="piyush_msg_out_3">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   058e2b60cdde11ddaffd001cc01cef0d
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="root">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7fb0d7d0cd1b11dd99ae001cc01cef0d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:complexType>
                             <xsd:sequence>
                                  <xsd:element name="Element1" type="xsd:string">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            7fb0d7d1cd1b11ddc07e001cc01cef0d
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                  </xsd:element>
                                  <xsd:element name="Element2">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            7fb0d7d2cd1b11dd9385001cc01cef0d
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element name="subelement" type="xsd:string">
                                                      <xsd:annotation>
                                                           <xsd:appinfo source="http://sap.com/xi/TextID">
                                                           7fb0d7d3cd1b11dda9d7001cc01cef0d
                                                           </xsd:appinfo>
                                                      </xsd:annotation>
                                                 </xsd:element>
                                            </xsd:sequence>
                                       </xsd:complexType>
                                  </xsd:element>
                             </xsd:sequence>
                        </xsd:complexType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>
    thanks
    manian

  • Problem configure Ldap realm with multi master Ldap server

    I have a multimaster Directory Server (Ldap) eg: LdapMaster01 & LdapMaster02.
    I configured the realm Ldap:
    realm= myLdapRealm
    class name =com.sun.enterprise.security.auth.realm.ldap.LDAPRealm
    jaas-context = myLdapRealm
    directory = ldap://LdapMaster01:389
    base-dn = ou=my_APP, ou=Applications, dc=devinc, dc=com
    search-bind-dn = cn=Directory Manager
    search-bind-password = 99999999So how can i configure realm to automatically switch to LdapMaster02 when the LdapMaster01 is not up?
    Thanks in advance

    Probably you need an external intelligent
    loadbalancer unit, that receives all requests for an
    DNS like 'LdapMaster' and reroutes the traffic to
    LdapMaster01 or LdapMaster02.
    If one LdapMaster ist not available then the
    loadbalancer is responsible to route all requests
    only to the available server.Thank you very much. :)
    I found other post on the internet about this, and yes, probably the only way is a loadbalancer.
    Another way is to write a custum realm impl that receives the server list and try to connect until an available server is found.

  • Configuration Design question

    I have main site and remote sites connected via VPN (sometimes unreliable).   I understand that i should not install another management server in remote site due to the management servers should be close to each other and are in the same management
    group and pool for servers or pool for network devices.
    How can I separate each site to monitoring itself and each other?  For example, I would like Remote Site to have it's own set of SCOM componenets independent of main site so it's monitoring from its network but report everything back to the main site.  
    If main site is not available, remote site will operate and alert independently.
    Can the separate management group use its own management and sql servers? insteaded of remote management servers connecting to main site's sql db.

    Use the Connected Management Group
    http://technet.microsoft.com/en-us/library/hh230698.aspx
    Juke Chou
    TechNet Community Support

  • Help with Message Mapping - Context Change

    I need help with the following message mapping.  I am filtering by EMP_STAT in the Message Mapping.  I have this working for the ROW structures, but I can get the HEADER/REC_COUNT field to calculate.  I can do just a record count of ROW and get it to work, but I can't get it to work with the filter EMP_STAT = 'REG' added.  I get a context error.  Could someone send me the mapping code.
    Sender XML----
    <RECORD>
    <ROW>
    <EMPLOYEE>111</EMPLOYEE>
    <EMP_STAT>REG</EMP_STAT>
    </ROW>
    <ROW>
    <EMPLOYEE>222</EMPLOYEE>
    <EMP_STAT>PT</EMP_STAT>
    </ROW>
    <ROW>
    <EMPLOYEE>333</EMPLOYEE>
    <EMP_STAT>REG</EMP_STAT>
    </ROW>
    </RECORD>
    Receiver XML----
    <RECORD>
    <HEADER>
    <REC_COUNT>2</REC_COUNT>
    </HEADER>
    <ROW>
    <EMPLOYEE>111</EMPLOYEE>
    <EMP_STAT>REG</EMP_STAT>
    </ROW>
    <ROW>
    <EMPLOYEE>333</EMPLOYEE>
    <EMP_STAT>REG</EMP_STAT>
    </ROW>
    </RECORD>

    Hello,
    You can use this mapping
    For REC_COUNT:
    EMP_STAT -> equalsS: constant:REG -> ifWithoutElse -> removeContext -> count -> REC_COUNT
                                     EMPLOYEE -> /
    For ROW:
    EMP_STAT -> equalsS: constant:REG -> ifWithoutElse -> removeContext -> ROW
                                     EMPLOYEE -> /
    For EMPLOYEE:
    EMP_STAT -> equalsS: constant:REG -> ifWithoutElse -> removeContext -> SplitByValue -> EMPLOYEE
                                     EMPLOYEE -> /
    For EMP_STAT:
    Constant: REG -> EMP_STAT
    Hope this helps,
    Mark

  • Replacing & with & in message mapping

    Hi,
    In my scenario I'm using Graphical mapping tool and I have to replace the & that's coming in the input xml with &amp; in the output with in the message mapping, Is Value mapping is the only solution or do we have any other options that we can use for this.
    Basically I'm getting runtime error in the message Mapping since I had a & in the value which is not recognized.
    thanks,
    Joe.P

    Hi Bhavesh,
    My scenario is RFC-ABAPProxy--XI- File.
    so the RFC is sending me as & instead of &amp.
    this is what I see in the my incoming xml and this failing during runtime.
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:Messages xmlns:ns0=" http://sap.com/xi/XI/SplitAndMerge">
    <ns0:Message1>
    <nr1:MT_HCMPositionData xmlns:nr1="http://XXXX.com/xi/HCM/Recruitment ">
    <PositionIDs>
    <PositionID>20008644</PositionID>
    <Position_Desc>Director Finance M&A_Dept771_SSC7000</Position_Desc>
    <Job_Code>Director Finance M&A</Job_Code>
    <Staffing_Stat>1</Staffing_Stat>
    <Org_Type>DEPARTMENT</Org_Type>
    </PositionIDs>
    </nr1:MT_HCMPositionData>
    </ns0:Message1>
    </ns0:Message1>

  • UDF in message mapping instead of Java Mapping. Pls advice urgent

    Hi All,
    My scenario
    CRM --- XI -- CRM
    In XI I have to open socket connection.
    Pls refer link:
    /people/saravanakumar.kuppusamy2/blog/2005/12/15/socket-integration-with-xi
    Can Java Mapping code given in above link for socket connection can be used in Message Mapping (CRM -- CRM)UDF?
    Pls advice urgent
    Regards

    Hi Henry,
    I understood your requirement.
    But as per the architecture of XI/PI some message has to trigger your scenario.
    In this case there is no adapter where you can directly communicate with CRM system.
    Do one thing configure a dummy scenario on the sender side.
    Use File adapter for simplicity. once it pools the file with some dummy data in the file it comes to Interface mapping(message mapping) of the PIPELINE steps. Now use the code as you mentioned above(within UDF) for opening socket to CRM system and implement you business logic within that program and write the response to target interface which will infact talk with CRM system.
    Dont forget to do the coding in an infinite loop with some delay (if required). Other wise every time you have to put a message for File Adapter for triggering purposes.
    You can also acheive the same if you use Java Mapping instead of Graphical mapping with UDF(code for Opening socket and business logic). I suggest you to use Java Mapping.
    I dont know how you will comunicate with CRM system on receiver side.?
    Thanks,
    Gujjeti

  • Attachments deleted during message mapping in PI 7.1

    We have upgraded our SAP XI 3.0 SP 22 system to SAP PI 7.1 SP06. In XI 3.0 we created some message mappings that mapped an XML payload with attachments to another message type. The attachments would still exist after the mapping step. In SAP PI 7.1 we now see that attachements are deleted from the message. We cannot see why this is happening. We have tried to set the 3 new option in the operation mappings without any results. The attachements are still being deleted.
    Active Options in operation mappings:
        Use SAPXMLToolkit = true
        Do Not Resolve XOP includes = false
        Read Attachements = false
    In the SXMB_MONI we can see that the attachements are deleted after the Request Message Mapping step. It is a simple proxy-to-proxy scenario with interface and message mapping.
    <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
      <Trace level="2" type="T">......attachment XI_Context not found</Trace>
      <Trace level="3" type="T">Mapping already defined in interface determination</Trace>
      <Trace level="3" type="T">Object ID of Interface Mapping 46842937562139BCA3F2AC1F36E729FE</Trace>
      <Trace level="3" type="T">Version ID of Interface Mapping 5D945F00B00611DDB04FF8CF0A5B0156</Trace>
      <Trace level="1" type="T">Interface Mapping urn:kadaster-nl:SERV:ZA:KAD:DOVO im_mail_to_dms</Trace>
      <Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_mm_mail_to_dms_</Trace>
      <Trace level="3" type="T">MTOM Attachments are Transferred to the Payload</Trace>
      <Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
      <Trace level="2" type="T">Mode 0</Trace>
      <Trace level="3" type="T">Search com/sap/xi/tf/_mm_mail_to_dms_.class (urn:kadaster-nl:SERV:ZA:KAD:DOVO, -1) in swcv 5d945f00-b006-11dd-b04f-f8cf0a5b0156.</Trace>
      <Trace level="2" type="T">Loaded class com.sap.xi.tf._mm_mail_to_dms_</Trace>
      <Trace level="3" type="T">Search com/sap/xi/tf/_mm_mail_to_dms_$MT$InnerLibsList.class (urn:kadaster-nl:SERV:ZA:KAD:DOVO, -1) in swcv 5d945f00-b006-11dd-b04f-f8cf0a5b0156.</Trace>
      <Trace level="2" type="T">Loaded class com.sap.xi.tf._mm_mail_to_dms_$MT$InnerLibsList</Trace>
      <Trace level="3" type="T">Search com/sap/xi/tf/_mm_mail_to_dms_$MT$InnerParamsList.class (urn:kadaster-nl:SERV:ZA:KAD:DOVO, -1) in swcv 5d945f00-b006-11dd-b04f-f8cf0a5b0156.</Trace>
      <Trace level="2" type="T">Loaded class com.sap.xi.tf._mm_mail_to_dms_$MT$InnerParamsList</Trace>
      <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._mm_mail_to_dms_</Trace>
      <Trace level="1" type="T">*** START APPLICATION TRACE ***</Trace>
      <Trace level="3" type="T">Document start</Trace>
      <Trace level="3" type="T">Start tag [ns1:OpvoerenDocumentRequest]</Trace>
      <Trace level="3" type="T">Add raw attribute [ xmlns:ns1="urn:kadaster-nl:SERVICES:DMS:Opvoeren:ZI_KAD_DMS_MAIN"]</Trace>
      <Trace level="3" type="T">Start tag [DocumentInfoRecord]</Trace>
      <Trace level="3" type="T">Start tag [Type]</Trace>
      <Trace level="3" type="T">Put value [302]</Trace>
      <Trace level="3" type="T">Close tag [Type]</Trace>
      <Trace level="3" type="T">Start tag [Omschrijving]</Trace>
      <Trace level="3" type="T">Put value [Apeldoorn]</Trace>
      <Trace level="3" type="T">Close tag [Omschrijving]</Trace>
      <Trace level="3" type="T">Close tag [DocumentInfoRecord]</Trace>
      <Trace level="3" type="T">Close tag [ns1:OpvoerenDocumentRequest]</Trace>
      <Trace level="3" type="T">Document end</Trace>
      <Trace level="1" type="T">*** END APPLICATION TRACE ***</Trace>
      <Trace level="2" type="T">Java mapping com/sap/xi/tf/_mm_mail_to_dms_ completed. (executeStep() of com.sap.xi.tf._mm_mail_to_dms_).</Trace>
      <Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
      <Trace level="3" type="T">Attached will be Deleted cid:payload-001708D1A20E1DEDAD96471B4CCBC447(@)sap.com</Trace>
      <Trace level="3" type="T">Attached will be Deleted cid:payload-001708D1A20E1DEDAD96471B4C758447(@)sap.com</Trace>
      <Trace level="1" type="T">ContentType application/xml</Trace>
    Regards,
    Jeroen

    Hi Michal,
    Already tried this option too. However this option would only transfer the attachments to
    the mapping runtime in JAVA. We only map the actual payload in a graphical message
    mapping, so for our purpose, the other attachments could stay untouched and remain
    in the abap part for further pipeline processing.
    You can find the result of the Read attachment option during runtime here:
    <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
      <Trace level="2" type="T">......attachment XI_Context not found</Trace>
      <Trace level="3" type="T">Mapping already defined in interface determination</Trace>
      <Trace level="3" type="T">Object ID of Interface Mapping 46842937562139BCA3F2AC1F36E729FE</Trace>
      <Trace level="3" type="T">Version ID of Interface Mapping 5D945F00B00611DDB04FF8CF0A5B0156</Trace>
      <Trace level="1" type="T">Interface Mapping urn:kadaster-nl:SERV:ZA:KAD:DOVO im_mail_to_dms</Trace>
      <Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_mm_mail_to_dms_</Trace>
      <Trace level="3" type="T">MTOM Attachments are Transferred to the Payload</Trace>
      <Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
      <Trace level="2" type="T">Mode 0</Trace>
      <Trace level="3" type="T">Search com/sap/xi/tf/_mm_mail_to_dms_.class (urn:kadaster-nl:SERV:ZA:KAD:DOVO, -1) in swcv 5d945f00-b006-11dd-b04f-f8cf0a5b0156.</Trace>
      <Trace level="2" type="T">Loaded class com.sap.xi.tf._mm_mail_to_dms_</Trace>
      <Trace level="3" type="T">Search com/sap/xi/tf/_mm_mail_to_dms_$MT$InnerLibsList.class (urn:kadaster-nl:SERV:ZA:KAD:DOVO, -1) in swcv 5d945f00-b006-11dd-b04f-f8cf0a5b0156.</Trace>
      <Trace level="2" type="T">Loaded class com.sap.xi.tf._mm_mail_to_dms_$MT$InnerLibsList</Trace>
      <Trace level="3" type="T">Search com/sap/xi/tf/_mm_mail_to_dms_$MT$InnerParamsList.class (urn:kadaster-nl:SERV:ZA:KAD:DOVO, -1) in swcv 5d945f00-b006-11dd-b04f-f8cf0a5b0156.</Trace>
      <Trace level="2" type="T">Loaded class com.sap.xi.tf._mm_mail_to_dms_$MT$InnerParamsList</Trace>
      <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._mm_mail_to_dms_</Trace>
      <Trace level="1" type="T">*** START APPLICATION TRACE ***</Trace>
      <Trace level="3" type="T">Document start</Trace>
      <Trace level="3" type="T">Start tag [ns1:OpvoerenDocumentRequest]</Trace>
      <Trace level="3" type="T">Add raw attribute [ xmlns:ns1="urn:kadaster-nl:SERVICES:DMS:Opvoeren:ZI_KAD_DMS_MAIN"]</Trace>
      <Trace level="3" type="T">Start tag [DocumentInfoRecord]</Trace>
      <Trace level="3" type="T">Start tag [Type]</Trace>
      <Trace level="3" type="T">Put value [302]</Trace>
      <Trace level="3" type="T">Close tag [Type]</Trace>
      <Trace level="3" type="T">Start tag [Omschrijving]</Trace>
      <Trace level="3" type="T">Put value [Apeldoorn]</Trace>
      <Trace level="3" type="T">Close tag [Omschrijving]</Trace>
      <Trace level="3" type="T">Close tag [DocumentInfoRecord]</Trace>
      <Trace level="3" type="T">Close tag [ns1:OpvoerenDocumentRequest]</Trace>
      <Trace level="3" type="T">Document end</Trace>
      <Trace level="1" type="T">*** END APPLICATION TRACE ***</Trace>
      <Trace level="2" type="T">Java mapping com/sap/xi/tf/_mm_mail_to_dms_ completed. (executeStep() of com.sap.xi.tf._mm_mail_to_dms_).</Trace>
      <Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
      <Trace level="3" type="T">Attached will be Deleted cid:payload-001708D1A20E1DDDAD97A993DAB6CB91(@)sap.com</Trace>
      <Trace level="3" type="T">Attached will be Deleted cid:payload-001708D1A20E1DDDAD97A993DB0E4B91(@)sap.com</Trace>
      <Trace level="1" type="T">ContentType application/xml</Trace>
      </Trace>
      </Trace>
      </Trace>
    Thanks

  • Synchronous RFC -- SOAP Scenario: problem with SOAP Response/Fault Mapping

    Hi,
    I've a synchronous RFC --> PI --> SOAP Scenario. The problem is that the message structure of the sending RFC doesn't match the Webservice Structure.
    The (SAP standard) RFC has just a Request / Response message structure. Part of the Response Message structure is a exception structure.
    The Webservice has a Request / Response message structure and in case of an error I get a SOAP:Fault.
    Problem now is that I cannot configure that scenario without usage of BPM as I will have to map SOAP:Response or SOAP:Fault to the RFC Response structure.
    Has anybody another idea to do that synchronous scenario (with usage of message mapping) without BPM?
    BR
    Holger

    1)
    you maus define 3 mapping.
    1)request
    2)response
    3)Fault
    in Interface mapping define at response boths (2-3) mapping. its clear??
    2)
    otherwise sometjhing is not clear, why do you want fault?? why dont you  get only response message. we implement this kind of response:
    <response_MT>
    <ID> (error ID)
    <system> (target system) 
    <error> (Error Description)
    </response>
    by this way fault message is not needed. but if you must have it just follow the top of message else, propose second.
    Thanks
    Rodrigo
    Thanks
    Rodrigo
    Edited by: Rodrigo Pertierra on Feb 25, 2008 11:52 AM

  • 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

  • Lookup value mapping table through message mapping.

    Hello All,
    I am working on a graphical mapping (message mapping). When trying to map the source message to the target message, I need to find out it a particular <b>key</b> exists in the <b>value mapping table</b>. Depending on the result, I need to map different source fields to the target field.
    Is there any inbuilt function which will allow me to do a lookup on a value mapping table, or is it possible to lookup a value mapping table from a UDF?
    Please help!
    Warm Regards,
    Keerti

    Hi,
    Please see the below links for Value mapping ..
    Value mapping /people/sukumar.natarajan/blog/2006/10/23/accessing-value-mapping-defined-in-directory-using-java-functions
    Value mapping in XSLT /people/sreekanth.babu2/blog/2005/01/05/design-time-value-mappings-in-xslt
    Value Mapping replication - /people/sreekanth.babu2/blog/2005/02/23/value-mapping-replication
    Also see
    https://www.sdn.sap.com/irj/sdn/advancedsearch?query=value%20mapping%20in%20xi&cat=sdn_weblog
    /people/community.user/blog/2007/01/08/valuemapping-using-the-graphical-mapping-tool
    /people/alessandro.guarneri/blog/2006/03/27/sap-xi-lookup-api-the-killer
    https://www.sdn.sap.com/irj/sdn/advancedsearch?query=value%20mapping%20in%20xi&cat=sdn_weblog
    Regards
    Pradeep N

Maybe you are looking for