Unable to create IDocs

I have downloaded Idoc(Already existing in the system with status 53) data using FM IDOC_READ_COMPLETELY(by passing an Idoc number) and passing this downloaded data to FM MASTER_IDOC_DISTRIBUTE to create new Idoc with same data.
Idoc does gets created but with status 29(Partner profile missing). I am not able to figure out what is going wrong because Idoc already exists in the system with same data so how can the new Idoc with same data have this issue?
Also I tried to maintain the partner profile data( that i got as warning message in Long text after the creation of Idoc) but still it did not help.

Hi Nabheet,
Simply created a report where one FM gets data and using same data I try to create Idoc.
Even this fails to get the Idoc into correct status:
CALL FUNCTION 'IDOC_READ_COMPLETELY'
  EXPORTING
    document_number          = 0000000041115636
  IMPORTING
    idoc_control           = e_edidc
  TABLES
    int_edids                = ts_edids
    int_edidd                = ts_edidd
  EXCEPTIONS
    document_not_exist           = 1
    document_number_invalid  = 2
    OTHERS                              = 3.
IF sy-subrc <> 0.
ENDIF.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
  EXPORTING
    master_idoc_control                  = e_edidc
  TABLES
    communication_idoc_control     = ts_edidc
    master_idoc_data                      = ts_edidd
  EXCEPTIONS
    error_in_idoc_control                      = 1
    error_writing_idoc_status               = 2
    error_in_idoc_data                          = 3
    sending_logical_system_unknown = 4
    OTHERS                                           = 5.
IF sy-subrc EQ 0.
ENDIF.

