Error in the depreciation Run

dear all
i have around 9500 assets in my asset master, when i run the depreciation at the final point it stops giving the error Error(). how can i correct how can i find the actual error??
Thanks & Regards
Kanishka

Dear Kanishka,
There exist several possibilities which will lead to Depreciation Run failure. Please kindly check whether
the following senarios is the case in your situation:
- Please make sure that Depr. area 100 (Book Depreciation) is active
for to all asset classes. This is important.
- Another reason caused the depreciation run failed
is that an Asset Class is missing in the OITM table, but it still
exists in the Fixed Assets table[@ba_cclsdpa].To find such cases,
please refer to note :1236895
- Please refer to note 1023366.
how to set log level to 6
1. Choose "Start->Run", enter "regedit", and press Ok.
2. In the "Registry Editor" open the path
"HKEY_CURRENT_USER\Software\SAP\SAP Manage\SAP Business One\AddOn"
3. Double click on LogginLevel.
4. In "Value data" enter the value 6 and click "OK".
how to get log file.
Go to 'start', then Run..., and in the browser type: %temp%
You will see a folder 'SAP Business One Log' in it a text file
First, delete the original log files and start addon.
After error occurs, please save log file on that time before doing
anything like continuing the addon process.
In case the issue is not resolved and you get the log file, please create the
message for SAP support on channel partner portal and send us the log file.
Regards
Vikas Rastogi

Similar Messages

Error in Executing depreciation run

Hi,
After creating an asset in Jan'08, I am executing the depreciation run for Jan month as repeat run. But system is showing an error "Not all the documents in the last posting run were posted" Please advise what should I need to do to resolve this error.
Regards,
Parul

hello
This could be a fiscal year closing error message.
check this and assign ponts if useful
Fiscal Year Change
Purpose
From the point of view of the system, a fiscal year change is the opening of a new fiscal year for a company code. At the fiscal year change, the asset values from the previous fiscal year are carried forward cumulatively into the new fiscal year. Once the fiscal year change takes place, you can post to assets using value dates in the new fiscal year. At the same time, you can continue to post in the previous fiscal year. You find the fiscal year change program under Periodic processing.
Process flow
The fiscal year change can only be carried out (even in test mode) for the new fiscal year. The earliest that you can carry out a fiscal year change is in the last month of the old fiscal year. You can choose any point in the new fiscal year for carrying out the fiscal year change. Before you can change to fiscal year YYYY, you must have already closed fiscal year YYYY - 2 (refer to Year-End Closing). You can have a maximum of two fiscal years open for posting at one time.
No business transactions can be posted in a new fiscal year before the fiscal year change. You can continue to post in the old fiscal year, even after the fiscal year change. The system automatically corrects any values that are affected by postings in the past.
Background Processing
The fiscal year change has to be carried out as background processing for performance reasons. Therefore, start the report as a background job (in the selection screen of the report: Program ® Exec. in background). You can carry out test runs with fewer than 1000 assets in the foreground.
Error Log
The system carries out the fiscal year change for all assets, even if the assets have errors. The system provides statistics per company code for the assets that have been changed.
The system writes assets with errors to an error log and to a worklist (refer to Tools). You can access a long text for the error messages that appear (Long text).
In the case of program termination, you can repeat the fiscal year change as often as required.
You close the fiscal year for bookkeeping using the year-end closing program. After you run the year-end closing program, it is no longer possible to post in the closed fiscal year (refer to Carrying Out Year-End Closing).

Executing the Depreciation Run - AFAB

Hi, Gurus
For reasons of adjustments to the law 11 648( Brasil) was not executed the drepeciaton run since January.
Is trere any problema to Executing the Depreciation Run (AFAB) month by month in the past or I can execute all periods at once ?
the client need a to be sure about what is better to do or what is correct.
since now > Thanks a lot !!!!!!!!

You have to do it month by month...

Reverse the Depreciation run

Hi All,
My requirement is that..
I have run & Posted the Depreciation run in March & April ,2008..
Now I want to change the depriciation for the Month of march, 2008..
Is it possible to Reverse the Depreciation run? , If yes what are the steps..
Thanks in advance..
Raju

