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

Similar Messages

  • Unable to send IDOCs from SAP PI 7.3 system to a NON-SAP system

    Hi Experts,
       We have a simple file to IDOC scenario in our SAP PI system. There is no mapping as the file is already in the IDOC-XML format.
    However , the target system is a NON-SAP system. We are using a TCP/IP RFC destination to connect to it.
    Here are the settings we have done,
    1) Creates a 3rd party technical system and business system in SLD.
    2) We have assigned a logical system name for the business system (LSKABA100).
    3) Created a port in IDX1 with the same name LSKABA100 and assigned the TCP/IP RFC destination. The RFC destination is pinging fine.
    4) Imported the metadata for the IDOC from a SAP port and copied the same to LSKABA100 port.
    5) Created the sender agreement, receiver determination, interface determination and receiver agreement in ID.
    When we send the file, there is an error on SM58 transaction of our PI system. It says "RFC_ERROR_SYSTEM_FAILURE: IDocException occurred."
    Other than that it does not provide a lot of details.
    We have seen this thread and this blog but did not get any break through.
    Please help us, if someone has any ideas.
    Best Regards,
    Ravikanth Talagana

    Hi all,
        I am not using any SAP Jco user either in my config or in the RFC destination.
    What is the user id that needs to have the authorization?
    I am using a TCP/IP RFC destination and it does not have any user id/pwd.
    There is also, no problem while doing a connection test to the RFC destination.
    Best Regards,
    Ravikanth Talagana

  • 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

  • Unable to send an idoc from SAP R/3 to XI

    Hi,
    We are trying to send Z_CREMAS_SUSMM.CREMAS03 idoc from R/3 system to XI using IDOC adapter.
    We have done the following steps.
    On  SAP R/3 system:
    1.created a RFc Destination which points to the XI system using transaction SM59
    2.created a port in which we have selected  this RFC Destination   using tansaction WE21
    3.logical system for R/3  with transacion BD54
    4.In WE20 transaction,we have configured the PartnerProfile by adding the IDOC message type to the outbound Parameters of XI Logical system.
    On XI Sytem:
    1.Created RFC destination
    2.Created a Port
    3.Loaded metadata
    While trying to Post IDOc from SAP R/3,it is throwing an error"External segment name E2LFA1M001 cannot be interpreted"
    and "Basic type CREMAS03 does not exist" on XI side.
    Can anyone please provide a solution to this?

    HI Jagruthi,
    Have you loaded the metadata into the XI system by using IDX2?
    If it is done then try to delete once and do once again.
    And also delete the IDoc from IR and reimport the IDoc and activate it once again.
    Regards
    Goli Sridhar

  • During SAP outages,XI unable to send the IDoc to SAP System.

    Hi
    We have an interface in XI which posts IDoc to SAP .
    In the inbound side XI polls the database and executes a query.
    But during SAP outages ( Planned/unplanned) though XI executes SQL and process the messages successfully the message fails in the outbound side as SAP is not available.( Column 'c' will be marked with red flag)
    Is there any way we can queue up the messages till SAP is available and post the IDocs.
    Presently we have to either resend the message from the source system or using
    Run time workbench and payload post the IDoc manually.
    I guess there could be some settings in the J2EE stack if done can help with.
    My environment is XI 3.0 SP14.
    Please suggest a feasible solutions.
    Thanks in advance,
    KP

    Hi,
    if the quality of service is EO then your idoc is stuck in sm58 and you can force the idoc to be delivered once SAP will come back available.
    You can schedule the report RSARFCEX that does exactly this task.
    Normally this job is scheduled to run every 5 minutes.
    This should solve your problem.
    Btw, I suggest you to additionally have a look at this blog <a href="/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically">XI : How to Re-Process failed XI Messages Automatically</a>.
    Best Regards,
    Sergio

  • Error- Unable to lookup in the system.

    Dear All,
    For my backend server I have created system object on portal.
    Then I have made 1 transaction iview for the same system object.
    In the preview of the iview it is showing me correct screen and its operations are also fine.
    But when I am attaching that iview to ane role and attaching that role to any user and viewing that iview thru tht users login it is giving me an error 
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : N/A
    Component Name : N/A
    Unable to lookup System 'TEST'. Please check the system object and the alias..
    See the details for the exception ID in the log file
    Can anyone guide me in the above issue ?
    Regards,
    Aditya

    Hi All,
    While checking the permissions under SAP Authorizations it is giving me an error
    classcom.sapportals.connector.connection.ConnectionFailed ExceptionConnection Failed: Nested Exception. Failed to get connection.
    I have check all the parameters under connector property also
    they are fine.
    One more thing if this role I attched to administrator account it is working properly.But for normal user it is giving the run time error as mentioned above.
    Please anyone help me out in this situation.
    Regards,
    Aditya

  • 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

  • File to Idoc -- Unable to interpret IDoc interface mi_Orders05_In_Asyn..??

    Hi All,
    Im trying the File to Idoc scenario.. and im getting the following error in SXMB_MONI,
    Anyidea what might have gone wrong??
    <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
      <SAP:P1>mi_Orders05_In_Asyn</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      +<SAP:Stack>Unable to interpret IDoc interface mi_Orders05_In_Asyn</SAP:Stack>+
      <SAP:Retry>M</SAP:Retry>
    Waiting for your answers.
    Thank You.
    Seema.

    Hi Seema,
    I think you are using mi_Orders05_In_Asyn as the IDOC interface.
    Use the imported idoc as the interface. i.e you dont need to create Inbound Message interface for IDOC. You can use the imported idoc structure as interface.
    Let us know if that doesnt solve your problem.
    Regards,
    Sumit

  • Unable to interpret IDoc interface ReplenishmentOrderNotification_In

    Hi All,
    I am trsfering orders03 idoc from r/3 4.5 B system to XI and from XI to SNC system using idoc adapter.
    In sxmb_moni, When I double click on particular XML message with errors
    I am getting error in call adapter
    details:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
      <SAP:P1>ReplenishmentOrderNotification_In</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to interpret IDoc interface ReplenishmentOrderNotification_In</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

    Hi
    I am creating JDBC to IDOC scenario but experiencing the same issue.
    Can you advise how you solved this?
    Thanks.

  • Unable to interpret IDoc interface  Error

    Hi All,
    We are getting the following error while trying to translate a X12 to IDOC , we are using Seeburger Adapters for the translation.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
      <SAP:P1>I_867_ORDERS01_ZORDRS1X_PTD_SS</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Unable to interpret IDoc interface I_867_ORDERS01_ZORDRS1X_PTD_SS</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    The Reason we are using a Interface rather than using a IDOC directly is because our the IDOC Structure is 867.ORDERS01.ZORDRS1x and this is a custom IDOC in ECC and when we try to directly use the structure in the Interface Determination we get the error
    Check Result for Object ARROWUS | ARROWUS_IN_AS2 | A_867_V4010_ABS | | BS_ECC_D03_DEV
    First character invalid: 8 Only a(A)-z(Z), 0-9, and "/" and "_" are permitted
    Has anyone faced a similar problem ? If so please let me know how you fixed it.
    Appreciate your help
    Regards,
    Madhu

    have you seend below threads:
    [link1|Unable to interpret IDoc interface ZSHIPDEL_packageRD;
    [link2|IDOC Error;

  • Unable to interpret IDoc interface ZSHIPDEL_packageRD

    Hi,
    I am doing a file-xi-idoc scenerio.
    I've exported my custom idoc as an xsd and modified the schema to allow for multiple idocs to be generated for each file - as per note 814393.
    However I get the following error message at runtime (Call Adapter):
    <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
      <SAP:P1>ZSHIPDEL_packageRD</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to interpret IDoc interface ZSHIPDEL_packageRD</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
    Has anyone else experienced this error?
    Regards
    leenor

    I have a scenario exactly like the above one.
    My file structure is like
    TransactionDetailList
             TransactionDetail (1:N)
                    Transaction_Type (0:1)
                    Transaction_Date (0:1)
                    Add_Revise_Cancel_USER_ID (0:1)
                    Add_Revise_Cancel_Date_Time (0:1)
    My IDOC has the below structure,
    ZIDOC_BDS_DIVERSION
                       IDOC
                          ZSEGL_DIVERSION_HEADER
                                           SEGMENT
                                           NOMNR
                                           NOMIT
                                           EVENT_DATE
                                  ZSEGL_ DIVERSION_ITEM
                                            SEGMENT
                                            WHO_PAYS_DIVERSI
                                            LOCID
                                            DEST_CITY
    so i have to generate multiple idocs in the target side.
    I have created external defination based on my IDOC.Defined mapping between File and the external defination crerated from the IDOC. also defiined interface mapping between file and external defination.
    In the Integration Directory ->Interface Defination, I have used the actual Idoc as Inbound interface for which there is no mapping as we have not defined anything for this. This is exactly what you have defined above.
    I am getting the following errors like,
    "Error: MSGGUID A5EE4A305B4111DABFBE0002551F08EE: Tag TransactionDetailList found instead of tag IDOC BEGIN="
    Please let me know if I am missing some steps while configuring or I have to do something else.
    Thanks & Regards,
    Mukesh

  • Unable to lookup the Deploy Service. java.lang.ClassCastException in NWDS

    Hi All,
    I am getting the following exception while deploying an application in NWDS.
    Please help me in resolving this issue
    Sep 6, 2007 10:24:32 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [001]Deployment aborted
    Settings
    SDM host : bala
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/BALU/LOCALS1/Temp/temp64339RFCFlightList.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/BALU/LOCALS1/Temp/temp64339RFCFlightList.ear
    Aborted: development component 'RFCFlightList'/'local'/'LOKAL'/'0.2007.09.06.22.24.23'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy API:
    com.sap.engine.deploy.manager.DeployManagerException: Unable to lookup the Deploy Service. java.lang.ClassCastException
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
    Deployment exception : The deployment of at least one item aborted

    Hi Bala
    Some of the services at your server are not running..ask your system admin to restart the SDN server and try to deploy once
    Regards
    Chaitanya.A

  • Unable to lookup System object and the alias..

    Hello All,
    I am implementing the Business Package for CRM.
    I have created the SAP_CRM and SAP_BW systems and assigned them the same aliases as mentioned in the instructions in http://help.sap.com/saphelp_crm40/helpdata/en/11/0584016208bc4988c3791d6213b6d0/content.htm
    I have tested the connections to the WAS, as well as ITS server after configuring them from the portal system administration.
    However, I get the exception.
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : N/A
    Component Name : N/A
    Unable to lookup System 'SAP_CRM'. Please check the system object and the alias..
    The error in the log is as follows:
    #1.5#00112FCBC32C005E000000A9000007EC000412303370C08B#1145898137593#com.sap.portal.sapapplication#sap.com/irj#com.sap.portal.sapapplication#user1#95##LABNW_J2E_19311950#user1#15374a50d3b411da8f1e00112fcbc32c#SAPEngine_Application_Thread[impl:3]_36##0#0#Error#1#/System/Server#Plain###ApplicationIntegratorException: com.sapportals.portal.appintegrator.ApplicationIntegratorException: Unable to lookup System &\#39;SAP_CRM&\#39;.
    Please check the system object and the alias.com.sapportals.portal.appintegrator.ApplicationIntegratorException: Unable to lookup System &\#39;SAP_CRM&\#39;.
    Please check the system object and the alias.
         at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.getSystemLogonMethod(SingleSignOnLayer.java:243)
         at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:55)
         at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:173)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:71)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
         at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
         at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
         at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:800)
    Any hints recommendations for the same.
    Thank You.
    Sumit.

    Hi Sumit,
    System is an object in Portal Content Directory (PCD). User of portal should have permissions to access it. Looking up is a kind of access.
    Please go to System Administration -> System Configuration -> System Landscape. Find your system and right-click on it, then choose 'Permissions'. There you should make sure that your portal user has permissions.
    You can read about permissions here:<a href="http://help.sap.com/saphelp_nw04/helpdata/en/f6/2604e505fd11d7b84200047582c9f7/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/f6/2604e505fd11d7b84200047582c9f7/frameset.htm</a>
    There is an extract probably related to your problem:
    " If an iView is based on a system object defined in your system landscape (see System Landscape), you must assign end user permission for the relevant user, group, or role to the system object, as well. End user permission assigned to a system permits the iView to retrieve data from the respective back-end application through the system object at runtime."
    Regards,
    Sergei
    Message was edited by: Sergei Dneprov

  • Unable to lookup home: Path to object does not exist at : java:comp#

    Hallo,
    I do not understand why I am getting the exception:
    Unable to lookup home: Path to object does not exist at : java:comp#
    if i have defined in the ejb-j2ee-engine.xml the jndi name:
    <enterprise-beans>
         <enterprise-bean>
              <ejb-name>MyConverterBean</ejb-name>
              <jndi-name>MyConverterBean</jndi-name>
              <session-props/>
         </enterprise-bean>
    </enterprise-beans>
    and in the ejb-jar.xml :
    <enterprise-beans>
       <session>
          <description>the converter bean</description>
          <display-name>MyConverter</display-name>
          <ejb-name>MyConverterBean</ejb-name>
          <home>converter.MyConverterHome</home>
          <remote>converter.MyConverter</remote>
          <local-home>converter.MyConverterLocalHome</local-home>
          <local>converter.MyConverterLocal</local>
          <ejb-class>converter.MyConverterBean</ejb-class>
          <session-type>Stateless</session-type>
          <transaction-type>Container</transaction-type>
        </session>
    </enterprise-beans>
    I am creating the EJB in this way:
    ic = new InitialContext();
    objRef = ic.lookup("java:comp/env/ejb/MyConverter");
    home = (MyConverterHome)PortableRemoteObject.narrow(objRef, MyConverterHome.class);
    converter = home.create();
    I checked in the Administrator tool under JDNI / ejbContext and I can see MyConverterBean in the list.
    Do you have any idea what I am doing wrong?
    thanks a lot for your help,
    SAPLernen

    Hi Vladimir,
    do you have some example or tutorial of how can i implement java proxies from a java stand alone application.
    i allready make everyting but i'm still having problem.
    this line give me a null
    queryOutLocalHome = (UsersSyncMI_PortTypeLocalHome)ctx.lookup("java:comp/env/ejb/UsersSyncMI_PortTypeBean");
    this is my java class that invoke my ejb java proxy
    package com.gsk.xi.demo;
    import java.util.Properties;
    import javax.naming.Context;
    import javax.naming.InitialContext;
    import com.sap.aii.proxy.xiruntime.core.MessageSpecifier;
    public class InvokeProxy {
         private Object objRef = null;
         private InitialContext ic = null;
         public String getRole(String name, String pwd){
              String role="0";
              UsersSyncMI_PortTypeLocalHome queryOutLocalHome=null;
              UsersSyncMI_PortTypeLocal queryOutLocal=null;
              try{
                   Context ctx = null;
                   Object ref = null;
                   Properties p = new Properties();
                   p.put(Context.INITIAL_CONTEXT_FACTORY,"com.sap.engine.services.jndi.InitialContextFactoryImpl");
                   p.put(Context.PROVIDER_URL, "buasapp012.gwamericas.corpnet1.com:50004");
                   p.put(Context.SECURITY_PRINCIPAL, "J2EE_ADMIN");
                   p.put(Context.SECURITY_CREDENTIALS, "was1234");
                   ctx = new InitialContext();
                   //objRef = ic.lookup("java:comp/env/ejb/UsersSyncMI_PortTypeBean");
                   //queryOutLocalHome = (UsersSyncMI_PortTypeLocalHome)PortableRemoteObject.narrow(objRef, UsersSyncMI_PortTypeLocalHome.class);     
                   queryOutLocalHome = (UsersSyncMI_PortTypeLocalHome)ctx.lookup("java:comp/env/ejb/UsersSyncMI_PortTypeBean");
                   queryOutLocal = queryOutLocalHome.create();
                   MessageSpecifier msg = queryOutLocal.$messageSpecifier();
                   msg.setSenderService("JAVA");
                   queryOutLocal.$messageSpecifier(msg);
                   UserDT_Type reqtype = new UserDT_Type();
                   reqtype.setUsername(name);
                   reqtype.setPassword(pwd);
                   UsersDBMTResponse_Type response = new UsersDBMTResponse_Type();
                   response = queryOutLocal.usersSyncMI(reqtype);
                   role = role + response.getStatementResponse().getRow().getRole();
              catch(Exception ex){
                   System.out.println(ex.getMessage());
              return role;
    } //end of class
    thanks for your time
    Lionel

Maybe you are looking for