Process Chain Red 'X', Exec Infopckg Yellow, Infopckg monitor/data correct

Dear and respectable colleagues of the forum,
I am experiencing a problem in a process chain when executing infopackages. The process chain has 6 "Execute infopackage" processes. Sometimes (1 of 4 attempts average) my process chain ended with red color with 'X' status in the Process Chain Display Log View.
Reviewing within the chain Log, there is one of the "Execute infopackage" processes that appears in yellow color (it loads from direct update ODS to an infocube). However, revising the Logs for its corresponding Infopackage execution I found that it says that "Data successfully updated". Moreover, If I review the data loaded it seems to have been loaded correctly.
Then, Why does the "Execute infopackage" process in PC finishes with yellow color if the Infopackage execution itself finishes correclty?
To complete the whole scenario: I execute this process chain every night from an Abap program; the program has a Loop that traverses a table, and executes the process chain as many times as the quantity of rows in that table (table has 10 rows meaning offices). As you can understand, the chain is executed 10 times, and the error occurs in any of the 6 "Execute infopackage" processes indistinctly.
I review ST22 and SM37 for all users for the datetime when the error occured butnothing bizarre was reported. It is left to review SM21.
The following is the detail of messages.
Logs for Execute Infopackage
   Data successfully updated
Monitor of Infopackage
  Details Tab
     Requests (messages): Everything OK      
     Extraction (messages): Everything OK
     Transfer (IDocs and TRFC): Everything OK
     Processing (data packet): Everything OK
       Data Package 1 ( 45 Records ) : Everything OK
         Transfer Rules ( 45  -> 45  Records ) : No errors
         Update rules ( 45  -> 45  Records ) : No errors
         Update ( 45  new / 0 changed ) : No errors
         Processing end : No errors
     Process Chains : Errors occurred
       Llena cubos de carteras vtas sec por distrib - autom

Dear s v desh,
I am on SAP BW 3.5, I already checked the cube and it is green - all right.
The message in the infopackage excution node in the process chain says (non-error):
  "Data successfully updated"
The error message in process chain monitor (log) says:
......"Overall status: Error occurred: or: Missing messages
............Process Chains : Errors occurred"
I just realized that there is no messages at all in the infopackage monitor (log).
I have received a clue, someone asked me to review note 1396417, and I will.
Regards
Juan Alonso Teevin

