Managing Large Releases

Yahoo Archive
1
I guess I would have to go back and ask what's broken. Are you saying that if you ship it complete, the release does not close? In the shipping process is the shipment actually shipping the release complete? Does the flag get set (on the shipment) when you do?

The one to many and many to one principals have been in the software for years and I have never seen it broken unless the data is incorrect. One of the issues is that you must have multiple shipping lines because you are shipping from multiple jobs, if shipping all of the jobs at once. This can cause multiple invoice lines if you are not consolidating.

[scratching my head to see what is wrong]

Charlie Smith
Smith Business Services / 2W Technologies LLC
www.vistaconsultant.com/ www.2WTech.com




From: bryan_gerard_gft
Sent: Wed 7/7/2010 5:43 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Managing Large Releases



We thought about the one to one job to release link - but it is really very messy. Our customers certainly don't care that we would need to do it that way, and releases look like they should be able to handle multiple jobs tied to them. An invoice would be really bad on a big release that needs small batches (we can have 20 plus jobs for a release in some cases), plus it would really confuse our shipping department and it does not work very well with AMM this way. (We also have over 400 active jobs at any one time and it would be nice if the planners did not have to go in a change orders on top of their other workload.) I have been looking at it for a while today and think I just need to push Epicor to fix the BO and UI problems so that it actually works, or figure out how to customize around it not working.

--- In mailto:vantage%40yahoogroups.com, robertb_versa@... wrote:
>
> Split the line into multiple releases to maintain what I assume are preferred 1:1 (rel:job) make direct job relationships.
>
> You can schedule the releases to all ship at once and offset the job req'd dates to make production happy.
>
> If you do this (and are on v8.03.4xx) - schedule the linked jobs so the 1st release linked job is req'd last (and entered into shipping pack ID last).
>
> 4xx likes to close the entire line if release 1 is ship processed 1st. (Clearly one of those 'working as designed' support response bugs /:o )
>
> Rob
> --- Original Message ---
> From:"bryan_gerard_gft" <bryan.gerard@...>
> Sent:Wed 7/7/10 1:31 pm
> To:mailto:vantage%40yahoogroups.com
> Subj:[Vantage] Managing Large Releases
>
> We are having some difficulty managing large releases in Epicor 9 - currently, if we have a release for 20 parts, we may have to split it into 4 jobs to accomodate picking, machining, assembly, and testing stations etc. So now we have 4 jobs tied to one release - this makes it a bit tricky on shipping and accounting, not to mention that the release won't automatically close when it ships complete and the order screens stop showing any pricing (it exists in the background, just stops showing on the screen). Does anyone have a good process for this- it appears we are trying to make Epicor do something it does not want to do.
>





[Non-text portions of this message have been removed]
2
We are having some difficulty managing large releases in Epicor 9 - currently, if we have a release for 20 parts, we may have to split it into 4 jobs to accomodate picking, machining, assembly, and testing stations etc. So now we have 4 jobs tied to one release - this makes it a bit tricky on shipping and accounting, not to mention that the release won't automatically close when it ships complete and the order screens stop showing any pricing (it exists in the background, just stops showing on the screen). Does anyone have a good process for this- it appears we are trying to make Epicor do something it does not want to do.
3
Bryan:

Sun Is on M2K (Informix) but,
Going to: Epicor 9, 9.05.600B.2 SQL (go live date is 10/4/10)

For discussion purposes, we will say you have 20 parts that you want
to put in 4 'bunches' in order to handle at different times or different
processes.

I use "bunch" instead of Sub-assembly or Kit because those words
have too much associated with them that is irrelevant.

Create the top-level Part# that you sell. Configure it by:
Create a Parent for each bunch and add parts as BOM matl. Mark the
Parent as " Pull\pick as assembly".
Issue JOB for Top-level Part# - this will create requirements for
all parts. Based on what OPERATION each bunch is linked to. Each bunch
can have its own operations but no JOB is needed.

I have not been in on all the details, but having sub-assemblies
marked a "Pull as assembly" negates the need for separate JOB#'s.

Having the bunch be a Phantom would also work, but I always found
the costing of phantoms confusing. Plus Phantoms cannot have operations
- I think they can't.


len.hartka@...


________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of bryan_gerard_gft
Sent: Wednesday, July 07, 2010 1:29 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Managing Large Releases




