Difference between revisions of "BPCS Naming Conventions"

From MidrangeWiki
Jump to: navigation, search
(BPCS User Security at V 4.0.5.CD)
(BPCS Security)
Line 17: Line 17:
 
For reasons of Security, this is just a synopsis of key [[FAQ]].
 
For reasons of Security, this is just a synopsis of key [[FAQ]].
  
=== BPCS Security at Version 4.0.5.CD ===
+
=== BPCS V 4.0.5.CD Security ===
  
 
What people can access and run is controlled by several elements:
 
What people can access and run is controlled by several elements:
Line 25: Line 25:
 
* are they on the list for some menu we added?
 
* are they on the list for some menu we added?
  
==== BPCS User Security at V 4.0.5.CD ====
+
==== BPCS V4.0.5.CD User Security ====
  
 
BPCS User Security controls
 
BPCS User Security controls

Revision as of 07:32, 26 May 2005

As explained in some CLP/400 examples of CLP/400 programs, software for BPCS needs to be named in such a way that it is going to work within BPCS Security, which has some variations by version.

BPCS Conventions

For reasons of BPCS being a licensed and copyrighted ERP this is just a synopsis of key FAQ so as to avoid having to repeat ourselves within CLP/400 examples of programs.

BPCS V4.0.5.CD Conventions

BPCS comes with applications in which the first 3 letters of the programs are an abbreviation of the application area, such as

  • INV = Inventory;
  • ORD = Customer Orders;
  • PUR = Purchase Orders;
  • SYS = System Stuff.

BPCS Security

For reasons of Security, this is just a synopsis of key FAQ.

BPCS V 4.0.5.CD Security

What people can access and run is controlled by several elements:

  • their 400 user profile;
  • HOW do they access the 400 ... via Green Screen or Client Access?;
  • their BPCS user security;
  • are they on the list for some menu we added?

BPCS V4.0.5.CD User Security

BPCS User Security controls

  • Which BPCS Environments may this person access;
  • Is this person an ordinary user or a BPCS Security Officer?
  • What can the user access outside of the normal menu structure?
  • What applications and sub-application areas is this user authorized to run?
  • What Financial Companies is this user allowed to get into?
  • What Warehouses can this user get into?
  • What Inventory Transactions may this user do?