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

Similar Messages

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...

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

My BDOCs in CRM are all waiting with yellow status

I don't know why my BDOCs(transaction smw01) are all waiting with yellow status. Shouldn't they be automatically transfering data to my data source. If i manually process the BDOC then data goes to the datasource which can be seen via transaction RSA3. Help?
Message was edited by: Prakash Singh

hi Prakash,
again oss note 692195-FAQ: Sales Analytics and CRM-BW data Extraction ?
bwa5 and bwa7, delta is activated ?
and initialization performed in bw ?
626214 619122
3. If there are queues in SMQ1 with erroneous status then activate
   these queues.
   In Transaction SMQ1 if there are Queues existing with
   names beginning with CRM_BWAn (n is number) then
   activate these queues in the same transaction.
4.a)If required activate the datasource
    Go to transaction BWA5   > select the required datasource and
    activate.
4 b) The Delta may not be active ,activate the delta in BWA7 by
  selecting the name of the datsource and pressing the candle icon for
  'activate delta'.
Symptom
There may be problems or issues related to data tranfer from CRM to BW.
Other terms
CRM-BW extraction,upload,initial,delta,full upload ,Sales Analytics,
Reason and Prerequisites
There could be errors in customization or program errors due to which
data may not be transferred or incorrectly transferred to BW.
Solution
Question 1 : The Extraction from CRM to BW takes a very long time. What
can be done? (Performance Issues)
Question 2 : On executing transaction RSA3 I get records but I find 0
records when I load data from BW request.(No Data Available).
How can I extract data in this case?
Question 3 : The Deltas for my data source are not extracted . What can
I do?
Question 4: How can I extract the fields, which are not provided in the
standard data source extraction ?
Question 5: I am unable to extract user status correctly.What should I
do?
Question 6 : What can I do when the activity/Opportunity/Complaint
reasons(Code,CodeGruppe,Katalogart) are not extracted?
Question 7: What can I do if the deleted opportunities
are not reflected in BW?
Question 8: How do I activate the metadata?
Question 9: I donot get any records for the delta upload of my attribute
datasource(s).What is to be done?
Question 10: What do the status BWSTONESYS0 , BWSTONEUSS0,BWSTTECSYS0
and various other BW status mean ?
Solutions
Question 1 : The Extraction from CRM to BW takes a very long time. What can be done? (Performance Issues)
Suggestion 1: Please implement notes 653645 (Collective note) and
639072(Parallel Processing).
The performance could be slow because of the wrong control parameters
used for packaging.
You can change the package size for the data extraction.
Also note that changing the package size in the transaction SBIW
would imply a change for all the extractors. Instead, you could
follow the path in the bw system.
Infopackage (scheduler)    > Menu 'Scheduler'   > 'DataS. default data
transfer'   > maintain the value as 1500 or 1000(This value is variable)
The package size depends on the Resources available at the customer side
(The no of parallel processes that could be assigned =
1.5 times the no of CPU's available approx.)
Question 2 : On executing transaction RSA3 I get records but I find 0
records when I load data from BW request.(No Data Available)
Suggestion 2: First check if there are any entries in the table
CRMD_ORDER_INDEX.Only if there are entries in this table you can
extract records.
If this is not the case then,
It is possible that the user does not have sufficient
authorities for extraction of the relevant objects.
Additionally, please review and implement the following notes
615670
161570
150315
618953
If you are in the release 4.0 then
To do BW extraction with the user please see that the following
authorization object exists(display mode is enough):
CRM_ACT, CRM_OPP, CRM_LEAD, CRM_SAO, CRM_SEO, CRM_CO_SE, CRM_CO_SC
CRM_CO_SA, CRM_CON_SE, CRM_CMP, CRM_ORD_OP, CRM_ORD_LP, CRM_ORD_PR
CRM_ORD_OE, CRM_CO_PU, CRM_CO_PD, CRM_ORD_PO
(all these objects are linked to transaction crmd_order).
Question 3 : The Deltas for my data source are not extracted . What can I do?
Suggestion 3: Please check the following.
Please Check if the services have been generated in transaction GNRWB.
If they are not active(not marked 'X' before their names) then activate
the services following the steps here.
Go to transaction GNRWB
Select BUS_TRANS_MSG
Select (on the right, the services) : BWA_DELTA3, BWA_FILL, BWA_queue
Press Generate.
Also check for the following:
1. The delta should have been initialized successfully.
2. Confirm that all Bdocs of type BUS_TRANS_MSG
   are processed with success in SMW01.
3. If there are queues in SMQ1 with erroneous status then activate
   these queues.
   In Transaction SMQ1 if there are Queues existing with
   names beginning with CRM_BWAn (n is number) then
   activate these queues in the same transaction.
4.a)If required activate the datasource
    Go to transaction BWA5   > select the required datasource and
    activate.
