Master Comments
Using master comments gives you the ability to provide more information than can be given by using a code or description.
Example: In Purchasing you can record specific supplier requirements, or in Product Engineering you can record information concerning the implementation of engineering change orders for an item. Each master comment can have up to 99 pages of text. Master comments remain in the system until deleted.
Master comments differ from transaction comments in that they can be used globally, not only by the associated transaction.
Master comments are not only for storing and organizing text, you can use them with specific transactions for printing on reports or documents.
• In Sales Quotations, Sales Orders/Invoices, Service/Support Management, and Purchasing, you can enter comments on:
• Headers; for example, shipping instructions
• Line items, for example, item descriptions, specifications
• Work Orders (customer specifications) or work order routings (processing instructions)
• Accounts Receivable Dunning Letters Content
• Accounts Receivable uses master comments on dunning letters or aging reports
• General Ledger prints master comments at the top of income statements
• Service/Support Management field notifications
Note: Master comments do not have to appear on any transactions. You can use them to store general information such as additional customer contact names and telephone numbers.
Before you set up your master comments you need to consider two points:
1 There is no security on comments
• If a user has access to Master Comment Maintenance (2.1.12), they can look at, change, or delete any comment
• Master comments are not owned by a particular user
2 What type of coding scheme you are going to use
• It is a good idea to develop a consistent coding scheme, otherwise it is difficult to find comments when you need them
Example: You could code comments for sales order or purchase order headers with the Reference equal to the customer/supplier address code and Language equal to the customer/supplier language. For line items, you could code comments with the Reference equal to Item Number and the Language equal to the customer/supplier language. Since these are the default values on the sales order or purchase order screens, this will speed up order entry.
Note: Master Comment Maintenance is found in many places in QAD Enterprise Applications including: (2.1.12), (2.3.12), (2.5.12), (2.7.12) Standard Edition only, (1.12), (14.12), and (25.12) Standard Edition only.
Master Comment Maintenance
Use to create and modify master comments. QAD Enterprise Applications identifies master comments by Reference, Type, Language, and Page.
Field Definitions
Reference
Identifies a master comment. You can link a master comment to an entity by setting this code equal to an item number, customer code, or supplier code. If the master comment is for an item, use the item number as the reference code
Type
Use to group similar comments or identify the source or use of the comments; for example, PO for Purchasing, PE for Product Engineering. You can leave this field blank
Note: You have the option of validating this field against predefined Generalized Codes.
Language
Identifies the comment text language. If you are using multiple languages, you can leave this field blank; however, consider storing customer, supplier, and item comments in each language. During order entry, transaction comment language code defaults to the language code of the customer or supplier. This simplifies and speeds up data entry
Page
You can store up to 99 pages of text. The system identifies and accesses each page by using the page number. When a transaction accesses a multiple page master comment, it accesses each page one by one. This lets you select only a subset of pages such as 1, 4, and 7
