Process Chain gets unschedule after execution

I've created 1 event based process chain
i'm triggering this event from an abap program.
but after executing the process chain, the process chain gets unschedule automatically. I've used BP_RAISE_EVENT FM to trigger the event.
Thanks in advance.

Hi AG,
Can you please check the value of profile parameter:
rdisp/rfc_min_wait_dia_wp in you remote BW system. Is it 1?
If that is the case please increase the value to a more suitable value. This will determine the number of waiting dialog work processes in your system.
It is dynamically switichable. Please try this out and check the results.
Please award points if issue got solved.
Regards.
Ruchit.

Similar Messages

Process Chain running even after end date

Hi,
We are scheduling month end PC to run every 2 hours and also we have given end date for today evening.but process chain runs even after end date for every 2 hours.so we have to manually remove it from scheduling.
Any method how can PC stop on its own after end date .
Any help highly APPRECIATED
Thanks
Nilesh Pathak

There might be multiple release jobs for thie process chain.
So check the same. Right click on process chain --> Display scheduled jobs --> Here all the jobs logs of the chain will be available.. So check the same here...
As you have descheduled it now.. probably you may not be having it as the first release job might be moved to Schedule status as soon as the END date has reached and then second one might have gone when you have removed the chain from Schduling..
Anyway check the same.. and also check in SM37 whether any other user has triggered it manually today or not?

Selection Screen getting refreshed after execution..

Hello All,
I have a strange problem..
My selection-screen values are getting refreshed after execution and come back to selection screen. I am using normal ALV Fm to display the values. Can some suggest a possible reason?
Many thanks,
V Nair

No .. I have checked it..Selection variables are not getting refreshed.
My Code Below
REPORT yhr_icm_exception_report.
Type Pool declarations
TYPE-POOLS: slis,                                     "For AlV
            sdydo,                                    "Dynamic Documents
            icon.                                     "For ICON
Table declarations
TABLES : yhr_icm_exp_log,                             "ICM Exceptions Log
         yhr_icm_exp_hist.                            "ICM Exception History
Include Constants
INCLUDE   yhr_icm_constants .                         "Program to hold constants
Types declarations
*-To hold return field
TYPES: BEGIN OF ty_returntab.
        INCLUDE STRUCTURE ddshretval.                 "Interface Structure
TYPES: END OF ty_returntab.
*-To hold deletion records
TYPES : BEGIN OF ty_icm_del,
           tab_name      TYPE yhr_tabname,            "Internal table name
           objid         TYPE hrobjid,                "Object ID
           begda         TYPE begda,                  "Begin Date
           otype         TYPE otype,                  "Object Type
        END OF ty_icm_del.
*-Message details to be displayed
TYPES : BEGIN OF ty_message,
          msgnr          TYPE msgno,                 "System message number
          text           TYPE yhr_icm_exp_log-msgxx, "Message Text
        END OF ty_message.
*-To hold exception log
TYPES : BEGIN OF ty_icm_exp_log,
         msgno           TYPE msgnr,                  "Message number
         run_id          TYPE yhr_icm_erun_id,        "Exception Run ID
         delta_id        TYPE yhr_icm_run_id,         "Run ID
         record_type     TYPE yhr_icm_exp_type,       "Record Type
         otype           TYPE yhr_otype,              "Object Type
         objid           TYPE hrobjid,                "Object ID
         begda           TYPE begda,                  "Begin Date
         msgxx           TYPE msgxx,                  "Message
         status          TYPE yhr_icm_icon,           "Status
         delta_relevance TYPE yhr_delta_rel,          "Delta Relevance
        END OF ty_icm_exp_log.
*-To hold email attachment
TYPES: BEGIN OF ty_attach,
           text(500)     TYPE c,                      "Text
END OF ty_attach.
*To hold object type & text
TYPES :BEGIN OF ty_objid_text,
          objid          TYPE objid,                  "Object ID
          text           TYPE emnam,                  "Object Text
       END OF ty_objid_text.
*-To hold counter values - Exp , Del & historical
TYPES :BEGIN OF ty_count,
          exp(10)        TYPE c,                      "Exceptions
          del(10)        TYPE c,                      "Deletions
          hist(10)       TYPE c,                      "Historical Deletions
       END OF ty_count.
*- To hold lock details
TYPES : BEGIN OF ty_lock,
          live           TYPE c,                      "Live Callidus Program
          genr           TYPE c,                      "Generation Program
          exp            TYPE c,                      "Exception Program
        END OF ty_lock.
Range Declarations
RANGES :
       gr_objid          FOR hrp1001-objid,           "Range for Object ID
       gr_pernr          FOR pa0000-pernr.            "Range for Employee number
Internal Table Declarations
DATA : gt_records        TYPE STANDARD TABLE OF yhr_icm_exp_report,
       gt_objid_text     TYPE STANDARD TABLE OF ty_objid_text,
       gt_icm_exp_log    TYPE STANDARD TABLE OF ty_icm_exp_log,
       gt_returntab      TYPE STANDARD TABLE OF ty_returntab,
       gt_t777o          TYPE STANDARD TABLE OF t777o,
       gt_diff_tab       TYPE STANDARD TABLE OF yhr_icm_diff,
       gt_del_tab        TYPE STANDARD TABLE OF ty_icm_del, "#EC *
       gt_iattach        TYPE STANDARD TABLE OF ty_attach,
       gt_message        TYPE STANDARD TABLE OF ty_message,
       gt_fieldcat       TYPE slis_t_fieldcat_alv,
       gt_heading        TYPE slis_t_listheader,
       gt_exceptions     TYPE yhr_icm_exp_list_t,
       gt_events         TYPE slis_t_event.
Structure Declarations
DATA : gs_objid_text     TYPE ty_objid_text,
       gs_icm_exp_log    TYPE ty_icm_exp_log,
       gs_records        TYPE yhr_icm_exp_report,
       gs_exceptions     TYPE yhr_icm_exp_list,
       gs_count          TYPE ty_count,
       gs_fieldcat       TYPE slis_fieldcat_alv,            "#EC *
       gs_returntab      TYPE ty_returntab,
       gs_icm_exp_hist   TYPE yhr_icm_exp_hist,
       gs_iattach        TYPE ty_attach,
       gs_message        TYPE ty_message,                   "#EC *
       gs_layout         TYPE slis_layout_alv,
       gs_t777o          TYPE t777o,
       gs_lock           TYPE ty_lock.
