Row Security Question

We want a user to be able to see all accounts from one company but only certain accounts from other companies. Here is an example:

We want Jane to see Company (Alias CO) 10, Object Accounts (Alias OBJ) 100-200. We also want her to see Company 20 but only Object Accounts 190-200.

Right now if I put row security on OBJ for accounts 190-200 she can only see those 11 accounts for Company 10 too.

Does any one have a suggestion for handling this?

Thanks.
Melissa

I looked at a few of the tables F0911, F0902..it looks like you could
do row security using the data item 'account id'/alias GLAID (from
F0911). I saw the column in F0902, and I am pretty sure it is in
most/all(?) of the financial tables..and that number is something that
JDE creates as a key between tables, it is unique from accountID+company
to company...
BTW, I am NOT the financials person, but CNC, so if I am totally off,
sorry..but it looks like it is worth a shot..

John

----------------------------------------------------------
OneWorld Xe (B733.3)
Update 2, SP 16
Oneoffs: SP16_011, _018, _019
Running on: NT4/SP6a, SQL7/SP3
Windows TS/Metaframe 1.8
----------------------------------------------------------






Xe, Update2, SP16
NT/SP6a, SQL7/SP3, WTS/Metaframe 1.8

I looked at F0911, F0902, F4211, F0411 and that field is in each
table. The only place I did not see it on my quick look was in the sales
order header (but it was in the detail).
To look up the JDE's account id for a given company/account, go into
P0901/Accounts by Business Unit..it will be a pain setting up the row
security though, as it does not look like it is very consistant in the
numbering (at least on our system). So any other ideas would really be
appreciated..

John

----------------------------------------------------------
OneWorld Xe (B733.3)
Update 2, SP 16
Oneoffs: SP16_011, _018, _019
Running on: NT4/SP6a, SQL7/SP3
Windows TS/Metaframe 1.8
----------------------------------------------------------






Xe, Update2, SP16
NT/SP6a, SQL7/SP3, WTS/Metaframe 1.8

AID is the short/key account number assigned by OW for each unique
combination of MCU business unit, OBJ account, and SUB subsidiary, which
also appear as a concatenated string in field ANI as the equivalent of
MCU.OBJ.SUB. In a table where one is accessing object/account (OBJ) data one
will also find AID. Yes you could do the row security. In a typical company
with a lot of accounts it would be a big job.

Dave Mallory Denver Water OW 7332 SP 15.1 Oracle 8.1634 NT 4.0

John,

AID would not be a very good choice for row security. Although I don't know
your needs, I would look at CO company or MCU business unit as alternatives.
By default, there are only 32 data dictionary items that are set in the data
dictionary to work with row security, so keep in mind that if you choose
something other than those data items, you will need to change a setting in
the data dictionary.

Bill

Re: RE: Row Security Question

Did you send this to me by mistake?
============================================================
From: william_karsten <[email protected]>
Date: Thu, 8 Nov 2001 06:35:40 -0800 (PST)
To: [email protected]
Subject: RE: Row Security Question

John,

AID would not be a very good choice for row security. Although I don't know
your needs, I would look at CO company or MCU business unit as alternatives.
By default, there are only 32 data dictionary items that are set in the data
dictionary to work with row security, so keep in mind that if you choose
something other than those data items, you will need to change a setting in
the data dictionary.

Bill




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

If you look at the original post (I was replying), the choice of MCU or
CO would not work because of the request. The person stated that they
had the same account numbers for different companies. They had to grant
one set of permissions on one company's account numbers, and a different
set of permissions on the other. If you set row security by company, it
would isolate the accounts in the other company. The use of AID is an
system generated original number that is not duplicated between any
account, so you could set row security for a particular
company/paricular account, without worrying about isolating the same
account number from a different company/business unit.
I have turned on row security for other DD items and not experienced
any problems. Is there some reasoning why one would not want to change
that value? I can understand not changing the definition of the DD
alias, such as the number of characters, or type, etc, but this is just
a flag that application looks at to see if row security is turned on or
not...
Anyone with input on why not to change the row security setting for a
DD alias?

John

----------------------------------------------------------
OneWorld Xe (B733.3)
Update 2, SP 16
Oneoffs: SP16_011, _018, _019
Running on: NT4/SP6a, SQL7/SP3
Windows TS/Metaframe 1.8
----------------------------------------------------------






Xe, Update2, SP16
NT/SP6a, SQL7/SP3, WTS/Metaframe 1.8