Hi,
Reverse the dep. run not possible. You can do repeat run for the month of April (AFAB) only.
Regards,
Murali

Testrun error in posting depreciation run (AFAB)

Dear All,
I got testrun error when I posting depreciation run (AFAB) so I have checked acc.dep as technical massage everything look find. I think it need more config in somewhere. Anyone please suggest me how to fix this.
Account 'Acc.dep. accnt.for ordinary depreciation' could not be found.
     Message no. AU133
Diagnosis
     When creating the accounting document, the system could not find account
     'Acc.dep. accnt.for ordinary depreciation' for company code CC00.
Procedure
     Enter this account in the account determination for Asset Accounting.
Thank you so much in advance.
Best Regards,
Utarat.P

Hi Utarat,
additionally usefull information in the following link:
Error AU133 Account 'Contra account: Acquisition value' could not be found
Regards Bernhard

How to revrse the documnt posted through the Depreciation run AFAB

Hi,
Please advise, how to revrse the documnt posted through the Depreciation posting using tcode AFAB.
Thanks & Regards
Jai

Hi JayChandra
Hope I gave my reply vide your earlier todays thread Re: How to reverse the document posted through AFAB(Depreciation run)
Please check The answer is
You can not reverse
Make your correct changes in Asset Master/Depreciation data and rerun AFAB
System posts the difference

The 'java.lang.InterruptedException' error when the batch running

Hello everyone:
hope everyone go well in your CC&B project.
We have an obstacle we we run some bacth job(not all the time), the log is as following:
03:36:46,060 [DEFAULTWorker:7] ERROR (com.splwg.base.support.batch.GenericCobolBatchProgram) Unexpected interruption while waiting for a cobol batch thread to complete
java.lang.InterruptedException
     at java.lang.Object.wait(Native Method)
     at java.lang.Thread.join(Thread.java:1095)
     at java.lang.Thread.join(Thread.java:1148)
     at com.splwg.base.support.batch.GenericCobolBatchProgram.callCobolInCobolThread(GenericCobolBatchProgram.java:64)
     at com.splwg.base.support.batch.GenericCobolBatchProgram.execute(GenericCobolBatchProgram.java:38)
     at com.splwg.base.support.batch.CobolBatchWork$DoExecuteWorkInSession.doBatchWorkInSession(CobolBatchWork.java:76)
     at com.splwg.base.support.batch.BatchWorkInSessionExecutable.run(BatchWorkInSessionExecutable.java:60)
     at com.splwg.base.support.batch.CobolBatchWork.doExecuteWork(CobolBatchWork.java:53)
     at com.splwg.base.support.grid.AbstractGridWork.executeWork(AbstractGridWork.java:69)
     at com.splwg.base.support.cluster.ThreadWork.processBatchWork(ThreadWork.java:50)
     at com.splwg.base.support.cluster.BatchWorkManager.processWork(BatchWorkManager.java:63)
     at com.tangosol.coherence.commonj.WorkManager$ScheduleWork.run(WorkManager.java:2266)
     at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.InvocationService.onInvocationRequest(InvocationService.CDB:12)
     at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.InvocationService$InvocationRequest.run(InvocationService.CDB:1)
     at com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CDB:1)
     at com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CDB:32)
     at com.tangosol.coherence.component.util.DaemonPool$Daemon.onNotify(DaemonPool.CDB:63)
     at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
     at java.lang.Thread.run(Thread.java:595)