4 b) The Delta may not be active ,activate the delta in BWA7 by
selecting the name of the datsource and pressing the candle icon for
'activate delta'.
5. In BW system
   Go to transaction RSA1   > modeling   > infosources   > select the
   infosource   > right mouse click on the selected
   infosource   > choose option replicate datasource
    Activate the infosource.
6. Go to the scheduler for the infosource   > select delta in the
    update >choose the option PSA only (in the Processing tab)
    > start immediately
Check the entry in the RSA7 in the OLTP(CRM system)
Question 4: How can I extract the fields, which are not provided in the standard data source extraction .
Suggestion 4: Follow the steps mentioned below.
1. Enhance Extract Structure with the required fields. (Create & include
   an append structure to the extract structure via transaction RSA6).
2.a) Release the fields of the append for usage. ( To do this, double
   click on the Datasource and remove the flags in the column 'Hide
   Field' for all fields of Append. )
2.b)If the new fields cannot be seen in the extract structure of
    the transaction BWA1 then change and save the datasource, and then
    activate it in RSA6.
3. Define your mappings in BADI (CRM_BWA_MFLOW) to fill these fields.
Goto SPRO .
Follow the path ->
SAP Implementation guide ->Implementation with other mySAP components ->
Data transfer to the Business Information Warehouse->
Settings for the application specific datasources (CRM)->
Settings for BW adapter->
Badi :BW adapter :Enhancement of datasources in messaging flow.
4. Replicate the new Datasource to BW.
5. Expand the Communication Structure in BW.
6. Maintain transfer Rules for the new Datasource.
7. Activate the trasfer rules and perform the upload.
Question 5: I am unable to extract user status correctly.What should I
do?
Suggestion 5 :Check the following notes
531875
616062
713458
700714
765281
Question 6 : What can I do when the activity/Opportunity/Complaint
reasons(Code,CodeGruppe,Katalogart) are not extracted.
Suggestion 6 :Check the following notes
481686
516820
603609
617411
711146
Question 7:Deleted opportunities are not reflected in BW.
Suggestion 7: Check the note 706327.
Question 8: How do you activate the metadata?
Suggestion 8:CRM BW adapter meta data has to be activated first before
it is available in the system. You can use Transaction BWA5 to copy the
meta data for selected DataSources. You can reach the transaction via
the IMG maintenance 'SAP Reference IMG -> Settings for SAP Business
Information Warehouse -> Activate BW Adapter Meta Data'. For more
information, see the documentation on the IMG activity 'Activate BW
Adapter Meta Data'. (Note 432485)
Question 9: I donot get any records for the delta upload of my attribute
datasource(s).What is to be done?
Suggestion 9: In case of attribute datasources, it is possible that the
entry for the GUID is missing in the table SMOXAFLD.
If , for example the datasource 0CRM_OPPT_ATTR is not giving deltas
then you can follow the steps:
1)If Delta process is active for the attribute datasource e.g.
     0CRM_OPPT_ATTR, then stop the delta process in the BW
     system
2) In the CRM system, Make the entry in the table SMOXAFLD
   for the datasource with the Key
   as 0CRM_OPPT_ATTR     GUID 3) Save the entry.Activate the datasource                           4) Check that the above entry is replicated in smoxafld_s also    after this.               5) Create a transport request manually for the following    object             R3TR   SMO4   0CRM_OPPT_ATTR
Question 10: What do the status BWSTONESYS0 , BWSTONEUSS0,BWSTTECSYS0 and various other BW status mean ?
Suggestion 10: The BW status are used to extract system and user defined
status.
The BW status are defined in the customization settings in SPRO.
Check for-> Status Concept for BP/Product/CRM objects
Here goto-> Process user status You will find the documentation attached here for the user status. Going inside the transaction you will find the status groups USS0, ZIOP,ZMOP etc. The names of the various BW status are derived from this For ex. BW + ST+ One + USS0 gives the name of the field BWSTONEUSS0 or BWST + ONE + ZMOP = BWSTONEZMOP (Master opportunity values) (which means BWST + (status group name) + status object group name) Double clicking on any of the object groups will take you to the values that these status can have . For ex. BWSTONEUSS0 in your system can have values E001 ,E002,E003,E007 which will be shown in RSA3 as BW status values 1,2,3,7, respectively.
Similarly we have Goto -> Process system status (in SPRO). Here you can get the values for the system status in exactly the same way as BWSTONESYS0(Lifecycle status) , BWSTTECSYS2 (Error) etc. In RSA3 you get the names as BW status, To know which corresponds to which status here,Goto the record list in RSA3 . Here goto Settings - Layout -Current . Right click -> Press Show technical field names . You will be able to see the BW status names and will be able to adjust the layout accordingly.

