Reconciliation is killing me !!!

Could someone please help me generate a report in R/3 through which I could match my numbers in BW. The Report in BW is based on a Purchasing Cube. But the KF I have to match (CO ACtuals) is a virtual keyfigure taken from an ODS from Controllong side. Now, How do I dig to the bottem of this??? I'm stuck badly on this issue.

Hi,
According to my thinking, you should not validate ODS numbers against BW report (which might be defined on the ODS itself or the cube) because, you would have done some manipulations to the R/3 data in the Transfer rules or Update rules from Data source to the ODS.You are supposed to validate R/3 data against BW data.
Generally speaking, there will be some standard t-codes existing on R/3 for viewing purchasing reports. You should run this report against a BW report and compare the numbers.
I have not worked with Virtual Key Figures before. Is the Virtual Key Figure included in the cube. Check if there is some logic for filling the virtual key figure in the report.
Is there any corresponding field on R/3 for the virtual key figure in the cube. Is there any corresponding Info object for the virtual key figure in the cube.
Thanks.

Similar Messages

Remove Pendng Reconciliation Events

Hello All,
I have run into this problem a number of times- Where I kick off a misconfigured reconciliation task. As a result, OIM then potentially creates thousands of records which ultimately fail and remain in event received status. Due to a number of reasons, the reconciliation processing time may last for hours. To avoid having to wait for a reconciliation job I already know will fail to complete, my question is this-
How do I remove the reconciliation tasks which are still in queue/have not been processed by OIM? I would rather kill all the tasks OIM is currently reconciling than wait around for the task to complete, especially if I know these tasks will will fail.
So far, I know a few things -
1. The "disable" and "stop execution" checkboxes in the DC are useless.
2. The reconciliation events all reside in the RCE table
I have been trying to find a pattern in the table counts, but have not come up with any conclusions. Any ideas on how to cut this down?
Thanks.

Hi,
I did this long time back but you can try this one but please take a backup of your database as this is direct sql query. I won't recommend untill its inevitable.
delete from rcb where rce_key in ( select rce_key from rce where rce_status='Required Data Missing' );
delete from rcd where rce_key in ( select rce_key from rce where rce_status='Required Data Missing' );
delete from rch where rce_key in ( select rce_key from rce where rce_status='Required Data Missing' );
delete from rpc where rce_key in ( select rce_key from rce where rce_status='Required Data Missing' );
delete from rcm where rce_key in ( select rce_key from rce where rce_status='Required Data Missing' );
delete from rcd where rce_key in ( select rce_key from rce where rce_status='Required Data Missing' );
delete from rcp where rce_key in ( select rce_key from rce where rce_status='Required Data Missing' );
delete from rce where rce_status='Required Data Missing';
You can change your rce_status.
Regards
Nitesh

Reconciliation status showing as pending

Hi All,
I have a problem with reconciliation , always the reconciliation status is showing as pending, since 2 days. I rebooted the app server but still the same problem exists. I tried to cancel the reconciliation, but it not cancelled. Itseems like reconciliation doing nothing, just it showing the status as pending.
How can I kill the reconciliation process?can I do it from the dubug pages or what are the other option?
please share your ideas.
Thanks in advance

