move accounting units between zones

When you reorg or move Acct units, the effective date is not what you think - all the history follows the AU and the day you move it, all reporting will show in new Corp, as though it'd always been there. We encountered this problem some time back and our resolution was to leave the old AU's and create new AU's, journal over any beg balances. As you know, moving AU's to a new Corp distorts your audited financials. We elected to never move across Corps & create new AU's. The only reporting mechanism I know of to report historical data after you move the AU is to dump your AU's into a AU LIST, use report writer, crystal, Access or some custom reporting.

In HR if the department is mapped to the Gl accounting unit and the level changes, this does not affect HR. In GL when we had to do a reorg we ran all of our financial reports like the GL291, GL292, GL293 and any RW100 reports and saved it before doing the reorg.

We then did the reorg, and in some cases inactivated the old accounting units and activated new ones and in some cases moved the old ones. Lawson is right, the history moves over when you do a reorg but our old financial reports we saved was the link to history. For the new ones we created accounting unit groups and lists that maps the old cost centers to the new ones, so we can run reporting against them for historical purposes.

When we previously moved depts between facilities (zones) under the company umbrella, we have consistently created new A/U and inactivated the old A/U. This gave us a clean break for reporting and transactional activity. As Robert says (and we concur) the Eff Date on GL20 borders on meaningless as far as separating pre- and post "effective date" changes. Our problem is our feeder systems for these depts - Revenue and Payroll - are non-Lawson and essentially requiring these dept #s to remain the same after the corp transition. We make extensive use of A/U attributes for our reporting and have discussed internally multiple scenarios. a

Your response was what I expected. Here is what I am contemplating; please point out the flaws as you see them.
A) Export a file listing the balances by A/U, by Account, by Period, by Year for all of the A/Us in question;
B) Create two new depts similar in structure and attributes to the dept being moved (ex. for A/U 00364 being moved from Corp 001 --> 004, create 10364 on Corp 001 and 40364 on Corp 004)
C) Create a GLMASTREL based on the balances from (A), where the balances in 10364 are a mirror of 00364 and 40364 is an exact offset
D) Perform the steps necessary to move 00364 from Corp 001 to 004 (GL20, GL24, GL120)
E) Then interface the GLMASTREL so that, in effect 10364 becomes the "placeholder" dept on Corp 001, and 40364 is an offset dept on Corp 004 for the balances by account for all periods prior to move date.
F) 10364 and 40364 would immediately be inactivated on GL20 to prevent any posting activity and 00364 would continue to operate as before (just now as a Corp 004 A/U instead of Corp 001).