03:36:46,063 [DEFAULTWorker:7] ERROR (com.splwg.base.support.cluster.ClusteredExecutionContext) An error has occurred while processing distributed grid work. A rollback will be issued. Processing of other work will continue.
com.splwg.shared.common.LoggedException: Unexpected interruption while waiting for a cobol batch thread to complete
     at com.splwg.shared.common.LoggedException.wrap(LoggedException.java:198)
     at com.splwg.shared.common.LoggedException.wrap(LoggedException.java:85)
     at com.splwg.base.support.batch.GenericCobolBatchProgram.callCobolInCobolThread(GenericCobolBatchProgram.java:66)
     at com.splwg.base.support.batch.GenericCobolBatchProgram.execute(GenericCobolBatchProgram.java:38)
     at com.splwg.base.support.batch.CobolBatchWork$DoExecuteWorkInSession.doBatchWorkInSession(CobolBatchWork.java:76)
     at com.splwg.base.support.batch.BatchWorkInSessionExecutable.run(BatchWorkInSessionExecutable.java:60)
     at com.splwg.base.support.batch.CobolBatchWork.doExecuteWork(CobolBatchWork.java:53)
     at com.splwg.base.support.grid.AbstractGridWork.executeWork(AbstractGridWork.java:69)
     at com.splwg.base.support.cluster.ThreadWork.processBatchWork(ThreadWork.java:50)
     at com.splwg.base.support.cluster.BatchWorkManager.processWork(BatchWorkManager.java:63)
     at com.tangosol.coherence.commonj.WorkManager$ScheduleWork.run(WorkManager.java:2266)
     at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.InvocationService.onInvocationRequest(InvocationService.CDB:12)
     at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.InvocationService$InvocationRequest.run(InvocationService.CDB:1)
     at com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CDB:1)
     at com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CDB:32)
     at com.tangosol.coherence.component.util.DaemonPool$Daemon.onNotify(DaemonPool.CDB:63)
     at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
     at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.InterruptedException
     at java.lang.Object.wait(Native Method)
     at java.lang.Thread.join(Thread.java:1095)
     at java.lang.Thread.join(Thread.java:1148)
     at com.splwg.base.support.batch.GenericCobolBatchProgram.callCobolInCobolThread(GenericCobolBatchProgram.java:64)
     ... 15 more
