If you do not use Output Order for complete posting and you use Position Journal, you need to use Job Journals for posting item and resource consumption on projects. In this variant, we use Position Journals for revenue posting and Job Journals for expenses posting (COGS and resource cost). This is in principle standard NAV Job Journal with some customization as Output Order lines.
We use the Job Journal to post usage for a job. Each entry on a job journal line must be related to a job. As all NAV journals, the information we enter in the Job Journal is temporary and can be changed as long as it is in the journal. After we post a journal, the journal will be empty and the transactions will be posted to individual accounts and entries.
When we start to enter data, we must fill ‘Job No.’ and ‘Job Task No.’ and after that we need to choose line Type (Resource or Item) and choose desired Resource/Item. After that, process is different depend of line type (as Output Order lines):
Item
For Item, we need to fill ‘Location Code’. We can get default location code for project if we make this setup on Project Card. We need to fill item quantity, as well and this is all. All costs and prices for the item will be filled automatically.
Resource
For Resource, we can fill more fields. There are not all mandatory and this depend of setup for company and/or project. It is necessary to fill quantity per Unit of Measure and we can choose ‘Work Type Code’ for different Unit of Measures/Cost/Price. If this is people type of resource, this is enough and as items, costs and prices will be automatic filled. But if we choose machine resource type, we can fill more fields.
First of them are ‘Waiting Time’ and ‘Extremely Stagnation Time’. ‘Waiting Time’ is time when resource did not work because bad organization. System will be calculate cost for all quantity time, but price for (‘Quantity’ – ‘Waiting Time’) if ‘Waiting Time’ is acceptable. If this time is not acceptable, system will calculate price based on specific formula (this is very complex setup, and I will explain it in independent post). ‘Extremely Stagnation Time’ is time we use only for evidence. This is a time when we was prevented for work (nasty weather or some other force majeure).
We can fill ‘Mechanization Resource Code’ if we know exactly what machine is worked. System can propose only machines for choosing resource. If we in advance know what machine worked, we can fill this field, and ‘Resource No.’ will be filled automatically. If we have configured machinist for mechanization resource, this field will be filled automatically, but if we have not it, we can choose ‘Employee No.’ for machinist from filtered employee list only from departments who use machines.
Know we know what time machines spend for making position, but we don’t know what they are worked exactly. Because of that, we have ‘Ongoings Code’ where we can define what our machine really do. ‘Ongoings Code’ list has Unit of Measures and they are configured depending resource types. When we choose this code, we need to fill ‘Ongoings Quantity’.
If our machine is the vehicle, we can fill additional fields: ‘Mileage’ and ‘Tour Quantity’.
We can post this Job Journal as standard NAV journals.
In next posts, I will explain Recurring Position and Job Journals and after that result differences between presented two methods of posting in construction.
