Activating parallel processing in SAINT when import is active

Hi All,
I am installing EHP3 for ECC 6.0 at the moment and the import takes a long time. Does anyone know if I can adjust the parallel import options in SAINT after I stop the import?
So
1. Stop the import.
2. adjust settings.
3. restart the import.
I'm not sure that the settings options are released for editing when the import is canceled.
I first want to make sure before killing the running import.
Thanks,
Arjan

Hi Arjan,
What is the number of parallel R3trans processes are you using ? SAP does not recommends more than 5. Check SAP note 1083533. See below extract from this note: 
Number of parallel processes during the installation: You can reduce the duration of the installation by using parallel processing for several R3trans processes. Five parallel R3trans processes are known to be effective. We do not recommend several
background processes for parallel processing of the method execution (otherwise, it may result in a termination as described
in section 5)
Also, for this it is also recommended to use latest R3trans and tp. for this check SAP note 1110690.
Thanks
Sunny

Similar Messages

  • VAMT 3.0 Database Merge Error When Importing Product Activation

    Hi all,
    We are attempting to combine data currently stored in local sql server from several VAMT installs into a single database on a SQL Server 2008.
    We export the data into a cilx file from the local database, change the VAMT connection to the new server database successfully, then try to import the file back into that new database.  We get the error:
    The MERGE statement conflicted with the FOREIGN KEY constraint "FK_ActiveProduct_AvailableProduct". The conflict occurred in database "VAMT", table "base.AvailableProduct".
    Being a database guy, I can see that the problem is that there is a missing reference key from AvailableProduct when the script attempts to load products into ActiveProduct.
    Has anybody found a way around this?  We have tried first importing a Products Only file, but that got the same error.  I am considering having to reorder the stored procedure that loads the data, although I don't much like the idea of having to
    rewrite black box code.
    Thanks,
    Reinis

    Hi,
    Here is the guidance:
    Import-VamtData
    http://technet.microsoft.com/en-us/library/hh852150.aspx
    Check the integrity of SQL server database.
    For SQL specified issue you can also ask here:
    http://social.technet.microsoft.com/Forums/sqlserver/en-US/home?category=sqlserver

  • Parallel processing using ABAP objects

    Hello friends,
                        I had posted in the performance tuning forum , regarding a performance issue problem , I am reposting it as it involves OO concept .
    the link for the previous posting
    Link: [Independent processing of elements inside internal table;
    Here is the scenario,
    I have a internal table with 10 records(indepentent) , and i need to process them .The processing of one record doesnt have any influence on the another . When we go for loop , the performance issue is that , the 10 th record has to wait until the 9 records get processed even though there is no dependency on the output.
    Could some one tell a way out to improve the performance..
    If i am not clear with the question , i would explain it still clearer...
    A internal table has 5 numbers , say( 1,3,4,6,7)
    we are trying to find square of each number ,,,
    If it is a loop the finding of suare of 7 has to wait until 6 is getting completed and it is waste of time ...
    This is related to parallel processing , I have refered to parallel processing documents,But I want to do this conceptually ..
    I am not using conventional procedural paradigm but Object orientedness...I am having a method which is performing this action .What am I supposed to do in that regard.
    Comradely ,
    K.Sibi

    Hi,
    As examplified by Edward, there is no RFC/asynchronous support for Methods of ABAP Objects as such. You would indeed need to "wrap" your method or ABAP Object in a Function Module, that you can then call with the addition "STARTING NEW TASK". Optionally, you can define a Method that will process the results of the Function Module that is executed asynchronously, as demonstrated as well in Edward's program.
    You do need some additional code to avoid the situation where your program takes all the available resources on the Application Server. Theoretically, you cannot bring the server or system down, as there is a system profile parameter that determines the maximum number of asynchronous tasks that the system will allow. However, in a productive environment, it would be a good idea to limit the number of asynchronous tasks started from your program so that other programs can use some as well.
    Function Group SPBT contains a set of Function Modules to manage parallel processing. In particular, FM SPBT_INITIALIZE will "initialize" a Server Group and return the maximum number of Parallel Tasks, as well as the number of free ones at the time of the initialization. The other FM of interest is SPBT_GET_CURR_RESOURCE_INFO, that can be called after the Server Group has been initialized, whenever you want to "fork" a new asynchronous task. This FM will give you the number of free tasks available for Parallel Processing at the time of calling the Function Module.
    Below is a code snippet showing how these Function Modules could be used, so that your program always leaves a minimum of 2 tasks for Parallel Processing, that will be available for other programs in the system.
          IF md_parallel IS NOT INITIAL.
            IF md_parallel_init IS INITIAL.
    *----- Server Group not initialized yet => Initialize it, and get the number of tasks available
              CALL FUNCTION 'SPBT_INITIALIZE'
              EXPORTING
                GROUP_NAME                           = ' '
                IMPORTING
                  max_pbt_wps                          = ld_max_tasks
                  free_pbt_wps                         = ld_free_tasks
                EXCEPTIONS
                  invalid_group_name                   = 1
                  internal_error                       = 2
                  pbt_env_already_initialized          = 3
                  currently_no_resources_avail         = 4
                  no_pbt_resources_found               = 5
                  cant_init_different_pbt_groups       = 6
                  OTHERS                               = 7.
              md_parallel_init = 'X'.
            ELSE.
    *----- Server Group initialized => check how many free tasks are available in the Server Group
          for parallel processing
              CALL FUNCTION 'SPBT_GET_CURR_RESOURCE_INFO'
                IMPORTING
                  max_pbt_wps                 = ld_max_tasks
                  free_pbt_wps                = ld_free_tasks
                EXCEPTIONS
                  internal_error              = 1
                  pbt_env_not_initialized_yet = 2
                  OTHERS                      = 3.
            ENDIF.
            IF ld_free_tasks GE 2.
    *----- We have at leasr 2 remaining available tasks => reserve one
              ld_taskid = ld_taskid + 1.
            ENDIF.
        ENDIF.
    You may also need to program a WAIT statement, to wait until all asynchronous tasks "forked" from your program have completed their processing. Otherwise, you might find yourself in the situation where your main program has finished its processing, but some of the asynchronous tasks that it started are still running. If you do not need to report on the results of these asynchronous tasks, then that is not an issue. But, if you need to report on the success/failure of the processing performed by the asynchronous tasks, you would most likely report incomplete results in your program.
    In the example where you have 10 entries to process asynchronously in an internal table, if you do not WAIT until all asynchronous tasks have completed, your program might report success/failure for only 8 of the 10 entries, because your program has completed before the asynchronous tasks for entries 9 and 10 in your internal table.
    Given the complexity of Parallel Processing, you would only consider it in a customer program for situations where you have many (ie, thousands, if not tens of thousands) records to process, that the processing for each record tends to take a long time (like creating a Sales Order or Material via BAPI calls), and that you have a limited time window to process all of these records.
    Well, whatever your decision is, good luck.

  • LabVIEW 8.5 Parallel processing

    I am using lv 8.If i use 2 file dialog in the vi.Can i get 2 simultaneous pop or is it still the same ie one at a time in 8.5?

    muks wrote:
    same is the case when i use a control instead of dialog right?
    What do you mean by "same"? What kind of control? can you be a bit more specific? Most users i know can only press one control at any given time, so parallel processing is not that important here. Of course the UI runs in it's own thread, so other things can happen at the same time in the background.
    muks wrote:
    Then what do you exactly mean by multi threading and parallel processing?
    The only person in the thread that mentioned parallel processing was you (in the title) and multithreading was never mentioned here? Are you by any chance referring to a different thread or post with this part of your question?
    In any case, LabVIEW was multithreaded way before version 8.0, so you won't see much of a difference going to 8.5 in this respect. Of course there are other nice new features that make upgrading worth it.
    What kind of problem are you actually trying to solve?
    LabVIEW Champion . Do more with less code and in less time .

  • Parallel process in Application engine

    could any one explain me what is parallel process in Application engine where temp table is use?
    give me with example?

    Parallel processing is used when considerable amounts of data must be updated or processed within a limited amount of time, or batch window. In most cases, parallel processing is more efficient in environments containing partitioned data.
    To use parallel processing, partition the data between multiple concurrent runs of a program, each with its own dedicated version of a temporary table (for example, PS_MYAPPLTMP). If you have a payroll batch process, you could divide the employee data by last name. For example, employees with last names beginning with A through M get inserted into PS_MYAPPLTMP1; employees with last names beginning with N-Z get inserted into PS_MYAPPLTMP2.
    To use two instances of the temporary table, you would define your program (say, MYAPPL) to access to one of two dedicated temporary tables. One execution would use A-M and the other N-Z.
    The Application Engine program invokes logic to pick one of the available instances. After each program instance gets matched with an available temporary table instance, the %Table meta-SQL construct uses the corresponding temporary table instance. Run control parameters passed to each instance of the MYAPPL program enable it to identify which input rows belong to it, and each program instance inserts the rows from the source table into its assigned temporary table instance using %Table. The following diagram illustrates this process:
    Multiple program instances running against multiple temporary table instances
    There is no simple switch or check box that enables you to turn parallel processing on and off. To implement parallel processing, you must complete the following set of tasks. With each task, you must consider details regarding your specific implementation.
    Define and save temporary table records in PeopleSoft Application Designer.
    You don't need to run the SQL Build process at this point.
    In PeopleSoft Application Engine, assign temporary tables to Application Engine programs, and set the instance counts dedicated for each program.
    Employ the %Table meta-SQL construct so that PeopleSoft Application Engine can resolve table references to the assigned temporary table instance dynamically at runtime.
    Set the number of total and online temporary table instances on the PeopleTools Options page.
    Build temporary table records in PeopleSoft Application Designer by running the SQL Build process.

  • CIF compare/reconcile -- Parallel process profile in R/3

    Dear experts, I'm opening a complete new discussion with this topic...
    does anybody have experience setting up parallel processing for CCR?
    I did create 2 parallel profiles in customizing (1 for APO and 1 for R3) and I executed the report in background.
    Most of the performance time that the report uses is spent on R3 side reading tables like VAPMA and VLPMA. In order to improve runtime performance I set up the 2 parallel process profiles as shown above (defiining server, number of processes and block size in customizing following SAP recommendations already).
    In APO I am perfectly able to see how more than one process is being triggered and therefore parallelization works.
    Nevertheless, I never see in R/3 the same thing happening. No matter how I define the parallel process profile for R/3, I always see one unique process in transations SM51 and SM66 on this system as shown below.
    Is there a specific setting I need to maintain to achieve this process parallelization in R/3? Is it even possible to split processes in R3? and if not, what is the purpose of having Parallel Process profiles in R3?
    Thanks for your support
    Salvador

    Hi Rupesh,
    indeed a good remark, but we already got this note in R3 upfront.
    Regarding VBBE, we did ran CCR without it being selected. This has an equivalent effect to running report SDRQCR21 as it will also update index tables. It is recommented by SAP to schedule it on a regular basis and that's the direction we took.
    These ones certainly improve performance significantly, but still we are wondering about parallel processing in R3.
    If there is a profile for parallel process available in CCR, why are we not able to see parallel processes in R3 when executing the report? This should also help in improving even more performance if we could get it working properly...
    Further information...
    Is maybe someone aware of the following points?
    - RFC call is using DIA processes. Are these suitable for parallellization in any case?
    - what are the profile parameters that need to be set up (RZ10) and is there a direct link with parallel processing? For example, I notice that rdisp/rfc_pool_size is equal to zero in my R3 system but it is 10% in APO.
    - are there other parameters like rdisp/rfc* that can really block me from getting parallel processes?
    Thanks for your interventions
    Salvador
    Message was edited by: Salvador García

  • Parallel processing for compression

    Hello Experts,
    Is there a way to control the number of parallel processes (background) used when compressing a request in a cube?
    Sunil

    Hi Sunil,
    Kindly have a look at below link, hope this helps.
    http://help.sap.com/saphelp_nw70/helpdata/en/c5/40813b680c250fe10000000a114084/content.htm
    Regards,
    Mani

  • Parallel process run independently, but do not stop when vi completes

    So I posted a problem yesterday about getting 'elapsed time' express vi to provide updates from a sub-vi to the calling vi. It was suggested that I create a parallel process in the sub-vi that will run the elapsed time function at the same time the other processes are running. I tried to implement this idea, but ran into a problem. The elapsed time process is a While loop paralleled with the main While loop in the sub-vi, It updates every second, based on my time delay, and when I view the running sub-vi, the elapsed time indicator is updating as it should. The calling vi, however, is not seeing these updates. I have wired an indicator to the sub-vi icon, but does not change until the sub-vi finishes.
    Also, the other problem with the parallel process is that it runs forever, regardless of the other loop finishing. I have tried to wire an or'd bool to the stop inside the While loop, but when I do that, the elapsed time process does not start. 
    I have tried data binding a shared variable in the project, and then dragging that to my calling vi, but again I get no updates on the elapsed time.
    Any ideas????

    A VI must finish looping before it has an available output (the terminal on the sub-vi icon).   Research how to communicate between loops. What you are doing can be accomplished with Notifiers (that's what I'd use), Queues, or Global/Shared Variables.
    Your issues appear to be due to a lack of understanding of the LabVIEW data-flow paradigm. Check out the Producer / Consumer example. Post code here and see if one of us can give more guidance.
    Richard

  • Parallel processing using flow activity

    Hey, I have two input directories in the same process for two different partnerlinks and I want to use these two directories to input two flat files to two tables simultaneously.I tried using flow to do this parallel process. But the process when uploaded onto the console takes one input file and it fails. It changes the state of the process to 'off'. Can anyone let me know as to what could be the reason? thanks and regards

    Hi can someone help me please

  • When importing files into fcpx from go pro hero2, some are importing as .mov and some as .mp4. when making a multi cam clip it will only add one type, if you try and add the other it says camera clip cannot be processed.

    when importing files into fcpx from go pro hero2, some are importing as .mov and some as .mp4. when making a multi cam clip it will only add one type, if you try and add the other it says camera clip cannot be processed. need to figure out why it randomly imports differently, or how to add different file tyoes to multi cam.

    here is one that is imported and stays .mp4. the specs are same as original file before import.
    here is one that has changed somehow during import. specs on original file are same as above, but once it is imported it changes to this in event folder, and others randomly keep the above specs.

  • Error durring DDIC activation phase when Importing SP13 on ERP 6.0 IDES

    Hi.
    I´m applying SP13 on ERP6.0 IDES. Durring the DDIC activation phase I encounter several warnings and a few errors that prevent me from completing. I have been unable to find notes that explains this error - I hope you can help me out.
    1 ED0306       "Final log"
    1 ED0301 *************************************************************************
    1 EDO578XFollowing objects not activated/deleted or activated/deleted w. warning:
    1EEDO519X"Table" "WB2_KEY_CHANGE" could not be activated
    1EEDO519 "Table" "WB2_KOMG" could not be activated
    1EEDO519 "Table" "WCB_COND_DISP" could not be activated
    1EEDO519 "Table" "WVKOMP" could not be activated
    1EEDO519 "Table Type" "WB2_KEY_CHANGE_STAB" could not be activated
    1EEDO519 "Table Type" "WB2_KOMG_STAB" could not be activated
    1EEDO519 "Table Type" "W_TT_KOMP" could not be activated
    2WEDO517 "Table" "KONBBYH" was activated (error in the dependencies)
    2WEDO517 "Table" "WRF_KOMG_MATGRP_AP01" was activated (error in the dependencies)
    2WEDO517 "Table Type" "WB2_CHANGED_FIELDS_STAB" was activated (error in the dependencies)
    2WEDO517 "Table Type" "WB2_VAKE_TAB" was activated (error in the dependencies)
    2WEDO549 "Domain" "J_3R_BRAND" was activated (warning for the dependent tables)
    2WEDO549 "Domain" "P02_NAHVNR" was activated (warning for the dependent tables)
    2WEDO549 "Data Element" "BCA_DTE_DIM_ACEXT" was activated (warning for the dependent tables)
    2WEDO549 "Data Element" "BCA_DTE_DIM_GROUP_OBJECT" was activated (warning for the dependent tables)
    2WEDO549 "Data Element" "BCA_DTE_DIM_REF_CATEGORY" was activated (warning for the dependent tables)
    2WEDO549 "Data Element" "HRCCE_CURR_ASSIGNMENT" was activated (warning for the dependent tables)
    2WEDO549 "Data Element" "HRCCE_QUOTA_SHARED" was activated (warning for the dependent tables)
    2WEDO549 "Data Element" "HRCCE_VALID_FOR" was activated (warning for the dependent tables)
    2WEDO549 "Data Element" "L_EVPTYP" was activated (warning for the dependent tables)
    2WEDO549 "Data Element" "PKR_RENUM" was activated (warning for the dependent tables)
    2WEDO549 "Table" "BCA_STR_DIM_OI_KEYS" was activated (warning for the dependent tables)
    2WEDO549 "Table" "BCA_STR_DIM_REF_REVERSAL" was activated (warning for the dependent tables)
    2WEDO549 "Table" "BCA_STR_DIM_REF_REVERSAL_KEYS" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PSHD1" was activated (warning for the dependent tables)
    2WEDO549 "Table" "SFW_BF" was activated (warning for the dependent tables)
    2WEDO549 "Table" "SI_FKKMAKOR" was activated (warning for the dependent tables)
    2WEDO549 "Table" "SI_FKKOPS" was activated (warning for the dependent tables)
    2WEDO549 "Table" "SI_FKKVKPS" was activated (warning for the dependent tables)
    2WEDO549 "Table" "SI_FKKVKPSICA" was activated (warning for the dependent tables)
    2WEDO549 "Table" "SI_RDFKKRH" was activated (warning for the dependent tables)
    2WEDO549 "Table" "/BKC/S21_STAMM" was activated (warning for the dependent tables)
    2WEDO549 "Table" "/BKC/S21_STAMM00128" was activated (warning for the dependent tables)
    2WEDO549 "Table" "/BKC/S21_STAMM00256" was activated (warning for the dependent tables)
    2WEDO549 "Table" "/BKC/S21_STAMM00512" was activated (warning for the dependent tables)
    2WEDO549 "Table" "/BKC/S21_STAMM01024" was activated (warning for the dependent tables)
    2WEDO549 "Table" "/BKC/S21_STAMM02048" was activated (warning for the dependent tables)
    2WEDO549 "Table" "/BKC/S21_STAMM04096" was activated (warning for the dependent tables)
    2WEDO549 "Table" "/BKC/S21_STAMM08192" was activated (warning for the dependent tables)
    2WEDO549 "Table" "/BKC/S21_STAMM16384" was activated (warning for the dependent tables)
    2WEDO549 "Table" "BCA_STR_DIM_REF_REVERSAL_KEYS" was activated (warning for the dependent tables)
    2WEDO549 "Table" "EEDM_FRAME_OBJECT" was activated (warning for the dependent tables)
    2WEDO549 "Table" "EWEBIAC_MOVEOUTOBJ" was activated (warning for the dependent tables)
    2WEDO549 "Table" "FICAX_INTEREST_STR_INTER_DOC" was activated (warning for the dependent tables)
    2WEDO549 "Table" "FICA_INV_S_HEADER" was activated (warning for the dependent tables)
    2WEDO549 "Table" "FKKVK_PARTNERDATA_TYPE" was activated (warning for the dependent tables)
    2WEDO549 "Table" "FKKWH_LOGTYP" was activated (warning for the dependent tables)
    2WEDO549 "Table" "FKK_CORR_SINGLE" was activated (warning for the dependent tables)
    2WEDO549 "Table" "FKK_WO_S_WRITEOFF" was activated (warning for the dependent tables)
    2WEDO549 "Table" "FMCA_DUNN_S_DUNN_HEAD" was activated (warning for the dependent tables)
    2WEDO549 "Table" "FSC_STR_INSTP_INST_DOC" was activated (warning for the dependent tables)
    2WEDO549 "Table" "FSC_STR_INSTP_INST_ITEM" was activated (warning for the dependent tables)
    2WEDO549 "Table" "FSC_STR_SEC_SECURITY" was activated (warning for the dependent tables)
    2WEDO549 "Table" "HRDEPBSNVS_AVIS" was activated (warning for the dependent tables)
    2WEDO549 "Table" "HRFPM_S_ADT_SUB_SCR_PA_CONTEXT" was activated (warning for the dependent tables)
    2WEDO549 "Table" "HRFRPBS5_QAVGLS" was activated (warning for the dependent tables)
    2WEDO549 "Table" "HRIFT_TS_CONT" was activated (warning for the dependent tables)
    2WEDO549 "Table" "HRPAD_INFOTYPE_DATA" was activated (warning for the dependent tables)
    2WEDO549 "Table" "HRPD_WORKTAB_NEW" was activated (warning for the dependent tables)
    2WEDO549 "Table" "HRPP_S_ARFC_TASK" was activated (warning for the dependent tables)
    2WEDO549 "Table" "HRPP_S_PERSON_GROUP" was activated (warning for the dependent tables)
    2WEDO549 "Table" "HRTIM00WS_ORG_DATA" was activated (warning for the dependent tables)
    2WEDO549 "Table" "HRTIM00WS_PWS_INFTIES" was activated (warning for the dependent tables)
    2WEDO549 "Table" "HRTIM00WS_TIME_DATA" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISM_CA_DUNNING_STR_DUNN_HEAD" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISM_CA_INSTPLAN_STR_INST_DOC" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISM_CA_INSTPLAN_STR_INST_ITEM" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISM_CA_INTEREST_STR_INTER_DOC" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISM_CA_RETURN_STR_RETURN_DOC" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISM_CA_SEC_DEP_STR_SECURITY" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISU25_BUDBILPLAN" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISUMI_DUNNING_AUTO" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISUWA_ALL_OBJECTS" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISUWA_OBJ" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISUWA_ORDER" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISUWA_PROP" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISUWA_ROB" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISUWA_ROB_LINES" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISUWA_ROUTE" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISUWA_SERVLOC" was activated (warning for the dependent tables)
    2WEDO520 "Table" "ISU_BI_BILL_S_DOC_HEADER" was activated with warnings
    1 ED0313 (W- Field name DECIMAL is reserved (Do not use structure as include in DB table) )
    2WEDO549 "Table" "ISU_BI_COLL_BILL_S_CDOC_HEAD" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISU_BI_COLL_BILL_S_DOC_HEADER" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISU_CA_ACCTBALA_STR_BUS_PART" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISU_CA_ACCTINFO_STR_ACCTINFO" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISU_CA_BANK_MAIN_STR_DETAIL" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISU_CA_CCARD_MAIN_STR_DETAIL" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISU_CA_DUNNING_STR_DUNN_HEAD" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISU_CA_INSTPLAN_STR_INST_DOC" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISU_CA_INSTPLAN_STR_INST_ITEM" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISU_CA_INTEREST_STR_INTER_DOC" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISU_CA_RETURN_STR_RETURN_DOC" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISU_CA_SEC_DEP_STR_SECURITY" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISU_CS_ACCNT_STR_CONT_ACCT" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISU_CS_DISC_STR_BUS_PART" was activated (warning for the dependent tables)
    2WEDO520 "Table" "ISU_CS_MOVEIN_STR_MOVEINDOC" was activated with warnings
    1 ED0313 (W- Field name DATE is reserved (Do not use structure as include in DB table) )
    2WEDO520 "Table" "ISU_CS_MOVEOUT_STR_MOUT_DOC" was activated with warnings
    1 ED0313 (W- Field name DATE is reserved (Do not use structure as include in DB table) )
    2WEDO520 "Table" "ISU_CS_RATE_STR_CONT_ACCT" was activated with warnings
    1 ED0313 (W- Field name DATE is reserved (Do not use structure as include in DB table) )
    2WEDO549 "Table" "ISU_IN_BBP_S_BBP_DUE_DT" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ISU_IN_BBP_S_BBP_HEADER" was activated (warning for the dependent tables)
    2WEDO520 "Table" "ISU_IN_COLL_BILL_S_CDOC_HEAD" was activated with warnings
    1 ED0313 (W- Field name DECIMAL is reserved (Do not use structure as include in DB table) )
    2WEDO520 "Table" "ISU_IN_COLL_BILL_S_DOC_HEADER" was activated with warnings
    1 ED0313 (W- Field name DATE is reserved (Do not use structure as include in DB table) )
    2WEDO549 "Table" "ISU_PPM_OBJECT" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0027X" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0096" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P00_P0716" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0129" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0180" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P01C_CNNNN" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0206" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0262" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0294" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0316" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0495" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0716" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0718" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0722" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0723" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0738" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0741" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0742" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0744" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0748" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0752" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0754" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0755" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0757" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P08P_ME_ABS_INFOTYPES" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P08P_ME_ACT_INFOTYPE" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P08P_ME_AWE_SMP_INFOTYPES" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P08P_ME_AWE_SSP_INFOTYPES" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P08P_ME_CHK_INFOTYPES" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P08P_ME_P2001" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P08P_ME_PRI_INFOTYPES" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P08P_ME_SXP_INFOTYPES" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P08P_MIC_MATCH_0085" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P08P_MIC_MATCH_0086" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P08P_MIC_MATCH_2001" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P08P_P46_BASISDATA" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0958" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0959" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0961" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0963" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0964" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P0965" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P13_P0011" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P13_P0023L" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P13_P0188" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P13_P0220" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P13_P0220_PBS" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P13_P0508" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P13_P0509" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P13_P0509P" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P13_P0573" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P15_INAIL_MISC" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P15_PRELP" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P2007X" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P41_P0541" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9019" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9075" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9099" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9390" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9429" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9500" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9640" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9701" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9725" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9741" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9742" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9825" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9901" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9929" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9945" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9990" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9991" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9992" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9993" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9995" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9996" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9997" was activated (warning for the dependent tables)
    2WEDO549 "Table" "P9998" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0002" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0129" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0180" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0206" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0262" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0294" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0495" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0716" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0718" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0722" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0723" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0738" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0741" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0742" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0744" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0748" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0752" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0754" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0755" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0757" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0958" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0959" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0961" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0963" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA0964" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9019" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9075" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9099" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9390" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9429" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9500" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9640" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9701" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9725" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9741" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9742" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9825" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9901" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9945" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9990" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9991" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9992" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9993" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9995" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9996" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9997" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PA9998" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PANNNN" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PAYUN_NATIONAL" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PAYUN_RESULT" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PB0002" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PB0433" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PB0744" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PB0858" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PBNNNN" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PMMMM" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PSHDR" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PSOPER" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTARQ_P2001_STRUC" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTARQ_P2002_STRUC" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTARQ_REQLIST_STRUC_FLAT" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTCOR_REQS_LIST" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTM_PT50_ABS_QUOTAS" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_AP2002" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P0000" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P0001" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P0002" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P0003" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P0003_REF" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P0004" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P0007" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P0008" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P0016" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P0019" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P0041" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P0050" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2001" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2001_NEW" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2001_NEW_REF" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2001_REF" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2002" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2002_NEW" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2002_NEW_REF" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2002_REF" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2003" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2003_REF" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2004" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2004_REF" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2006" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2006_REF" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2007" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2007_REF" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2012" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2012_REF" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2013" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_P2013_REF" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_CONTRACT_PSOPER" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_P2001_NEW" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_P2002_NEW" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PTR_PSOPER" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PUNAAP_ACTION" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PUNAAP_INFOTYPE" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PUNAAP_PERNR_ACTIONS" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PUNAAP_PNNNN" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PUNPAD_EGEXPSTR" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PUNPAD_EGINFTY" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PUNPAD_EG_SUM" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PUNPAY_PF" was activated (warning for the dependent tables)
    2WEDO549 "Table" "PZZZZ" was activated (warning for the dependent tables)
    2WEDO549 "Table" "RPBENIDOC_DOCUMENT" was activated (warning for the dependent tables)
    2WEDO549 "Table" "SITAGCYACCGROUP" was activated (warning for the dependent tables)
    2WEDO549 "Table" "SITAGCYOPENCOSTCTRL_GROUP" was activated (warning for the dependent tables)
    2WEDO549 "Table" "SITAGCYOPENITEMCTRL_GROUP" was activated (warning for the dependent tables)
    2WEDO549 "Table" "SITAGCYOPENITEMOPCTRL_GROUP" was activated (warning for the dependent tables)
    2WEDO549 "Table" "SITAGCYPRINTDATA" was activated (warning for the dependent tables)
    2WEDO549 "Table" "SPA_IPREL" was activated (warning for the dependent tables)
    2WEDO549 "Table" "T7UNPAD_EGEXPMGT" was activated (warning for the dependent tables)
    2WEDO549 "Table" "TIM_TMW_BLPREQUEST_ENTRY" was activated (warning for the dependent tables)
    2WEDO549 "Table" "TIM_TMW_COMMTAB_ENTRY" was activated (warning for the dependent tables)
    2WEDO549 "Table" "TIM_TMW_INFOTYPE_ENTRY" was activated (warning for the dependent tables)
    2WEDO549 "Table" "TIM_TMW_MODIFY_IT_ENTRY" was activated (warning for the dependent tables)
    2WEDO549 "Table" "TIM_TMW_READ_REQRES_ENTRY" was activated (warning for the dependent tables)
    2WEDO549 "Table" "TIM_TMW_TIME_DATA" was activated (warning for the dependent tables)
    2WEDO549 "Table" "TIM_TMW_UPDATE_IT" was activated (warning for the dependent tables)
    2WEDO549 "Table" "TIM_TMW_UPDATE_IT_ENTRY" was activated (warning for the dependent tables)
    2WEDO549 "Table" "ZPTTAM_COPY_PERNR_INFTY" was activated (warning for the dependent tables)
    2WEDO549 "Table Type" "FKKWH_LOGTTAB" was activated (warning for the dependent tables)
    2WEDO549 "Table Type" "ISU25_AUTO_PORTION_CHANGE_TAB" was activated (warning for the dependent tables)
    2WEDO549 "Table Type" "ISU25_BBP_PRINTDATA_TAB" was activated (warning for the dependent tables)
    2WEDO549 "Table Type" "ISU25_BUDBILDATE_TABLE" was activated (warning for the dependent tables)
    2WEDO549 "Table Type" "ISU25_BUDBILPLAN_HEADDATA" was activated (warning for the dependent tables)
    2WEDO549 "Table Type" "ISU25_ITAB_IEABPS" was activated (warning for the dependent tables)
    2WEDO549 "Table Type" "ISU25_T_OBJ" was activated (warning for the dependent tables)
    2WEDO549 "Table Type" "ISUWA_ROB_TAB" was activated (warning for the dependent tables)
    2WEDO549 "Table Type" "ISUWA_T_ORDER" was activated (warning for the dependent tables)
    2WEDO549 "Table Type" "ISUWA_T_ROUTE" was activated (warning for the dependent tables)
    2WEDO549 "Table Type" "T_FKKEPOS" was activated (warning for the dependent tables)
    2WEDO549 "Table Type" "T_ISU_PPM_FKKOP" was activated (warning for the dependent tables)
    2WEDO549 "Table Type" "VVSC_PPLAN_SINGLE_TAB_SVSFKKOP" was activated (warning for the dependent tables)
    2WEDO549 "Table Type" "VVSC_PPLAN_TAB_ITEMS" was activated (warning for the dependent tables)
    2WEDO549 "Table Type" "VVSC_T_SVSFKKOP" was activated (warning for the dependent tables)1 ED0301X*************************************************************************
    1 ED0306       "Final log"
    1 ED0322 End phase  "002" ***********************************************************
    1 ED0320XStart phase "003" **********************************************************
    1 ED0306       "Statistics on Activated and Deleted Objects"
    1 ED0301 *************************************************************************
    1 EDO601XNumber of objects to be activated............:  "3540"
    1 EDO605 Objects not activated........................:  "7"
    1 EDO606 Activated objects with errors in dependencies:  "4"
    1 EDO604 Objects activated with warning...............:  "311"
    1 EDO603 Successfully activated objects...............:  "3218"
    1 EDO602 Number of objects to be deleted..............:  "0"
    1 EDO608 Objects not successfully deleted.............:  "0"
    1 EDO607 Successfully deleted objects.................:  "0"
    1 EDO609 Tables/views with DROP/CREATE................:  "0"
    1 EDO610 No. of them marked for DROP/CREATE: "0"
    1 EDO611 Not marked for DROP/CREATE: "0"
    1 EDO620 Number of nametabs to be deleted.............:  "0"
    1 EDO622 Successfully deleted nametabs................:  "0"
    1 EDO621 Nametabs that were not successfully deleted..:  "0"
    1 ED0301X*************************************************************************
    1 ED0306       "Statistics on Activated and Deleted Objects"
    1 ED0322 End phase  "003" ***********************************************************
    1 ED0302X=========================================================================
    1 ED0314 Mass Activation
    1 ED0302 =========================================================================
    1 ED0327 Process..................: "MASTIDES_9"
    1 ED0319 Return code..............: "8"
    1 ED0313 Phase 001..................: 00:09:25 (Object Activation)
    1 ED0314 Phase 002..................: < 1 sec. (Final log)
    1 ED0314 Phase 003..................: < 1 sec. (Statistics on Activated and ...)
    1 ED0309 Program runtime..........: "00:09:44"
    1 ED0305 Date, time...............: "23.07.2008", "14:40:29"
    1 ED0318 Program end==============================================================
    1 ETP155 ACTIVATION OF DD-OBJECTS
    1 ETP110 end date and time   : "20080723144029"
    1 ETP111 exit code           : "8"
    1 ETP199 ######################################
    Edited by: Teddy Larsen on Jul 24, 2008 11:18 AM

    in ides few dataelements.... will be missing in tables
    during support package when these tables are activated they fail
    so take the help of abaper to resolve this issue
    samrat

  • Parallel Processing when running in background

    Hi
    We have implemented a parallel processing solution using the Call Function Starting New Task Destination in Group format to split a large number of updates across an RFC Server Group.
    This works well when running the ABAP in dialog, but when we schedule for background processing, the parallel processing does not seem to occur, we get a single background process.
    Does anyone have any ideas why this may be occuring ?
    Thanks
    Paul

    Paul,
    Starting new task will start a new LUW in dialog process and not in background. This is the reason you are having a problem. While technically STARTING NEW TASK is used for parallel processing, you need to consider whether the program will be run in foreground or background mode.
    In case of background, you need consider using multiple jobs via job open, submit, job close. This way you can initiate more than one process in your server group to do the work.
    You will need to consider the # of background WP available and the # of WPs you can use for this program.
    So if there are 100 WPs available and you can use only 10 at any give time, then you should schedule 10 jobs and then check the status of the 10 jobs before you can start scheduling the next jobs.
    You can use the FM SPBT_INITIALIZE to check the # of WPs that are currently available in the server group.
    Hope this helps.
    Thanks,
    Vikram.M

  • Process runs faster when executed independently, but runs slower when a parallel big process is running

    Hi,
    The issue is,  a process, say "A" is running fine on certain days. On some days there are additional processes running on the server. When these additional processes are running, "Process A" suffers performance issue.
    Interesting point is that, these additional processes were running since long time. But, earlier "Process A" was running fine even when these additional process were running. Suddenly from past 2 or 3 weeks there is performance issue in "Process
    A", when these additional process run.
    Note: Nothing has been modified for the process A.
    Process A is an SQL job which has SSIS Package and stored proc in different steps
    When multiple parallel processes are running, SSIS Package step suffers around 40% increase in execution time, where as stored procs have only 15-20% increase in execution time
    When Process A is executed while no other big processes are running, it's execution time is fine. From past few days, issue is only when, some other big parallel processes are running.
    Currently below is my analysis:
    Since Process A is running fine when it is executed independently, I assume there is no issue in this process.
    Since issue occurs when some other big process is running, when Process A is running, I believe it is DiskIO issue. Will the issue be resolved if RAM size is increased?
    Is there any way to check if RAM is being fully utilized by the server
    Is there any other possibility why there is a sudden dip in performance when parallel processes are running.
    Is there any possibility of having issues in additional processes. Incase if it has some issues, does it impact "Process A"
    Please let me know if you need any further information. Infact I am not able to diagnose what is the actual root cause for the performance issue in "Process A" as nothing has been modified.
    Also it would be very much helpful, if I get any idea on different ways in reaching the actual root cause of this performance issue.
    NOTE: This is a data warehouse
    Thanks,
    Raksha

    When a query has a parallel plan, it will in general try to grab all cores up to the maxdop setting, but then it often uses them inefficiently. 
    But in that case, there are better odds for the queries not battling on resources with each other!
    What Josh alludes is to the fact that SQL Server needs to partition the data, so that different partitions are processed on different cores. This partitioning is based on statistics, and the statistics may be out of date or not accurate enough. This may
    result in that the data is not partitioned proportionally, and some threads gets very little data to work with. Thus, these CPUs are still idle, so there may still be room for the two processes to run at full speed. (That is, full speed with the given plan,
    which is not the full speed, had the partitioning been accurate.)
    I mention this because you asked about parallelism, and many systems leave maxdop at its default setting of 0 (which means "go ahead and grab everything!") even though Microsoft recommends you set it to a different number depending on this and
    that.
    Since this is a data warehouse, Raksha should not tamper with "max degrees of parallelism", I think.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Limit number of parallell processes when archiving

    Hello,
    I am about to achive object SD_VBAK. This will take a long time to run, so I want to limit the number of parallell batch process it runs in. When I did this in our development system the archiving took all available batch processes. It there a way to set the number of parallell processes? I don´t want to affect the normal business.
    We run on ECC 6.0.
       Best Regards
       Ann-Sofie Svensson

    Hi ann,
    Check this link
    http://help.sap.com/saphelp_erp2004/helpdata/en/d2/36e2791560ed4a96e97a3175694886/content.htm
    You can set parallel work process, or you can run archiving only in night, for example in Cross-Object Customizing you set parameter Max. Duration Hrs, then schedule Archiving job and finish automatically in XX Hours.
    Regards,
    William Neira

  • Job fail with Timeout for parallel process (for SID Gener.): 006000

    Hello all,
    Im getting below error and not able to find any issue with Basis side. Please anyone help on this!
    Job started
    Data package has already been activated successfully (will be skipped)
    Process started
    Process started
    Process started
    Process started
    Process started
    Import from cluster of the data package to be activated () failed
    Process 000001 returned with errors
    Process 000002 returned with errors
    Process 000003 returned with errors
    Process 000004 returned with errors
    Background process BCTL_4XU7J1JPLOHYI3Y5RYKD420UL terminated due to missing confirmation
    Process 000006 returned with errors
    Data pkgs 000001; Added records 1-; Changed records 0; Deleted records 0
    Log for activation request ODSR_4XUG2LVXX3DH4L1WT3LUFN125 data package 000001...000001
    Errors occured when carrying out activation
    Analyze errors and activate again, if necessary
    Activation of M records from DataStore object CRACO20A terminated
    Activation is running: Data target CRACO20A, from 1,732,955 to 1,732,955
    Overlapping check with archived data areas for InfoProvider CRACO20A
    Data to be activated successfully checked against archiving objects
    Parallel processes (for Activation); 000005
    Timeout for parallel process (for Activation): 006000
    Package size (for Activation): 100000
    Task handling (for Activation): Backgr Process
    Server group (for Activation): No Server Group Configured
    Parallel processes (for SID Gener.); 000002
    Timeout for parallel process (for SID Gener.): 006000
    Package size (for SID Gener.): 100000
    Task handling (for SID Gener.): Backgr Process
    Server group (for SID Gener.): No Server Group Configured
    Activation started (process is running under user *****)
    Not all data fields were updated in mode "overwrite"
    Data package has already been activated successfully (will be skipped)
    Process started
    Process started
    Process started
    Process started
    Process started
    Import from cluster of the data package to be activated () failed
    Process 000001 returned with errors
    Process 000002 returned with errors
    Process 000003 returned with errors
    Process 000004 returned with errors
    Errors occured when carrying out activation
    Analyze errors and activate again, if necessary
    Activation of M records from DataStore object CRACO20A terminated
    Report RSODSACT1 ended with errors
    Job cancelled after system exception ERROR_MESSAGE

    Thanks for the link TSharma I will try that today.
    UPDATE:
    I ran a non-parallel Data Pump and just let it run overnight. This time it finished after 9 hours.  In this run I set the STATUS=300 parameter in the PARFILE which basically echos STATUS updates to standard out every 300 seconds (5 minutes).
    And as before after 2 hours it finished 99% of the export and just spit out WAITING status for the last 7 hours until it finished.  The remaining TABLES it exported (a few hundred) were all very small or ZERO rows.  There clearly is something going on that is not normal.  I've done this expdp before on clones of this database and it usually takes about 2-2.5 hours to finish.
    The database is about 415 Gigabytes in size.
    I will update what the TRACE finds and I'm also opening a case with MOS.

Maybe you are looking for

  • Memory speed problems with Neo2 Platinum

    Hi all -- I'm trying to figure out a problem I'm having getting my memory frequency up to speed. Right now I have two 512MB sticks of Crucial Ballistix PC4000 RAM but I can't get them running any faster than 166Mhz each (or 333 Mhz DDR). I'm using a

  • SAP R/3 FICO CONFIGURATION

    Hi Gurus, Can any one have soft copy of Configuring SAP R/3 FICO" by Quentin Hurst and David Nowak. I would appreciate, if someone could forward to me at [email protected] Full points will be rewarded. Thanks Mohit

  • Tax Jurisdiction issues in AR Invoice Creation

    MODULE = AR EBS Version = R12.1 EBS Tax is setup Hi All I am currently trying to mimic the functionality in the front end of AR Transaction workbench from the back end via Auto Invoice process From the front end+ When I manually create an invoice and

  • I use iPod video in thailand

    I had a problem after i upgrade my iPod to newest version (1.2), it's not support the thai font. How can i solve this problem ? Let's me know by send email to me at [email protected] Regrads, Pantin N.

  • Cinnamon crashes after package upgrade today

    Last upgrade was yesterday and it was ok. Not sure how to deal with this kind of problem. Is anybody even looking into what goes into the package builds, or some stuff just gets pulled from the repository, whatever the latest version is there? I know