SL 2011 appears to use a stored procedure called fetch_modulepernbr to pull posting periods from the various setup files (I determined this by running a SQL trace as the ROI screen opens). I executed that stored procedure in both the failing database and the working database and the returned AR period number in both is the correct 01-2014. So, that is about as far as I can take it. At this point, only someone who has access to the ROI screen code can determine what it does after executing that stored procedure. I tried to open the ROI screen with Customization Manager but, unfortunately, that screen is block as being non-customizable.
Carolyn, if you happen to be following this post, you appear that you might have access to the code or someone who does. I am interested in the code that actually populates the perpost field on the ROI screen. Since that is an optional field and can be either a single field or a from/to pair of fields, I am assuming that the ROI code looks at the report control and exposes one or both fields depending on the report control.