Hi ,
Thanks for your Response!
Here are the answers for your queries :
1.1) What Recon are you trying to run : Full / Incremental
I am currently running an incremental bcz i have already done a full for the same resource.
2) How do you say that the threads have hung ? Where do you see an indication for a hang ?
from the Show_Reconciler.jsp page i saw that the thread state was idle and from that i confirmed that they r hung. I had provided this to you in my previous mail.I see an indication of Hang when the reconiliation reaches ... 99 % after that it stops responding i tried waiting for 1 full day to see if it responds but it did not.
3) Does the supposed hang go away after you restart server?
When i restart my server the recon gets cancelled.
4) Does it work if the post recon workflow is disabled ? (try removing the post recon process and try to recon again)
Yes , I have tried testing by removing teh post recon workflow and it was working.Working in the sense it was getting COMPLETED WITH ERRORS.it was not completed successfully even once without errors.
There was an attribute called waitforcompleteion which was set to true, i changed that to false and reconciliation is not gettingc ompleted with errors and also Mail is getting triggered.But now the prob is ... recon is completing with errors and its not getting stuck. The error is as follows :
Reconciliation Mode Results
Started at 1/30/08 4:34 AM
Finished at 1/30/08 5:01 AM Incremental Processed 107 accounts.
Some errors occurred during processing.
Started at 1/30/08 12:30 AM
Finished at 1/30/08 12:59 AM Full Processed 182 accounts.
Some errors occurred during processing.
The following errors were received during reconciliation:
Error while reconciling accountId AUTOINSTALL on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId THENDRAW on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId GUEST on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId RGILLIES on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId GCANTY on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId KJONGSUK on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId DJAGO on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId GYANG on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId DWHELAN on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId SKIM on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId SYSADMIN on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId SPERERA on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId DONG on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId TWHELAN on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId SPARKER on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId JLOW on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId PSAMUEL on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId THARDY on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId EKUO on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId WFADMIN on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId SASONG on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId NROBLES on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId MSCHWERDT on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId WKIMSAWA on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId MKANG on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId TTU on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId RVERNAY on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId DBALA on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId YMAK on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId PSORAT on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId RCHADHA on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId SMAHESHW on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId TLANE on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId JGATT on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId ATHOMAS on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId DZHANG on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId RMOTT on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId HCHOI on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId SPIMSAWA on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId NHANKIJ on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId SAMONWAN on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId PKANOK on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId ASUTABEN on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId SKUPPUSW on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId SPANGAM on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId PVENKATE on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId JPROWSE on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId FRIDEG on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId JVALMADRID on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId NCHALIRI on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId CHUANG on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId HSYLVEN on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId NCHANG on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId PKALRA on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId JENLU on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId JPKOH on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId 501120063 on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId JXFLU on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId EJKIM on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId RSAIDI on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId SYXU on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId LHO on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId BKOTHAND on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId CALLENANKINS on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId YJKWON on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId PCROSS on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId IANGGRAINI on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId SMIKHAIL on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId CFSMALAYSIA on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId IYANG on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId 500000003 on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId 500000001 on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId PSONAL on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId RARANGO on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId 500000002 on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId RSHARMA on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId RGAMBOA on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId PRUNDLE on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId CHATAN on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId HHUGHES on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId YCHAMOLI on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId TDELPHIN on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId KHONGTHONG on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId RSOUMYA on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId DKARUNAR on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId SSURINYA on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId ADELINEHO on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId TKULSIRI on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId OKOYDUN on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId AGAYWEE on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId CTHURAPHAN on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId ATANGPAN on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId PWONGSE on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId YJKU on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId MAWARREN on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId PNARKHED on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId KMINAMI on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId MMCLAREN on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId KSORNMARK on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId EGAO on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId PSUBRAMANIAN on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId SONAL on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId JPOPAIROJ on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId TONITESTB1 on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId SHLEE on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId NKALIDIN on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
Error while reconciling accountId STECHAPIT on resource APSSStaging:
com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.
I am attaching the part of app server logs which i tuk when exceuting reocn yesterday for yoru reference.I am also attaching all the file srelated to my reocn for this resource APSS Staging.Please help me in fixing why this type of error is coming.Please reply at the earliest .... as its v urgent
TRACE FILE :
01/29/08 11:10:53 EST
Executing case: 00186.2008_01_24.02_20_PM_GECF_WF_Notify_Reconcile_Finish
Walking case '00186.2008_01_24.02_20_PM_GECF_WF_Notify_Reconcile_Finish'
Processing steps in '00186.2008_01_24.02_20_PM_GECF_WF_Notify_Reconcile_Finish'
Step pass 1
Initializing variables
Initial Case Variables
WF_CASE_OWNER = proxyAdmin
loginApplication = Reconciler
resourceId = #ID#9A8188BF9A98323F:6D5BB4:11772D33089:-B9E
resourceName = APSSStaging
Case title set to '00186.2008_01_24.02_20_PM_GECF_WF_Notify_Reconcile_Finish'
Step executing 'start'
Step complete 'start'
Step inactive 'start'
Step executing 'Notify Admin'
Action Get Results
Result title set to 'Get Results'
Argument op = getView
Argument type = ReconcileStatus
Argument id = #ID#9A8188BF9A98323F:6D5BB4:11772D33089:-B9E
Argument waitForCompletion = false
Calling application 'com.waveset.session.WorkflowServices'
Application requested argument op
Application requested argument viewId
Application requested argument type
Application requested argument id
Application requested all arguments
Application requested argument subject
Application requested argument loginApplication
Application requested argument authorized
Application assignment view =
<Object id='ReconcileStatus:#ID#9A8188BF9A98323F:6D5BB4:11772D33089:-B9E' name='#ID#9A8188BF9A98323F:6D5BB4:11772D33089:-B9E'>
<Attribute name='accountsProcessed' value='107'/>
<Attribute name='errors'>
<Object>
<Attribute name='warnings'>
<List>
<String>Error while reconciling accountId THENDRAW on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId AUTOINSTALL on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId GUEST on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId RGILLIES on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId GCANTY on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId KJONGSUK on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId DWHELAN on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId NROBLES on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId SKIM on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId SPERERA on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId GYANG on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId TWHELAN on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId DONG on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId SYSADMIN on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId RMOTT on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId SPARKER on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId DJAGO on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId JLOW on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId ATHOMAS on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId THARDY on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId SASONG on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId MSCHWERDT on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId EKUO on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId DBALA on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId WKIMSAWA on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId WFADMIN on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId TTU on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId MKANG on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId RCHADHA on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId PSORAT on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId HCHOI on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId SMAHESHW on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId RVERNAY on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId TLANE on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId YMAK on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId JENLU on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId JGATT on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId PSAMUEL on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId SPIMSAWA on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId PKANOK on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId SKUPPUSW on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId DZHANG on resource APSSStaging: com.waveset.util.WavesetException: Concurrent operations prevented completion of the request.</String>
<String>Error while reconciling accountId FRIDEG on resource APSSStaging: c

