Error log in Process chains...

hai friends,
am getting this error log messages while running the process chains...
There is a discrepancy between the confirmation and deletion of qRFC-LUWs
Message no. RSQU016
Diagnosis
When data was confirmed and deleted in the qRFC queue, the system found a discrepancy between the number of newly confirmed LUWs ( 2282) and the number of LUWs to be deleted ( 3424).
Where more LUWs are to be deleted than were previously confirmed, a previous delete attempt was terminated.
The LUWs were confirmed but not completely deleted from the qRFC and tRFC tables. The confirmation already ensures that the data is not transferred into the BW again with a subsequent request.
Delta extraction was continued.
Procedure
You do not need to do anything urgently.
If the message also arises during all subsequent delta requests, contact SAP Support with the message number at hand. In this case, there is a danger that the qRFC and tRFC tables run at full capacity, which may also affect other applications.
please help me friendds...

Refer to the OSS note: 583086
Also you can refer to the smililar kind of discussion in this link:
Discrepancy between the confirmation and deletion of qRFC-LUWs
Hope this helps..

Similar Messages

How to display error logs of Processed Data chain(BW) in a ALV Report

Hi Experts,
I have a requirement, to display all the errors of a Processed chain in Business Warehouse.
Is there any approach to achieve this requirement ?
Your replies will be appreciated.
Thanks in Advance,
Regards,
Giri

Some id/log tables for the report
RSPCLOGCHAIN
RSPCPROCESSLOG
Some master tables associated
RSPCCHAIN (-T)
RSPCVARIANT (-T)
RSLDPIO (-T)
RSPROCESSTYPES (-T)
FM to call to check/update status of chain/logid
RSPC_API_CHAIN_GET_STATUS
Regards,
Raymond

How to display error logs of Processed Data chain in a ALV Report

Hi Experts,
I have a requirement, to display all the errors of a Processed chain in Business Warehouse.
Is there any approach to achieve this requirement ?
Your replies will be appreciated.
Thanks in Advance,
Regards,
Giri

Hi Kodanda Pani,
Thanks your reply,
Normally we will be having many Process chains in real time BW, and those all will be scheduled in Back Ground.
If any process chain gets stuck up with any error, that error we have capture and to be display in a ABAP Report( i.e, ALV Report ).
Regards,
Giri

Error messages in Process chains

Hello BI fans
In which transaction can I maintain batch-initiated error messages from process chains.
I am not looking for the process chain variant for messages.
I would like to create messages only for errorness messages.
thanks
BEO

Hi,
Please check the forum before posting for this issue.
Here You can follow below steps:
1) right click on process type and select "create messages".
2) choose "error" and create variant for error message
3)write message body in "EDIT DOCUMENT" and mention email ID's in "Maintain Recipient list" tab
4) save and schedule the chain again
Edited by: shailesh patil on Nov 14, 2011 5:51 PM

Error handling in process chain-doubts

Hi ,
I have some doubts in error handling of process chains.
1) I have aprocess load infopackeage and subsequent process is update fromPSA.
process load infopackage got failed , so i loaded the IP manually and repeated the next i.e process update from PSA .
How to correct the process chain from now?
2) I have aprocess load infopackeage and subsequent process is Delete request in infocube .process load infopackage got failed , so i loaded the IP manually and repeated the next process i.e Delete request in infocube. Chain continued by deleting the right request . How this is possible ?
Plz help me as this is urgent and daily i have to deal with this issues. If any documents on error handling is greatly appreciated.
My mail id is [email protected]
Regards,
Pavan

Hi Pavan,
Hope the following links will give u a clear idea about process chains and clear ur doubts.
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
Errors in monitoring of process chains can be categorized into 4 different sections...
Master data - Full Update
Master data - Delta Update
Transaction data - Full Update
Transaction data - Delta Update.. in terms of loading of data which can be due to server shut down or system maintenance... errors due to incorrect entries in the OLTP system in which case you'll have to fix the errors in the PSA and manually load the data...
Otherwise it can have errors on Attribute change run being locked by some other job... Aggregate Roll up failing because of attribute change run being run at the same time... Problem with hierarchies and save hierarchies...
There can be problems with the data store activation if the ODS object contains any incorrect request sitting inside it... then, you need to delete the incorrect request and reload the data again...
In case of Transaction Delta failure, you'll have to request for a repeat either manually in the infopackage or using the repeat option if available on right clicking the load event...
For Master Data Delta failures, you need to do an Re-init by deleteing the previous initalization condition in the "initalization option for source systems" in the menu scheduler or reschedule the enitre chain... because, master data generally do not support repeat of last delta ...
U can even 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
****Assign Points if Helpful****
Regards,
Ravikanth.

How to identify what are all the errors appears in process chain,

Hi all,
i have a process chain running, but i want to find out what are all the errors that the process chain has thrown
thanks
pooja

Hi Pooja,
Errors in monitoring:
SID error
Reason: If the corresponding master data is missing for the particular transaction data.
         1. Check for the load timing for the respective master data, if it less than an hour then make the request red and repeat the ip.
         2. If the data is loaded to PSA then you have to delete the request from target and manually push the data to from PSA.
         3. If we are required for selective update then note down the info source from header and find it in RSA1,select the one with Single as postfix.
         4. Goto data selection tab and change the range.
Tip: change the last 4 digits for from to 0000and the last 4 digit for to     9999.
        5. Repeat the ip.
         6. In case only of failure in one target goto RSA1 find the PSA, put he request no. and reschedule it.
Note: IF PSA is present never make the request red rather delete it.
Replication error
Reason: Data source replication Failed.
         1. In order to handle this error you should be known to IP, info source and source system.
         2. Goto RSA1, find the data source in the source sys tab.
         3. Right click on the data source and replicate it.
         4. Since all the transformation rules pertaining to this data source need to be reactivated so go to SE38 and execute rs_transtru_activat_all, data source and sys name.
         5. Delete the red request from the target.
Update R not supported
Reason: The corresponding initialization flag for the ip is lost.
         1. Goto header click on the ip and goto schedule tab and click initialize in the source system, whatever screen appears delete the only request present(the initialization flag).
         2. Goto RSA1, find the ip in the info source (one with the Adhoc initialize flag).
         3. Goto update tab and select Initialize delta process try going for with data transfer.
         4. Reschedule the IP.
Duplicate Record Error
Reason: Duplicate error records for the loaded master data.
         1. Goto info package via header or via RSA1.
         2. Goto processing tab and change the ip setting, selecting only PSA and ignore duplicate records and re run the ip.
         3. Do remember to change the ip settings back to the original once after the second step.
ODS activation failure
Reason: Prerequisites for ODs activation not satisfied i.e. unique key.
         1. Goto maintain variant.
         2. Check for the QM status of the requests in the target they should be green.
         3. Then click the ODS activation tab.
         4. In the screen which appears put the requests for which ODS activation failed.
         5. Activate these and keep on refreshing them until status reverts from green,
Remember to refresh these requests one at a time.
         6. If requests are red then delete them from target.
         7. Reschedule the IP.
Note: Never Try activating ODS manually if it is Y1.
Aggregate Rollup error
Reason: No aggregate found for the respective rollup.
         1. Click on the variant in which the error occurred.
         2. Goto chain tab and copy the variant and instance.
         3. Run the nestle provided program YBW05.
         4. Put in info in there and put the status as g green.
         5. Execute and refresh the status.
Lock issue
Reason: The same ip is been locked by other user or may be used by other process chain.
         1. We can see the locked entries and in the transaction SM12.
         2. Wait for the other process to get complete once the ip loads to target in that process then there is no need for running it for the process.
         3. In other case make the request red, when PSA is present then goto environment tab ->schedule->initiate update.
         4. In the box appears select update in the background.
         5. And the manually update the failed IPs by selecting manual update in the context menu.
Alfa confirming value error, Time conversion error, Chain didnt start, Delay due to long running job, Poor system performance,Heirarchy node exist in duplicate.
Reasons:
Alfa confirming error: Data format mismatch.
Time conversion error: Date, time format mismatch.
Chain didnt start: A scheduled chain didnt triggered at the prescribed timing.
-For all the above error we have to raise a ticket.
Idoc or TRFC error
Reason: An Idoc is been stuck somewhere.
         1. Reload the Master Data manually again from Info-package at RSA1.
         2. Release the Idoc.
         3. In the source system level got environment->transaction->Transaction RFC or Data ware housing level.
         4. In the Screen if the status is Transaction Recorded it means its stuck goto edit and click Execute LUW or press F6.
         5. If status is Transaction executing then it means its fine wait.
         6. Or raise ticket.
