https://netsuiteprofessionals.com logo
Join Slack
Powered by
I'm looking to make a report (not using the actual...
# general
r
I'm looking to make a report (not using the actual report tool in NS) that shows me each day how many transactions are open. Anyone have any ideas on what to use for this? I'm not sure if a saved search will be able to do this. Perhaps a workbook can do this? I have not used that feature yet.
n
I use saved searches for things like this. I have one to show all my open RAs, all my open Sales Orders, Etc. I loved saved searches but am still learning a lot about them.
r
I know how to have them to show open sales orders, but not a historical view, example: 1/1: 50 open, 1/2: 40 open, 1/3: 55 open
I wanna see how many open on every day looking back years
perhaps a SQL function will do this
n
sorry if this is a dumb question - when you say how many were open each day, are you looking for how many were created that day, or how many were open at the start or the end of the work day, or something else. Like for me our company wants to ship at least 90% of all orders same day. So I need a report that shows me how many were opened that day and how many were not fulfilled by the end of that day. Is that kind of what you are looking for or am I just way off LOL.
r
how many fall within a current status, for example all work orders with a status of "released", showing that total per day
it's basically a historical pipeline chart I want
n
Oh ok... wasnt quite what I was thinking then, sorry! Wish I knew a little more to be able to help. we dont actually use the release feature
r
The problem is the report just gives you the current total as of today. if you ran the report yesterday the total would be different. I don't see how to save each days total in a table to show historical view
k
I don't think this is possible.
You're probably better off with a customization to run the search at the end of each day and create a custom record for handling this reporting requirement.
r
What type of customization. A suitesctipt?
k
Yes
r
I’m curious if a workflow could handle this
k
Definitely not
actually
it probably could
use the create record action.
Actually, it'd be fairly comically simple to do it
you'd just have to have a workflow run on all your records that are open - and have it run once per day.
only issue might be governance.
Yeah, you'd probably have to have it run on repeat - and store the "last created log" in a custom field on the record so it only hits it once per day.
would have to allow non GL edits in closed periods too.
I'm sure there are other considerations you'd have to do, but that should be enough to get a couple ideas on how to handle it.
r
thank you !
so basically this would require, creating a new record type. having a workflow create a new record in that record type to log each days value. then having a report that will show each record, as each one is a unique days value?
k
It would have to create a record for every transaction
If you were trying to capture line values - it would have to create a record for EVERY line. (for example items)
and at that point - I'd expect to start having problems with validity/accuracy of data without a script
in which case - you may as well script it the right way to create the reporting points that you want exactly like you want them instead of basically exploding your database out.
r
Yea makes sense, a new record for every work order would not be good
k
Could also do one on your item records. Create saved search fields.
for calculating the values and then store that in your custom records.
r
I am just trying to see how many work orders are in process on each day, comparable to historical pipeline reports for sales orders pending fulfillment
k
Yeah, definitely a summary saved search field for each value you want to capture (maybe count of work orders, and count of sales orders, and then quantity unfililled and quantity to be built on the work orders) and then you can do a custom record that holds that will all the date - and it's by item. I'd probably bank on 5-6 hours getting it up and running a test, and then some additional time after that to fine tune and I have a pretty good idea on what I'd be doing.
👍 1
You might find your expectation on time would be a little different.
2 Views
Open in Slack
PreviousNext
Powered by