IPhone 4 - 4.2 upgrade killed visual voicemail

*iPhone 4 - 4.2 upgrade killed visual voicemail*
Ok, I upgraded to 4.2 and deleted all previous backups, so I know I'm screwed untill the next update.
I've synced, backed up, restored from backup and still no "Visual Voicemail".
My voicemail only works if I restore the phone to original settings. But if I do that, I loose important data in my apps. As soon as I "Restore From Backup" I loose my "Visual Voicemail".
If I reset my voicemail password with AT&T, I get the screen to set up a new password and greeting in Visual Voicemail. When I go through these steps I get the spinning wheel "Saving".
It never saves, and I get an alert that says it can't connect to voicemail.
I can set up voicemail by dialing "1", but then all I see is a blank screen in my "Visual Voicemail".
I've also tried a full reset of my voicemail with AT&T.
I even got a new SIM card. That didn't work.
Can anybody figure this one out???
-Thanks

Well, thats the first time I've been told that after a week of phone calls. Maybe it's possible.
I forgot to backup my phone before I upgraded to 4.2. Oops!
When I noticed my Visual Voicemail was gone I tried to backup but ran out of memory.
So I deleted previous backups to make more room. It backed up fine after that.
I don't think it ran out of memory during the update, but maybe it did.
Crap!

Changing vendor reconciliation account

Hi Experts
There are around 1500 vendors for whom we entered wrong reconciliation account. There would be around 20000 line items (uploaded line items, open line items and cleared line items).
Now I want to know what would be the best practice for correcting mistake.
1. Do we need to create new vendor master and transfer balances to new balances to vendor master using LSMW program
2. Do we need to change reconciliation account and run F101 every month end for next 8-10months unless all opening balance is knocked off.
Please let me know impact of above two options considering volume and reporting.
Meenu

If option 2 is acceptable to business, then I would suggest to go with second option, SAP allows to modify Reconciliation account with respective configuration change at master data setup. However, I am not sure, how system would react in following situation, please do a POC for same:
After recon account is changed from 1000 to 1001 at respective vendor master record, and you are processing a payment for against open item, which was recorded with 1000 recon account. In this case, just double check, whether system is able bring open items for clearing and also check it is adjusting against 1000 recon account.
Best regards

Change Customer Reconciliation Account

