Unplanned Depeciation showing in wrong posting period

Hi Gurus
i want to post unplanned depreciation for one asset as on 31.12.2009. i did it in abaa for posting period 9 (Dec).
When i see this unplan dep in aw01n it is showing in posting period 10 as unplan depreciation.
Unable to know why it is coming in posting period 10 and not in 9
I tried same thing in development client it is showing properly in period 9.
Please help me in resolving this issue
Edited by: Shekhar Sonar on Jan 20, 2010 12:58 PM

Hi Paul
Fiscal year is April to March . that is why i had given period 9 while executing unplanned depreciation. Problem is it is showing in period 10 and not in 9.

Similar Messages

Wrong posting period setup

Hi,
I have a customer whose posting period is setup wrongly. Their fiscal year is from Oct to Sept but their posting period has been setup from Jan to Dec.
They have made transactions from Aug 08 till now. Kindly advise is there any solution to correct this?
Thanks.

Hi Fabian,
Please check if this thread can be helpful:
How to Delete or change a fiscal period in 2005 A
Thanks,
Gordon

Wrong posting period created and has transactions, how to amend

Hi All,
I have created the posting period in 2005B, forgot to change the Sub-Periods from defaulted Year to Months. So my posting period for 2009 is actually only one period instead of the normal 12 periods in a month.
I have some transactions posted into the period, how can I amend this situation? Hope anyone can assist as soon as possible. Thanks in advance.
Regards,
MH

Hi MH,
I am afraid you cannot do that, because period setting is a very basic setting and the system checks if there are already transactions for that period.
Even if you reverse all transactions the system still considers them as transactions belong to the period.
I suggest that you do it this way:
1. Download the transactions that are already entered
2. Prepare them into templates
3. Go back to the status where database is still empty
4. Correct the period settings
5. Upload back the transactions to the database.
Cheers,
Marini

Documents posted wrong posting periods

hi,
we are using sap 4.7e version.our fiscal year is april to march.we posted 7 billing documents on 01.03.2007 .but 6 accounting documents posted to 13 th period.one document posted to 12 th period. we are unable to identify the problem how it happend .all posting and document dates are on 01.03.2007. could any body give solution to this probelm.

Hi Naga,
Normally the system always takes the posting period based on posting date.
You can enter in the special periods only by actually selecting the posting date of last posting period and manually selecting the posting period as the special period of 13-16.
There could be two possibilities for the issues:
Someone must have manually changed the posting period in billing document header (field VBRK-POPER) to 13 while the posting date is 1.3.07.
OR
Based on certain parameters, a user exit is triggered to change the posting period to a special period 13.
You can reach me at [email protected]
Thanks
Ajay

Wrong posting period open

Dear All,
Wrongly i had opened June 2009 instade of May 2009. How i can delete this entry.
I got note no. 487381 but i am not able to find the transaction or manu path for the same.
there are no postings made in june 2009. Please reply urgently if anybody has faced the same issue.
Regards,
Umesh

Hi
As per other experts contact SAP first and do all these things later.
It is possible to reopen closed period. However, it is not advisable to do so because the valuation data of the previous period could get affected.
If you still decided to proceed with this process, please review the documentation of program RMMMINIT (in SE38, enter the program RMMMINIT, select the documentation radio button and click on 'Display').
Please also, have a look at the documentation of the program RMMMINIT in the paragraph 'Precondition'.
Also study note 70545, 369637.
Also note that carry out same in Dev server first test it in all respect and then dare to make same in PRD server.
Also important is SAP will not support you the problems which are may occur due to this.
Best luck
Regs,
Appie

Field posting period is not a document property

Hi Team
We are attaching comment for every manual adjustment.
While one of the user posted entry in the pervious preiod and upload comment also.
Now in this month he did some changes in comment file.
After that he try to see the attachment for manual adjustment posted are not visable and it shows message "Field posting period is not a document property".
Please help me how to fix this.
Regards
Madhu