Constant declarations
CONSTANTS:
       c_yes             TYPE string        VALUE 'YES',
       c_no              TYPE string        VALUE 'NO',
       c_true            TYPE c             VALUE 'X',
       c_deletions       TYPE c             VALUE 'D',
       c_delta_no        TYPE c             VALUE 'N',
       c_delta_yes       TYPE c             VALUE 'Y',
       c_historical      TYPE c             VALUE 'H',
       c_a               TYPE c             VALUE 'A',
       c_error           TYPE c             VALUE 'E',
       c_equal(2)        TYPE c             VALUE 'EQ',
       c_participants    TYPE c             VALUE 'P',
       c_include         TYPE c             VALUE 'I',
       c_position        TYPE c             VALUE 'S',
       c_organization    TYPE c             VALUE 'O',
       c_runlock         TYPE string        VALUE 'RUN_LOCK',
       c_parameter       TYPE string        VALUE 'P',
       c_selfield        TYPE string        VALUE 'SEL_FIELD' ,
       c_type            TYPE string        VALUE 'TYPE',
       c_topofpage       TYPE string        VALUE 'TOP_OF_PAGE',
       c_rectype         TYPE string        VALUE ' S_RECTYPE',
       c_objectkey       TYPE string        VALUE 'OBJECTKEY1',
       c_icon_green      TYPE string        VALUE '@08@',
       c_icon_red        TYPE string        VALUE '@0A@',
       c_icon_amber      TYPE string        VALUE '@09@',
       c_green           TYPE string        VALUE 'GREEN',
       c_amber           TYPE string        VALUE 'AMBER',
       c_red             TYPE string        VALUE 'RED',
       c_tabname         TYPE slis_tabname VALUE 'GT_RECORDS',
       c_structname      TYPE dd02l-tabname VALUE 'YHR_ICM_EXP_REPORT' ,
       c_siwb_wallpaper TYPE sdydo_key     VALUE 'SIWB_WALLPAPER',
       c_user_command    TYPE slis_formname VALUE 'F01_ALV_EVENT_USER_COMMAND',
       c_genname         TYPE trdir-name    VALUE 'YHR_ICM_GENERATE_EXCEPTIONS',
       c_expname         TYPE trdir-name    VALUE 'YHR_ICM_EXCEPTION_REPORT',
       c_pf_status       TYPE slis_formname VALUE 'SET_PF_STATUS',
       c_msg_class       TYPE string        VALUE 'YHR_ICM'.
Global Variable Declarations
DATA: gv_email_error    TYPE c,
       gv_email_sent     TYPE c,
       gv_exit           TYPE c.
Selection Screen - Block I
SELECTION-SCREEN:   BEGIN OF BLOCK b3 WITH FRAME TITLE text-s07.
SELECT-OPTIONS:
*- Run ID
    s_run_id             FOR yhr_icm_exp_hist-run_id,
*- Exception Type
    s_rectyp             FOR yhr_icm_exp_log-record_type NO INTERVALS,
*- Object Type
    s_otype              FOR yhr_icm_exp_log-otype NO INTERVALS,
*- Object ID
    s_objid              FOR yhr_icm_exp_log-objid NO INTERVALS,
*- Start Date
    s_begda              FOR yhr_icm_exp_log-begda,
*- Message number
    s_msgno              FOR yhr_icm_exp_log-msgno,
*- Message Text
    s_msgxx              FOR yhr_icm_exp_log-msgxx.
SELECT-OPTIONS:
*- Delta Relevance
   s_relv                FOR yhr_icm_exp_log-delta_relevance NO INTERVALS.
PARAMETERS:
*- Long Text
   p_ltext               AS   CHECKBOX DEFAULT ' '.
SELECTION-SCREEN:   END OF BLOCK b3.
Selection Screen - Block II
SELECTION-SCREEN:   BEGIN OF BLOCK b2 WITH FRAME TITLE text-s08.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(14) text-033.
*-Sucess
PARAMETERS:
p_stat_s               AS CHECKBOX.                  "D11K917251
SELECTION-SCREEN COMMENT 24(14) text-034.
*-Warning
PARAMETERS:
p_stat_w               AS CHECKBOX.                  "D11K917251
SELECTION-SCREEN COMMENT 48(15) text-035.
PARAMETERS:
*-Error
p_stat_e               AS CHECKBOX .                 "D11K917251
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN:   END OF BLOCK b2.
Selection Screen - Block III
SELECTION-SCREEN:   BEGIN OF BLOCK b4 WITH FRAME TITLE text-s09.
*-Email Details
PARAMETERS:
p_email(128)            TYPE c.
SELECTION-SCREEN:   END OF BLOCK b4.
             Selection Screen on value request.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR s_msgno-low.
PERFORM f4_message.
             Selection Screen Output.
AT SELECTION-SCREEN OUTPUT.
CHECK gt_returntab[] IS NOT INITIAL.
REFRESH s_msgno.
s_msgno-option = c_equal.
s_msgno-sign = c_include.
LOOP AT gt_returntab INTO gs_returntab.
    s_msgno-low = gs_returntab-fieldval.
    s_msgno-high = space.
    APPEND s_msgno.
ENDLOOP.
At Selection Screen for Validation
AT SELECTION-SCREEN.
CLEAR gv_email_error.
*-Validate Object Type
PERFORM validate_objecttype.
*-Validate Exception ID
PERFORM fetch_exp_header.
*-Validate Exception Type
PERFORM validate_exptype.
*-Validate Message Number
PERFORM validate_msgno.
*-Validate Message Type
PERFORM validate_msgtype.
*-Validate Delta
PERFORM validate_delta.
*-Validate Email ID
PERFORM validate_email USING p_email
                         CHANGING gv_email_error.
IF gv_email_error IS NOT INITIAL.
    MESSAGE e000(yhr_icm) WITH text-027.
ENDIF.
Initialization
INITIALIZATION.
Initialization
PERFORM initialization.
Start Of Selection
START-OF-SELECTION.
CLEAR : gv_email_error,
          gv_email_sent,
          gv_exit,
          gs_lock.
Try locking the main program
PERFORM lock_generation_program.
CHECK gs_lock IS INITIAL.
*-Fetch the messages stored in table
PERFORM fetch_item_records.
Read object type text.
PERFORM read_text.
Get Object Text
PERFORM get_object_text.
*-Fetch the current SAP messages
PERFORM fetch_records.
*-Update Delta Flag
PERFORM update_delta_flag.
*-Compare messages in table & in SAP
PERFORM compare_message.
If receiver is not blank, try sending out mail
PERFORM send_mail USING p_email.
End Of Selection
END-OF-SELECTION.
IF gv_exit IS NOT INITIAL.
    EXIT.
