The manufacturing team wanted me to ask on here about a Resource Group question they have. We have some machines that are “split” between two different divisions that have separate accounting needs due to some contractual obligations. One week the machines may be working for Division A and some weeks Division B. A Resource Group can only have one GL control and if we split them into separate Resource Groups we would be duplicating resources. Is this situation familiar to anyone? If so, how do work around it?
why cant you get put them as duplicate items - but adjust the RG calendar to show when they are available?
I will ask that to the group and let you know.
when you say “Division A”, I am assuming that this is a different SITE (Plant)…
Rules:
- a resource can only exist in one site
- if two sites each have a job that uses the same equipment, then that equipment must exist in both sites (with two different IDs).
- as @amaragni said, you could just create a calendar to specify when they are “allowed” to run, and then scheduling would be good… this doesnt address the GL account unless you have the resources in two different sites. the SITES can drive the GL Division.
Tim,
The way our plant was set up is a bit complicated but I will do my best to explain it. We are very much not your typical Epicor manufacturing operation as manufacturing is just a small piece of what the agency does. There is everything from medical practices, to group homes, to transportation services to manufacturing. This puts us in a situation where we have to document things very specific ways and keep specific things separate from each other.
We have two separate manufacturing locations physically but they were both set up as one plant during implementation. The machines in question are actually all located at one of the locations. The issue they are running into is that the administratively some pieces of the business fall under one category while others fall under a second. These two categories produce the exact same things on the exact same machines but due to our unique situation they must be accounted for completely separately.
I did pass the previous suggestion about creating a duplicate Resource Group and basing it on resource availability but I haven’t gotten a response from anyone on the idea.