Process chain stopping in middle

process chain stopping in middle , after a info-object present in the process chain has been manually set to green.Please advice me what to do????

Hi,
Please follow the below steps:
Step 1: At the step where the process chain is stuck
Go to display messages -chain- copy variant, instance & start date
Step 2: Go to se16, table rspcprocesslog  execute
Copy as below,
Variant-- variante
Instance instance
Batch datestart date
This will give a single entry in the table rspcprocesslog.
Step 3: Go to se37, input FM RSPC_PROCESS_FINISH and execute
Copy
Rspcprocesslog u2013 instance -
I_INSTANCE.
Rspcprocesslog u2013variante -
I_VARIANT
Rspcprocesslog u2013 logid----I_LOGID
Rspcprocesslog u2013 type ---I_TYPE
Enter u2018Gu2019 for parameter I_STATE and press execute (F8).
After executing the above FM, with the above stated parameters, the actual process will be set to green and the following process in the chain will be started and the chain can run to the end.
-Vikram

Process chain doesn't even with errors in bacrground processes

Hi experts,
I need your help again.
My client is using a process chain to automate the consolidation process in SEM-BCS. This is done using variants of programs UCBATCH01 and UCBATCH11.
The problem now is that the process chain doesnu2019t stop even though the steps have errors. The validation tasks are the best example.
Do you know a way to make the process chain stop?
Best regards
João Arvanas,

Hi Marsy,
I'm having the same issue as discussed in this thread and since I am still very new in BCS I have some additional question
1. Is the status table for task that you are referring to = /1SEM/UCS001USV1 ?
2. I read in another source that status table only store the latest run log ? not historical ? is that true or would you might be aware of a historical table ?
3. The table split cons area task run status into each of the cons unit, so if one of them has error, basically the task error
Thank You,

My BDOCs(transaction smw01) are all waiting with yellow status

I don't know why my BDOCs(transaction smw01) are all waiting with yellow status. Shouldn't they be automatically transfering data to my data source. If i manually process the BDOC then data goes to the datasource which can be seen via transaction RSA3. Help?

Hi Kaushal,
I am also facing the similar problem as Prakash, I don't know why my Bdocs are all waiting with yellow status in smw01.I followed your steps but in SMOHQUEUE the status of the queue demon is Hold because of this the status of Bdocs are yellow.If yes would you pls tell me the steps to turn it to green.If i manually do(Reprocess or register that queue in smqr) everything is working fine but is there any way we can turn Bdocs from yellow to green automatically.I appreciate it in advance. If you find any doc. pls fwd it to [email protected]
Thanks a lot
With Regards
Nagamani.

Help with Process Chain - Stop remaining Processes if Package returns 0 rec

Hi, i have a Process Chain that starts with a single InfoPackage. Then it goes on to distribute the load to multiple DSO's and then onto DSO Activation. I would like the Process Chain to stop right after the InfoPackage if no records are loaded.
Is this possible using the decision variant somehow? Any details on how to achieve this are greatly appreciated!

Hi ,
The request is goin to red status when 0 records are pulled in. There is a option in info package so that even when 0 records come in the request status would be green.
Open your info package , then in the menu goto "Scheduler > Treatment of warnings > Select Green" so that in future even if the info package pulls 0 records the status would be green . then the activation step in the process chain would also be carried out smoothly.
In this way you need not manually change any request status to green . Saves you time.
regards
Venky

Process chain stops - previous processes are green

Hi All,
We have a process chain that loads our master data each night. It chain is mostly made up of infopackages (mostly full loads) and the change run for those objects. We recently upgraded from 3.5 to BI7, SP16.
Since the upgrade, this chain, and a few others just seem to stop. They will start, and successfully complete some of the processes in the chain (all green), but then will not move on to the next process. The next process will not be yellow, it just won't start. The overall status of the chain is yellow.
I am 100 percent sure there are no other chains running during this time frame. This chain has been running for over 4 years in production, and we have never encountered this issue.
Last night, I removed the chain from the schedule, and then rescheduled. I'm not sure if that is going to prevent us from having this issue. I have also set the priority to high.
Should this prevent us from encountering this issue again? I have searched OSS and found some related notes, but we are on a higher support pack than what is in the notes, so they are already applied.
Any suggestions?
Thanks!
Charla

