Settlement Posted to future period

Hi All,
User has execute the settlement in CJ88 to an asset by giving future period 12/2010. Value of settlement was Zero and no accounting document got generated. Only CO and Asset line items with Zero values.
Now when he tries to reverse the settlement it is giving error
"Reversal cannot be posted (system error)
Procedure
When you reverse a posting that originated during the transfer of balances during the asset data transfer, use transaction OASV (FI-AA Customizing "Transfer balances"). Manually create a reverse posting (with reversed positive/negative signs) for each line item in the document you want to reverse. If it is no longer possible to use transaction OASV, use transaction ABF1"
There is no asset document generated and we can reverse as above.
It is not allowing to settle for 01/2010, as it says perform settlement after 12/2010.
Please let me know how this issue can be resolved.
Thanks
Satish

Hi,
For new asset the Capitalization date is not updated in the Asset Master and for old asset the date is previous settlement date.
Thanks
Satish

Similar Messages

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.

Posting run for future period requested (check entry)

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
I checked in OB52 postings periods are open for 2009(all periods)
SAP note 1150235 (all corrections) and 1153718 are completely implemented.
Still the problem is not resolved.
Regards,
Sankar

Hi Sankar,
I would like to refer you to the already implemented note 1153718 which states :
After you implement the changes, the system issues error message AA 697
"Posting run for future period requested (check entry)" immediately when
you use a fiscal year that is in the future. In principle, you can
customize this message. However, in this case, no settings are taken
into account; the system always issues an error message.
Regards Bernhard

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

Settlement in a closed period

Hi,
I've got internal orders (or projects) which have costs but were not settled in their previous periods/fiscal year (e.g. FY 2006). These periods are now closed, and the organization is not willing to open the periods. The company wants to settle these projects in the curent FY. Is this feasible?
Regards,
Mahlomola

Hi,
Confirm how the fiscal year has been defined. Normally 12 posting periods with 4 special periods will be there. If you have been provided with special periods, you can post the same entry and the document will be posted in the last working day of
the last period during the special period so that you can account in the same FY.
Regards,
Sadashivan

PO: Cannot Split Shipment for Future Period

Hi All,
We are implementing Oracle 11i release 11.5.5 under multi org setup.
I have question in PO module that should I open current and future periods in PO module in order to receive PO in a future period?
In details: my current opened period in Purchasing is may 2002
And Im not able split the PO line into two shipment. First shipment in may 20002 and second one in future period June 2002
But unless and until I open the period June 2002 in purchasing module, its not allowing me to split the shipment.
But one of our operating unit running in Oracle 11.O.3 and they are able to able split the shipment for any future period.
So my question is that, is it pertaining to any Profile option or something or how its control in PO module?
We are on apps 11i on Windows NT 2000 and multi org setup
RDBMS 8.1.7.1.1
please provide your valid comments on this matter.
Thanks
Altaf
[email protected]

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.

Change future periods for Fiscal year variant-OB29

Hi experts,
We are using 4-4-5 rule, Fiscal year variant is M1, Future Periods for FY variant M1 is not maintained correctly. Our year end is on 6/25/2011 but in our variant M1 it is defined as 7/2/2011 and periods following that are defined incorrectly.
Company - US (4-4-5 rule)
FY variant - M1
Period - P12/2011 and following periods are not defined correctly
1.     There are risks involved if you change the fiscal year in Live SAP system. What is the risks for changing future periods - 2 months from now.
2.     Posting are not carried out for the periods we are changing. We need to check plan data if any
3.     Impact on other modules, organization structure, master data, transaction data
4.     How intense the testing needs to be.
Any help will be appreciated and point will be assigned.
Thanks
Monica

Hello,
If you change the Fiscal year period in the live system the following problems may come as per my understanding.
For Costing Module Planning would have already been carried our at the start of the year,
similarly for CS, PP and PS modules if they are implemented in your company the planning data will be effected.
If there is any Budjet posted even you have to consider how to change the budget and reaccolation
Best Regards,
Ravi

Future period R12

Hi frnds,
When I try to open a period in GL I get error telling not enough future period defined. I inserted few future periods and could open period now normally.
My qustion is, where to check how many future periods do I need to maintain to avaid such error in Oracle EBS R12?
Thanks,
Lisan

Hi Adam, thanks for your reply
The problem is that, activating this message as an error, all invoice posting are going to be affected. I can't just use it for MIRO transaction, for that matter. Therefore, I should use some user exit implementation or a validation rule.
Regards,
Marcelo Buosi.

Which invoice validation status transfer to next period or future period.

