Hi Devendra,
When using $repeatPackages at the top level of the report, this loops through *all* packages in your project, in the same order they appear in the project browser. This is different than how parent/child requirements get reported on, which is where I was mistaken. So, the following line:
$repeatPackages0 where Parent <> ‘’
...has the result of cycling through *all* of the packages in your project (parent and child packages) that aren't at the top level. While you get the desired Loan Origination package lower down in your report - it's included a second time by the $repeatPackages1 keyword - that first repeat loop is grabbing it as well, since it is not at the top level.
In order to get the results you're looking for, we need to change up the formatting a bit. Since there isn't an "IsTopLevel" keyword for packages as there is for requirements, instead of having a repeat packages loop on all child packages - that line from your template I included above - we need to limit that first level loop so that it's only looking at the top level of your project. (You can leave out any other keywords if you don't want any information reported on that top level.)
Once we've done that, just nest as many additional $repeatPackages keywords within the first level as are necessary to include as many nested package levels you have in your project.
As an example, I've modified your template so that the first loop is only looking at the top level package - yet returns no information - then included two additional nested repeats duplicating what you already had there to drill down to two levels of packages in your project.
Jason