Last posting run terminated (Restart in period 2011 010) _ Depre posting

Hi
I am trying post depreciation for the month of October 2011 for an asset.
I am getting the following error:
Last posting run terminated (Restart in period 2011 010)
Message no. AA730
Diagnosis
The last posting run in period 010 2011 was terminated by an error. Before any more posting runs are performed, you must restart the posting run for period 010 2011.
Procedure
Start the posting run for period 010 2011 again using the restart parameter.
I checked OB52 and the settings look ok.
Any idea what might be the reason for the error?
Thank you in advance
Regards
Vedavatee

i checked in TABA
and found:
Client         Co Code    Fiscal year     Posted up to No. of posting runs FROM Doc.No.     To doc.no.     Document posted
123     ABCD     2011     008     01          0000000001     0000000001              N
123     ABCD     2011     009     01          0000000001     0000000001              N
123     ABCD     2011     009     02          0000000001     0000000001              N
123     ABCD     2011     009     03          0000000001     0000000001              N
123     ABCD     2011     010     01          0000000001     0000000001              1

Similar Messages

Depreciation Run -"Last Posting run terminated Restart in period 03 2010"

Hello Friends,
Please help me for this. I am trying to run depreciation for a CoCd 2002 in
production. When I do AFAB
for FY 2010 Period 04. It gives a error message "Last Posting run
terminated, restart in period 2010 003"
Diagnosis*
The last posting run in period 003 2010 was terminated by an error.
Before any more posting runs are performed, you must restart the
posting run for period 003 2010.
Procedure
Start the posting run for period 003 2010 again using the restart
parameter.
After this I run AFAB (03 2010) using the Restart radio tab, it runs ok in
Test and w/o Test (i.e in backgrond),
when I check SM37 - it shows a program RAPOST2000 is finished. Then I am
able to run AFAB for (04 2010)
in test and background also. Again a program is there in SM37.
But when I try to run for period 05 2010 - it again shows the earlier error
" "Last Posting run terminated, restart in period 2010 003""
You see the error message comes again.
Can someone suggest me a solution. Do I need to go sm35 and process the
Batch I/P session . Why this error is
coming up?
Regards,
George

Hi George,
please look at table-field TABA-XBUKZ.
If there is a "1" it means "Restart" necessary.
If you have the restart sign you have to solve the error and after the restart the TABA-XBUKZ shoudl change to "X".
regards Bernhard

Last posting run terminated (Restart in period 2010 001)

HI,
There is the challenge issue for Depreciation run in AFAB,
While running the depreciation for the month of jan month system never allowing to post.
After the upload of assets through BDC, this is the first time we are trying to run the depreciation
Also, in the test run, some times documents are created and for the same input parameters, if the test run is executed again, the below error appears.
Job started
Step 001 started (program RAPOST2000, variant &0000000000027, user ID TRAINING1)
Last posting run terminated (Restart in period 2010 001)
Spool request (number 0000010067) created without immediate output
Job finished
Can somebody help on this issue...
Thanks & Regards
Rajesh Kumar.S
09620791110

Hi Rajesh,
Please check the depreciation (production run) log in AFBP by inputing Company Code Fiscal Year and period. This will provide you mored details of the error as to why the depreciation run went into error.
After the errors are rectified, please run AFAB in restrat mode, this will resolve your issue.
Thanks!!!
Murlidhar Khatri

Last posting run terminated (Restart in period 2008 12)

One Week ago we upgraded from SAP 4.6 to ECC6 and implemented recommendation in note 890976 (in transaction FBN1 I have set the accounting doc. 03 to internal number range determination). The first period (11) we executed the depreciation run for appeared to run successfully but for the second period (12) we are receiving the message "Last posting run terminated (Restart in period 2008 012)". This message will appear each time we run the depreciation for period 12.
When I run transaction ARMO, I get the error "Document number 2100 300000001 2008 was already assigned
Message no. F5152"
In Transaction FBN1, we can no longer set the number range to external and the current status for company 2100 is 300000000.
Can any one assist with resolving this issue?
Thanks,
Nicholas

Ran some test in our QA system and found the solution. Changed the status number from 30000000 to 30000050 using transaction FBN1. Everything appears to be working now.
Edited by: Nicholas Archer on Sep 15, 2008 11:56 AM

