Process terminates in process chain

Hi ,
I do have 7 Meta Chains running under one of the Process parallely in BI 7.0. Unfortunately once in a while some of the process are terminating. Its start at the same time as all other of the process, but it does not executes the chain and turns red.
I don't even get a Process Monitor on that particular process nor a error message. i do can find the two clock symbols on that particular chain the LAST_SAVED & LAST_ACTIVATED. But the process chain does not run future.
If i run that particular process chain manually again it works properly.
Can you help me out, to run the process automatically .
Thanks in advance
Raju

Hi Akula,
When you Schedule a Process chain the Process will be ASSIGNED TO A WORKPROCESS OF aN Application server.
If there is no workprocess is avaliable in the Application server. the Process will be Terminated.
As you are scheduling Process chains there may be a Problem with Avaliability of work Processes.Check in sm50 for the no of application servers avaliable and check whether the work Processes are avaliable for each Application servers if you have more than one.
Try to avoid scheduling the Chains at the sametime.
hope it helps.
Thanks,
-Vijay

Similar Messages

  • Process Chain Terminates without errors

    Hi Experts,
    I'm facing a strange situation; my process chain terminates half way though. Loops are not completed till the end. e.g. it runs the Info Package and DTP then stop there, in some loops only the Info Package is run.
    There are no error messages.
    i can go to each process and update the targets manually. All are successful no errors.
    Does anyone have a clue as to why it will stop half way?
    Thanks
    FAzal

    Hi,
    Can you please tell whether this chanin has trabsported.
    In the RSPC in the process chain tab there is a option called reset to active version other wise activate the chain and try to start.
    hope this helps.
    Cheers,
    Vikram

  • Need help to terminate the local process chain

    hi
    Master DATA attribute local process chain was triggered twice in our daily master process chain. it is showing twice in the logs.
    Can any one help us to terminate the one replica of the running master data attribute local process chain.
    Thanks much in advance
    Raj
    Edited by: Gangaraju Eegu on Dec 10, 2008 3:03 PM

    Hi,
    Please check in execution selection any periodic job is running twice, so remove there.Double click on first node i.e. start and > Chamge Selections> Periodic Values.
    Or
    Find any event is triggering twice in a day?. and tehn cancle it.
    Thanks
    Reddy

  • 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 reset an failed asynchron abap-process in a process-chain?

    Hi specialists,
    I've got a process-chain which triggers (as one of its steps) an abap-program.
    The program should run asychroniously, so the process-chain waits until the programm reports its ending.
    When the abap-program fails/crashes/dumps, then the endings is never reported and the process-chain gets stuck.
    If I try to re-run that process-chain, it fails again with the message "Variant XYZ still executing from previous run".
    What I already found so far is the following note:
    The process chain management will not know if your program terminates!
    Thus if you re-start the chain, this will also terminate, because the old run would not have finished yet. To avoid this, you need to manually set the process in the chain log view in the process monitor to terminate before you start again.
    My problem: I cannot find any possibility to set the process to "terminate" in the chain's log view.
    Could you please gimme a hint where I can find that option?
    Best regards,
      Marco

    Hi,
    You can remove the process chain from scheduling before staring the process chain again.
    Also can edit the entries in RSPROCESSLOG table before running the process chain.
    Alternatively you can create a custom ABAP process type which handles the success as well as fail cases.
    Refer : [How To- Trigger subsequent processes in a Process Chain based on the Success or Failure of ABAP program|/people/balaji.venugopal/blog/2009/04/07/how-to-trigger-subsequent-processes-in-a-process-chain-based-on-the-success-or-failure-of-abap-program]
    Hope this helps,
    Regards,
    anil

  • Log from ABAP program in Process chain

    Hello.
    I have some problem. I wrote the ABAP program and insert this program in process chain. This program a correctly work, but I canu2019t view the steps of work this program. In help:
    You can write logs by outputting success messages. (Error messages terminate the task!)
    Example: MESSAGE s051(rsar) WITH 'Process successfully ended'.
    You can see these logs on the tab page Batch in the detail monitors of the process chain.
    I append this code to my program, but nothing in process chain.
    Help me, please - what code I need to insert in my program so that view this message in a process chain logs?

    We have an ABAP that outputs a message.  The output from the following code is visible when you click on a process chain step icon, and select the middle tab that says "Backg" for background.
    IF sy-subrc = 0.
        CONCATENATE text-005 p_date INTO l_msg SEPARATED BY space.
        MESSAGE i162(00) WITH l_msg.
      ELSE.
        CONCATENATE text-003 p_date INTO l_msg SEPARATED BY space.
        MESSAGE e162(00) WITH l_msg.
      ENDIF.

  • Process Chain execute method Schedule or Execute Synchronously

    Hi  Expert:
          When i execute  process chain, there are two methods to start the PC: Schedule and Execute Synchronously .
          Now i wander what the difference between the two methods for executing the PC.
          Thanks inadvance.

    Hi  prashanthk
        Thank your response,
        As a matter of fact, i execute the same process chain  which contains a  Abap Program with schedule and execute synchronously .
       But with schedule, the PC terminate with a error and execute synchronnusly the PC it run correctly .
      whether execute the PC in background or dialog mode can make a different result for the same PC .
      Now i  confused about this.
      Can you explain this in more detail for me?
    Thanks .

  • Short dump in program to trigger process chain

    Hi all,
    We have an ABAP program written to trigger a process chain...When we execute the ABAP program it goes on for a long time and then returns a short dump.It dosent even trigger the process chain.
    What could be the reason for this?
    Can someone please help...
    Regards,
    Suchitra

    Following is the error
    An exception occurred. This exception is dealt with in more detail bel
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', w
      neither
    caught nor passed along using a RAISING clause, in the procedure
      "Z_BPS_FIELDS_SET_REMOTE_C35" "(FUNCTION)"
    Since the caller of the procedure could not have expected this excepti
      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.)

  • Termination of Process chain

    Hi,
    I have a BIG process chain with a lot of master data loadings from the source system up to BI. All activities in the chain are linked to ALWAYS move on either the step was successful or failed.
    When I started the chain I immediately faced problems with the connections towards the source system. Therefore I wanted to terminate the entire process chain. I do not know how to do that.
    If I teminate the single activity (change the traffic light to red) it will move on to the next activity. When I check SM50 there are no background processes and in SM37 everything is marked "Finished".
    Regards,
    Sofie

    Hi Sofie,
    When the process chain is half run , the steps that have not run have jobs in the backgrounfd in the released state , witing for the event above them to schedule them.
    You can go to SM37 and delete all such jobs. The chain will have no jobs then to complete the chain completely and it will terminate with an error that an even was triggered but no job could process it.
    If you have chain set as periodic, new set of jobs would be release as soon as you delete the old ones. If this doesnt happen you would need to reactivate the chain.
    Also please ensure you are deleting only the jobs relevant to the chain and not any other unintended jobs.
    To see the jobs of the chain, you can right click any process variant in the active chain and click on command display all scheduled jobs.
    You said in SM37 everything is marked as finished, check if you had swithced on scheduled jobs in your selection , they are switched off by default.
    Also why are you desisting from changing the events to trigger only when successful?
    Hope this helps.
    Regards,
    Sunmit.

  • About process chain issue

    Dear BW Expert,
    We have argument about  PC load data by manual
    For the first time, I have change data selection in infopackage, then save and run the Process chain.
    When my PC not running finish, the one colleague  have change data selection of infopacakge, he also run that PC,  at the moment, the BW System prompt:
    Remove Pocess Chain from scheduling:
    Last  process chain run is still active
    If you continue, this run will be terminated
    The button are u201Ccontinueu201D & u201CCancelu201D
    We have argument  as following:
    I think that  if I click  u201CConinueu201D,  My PC will be terminated, my extract data will failure. Run PC like Run SM36 job.  when PC run finish, my log status is RED, him log status is GREEN. Because is refresh workbook, we canu2019t directly see the data change.
    he think that if Click u201CContinueu201D, My PC will be not terminated. my extract data will not faiure. 
    My process chain will be included him PC. He said, as long as him pc run successful, my also success. PC have change log technology,  I canu2019t understand.
    If so, But why my log status is RED, she log status is GREEN?  Whom view is right?
    Many Thanks,
    Best Regards
    Steve

    If you will activate the process chain when it is running then the process chain execution will terminate and the status of the chain will be red.
    So it is never advised to change a process chain object while it is running.
    You can check the data in objects, whether it has been loaded properly.

  • 50 Parallel Processing through Process Chain

    Hello Experts,
    Here is what I am trying to do.
    I want to create Process Chain which run 50(for ex.) Abap Program in parallel. I can create one by one through Process Types and select 'ABAP Program' and drag in the chain which is really very time consuming and tidious.
    Does anybody have better approach to do that ?? Any table where I can create all this parallel steps and put it in a chain ?? or copy each step and put it in parallel in chain ??
    Quick reply will be appreciated.
    Points are guaranteed for Right Resolution.
    Thanks in Advance.

    Hi "Believe in Jainism",
    Do you need to execute other process chain steps after executing the 50 abap programs? If not, why not just do the following:
    1) Create an ABAP program
    2) Inside the ABAP program, use the SUBMIT statement to execute the 50 ABAP programs in a background task.
    If you need to execute steps after the 50 abap programs, you can try to create a custom process type that executes the 50 ABAP programs in a background task and then monitors the statuses and then terminate only once all of these programs have executed successfully or if 1 has failed.
    Hope this helps.
    P.S. If you don't mind, may I ask why do you need to execute 50 ABAP programs in parallel?

  • Process Chain Creation

    Hi All,
    I am creating process chain.
    first i have given the name and description of the process chain --> then next step is insert start process So, i have clicked on new and given the name then click on continue --> so it populates one window  and it says that " Changes to Repository or cross-client Customizing are not permitted " AND ''Choose 'Display object' or 'Cancel'' .
    when i clicked on display object it shows "Changes cannot be made, display user only"
    and in brief it says that
    Diagnosis:
    In this logon client, any changes to the Repository and to cross-client Customizing objects are prohibited.
    System Response:
    The function terminates
    Procedure:
    If you still want to make the changes, contact the system administrator, who can allocate you a user in a client where you can make the changes.
    What should i do ?
    Regards,
    BI NEW

    Hi
    This is an authorization problem
    Check this link
    http://help.sap.com/saphelp_nw2004s/helpdata/en/35/c7e442e3c15704e10000000a155106/frameset.htm.
    Ask for proper authorization for creating the process chain.
    Hope this helps.
    Regards
    Shilpa

  • Process Chain Descheduling

    Hi All.
    Our system is pretty straight forward.  Our loads are controlled by a metachain that in turn kicks off other process chains.  Everything was running fine until all the sudden, some of the subchains stopped executing.
    They show up red in the metachain log but when I look at their individual logs, there are no logs for the day.  It's as if they were never touched by the metachain.
    When I manually trigger the subchain, they execute correctly.
    Better yet, it's not always the same set of chains that fail.  Sometimes, it's just an AR chain.  The next day AR and SL.  Later in the week ECCS fails.
    Obviously, it's rather annoying to have to go in every day and rerun part of the loads.  Does anyone have an idea what might be going on?
    Thanks,
    Adam

    Which support pack are you currently on. There are lot of program errors that were fixed recently with respect to metachains and subchains
    1106363       Correction: Repeat is not reported       19.05.2008
    1075876      Correction: Metachain is not set to active      15.02.2008
    1094400      Correction: Logging missing if the status is unclear      15.10.2007
    1063298      Correction: Incorrect status when you terminate subchain      11.06.2007
    1031742      Corr.: Message not sent to metachain if error before AND      25.04.2007
    1026907      Correction: Green instead of 'Terminated' in sub-subchain      28.03.2007
    1025647      Correction: Execution user not used for trigger w/ subchains      28.03.2007
    1007777      Correction: Process chain does not turn green after restart      11.12.2006
    970410      Correction: No synchronous update to subchains      25.10.2006
    893563      Correction: Deadlock on completion of a remote chain      30.01.2006
    601519      Correction: Subchains are not confirmed      18.11.2004
    Assign points if helfpul.
    Regards, Uday pothireddy

  • Set process chain status to green despite an error

    Hi everybody,
    I've made a process chain with an ODS activation. If there's an error, an AND process comes with a message to users.
    When an error occurs on the ODS activation, the process chain ends like I want but his status is red.
    How can I do to set the status to green ? Is that possible ?
    Thanks

    Ok,
    In that case it can be simplier than that.
    You need after activation of ODS in your chain have two branches, one with error and another one with success.
    In the case of the success the branch is connected to the rest of the chain and the rest of the chain will continue and remain green status for that chain as the overall result of the chain.
    In the case of error the new branch is connected to a process that will always terminate with sucess. As an example you could create a variant for roll-up of aggregates of an Infocube. In these variant do not select any InfoCube and mark the option End Process Sucessfully if No Aggregates Exist. This will always force this process to OK, green status, and therefore will always end your chain as green status even when the ODS activation fails
    Hope this helps.
    Diogo.

  • Process chain doesnt run in background! URGENT

    hey
    i have a issue with process chains.  we are using a meta chain which consists of 5 local chains, when i activate and schedule this meta chain from the RSPC transcation code the meta chain runs fine. But when i schedule this as a job in SM37 than the job terminates. the start variant of the meta chain has direct scheduling and a date / time on it at which we want to run the meta chain. the local chain start variants have "start using meta chain" option. I dont know whats the problem.
    The error message in the job log says: Job BI_PROCESS_TRIGGER has been started because of event. This job is not known, in the active version of the process chain" What does this mean ?
    Please let me know
    thanks
    Laura.
    Message was edited by:
            laura s

    Hi:
    You cannot start process chains from SM37, that is the problem.  You shouldn't have to...?  You have not indicated why you would go into SM37 instead of simply starting the chain in process chains - you can simply edit the process variant of the meta chain start process if you want to change the start time.
    Thanks for any points you choose to assign.
    Best Regards -
    Ron SIlberstein
    SAP