ENDIF.
*-Display ALV
PERFORM display_alv.
*-Build the event table for ALV display
PERFORM build_eventtab CHANGING gt_events[].
*-Fill the layout details
PERFORM layout_build .
Release all locks
PERFORM release_locks.
*-Finally call the grid display
PERFORM display_data.
*&      Form set_pf_status
      text
     -->RT_EXTAB   text
FORM set_pf_status USING rt_extab TYPE slis_t_extab.        "#EC *
Set PF Status
SET PF-STATUS 'STANDARD'.
ENDFORM. "Set_pf_status
*&      Form DISPLAY_ALV
      text
--> p1        text
<-- p2        text
FORM display_alv .
*- Use FM to create field catalog
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
    EXPORTING
      i_program_name         = sy-repid
      i_internal_tabname     = c_tabname
      i_structure_name       = c_structname
    CHANGING
      ct_fieldcat            = gt_fieldcat
    EXCEPTIONS
      inconsistent_interface = 1
      program_error          = 1
      OTHERS                 = 1.
IF sy-subrc = 1.
    MESSAGE i000(yhr_icm) WITH text-001.
    EXIT.
ENDIF.
*- Remove SEL Field Column as it is not required
DELETE gt_fieldcat WHERE fieldname = c_selfield.
*-If user chooses long text, activate icon
IF p_ltext IS INITIAL.
    LOOP AT gt_fieldcat INTO gs_fieldcat WHERE fieldname = c_type.
      gs_fieldcat-icon = c_true.
    ENDLOOP.
ENDIF.
ENDFORM.                    " DISPLAY_ALV
*&      Form BUILD_EVENTTAB
      text
     <--P_GT_EVENTS[] text
FORM build_eventtab CHANGING    p_events TYPE slis_t_event.
DATA: ls_event TYPE slis_alv_event.
*-Get the list of event for alv
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
    EXPORTING
      i_list_type = 0
    IMPORTING
      et_events   = p_events.
*-Add top of page event to event list
READ TABLE p_events
        WITH KEY name = slis_ev_top_of_page
         INTO ls_event.
IF sy-subrc = 0.
    MOVE c_topofpage TO ls_event-form.
    APPEND ls_event TO p_events.
ENDIF.
ENDFORM.                    " BUILD_EVENTTAB
*&      Form LAYOUT_BUILD
      text
--> p1        text
<-- p2        text
FORM layout_build .
gs_layout-zebra                = c_true.
gs_layout-colwidth_optimize    = c_true.
gs_layout-detail_popup         = c_true.
gs_layout-detail_initial_lines = c_true.
gs_layout-detail_titlebar      = text-044.
gs_layout-box_fieldname        = c_selfield.
ENDFORM.                    " LAYOUT_BUILD
*&      Form DISPLAY_DATA
      text
--> p1        text
<-- p2        text
FORM display_data .
*-Display ALV display
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      i_callback_user_command = c_user_command
      i_background_id          = c_siwb_wallpaper
      i_callback_program       = sy-repid
      i_callback_pf_status_set = c_pf_status
      i_default                = c_true
      i_save                   = c_a
      is_layout                = gs_layout
      it_fieldcat              = gt_fieldcat
      it_events                = gt_events
    TABLES
      t_outtab                 = gt_records.
ENDFORM.                    " DISPLAY_DATA
*&      Form FETCH_RECORDS
      text
--> p1        text
<-- p2        text
FORM fetch_records .
REFRESH : gt_diff_tab,
            gt_del_tab,
            gr_pernr,
            gt_exceptions.
CLEAR:    gs_icm_exp_log.
*-Get Employee details
PERFORM get_person_data.
*-Get Position Details
PERFORM get_position_data.
*-Get Organization Details
PERFORM get_org_data.
*-Get Exception current SAP exception list.
PERFORM get_exception_list.
*-Add deletion records
PERFORM filter_deletions.
ENDFORM.                    " FETCH_RECORDS
*&      Form top_of_page
      text
FORM top_of_page.                                           "#EC *
PERFORM build_comment   USING    gt_heading.
*-Display Use FM to display Top Of Page
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      it_list_commentary = gt_heading[].
CLEAR gt_heading.
ENDFORM.                    "TOP_OF_PAGE
*&      Form build_comment
      text
     -->P_HEADING text
FORM build_comment USING p_heading TYPE slis_t_listheader.
DATA: ls_hline     TYPE slis_listheader,
        lv_text(120) TYPE c.
*-Display report title
ls_hline-typ = c_historical.
WRITE text-006 TO lv_text.
ls_hline-info = lv_text.
APPEND ls_hline TO p_heading.
CLEAR ls_hline.
ls_hline-typ = c_s.
*-Remove leading & trailing spaces
CONDENSE : gs_count-del, gs_count-exp, gs_count-hist.
*-If the count is space then pass 0
IF gs_count-del = space.
    gs_count-del = 0.
ENDIF.
IF gs_count-exp = space.
    gs_count-exp = 0.
ENDIF.
IF gs_count-hist = space.
    gs_count-hist = 0.
ENDIF.
IF gs_lock IS INITIAL.
*-Display Deletion, Exception, Historical Count
    CONCATENATE text-037 gs_count-del
                 text-032 gs_count-exp
                 text-039 gs_count-hist
            INTO ls_hline-info SEPARATED BY space.
ELSEIF gs_lock-live IS NOT INITIAL.
    ls_hline-info = text-007.
ELSEIF gs_lock-genr IS NOT INITIAL.
    ls_hline-info = text-008.
ELSEIF gs_lock-exp IS NOT INITIAL.
    ls_hline-info = text-009.
ENDIF.
APPEND ls_hline TO p_heading.
CLEAR ls_hline.
ENDFORM.                    "BUILD_COMMENT
*&      Form INITIALIZATION
      text
--> p1        text
<-- p2        text
FORM initialization .
Read Previous run
SELECT MAX( run_id )
   INTO s_run_id-low
   FROM yhr_icm_exp_hist.                                  "#EC *
s_run_id-option = c_equal.
s_run_id-sign = c_include.
APPEND s_run_id.
s_rectyp-option = c_equal.
s_rectyp-sign = c_include.
s_rectyp-low = c_error.
APPEND s_rectyp.
s_rectyp-low = c_deletions.
APPEND s_rectyp.
PERFORM restrict_selections.
*Get the message from Message Class YHR_ICM
SELECT msgnr
         text
    FROM t100
    INTO TABLE gt_message
   WHERE arbgb = c_msg_class AND
         msgnr GT '000'.                                    "#EC *