We are having some difficulty managing large releases in Epicor 9 -
currently, if we have a release for 20 parts, we may have to split it
into 4 jobs to accomodate picking, machining, assembly, and testing
stations etc. So now we have 4 jobs tied to one release - this makes it
a bit tricky on shipping and accounting, not to mention that the release
won't automatically close when it ships complete and the order screens
stop showing any pricing (it exists in the background, just stops
showing on the screen). Does anyone have a good process for this- it
appears we are trying to make Epicor do something it does not want to
do.






This e-mail and any attachments may contain proprietary and/or confidential information. If you are not the intended recipient, please notify the sender immediately by reply e-mail or at 410-472-2900 and then delete the message without using, disseminating, or copying this message or any portion thereof. With e-mail communications you are urged to protect against viruses.


[Non-text portions of this message have been removed]
4
You might consider changing the sales order into multiple releases. This ties the individual release to a specific job rather than multiple jobs to a single release. This will give you more control on shipping and order management.

Charlie Smith
Smith Business Services / 2W Technologies LLC
www.vistaconsultant.com/ www.2WTech.com




From: bryan_gerard_gft
Sent: Wed 7/7/2010 1:29 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Managing Large Releases



We are having some difficulty managing large releases in Epicor 9 - currently, if we have a release for 20 parts, we may have to split it into 4 jobs to accomodate picking, machining, assembly, and testing stations etc. So now we have 4 jobs tied to one release - this makes it a bit tricky on shipping and accounting, not to mention that the release won't automatically close when it ships complete and the order screens stop showing any pricing (it exists in the background, just stops showing on the screen). Does anyone have a good process for this- it appears we are trying to make Epicor do something it does not want to do.





[Non-text portions of this message have been removed]
5
Split the line into multiple releases to maintain what I assume are preferred 1:1 (rel:job) make direct job relationships.

You can schedule the releases to all ship at once and offset the job req'd dates to make production happy.

If you do this (and are on v8.03.4xx) - schedule the linked jobs so the 1st release linked job is req'd last (and entered into shipping pack ID last).

4xx likes to close the entire line if release 1 is ship processed 1st. (Clearly one of those 'working as designed' support response bugs /:o )

Rob
--- Original Message ---
From:"bryan_gerard_gft" <bryan.gerard@...>
Sent:Wed 7/7/10 1:31 pm
To:vantage@yahoogroups.com
Subj:[Vantage] Managing Large Releases

We are having some difficulty managing large releases in Epicor 9 - currently, if we have a release for 20 parts, we may have to split it into 4 jobs to accomodate picking, machining, assembly, and testing stations etc. So now we have 4 jobs tied to one release - this makes it a bit tricky on shipping and accounting, not to mention that the release won't automatically close when it ships complete and the order screens stop showing any pricing (it exists in the background, just stops showing on the screen). Does anyone have a good process for this- it appears we are trying to make Epicor do something it does not want to do.
6
We thought about the one to one job to release link - but it is really very messy. Our customers certainly don't care that we would need to do it that way, and releases look like they should be able to handle multiple jobs tied to them. An invoice would be really bad on a big release that needs small batches (we can have 20 plus jobs for a release in some cases), plus it would really confuse our shipping department and it does not work very well with AMM this way. (We also have over 400 active jobs at any one time and it would be nice if the planners did not have to go in a change orders on top of their other workload.) I have been looking at it for a while today and think I just need to push Epicor to fix the BO and UI problems so that it actually works, or figure out how to customize around it not working.

--- In vantage@yahoogroups.com, robertb_versa@... wrote:
>
> Split the line into multiple releases to maintain what I assume are preferred 1:1 (rel:job) make direct job relationships.
>
> You can schedule the releases to all ship at once and offset the job req'd dates to make production happy.
>
> If you do this (and are on v8.03.4xx) - schedule the linked jobs so the 1st release linked job is req'd last (and entered into shipping pack ID last).
>
> 4xx likes to close the entire line if release 1 is ship processed 1st. (Clearly one of those 'working as designed' support response bugs /:o )
>
> Rob
> --- Original Message ---
> From:"bryan_gerard_gft" <bryan.gerard@...>
> Sent:Wed 7/7/10 1:31 pm
> To:vantage@yahoogroups.com
> Subj:[Vantage] Managing Large Releases
>
> We are having some difficulty managing large releases in Epicor 9 - currently, if we have a release for 20 parts, we may have to split it into 4 jobs to accomodate picking, machining, assembly, and testing stations etc. So now we have 4 jobs tied to one release - this makes it a bit tricky on shipping and accounting, not to mention that the release won't automatically close when it ships complete and the order screens stop showing any pricing (it exists in the background, just stops showing on the screen). Does anyone have a good process for this- it appears we are trying to make Epicor do something it does not want to do.
>