03:36:50,315 [CobolThread 489] ERROR (com.splwg.base.support.context.FrameworkSession) Operation not allowed. The session has been closed. This indicates a session management issue commonly where an old reference continues to be held to a closed session
com.splwg.shared.common.LoggedException: Operation not allowed. The session has been closed. This indicates a session management issue commonly where an old reference continues to be held to a closed session
     at com.splwg.shared.common.LoggedException.raised(LoggedException.java:65)
     at com.splwg.base.support.context.FrameworkSession.verifySessionIsOpen(FrameworkSession.java:1669)
     at com.splwg.base.support.context.FrameworkSession.createQuery(FrameworkSession.java:930)
     at com.splwg.base.api.GenericBusinessObject.createQuery(GenericBusinessObject.java:114)
     at com.splwg.cm.domain.admin.trendArea.CmlTrendAreaMeterReadEstimationAlgComp_Impl.getBillSegmentReads(CmlTrendAreaMeterReadEstimationAlgComp_Impl.java:324)
     at com.splwg.cm.domain.admin.trendArea.CmlTrendAreaMeterReadEstimationAlgComp_Impl.invoke(CmlTrendAreaMeterReadEstimationAlgComp_Impl.java:150)
     at com.splwg.cm.domain.admin.trendArea.CmlTrendAreaMeterReadEstimationAlgComp_Impl__.CGLIB$invoke$0(<generated>)
     at com.splwg.cm.domain.admin.trendArea.CmlTrendAreaMeterReadEstimationAlgComp_Impl__$$FastClassByCGLIB$$c326a1b1.invoke(<generated>)
     at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:167)
     at com.splwg.base.support.interception.BusinessMethodInterceptor.intercept(BusinessMethodInterceptor.java:84)
     at com.splwg.cm.domain.admin.trendArea.CmlTrendAreaMeterReadEstimationAlgComp_Impl__.invoke(<generated>)
     at com.splwg.base.support.algorithm.AbstractFromCobolAlgorithmWrapper.invoke(AbstractFromCobolAlgorithmWrapper.java:43)
     at com.splwg.ccb.domain.admin.trendArea.TrendAreaMeterReadEstimationAlgorithmFromCobolWrapper_Gen.invoke(TrendAreaMeterReadEstimationAlgorithmFromCobolWrapper_Gen.java:55)
     at sun.reflect.GeneratedMethodAccessor4943.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:592)
     at com.splwg.base.support.cobol.CobolToJavaGateway$MethodDispatcherCache$MethodDispatcher.dispatchToRequestedMethod(CobolToJavaGateway.java:337)
     at com.splwg.base.support.cobol.CobolToJavaGateway$MethodDispatcherCache$MethodDispatcher.access$300(CobolToJavaGateway.java:255)
     at com.splwg.base.support.cobol.CobolToJavaGateway$MethodDispatcherCache.dispatchToRequestedMethod(CobolToJavaGateway.java:250)
     at com.splwg.base.support.cobol.CobolToJavaGateway$MethodDispatcherCache.access$000(CobolToJavaGateway.java:232)
     at com.splwg.base.support.cobol.CobolToJavaGateway.callJava(CobolToJavaGateway.java:65)
     at com.splwg.base.support.cobol.host.command.CobolToJavaGatewayCommand.invoke(CobolToJavaGatewayCommand.java:33)
     at com.splwg.base.support.cobol.host.SingleJvmRunner.invoke(SingleJvmRunner.java:22)
     at com.splwg.base.support.cobol.host.CommandRunnerHolder.invoke(CommandRunnerHolder.java:31)
     at com.splwg.base.support.cobol.host.CobolToJavaClient.privateCallJava(CobolToJavaClient.java:169)
     at com.splwg.base.support.cobol.host.CobolToJavaClient.callJava(CobolToJavaClient.java:137)
     at com.microfocus.cobol.RuntimeSystem.cobcall(Native Method)
     at com.splwg.base.support.cobol.host.command.CallCobolCommand.invoke(CallCobolCommand.java:73)
     at com.splwg.base.support.cobol.host.SingleJvmRunner.invoke(SingleJvmRunner.java:22)
     at com.splwg.base.support.cobol.host.CommandRunnerHolder.invoke(CommandRunnerHolder.java:31)
     at com.splwg.base.support.cobol.AbstractCobolProgram$CallCobolClosure.run(AbstractCobolProgram.java:195)
     at com.splwg.base.support.interception.SessionInterceptionManager.notifyGenericCallStackJump(SessionInterceptionManager.java:268)
     at com.splwg.base.support.context.FrameworkSession.notifyGenericCallStackJump(FrameworkSession.java:1683)
     at com.splwg.base.support.cobol.AbstractCobolProgram$1.run(AbstractCobolProgram.java:115)
     at com.splwg.base.support.batch.NewCobolThreadExecuter.run(NewCobolThreadExecuter.java:104)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
     at java.lang.Thread.run(Thread.java:595)
     at com.splwg.base.support.cobol.host.CobolThread.run(CobolThread.java:36)
This is really a big problem for our stability, is anyone has the same problem and has solved it?
thank you in advance for any help and information.
Regards
Eric ZHOU

Thank you, Klaus. Sorry for the delayed response.
Since I could not install scheduler schema from the Administrator page under "Scheduler Configuration" I manually applied. Actually, one of the posts in the forum provided those tables. I created the following tables:
RTZ_BLOB_TRIGGERS
QRTZ_LOCKS
QRTZ_JOB_DETAILS
QRTZ_PAUSED_TRIGGER_GRPS
QRTZ_FIRED_TRIGGERS
SEQUENCE
QRTZ_JOB_LISTENERS
XMLP_SCHED_OUTPUT
QRTZ_SCHEDULER_STATE
XMLP_SCHED_SUBSCRIPTION
QRTZ_SIMPLE_TRIGGERS
XMLP_SCHED_JOB
I installed BI Published on my laptop (XP, SP3) and connecting to Oracle 10g, version 10.1.0.2.
Thanks indavance...
harry

Depreciation Run Error Message Error 0()

We imported Fixed Assets at a client using the importation utility in the FA module. Then we are trying to do the Depreciation Run for the first time and we are getting the following error message "The depreciation run 100000010 failed and has been cancelled. Error 0()".
May anyone help on how to solve the error.
Edited by: Tendayi Chidawanyika on Jan 29, 2009 3:11 PM