ENDFORM.                    " INITIALIZATION
*&      Form F4_MESSAGE
      text
     <--P_P_MSGNO text
FORM f4_message.
F4 Help - Display all messages
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
      retfield        = 'MSGNR'
      dynpprog        = sy-cprog
      dynpnr          = sy-dynnr
      dynprofield     = 'S_MSGNR'
      window_title    = text-045
      value_org       = c_s
      multiple_choice = c_true
    TABLES
      value_tab       = gt_message
      return_tab      = gt_returntab
    EXCEPTIONS
      parameter_error = 1
      no_values_found = 2
      OTHERS          = 1.
IF sy-subrc = 1.
    MESSAGE i000(yhr_icm) WITH text-002.
    EXIT.
ELSEIF sy-subrc = 2.
    MESSAGE i000(yhr_icm) WITH text-003.
    EXIT.
ENDIF.
ENDFORM.                    " F4_MESSAGE
*&      Form VALIDATE_OBJECTTYPE
      text
--> p1        text
<-- p2        text
FORM validate_objecttype .
CHECK s_otype-low IS NOT INITIAL.
CONDENSE s_otype-low.
Validate object type to check whether user has entered only S, P or O
IF s_otype-low NE c_organization AND
        s_otype-low NE c_position AND
          s_otype-low NE c_participants .
    MESSAGE e000(yhr_icm) WITH 'Enter either S(Position), P(Person) or O(Org Unit)'(021).
ENDIF.
ENDFORM.                    " VALIDATE_OBJECTTYPE
*&      Form VALIDATE_OBJECTTYPE
FORM f01_alv_event_user_command USING r_ucomm LIKE sy-ucomm
                                      rs_selfield TYPE slis_selfield."#EC *
DATA : lv_answer TYPE c,
         lt_fields TYPE STANDARD TABLE OF sval,
         ls_fields TYPE sval.
*-Get the row user has selected in ALV list
READ TABLE gt_records INTO gs_records INDEX rs_selfield-tabindex.
CASE r_ucomm.
    WHEN 'DISP'.
      CASE gs_records-otype.
        WHEN 'S'.
          SET PARAMETER ID 'POT' FIELD gs_records-otype.
          SET PARAMETER ID 'PON' FIELD gs_records-objid.
          CALL TRANSACTION 'PP01_DISP' AND SKIP FIRST SCREEN.
        WHEN 'P'.
          SET PARAMETER ID 'PER' FIELD gs_records-objid.
          CALL TRANSACTION 'PA20' AND SKIP FIRST SCREEN.
        WHEN 'O'.
          SET PARAMETER ID 'POT' FIELD gs_records-otype.
          SET PARAMETER ID 'PON' FIELD gs_records-objid.
          CALL TRANSACTION 'PP01_DISP' AND SKIP FIRST SCREEN.
      ENDCASE.
    WHEN 'CHNG'.
      CASE gs_records-otype.
        WHEN 'S'.
          SET PARAMETER ID 'POT' FIELD gs_records-otype.
          SET PARAMETER ID 'PON' FIELD gs_records-objid.
          CALL TRANSACTION 'PP01' AND SKIP FIRST SCREEN.
        WHEN 'P'.
          SET PARAMETER ID 'PER' FIELD gs_records-objid.
          CALL TRANSACTION 'PA30' AND SKIP FIRST SCREEN.
        WHEN 'O'.
          SET PARAMETER ID 'POT' FIELD gs_records-otype.
          SET PARAMETER ID 'PON' FIELD gs_records-objid.
          CALL TRANSACTION 'PP01' AND SKIP FIRST SCREEN.
      ENDCASE.
    WHEN 'EMAIL'.
*-    Check whether email has already been sent
      IF gv_email_sent = c_true.
*-      If yes, then display pop up to confirm for mailing again
        CALL FUNCTION 'POPUP_TO_CONFIRM'
          EXPORTING
            text_question = text-041
            text_button_1 = text-042
            text_button_2 = text-043
          IMPORTING
            answer         = lv_answer
          EXCEPTIONS
            text_not_found = 1
            OTHERS         = 1.
        IF sy-subrc = 1.
          MESSAGE i000(yhr_icm) WITH text-004.
          EXIT.
        ENDIF.
*-     Continue only if user has selected Yes
        CHECK lv_answer = '1'.
      ENDIF.
*-      Add Email Field & Table
      ls_fields-tabname = 'SZA5_D0700'.
      ls_fields-fieldname = 'SMTP_ADDR'.
      APPEND ls_fields TO lt_fields.
*-      Use FM to get new Email ID
      CALL FUNCTION 'POPUP_GET_VALUES'
        EXPORTING
          popup_title     = text-s09
          start_column    = '5'
          start_row       = '5'
        TABLES
          fields          = lt_fields
        EXCEPTIONS
          error_in_fields = 1
          OTHERS          = 1.
      IF sy-subrc = 1.
        MESSAGE i000(yhr_icm) WITH text-004.
        EXIT.
      ENDIF.
*-    Get the Email user has entered
      READ TABLE lt_fields INTO ls_fields INDEX 1.
*-      Validate Email ID
      PERFORM validate_email USING ls_fields-value
                     CHANGING gv_email_error.
*-    If the flag is not initial, indicates possible error
      IF gv_email_error IS NOT INITIAL.
        MESSAGE i000(yhr_icm) WITH text-027.
        EXIT.
      ELSE.
      If no error, then try ending email
        PERFORM send_mail USING ls_fields-value.
      ENDIF.
    WHEN 'REFRESH'.
*-    Fetch the current SAP messages
      PERFORM fetch_records.
*-    Update Delta Flag
      PERFORM update_delta_flag.
*-    Compare messages in table & in SAP
      PERFORM compare_message.
*-    Refresh alv which is already displayed
      rs_selfield-refresh = c_true.
ENDCASE.
ENDFORM.                    "F01_ALV_EVENT_USER_COMMAND
*&      Form RESTRICT_SELECTIONS
      text
--> p1        text
<-- p2        text
FORM restrict_selections .
TYPE-POOLS sscr.
STATICS: lt_restrict TYPE sscr_restrict,
           lt_opt_list TYPE sscr_opt_list,
           ls_***      TYPE sscr_***.
