This page (revision-21) was last changed on 26-Nov-2021 10:22 by rmorrell

This page was created on 26-Nov-2021 10:22 by Administrator

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
21 26-Nov-2021 10:22 6 KB rmorrell to previous

Page References

Incoming links Outgoing links
NAMING CONVENTION AND STANDARDS
NAMING CONVENTION AND STANDARDS

Version management

Difference between version and

At line 3 removed one line
The intention of this document is to help people understand the discipline used for coming up with function names, etc. as well as show changes or new items.
At line 8 changed 3 lines
The table name is assembled by the prefix (P2K_), the module abbreviation (CM_) and then the entity name in plural (DEPARTMENTS) thus: P2K_CM_DEPARTMENTS.
If the entity name has multiple words then these are separated by underscores (i.e. P2K_PR_PAY_LINE_DETAILS)
If the plural of the entity name is an irregular ending, then the correct pluralization applies (i.e. P2K_HR_IDENTITIES from the IDENTITY entity)
The table name is assembled by the prefix (P2K_), the module abbreviation (CM_) and then the entity name in plural (DEPARTMENTS) thus: [P2K_CM_DEPARTMENTS].
If the entity name has multiple words then these are separated by underscores (i.e. [P2K_PR_PAY_LINE_DETAILS])
If the plural of the entity name is an irregular ending, then the correct pluralization applies (i.e. [P2K_HR_IDENTITIES] from the IDENTITY entity)
At line 13 changed one line
View names are similarly constructed to table names but it is differentiated as a view by the inclusion of a letter "V" at the beginning of the third section. For example, P2K_HR_EMPLOYMENTS is a table name, P2K_HR_VEMPLOYMENTS is a view that references this table and P2K_HR_IDENTITIES together.
View names are similarly constructed to table names but it is differentiated as a view by the inclusion of a letter "V" at the beginning of the third section. For example, [P2K_HR_EMPLOYMENTS] is a table name, [P2K_HR_VEMPLOYMENTS] is a view that references this table and [P2K_HR_IDENTITIES] together.
At line 43 changed one line
The rest of the letters are a useful mnemonic of what the function is intended to do. For interactive screens, it is often the [table alias|Table_Alias] of the table primarily maintained (e.g. IEID is an [I|]nteractive screen that maintains the [EID|] table, UPCALC is an [U|]pdate process for [P|]ayroll [CALC|]ulation)
The rest of the letters are a useful mnemonic of what the function is intended to do. For interactive screens, it is often the [table alias|Table_Alias] of the table primarily maintained (e.g. [IEID] is an [I|]nteractive screen that maintains the [EID|] table, UPCALC is an [U|]pdate process for [P|]ayroll [CALC|]ulation)
At line 66 removed 3 lines
At line 71 removed one line
Note that technical product modules may vary from license product modules (or business groupings) as they are different views of the world.
At line 68 added 2 lines
%%information The technical product modules may vary from license product modules (or business groupings) as they are different views of the world.%%
At line 98 changed 3 lines
|A|HR Administrator|WWW_HRADMIN|Manually
|C|Candidates|WWW_CANDIDATE|Manually – 1 user only
|E|Employees|WWW_EMPLOYEE|Manually
|A|HR Administrator|[WWW_HRADMIN]|Manually
|C|Candidates|[WWW_CANDIDATE]|Manually – 1 user only
|E|Employees|[WWW_EMPLOYEE]|Manually
At line 102 changed 4 lines
|M|Managers|WWW_MANAGER|Manually
|P|Publicly Available|WWW_PUBLIC|Manually – 1 user only
|R|Recruiters|WWW_RECRUITER|Automatically
|S|Schedulers|WWW_SCHEDULER|Automatically
|M|Managers|[WWW_MANAGER]|Manually
|P|Publicly Available|[WWW_PUBLIC]|Manually – 1 user only
|R|Recruiters|[WWW_RECRUITER]|Automatically
|S|Schedulers|[WWW_SCHEDULER]|Automatically
At line 108 removed 2 lines
This page (revision-21) was last changed on 26-Nov-2021 10:22 by rmorrellTop