Invoicing as Nightly Batch Process

system · April 21, 2009, 2:56pm

Hi

Has anyone tried posting AR invoices in nightly batch ? we are on 8.00 11b . In most ERPs this used to be a standard functionality but haven't found it in Vantage yet. Please advise.

Vishal

To: vantage@yahoogroups.com
From: robertb_versa@...
Date: Tue, 21 Apr 2009 11:23:50 -0700
Subject: Re: [Vantage] Re: Resource Error When Posting Labor Through MES with AMM

405a - but this also worked fine on 404.

--- On Tue, 4/21/09, markewhittaker <markewhittaker@...> wrote:

From: markewhittaker <markewhittaker@...>
Subject: [Vantage] Re: Resource Error When Posting Labor Through MES with AMM
To: vantage@yahoogroups.com
Date: Tuesday, April 21, 2009, 12:46 PM

Robert Brown, what patch level are you running?

--- In vantage@yahoogroups .com, Robert Brown <robertb_versa@ ...> wrote:
>
>
> We have Automove defualt checked on all resource groups/resources & use the same whs/bin for both In/Out (within each department's resource groups/resources. .. Different deparments have different warehouses associated with them as well as correspponding bins.)
>
> Works just fine using same whse/bin for both in/out & automove checked.
>
> (On 405a) We also had to customize MES End Activity and Qty reporting to force the prod complete and op complete checkboxes to be true when the total reported qty (+ pior reproted qtys's complete) match the total qty due.
>
> Also added a stop update loop to prevent overreporting.
>
> These were vb.net customizations though and are subject to 'silent breakdown' (with no warning to user)... Eventualyy we'll get around to replacing with sturdier BPMs.
>
> Rob (Brown).
>
> --- On Tue, 4/21/09, Rob Bucek <rbucek@...> wrote:
>
> From: Rob Bucek <rbucek@...>
> Subject: RE: [Vantage] Re: Resource Error When Posting Labor Through MES with AMM
> To: vantage@yahoogroups .com
> Date: Tuesday, April 21, 2009, 10:30 AM
>
>
>
>
>
>
>
>
> I have a customization that defaults that box to checked as well as the
> fact that I have it hidden and no tab stop. We struggled a lot to get
> this working at first then broke through it but im struggling to
> remember what our break throughs were. You do want the check box = to
> true however. You also always want your input and output bins to be
> different. Also uncheck autmove.
>
> Rob Bucek
>
> Manufacturing Engineer
>
> PH: 715-284-5376 ext 311
>
> FAX: 715-284-4084
>
> <http://www.dsmfg com/>
>
> (Click the logo to view our site)
>
> ____________ _________ _________ __
>
> From: vantage@yahoogroups .com [mailto:vantage@ yahoogroups .com] On Behalf
> Of markewhittaker
> Sent: Tuesday, April 21, 2009 9:23 AM
> To: vantage@yahoogroups .com
> Subject: [Vantage] Re: Resource Error When Posting Labor Through MES
> with AMM
>
> Another think I have noticed that may provide a clue. On the operations
> that will actually let me clock through and complete activity, when I go
> into the End Activity screen, the Request Move checkbox is checked by
> default. Any operations that are going to give me the error, that
> checkbox is not checked by default. And on those operations where the
> checkbox is not checked by default, no matter if I check it or not, I
> get the same error message. Help screen doesn't say anything about what
> would cause that flag to come up checked by default.
>
> --- In vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com> ,
> Robert Brown <robertb_versa@ ...> wrote:
> >
> >
> > Make sure the resource GROUPS your resources are under have default
> In/Out Whse Bins defined. AMM has been working fine for us (re WIP
> moves) set up like this and, in counterpoint, Backflushing DID NOT work
> for us UNTIL we set up like this.
> >
> > It seems the processing logic looks at the resource group level 1st,
> and only looks further (at resource level) if the In/Out field aren't
> left blank at the resource group level. (I believe there is an SCR on
> this - at least for backflushing. )
> >
> > Also: Are you moving WIP OUT to a whse bin that differs from where the
> next OP's resource is defined to move the WIP IN from?
> >
> > ...Something to be said for KISS principles re the IN/OUT whse bins
> (define a single common WIP move whse bin for both IN/OUT use on all
> resources) UNLESS you are continuous processing and your OPs always
> follow a single sequence.
> >
> > Hope that helps.
> >
> > Rob
> >
> > --- On Mon, 4/20/09, markewhittaker <markewhittaker@ ...> wrote:
> > From: markewhittaker <markewhittaker@ ...>
> > Subject: [Vantage] Resource Error When Posting Labor Through MES with
> AMM
> > To: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
> > Date: Monday, April 20, 2009, 6:22 PM
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > We recently purchased the AMM license and I am trying to use the
> material queue function to generate moves for WIP in the material queue
> as a job completes one operation and moves to the next. I set up the
> resources with input/output whse/bins. But when I start posting labor in
> MES and try to end an activity, on many operations it crashes and will
> not end the operation. A message pops up telling me to check the
> appserver log. The appserver log shows this: Procedure: 'ConsumeQty
> lib/pwipmtlq. p' Line:1037) ** No Resource record is available. (91). I
> have a call in to Epicor. At first the support person said that patch
> 407b fixes the problem (I am on 8.03.404a). Then when I described more
> detail, she said she would try to re-create the problem and get back to
> me. Experience tells me that when they say that, you won't hear from
> them for weeks.
> >
> >
> >
> > Anyone else run into this issue?
> >
>
> [Non-text portions of this message have been removed]
>

[Non-text portions of this message have been removed]

system · April 20, 2009, 6:22pm

We recently purchased the AMM license and I am trying to use the material queue function to generate moves for WIP in the material queue as a job completes one operation and moves to the next. I set up the resources with input/output whse/bins. But when I start posting labor in MES and try to end an activity, on many operations it crashes and will not end the operation. A message pops up telling me to check the appserver log. The appserver log shows this: Procedure: 'ConsumeQty lib/pwipmtlq.p' Line:1037) ** No Resource record is available. (91). I have a call in to Epicor. At first the support person said that patch 407b fixes the problem (I am on 8.03.404a). Then when I described more detail, she said she would try to re-create the problem and get back to me. Experience tells me that when they say that, you won't hear from them for weeks.

Anyone else run into this issue?

system · April 21, 2009, 6:21am

Make sure the resource GROUPS your resources are under have default In/Out Whse Bins defined. AMM has been working fine for us (re WIP moves) set up like this and, in counterpoint, Backflushing DID NOT work for us UNTIL we set up like this.

It seems the processing logic looks at the resource group level 1st, and only looks further (at resource level) if the In/Out field aren't left blank at the resource group level. (I believe there is an SCR on this - at least for backflushing.)

Also: Are you moving WIP OUT to a whse bin that differs from where the next OP's resource is defined to move the WIP IN from?

...Something to be said for KISS principles re the IN/OUT whse bins (define a single common WIP move whse bin for both IN/OUT use on all resources) UNLESS you are continuous processing and your OPs always follow a single sequence.

Hope that helps.

Rob

--- On Mon, 4/20/09, markewhittaker <markewhittaker@...> wrote:
From: markewhittaker <markewhittaker@...>
Subject: [Vantage] Resource Error When Posting Labor Through MES with AMM
To: vantage@yahoogroups.com
Date: Monday, April 20, 2009, 6:22 PM

We recently purchased the AMM license and I am trying to use the material queue function to generate moves for WIP in the material queue as a job completes one operation and moves to the next. I set up the resources with input/output whse/bins. But when I start posting labor in MES and try to end an activity, on many operations it crashes and will not end the operation. A message pops up telling me to check the appserver log. The appserver log shows this: Procedure: 'ConsumeQty lib/pwipmtlq. p' Line:1037) ** No Resource record is available. (91). I have a call in to Epicor. At first the support person said that patch 407b fixes the problem (I am on 8.03.404a). Then when I described more detail, she said she would try to re-create the problem and get back to me. Experience tells me that when they say that, you won't hear from them for weeks.

