Unable to do the restriction at Fund Center or FM Area when FM is not activ

Question

Hi,
we have the following business requirement:
Background of the issue:
Field Status variant in Account Assignment category and GL:
We are in the process of rolling out one of our company codes which is
in a different instance(server).
We already have some 130+ company codes running in a different
instance. This is a kind of Instance consolidation to bring all systems
under one instance.
Funds Management has been activated in the company code for which we
are carrying out the rollout. FM has not been activated for the
existing company codes.
Now, the issue is with regard to the field status variants, which can
be controlled at the company code level and which cannot be controlled
which is at the client level.
(i)     The existing company codes have a field status variant which
has the field status groups having the fields Commitment items and
Funds center in Suppress mode in the existing instance.
(ii)     The company to be rolled out has the field status variant which
has field status groups having the fields Commitment items and Funds
Center in Optional mode.
(iii)     On the other hand, there is yet another field status control
for the Account assignment objects like Cost center, WBS elements, etc.
in the MM-FI integration area. This is at client level and at present
the same has the status of u201CSuppressu201D for Commitment items and Funds
Center. We have changed the same to u201COptionalu201D for the purpose of
testing the proposed roll out in our existing instance.
In that case, the status of GL account assignment in above is
clashing with our client level field status as described in (iii)
above. As a result, we are forced to change the field status in
above to optional mode for our existing company codes which we do not
intend to do.
When only one company within a group of companies is activated with FM,
I feel that:
(i)     At the client level, there is no option for me other than to
keep the Funds center and commitment items in optional mode
(ii)     At the GL level, I should be able to keep my field status in
Suppress mode (If FM is not activated) and in Optional mode (If FM is
activated) and SAP should be able to take care of the clash in the
field status at the transaction level in such a scenario.
The issue is we are able to control the access if FM is activated for a particular company code, where as we are unable to control the access for other company codes where FM is not activated and FM Area is not linked.
We tried to use the BADI ME_PROCESS_REQ_CUST, but this is applicable for POs only.
Please look into this  issue and help us in meeting our business requirement.
Thanks & Regards,
Ramakrishna

Answer 1

Hi Justin,
Thanks for the extra points.
Copy and save this bold text some where
/Applications/iChat.app/Contents/MacOS/iChat -errorLogLevel 7
This needs to be run in Terminal.
iChat needs to be shut down to do so.
Just paste it in Terminal after the Welcome to Darwin message and hit enter.
It will launch iChat and create an on-going log in the Terminal window.
You will see the reference to the Harware rules.plist
Further down you will see the bandwidth found by iChat, followed by the number of Audio and Video Buddies that you can support.
It goes on.....
It makes a note of the router that you are connected to.
After that it will end up lists listening checks until you connect to a Chat.
This makes this a useful way to find out what iChat can see at it's startup.
To Stop - Quit iChat in the Normal way.
Save the Log in a Text editor of some sort. (Post here if required).
Then Quit Terminal.
It is a useful tool to highlight some things in the start up phase, (And a reminder to look in specific places) when you think you have looked at all the settings.
8:12 PM Wednesday; November 15, 2006