Posting run terminated AFAB

Hi All,
When I post dep. with AFAB for the period 3 the error follows:
LAST POSTING RUN TERMINATED(Restart in period 2011 002)
When I restart post dep in AFAB
Background job is in finished status with no list, but it say's "document posted in restart" but no document is created.
Thanks in advance,
Sreeni

Hello Sreeni,
I assume you re receiving message AA730, isn't it?
as note 174300 describes error AA730 is caused by improper handling
of the incorrect depreciation posting run.
Please review the Consistency Check Report FI-AA Customizing
and correct the errors.
Go to the IMG ->
Financial Accounting -> Asset Accounting -> Preparing for Production
Start up -> Check Consistency ->Consistency report: FI-AA Customizing
Please review carefully the attached notes 174300, 193984 (this
note describes possible reasons of issues and how to correct it).
br, Guido
Edited by: GUIDO BONI on Apr 11, 2011 4:03 PM

Message no. AA730 Last posting run terminated

Hello,
I loaded incorrectly assets (asset class land) with depreciation key but for a land there is no account determination.
I´ve deleted the incorrect assets and when I run the depreciaton I´m receiving the error message Message no. AA730 Last posting run terminated Start the posting run for period xxxx again using the restart parameter.
When I run the Restart there is the error message Message no. AU101 - There is no data record which meets the selection conditions specified.
Is there any correction programm.
Thanks

Hi, it´s testing client but I can´t to delete the line item within one company code. I´ve found out the table ANLP has still value even I deleted the assets. Is there any transaction or program to delete ANLP entries with determination of Fixed asset No (one asset No not all table). I cant to go and delete directly in a table.
Thank you a lot

Error "Last posting run terminated"

Hi Experts,
When I tried to run the depreciation for Nov, I encounter the error "Last posting run terminated. Restart in period 2009 010",
But when I tried to restart the depreciation for October, I encounter the error Account 'Expense account for ordinary depreciat.' could not be found for area 01. When I checked the assets, I can see in AW01N, that it has already posted a depreciation for October. Why then would it ask for an expense account for period 10 when it has already posted a depreciation last October.
Thanks to advise.
Regards,
Thess

Dear,
Just check account assignment in AO90 if G/L for 'Expense account for ordinary depreciat.' has not been changed. And also see the change document for more clarity.
Regards,
Chintan Joshi.

Posting run request for future period; check your entry message no.AA697

Hello Guru's,
I have below error while Depreciation run in T.Code AFAB
"Posting run requested for future period; check your entry" message no.AA697
Request help
thanks in advance
Regards
Chintamani

Hello Chintamani,
Why you want to post the depreciation for future period?
Is the future fiscal year in open or is the posting period open for that? If no, please open that period with AJRW T code if you want to post the depreciation for future period but it is not recommendable.
Check the posting period once again because the given posting period belongs to future year? So please do re-chk and give correct period according to your current fiscal year.
You can get your fiscal year details and assignment of fiscal year variant to the co,code details in OB29 and OB37 t codes respectfully.
Check the OSS Note: 1150235 - Preventing depreciation posting run for future
I hope it helps else revert us with your query.
Thanks & Regards,
Lakshmi S

Can't Run AFAB - Posting run requested for future period

Hi,
While taking depreciation run for company code in AFAB system is generating the error message "Posting run for future period requested (check entry)" SAP error AA697
Diagnosis
There was a check of your entries in the company code and posting period fields for the current system date. The result of this check is that you requested a posting run for company code xxxx for a future fiscal period.
Please help me, cause I must close the period.
Thanks

Hi
Check Table TABA, whats your last posted period for depreciation
If you are executing depreciation for last period + 1, then this error is not justified
If you are doing it for last period + 2, then its justified
Br, Ajay M

Depreciation error - Unplanned posting run allow for future period

