Business Function Naming Convention in EnterpriseOne

Purpose of Document

This document provide supplementary information about business function naming convention to JD Edwards EnterpriseOne Tools Development Standard for Business Function Programming Guide.

Existing Standard Business Functions Prefix

Also see the blog post - Understanding JD Edwards EnterpriseOne Object Naming

The table below provide explanation to the EnterpriseOne existing Business Functions prefix. This is meant for user who are not familiar with JD Edwards World Software because some of file names are originated from it.

In EnterpriseOne, business functions can be started with below prefix,

Prefix Used For Example
B B for Business Function In EnterpriseOne most of business function witten by C Code are categorised as B
...
CCW Business Function for Apparal Management (System Code 41F) All the functions categorized here is to handle Apparal management
CCW01 - FetchInsertF4101 (FetchInsertF4101)
...
N N for NER. F9860.sisrclng = 'NER' Business Functins written by NER (Named Event Rule) is categories as this
N4200790 - Shipment Confirmation
NXT43092 - Receipt Routing
...
ND Named Event Rule for DC Link (3rd party software) ND3N0001 - dcLINK Xpress Check Out
...
X This function is to read file/table and/or when it needs Scrub and Edit Server X0051 - F0902 Balance Retrieval
X00TAX - Calculate and Edit Tax Amount
X0903 - Fiscal Date Edits +
X3111 - F3111 Process Master Data
X3112 - F3112 Process Master Data
X4108 - Lot Master Update
X43199 - Insert Purchase Ledger
X4801 - X4801 Work Order Entry Master Business Function
X983051 - Version List Business Functions - Menu Driver
X983052 - Versions List Functions - Run Time
...
XF Functions starts with XF may update tables and/or Input/Output File server XF41021 - Update F41021 Locations
XF4105 - Item Cost I/O
XF4106 - Base Price Item
XF4111 - Verify and Get Item Ledger
XF43121 - Purchase Order Item Ledger Functions
...
XS Input only/Caching Server XS4100 - Verify And Get Location Master
XT Functional server which is to be called by X & XF
For this example, functional server is functions called by other business functions
XT4111Z1 - Inventory Transactions
XT4113Z1 - Inventory Transfer
XT4114Z1 - Inventory Issues/Adjustments
XT4116Z1 - Item Reclassificaitons (writtenby NER)
XT4311Z1 - Purchase Order Entry
XT4312Z1 - Purchae Order Receipts
XT4314ZN - Voucher Match
...
Others XX0901 - Validate Account Number
GETABDA7 - GetAddressBookDescriptionA7 (F0101 Get Alpha Name)
GETCCDA7 - GetCostCenterDescriptionA7 (F0006 Get Business Unit Description A7)
ISCOLBU - IsColumnInBusinessUnitTable (F0006 Get Business Unit)
ISCOLCO - IsColumnInCompanyTable (F0010 Get Company)
ISCOLPT - IsColumnInPymtTermsTable (Payment Terms Code, Verify in Payment Terms Table)
JDEAPP - JDEAPP_BlankFunction_DoNotUse (JDEAPP_Blank Function_Do Not Use)
JDEAPPER - JDEAPPER_BlankFunction_DoNotUse (JDEAPPER_Blank Function_Do Not Use)
MD_DEBUG - MDDebug (M & D Debug Function)

Note:


Exported Function Name

There is no naming convention for a BSFN exported function name. However, JDE Oracle GSC recommends naming a BSFN exported function name with a unique name (start with 55 or company name), so that JDE developers will not provide the same BSFN exported function name as your custom BSFN exported function name in the future application release.

Example exported function name:-

Object Name Exported Function Name
B0000164 CurrencyDecimalsGet
B0000164 CurrencyDecimalsSet
B0000164 DisplayDecimalsSet

File Name

Business function file name case sensitivity is operating system specific. In case of Windows, both the file names B550003.C and b550003.c are treated as same. However in Unix / Linux machines, these two files will be treated as different files.
So package build might fail because it was unable to locate b420101.c, even though the pathcode\source might have the file B420101.c.

Also allowedFileExtensions in the jde.ini is case sensitive, see
E1: PKG: Understanding Server Only Packages Functionality - From EnterpriseOne Tools Release 9.1.5 Package Build Process (Doc ID 2099715.2)

for instance, there is a filename.C file in pathcode\source, that .C extension needs to be added to the allowedFileExtensions= list in the jde.ini files.

Other reference:

Below link lead you to "World A7.3 Advanced Programming Concepts & Skills PeopleBook" which contains basic concept of business function naming for both World software and EnterpriseOne.

http://docs.oracle.com/cd/E40228_01/technical/a73_apcs.pdf