Org Restructure

[patty_scully]

All,

My client is considering a restructuring of their organizational structure.
A quick overview of what they are trying to acheive ... we currently have a
single BU for balance sheet and multiple BU's for income statement
locations. They would like to 'merge' and create a BU that holds both BS
and IS accounts.

Any experiences ..... good or bad ... that we could learn from? My gut
reaction is that this will create a fairly intensive reiview and testing
exercise to check all reports, all AAI's, all transactiosn, etc.... Did I
mention that they would like to convert all the 'old' transactions to the
new format?

We are on xe, using multiple modules in financials and distribution.

Thanks for any info!

Patty Scully
Financial Systems Specialists
248-668-0902

 

[lawrence_janes]

Hi Patti

It is quite normal under Job cost to have business units that span the
balance sheet and income statements. Normally the balance sheet side would
only hold WIP accounts. If your client was going to hold all balance sheets
accounts by BU then that would seem quite strange to me. I have changed the
organisational structure within a site that uses Financials Only.

1) You are correct in stating that a detailed review of AAIs and reports is
required
2) Obviously test in an alternative environment and complete in PROD during
some down time. Use you integ reports before & after.
3) Change your COA (P09812, P09803, P09805, P0901) - ensuring Account ID
integrity. Your Balances and Transactions will hold BU OBJ SUB and AID.
The AID is the important element. Changes can be made to the F0901 BU OBJ
SUB - the AID will remain constant.
4) Once the changes have been made to the F0901 run the update R09806 - This
will update the BU OBJ & SUB from the F0901 based upon the AID. - This only
updates the F0911 & F0902
5) The risk is that there are tables that hold the BU OBJ SUB rather that
the AID. If the AID is held then all is OK.
6) If you have changed the BU's company there are 3 integrity reports that
will update the Co no on the F0901 F0902 F0911. Again the risk is if the CO
number changes should be filtered back to other tables.

Good Luck

Lawrence

 

[patty_scully]

Lawrence,

Thanks for your insights!!! What you detailed is similar to the plan we have
put together.

Patty


Patty Scully
Financial Systems Specialists
248-668-0902



From: [email protected]
Reply-To: [email protected]
To: [email protected]
Subject: RE: Org Restructure
Date: Tue, 28 Aug 2001 08:18:40 -0700 (PDT)

Hi Patti

It is quite normal under Job cost to have business units
that span the
balance sheet and income statements. Normally the
balance sheet side would
only hold WIP accounts. If your client was going to
hold all balance sheets
accounts by BU then that would seem quite strange to me.
I have changed the
organisational structure within a site that uses
Financials Only.

1) You are correct in stating that a detailed review of
AAIs and reports is
required
2) Obviously test in an alternative environment and
complete in PROD during
some down time. Use you integ reports before & after.
3) Change your COA (P09812, P09803, P09805, P0901) -
ensuring Account ID
integrity. Your Balances and Transactions will hold BU
OBJ SUB and AID.
The AID is the important element. Changes can be made
to the F0901 BU OBJ
SUB - the AID will remain constant.
4) Once the changes have been made to the F0901 run the
update R09806 - This
will update the BU OBJ & SUB from the F0901 based upon
the AID. - This only
updates the F0911 & F0902
5) The risk is that there are tables that hold the BU
OBJ SUB rather that
the AID. If the AID is held then all is OK.
6) If you have changed the BU's company there are 3
integrity reports that
will update the Co no on the F0901 F0902 F0911. Again
the risk is if the CO
number changes should be filtered back to other tables.

Good Luck

Lawrence




--------------------------

 

[sbamsey]

Patty
We went through a similar exercise earlier this year and the project
spanned the months Jan through April, with some leftover custom financial
reporting that was completed thereafter.
The most intensive activity related to the conversion of all the old
data to the new chart of accounts structure. All the rules have to be
identified up front, then developed into workable conversions. We found
that the One World data conversion would have worked well but there was a
problem at the B7331 release - now resolved in later releases. Naturally,
the most effective time to complete such a shift is at fiscal year end.
On the tech side, we created two new (additional) environments, a
new CRP and new PRD. We could load and test the data conversion into new
CRP and when we had some certainty through testing etc. we pulled it all
into newPRD and went live. Our existing production and CRP environments
were then shelved. At that, we missed a few mappings and repaired
thereafter. A complex but worthwhile process.
Sheena

AS400 enterprise, B7331, World A7.3, WTS, CO's on SQL server.