If you're pulling Est. GP and Cost on an invoice s...
# suiteanalytics
j
If you're pulling Est. GP and Cost on an invoice search, won't that pull the actual GP at that point since the numbers are finalized? Team is hung up on it saying "estimated". Seems weird to have to do formulas to get the "real" GP numbers. Never questioned it before, but being asked about it made me wonder. It seemed good to me, but maybe I'm off the beam. Funny how having someone ask makes you wonder.
k
No
Est GP is established at time of SO - and flows through to the invoice, but your actual cost is incurred on the fulfillment, or on a vendor bill (depending on if you are doing drop ship or not)
Now generally, it's gonna be in the ballpark if you are using the same costing method
however, FIFO/LIFO aren't supported for estimated cost.
j
Okay, so we do have to do formula work to get "real" GP. Looks like we'll have to source from several different records?
k
Well, first question - are you always selling from inventory? or always dropship? or mix of the two?
j
Mix.
k
Drop ship makes getting real GP in a saved search stupid hard.
You might need a customization to push values back to a custom field on your invoices
j
We're probably 80% drop ship.
And because we do customized items, some of our items do not have set cost and price. It's set at the time of sales order creation.
k
alternatively - you might be able to fudge with the values to keep the SO # in a static field on the PO/Invoice/Vendor Bill
and then you do a search and decode it to get it grouped by Sales Order so that you can display the info
I'd probably expect to dump 4-5 hours into getting all the pieces working for it.
j
Okay, well, we do need it. It's one of the top requests.
Will the captured field on the invoice cover our flux price/cost items?
k
Yeah.
j
Sounds good. I think that's what we want, since this will primarily be used for commissions and such.
k
We're pretty close to the limit of what I'd want to do for free, but give me a sec and I'll give you high level approach
👍🏼 1
I'd add a custom field call it "Analysis" or something. Set that field value via workflow/script on records. On Invoice it's created from. On PO it's Created from Created from on VB It should inherit from PO.
What that should result in is a consistent field value like "SO #1234
Then you do a couple decode statements based on transaction type field in order to get values like maximum of "invoice number" (and # of invoices in case an SO gets billed more than once)
then your search contains your types of Item Fulfillment/invoices/vendor bills
from there you'll have to do decode statements to calculate the amount fields based on the transaction type
and your search gets grouped by the analysis field I suggested earlier
Definitely something you do in chunks in order to get the right values individually, and then work the way to it being done. 4-5 hours assumes you are good at decode/understand the base structure. probably takes longer if you're unfamiliar with it.
j
I've never done decode at all. 😞
k
and if you have to script the field value as oppsoed to workflow, probably adds another layer
you can use case statements in the same manner as a decode
so if you're familiar with that, it should work. In theory - case statements are slower, but you shouldn't be running into any character limits with this one due to only having to deal with a few transaction types
decodes work like
decode ( {field I want to check}, value 1, what I want if it's equal to value 1, value 2, what I want if it's equal to value 2,..etc., if it's not equal to any of my values)
j
I'll look into it. Thanks for your help!
k
Should be enough to get you started down the path.
j
We've solved for that issue. Our reporting product has unlimited joins across all the netsuite data to answer questions like "actual" GP on an invoice, SO, PO. Let me know if you are interested in a demo. www.satorireporting.com
Here's an old video...but shows the basic concept (high level): https://www.satorireporting.com/post/netsuite-sales-order-profitability/