Mapping problem on different levels. (IDOC) to SQL

I am having a mapping issue with a multi segment IDOC. It seems that it should be pretty straight forward but I am struggling. I have looked at some pretty good documentation but it still doesn't seem to help. The IDOC segments deal with text lines in SAP. The text identifier is at a higher level and the text lines are a level below the text identifier. I am writing these records to a SQL database table and the table will just contain the text identifier and then the text line. Both of these are at the same level. I need to combine the text identifier from the higher level to to each text line in the database table.
Here is my source file. It contains two different types of text identifiers (TDID)
<E1TXTH8 SEGMENT="1">
<TDID>0012</TDID>
<TDSPRAS>E</TDSPRAS>
<E1TXTP8 SEGMENT="1">
<TDLINE>This is line 1 of TDID 0012</TDLINE>
</E1TXTP8>
<E1TXTP8 SEGMENT="1">
<TDLINE>This is line 2 of TDID 0012</TDLINE>
</E1TXTP8>
<E1TXTP8 SEGMENT="1">
<TDLINE>This is line 3 of TDID 0012</TDLINE>
</E1TXTP8>
</E1TXTH8>
<E1TXTH8 SEGMENT="1">
<TDID>Z110</TDID>
<TDSPRAS>E</TDSPRAS>
<E1TXTP8 SEGMENT="1">
<TDLINE>This is line 1 of TDID Z110</TDLINE>
</E1TXTP8>
<E1TXTP8 SEGMENT="1">
<TDLINE>This is line 2 of TDID Z110.</TDLINE>
</E1TXTP8>
</E1TXTH8>
I wand this to map so that I see the following results:
<InsertStatement_ShippingText>
<MDB_tblshippingtext action="INSERT">
<access>
<TDID>0012</TDID>
<TDLINE>This is line 1 of TDID 0012</TDLINE>
</access>
<access>
<TDID>0012</TDID>
<TDLINE>This is line 2 of TDID 0012</TDLINE>
</access>
<access>
<TDID>0012</TDID> 
<TDLINE>This is line 3 of TDID 0012</TDLINE>
</access>
<access>
<TDID>Z110</TDID> 
<TDLINE>This is line 1 of TDID Z110</TDLINE>
</access>
<access>
<TDID>Z110</TDID> 
<TDLINE>This is line 2 of TDID Z110</TDLINE>
</access>
</MDB_tblshippingtext>
</InsertStatement_ShippingText>
So far I have been unsuccessful. I am mapping the access element to the lower level segment E1TXTP8. This gives me all of the text lines but the TDID is not filled in properly.
If I map the access element to the highler level E1TXTH8 then I do not get all of my text lines from the lower level. I have looked at the document "Replication of Nodes using the graphical tool mapper" but I still don't seem to understand my problem.
Any help is appreciated.
Thanks,
Jim

Hi Jim,
there are a couple of things to look at:
1. If you always have at least one E1TXTP8 segment under each E1TXTH8 segment, you can use the function useOneAsMany. Jin Chin gave you all the pointers to look at (remember to check the context for the mapping of your element "access")
2. If you test with samples that have a E1TXTH8 segment without a segment E1TXTP8 underneath, the function useOneAsMany will give you the error you encounter. In that case you need to use one of the different mappings described in the <a href="/people/claus.wallacher/blog/2006/04/17/replication-of-nodes-using-the-graphical-mapping-tool">weblog</a> you mentioned.
3. If it still doesn't work, can you give us the sample XML that causes the error?
Regards,
Claus