Error Due to short Dump
Reason: Error due to Short dump could be due to many reasons i.e. memory, table space, lock, error record, page allocation, failed change run.
Process terminated in the Source system.
           Reason: Sometimes we face that a load has failed due to job Termination at Source System.
      This happens due to unavailability of the source system or some connectivity problem between source and target systems.
1.      Make the request red.
2.      Delete the request from the data target.
3.      Reschedule the ip.
4.      If still the job fails raise the ticket.
And also check in following links:
Process Chain Errors
/people/mona.kapur/blog/2008/01/14/process-chain-errors
Common Process chain errors
For Data Load Errors check this blog:
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
Pls assign points if it helps u,
Thanks & Regards,
Madhu

Error while Executing Process chains

Hi All,
Initially i have created infopack with full load and Executed it manually, later i have changed same infopack to Delta load and kept in Process chains, when i execute the Process chains, the start Process have get triggred, but my Process stops at load data.when i have check the log file it is showing the Below Message:
"Message_Type_x" " "
"CL_RSSM_LOADING===============CP" or "CL_RSSM_LOADING===============CM005"
In Sm37 it is showing
BI_PROCESS_TRIGGER is Finished
BI_PROCESS_LOADING is Cancled
Please help meto find out what might be the cause of this Error.
Note: The infopackage will get data from Generic data Source.
when i run the Process chains, the request is not going to R/3 Side.
Thanks and regards,
santosh.

Hi Santosh,
Go through this below note.
Note 852443 - Dump in include LRSSMU36/RSSM_OLTPSOURCE_SELECTIONS.
If Init is successfull then you can manually try the delta and check it.
Hope this helps
regards
KP
Asign points if helpfull

Error msg in process chain

hi guys,
appended a process chain with process type compress,it shows fiine while checking & actvating,but while running it shows the error"Job BI_PROCESS_LOADING could not be activated
(return code 8)".kindly let me know if it is a known error.
Regards
Kishore

Hi,
This error code 8 comes when there is an error while scheduling a job. check the background user and its properties that schedule the job. Also look into the log of the error and see what it says. Background user should have USER TYPE set as SYSTEM.
Hope it helps. Assign points if helpful.
thanks
Laura.

Invalid DataStore object name error when running process chain after EHP1

Hello,
We recently upgraded our BW Dev platform to NW7.01 EHP1 SP6. I noticed that the layout for "Delete PSA Request" process in the Process Chain has changed after the upgrade. We can no longer specify the actual PSA table to delete eg, /BIC/B0001645. Instead we need to specify the Datasource name and the Source System.
Now after the upgrade when I run one of my process chains, it fails at "Delete PSA Request" step with error message "Invalid DataStore object name /BIC/B0001645: Reason: No valid entry in table RSTS". This datasource is based on the flat file source system and the PSA table for this Datasource is /BIC/B0001653.
Unfortunately the process chain is picking up an older PSA table for this datasource and there is no way for me to specify the current PSA table name after this change in layout with EHP1 upgrade. Any suggestions on how to resolve this issue.
Many Thanks,
Al

Hi,
Please implement OSS 1345331.
If this does not help try the below steps:
1. Run the report 'RSAR_PSA_CLEANUP_DIRECTORY/_MS' in check mode for a
       particular PSA table for finding the inconsistencies.
2.   After that please analyze the logs and if there is any problems related to partition, you need to correct them using the report u2013
3. 'SAP_PSA_PARTNO_CORRECT' in repair mode for the
      PSA tables. Run the report again after this
4. 'RSR_PSA_CLEANUP_DIRECTORY/_MS' in check mode to
     double check that the invalid partitions are
     corrected.
     Once this is done you can execute the report
     'RSR_PSA_CLEANUP_DIRECTORY/_MS' in repair mode.
-Vikram

ABAP Runtime error MESSAGE_TYPE_X in process chain

in our daily load process chain we have a level where datas are getting loaded in to a cube from 4 dso thru dtp. in this level the DTP fails approximately twice in a week. the DTP is shown in red in the log view. when we check the message its showin MESSAGE_TYPE_X ABAP runtime error.
if we give repeat it runs sucessfully and the following process are going well.
do u ppl have any ideas abt this.

