So close on this one. They are not going to give up Projects. I wonder why Epicor called it “Default Planning Contract” though, as if more than one Planning Contract for each Project was an option at some point…
We have heard the “Works as intended” and “Hire a consultant” arguments a few too many times. This is not the attitude that we were sold during Insights a few months ago, and it does not work for this company. Processes that should simply work and work simply (printing), don’t. Not sure how long we are putting up with this.
I think it’s better than it used to be, so at least there is movement in the right direction. But it’s still frustrating.
Insights is valuable to go to, because for some reason, the attitude there is “we can find a solution for anything” and people are super helpful. You will learn a lot and get all kinds of creative ideas. On the service line, not as much.
At least you have the people on this site to help out!
This site has been nothing but greatness! I think it is one of the strong points of the Epicor ERP platform; always has been… I have used quite a few other ERP systems and none had anything rivaling this group.
Ah; I just received word from support; “talk to a consultant or CAM to get a quote on a customization to allow Multiple Planning Contracts per Project”…
I wonder if this is something that could be customized? I am not sure why Project cares about Planning Contracts; could I somehow comment out the checks that validate the Planning Contract with the Project Menu?
Still kicking this issue around and looking for a solution; I can’t let go of the idea that if only Job Entry would not verify the Planning Contract and demand to find a match at the Project Entry level, I could likely make it a “go”. How hard/stupid, or impossible would it be to figure out what lines in the code call for this match and comment them out?
Quick update: We found a roadblock since Project Entry can only have a one-to-one relationship with a Planning Contract, but allows one-to-many relationship with Jobs. As each job has its own unique Planning Contract you run into a problem if you have more than one job on a project.
In order to get around this we resorted to C$G who built us a customization to circumvent this limitation and allow multiple Planning Contracts to be added to a Project.
Initial testing is promising. Currently creating a Bartender Auto Print label that prints Part and Job details for each PUR-STK with a value for Planning Contract.