1) Category - Categories are types of costs that are defined for a whole company i.

The CategoryTable table contains expense category definitions. ii.The ProjCategory table is used to store project specific category information . General category information are stored in the table named CategoryTable which is related to the ProjCategory table. Categories are used in the Project module when recording project transac tions. iii.ProjCategoryGroup is the table for category group. 2) Ledger Posting i. The ProjPosting table contains the ledger accounts that will default when ent ering project transactions. ii.In general, Ledger posting is setup on the category or category group levels for cost side of posting transactions and on the individual project or proje ct group for revenue and WIP transactions. Cost and sales price i. The cost price is the price per unit that is charged to the project. ii.If a customer is invoiced for expenses and consumption, a sales price is spec ified per unit. Read transaction type rules in Part 1.1 page 29 3) Line Property i. The ProjLineProperty table contains the line properties that are used when re cording project transactions. Line properties contain settings that will be used during posting. 4) Project contracts i. The ProjInvoice table contains information on project contracts and are used to group together projects. Project contracts could also be used for grouping project transactions i n reports and inquiries. -------------------------------------------A project hierarchy can have different project types. For eg, TM can have FP as child -------------------------------------------1) Hour Journal i. ProjJournalTable - Header Table as well as form name ii.ProjJournalTrans - Lines table iii.ProjJournalTransEmpl - Line form name iv.ProjJournalCheckPost - Class for validate & posting hour journals 2) Expense journal can also be entered through general journal and also through Accounts Payable. General Ledger -> general journal Accounts Payable -> Journal -> Invoice journal (When exact project is kn own) " -> Journal -> Invoice register (When exact project is n ot known) i. LedgerJournalTable - Header Table as well as form name ii.LedgerJournalTrans - Lines table

iii.LedgerJournalTransCost - Line form name. iv. LedgerJournalCheckPost -- Class accessed through LedgerJournalCheck and LedgerJournalPost 3) Fee journal are also automatically entered through service management module Only T&M Projects are allowed i. ProjJournalTable - Header Table as well as form name ii.ProjJournalTrans - Lines table iii.ProjJournalTransRevenue - Line form name iv.ProjJournalCheckPost - Class for validate & posting fee journals 4) Item journal Purchase order can also be created through Projects module. The differen ce between entering a PO from the Project module versus entering it from Accounts Payable is that in Accounts Payable, a project number cannot be selected, and in the Project module, the project number is a required field. i. InventJournalTable - Header Table as well as form name ii.InventJournalTrans - Lines table iii.InventJournalProject - Line form name iv.InventJournalCheckPost - Class for validate & posting item journals -----------------------------------------------------1) Invoice proposal Table description: The ProjProposalJour table is used to store invoice proposal headers. Project invoice proposals are created when billing customers. Posting a project invoice proposal will create a project invoice. Hour tab - ProjProposalEmpl & ProjEmplTrans Expense - ProjProposalCost & ProjCostTrans Fee - ProjProposalRevenue & ProjEmplRevenue Item - ProjProposalItem & ProjItemTrans ProjInvoiceChoose is the class called while creating Invoice proposal, w hich in turn calls ProjInvoiceChooseNormal class 2) Invoice ProjFormLetter is the base class, which in turn calls ProjFormLetter_Inv oice