SAP PI 7.3 AEX Multi mapping: Mapping failed with exception

Hi
I am encountering an issue with the multi mapping in SAP PI 7.3 AEX system.
Requirement for my interface is to pull a single file which has multiple records from the file directory.
Interface need to split the single file to multiple files.
For this I have implemented multi mapping in SAP PI 7.3(Stand alone Java) to split the single file to multiple files just like the way it is done in SAP PI 7.1. Tried this interface in SAP PI 7.1 system and works fine end to end.
I have done the testing in mapping(Test tab) in operational mapping, I could see response is getting generated successfully.
But when testing end to end,
I could see message is getting failed during mapping with the exception "failed to execute: ArrayIndexOutOfBoundsException: 1” .
Note:
Occurrence has been changed to 0..unbounded in the Signature tab of the message mapping & same interface works fine in SAP PI 7.1
Our system is currently on SAP PI 7.31 (AEX) SP05 Patch "0".
Kindly let me know if someone has any idea on this particular exception in SAP PI 7.31 multi mapping Interface.
Thanks & Regards
Ram

Hi Jegathees,
Thanks for your reply.
In PI 7.31:
As we are doing 1:n mapping, I have maintained the source side occurrence as "1" and target side occurrence as "0..unbounded" in the signature tab of message mapping.
Even in PI 7.11 Occurrences were maintained in the same way.
Can you please give me more details of how exactly multimapping in PI 7.31 is different with respect to PI 7.1
Thanks & Regards
Ram

