All Job Requiring Serial Numbers

Epicor ERP 10
,
1

Is there a search screen or report that will show all jobs/assemblies that require a serial number? We have multiple jobs that get released and we are looking for a way to view all serial numbers that need created and assigned for all jobs.

2

Run a BAQ on the Part table where the field TrackSerialNum is true. Join that with JobHead (filtering for released and not closed/completed jobs) to see all active serialized jobs. We don’t do multi-level assemblies in a single job (it’s split among several jobs for traceability), but you could join Part or JobHead to JobAsmbl and get that level of data.

If you wanted to see which serial numbers have already been issued to a job, you’d have to bring in the SNTran table as well. Possibly JobMtl as well.

I don’t believe there’s a canned solution for what you’re trying to do. However, building your own via BAQ (and possibly turning that into a Dashboard) shouldn’t take much time.

3

Do you know of a way to only show jobs/parts that still need serial numbers? When I add SNTran it removes all the fields that do not have Serial numbers(like it should).

4

You should be able to add a where clause to the JobMtl table by seeing if JobMtl.IssuedComplete is true. You could also compare if RequiredQty > IssuedQty if you have a fudge factor. That’s the most straightforward option and, I believe, is what the Job Entry/Tracker screens use.

You’d only need SNTran to see which SN’s have been assigned to the job, and what happened to them after issuance.

5

So the parts that are serial tracked where we have to manually enter the serial numbers are all Assemblies and that is all they want to see is what job with assembly still needs a serial number. Is their any way to say where the part is serial tracked but in the job it has not been assigned a serial number? We do not issue assemblies currently so their is not an easy way for me to filter out by issues completed. I have a BAQ setup that shows me all parts that are serial tracked along with job assembly and job head and I am pulling in all jobs that have parts(all these are assemblies) that need serial tracked. The issue that I am having currently is how to filter out parts in jobs that already have a serial number assigned. For example, we have a job 000034-10-1 that has 5 assemblies that require serial numbers assigned to them, our QA department has already assigned two Serial Numbers but they are still showing up in my BAQ.

6

Is this one job with multiple subassemblies or one job per assembly and if the latter how are the jobs connected?

7

It is one job with multiple assemblies. After speaking with one of our consultants they recommended doing 2 queries and join them and only show the job and part of what still needs done. I have created 2 queries on a BAQ just trying to figure out how to join and show the needed information.

8

Create the subquery in your BAQ. Make sure the “type” (under the subquery options tab) is “InnerSubQuery”. This will make it available as a “table” in the phrase builder tab when you select another query in the BAQ.

I think I have one BAQ that’s like 5 levels deep with subqueries. It was driving a “single pane of glass” style dashboard. At that point, run-time becomes constrained by Epicor checking (and rechechking) column permissions for the user at each level. There’s a way around that, but hopefully your lookup is simpler.

9

Thank you for the information I have made both SubQueries “InnerSubQuery”. How would I go about linking up the subqueries by job and then filtering based on two different calculated fields? For example, one subquery counts the total qty of parts that need serial numbers in a job and my other subquery counts the total number of Serial numbers already created for a specific job. How would I make a filter to only show jobs where the qty needed does not meet the number of created SN?

10

There’s a few ways to do that. From (IMO) best to worst (in general):

  • Use the Table Criteria tab to filter results from one subQ table by the results of another using the “specified expression” option.

  • You can create a calculated field in the top level data set and then filter on that value at the dashboard level.

  • You could also join the two subQ tables together and place a filter on the join.