Similar Messages

  • Mapping problem on different levels. (IDOC) to XML

    I am having a mapping issue with a multi segment IDOC. It seems that it should be pretty straight forward but I am struggling. I have looked at some pretty good documentation but it still doesn't seem to help. The IDOC segments deal with text lines in SAP. The text identifier is at a higher level and the text lines are a level below the text identifier. I am writing these records to XML . Both of these are at the same level. I need to combine the text identifier from the higher level to to each text line in the XML.
    Here is my source file. It contains two different types of text identifiers (TDID)
    <E1TXTH8 SEGMENT="1">
    <TDID>0012</TDID>
    <TDSPRAS>E</TDSPRAS>
    <E1TXTP8 SEGMENT="1">
    <TDLINE>This is line 1 of TDID 0012</TDLINE>
    </E1TXTP8>
    <E1TXTP8 SEGMENT="1">
    <TDLINE>This is line 2 of TDID 0012</TDLINE>
    </E1TXTP8>
    <E1TXTP8 SEGMENT="1">
    <TDLINE>This is line 3 of TDID 0012</TDLINE>
    </E1TXTP8>
    </E1TXTH8>
    <E1TXTH8 SEGMENT="1">
    <TDID>Z110</TDID>
    <TDSPRAS>E</TDSPRAS>
    <E1TXTP8 SEGMENT="1">
    <TDLINE>This is line 1 of TDID Z110</TDLINE>
    </E1TXTP8>
    <E1TXTP8 SEGMENT="1">
    <TDLINE>This is line 2 of TDID Z110.</TDLINE>
    </E1TXTP8>
    </E1TXTH8>
    I wand this to map so that I see the following results:
    <TDID>0012</TDID>
    <TDLINE>This is line 1 of TDID 0012</TDLINE>
    </access>
    <access>
    <TDID>0012</TDID>
    <TDLINE>This is line 2 of TDID 0012</TDLINE>
    </access>
    <access>
    <TDID>0012</TDID>
    <TDLINE>This is line 3 of TDID 0012</TDLINE>
    </access>
    <access>
    <TDID>Z110</TDID>
    <TDLINE>This is line 1 of TDID Z110</TDLINE>
    </access>
    <access>
    <TDID>Z110</TDID>
    <TDLINE>This is line 2 of TDID Z110</TDLINE>
    </access>
    </MDB_tblshippingtext>
    </InsertStatement_ShippingText>
    So far I have been unsuccessful. I am mapping the access element to the lower level segment E1TXTP8. This gives me all of the text lines but the TDID is not filled in properly.
    If I map the access element to the highler level E1TXTH8 then I do not get all of my text lines from the lower level. I have looked at the document "Replication of Nodes using the graphical tool mapper" but I still don't seem to understand my problem.
    Any help is appreciated.
    Thanks,

    Hi Neela,
    I have uploaded Mapping pictures(Access node Mapping,TDID field Mapping,TDLINE Field Mapping).
    http://www.flickr.com/photos/14144840@N02
    In Access node Mapping You can use removeContexts node function as shown in Pic or without using removeContexts function Change Context to parent of E1TXTH8 node (How to Change Context: Right click on TDLINE in Data flow editor Context->select parent of E1TXTH8 node)
    In TDID field Mapping  useOneAsMany node function and change contexts of 2nd and 3rd inputs of this function to E1TXTH8 as shown in Pic.
    Please let me know if you have any issues.
    Thanks,
    Jag

  • Problems with different received message from sql function

    Hello all!
    I have a little problem with my BPEL process. I call a sql function that returns a string. In this string I have a xml. The returned message can be something like:
    <error><id>id_error</id><message>descr_error</message></error>
    or
    <comm>
    <header>
    children tags
    </header>
    <body>
    children tags
    </body>
    </comm>
    As you see, I can receive two types of messages. Of course, the process transforms string -> xml.
    Depending on the type, the process must choose between two flows.
    My questions are: what should be the solution(the steps) to determine what type of message the function returns? In my project, where should I define the same message types in order to assignate them to a variable? In a xsd?
    Thanks in advance!!

    seems like you could solve this with a <pick>. Take a look at the section "One Request, One of Two Possible Responses" in chapter 13 of the bpel developer guide.

  • IDoc to EDI mapping problem (Invoic01 to 810 v4010)

    Hi,
    I have a problem with my invoice mapping.
    I need to exclude children parts from the outbound EDI invoice.
    In my mapping I was able to control the number of lines that should go out from the top line item node level using:
    G_SIT1 ->  If E1EDP02-QUALF = 002 then E1EDP02-ZEILE->Remove Context->SplitByValue->CollapseContext->G_STI1
    I have the right amount of lines but the fields under G_STI1 are wrong since I'm missing the last ones. 
    Then I tried different combinations + playing with the contexts and played again with the top node and my conclusion is that it might be easier to exclude them in IDoc in SAP using an UserExit?!?
    Anybody was able to get around this problem without changing the IDoc in R/3?

    Can I filter on a partner type KU? I need to customize an outboud invoice to not send some segments.
    Or is it only for type LS?
    Rgds,
    Yves

  • Mapping the Fact table to different levels of a dimension

    Hi,
    I have a fact table which stores the data for 4 levels of the dimensions. The aggregation method was taken care by PL/SQL and the fact table will have the data for all the 4 levels. When im trying to map all the levels to a column in the fact table using the OEM, it is generating the F KEY constraints referncing the columns mapped for the various levels of the dimension.
    The problem is that im using a denormalised table for maintaing the values of the dimension. So the columns mapped for the levels(Except for the lowest) can't have the unique key defined on it. The cube is not getting created because of the error in creating the F KEY.
    Can u please suggest how to map this fact table.
    Thnks,
    Manohar Vanama

    I am not exactly clear on your schema but I believe you are trying to map tables which are not strict star or snowflake. This means that you cannot use CWM1 (and OEM), unless you change the structure of the tables. You might be able to map the tables with CWM2. The document below will assist you:
    Oracle9i OLAP User's Guide
    Chapter 4. Designing Your Database for OLAP
    Chapter 5. Creating OLAP Catalog Metadata

  • Context Mapping Problem from IDoc to EDI

    Hi,
    I'm trying to map an IDoc to an EDI and I get this problem.
    In my IDoc, I have segment E1ADRM1 (1:N)
    My mapping condition is if E1ADRM-PARTNER_Q = OSP then copy E1ADRM-REGION into x (EDI field)
    So here is my problem:
    In my IDoc test, the segment E1ADRM1 is repeated 6 times and the field REGION is not populated in all iterations so the wrong
    REGION is being copied to my EDI field.
    If I do a display queue on E1ADRM-PARTNER_Q, the value OSP is at the 5th position
    AG
    SP
    VE
    WE
    OSP  ***
    OSO
    If I do a display queue on E1ADRM-REGION, since only 5 segment E1ADRM have the field REGION populated, I get
    KS
    VA
    KS
    ON
    VA
    **(E1ADRM-PARTNER_Q = SP do not have the RIGION populated so not showing in the IDoc)
    So now, since E1ADRM-PARTNER_Q = OSP is at the 5th position, it is copying the 5th E1ADRM-REGION from the list but it should be the 4th.
    How can I do that?
    Rgds,
    Yves

    Hi,
    For the mapping to work as you are expecting the queue should look like this(<b>CC</b> denotes context change)..
    KS
    <b>CC</b>
    <b>CC</b>
    VA
    <b>CC</b>
    KS
    <b>CC</b>
    ON
    <b>CC</b>
    VA
    If you are not having the context changes, check at what level is field REGION at, right click on REGION in graphical mapping and choose menu item context, the 1st entry should have the tick mark(same should be for the PARTNER_Q field also).
    Thanks,
    Renjith.

  • JDBC to IDOC scenario - Mapping problem with E1FIBSEG

    Hi friends,
    I have problem when generate multiple Idocs (FIDCC1) an multiple positions based on an External Definition for a SQL Server table. I have selected all fields from this table from a SELECT into the JDBC configuration.
    My mapping is like this:
    DWCAJA.ResultSet  1..1
         IDOC.
    Thats ok and generate n IDOCs by every change of PK.
    The problem is when i want to map positions because i dont have any field in source message to identify the number of positions to map with E1FISEG.
    If I have two differents Pks and n rows, the result of testing is as folow:
    FIDCC1
      IDOC
         E1FIKPF
             E1FISEG
             E1FISEG
      IDOC
            E1FIKPF
    I cant obtain n BSEG segments according PK. I've mapped and all fields of row segment but those are created in the first IDOC node only,
    Any suggestions?
    Regards,
    Pablo.-

    Important: Primary key : DWSucCod + DWCajSec
    Payload:
    - <row>
      <DWSucCod>11</DWSucCod>
      <DWCajSec>1</DWCajSec>
      <DWCtaConCo>1100001</DWCtaConCo>
      <DWRecImp>100</DWRecImp>
      </row>
    - <row>
      <DWSucCod>11</DWSucCod>
      <DWCajSec>1</DWCajSec>
      <DWCtaConCo>1100002</DWCtaConCo>
      <DWRecImp>200</DWRecImp>
      </row>
    Result:
    IDOC
       E1FIKPF
         E1FISEG
             hkont :1100001
             dmbtr : 100
         E1FISEG
              hkont :1100002
             dmbtr : 200
    Payload:
    - <row>
      <DWSucCod>11</DWSucCod>
      <DWCajSec>1</DWCajSec>
      <DWCtaConCo>1100002</DWCtaConCo>
      <DWRecImp>200</DWRecImp>
      </row>
    - <row>
      <DWSucCod>12</DWSucCod>
      <DWCajSec>1</DWCajSec>
      <DWCtaConCo>1100003</DWCtaConCo>
      <DWRecImp>300</DWRecImp>
      </row>
    Result:
    IDOC
       E1FIKPF
         E1FISEG
             hkont :1100002
             dmbtr : 200
    IDOC
       E1FIKPF
         E1FISEG
             hkont :1100001
             dmbtr : 300
    Payload:
    - <row>
      <DWSucCod>11</DWSucCod>
      <DWCajSec>1</DWCajSec>
      <DWCtaConCo>1100001</DWCtaConCo>
      <DWRecImp>100</DWRecImp>
      </row>
    - <row>
      <DWSucCod>11</DWSucCod>
      <DWCajSec>1</DWCajSec>
      <DWCtaConCo>1100002</DWCtaConCo>
      <DWRecImp>200</DWRecImp>
      </row>
    - <row>
      <DWSucCod>12</DWSucCod>
      <DWCajSec>1</DWCajSec>
      <DWCtaConCo>1100003</DWCtaConCo>
      <DWRecImp>300</DWRecImp>
      </row>
    Result:
    IDOC
       E1FIKPF
         E1FISEG
             hkont :1100001
             dmbtr : 100
         E1FISEG
             hkont :1100002
             dmbtr : 200
    IDOC
       E1FIKPF
         E1FISEG
             hkont :1100003
             dmbtr : 300

  • Mapping to 3rd hierarchical level in IDoc

    Hi, well i have a little problem.
    Scenario: File to IDoc
    i get this kind of file:
    <i>P|67220400|9991233643|
    W|71123456|1|4|BPL
    K|70100005|15|X|9999
    K|70100200|4||1200
    K|70100210|3||300
    W|71123456|1|4|ABM
    K|70100005|15|X|9999
    K|70100200|4||1200
    K|70100210|3||300</i>
    ...where P, W, K are keyfields.
    The IDoc has three hierarchical levels, whereas P is first, W second and K third.
    All these values should be mapped in one IDoc. But everytime a new W occurs there is a new recordset generated, so a new IDoc.
    Nevertheless i map as follows:
    <i>/ZIDOC/IDOC =/MT_EPLAN/ EPLANRecordSet=
    /ZIDOC/IDOC/@BEGIN =const([value=])
    /ZIDOC/IDOC/EDI_DC40/@SEGMENT =const([value=])
    /ZIDOC/IDOC/EDI_DC40/TABNAM =const([value=])
    /ZIDOC/IDOC/EDI_DC40/DIRECT =const([value=])
    /ZIDOC/IDOC/EDI_DC40/IDOCTYP =const([value=])
    /ZIDOC/IDOC/EDI_DC40/MESTYP =const([value=])
    /ZIDOC/IDOC/EDI_DC40/SNDPOR =const([value=])
    /ZIDOC/IDOC/EDI_DC40/SNDPRT =const([value=LS])
    /ZIDOC/IDOC/EDI_DC40/SNDPRN =const([value=COS])
    /ZIDOC/IDOC/EDI_DC40/RCVPOR =const([value=])
    /ZIDOC/IDOC/EDI_DC40/RCVPRN =const([value=])
    /ZIDOC/IDOC/ ZBC15_EPLAN= /MT_EPLAN/EPLANRecordSet/EPLANHead =
    /ZIDOC/IDOC/ZBC15_EPLAN/ @SEGMENT=const([value=])
    /ZIDOC/IDOC/ZBC15_EPLAN/EPLAN =/MT_EPLAN/EPLANRecordSet/EPLANHead/ Data1=
    /ZIDOC/IDOC/ZBC15_EPLAN/ WERKSTUECK= /MT_EPLAN/EPLANRecordSet/EPLANHead/Data2 =
    /ZIDOC/IDOC/ZBC15_EPLAN/ ZBC15_WERK= /MT_EPLAN/EPLANRecordSet/EPLANWerkz =
    /ZIDOC/IDOC/ZBC15_EPLAN/ZBC15_WERK/ @SEGMENT=const([value=])
    /ZIDOC/IDOC/ZBC15_EPLAN/ZBC15_WERK/ WERKSTUECK= /MT_EPLAN/EPLANRecordSet/EPLANWerkz/Data1 =
    /ZIDOC/IDOC/ZBC15_EPLAN/ZBC15_WERK/ POSNR= /MT_EPLAN/EPLANRecordSet/EPLANWerkz/Data2 =
    /ZIDOC/IDOC/ZBC15_EPLAN/ZBC15_WERK/ ANZAHL= /MT_EPLAN/EPLANRecordSet/EPLANWerkz/Data3 =
    /ZIDOC/IDOC/ZBC15_EPLAN/ZBC15_WERK/ KTEXT= /MT_EPLAN/EPLANRecordSet/EPLANWerkz/Data4 =
    /ZIDOC/IDOC/ZBC15_EPLAN/ZBC15_WERK/ ZBC15_KOMP= /MT_EPLAN/EPLANRecordSet/EPLANKomp =
    /ZIDOC/IDOC/ZBC15_EPLAN/ZBC15_WERK/ZBC15_KOMP/ @SEGMENT=const([value=])
    /ZIDOC/IDOC/ZBC15_EPLAN/ZBC15_WERK/ZBC15_KOMP/ KOMP= /MT_EPLAN/EPLANRecordSet/EPLANKomp/Data1 =
    /ZIDOC/IDOC/ZBC15_EPLAN/ZBC15_WERK/ZBC15_KOMP/ ANZAHL= /MT_EPLAN/EPLANRecordSet/EPLANKomp/Data2 =
    /ZIDOC/IDOC/ZBC15_EPLAN/ZBC15_WERK/ZBC15_KOMP/ ART= /MT_EPLAN/EPLANRecordSet/EPLANKomp/Data3 =
    /ZIDOC/IDOC/ZBC15_EPLAN/ZBC15_WERK/ZBC15_KOMP/ MENGE= /MT_EPLAN/EPLANRecordSet/EPLANKomp/Data4 =
    </i>
    Can someone help me?!
    br

    Hi Carsten,
          As per my understanding of u r requirement check the maping for IDOC field in the strucutre.you have mapped with MT_EPLAN/ EPLANRecordSet.Once check the occurence of this.
    Cheers
    Veera
    >>>Reward Points,If it is needful.

  • Can I map different levels of a hierarchy to different sources

    Hi,
    I want for AWM not to aggregate the upper levels of a dimension by itself. Instead, i want to feed the data for upper levels also through different sources.
    Its becauese, the measure values of my dimension can not be aggregated from lower level. The value has to be calculated separetely.
    I know that the AWM will not aggregate when i specify the dimension agg rule as 'NON ADDATIVE' or something like that. I did it and i was done too. There were the data only for base level for that particular dimension. The other levels were empty.
    Now i want to feed the data for other empty levels from different source.
    Does anyone knows if it is possible in AWM 10.2.0.1 or can i do it from any other way?
    If one knows how to do it, i would be very much grateful to know it clearly.
    with regards,
    subash

    The following method assumes that you are assuming responsibility for managing all of the aggregate level data on your own:
    1. Define the cube as (a) uncompressed (the aggregate space of a compressed cube is always managed by the multidimensional engine), (b) with aggregation methods of SUM for all dimensions and (c) with only the detail levels selected on the 'Summarize To' tab of the cube definition. This will set up the cube so that it will not aggregate data when it is loaded.
    You will have a formula used to represent the measure and it will look something like this:
    DEFINE SALES_CUBE_SALES FORMULA DECIMAL <TIME CHANNEL CUSTOMER PRODUCT>
    EQ aggregate(this_aw!SALES_CUBE_SALES_STORED using this_aw!OBJ1819687276)
    You can see from the AGGREGATE command in the formula that it is set up to aggregate data at runtime if necessary. The formula reads from a variable that will look something like this:
    DEFINE SALES_CUBE_SALES_STORED VARIABLE DECIMAL WITH AGGCOUNT <SALES_CUBE_PARTITION_TEMPLATE <TIME CHANNEL CUSTOMER PRODUCT>>
    2. Load the data. You can load the base data through AWM if you wish or you can load it into the variable of the measure using OLAP DML code. You cannot map tables to summary levels using AWM, so you will need to use OLAP DML code to do this. An example program follows.
    DEFINE LOAD_SALES PROGRAM INTEGER
    PROGRAM
    vrb _errortext text
    trap on HADERROR noprint
    sql declare c1 cursor for -
    select -
    to_char(MONTH_ID), -
    to_char(ITEM_ID), -
    to_char(SHIP_TO_ID), -
    to_char(CHANNEL_ID), -
    SALES -
    from GLOBAL.SALES_FACT -
    where -
    (MONTH_ID IS NOT NULL) and -
    (ITEM_ID IS NOT NULL) and -
    (SHIP_TO_ID IS NOT NULL) and -
    (CHANNEL_ID IS NOT NULL) -
    order by -
    CHANNEL_ID, -
    SHIP_TO_ID, -
    ITEM_ID, -
    MONTH_ID
    sql open c1
    if sqlcode ne 0
    then do
    _errortext =  SQLERRM
    goto HADERROR
    doend
    sql import c1 into -
    :MATCHSKIPERR TIME_MONTH -
    :MATCHSKIPERR PRODUCT -
    :MATCHSKIPERR CUSTOMER -
    :MATCHSKIPERR CHANNEL -
    :UNITS_CUBE_PRT_TOPVAR(UNITS_CUBE_PRT_MEASDIM 'SALES')
    if sqlcode lt 0
    then do
    _errortext =  SQLERRM
    goto HADERROR
    doend
    sql close c1
    sql cleanup
    return 0
    HADERROR:
    trap on NO_ERROR noprint
    sql close c1
    NO_ERROR:
    trap off
    sql cleanup
    END
    3. Change the formula of the measure so that it does not aggregate using OLAP DML commands. E.g.,
    consider sales_cube_sales
    eq SALES_CUBE_SALES_STORED
    The formula will then simply get data from the variable rather than call the aggregate system.
    Since you are writing to the physical implementation of the AW you will need to check this code each time you upgrade the database because the physical implementation changes from time to time. (Usually major releases such as 10.1 and 10.2, not usually maintenance releases, but you never know.)

  • Mapping Problem ORDERS Idoc to Edifact

    Hi,
    I have a mapping problem with the IDOC ORDERS:
    I get the IDOC with several E1EDP01. Each E1EDP01 has several E1EDPT1, where i want only the first one (which I get over the TDID value). Each E1EDPT1 has min. 1 E1EDPT2.
    Now I have to map each field TDLINE from first two E1EDPT2 of the first E1EDPT1 to the Edifact fields /LIST/S_UNB/S_UNH/G_SSG25/S_LIN/S_IMD[1]/C_C273/D_7008 (from the first E1EDPT2) and, if a second E1EDPT2 exists in /LIST/S_UNB/S_UNH/G_SSG25/S_LIN/S_IMD[1]/C_C273/D_7008_2.
    I use following UDF:
    //a = TDLINE
    //b = Number of entry in the List
    int pos =Integer.parseInt(b[0]);
    if ( pos < a.length )
    result.addValue(a[pos]);
    else
    result.addValue(ResultList.SUPPRESS);
    Unfortunatly, I think becaus of the context problems (not every E1EDPT1 has two E1EDPT2), it's not working. Could somebody help me with this problem?
    Thanks in advance
    Dominic

    Dear Dominic ,
    I had same problem when I was trying to do the same thing for FTX segment.
    Your UDF is fine but you don't need else condition.
    //a = TDLINE
    //b = Number of entry in the List
    int pos =Integer.parseInt(b[0]);
    if ( pos < a.length )
    result.addValue(a[pos]);
    for C_C273 assigned contant value and
    D_7008 assigned TDLINE but change the context to E1EDPT1
    and for D_7008_2
    TDLINE(context to E1EDPT1 )
                                                      ====>UDF====>D_7008_2
    Contant(=1)
    It should work becasue my map is working fine. If not let me know error message.
    Thanks
    Shubhankar

  • File to Idoc Mapping Problem

    Hi all,
    i'm getting an error from SXMB_MONI in a scenario File to Idoc.
    I have done the mapping from source file and Idoc CREMAS03, when i try to test from Integration Repository it's all ok, but when the scenario is executed i find this error in Idoc Adapter :
    <SAP:P1>MSGGUID EF7E2140A08811DDBE1202004C4F4F50: Tag #TEXT found instead of tag IDOC BEGIN=</SAP:P1>
    The field BEGIN in idoc structure is filled with constant value 1, than i dont understand the error.
    This is the xml source file :
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:Vendor xmlns:ns0="urn:tbit40:workshop:group01:legacy">
    - <Address>
      <Country>IT</Country>
      <Zip>001</Zip>
      <City>ROMA</City>
      <Street>SATTA</Street>
      </Address>
      <Currency>USD</Currency>
      <SearchTerm>TEST</SearchTerm>
      <LastName>GUIDA</LastName>
      <VendorNumber>44332</VendorNumber>
      </ns0:Vendor>
    Any help is really appreciated.
    Thanks.

    Hi all and thanks for your answer.
    My problem is that for what i can see all Idoc attribute (like the attribute BEGIN) are mapped with constant value.
    In taget source i can see :  BEGIN = Constant([value=1])
    What i dont understand is why when i execute the scenario it ends with this message :
    <SAP:P1>MSGGUID EF7E2140A08811DDBE1202004C4F4F50: Tag #TEXT found instead of tag IDOC BEGIN=</SAP:P1>
    It seem to me that the tag BEGIN is not filled with value, i also tried to copy the source xml file directly from SXMB_MONI  (from payload) and test it in Integration Repository mapping section, but here is all ok and the test end succesfully.

  • Sorry last question got knocked back my ipad and iPhone on two different levels and I am not able to play through Facebook so not able to progress or unlock next level through Apple store. Don't know how to resolve problem

    Sorry last question got knocked back my ipad and iPhone on two different levels and I am not able to play through Facebook so not able to progress or unlock next level through Apple store. Don't know how to resolve problem

    Thank you again for all of your help!! I really appreciate it!
    I think I am following -- I was able to upload to my iPhoto and all photos and videos are there that is a plus! I tried to create an Event in my iPhoto and put all of my photos in that event but for some reason, now my iTunes it not recognizing that Event in my iPhoto. It is not allowing me to import just that event at the moment but I may be doing something wrong. At least all of my pics and vids are in iPhoto so that is a plus and I know they are at least saved somewhere. Just for some reason, my iTunes it not locating the event that I created with only those photos.
    Thank you for letting me know about my contacts! How do I know if I have the contacts app?
    Also, I had no clue that my iCloud could be backed up via cellular data! However, is this a new feature with the most updated iOS?? Unforutnatly I am like 2 iOS updates behind because I don't have enough storage on my phone. I still get the notification that my phone needs to be plugged in and connected to wifi in order to back up to the cloud :-(
    How can I sync using USB? Right now when i click on the info tab for my iPhone in my iTunes this is the answer that I get -- I am a little unclear as to what it means.
    Sync Contacts:
    Your contacts are being synced with you iPhone over the air from iCloud. Over-the-air sync settings can be changed on you iPhone
    Sync Calendars:
    Your calendars are being synced with you iPhone over the air from iCloud. Over-the-air sync settings can be changed on you iPhone

  • Problems with ViaVoice under Leopard, especially key mapping problems

    ViaVoice's behavior has changed considerably under Leopard. First I will discuss the key mapping problem, since I'm eagerly looking for an answer to this problem. At the end of this post, I will voice some of the other problems I've experienced for those who may be interested. The key mapping problem may be specific to the fact that I use a foreign keyboard with a US version of ViaVoice.
    INTRO:
    I have used ViaVoice on my Mac for years, more or less without problems (ViaVoice's bugginess is notorious).
    Those who know ViaVoice will know that one has two general options for dictation. One can dictate into ViaVoice's so-called SpeakPad, which allows special formatting, editing and dictation error correction within the dictated text, or one can dictate into "external" software such as Microsoft Word, in which case ViaVoice just sends a string of characters to that software. SpeakPad appears to make strong use of the operating system's built-in functionality for character formatting, document formatting, etc.
    *MY PROBLEM*
    I have a German keyboard on my PowerBook, yet dictate in US English. When I dictated into SpeakPad under Tiger, all characters appeared correctly. However, when I dictated into Microsoft Word using Tiger, I had to switch the keyboard mapping from German to US to get all characters (that means including the characters that are located at different positions on a German keyboard than they are on a US keyboard such as y, z, apostrophes and parentheses) to appear correctly.
    Under Leopard, things have changed. Now it doesn't matter whether I dictate into SpeakPad or Word; the results are the same and many characters do not appear correctly.
    If set to a German keyboard, y and z appear as expected. To name a few irregularities:
    "(" appears as ")"
    ")" appears as "="
    apostrophes appear as "#" and
    ";" appears as ","
    If set to a US keyboard, y and z are interchanged. "(" and ")" appear as expected. Apostrophes appear as "\" and ";" appears as ","
    By comparison, if typed (as opposed to dictated, as in the examples above) "correctly" (i.e. based on the letters printed on the keyboard) on a German keyboard set to imitate a US keyboard:
    y and z are interchanged
    apostrophes appear as "|"
    "(" appears as "*"
    ")" appears as "(" and
    ";" appears as the symbol for "less than"
    Since I don't have a US keyboard, I can't say how it would behave if set to imitate a German keyboard, i.e. if there's a correlation to the results I get when I dictate.
    Since I was previously able to dictate correctly into SpeakPad by setting the keyboard to "German" and into Word by setting the keyboard to "US," I presume that this is a problem in Leopard, not ViaVoice.
    *OTHER PROBLEMS WITH VIAVOICE UNDER LEOPARD*
    In addition to the aforementioned key mapping problems (that may be specific to those of us with foreign keyboards), ViaVoice appears to have lost considerable functionality in Leopard. I cannot access SpeakPad's Preferences and the correction window. Moreover, the traffic-light like window buttons have disappeared from the VoiceCenter (although they work if you click where they should be). SetupAssistent appears to function.
    I've written to Nuance about these problems, but have little hope that they will invest the time in producing a patch since they haven't released any updates since 2003.

    Thrums1,
    I've never had to "register" ViaVoice after updating the system. I thus suspect you haven't fully followed my above, three-step advice (particularly step 3).
    1) Reinstall ViaVoice from CD.
    2) Update to the latest version (using the patch downloadable from Nuance's website).
    3) Replace the “temp” and “users” folders (in the "ViaVoice" folder at the upper level of your home directory) by a previous copy thereof. When I say previous copy, I mean a copy from when ViaVoice was still working properly, e.g. a copy from when it was running under Tiger.
    As I said, I've gotten ViaVoice to survive several system updates by following the above steps. To my knowledge, the last step is critical since it saves you from having to reconfigure ViaVoice under the new operating system (in this case Leopard). I suspect that ViaVoice is crashing on your system because it's trying to start some module of the SetUpAssistant that is incompatible with Leopard (as many are). If you instead use old copies of the "temp" and "users" folders (from the previous system), then ViaVoice doesn't have to go through the initial "registration" process; ViaVoice doesn't need the SetUpAssistant; and all is (more or less) fine.
    Good luck!
    BTW, to my knowledge, Dictate only runs on Intel Macs. It thus won't run on a G4 iBook, just as it won't run on my PowerBook G4.

  • Getting problem in File to IDOC scenario

    Hi,
    In SXMB_MONI, I am getting an error "Message has error status on outbound side". file is being picked by XI and it is not appearing in the R/3 system as IDOC. I am getting black & white chequered flag at left side and red flag at right side in the SXMB_MONI. Plz help me in this regard.
    Thanks
    Raghavesh.

    Hi Divija,
    Thanks for ur reply.Mapping is done correctly. I have tested it and executed successfully.
    The error message is "Message has error status on outbound side". I checked the Message ID about error, but i couldn't found any error in that.Plz check the following payload below.----
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Response
      -->
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SOAP:Header>
    - <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
      <SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
      <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
      <SAP:MessageId>087E57E0-25F3-11DB-AB31-001143D6B120</SAP:MessageId>
      <SAP:TimeSent>2006-08-07T08:59:28Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Service>FILE_TO_IDOC_BS</SAP:Service>
      <SAP:Interface namespace="http://filetoidoc/xi">ZEP_TO_IDES_MI</SAP:Interface>
      </SAP:Sender>
    - <SAP:Receiver>
      <SAP:Party agency="" scheme="" />
      <SAP:Service>SAPIDES</SAP:Service>
      <SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">DEBMAS.DEBMAS03</SAP:Interface>
      </SAP:Receiver>
      <SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">DEBMAS.DEBMAS03</SAP:Interface>
      </SAP:Main>
    - <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
      </SAP:ReliableMessaging>
    - <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    - <SAP:Hop timeStamp="2006-08-07T08:59:28Z" wasRead="false">
      <SAP:Engine type="AE">af.xi2.igatesap09</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
      <SAP:MessageId>087E57E0-25F3-11DB-AB31-001143D6B120</SAP:MessageId>
      <SAP:Info />
      </SAP:Hop>
    - <SAP:Hop timeStamp="2006-08-07T08:59:28Z" wasRead="false">
      <SAP:Engine type="IS">is.00.igatesap09</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>087E57E0-25F3-11DB-AB31-001143D6B120</SAP:MessageId>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
    - <SAP:Hop timeStamp="2006-08-07T08:59:29Z" wasRead="false">
      <SAP:Engine type="IS">is.00.igatesap09</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">IDoc</SAP:Adapter>
      <SAP:MessageId>087E57E0-25F3-11DB-AB31-001143D6B120</SAP:MessageId>
      <SAP:Info>0000000000045522;</SAP:Info>
      </SAP:Hop>
      </SAP:HopList>
    - <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <SAP:TABNAM>EDI_DC40</SAP:TABNAM>
      <SAP:MANDT>100</SAP:MANDT>
      <SAP:DOCREL>640</SAP:DOCREL>
      <SAP:DOCNUM>0000000000045522</SAP:DOCNUM>
      <SAP:DIRECT>2</SAP:DIRECT>
      <SAP:IDOCTYP>DEBMAS03</SAP:IDOCTYP>
      <SAP:CIMTYP />
      <SAP:MESTYP>DEBMAS</SAP:MESTYP>
      <SAP:MESCOD />
      <SAP:MESFCT />
      <SAP:SNDPOR>SAPXI2</SAP:SNDPOR>
      <SAP:SNDPRN>FILETOIDOC</SAP:SNDPRN>
      <SAP:SNDPRT>LS</SAP:SNDPRT>
      <SAP:SNDPFC />
      <SAP:RCVPOR>SAPDES</SAP:RCVPOR>
      <SAP:RCVPRN>IGATE_800</SAP:RCVPRN>
      <SAP:RCVPRT>LS</SAP:RCVPRT>
      <SAP:RCVPFC />
      <SAP:TEST />
      <SAP:SERIAL />
      <SAP:EXPRSS />
      <SAP:STD />
      <SAP:STDVRS />
      <SAP:STATUS>03</SAP:STATUS>
      <SAP:OUTMOD />
      <SAP:SNDSAD />
      <SAP:SNDLAD />
      <SAP:RCVSAD />
      <SAP:RCVLAD />
      <SAP:STDMES />
      <SAP:REFINT />
      <SAP:REFGRP />
      <SAP:REFMES />
      <SAP:CREDAT>2006-08-07</SAP:CREDAT>
      <SAP:CRETIM>04:59:29</SAP:CRETIM>
      <SAP:ARCKEY>087E57E025F311DBAB31001143D6B120</SAP:ARCKEY>
      </SAP:IDocOutbound>
    - <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Date>20060807</SAP:Date>
      <SAP:Time>045928</SAP:Time>
      <SAP:Host>iGateSAP09</SAP:Host>
      <SAP:SystemId>XI2</SAP:SystemId>
      <SAP:SystemNr>00</SAP:SystemNr>
      <SAP:OS>Windows NT</SAP:OS>
      <SAP:DB>ORACLE</SAP:DB>
      <SAP:Language />
      <SAP:ProcStatus>003</SAP:ProcStatus>
      <SAP:AdapterStatus>001</SAP:AdapterStatus>
      <SAP:User>XIAFUSER</SAP:User>
      <SAP:TraceLevel>3</SAP:TraceLevel>
      <SAP:Logging>1</SAP:Logging>
      <SAP:LogSeqNbr>008</SAP:LogSeqNbr>
      <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
      <SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
      <SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
      <SAP:PipelineElementId />
      <SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
      <SAP:PipelineService />
      <SAP:QIdInternal>XBTO3___0000</SAP:QIdInternal>
      <SAP:CommitActor>X</SAP:CommitActor>
      <SAP:SplitNumber>0</SAP:SplitNumber>
      <SAP:NumberOfRetries>0</SAP:NumberOfRetries>
      <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
      <SAP:TypeOfEngine client="100">CENTRAL</SAP:TypeOfEngine>
      <SAP:PlsrvExceptionCode />
      <SAP:EOReferenceRuntime type="TID">C0A84641121044D700F02DB4</SAP:EOReferenceRuntime>
      <SAP:EOReferenceInbound type="TID" />
      <SAP:EOReferenceOutbound type="TID">C0A84641121044D700F12DB5</SAP:EOReferenceOutbound>
      <SAP:MessageSizePayload>752</SAP:MessageSizePayload>
      <SAP:MessageSizeTotal>3020</SAP:MessageSizeTotal>
      <SAP:PayloadSizeRequest>752</SAP:PayloadSizeRequest>
      <SAP:PayloadSizeRequestMap>1124</SAP:PayloadSizeRequestMap>
      <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
      <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
      <SAP:Reorganization>INI</SAP:Reorganization>
      <SAP:AdapterInbound>XIRA</SAP:AdapterInbound>
      <SAP:AdapterOutbound>IDOC</SAP:AdapterOutbound>
      <SAP:RandomNumber>81</SAP:RandomNumber>
      <SAP:AckStatus>000</SAP:AckStatus>
      <SAP:SkipReceiverDetermination />
      </SAP:RunTime>
    - <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="begin" host="iGateSAP09">20060807085928.765</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="end" host="iGateSAP09">20060807085928.781</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="begin" host="iGateSAP09">20060807085928.781</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="iGateSAP09">20060807085928.781</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="iGateSAP09">20060807085928.781</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="iGateSAP09">20060807085928.859</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="iGateSAP09">20060807085928.875</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="iGateSAP09">20060807085928.875</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="iGateSAP09">20060807085928.89</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="iGateSAP09">20060807085928.89</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="begin" host="iGateSAP09">20060807085928.906</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="end" host="iGateSAP09">20060807085928.906</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="iGateSAP09">20060807085928.906</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="iGateSAP09">20060807085928.984</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="begin" host="iGateSAP09">20060807085929.0</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="end" host="iGateSAP09">20060807085929.015</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="begin" host="iGateSAP09">20060807085929.015</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="end" host="iGateSAP09">20060807085929.031</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
      <SAP:Timestamp type="begin" host="iGateSAP09">20060807085929.046</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
      <SAP:Timestamp type="end" host="iGateSAP09">20060807085929.062</SAP:Timestamp>
      </SAP:RunTimeItem>
      </SAP:PerformanceHeader>
    - <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:TraceLevel>Information</SAP:TraceLevel>
      <SAP:Logging>Off</SAP:Logging>
      </SAP:Diagnostic>
    - <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    - <SAP:OutboundBindingEntry version="30">
      <SAP:OutboundBindingObjectId>7E9DD53BBCC334B78F5D7E5373481745</SAP:OutboundBindingObjectId>
      <SAP:FromPartyName />
      <SAP:FromServiceName>FILE_TO_IDOC_BS</SAP:FromServiceName>
      <SAP:ToPartyName />
      <SAP:ToServiceName>SAPIDES</SAP:ToServiceName>
      <SAP:ToInterfaceName>DEBMAS.DEBMAS03</SAP:ToInterfaceName>
      <SAP:ToInterfaceNamespace>urn:sap-com:document:sap:idoc:messages</SAP:ToInterfaceNamespace>
    - <SAP:OutboundBindingAttributes>
      <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      </SAP:OutboundBindingAttributes>
    - <SAP:HeaderMapping>
      <SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      </SAP:HeaderMapping>
    - <SAP:ChannelEntry version="30">
      <SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">SAPIDES</SAP:ServiceName>
      <SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">ZEP_TO_IDES_RCC</SAP:ChannelName>
      <SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:AdapterName>
      <SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System</SAP:AdapterNamespace>
      <SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">3B787A8035C111D6BBE0EFE50A1145A5</SAP:AdapterSWCV>
      <SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">IS</SAP:AdapterEngineType>
      <SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:MessageProtocol>
      <SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:TransportProtocol>
      <SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ChannelDirection xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection>
      <SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
    - <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:Attribute>
      <SAP:Name>interfaceVersion</SAP:Name>
      <SAP:Value>3</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>passControlSetValues</SAP:Name>
      <SAP:Value>0</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>port</SAP:Name>
      <SAP:Value>SAPDES</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>queueing</SAP:Name>
      <SAP:Value>0</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>rfcDestination</SAP:Name>
      <SAP:Value>IGATE_800</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>sapRelease</SAP:Name>
      <SAP:Value>640</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>segmentVersion</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
      </SAP:AdapterTypeData>
      </SAP:ChannelAttributes>
      </SAP:ChannelEntry>
      </SAP:OutboundBindingEntry>
      </SAP:OutboundBinding>
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="T">Party normalization: sender</Trace>
      <Trace level="1" type="T">Sender scheme external = XIParty</Trace>
      <Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
      <Trace level="1" type="T">Sender party external =</Trace>
      <Trace level="1" type="T">Sender party normalized =</Trace>
      <Trace level="1" type="T">Party normalization: receiver</Trace>
      <Trace level="1" type="T">Receiver scheme external =</Trace>
      <Trace level="1" type="T">Receiver agency external =</Trace>
      <Trace level="1" type="T">Receiver party external =</Trace>
      <Trace level="1" type="T">Receiver party normalized =</Trace>
      <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
      <Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
      <Trace level="2" type="T">Host = 192.168.70.65:8000</Trace>
      <Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
      <Trace level="2" type="T">Remote address = 192.168.70.65</Trace>
      <Trace level="1" type="T">COMMIT is done by XMB !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
      <Trace level="3" type="T">Getting type of XMB...</Trace>
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="2" type="T">XMB kind = CENTRAL</Trace>
      <Trace level="3" type="T">Start pipeline found</Trace>
      <Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
      <Trace level="3" type="T">No triggers found. OK.</Trace>
      </Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="3" type="T">system-ID = XI2</Trace>
      <Trace level="3" type="T">client = 100</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = XIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = 087E57E025F311DBAB31001143D6B120</Trace>
      <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">QOS = EO</Trace>
      <Trace level="3" type="T">Message-GUID = 087E57E025F311DBAB31001143D6B120</Trace>
      <Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
      <Trace level="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">Generate prefixed queue name</Trace>
      <Trace level="1" type="T">Queue name : XBTI0008</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0008</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="3" type="T">Setup qRFC Scheduler</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="3" type="T">Call qRFC .... MsgGuid = 087E57E025F311DBAB31001143D6B120</Trace>
      <Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
      <Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
      <Trace level="3" type="T">OK.</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="3" type="T">Version number = 000</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 001</Trace>
      <Trace level="3" type="T">Message version 000</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
      <Trace level="3" type="T">Trace object available again now. OK.</Trace>
      <Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
      <Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
      <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
      <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
      </Trace>
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
      <Trace level="2" type="T">Increment log sequence to 001</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="3" type="T">system-ID = XI2</Trace>
      <Trace level="3" type="T">client = 100</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = XIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
      <Trace level="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline attributes</Trace>
      <Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">ENABLE = 1</Trace>
      <Trace level="3" type="T">TRACELEVEL = 0</Trace>
      <Trace level="3" type="T">EXEMODE = A</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline elements</Trace>
      <Trace level="3" type="T">ELEMPOS = 0001</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0002</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0003</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0004</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0007</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0008</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0009</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
      <Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      <Trace level="2" type="T">Start without given receiver</Trace>
      <Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
      <Trace level="2" type="T">...valid Receiver w/o Condition: - SAPIDES</Trace>
      <Trace level="2" type="T">Number of Receivers:1</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 001</Trace>
      <Trace level="3" type="T">Message version 001</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
      <Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      <Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) SAPIDES DEBMAS.DEBMAS03</Trace>
      <Trace level="2" type="T">...valid InbIf without Condition: DEBMAS.DEBMAS03</Trace>
      <Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 002</Trace>
      <Trace level="3" type="T">Message version 002</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
    - <!--  ************************************
      -->
      <Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
      <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="2" type="T">got property produced by receiver determination</Trace>
      <Trace level="1" type="T">number of receivers: 1</Trace>
      <Trace level="1" type="T">Single-receiver split case</Trace>
      <Trace level="1" type="T">Post-split internal queue name = XBTO3___0000</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Persisting single message for post-split handling</Trace>
      <Trace level="1" type="T" />
      <Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 012</Trace>
      <Trace level="3" type="T">Message version 003</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
      <Trace level="3" type="T">Trace object available again now. OK.</Trace>
      <Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
      <Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
      <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
      <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
      </Trace>
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">message version successfully read from persist version= 004</Trace>
      <Trace level="2" type="T">Increment log sequence to 005</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="3" type="T">system-ID = XI2</Trace>
      <Trace level="3" type="T">client = 100</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = XIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
      <Trace level="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline attributes</Trace>
      <Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">ENABLE = 1</Trace>
      <Trace level="3" type="T">TRACELEVEL = 0</Trace>
      <Trace level="3" type="T">EXEMODE = A</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline elements</Trace>
      <Trace level="3" type="T">ELEMPOS = 0001</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0002</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0003</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0004</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0007</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0008</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0009</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
      <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
    - <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
      <Trace level="1" type="Timestamp">2006-08-07T08:59:29Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <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="1" type="T">Interface Mapping http://filetoidoc/xi ZEP_TO_IDES_IM</Trace>
      <Trace level="3" type="T">Object ID of Interface Mapping 15340465420C3DA1A9475DA6856A09C7</Trace>
      <Trace level="3" type="T">Version ID of Interface Mapping D9FF93C122D711DBA80DE4DEC0A84641</Trace>
      <Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_ZEP_TO_IDES_MM_</Trace>
      <Trace level="2" type="T">Mode 0</Trace>
      <Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_ZEP_TO_IDES_MM_.</Trace>
      <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._ZEP_TO_IDES_MM_</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 [DEBMAS03]</Trace>
      <Trace level="3" type="T">Start tag [IDOC]</Trace>
      <Trace level="3" type="T">Add attribute: [BEGIN]=[1]</Trace>
      <Trace level="3" type="T">Start tag [EDI_DC40]</Trace>
      <Trace level="3" type="T">Add attribute: [SEGMENT]=[99]</Trace>
      <Trace level="3" type="T">Start tag [TABNAM]</Trace>
      <Trace level="3" type="T">Put value [EDI_DC40]</Trace>
      <Trace level="3" type="T">Close tag [TABNAM]</Trace>
      <Trace level="3" type="T">Start tag [DOCREL]</Trace>
      <Trace level="3" type="T">Put value [640]</Trace>
      <Trace level="3" type="T">Close tag [DOCREL]</Trace>
      <Trace level="3" type="T">Start tag [DIRECT]</Trace>
      <Trace level="3" type="T">Put value [2]</Trace>
      <Trace level="3" type="T">Close tag [DIRECT]</Trace>
      <Trace level="3" type="T">Start tag [IDOCTYP]</Trace>
      <Trace level="3" type="T">Put value [DEBMAS03]</Trace>
      <Trace level="3" type="T">Close tag [IDOCTYP]</Trace>
      <Trace level="3" type="T">Start tag [MESTYP]</Trace>
      <Trace level="3" type="T">Put value [DEBMAS]</Trace>
      <Trace level="3" type="T">Close tag [MESTYP]</Trace>
      <Trace level="3" type="T">Start tag [SNDPOR]</Trace>
      <Trace level="3" type="T">Put value [SAPXI2]</Trace>
      <Trace level="3" type="T">Close tag [SNDPOR]</Trace>
      <Trace level="3" type="T">Start tag [SNDPRT]</Trace>
      <Trace level="3" type="T">Put value [LS]</Trace>
      <Trace level="3" type="T">Close tag [SNDPRT]</Trace>
      <Trace level="3" type="T">Start tag [SNDPRN]</Trace>
      <Trace level="3" type="T">Put value [XI2CLNT100]</Trace>
      <Trace level="3" type="T">Close tag [SNDPRN]</Trace>
      <Trace level="3" type="T">Start tag [RCVPOR]</Trace>
      <Trace level="3" type="T">Put value [SAPDES]</Trace>
      <Trace level="3" type="T">Close tag [RCVPOR]</Trace>
      <Trace level="3" type="T">Start tag [RCVPRT]</Trace>
      <Trace level="3" type="T">Put value [LS]</Trace>
      <Trace level="3" type="T">Close tag [RCVPRT]</Trace>
      <Trace level="3" type="T">Start tag [RCVPRN]</Trace>
      <Trace level="3" type="T">Put value [IGATE_800]</Trace>
      <Trace level="3" type="T">Close tag [RCVPRN]</Trace>
      <Trace level="3" type="T">Close tag [EDI_DC40]</Trace>
      <Trace level="3" type="T">Start tag [E1KNA1M]</Trace>
      <Trace level="3" type="T">Add attribute: [SEGMENT]=[1]</Trace>
      <Trace level="3" type="T">Start tag [MSGFN]</Trace>
      <Trace level="3" type="T">Put value [005]</Trace>
      <Trace level="3" type="T">Close tag [MSGFN]</Trace>
      <Trace level="3" type="T">Start tag [KUNNR]</Trace>
      <Trace level="3" type="T">Put value [000000I236]</Trace>
      <Trace level="3" type="T">Close tag [KUNNR]</Trace>
      <Trace level="3" type="T">Start tag [KTOKD]</Trace>
      <Trace level="3" type="T">Put value [0001]</Trace>
      <Trace level="1" type="T">*** APPLICATION TRACE TRUNCATED (for more details see LogViewer)***</Trace>
      <Trace level="2" type="T">Java mapping com/sap/xi/tf/_ZEP_TO_IDES_MM_ completed. (executeStep() of com.sap.xi.tf._ZEP_TO_IDES_MM_</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2006-08-07T08:59:29Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 005</Trace>
      <Trace level="3" type="T">Message version 005</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
      <Trace level="1" type="Timestamp">2006-08-07T08:59:29Z CET Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
      <Trace level="1" type="T">processing the outbound binding</Trace>
      <Trace level="1" type="T">search outbound bindings</Trace>
      <Trace level="2" type="T">search outbound binding for:</Trace>
      <Trace level="2" type="T">... sender party =</Trace>
      <Trace level="2" type="T">... sender service = FILE_TO_IDOC_BS</Trace>
      <Trace level="2" type="T">... receiver party =</Trace>
      <Trace level="2" type="T">... receiver service = SAPIDES</Trace>
      <Trace level="2" type="T">... receiver interface namespace = urn:sap-com:document:sap:idoc:messages</Trace>
      <Trace level="2" type="T">... receiver interface name = DEBMAS.DEBMAS03</Trace>
      <Trace level="2" type="T">outbound binding found</Trace>
      <Trace level="2" type="T">outbound channel is:</Trace>
      <Trace level="2" type="T">... party =</Trace>
      <Trace level="2" type="T">... service = SAPIDES</Trace>
      <Trace level="2" type="T">... name = ZEP_TO_IDES_RCC</Trace>
      <Trace level="2" type="T">no header mapping defined</Trace>
      <Trace level="1" type="T">outbound bindings found</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2006-08-07T08:59:29Z CET End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 006</Trace>
      <Trace level="3" type="T">Message version 006</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
      <Trace level="1" type="Timestamp">2006-08-07T08:59:29Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">ADRESSMOD = SD</Trace>
      <Trace level="3" type="T">P_CLASS =</Trace>
      <Trace level="3" type="T">P_IFNAME =</Trace>
      <Trace level="3" type="T">P_METHOD =</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Channel for IDOC adapter: IDoc</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = IDOC</Trace>
      <Trace level="3" type="T">ADRESSMOD = SD</Trace>
      <Trace level="3" type="T">P_CLASS = CL_IDX_IDOC_SERVICE</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">---- Outbound IDoc-Adapter -
    </Trace>
      <Trace level="1" type="T">----
    </Trace>
    - <Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-ENTER_PLSRV">
      <Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>
      <Trace level="1" type="T">Get Information from IS-Header Objekt</Trace>
      <Trace level="1" type="T">Get Information from SD-IDoc-Endpoint</Trace>
      <Trace level="2" type="T">----
    </Trace>
      <Trace level="2" type="T">IDoc-Endpoint Channel :</Trace>
      <Trace level="2" type="T">RFCDEST : IGATE_800</Trace>
      <Trace level="2" type="T">Port : SAPDES</Trace>
      <Trace level="2" type="T">Docrel :</Trace>
      <Trace level="2" type="T">Version : 3</Trace>
      <Trace level="2" type="T">Saprel : 640</Trace>
      <Trace level="2" type="T">Queue-ID:</Trace>
      <Trace level="2" type="T">----
    </Trace>
      <Trace level="1" type="T">Get IDoc-XML from the Resource Objekt</Trace>
    - <Trace level="1" type="B" name="IDX_XML_TO_IDOC">
      <Trace level="1" type="T">Parse XML-BODY</Trace>
      <Trace level="1" type="T">Get the Metadata for port SAPDES</Trace>
      <Trace level="2" type="T">----
    </Trace&g

  • Graphical Mapping Problem : Create Segments by conditions

    Hi,
    i have a problem while mapping an incoming invoice to IDoc Invoic02. I had to create some Segments (E1EDP02) on basis of identifiers in the incoming message. I hope the following example i created will help to understand my exact problem:
    EXAMPLE MESSAGE:
    <invoice>
    <document>
    <position>
       <line>
         <posnum> 1 </posnum>
         <IMD>
         <ident> Name </ident>
         <val>   Maxx </val>
         </IMD>
         <IMD>
         <ident> Age </ident>
         <val>   19 </val>
         </IMD>
         <IMD>
         <ident> Gender </ident>
         <val>   Male </val>
         </IMD>
       </line>
    </position>
    <position>
       <line>
         <posnum> 2 </posnum>
         <IMD>
         <ident> Name </ident>
         <val>   Tina </val>
         </IMD>
         <IMD>
         <ident> Age </ident>
         <val>   28 </val>
         </IMD>
         <IMD>
         <ident> Gender </ident>
         <val>   Female </val>
         </IMD>
       </line>
    </position>
    </document>
    </invoice>
    THE RESULT I WANT:
    <invoic02>
    <E1EDP01>
    <SEGMENT> </SEGMENT>
    <POSEX> 1 </POSEX>
      <E1EDP02>
           <SEGMENT> </SEGMENT>
         <QUALF> 021 </QUALF>
         <BELNR> 19 </BELNR> // THIS should be the Age
      </E1EDP02>
      <E1EDP19>
      </E1EDP19>
    </E1EDP01>
    <E1EDP01>
    <SEGMENT> </SEGMENT>
      <POSEX> 2 </POSEX>
      <E1EDP02>
         <SEGMENT> </SEGMENT>
         <QUALF> 021 </QUALF>
         <BELNR> 28 </BELNR> // THIS should be the Age
      </E1EDP02>
      <E1EDP19>
      </E1EDP19>
    </E1EDP01>
    </invoic02>
    I tried to different ways to get the above result but i failed
    My first try:
    ident      -------|--- equalsS ------ createIf ---- E1EDP02
    Constant[000] --------- SEGMENT
    Constant[Age]--|
    ident      -------|--- equalsS ------ ifWithoutElse ---- QUALF
    Constant[Age]--|             |          
                           |
                        Constant[021]
    ident      -------|--- equalsS ------ ifWithoutElse ---- BELNR
    Constant[Age]--|             |          
                           |
                           val
    Result:
    The E1EDP02 Element will not created reliable. Sometimes it is there sometimes not dunno why ? Any Idea ?
    My second try:
    IMD -------------- E1EDP02
    Constant[000] --------- SEGMENT
    ident      -------|--- equalsS ------ ifWithoutElse ---- QUALF
    Constant[Age]--|             |          
                           |
                        Constant[021]
    ident      -------|--- equalsS ------ ifWithoutElse ---- BELNR
    Constant[Age]--|             |          
                           |
                           val
    Result:
    Now every E1EDP01 Element has two E1EDP02 Elements. One correct one and an empty one with only a segment element. Is there a way to delete this empty elements ?
    Any ideas to create a working mapping ?
    Thanks

    @Liang Ji 
    When i do this i have only the first E1EDP01 Element
    @Tarang Shah
    Which function i had to use for this ?
    Thank you

Maybe you are looking for

  • Develop history in Lightroom mobile?

    Trying out the LR CC syncing. From desktop, I synced a collection and one photo (RAW) in it appeared correctly in my phone app. Then I made some develop edits on my phone and those changes appeared correctly in my desktop. However, when viewing the p

  • Ipod Touch no longer syncing/backing up automatically

    I recently had to get my laptop "cleaned" due to a nasty virus, I had to reinstall Itunes but when I plug in my ipod nothing happens, itunes no longer syncs or backs up automatically, although it does recognise my ipod and everything is just the same

  • FPCOMP_FORM_START Problem Adobe.

    In production server i am taking print out of one adobe form but while executing it is showing USAGE ERROR in FM FPCOMP_FORM_START , as a result program enable to generate its o/p. Pls suggest to remove this probelm.!

  • When I connect a second display both displays start to cycle on and off.

    I am connecting a second display that works on both my macbook and macbook pro. When I connect it to my imac, both monitors start blinking on and off. Any ideas? Thanks Message was edited by: Stephen Ethan Message was edited by: Stephen Ethan

  • Refresh/Copy of SAP BPC/HANA Environment

    Hi experts, We are running SAP BPC on HANA with BW as our EDW. We would like to refresh our Regression environment with Production. However, i understand that with HANA technology the refresh may not be as simple as just a copy exercise. Could you pl