Hi Team
Thanks for you support.
Issue was solved
Regards
Rajesh

Posting Periods Error

Hello Experts,
My Customer Creating the Wrong Posting Period like
01/01/2011 to 12/31/2020
and My Customer Posted the 2011 Year Transaction in this Period
Now I want to Change the Posting period
01/01/2011 to 12/31/2011
then System can not allow the Changes,
if i will updated in SQL OFPR Table then System give the Error Message
"Transactions created before the %s were found in the system [Message 636-7]"
SO Please Guide me
Dixit Patel
(+91-9904375120)

HI Dixit Patel
If any transaction has been post in Data base so can't change Posting Period . Do one think Restore ur database Backup before posting period Creation and again create ur posting period correctly.
Thanks
Khan Imran

How to reverse wrongly posted unplanned depreciaiton

Hello Gurus,
There has been wrong posting of unplanned depreciation for an asset and now the user needs to reverse such posting.
This occured when the Asset was transferred and some unplanned depreciaiton was posted wrongfully. Now the user wants to reverse the unplanned depreciation.
Can someone please help me with the steps and the T-Codes to reverse such wrong unplanned depreciaiton posting.
Would be really nice of you.
Thanks
Subhankar

Hi,
With u201CUnplanned Depreciationu201D posting, as immediately it will not be posted to FI and no FI document will be generated. It will be posted in next normal depreciationrun i.e., Whenever you run the t-code AFAB-Depreciation Run as part of month-end activities, system will post the u201CUnplanned depreciationu201D along with normal depreciation. So there will be no FI document will be generated with u201CUnplanned Depreciation posting. You need to reverse only Asset document . For this purpose do the following steps :
Option :1: a) Go to t-code-AW01N-Asset Explorer, specify the Asset No., click the posted u201CUnplanned depreciationu201D value
                     and get the Asset Document No. which is available under the head u201CTransactionsu201D.
                   b) Use t-code-AB08 and reverse the Asset document     OR
Option :2: a) Go to t-code AS02-Change Asset Masteru2014Depreciation Areas, keep the Depreciation key with u201C0000u201D value
                   b) Run t-code-AFAB-Depreciation Run with u201CRepeatu201D option by giving/selecting the only the specific Main
                     Asset No. and Asset Sub-number at the bottom of the screen.
Regards
appalas
Edited by: appalas on Dec 14, 2010 1:21 PM

Posting period is showing in future date

Hi,
This is issue am facing in my IDES system.
The error it is showing is as below:
Posting only possible in periods 2015/03 and 2015/02 in company code z001 and message number M7053
other inputs: MMRV : Current peiod   : 03 2015
                                       Previous period: 03 2015
                                   Last period in previous .year 12 2014
And one more input about this is, in my system the system timing was showing 2011, this i did not recogbise, and when i tried to do the post goods issue(PGI) system shown some Posting error then i cloed the periods through MMPV t code, and closed upto 02 2015, then i reliazed why still system is allowoing to close the periods. then i checked the sytem timing and corrected it to current date.(13 th July 2014).
In OB29 my Fiscal year variant is K4 (number of posting periods 12 and no of Special periods 4) is assigned to my company code z001 in t code ob37
In OMSY "also showing the 2015 3
Now even after changing the sytem date to correct date still system is showing the periods problem, when i tried to initialize the periods in t code MMPI sytem is showing the below message "Follow the instruction note 487381 before initialiazation"
I found many treads similar to this issue, but all of them faced past date, needs to be closed the periods until current date, where as in my case the periods alredy open in future date.
am not much familiar with this periods problem as am SD consultant.
Please help to resolve this issue.
thanks,

Nobody needs help of an ABAPer to close or open periods, this is just normal customizing.
Goto service.sap.com/notes and read the content of the OSS note mentioned in your message and just follow it, as it is the only way to run period initialization. It does not matter it you rolled it to far into the future or if you still have stone old periods like in the hundreds of other discussions on the same issue.
And since this is that often discussed I am locking this thread.

