I realize that this is not exactly what you are asking for.But, an alternative would be to do a cost roll using the costing workbench and NOT post it.You can easily query against the results of that.
Both had quite good ideas.However, I prefer for “expense items” to use Stocked=true and Qty bearing=false.
to be thorough, you could link from the GL Account via TranGLC table to the invoice.Invoice Detail should include quantity, revenue, and cost.
The way we set it up is below, and it works wellQty Bearing checkbox clear Non-stock item checkbox clear Standard cost of $x Process MRP checkbox clear Note that the product group and part class below control the GL accounts impacted with transactions (for instance, the inventory context should be a contra/offset account somewhere in the income statement, not on the balance sheet) Service Labor Parts For Service to record their time against the Sales Order and charge the customer for the time, we will create several non-physical parts, named something like the following: Service Time-Portables Service Time-Hand Pieces Service Time-Chairs/Stools Service Time-Elect Service Time-Motors Service Time-Anesthesia These will have the following parameters, and will likely be manually created in Epicor (Not via DMT) Product Group=CSTSVC Part Class = SVC New UOM will be created (Scott) UOM of Hours with 2 decimal places UOM Class of Time
Arno,If you have that requirement, you should implement and use the legal numbering for Invoices.Standard Epicor invoice numbering allows invoices to be deleted after being created (if not posted), and does not retain anything about the deleted invoices. This is fine in most cases, in the US. But I understand that some entities enforce additional rules.Alternative, one could add customizations to track deleted invoices.
To fix these, have you tried the normal approach for Unreceived lines, of using Invoice Receipt Match program/screen?
And, that is one reason I always recomment NOT using “unreceived lines” in AP.There are better ways to meet the objective that cause less problems. To fix this, I would try a new invoice to use up the invoice receipt match and adjust the dollars appropriately.
I use ERPEdge from SeattleShroades@erpedge.net
Erin,We could discuss options at length, but the following is what I have done over and over as both an Epicor financial consultant, as well as a Controller and CFO.First, use the system!Enter invoices and post them as soon as possible, using accurate payment terms.When it is time to pay them, use the system to have them selected based on DUE date. This even pulls ahead for prompt payment discounts, which are almost always worth taking.For times when cash is tight, one can select individual invoices to pay from either the aging, or an alternative source.
Hi Shannon,I have done a variation of Glenn Owers solution using BPMs. This allows you to put up messages when it denies the action.Of course, in your testing, you will want to validate all other Posting process to be sure they function as you wish (AR, AP, Capture COS, bank,….)
Another technique for troubleshooting this kind of problem is to use the RightClick Open With functionality to drill through all the setup screens to the GL Control code, Starting at the PO Line/Release in question. Another thing that can happen, if you are flexing your division segment on warehouse or Site, is that the combination of all the segments may not exist as a valid GL Account.Another thing that helps is to be sure that you have populated ALL contexts in the default ‘Inventory, COS, WIP’ GL Control code, with a valid account. This is a good place to put suspense accounts for when your other GL Control codes fail.Yet another troubleshooting technique is to turn on the PE Log viewer, post again, and review the results. This is very hard to read, but generally has the answer buried in the details.
this is a long shot, but you might try clearing personalizations for that user for that screen.I have experienced users being unable to open a screen after personalizing it, and been successful at solving it with this approach.
Lots of good answers above.Agreed- a journal entry is required to reclass when you change part class. Regarding the obsolete/slow moving separation, the cleanest approach is to move it to a separate warehouse, after setting up the division GL Control on the warehouse, and setting up appropriate GL accounts. Note that there are a lot of pieces to this approach. It works well and is common, but is not intuitive to setup. I recommend engaging a consultant to help with this setup.
we used a phone consultant to assess our choices when we had to go remote with Covid.His name is Andrew Bond (abond@bandwidthave.com)425-232-8687 (mobile)
In current versions, posting of the AP invoice is irrelevant for the question of whether you can update the Misc PO Part Class or release GL Account. If you dont believe me, then test it, because it is true in our version--we do it. And, no, you do not need to reverse the receipt. (though I used to think so, so maybe we had to do that in E9).The reason it works is the nature of how/when Epicor posts to the GL. On the financial side, it posts immediately when you post the group/batch. On the Production side, it runs the posting rules and looks at the GL Control codes at the time of running Capture COS. It does not care whether it has been invoiced or not.My credentials for you believing me: I have been using Epicor since 2003, and spent 4 years as an Epicor employee doing implementations (E9 and E10).
It should not matter that the AP Invoice has posted. It is only relevant that the Capture COS has not posted the relevant transaction (PO Receipt, or sometimes PO Variance and Misc Charge).Remember that the Capture COS looks at the GL Controls for the GL Account at the time it runs (not at receipt or AP Invoice).
Alex Have you played with crew size? Paul Jackson pjackson@aseptico.com ------
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.