The first thing that I'd recommend is to look at the Start Process Variants for the Process/Local Chains that are not starting. Specifically, I would check to see if the scheduling in those Start Process Variants are set to Direct Scheduling with Immediate Start or set to Start Using Meta Chain or API. It is possible that the conversion from BW 3.x to BW 7.x change the parameters of the scheduling withing the Start Process Variants, even though they were not physically changed and transported.
My recollection is, when we upgraded Support Package Stacks, we had some Local Chains just change on their own where the Immediate Start checkbox mysteriously become unchecked.

Process Chain stops if no data

Hello,
My proccess chain stops if one of my infopackages doesn't return any data. How do I change the settings so no data returns a 'success' status??
Thanks
Sheena

Hi,
if there is no data then you process will be in yellow colour, and other process are waiting for this, we are also having the same problem and we change the status in monitor to green from yellow couple of times after that system automatically converts the status to green from yellow even though there is no data, i think you can try this option, which we used earlier and working fine now.
Regards
Sankar

Process chain stopped and unable to trigger next process

Hi all , i am working on process chains, today process completed at DTP and the next process at activation of dso process failed and the rest of the pc completed even though the activation process is red. after the completion of that , chain process stopped, next pc didnt started. plz help me wiht this, thanks in advance..

you can evaluate a local chain as 'green' even if one of the steps is 'red'. in the planning view of the process chain, go to process chain --> attributes --> process status valuation. flag the checkbox. this will enable the next pc to start even after a red status of the local chain...
detailed info:
Red Outcome Renders Chain Green If Process Is Red
If errors are raised for processes that have scheduled an event "With Errors" they are judged as successful for the determination of the overall status of the chain run.
Use
If this indicator is set, all the processes in this chain with errors are judged as successful with regard to the overall status of the run, if they have scheduled a successor process "With Errors" or "Always".
Dependencies
Mailing and alerting is not affected by this indicator. This is also triggered for processes with errors if this has a successor process "With Errors".
Example
You use this indicator in meta-chains to evaluate the run of a subchain as successful in spite of errors in "unimportant" processes. The successors to this process are "always" scheduled, while the successors to key processes are only scheduled "With Success".
Accordingly, successors in the subchain within the meta-chain are only scheduled "With Success"; however they do continue to run if errors have only occurred in the unimportant processes of the subchain.

Process chain stopped in the middle ?

I have a PC in production and its really strange that after the DTP step ,ODS activation step in the PC did not run and the chain status shows in the yellow color, I know if it fails in the activation step we need to see the error and fix it. But here neither its yellow which means running and not red, its just did not execute and the dtp is successful....and there are a lot of chains next to this chain. SO how to make it run, and what do i do ? there is no job running in the SM37 related to it. Please help.

Hi ,
Please perform the below steps, this will solve your issue.
Step 1: At the step where the process chain is stuck
Go to display messages -chain- copy variant, instance & start date
Step 2: Go to se16, table rspcprocesslog  execute
Copy as below,
Variant-- variante
Instance instance
Batch datestart date
This will give a single entry in the table rspcprocesslog.
Step 3: Go to se37, input FM RSPC_PROCESS_FINISH and execute
Copy
Rspcprocesslog u2013 instance -
I_INSTANCE.
Rspcprocesslog u2013variante -
I_VARIANT
Rspcprocesslog u2013 logid----I_LOGID
Rspcprocesslog u2013 type ---I_TYPE
Enter u2018Gu2019 for parameter I_STATE and press execute (F8).
After executing the above FM, with the above stated parameters, the actual process will be set to green and the following process in the chain will be started and the chain can run to the end.
You can also check this blog:
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
-Vikram

Process chains stopped

Hi,
I am new to BI, my BI server got shotdown due to some reason and process chains are stopped. so how do it re run again? how do check which are stopped and how do re run manually ? any problem if we run manually ?can pls help any body. thanks in advance.
Sari. K.