Anyone else run into this issue?

system · April 21, 2009, 9:38am

That has been our experience as well, it sounds like Rob's set up is
much like our own, which works fine.

Rob Bucek

Manufacturing Engineer

PH: 715-284-5376 ext 311

FAX: 715-284-4084

<http://www.dsmfg.com/>

(Click the logo to view our site)

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Robert Brown
Sent: Tuesday, April 21, 2009 5:21 AM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Resource Error When Posting Labor Through MES
with AMM

Make sure the resource GROUPS your resources are under have default
In/Out Whse Bins defined. AMM has been working fine for us (re WIP
moves) set up like this and, in counterpoint, Backflushing DID NOT work
for us UNTIL we set up like this.

It seems the processing logic looks at the resource group level 1st, and
only looks further (at resource level) if the In/Out field aren't left
blank at the resource group level. (I believe there is an SCR on this -
at least for backflushing.)

Also: Are you moving WIP OUT to a whse bin that differs from where the
next OP's resource is defined to move the WIP IN from?

...Something to be said for KISS principles re the IN/OUT whse bins
(define a single common WIP move whse bin for both IN/OUT use on all
resources) UNLESS you are continuous processing and your OPs always
follow a single sequence.

Hope that helps.

Rob

--- On Mon, 4/20/09, markewhittaker <markewhittaker@...
<mailto:markewhittaker%40yahoo.com> > wrote:
From: markewhittaker <markewhittaker@...
<mailto:markewhittaker%40yahoo.com> >
Subject: [Vantage] Resource Error When Posting Labor Through MES with
AMM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Date: Monday, April 20, 2009, 6:22 PM

We recently purchased the AMM license and I am trying to use the
material queue function to generate moves for WIP in the material queue
as a job completes one operation and moves to the next. I set up the
resources with input/output whse/bins. But when I start posting labor in
MES and try to end an activity, on many operations it crashes and will
not end the operation. A message pops up telling me to check the
appserver log. The appserver log shows this: Procedure: 'ConsumeQty
lib/pwipmtlq. p' Line:1037) ** No Resource record is available. (91). I
have a call in to Epicor. At first the support person said that patch
407b fixes the problem (I am on 8.03.404a). Then when I described more
detail, she said she would try to re-create the problem and get back to
me. Experience tells me that when they say that, you won't hear from
them for weeks.

Anyone else run into this issue?

[Non-text portions of this message have been removed]

system · April 21, 2009, 10:08am

I have all that set up. On a test part, I have even gone so far as to have every resource and resource group on every operation have the same values for input and output whse and bin and set them all for auto-move, which should not even produce a material move request. I can clock through the first operation fine, and then start the second operation, but I get the crash when I try to complete the second operation. The part tracker will show the parts in that whse bin for that operation, but I can't move it out. I have been trying every possible combination I can come up with and can't get it to work. Forget the wip moves, I would be happy to be able to complete a job again. Luckily I did not apply the licensing to our live system yet or we would be at a standstill.

