We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

RE:[sap-acct] AJAB Error-Fiscal Year Already Closed Not Necessary To Perform A Year-End Closing

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Reply from Ron Roberts on Jan 18 at 2:09 PM
As mentioned earlier, you can open 2016 without running close for 2015, so that is no indicator for you.
Look at SAP table T093B to see closed status by depreciation area. I'm guessing you will see all of the areas closed for 2015. Perhaps you just don't remember running 2015 close, or someone else ran it.
You can close 2016 without re-running AJAB for 2015, as SAP says 2015 is closed. If any depreciation area has 2015 open, you will be required to run AJAB for 2015 before you can run it for 2016.
Any time you run AJAB in test mode it will tell you close was not carried out.

---------------Original Message---------------
From: Guest
Sent: Wednesday, January 13, 2016 8:47 AM
Subject: AJAB Error-Fiscal Year Already Closed Not Necessary To Perform A Year-End Closing

Dear Team,

While I try to run AJAB I get error message "The fiscal year 2015 is already closed for company code XXXX. It is not necessary to perform a year-end closing"

Procedure
Check the last closed fiscal year (Application menu: Periodic processing -> Year-end closing -> Reverse).

I have done AA transactions in new year 2016 without executing AJAB, so whether due this transactions I receive this error or any other reason.

Please help asap.

Thanks,
John

 
Reply to this email to post your response.
 
__.____._
Manage Settings | Unsubscribe | Create FAQ | Send Feedback
  
© 2016 Ziff Davis, LLC. and message author.
Ziff Davis, LLC. 28 E 28th Street New York, NY 10016
Ron Roberts  

achievements
 
Mark as helpful
View this online
Ask a new question
 
In the Spotlight
Earn Recognition for Your Contributions at Toolbox for IT. Gain Points for Community Achievements

_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language