Dear ,
Need urgent advice for depreciation error happen in our production system.
FYI, our fiscal year variant 2013 = Feb 2012 - Jan 2013 ( We are now at month-end close for Pr 1 2013 ).And fiscal year close 2012 AJAB and Carry forward ARJW have successfully run for new FY 2013.
In short, in our asset accounting user was accidentally run unplannned depreciation for future period 12/2013 of one particular asset, while we are now in Pr 1/2013. And, Pr12/2013 is open for asset posting.However, no FI posting posted into the system.
Just a curiosity as to why system allow user to run unplanned depreciation for future posting without giving an error message to follow the posting cycle.
The impact/error of above unplanned depreciation run:
User is not allowed to execute AFAB depreciation run for Pr 1/2013. Even worst, in the AFAB program shows from Pr 1/2013 - 12/2013 is already posted when we do depreciation test run. We can't perform any planned,repeat,restart for Pr1/2013.
Because of only one asset had accidentally run for Pr12/2013, all of our asset (96,773 asset) cannot proceed with depreciation run for Pr 1/2013 in the new fiscal year.
This is high priority as it will impact the entire depreciation run for 12 month of our company.
Your early reply on this issue is greatly appreciated.
Thank you,
Regards,
Latifah

Thank you for the response.
FYI, the asset posting actually has been executed but no document was posted as there's no value.
I've check the 2 tables below:
ANLC - No numbers of run for any period in FY2013
ANLP - No depreciation run was posted in FY13 (all periods).
Is there anyway for us to do normal planned run for Pr 1/2013? As i understand SAP has no function to perform reversal depreciation run in AFAB. How
With regard to the posting period 12/2013 that is open for user, I already highlighted this to the respective custodian.
Thanks.