Have you changed the status of the module from Transfer to Production in the Administration > Company details?

Error while Executing the Depreciation... in AFAB

Hi experts
We have not at run the depreciation for 2008. If i run the depreciation in AFAB by selecting the following parameters
Company code = ABCD
Fiscal year = 2008
Posting Period = 001
Planned posting run
Test run
i m getting the following error.....
According to posting cycle, you should post period 003 next
Message no. AA683
Diagnosis
You cannot post depreciation in the period specified, as this will miss out a posting period.
System Response
No posting can be made in this period.
Procedure
According to the posting cycle, you should post period 003 next. Either enter period 003, which corresponds to the posting cycle, or request an unplanned posting run explicitly for this parameter.
How to solve this problem
Thanks in adcance
A

When you have run depreciation in a test system some times this date is transported to the test / production system and you can have this problem. there are some SAP note for this.
You have 3 options
Look to these note's
Do for period 01 and 02 not a planned posting but a Repeat run. (do this first in test modus)
Post period 1, 2 and 3 as one depreciation run (do this first in test modus)
Can you have a look wath the value is in the table T093D
Edited by: Paul Annotee on Dec 22, 2008 3:32 PM
I had put this in an old message:
Hi,
This you can have when you did more transports, it takes then the value from your last depreciation run from your development system.
The values are stored in the the table T093D. You can have a look to it.
I think you can run the depreciation run for period 1, 2, 3, 4 and 5 as repeat run. Then you get the real values in the correct period. An other option is to run in period 5 *** (1 to 5)
see SAP note
https://websmp230.sap-ag.de/sap(bD1ubCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1065154
https://websmp230.sap-ag.de/sap(bD1ubCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=26073
There are more note's with T093D
Edited by: Paul Annotee on Dec 22, 2008 3:34 PM

Depreciation Run Error (Message no. AA693)

Hi,
User has posted an entry to transfer an asset from one companyh code to the new company code into last FY 2010 in P13. This new company code do not have any asset prior to this. When perfomring the depreciation run, an error message was encounter as per below.
Only an unplanned posting run is possible in this fiscal year.
Message no. AA693
Diagnosis
You have already posted in fiscal years that come after 2010. This means that you can only post in the last posting period 012 in fiscal year 2010. Or you can post to a special period, if one is set up. Since you have not posted yet in this fiscal year, you must specify that the depreciation posting run is unplanned.
Procedure
Please check the fiscal year entered. If you are certain you want to post to fiscal year 012, you must start the depreciation posting run in the last posting period (or in the special period). Be sure to indicate that this posting run is unplanned, since it falls outside of the normal posting cycle.
User has tried the various method (Planned, repeat, restart and unplanned) but still got the same message.
Can someone advise urgently ?
Thanks in advance
Ang.

Hi,
I assume you have in 2010, no entry in the table TABA, because you have made no depreciation run in 2010.
I suppose you have already made a depreciation run in 2011 - right?
In this case you can not post in 2010,
In this case we make a dummy entry in the table TABA in 2010 for period 12. Then you can post in the special period in 2010.
regards Bernhard

Error in Depreciation run for 7 th period

Hi Guruu2019s
When we run depreciation run year 2008 for period 7 has failed with the following error :
Account 'Accumulated dep. account unpl. deprec.' could not be found.
however it has posted to few assets and not posted to few assets, when I checked in the log for posting run there is a message saying that u201Cthere are error in the posting run.after correcting, restart the run.
u201C2documetns were createdu201D
If I go to previous log for posting there is no error message and it says with green signals that 3 documents were created. From 1 to 6 periods, in every log says that 3 document were cresated
Only this particular run says 2 documents were created.
Any advise?
Thanks in advance
Regards
Sunitha,