Wrong period indicator linked to 2011 posting periods

Hello,
My customer has created new series for 2011 and linked them to 2011 period indicator.
The problem is that the posting period was linked to 2010 period indicator. They've already created several transactions and therefore the period indicator in the posting period window cannot be updated.
Any ideas on how to solve it (except for restoring a backup and retyping the transactions)?
Thanks in advance.
Best regards,
Maya
Problem solved..
Edited by: Maya Alon on Jan 4, 2011 2:10 PM

HI Dixit Patel
If any transaction has been post in Data base so can't change Posting Period . Do one think Restore ur database Backup before posting period Creation and again create ur posting period correctly.
Thanks
Khan Imran

Posting period issue while deleting a confirmation posted for a limit PO

Hi ..
I am facing an issue whiel deleting a confirmation posted for a limit PO.
Confirmation was posted for a limit PO in SRM and it created a service entry sheet in SAP. If I deleted that confirmation in the same posting period, then it is getting deleted. No issue here.
But if I deleted that confirmation in the next posting period then the reversal document is going to error in process. RZ20 is showing the error "Positng only possible in periods 2012/2 and 2012/3".
Posting date of reversal document is current date only and the backend posting period is 2012/3, but still it is failing with this posting period error.
If I tried to delete a confirmation posted for a normal PO then I could able to delete it even in next posting period by just changing the posting date.
Why this posting occurs while deleting the limit confirmation, even through the posting date is falls within the backenn posting periiod? Is it like, SAP system is trying to delete the service entry sheet in original posting period? Kindly help.
I am in SRM 5.0 (server 5.5) SP12.
Thanks,
Arun

OK.
Well, if the variable is not used in any interval selection, then I would say "something happened to it".
I would make a copy of the query and run it to check if I get the same problem with period 12.
   -> If not, something is wrong in the original query (you can proceed as below, if changes to original are permitted).
If so, then try removing the variable completely from the query and hardcode restriction to 12.
   -> If problem still persists, I would have to do some thinking.
If problem is gone, then add the variable again. Check.
   -> If problem is back, then the variable "is sick". Only quick thing to do, is to build an identical variable and use that one.
If problem also happens with the new variable, then it's time to share this experience with someone else and consider raising an OSS.
Good luck!
Jacob
P.S: what fisc year variant are you using?
Edited by: Jacob Jansen on Jan 25, 2010 8:36 PM

Allowed posting periods: 06 2010 / 05 2010 / 12 2009 (Message no. M8022)

Dear Experts,
I took a old shipment & do a new shipment cost but when I went to go for MIRO posting below error message showing. Fyki, every month we run S_ALR_87003642, MMPV & MMRV properly then why below message showing prior MIRO posting. Is there anything else what we are missing? or How can I resolve this issue?
"QUOTE
Allowed posting periods: 06 2010 / 05 2010 / 12 2009
Message no. M8022
Diagnosis
The posting date is not within one of the allowed posting periods.
This can be due to one of two reasons:
The correct current period has not been set in the system.
For the system, the first of the specified periods is the current period. At the beginning of a new period, your system administrator must change the current period in the material master record using the function "Close period". This has not yet been done.
You have entered the wrong date in the field "Posting date".
Procedure
Check the posting date and correct it if necessary. If your entry is correct, inform your system administrator that the "period closing" procedure has not yet been implemented.
UNQUOTE"
Thanks in advance for your valuable comments.
Best Regards.
Ripon K Paul

Hello ,
MIRO doc can be posted on a particular posting date if:
1. MM Period is open for the posting date .
2.FI period is open for the posting date .
No matter what date the preceding documents had been created on ( PO /MIGO/ML81N ) the posting date in MIRO doc shud fall withing the open MM & FI periods.
check the Fiscal year variant in OBY6 trxn, Basing on that the MM periods will be maintained in OBYC trxn..
the below are some of the Fiscal year periods normally we use
K4--- Is for Calender year( Jan to Dec), that means jan is 01, & Feb 02 etc..
V3--- Is April to march, that means Peroid 01 should be April & 02 is May etc..
V9----Is Oct.- Sept., here period 01 should be Oct & Period 02 should be Nov etc...
Regards
JOse

