Naming conventions for using Prefixes
Subject area object prefix
A subject area specific application object is prefixed with the name of the subject area the object belongs to.
Following prefixes should be used in different subject areas:
| Subject area | Prefix | Examples |
|---|---|---|
| Inventory | Invent* | InventAccountType_PRJ |
| Products | EcoResProduct* | EcoResProductType_PRJ |
| Product categories | EcoResCategory* | EcoResCategoryClass_PRJ |
| Customers | Cust* | CustBankAccount CustBalanceCurrency |
| Vendors | Vend* | |
| Ledger | Ledger* | |
| Project | Proj* | |
| Production | Prod* | |
| Warehouse management | WMS WHS |
WMSOrderSplit |
Application area object prefix
An application area object is prefixed with the name of the application area the object belongs to.
| Subject area | Prefix | Examples |
|---|---|---|
| System wide feature | Sys System |
SysEnvironments_PRJ |
| Workflow | Workflow* | |
| Data Management Framework | DMF* |
The DEL_ prefix
DEL_ is a special prefix. It is an abbreviation for Deleted and is used for application objects that will be deleted. After an object is prefixed with DEL_, it will be supported for a release and then deleted in the next version of the product.
DEL_ tables and fields are necessary to allow data update. Such objects allow access to old data that must be migrated to a new location.
When an object with a DEL_ prefix is introduced, the update mechanisms handle changes in the standard application, for example by moving fields and X++ code to the table that replaces the one with the DEL_ prefix. But, if you have written X++ code that references an application object that has been given a DEL_ prefix, you have to update these references yourself.