Hi,
This failure would happen for many reasons, like,
Source system connection failure
Short dump.
System overload
Non availability od work processes as a reasonthe load would have been timed out.
Locked due to another load.
That is the reason as to which the load when repeated is successful, as by then,
The source connection would have been restored
there would be free processes available
The other load would have completed.
Regards,
Savitha

Error in RSSDK_DATA_REMOTE_GET Process Chain

Hello,
   I am getting 'Communication error: Call of FM RSSDK_DATA_REMOTE_GET to ProgId (progname)' when I launch a process chain in my BW Production system. The process chain extract data from Oracle database.
   However, if I launch the InfoPackage manually, the extraction process complete successfully.
   In BW Test system, I can launch the same process chain without problem.
   Anybody know what is the problem or could tell me any log where I can check the error with more details?
   I have been watching DefaultTrace.trc, Dev_rfc.trc, Dev_jrfc.trc, tx.SM21,... but there is nothing relative to the error. Also, I have checked JCo Destinations, SLD connection and SupportDesk tool and everything is OK.
   I don't know what more can I do...
   Please, any clue could be interesting. I hope you can help me.
Regards,

Problem solved!
First, you should know that if you are using more than one UD Connect source system, each of them have to use different RFC and Program ID name.
Also, you have to check in tx.SM59 if the RFC you are using for UD Connect have the field 'Send Assertion ticket' (in Logon & Security tab) marked or not. In tab MDMP & Unicode, you have to define if your RFC is unicode or not.
In my case, I had to create new RFC (tx sm59) and Prog ID (in Visual Admin) for my second UD connect source system. One of the RFCs was unicode (to access to MSACCESS database) and both of them have unmarked the field 'Send Assertion ticket'.
Now the issues desappeared and my process chains works fine.
Regards,

Problem delete chang log from process chain BW 7.01

We have upgrade BW from 3.5 version to 7.01 version two month ago.
Now I realized that the process chain running one a week to delete PSA and change log don't work well after upgrade.
The process chain end without errors (status is green), but the change log are not deleted.
In the test system I try to delete the Change Log in 2 mode:
1-with the variant "Deletion of Requests from the Change Log " and the datastoreobject = myods and all the option (correct request, incorrect request and "Delete Activation Requests Only"). In the log i see this messagge
The following excluded selections will be processed:
No excluded selections found
The following included selectiosn will be processed:
Pattern: DataStore = 0FIGL_O06, InfoArea = *
The following reqeust selections were set:
Number of days = 0000000010, Successful = X, Incorrect = X, Curr. Requests =
The following change logs were selected:
2-with the variant "Deletion of Requests from PSA " and the datasource= 8myods and all the option (correct request, incorrect request). In the log i see this messagge
The following excluded selections will be processed:
No excluded selections found
The following included selectiosn will be processed:
Pattern: DS = 80FIGL_O06, LS = BWTCLNT100, IS = , AC =
The following reqeust selections were set:
Number of days = 0000000015, Successful = X, Incorrect = X, Load requests =
The following PSAs were selected:
In both case the change log is not deleted.
I can delete the change log only using Manage screen of my ods and then using Menu -> Environment ->Delete Change Log Data.
Anna Maria

I see that this topic is still active/unanswered...
We're having the same problem, but not just changelogs, also for PSAs. We have a weekly process chain that does housekeeping on our BW system, cleaning up PSAs and changelogs, compressing cubes, realigning time-dep masterdata and renewing indexes.
The PSA chain runs fine and about 90% of all PSAs get deleted, but there are some datasources (all of them are of type 8* datamart datasources) that don't get their PSAs deleted. It says "The following PSAs were selected:" and then nothing happens...
I tried all tickbox combinations and checked that there are no PSA entries blocked by invalid partitions. Manual deletion (via "manage" in the datasource) works fine, but is tedious and time consuming.
Also, most of the 8* datasource PSAs do get deleted. Just a handful (+/- 25) get skipped somehow.
Any ideas?
Thanks,
Eduard
PS: We're still running 3.5-style backend dataflow, but will eventually get converted to transformations and DTPs. But that's not on our agenda (yet).

Error while activating Process Chains

