Unable to find Idoc in XI

Hi,
Idoc -> XI -> File
I am trying to send an Idoc (ZANSO_MT) from R/3 side to XI.
Status of the message is green in we05 in R/3 but I am unable to find it in XI. I have checked in idx5, we05.
All the RFC connections are working fine with authorization test.
Althought, I was successfully able to import Idoc metadata in IR but I have an error in idx2 "Basic Type ZANSO_MT is unknown". This IDoc is released in R/3 side and I am successfully able to generate and send it.
Pls let me know where to check.
Regards,
Anirudh.

Thank you all for your responses.
@Jayasimha
RFC destinations are working fine as mentioned in my first post.
I have done connection test and also authorization test.
I can see the IDoc successfully sent in we05 in R/3.
I have also changed the port name in idx1 in XI same as in R/3 but still no success.
@Vijayanth
Check smq1,2. Both are empty. I can import Idoc metadata for ORDERS03 or WP_PLU03 from R/3 but not ZANSO_MT.
I created this custom Idoc in R/3 and I am able to import it in IR.
@Nallam
I have released Idoc in R/3 with transaction we30, we31 and we82. I am successfully able to import this Idoc in IR.
@Seshagiri
I have created this basic type in R/3 and able to import it in IR.
The problem is that in idx2 when I try to import it, it doesn't work but other Idocs like orders etc are getting imported successfully.
@NagaDurga
Tried it but no success.
@Jakub
I can see some errors for this Idoc in sm58 in R/3 but many ZANSO_MT Idocs are successfully processed and their status is green in we05.
Regards,
Anirudh.