Similar Messages

  • SAP Strategy Management 7.0 SSM Component Deployment failed with JSPM

    Dear experts,
    i have installed a SAP Netweaver CE 7.1 on Windows Server 2003 Enterprise x64 with MS SQL and i wish to install now SAP Strategy Management 7.0 with JSPM Tool.
    I have copied the CPMSTRMGMAPC00_0.SCA file on the usr\sap\trans\EPS\in\ directory and the deployment precessus failed with error before the AS JAVA has been restarted.
    How can i manage this problem? Any suggestion is welcomed.
    Thank you very much.
    Best regards,
    Pascal.

    Any ideas?
    Here is the F:\usr\sap\PI7\J71\j2ee\JSPM\log\log_2009_06_15_12_51_48\deploy_2009-06-15_14-56-58.log
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.7.1006]/>
    <!NAME[F:\usr\sap\PI7\J71\j2ee\JSPM\log\log_2009_06_15_12_51_48\deploy_2009-06-15_13-07-03.log]/>
    <!PATTERN[deploy_2009-06-15_13-07-03.log]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%25d[%6s]:%m)]/>
    <!ENCODING[UTF8]/>
    <!LOGHEADER[END]/>
    Jun 15, 2009 1:07:03 PM  [Info  ]:DC API is trying to connect to 'sap-pi7:57104'
    Jun 15, 2009 1:07:03 PM  [Info  ]:DC API has Connected to 'sap-pi7:57104'
    Jun 15, 2009 1:07:03 PM  [Path  ]:+++++ Starting  V A L I D A T E action +++++[ deployerId=2 ]. timerId=7
    Jun 15, 2009 1:07:03 PM  [Path  ]:Selected archives for validation. [ deployerId=2 ]
    Jun 15, 2009 1:07:03 PM  [Path  ]:
    sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca
    Jun 15, 2009 1:07:03 PM  [Debug ]:Got full sdu path '
    sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca'
    Jun 15, 2009 1:07:03 PM  [Path  ]:component version handling rule is UpdateLowerVersionsOnly.[ deployerId=2 ]
    Jun 15, 2009 1:07:03 PM  [Path  ]:deployment workflow strategy is safety deploy strategy.[ deployerId=2 ]
    Jun 15, 2009 1:07:03 PM  [Path  ]:life cycle deploy strategy is disable LCM deploy strategy.[ deployerId=2 ]
    Jun 15, 2009 1:07:03 PM  [Path  ]:Error strategies[ deployerId=2 ]:
    Jun 15, 2009 1:07:03 PM  [Path  ]:error action 'DeploymentAction' is 'OnErrorStop'
    Jun 15, 2009 1:07:03 PM  [Path  ]:error action 'PrerequisitesCheckAction' is 'OnErrorSkipDepending'
    Jun 15, 2009 1:07:03 PM  [Debug ]:deployer initialized successfully:[id:#8, elapsed: 0 ms.].[ deployerId=2 ]
    Jun 15, 2009 1:07:03 PM  [Debug ]:Total time:[#8: 0.0 sec].[ deployerId=2 ]
    Jun 15, 2009 1:07:03 PM  [Info  ]:Start validating.[ deployerId=2 ]
    Jun 15, 2009 1:07:06 PM  [Path  ]:Validating completed. Preparing the validation result.
    Jun 15, 2009 1:07:06 PM  [Path  ]:
    Sorted Items -
         1. Client path '
    sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca --> xappscpmsm~strategymanagement.sda'
         Sdu info :name 'xappscpmsm~strategymanagement', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465295', software type ('J2EE', sub type ''), dependencies :[none]
              Deploy status is 'Admitted'
         2. Client path '
    sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca'
         Sdu info :name 'CPM_STR_MGM_APC', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '1000.700.0.1.0.20080221071842'
              Deploy status is 'Admitted'
    Deployment Items -
         1. Client path '
    sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca'
         Sdu info :name 'CPM_STR_MGM_APC', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '1000.700.0.1.0.20080221071842'
              Deploy status is 'Admitted'
              Time statistics:
              Contained DCs:
              1.1:name 'xappscpmsm~strategymanagement', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465295', software type ('J2EE', sub type ''), dependencies :[none]          
                        Deploy status is 'Admitted'
              1.2:name 'xappscpmsm~strategymanagementactions', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465041', software type ('J2EE', sub type ''), dependencies :[none]          
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:2465041'.
              1.3:name 'xappscpmsm~strategymanagementdoc', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465046', software type ('J2EE', sub type ''), dependencies :[none]          
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:2465046'.
              1.4:name 'xappscpmsm~strategymanagementdic', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465042', software type ('JDDSCHEMA', sub type ''), dependencies :[none]          
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:2465042'.
    Jun 15, 2009 1:07:06 PM  [Info  ]:+++ Validation finished with status 'Success' +++[ deployerId=2 ]
    Jun 15, 2009 1:07:06 PM  [Path  ]:+++++ End  V A L I D A T E action +++++[ deployerId=2 ]. Total time:[#7: 3.016 sec]
    Jun 15, 2009 1:07:06 PM  [Path  ]:+++++ Starting  D E P L O Y action +++++ [ deployerId=2 ] [ timerId=9]
    Jun 15, 2009 1:07:06 PM  [Path  ]:Selected archives for deployment. [ deployerId=2 ]
    Jun 15, 2009 1:07:06 PM  [Path  ]:
    sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca
    Jun 15, 2009 1:07:06 PM  [Debug ]:Got full sdu path '
    sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca'
    Jun 15, 2009 1:07:06 PM  [Path  ]:component version handling rule is UpdateLowerVersionsOnly.[ deployerId=2 ]
    Jun 15, 2009 1:07:06 PM  [Path  ]:deployment workflow strategy is safety deploy strategy.[ deployerId=2 ]
    Jun 15, 2009 1:07:06 PM  [Path  ]:life cycle deploy strategy is disable LCM deploy strategy.[ deployerId=2 ]
    Jun 15, 2009 1:07:06 PM  [Path  ]:Error strategies[ deployerId=2 ]:
    Jun 15, 2009 1:07:06 PM  [Path  ]:error action 'DeploymentAction' is 'OnErrorStop'
    Jun 15, 2009 1:07:06 PM  [Path  ]:error action 'PrerequisitesCheckAction' is 'OnErrorStop'
    Jun 15, 2009 1:07:06 PM  [Debug ]:deployer initialized successfully:[id:#11, elapsed: 15 ms.].[ deployerId=2 ]
    Jun 15, 2009 1:07:06 PM  [Debug ]:Total time:[#11: 0.015 sec].[ deployerId=2 ]
    Jun 15, 2009 1:07:06 PM  [Path  ]:Starting deployment.[ deployerId=2 ]
    Jun 15, 2009 1:07:17 PM  [Debug ]:clusterRestartTriggered for transactionId:223, clusterEventAction:cluster restart triggered
    Jun 15, 2009 1:07:17 PM  [Debug ]:Mark transaction '223' as offline phase.
    Jun 15, 2009 1:07:17 PM  [Info  ]:+++ Performing offline deployment. Server is being restarted +++.The timeout for the operation is:  86400 sec.
    Jun 15, 2009 1:07:17 PM  [Path  ]:+++ Wait for server response +++. Elapsed: 0 ms.
    Jun 15, 2009 1:07:47 PM  [Path  ]:+++ Wait for server response +++. Elapsed: 484 ms.
    Jun 15, 2009 1:08:19 PM  [Path  ]:+++ Wait for server response +++. Elapsed: 30484 ms.
    Jun 15, 2009 1:08:49 PM  [Path  ]:+++ Wait for server response +++. Elapsed: 62140 ms.
    Jun 15, 2009 1:09:19 PM  [Path  ]:+++ Wait for server response +++. Elapsed: 92156 ms.
    Jun 15, 2009 1:09:49 PM  [Path  ]:+++ Wait for server response +++. Elapsed: 122171 ms.
    Jun 15, 2009 1:10:19 PM  [Path  ]:+++ Wait for server response +++. Elapsed: 152171 ms.
    Jun 15, 2009 1:10:49 PM  [Path  ]:+++ Wait for server response +++. Elapsed: 182296 ms.
    Jun 15, 2009 1:11:20 PM  [Path  ]:+++ Wait for server response +++. Elapsed: 212905 ms.
    Jun 15, 2009 1:12:22 PM  [Info  ]:Engine is up and running. Wait for engine deployment result.
    Jun 15, 2009 1:12:22 PM  [Debug ]:DC API will create new CM
    Jun 15, 2009 1:12:52 PM  [Path  ]:+++ Wait for server response +++. Elapsed: 305686 ms.
    Jun 15, 2009 1:13:22 PM  [Path  ]:+++ Wait for server response +++. Elapsed: 335685 ms.
    Jun 15, 2009 1:13:53 PM  [Path  ]:+++ Wait for server response +++. Elapsed: 365701 ms.
    Jun 15, 2009 1:14:23 PM  [Path  ]:+++ Wait for server response +++. Elapsed: 395701 ms.
    Jun 15, 2009 1:14:53 PM  [Path  ]:+++ Wait for server response +++. Elapsed: 425763 ms.
    Jun 15, 2009 1:15:24 PM  [Path  ]:+++ Wait for server response +++. Elapsed: 456856 ms.
    Jun 15, 2009 1:15:54 PM  [Path  ]:+++ Wait for server response +++. Elapsed: 487012 ms.
    Jun 15, 2009 1:15:57 PM  [Info  ]:Engine is up and running. Wait for engine deployment result.
    Jun 15, 2009 1:15:57 PM  [Info  ]:server is online, time:[id:#10, elapsed: 520059 ms.]
    Jun 15, 2009 1:15:57 PM  [Path  ]:Deployment completed. Preparing the deployment result.[ deployerId=2 ]
    Jun 15, 2009 1:15:57 PM  [Path  ]:
    Sorted Items -
         1. Client path '
    sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca --> xappscpmsm~strategymanagement.sda'
         Sdu info :name 'xappscpmsm~strategymanagement', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465295', software type ('J2EE', sub type ''), dependencies :[none]
              Deploy status is 'Aborted'
              Description:'1. class com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException
               -> class java.lang.NullPointerException'.
         2. Client path '
    sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca'
         Sdu info :name 'CPM_STR_MGM_APC', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '1000.700.0.1.0.20080221071842'
              Deploy status is 'Aborted'
              Description:'1. Contains Aborted deployment component:
    sdu id: sap.com_xappscpmsm~strategymanagement
    sdu file path: F:\usr\sap\PI7\J71\j2ee\cluster\server0\.\temp\tcbldeploy_controller\archives\223\CPMSTRMGMAPC00_0_sca1245064026979\DEPLOYARCHIVES\xappscpmsm~strategymanagement.sda
    version status: NEW
    deployment status: Aborted
    description: 1. class com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException
               -> class java.lang.NullPointerException'.
    Deployment Items -
         1. Client path '
    sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca'
         Sdu info :name 'CPM_STR_MGM_APC', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '1000.700.0.1.0.20080221071842'
              Deploy status is 'Aborted'
              Description:'1. Contains Aborted deployment component:
    sdu id: sap.com_xappscpmsm~strategymanagement
    sdu file path: F:\usr\sap\PI7\J71\j2ee\cluster\server0\.\temp\tcbldeploy_controller\archives\223\CPMSTRMGMAPC00_0_sca1245064026979\DEPLOYARCHIVES\xappscpmsm~strategymanagement.sda
    version status: NEW
    deployment status: Aborted
    description: 1. class com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException
               -> class java.lang.NullPointerException'.
              Time statistics:
              Contained DCs:
              1.1:name 'xappscpmsm~strategymanagementdic', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), dependencies :[none]          
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:2465042'.
              1.2:name 'xappscpmsm~strategymanagementdoc', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), dependencies :[none]          
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:2465046'.
              1.3:name 'xappscpmsm~strategymanagement', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465295', software type ('J2EE', sub type ''), dependencies :[none]          
                        Deploy status is 'Aborted'
              Time statistics( ms ):
                   1.deployment : 34906
                        1.1.Notify:Event triggered : 157
                        1.2.Disable LCM deployment : 34656
                             1.2.1.Perform delivery : 34656
                                  1.2.1.1.Application Deployer : 34656
                        1.3.Notify Observers : 15
                             1.3.1.Persist in storage : 15
                        1.4.Notify:Event performed : 78
                   2.Persist in storage : 16
                        Description:'1. class com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException
               -> class java.lang.NullPointerException'.
              1.4:name 'xappscpmsm~strategymanagementactions', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), dependencies :[none]          
                        Deploy status is 'AlreadyDeployed'
                        Description:'1. Already deployed component has version:2465041'.
    Jun 15, 2009 1:15:57 PM  [Info  ]:
    Deploy Result Description: Deployment exception occurred during deploy online data. Reason :An error occurred while deploying the deployment item 'sap.com_xappscpmsm~strategymanagement'.; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of sap.com_xappscpmsm~strategymanagement. Cannot deploy it.
    [ deployerId=2 ]
    Jun 15, 2009 1:15:57 PM  [Info  ]:+++ Deployment finished with status 'Error' +++.[ deployerId=2 ][#10: 530.465 sec]
    Jun 15, 2009 1:15:57 PM  [Path  ]:+++++ End  D E P L O Y action +++++[ deployerId=2 ]. Total time:[#9: 530.465 sec]
    Jun 15, 2009 1:15:57 PM  [Debug ]:Incorrect client ID. The stub is not connected yet.
    Jun 15, 2009 1:15:57 PM  [Debug ]:Incorrect client ID. The stub is not connected yet.

  • Install of SAP HANA Studio Dev Ed v1.00.80 fails with "Could not create the Java Virtual Machine"

    Hello,
    Scope: JVM error during initial install of SAP HANA Studio Developer Edition v1.00.80, Win86/32bit
    Source: installation files pulled from HANA Studio tab at https://hanadeveditionsapicl.hana.ondemand.com/hanadevedition/, which is a link from the main HANA site of http://scn.sap.com/community/developer-center/hana.  zip folder: "sap_hana_win32_studio_rev80"
    Targeted O/S: Windows 7, 32-bit, local Java is SE 7, update 67.   Java environment has been confirmed via checks provided at http://www.java.com/en/download/manual.jsp
    Actions taken:
    Attempted to update the installation's eclipse.ini file by reducing the -Xmx value; see details below.
    Read thru postings such as http://scn.sap.com/thread/3390626 and the threads it recommended.
    Checked OSS (ie Note 1859686 - HANA Studio does not start)
    Description of installation error:
    Shortly after executing "hdbinst", it fails with the error "Could not create the Java Virtual Machine".  I've verified that there is nearly 3G of memory free.  What I did notice, as shown in the attached files, is that Eclipse is part of this installation and it's pre-loaded with the "eclipse.ini".  I firmly believe the solution could be to reduce parameter "-Xmx1024m" to "-Xmx512m" but it's a catch-22 because even after updating eclipse.ini (in installation folder C:\Program Files\SAP\hdbstudio\tmp_p2director2014.08.13_13.36.44\director), the install program requires that the "hdbstudio" folder to be empty upon restarting it.
    Since the installation is basically a package with a lot of .jar files, there is no eclipse.ini file available in the source install folder; otherwise, updating it there would be the easiest solution if that option were available. The file is only available in the targeted deployment folder above.
    If you have encountered this same error and were able to resolve it, I would be grateful to know of your solution.  Thanks very much.
    FYI: the HANA Client installed with no issues.
    Jim Cleek
    FYI: the images below reflect the sequence of images produced during the installation.
    after clicking OK above, the screen below gets updated (see the "is not empty" msg).
    Below is the eclipse.ini file located in the deployed/target folder:
    Message was edited by: Jim Cleek
    FYI: Using information from the SAP HANA Database - Studio Installation and Update Guide, I tried to override the installation's use of its eclipse.ini file by passing my own modified version (with "-Xmx512m") of that file that was placed in a separate folder.  The cmd used via DOS window was "hdbsetup.exe -a studio --configfile=C:\Users\Admin\Downloads\eclipse.ini" and even though it successfully launched the SAP HANA Lifecycle Management gui, it failed on the first step with the same JVM create error as above because it appears to have used its own eclipse.ini file, which has "-Xmx1024m".

    Update: a message was opened with SAP but unfortunately they could not provide a resolution for this particular scenario.  They admitted that the eclipse.ini file cannot be updated since it is bundled as part of the installation package.  One point to make that I did not make before was that this was being attempted on an Oracle VirtualBox (4.3.10); the SAP HANA contact said he assumed that SAP has not tested this particular scenario, thus it could not be supported.
    Resolution: the end result was to abort trying to install SAP HANA Client and Studio on the Oracle VirtualBox but to install it locally on my own desktop, which runs on Windows 7 Enterprise 64-bit with 8G of memory.  The SAP HANA files below were downloaded, extracted and installed successfully in the order shown.
    FYI: the Studio installation detected that a 64-bit version of Java was not installed so I installed that and then adjusted the User environmental variable JAVA_HOME to point to that new path, leaving the System variable still pointing to the pre-existing 32-bit Java path.
    SAPCAR 7.20 -> Windows on x64 64bit:  SAPCAR_315-20010453.EXE
    IMDB_CLIENT100_80_0-10009664.SAR   Revision 80 for SAP HANA CLIENT 1.00
    Support Package SAP HANA CLIENT 1.00 Windows on x64 64bit
    IMC_STUDIO100_80_0-20007647.SAR   Revision 80 for SAP HANA STUDIO 1.00
    Support Package SAP HANA STUDIO 1.00 Windows on x64 64bit
    jre-7u67-windows-x64.exe - http://www.oracle.com/technetwork/java/javase/downloads/jre7-downloads-1880261.html
    Jim Cleek
    HP Enterprise Services

  • Import Map file failes with single/Multiple Occurance

    Hi All,
    Using a file I mapped the source and target structures.. The source file has one multiple occurance node . so I used look up option in source table and mapped with target fields...saved the map..
    When I used the following XML file .. I used the same map created befoe... I see the Remote System fields are not failed to map to target structure.. How can I get rid of this issue....
    <Product>
    --<Name>Rajeev</Name>
    --<REMOTE_SYSTEM>
    <Z_MDM_REMOTE_SYSTEM>
           <Z_MDM_SYSTEM_NAME>Panaroma AW Customer ID</Z_MDM_SYSTEM_NAME>
         <Z_MDM_VALUE>600013</Z_MDM_VALUE>
         <Z_MDM_VALUE1>600011</Z_MDM_VALUE1>
         <Z_MDM_VALUE2>600012</Z_MDM_VALUE2>
    </Z_MDM_REMOTE_SYSTEM>
    --<REMOTE_SYSTEM>
    </Product>
    Using above I saved the map.. Its fine.. I am able to import data in to MDM..
    When the file has multiple values of remote system as shown below then field are unmapped... vice versa is also the same..
    <Product>
    --<Name>Rajeev</Name>
    --<REMOTE_SYSTEM>
    <Z_MDM_REMOTE_SYSTEM>
           <Z_MDM_SYSTEM_NAME>Panaroma AW Customer ID</Z_MDM_SYSTEM_NAME>
         <Z_MDM_VALUE>600013</Z_MDM_VALUE>
         <Z_MDM_VALUE1>600011</Z_MDM_VALUE1>
         <Z_MDM_VALUE2>600012</Z_MDM_VALUE2>
    </Z_MDM_REMOTE_SYSTEM>
    <Z_MDM_REMOTE_SYSTEM>
           <Z_MDM_SYSTEM_NAME>Panaroma AW Customer ID</Z_MDM_SYSTEM_NAME>
         <Z_MDM_VALUE>600013</Z_MDM_VALUE>
         <Z_MDM_VALUE1>600011</Z_MDM_VALUE1>
         <Z_MDM_VALUE2>600012</Z_MDM_VALUE2>
    </Z_MDM_REMOTE_SYSTEM>
    --<REMOTE_SYSTEM>
    </Product>
    Do I need to create a seperate map for multiple iteration and single occurance..OR missing some thing? Please advice..
    Thanks
    Rajeev

    HI Ravi,
    May be I took the wrong example..
    I am not talking about remote systems... I am talking about XML source file.. If the XML source file consist of single occurance of any qualifier table then those qualifier table fields are not mapping.. IF I used the base file as multiple occurance Qualifier table....
    In the same way if I use base file as single occurance of Qualifer table .. Qualifier Fields are not getting mapped if the source file is single occurance..
    Suppose :If I use the base file as this and save the map.. I am able to import files whcih are single occurance of EMAIL...
    Fields are not getting mapped if the EMAIL occurnace is multiple.....
    <Product>
    --<Name>Rajeev</Name>
    --<EMAIL>
    <Z_MDM_EMAIL>
    <ID>ABC_yahocom</ID>
    <TYPE>TEMP</TYPE>
    </Z_MDM_EMAIL>
    --</EMAIL>
    </Product>
    In the same way: If I use the following XMl as base and create a map and save it.. Able to import files which had email occurance multiple.. Unable to import data and the fields are not mapped ......
    <Product>
    --<Name>Rajeev</Name>
    --<EMAIL>
    <Z_MDM_EMAIL>
    <Z_MDM_EMAIL>
    <ID>ABC_yahocom</ID>
    <TYPE>TEMP</TYPE>
    </Z_MDM_EMAIL>
    <Z_MDM_EMAIL>
    <ID>CDE_yahocom</ID>
    <TYPE>TEMP</TYPE>
    </Z_MDM_EMAIL>
    --</EMAIL>
    </Product>
    Please advise.. Thanks Rajeev.

  • Nokia 6700 maps download fails

    Hi,
    I have a nokia 6700 with Nokia Maps. When I want to update maps, it fails with an internal error message. Can anyone help me?
    Thanks,
    Renarios
    Solved!
    Go to Solution.

    Glad you managed to sort it out yourself  enjoy your phone  !!
    If I have helped at all, a click on the White Star is always appreciated :
    you can also help others by marking 'accept as solution' 

  • Error in Multi Message Mapping

    Hi,
    I am getting the following error in my multi message mapping scenario where I am trying to create 2 different output files from a single input file based on some condition. I tested the message mapping by using a test file and it works fine, but when I use the same file and test it end to end the scenario is failing with the following error.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--
    Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="MAPPING">GENERIC</SAP:Code>
      <SAP:P1>Split mapping created no messages</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Split mapping created no messages</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Is there something wrong with my configuration?
    The trace has the following content.
    Trace level="1" type="T">*** START APPLICATION TRACE ***</Trace>
      <Trace level="3" type="T">Document start</Trace>
      <Trace level="3" type="T">Start tag [ns0:Messages]</Trace>
      <Trace level="3" type="T">Add raw attribute [ xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"]</Trace>
      <Trace level="3" type="T">Start tag [ns0:Message1]</Trace>
      <Trace level="3" type="T">Close tag [ns0:Message1]</Trace>
      <Trace level="3" type="T">Start tag [ns0:Message2]</Trace>
      <Trace level="3" type="T">Close tag [ns0:Message2]</Trace>
      <Trace level="3" type="T">Close tag [ns0:Messages]</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/_Employee1_MT_To_Employee1_MT_AND_Employee2_MT_MM_ completed. (executeStep() of com.sap.xi.tf._Employee1_MT_To_Employee1_MT_AND_Employee2_MT_MM_).</Trace>
      <Trace level="3" type="T">Message Type 1 Number of Messages 0</Trace>
      <Trace level="3" type="T">Message Type 2 Number of Messages 0</Trace>
      <Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
      </Trace>
      <Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--
      -->
      <Trace level="3" type="T">Persisting message Status = 014</Trace>
      <Trace level="3" type="T">Message version 001</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </SAP:Trace>

    Hi,
    The scenario I am trying to test is a multi mapping scenario where I am trying to split one source message and create two target messages by using two different receiver interfaces, one for each message.
    I am on PI 7.1 and when I test message mapping and operation mapping using the payload from SXMB_MONI, it is successful. Whereas when I test the scenario end to end I am getting the following error messages:
    Operation Mapping
    Employee_Out_SI_To_Employee1_In_SI_AND_Employee2_In_SI_OM
    Name
    Employee_Out_SI_To_Employee1_In_SI_AND_Employee2_In_SI_OM
    Namespace
    http://accenture.com/1:N_multi-mapping
    Runtime error
    Split mapping created no messages
    Start tag ns0:Messages Add raw attribute xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge" Start tag ns0:Message1 Close tag ns0:Message1 Start tag ns0:Message2 Close tag ns0:Message2 Close tag ns0:Messages
    Could someone please help
    Cheers,
    S

  • Multi level mapping in PI. eg:  A = B= C w/o BPM

    Hi All,
    I want to do multi level mapping withou BPM i.e Structure A to structure B mapping and Structure B to Structure C i.e
    A=>B=> C. Let me know proc in PI 7.0/7.1 without BPM. Is this possible through Interface mapping or Interface determination ?
    Thanks,
    Jogula Ramesh

    Hi Ramesh,
    Finally you want Strcuture C as the out from PI System,?? if Yes then develop two mappings(A>B,B>C)and add it in Interface mapping,we can add any number of mappings in Interface mappings.
    The source message to Interface mapping is A and receiver would be C.
    This is will work.
    Regards,
    Raj

  • Multi-Message Mapping based on value of field - (Without BPM)

    Hi.
    I am having a bit of difficulty with multi-message mapping without BPM. I want to map to message1 & message2 based on a field in the rows of the source structure.
    e.g.
    row1-Source-Field1=> (if equal 0)   => <b>Message1</b>-field1.
    row2-Source-Field1=> (if equal 10) => <b>Message2</b>-field1.
    To attempt to do this, I use the conditions in the graphical mapper:
    if row-Source-Field1 = 0   => Map "Row to MessageType1".
    if row-Source-Field1 = 10 => Map "Row to MessageType2".
    However when I test this the mapping only seems to consider the first row value in row-Source-Field1 and ignores the fact that row two has a value of 10. I think this has something to do with contexts etc..
    I would appreciate any help please.
    Regards.
    Mick.

    in that case try this out
    row1-source-field1 (remove context) -- UDF -splitbyvalue-target
    UDF1(for message 1)
    for(int i=0;i<field1.length;i++)
    if(field1<i>.equals("0"))
    result.addValue(<field to be mapped><i>);
    UDF2(for message 2)
    for(int i=0;i<field1.length;i++)
    if(field1<i>.equals("10"))
    result.addValue(<field to be mapped><i>);

  • Query Regarding Multi-Message Mapping in Interface Mapping.

    Hi All,
    I've a query that can we use Multi-Message Mapping in Interface Mapping if:
    One mapping structure is simple one-2-one mapping and
    Second mapping is calling a stored procedure.
    Please give me some links if the answer is YES.
    Thanks in Advance.
    Regards,
    Sreedhar.
    Edited by: Sreedhar Av on Oct 12, 2009 1:26 PM

    Hi,
    Your question not clear buddy..what i understood is..
    If you want execute multiple message mappings in Interface mapping we can ,just add two mapping programs in interface mapping.first mapping program output is input to the second mapping program.
    If first mapping program is very simple,if you want to execute stored procedure in second level mapping write used defned fun ction to conect to data base or create JDMC receiver communication channel ,cal the communictaion channel in udf.write stored procedure in UDF.
    SEARCH for more info in sdn how to perform DBLOOKUPS.
    regards,
    Raj

  • Connecting to EMS fails with No mapping for the Unicode character exists in the target multi-byte code page

    I am getting the following error when trying to connect to both my exchange servers.
    New-PSSession : [ex2013-002.nafa.ca] Connecting to remote server ex2013-002.nafa.ca failed with the following error
    message : No mapping for the Unicode character exists in the target multi-byte code page. For more information, see
    the about_Remote_Troubleshooting Help topic.
    At line:1 char:12
    + $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri ht ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
       gTransportException
        + FullyQualifiedErrorId : 1113,PSSessionOpenFailed
    EMS used to connect ok. I am not sure if there is any connection but Outlook was installed recently on the exchange server to enable mailbox level backups.
    Any help would be appreciated.
    Steve Hurst

    Hello Steve,
    Firstly, you cannot install Outlook with Exchange because they share certain dll files.
    About the EMS question, I suggest we try rebuilding the powershell virtual directory. If it still does not work, check the application log for more referernce.
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Could Mapping Template  be used in Multi Message mapping

    I had a 1:1 message mapping: MM_A
    but later i foudd that the mapping should be 1:n
    Multi message mapping
    so firstly i created mapping template of MM_A
    but the template doesn't work when i am doing the multi mapping.
    Could Mapping Template  be used in Multi Message mapping?
    Thank you very much

    Hi leo,
    <i>
    Could Mapping Template be used in Multi Message mapping?</i>
    Yes it can be used......
    Regards,
    Abhy

  • Where to find multi-layered maps???

    I'm making a documentary about WWII. Can anyone tell me where I could find a multi-layered map of 1930s Europe with each country on its own layer, like that when I do the spill effect illustrating the invasions of Poland, etc, the spill effect will pour into each country at a time.
    Thanks very much in advance,
    - Nicholas

    I could be wrong, but I would suspect that you will not find such a thing anywhere. But it would be a simple process to make your own in Photoshop or equivalent image editor.

  • Need help in Component Mapping - "Mapping has not been completed" !

    Hi Experts,
    i read the SAP Galileo Press Book "Web Dynpro for ABAP" and i try in Chapter 2 some exercise for Multi-Component-Architecture.
    In this Chapcter i have 2 Components "Main" and "Nations". In one of this Components i created Node´s and Attributes in the Context of Component-Controller. After this i changed to the View and tryed to mapping the Component-Controller and View.
    Before i explain what i have done, i want show us the following Error:
    Note
    -> The following error text was processed in system FID : Adapter error in TEXT_VIEW "TV_LANDX50" of view "ZZWDC_CHAP02_NATIONS.V_NATIONS": Context binding of property TEXT cannot be resolved: The Mapping to Node COMPONENTCONTROLLER.1.T005T Has Not Been Completed.
    -> The error occurred on application server fidvfid0_FID_00 and in work process 0 .
    -> The termination type was: RABAX_STATE
    -> The ABAP call hierarchy was:
    -> Method: RAISE_FOR of program CX_WDR_ADAPTER_EXCEPTION======CP
    -> Method: RAISE_BINDING_EXCEPTION of program CL_WDR_VIEW_ELEMENT_ADAPTER===CP
    -> Method: GET_BOUND_ELEMENT of program CL_WDR_VIEW_ELEMENT_ADAPTER===CP

    ETN_58 wrote:
    Hi Experts,
    >
    > i read the SAP Galileo Press Book "Web Dynpro for ABAP" and i try in Chapter 2 some exercise for Multi-Component-Architecture.
    >
    > In this Chapcter i have 2 Components "Main" and "Nations". In one of this Components i created Node´s and Attributes in the Context of Component-Controller. After this i changed to the View and tryed to mapping the Component-Controller and View.
    >
    > Before i explain what i have done, i want show us the following Error:
    >
    > Note
    >
    > -> The following error text was processed in system FID : Adapter error in TEXT_VIEW "TV_LANDX50" of view "ZZWDC_CHAP02_NATIONS.V_NATIONS": Context binding of property TEXT cannot be resolved: The Mapping to Node COMPONENTCONTROLLER.1.T005T Has Not Been Completed.
    > -> The error occurred on application server fidvfid0_FID_00 and in work process 0 .
    > -> The termination type was: RABAX_STATE
    > -> The ABAP call hierarchy was:
    > -> Method: RAISE_FOR of program CX_WDR_ADAPTER_EXCEPTION======CP
    > -> Method: RAISE_BINDING_EXCEPTION of program CL_WDR_VIEW_ELEMENT_ADAPTER===CP
    > -> Method: GET_BOUND_ELEMENT of program CL_WDR_VIEW_ELEMENT_ADAPTER===CP
    hello,
    i think you missed mapping the layout with the context attributes....check out the property of all the elements in the view, if not mapped map it by selecting the attribute from the node.
    Regards,
    Sahai.S

  • Error when mapping a node with multiple occurence

    Hi,
    When I try to run my process where I have countries defines in a drop down box in the UI. I get the following error when completing this step. The target in the mapping is a dataobject which should be able to occure multiple times.
    Here is the mapping:
    Source:                                          Target:
    Country(Node)                             Country(Node)
           Country(String)
           Code(String)
    com.sap.glx.adapter.api.AdapterException: com.sap.glx.core.kernel.api.TransitionRollbackException: Exception during prepare, rolling back
    at com.sap.glx.process.adapter.bpmn.impl.BPMNAdapter.startProcesses(BPMNAdapter.java:1444)
    at com.sap.glx.process.adapter.bpmn.impl.BPMNAdapter.startProcesses(BPMNAdapter.java:1540)
    at com.sap.glx.process.impl.ProcessManagerImpl.startProcess(ProcessManagerImpl.java:938)
    at com.sap.glx.process.impl.ProcessManagerBean.startProcess(ProcessManagerBean.java:372)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
    at $Proxy453.startProcess(Unknown Source)
    at com.sap.tc.bpem.wdui.procstarter.procstarter.comp.ProcStarterComp.startProcess(ProcStarterComp.java:377)
    at com.sap.tc.bpem.wdui.procstarter.procstarter.comp.wdp.InternalProcStarterComp.startProcess(InternalProcStarterComp.java:175)
    at com.sap.tc.bpem.wdui.procstarter.procstarter.comp.ProcStarterCompView.onActionStartProcess(ProcStarterCompView.java:626)
    at com.sap.tc.bpem.wdui.procstarter.procstarter.comp.wdp.InternalProcStarterCompView.wdInvokeEventHandler(InternalProcStarterCompView.java:325)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:131)
    at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:72)
    at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:156)
    at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:91)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:468)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:52)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1505)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1319)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:154)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:114)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:80)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:571)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:602)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:523)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:270)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:729)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:256)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:258)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:457)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Caused by: com.sap.glx.core.kernel.api.TransitionRollbackException: Exception during prepare, rolling back
    at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.rollback(AbstractTransactionBase.java:517)
    at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:174)
    at com.sap.glx.core.kernel.mmtx.AbstractTransaction.commit(AbstractTransaction.java:77)
    at com.sap.glx.process.adapter.bpmn.impl.BPMNAdapter.startProcesses(BPMNAdapter.java:1429)
    ... 100 more
    Caused by: com.sap.glx.core.kernel.api.TransitionRollbackException: Exception during prepare, rolling back
    at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.rollback(AbstractTransactionBase.java:517)
    at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:174)
    at com.sap.glx.core.kernel.mmtx.AbstractTransaction.commit(AbstractTransaction.java:77)
    at com.sap.glx.core.kernel.mmtx.PrimaryTransaction.inPrepare(PrimaryTransaction.java:88)
    at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:172)
    ... 102 more
    Caused by: com.sap.glx.core.kernel.api.TransitionException: An exception occurred while executing the script "_Create_Customer:START_CONTROL_EVENT_Start_0(
          com.sap.glx.adapter.BPMNAdapter:Request request,
          com.sap.glx.adapter.BPMNAdapter:Event_0_Start_0_be1d130db236787f7569b7e757e720a8 event){
      initiator=request:initiator;
      kicker=request:kicker;
      parent=new com.sap.glx.adapter.BPMNAdapter:Instance_0_prcMido_be1d130db236787f7569b7e757e720a8(initiator, null, kicker, false);
      token=new com.sap.glx.adapter.BPMNAdapter:Token_0_prcMido_be1d130db236787f7569b7e757e720a8(parent, 0);
      exit=new com.sap.glx.adapter.BPMNAdapter:Exit();
      exit:addParameter(request);
      exit:addParameter(event);
      exit:onActivation("48EDB5A6AD6960C095D511DDA4DA0013E88242DB", parent, token);
      delete exit;
      controller=new com.sap.glx.adapter.internal.ExceptionAdapter:ExceptionController();
      controller:setContext(token);
      delete controller;
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_8_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      role_2=new com.sap.glx.adapter.internal.ContainerAdapter:View_0_Approver_PotentialOwners_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_0_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      role_3=new com.sap.glx.adapter.internal.ContainerAdapter:View_1_Enhance_PotentialOwners_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_10_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      role_4=new com.sap.glx.adapter.internal.ContainerAdapter:View_2_Administrators_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_1_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      role_5=new com.sap.glx.adapter.internal.ContainerAdapter:View_3_Creator_ExcludedOwners_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_3_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      role_6=new com.sap.glx.adapter.internal.ContainerAdapter:View_4_Approver_ExcludedOwners_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_2_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      context_0=new com.sap.glx.adapter.internal.ContainerAdapter:Context_0_DO_Customer2_be1d130db236787f7569b7e757e720a8(parent, scope, 0, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_4_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      role_7=new com.sap.glx.adapter.internal.ContainerAdapter:View_5_Create_Customer_In_MDM_PotentialOwners_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_5_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      role_9=new com.sap.glx.adapter.internal.ContainerAdapter:View_7_Enhance_ExcludedOwners_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_12_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      role_8=new com.sap.glx.adapter.internal.ContainerAdapter:View_6_Creator_PotentialOwners_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_7_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      view_11=new com.sap.glx.adapter.internal.ContainerAdapter:View_9_TextVariables_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_14_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      role_10=new com.sap.glx.adapter.internal.ContainerAdapter:View_8_Create_Customer_In_MDM_ExcludedOwners_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_6_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      context_1=new com.sap.glx.adapter.internal.ContainerAdapter:Context_1_DO_Customer_be1d130db236787f7569b7e757e720a8(parent, scope, 0, false);
      message=request:getData();
      mapper=new com.sap.glx.adapter.internal.Transformer:DataMapper();
      yves_in=new com.sap.glx.adapter.internal.Transformer:Data();
      yves_out=new com.sap.glx.adapter.internal.Transformer:Data();
      yves_in:setData("http://mido.se/", "$http://mido.se/:StartProcess2", message, "61302BDB06E4BB8B9F557FC1D1D2ACC9");
      data=context_1:getData();
      scope=new com.sap.glx.adapter.internal.TypeRegistry:GenericScope(null, "872ED00C5EA0B74AE6F92027833B9366");
      copy=scope:copy(data);
      delete scope;
      yves_out:setData("sap.com/glx/", "$sap.com/glx/:DO_Customer", copy, "872ED00C5EA0B74AE6F92027833B9366");
      mapper:map("48EDB5A6AD6960C395D511DD84C80013E88242DB_be1d130db236787f7569b7e757e720a8", yves_in, yves_out);
      data=yves_out:getData("sap.com/glx/", "$sap.com/glx/:DO_Customer", "872ED00C5EA0B74AE6F92027833B9366");
      context_1:setData(data);
      delete yves_in;
      delete yves_out;
      delete mapper;
      delete event;
    at com.sap.glx.core.kernel.execution.transition.ScriptTransition.execute(ScriptTransition.java:69)
    at com.sap.glx.core.kernel.execution.transition.Transition.commence(Transition.java:241)
    at com.sap.glx.core.kernel.mmtx.DirectNestedTransaction.inPrepare(DirectNestedTransaction.java:57)
    at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:172)
    ... 105 more
    Caused by: com.sap.glx.core.kernel.api.TransitionException: An exception occurred while executing the script command "mapper:map("48EDB5A6AD6960C395D511DD84C80013E88242DB_be1d130db236787f7569b7e757e720a8", yves_in, yves_out)"
    at com.sap.glx.core.kernel.trigger.config.Script.execute(Script.java:675)
    at com.sap.glx.core.kernel.execution.transition.ScriptTransition.execute(ScriptTransition.java:64)
    ... 108 more
    Caused by: java.lang.IllegalStateException: Occurrence violated
    at com.sap.glx.mapping.execution.implementation.node.SdoNode$PrimitiveItemContainer.appendNode(SdoNode.java:372)
    at com.sap.glx.mapping.execution.implementation.assignment.SetAssignment.assign(SetAssignment.java:23)
    at com.sap.glx.mapping.execution.implementation.Interpreter.mapPart(Interpreter.java:145)
    at com.sap.glx.mapping.execution.implementation.Interpreter.mapPart(Interpreter.java:151)
    at com.sap.glx.mapping.execution.implementation.Interpreter.mapPart(Interpreter.java:151)
    at com.sap.glx.mapping.execution.implementation.Interpreter.mapMapping(Interpreter.java:140)
    at com.sap.glx.mapping.execution.implementation.Interpreter.map(Interpreter.java:135)
    at com.sap.glx.core.internaladapter.Transformer$ClassRegistry$MapperClassManager$MapperClassHandler$MapperInvocationHandler.invoke(Transformer.java:1797)
    at com.sap.glx.core.internaladapter.Transformer$TransformerInvocationHandler.invoke(Transformer.java:399)
    at com.sap.glx.core.dock.impl.DockObjectImpl.invokeMethod(DockObjectImpl.java:459)
    at com.sap.glx.core.kernel.trigger.config.Script$MethodInvocation.execute(Script.java:247)
    at com.sap.glx.core.kernel.trigger.config.Script.execute(Script.java:670)

    Hi Michael,
    could you provide much more details about the source and target structures and the mappings you need to define?
    Something like :
    Source:
    Country (single or multiple? )
    ..Country (single or multiple? )
    ..Code (single or multiple? )
    Target
    Country (single or multiple? )  --> does it have the same type as the source node?
    In general If you try to assign a list of values to target which accepts single value you are most likely to get exception like the one given in your post.
    In other words let's assume :
    Country[]     Country
    ..Country------>Country
    ..Code
    this will throw exception at runtime in most of the cases.
    The reason is that the result of select Country/Country is a list with all Countries. And then the engine will try to assign this list to the single valued target node.
    Is this what you have described or it si something different?
    BTW for the example above there is a fix in SP1 and such kind of mappings are marked as erroneous.
    Best Regards,
    Boris

  • Interface mapping test successful, throws exception in BPM

    Hi.
    We are having a problem with an Interface mapping which works when
    tested in Integration Builder, but throws an Exception when it is part
    of the Transformation in a BPM.
    The scenarion is such:
    1. The sender calls the outbound interface using a web service.
    2. XI uses the input and passes to the Integration Process
    3. In the BPM, a LOGON message is built to call the web service as
    specified by an external web service . The input and
    output messages are just a single string, in which the other XML is
    embedded.
    4. XI receives a response from the web service call
    5. XI Extracts the sessionId from the response and combines it with the
    initial input (Step 1) to create the query for the query message in
    the web service.
    It is in Step 5 where the transformation fails, with an Exception in
    the DefaultTrace.trc as
    Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_LogonResponse_PropertySearchRequest_to_ExternalRequestSOAP_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Messages/ns0:Message1/ns1:EXTERNAL/REQUEST. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
    Thrown:
    MESSAGE ID: com.sap.aii.ibrun.server.mapping.rb_MappingRuntimeException.EXCEPTION_DURING_EXECUTE
    com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_LogonResponse_PropertySearchRequest_to_ExternalRequestSOAP_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Messages/ns0:Message1/ns1:EXTERNAL/REQUEST. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
    I have extracted the data from the initial request (step 1) and the
    logon response (step 4) and using these I have tested the Interface
    Mapping. There is no problem with this and the tests are successful.
    From what I can see, because the Response field in the LOGONResponse
    contains more XML tags, XI must be parsing it and assuming the tags are
    tags in the message, and not just the string, thus it is complaining
    that the XSD types do not match. This extra XML Parsing does not take
    place in the Interface Mapping Test.
    I have put the response into a User Defined Function which just has one
    line "return new String("Hello")" and that fails. However, if this UDF
    does not have the Response as the input, it does not complain.
    Please advise.
    --Reenal

    hi
    You will have to use specific replacements for you xml tags if it is coming as a paramter
    replace '<' with &lt;
    replace '>' with &gt;
    for eg: I want to pass <TakeIt>200</TakeIt> as value to Element <A>
    Mapping won't work if it is passed like
    a) <A><TakeIt>200</TakeIt></A> - Wrong
    Instead the replace the angle brackets
    b) <A>&lt;TakeIt&gt;200&lt;/TakeIt&gt;</A> - Correct
    While testing the mapping in IR (a) will work bcoz the test tool will convert it to (b) format. Check the xml source in test tool.
    So ensure the web response is like (b)
    rgds,
    Arun