Restrict the wage type selection so the user can only enter
values with the 'EQ' clause.
CLEAR lt_opt_list.
MOVE c_objectkey TO lt_opt_list.
MOVE c_true TO: lt_opt_list-options-eq,
                  lt_opt_list-options-bt,
                  lt_opt_list-options-cp,
                  lt_opt_list-options-eq,
                  lt_opt_list-options-ge,
                  lt_opt_list-options-gt,
                  lt_opt_list-options-le,
                  lt_opt_list-options-lt.
APPEND lt_opt_list TO lt_restrict-opt_list_tab.
MOVE: c_s         TO ls_***-kind,
        c_rectype   TO ls_***-name,
        c_include         TO ls_***-sg_main,
        space       TO ls_***-sg_addy,
        c_objectkey TO ls_***-op_main.
APPEND ls_***     TO lt_restrict-***_tab.
*-Restrict the values OTYPE
MOVE 'S_OTYPE'    TO ls_***-name.
APPEND ls_***      TO lt_restrict-***_tab.
*-Restrict the values OBJID
MOVE    'S_OBJID' TO ls_***-name.
APPEND ls_***      TO lt_restrict-***_tab.
*-Use FM to restrict the values
CALL FUNCTION 'SELECT_OPTIONS_RESTRICT'
    EXPORTING
      restriction = lt_restrict.
ENDFORM.                    " RESTRICT_SELECTIONS
*&      Form GET_PERSON_DATA
      text
--> p1        text
<-- p2        text
FORM get_person_data .
DATA : lt_del_tab TYPE STANDARD TABLE OF yhr_icm_diff.
SORT gt_icm_exp_log BY msgno .
gr_pernr-sign = c_include.
gr_pernr-option = c_equal.
LOOP AT gt_icm_exp_log INTO gs_icm_exp_log WHERE otype = c_participants AND
                                                   record_type = c_error.
*- Sort the table based on msgno and collect pernr
    gr_pernr-sign = c_include.
    gr_pernr-option = c_equal.
    gr_pernr-low = gs_icm_exp_log-objid.
    APPEND gr_pernr.
    CLEAR gr_pernr-low.
    AT END OF msgno.                                        "#EC *
*-    For the list of Pernr having same PERNR get the current exp details
      IF gs_icm_exp_log-msgno = c_msg_100.
*-      Export the pernr list to memory id & import in the below FM
*-      Selection of records should be based on values exported from here
        EXPORT gr_pernr TO MEMORY ID 'PERNR_0001'.
      Get Org Assignment 0001 Data
        CALL FUNCTION 'Y_HR_DIFF_PERNR_0001_DATA'
          EXPORTING
            period_begda = gs_icm_exp_hist-begda
            period_endda = gs_icm_exp_hist-endda
            refresh      = space
            UPDATE       = space
          TABLES
            diff_tab     = gt_diff_tab
            del_tab      = lt_del_tab.
    ELSEIF gs_icm_exp_log-msgno = c_msg_101. "Y_HR_DIFF_PERNR_0001_ORG_DATA
      ELSEIF gs_icm_exp_log-msgno = c_msg_102 .
        EXPORT gr_pernr TO MEMORY ID 'PERNR_0000'.
      Get Actions 0000 Data
        CALL FUNCTION 'Y_HR_DIFF_PERNR_0000_DATA'
          EXPORTING
            period_begda = gs_icm_exp_hist-begda
            period_endda = gs_icm_exp_hist-endda
            refresh      = space
            UPDATE       = space
          TABLES
            diff_tab     = gt_diff_tab
            del_tab      = lt_del_tab.
      ELSEIF gs_icm_exp_log-msgno = c_msg_103.
        EXPORT gr_pernr TO MEMORY ID 'PERNR_0002'.
      Get Personal Details 0002 Data
        CALL FUNCTION 'Y_HR_DIFF_PERNR_0002_DATA'
          EXPORTING
            period_begda = gs_icm_exp_hist-begda
            period_endda = gs_icm_exp_hist-endda
            refresh      = space
            UPDATE       = space
          TABLES
            diff_tab     = gt_diff_tab
            del_tab      = lt_del_tab.
      ELSEIF gs_icm_exp_log-msgno = c_msg_104.
        EXPORT gr_pernr TO MEMORY ID 'PERNR_0004'.
      Get Disability 0004 Data
        CALL FUNCTION 'Y_HR_DIFF_PERNR_0004_DATA'
          EXPORTING
            period_begda = gs_icm_exp_hist-begda
            period_endda = gs_icm_exp_hist-endda
            refresh      = space
            UPDATE       = space
          TABLES
            diff_tab     = gt_diff_tab
            del_tab      = lt_del_tab.
      ELSEIF gs_icm_exp_log-msgno = c_msg_105.
        EXPORT gr_pernr TO MEMORY ID 'PERNR_0006'.
      Get Addresses 0006 Data
        CALL FUNCTION 'Y_HR_DIFF_PERNR_0006_DATA'
          EXPORTING
            period_begda = gs_icm_exp_hist-begda
            period_endda = gs_icm_exp_hist-endda
            refresh      = space
            UPDATE       = space
          TABLES
            diff_tab     = gt_diff_tab
            del_tab      = lt_del_tab.
      ELSEIF gs_icm_exp_log-msgno = c_msg_106.
        EXPORT gr_pernr TO MEMORY ID 'PERNR_0007'.
      Get Planned Time 0007 Data
        CALL FUNCTION 'Y_HR_DIFF_PERNR_0007_DATA'
          EXPORTING
            period_begda = gs_icm_exp_hist-begda
            period_endda = gs_icm_exp_hist-endda
            refresh      = space
            UPDATE       = space
          TABLES
            diff_tab     = gt_diff_tab
            del_tab      = lt_del_tab.
      ELSEIF gs_icm_exp_log-msgno = c_msg_107.
        EXPORT gr_pernr TO MEMORY ID 'PERNR_0016'.
      Get Contract Element 0016 Data
        CALL FUNCTION 'Y_HR_DIFF_PERNR_0016_DATA'
          EXPORTING
            period_begda = gs_icm_exp_hist-begda
            period_endda = gs_icm_exp_hist-endda
            refresh      = space
            UPDATE       = space
          TABLES
            diff_tab     = gt_diff_tab
            del_tab      = lt_del_tab.
      ELSEIF gs_icm_exp_log-msgno = c_msg_108.
        EXPORT gr_pernr TO MEMORY ID 'PERNR_0077'.
      Get Additional Personal 0077 Data
        CALL FUNCTION 'Y_HR_DIFF_PERNR_0077_DATA'
          EXPORTING
            period_begda = gs_icm_exp_hist-begda
            period_endda = gs_icm_exp_hist-endda
            refresh      = space
            UPDATE       = space
          TABLES
            diff_tab     = gt_diff_tab
            del_tab      = lt_del_tab.
      ELSEIF gs_icm_exp_log-msgno = c_msg_109 .
        EXPORT gr_pernr TO MEMORY ID 'PERNR_0105'.
      Get Communications 0105 Data
        CALL FUNCTION 'Y_HR_DIFF_PERNR_0105_DATA'
          EXPORTING
            period_begda = gs_icm_exp_hist-begda
            period_endda = gs_icm_exp_hist-endda
            refresh      = space
            UPDATE       = space
          TABLES
            diff_tab     = gt_diff_tab
            del_tab      = lt_del_tab.
      ELSEIF gs_icm_exp_log-msgno = c_msg_110.
        EXPORT gr_pernr TO MEMORY ID 'PERNR_2001'.
      Get Absences 2001 Data
        CALL FUNCTION 'Y_HR_DIFF_PERNR_2001_DATA'
          EXPORTING
            period_begda = gs_icm_exp_hist-begda
            period_endda = gs_icm_exp_hist-endda

