Process Chain changing start time?

hi guysm i have 76 process chains that run every day in BWD system, so i removed all the timings from the start variant and in the infopackages, but it seems some process chains are still running, i did do the following steps on chnaging the time from a particular time to immediate, Save, Check and activate, i didnt schedule it as i dont want it to load right away .
do i have to hit check , save , schedule once i change the time from a particular time to immediate load or activate will work as well.?
what else could be the cause of process chains still loading even there are no events, or time given to any process chains at all.
i went to sm 37 and i can see the bi process are all running at the time they were orignially set up on.
so any suggestions would help,
is there any way from sm 37 i can tell which process chain is triggered off?
thanks
Dante(devils never cry)

Dante, the start conditions on the infopackages do not affect when they run in process chains.  The process chains have their own start job.  If you want to change the start time of a process chain, then you need to go to maintain the process chain, right-click on the Start process and select Displaying Scheduled Job(s)... .  Here you will see a job called BI_PROCESS_TRIGGER.  Change the start conditions of this job. 
The start job for all process chains is BI_PROCESS_TRIGGER, so using SM37 may be difficult to identify which BI_PROCESS_TRIGGER job is associated to a particular chain. 
Also, to let you know, each process in a process chain has an associated job.  All jobs called BI_PROCESS_xxxxx are jobs associated with a process chain. 
Eg. 
BI_PROCESS_LOADING is an infopackage.
BI_PROCESS_TRIGGER is the start job
Does this help?