Maybe you are looking for

  • Calling parmeter form

    Hi All i have two forms first form is sale_order and next is order_tracker2 and the structure of table is like that SQL> desc sale_order; Name                                      Null?    Type ID                                        NOT NULL NUMBE

  • File receiver nl

    hello I have a JDBC to File scenario with content conversion csv file. in one of the field of the file I have a String. for some reason I might be getting a nl from the DB (or something else that cuase my file to go to the next line). I am using fiel

  • Any way to get split mono tracks in a Multicam Sequence?

    I have video from 4 different cameras which I'm trying to sync as a Multicamera clip. They sync great, but the audio mapping is not how I want it. All the cameras recorded 2 separate audio channels, but they appear upon import in Premiere as Stereo.

  • Is Photoshop CS3 compatible with Windows 8

    I am planing to get a new computer with windows 8 and I am currently using Photoshop CS3 in a windows XP computer.  Do I need to get the upgrade to CS6 or can I get an update for CS3 to work on Windows 8?

  • 45+hrs and gaining

    I've got a: MacBook Pro 2.8GHz Core 2 Duo 4GB running 10.5.7 iDVD 7.0.4 Quicktime 7.6 AND a: Mac Pro 2 x 2.8 Ghz Quad Core Xeon 6GB 8000 Mhz DDR2 10.5.6 iDVD 7.0.3 Quicktime 7.6 It is not easy to update the Mac Pro because of the nature of my busines