--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...> wrote:
>
>
> Make sure the resource GROUPS your resources are under have default In/Out Whse Bins defined. AMM has been working fine for us (re WIP moves) set up like this and, in counterpoint, Backflushing DID NOT work for us UNTIL we set up like this.
>
> It seems the processing logic looks at the resource group level 1st, and only looks further (at resource level) if the In/Out field aren't left blank at the resource group level. (I believe there is an SCR on this - at least for backflushing.)
>
> Also: Are you moving WIP OUT to a whse bin that differs from where the next OP's resource is defined to move the WIP IN from?
>
> ...Something to be said for KISS principles re the IN/OUT whse bins (define a single common WIP move whse bin for both IN/OUT use on all resources) UNLESS you are continuous processing and your OPs always follow a single sequence.
>
> Hope that helps.
>
> Rob
>
> --- On Mon, 4/20/09, markewhittaker <markewhittaker@...> wrote:
> From: markewhittaker <markewhittaker@...>
> Subject: [Vantage] Resource Error When Posting Labor Through MES with AMM
> To: vantage@yahoogroups.com
> Date: Monday, April 20, 2009, 6:22 PM
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> We recently purchased the AMM license and I am trying to use the material queue function to generate moves for WIP in the material queue as a job completes one operation and moves to the next. I set up the resources with input/output whse/bins. But when I start posting labor in MES and try to end an activity, on many operations it crashes and will not end the operation. A message pops up telling me to check the appserver log. The appserver log shows this: Procedure: 'ConsumeQty lib/pwipmtlq. p' Line:1037) ** No Resource record is available. (91). I have a call in to Epicor. At first the support person said that patch 407b fixes the problem (I am on 8.03.404a). Then when I described more detail, she said she would try to re-create the problem and get back to me. Experience tells me that when they say that, you won't hear from them for weeks.
>
>
>
> Anyone else run into this issue?
>

system · April 21, 2009, 10:24am

Another think I have noticed that may provide a clue. On the operations that will actually let me clock through and complete activity, when I go into the End Activity screen, the Request Move checkbox is checked by default. Any operations that are going to give me the error, that checkbox is not checked by default. And on those operations where the checkbox is not checked by default, no matter if I check it or not, I get the same error message. Help screen doesn't say anything about what would cause that flag to come up checked by default.

--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...> wrote:
>
>
> Make sure the resource GROUPS your resources are under have default In/Out Whse Bins defined. AMM has been working fine for us (re WIP moves) set up like this and, in counterpoint, Backflushing DID NOT work for us UNTIL we set up like this.
>
> It seems the processing logic looks at the resource group level 1st, and only looks further (at resource level) if the In/Out field aren't left blank at the resource group level. (I believe there is an SCR on this - at least for backflushing.)
>
> Also: Are you moving WIP OUT to a whse bin that differs from where the next OP's resource is defined to move the WIP IN from?
>
> ...Something to be said for KISS principles re the IN/OUT whse bins (define a single common WIP move whse bin for both IN/OUT use on all resources) UNLESS you are continuous processing and your OPs always follow a single sequence.
>
> Hope that helps.
>
> Rob
>
> --- On Mon, 4/20/09, markewhittaker <markewhittaker@...> wrote:
> From: markewhittaker <markewhittaker@...>
> Subject: [Vantage] Resource Error When Posting Labor Through MES with AMM
> To: vantage@yahoogroups.com
> Date: Monday, April 20, 2009, 6:22 PM
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> We recently purchased the AMM license and I am trying to use the material queue function to generate moves for WIP in the material queue as a job completes one operation and moves to the next. I set up the resources with input/output whse/bins. But when I start posting labor in MES and try to end an activity, on many operations it crashes and will not end the operation. A message pops up telling me to check the appserver log. The appserver log shows this: Procedure: 'ConsumeQty lib/pwipmtlq. p' Line:1037) ** No Resource record is available. (91). I have a call in to Epicor. At first the support person said that patch 407b fixes the problem (I am on 8.03.404a). Then when I described more detail, she said she would try to re-create the problem and get back to me. Experience tells me that when they say that, you won't hear from them for weeks.
>
>
>
> Anyone else run into this issue?
>

system · April 21, 2009, 10:32am

I have a customization that defaults that box to checked as well as the
fact that I have it hidden and no tab stop. We struggled a lot to get
this working at first then broke through it but im struggling to
remember what our break throughs were. You do want the check box = to
true however. You also always want your input and output bins to be
different. Also uncheck autmove.

Rob Bucek

Manufacturing Engineer

PH: 715-284-5376 ext 311

FAX: 715-284-4084

<http://www.dsmfg.com/>

(Click the logo to view our site)

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of markewhittaker
Sent: Tuesday, April 21, 2009 9:23 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Resource Error When Posting Labor Through MES
with AMM

Another think I have noticed that may provide a clue. On the operations
that will actually let me clock through and complete activity, when I go
into the End Activity screen, the Request Move checkbox is checked by
default. Any operations that are going to give me the error, that
checkbox is not checked by default. And on those operations where the
checkbox is not checked by default, no matter if I check it or not, I
get the same error message. Help screen doesn't say anything about what
would cause that flag to come up checked by default.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
Robert Brown <robertb_versa@...> wrote:

>
>
> Make sure the resource GROUPS your resources are under have default

In/Out Whse Bins defined. AMM has been working fine for us (re WIP
moves) set up like this and, in counterpoint, Backflushing DID NOT work
for us UNTIL we set up like this.

>
> It seems the processing logic looks at the resource group level 1st,

and only looks further (at resource level) if the In/Out field aren't
left blank at the resource group level. (I believe there is an SCR on
this - at least for backflushing.)

>
> Also: Are you moving WIP OUT to a whse bin that differs from where the

next OP's resource is defined to move the WIP IN from?

>
> ...Something to be said for KISS principles re the IN/OUT whse bins

(define a single common WIP move whse bin for both IN/OUT use on all
resources) UNLESS you are continuous processing and your OPs always
follow a single sequence.

>
> Hope that helps.
>
> Rob
>
> --- On Mon, 4/20/09, markewhittaker <markewhittaker@...> wrote:
> From: markewhittaker <markewhittaker@...>
> Subject: [Vantage] Resource Error When Posting Labor Through MES with

AMM

> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Date: Monday, April 20, 2009, 6:22 PM
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> We recently purchased the AMM license and I am trying to use the

