Search HansaManuals.com HansaManuals Home >> Standard ERP >> Nominal Ledger >> Reports Previous Next Entire Chapter in Printable Form Search This text refers to program version 5.3 Nominal Ledger - Examples In this section, we will illustrate the features offered by the Nominal Ledger report, using the Transactions resulting from a day's invoicing. Each Invoice carries an Object representing the sales person and one representing the office making the sale. The Objects representing the sales people belong to the "PERS" Object Type, while those representing the offices belong to the "OFF" Object Type.The Transactions involved are as follows:
First, use the Nominal Ledger report to list the journal postings to each Sales Account (i.e. to list Transaction rows with Sales Accounts): This is the resulting report: The next example is a list of Transaction rows with Objects belonging to a particular Object Type. As well as again entering the Sales Account range in the Loop 1 field, enter "PERS" in the Object Type field, with the aim of listing all Transaction rows that have an Object representing a sales person:
In one sense, entering "PERS" in the Loop 2 field is the same as entering it in the Object Type field in the previous example: it ensures that only Transaction rows with Objects belonging to the "PERS" Object Type will be listed in the report (although, as we are using the Show Object option, every Object is printed for each Transaction row, not just those belonging to the Object Type). However, entering "PERS" in the Loop 2 field also means that within each Account the postings will be sorted by sales person. This means that subtotals will be provided for each sales person within each Account. In general terms, you should use Loops 1, 2 and 3 to impose a sort order on the report. As you have entered the Account range in the Loop 1 field, the top level sort order is by Account. Entering the "PERS" Object Type in the Loop 2 field means that the second level sort order is by the Objects belonging to that Type. Subtotals are provided at the lowest level of sorting. So, in this case, the report is sorted by Account and then by Object, with subtotals for each Object: The Loop 2 and Loop 3 fields are both used as search criteria (only Transaction rows with Objects belonging to both Object Types will be listed in the report). Also, because an entry has been made to the Loop 3 field, subtotals will be provided at this level. Again, the resulting report is structured on an Account-by-Account basis (i.e. the top level sort is by Account). This time, within each Account the postings are sorted first at the Loop 2 level (i.e. by office) and then at the Loop 3 level (i.e. by sales person). Within each Loop 2 Object (i.e. within each office) subtotals are provided for each Loop 3 Object (i.e. for each sales person): This is the report, sorted by Object (level 1) and then by Account (level 2), with subtotals provided for each Account within each Object: |