Dear All
can any one explain which invoice validation status transfer to next period or future period.
The validation status can be 1) Validated 2) Needs revalidation 3) cancelled 4) Approved 5) never validated.
can i know which validation status moves to next open period and which can be to future open period.
Regards
Shaizy
Edited by: user11298424 on 10 Aug, 2012 2:51 AM

Hi ,
I have run the query given by you. it shows Y for posted. but when I query JE_BATCH_ID from AP_INVOICE_DISTRIBUTIONS_ALL, it shows null JE_BATCH_ID.
How can I get corresponding GL Batch and journals for these invoices?
JE_BATCH_ID     ACCOUNTING_DATE     PERIOD_NAME     POSTED_FLAG     ACCRUAL_POSTED_FLAG
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y
     3/28/2012     MAR-12     Y     Y

Error: No depreciation posting required in period 009 (current period)

Hi,
I am getting error " No depreciation posting required in period 009" and 009 is my current period.
The description of the error says " Do depreciation is posted, since according to the posting cycle no postings are required in this period". In fact this is the first time i am running depreciation. I want to post the depreciation for 1st period. More over i could not able to see the planned values in asset explorer also.
Whenever i am entering this asset in the asset explorer it is giving the above error. But while i run the depreciation its not giving any error. When i check in spool to view the depreciation, its giving msg as "List contains no data" check error log.
Could anyone help me in resolving this error. what could be the reason for this error.
Thanks
Sabera

Hi,
I checked in TABA table, its showing that till 9 the period depreciation has been posted. But i have not posted the depreciation. If it is posted, then it has to show in the planned values as posted, but its showing as "No depreciation" and its not even showing the depreciation for other periods. Could you able to clear this query? I wonder why it is giving this kind of error.
Regards
Sabera

Allow Posting to Previous Period - MMRV

Dear Friends,
We can open / close MM periods thru MMPV & see the currently open periods thru MMRV.
Now when we check current Period in MMRV, we see three periods:
Current period 07 2009 (October 2009)
Previous period 06 2008 (Septermber 2009)
Last period in prev.year 12 2008 (March 2009)
Here we have also Allowed posting to Previous Periods.
Thus current open period is 07 2009 (October 2009) & we can also post in Septermber 2009 (06 2009).
But the real problem is can we post some MM Documents in March 2009 (i.e. 12 2008)? Currently when we try system gives error - Posting only possible in 07 2009 & 06 2009.
I know it is SAP standard to allow only two MM months to be open at a given point of time.
Then what is the use of "Last period in prev.year 12 2008" in MMRV screen?
Waiting for early replies...
Thanks,
Jignesh Mehta

In SAP system, you can only post stocks to one back period only by checking the Check Box in MMRV Transaction.
The entries you mentioned (Current Period, Previous Period, etc. are just information purpose only.
In certain cases, for ex: changing valuation Class etc., you have to check the stocks in Current, previous period and last period in previous year.
So you can get information of periods in MMRV Transactions.
For back posting to other periods (other than previous period), you should use Transaction MMPI.

Allow posting to previous period (Backposting) in MM period close

Hi,
Does anyone know the implications/consequences of allowing posting to previous period (Backposting) when doing MM period closing?
Thanks.

Hi Irene,
We need to close posting period in MM module to allow posting in new posting period. However, if there are still some transactions need to be posted for the just closed period, we allow posting for closed period as well.
However, we can allow postings only for one previous period in MM. We can't post to earlier posting periods.
After all the transactions get posted in initial days of new posting period, we can close previous posting period in FI. Automatically system will not allow posting for MM transactions that has financial implication.
Hope this helps
Cheers,
Som

Info Record Validity Dates - Future Period

Hi Gurus
can you help
we have current Purchase Info Recs in place, with pricing condition records that have a validity date that will expire in the next few days
we have already loaded the next pricing for the next cotnract period with the vendor, but wish to check the accuracy of the data before that pricing condition becomes "current"
do you know how can we pull the data from the future validity period pricing condition record, so we can validiate this
i have only found ways to get the current pricing conditions, but not the one for the future period
please advise
many thanks

hi Velu
we maintain Pricing Condition Type PB00 in ME13
when i key a Pur Ord for the part, then go to Conditions tab in ME21n, then select the Analysis of the Pricing Condition, it bring up Procedure RM0000
then Gross Price PB00, then various steps under this
a number of steps not executed due to requirements not filled etc, being Contracts, outline agreements, Plant Infor Rec Order Unit, then Material Info Rec (Plant Specific) A017, then Material Info Rec table A018 with various field names
For Access Sequence step Mat Info Rec (Plant Specific) it does say No condition record was found for this condition using the document data.
any thoughts
If we cannot resolve i shall leave it for now, and review on the day it becomes current
many thanks

Settlement Posted to future period

Similar Messages

Maybe you are looking for