All cost buckets can be deleted, including the blank one, by using option 11
(delete all cost buckets) on any of the existing buckets.

-----Original Message-----
From: []
Sent: Tuesday, February 19, 2002 1:01 PM
Subject: BPCS-L digest, Vol 1 #192 - 2 msgs

Send BPCS-L mailing list submissions to

To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to

You can reach the person managing the list at

When replying, please edit your Subject line so it is more specific
than "Re: Contents of BPCS-L digest..."

Today's Topics:

   1. Re: User Group Security Maintenance (Genyphyr Novak)
   2. Re: User Group Security Maintenance - SSALOG00 (Genyphyr Novak)


Message: 1
From: "Genyphyr Novak" <>
To: <>
Subject: Re: User Group Security Maintenance
Date: Mon, 18 Feb 2002 18:23:34 +0100
Organization: SSA Global Technologies


This topic of adding more programs to Group Security is not covered in the
DOC menu items such as SSALOG00, because it requires modifications to BPCS
to make a program use group security if it was not already shipped that way
to start with. This feature (Group Security SYS603) was not available in
older BPCS releases, such as BPCS CD. It was first introduced in BPCS with
the product 'LMS' and became a popular enhancement request for other BPCS
programs after it was first developed.

There is a FAQ entry on OGS which covers how to do this in some detail, or
you can get the programming details from calling Support Center, who can
help you find the FAQ I am referring to, or you can determine this for
yourself via analyzing the differences between a program which is already in
the Group Security and those which are not. Then, find out which priming
data files need to be updated by analyzing which files the display programs
for Group Security looks at to find and list the program options.

To add a new program to the BPCS Group Security options requires both
programming and priming data database changes in BPCS. The programs
currently featured in Group Security were those identified by various
customers at various times in the life of BPCS as being something they
wanted to have group security on (ie, securing the program options available
to a given user by use of a 'group' which had those set of authorities set
up already). Enhancements were made over time to add new programs to Group
Security, usually in new BPCS releases.

You can call the Support Center and make an 'E' BMR request for future
enhancement to get another program added to the Group Security, or find out
if a newer release of BPCS happens to have this already activated for the
program you are interested in. The fastest way to get this for yourself at
your current release would be to have this programmed. SSA GT has services
personnel available who can do this programming for you, or you can do this
yourself if you have programming skills available. It is not overly
complicated, but does require careful planning when updating the priming
data files.


Genyphyr Novak
----- Original Message -----
From: "Yanti" <>
To: <>
Sent: Monday, February 18, 2002 8:23 AM
Subject: RE: User Group Security Maintenance

> where can i find the BPCS on-line documentation for BPCS security ..???
> as far as i have the documentation there's none of them mention about the
> thing that i need.
> or might be i don't have that document yet..
> can i get that documentation..??


Message: 2
From: "Genyphyr Novak" <>
To: <>
Subject: Re: User Group Security Maintenance - SSALOG00
Date: Mon, 18 Feb 2002 19:20:33 +0100
Organization: SSA Global Technologies


The other thing I forgot to mention is that for C/S user, the DOC menu does
not exist (ie, this is an SEU AS/400-centric menu, and is not available from
the C/S interface). You can access this from a raw green screen with a
WRKMBRPDM command, on the BPCSO/BPCSDOC file, for *ALL members to see the
list of available texts, including SSALOG00 which is the BPCS 'Logic
Guide' - a system administrator/programmer level document, not required by
average BPCS users.

The DOC menu in Mixed Mode BPCS just gives a user interface to this
multi-membered file, and allows security to be added so that not everyone
has the right to view/change them. Since it is possible to edit the text
from inside PDM, make sure that this file is locked down in your C/S
environment, and I suggest making a copy of the original file into a library
where no one in the SSA group has authority to it, so that you can use this
as a backup to restore any members that become 'corrupted' by 'accident'.
Via object security on the AS/400 and with the way BPCS installs by default
(everything owned by SSA user, with BPCS users getting SSA group authority),
any BPCS user with command line access has all rights to modify this file.
The DOC menu therefore only truly secures these members if the end-user has
no command line access in or out of BPCS.

The RUNDOC information for the BPCS application programs has been turned
into .hlp files on the PC client (press F1 from the GUI application), and is
therefore available as helptext on the client, so you don't really need all
the members in this file from Green Screen if you are Full C/S. But the
SSALOG00 was not transformed this way, and must be viewed in the green
screen SEU interface.

At V8, the SSALOG00 was made available as a Word document on OGS Online, so
that all V8 BPCS users (including Unix clients) could access this more
easily.. Some of the information definitely doesn't apply to Unix (setting
up new environments is strictly AS/400-centric in SSALOG00) but other
information on ODW/ADK programming standards and naming conventions in BPCS
will help anyone wanting to modify BPCS or understand the priming data files
better etc..


Genyphyr Novak


This is the SSA's BPCS ERP System (BPCS-L) digest list
To post a message email:
To subscribe, unsubscribe, or change list options,
or email:
Before posting, please take a moment to review the archives

End of BPCS-L Digest

Cott - The Leader in Premium Retailer Brand Beverage Innovation.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].