"Save Hierarchies" step in Process chain getting failed

Hello all,
After searching thoroughly through various links / forums, i failed to get a solution. So, I am posting here.
Recently we had a system copy. After that, in Quality system - "Save all Hierarchies" step in PC is getting failed.
I ran the process chain for 3 times till now:
1) Sometimes, it fails at batch monitor itself with UNCAUGHT_EXCEPTION runtime error.
2) Sometimes, it fails saying "Error 0 when reading PSA 1" & "No hierarchy found for the selection criteria entered".
When it fails with "Error 0 when reading PSA 1", then the above Hierarchy info package which is green automatically turns RED again with Process monitor saying "No PSA tables for the selection criteria".
I also went through the below sdn links.
http://scn.sap.com/thread/278794
http://scn.sap.com/thread/1753212
Things I did:
1) Tried replicating & activating the Transfer rules and Data source.
2) Repeated the step, as suggested in one post.
3) Refreshed the OLTP hierarchies in Infopack. selections.
I have attached a screenshot of a sample Data source which says Modified, though the transfer rules are active. Also, the process chain sample.
Please let me know, if someone has faced this issue. Whatelse did I miss? Any clue.
Thanks,
Vikranth.

Hi Raman,
I couldn't retransport, but i removed it from schedule and re-activated it. But, i think the issue lies with one of the Info objects 0PROFIT_CTR.
Because, when i tried to check the hierarchy structure; there are duplicate entries for one code. Can we delete one of them? Is it preferable.
I tried using OSS and used a program RSR_REPAIR_INFOAREAHIER but this showed no errors.
Any clue?
Thanks,
VIkranth

Problem in activating Process chain in Quality after transport

Hi All,
We have moved a set of process chain to Quality system.
When tried to activate the Process chain it is showing error in DTP.
The DTP name is same as in the Dev system.
So, we tried moving the DTP alone in another transport request.
Still the error exists. We also tried moving the process chain again.
We had tried importing only the structure and also the entire flow again.
Nothing worked.
Please suggest some solution.
Thanks in Advance,
Geetha

Thanks for yor reply.
Suman,
I have checked the Object Changeablity now in Dev system, I found it like Not changable for DTPA.
The DTP from DSO to Cube is fine, but we have problem with the DTP from DataSource to DSO.
Also, in the dev system when i clicked on Object Changeablity I get a popup like "System can be changed; settings not necessary".
Please suggest me like what must be done.
Prashantk & Arvind,
We imported the Process Chain along with the DTP first and we faced the problem.
So we imported the DTP alone again, but still we had the problem.
Again we imported the Process Chain after importing the DTPs.
So what i feel is DTPs must be there in the Quality, but why we have the problem persisting.
That too only for DTP from Data Source to DSO but not for the DTP from DSO to Cube.
Regards,
Geetha
Edited by: Geetha Devi Ramalingam on Jul 12, 2011 9:43 AM

Process Chain triggers Automatically after the Transport

Hello There,
I have a Process chain setup to load Transaction Data and the infopackets are set to "Immediate Start"..
When I transport these to Test environment, they are getting executed immediately after the transport..
Just wondering ,, this is what it intended to do.. because I don't want to run them after the transport.. is it something I am missing anything here ??
Your comments are much appreciated..
Thanks
Mavi

Mavi,
Once you click delete and save. The schedule is deleted. You could view via Maintain Start Variant -> Direct Scheduling button.
You will noticed that there is nothing schedule i.e. all tabs (immediate, specific datetime, etc) are not scheduled.
Answering to your question on modifiable in Test and Production box :
All you have to do is go to RSA1 -> Transport Connection -> Object Changeability -> Change the Process Chain objects to Changeable -> Save.
And you are done i.e. you could change the scheduling of the RSPC in Test and Production.
Remember to assign the point to the solution provided...:-)
Thanks.
Regards,
Lye

Local Process chain getting failed

Hi All,
My local process chain is getting failed due to the following error.
"Job started
Step 001 started (program RSPROCESS, variant &0000000068733, user ID ALEREMOTE)
Start process CHAIN EC_EW_M_COMPLAIN_ZMTCOCR1 in run 1HN75DVW2PG2WFU98WGFIXOGV of chain EC_EW_M_TRAN_L1
Communication buffer deleted from previous run F0CDWKC96L0O0D8NQBGVHYK9R (status X)
Chain Is OK
No job found
Job cancelled after system exception ERROR_MESSAGE"
How to resolve this issue?
Thanks,
Sathya

Hi
Communication buffer deleted from previous run F0CDWKC96L0O0D8NQBGVHYK9R (status X)
This means, the previous step is completed and system should get the status as G(green), but in above system got this as X(Deleted). That's why system unable to start the next process(your local chain).
I don't think, this is an issue with background processes.
try to repeat the step once again and monitor the display messages, if you get same error again check process type before this local chain.
Regards,
Venkatesh

Process chains get an error when run analysis process