Similar Messages

  • Process chain stops in infopackage with yellow status

    Hi Gurus,
    We are experiencing some difficulties regarding the use of process chains with warnings. Our SAP BI system is connected to an ETL server which feeds us with data from other systems. We have a query that has a push-button functionality that starts a process chain beginning with data extraction with an infopackage and ending in a infocube. The problem we have nowadays is that whenever the ETL workflow fails the infopackage status remains yellow, while our objective would be a red status. To try and solve this problem we forced a timeout in the infopackage. Once we check the log in the process chain it displays a message containing something like "status request modified , do you wish to add subsequent processes?", if we say yes it refreshes the status of the infopackage to red and it all goes ok. What we want is to get rid of this warning and that the status is automatically changed. We've checked other posts and we didn't reach any conclusion... Note 708480 gives us a possibility of automatic desicion but how could we integrate it in our process chains since it is based on shcedulling and not triggers?
    Your help would be much appreciated,
    Thank you
    Bruno Rodrigues

    Hi,
    We have two connected links in the process, one to continue the process chain when process status is green and other link to red status. The problem is the process status remains yellow until our confirmation in pop-up.
    The process chain should be started by user in web browser. So, it isn't possible run it in background.
    Thank you,
    Regards,
    BR

  • Check syntax of process chain get three variants with yellow color

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

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

  • Archiving using Process Chain, writes to archive but doesn't delete data

    I have created an Archiving Process for a cube, and set it up to automatically start the "delete". I then created a process chain to execute the Archiving Process.
    When I execute the process chain, here's what I notice in the joblogs:
    1) Archiving job runs, writing the selected data to archive file
    2) A separate deletion job is started, but the deletion job runs in "test" mode (which seems kind of like simulation mode) and identifies the records it would delete but it never actually deletes the data from the cube.
    3) In SARA (Archive Administration), this run shows up as an "Incomplete Archiving Session", showing that archiving step was complete but deletion hasn't occured.
    I am able to delete the data by running the "Delete" manually in SARA and then the "Archiving Session" goes to "completed" status. When I run it manually from SARA, the job log shows that it is running in "production mode" and not "test mode".
    My question is...  Is there a way to start the deletion in "production mode" and not "test mode" when I run the process chain?
    Or is this a bug, that I should report to OSS?
    Thanks much.
    Padmaja

    Hello,
    You can set the Production Mode in Customizing
    Have you tried with this function module ARCHIVE_OPEN_FOR_DELETE
    Also see [Developing Delete Programs|http://help.sap.com/saphelp_nw04/helpdata/en/2a/fa0495493111d182b70000e829fbfe/content.htm]
    Note 1119944 - Archiving request:Production mode instead of simulation mode
    Thanks
    Chandran

  • Process chain program variant will not change from yellow...

    Hello,
    <b>Problem:</b>
    I have a process chain that has two branches with 3 process chain variants on each leg in a parallel configuration.  The process chain variants run different program variants.  I am using variant object called "ABAP Program with Success/Failure " which can have a yellow, green, or red status and has status arrows that can be either red or green that connect to other process chain variants.  The program executed with these variants is a customized BPS UPC_BUNDLE_EXECUTE program.  When I run this PC the first variant on each leg usually hangs indefinitley on the yellow status.  In the Backg tab log (double click PC variant in Log View) I can see the various SQL code that was ran.  The last line of the log is an SQL-END:...  Sometimes it will get past the first 2 varaints and hang on the next set of 2.  Other times it will just hang on the last variant of one leg.  It is very sporadic.
    <b>What I have observed and tried:</b>
    If I check my SM51 for the server the chain is running on I can see that the program in question is not running.  If I run the same program through SE38 that runs via a PC variant it runs sucessfully in an appropriate amount of time.  If I kill the process that has been running indefinitley through SM51 the process chain variant will go from a yellow status to a red as expected.
    I changed they way I ran the programs from running in parallel in 2 legs to running all of them in one leg serially.  That did not work.  At least one program variant will hang on the yellow status.
    I replaced all the variants using "ABAP Program with Success/Failure" to "ABAP Program" which has a red/green status but no red or green arrows, but black coming out of the variant forcing it to move down the chain on a sucess or failure.  The process chain variants also hung in the yellow status using the "ABAP Program" variant. 
    I have tried starting the process chain using both "Direct Scheduling" with "Immediate" and "After Event."  I have also kicked it off using "Start Using Meta Chain or API" so it was functioning as a sub process chain. Programs were still yellow in every case without changing to red or green. 
    I created new process chain variants for every single program/variant that I am using.  Still no luck.
    I have tried removing the chain from the schedule and re-activating and re-running and still no luck. 
    Thanks in advance,
    Gary Martins

    bump

  • How to stop the process chain showing status as yellow but no process step

    Dear Friends,
    How to stop the process chain showing status as yellow but no process step is running in that process chain.
    We have manually triggered the process chain for sales it finished successfully till load data but the next step is create index and DB statistics. Both of this steps are in unscheduled position only and no background job for this.
    Please guide me.
    Thanking you in advance.
    Regards,
    Shubhangi

    Hi,
      At times even I have faced this situation.  During those times, running the Function module RSPC_PROCESS_FINISH by passing the right parameters came to my rescue.
    Regards,
    Raj

  • Process chains problems : Working every day with error (red)

    Hi All,
    I have a next question, about process chains problem.
    When I start my process chains immediate, then working without errors,  but I want this process chains work every day and chainged properties, selected date/time and periodicaly (every day) but now it work with error.
    How to I find problems? What are yours offers?
    p.s. I see logs, but every day have diffence between errors.
    Regards,
    Mahir M. Quluzade

    HI,
    just check the time which you have given is OK or is overlappintg with some other job which is locking your table in process chain
    or is colliding with attribute change run
    or it fails because of lack of background processes.
    There could be numerious reasons and you need to analyze the log for this.
    But as you said the job is failing everday for different reasons..try to find the most common errors and try to remove it or mention that here.
    Thanks
    Ajeet

  • Error while executing the Process chain

    Hi Friends,
    The process chain that I scheduled is getting failed at the Infopackage loading stage.
    On checking the diplay message, I found the following log:
    Cannot stage requested data for datasource
    Error in source system
    I activated the datasource in source system, then replicated the same and tried to load data.
    But the issue remains the same.
    I checked in RSA7. The status corresponding to this datasource is in yellow status.
    Can I delete this entry and try again?
    Please suggest.
    Thanks in advance.
    Surjit P

    Hi,
    /people/mona.kapur/blog/2008/01/14/process-chain-errors
    Deadlock
    http://help.sap.com/saphelp_nw04s/helpdata/en/2e/44934257a5c86ae10000000a155106/frameset.htm
    Dead Locks
    2. Error in unit conversion
    Units of measure
    3.Error 1 in update
    When Src file is already open or not accessible.
    4.Processing no data
    theres no data selected after extraction
    5.Caller 70 missing
    "• This error normally occurs whenever BW encounters error and is not able to classify them. There could be multiple reasons for the same
    1) Whenever we are loading the Master Data for the first time, it creates SID’s. If system is unable to create SIDs for the records in the Data packet, we can get this error message.
    2) If the Indexes of the cube are not deleted, then it may happen that the system may give the caller 70 error.
    3)Whenever we are trying to load the Transactional data which has master data as one of the Characteristics and the value does not exist in Master Data table we get this error. System can have difficultly in creating SIDs for the Master Data and also load the transactional data.
    4) If ODS activation is taking place and at the same time there is another ODS activation running parallel then in that case it may happen that the system may classify the error as caller 70. As there were no processes free for that ODS Activation.
    5) It also occurs whenever there is a Read/Write occurring in the Active Data Table of ODS. For example if activation is happening for an ODS and at the same time the data loading is also taking place to the same ODS, then system may classify the error as caller 70.
    6) It is a system error which can be seen under
    the “Status” tab in the Job Over View.
    solution:
    "• If the Master Data is getting loaded for the first time then in that case we can reduce the Data Package size and load the Info Package. Processing sometimes is based on the size of Data Package. Hence we can reduce the data package size and then reload the data again. We can also try to split the data load into different data loads
    • If the error occurs in the cube load then we can try to delete the indexes of the cube and then reload the data again.
    • If we are trying to load the Transactional and Master Data together and this error occurs then we can reduce the size of the Data Package and try reloading, as system may be finding it difficult to create SID’s and load data at the same time. Or we can load the Master Data first and then load Tranactional Data
    • If the error is happening while ODS activation cause of no processes free, or available for processing the ODS activation, then we can define processes in the T Code RSCUSTA2.
    • If error is occurring due to Read/Write in ODS then we need to make changes in the schedule time of the data loading.
    • Once we are sure that the data has not been extracted completely, we can then go ahead and delete the red request from the manage tab in the InfoProvider. Re-trigger the InfoPackage again.
    • Monitor the load for successful completion, and complete the further loads if any in the Process Chain.
    6.Idoc not processed completely.
    Here the request remains yellow (in process) and with the same details (as seen in the details tab of the monitor) for an abnormally long time. Many-a-times, the port for communication is not open and re-starting the load helps. For long running jobs, it may not be advisable to restart the extraction
    Contact the BASIS administrator to push the IDOC.
    look into these links:
    /people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
    For common data load errors check this link:
    /people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
    Majority of the issues will be based on these things only..
    Hope the following links will give u a clear idea about process chains and clear ur doubts.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/events/sap-teched-03/using%20process%20chains%20in%20sap%20business%20information%20warehouse
    Business Intelligence Old Forum (Read Only Archive)
    http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/c08b3baaa59649e10000000a11402f/frameset.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/8da0cd90-0201-0010-2d9a-abab69f10045
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/19683495-0501-0010-4381-b31db6ece1e9
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/36693695-0501-0010-698a-a015c6aac9e1
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9936e790-0201-0010-f185-89d0377639db
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3507aa90-0201-0010-6891-d7df8c4722f7
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/263de690-0201-0010-bc9f-b65b3e7ba11c
    /people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
    Siggi's weblogs for data load error and how to restart process chain
    /people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
    /people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
    Hope this helps.
    pls award me some points
    thanks.
    Thanks

  • How to stop/cancel Process Chain in BI 7.0

    Hi,
    Could you tell me how to stop/cancel a process chain that hangs with status yellow or green in BI 7.0? There was an easy option to do it in 3.x, but I cannot find a similar option in 7.0.
    What happens is that at random our process chains hang at a certain variant with either yellow or even green status and do not proceed further. What happens is that in a couple of hours another pchain run occurs and it executes fine. Then again at random (might be the same day or the next day) the process chain hangs again. I think that all those "hanged" pchains pile up in the queue, so that it cause other future pchains to hang as well at some point. So, is there anyway to stop/cancel these zombie process chains when it stops at a particular event RSPROCESS in BI 7?
    Thank you,
    AG
    Message was edited by:
            AG

    Hi Frank,
    Thanks for your reply. I have a few questions.
    1)SM37 -->Kill Job
    We cannot do that because the job has already finished.
    2)SM50/sm66- ->Kill process
    There are no hanged processes to kill
    3)RSPC>Job Log>Make the process RED forecefully
    How do you do that exactly?
    4)RSPC>Process chain> main Menu"Remove from Scheduling"  OR
    5)se37-->RSPC_API_CHAIN_INTERRUPT
    give RFC BW system name(technical) and process chain name(technical) - we can do this,  but what exactly would it accomplish. Would it remove the process chain from any runs in the future or also any hanged ones in the past? An how is this step different from #4?
    Thank you,
    AG

  • Process Chain Error while activating DSO

    Hello.
    1st, let me say that I'm pretty new to BI so I apologize for the stupid question :-S
    I have a process chain (Warehouse Mangement) that failed this morning at the DSO data activation step.  It's simply because some entries have lowercase value in a field that should not.  I know how easy this is to fix in the transformation but my problem is more on how to fix the actual fail of the process chain.  Can I edit the "non-activated" data in the DSO (only 2-3 records that I need to put in uppercase) and "repair" my process chain or should I proceed another way?
    Thanks for your help.

    Hi John.
      If guess your Process Chain process ended in "Red color". Once you fix the error you can try to make "right-click" on the process with error and select "Repair". If this operation is "supported" by the activation process you won't have error.
      But I really believe that you'll have to erase the request and launch the complete process (o set of related processes) once again. It's possible that the data you want its already in the NEW-DATA table of your ODS.
      This tables is the following.  /BIC/A<your ods tech-name>40
    Hope it helps
    gdmon.-

  • Local Process Chains

    HI Guys,
    I am in the process of designing the process chains for data loading. I have a situation where I am planning to use local process chains in the meta chain. Situation is like this:I have created Meta Chain for Master Data loading, which is having 2 local process chains, one is for Attributes and another is for loading texts. I placed them in the sequential order. First Attributes chain and on successful completion of Attribute chain it should run the Text process chain. But in the system it executes the Attribute chain successfully but the text process chain is always in the YELLOW( in progress ) state even though in that process chain I have only start process. In the SM50 it shows two background process with the user id ALEREMOTE, but process chain never finishes. In the Messages of the Text process chain I see the message"Communication buffer delted from the previous run ".
    So I put the process chains in the parallel manner, meaning after start process of Meta chain I attached the two process chains so that they should execute simultaneously. But in this case too, Attribute local process chain gets executed but not the Text local process chain.
    We tried debugging the process in SM50, it seems that there is some infinite loop.
    If anybody has any clue then please reply back at your earliest. Your help is highly appreicated,
    Thanks.
    Santosh Taware

    first point, i think you can have single process chian for both attributes and texts one after other.
    second thing check in st22 if any dumps are occuring and check in the monitor in which step it is still running.
    reward if helps.

  • How to trigger a local process chain to run manually

    Dear Experts,
    In my company, I have a Daily process chain.
    In this Daily process chain, it contains many other local process chains which are grouped by modules.
    For example, I have created the following 3 process chains:
    - Accounts Receivables Process Chain which contains all the required process for loading FIAR data.
    - Accounts Payables Process Chain which contains all the required process for loading FIAP data.
    - Inventory Process Chain which contains all the required process for loading  Stocks data.
    These 3 process chains are scheduled one after the other in the main process chain which is called Daily Process Chain.
    FIAR needs to be successful before FIAP can run and Inventory chain will run only after FIAP is successful.
    Normally it runs without any problems.
    But recently, when the previous chain is successful, the next process chain does not get triggered to run.
    In the end, I have to manually execute the remaining process chains to start running.
    With this, all data are loaded, but the Daily Process Chain status for the day is yellow because it is not complete.
    Is there a program or method which I can execute or use to trigger the process chain to continue to run in the Daily Process Chain? If there is, please let me know so that I can avoid having to run the process chains manually one by one.
    Thanks in advance for your help.
    Regards,
    Shunhui.

    Check thid thread with the similar issue:
    Process Chain - Node untriggered.
    /people/siegfried.szameitat/blog/2006/02/26/restarting-processchains

  • Problem with triggering process chain

    Hi
    We have a remote process chain that calls a process chain in another system.The process chain in the other system is not getting triggered with the remote chain.
    We have 3 such remote chains and we are facing such a problem with only one of them.
    The process chain in the other system has a start variant which gets triggered( i suppose) and gives an instance id...the next step in the process chain is to load data into a ODS.Now this step remains yellow forever.When i manually try to schedule this step it gives me records and the request in the monitor screen turns green.But the process chain step continues to remain yellow.
    What can be a way out for triggering the process chain or where could the problem be?
    Please help
    Thanks,
    Suchi

    Hi Suchitra,
    Even though ur process seems to be in yellow your data loading may be completed and the  reason for it may be the delay in activation of ODs by ur PC.
    For your information please go through the below infm provided in SAp Library
    Note when loading into an ODS object and for the subsequent, event-controlled update:
    If you switched on the automatic activation in the ODS maintenance or administration, the monitor status for the request remains yellow after the load was successfully completed. Nevertheless, the subsequent processing for the InfoPackage is started, because the loading process is successfully completed.
    [http://help.sap.com/saphelp_nw04/helpdata/en/65/163d3873130057e10000009b38f842/content.htm]
    I hope ur doubt is clear.
    Regards,
    Rajkandula

  • Plzz correct me reagrding process chains.

    hi friends,
    iam  working on BW in process chains.
    i want to know the possible ways of correcting the process chains  and plz help me if iam wrong and by providing ur suggestions.
    1) whenever process chain fails ,  we will check process monitor in logview and find out  that type of load . if it full load,  we delete the request and we will restart the entire process chain.
    restarting means we will again  schedule and activate it right?
    I refer a  weblog on restarting of PC , it said  that
    Sometimes, it doesn't help to just set a request to green status in order to run the process chain from that step on to the end.
    You need to set the failed request/step to green in the database as well as you need to raise the event that will force the process chain to run to the end from the next request/step on.
    My question is why will make the request green  from red? and also if we the reuqest from rd to green , will the process chain works normally though it contains errors ?
    2) how to correct if teh load is delta load.
    Iam very much confused in handling the errors of process chains .
    can any one explain me clearly plzz. any good documentation for error handlin plzz.
    regards,
    Siddartha

    No duplicate posts please. Moderators will not entertain the duplicate posts.

  • Process chain - ODS Activation error

    Hello All,
    I have a process chain which has the following data load sequences:
    Load data to ODS
    Activate ODS
    Load data to ODS2
    Activate data ODS2
    Load data to ODS3
    Activate ODS3.
    Used the Program to RSPC_SYNCHRONOUS_RUN to schedule the process chain in Background.
    When the process chain is executed in background it loads the data to ODS1 and Activation process is not happening. It registers short dump like shown below at the end. But when i execute the same process chain in RSPC, Schedule option with Start variant set to immediate, it is activating the ODS Data and completes the process chain Succesfully.
    Help me to solve this problem.
    ABAP Short dump information:
    Invalid interruption of a database selection.
    t happened?
    Error in ABAP application program.
    The current ABAP program "GP4BRKGANFKJY5K2A3ACVGAPTN4" had to be terminated
      because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    Unable to perform database selection fully.
    record.
    t can you do?
    If the error occurs in debugging mode, you should first run the process
    without debugging activated.
    If the error persists outside debugging, you must check the application
    program more closely.
    No error requiring recovery has occurred.
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
      termination messages, especially those beyond their normal deletiondate.
    is especially useful if you want to keep a particular message
    Error analysis
        An exception occurred. This exception is dealt with in more detail below
        . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
         neither
        caught nor passed along using a RAISING clause, in the procedure "ACTIVATE_ODS"
         "(FORM)"
        Since the caller of the procedure could not have expected this exception
         to occur, the running program was terminated.
        The reason for the exception is:
        One of the database selections included a database commit.
        The selection was then supposed to continue. Before a
        database commit, however, all outstanding database selections must be
        concluded.
        Possible causes in the application program:
        Within a loop (SELECT/LOOP/EXEC SQL), one of the following
        statements is used:
        - MESSAGE (apart from MESSAGE S...)
        - COMMIT WORK
        - ROLLBACK WORK
        - CALL SCREEN
        - CALL DIALOG
        - CALL TRANSACTION
        - SUBMIT
        - BREAK-POINT
        - WAIT
        In debugging mode, a program sometimes triggers
        a "COMMIT WORK" during the database selection. As a result
        this termination may also occur in debugging mode with a correct
        program.
    A "COMMIT WORK" during debugging may be due to the following reasons:
    1. A program or screen was regenerated
        and updated in the database.
    2. Each user needs a private process in debugging mode, but
        the number of available processes is restricted. If this
        limit is exceeded, each debugging step then requires a
        "COMMIT WORK".
    The error occurred in a statement that accesses the table "/BIC/AZXOQMATR40 ".
    Thanks in Advance.
    Points will be assigned.
    Regards
    M.A

    Hi,
    If it is a daily process chain u define it on a periodic basis in the variant and it'll run successfully.
    I guess the DUMP may be due to less processes at the time u run...It is gving the same in the dump also..
    So when u run the chain immediate in the BKGD the ODS will be automatically getting the required processes dailog and bkgd to run according to ur settings and it was successful..
    U try to execute the chain using FM: RSPC_API_CHAIN_START and give the tecnical name of the chain under I_CHAIN filed and conitinue...It'll scedule the chain in the BKGD only and if it is a periodic one the chain will be automatically ready for the next run also...
    rgds,

Maybe you are looking for