Difference between revisions of "BPCS Naming Conventions"
From MidrangeWiki
m (→BPCS Naming Conventions) |
(→BPCS V4.0.5.CD Naming Conventions) |
||
| Line 6: | Line 6: | ||
=== BPCS V4.0.5.CD Naming Conventions === | === BPCS V4.0.5.CD Naming 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 == | == BPCS Security == | ||
Revision as of 07:21, 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.
Contents
BPCS Naming 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 Naming 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 Security at Version 4.0.5.CD
What people can access and run is controlled by several elements:
- their 400 user profile;
- their BPCS user security;
- are they on the list for some menu we added?