Similar Messages

  • Trigger Process chain at set time or when an event is raised.

    Hi All,
             I have a requirement where a process chain should get scheduled at fix time, say at 1:00 AM. Also, it should get scheduled when an event is raised by one BSP application. So, its like Set time OR Event should trigger the chain. Can you please guide, how can i implement this without using a special SM37 job?
    Thanks and Regards,
    Harpal

    Hi Gohil,
    The steps to create an event is as follows:
    1. Create the event with SM62.
    2. In the process chain, maintain your Start process. In the change selections screen, choose the button 'After event'. On the bottom, select your event. Click also on 'Periodic job'.
    3. Activate and schedule your process chain. It will then be visible in SM37, waiting for the event.
    4. Then you may raise this event from any ABAP program with function module BP_EVENT_RAISE. Each time you raise the event the process chain will start. You can raise the event also manually with SM64.
    If you want to fix a time i.e., at 1:00 A.M, you need to got RSPC tcode --> click on the chain --> right click on Start variant --> Click on maintain variant --> Change selections --> Click on Date/Time --> Give the date and time.
    If you want to ru7n your chain daily or weekly like periodically, check Periodic Job and click on "Period Values" and select accordingly. Now save everything and click on start variant and activate and schedule your chain.
    Also check below thread for more info on Event:
    Triggering a Process Chain From R/3 pgm
    Regards,
    KK.

  • Scheduling process chain 3 specific times a day

    Hi ,
    my requirement is to schedule a process chain 3 times a day.
    i have gone through the forum and got the solution EVENTS.
    please provide me how to do this in detail like step by step.
    how to create a event in SM64 and how we will define the time there.
    and creating a ZPROGRAM with the function module (please provide step bystep).
    thanks
    Sridhar

    You create user events in SM62.  In SM62, next to "User even names", click on <b>Maintain</b> and press Enter.  Click on the Create icon to create a new event (let's call it ZEVENT).
    Next, in your process chain, change the Start variant to be scheduled "After event", and put in ZEVENT for the event name.  Also, click on the "Periodic job" at the bottom.  This will automatically reschedule the jobs for the process chain after it executes.
    Next, create an ABAP program (let's call it Z_EVENT_RAISE) to call the function module BP_EVENT_RAISE.  You're code can look like this:
    REPORT Z_EVENT_RAISE.
    PARAMETERS: P_EVENT LIKE TBTCO-EVENTID.
    CALL FUNCTION 'BP_EVENT_RAISE'
    EXPORTING
    EVENTID = P_EVENT.
    IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    * WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    This ABAP program will prompt for an event name, so you will need to create a variant (let's call it ZEVENT) which will save the value of the event name (also ZEVENT).  You will need the variant name to be able to trigger the event in a batch job.
    Now all you need is the batch job.  Use tcode SM36 to create a batch job where you call the ABAP program (Z_EVENT_RAISE) using the variant (ZEVENT).
    Note, SM64 only triggers an event manually.
    Does this help?
    Oh, and you can copy this job to schedule it three times a day.
    Message was edited by:
            Geo

  • The 0co_om_opa_6 ip in the process chains takes long time to run

    Hi experts,
    The 0co_om_opa_6 ip in the process chains takes long time to run around 5 hours in production
    I have checked the note 382329,
    -> where the indexes 1 and 4 are active
    -> index 4 was not "Index does not exist in database system ORACLE"- i have assgined to " Indexes on all database systems and ran the delta load in development system, but guess there are not much data in dev it took 2-1/2 hrs to run as it was taking earlier. so didnt find much differnce in performance.
    As per the note Note 549552 - CO line item extractors: performance, i have checked in the table BWOM_SETTINGS these are the settings that are there in the ECC system.
    -> OLTPSOURCE -  is blank
       PARAM_NAME - OBJSELSIZE
       PARAM_VALUE- is blank
    -> OLTPSOURCE - is blank
       PARAM_NAME - NOTSSELECT
       PARAM_VALUE- is blank
    -> OLTPSOURCE- 0CO_OM_OPA_6
       PARAM_NAME - NOBLOCKING
       PARAM_VALUE- is blank.
    Could you please check if any other settings needs to be done .
    Also for the IP there is selction criteris for FISCALYEAR/PERIOD from 2004-2099, also an inti is done for the same period as a result it becoming difficult for me to load for a single year.
    Please suggest.

    The problem was the index 4 was not active in the database level..it was recommended by the SAP team to activate it in se14..however while doing so we face few issues se14 is a very sensitive transaction should be handled carefully ... it should be activate not created.
    The OBJSELSIZE in the table BWOM_SETTINGS has to be Marked 'X' to improve the quality as well as the indexe 4 should be activate at the abap level i.e in the table COEP -> INDEXES-> INDEX 4 -> Select the  u201Cindex on all database systemu201D in place of u201CNo database indexu201D, once it is activated in the table abap level you can activate the same indexes in the database level.
    Be very carefull while you execute it in se14 best is to use db02 to do the same , basis tend to make less mistake there.
    Thanks Hope this helps ..

  • Delete Index in Process Chain Takes long time after SAP BI 7.0 SP 27

    After upgrading to SAP BI 7.0 SP 27 Delete index Process & Create index process in Process chain takes long time.
    For example : Delete index for 0SD_C03 takes around 55 minutes.
    Before SP upgrade it takes around 2 minutes to delete index from 0SD_C03.
    Regards
    Madhu P Menon

    Hi,
    Normally  index  creation or deletion can take long time in case  your database statistics are not updated properly, so can check  stat  after your data loading is completed and index generation is done,  Do creation of database statistics.
    Then try to recheck ...
    Regards,
    Satya

  • How to dynamically  change start time in calendar

    Hi !
    Is it possible dynamically change start time attribute in calendar. Let's say I'd like to have start time = sysdate through 24 for display

    Hello Johann,
    If you created the calendar region using the wizard, it should have created a page item 'P#_CALENDAR_DATE' (# being your page number). Look at the Default setting for that item and it will likely be:
    return to_char(localtimestamp,'YYYYMMDD');This is the default date for the calendar (current date), in 'YYYYMMDD' format. Any code that sets this item to a date in 'YYYYMMDD' format should tell the calendar to display the calendar for that date. For example, I just changed it to this:
    return '20080101';And it displayed the calendar for that January, 2008. To test further I created a submit button and a branch, and in that branch I specified to set my P1_CALENDAR_DATE item to 20080601 and when I clicked the button it redisplayed the calendar for June, 2008.
    Hope this helps,
    John

  • Started same Process Chain automatically several times

    Hi BW Experts,
    could you help me, please?
    I don't know, how I started the same Process Chain automatically again.
    I have a following easily process chain as a example:
    1. Start Process
    2. DTP
    3. DSO Acitvated
    I have the idea to insert the process 4. "Abap program" to start the function module "RSPC_API_START_CHAIN" again. But their are any problems......
    Have you another idea?
    Thank you and regards.
    Volker

    Hi,
    Are u sing the Direct DTP or the normal DTP's?
    If u are using the normal DTP then u need change the process in ur PC..
    Start Process
    Infopackge load till PSA
    DTP to load data to DSO
    Activation of DSO
    ... U can also add the ABAP process as per requirement .. there wont be any issues in that..
    thanks
    Assign points if this helps

  • Process chain fails every time at "roll up of aggregates"

    hi all,
    A process is deffined in such a way that...                                        start
                                                                                    i
                                                                                    i
                                                            Delta loads to infocube1(load)  deltaload to infocube2(load)       deltaload to infocube3(load)
                                                                            i                                                 i                                          i
                                                                            i                                                 i                                          i
                                                            delta load of aggregate(cube1)   delta load  of aggregates(cube2)     delta load  of aggregates
    Every time when this process chain get executed,this fails at delta laod of aggregates step.If i repeat again it works fine.But repeating is not a solution for this.So,i want a permanent soltuion for this..
    Please guide me what to do?and explain me why this happens.
    Error message:-process rollup of filled aggregates/bia indexes,variant delta load of aggregates
    Thanks( in advance)
    Moushmi

    Hi Moushmi,
    Have you checked if the system has processes available while the chain is running?  It could be that your system is overloaded and the aggregates wouldn't roll up because you have no processes or available memory.
    Check with your Basis resource.  Also, try changing your chain to do only 1 at a time.  Do you have many aggregates to load, are they big, and most important are they being used.
    Kathleen

  • Process Chain for Real Time Demon

    Please help I am stuck I followed the step by sdn but this is missing in step. how to create now process chain.
    I created the below
    DSO CONNECTED TO dATASOURCE via Trans,
    Real Time IP
    Real Time DTP
    assigned to Datasource and assigned the DS, IP, DTP to Deamon in RSRDA. NOW I started also manually via start all IP. but How to set the process chains now.
    PLEASE HELP ME STEP BY STEP TO PROCESS CHAIN SINCE i am new to this daemon in process chains
    Thanks
    Soniya
    null

    Hi
    refer to this
    CREATION OF PROCESS CHAINS
    Process chains are used to automated the loading process.
    Will be used in all applications as you cannot schedule hundreds of infopackages manually and daily.
    Metachain
    Steps for Metachain :
    1. Start ( In this variant set ur schedule times for this metachain )
    2.Local Process Chain 1 ( Say its a master data process chain - Get into the start variant of this chain ( Sub chain - like any other chain ) and check the second radio button " Start using metachain or API " )
    3.Local Process Chain 2 ( Say its a transaction data process chain do the same as in step 2 )
    Steps for Process Chains in BI 7.0 for a Cube.
    1. Start
    2. Execute Infopackage
    3. Delete Indexes for Cube
    4.Execute DTP
    5. Create Indexes for Cube
    For DSO
    1. Start
    2. Execute Infopackage
    3. Execute DTP
    5. Activate DSO
    For an IO
    1. Start
    2.Execute infopackage
    3.Execute DTP
    4.Attribute Change Run
    Data to Cube thru a DSO
    1. Start
    2. Execute Infopackage ( loads till psa )
    3.Execute DTP ( to load DSO frm PSA )
    4.Activate DSO
    5.Further Processing
    6.Delete Indexes for Cube
    7.Execute DTP ( to load Cube frm DSO )
    8.Create Indexes for Cube
    3.X
    Master loading ( Attr, Text, Hierarchies )
    Steps :
    1.Start
    2. Execute Infopackage ( say if you are loading 2 IO's just have them all parallel )
    3.You might want to load in seq - Attributes - Texts - Hierarchies
    4.And ( Connecting all Infopackages )
    5.Attribute Change Run ( add all relevant IO's ).
    Start
    Infopackge1A(Attr)|Infopackge2A(Attr)
    Infopackge1B(Txts)|Infopackge2B(Txts)
    /_____________________|
    Infopackge1C(Txts)______|
    \_____________________|
    \___________________|
    __\___________________|
    ___\__________________|
    ______ And Processer_ ( Connect Infopackge1C & Infopackge2B )
    __________|__________
    Attribute Change Run ( Add Infobject 1 & Infoobject 2 to this variant )
    1. Start
    2. Delete Indexes for Cube
    3. Execute Infopackage
    4.Create Indexes for Cube
    For DSO
    1. Start
    2. Execute Infopackage
    3. Activate DSO
    For an IO
    1.Start
    2.Execute infopackage
    3.Attribute Change Run
    Data to Cube thru a DSO
    1. Start
    2. Execute Infopackage
    3.Activate DSO
    5.Further Processing
    6.Delete Indexes for Cube
    7.Execute Infopackage
    8.Create Indexes for Cube

  • Process chain taking long time

    Hi,
        I developed a Process chain. In developemnt for Completion of the Update rules(Start routine) its taking 60m( for around 50,000 records).
    After transporting the Process chain to Production for Start routine completion (For 1,70,000 records) its taking 7hrs and sometimes its failing as the "Process is Over due" and sometimes due to "Short dump".
    How to handle this.........
    Thanks

    Hi js,
    Check the ST22... Any dumps
    Check out for the short dump in source system and try loading the delta again
    then
    I have got the problem when u have posted...but little later.Even I was about to post the issue.. Actually my issue was...
    My PC is like this
    1) Start Process
    2) Delete index
    3) Load IP
    4) delete overlapping request
    5) create Index
    6) ABAP program
    Process chain hangs at Overlapping requests process type but the status was yellow. And the previous step (3) was success. From there its not moving to next further steps.. But the Job in SM37 was canceled.
    I saw Ur post and saw the note 833168 and which matches exactly our issue.
    Like we run the PCs thru the TIDAL where due to some problems PC got triggered twice... I can see the two logs in the PC. (Log view) and two requests at RSMO.
    Everything was recovered again thru manual steps. This is the first time we encountered... the note helped us ... We now are very cautious about the Tidal runs...
    Now PC is running perfectly
    we have instructed the Supported team to make the necessary changes or fix this issues in TIDAL...
    i hope this is helpful to u
    bye now
    suresh

  • Process chain taking long time to complete

    Hi,
    I am having following issues in the process chain daily loads
    1) The PSA deletion is taking very long time on fridays only (nearly 3 hrs). Other days it gets deleted in 1 hr max.
    2) Just to load 381 records via dtp from DSO to cube takes nearly 2 hrs(Delta load). No major routines are written in the transformation.
    How to analyse a process in process chain which does not fail, but takes very long time to complete. Is there any tool or transaction in BW which can help us to analyse why the process chain takes so long time to complete in different days. One day it completes in 8 hrs, another day it takes 12 hrs.
    None of the transactions, SM37, SM50, SLG1, LOGS etc are giving me any help to analyse this issue.
    If it fails we have error logs to check and analyse, but without failing how we can analyse and fix the delay and reduce the time of loading data. Please guide me.
    Thanks in advance.
    Vishwanath

    Hi.......
    1) This might be due to the poor performance of the system ..there wont be enoughwork processes avilabe in teh system .- What needs to be done if it does not have enough work processes available. Though I can find that lots of dialog processes were free during these jobs as well some Background processes were also free.?
    Look to increase Work Process.......................u can do two things..............U can cancel some Job...........which r not progressing...........or which r not very important for the time being..........
    Or if possible........u can increase number of servers..........
    Look When a Job will start...............first it will run in background.............u can start in in Dialog also..........but for Dialogue after some time ..load will go to time out.................now many Child jobs will be created for a single background jobs..............they may run in Dialogue..........u can monitor them through SM66............
    2) Check ST04 for lock waits and dead locks ..if the same lock persist for long then check with basis team.
    What needs to be conveyed to the basis team when these locks happen?
    generally these will be temporary Locks.............after some time locks will be realeased..............if they persist for a long time...........then u can contact Basis people..........Or if u can understand that which job is creating the lock.............like if u double click on the job >> click on Job details...............from there u will find the PID................copy that.............and check in ST04..........whether they matches or not..............now suppose it match.............and u know that job is not very important............then u can cancel the job.............
    Check also the table space availba in St04 . the usuage should nt be more than 90%
    What needs to be conveyed to the basis team if the usage is more than 90%.?
    U can ask them to increase the Table space........
    Check the sm37 >> delay column it should nt be high
    What needs to be done if delay column is high. Actually it is high for these jobs (PSA deletion and load from DSO to Cube visa DTP (Delta load)?
    If Delay is more.............it means ...........that there is no free work process...jobs r going to Release state............solution I had already given u.......
    Check the PID refeclting in lock waits in sm66 wether they are progressing or nt ..
    If they are not progressing what action needs to be taken?
    Actually...........suppose one Dialogue job is running............it may change..........ie  that Dialogue job will go to Stop status.........some other job will start............anyways if it does'nt progress............u can cacel the JOb.........
    Check OS07 for DB if the idle time is less then 20% then its a problem ..
    If the Idle time is less than 20% what action needs to be taken?
    U can contact the Basis people.......
    Check sm21 and RFC connection with other source systems in sm59 ..
    What needs to be checked in SM21 and SM59 specifically? What parameter i need to check?
    In SM21.............if red status is there............check the Log beside that..............may be it will be some Terminal disconnected.......
    In SM59...........clck on test connection..........
    if the problem is occuring due to only one source system then check the performance of that system ..
    How to check the performance of these systems? Any tools available in R/3 system to check its performance?
    No.....in this way u can check performance for all the source system...........go to SM59............double click on the desired source system>> click on test connection......
    If All these are persisting then its a performance problem and check with basis team ..
    Is there any special settings which needs to be maintained to achieve better performance of Process chain loads?
    U can Improve the performance of process chain by Parallel Processing..........ie split the loads by giving selections...........and execute thenm in parallel..........
    Regards,
    Debjani........

  • BPM Process chain takes long time to process

    We have BI7, Netweaver 2004s on Oracle and SUN Solaris
    There is a process chain (BPM) which pulls data from the CRM system into BW. The scheduled time to run this chain is 0034 hrs. This chain should ideally complete before / around 0830 Hrs. <b>Now the problem is that every alternate day this chain behaves normally and gets completed well before 0830 hrs but every alternate day this chain fails…</b> there are almost 40 chains running daily. Some are event triggered (dependent with each other) or some run in parallel. In this, (BPM) process chain, usually there are 5 requests with 3 Delta and 2 full uploads (Master Data). The delta uploads finishes in 30 minutes without any issues with very few record transfers. The first full upload is from 0034 hrs to approximately 0130 hrs and the 2nd upload is from 0130 hrs to 0230 hrs. Now if the 1st upload gets delayed then the people who are initiating these chains, stop the 2nd full upload and continue it after all the process chains are completed. Now this entire BPM process chain sometimes takes 17 -18 hrs to complete!!!!!
    No other loads in CRM or BW when these process chains are running
    CRM has background jobs to push IDOCS to BW which run every 2 minutes which runs successfully
    Yesterday this chain got completed successfully (well within stipulated time) with over 33,00,000 records transferred but sometimes it has failed to transfer even 12,00,000 records!!
    Attaching a zip file, please refer the “21 to 26 Analysis screen shot.doc” from the zip file
    Within the zip file, attaching “Normal timings of daily process chains.xls” – the name explains it….
    Also within the zip file refer “BPM Infoprovider and data source screen shot.doc” please refer this file as the infopackage (page 2) which was used in the process chain is not displayed later on in page number 6 BUT CHAIN GOT SUCESSFULLY COMPLETED
    We have analyzed:--
    1)     The PSA data for BPM process chain for past few days
    2)     The info providers for BPM process chain for past few days
    3)     The ODS entries for BPM process chain for past few days
    4)     The point of failure of BPM process chain for past few days
    5)     The overall performance of all the process chains for past few days
    6)     The number of requests in BW for this process chain
    7)     The load on CRM system for past few days when this process chain ran on BW system
    As per our analysis, there are couple of things which can be fixed in the BW system:--
    1)     The partner agreement (transaction WE20) defined for the partner LS/BP3CLNT475 mentions both message types RSSEND and RSINFO: -- collect IDOCs and pack size = 1 Since the pack size = 1 will generate 1 TRFC call per IDOC, it should be changed to 10 so that less number of TRFCs will be generated thus less overhead for the BW server resulting in the increase in performance
    2)     In the definition of destination for the concerned RFC in BW (SM59), the “Technical Setting” tab says the “Load balancing” option = “No”. We are planning to make it “Yes”
    But we believe that though these changes will bring some increase in performance, this is not the root cause of the abnormal behavior of this chain as this chain runs successfully on every alternate day with approximately the same amount of load in it.
    I was not able to attach the many screen shots or the info which I had gathered during my analysis. Please advice how do I attach these files
    Best Regards,

    Hi,
    Normally  index  creation or deletion can take long time in case  your database statistics are not updated properly, so can check  stat  after your data loading is completed and index generation is done,  Do creation of database statistics.
    Then try to recheck ...
    Regards,
    Satya

  • Info Package in Process Chain taking long time

    Dear All,
    Info Package in Process Chain having 0 records is taking 1 hr 5 mins to complete. Time out time is set to 10 mins.
    Does any one of you know the reason why it is happening like this?
    Regards.

    When the info package status turns to green : final message is :
    No data available
    Diagnosis
    The data request was a full update.
    In this case, the corresponding table in the source system does not
    contain any data.
    System Response
    Info IDoc received with status 8.
    Procedure
    Check the data basis in the source system.
    Diagnosis
         The data request was a full update.
         o   In this case, the corresponding tab
                 contain any data.
         o   System Response
                 Info IDoc received with status
                 Procedure
    Check the data basis in the source system.
    Analysis
    ========
    No data available in the source system for this selection
    No further action necessary
    When the status was red, I checked BD87 and SM58 and there were no entries.
    The corresponding job in sm37 took 869 seconds to complete. Below was the job Log.
    Job started
    DATASOURCE = 0CO_PC_02
    Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 0 records
    Result of customer enhancement: 0 records
    Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 0 records
    Result of customer enhancement: 0 records
    IDOC: Info IDoc 2, IDoc No. 1345319, Duration 00:00:00
    IDoc: Start = 24.10.2011 18:29:54, End = 24.10.2011 18:29:54
    Synchronized transmission of info IDoc 3 (0 parallel tasks)
    IDOC: Info IDoc 3, IDoc No. 1345330, Duration 00:00:00
    IDoc: Start = 24.10.2011 18:44:18, End = 24.10.2011 18:44:18
    Job finished.
    PLease help.
    Regards.

  • DSO activation in Process Chains - takes long time

    Dear All,
    We have included DSO activation in Process Chains. This process takes a long time to execute. We manually cancel the corresponding process in Process Overview and repeat it from chain. The chain runs daily and this issue also occurs on a daily basis.
    Does anyone one of you have an idea of how to deal with this performance issue?
    Regards.

    Figure out in which class does your process fall in:
    Class A- High Priority
    Class B- Medium Priority
    Class C- Least Priority
    Background processes
    Class A jobs
    The number of work processes reserved for job class A is a subset of the number of background processes.
    You should only reserve work processes for job class A if it makes sense within your system organization. Work processes reserved for class A jobs are no longer available for job classes B or C.
    Set parallel processing for a specific BW process in the (variant) maintenance of the process
    Call the function for setting the parallel processes.
    You can call the function in the process variant maintenance of a process chain or in the process maintenance. The function call varies for the different BW processes.
    For example, in the data transfer process you call the function with Goto-->  Background Manager Settings.
    The Settings for Parallel Processing dialog box appears
      Under Number of Processes, define the maximum number of work processes that should be used to process the BW process.
    If you enter 1, the BW process is processed serially.
    If you enter a number greater than 1, the BW process is processed in parallel
    In the Parallel Processing group frame, make the relevant settings for parallel processing in the background:
    Enter a job class for defining the job priority.
    The job priority defines how the jobs are distributed among the available background work processes
      In the group frame Parallel Processing, you can define whether parallel processing should take place in dialog work processes or in background work processes for the processes ODSACTIVAT, ODSSID and ODSREQUDEL for the DataStore object
    Transport:
    The entries in tables RSBATCHPARALLEL and RSBATCHSERVER are written on a transport request of the Change and Transport System.
    Edited by: ram.pch on Oct 7, 2011 9:55 PM

  • Infopackage in process chain taking long time to run

    HI Experts,
    One of the element (Infopackage) in process chain(Daily process chain) is taking much longer time(6 hr and still runing) as generally it takes 15-20 mins to complete and the status is in yellow and still running in process monitor without giving any clear picture of  error. Manually we are making the staus red and we are updating from PSA and this time it is getting completed in time as specified.
    Flow from PSA to datatarget(DSO) in series
    For last one week we are facing same issue and i would like to mention that we don't have access to SM37,SM12 to look the logs
    and any locks.
    without this i need to investigate what is the root cause for the same.
    with regards,
    murali

    Hi,
    please find the job log.
    Date
    Time
    Message
    MsgID/No./Ty
    13.12.2010
    21:45:30
    Job started
    00
    516
    S
    13.12.2010
    21:45:30
    Step 001 started (program SBIE0001, variant &0000000109368, user ID RFCUSER)
    00
    550
    S
    13.12.2010
    21:45:30
    Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
    R3
    413
    S
    13.12.2010
    21:45:30
    DATASOURCE = 2LIS_17_I3HDR
    R3
    299
    S
    13.12.2010
    21:45:30
    RLOGSYS    = PBACLNT200
    R3
    299
    S
    13.12.2010
    21:45:30
    REQUNR     = REQU_D9GSSV08BTS93Z6Y7XWP1ZEUJ
    R3
    299
    S
    13.12.2010
    21:45:30
    UPDMODE    = D
    R3
    299
    S
    13.12.2010
    21:45:30
    LANGUAGES  = *
    R3
    299
    S
    13.12.2010
    21:45:30
    R8
    048
    S
    13.12.2010
    21:45:30
             Current Values for Selected Profile Parameters               *
    R8
    049
    S
    13.12.2010
    21:45:30
    R8
    048
    S
    13.12.2010
    21:45:30
    abap/heap_area_nondia......... 0                                       *
    R8
    050
    S
    13.12.2010
    21:45:30
    abap/heap_area_total.......... 25500319744                             *
    R8
    050
    S
    13.12.2010
    21:45:30
    abap/heaplimit................ 40000000                                *
    R8
    050
    S
    13.12.2010
    21:45:30
    zcsa/installed_languages...... ED                                      *
    R8
    050
    S
    13.12.2010
    21:45:30
    zcsa/system_language.......... E                                       *
    R8
    050
    S
    13.12.2010
    21:45:30
    ztta/max_memreq_MB............ 2047                                    *
    R8
    050
    S
    13.12.2010
    21:45:30
    ztta/roll_area................ 3000320                                 *
    R8
    050
    S
    13.12.2010
    21:45:30
    ztta/roll_extension........... 2000000000                              *
    R8
    050
    S
    13.12.2010
    21:45:30
    R8
    048
    S
    13.12.2010
    21:45:31
    70 LUWs confirmed and 70 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA
    RSQU
    036
    S
    13.12.2010
    21:45:33
    Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 9,895 records
    R3
    407
    S
    13.12.2010
    21:45:33
    Result of customer enhancement: 9,895 records
    R3
    408
    S
    13.12.2010
    21:45:33
    Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 9,895 records
    R3
    407
    S
    13.12.2010
    21:45:33
    Result of customer enhancement: 9,895 records
    R3
    408
    S
    13.12.2010
    21:45:33
    PSA=0 USING & STARTING SAPI SCHEDULER
    R3
    299
    S
    13.12.2010
    21:45:33
    Asynchronous send of data package 1 in task 0002 (1 parallel tasks)
    R3
    409
    S
    13.12.2010
    21:45:34
    IDOC: Info IDoc 2, IDoc No. 5136702, Duration 00:00:00
    R3
    088
    S
    13.12.2010
    21:45:34
    IDoc: Start = 13.12.2010 21:45:30, End = 13.12.2010 21:45:30
    R3
    089
    S
    13.12.2010
    21:45:35
    Asynchronous transmission of info IDoc 3 in task 0003 (1 parallel tasks)
    R3
    413
    S
    13.12.2010
    21:45:35
    Altogether, 0 records were filtered out through selection conditions
    RSQU
    037
    S
    13.12.2010
    21:45:35
    IDOC: Info IDoc 3, IDoc No. 5136703, Duration 00:00:00
    R3
    088
    S
    13.12.2010
    21:45:35
    IDoc: Start = 13.12.2010 21:45:35, End = 13.12.2010 21:45:35
    R3
    089
    S
    13.12.2010
    21:55:37
    tRFC: Data Package = 1, TID = 0AF0842B00C84D0694000F00, Duration = 00:10:03, ARFCSTATE = SYSFAIL
    R3
    038
    S
    13.12.2010
    21:55:37
    tRFC: Start = 13.12.2010 21:45:34, End = 13.12.2010 21:55:37
    R3
    039
    S
    13.12.2010
    21:55:37
    Synchronized transmission of info IDoc 4 (0 parallel tasks)
    R3
    414
    S
    13.12.2010
    21:55:37
    IDOC: Info IDoc 4, IDoc No. 5136717, Duration 00:00:00
    R3
    088
    S
    13.12.2010
    21:55:37
    IDoc: Start = 13.12.2010 21:55:37, End = 13.12.2010 21:55:37
    R3
    089
    S
    13.12.2010
    21:55:37
    Job finished
    00
    517
    S

Maybe you are looking for