It looks like that in period 7, you do the first "unplanned depreciation". That's explain why the error only happen in period 7.
The problem happens because GL account for "unplanned depreciation" is not created.
Try to check in t-code : AO90 => Choose your Chart of Account => Choose Account determination for asset class in which you did the unplanned depreciation => Choose Depreciation => Check all GL accounts assignment in "UNPLANNED DEPRECIATION ACCOUNT ASSIGNMENT".
Then check in t-code :FS00 whether the GL Accounts (in "UNPLANNED DEPRECIATION ACCOUNT ASSIGNMENT) are exist or not.
If the GL accounts are not exist then you should created the GL accounts first. Afterwards, try to running the AFAB again using "Restart".
Good luck.

Depreciation Run fails with out providing a proper error

Hi Experts
I have some where around 14,000 assets in my fixed assets master in SAP B1. Currently it takes 15 hours to run the depreciation. But from December after it runs for 15 hours it shows the status as Posting journal entries but after a while it fails the run saying the depreciation run has been failed and cancelled. But there is no error description. When i check the log file in the %temp% folder also there is no error given.
How can i solve this problem this is critical to our operation, please let me know the settings that i have to check and everything
Thanks & Regards
Kanishka Wickrama

Hi Gordon
When we ran the depreciation in November it was successful, but in December we added some where around 2,000 more assets. After that only the depreciation started failing again. So is there any criteria that i have to check in the database.and is there anything that i can do to speed up the depreciation run.
Do you know any other third party add-on that we can use to manage the fixed assets because currently i find it very hard to trouble shoot.
Thanks & Regards
Kanishka Wickrama

Error at the time of dep. run

Dear All,
I have assigned the cost centers in the asset master & also create the Dep. GL accounts as a cost element but the problem arise when i run the depreciation.
At the time of running the depreciation run, we are getting the following error, "GL account requires a CO assignment".
The problem is we can't assign one cost center to the cost element because assets are related to different cost centers and depreciation should be posted to different relevant cost centers so we can't assign the cost center in the Depreciation GL cost element.
The requirement is when we run the planned dep., all the dep. related cost should post to relevant asset cost centers.
Even in the OKB9 settings, we can assign only one cost center against that dep.gl cost element.
Kindly do the needful.
Regards
Anuj

Hi
It is clear that your Org structure is different. You cant post deprciation to various cost centres. Post it to one cost centre and then go for assement/distribution. Alternatively you can use TCode KB11N for manual reposting from one cost centre to another.
Cheers
Srinivas

Error when Depreciation Run

Dear All,
This error message displayed when i running the Fixed Asset Depreciation Run directly until period 10, while it is ok if i running the Depr Run until period 8 and 9.
"The depreciation run 100000001 failed and has been cancelled;
Error: -10 ( - Overlapped I/O operation is in progress. )"
The error arises when i tried the depr run until period 10 onwards.
Please let me know if you have any solutions.
Thanks in advance.
Regards,
Lina Yuanita

Greetings,
Hi there, we've received the same error message before and SAP Support's reply is that this is because of the Budget setup. Below is their support message:
This problem is caused by budget deviation.
Kindly refer to the solution as follows:
1) choose Adminstration => System Initialization => General Setting
=> Budget Tab.
2) tick 'Block Deviation from Budget'
3) perform Depreciation Run in Fixed Assets
4) adjust the budget of accounts in accordance with the error message
poped up in step 3
5) perform Depreciation Run again
BTW the error message("-10(Overlapped I/O operation is in progress)")
in this scenario had been improved in B1 2007A. It will be more
user-friendly and comprehensible.
PS: Maybe we should keep the forum posts in English even if I do understand Bahasa Malaysia / Indonesia

Running TCODE (AFAB) - Depreciation Run in Background - Error: Printer name

Hi SAP experts,
This is actually a basis technical question.
But the error occurred in the Depreciation Run.
When one of our users run this process in Background, she encountered an error 'Printer name not defined'.
But when I use my account, I was able to successfully run it with no errors.
I have checked SU01 and the default name of the printer (LP01) is both assigned to the users.
We are using SAP 4.6 (4.0B). I hope we could find solutions for this.
Thanks!

Hi,
Could you please check note 1292602.
Regards Bernhard

Error in the depreciation Run

Similar Messages

Maybe you are looking for