Notes are used throughout the system to add, edit, and save text to transactions and master files. Various transactions and master files support 'Note Types' that allow users to further classify/organize notes. The purpose of the Notes List View is to show all the areas of the software that support Notes. Users are unable to add new Note Types but they can be added by emailing NLP Support. Notes are used throughout the application to add more detail to Master Files and Transactions.
...
Toolbar Icons | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
Favorites |
| ||||||||
Grid Layout |
| ||||||||
Help |
| ||||||||
Fields | Description | ||||||||
Module | A label to show the source module of the transaction that the reason code(s) belong to. This is a system controlled list and users cannot add or remove transactions from this list. Linked Database Field: ERPx_MFNoteType.ModuleSK. | ||||||||
Type | A label to show which Transaction and or Master File the Reason Code is used. The 'Where Used' and 'Type' columns work together to identify which transaction and/or master file as well as where on the record the Reason Code applies to. This is a system controlled list and users cannot add or remove transactions from this list. Linked Database Field: ERPx_MFNoteType.NoteType. | ||||||||
Where Used | A label to show where the Reason Code is used. The 'Where Used' and 'Type' columns work together to identify which transaction and/or master file as well as where on the record the Reason Code applies to. This is a system controlled list and users cannot add or remove transactions from this list. Linked Database Field: ERPx_MFNoteType.Description. |
...