Similar Messages

  • Unable to find the IDOC number in WE02

    HI All,
    I have executed an outbound program from SM37 and i can see that job got finished in the log.
    but when i check the spool, it doesnt contain any list and also i am unable to find the Idoc number in WE02.
    I am not clear in this. Please expalin me in detail.

    Hi there,
    Go to Sales order screen, In the main screen below the command line, one button will be there " Services for object" Click that...... It will open one tool bar.... on that tool bar one icon will be there with thee arrow ..... Click on that,,,,, and here you can see the idoc number....
    Thanks,
    Raja

  • Unable to find security data for sender

    Hello, does anybody know what this message means. The problem appear when I send an Idoc to XI. Other interfaces (Master data) are working properly. My question is, do I need to make some extra settings for the transactional data interfaces (SHPMNT)?
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Technical Routing
      -->
    - <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
      <SAP:Context />
      <SAP:Code p1="sapdev222,SHPMNT.SHPMNT05/urn:sap-com:document:sap:idoc:messages" p2="VENDORMASTER_WOLTERKLUWER_ERP_BE,IDZ0001_DeliveryReplicate_IB/http://wolterskluwer.com/xi/midas_deliveries" p3="" p4="">PHYROU.UNDEFINED_SECURITY</SAP:Code>
      <SAP:Text language="EN">Technical routing: Unable to find security data for sender sapdev222,SHPMNT.SHPMNT05/urn:sap-com:document:sap:idoc:messages for receiver VENDORMASTER_WOLTERKLUWER_ERP_BE,IDZ0001_DeliveryReplicate_IB/http://wolterskluwer.com/xi/midas_deliveries</SAP:Text>
      </SAP:ErrorHeader>
    regards
    Ernesto Duran

    HI,
    i am also getting the same error in my scenario. Could u plz inform me what is the solution?
    Rgds,
    Ram Sri

  • Unable to create IDOCs after client copy

    I'm unable to create IDOCs after a client copy.  I receive a SAPSQL_ARRAY_INSERT_DUPREC or insert of duplicate rows ABAP dump.
    Does anyone know what how to fix this.  Thank you in advance.
    Runtime Error          SAPSQL_ARRAY_INSERT_DUPREC
    Except.                CX_SY_OPEN_SQL_DB
    Date and Time          22.10.2007 16:50:51
    ShrtText
    The ABAP/4 Open SQL array insert results in duplicate database records.
    What happened?
    Error in ABAP application program.
    The current ABAP program "SAPLEDI1" had to be terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    is especially useful if you want to keep a particular message.
    Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
    neither
    caught nor passed along using a RAISING clause, in the procedure
    "F09_IDOC_INSERT_WITH_NUMBER" "(FORM)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    If you use an ABAP/4 Open SQL array insert to insert a record in
    the database and that record already exists with the same key,
    this results in a termination.
    (With an ABAP/4 Open SQL single record insert in the same error
    situation, processing does not terminate, but SY-SUBRC is set to 4.)
    How to correct the error
    Use an ABAP/4 Open SQL array insert only if you are sure that none of
    the records passed already exists in the database.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "SAPSQL_ARRAY_INSERT_DUPREC" CX_SY_OPEN_SQL_DBC
    "SAPLEDI1" or "LEDI1F09"
    "F09_IDOC_INSERT_WITH_NUMBER"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
    2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
    after the short dump. In the display, then select the function
    "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, select the Editor function "Further Utilities->
    Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    The exception must either be prevented, caught within the procedure
    "F09_IDOC_INSERT_WITH_NUMBER"
    "(FORM)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    System environment
    SAP Release.............. "640"
    Application server....... "auaplxr3q"
    Network address.......... "128.197.135.5"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "000B439ED600"
    Character length......... 8 Bits
    Pointer length........... 64 Bits
    Work process number...... 1
    Short dump setting....... "full"
    Database server.......... "auaplxr3q"
    Database type............ "ORACLE"
    Database name............ "Q63"
    Database owner........... "SAPR3"
    Character set............ "en_US.ISO8859-1"
    SAP kernel............... "640"
    Created on............... "Mar 22 2007 20:48:46"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
    Patch level.............. "175"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
    10.2.0.."
    SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
    Memory usage.............
    Roll..................... 16128
    EM....................... 4189928
    Heap..................... 0
    Page..................... 0
    MM Used.................. 1469352
    MM Free.................. 2718056
    SAP Release.............. "640"
    User and Transaction
    Information on where terminated
    The termination occurred in the ABAP program "SAPLEDI1" in
    "F09_IDOC_INSERT_WITH_NUMBER".
    The main program was "SAPMSSY1 ".
    The termination occurred in line 108 of the source code of the (Include)
    program "LEDI1F09"
    of the source code of program "LEDI1F09" (when calling the editor 1080).
    Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
    the
    procedure "F09_IDOC_INSERT_WITH_NUMBER" "(FORM)" but was not handled locally,
    not declared in the
    RAISING clause of the procedure.
    The procedure is in the program "SAPLEDI1 ". Its source code starts in line 5
    of the (Include) program "LEDI1F09 ".
    Source Code Extract
    Line
    SourceCde
    78
    perform call_badi tables list_container_insert
    79
    using  control
    80
    ident.
    81
    Aufruf des Badi's für das einstreuen neuer Segmente
    82
    perform call_insert_badi tables list_container_insert
    83
    using control
    84
    ident
    85
    changing maxsegnum.
    86
    87
       free list_container_insert
    88
    FREE_RETURN = 1.
    89
    ELSE. " no other IDoc is open in create-mode
    90
    LOOP AT LIST_CONTAINER_CREATE WHERE MANDT EQ SY-MANDT
    91
    AND   DOCNUM EQ IDENT.
    92
    LIST_CONTAINER_CREATE-DOCNUM = DOCNUM.
    93
    MODIFY LIST_CONTAINER_CREATE.
    94
    ADD 1 TO MAXSEGNUM.
    95
    ENDLOOP.
    96
    if control-mestyp eq c_mestyp.
    97
    CALL FUNCTION 'FUNCTION_EXISTS'
    98
    EXPORTING
    99
    funcname           = c_func
    100
    EXCEPTIONS
    101
    FUNCTION_NOT_EXIST = 1.
    102
    IF syst-subrc IS INITIAL.  "Anwendungssystem
    103
    perform call_transform
    104
    tables list_container_create
    105
    using  control.
    106
    ENDIF.
    107
    endif.
    >>>>>
    INSERT EDID4 FROM TABLE LIST_CONTAINER_CREATE.
    109
    Aufruf des Badi's für das Anwendungsmapping einzelner Felder
    110
    perform call_badi tables list_container_create
    111
    using  control
    112
    ident.
    113
    perform call_insert_badi tables list_container_create
    114
    using  control
    115
    ident
    116
    changing maxsegnum.
    117
    118
      free list_container_create
    119
    FREE_RETURN = 0.
    120
    ENDIF.
    121
    122
    insert status records
    123
    124
    SYN_ERROR_IN = ' '.
    125
    CNTR_STATUS = 0.
    126
    REFRESH LIST_STATUS.
    127
    CLEAR LIST_STATUS.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    2
    SY-TABIX
    1
    SY-DBCNT
    1
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    CPIC and RFC Control
    SY-MSGTY
    SY-MSGID
    SY-MSGNO
    000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    13 FORM         SAPLEDI1                            LEDI1F09                              108
    F09_IDOC_INSERT_WITH_NUMBER
    12 FUNCTION     SAPLEDI1                            LEDI1U19                               33
    EDI_DOCUMENT_CLOSE_CREATE_TAB
    11 FUNCTION     SAPLEDIR                            LEDIRU01                              273
    IDOC_INBOUND_WRITE_TO_DB
    10 FORM         SAPLEDIN                            LEDINF01                              457
    ONE_IDOC_STORE
    9 FUNCTION     SAPLEDIN                            LEDINU05                              234
    IDOC_INBOUND_ASYNCHRONOUS
    8 FORM         SAPLEDIN                            LEDINV05                               19
    IDOC_INBOUND_ASYNCHRONOUS
    7 FORM         SAPMSSY1                            SAPMSSY1                              254
    XAB_RUN_DRIVER
    6 FUNCTION     SAPLSXAB                            LSXABU01                                9
    RFC_RUN_XAB_DRIVER
    5 FUNCTION     SAPLERFC                            LERFCU01                               59
    ARFC_EXECUTE
    4 FUNCTION     SAPLERFC                            LERFCU02                              229
    ARFC_DEST_SHIP
    3 FORM         SAPLERFC                            LERFCV02                               28
    ARFC_DEST_SHIP
    2 FORM         SAPMSSY1                            SAPMSSY1                               69
    REMOTE_FUNCTION_CALL
    1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
    %_RFC_START
    Chosen variables
    Name
    Val.
    No.      13 Ty.          FORM
    Name  F09_IDOC_INSERT_WITH_NUMBER
    CONTROL-MESTYP
    USERCLONE
    554544444222222222222222222222
    53523CFE5000000000000000000000
    C_MESTYP
    FIDCCH
    444444222222222222222222222222
    694338000000000000000000000000
    SY-XFORM
    IDOC_INBOUND_ASYNCHRONOUS
    444454444544545544454445522222
    94F3F9E2F5E4F139E382FEF5300000
    LIST_STATUS-STAPA2
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    C_FUNC
    IDOC_TRANSFORM
    444455544544542222222222222222
    94F3F421E36F2D0000000000000000
    SYST-REPID
    SAPLEDI1
    5454444322222222222222222222222222222222
    310C549100000000000000000000000000000000
    SY-UNAME
    Q63CLNT140
    533444533322
    1633CE414000
    %_DUMMY$$
    2222
    0000
    SY-MSGV1
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SYST-SUBRC
    0
    0000
    0000
    ALE_IDOC_TO_APL_OK
    62
    33
    62
    LIST_CONTAINER_CREATE[]
    Table IT_20[9x1068]
    FUNCTION-POOL=EDI1DATA=LIST_CONTAINER_CREATE[]
    Table reference: 14
    TABH+  0(20) = 070000008036F5B8000000000000000000000000
    TABH+ 20(20) = 0000000E00000014000000090000042CFFFFFFFF
    TABH+ 40(16) = 0400002300000CA0000824C401000000
    store        = 0x070000008036F5B8
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 14    (0x0000000E)
    label        = 20    (0x00000014)
    fill         = 9     (0x00000009)
    leng         = 1068  (0x0000042C)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000048
    occu         = 8     (0x00000008)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x070000008036F610
    pghook       = 0x07000000802D86D0
    idxPtr       = 0x0000000000000000
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    store_id     = 23    (0x00000017)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    LIST_CONTAINER_CREATE
    1400000000000511747000000009E1BPADRML                     00000002#èXD63        070TST_QA140_1
    3333333333333333333333333333434544544222222222222222222222333333330E54332222222233355555433353
    14000000000005117470000000095120142DC0000000000000000000000000000238846300000000070434F11140F1
    CONTROL
    1400000000000511747640 64        2SAPQ63    LSQ63CLNT140
    3333333333333333333333233222222223545533222245533444533322222222222222222222222222222222222222
    14000000000005117476400640000000023101630000C31633CE414000000000000000000000000000000000000000
    G_MAXSYNERR
    1
    0000
    0001
    <%_TABLE_EDID4>
    ALE_DISPATCH_ERROR
    27
    33
    27
    ALE_IDOC_READY_FOR_APL
    64
    33
    64
    %_SPACE
    2
    0
    IDENT
    0000000000000001
    3333333333333333
    0000000000000001
    ALE_IDOC_TO_APL_ERROR
    63
    33
    63
    No.      12 Ty.          FUNCTION
    Name  EDI_DOCUMENT_CLOSE_CREATE_TAB
    IDENTIFIER
    0000000000000001
    3333333333333333
    0000000000000001
    NO_DEQUEUE
    X
    5
    8
    SYN_ACTIVE
    Y
    5
    9
    IDOC_CONTROL
    1400000000000511747640 64        2SAPQ63    LSQ63CLNT140
    3333333333333333333333233222222223545533222245533444533322222222222222222222222222222222222222
    14000000000005117476400640000000023101630000C31633CE414000000000000000000000000000000000000000
    SYNTAX_RETURN
    0
    0000
    0000
    INT_EDIDD[]
    Table IT_10[9x1062]
    FUNCTION-POOL=EDINDATA=G_T_DATA_RECORDS[]
    Table reference: 9
    TABH+  0(20) = 0700000080284B80070000008028530800000000
    TABH+ 20(20) = 000000090000000A0000000900000426FFFFFFFF
    TABH+ 40(16) = 0400000900000AA8000824C401000000
    store        = 0x0700000080284B80
    ext1         = 0x0700000080285308
    shmId        = 0     (0x00000000)
    id           = 9     (0x00000009)
    label        = 10    (0x0000000A)
    fill         = 9     (0x00000009)
    leng         = 1062  (0x00000426)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000039
    occu         = 8     (0x00000008)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x0700000080320D90
    pghook       = 0x07000000802E1508
    idxPtr       = 0x0000000000000000
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    store_id     = 17    (0x00000011)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    hsdir        = 0x0000000000000000
    ext2         = 0x07000000802852A8
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x0700000080284B30
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    NO_IGNORE
    2
    0
    EDI_IDOC_SYNTAX_ERROR_IN
    60
    33
    60
    DOCNUM
    0000000000511747
    3333333333333333
    0000000000511747
    EXCLUSIVE
    E
    4
    5
    SYNCHRONOUS
    S
    5
    3
    APL_TESTIDOC_CHECK_OK
    55
    33
    55
    FREE_RETURN
    0
    0000
    0000
    INT_EDIDD
    1400000000000000001000009E1BPADRML                  00000000##XD63        070TST_QA140_17  X00
    3333333333333333333333333434544544222222222222222222333333330054332222222233355555433353322533
    14000000000000000010000095120142DC0000000000000000000000000000846300000000070434F11140F1700800
    SUB_INT_ACK_POSITIVE
    14
    33
    14
    G_INSERT_OK
    2
    0
    LIST_CONTAINER_INSERT_TMP[]
    Table[initial]
    LIST_CONTAINER_INSERT_TMP
    0000000000000000000000000                              00000000##
    2223333333333333333333333333222222222222222222222222222222333333330022222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    No.      11 Ty.          FUNCTION
    Name  IDOC_INBOUND_WRITE_TO_DB
    PI_DO_HANDLE_ERROR
    X
    5
    8
    PI_NO_DEQUEUE
    X
    5
    8
    PI_RETURN_DATA_FLAG
    X
    5
    8
    PI_RFC_MULTI_CP
    0000
    3333
    0000
    PI_STATUS_MESSAGE
    000000000000000000000000000000000000000000000000000000000000
    2223333333333333333333333333333333333333333333333333333333333332222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    PE_IDOC_NUMBER
    0000000000000001
    3333333333333333
    0000000000000001
    PE_INBOUND_PROCESS_DATA
    140BAPI                                                  6
    3334454222222222222222222222222222222222222222222222222223222222222222222222222222222222222222
    1402109000000000000000000000000000000000000000000000000006000000000000000000000000000000000000
    PE_STATE_OF_PROCESSING
    0
    0000
    0000
    T_DATA_RECORDS[]
    Table IT_10[9x1062]
    T_LINKED_OBJECTS[]
    Table IT_11[0x100]
    FUNCTION-POOL=EDINFORM=ONE_IDOC_STOREDATA=LT_LINKED_OBJECTS[]
    Table reference: 10
    TABH+  0(20) = 000000000000000007000000802853F000000000
    TABH+ 20(20) = 0000000A0000000B0000000000000064FFFFFFFF
    TABH+ 40(16) = 0400000900002BB00010249401000000
    store        = 0x0000000000000000
    ext1         = 0x07000000802853F0
    shmId        = 0     (0x00000000)
    id           = 10    (0x0000000A)
    label        = 11    (0x0000000B)
    fill         = 0     (0x00000000)
    leng         = 100   (0x00000064)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000190
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    store_id     = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    hsdir        = 0x0000000000000000
    ext2         = 0x0700000080285390
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x0700000080285340
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    PC_CONTROL_RECORD
    1400000000000000000    30        2          LSQ63CLNT140
    3333333333333333333222233222222223222222222245533444533322222222222222222222222222222222222222
    14000000000000000000000300000000020000000000C31633CE414000000000000000000000000000000000000000
    %_VIASELSCR
    0
    4
    %_SPACE
    2
    0
    L_STATUS
    64
    33
    64
    L_ALE_SUCCESS_MESSAGE
    B1                  S005                                                  No filters
    4322222222222222222253332222222222222222222222222222222222222222222222222246266676772222222222
    21000000000000000000300500000000000000000000000000000000000000000000000000EF069C45230000000000
    ST_PREVIOUS_PARTNER_DATA-SYNCHK
    X
    5
    8
    C_TRUE
    X
    5
    8
    SYST-REPID
    SAPLEDIR
    5454444522222222222222222222222222222222
    310C549200000000000000000000000000000000
    C_ELEMENT_UNPROCESSED_IDOCS
    Unprocessed_IDocs
    56776667766544667222222222222222
    5E02F353354F94F33000000000000000
    ST_PREVIOUS_STATE_OF_PROCE
    0
    0000
    0000
    ST_INBOUND_PROCESS_DATA-EDIVR2
    6
    3
    6
    SY-MSGV4
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    L_SYN_ACTIVE
    Y
    5
    9
    SY-XFORM
    IDOC_INBOUND_ASYNCHRONOUS
    444454444544545544454445522222
    94F3F9E2F5E4F139E382FEF5300000
    L_SYNTAX_RETURN
    0
    0000
    0000
    %_DUMMY$$
    2222
    0000
    SY-REPID
    SAPLEDIR
    5454444522222222222222222222222222222222
    310C549200000000000000000000000000000000
    No.      10 Ty.          FORM
    Name  ONE_IDOC_STORE
    IDOC_NUMBER_IN
    0000000000000000
    3333333333333333
    0000000000000000
    STATE_OF_PROCESSING_IN
    0
    0000
    0000
    INBOUND_PROCESS_DATA_IN
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    GT_NEW_IDOC_IDENTIFICATIONS[]
    Table[initial]
    G_LAST_IDOC_NUMBER
    0000000000000000
    3333333333333333
    0000000000000000
    SYST-REPID
    SAPLEDIN
    5454444422222222222222222222222222222222
    310C549E00000000000000000000000000000000
    CURRENT_CONTROL_RECORD_IN-DOCNUM
    0000000000000000
    3333333333333333
    0000000000000000
    CONV_ERROR
    2
    0
    C_TRUE
    X
    5
    8
    SY
    0000000000000000000000000000000000000000000000000000000000000000000000000000000200000000000000
    0002000000010009000000000000000000000000000100000001000000010000000000000000004C00000000000000
    STATUS_MESSAGE_IN
    000000000000000000000000000000000000000000000000000000000000
    2223333333333333333333333333333333333333333333333333333333333332222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    C_IDOC_SELECT_AND_WRITE_TO_DB
    5
    3
    5
    SY-REPID
    SAPLEDIN
    5454444422222222222222222222222222222222
    310C549E00000000000000000000000000000000
    STATUS_MESSAGE_IN-STAMID
    22222222222222222222
    00000000000000000000
    GT_NEW_IDOC_IDENTIFICATIONS
    0000000000000000
    3333333333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SPACE
    2
    0
    STATUS_MESSAGE_IN-STAMNO
    000
    333
    000
    RET_FLAG
    X
    5
    8
    G_RFC_CODEPAGE
    0000
    3333
    0000
    RSJOBINFO-JOBSUBRC
    0
    0000
    0000
    SY-XFORM
    IDOC_INBOUND_ASYNCHRONOUS
    444454444544545544454445522222
    94F3F9E2F5E4F139E382FEF5300000
    SY-LANGU
    E
    4
    5
    G_T_DATA_RECORDS[]
    Table IT_10[9x1062]
    LT_LINKED_OBJECTS[]
    Table IT_11[0x100]
    CURRENT_CONTROL_RECORD_IN
    1400000000000000000    30        2          LSQ63CLNT140
    3333333333333333333222233222222223222222222245533444533322222222222222222222222222222222222222
    14000000000000000000000300000000020000000000C31633CE414000000000000000000000000000000000000000
    %_DUMMY$$
    2222
    0000
    SWO_%OBJID
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    No.       9 Ty.          FUNCTION
    Name  IDOC_INBOUND_ASYNCHRONOUS
    IDOC_CONTROL_REC_40[]
    Table IT_3[1x524]
    FUNCTION-POOL=EDINFORM=IDOC_INBOUND_ASYNCHRONOUSDATA=IDOC_CONTROL_REC_40[]
    Table reference: 3
    TABH+  0(20) = 07000000802D876007000000802D449000000000
    TABH+ 20(20) = 0000000300000003000000010000020C000000E0
    TABH+ 40(16) = 0400000900001FE0000A249001000000
    store        = 0x07000000802D8760
    ext1         = 0x07000000802D4490
    shmId        = 0     (0x00000000)
    id           = 3     (0x00000003)
    label        = 3     (0x00000003)
    fill         = 1     (0x00000001)
    leng         = 524   (0x0000020C)
    loop         = 224   (0x000000E0)
    xtyp         = TYPE#000136
    occu         = 10    (0x0000000A)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 0
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000802DB9D8
    pghook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 10    (0x0000000A)
    lineAlloc    = 10    (0x0000000A)
    store_id     = 9     (0x00000009)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    hsdir        = 0x0000000000000000
    ext2         = 0x07000000802D88A0
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x07000000802D8710
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    IDOC_DATA_REC_40[]
    Table IT_4[9x1063]
    FUNCTION-POOL=EDINFORM=IDOC_INBOUND_ASYNCHRONOUSDATA=IDOC_DATA_REC_40[]
    Table reference: 4
    TABH+  0(20) = 07000000802D880807000000802D896000000000
    TABH+ 20(20) = 00000004000000040000000900000427FFFFFFFF
    TABH+ 40(16) = 04000009000020500008249001000000
    store        = 0x07000000802D8808
    ext1         = 0x07000000802D8960
    shmId        = 0     (0x00000000)
    id           = 4     (0x00000004)
    label        = 4     (0x00000004)
    fill         = 9     (0x00000009)
    leng         = 1063  (0x00000427)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000138
    occu         = 8     (0x00000008)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 0
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000802E1550
    pghook       = 0x07000000802D8860
    idxPtr       = 0x0000000000000000
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    store_id     = 12    (0x0000000C)
    shmIsReadOnly = 0     (0x

    Hi Rohan,
    Welcome to SDN!
    This error means that you're trying to duplicate a record on the DB... check the IDOC  number ranges... it might help
    Regards
    Juan
    Please reward with points if helpful

  • Problem "Unable to find resource" in SAP PI 7.0 Sp12

    Hi Experts - We are experiencing below problem in SAP PI 7.0 SP 12.
    Objects are available in the system and cache notifications are green. Even after multiple attemps messages are not processing.
    Is there any resolution action we can take? Details below.
    THanks, Mathias.
    <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">Dynamic Receiver Determination via Mapping.</Trace>
    <Trace level="2" type="T">......attachment XI_Context not found</Trace>
    <Trace level="3" type="T">Object ID of Interface Mapping 721735504F3735BB885E49DD430ACFB0</Trace>
    <Trace level="3" type="T">Version ID of Interface Mapping 4E0CDFA06AAB11DBBE41EACA91374078</Trace>
    <Trace level="1" type="T">Interface Mapping http://eu.Company.com/SC/Mak/Pack/ProdRec/xi NAME_WMTORD_TO_SAP_BASIS_Receivers</Trace>
    <Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_NAME_WMTORD_TO_SAP_BASIS_Receivers_</Trace>
    <Trace level="3" type="T">Dynamic Configuration ( http://sap.com/xi/XI/System/IDoc SNDPOR SAPSXX ) ( http://sap.com/xi/XI/System/IDoc SNDPRN SXXCLNT010 ) ( http://sap.com/xi/XI/System/IDoc SNDPRT LS ) ( http://sap.com/xi/XI/System/IDoc RCVPOR XXXCLNT010 ) ( http://sap.com/xi/XI/System/IDoc RCVPRN X1295_LWHA ) ( http://sap.com/xi/XI/System/IDoc RCVPRT LS ) ( http://sap.com/xi/XI/System/IDoc MESTYP WMTORD ) ( http://sap.com/xi/XI/System/IDoc IDOCTYP WMTOID01 ) ( http://sap.com/xi/XI/System/IDoc CIMTYP )</Trace>
    <Trace level="2" type="T">Mode 0</Trace>
    <Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_NAME_WMTORD_TO_SAP_BASIS_Receivers_.</Trace>
    <Trace level="3" type="T">Load 4e0cdfa0-6aab-11db-be41-eaca91374078, http://eu.Company.com/SC/Mak/Pack/ProdRec/xi, -1, com/sap/xi/tf/_NAME_WMTORD_TO_SAP_BASIS_Receivers_.class.</Trace>
    <Trace level="3" type="T">Search com/sap/xi/tf/_NAME_WMTORD_TO_SAP_BASIS_Receivers_.class (http://eu.Company.com/SC/Mak/Pack/ProdRec/xi, -1) in swcv 4e0cdfa0-6aab-11db-be41-eaca91374078.</Trace>
    <Trace level="3" type="T">Does not found exact entry. Search in other namspaces.</Trace>
    <Trace level="3" type="T">Search com/sap/xi/tf/_NAME_WMTORD_TO_SAP_BASIS_Receivers_.class (-1) in swcv 4e0cdfa0-6aab-11db-be41-eaca91374078 without namespace.</Trace>
    <Trace level="1" type="T">Class not found: com.sap.xi.tf._NAME_WMTORD_TO_SAP_BASIS_Receivers_</Trace>
    <Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.persist.ResourceNotFoundException: Unable to find resource com/sap/xi/tf/_NAME_WMTORD_TO_SAP_BASIS_Receivers_.class (http://eu.Company.com/SC/Mak/Pack/ProdRec/xi, 4e0cdfa0-6aab-11db-be41-eaca91374078, -1) at com.sap.aii.ibrun.server.mapping.persist.DBSwcvMappingPersistor.getInputStream(DBSwcvMappingPersistor.java:325) at com.sap.aii.ibrun.server.mapping.persist.DBSwcvMappingPersistor.readFile(DBSwcvMappingPersistor.java:203) at com.sap.aii.ibrun.server.mapping.persist.DBSwcvMappingPersistor.readClass(DBSwcvMappingPersistor.java:195) at com.sap.aii.ibrun.server.mapping.MappingLoader.findClass(MappingLoader.java:138) at java.lang.ClassLoader.loadClass(ClassLoader.java:627) at java.lang.ClassLoader.loadClass(ClassLoader.java:593) at com.sap.aii.ibrun.server.mapping.JavaMapping.load(JavaMapping.java:95) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:45) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor329.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:62) at java.lang.reflect.Method.invoke(Method.java:391) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy252.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor328.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:62) at java.lang.reflect.Method.invoke(Method.java:391) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:275) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:217) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7803) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2405) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1728) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8164) at com.sap.mw.jco.JCO$Server.work(JCO.java:8284) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8231) at com.sap.mw.jco.JCO$Server.run(JCO.java:8147) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:219) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</Trace>
    <Trace level="1" type="T">java.lang.ClassNotFoundException at JavaMapping.load(): Could not load class: com/sap/xi/tf/_NAME_WMTORD_TO_SAP_BASIS_Receivers_</Trace>

    Hi - We have executed the re-transport which resolved the situation described above.
    However we have not been able to fully close the topic and understand the root cause.
    Our current understanding is as follows:
    At the time of a transport activation, a cache notification is created and the information is transmitted from the Integration Directory to the different caches using user XIDIRUSER. After the successful notification, the cache update is triggered. This is initiated by the IE ABAP Runtime via user XIISUSER. This user is calling the Integration Directory which than takes user XIDIRUSER to retrieve the required objects, e.g. message mappings, from the Integration Repository. If at this stage, the user XIDIRUSER does not receive an available Work-Process, the action is not completed. This means also the cache notification stays green, as the negative feedback cannot be transmitted either, since the user XIDIRUSER 'died out'.
    This was confirmed to happen in an overload situation for our system.
    Please comment if you have any further experiences or different explanation.
    Mathias

  • Unable to find channel ID at inbound SOAP Adapter

    Hi experts,
    I encountered a very puzzling problem:
    I have a scenario:
    IDOC -> XI -> SOAP
    For 2 interfaces of such nature, 1 works fine, 1 doesn't.
    The one that does not work is throwing the following error in RWB - Message Display Tool (MDT):
    2007-03-22 10:57:05 Success The message was successfully received by the messaging system. Profile: XI URL: http://ootspdbs02:50100/MessagingSystem/receive/AFW/XI
    2007-03-22 10:57:05 Success Using connection AFW. Trying to put the message into the receive queue.
    2007-03-22 10:57:06 Success Message successfully put into the queue.
    2007-03-22 10:57:06 Success The message was successfully retrieved from the receive queue.
    2007-03-22 10:57:06 Success The message status set to DLNG.
    <b>2007-03-22 10:57:06 Error Unable to find channel ID
    2007-03-22 10:57:06 Error Delivery of the message to the application using connection AFW failed, due to: Couldn't find delivery channel for message: a277e57c-c837-e44f-9ae2-da0d701980c4. </b>
    2007-03-22 10:57:06 Success The asynchronous message was successfully scheduled to be delivered at Thu Mar 22 10:58:06 SGT 2007.
    2007-03-22 10:57:06 Success The message status set to WAIT.
    In SXMB_MONI, it shows the message has been processed successfully - indicating that the mapping is fine. Status = Awaiting acknowledgement.
    I've looked up the forums, and the general solution offered is to refresh the SLD cache.
    I've tried that, but it doesn't work.
    Please help.
    Thanks.
    Ron

    > hmm.. then things not a problem with the cache.
    > Is the error in MONI? Or is it in the Adapter Engine?
    >
    >
    > I know it isrepeatitive, but checking if the Objects
    > are all active and correct in the ID is the only
    > solution I can suggest.
    >
    > Regards
    > Bhavesh
    In the MONI, the status is successful, awaiting acknowledgement.
    After sometime, the ack status will be "Acknowledgement contains System Errors"
    <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="OUTBINDING">CO_TXT_ROUTING_BACK_ERROR</SAP:Code>
      <SAP:P1>,BS_DEV1_NAUTICUS_OOTS</SAP:P1>
      <SAP:P2>,BS_NHGDDBS01,,</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error occurred during back-routing Error in communication channel</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
    But I don't think these are related, because the message wasn't sent out, naturally there's an error in the ack.

  • Unable to find payment document.

    Dear Gurus,
    Recently it happened that a user ran F110 for few vendors. Three of these vendors were part of two different F110 run, both run by the same user (with a time gap of 5 min). However, a payment document has got created in each payment run.
    What I mean is for the three vendors who were part of both the payment runs I can see two payment documents per one open item- i.e. one ZP document in each payment run. I went through the Payment Run Log to check that I was looking at things in the right manner and confirmed the above. Even if I consider that both payment documents might have paid two different accounting documents, how is it possible that a "ZP" document created during payment run is not visible through FB03 or FBL1N.
    The error message I am getting is "Document number does not exist in company code XYZA or has been archived".
    However, though I am able to see one of the payment documents through FBL1N or FB03, I am unable to find the one created in the second payment run.
    Could any of you kindly guide me as to what is wrong or what I could have missed??????????
    Thank you guys

    Dear Mr. BIANCOTTI,
    Thank you for your kind reply.
    I have checked the REGUP & REGUH tables. The payment documents that appear in the F110 payment log appear there as well. It further clears the earlier point that I made in my previous post - there are two payment documents (and even two IDoc numbers) per accounting document for those vendors.
    Tables BKPF & BSEG only has those documents which I can trace through FB03.
    If you think I might have missed somthing else, kindly let me know.
    Thank you

  • Unable to find the timestamp in SPRO-"delete timestamp for infosource"

    in system BIT.
    issue: unable to find the timestamp in SPRO-"delete timestamp for infosource" in ECQ, for a load which i did in BIQ and getting error that init was already done but request was deleted from target.
    for cube 0CFM_C10, i did init load from 0CFM_POSITIONS flow , was fine
    next init load from flow 0CFM_DELTA_POSITIONS, some issue,
    got messaget that init was already done but request was deleted from target.
    so i deleted req from infopkg-scheduler-init options for src system - here deleted the req.
    did load got same error again.
    next in ECQ, SPRO- "delete timestamp for infosource", for this option when i search, i am getting msg that "0 timestamps deleted for infosource".
    why is that i am unable to find the timestamp here in SPRO in ECQ? any other solution ?
    pls  help
    regards,
    swetha

    thanks.
    deleted the additional entry from SPRO as suggested in this thread.
    Error while executing RSA3
    did the load ,
    init load via 0CFM_DELTA_POSITIONS flow, successful :   so that error got solved.
    delta load via 0CFM_DELTA_POSITIONS flow, getting another new error and message below
    Job terminated in source system --> Request set to red
    can anyone suggest on how to solve this?
    in src system logs, this data was found
    Job log overview for job:    BIREQU_DAVZG15LMNNG2N3XPN9J5C6QS / 11111300
    Date       Time     Message text                                                                      Message class Message no. Message type
    19.07.2011 11:11:13 Job started                                                                            00           516          S
    19.07.2011 11:11:13 Step 001 started (program SBIE0001, variant &0000000083979, user ID ALEECQREMOTE)      00           550          S
    19.07.2011 11:11:13 Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)               R3           413          S
    19.07.2011 11:11:13 DATASOURCE = 0CFM_DELTA_POSITIONS                                                      R3           299          S
    19.07.2011 11:11:13 RLOGSYS    = BITST                                                                     R3           299          S
    19.07.2011 11:11:13 REQUNR     = REQU_DAVZG15LMNNG2N3XPN9J5C6QS                                            R3           299          S
    19.07.2011 11:11:13 UPDMODE    = D                                                                         R3           299          S
    19.07.2011 11:11:13 LANGUAGES  = *                                                                         R3           299          S
    19.07.2011 11:11:13 *************************************************************************              R8           048          S
    19.07.2011 11:11:13 *          Current Values for Selected Profile Parameters               *              R8           049          S
    19.07.2011 11:11:13 *************************************************************************              R8           048          S
    19.07.2011 11:11:13 * abap/heap_area_nondia......... 0                                       *             R8           050          S
    19.07.2011 11:11:13 * abap/heap_area_total.......... 16777216000                             *             R8           050          S
    19.07.2011 11:11:13 * abap/heaplimit................ 40000000                                *             R8           050          S
    19.07.2011 11:11:13 * zcsa/installed_languages...... 1CEFIJKLNOSUV                           *             R8           050          S
    19.07.2011 11:11:13 * zcsa/system_language.......... E                                       *             R8           050          S
    19.07.2011 11:11:13 * ztta/max_memreq_MB............ 2047                                    *             R8           050          S
    19.07.2011 11:11:13 * ztta/roll_area................ 3000000                                 *             R8           050          S
    19.07.2011 11:11:13 * ztta/roll_extension........... 2000000000                              *             R8           050          S
    19.07.2011 11:11:13 *************************************************************************              R8           048          S
    19.07.2011 11:14:15 Internal session terminated with a runtime error (see ST22)                            00           671          A
    19.07.2011 11:14:15 Job cancelled                                                                          00           518          A
    Edited by: Swetha N on Jul 21, 2011 6:40 AM
    Edited by: Swetha N on Jul 21, 2011 6:40 AM

  • "Unable to find channel ID" error.

    Hello experts,
    We are building an IDOC->XI->JMS scenario.
    Sending the IDOC gets it into the XI and it is visible inside the SXMB_MONI. Looking at a trace level 3 on the trace section of the message you can see that all pipeline activities are performed as normal.
    The last action of the Outbound Binding is successful and the correct Communication channel name (from the Receiver Agreement) is displayed in the trace - meaning was selected.
    Looking in the RWB on the details of the message show that:
    - message was received from http://xiserver:50000/MessagingSystem/receive/AFW/XI
    - The message goes in and out of the receive queue.
    - the message status set to DLNG
    - Unable to find channel ID.
    - ... error stuff..
    This Channel ID error is the one who causes us trouble.
    Looking at the same place for a PROXY->XI->JMS scenario shows that the correct channel is selected. this channel is the channel in the receiver determination - the name only exists there so it doesn't relate to any other channel (like MQ channel).
    Could really use help finding this problem source or activating J2EE traces the could point to what's wrong.
    Thank's - Yoad.

    Hi,
    One thing which could be wrong is the cache. Try in the IB:Directory to see if all things have been succesfully committed to the CPA.
    Then try to refresh the CPA cache. http://xiserver:50000/CPACache/refresh?mode=full (Login as XIDIRUSER)
    If you are on SP 12, you could use NW administrator on http://xiserver:50000/nwa -> select Monitoring -> Logs and traces and in the blank dropdownbox select Default trace.
    Hope this helps

  • Webmehods unable to lookup IDOC in SAP

    Hi
    We have some IDOCS in SAP.
    Webmethods is talking to SAP and looking up these IDOCS.
    However it is unable to lookup all the IDOCS.
    We are using ECC6 system.
    On further observation we've observed that IDOCS with release 4.6 are lookedup by Webmethods but IDOCS with release 700 ae not looked up.
    What is the reason for this?
    This is the error message that Webmethods gets
    [SAP.108.9351] WmSAP Adapter: Could not find IDoc "ORDERS05.ZGSLSITE_CO(700)
    Rergards
    Dexter

    HI,
    ORDERS05.ZGSLSITE_CO looks like a custom Messagetype.
    Maybe you have the wrong Messagetype or reimport the Metadato for ORDERS05.ZGSLSITE_CO.
    Regards,
    Gordon

  • Unable to find Oracle quote Lines Data

    Hi,
    I have to find the query or any other data source which is getting the data for the Print quote report. I am unable to find out from where the data in report is being displayed.
    The Flow is like...
    Search for any quote.
    Click on the quote link
    One Drop poplist will be displayed. Select Print Quote
    And click on the submit button. The PDF report generated,
    Now I have to find out from where this data is coming. Can anyone help me on this.
    Thanks
    Anoop

    Anoop,
    This is a JTT page and there is no VO. If you wanna see how this report is built check out qotSCocPrint.jsp. Here data source are quoting classes. If u need any quoting related data y do u worry about source, y don't u directly hit quoting tables like aso_quote_headers_all and aso_quote_lines_all.
    --Mukul                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • I'm using matchbook pro and I'm unable to find iPhoto after upgrading to Maverick os

    I'm using matchbook pro and I'm unable to find iPhoto after upgrading to Maverick os

    Open the Mac App Store application and see if iPhoto is under your "Purchases" tab.
    Clinton

  • Unable to import idoc into PI 7.0 system from SAP r/3 system

    Hi Experts,
        I am getting an error while importing an Idoc structure from SAP r/3 system. The error says "unable to read Idoc segments". The Idoc has recently undergone changes. When We are looking at the struture of idoc through IDOCSYN table it is showing updated structure in SAP R/3 system but import to SAP XI is failing.
    Can you suggest some way to tackle this kind of problem.
    regards
    Anupam

    Hi Francis,
       This was indeed an authorization issue. Thank you so much for your valuable suggestion. The user lacked proper authorization to import the idocs.
    Hi All,
        Thank you for all your support. 
    Regards
    Anupam

  • Error Message: "Unable to find qm_dw.htm

    (I'm a low-to-moderate ability user - just upgraded from MX2004 to CS4 and just moved from PC to MacBook) I'm working through various DW CS4 tutorials and added one 'Adobe' plug-in (Lorem and More). On recent DW start-ups I have started getting the message "Unable to find qm_dw.htm in the Configuration/Floaters directory. The floater will not be shown." Does anyone know how I can resolve this? Many thanks in anticipation. John.

    In case it helps, try deleting the DW cache file
    http://kb2.adobe.com/cps/191/tn_19105.html#dat (step 4)

  • Photoshop unable to find Java script plugin

    Since the last ACR update to PSCS6, I am unable to browse in Bridge or Mini Bridge and I get the error message "Could not complete the Browse in Bridge Command because Photoshop was unable to find the JavaScript plugin". When I try to open mini bridge, it will open but there is the error message: "Could not complete the command because the extension could not be loaded". I have tried a system restore and read all of the posts related to this error but no one seems to come up with an answer. I tried pasting the .dll files recommended in another post but that did not help. I tried the suggestion to run PS as an administrator but that did not work. I have searched the web, many people have this problem but very few answers, as per usual with Adobe. Using PSCS6 x64 with Windows7x64. Need help!

    My mind reading abilities are a bit fuzzy today.
    I can't seem to read what version of Photoshop, what computer, what OS you are using?

Maybe you are looking for