I need some assistance in verifying the steps for changing Recon account for a group of customers.
Scenario. We have a group of customers (about 60) who have postings to them. Some of the posting are open and some are cleared. We need to change the reconciliation account on these customers. We are running under ECC 6.0
I know how to change the reconciliation account on the customer. That is not a problem. The problem comes with handling the open and cleared items already posted to these customers.
I believe that at some point in time I need to run trans F101. In order to run this transaction I need to define an adjustment account using transaction OBBW. One of my questions here is do I define this as an adjustment account for both the old and the new reconciliation account or for just the old reconciliation account.
Now most of my questions relate to:
1. What are the steps required in order to run F101(FAGLF101 for 6.0)?
2. Is there something that I will need to do each month or will this be a one time situation only for me?
3. Will/are there any special steps required for clearing the open items once the reconciliation accounts have been changed?
4. Is there anything else (any gotchas) that I should be aware of?
Any assistance will be greatly appreciated.
Greg Brown
FI/CO Consultant

the thread you sent me answers part of my questions (namely the fact that I need multiple recon adjustment accounts and the basic steps for executing F101 (FAGLF101).
However, with regards to my other questions, here is what I am interpreting from the thread.
1. Is there something that I will need to do each month or will this be a one time situation only for me?
Assumed answer: I will need to run this every month until the balance of the old recon account for the customers in question is zero.
2. Will/are there any special steps required for clearing the open items once the reconciliation accounts have been changed?
Assumed answer: Apparently not. I will clear the old items (posted but not cleared at the time I changed the recon account) from the old recon account; clear new items (posted and cleared after I change the recon account) for the customer for the new recon account.
Am I correct on this?
Any additional help that you can provide me will be greatly appreciated.
Greg Brown

Questions on AP and PO Accrual Reconciliation?

Dear all,
I know the purpose of "The AP and PO Accrual Reconciliation Report" provides a transactional breakdown of each accrual account with a net balance not equal to zero in a summarized or full transaction details version.
However, I found out that on of the Purchase Order has been done the PO receipt and created an invoice in AP (validate and accounted). But the report still showing PO is 0 and AP is 343,000 in AP and PO Accrual Reconciliation report. I am just wondering what I have done wrong suppose the PO and AP should be equal in that case.
Please advice.
Thanks.

Is there any miscellaneous transactions recorded in error to your accrual accounts,These miscellaneous transactions or transactions unrelated to purchase order receipts may be from Payables.

Error in updating OBNK Table ( Bank Statements and Reconciliations,Manual)

PLease advise ,
Bank Statements and Reconciliations,Manual Reconciliation
Client is receiving the following message:
Error in updating OBNK Table
Edited by: Philip Eller on May 20, 2008 9:03 AM

Hi Darpal Thiarha,
Please kindly refer to note 1132591 and note 1128677 to see if these are relevant to this issue. Upgrading to 2007A PL15 or above may avoid such issues relevant with the error 'Error in updating OBNK Table'.
Regards,
Candice Ren
SAP Business One Forums Team

Reconciliation to verify data in R/3 and BW

Hi Experts,
Can any one explain me how we will maintain reconciliation to verify the data in SAP R/3 and SAP BW are same or not after the data loads. Please explain all the sources that we have.
Thanks in advance
Mallik

For Unit Test, you don't need to reconcile all the records. So, I take a couple of selections. Using these, go to RSA3 in R/3 and extract the data and take sub-totals in Excel.
Now, go to Info Provider in BW, and using same selections, download the data in BW or BEx and take sub-totals again and compare both.
If the extractor is generic extractor based on View/Tables, you can go one additional step and get data from SE16 in R/3 to make sure RSA3 and Tables also match.
For Business Content extractor, its a little difficult is do this step because most of them are Function Modules.
This should be enough as long as your selections are good.
You can compare the data from RSA3. Run RSA3 and save the data in a file and then compare with BW.
You can compare the PSA data with R/3 to check whether your data transport is correct.But its very much important the end result (with data in Data Targets ex.Infocube...) should be reconciled with the R/3 data to check your update and transfer rules are working fine.
The second part is too tricky since you cannot directly compare the reports while the formats and grouping are different.
You can execute the reports in R/3 and apply the Update and transfer conversions (at least for random records) then reconcile with the BW data.
Take a look on the note: 543188
"How to Reconcile Data Between SAP Source Systems and SAP NetWeaver BI"
The Data Reconciliation procedure is still in the SAP action item for the future release.
But we can reconcile the data by extracting the reports and compare with the query output in Excel sheet.
Please check for a tool "Excel Compare" in google which is really useful in comparing excel files.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7a5ee147-0501-0010-0a9d-f7abcba36b14
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/how%20to%20validate%20infocube%20data%20by%20comparing%20it%20with%20psa%20data
By this method you can compare your infocube data with PSA ones...clearly, every changes in R/3 (due to user exit or, above all, BW-specific standard logic) is not taken into account...if you want to consider also this part (back-end), there is no std method and it depends from every specific flow!
also check in service.sap.com/bi
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7a5ee147-0501-0010-0a9d-f7abcba36b14
One way is to define Remote Cube on the R3 data source and create multiprovider on BW with the Remote Cube and the BW target. Subtract the KF on R3 from the KF in BW - anything not 0 becomes an exception.
Sometimes the source on R3 is not as straight forward and we have had ABAP developers create summary table on R3 to compare to BW.
Actually one to one Data comparison between R/3 and BW is done during Integration Test phase. During this time we need to sit with R/3 team and work closely because they know exactly the numbers in R/3 side and which tables Data resides and all. After loading Data same data in to BW we compare the numbers between R/3 BW. If both the teams feel there is some data missing then we start the analysis. As a first stem we will see in the extractors then BW side during transformation like transfer and update rules.
Pleases see this document for more help
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/968dab90-0201-0010-c093-9d2a326969f1
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/how%20to%20validate%20infocube%20data%20by%20comparing%20it%20with%20psa%20data
verifying the data which is coming from R/3 to BW system. That is called as Reconciliation.
That process is done with v lookup functionality.
Hope this helps and assihn points, if so
Regards
Raja

Reconciliação interna com IRF no Pagamento

Bom dia pessoal,
Estou precisando uma uma ajuda. Não vou colocar valores reais, mas vou explicar o que está acontecendo. Meu cliente passou o teto do imposto retido configurado nos detalhes da empresa no contas à pagar (R$ 5.000). Toda nota que ele fizer neste mes, sujeito a IRF, será contabilizado. Digamos que ele tenha feito uma Nota fiscal de Entrada no valor de R$ 100,00 com um imposto retido de 5% configurado para retenção no pagamento. O sistema só irá contabilizar esse imposto quando ele for pagar pelo contas à pagar. O problema é que meu cliente não está realizando o pagamento pelo contas à pagar. Ele fez um lançamento contábil confrontando o PN com uma conta caixa no valor de R$ 100. Na hora de efetuarmos a reconciliação da NFE com o lançamento contábil o sistema critica pois, na verdade, ele deve pagar R$ 95 reais e não os R$ 100. A mensagem é esta "Usar o mesmo código de imposto retido na fonte da categoria de pagamento para todas as transações durante a reconciliação " . Como devo proceder?

Boa tarde,
Neste caso, é necessário fazer um contas a pagar para a nota em questão. Dessa forma, o sistema irá fazer a retenção do valor do imposto e a reconciliação será feita automaticamente, não sendo necessário o lançamento contábil.
Att.,
Tiago Miranda.

Reconciliação Interna / Imposto Retido na Fonte

Boa tarde,
Estou tentando fazer uma reconciliação Interna para um PN (Fornecedor) e é exibida a seguinte mensagem de erro no rodapé do SAP B1:
"O imposto retido na fonte tem de ser processado para pelo menos uma das transações selecionadas. Isto só é possivel restingindo a reconciliação a transações com o mesmo código IRF."
O que pode estar havendo?
Obrigado.

Bom dia,
Estou com este mesmo problema. Ninguém mais passou por esta situação?

Creative Cloud update to version 2.7.1.418 killed my Windows 8.1 system!

Earlier tonight, I saw the balloon from Creative Cloud stating that an update was available. So I installed it. Half-way during the installation, my windows desktop disappeared.
I started the task manager and restarted "Explorer.exe". That made the background reappear, but the taskbar was blank with just the lone Windows 8.1 icon on the very left. Hovering over the taskbar showed the wait cursor.
The task manager showed everything was running normally but the desktop was clearly broken. I checked the directories and everything was as expected.
So I held my breath and rebooted. After logging in, the desktop slowly appeared over about 10 minutes, but all the desktop icons were still missing, as were the taskbar icons. Only a few of the notification icons appeared.
I then managed to bring up a command window with the task manager (fortunately, Ctrl+Alt+Esc still worked) and launched System Restore (rstrui.exe). It showed me the Adobe Creative Cloud was the most recent restore point (below); the previous restore point after that was a Microsoft Windows update from 2 days ago. When I asked for the list of files that were affected by the Creative Cloud update and would be reverted, it showed this:
I again held my breath and restored my machine to before the above CC update; after about 20 minutes of shucking and jiving and a reboot, everything was working properly again.
So there is clearly something out of kilter with this latest update. Adobe the Time Vampire has once again stolen 2 hours of my life, but this time, at least it wasn't a license server issue. I think.

Dave: I did the Microsoft Update two days before this happened, and rebooted as required. I just created a new restore point and lauched Creative Cloud. Now I get the famous white screen:
It just sits and spins (been 10 minutes now).
Fortunately, I saved away this command (which I've had to use 4 or 5 times already):
del %USERPROFILE%\AppData\Local\Adobe\OOBE\opm.db
Unfortunately now, I get this (even after closing the above window):
The process cannot access the file because it is being used by another process.
So I killed everything that said "Adobe" in the task manager and this time, the command succeeded.
Fortunately, the current apps seem to still work. I can't seem to find the "Creative Cloud" app in the applications on my system, but I launched Photoshop CC, told it to look for updates, and got a list of the 5 prgorams that need updates in the Adobe Application manager:
I will proceed with the updates, holding my breath.

What is difference between Reconciliation Account and Revenue account.?`

What is difference between Reconciliation Account and Revenue account.?
Where does it effects after a sales order , delivery doc. or billing doc.?

Hello Mukesh the comments givan by Amol and Siva kumar are correct.
Here I am telling you how these accouts arer wrking in sales order and at billing and delivery.
Our reconsilation account is reconsile with customer that why when you create the sales order you are mentioning the customer at this time reconsiation account works.
Whenever you doing any posting there is an accounting entry is mae in accounts book right .
At the time of Delivery and billing both the accounts are affected as per the accounting rule .
I hpoe this will you help you
Regards
ravi

RFINDEX - Errors in section Reconciliation INDEX vs BSEG

Hi Experts,
After converting a normal GL account into OIM, we have executed the report RFINDEX for consistency check.
We have found errors in the section Reconciliation INDEX vs BSEG.
But I am not sure what exactly the system trying to make me understand and the list of documents that got affected.
Analysis log says that error msg appears at XBLNR field in BSEG & BSIS table.
However, we do not find the field in BSEG table. Then why the system is showing it as "error msg "?
May I request the forum to throw some light and route me towards solution for overcoming the issue?
Regards,
BSK..

Hi Surya,
Please note first of all that the repair option in RFINDEX is only available for use SAP Support. We never recommend that customers or general systems users use this report in repair mode themselves. It can lead to further inconsistencies if used incorrectly.
The error you have seen on this account related to XBLNR is arising because there are differences in the values when comparing the contents of field BKPF-XBLNR and BSIS-XBLNR for a particular set of line items. The XBLNR field is in the header table BKPF and not BSEG.
This error is usually a non critical error and can occur when customising settings such as user exits, substitutions update the XBLNR field in one table (eg BKPF) but not in another (eg BSIS). In these types of situations we usually advise customers to first take time in understanding why the values are updated for XBLNR in their system; the field is highly customizable and therefore errors like this can often appear in systems when running RFINDEX. There is no bug in the standard system which causes these types of differences.
The good news is that this error has nothing to do with the open item management which you enabled. Otherwise you would see error messages like "XOPVW" etc. From your description it seems that the conversion to Open Item Management you did was successful.
Kind regards,
Declan

Killing an application running on RT

Hi
Am using an PXI -8186 embedded controller with PharLap ETS RTOS, i have downloaded an application on to the RT startup directory. I want to deleted the application as i dont need it, but as it automatically starts running when pxi boots up i am unable to delete it. How can i Kill the application and delete it from startup? The rtos does not have a promt, so i can kill the task or look in to directory.
I have to use only Ftp. can any one please help.
thanx
Arun

Hello!
On your 8186 there is a disable start up VI switch. On page 2-12 of the manual you will be able to find the location of this switch. Just incase I have pasted the link to the manual below.
http://www.ni.com/pdf/manuals/370747c.pdf
After you disable the start VI you will be able to remove it. Hope this helps. Let me know if I can give you anymore assistance.
Allan S.
National Instruments

Reconciliation is killing me !!!

Similar Messages

Maybe you are looking for