Skip to main content
Solved

Loose Inventory Due Tab


Forum|alt.badge.img+3
  • Sidekick (Customer)
  • 8 replies

Which Tables populate the ‘Loose Inventory Due Tab’? Maintenix Version 8.3, SP5 u25.

Best answer by sureamiceman

Looks like that Tab uses a query where the logic is:

  • It is LOOSE INVENTORY
  • Not yet issued
  • IS Serviceable 
  • IS Authorized for the current user to view
  • Has at least one non-historic task due WITHIN THE MINIMUM USAGE FOR RELEASE ← probable reason #1
  • Exclude NaN situations (not sure what NaN stands for)
  • % of remaining usage is greater than the minimum for release [(usage remaining qty/interval)<minimum usage %] ← #2

I’m guessing the minimum usage % remaining is why nothing is showing up...meaning it is not close ENOUGH to trigger it to show up in the queue.

View original
Did this topic help you find an answer to your question?

6 replies

sureamiceman
Sidekick (Partner)
Forum|alt.badge.img+5
  • Sidekick (Partner)
  • 14 replies
  • March 17, 2025

 

With the Tab description:

Loose Inventory Due idTabLooseInventoryDue A list of loose inventory items that have accumulated enough usage to require maintenance. Use this tab to coordinate the execution of that maintenance work.

 

It is going to be several tables I’m sure, INV_INV being a primary table (for the inventory itself) and likely SCHED_STASK (the activated task(s) against the Inventory).

What are you trying to accomplish by knowing the tables where that data is drawn from?


Forum|alt.badge.img+3
  • Author
  • Sidekick (Customer)
  • 8 replies
  • March 17, 2025

Hi Tim.

Currently our Loose Inventory Due Tab is empty. Even though there is inventory removed for access and NOT Turned In. The removed Inventory has plenty of SCHED_STASKs. But we do not see any Inventory, Tasks or Dates on the Tab. I wasn’t sure whether the Tab is connected to an ‘Materialised View’ to populate or particular scenarios which trigger the inventory to appear on the Tab.

 

Thanks 

Reg


sureamiceman
Sidekick (Partner)
Forum|alt.badge.img+5
  • Sidekick (Partner)
  • 14 replies
  • Answer
  • March 17, 2025

Looks like that Tab uses a query where the logic is:

  • It is LOOSE INVENTORY
  • Not yet issued
  • IS Serviceable 
  • IS Authorized for the current user to view
  • Has at least one non-historic task due WITHIN THE MINIMUM USAGE FOR RELEASE ← probable reason #1
  • Exclude NaN situations (not sure what NaN stands for)
  • % of remaining usage is greater than the minimum for release [(usage remaining qty/interval)<minimum usage %] ← #2

I’m guessing the minimum usage % remaining is why nothing is showing up...meaning it is not close ENOUGH to trigger it to show up in the queue.


Forum|alt.badge.img+3
  • Author
  • Sidekick (Customer)
  • 8 replies
  • March 17, 2025

Thanks Tim. I hadn’t considered MINIMUM USAGE FOR RELEASE as being a factor.


Robert Bellemare
Hero (Employee)
Forum|alt.badge.img+10

Hey Reg,

You can find the qrx driving this page as plain text inside the Maintenix ear. I keep a copy of Maintenix on my computer with all the war and jar files extracted for occasions such as this, so that I can share the information that you will be able to see without access to the full source code.

If you install a copy on your local computer you can extract apps\assetmanagement\app\assetmanagement.ear\maintenix.war. I extracted all the archive files in this folder into their own respective folders.

Within \maintenix\WEB-INF\lib you will find and extract maintenix.jar.

From here you can find the folder maintenix\com\mxi\mx\web\query\todolist which contains the queries that populate all the To Do Lists. LooseInvDue.qrx is used for this page. As explained by Tim, it’s likely that you are not seeing this inventory because it is not turned in (issued_bool = 0).


Forum|alt.badge.img+3
  • Author
  • Sidekick (Customer)
  • 8 replies
  • March 18, 2025

Thanks Rob.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings