Share A/B and CO security constraints

[maher_samet]

Hi List,

In a multi-company configuration, we share the same Address Book without
restriction. But there is a field: BU in the P01012 that is automatically
filled with 1 if user leave it blank. The problem is that we put Row
security for users for Company Column (*ALL, all tables), and that a user
allowed to access Company # 3 (and can access #0 for common parameters)
cannot access Company # 1 and automatically BU # 1 (every company has a BU
that is the same as its number).
When adding standard Invoice entry (P03B11/W03B11A), after filling the
header and when I click into the grid, the row security put on access only
to Company 0 and 3 (for example) gives me 2 errors: 0052 (Business Unit
Invalid) and 019T (Business Unit has an invalid dictionary value).
But if I change this BU in A/B to one such 3, another user that is not
allowed to access CO # 3 will have the same error.
We thought about adding a common BU in Company 0, but this is forbidden.
- Why this program do such request ? (select * from F0006 where BU=' 1'
and CO not between 00001 and 00002 and CO not between 00004 and 99999) ?
- How to do ?
- Has any one has experience with that ?
- What this BU in A/B will serve for ?

HELP PLEASE.

 

[Mike Dupaix]

Maher,

The BU in the address book is the security BU. If you implement BU security allowing all users access to BU '1', you can avoid the problem. Another option is to change the security BU in the data dictionary.

> Hi List,

In a multi-company configuration, we share the same Address Book without
restriction. But there is a field: BU in the P01012 that is automatically
filled with 1 if user leave it blank. The problem is that we put Row
security for users for Company Column (*ALL, all tables), and that a user
allowed to access Company # 3 (and can access #0 for common parameters)
cannot access Company # 1 and automatically BU # 1 (every company has a BU
that is the same as its number).
When adding standard Invoice entry (P03B11/W03B11A), after filling the
header and when I click into the grid, the row security put on access only
to Company 0 and 3 (for example) gives me 2 errors: 0052 (Business Unit
Invalid) and 019T (Business Unit has an invalid dictionary value).
But if I change this BU in A/B to one such 3, another user that is not
allowed to access CO # 3 will have the same error.
We thought about adding a common BU in Company 0, but this is forbidden.
- Why this program do such request ? (select * from F0006 where BU=' 1'
and CO not between 00001 and 00002 and CO not between 00004 and 99999) ?
- How to do ?
- Has any one has experience with that ?
- What this BU in A/B will serve for ?

HELP PLEASE.




--------------------------
To view this thread, visit the JDEList forum at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=4622
*************************************************************
This is the JDEList One World / XE Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************

<



Mike Dupaix
JDE Certified Professional
(630) 904-5373 – Office/Fax
(630) 750-2500 - Cell

 

[got_to_love_jde]

Re: re: Share A/B and CO security constraints

Mike,
could he also just blank out the BU in the address book and that would then make it available to all ? i think that is how we have it set up over here and we use BU security.
dave


NT 4.0 SP5, SQL 7.0, One World B7321 SP12.4, Citrix 1.8 (XE soon)

 

[Mike Dupaix]

re[3]: Share A/B and CO security constraints

If you look at F0101 (AB Master), field ABMCU will have a value populated. If you do not, the change has been made in the DD. You can check alias MCU. You may have modified the DD item to allow blanks. This is dangerous as it would allow entries without proper accounting. Chances are, business unit will has security set for all users.

> Mike,
could he also just blank out the BU in the address book and that would then make it available to all ? i think that is how we have it set up over here and we use BU security.
dave


NT 4.0 SP5, SQL 7.0, One World B7321 SP12.4, Citrix 1.8 (XE soon)
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=4678
*************************************************************
This is the JDEList One World / XE Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************

<



Mike Dupaix
JDE Certified Professional
(630) 904-5373 – Office/Fax
(630) 750-2500 - Cell

 

[roland_rueegg15]

AW: Share A/B and CO security constraints

this BU can be uned in sales as default Branch Plant or BU (check PO of
P4210).


-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto[email protected]]Im
Auftrag von maher samet
Gesendet: Freitag, 26. Januar 2001 10:01
An: [email protected]
Betreff: Share A/B and CO security constraints ~~0:4622


Hi List,

In a multi-company configuration, we share the same Address Book without
restriction. But there is a field: BU in the P01012 that is automatically
filled with 1 if user leave it blank. The problem is that we put Row
security for users for Company Column (*ALL, all tables), and that a user
allowed to access Company # 3 (and can access #0 for common parameters)
cannot access Company # 1 and automatically BU # 1 (every company has a BU
that is the same as its number).
When adding standard Invoice entry (P03B11/W03B11A), after filling the
header and when I click into the grid, the row security put on access only
to Company 0 and 3 (for example) gives me 2 errors: 0052 (Business Unit
Invalid) and 019T (Business Unit has an invalid dictionary value).
But if I change this BU in A/B to one such 3, another user that is not
allowed to access CO # 3 will have the same error.
We thought about adding a common BU in Company 0, but this is forbidden.
- Why this program do such request ? (select * from F0006 where BU=' 1'
and CO not between 00001 and 00002 and CO not between 00004 and 99999) ?
- How to do ?
- Has any one has experience with that ?
- What this BU in A/B will serve for ?

HELP PLEASE.




--------------------------
To view this thread, visit the JDEList forum at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=
4622
*************************************************************
This is the JDEList One World / XE Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************

 

[maher_samet]

Re: re: Share A/B and CO security constraints

Hi,
Blank out the BU in A/B will fill it (when the Database transaction is
done) with the value of 1. When request the same entry, you find it equal
to 1. The funniest is if the user who do this is secured out of the value 1
for BU, there will be an error message but the record is commited in the DB
and he can continue inserting the value of 1.
I think you used other issue, because this one (blank) do not work.

Maher

At 12:15 26/01/01 -0800, you wrote:
>Mike,
> could he also just blank out the BU in the address book and that would
> then make it available to all ? i think that is how we have it set up
> over here and we use BU security.
>dave
>
>
>NT 4.0 SP5, SQL 7.0, One World B7321 SP12.4, Citrix 1.8 (XE soon)
>--------------------------
>Visit the forum to view this thread at:
>http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=4678
>
>*************************************************************
>This is the JDEList One World / XE Mailing List.
>Archives and information on how to SUBSCRIBE, and
>UNSUBSCRIBE can be found at http://www.JDELIST.com
>*************************************************************

 

[got_to_love_jde]

Re: re: Share A/B and CO security constraints

not to belabor this point but perhaps it is an aberration in P0101 in B7321 that allows a blank business unit. i assure you i did not change the DD to accomodate allowing users to enter a blank. MCU in my data dictionary does not have a check in the box for allow blank entry.
testing an addition just now and the 1 was inserted (even though it is invalid) during an add. on the other hand, after selecting for change it did allow me to enter a blank.
at least i now know that the business unit is going to need an entry in XE.

NT 4.0 SP5, SQL 7.0, One World B7321 SP12.4, Citrix 1.8 (XE soon)