When my PRD system‘s process chains run analysisi process, I gets below error message:
Error occurred when starting the parser: Error when opening an RFC connection (FUNCTION: 'R
Message no. BRAINOLAPAPI011
Diagnosis
Failed to start the MDX parser.
System Response
Error when opening an RFC connection (FUNCTION: 'R
Procedure
Check the Sys Log in Transaction SM21 and test the TCP-IP connection MDX_PARSER in Transaction SM59.
It's OK when i test the TCP-IP connection MDX_PARSER in Transaction SM59.
The Sys Log in Transaction SM21(error part):
M Wed Mar 19 09:22:50 2014
M *** ERROR => ThPOpen: ExecPopen("/usr/sap/BWP/DVEBMGS00/exe/tp" bwprd sapgw00 18933904 IDX=35, r, ..) returned -14 [thxxexec.c
M {root-id=532810645F5D12A0E1008000C0A8642F}_{conn-id=5328109B5F5D12A0E1008000C0A8642F}_5
A RFC 1878 CONVID 18933904
A   * CMRC=0 DATA=0 STATUS=0 SAPRC=0 RfcExecProgramKernel RfcRaiseErrorMessage cmd could not be started by OS (rc = 1)
A RFC> ABAP Programm: SAPLSTPA (Transaction: )
A RFC> User: JY-LKZ (Client: 900)
A RFC> Destination: CALLTP_AIX (handle: 8, DtConId: 530F4E5C30AF4550E1008000C0A8642E, DtConCnt: 0, ConvId: ,)
A RFC SERVER> RFC Server Session (handle: 1, 68443927, {5328109B-5F5D-12A0-E100-8000C0A8642F})
A RFC SERVER> Caller host:
A RFC SERVER> Caller transaction code: STMS (Caller Program: SAPLTMSC)
A RFC SERVER> Called function module: TMS_CI_START_SERVICE
A *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1887
FUNCTION: 'RfcExecProgramKernel'
RfcRaiseErrorMessage cmd could not be started by OS (rc = 1)
PROG ="/usr/sap/BWP/DVEBMGS00/exe/tp" bwprd sapgw00 18933904 IDX=35
[abrfcio.c    9213]
A {root-id=532810645F5D12A0E1008000C0A8642F}_{conn-id=5328109B5F5D12A0E1008000C0A8642F}_5
A TH VERBOSE LEVEL FULL
A ** RABAX: end RX_GET_MESSAGE
M
M Wed Mar 19 09:23:15 2014
M *** ERROR => ThPOpen: ExecPopen("/usr/sap/BWP/DVEBMGS00/exe/tp" bwprd sapgw00 18968493 IDX=61, r, ..) returned -14 [thxxexec.c
M {root-id=532810645F5D12A0E1008000C0A8642F}_{conn-id=532811958F750F10E1008000C0A8642F}_1
A RFC 1878 CONVID 18968493
A   * CMRC=0 DATA=0 STATUS=0 SAPRC=0 RfcExecProgramKernel RfcRaiseErrorMessage cmd could not be started by OS (rc = 1)
A RFC> ABAP Programm: SAPLSTPA (Transaction: )
A RFC> User: TMSADM (Client: 000)
A RFC> Destination: CALLTP_AIX (handle: 3, DtConId: 530F4E7830AF4550E1008000C0A8642E, DtConCnt: 0, ConvId: ,)
A RFC SERVER> RFC Server Session (handle: 1, 70212851, {53281195-8F75-0F10-E100-8000C0A8642F})
A RFC SERVER> Caller host:
A RFC SERVER> Caller transaction code: STMS (Caller Program: SAPLTMSC)
A RFC SERVER> Called function module: TMS_CI_START_SERVICE
A *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1887
FUNCTION: 'RfcExecProgramKernel'
RfcRaiseErrorMessage cmd could not be started by OS (rc = 1)
PROG ="/usr/sap/BWP/DVEBMGS00/exe/tp" bwprd sapgw00 18968493 IDX=61
[abrfcio.c    9213]
A {root-id=532810645F5D12A0E1008000C0A8642F}_{conn-id=532811958F750F10E1008000C0A8642F}_1
A TH VERBOSE LEVEL FULL
A ** RABAX: end RX_GET_MESSAGE.
ps.
1、IT's everything ok in the development system.
2、It’s ok when i repeat this analysis process .
3、It’s ok when i run this analysis process in analysis process designer.
4、Attachment is the sys log in sm21.
Thanks everyone.

Hi Vignesh.B,
Yes,it's not user's problem . But i don't think it APD's problem .Cause all APD has the same problem and .
Below is one of APD souce and target :
Hope this information is useful .
Regards,
Lian

Process Chain behavior changed after SP upgrade

Hi all, we've recently updated SP from SAP_BW 700, SAPKW70016 to SAPKW70021.
We realized about a particular process chain behavior:
We have many process chains configured to execute the next step "Always" (whatever it happens with the previous process).
This is the situation which changed:
BEFORE the upgrade:
If error raises on a process, this one remains "red" but the subsequent processes continues.
Once repaired (repeat/repair from the PC) the "crashed" process it is updated to "Green" status.
AFTER the upgrade:
If error raises on a process, this one remains "red" but the subsequent processes continues.
Once repaired (repeat/repair from the PC) the "crashed" process it is updated to "Green" status.
The remaining processes are executed once again (a new branch is generated). <- This is different
I want the "BEFORE the upgrade" behavior to keep working as always.
Do you know if there's some OSS note or tips of configs available to set this as my needs? (we have found the OSS Note 1398868 and implemented it, but the "effect" is not as we should expect for this case in particular).
I hope you can help. Thanks in advance and best regards,
Bernardo

I've found the OSS note: Note 1473491 - Chain not continued with termination and "ALWAYS" link; delivered with "SAPKW70025" corrections. It seems to be solving the issue I've originally mentioned. I'll perform some tests on this and update.
Regards,
Bernardo

Process chain not continue after successful node

Hi gurus,
   In my process chain I load data from R/3 to PSA and then execute DTP to DSO, all actions are serially. Usually our PC is running well. But recently the PC will stop after the loading to PSA was successfully end , which means in the log view of PC this node was green.
   I have checked the table RSPCPROCESSLOG, the entry here was also marked as successful. ( STATE = G )
   I have no idea why this PC wouldn't continue automatically?
Regards,
Aaron

Hi Ashok,
We have tried manually execute DTP to load data from PSA into DSO. Everything is OK. And as I mentioned, this PC was OK before! Sometimes when execute the failed PC several times, it runs correctly.
   This is why it looks so weird! I guess is it related to time exceed (load to PSA cost 2 hours) or some potential restrictions?
Regards,
Aaron

Issue in process chain with DTP after imported to production

Hi,
we have a issue with process chain.
after transportation DTP technical name is differ in prod and dev. process chain is went inactive.
i have read some related threads, i'm not find any suitable solution for this.
we don't have access to change process chain(they are not willing to open prod system)
could you please provide solution on this issue .
Thanks,
EDK....
Edited by: EdK666 on Oct 21, 2011 2:54 PM

Hi,
I have observed the behavior of changing technical name for DTP but still I think your process chain should not become inactive due to this. I think process chain somehow adjust the new technical name but anyways you should be able to change the DTP in process chain directly in production system.
If that is not possible you can just try re-transporting it.
Regards,
Durgesh.

Starting process chains using RSPC_API_CHAIN_START(parallel execution of processes)

Hi,
We've got sap bw 3.5 installed.
We are using API RSPC_API_CHAIN_START to start executing process chains.
IF we are using param I_SYNCHRONOUS = 'X' then if we have parallel processes in chains they are executing one by one.
IF we are setting param I_SYNCHRONOUS = '' then proccesses are executed in parallel. But I recieved all the prompts. For example for chosing background server.
and others.
Is there an opportunity to combine these 2 cases: not to have prompts and execute processes in parallel?
Thanks for you help
Andrey

Hi,
I tried without I_SYNCHRONOUS param, it works the same as I_SYNCHRONOUS = ''. I recieve all the promts.
Thanks for you help.

Check syntax of process chain get three variants with yellow color

When I click the "Checking View" picture icon to check the syntax of process chain, find there are three variants with yellow color. All the displaying msgs of the three yellow color variants says:
There must be a type "Read PSA and Update Data Target" process behind process "Execute InfoPackage" var.ZPAK_3WN4PJ43QNW7DC2Z3ZV532ZFF in the chain
What does this mean? Do we have to take care of the three yellow color errors?
Thanks

Hi Kevin,
Sometimes you need to instruct process chains explicitly. Even though you have it mentione din your InfoPackage, still it needs another process (and variant) to load from the PSA to the data target. In the RSPC screen where all the processes are listed on the left hand side, under Load Processes and Post Processing, you will find Read PSA and Update Data Target as the second process.
Hope this helps...

Conditioning Process Chain : weekly PC after a daily one

Hi
I am wondering the best way to implement a Metachain. I have daily process chain that should include a extra step (local proc chain) to be run on weekly bases.
I just dont know how to implement this situation....
If I use weekly in Start condition and put this local chain within the daily main one I dont know if would work or be the correct way to do it...
Once is defined as local I understand a chain has to be set as "Start using metachain " selection so no way to control it. yes?
appreciate your prompt replies!!!

Geo
I see my mistake i always consider to have only 1 initial SALES (daily) and from there ABAP ....
So lets say it would be:
Meta 1(event daily) = Meta Sales + Meta Forecasting &
Meta 2 (event weekly) = Meta Sales + Prop Factors PC + Meta Forecasting
But still face 2 problems:
a) when I define meta 1 for Sales & Forecasting and then second meta using same process chains for SALES and FORECASTING in meta 2 it tells me that they are repetitive and should choose only one place and delete them from 1 of them ???
b) Meta sales should be activated by another event as they are 5 sales uploads types...
Appreciate your lasts comments!! thank you all!

Enqueue process not getting start after failover

Hi Experts,
We are facing problem suddenly after doing failover test. This problem arrived today only. Before it was happening successfully.
Before failover everything is running fine on primary node. After doing failover the enqueue sever process on ASCS instance is not starting in secondary node.
It's also showing license will expire on 16.11.2010, but system has
already license installed.
The ASCS start logs are showing as below -
Execute Pre-Startup Commands
(12517410) Local: /usr/sap/PRD/SYS/exe/run/sapcpe pf=/usr/sap/PRD/SYS/profile/PRD_ASCS00_sapprd1 list:/usr/sap/PRD/SYS/exe/run/scs.lst
(11534542) system(/usr/sap/PRD/SYS/exe/run/sapcpe pf=/usr/sap/PRD/SYS/profile/PRD_ASCS00_sapprd1 list:/usr/sap/PRD/SYS/exe/run/scs.lst) returns 4
(12517412) Local: /usr/sap/PRD/SYS/exe/run/sapcpe pf=/usr/sap/PRD/SYS/profile/PRD_ASCS00_sapprd1 list:/usr/sap/PRD/SYS/exe/run/sapcrypto.lst
(11534542) system(/usr/sap/PRD/SYS/exe/run/sapcpe pf=/usr/sap/PRD/SYS/profile/PRD_ASCS00_sapprd1 list:/usr/sap/PRD/SYS/exe/run/sapcrypto.lst) returns 255
(12517414) Local: rm -f ms.sapPRD_ASCS00
(12517416) Local: ln -s -f /usr/sap/PRD/ASCS00/exe/msg_server ms.sapPRD_ASCS00
(12517418) Local: rm -f en.sapPRD_ASCS00
(12517420) Local: ln -s -f /usr/sap/PRD/ASCS00/exe/enserver en.sapPRD_ASCS00
Starting Programs
24.10.2010 18:39:42
ShmDetach
OK
(12517424) Starting: local ms.sapPRD_ASCS00 pf=/usr/sap/PRD/SYS/profile/PRD_ASCS00_sapprd1
(8585426) Starting: local en.sapPRD_ASCS00 pf=/usr/sap/PRD/SYS/profile/PRD_ASCS00_sapprd1
(11534542) Waiting for Child Processes to terminate.
(11534542) **** 2010/10/24 18:39:42 Child 8585426 terminated with Status 1 . ****
(8585426) **** 2010/10/24 18:39:42 No RestartProgram command for program 1 ****
It's unable to start enqueue server process.
Please suggest your solutions.
Regards,
Ramesh.

Hi Gagan,
The enqueue problem is resolved. Atually 2 days before we increased RAM of primary node by 1GB, and that was creating issue. we revert it back and again did a switchover and everything is running fine. It was strange that my secondary node is getting affected due to increasing the RAM in primary node.
Regarding license key, can you please provide me detail steps to resolve it. I have gone through installation doc but couldnt find it. Now Tcode slicense is showing another hardware key in my DI system. Do I need to get seperate permenant license key for DI by registering DI host and new hardware key??
Just confirm and also add some of your expert suggetsions.
Regards,
Ramesh.
Edited by: ramesh_basis on Oct 25, 2010 7:26 AM

Process Chain gets unschedule after execution

Similar Messages

Maybe you are looking for