Trying to get an idea of the best way to setup package codes. We have cartons that contain properties of their own, but we also have pallet configurations of how those cartons go on a pallet. Would that specific pallet configuration be it’s own package code or is that not ideal? I feel that might be too rigid, but then i’m not sure how to memorialize that information in Epicor. Anyone out there using package codes that can shed some light on how they have their stuff setup? Our configurations look like this.
We had similiar challenge. So we used the part revision to hold data about how a part is packaged:
Volume (including the wooden palet )
Weight
Height, width and lenght
Number of items in the package
Then we modified Order entry module, shipping module and any other needing to address those UD fields… and all the related reports to show the different new ud fields as well…
So our customers are not only buying parts, they are buying x number of packages of y parts each.
The shippers also need the volume of the package contents and it’s weight so they can provide us with a valid delivery price to submit.
We are not using third party tools such as Manifest…
I have read that 10.2 has improved on the packaging info, but I have not yet take a look into it. we are on 10.0…
Pierre
Would a Part specific UOM do the trick? The UOM code could be 2x3x8 which indicates both the qty, and the stacking (2 wide, 3 deep, and 8 high)
Still puts us in a bind if the packaging requirements change. Then we are making a new part again. We use Part Specific right now. If I’m going to make vast changes in how we handle stuff I want to try and make it painful once.
1 Like