Change Depreiation Posting Period

Dear Sap Friends,
I am working in a implementation project & just now I have completed my golive activities & uploaded the asset cut over data in the production server. I set the asset transfer date as 30.11.2008. while uploading the asset cut over data.
As per the asset transfer date first planned depreciation run should be in the month of December 2008 i.e. in 9th Posting Period. But when I execute (test mode) the same systems gives me an following error message
According to posting cycle, you should post period 010 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 010 next. Either enter period 010, which corresponds to the posting cycle, or request an unplanned posting run explicitly for this parameter
Even I also check that their no Depreciation Run is taken on Production Server. Now I want to post the Depreciation in the month of December 2008 i.e. in Posting Period 9th.
Please provide me the any solution on the above issue ASAP.
Thanks in Advance.
Regards,
Sandeep

Have a look in the table T093d with SE16.
It is possible that with the transport a wrong value is created in there.
For the solution seach with T093d. There is SAP note that you can implement.
An other option is not to run period 10 but start with 11 (will post 10 and 11). You tray to to do a repeat run first in test mode for period 10

MIRO : Allowed Posting Period

Hello experts ,
Is it possible to allow to do an invoice verification through MIRO with a posting date prior to that in the current & pervious period ?
Does MIRO also depend upon MM period only?
Regards
Anis

Hello AP ,
But when i try to post an invoice prior to the "allowed MM Period", the system shows the following error :
Allowed posting periods: 12 2008 / 11 2008 / 12 2007
     Message no. M8022
Diagnosis
     The posting date is not within one of the allowed posting periods.
     This can be due to one of two reasons:
     o   The correct current period has not been set in the system.
         For the system, the first of the specified periods is the current
         period. At the beginning of a new period, your system administrator
         must change the current period in the material master record using
         the function "Close period". This has not yet been done.
     o   You have entered the wrong date in the field "Posting date".
Procedure
     Check the posting date and correct it if necessary. If your entry is
     correct, inform your system administrator that the "period closing"
     procedure has not yet been implemented.
IS THERE ANY SETTING THAT WOULD ALLOW ME TO POST AN INVOICE IN ANY PERIOD ????
PLS REPLY
REGARDS

Error while running a query-Input for variable 'Posting Period is invalid

Hi All,
NOTE: This error is only cropping up when I input 12 in the posting period variable selection. If I put in any other value from 1-11 I am not getting any errors. Any ideas why this might be happening?
I am getting the following error when I try and run a query - "Input for variable 'Posting Period (Single entry, mandatory)' is invalid" - On further clicking on this error the message displayed is as follows -
Diagnosis
Variable Posting Period (Single Value Entry, Mandatory) is used as a lower limit (X) and an upper limit () in an interval selection. This limit has the value #.
System Response
Procedure
Enter a different value for variable Posting Period (Single Value Entry, Mandatory). If the value of the other limit is determined by another variable, you can change its value also.
Procedure for System Administration

OK.
Well, if the variable is not used in any interval selection, then I would say "something happened to it".
I would make a copy of the query and run it to check if I get the same problem with period 12.
   -> If not, something is wrong in the original query (you can proceed as below, if changes to original are permitted).
If so, then try removing the variable completely from the query and hardcode restriction to 12.
   -> If problem still persists, I would have to do some thinking.
If problem is gone, then add the variable again. Check.
   -> If problem is back, then the variable "is sick". Only quick thing to do, is to build an identical variable and use that one.
If problem also happens with the new variable, then it's time to share this experience with someone else and consider raising an OSS.
Good luck!
Jacob
P.S: what fisc year variant are you using?
Edited by: Jacob Jansen on Jan 25, 2010 8:36 PM

Unplanned Depeciation showing in wrong posting period

Similar Messages

Maybe you are looking for