Depreciaton run terminated(restart period 2011 002

Hi Everyone,
I have an issue with the Asset Dep run for the period 3, It is not creating any documents in dep run in the T code AFAB.
Please clarify
thanks in advance
Sree

Hi everyone,
Actually If we have assigned the Accounts in table T095b in Ktaafb, that would solve the problem of posting of depreciation to the the correct area, But the user does not want to do so he want s to check how to remove the transactions that were posted wrongly. If we configure those GL, I think system may pass debit and credit entries to nullify the account.
thanks
Sree

Posting period of "Depreciation Posting Run" problem

Hi all,
I was configured my company code with 12 period of nomal fiscal year (defauld fiscal year variant K4). I think Posting period field of Depreciation Posting Run screen (T-code: AFAB) must have 12 posible entries, are 1,2,3,...,11,12. But when I display posible entries of this filed, it only have to posible entries (000-000, 000-365). So that, I can't choose a period to excute real depreciation run.
How to define posible entries 1,2,3,..,11,12 of posting period field of Depreciation posting run screen?
Chinhvh

Hi,
If I have understood your question correctly
When u do F4 in field "Posting Period" in AFAB you get the following screen:
From            To
000               000
000               365
You don't do F4 in that field. Since your Posting Period Variant is K4, just manual input the relevant posting period in the field. i.e if you want to post depreciation for April then just input Period 4 in the field.
Now what you have to be careful is which depreciation method you are going to select for doing the Posing Run. (i.e the Reason for Posting Run fields)
You have 4 methods which is described below:
1. Planned Posting Run. (This should be done if all the depreciation upto the earlier posting period has been done properly under the planned posting run).
If you have done unplanned run for earlier periods and have never done a planned posting run for the earlier periods for the concerned asset, then you cannot do planned posting run for period 4 directly. You should first do planned posting for period 1, then for period 2, then for period 3, and then finally for period 4. The depreciation will be zero for Posting periods 1,2,3 if your start depn in your asset master is 1st April.
2. Repeat Run: You can use this to do repeat run. You can do Planned depreciation run only once for a particular asset for a particular period. You can then do a repeat run for doing the depreciation run for the same asset.
3.I don't think you wll need to do Restart run.
4. You can do unplanned depreciation run directly for period 4, if you have not done the depreciation run for the particular asset for the earlier period. but this is not recommended. This should be done only in specific circumstances when you have no chance of doing either planned depn run or repeat run.
Pl assign points.
Rgds
PRasad

Posting run for future period requested

Dear Team,
While taking depreciation run for company code in AFAB system is generating the error message "Posting run for future period requested (check entry)" SAP error AA697
please help to reslove the issue.
Regards,
MAhendra

Hi,
look into the Threads,
Can't Run AFAB - Posting run requested for future period
Regards
Andi

Posting an unplanned depreciation run for the previous period

Hi SDN forum,
May I just ask if it's possible to run an unplanned posting run for a previous period wherein the depreciation run has already been executed?
The scenario is more like a "repeat unplanned posting run"
I can't seem to include this unplanned depreciation whenever I select the repeat run for the previous period.
Please help.
Thanks

Hi
Through T.Code: ABAA you can able to post unplanned dep for previous period.
Executing AFAB for previous
1 - open FI Periods (OB52)
2 - Post Unplanned Dep T.Code: ABAA
3 - Run AFAB with Repeet run & Test run
you feel it is ok with test run execute production run
Regards
Viswa

Posting Run Month end accruals error

Hi Guys,
after running the payroll driver on test mode for period 26 2009...when I look at the log file...I get an error that the employee has been rejected...and the maximum number of search runs exceeded under Month end accruals...
looking fwd to your comments and suggestions

Hello Shiloh S,
The error message "Maximum number of search runs exceeded" occurs in
function UACGF, which is for the Month End Accruals calculations.
Below, I've updated information which explains the Month End Accruals
process, calculations and required table entries:
1. Tables T549S and T51A1:
The T549S table needs 3 dates specified for each pay id. Those 3
dates and their respective Date IDs are:
01 = pay date
04 = posting run
05 = ACC: Earliest Doc. creation date
To check if these entries have been made, please go to sm31 and view
if the entries have been made for the year for example: 2002
(you should also check consistency of future entries as well!)
You can create the entries via the IMG paths specified below for the
respective Date IDs (if you have not already done so).
NOTE: The tables are only changed if a flag has been set for the field
'Carry out table change'. If no flag is set, a test run is performed.
01 = pay date
    IMG -> Payroll US -> Basic Settings -> Payroll Organization
        -> Generate Payroll Period
           You can view the documenation on this step by doubleclicking
           the title of the step. (NOTE: first change your Text Display
           by going to 'Utilities - Text Display - SAPscript)
           For further explanation - click 'Report Documentation'
04 = posting run
    IMG -> Payroll US -> Month end accruals -> Triggering Month End
        Accrual computation -> Maintain Posting Date
         -Create      ('Info' icon provides explanation of how to run.)
05 = ACC: Earliest Doc. creation date
    IMG -> Payroll US -> Month end accruals -> Triggering Month End
        Accrual computation -> Set latest earliest document creation
         date
For T51A1 - Final date for HR Postings (Accruals):
This date determines the final date on which postings may be effected
from HR for each posting period. I would advise you to set this up
for each company code and each accounting period of 2001. For more
info, please select F1 in the fields that you are unsure of.
You can maintain these dates via the path:
   IMG -> Payroll US -> Month end accruals -> Triggering Month End
        Accrual computation ->
2. Explanation of Month End Accruals:
First of all there is a switch to say in general if accruals are to be
computed for an employee or not. This switch is called ACCMO and
is set to 'ON' (1) in rule UAC0. Unfortuately this rule is deactivated
in your development system so that accruals are not calculated.
If this switch is set to 'ON', the system first tries to find out if it
has to calculate accruals and for which periods this is to be done.
If you have a payroll period which overlaps two posting periods, you
will have accruals for this period.
Generally the system can calculate accruals according to exact/current
values and or the system can estimate the accruals. The system always
tries to be as exact as possible which means it always tries to use
current values.
So: How does the system decide if for one period current values can be
taken or if an estimation has to be done?
If you need to post accruals for a payroll period because it overlaps
two posting periods, you have to post to both posting periods. So you
have to make sure, that you are still able to post to both posting
periods when the posting for the payroll period is done. This means the
system has to check that the LDCD (Latest earliest document creation
date) of the payroll period is earlier than the closing date of both
posting periods concerned. Often one posting period is already closed
which means that it is no longer possible to post accruals to this
posting period when the overlapping payroll period is calculated. This
means the system has to estimate values for this overlapping payroll
period before. In other words, the system calculates accruals for a
payroll period in the last payroll period with a LDCD which is is
earlier than the closing date of the overlapped posting periods.
Thus during payroll, the system checks for the current and for the
following payroll periods if things have already been done (because now
it is too late), if things have to be done now (because when the next
payroll period is calculated it will be too late) or if it will be
possible to post accruals after the next payroll period.
Hoping the above information are helpful.
Kind regards,
Graziela

Last posting run terminated (Restart in period 2011 010) _ Depre posting

Similar Messages

Maybe you are looking for