Maybe you are looking for

  • One View in multiple Windows

    Hi, This is rather a note than a question and written purely in the hope of Google finding it if I (or someone else) ever need it again: Situation: (V = view; W = window) is displaying a table has a view container with embedded in it opens as a popup

  • Problem in reading the JDK1.4Logger configuration file from java prog

    I have written a java program and want to log the messages in a log file , I'm using commons logging with JDK1.4logger as logging subsystem . I am facing the problem in reading the JDK1.4Logger configuration file which is commons-logging .properties

  • Pictures on iphone not showing up on mac pro

    Just purchased a new iphone.  when I take a picture using the phone and then go to my mac book pro.  it's not showing up on my mac book pro in my photos.  thought the automatically pushed to lap tops and ipads??  I have plugged in the phone after tak

  • Problem in select statment writing

    Hi, I have two tables. P_PLAN_ITEM_DTL --> A table P_SCHDLE_ITEM_UPLOAD --> B table A and B tables contain same structure. A table contain Lot of records. B contain data or may not contanain data. If B contain records then data should filter based on

  • Troubles importing a change request

    Hi experts, Does anybody know how to import a local change Request into another system, in this case my QAS? I was applying the following OSS notes: 1082441 Mexico Legal change Format-A29 SAPKH50020 12/02/2008 1111107 RFIDMXFORMAT29: Country name not