Hi Sasi,
Plz find here one of our expert explanation..
How is it possible to restart a process chain at a failed step/request?
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.
Therefore you need to open the messages of a failed step by right clicking on it and selecting 'display messages'.
In the opened popup click on the tab 'Chain'.
In a parallel session goto transaction se16 for table rspcprocesslog and display the entries with the following selections:
1. copy the variant from the popup to the variante of table rspcprocesslog
2. copy the instance from the popup to the instance of table rspcprocesslog
3. copy the start date from the popup to the batch date of table rspcprocesslog
Press F8 to display the entries of table rspcprocesslog.
Now open another session and goto transaction se37. Enter RSPC_PROCESS_FINISH as the name of the function module and run the fm in test mode.
Now copy the entries of table rspcprocesslog to the input parameters of the function module like described as follows:
1. rspcprocesslog-log_id -> i_logid
2. rspcprocesslog-type -> i_type
3. rspcprocesslog-variante -> i_variant
4. rspcprocesslog-instance -> i_instance
5. enter 'G' for parameter i_state (sets the status to green).
Now press F8 to run the fm.
Now the actual process will be set to green and the following process in the chain will be started and the chain can run to the end.
Of course you can also set the state of a specific step in the chain to any other possible value like 'R' = ended with errors, 'F' = finished, 'X' = cancelled....
Check out the value help on field rspcprocesslog-state in transaction se16 for the possible values.
Regards.....KP

Is a save step neccessary in a Process Chain when loading hierarchies with an ABAP program?

We are loading hierarchies using the ABAP routine found here in the SDN.
We have come accross the issue where the process chain loads successfully, but does not update the hierarchy (this problem is documented in the SDN). It is not a consistent issue, but it causes problems when it does occur.
OSS note 652856 points out that a SAVE HIERARCHY step is needed after the load and before the Change Attribute run.
We have added the step to the process chain, which leads me to the question.
In using the ABAP program to load hierarchies is the addition of the Save Hierarchy step necessary?
Will that resolve the issue with hierarchies not updating?

Hi Bill,
Yes, SAVE HIERARCHY step is required when hierarchies are loaded as part of process chain. This step ensures that the hierarchy data loaded to BW has been saved. Then we have to run ACR so that these hierarchies will be activated and adjusted.
This is the reason why even the hierarchy data loaded using infopackage needs this step. This step is not required if the Infopackage is triggered manually.
This link will help you in better understanding
http://help.sap.com/saphelp_nw04/helpdata/en/3d/320e3d89195c59e10000000a114084/content.htm
Regards
Chandu

Process Chain Stopped in BI PRD

Data Loading Error :
Hi All,
In BI PRoduction, all the process Chains are stopped and while Checking the errors, it is giving the error message as
Errors while sending packages from OLTP to BI
Diagnosis
No IDocs could be sent to BI using RFC.
System Response
There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of BI.
Further analysis:
Check the TRFC log.
You can access this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Error handling:
If the TRFC is incorrect, check whether the source system is fully connected to BI. In particular, check the authorizations of the background user in the source system.
Morning, I have logged into BW Production, and saying BW Production is down. This is happening frequently.By the help of basis, the system is up.
Please help on this issue.
Thanks,
Jelina.

Thanks for the reply.
I have Checked in ST22 and found, Time Out error is there.
These are the error messages in ST22.
The program "SAPMSSY1" has exceeded the maximum permitted runtime without interruption and has therefore been terminated.
Error Analysis :
After a specific time, the program is terminated to make the work area available to other users who may be waiting.
This is to prevent a work area being blocked unnecessarily long by, for
example:
- Endless loops (DO, WHILE, ...),
- Database accesses with a large result set
- Database accesses without a suitable index (full table scan)
The maximum runtime of a program is limited by the system profile
parameter "rdisp/max_wprun_time". The current setting is 3600 seconds. If this time limit is exceeded, the system attempts to cancel any running SQL statement or signals the ABAP processor to stop the running program. Then the system waits another 60 seconds maximum. If the program is then still active,the work process is restarted.
How to correct the Error :
Programs with long runtime should generally be started as background jobs. If this is not possible, you can increase the system profile parameter "rdisp/max_wprun_time".
Depending on the cause of the error, you may have to take one of the following measures:
- Endless loop: Correct program;
- Dataset resulting from database access is too large:
Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
(for example);
- Database has unsuitable index: Check index generation.
If the error occures in a non-modified SAP program, you may be able to find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following keywords:
"TIME_OUT" " "
"SAPMSSY1" or "SAPMSSY1"
"REMOTE_FUNCTION_CALL"
If you cannot solve the problem yourself and want to send an error notification to SAP, include the following information:
1. The description of the current problem (short dump)
   To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
   Display the system log by calling transaction SM21.
   Restrict the time interval to 10 minutes before and five minutes after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP program: The source code of the program
   In the editor, choose "Utilities->More Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
Thanks,
Ram
Edited by: Ram Siva on Jul 28, 2009 6:59 AM

Process chain stops in infopackage with yellow status

Similar Messages

Maybe you are looking for