Blank PackIDs (Shiphead)

Epicor ERP 10
1

Over the past few months, blank ShipHead rows being generated occasionally. We always ship products by going in to Customer Shipment Entry, new Pack, enter SO number, and proceed with the rest of the shipment, then Print and/or mark the Shipped checkbox. Somehow extra PackIDs are getting created in between those real PackIDs. Here’s a search of recent Packs: The ones with no customer have no information at all except PackNum, LegalNum, and ShipDate. The Shipper says that she does not start a pack, then abandon it.
image
I enabled tracing on the shipper’s workstation for almost a week, and of course, the problem didn’t occur. So, I turned it off, and now I see that black PackIDs are still generated occasionally. I enabled a Change Log BPM on ShipHead, but so far no hits.
Any ideas what could be generating these blank rows in ShipHead table, or how to troubleshoot the source?

E10.2.200.20, single company, single site.

2

A Counter Sale sales order can automaticallyt make a packer. But it would have the customer name, and related ShipDtl records.

Do you create the Change log on ShipHead? It should show the user, date and time that created the record.

3

Make a BAQ of ShipHead, showing PackNum, ShipDate, ShipPerson, EntryPerson, ChangedDate, ChangedBy, ChangedTime
Where ShipHead.CustNum = 0

4

Good Morning,

I see ship head records with zeros on cust num similar to yours where user did not actually add lines and complete the pack, but left empty pack slips out there.

Nancy

1 Like
5

Calvin, I just turned on BPM Change Logging on ShipHead today, so no data yet. And here’s a BAQ with Changed by and Created On (the ‘manager’ entries are when a DMT updates the tracking number after UPS end-of-day processing.

image
image.png733×401 10.6 KB

So, the BAQ points to our shipper (JAF) doing something to create the Packs. Maybe as Nancy suggested, creating but not completing.

1 Like
6

#8050 has a ChangeTime of 38618, wich is equal to 10:43:38. Which is close to the Created On value.

#8051 has a Created On value of 10:44 (within a minute of #8050.

My guess is that JAF created 8050, then created 8051 and populated that Packer, leaving 8050 “orphaned”

7

Yes, those create times do look suspicious. Hopefully the ChangeLog will catch JAF in the act.

8

We had that issue also and traced it to user behavior. The user finished a packing slip and then to clear the form of the data they were using the New icon instead of the clear icon at the top. This created a new pack but the user did not need a new pack at the time, went onto other things then came back, hit save and click new again.

So we retrained the users and the incidence of such blanks does still happen but very rare.

Vinay Kamboj

1 Like
9

OK, with both Vinay’s and Nancy’s comments, I think I have to admit that the blank Packs are caused by user error. Even though the shipper says she never creates a new Pack unless she needs it, I think it is just to easy to do inadvertently
So, thanks for the feedback everyone.

10

agreed - i had the same problem way back in V9

11

If you hit new pack twice it saves the blank pack number and generates another one. Except for the cursor changing the user has no indication it happened.

12

Customer Shipment Entry > New Pack > Save
Congratulations, you have a new packing slip with no customer or order info.

1 Like