material queue function to generate moves for WIP in the material queue
as a job completes one operation and moves to the next. I set up the
resources with input/output whse/bins. But when I start posting labor in
MES and try to end an activity, on many operations it crashes and will
not end the operation. A message pops up telling me to check the
appserver log. The appserver log shows this: Procedure: 'ConsumeQty
lib/pwipmtlq. p' Line:1037) ** No Resource record is available. (91). I
have a call in to Epicor. At first the support person said that patch
407b fixes the problem (I am on 8.03.404a). Then when I described more
detail, she said she would try to re-create the problem and get back to
me. Experience tells me that when they say that, you won't hear from
them for weeks.

>
>
>
> Anyone else run into this issue?
>

[Non-text portions of this message have been removed]

system · April 21, 2009, 11:29am

Scratch my last comment. I am getting the error when the Request Move checkbox
is already checked.

Why do your input and output bins need to be different within the resource
group? I thought that a move was generated if the output bin of the resource
group of one operation did not match the input bin of the resource group of the
next operation. Below is some text from the AMM Cource Student Handbook:

Operation 10 - CNC Input Whse/Bin Plant Floor/CNC
Output Whse/Bin Plant Floor/CNC
Operation 20 - ASMB Input Whse/Bin Plant Floor/ASMB
ASMB Output Whse/Bin Plant Floor/ASMB

In this example when parts are completed at operation 10, a move request will be placed in the move queue for the material to be moved from the CNC bin to the ASMB bin. If the user does not want a move request placed into the queue, but does want to see the wip material moved, the Auto Move checkbox can be enabled to accomplish this.

If the input bin of operation 20 is different from the output bin of operation 10, a move request will occur. If the input bin of operation 20 and the output bin of operation 10 are the same, a move request will not occur.

--- In vantage@yahoogroups.com, "Rob Bucek" <rbucek@...> wrote:
>
> I have a customization that defaults that box to checked as well as the
> fact that I have it hidden and no tab stop. We struggled a lot to get
> this working at first then broke through it but im struggling to
> remember what our break throughs were. You do want the check box = to
> true however. You also always want your input and output bins to be
> different. Also uncheck autmove.
>
>
>
> Rob Bucek
>
> Manufacturing Engineer
>
> PH: 715-284-5376 ext 311
>
> FAX: 715-284-4084
>
> <http://www.dsmfg.com/>
>
> (Click the logo to view our site)
>
>
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of markewhittaker
> Sent: Tuesday, April 21, 2009 9:23 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Resource Error When Posting Labor Through MES
> with AMM
>
>
>
>
>
> Another think I have noticed that may provide a clue. On the operations
> that will actually let me clock through and complete activity, when I go
> into the End Activity screen, the Request Move checkbox is checked by
> default. Any operations that are going to give me the error, that
> checkbox is not checked by default. And on those operations where the
> checkbox is not checked by default, no matter if I check it or not, I
> get the same error message. Help screen doesn't say anything about what
> would cause that flag to come up checked by default.
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> Robert Brown <robertb_versa@> wrote:
> >
> >
> > Make sure the resource GROUPS your resources are under have default
> In/Out Whse Bins defined. AMM has been working fine for us (re WIP
> moves) set up like this and, in counterpoint, Backflushing DID NOT work
> for us UNTIL we set up like this.
> >
> > It seems the processing logic looks at the resource group level 1st,
> and only looks further (at resource level) if the In/Out field aren't
> left blank at the resource group level. (I believe there is an SCR on
> this - at least for backflushing.)
> >
> > Also: Are you moving WIP OUT to a whse bin that differs from where the
> next OP's resource is defined to move the WIP IN from?
> >
> > ...Something to be said for KISS principles re the IN/OUT whse bins
> (define a single common WIP move whse bin for both IN/OUT use on all
> resources) UNLESS you are continuous processing and your OPs always
> follow a single sequence.
> >
> > Hope that helps.
> >
> > Rob
> >
> > --- On Mon, 4/20/09, markewhittaker <markewhittaker@> wrote:
> > From: markewhittaker <markewhittaker@>
> > Subject: [Vantage] Resource Error When Posting Labor Through MES with
> AMM
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > Date: Monday, April 20, 2009, 6:22 PM
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > We recently purchased the AMM license and I am trying to use the
> material queue function to generate moves for WIP in the material queue
> as a job completes one operation and moves to the next. I set up the
> resources with input/output whse/bins. But when I start posting labor in
> MES and try to end an activity, on many operations it crashes and will
> not end the operation. A message pops up telling me to check the
> appserver log. The appserver log shows this: Procedure: 'ConsumeQty
> lib/pwipmtlq. p' Line:1037) ** No Resource record is available. (91). I
> have a call in to Epicor. At first the support person said that patch
> 407b fixes the problem (I am on 8.03.404a). Then when I described more
> detail, she said she would try to re-create the problem and get back to
> me. Experience tells me that when they say that, you won't hear from
> them for weeks.
> >
> >
> >
> > Anyone else run into this issue?
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

system · April 21, 2009, 12:38pm