Similar Messages

  • 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

  • Unable to create Business Partner in CRM

    Hi I am unable to Create a Business Partner (BP)in CRM though I could  see that the INBOUND  IDOC ( Msg type : CRMXIF_PARTNER_SAVE_M ) is getting posted.I created the IDOC through the test transaction (we19).Also i dont have any data to give in the field PARTNER_GUID without which the IDOC was failing.So i took an existing value from the table BUT000 and used it and it posted successfully but still the BP is not getting created in the system.Request you to pls suggest a solution..

    Kanth,
    You dont have to populate BP IDOC with partner guid.System generates partner GUID whenever BP is created.
    Try to create a BP without populating guid.
    Thanks,
    Thirumala.

  • 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

  • FTP error-Unable to create new pooled resource: com.sap.aii.adapter.file.ft

    Hi,
    We have a scenario where XI receives a Idoc and based on the contents of Idoc, It will generate 5 different files and send it to the external FTP server.We configured 5 receiver channels for these 5 files.
    When this interface runs, most of the files will be delivered but some of the messages will be errored out.
    The receiver channel has shown the following error-
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error when getting an FTP connection from connection pool: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: com.sap.aii.adapter.file.ftp.FTPEx
    I tried to resend them by temperorily stopping other channels to reduce connections to this FTP server.But these messages again resulted with same error.
    Can someone suggest what might be the cause for this error.
    Thanks in advance.

    Hi ,
    As I am not sure about the problem so U just try all of the option I am writing below. It may help u as these are the probable solutions for this problem.
    1.perform Full CPA cache refresh using PIDIRUSER
    2.The problem seems to be in establishing the connection with the File server . This could be due to
    a. Wrong user name or password in receiver adapter .
    b. Firewall connection are not open
    actually you are saying that some files are being delivered so all the file has to be deliverd on same server on diffrent directory or all files are going on diffrent server at present I am assuming that all files are going on diffrent server so please check UID & PWD properly.if they are on same server but diff. directory it can be easily done using one Communication channel only.
    3. Finally please check the errorneous communication channel .
    to check your communication channels are working fine or not you can check in channel monitoring in PI7.0, adapter monitoring in Xi3.0.
    if you are on PI7.0, goto RWBCache monitoring select AE and cilck disply-select the date todays--check everything is greent here
    4.Please check your maximal connection pool .
    Regards,
    Saurabh

  • Exception caught by adapter framework: unable to create a socket

    Hi All,
          I am using Idoc to XI To SOAP scinario. I got a alert asying that some messsage id is error. When i am trying to monitor that massage by taking help of the messgae id in the alert the message was successful in the SXMB_MONI,. Then i Went to message monitoring There the message statu was syetem error. Errror log is *Exception caught by adapter framework: unable to create a socket*. The communication channel was inactive wehere as the statsu of the channel was active in the directory... what is the reasonm for this error. and how to resilev this.

    As pointed already, a socket exception occurs when then message cannot pass the Firewall settings....there will be a port configured to send message to the SOAP receiver.....ask network guys to make relevant settings so that the port is free from Firewall restrictions.
    @Supriya --> Active/ Inactive status of the channel in ID and in CC monitoring are different things.
    To change the status of your CC in RWB --> Stop & Start your SOAP CC....the channel will remain inactive till no message is passed through it....once a message is passed the status will change to success/ error.
    You can also change the CC status to Automatic.
    Regards,
    Abhishek.

  • 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 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 interpret IDoc interface

    Hi,
    I have a File to multiple IDOC scenario. I have change the IDOC occurance by creating ED.
    I have developed everything but the following error is coming during my end to end testing.
    Unable to interpret IDoc interface
    Thanks,
    Raj

    Raj Says..
    I have change the IDOC occurance by creating ED.
    Hi Raj,
    Since you have changed the IDOC occurrences by creating an ED so you have to make sure that IDOC and ED has been used properly in your scenario.
    1. MM = use ED
    2. IM = use original IDOC
    3. ID = use original IDOC
    Regards,
    Madan Agrawal

  • Unable to create communication channel - RFC

    Hi ,
    I am trying to create communication channel automatically , when adding business systems from SLD to integration repository. I get the following error only for RFC
    all other communication channel gets generated correctly.. Is there any thing i am missing.
    HTTP communication channel GeneratedReceiverChannel_HTTP created
    IDoc communication channel GeneratedReceiverChannel_IDoc created
    XI communication channel GeneratedReceiverChannel_XI created
    Unable to create communication channel: Unable to generate the communication channel (NWR_107, GeneratedReceiverChannel_RFC): com.sap.aii.utilxi.misc.api.ClientServerException
    Thanks,
    Ganesh Ram

    Please run transaction SLDCHECK. The connection to SLD might not be working properly.
    Plus, in the business system you created, check if client number and all other parameters associated with SAP systems are valid.
    Dmitriy

  • Problem in creating idocs

    hi,
    While creating idocs I created logical system using SPRO,then created RFC then Port but when i am creating partner profiles I am unable to get the destination system which I have created.Could any one guide me.

    Hi,
    below is scenario for ALE/IDOC.
    ALE-IDOC Scenario using Custom IDOC
    Aim: Transfer the data from one system to another using user customized IDOC.
    Sender System: 
    Server: 172.25.8.185
    Client: 200
    Data from Z table: zsach1 
    ReceiverSystem:
    Server: 172.25.9.198
    Client: 800
    Data from Z table: zsach1 
    Data is fetched from Z table on the sender system and inserted it in the Z table of Receiver system using ALE/IDOC. 
    Settings on the Sender End 
    Table Creation T – Code SE11. The table contains data that is to be sent to Receiver. 
    ALE Configuration 
    T-Code – SALE 
    Defining Logical System 
    200 is our sender
    800 is our receiver 
    Assigning Client to Logical System 
    200 is our sender
    800 is our receiver 
    Defining Target System for RFC Calls (Tcode – SM59)
    Click on R/3 Connections and then Create TAB 
    Step 1 
    Step 2 
    Save and test the connection. 
    Defining Port 
    The sender system is connected to the receiver system through this Port.
    Defining Partner Profiles 
    The partner for client 200(Sender) is the client 800 (Receiver) 
    Since this is a sender we have to define only Outbound Parameters in this case.
    Here you can see the Message type is Z message type.  
    2.                   Maintaining Distribution Model ( TCode BD64 ) 
    Create new Distribution Model 
    Add Message Type 
    Now Distribute this Model View  
    Distribute it from Edit à Model View à Distribute
    Defining the Z Segment type
    Tcode – WE31 
    Defining the Basic Type
    T Code WE30 
    Click on New 
    This will take you to next screen as follows 
    Here you have connected the basic type to the segment type.
    Enter again and this will take you to screen as follows  
    This shows the relation between the basic and the segment types. 
    Next you need to make the entry of the segment in the system table.
    Tcode : WE81 
    Next is the following entry which is required. 
    Here you are specifying the message type and the basic type and the release version. 
    This is all about the configuration you need to do on the sender side.
    Now on the sender side you also need a program that will fetch the required data, couple it in the IDOC format and post it. 
    Here is a small piece of code that could be useful.
    *& Report  ZSACH_CUST_IDOC                                             *
    *report  zsach_cust_idoc                         .
    parameters :            p_logsys like tbdlst-logsys.data : gen_segment like edidd-segnam value 'ZSACH'.data : control_dat like edidc,
          gen_data like z1hdr .tables :zsach1.data: begin of inttab occurs 0,
            lname type z1hdr-lname,
            fname type z1hdr-fname,
          end of inttab.
    data :
          int_edidd like edidd occurs 0 with header line,
          int_edidc like edidc occurs 0 with header line.
    select * from zsach1 into corresponding fields of table inttab.if sy-subrc ne 0.
      message 'no data' type 'I'.
      exit.
    endif.control_dat-mestyp = 'ZSACH'.
    control_dat-idoctp = 'ZSACH'.
    control_dat-rcvprt = 'LS'.
    control_dat-rcvprn =  p_logsys.
    loop at inttab.
      gen_data-lname = inttab-lname.
      gen_data-fname = inttab-fname.
    GEN_DATA-SSN = INTTAB-SSN.
    GEN_DATA-DOB = INTTAB-DOB.  int_edidd-segnam = gen_segment.
      int_edidd-sdata = gen_data.  append int_edidd.
    endloop.call function 'MASTER_IDOC_DISTRIBUTE'
      exporting
        master_idoc_control                  = control_dat
      OBJ_TYPE                             = ''
      CHNUM                                = ''
      tables
        communication_idoc_control           = int_edidc
        master_idoc_data                     = int_edidd exceptions
       error_in_idoc_control                = 1
       error_writing_idoc_status            = 2
       error_in_idoc_data                   = 3
       sending_logical_system_unknown       = 4
       others                               = 5
    if sy-subrc <> 0.
      message id sy-msgid type sy-msgty number sy-msgno.
    else.  loop at int_edidc.
        write :/ 'IDOC GENERATED',int_edidc-docnum.
      endloop.
      commit work.
    endif.
    Settings on the receiver side. 
    The ALE configuration is same as we did it on the sender side. Please refer to earlier pages. 
    The receiver specific differences are mentioned below. 
    T-Code – SALE 
    200 is our sender
    800 is our receiver 
    Steps  
    Defining Logical System (Same as sender)
    Assigning Client to Logical System (Same as sender)
    Defining Target System for RFC Calls (Tcode – SM59) (Same as sender)
    Defining Port(Same as sender) 
    Defining Partner Profiles – Here we are accepting the data from Sender system. Hence we need to configure it as Inbound. 
    Click on the   sign above to go to next screen. 
    Here the message type is to be created again as it was created on the sender side.
    The following steps are repeated, as done on the sender side, on the receiver end 
    Tcode WE30
    Tcode WE31
    Tcode WE82
    Tcode WE81
    Here on the receiver end, we need to specify a process code at the time of defining the partner profile.
    Process code is something that has the logic defined about what to be done after receiving the IDOC. 
    In our case, on receipt of the IDOC, we are updating the Z Table. i.e Inserting the data from the IDOC into the Z Table. 
    Creating a Process Code
    Tcode – WE42  
    The logic associated is coded in the Function Module which is specified in the Identification Field above. 
    Also the processing type is selected as Processing by Function Module as above. 
    The function Module is specified in the following screen. 
    To have your function Module in the above drop down list, the entry is to be made using the following transaction 
    TCode – BD51 
    Once the entry is done here, the function module appears in the drop down list in the previous stage.
    Also it is important to make the following entry
    Tcode WE57 
    Function Module will look something as below: 
    Source Codefunction z_idoc_input_sach .
    ""Local interface:
    *"  IMPORTING
    *"     VALUE(INPUT_METHOD) LIKE  BDWFAP_PAR-INPUTMETHD
    *"     VALUE(MASS_PROCESSING) LIKE  BDWFAP_PAR-MASS_PROC
    *"     VALUE(NO_APPLICATION_LOG) LIKE  SY-DATAR OPTIONAL
    *"     VALUE(MASSSAVEINFOS) LIKE  MASSSAVINF STRUCTURE  MASSSAVINF
    *"       OPTIONAL
    *"  EXPORTING
    *"     VALUE(WORKFLOW_RESULT) LIKE  BDWF_PARAM-RESULT
    *"     VALUE(APPLICATION_VARIABLE) LIKE  BDWF_PARAM-APPL_VAR
    *"     VALUE(IN_UPDATE_TASK) LIKE  BDWFAP_PAR-UPDATETASK
    *"     VALUE(CALL_TRANSACTION_DONE) LIKE  BDWFAP_PAR-CALLTRANS
    *"  TABLES
    *"      IDOC_CONTRL STRUCTURE  EDIDC
    *"      IDOC_DATA STRUCTURE  EDIDD
    *"      IDOC_STATUS STRUCTURE  BDIDOCSTAT
    *"      RETURN_VARIABLES STRUCTURE  BDWFRETVAR
    *"      SERIALIZATION_INFO STRUCTURE  BDI_SER
    *"  EXCEPTIONS
    *"      WRONG_FUNCTION_CALLED
      include mbdconwf.
      data : it_emp_data like zsach1 occurs 0 with header line.
      data : gen_data like zsach1 .
      workflow_result = c_wf_result_ok.
    data : counter type int4.select count( * ) from zsach1 into counter.
    counter = counter + 1.  loop at idoc_contrl.    if idoc_contrl-mestyp ne 'ZSACH'.
          raise wrong_function_called.
        endif.    clear gen_data.
        refresh it_emp_data.    loop at idoc_data where docnum eq idoc_contrl-docnum.      if idoc_data-segnam = 'ZSACH'.        gen_data = idoc_data-sdata.          it_emp_data-mandt = counter.
              it_emp_data-lname = gen_data-lname.
              it_emp_data-fname = gen_data-fname.          counter = counter + 1.        append it_emp_data.
          else.
            message 'ERROR' type 'I'.
          endif.    endloop.  endloop.insert zsach1 from table it_emp_data.
    call function 'EDI_DOCUMENT_OPEN_FOR_EDIT'
      exporting
        document_number               = idoc_data-docnum
      importing
        idoc_control                  = idoc_contrl
      tables
        idoc_data                     = idoc_data
      exceptions
        document_foreign_lock         = 1
        document_not_exist            = 2
        document_not_open             = 3
        status_is_unable_for_changing = 4
        others                        = 5.call function 'EDI_CHANGE_DATA_SEGMENTS'
      tables
        idoc_changed_data_range = idoc_data
      exceptions
        idoc_not_open           = 1
        data_record_not_exist   = 2
        others                  = 3.
    data t_itab_edids40 like edi_ds40 occurs 0 with header line.clear t_itab_edids40.
    t_itab_edids40-docnum      = idoc_data-docnum.
    t_itab_edids40-status      = '51'.
    t_itab_edids40-repid       = sy-repid.
    t_itab_edids40-tabnam      = 'EDI_DS'.
    t_itab_edids40-mandt       = sy-mandt.
    t_itab_edids40-stamqu      = 'SAP'.
    t_itab_edids40-stamid      = 'B1'.
    t_itab_edids40-stamno      = '999'.
    t_itab_edids40-stapa1      = 'Sold to changed to '.
    *t_itab_edids40-stapa2      = t_new_kunnr.
    t_itab_edids40-logdat      = sy-datum.
    t_itab_edids40-logtim      = sy-uzeit.append t_itab_edids40.call function 'EDI_DOCUMENT_CLOSE_EDIT'
      exporting
        document_number  = idoc_data-docnum
        do_commit        = 'X'
        do_update        = 'X'
        write_all_status = 'X'
      tables
        status_records   = t_itab_edids40
      exceptions
        idoc_not_open    = 1
        db_error         = 2
        others           = 3.endfunction.
    Running the Application 
    Sender system
    Execute the program we created earlier 
    Checking the IDOC 
    T Code WE02 
    Checking the data on the Receiver end 
    Tcode: WE02 
    The IDOC has arrived here 
    Checking the Data  
    Double click on the IDOC  
    Checking the Database 
    This way, the data has come to the receiver end successfully. 
    REWARD IF HELPFULL.

  • Help! MBeanCreationException: Unable to create bean...missing create method

    I am trying to configure an authentication provider with ant using the wlconfig task. This has been working fine until recently and I have no idea what could be wrong. The ant script has not changed and I'm not sure what information to post to be more useful. Hopefully someone has had this problem or can point me in the right direction.
    Below is the target I'm trying to run. I fails with the following exception. I am able to configure the provider manually through the console, however, but this is not an option for our deployments:
    Caused by: weblogic.management.MBeanCreationException: Unable to create new bean of type com.xxx.MyAuthenticator for myDomain:Name=myDomain,Type=Domain:missing create method
    Caused by: java.lang.NoSuchMethodException: MyAuthenticator(java.lang.String,)
         <target name="configure-auth-provider">
              <echo message="Configuring Security Auth Provider..."/>
              <taskdef name="wlconfig" classname="weblogic.ant.taskdefs.management.WLConfig" classpath="${weblogic.jar}"/>
              <wlconfig url="t3://${weblogic.host}:${weblogic.listen.port}" username="${weblogic.username}" password="${weblogic.password}">
                   <create type="com.xxx.MyAuthenticator" domain="Security" name="MyAuthenticator" property="MyAuthenticator">
                        <set attribute="ControlFlag" value="OPTIONAL"/>
                   </create>
                   <query type="weblogic.management.security.Realm" domain="Security" name="MyCustomRealm">
                        <set attribute="AuthenticationProviders" value="MyAuthenticator"/>
                   </query>
              </wlconfig>
              <echo message="Security Auth Provider configured Successfully."/>
         </target>

    Hi Balaji,
    LSMW using IDOC is similar to using flat file method. Here you are getting data from IDOC container and mapping data with Idoc segments insted of flatfile column.
    Hope this is what you are looking for. If helpful then don’t forget to reward me for that
    Darshan

  • Unable to Load Database/Unable to create database.

    RoboHelp 6.0 on my PC is suddenly unable to open existing
    projects or create new ones. The problem is not in the projects, as
    other people can unzip the same set of files and open them with
    RoboHelp on their PCs.
    The Details:
    When attempting to open an existing project (any project
    whether in version control or not), I get the message " Open
    project was cancelled or the application was unable to load
    database for..."
    I found the article that says to delete the CPD and XPJ files
    and then to use the Edit option to open the HHP file so that
    RoboHelp will recreate the two files. When I try that, I get the
    message "Unable to create database. Check that the directory is not
    read-only." It's
    not read-only.
    When I attempt to create a new project, the application acts
    like it is going to create one, but it just creates a project
    folder without the new first topic and then repeats the New Project
    Wizard window that prompts for title, etc. It will keep creating
    folders and returning to this window in a loop without ever really
    creating a project.
    RoboSource Control is functioning normally, by the way.
    I have uninstalled and reinstalled RH 6 several times, and
    have even uninstalled RH 6 and installed to RH 5 just to see if it
    could open projects, which it does with no problems. After that
    test, I uninstalled RH 5 and reinstalled RH 6, only to encounter
    the same problem all over again.
    This started happening after I uninstalled other unrelated
    software and received a message that some Service Pack 2 files had
    been changed and prompting me to insert the Service Pack 2 CD,
    which I don't have. This is because our IT department pre-builds
    our systems from an image and then distributes job-specific
    applications over the network. IT tried repairing Service Pack 2,
    but that didn't work. I'd like to uninstall and reinstall Service
    Pack 2, but the IT person says it's too risky on a system that was
    built from an image.
    We would like to find out
    which files RoboHelp is looking for when it launches a
    project so we can replace those files manually. Does anyone
    know what they are or have another suggestion that might fix the
    problem?
    Otherwise, I am stuck having to allow IT to rebuild my
    system. That means reinstalling and reconfiguring everything on it,
    just as if I were upgrading to a new PC. This can take a whole work
    week. However, I have already spent close to a work week on this
    problem, so maybe rebuilding would save time in the long
    run.

    Problem Resolution = HHA.dll
    For anyone who might be interested in the resolution to this
    issue, we did rebuild my PC and reinstall all of my software. The
    RoboHelp installation "complained" that I did not have HTML Help
    Workshop on my system and told me to download version 1.4 from
    Microsoft. I did have HTML Help Workshop..it's in my programs list.
    (It's not listed in programs on my co-workers' PCs, and they were
    not having problems, by the way.) But to make RH happy, I
    uninstalled the workshop and tried to install the version from
    Microsoft. But a message informed me that I already had a newer
    version of the workshop on my system, and I was back where I
    started. I could open projects, but there were weird problems.
    Selecting Topic Properties was met with an error message, and when
    the properties window opened, I could only see whatever template
    was assigned (or none if the topic had lost its template), and
    there was an extra section for Oracle help.
    So I started dinking around in the registry to see if I could
    get rid of any traces of the workshop so I could install the
    version RH wanted or to find any other clues to my problem. Under
    HTMLHelpAuthor, there was a reference to an HHA.dll file located in
    C:\WINDOWS\system32...only the file did not exist on my system.
    (Remember that my original problem was that some Service Pack 2
    files were either modified or missing.) So I did a Google search on
    that file name and found out that HTML Help Workshop is included in
    newer Windows operating systems, but that people used to have to
    get HTML Help Workshop from Microsoft, and that some people had
    made the mistake of just putting the HHA.dll file into the
    C:WINDOWS\system32 folder without also installing HTML Help
    Workshop. At this point it was obvious that I needed the HHA.dll,
    so I got it from a co-worker's PC. (Looking at the registry
    entries, I can also see that my system was built with a slightly
    different version of the operating system than my co-workers have.)
    Adding the HHA file to my system solved the problem. All
    projects but one were fine; one was still exhibiting the strange
    behavior. I fixed it by going back to the RoboHelp 5 version of the
    project and re-converting it to RoboHelp 6.
    I suspect that if I had known about the HHA.dll file before
    we rebuilt the PC, I could have solved the problem without going
    through that painful process. That is why I thought I should post
    the solution even though it was after the rebuild.

  • Unable to create a report in bi publisher 10g

    Hi All,
    Unable to create a report in bi publisher. When we tried to create a report abcd, then it is giving the below error.
    Operation failed: /abcd/abcd.xdo.
    When we tried to create a report with the existing name, it is saying
    An object with the same name already exists: /crm/crm.xdo
    I can say this is not any permissions problem, I have logged inwith Administrator user.
    Thanks

    Hi,
    Can any one..???

  • Unable to create report. Query produced too many results

    Hi All,
    Does someone knows how to avoid the message "Unable to create report. Query produced too many results" in Grid Report Type in PerformancePoint 2010. When the mdx query returns large amount of data, this message appears. Is there a way to get all
    the large amount in the grid anyway?
    I have set the data Source query time-out under Central Administration - Manager Service applications - PerformancePoint Service Application - PerformancePoint Service Application Settings at 3600 seconds.
    Here Event Viewer log error at the server:
    1. An exception occurred while running a report.  The following details may help you to diagnose the problem:
    Error Message: Unable to create report. Query produced too many results.
            <br>
            <br>
            Contact the administrator for more details.
    Dashboard Name:
    Dashboard Item name:
    Report Location: {3592a959-7c50-0d1d-9185-361d2bd5428b}
    Request Duration: 6,220.93 ms
    User: INTRANET\spsdshadmin
    Parameters:
    Exception Message: Unable to create report. Query produced too many results.
    Inner Exception Message:
    Stack Trace:    at Microsoft.PerformancePoint.Scorecards.Server.PmServer.ExecuteAnalyticReportWithParameters(RepositoryLocation analyticReportViewLocation, BIDataContainer biDataContainer)
       at Microsoft.PerformancePoint.Analytics.ServerRendering.OLAPBase.OlapViewBaseControl.ExtractReportViewData()
       at Microsoft.PerformancePoint.Analytics.ServerRendering.OLAPBase.OlapViewBaseControl.CreateRenderedView(StringBuilder sd)
       at Microsoft.PerformancePoint.Scorecards.ServerRendering.NavigableControl.RenderControl(HtmlTextWriter writer)
    PerformancePoint Services error code 20604.
    2. Unable to create report. Query produced too many results.
    Microsoft.PerformancePoint.Scorecards.BpmException: Unable to create report. Query produced too many results.
       at Microsoft.PerformancePoint.Scorecards.Server.Analytics.AnalyticQueryManager.ExecuteReport(AnalyticReportState reportState, DataSource dataSource)
       at Microsoft.PerformancePoint.Scorecards.Server.PmServer.ExecuteAnalyticReportBase(RepositoryLocation analyticReportViewLocation, BIDataContainer biDataContainer, String formattingDimensionName)
       at Microsoft.PerformancePoint.Scorecards.Server.PmServer.ExecuteAnalyticReportWithParameters(RepositoryLocation analyticReportViewLocation, BIDataContainer biDataContainer)
    PerformancePoint Services error code 20605.
    Thanks in advance for your help.

    Hello,
    I would like you to try the following to adjust your readerquotas.
    Change the values of the parameters listed below to a larger value. We recommend that you double the value and then run the query to check whether the issue is resolved. To do this, follow these steps:
    On the SharePoint 2010 server, open the Web.config file. The file is located in the following folder:
    \Program Files\Microsoft Office Servers\14.0\Web Services\PpsMonitoringServer\
    Locate and change the the below values from 8192 to 16384.
    Open the Client.config file. The file is located in the following folder:
    \Program Files\Microsoft Office Servers\14.0\WebClients\PpsMonitoringServer\
    Locate and change the below values from 8192 to 16384.
    After you have made the changes, restart Internet Information Services (IIS) on the SharePoint 2010 server.
    <readerQuotas
    maxStringContentLength="2147483647"
    maxNameTableCharCount="2147483647"
    maxBytesPerRead="2147483647"
    maxArrayLength="2147483647"
                  maxDepth="2147483647"
    />
    Thanks
    Heidi Tr - MSFT
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Maybe you are looking for

  • Cancellation of Goods receipt (Partial Quantity)

    Dear Experts, One of my user creates sales order for 1363 Cartons and create Goods Receipt for the same. But he created outbound for 738 carton (actually received quantity)  and completed full process like PGI, Shipment & billing Documents with 738 c

  • Restore firmware on a Macbook Late 2008

    I bought this Macbook a month ago, and After last firmware and leopard update, once I re-started the computer I am unable to boot the OS. When trying to do a normal boot I just get a grey screen with the apple logo and the spinning wheel for around 3

  • Problem with ESM

    I have register database, but in ESM in the navigator window under Enterprice Domains>OracleDefaultDomain in Database tab is not possible choose User Authentication: Oracle Wallet(SSL) And Password in the popup list I use OID 10g, when I use OID 9.2

  • Adobe Presenter using pre-recorded video

    is there a way for adobe presenter 8 to take a pre-recorded video instead a webcam for video input? so i have a pre-recorded video file, and I can run it side by side with the slide, and program when the transition supposed to be, when the video and

  • Mobility Secure Mode

    Hello, We are working with WLC 5508 version 7.0.98.0 and we want to secure (encrypt) mobility messages between controllers but the command "config mobility secure-mode enable" apparently doesn't exist in this WLC version. Does anybody know how to con