SAPSQL_ARRAY_INSERT_DUPREC in tcide SU01

Hi Gurus,
Good day!
I would to seek your assistance how can deal with this ABAP dump issue "SAPSQL_ARRAY_INSERT_DUPREC". This error occured while creating a user via transaction SU01.
Do we need to apply OSS note in order to get rid of this error?
Please advise.
Appreciate your help.
Cheers,
Virgilio

Hi Virgilio Padios ,
Have you checked the ranges of numbers? It may be that the range is exhausted. Then the system tries to assign a number that has already been used (for this the DUPREC). If this is the case you should go through SNRO and change the object range.
Hope this information is help to you.
Regards,
José

Similar Messages

  • Getting "SAPSQL_ARRAY_INSERT_DUPREC" error while creating a new layout

    Hi,
    I deleted a layout from a level.  When I tried to create a new layout with the same technical name, I was getting a run time error.
    Name of the error : SAPSQL_ARRAY_INSERT_DUPREC
    Exception           : CX_SY_OPEN_SQL_DB
    I went to ST22 and analyzed the dump.  I found that the entries for the layout that I deleted were still present in the following 2 tables:
    1) UPP_PARAMT
    2) UPP_ELEMT
    My questions are:
    1) Is there any possibilities that I can retrive the layout that I deleted with the help of the entries present in the above tables?
    2) Can I remove the entries from these two tables so that I can create a new layout with the same technical name?
    Thanks,
    Seetharaman V

    Hi Matt
    Thanks for your comments.  I was getting this error while trying to save the new layout i created and not during the creatiion.
    Thanks,
    Seetha

  • SAPSQL_ARRAY_INSERT_DUPREC during saving of Process Chain

    Dear all,
    On saving, when adding a process to an existing Process Chain - like Rollup or Change Run - in our SCM 5.0 system, we receive a short dump 'SAPSQL_ARRAY_INSERT_DUPREC' (complete short dump at the end of the msg).
    A problem arose on the line 'insert rsbatchparallel from table g_t_batch_par.' of include 'LRSBATCHF01'.
    The version of this include is the same as all other systems in our environment.
    In the table 'rsbatchparallel' we don't find any entry that can cause a duplicate entry.
    We are really stuck with this issue - any help is highly appreciated!
    Best regards,
    Ingrid
    Complete short dump
    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
    Exception              CX_SY_OPEN_SQL_DB
    Date and Time          08.10.2007 16:56:50
    Short text
    The ABAP/4 Open SQL array insert results in duplicate database records.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLRSBATCH" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
    in
    procedure "SAVE_SETTINGS" "(FORM)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is 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.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"
    "SAPLRSBATCH" or "LRSBATCHF01"
    "SAVE_SETTINGS"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "SAVE_SETTINGS" "(FORM)", or its possible occurrence must be declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
    System environment
    SAP-Release 700
    Application server... "eccdb603"
    Network address...... "19.106.69.177"
    Operating system..... "AIX"
    Release.............. "5.3"
    Hardware type........ "00C485BD4C00"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "eccdb603"
    Database type..... "DB6"
    Database name..... "A8P"
    Database user ID.. "SAPA8P"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Mar 19 2007 20:40:49"
    create on........ "AIX 2 5 005DD9CD4C00"
    Database version. "DB6_81 "
    Patch level. 102
    Patch text.. " "
    Database............. "DB6 08.02., DB6 09."
    SAP database version. 700
    Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5"
    Memory consumption
    Roll.... 16192
    EM...... 25139088
    Heap.... 0
    Page.... 212992
    MM Used. 16132952
    MM Free. 4812888
    User and Transaction
    Client.............. 510
    User................ "IERNAELS"
    Language key........ "E"
    Transaction......... "RSPC "
    Transactions ID..... " "
    Program............. "SAPLRSBATCH"
    Screen.............. "SAPLRSSM_PROCESS 0100"
    Screen line......... 19
    Information on where terminated
    Termination occurred in the ABAP program "SAPLRSBATCH" - in "SAVE_SETTINGS".
    The main program was "RSPC_MAINTAIN ".
    In the source code you have the termination point in line 1082
    of the (Include) program "LRSBATCHF01".
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "SAVE_SETTINGS" "(FORM)", but it was neither handled locally nor
    declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLRSBATCH "; its source code begins in line
    1045 of the (Include program "LRSBATCHF01 ".
    Source Code Extract
    Line
    SourceCde
    1052
    loop at g_t_batch_par.
    1053
    if  g_t_batch_par-pc_variant is initial.
    1054
    l_var = '//SPACE//SPACE//SPACE//SPACE//'.
    1055
    else.
    1056
    l_var =  g_t_batch_par-pc_variant.
    1057
    endif.
    1058
    do.
    1059
    call function 'ENQUEUE_ERSBATCHSERVER'
    1060
    exporting
    1061
    mode_rsbatchserver = 'E'
    1062
    process_type       = g_t_batch_par-process_type
    1063
    pc_variant         = l_var
    1064
    _scope             = '3'
    1065
    _wait              = 'X'
    1066
    exceptions
    1067
    foreign_lock       = 1.
    1068
    if sy-subrc = 0.
    1069
    exit.
    1070
    endif.
    1071
    enddo.
    1072
    endloop.
    1073
    1074
    loop at g_t_batch_par.
    1075
    delete from rsbatchparallel where
    1076
    process_type = g_t_batch_par-process_type and
    1077
    pc_variant   = g_t_batch_par-pc_variant.
    1078
    delete from rsbatchserver where
    1079
    process_type = g_t_batch_par-process_type and
    1080
    pc_variant   = g_t_batch_par-pc_variant.
    1081
    endloop.
    >>>>>
    insert rsbatchparallel from table g_t_batch_par.
    1083
    insert rsbatchserver   from table g_t_batch_serv.
    1084
    call function 'DB_COMMIT'.
    1085
    1086
    loop at g_t_batch_par.
    1087
    if  g_t_batch_par-pc_variant is initial.
    1088
    l_var = '//SPACE//SPACE//SPACE//SPACE//'.
    1089
    else.
    1090
    l_var =  g_t_batch_par-pc_variant.
    1091
    endif.
    1092
    do.
    1093
    call function 'DEQUEUE_ERSBATCHSERVER'
    1094
    exporting
    1095
    mode_rsbatchserver = 'E'
    1096
    process_type       = g_t_batch_par-process_type
    1097
    pc_variant         = l_var
    1098
    _scope             = '3'
    1099
    _synchron          = 'X'.
    1100
    if sy-subrc = 0.
    1101
    exit.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    3
    SY-DBCNT
    0
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    0001
    SY-UCOMM
    SAVE
    SY-TITLE
    Process Maintenance: Attribute Change Run
    SY-MSGTY
    SY-MSGID
    SY-MSGNO
    000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    1
    SY-DATUM
    20071008
    SY-UZEIT
    165610
    SY-XPROG
    SAPFGUICNTL
    SY-XFORM
    %_CONTROL_EXIT_DYNPRO
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    20 FORM         SAPLRSBATCH                         LRSBATCHF01                          1082
    SAVE_SETTINGS
    19 FUNCTION     SAPLRSBATCH                         LRSBATCHU08                           279
    RSBATCH_MAINTAIN_PAR_SETTINGS
    18 FORM         SAPLRSSM_PROCESS                    LRSSM_PROCESSF04                     1917
    MAINTAIN_PARALLEL_SETTINGS
    17 MODULE (PAI) SAPLRSSM_PROCESS                    LRSSM_PROCESSI01                      125
    USER_COMMAND_0100
    16 FUNCTION     SAPLRSPC_VARIANT                    LRSPC_VARIANTU01                       93
    RSPC_VARIANT_MAINTAIN
    15 FUNCTION     SAPLRSSM_PROCESS                    LRSSM_PROCESSU01                       56
    RSSM_PROCESS_VARIANT_DIALOG
    14 METHOD       CL_RSSM_ATTRIBCHANGE==========CP    CL_RSSM_ATTRIBCHANGE==========CM003     3
    CL_RSSM_ATTRIBCHANGE=>IF_RSPC_MAINTAIN~MAINTAIN
    13 METHOD       CL_RSPC_FRONTEND==============CP    CL_RSPC_FRONTEND==============CM00E    16
    CL_RSPC_FRONTEND=>_EDIT_NODE
    12 METHOD       CL_RSPC_FRONTEND==============CP    CL_RSPC_FRONTEND==============CM00T   139
    CL_RSPC_FRONTEND=>_ON_MENU_SEL
    11 METHOD       CL_RSPC_FRONTEND==============CP    CL_RSPC_FRONTEND==============CM016    40
    CL_RSPC_FRONTEND=>_ON_NET_DOUBLECLICK
    10 METHOD       CL_GUI_RSNETGRAPHIC_NETPLAN===CP    CL_GUI_RSNETGRAPHIC_NETPLAN===CM00W    40
    CL_GUI_RSNETGRAPHIC_NETPLAN=>_HANDLE_OBJECTDBLCLICK
    9 METHOD       CL_GUI_RSNETGRAPHIC_NETPLAN===CP    CL_GUI_RSNETGRAPHIC_NETPLAN===CM005    37
    CL_GUI_RSNETGRAPHIC_NETPLAN=>HANDLE_EVENTS
    8 METHOD       CL_GUI_RSNETGRAPHIC_NETPLAN===CP    CL_GUI_RSNETGRAPHIC_NETPLAN===CM003     3
    CL_GUI_RSNETGRAPHIC_NETPLAN=>DISPATCH
    7 METHOD       CL_GUI_CFW====================CP    CL_GUI_CFW====================CM00K   173
    CL_GUI_CFW=>DISPATCH_SYSTEM_EVENTS
    6 FORM         SAPFGUICNTL_CFW                     SAPFGUICNTL_CFW                        23
    CONTROL_DISPATCH
    5 FORM         SAPFGUICNTL                         SAPFGUICNTL                            20
    CONTROL_DISPATCH
    4 FORM         SAPMSSYD                            SAPMSSYD                              288
    %_CTL_INPUT
    3 MODULE (PAI) SAPMSSYD                            SAPMSSYD                              236
    %_CTL_INPUT1
    2 FUNCTION     SAPLRSPC_FRONTEND                   LRSPC_FRONTENDU10                      76
    RSPC_CHAIN_MAINTAIN
    1 EVENT        RSPC_MAINTAIN                       RSPC_MAINTAIN                          11
    START-OF-SELECTION
    Chosen variables
    Name
    Val.
    No.      20 Ty.          FORM
    Name  SAVE_SETTINGS
    G_T_400_SAVE
    Table[initial]
    <%_TABLE_RSBATCHSERVER>
    SYST-REPID
    SAPLRSBATCH
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5454554454422222222222222222222222222222
    310C232143800000000000000000000000000000
    G_H_DEBUG_TYPE
    Table[initial]
    SY-REPID
    SAPLRSBATCH
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5454554454422222222222222222222222222222
    310C232143800000000000000000000000000000
    G_T_WAIT
    0.1.
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222220022222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    G_T_BATCH_PAR-PROCESS_TYPE
    ATTRIBCHAN
    0000000000
    0000000000
    4555444444
    144292381E
    %_DUMMY$$
    0000
    0000
    2222
    0000
    G_T_300_OBJECT[]
    Table[initial]
    G_T_BATCH_PAR-PC_VARIANT
    CHANGE_RUN_MASTER_DATA
    000000000000000000000000000000
    000000000000000000000000000000
    444444555454455455445422222222
    381E75F25EFD13452F414100000000
    G_T_300_OBJECT
    0000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222223333
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    <%_TABLE_RSBATCHPARALLEL>
    G_S_ADM-PRIORITY
    0
    0
    2
    0
    G_T_BATCH_PAR[]
    Table IT_8429[3x212]
    FUNCTION-POOL=RSBATCHDATA=G_T_BATCH_PAR[]
    Table reference: 176
    TABH+  0(20) = 0700000040337FA0000000000000000000000000
    TABH+ 20(20) = 000000B0000020ED00000003000000D4FFFFFFFF
    TABH+ 40(16) = 04000276000007400010249401800000
    store        = 0x0700000040337FA0
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 176   (0x000000B0)
    label        = 8429  (0x000020ED)
    fill         = 3     (0x00000003)
    leng         = 212   (0x000000D4)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000024
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000410D8D60
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 6428  (0x0000191C)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x00000001)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    G_T_BATCH_SERV[]
    Table IT_8430[2x166]
    FUNCTION-POOL=RSBATCHDATA=G_T_BATCH_SERV[]
    Table reference: 181
    TABH+  0(20) = 07000000410D9AB8000000000000000000000000
    TABH+ 20(20) = 000000B5000020EE00000002000000A6FFFFFFFF
    TABH+ 40(16) = 04000276000003E00010249401800000
    store        = 0x07000000410D9AB8
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 181   (0x000000B5)
    label        = 8430  (0x000020EE)
    fill         = 2     (0x00000002)
    leng         = 166   (0x000000A6)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000006
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x0700000040360F08
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 6429  (0x0000191D)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x00000001)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    No.      19 Ty.          FUNCTION
    Name  RSBATCH_MAINTAIN_PAR_SETTINGS
    I_NO_DIALOG
    0
    0
    2
    0
    I_TYPE
    ATTRIBCHAN
    0000000000
    0000000000
    4555444444
    144292381E
    I_VARIANT
    CHANGE_RUN_MASTER_DATA
    000000000000000000000000000000
    000000000000000000000000000000
    444444555454455455445422222222
    381E75F25EFD13452F414100000000
    E_T_SERVER
    Table[initial]
    C_T_BATCH_PAR[]
    Table IT_8427[3x210]
    FUNCTION-POOL=RSSM_PROCESSFORM=MAINTAIN_PARALLEL_SETTINGSDATA=L_T_PAR
    Table reference: 377
    TABH+  0(20) = 070000004050EFA8070000004033896000000000
    TABH+ 20(20) = 00000179000020EB00000003000000D2FFFFFFFF
    TABH+ 40(16) = 040001900000CEF00010249401800000
    store        = 0x070000004050EFA8
    ext1         = 0x0700000040338960
    shmId        = 0     (0x00000000)
    id           = 377   (0x00000179)
    label        = 8427  (0x000020EB)
    fill         = 3     (0x00000003)
    leng         = 210   (0x000000D2)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#001089
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x0700000040332390
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 6426  (0x0000191A)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x00000001)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0x070000004110CD08
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x0700000040F34148
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    G_T_CLASS_100[]
    Table IT_8436[3x122]
    FUNCTION-POOL=RSBATCHDATA=G_T_CLASS_100[]
    Table reference: 355
    TABH+  0(20) = 07000000410F9E48070000004110865000000000
    TABH+ 20(20) = 00000163000020F4000000030000007AFFFFFFFF
    TABH+ 40(16) = 0400027600000B900010249401800000
    store        = 0x07000000410F9E48
    ext1         = 0x0700000041108650
    shmId        = 0     (0x00000000)
    id           = 355   (0x00000163)
    label        = 8436  (0x000020F4)
    fill         = 3     (0x00000003)
    leng         = 122   (0x0000007A)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000047
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x070000004081DE00
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 6435  (0x00001923)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x00000001)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0x07000000406795C8
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x07000000410FB438
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    G_T_CLASS_100
    C'C'
    0000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000
    4242222222222222222222222222222222222222222222222222222222222
    3737000000000000000000000000000000000000000000000000000000000
    %_FL2*CTRL_SERVER
    1
    0000
    0001
    G_T_CLASS_100-TEXT
    'C'
    000000000000000000000000000000000000000000000000000000000000
    000000000000000000000000000000000000000000000000000000000000
    242222222222222222222222222222222222222222222222222222222222
    737000000000000000000000000000000000000000000000000000000000
    TEXT-008
    'C'
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    24222222222222222222222222222222222222222222222222
    73700000000000000000000000000000000000000000000000
    SAVEOK
    SAVE
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    5454222222222222222222222222222222222222222222222222222222222222222222
    3165000000000000000000000000000000000000000000000000000000000000000000
    OKCODE
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000
    G_SUBRC
    0
    0000
    0000
    G_FIRST_TIME_100
    0
    0
    2
    0
    G_T_WP_400
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    G_500_WP_NO
    000
    000
    222
    000
    CX_TRUE
    X
    0
    0
    5
    8
    SY-MSGID
    00000000000000000000
    00000000000000000000
    22222222222222222222
    00000000000000000000
    SPACE
    0
    0
    2
    0
    SY-MSGNO
    000
    000
    000
    333
    000
    SY-MSGV1
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV2
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV3
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV4
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    No.      18 Ty.          FORM
    Name  MAINTAIN_PARALLEL_SETTINGS
    SY-REPID
    SAPLRSSM_PROCESS
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5454555455544455222222222222222222222222
    310C233DF02F3533000000000000000000000000
    SYST-REPID
    SAPLRSSM_PROCESS
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5454555455544455222222222222222222222222
    310C233DF02F3533000000000000000000000000
    P_VARIANT
    CHANGE_RUN_MASTER_DATA
    000000000000000000000000000000
    000000000000000000000000000000
    444444555454455455445422222222
    381E75F25EFD13452F414100000000
    G_T_BATCH_PAR
    ATTRIBCHANCHANGE_RUN_MASTER_DATA        03C
    000000000000000000000000000000000000000000000
    000000000000000000000000000000000000000000000
    455544444444444455545445545544542222222233422
    144292381E381E75F25EFD13452F41410000000003300
    G_T_BATCH_PAR[]
    Table IT_8382[3x90]
    FUNCTION-POOL=RSSM_PROCESSDATA=G_T_BATCH_PAR[]
    Table reference: 344
    TABH+  0(20) = 070000004049B188000000000000000000000000
    TABH+ 20(20) = 00000158000020BE000000030000005AFFFFFFFF
    TABH+ 40(16) = 04000190000016A00010249401800000
    store        = 0x070000004049B188
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 344   (0x00000158)
    label        = 8382  (0x000020BE)
    fill         = 3     (0x00000003)
    leng         = 90    (0x0000005A)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000106
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x0700000040F33B90
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 6392  (0x000018F8)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x00000001)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    L_PC_TYPE
    ATTRIBCHAN
    0000000000
    0000000000
    4555444444
    144292381E
    SPACE
    0
    0
    2
    0
    P_PC_TYPE
    ATTRIBCHAN
    0000000000
    0000000000
    4555444444
    144292381E
    L_T_PAR
    Table IT_8427[3x210]
    L_S_PAR
    ATTRIBCHANCHANGE_RUN_MASTER_DATA        03C
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    4555444444444444555454455455445422222222334222222222222222222222222222222222222222222222222222
    144292381E381E75F25EFD13452F414100000000033000000000000000000000000000000000000000000000000000
    G_S_CHAIN
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    G_T_F4
    Table IT_4031[5x222]
    FUNCTION-POOL=RSSM_PROCESSDATA=G_T_F4
    Table reference: 122
    TABH+  0(20) = 0700000040293BE0000000000000000000000000
    TABH+ 20(20) = 0000007A00000FBF00000005000000DEFFFFFFFF
    TABH+ 40(16) = 04000190000009B00010249401800000
    store        = 0x0700000040293BE0
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 122   (0x0000007A)
    label        = 4031  (0x00000FBF)
    fill         = 5     (0x00000005)
    leng         = 222   (0x000000DE)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000037
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x070000004035B278
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 3652  (0x00000E44)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x00000001)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>&

    When modifying the PC, you are likely using a process variant twice, or, using a variant already used somewhere else.

  • How to provide a same user SU01  for admin and display authority on PFCG

    Hello Security Experts,
    I am working on a requirement where I have to create a role for user administrator with Display access in PFCG but user should be able to use SU01 to do user administration meaning create , change user ( including role assignments) , delete , lock/unlock user.
    First I have maintained S_USER_AGR as ACTVT 03,08,22  / S_USER_AUT as ACTVT 03,08,22 / S_USER_GRP as ACTVT 01, 02, 03, 05, 06, 08, 22, 78 / S_USER_PRO as ACTVT 03, 08, 22.
    Disabled Objects S_USER_VAL and S_USER_TCD.
    While testing the role I got authorization error where my SU53 and trace pointing at missing value in S_USER_AGR as ACTVT 02.
    After assigning S_USER_AGR as ACTVT 02 the role assignment is allowed in SU01 however the role change is also enabled from PFCG where my test user is able to get in to the role in edit mode (however he cant do any changes in role or generate the role as I have disabled S_USER_VAL and did not provide 02 on S_USER_PRO ) and save the role.  This should not happen as per requirement.
    How can I restrict PFCG to display and allow user to assign roles to end users ? Kindly suggest and help.
    Thanks in advance for your help.
    Regards
    Murali

    Hi
    Run pfcg and try to go to change with your restricted settings then click on the error message to get the table entries in performance assistant. Put those in prgn_cust via sm30.
    Then use 22 instead of 02 in newly called object S_USER_SAS.
    Make sure you have at least one user with * in that object for full access across the landscape before transporting the table.
    Cheers
    David
    Edited by: David Berry on Oct 23, 2010 10:25 AM
    Edited by: David Berry on Oct 23, 2010 10:26 AM
    Forgot to say - when you have the new object value 22 in your restricted role and assigned to test user prior to moving to PROD the only way to go into change mode is to first go to the USER tab and then press change. Anywhere else and you'll still get the 'you are not authorised' message.
    Edited by: David Berry on Oct 25, 2010 8:04 PM

  • Short Dump SAPSQL_ARRAY_INSERT_DUPREC

    Hi Experts,
    I am getting a the short dump SAPSQL_ARRAY_INSERT_DUPREC after executing report SDRQCR21 at line 1258
    INSERT VBBE FROM TABLE DA_XVBBE.
    Please help.

    Did you look for OSS notes for your version ?
    33267
    SDRQCR21 cancels with duplicate record
    25444
    SDRQCR21: Recovery of sales and delivery requirements
    1023578
    SDRQCR21 not fixing when wrong plant or material in VBBE
    1562605
    CALL_FUNCTION_REMOTE_ERROR SAPSQL_ARRAY_INSERT_DUPREC
    Regards,
    Raymond

  • SAP ST22 dump SAPSQL_ARRAY_INSERT_DUPREC

    Hi All,
    We are getting dump SAPSQL_ARRAY_INSERT_DUPREC in testing system. SAP basis: 701 and Oracle 10.2.0.2
    We are getting this dump from yesterday only and the details of the dump are as mentioned below:
    ============================================================================================
    Short text
        The ABAP/4 Open SQL array insert results in duplicate database records.
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "SAPLSBAL_DB_INTERNAL" had to be terminated because it
         has
        come across a statement that unfortunately cannot be executed.
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
         in
        procedure "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", nor was it propagated
         by a RAISING clause.
        Since the caller of the procedure could not have anticipated that the
        exception would occur, the current program is 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.)
    Information on where terminated
        Termination occurred in the ABAP program "SAPLSBAL_DB_INTERNAL" - in
         "BAL_DB_INTERNAL_NO_UPDATE_TASK".
        The main program was "SWNCCOLL ".
        In the source code you have the termination point in line 64
        of the (Include) program "LSBAL_DB_INTERNALU02".
        The program "SAPLSBAL_DB_INTERNAL" was started as a background job.
        Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
        Job Initiator.. "BASIS"
        Job Number..... 08893100
        The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
        procedure "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", but it was neither
         handled locally nor declared
        in the RAISING clause of its signature.
        The procedure is in program "SAPLSBAL_DB_INTERNAL "; its source code begins
         line
        1 of the (Include program "LSBAL_DB_INTERNALU02 ".
    System environment
        SAP-Release 701
        Application server... "appl543"
        Network address...... "122.99.01.88"
        Operating system..... "AIX"
        Release.............. "5.3"
        Hardware type........ "099DER88BN90000"
        Character length.... 16 Bits
        Pointer length....... 64 Bits
        Work process number.. 27
        Shortdump setting.... "full"
        Database server... "appl543"
        Database type..... "ORACLE"
        Database name..... "Q22"
        Database user ID.. "SAPSR3"
    =====================================================================================================
    Also some jobs are cancelled and they are forming the above dump. the detials are:
    SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 00:43:31
    SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 02:43:31
    SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 03:43:31
    SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 04:43:31
    SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 05:43:31
    SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 06:43:31
    **The cancelled job SAP_COLLECTOR_FOR_NONE_R3_STAT generating the above dump at ST22.**
    Please suggest us a solution. Thanks in advance!!!
    Regards
    Veera
    Edited by: Veerab on Dec 17, 2010 11:33 AM

    >     1 of the (Include program "LSBAL_DB_INTERNALU02 ".
    Try the following:
    open http://service.sap.com/notes
    Search for "LSBAL_DB_INTERNALU02"
    Markus

  • How to Change the Alias name for Internet user in SU01 tr code through cod?

    Hi Guys,
                 My req is we have to change the Alias name(SU01 tr code) for the existing users thru code.So can anybody tell me how to change the Alias name like which we do it in SU01 tr code thru code or FM.?
                Is there any FM for tha changing Alias Name?
    Thanks,
    Gopi.

    Hello Gopi Anne ,
                                 You can use the following FM / BAPI :
    BAPI_USER_CHANGE
    MY_BAPI_USER_CHANGE
    For BAPI_USER_CHANGE :
    You need to make use of the IMPORT parameter :
    ALIAS     TYPE     BAPIALIAS                               User Name Alias
    ALIASX     LIKE     BAPIALIASX                               User alias change flag
    Thanks,
    Greetson

  • Error has come while creating USER from SU01

    Dear Expert,
    I have got typical error while creating user from T-Code SU01.
    Problem is like that : I suppose to  use SU01 and "User Maintanace: Initial Screen
    has come. Now I put the new user name like ABAP2008 or FI2008 (what ever the name thats hardly matter) and click on CREAT button then next screen Maintain User has been appeared.In this screen Address TAB is on and asking for fillup all the required user information.So I have been made all information like :First name /Last name /Tele ph/Fax / email etc etc. After complete this tab when I clicked on next tab is called "LOGON DATA, it has been given a error "Specify a valid country indicator
    Message no. T5027" . Even thogh I didn't able to go to next screen LOGON DATA.Because of these problem I doesn't able to creat a user.
    SAP : IDES version ECC 6
    DB:SQL2005
    OS: Windows 2003 server
    Please do the needfull
    Thanks & Regards
    Pavel

    Hey Pavel,
    Are you using ECC with ISU.. ? I am not sure but I feel your issue can be solved with information provided in SAPnote,
    Note 1046566 - EC70: address-independent telephone number no country.
    The system does not transfer any country from the master data template with the address-independent telephone number.  The system issues the warning message T5027 "Specify a valid country indicator".
    All the best !

  • Role design issue in regarding SU01 and UserGroups

    Hi Experts,
    I got a requirement to set up a custom role in regarding SU01 access and User groups. Create a role that allows users with this role to go to SU01 but only is allowed to lock/unlock account or reset password. Also should be able to do only with their particular group, not for all groups.
    Suppose consider a scenario, we have 2 groups called India with 4 members and America with 5 members. Now admin of India group can only restrict those 4 people, should not have access to users of America group.
    I have tried in a way that, created a role with one tcode SU01 in Menu tab and fields Activity:05 , Group Name: Test_group for S_USER_GRP object. Now assigned this role to a user(TEST1) and also mentioned the group name in Logon tab.So he will be the admin for group "Test_Group". in this way he is able to do lock/unlock account and pwd reset for all group members not only for Test_Group. I am not getting Where I am doing the mistake.
    Please help me out to solve this issue.
    Thanks in advance.

    As you suggested,I have created a role with only one tcode  SU01 and for S_USER_GRP I have given in the following way:
    Activity: 05
    Group name: Test_Group
    and assigned this to user(Test1).
    We have other groups like Test_Group1,Test_Group2 etc. But User(Test1) still able to do changes for Test_Group1 and T_Group2 rather than Test_Group

  • PR creation ERROR: SAPSQL_ARRAY_INSERT_DUPREC via PS

    When I create a Purchase Requisition via project systems, I get this error ERRO info 00671: Abap/4 processor: SAPSQL_ARRAY_INSERT_DUPREC. I configured a new PR document type and assigned a number range to it, I transported it o QAS and then PRD, I didnt test PS in detail, when I use base unit % there is not problem, but when I use PC and ROL, then I get an Update was terminated ERROR. How do i fix this?
    Please give directive on which transactions or path I have to use to fix it.
    Thank you.

    Hi,
    If you are using some badi or exit, check the process by de activating the same.
    If same results are coming, then check OSS notes applicability in your case. (e.g. 148828, 193580 etc)
    Other wise take help from OSS message, since this problem mainly occures due to program error.
    Regards,
    Manoj

  • FI-SL error SAPSQL_ARRAY_INSERT_DUPREC during direct posting to the SL.

    I am working on FI- Special Ledger and currently encountering an error:
    I am trying to post journals to the special purpose ledger using a local file where I am encountering the following error:
    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC  
    Except.                CX_SY_OPEN_SQL_DB           
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught 
      in                                                                           
    procedure "INS_XXXXXA" "(FORM)", nor was it propagated by a RAISING clause.  
    Since the caller of the procedure could not have anticipated that the         
    exception would occur, the current program is 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.                                                
    XXXXXA is the custom database table name.
    The form mentioned is a item table for one the special ledger which has been custom defined.
    I have debugged the code and found out the following:
    1. There are two records which needs to be updated to the items table of the ledger.
    2. When I checked the items table the key value (which needs to be updated) doesn't exist currently.
    3. I saw some resolution on the number range definition which i tried to apply but not fruitful.
    Although the new records which needs to be inserted to the database table is not there I am getting the error SAPSQL_ARRAY_INSERT_DUPREC.
    Please let me know of any suggestion to resolve the issue.
    I might have not correctly implemented the solution for the number range.
    Your valuable suggestions will be awarded accordingly.
    Also let me know if anymore clarity is required.
    Kind Regards,
    himansu roy

    Hello everyone,
    Got the issue and resolution.
    The problem was in the custom code the ledger update was happening twice so the duplicate entries were giving dump during the COMMIT.
    Regards,
    Himansu Roy

  • Update terminate : error SAPSQL_ARRAY_INSERT_DUPREC

    We are getting error "SAPSQL_ARRAY_INSERT_DUPREC" while using tcode : VK12 ME13 ME11,
    Error is in function module 'RV_KONDITION_SICHERN_VK13' , form 'KONH_CHANGE" in program "SAPLV13A". I checked OSS notes also but didnot find anything.We using ECC6. Can anybody tell what could be the reason and how to eliminate this.

    Hi Meena ,
    are u running out of Number series ?, i had this kind of errors while i'm creating Delivery documents , then i found out Number ranges are missing ,thats y i got that errors, in ur case , i never seen number ranges for CONDITION records , but still u can cross check with ur function consultants.
    regards
    Prabhu

  • Run-time error SAPSQL_ARRAY_INSERT_DUPREC occurred

    When creating a new SyncBo (T51) instance after syncing eventually MI Clients shows the following message:
    [20070315 01:28:14:343] E [MI/Sync ] Received exception info code 10 and detailed message "Exception while callSync: The ABAP/4 Open SQL arrayinsert results in duplicate database records. records in the data base."
    In sm21 shows message:
    AB0 Run-time error "SAPSQL_ARRAY_INSERT_DUPREC" occurred
    AB1 > Short dump "070316 205056 sapnw ELDA " generated
    Looking for SAPSQL_ARRAY_INSERT_DUPREC error in SAP Note we found the note 817849 (Runtime error SAPSQL_ARRAY_INSERT_DUPREC occurs during sync).
    We have downloaded and applied this note in Backend as note requires and ALL prerequisites of this note. Also we have upgraded to SP19 and Kernel to 155 (part 1 and 2). But problem continues and the client that happened this problem does not work any more, all new SyncBO instances created goes to MEREP_MON as Waiting status.
    The dump on duplicate record is happening when the user is synchronizing and when a record is getting inserted to table merep_10100.
    The solution /workaround could be to do a client reset for those devicesand test again and see if it is happening, but error returns happening after this.
    When this happen SyncBo instance keeps on Waiting status (MEREP_MON). We couldn't understand why this happen suddenly and then no more new SyncBo could be created, all goes to Waiting status. Reprocess (ShiftF5) or start handler (Shift10) does not take any effect.
    Best Regards,
    Rogério

    Hi Ajith
    I am getting the same error and below is the error message from ST22. The only change is I am using for MTR application and the sync fails for the 2nd time when synched for patches for the MTR application. As it is generic sync, could you please advice to get rid of the problem.
    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
      "LOG_INSERT_DB" "(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.)
    Thanks, Raj

  • Runtime error SAPSQL_ARRAY_INSERT_DUPREC  during migo

    Hi Friends,
    When I try doing MIGO with reference to a PO and save the document it gives me runtime error SAPSQL_ARRAY_INSERT_DUPREC.
    I have check the buffer, and the no. range everything is perfect, but still i am getting this error.
    Can anyone please give me the possible solution for this. Is there any SAP note that I need to apply.
    Regards,
    Wasim.

    Hello Wasim,
    The common cause of this termination is the material document             
    number range as per note 31793 - SAPSQL_ARRAY_INSERT_DUPREC.                                                                               
    So please check if the current numbers are synchronized with the          
    database tables:                                                                               
    OMBT trx x MKPF table                                                     
    OMH6 trx x EKKO table                                                                               
    If it has the same number range the sort dump should not be raised        
    anymore.                                                                               
    The main root causes are:                                                 
    -> when you are transporting number ranges from one client to another;                                                                               
    -> when you face a shut down in your system and you have defined a        
    buffer application server tolerance in transaction SNRO;                                                                               
    -> when you are doing the posting by using BAPI's and for some reason     
    the BAPI failed.                                                                               
    I hope it helps you.                                                      
    Best Regards,
    Fábio Almeida
    MM Consultant

  • DUMP "SAPSQL_ARRAY_INSERT_DUPREC" WHILE MODIFYING A SALES ORDER

    Hi,
    when I modify a certain sales order document I get a Dump with the error "SAPSQL_ARRAY_INSERT_DUPREC" in INSERT_POS_IN_DB
    Any ideas?
    Thanks in advance,
    F

    i guess...then internal table in which you are inserting a value is  a sorted table.
    try using:
    insert wa into table itab.
    or it you are inserting a duplicate record in DB
    Edited by: Amit Gupta on Oct 7, 2008 3:56 PM

Maybe you are looking for

  • Switch Layers Script Question

    Hi I have a small script here which someone from these forums posted not too long ago... was it Noel? Either way, this script is fantastic and brings up a sub-menu to switch documents. When the menu pops up, it shows a list of all open documents in P

  • I am getting this error code when trying to open an mpeg4 "OSStatus error -12909" anyone know why. Thanks

    I am getting this error code when trying to open an mpeg4 file "OSStatus error -12909" Has anyone had this happen to them. I am new to the support community. Thanks

  • Optical Out

    I set up my power mac g5 with an optical out cable to a surround sound receiver but no noise at all is coming out. The receiver is set up right, I changed the settings to optical out and nothing is happening. Anything this could be? Thanks

  • OSB MFL UTF-8 Issue

    I'm having a similar issue as in the discussion linked below: https://community.oracle.com/thread/3554623 I have a Binary to XML MFL setup, with UTF-8 codepage set for each field and as Default MFL Encoding (File->Properties in Format Builder) set to

  • Outlook 2010 - One of My Email Accounts Keeps Archiving/Deleting Emails

    I have three email accounts on my one Outlook 2010 program. This problem is only happening to one of them. At the end of the week (Friday) I close out of my email. Whether I use my email again over the weekend doesn't matter, come Monday morning - al