We have Automove defualt checked on all resource groups/resources & use the same whs/bin for both In/Out (within each department's resource groups/resources... Different deparments have different warehouses associated with them as well as correspponding bins.)

Works just fine using same whse/bin for both in/out & automove checked.

(On 405a) We also had to customize MES End Activity and Qty reporting to force the prod complete and op complete checkboxes to be true when the total reported qty (+ pior reproted qtys's complete) match the total qty due.

Also added a stop update loop to prevent overreporting.

These were vb.net customizations though and are subject to 'silent breakdown' (with no warning to user)... Eventualyy we'll get around to replacing with sturdier BPMs.

Rob (Brown).

--- On Tue, 4/21/09, Rob Bucek <rbucek@...> wrote:

From: Rob Bucek <rbucek@...>
Subject: RE: [Vantage] Re: Resource Error When Posting Labor Through MES with AMM
To: vantage@yahoogroups.com
Date: Tuesday, April 21, 2009, 10:30 AM

I have a customization that defaults that box to checked as well as the
fact that I have it hidden and no tab stop. We struggled a lot to get
this working at first then broke through it but im struggling to
remember what our break throughs were. You do want the check box = to
true however. You also always want your input and output bins to be
different. Also uncheck autmove.

Rob Bucek

Manufacturing Engineer

PH: 715-284-5376 ext 311

FAX: 715-284-4084

<http://www.dsmfg com/>

(Click the logo to view our site)

____________ _________ _________ __

From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On Behalf
Of markewhittaker
Sent: Tuesday, April 21, 2009 9:23 AM
To: vantage@yahoogroups .com
Subject: [Vantage] Re: Resource Error When Posting Labor Through MES
with AMM

Another think I have noticed that may provide a clue. On the operations
that will actually let me clock through and complete activity, when I go
into the End Activity screen, the Request Move checkbox is checked by
default. Any operations that are going to give me the error, that
checkbox is not checked by default. And on those operations where the
checkbox is not checked by default, no matter if I check it or not, I
get the same error message. Help screen doesn't say anything about what
would cause that flag to come up checked by default.

--- In vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com> ,
Robert Brown <robertb_versa@ ...> wrote:
>
>
> Make sure the resource GROUPS your resources are under have default
In/Out Whse Bins defined. AMM has been working fine for us (re WIP
moves) set up like this and, in counterpoint, Backflushing DID NOT work
for us UNTIL we set up like this.
>
> It seems the processing logic looks at the resource group level 1st,
and only looks further (at resource level) if the In/Out field aren't
left blank at the resource group level. (I believe there is an SCR on
this - at least for backflushing. )
>
> Also: Are you moving WIP OUT to a whse bin that differs from where the
next OP's resource is defined to move the WIP IN from?
>
> ...Something to be said for KISS principles re the IN/OUT whse bins
(define a single common WIP move whse bin for both IN/OUT use on all
resources) UNLESS you are continuous processing and your OPs always
follow a single sequence.
>
> Hope that helps.
>
> Rob
>
> --- On Mon, 4/20/09, markewhittaker <markewhittaker@ ...> wrote:
> From: markewhittaker <markewhittaker@ ...>
> Subject: [Vantage] Resource Error When Posting Labor Through MES with
AMM
> To: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
> Date: Monday, April 20, 2009, 6:22 PM
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> We recently purchased the AMM license and I am trying to use the
material queue function to generate moves for WIP in the material queue
as a job completes one operation and moves to the next. I set up the
resources with input/output whse/bins. But when I start posting labor in
MES and try to end an activity, on many operations it crashes and will
not end the operation. A message pops up telling me to check the
appserver log. The appserver log shows this: Procedure: 'ConsumeQty
lib/pwipmtlq. p' Line:1037) ** No Resource record is available. (91). I
have a call in to Epicor. At first the support person said that patch
407b fixes the problem (I am on 8.03.404a). Then when I described more
detail, she said she would try to re-create the problem and get back to
me. Experience tells me that when they say that, you won't hear from
them for weeks.
>
>
>
> Anyone else run into this issue?
>

[Non-text portions of this message have been removed]

system · April 21, 2009, 12:46pm

Sounds like you are in job shop environment (CNCs) and if your's is like us, it is rare for one reosurces output to ALWAYS feed anothers.

Because of the that, we use the same whse/bin for both In & Out.

If we were modelling some continuous process (say a textile process where raw fiber was always fed to drawing 1 & from drawing 1 to drawing 2, then from drawing 2 to spinning 1, then from spinning 1 to winding 1, then from winding 1 to dying/sizing 1 - ALWAYS the same) - then you might benefit (WIP tracking info) from having differing In versus Out bins. (Example above: drawing 1's out = drawing 2's in, drawings 2's, out = spinning 1's in, etc.,).

In a large layout plant, that might facilitate WIP movement via some real time dispatch used by material/WIP handlers.

Otherwise, a single whse/bin for all in/out is probably best.

Rob

--- On Tue, 4/21/09, markewhittaker <markewhittaker@...> wrote:

From: markewhittaker <markewhittaker@...>
Subject: [Vantage] Re: Resource Error When Posting Labor Through MES with AMM
To: vantage@yahoogroups.com
Date: Tuesday, April 21, 2009, 11:10 AM

Scratch my last comment. I am getting the error when the Request Move checkbox is already checked.

Why do your input and output bins need to be different within the resource group? I thought that a move was generated if the output bin of the resource group of one operation did not match the input bin of the resource group of the next operation. Below is some text from the AMM Cource Student Handbook:

Example of a move, using a job with the following operations:

Operation Number Name Input Warehouse Output Warehouse In Bin Out Bin
10 CNC Plant Floor CNC
Plant Floor CNC
20 ASMB Plant Floor ASMB
Plant Floor ASMB

In this example, when parts are reported completed at operation 10, a move request will be placed in
the move queue for the material to be moved from the CNC bin to the ASSY bin. If the user does not
want a move request placed into the queue, but does want to see the WIP material moved, the Auto
Move checkbox can be enabled to accomplish this.

--- In vantage@yahoogroups .com, "Rob Bucek" <rbucek@...> wrote:
>
> I have a customization that defaults that box to checked as well as the
> fact that I have it hidden and no tab stop. We struggled a lot to get
> this working at first then broke through it but im struggling to
> remember what our break throughs were. You do want the check box = to
> true however. You also always want your input and output bins to be
> different. Also uncheck autmove.
>
>
>
> Rob Bucek
>
> Manufacturing Engineer
>
> PH: 715-284-5376 ext 311
>
> FAX: 715-284-4084
>
> <http://www.dsmfg com/>
>
> (Click the logo to view our site)
>
>
>
> ____________ _________ _________ __
>
> From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On Behalf
> Of markewhittaker
> Sent: Tuesday, April 21, 2009 9:23 AM
> To: vantage@yahoogroups .com
> Subject: [Vantage] Re: Resource Error When Posting Labor Through MES
> with AMM
>
>
>
>
>
> Another think I have noticed that may provide a clue. On the operations
> that will actually let me clock through and complete activity, when I go
> into the End Activity screen, the Request Move checkbox is checked by
> default. Any operations that are going to give me the error, that
> checkbox is not checked by default. And on those operations where the
> checkbox is not checked by default, no matter if I check it or not, I
> get the same error message. Help screen doesn't say anything about what
> would cause that flag to come up checked by default.
>
> --- In vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com> ,
> Robert Brown <robertb_versa@ > wrote:
> >
> >
> > Make sure the resource GROUPS your resources are under have default
> In/Out Whse Bins defined. AMM has been working fine for us (re WIP
> moves) set up like this and, in counterpoint, Backflushing DID NOT work
> for us UNTIL we set up like this.
> >
> > It seems the processing logic looks at the resource group level 1st,
> and only looks further (at resource level) if the In/Out field aren't
> left blank at the resource group level. (I believe there is an SCR on
> this - at least for backflushing. )
> >
> > Also: Are you moving WIP OUT to a whse bin that differs from where the
> next OP's resource is defined to move the WIP IN from?
> >
> > ...Something to be said for KISS principles re the IN/OUT whse bins
> (define a single common WIP move whse bin for both IN/OUT use on all
> resources) UNLESS you are continuous processing and your OPs always
> follow a single sequence.
> >
> > Hope that helps.
> >
> > Rob
> >
> > --- On Mon, 4/20/09, markewhittaker <markewhittaker@ > wrote:
> > From: markewhittaker <markewhittaker@ >
> > Subject: [Vantage] Resource Error When Posting Labor Through MES with
> AMM
> > To: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
> > Date: Monday, April 20, 2009, 6:22 PM
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > We recently purchased the AMM license and I am trying to use the
> material queue function to generate moves for WIP in the material queue
> as a job completes one operation and moves to the next. I set up the
> resources with input/output whse/bins. But when I start posting labor in
> MES and try to end an activity, on many operations it crashes and will
> not end the operation. A message pops up telling me to check the
> appserver log. The appserver log shows this: Procedure: 'ConsumeQty
> lib/pwipmtlq. p' Line:1037) ** No Resource record is available. (91). I
> have a call in to Epicor. At first the support person said that patch
> 407b fixes the problem (I am on 8.03.404a). Then when I described more
> detail, she said she would try to re-create the problem and get back to
> me. Experience tells me that when they say that, you won't hear from
> them for weeks.
> >
> >
> >
> > Anyone else run into this issue?
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

system · April 21, 2009, 1:03pm

My apologies, its been a while since I configured all that. I do know
that's what worked for us, more than one configuration is possible im
sure. It does however make it readily apparent to the material handler
what is queue and what is move if you use a consistent naming scheme. I
do know we struggled with that automove check box marked true on the
resource group setup page. Once we forced condition on the request move
from end activity it all seemed to work consistently.

Rob Bucek

Manufacturing Engineer

PH: 715-284-5376 ext 311

FAX: 715-284-4084

<http://www.dsmfg.com/>

(Click the logo to view our site)

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of markewhittaker
Sent: Tuesday, April 21, 2009 10:29 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Resource Error When Posting Labor Through MES
with AMM

Scratch my last comment. I am getting the error when the Request Move
checkbox
is already checked.

Why do your input and output bins need to be different within the
resource
group? I thought that a move was generated if the output bin of the
resource
group of one operation did not match the input bin of the resource group
of the
next operation. Below is some text from the AMM Cource Student Handbook:

Operation 10 - CNC Input Whse/Bin Plant Floor/CNC
Output Whse/Bin Plant Floor/CNC
Operation 20 - ASMB Input Whse/Bin Plant Floor/ASMB
ASMB Output Whse/Bin Plant Floor/ASMB

In this example when parts are completed at operation 10, a move request
will be placed in the move queue for the material to be moved from the
CNC bin to the ASMB bin. If the user does not want a move request placed
into the queue, but does want to see the wip material moved, the Auto
Move checkbox can be enabled to accomplish this.

If the input bin of operation 20 is different from the output bin of
operation 10, a move request will occur. If the input bin of operation
20 and the output bin of operation 10 are the same, a move request will
not occur.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , "Rob
Bucek" <rbucek@...> wrote:

>
> I have a customization that defaults that box to checked as well as

the

> fact that I have it hidden and no tab stop. We struggled a lot to get
> this working at first then broke through it but im struggling to
> remember what our break throughs were. You do want the check box = to
> true however. You also always want your input and output bins to be
> different. Also uncheck autmove.
>
>
>
> Rob Bucek
>
> Manufacturing Engineer
>
> PH: 715-284-5376 ext 311
>
> FAX: 715-284-4084
>
> <http://www.dsmfg.com/ <http://www.dsmfg.com/> >
>
> (Click the logo to view our site)
>
>
>
> ________________________________
>
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf

> Of markewhittaker
> Sent: Tuesday, April 21, 2009 9:23 AM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Re: Resource Error When Posting Labor Through MES
> with AMM
>
>
>
>
>
> Another think I have noticed that may provide a clue. On the

operations

> that will actually let me clock through and complete activity, when I

go

> into the End Activity screen, the Request Move checkbox is checked by
> default. Any operations that are going to give me the error, that
> checkbox is not checked by default. And on those operations where the
> checkbox is not checked by default, no matter if I check it or not, I
> get the same error message. Help screen doesn't say anything about

what

> would cause that flag to come up checked by default.
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

<mailto:vantage%40yahoogroups.com> ,

> Robert Brown <robertb_versa@> wrote:
> >
> >
> > Make sure the resource GROUPS your resources are under have default
> In/Out Whse Bins defined. AMM has been working fine for us (re WIP
> moves) set up like this and, in counterpoint, Backflushing DID NOT

work

> for us UNTIL we set up like this.
> >
> > It seems the processing logic looks at the resource group level 1st,
> and only looks further (at resource level) if the In/Out field aren't
> left blank at the resource group level. (I believe there is an SCR on
> this - at least for backflushing.)
> >
> > Also: Are you moving WIP OUT to a whse bin that differs from where

the

> next OP's resource is defined to move the WIP IN from?
> >
> > ...Something to be said for KISS principles re the IN/OUT whse bins
> (define a single common WIP move whse bin for both IN/OUT use on all
> resources) UNLESS you are continuous processing and your OPs always
> follow a single sequence.
> >
> > Hope that helps.
> >
> > Rob
> >
> > --- On Mon, 4/20/09, markewhittaker <markewhittaker@> wrote:
> > From: markewhittaker <markewhittaker@>
> > Subject: [Vantage] Resource Error When Posting Labor Through MES

with

> AMM
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

<mailto:vantage%40yahoogroups.com>

> > Date: Monday, April 20, 2009, 6:22 PM
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > We recently purchased the AMM license and I am trying to use the
> material queue function to generate moves for WIP in the material

queue

> as a job completes one operation and moves to the next. I set up the
> resources with input/output whse/bins. But when I start posting labor

in

> MES and try to end an activity, on many operations it crashes and will
> not end the operation. A message pops up telling me to check the
> appserver log. The appserver log shows this: Procedure: 'ConsumeQty
> lib/pwipmtlq. p' Line:1037) ** No Resource record is available. (91).

I

> have a call in to Epicor. At first the support person said that patch
> 407b fixes the problem (I am on 8.03.404a). Then when I described more
> detail, she said she would try to re-create the problem and get back

to

> me. Experience tells me that when they say that, you won't hear from
> them for weeks.
> >
> >
> >
> > Anyone else run into this issue?
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

[Non-text portions of this message have been removed]

system · April 21, 2009, 1:16pm

Robert Brown, what patch level are you running?

--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...> wrote:
>
>
> We have Automove defualt checked on all resource groups/resources & use the same whs/bin for both In/Out (within each department's resource groups/resources... Different deparments have different warehouses associated with them as well as correspponding bins.)
>
> Works just fine using same whse/bin for both in/out & automove checked.
>
> (On 405a) We also had to customize MES End Activity and Qty reporting to force the prod complete and op complete checkboxes to be true when the total reported qty (+ pior reproted qtys's complete) match the total qty due.
>
> Also added a stop update loop to prevent overreporting.
>
> These were vb.net customizations though and are subject to 'silent breakdown' (with no warning to user)... Eventualyy we'll get around to replacing with sturdier BPMs.
>
> Rob (Brown).
>
> --- On Tue, 4/21/09, Rob Bucek <rbucek@...> wrote:
>
> From: Rob Bucek <rbucek@...>
> Subject: RE: [Vantage] Re: Resource Error When Posting Labor Through MES with AMM
> To: vantage@yahoogroups.com
> Date: Tuesday, April 21, 2009, 10:30 AM
>
>
>
>
>
>
>
>
> I have a customization that defaults that box to checked as well as the
> fact that I have it hidden and no tab stop. We struggled a lot to get
> this working at first then broke through it but im struggling to
> remember what our break throughs were. You do want the check box = to
> true however. You also always want your input and output bins to be
> different. Also uncheck autmove.
>
> Rob Bucek
>
> Manufacturing Engineer
>
> PH: 715-284-5376 ext 311
>
> FAX: 715-284-4084
>
> <http://www.dsmfg com/>
>
> (Click the logo to view our site)
>
> ____________ _________ _________ __
>
> From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On Behalf
> Of markewhittaker
> Sent: Tuesday, April 21, 2009 9:23 AM
> To: vantage@yahoogroups .com
> Subject: [Vantage] Re: Resource Error When Posting Labor Through MES
> with AMM
>
> Another think I have noticed that may provide a clue. On the operations
> that will actually let me clock through and complete activity, when I go
> into the End Activity screen, the Request Move checkbox is checked by
> default. Any operations that are going to give me the error, that
> checkbox is not checked by default. And on those operations where the
> checkbox is not checked by default, no matter if I check it or not, I
> get the same error message. Help screen doesn't say anything about what
> would cause that flag to come up checked by default.
>
> --- In vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com> ,
> Robert Brown <robertb_versa@ ...> wrote:
> >
> >
> > Make sure the resource GROUPS your resources are under have default
> In/Out Whse Bins defined. AMM has been working fine for us (re WIP
> moves) set up like this and, in counterpoint, Backflushing DID NOT work
> for us UNTIL we set up like this.
> >
> > It seems the processing logic looks at the resource group level 1st,
> and only looks further (at resource level) if the In/Out field aren't
> left blank at the resource group level. (I believe there is an SCR on
> this - at least for backflushing. )
> >
> > Also: Are you moving WIP OUT to a whse bin that differs from where the
> next OP's resource is defined to move the WIP IN from?
> >
> > ...Something to be said for KISS principles re the IN/OUT whse bins
> (define a single common WIP move whse bin for both IN/OUT use on all
> resources) UNLESS you are continuous processing and your OPs always
> follow a single sequence.
> >
> > Hope that helps.
> >
> > Rob
> >
> > --- On Mon, 4/20/09, markewhittaker <markewhittaker@ ...> wrote:
> > From: markewhittaker <markewhittaker@ ...>
> > Subject: [Vantage] Resource Error When Posting Labor Through MES with
> AMM
> > To: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
> > Date: Monday, April 20, 2009, 6:22 PM
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > We recently purchased the AMM license and I am trying to use the
> material queue function to generate moves for WIP in the material queue
> as a job completes one operation and moves to the next. I set up the
> resources with input/output whse/bins. But when I start posting labor in
> MES and try to end an activity, on many operations it crashes and will
> not end the operation. A message pops up telling me to check the
> appserver log. The appserver log shows this: Procedure: 'ConsumeQty
> lib/pwipmtlq. p' Line:1037) ** No Resource record is available. (91). I
> have a call in to Epicor. At first the support person said that patch
> 407b fixes the problem (I am on 8.03.404a). Then when I described more
> detail, she said she would try to re-create the problem and get back to
> me. Experience tells me that when they say that, you won't hear from
> them for weeks.
> >
> >
> >
> > Anyone else run into this issue?
> >
>
> [Non-text portions of this message have been removed]
>

system · April 21, 2009, 2:23pm

405a - but this also worked fine on 404.

--- On Tue, 4/21/09, markewhittaker <markewhittaker@...> wrote:

From: markewhittaker <markewhittaker@...>
Subject: [Vantage] Re: Resource Error When Posting Labor Through MES with AMM
To: vantage@yahoogroups.com
Date: Tuesday, April 21, 2009, 12:46 PM

Robert Brown, what patch level are you running?

--- In vantage@yahoogroups .com, Robert Brown <robertb_versa@ ...> wrote:
>
>
> We have Automove defualt checked on all resource groups/resources & use the same whs/bin for both In/Out (within each department's resource groups/resources. .. Different deparments have different warehouses associated with them as well as correspponding bins.)
>
> Works just fine using same whse/bin for both in/out & automove checked.
>
> (On 405a) We also had to customize MES End Activity and Qty reporting to force the prod complete and op complete checkboxes to be true when the total reported qty (+ pior reproted qtys's complete) match the total qty due.
>
> Also added a stop update loop to prevent overreporting.
>
> These were vb.net customizations though and are subject to 'silent breakdown' (with no warning to user)... Eventualyy we'll get around to replacing with sturdier BPMs.
>
> Rob (Brown).
>
> --- On Tue, 4/21/09, Rob Bucek <rbucek@...> wrote:
>
> From: Rob Bucek <rbucek@...>
> Subject: RE: [Vantage] Re: Resource Error When Posting Labor Through MES with AMM
> To: vantage@yahoogroups .com
> Date: Tuesday, April 21, 2009, 10:30 AM
>
>
>
>
>
>
>
>
> I have a customization that defaults that box to checked as well as the
> fact that I have it hidden and no tab stop. We struggled a lot to get
> this working at first then broke through it but im struggling to
> remember what our break throughs were. You do want the check box = to
> true however. You also always want your input and output bins to be
> different. Also uncheck autmove.
>
> Rob Bucek
>
> Manufacturing Engineer
>
> PH: 715-284-5376 ext 311
>
> FAX: 715-284-4084
>
> <http://www.dsmfg com/>
>
> (Click the logo to view our site)
>
> ____________ _________ _________ __
>
> From: vantage@yahoogroups .com [mailto:vantage@ yahoogroups .com] On Behalf
> Of markewhittaker
> Sent: Tuesday, April 21, 2009 9:23 AM
> To: vantage@yahoogroups .com
> Subject: [Vantage] Re: Resource Error When Posting Labor Through MES
> with AMM
>
> Another think I have noticed that may provide a clue. On the operations
> that will actually let me clock through and complete activity, when I go
> into the End Activity screen, the Request Move checkbox is checked by
> default. Any operations that are going to give me the error, that
> checkbox is not checked by default. And on those operations where the
> checkbox is not checked by default, no matter if I check it or not, I
> get the same error message. Help screen doesn't say anything about what
> would cause that flag to come up checked by default.
>
> --- In vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com> ,
> Robert Brown <robertb_versa@ ...> wrote:
> >
> >
> > Make sure the resource GROUPS your resources are under have default
> In/Out Whse Bins defined. AMM has been working fine for us (re WIP
> moves) set up like this and, in counterpoint, Backflushing DID NOT work
> for us UNTIL we set up like this.
> >
> > It seems the processing logic looks at the resource group level 1st,
> and only looks further (at resource level) if the In/Out field aren't
> left blank at the resource group level. (I believe there is an SCR on
> this - at least for backflushing. )
> >
> > Also: Are you moving WIP OUT to a whse bin that differs from where the
> next OP's resource is defined to move the WIP IN from?
> >
> > ...Something to be said for KISS principles re the IN/OUT whse bins
> (define a single common WIP move whse bin for both IN/OUT use on all
> resources) UNLESS you are continuous processing and your OPs always
> follow a single sequence.
> >
> > Hope that helps.
> >
> > Rob
> >
> > --- On Mon, 4/20/09, markewhittaker <markewhittaker@ ...> wrote:
> > From: markewhittaker <markewhittaker@ ...>
> > Subject: [Vantage] Resource Error When Posting Labor Through MES with
> AMM
> > To: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
> > Date: Monday, April 20, 2009, 6:22 PM
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > We recently purchased the AMM license and I am trying to use the
> material queue function to generate moves for WIP in the material queue
> as a job completes one operation and moves to the next. I set up the
> resources with input/output whse/bins. But when I start posting labor in
> MES and try to end an activity, on many operations it crashes and will
> not end the operation. A message pops up telling me to check the
> appserver log. The appserver log shows this: Procedure: 'ConsumeQty
> lib/pwipmtlq. p' Line:1037) ** No Resource record is available. (91). I
> have a call in to Epicor. At first the support person said that patch
> 407b fixes the problem (I am on 8.03.404a). Then when I described more
> detail, she said she would try to re-create the problem and get back to
> me. Experience tells me that when they say that, you won't hear from
> them for weeks.
> >
> >
> >
> > Anyone else run into this issue?
> >
>
> [Non-text portions of this message have been removed]
>