Hi all,
while activating the Process Chains, i am getting the following error "Job BI_PROCESS_PSAPROCESS could not be scheduled. Termination with returncode 8"
when i double click on the error msg, i got the following help msg: "
Message no. RSPC065
Diagnosis
Program RSPROCESS is to be scheduled as job BI_PROCESS_PSAPROCESS under user ALEREMOTE.
Can any one please show some way to solve this problem? please do this favor, i have been suffering with error for a long time.
Points will be given
Thanks
Ganesh

Hi,
Just analyze the error message that you get while activating the PC, don't give any server name.If you are trying to run process chain using Flat file, it won't work,
and you should have source system R/3 or you have own datasources in BW system itself at that toime you can use PC to extract data. If your source system is Flat ile, it won't work. other wise you should place your flat file in application server, using AL11 tcode.
OSS : 511475
Symptom
You cannot schedule or perform any batch jobs with the BW or source system background user.
The error RSPC 065 occurs in the process chains:"Job could not be scheduled, termination with return code 8"
Other terms
RSPC065
Reason and Prerequisites
The user type is
"CPIC" up to 4.6B
"Communication" as of 4.6C
This user type may not execute or start any batch jobs, irrespective of the user authorizations.
Solution
Set the type of background user to
"Background" up to 4.6B
"System" as of 4.6C
This user type corresponds to the "Communication" type and may also perform background functions.
Through the Customizing, the BW user is automatically created by mistake as a communication user.Depending on your BW system release, you can solve this problem as follows:
BW 2.0B
 Import Support Package 24 for 2.0B (BW2.0B patch24 or SAPKW20B24) into your BW system. The Support Package is available once note 456551 with the short text "SAPBWNews BW 2.0B Support Package 24", which describes this Support Package in more detail, has been released for customers.
BW 2.1C
 Import Support Package 16 for 2.1C (BW2.1C patch16 or SAPKW21C16) into your BW system. The Support Package is available once note 456566 with the short text "SAPBWNews BW 2.1C Support Package 16" has been released for customers.
BW 3.0A
 Import Support Package 8 for 3.0A (BW3.0A patch08 or SAPKW30A08) into your BW system. The Support Package is available once note 452632 with the short text "SAPBWNews BW 3.0A Support Package 08" has been released for customers.

How to delete the error stack in process chain?

Hi all,
we just want to do the following:
- we are loading in FULL daily to our datatarget (data is versionized by 0calday)
- we want to use the error-stack in order to analyze wrong data
--> but we now encounter the problem that, if data has once been added to the error stack and has not been handled yet, all data from the next daily load will be sorted out as records with this key do already exist in the error-stack. But that's exactly what we want to avoid.
with other words: how can we delete the records in the error stack by a report by e.g. using this in a process chain?
Thanks in advance,
Best regards,
bivision
Edited by: bivision2009 on Jul 6, 2010 12:25 PM

Dbl click that DTP.... From menu... Extras -> Setting for Error Stack
Here U can see error stack table name /BIC/B0001234000.
Using SE38, create simple program "Delete from /BIC/B0001234000"
In the process chain, add process type "ABAP Program" to add above deletion statement.

"Error While creating Process Chain"

Hi all,
I am Creating a process chain in that I have to load from ODS to Cube,
If I include process types "Activate ODS" and "Update ODS" in process chain its Loading Delta from ODS to Cube, But my Requirement is to load FULL LOAD from ODS to Cube, If i select Full load infopackage from 8ZODS and place it in the chain after Activate ODS its giving errors as
Errors:
InfoPackage is generated; NOT able to be used as loading variant
A type "Activate ODS Object Data" process cannot precede process "Execute InfoPackage" var. ZPAK_42622G5QGKNFH2LSX5PN6DAG6 in the chain
Please Guide me what to do? and Brief me the sequence to create a Process Chain(loading full and delta from ODS to Cube).
Thanks in Advance,
Sai

hi Sai ram...
Create a FULL Infopack by Copying the Full IP which was generated at the 8ZODS.
Sequence for full is.
1) start Process
2) LOAD IP
3)ACTIVE ODS
4)EXECUTE IP(Full IP which was copied)
For Delta
1) start Process
2) LOAD IP
3)ACTIVE ODS
4)Further Update Process type..(give the ODS name here from where u want to load to Cube.)
put the Indexes where ever nececssary ...
hope it helps
regards
AK
Thanks=points
Message was edited by:
A K

Error log in Process chains...

Similar Messages

Maybe you are looking for