Dump : SAPSQL_ARRAY_INSERT_DUPREC  in VA42.

Hi All,
I got one critical Dump issue,
I got the issue like dump : SAPSQL_ARRAY_INSERT_DUPREC  in VA42.
Runtime Error      :    SAPSQL_ARRAY_INSERT_DUPREC
Except.               :  CX_SY_OPEN_SQL_DB
The user is trying to add a line item from Contract its going to dump, the dump is saying like  duplicate  object number .
can any one suggest the how to resolve the issue.
Regards,
Jayan.

Check SM13 for the update termination records.  View the update data and check the data condition causing the issue.  Debug.  Check for bad user exits and/or recent changes to the code.  OSS does have notes regarding the issue but it's unlikely that you'll find the issue there, especially if it just started happening, unless you just implemented support packs or notes.

Similar Messages

  • 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

  • After system copy, dump 'SAPSQL_ARRAY_INSERT_DUPREC' per every hour.

    hi experts,
    I did system copy solman 701. but I found short dump 'SAPSQL_ARRAY_INSERT_DUPREC' per every hour.
    I attach part of short dump.
    ===============================================================================
    Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
    Exception CX_SY_OPEN_SQL_DB
    Date and Time 2010.09.02 06:14:16
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "GP4II5O0KKJ13RR6R50N44F7KST" 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 "WRITE_ICFACT" "(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.)
    User and Transaction
    Client.............. 001
    User................ "SMD_RFC"
    Language Key........ "E"
    Transaction......... " "
    Transactions ID..... "D30DB6DF06D7F16BA277005056AD47D2"
    Program............. "GP4II5O0KKJ13RR6R50N44F7KST"
    Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    ================================================================================================
    I think the program GP4II5O0KKJ13RR6R50N44F7KST is related with BW.
    I found information of the program GP4II5O0KKJ13RR6R50N44F7KST
    Generated report : InfoCube Write
    Template......: RSTMPLWIDTP
    RSAUInfoCube......: 0SMD_PE2H
    Author........: SMD_RFC
    Date..........: 16.07.2010 18:56:23
    How can I correct ?
    thanks and regards
    jun

    hi,
    thanks your reply.
    I applied sapnote 1500227 but still error.
    what can I do?
    Regards
    jun

  • Dump SAPSQL_ARRAY_INSERT_DUPREC when loading a hierarchy

    Hi Guru's,
    I have an error when i try to load a hiearchy on my BI system. I want to load the Cust_sales hierarchy but i ahev a short dump : SAPSQL_ARRAY_INSERT_DUPREC
    Any idea ?
    Cyril

    hi...
    it seems you have tried to insert data fro an internal table to database and in the mean it tried to insert duplicate entry ie records with same key fields.
    way to solve it:::
    way1.
    *sort the internal table in use.
    sort t_table.
    Delete adjecent duplicates.
    DELETE ADJACENT DUPLICATE ENTRIES FROM t_table
    now proceed.
    way2.
    loop at the internal table and now go for insert....
    if duplicte exist in that case it will set sy-subrc but will not give dump....
    regards

  • 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

  • ABAP dump(SAPSQL_ARRAY_INSERT_DUPREC) while creating a delivery

    Hello Friends,
    I am getting the dump while creating the delivery .The error details are as follows.
    The ABAP/4 Open SQL array insert results in duplicate database record
    What happened?
    The current ABAP/4 program "SAPLV05I " had to be terminated because
    one of the statements could not be executed.
    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 occurred in a non-modified SAP program, you may be
    able to find a solution in the SAP note system.
    If you have access to the note system yourself, use the following
    search criteria:
    "SAPSQL_ARRAY_INSERT_DUPREC"
    "SAPLV05I " or "LV05IU15 "
    "SD_PARTNER_UPDATE"
    Source code extract
    004500                                           POSNR = I_XVBPA-POSNR
    004510                                           PARVW = I_XVBPA-PARVW.
    004520               IF I_YVBPA-STCD1 <> I_XVBPA-STCD1 OR
    004530                   I_YVBPA-STCD2 <> I_XVBPA-STCD2 OR
    004540                   I_YVBPA-STCD3 <> I_XVBPA-STCD3 OR
    004550                   I_YVBPA-STCD4 <> I_XVBPA-STCD4 OR
    004560                   I_YVBPA-STCDT <> I_XVBPA-STCDT OR
    004570                   I_YVBPA-STKZN <> I_XVBPA-STKZN OR
    004580                   I_YVBPA-J_1KFREPRE <> I_XVBPA-J_1KFREPRE OR
    004590                   I_YVBPA-J_1KFTBUS <> I_XVBPA-J_1KFTBUS OR
    004600                   I_YVBPA-J_1KFTIND <> I_XVBPA-J_1KFTIND.
    004610                 MOVE-CORRESPONDING I_XVBPA TO WA_XVBPA3I.
    004620                 APPEND WA_XVBPA3I TO DA_XVBPA3I.
    004630               ENDIF.
    004640             ENDIF.
    004650           ENDIF.
    004660         WHEN UPDKZ_OLD.
    004670           IF DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_OLD   OR
    004680              DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_ADRC.
    004690             YADR-ADRNR = DA_VBPA-ADRNR. COLLECT YADR.
    004700           ENDIF.
    004710           IF DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_OLD   OR
    004720              DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_ADRC.
    004730             XADR-ADRNR = DA_VBPA-ADRNR. COLLECT XADR.
    004740           ENDIF.
    004750       ENDCASE.
    004760     ENDLOOP.
    004770     UPDATE (OBJECT) FROM TABLE DA_XVBPAU.
    004780     UPDATE VBPA3 FROM TABLE DA_XVBPA3U.
    004790
         >     INSERT (OBJECT) FROM TABLE DA_XVBPAI.
    004810     INSERT VBPA3 FROM TABLE DA_XVBPA3I.
    004820
    004830     IF SY-SUBRC > 0.
    Could you please suggest me ,what could be the reason for dump and how to avoid dump?
    <REMOVED BY MODERATOR>
    Thank you in advance,
    Arvind.
    Edited by: Alvaro Tejada Galindo on Apr 22, 2008 5:16 PM
    Edited by: Alvaro Tejada Galindo on Apr 22, 2008 5:16 PM

    Hello, I have very same error
    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
    Exception              CX_SY_OPEN_SQL_DB
    Transaction......... "VL01N "                                                                
    Program............. "SAPLV05I"                                                              
    Screen.............. "RSM13000 3000"                                                         
    Screen line......... 2   
    SAP kernel....... 700  
    Patch level. 75 
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"                             
    SAP database version. 700                                                                    
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2" 
    The ABAP/4 Open SQL array insert results in duplicate database records.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught  in procedure "SD_PARTNER_UPDATE" "(FUNCTION)", nor was it propagated by a RAISING clause.
    I use SAP_APPL SAPKH60006 Support Package
    The NUMBER RANGE OBJECT HAS NO ERRORS!
    I went trough the zillions of notes all of them affect the old releases.... Please advice.
    Patiently yours,
    SAP User

  • Dump issues in VA42

    tables:  rv45a, vbak.
    data:   bdcdata like bdcdata    occurs 0 with header line.
    data : begin of it_va42 occurs 0,
           vbeln like vbak-vbeln,
           mabnr like rv45a-mabnr,
           end of it_va42.
    data it_va42_a like it_va42 occurs 0 with header line.
    data it_va42_b like it_va42 occurs 0 with header line.
    call function 'UPLOAD'
    exporting
    *   CODEPAGE                      = ' '
       filename                      = ' '
       filetype                      = 'ASC'
    *   ITEM                          = ' '
    *   FILEMASK_MASK                 = ' '
    *   FILEMASK_TEXT                 = ' '
    *   FILETYPE_NO_CHANGE            = ' '
    *   FILEMASK_ALL                  = ' '
    *   FILETYPE_NO_SHOW              = ' '
    *   LINE_EXIT                     = ' '
    *   USER_FORM                     = ' '
    *   USER_PROG                     = ' '
    *   SILENT                        = 'S'
    * IMPORTING
    *   FILESIZE                      =
    *   CANCEL                        =
    *   ACT_FILENAME                  =
    *   ACT_FILETYPE                  =
      tables
        data_tab                      = it_va42
    * EXCEPTIONS
    *   CONVERSION_ERROR              = 1
    *   INVALID_TABLE_WIDTH           = 2
    *   INVALID_TYPE                  = 3
    *   NO_BATCH                      = 4
    *   UNKNOWN_ERROR                 = 5
    *   GUI_REFUSE_FILETRANSFER       = 6
    *   OTHERS                        = 7
    if sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    endif.
    loop at it_va42.
    split it_va42 at ' ' into it_va42_a-vbeln
                              it_va42_a-mabnr.
    append it_va42_a.
    endloop.

    okay, this is your coding, but what is your question?

  • Dump error - SAPSQL_ARRAY_INSERT_DUPREC while executing Curr trans task

    Hi all,
    While executing currency translation task in SEM BCS, we are getting short dump - SAPSQL_ARRAY_INSERT_DUPREC. This error appears only for few consolidation units.
    we are on BI7 - SP 17.
    Please help me to sort out this issue.
    Thanks,
    Harry

    Hi,
    Usually, such kinds of errors are either
    1. consequences of inconsistencies )) in the data basis/ConsArea
    or
    2. program bugs.
    If you thoroughly searched for OSS notes and found nothing relevant,
    then,
    most likely, the guilty party is #1 == in this case, regenerate everything that may be relevant for the issue,
    starting from the data streams, data basis, ConsArea and so on.

  • Dump error in mb1a(SAPSQL_ARRAY_INSERT_DUPREC)

    Dear Friends,
                           We got a dump error(SAPSQL_ARRAY_INSERT_DUPREC)
                           when relesing particular material of the production order in mb1a. the detail error is as follows.
    ABAP runtime errors    SAPSQL_ARRAY_INSERT_DUPREC
    "SAPSQL_ARRAY_INSERT_DUPREC"
    "SAPLIEP1 " or "LIEP1U04 "
    "REMAINDER_OF_EQUI_POST"
    SAP Release.............. "46C"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "8x Intel 80686"
    Database type............ "ORACLE"
    Database owner........... "SAPR3"
    Character set............ "English_United State"
    SAP kernel............... "46D"
    Created on............... "Jul 10 2006 21:36:37"
    Created in............... "NT 4.0 1381 Service Pack 6 x86 MS VC++ 12.00"
    Database version......... "OCI_920_SHARE__OCI_7_API "
    Patch level.............. "2257"
    Patch text............... " "
    Transaction......... "MB1A "
    000010   FUNCTION REMAINDER_OF_EQUI_POST.
    000020   *"
    000030   ""Verbuchungsfunktionsbaustein:
    000040   *"
    000050   ""Lokale Schnittstelle:
    000060   *"       TABLES
    000070   *"              SEREQUZ STRUCTURE  EQUZ
    000080   *"              SERILOA STRUCTURE  ILOA
    000090   *"              SEREQKT STRUCTURE  EQKT
    000100   *"
    000110   DATA: RECORDS_POST LIKE SY-DBCNT.
    000120   * Anzahl der zu verbuchenden Sätze fest
    000130     DESCRIBE TABLE SEREQUZ LINES RECORDS_
    000140
    000150   * Zeitsegmente hinzufügen
    000160
         >     INSERT EQUZ FROM TABLE SEREQUZ.
    please let me know if you know the solution.
    Thanks and Regards,
    Shans.

    Go to transaction code OMBT, click view "Intervals" and make sure the number range for previous fiscal year and current fiscal year is not clashing.
    for example:
    Year        From Number   To Number      Current Number
    2010     4900000000     4999999999     5000533839
    2011      5000000000     5999999999     5000135509
    In the above case it will give this dump SAPSQL_ARRAY_INSERT_DUPREC. There may be other reason also.
    You can also follow this method
      Go to T-code SE16N and input table name MKPF.
      Step find:  Find the highest material document number.
      Go to T-code SNUM or SNRO.and Input object MATBELEG ( direct OMBT)
      Click on 'Number ranges' button.
      Click on 'Intervals' button.
      Check 'Current number'
      Now compare it with the highest material document number of STEP FIND.
      Change 'Current number' to a higher number.
    From my experience this normally happens when number ranged is transported from DEV to PRD accidentally during some IMG config.

  • 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.

  • Getting runtime error SAPSQL_ARRAY_INSERT_DUPREC In production

    Hi,
    can somebody help me regarding below issue.i am abaper.
    During SAP technical monitoring it has been noticed
    that there are many System dumps SAPSQL_ARRAY_INSERT_DUPREC other terms in the dump file are SALLZED7, LZED7F01, and UPDATE_TORGUE_TABLE. The user is WF-BATCH and is in a dialogue session. Error Message : SAPSQL_ARRAY_INSERT_DUPREC
    Report : SAPLZED7

    Hello ,
    Thanks for ur reply.
    i am providing detailed dump information , please guide me if anything u get.
    What happened?    The database system detected a deadlock and avoided it by rolling back
        your transaction.
    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 "/TOPFLOW/BDE_ZPRM_VERBUCHER" "(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:
        The database system recognized that your last operation on the database
        would have led to a deadlock.
        Therefore, your transaction was rolled back
        to avoid this.
        ORACLE always terminates any transaction that would result in deadlock.
        The other transactions involved in this potential deadlock
        are not affected by the termination.
    How to correct the error
        Database error text........: "ORA-00060: deadlock detected while waiting for
         resource"
        Internal call code.........: "[RSQL/DELE//TOPFLOW/BTANM ]"
        Please check the entries in the system log (Transaction SM21).
        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:
        "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
        "/TOPFLOW/SAPLBDE_ZPRM" or "/TOPFLOW/LBDE_ZPRMU25"
        "/TOPFLOW/BDE_ZPRM_VERBUCHER"
        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
    Information on where terminated    Termination occurred in the ABAP program "/TOPFLOW/SAPLBDE_ZPRM" - in
         "/TOPFLOW/BDE_ZPRM_VERBUCHER".
        The main program was "SAPMSSY1 ".
        In the source code you have the termination point in line 26
        of the (Include) program "/TOPFLOW/LBDE_ZPRMU25".
        The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
        procedure "/TOPFLOW/BDE_ZPRM_VERBUCHER" "(FUNCTION)", but it was neither
         handled locally nor declared
        in the RAISING clause of its signature.
        The procedure is in program "/TOPFLOW/SAPLBDE_ZPRM "; its source code begins in
         line
        1 of the (Include program "/TOPFLOW/LBDE_ZPRMU25 ".

  • SAPSQL_ARRAY_INSERT_DUPREC Error

    Hello all,
    I am getting the dump "SAPSQL_ARRAY_INSERT_DUPREC" in RSA3 (Extract checker)  while selecting GL Account hierarchy from F4, can anyone explain me the reason for this?
    Where can i see all the GL Account hierarchies in ECC System.
    Thanks in Advance.
    Sathish T.

    HI,
    reagrding the second part of your question, tables SETHEADER, SETNODE, SETLEAF store all the group information (hierarchy nodes, hierarchy relationsship, account numbers within hierarchy nodes).
    For account groups SETCLASS is 0109.
    Best regards, Christian

  • ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC on creation of a Purchase Req

    Hi Gurus,
    we are encountering an situation whereby, when a user creates and saves a PReq, the Preq number is displayed at the bottom, yet a termination message appears : '' ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC   ''
    have checked the number range and it doesnt seem to be that. May you please help
    Regards
    Nsovo

    Hello Mahee
    Normally there are two reasons for short dump SAPSQL_ARRAY_INSERT_DUPREC
    1, commit work in user exit;
    2. inconsistancy between the last number in the table and the current number in the number range;
    please check the short dump happens where inserts entry in table XXXX. check the lastest number in this table and compare it with the current number in number range object. In this case, the current number in number range is no larger than the lastest number in DB.
    The solution would be to manually adjust the current number in the number range object in SNRO.
    I hope the information is helpful.
    Regards,
    Jane

  • FI_GL LOAD GETTING INTO SHORTDUMP  "SAPSQL_ARRAY_INSERT_DUPREC"

    Hi Experts,
        We have FI_GL  DTP load from datasource PSA to  DSO, this was loading sucessfully till 25 of JUNE. From 28 th of June this load is getting into short dump "SAPSQL_ARRAY_INSERT_DUPREC"but surprisingly when i repeat this step the load getting successfull.  please let me know how can i stop this Shortdump in future.
    thanks in advance
    please see the below deatiled shortdump message.
    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
    Exception              CX_SY_OPEN_SQL_DB
    Date and Time          07.07.2010 04:15:51
         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 "SAPLSDDO" 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 "DD_DTEL_SET_PUT" "(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.)
         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"
              "SAPLSDDO" or "LSDDOU08"
              "DD_DTEL_SET_PUT"
              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
              "DD_DTEL_SET_PUT" "(FUNCTION)", 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 701
              Application server... "EUAX418-ZEP"
              Network address...... "10.129.6.97"
              Operating system..... "AIX"
              Release.............. "5.3"
              Hardware type........ "00C13D524C00"
              Character length.... 16 Bits
              Pointer length....... 64 Bits
              Work process number.. 18
              Shortdump setting.... "full"
              Database server... "EUAX418-ZEP"
              Database type..... "DB6"
              Database name..... "BWP"
              Database user ID.. "SAPBWP"
              Terminal.......... " "
              Char.set.... "C"
              SAP kernel....... 701
              created (date)... "Feb 15 2010 21:28:06"
              create on........ "AIX 2 5 00CB5A5B4C00"
              Database version. "DB6_81 "
              Patch level. 81
              Patch text.. " "
              Database............. "DB6 08.02., DB6 09."
              SAP database version. 701
              Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
              Memory consumption
              Roll.... 16192
              EM...... 16759392
              Heap.... 0
              Page.... 24576
              MM Used. 6041768
              MM Free. 2335128
         User and Transaction
              Client.............. 100
              User................ "ALEREMOTE"
              Language key........ "E"
              Transaction......... " "
              Transactions ID..... "4C27AEF624350086E10080000A810661"
              Program............. "SAPLSDDO"
              Screen.............. "SAPMSSY0 1000"
              Screen line......... 6
         Information on where terminated
              Termination occurred in the ABAP program "SAPLSDDO" - in "DD_DTEL_SET_PUT".
              The main program was "RSBATCH_EXECUTE_PROZESS ".
              In the source code you have the termination point in line 54
              of the (Include) program "LSDDOU08".
              The program "SAPLSDDO" was started as a background job.
              Job Name....... "BIDTPR_207115_1"
              Job Initiator.. "ALEREMOTE"
              Job Number..... 04140400
              The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
              procedure "DD_DTEL_SET_PUT" "(FUNCTION)", but it was neither handled locally
               nor declared
              in the RAISING clause of its signature.
              The procedure is in program "SAPLSDDO "; its source code begins in line
              1 of the (Include program "LSDDOU08 ".
                 leng         = 4     (0x00000004)
                 loop         = -1    (0xFFFFFFFF)
                 xtyp         = TYPE#000126
                 occu         = 25    (0x00000019)
                 access       = 1     (ItAccessStandard)
                 idxKind      = 0     (ItIndexNone)
                 uniKind      = 2     (ItUniqueNon)
                 keyKind      = 1     (default)
                 cmpMode      = 0     (cmpAllDynamic)
                 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         = 0x07000000606AC9E8
                 pgHook       = 0x0000000000000000
                 idxPtr       = 0x0000000000000000
                 shmTabhSet   = 0x0000000000000000
                 id           = 2095  (0x0000082F)
                 refCount     = 0     (0x00000000)
                 tstRefCount  = 0     (0x00000000)
                 lineAdmin    = 25    (0x00000019)
                 lineAlloc    = 25    (0x00000019)
                 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
         I

    Hi,
    This error due to that you are inserting duplicate records into DSO Key fields.
    Check your record in PSA and remove duplicate reocrds from PSA and try to run transformation again or you need to change primary key of your DSO to fit PSA data.
    Thank you,
    Regards,
    Govind.

Maybe you are looking for

  • Choosing s-video or composite

    Hi, my TV Card has a s-video, a composite and a tv-tuner input. I would like to know if there is a way to tell JMF which of these 3 inputs it should use. When I change the video input in the software of the manufacturer of my tv card, it also changes

  • Emailing Invite created in Flash doesn't work

    I created a flash invite for a client and cannot get it to deliver correctly through email. I've tried everything that I have found here and it won't show up in some of the emails that I have tested. (mine is the only one that works). I then tried ex

  • Dates for this sessiions are overdue-Sap ealy watch report

    Hi all, I have too many sessions scheduled for EWA one if my system in Landscape wit Red flags & i wanted to remove them as they are with very old Dates.I couldn't  manage to find any option pls advice me on that. How can i remove OLD EWA  with RED f

  • Suddenly can't download songs from iTunes store

    I'm on a Mac OS X 10.4.11, using iTunes 9.2.1 (4) and Safari 4.1.3.  This worked fine back in June, the last time I downloaded anything!  Now I am again trying to purchase from iTunes store, and repeatedly getting the message, 'Session timed out.  Tr

  • No file sharing option in Sharing pref panel

    Hi, MacBookPro 2.53 GHz Intel Core 2 Duo Mac OS X 10.6.8 Sharing pref pane (all accounts, even root) don't offer file sharing option. I suspect it happened after installing Amazon Cloud Share or TeamViewer. I uninstalled both but no change. I tried t