Orders not closing

We're having a heatwave in UK at the moment and we're not used to it ;)

If you want a copy of the BPM let me know :)

--- In vantage@yahoogroups.com, "Joshua Serwe" <jserwe@...> wrote:
>
> LOL, do you have your laptop out on the beach?
>
>
>
> I think having it right in front of them as they are working will help. I
> will see what we can do about getting a reminder for them as well. I think
> most of the problem was that it was out of sight since most of them are
> being packed out on the HH, and then entering the packaging, and shipping
> on the desktop. Hopefully we can get this fixed so we can do everything on
> the HH soon.
>
>
>
> Josh Serwe
>
> Manager of Warehouse & Logistics
>
> 920.437.6400 Ext. 330
>
>
>
> Safety
>
> Professionalism
>
> Effectiveness
>
> Easy
>
> Demand Results
>
> _____
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of tracy.tmat
> Sent: Wednesday, May 23, 2012 2:31 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Orders not closing
>
>
>
>
>
> We had a problem with orders not closing too (we're on Vantage 8.03.409a).
> After some monitoring we discovered it was where we had more than one pack
> slip open for the same release and where amendments to the pack slip were
> being made.
>
> We never had a problem if the changes were reductions as the user knew to
> untick the Ship Complete flag but they had no idea if they increased that
> they needed to tick it as the system only seemed to advise by calculating
> Shipped quantities and not pending.
>
> We resolved it by writing a BPM that queries all shipments per release and
> if they add up to the order value then a message appears avising the user
> to tick the box. We've been doing this for about 4 months now and so far
> don't have any problems reported.
>
> Hope this makes sense as it's been a long hot day here and am sunfried!
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "Joshua Serwe" <jserwe@> wrote:
> >
> > Ok, I have done some personalization to our customer shipment entry
> screen
> > so it can easily be checked from the summary page. I guess we will just
> > have to close them all manually.
> >
> >
> >
> > Josh Serwe
> >
> > Manager of Warehouse & Logistics
> >
> > 920.437.6400 Ext. 330
> >
> >
> >
> > Safety
> >
> > Professionalism
> >
> > Effectiveness
> >
> > Easy
> >
> > Demand Results
> >
> > _____
> >
> > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
> Behalf
> > Of leannah
> > Sent: Wednesday, May 23, 2012 2:12 PM
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] Re: Orders not closing
> >
> >
> >
> >
> >
> > I don't go around the business logic direct to the database unless it is
> > an "extreme" circumstance - read that as unable to do it ANY other way.
> > You could probably do an updateable dashboard that only picks up order
> > lines that should be closed and set it to closed from there. That the
> best
> > I could do.
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com> ,
> > "joshserwe" <jserwe@> wrote:
> > >
> > > LOL,I really LOVE manually closing them too. I feel it is the best use
> > of my time.
> > >
> > > We created a dashboard that shows all orders with shipped quantities
> to
> > see if I could come up with some type of similarities for the orders
> that
> > are not closing properly, and that didn't help me come up with a rhyme
> or
> > reason that I could find.
> > >
> > > Is it possible to add anything on to the query to close the orders
> that
> > it finds so they don't have to be closed manually?
> > >
> > > Thanks for your help!
> > >
> > > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com> ,
> > "leannah" <dave.leannah@> wrote:
> > > >
> > > > We have exactly the same problem. I have narrowed it down to packing
> > the full quantity, then unpack a line or a quantity and it never checks
> > for closed orders again. It unchecks the ship complete. I think there
> are
> > more cases where it does it but have not had a chance to get it all
> > tested.
> > > >
> > > > Here is a query I wrote to identify open orders that should have
> been
> > closed:
> > > >
> > > > SELECT shipdtl.ordernum, shipdtl.orderline, shipdtl.jobnum,
> > shipdtl.packnum, shipdtl.ourjobshipqty, shipdtl.ourinventoryshipqty
> > > > --orderdtl.openline ,shiphead.shipdate, shipdtl.*
> > > > FROM (Epicor905.dbo.ShipDtl ShipDtl
> > > > INNER JOIN OrderDtl with (nolock)
> > > > ON (ShipDtl.company = OrderDtl.company)
> > > > AND (ShipDtl.ordernum = OrderDtl.ordernum)
> > > > AND (ShipDtl.orderline = OrderDtl.orderline))
> > > > INNER JOIN ShipHead with (nolock)
> > > > ON (ShipDtl.company = ShipHead.company)
> > > > AND (ShipDtl.packnum = ShipHead.packnum)
> > > > WHERE shipdtl.shipcmpl = 0 and shiphead.invoiced = 1 and openline =
> 1
> > and orderdtl.orderqty = (shipdtl.ourinventoryshipqty +
> > shipdtl.ourjobshipqty)
> > > > ORDER BY shipdtl.ordernum DESC
> > > >
> > > > They can close them manually - which they LOVE doing.
> > > >
> > > > You will also find that the ship date is filled in improperly as
> well.
> > In V8 it filled in on invoicing, now shipping randomly fills it in. Not
> a
> > problem unless your manifesting system uses that date for freighting -
> > then you get really odd results in closing shipment days.
> > > >
> > > >
> > > >
> > > > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com> ,
> > "joshserwe" <jserwe@> wrote:
> > > > >
> > > > > We are in Epicor 9.05.607a, and have random orders not closing
> > automatically upon shipment. Has anyone else experienced this issue?
> Does
> > something on the shipment cause it to not mark the "shipped complete"
> > check box checked even though it is for the entire quantity of the
> > release?
> > > > > Thank you in advance for your help!
> > > > > Josh
> > > > >
> > > >
> > >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
We are in Epicor 9.05.607a, and have random orders not closing automatically upon shipment. Has anyone else experienced this issue? Does something on the shipment cause it to not mark the "shipped complete" check box checked even though it is for the entire quantity of the release?
Thank you in advance for your help!
Josh
Sometimes we run into that if there are more than one packing slips for that line item and quantity. Typically if they didn't realize they already had a packing slip for that order & started/opened a new packing slip (might not have actually checked the shipped button).
Â
That's where I look first.


________________________________
From: joshserwe <jserwe@...>
To: vantage@yahoogroups.com
Sent: Tuesday, May 22, 2012 4:25 PM
Subject: [Vantage] Orders not closing


Â
We are in Epicor 9.05.607a, and have random orders not closing automatically upon shipment. Has anyone else experienced this issue? Does something on the shipment cause it to not mark the "shipped complete" check box checked even though it is for the entire quantity of the release?
Thank you in advance for your help!
Josh




[Non-text portions of this message have been removed]
I did notice that some of them were because we had to back order it on the
first shipment but not all of them. We have quite a few orders that
haven't closed though, and we don't have any open packs sitting out there.
Thank you for the suggestion.



Josh Serwe

Manager of Warehouse & Logistics

920.437.6400 Ext. 330



Safety

Professionalism

Effectiveness

Easy

Demand Results





<http://www.wisconsinconverting.com>







[Non-text portions of this message have been removed]
In your test environment, after you bring in the shipment line and it defaults to complete, try changing the quantity below the requested amount so the complete flag on the line unchecks. Then change the quantity to the required amount again and see if the ship complete flag rechecks itself. We had seen some issues with this, although it was intermittent. It could be the quantity changed and the flag did not reset so the order line did not close



________________________________
From: Joshua Serwe <jserwe@...>
To: vantage@yahoogroups.com
Sent: Wednesday, May 23, 2012 8:18 AM
Subject: Re: [Vantage] Orders not closing


Â
I did notice that some of them were because we had to back order it on the
first shipment but not all of them. We have quite a few orders that
haven't closed though, and we don't have any open packs sitting out there.
Thank you for the suggestion.

Josh Serwe

Manager of Warehouse & Logistics

920.437.6400 Ext. 330

Safety

Professionalism

Effectiveness

Easy

Demand Results

<http://www.wisconsinconverting.com>

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




[Non-text portions of this message have been removed]
We have exactly the same problem. I have narrowed it down to packing the full quantity, then unpack a line or a quantity and it never checks for closed orders again. It unchecks the ship complete. I think there are more cases where it does it but have not had a chance to get it all tested.

Here is a query I wrote to identify open orders that should have been closed:

SELECT shipdtl.ordernum, shipdtl.orderline, shipdtl.jobnum, shipdtl.packnum, shipdtl.ourjobshipqty, shipdtl.ourinventoryshipqty
--orderdtl.openline ,shiphead.shipdate, shipdtl.*
FROM (Epicor905.dbo.ShipDtl ShipDtl
INNER JOIN OrderDtl with (nolock)
ON (ShipDtl.company = OrderDtl.company)
AND (ShipDtl.ordernum = OrderDtl.ordernum)
AND (ShipDtl.orderline = OrderDtl.orderline))
INNER JOIN ShipHead with (nolock)
ON (ShipDtl.company = ShipHead.company)
AND (ShipDtl.packnum = ShipHead.packnum)
WHERE shipdtl.shipcmpl = 0 and shiphead.invoiced = 1 and openline = 1 and orderdtl.orderqty = (shipdtl.ourinventoryshipqty + shipdtl.ourjobshipqty)
ORDER BY shipdtl.ordernum DESC

They can close them manually - which they LOVE doing.

You will also find that the ship date is filled in improperly as well. In V8 it filled in on invoicing, now shipping randomly fills it in. Not a problem unless your manifesting system uses that date for freighting - then you get really odd results in closing shipment days.



--- In vantage@yahoogroups.com, "joshserwe" <jserwe@...> wrote:
>
> We are in Epicor 9.05.607a, and have random orders not closing automatically upon shipment. Has anyone else experienced this issue? Does something on the shipment cause it to not mark the "shipped complete" check box checked even though it is for the entire quantity of the release?
> Thank you in advance for your help!
> Josh
>
LOL,I really LOVE manually closing them too. I feel it is the best use of my time.

We created a dashboard that shows all orders with shipped quantities to see if I could come up with some type of similarities for the orders that are not closing properly, and that didn't help me come up with a rhyme or reason that I could find.

Is it possible to add anything on to the query to close the orders that it finds so they don't have to be closed manually?

Thanks for your help!

--- In vantage@yahoogroups.com, "leannah" <dave.leannah@...> wrote:
>
> We have exactly the same problem. I have narrowed it down to packing the full quantity, then unpack a line or a quantity and it never checks for closed orders again. It unchecks the ship complete. I think there are more cases where it does it but have not had a chance to get it all tested.
>
> Here is a query I wrote to identify open orders that should have been closed:
>
> SELECT shipdtl.ordernum, shipdtl.orderline, shipdtl.jobnum, shipdtl.packnum, shipdtl.ourjobshipqty, shipdtl.ourinventoryshipqty
> --orderdtl.openline ,shiphead.shipdate, shipdtl.*
> FROM (Epicor905.dbo.ShipDtl ShipDtl
> INNER JOIN OrderDtl with (nolock)
> ON (ShipDtl.company = OrderDtl.company)
> AND (ShipDtl.ordernum = OrderDtl.ordernum)
> AND (ShipDtl.orderline = OrderDtl.orderline))
> INNER JOIN ShipHead with (nolock)
> ON (ShipDtl.company = ShipHead.company)
> AND (ShipDtl.packnum = ShipHead.packnum)
> WHERE shipdtl.shipcmpl = 0 and shiphead.invoiced = 1 and openline = 1 and orderdtl.orderqty = (shipdtl.ourinventoryshipqty + shipdtl.ourjobshipqty)
> ORDER BY shipdtl.ordernum DESC
>
> They can close them manually - which they LOVE doing.
>
> You will also find that the ship date is filled in improperly as well. In V8 it filled in on invoicing, now shipping randomly fills it in. Not a problem unless your manifesting system uses that date for freighting - then you get really odd results in closing shipment days.
>
>
>
> --- In vantage@yahoogroups.com, "joshserwe" <jserwe@> wrote:
> >
> > We are in Epicor 9.05.607a, and have random orders not closing automatically upon shipment. Has anyone else experienced this issue? Does something on the shipment cause it to not mark the "shipped complete" check box checked even though it is for the entire quantity of the release?
> > Thank you in advance for your help!
> > Josh
> >
>
I haven't tested our Vantage bugs in Epicor 9 yet...but thought I'd mention that there are a number of bugs in the order shipment process in Vantage. One of them happens when you ship a complete order and then change or remove some ship quantities; it has trouble knowing when the shipment is really complete. I don't think all the quantities shipped are getting updated correctly which causes problems with the shipment (and order) getting marked shipped complete. You might want to try looking in the customer matrix viewer on EpicWeb. If you do a search on something like "shipping" you may find some problem spots to check; it may also give you an indication if they've been fixed in 9.05.700.
Sue

--- In vantage@yahoogroups.com, "Joshua Serwe" <jserwe@...> wrote:
>
> I did notice that some of them were because we had to back order it on the
> first shipment but not all of them. We have quite a few orders that
> haven't closed though, and we don't have any open packs sitting out there.
> Thank you for the suggestion.
>
>
>
> Josh Serwe
>
> Manager of Warehouse & Logistics
>
> 920.437.6400 Ext. 330
>
>
>
> Safety
>
> Professionalism
>
> Effectiveness
>
> Easy
>
> Demand Results
>
>
>
>
>
> <http://www.wisconsinconverting.com>
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
I don't go around the business logic direct to the database unless it is an "extreme" circumstance - read that as unable to do it ANY other way. You could probably do an updateable dashboard that only picks up order lines that should be closed and set it to closed from there. That the best I could do.

--- In vantage@yahoogroups.com, "joshserwe" <jserwe@...> wrote:
>
> LOL,I really LOVE manually closing them too. I feel it is the best use of my time.
>
> We created a dashboard that shows all orders with shipped quantities to see if I could come up with some type of similarities for the orders that are not closing properly, and that didn't help me come up with a rhyme or reason that I could find.
>
> Is it possible to add anything on to the query to close the orders that it finds so they don't have to be closed manually?
>
> Thanks for your help!
>
> --- In vantage@yahoogroups.com, "leannah" <dave.leannah@> wrote:
> >
> > We have exactly the same problem. I have narrowed it down to packing the full quantity, then unpack a line or a quantity and it never checks for closed orders again. It unchecks the ship complete. I think there are more cases where it does it but have not had a chance to get it all tested.
> >
> > Here is a query I wrote to identify open orders that should have been closed:
> >
> > SELECT shipdtl.ordernum, shipdtl.orderline, shipdtl.jobnum, shipdtl.packnum, shipdtl.ourjobshipqty, shipdtl.ourinventoryshipqty
> > --orderdtl.openline ,shiphead.shipdate, shipdtl.*
> > FROM (Epicor905.dbo.ShipDtl ShipDtl
> > INNER JOIN OrderDtl with (nolock)
> > ON (ShipDtl.company = OrderDtl.company)
> > AND (ShipDtl.ordernum = OrderDtl.ordernum)
> > AND (ShipDtl.orderline = OrderDtl.orderline))
> > INNER JOIN ShipHead with (nolock)
> > ON (ShipDtl.company = ShipHead.company)
> > AND (ShipDtl.packnum = ShipHead.packnum)
> > WHERE shipdtl.shipcmpl = 0 and shiphead.invoiced = 1 and openline = 1 and orderdtl.orderqty = (shipdtl.ourinventoryshipqty + shipdtl.ourjobshipqty)
> > ORDER BY shipdtl.ordernum DESC
> >
> > They can close them manually - which they LOVE doing.
> >
> > You will also find that the ship date is filled in improperly as well. In V8 it filled in on invoicing, now shipping randomly fills it in. Not a problem unless your manifesting system uses that date for freighting - then you get really odd results in closing shipment days.
> >
> >
> >
> > --- In vantage@yahoogroups.com, "joshserwe" <jserwe@> wrote:
> > >
> > > We are in Epicor 9.05.607a, and have random orders not closing automatically upon shipment. Has anyone else experienced this issue? Does something on the shipment cause it to not mark the "shipped complete" check box checked even though it is for the entire quantity of the release?
> > > Thank you in advance for your help!
> > > Josh
> > >
> >
>
Ok, I have done some personalization to our customer shipment entry screen
so it can easily be checked from the summary page. I guess we will just
have to close them all manually.



Josh Serwe

Manager of Warehouse & Logistics

920.437.6400 Ext. 330



Safety

Professionalism

Effectiveness

Easy

Demand Results

_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of leannah
Sent: Wednesday, May 23, 2012 2:12 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Orders not closing





I don't go around the business logic direct to the database unless it is
an "extreme" circumstance - read that as unable to do it ANY other way.
You could probably do an updateable dashboard that only picks up order
lines that should be closed and set it to closed from there. That the best
I could do.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"joshserwe" <jserwe@...> wrote:
>
> LOL,I really LOVE manually closing them too. I feel it is the best use
of my time.
>
> We created a dashboard that shows all orders with shipped quantities to
see if I could come up with some type of similarities for the orders that
are not closing properly, and that didn't help me come up with a rhyme or
reason that I could find.
>
> Is it possible to add anything on to the query to close the orders that
it finds so they don't have to be closed manually?
>
> Thanks for your help!
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"leannah" <dave.leannah@> wrote:
> >
> > We have exactly the same problem. I have narrowed it down to packing
the full quantity, then unpack a line or a quantity and it never checks
for closed orders again. It unchecks the ship complete. I think there are
more cases where it does it but have not had a chance to get it all
tested.
> >
> > Here is a query I wrote to identify open orders that should have been
closed:
> >
> > SELECT shipdtl.ordernum, shipdtl.orderline, shipdtl.jobnum,
shipdtl.packnum, shipdtl.ourjobshipqty, shipdtl.ourinventoryshipqty
> > --orderdtl.openline ,shiphead.shipdate, shipdtl.*
> > FROM (Epicor905.dbo.ShipDtl ShipDtl
> > INNER JOIN OrderDtl with (nolock)
> > ON (ShipDtl.company = OrderDtl.company)
> > AND (ShipDtl.ordernum = OrderDtl.ordernum)
> > AND (ShipDtl.orderline = OrderDtl.orderline))
> > INNER JOIN ShipHead with (nolock)
> > ON (ShipDtl.company = ShipHead.company)
> > AND (ShipDtl.packnum = ShipHead.packnum)
> > WHERE shipdtl.shipcmpl = 0 and shiphead.invoiced = 1 and openline = 1
and orderdtl.orderqty = (shipdtl.ourinventoryshipqty +
shipdtl.ourjobshipqty)
> > ORDER BY shipdtl.ordernum DESC
> >
> > They can close them manually - which they LOVE doing.
> >
> > You will also find that the ship date is filled in improperly as well.
In V8 it filled in on invoicing, now shipping randomly fills it in. Not a
problem unless your manifesting system uses that date for freighting -
then you get really odd results in closing shipment days.
> >
> >
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"joshserwe" <jserwe@> wrote:
> > >
> > > We are in Epicor 9.05.607a, and have random orders not closing
automatically upon shipment. Has anyone else experienced this issue? Does
something on the shipment cause it to not mark the "shipped complete"
check box checked even though it is for the entire quantity of the
release?
> > > Thank you in advance for your help!
> > > Josh
> > >
> >
>





[Non-text portions of this message have been removed]
We had a problem with orders not closing too (we're on Vantage 8.03.409a). After some monitoring we discovered it was where we had more than one pack slip open for the same release and where amendments to the pack slip were being made.

We never had a problem if the changes were reductions as the user knew to untick the Ship Complete flag but they had no idea if they increased that they needed to tick it as the system only seemed to advise by calculating Shipped quantities and not pending.

We resolved it by writing a BPM that queries all shipments per release and if they add up to the order value then a message appears avising the user to tick the box. We've been doing this for about 4 months now and so far don't have any problems reported.

Hope this makes sense as it's been a long hot day here and am sunfried!

--- In vantage@yahoogroups.com, "Joshua Serwe" <jserwe@...> wrote:
>
> Ok, I have done some personalization to our customer shipment entry screen
> so it can easily be checked from the summary page. I guess we will just
> have to close them all manually.
>
>
>
> Josh Serwe
>
> Manager of Warehouse & Logistics
>
> 920.437.6400 Ext. 330
>
>
>
> Safety
>
> Professionalism
>
> Effectiveness
>
> Easy
>
> Demand Results
>
> _____
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of leannah
> Sent: Wednesday, May 23, 2012 2:12 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Orders not closing
>
>
>
>
>
> I don't go around the business logic direct to the database unless it is
> an "extreme" circumstance - read that as unable to do it ANY other way.
> You could probably do an updateable dashboard that only picks up order
> lines that should be closed and set it to closed from there. That the best
> I could do.
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "joshserwe" <jserwe@> wrote:
> >
> > LOL,I really LOVE manually closing them too. I feel it is the best use
> of my time.
> >
> > We created a dashboard that shows all orders with shipped quantities to
> see if I could come up with some type of similarities for the orders that
> are not closing properly, and that didn't help me come up with a rhyme or
> reason that I could find.
> >
> > Is it possible to add anything on to the query to close the orders that
> it finds so they don't have to be closed manually?
> >
> > Thanks for your help!
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "leannah" <dave.leannah@> wrote:
> > >
> > > We have exactly the same problem. I have narrowed it down to packing
> the full quantity, then unpack a line or a quantity and it never checks
> for closed orders again. It unchecks the ship complete. I think there are
> more cases where it does it but have not had a chance to get it all
> tested.
> > >
> > > Here is a query I wrote to identify open orders that should have been
> closed:
> > >
> > > SELECT shipdtl.ordernum, shipdtl.orderline, shipdtl.jobnum,
> shipdtl.packnum, shipdtl.ourjobshipqty, shipdtl.ourinventoryshipqty
> > > --orderdtl.openline ,shiphead.shipdate, shipdtl.*
> > > FROM (Epicor905.dbo.ShipDtl ShipDtl
> > > INNER JOIN OrderDtl with (nolock)
> > > ON (ShipDtl.company = OrderDtl.company)
> > > AND (ShipDtl.ordernum = OrderDtl.ordernum)
> > > AND (ShipDtl.orderline = OrderDtl.orderline))
> > > INNER JOIN ShipHead with (nolock)
> > > ON (ShipDtl.company = ShipHead.company)
> > > AND (ShipDtl.packnum = ShipHead.packnum)
> > > WHERE shipdtl.shipcmpl = 0 and shiphead.invoiced = 1 and openline = 1
> and orderdtl.orderqty = (shipdtl.ourinventoryshipqty +
> shipdtl.ourjobshipqty)
> > > ORDER BY shipdtl.ordernum DESC
> > >
> > > They can close them manually - which they LOVE doing.
> > >
> > > You will also find that the ship date is filled in improperly as well.
> In V8 it filled in on invoicing, now shipping randomly fills it in. Not a
> problem unless your manifesting system uses that date for freighting -
> then you get really odd results in closing shipment days.
> > >
> > >
> > >
> > > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "joshserwe" <jserwe@> wrote:
> > > >
> > > > We are in Epicor 9.05.607a, and have random orders not closing
> automatically upon shipment. Has anyone else experienced this issue? Does
> something on the shipment cause it to not mark the "shipped complete"
> check box checked even though it is for the entire quantity of the
> release?
> > > > Thank you in advance for your help!
> > > > Josh
> > > >
> > >
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
LOL, do you have your laptop out on the beach?



I think having it right in front of them as they are working will help. I
will see what we can do about getting a reminder for them as well. I think
most of the problem was that it was out of sight since most of them are
being packed out on the HH, and then entering the packaging, and shipping
on the desktop. Hopefully we can get this fixed so we can do everything on
the HH soon.



Josh Serwe

Manager of Warehouse & Logistics

920.437.6400 Ext. 330



Safety

Professionalism

Effectiveness

Easy

Demand Results

_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of tracy.tmat
Sent: Wednesday, May 23, 2012 2:31 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Orders not closing





We had a problem with orders not closing too (we're on Vantage 8.03.409a).
After some monitoring we discovered it was where we had more than one pack
slip open for the same release and where amendments to the pack slip were
being made.

We never had a problem if the changes were reductions as the user knew to
untick the Ship Complete flag but they had no idea if they increased that
they needed to tick it as the system only seemed to advise by calculating
Shipped quantities and not pending.

We resolved it by writing a BPM that queries all shipments per release and
if they add up to the order value then a message appears avising the user
to tick the box. We've been doing this for about 4 months now and so far
don't have any problems reported.

Hope this makes sense as it's been a long hot day here and am sunfried!

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"Joshua Serwe" <jserwe@...> wrote:
>
> Ok, I have done some personalization to our customer shipment entry
screen
> so it can easily be checked from the summary page. I guess we will just
> have to close them all manually.
>
>
>
> Josh Serwe
>
> Manager of Warehouse & Logistics
>
> 920.437.6400 Ext. 330
>
>
>
> Safety
>
> Professionalism
>
> Effectiveness
>
> Easy
>
> Demand Results
>
> _____
>
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf
> Of leannah
> Sent: Wednesday, May 23, 2012 2:12 PM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Re: Orders not closing
>
>
>
>
>
> I don't go around the business logic direct to the database unless it is
> an "extreme" circumstance - read that as unable to do it ANY other way.
> You could probably do an updateable dashboard that only picks up order
> lines that should be closed and set it to closed from there. That the
best
> I could do.
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> ,
> "joshserwe" <jserwe@> wrote:
> >
> > LOL,I really LOVE manually closing them too. I feel it is the best use
> of my time.
> >
> > We created a dashboard that shows all orders with shipped quantities
to
> see if I could come up with some type of similarities for the orders
that
> are not closing properly, and that didn't help me come up with a rhyme
or
> reason that I could find.
> >
> > Is it possible to add anything on to the query to close the orders
that
> it finds so they don't have to be closed manually?
> >
> > Thanks for your help!
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> ,
> "leannah" <dave.leannah@> wrote:
> > >
> > > We have exactly the same problem. I have narrowed it down to packing
> the full quantity, then unpack a line or a quantity and it never checks
> for closed orders again. It unchecks the ship complete. I think there
are
> more cases where it does it but have not had a chance to get it all
> tested.
> > >
> > > Here is a query I wrote to identify open orders that should have
been
> closed:
> > >
> > > SELECT shipdtl.ordernum, shipdtl.orderline, shipdtl.jobnum,
> shipdtl.packnum, shipdtl.ourjobshipqty, shipdtl.ourinventoryshipqty
> > > --orderdtl.openline ,shiphead.shipdate, shipdtl.*
> > > FROM (Epicor905.dbo.ShipDtl ShipDtl
> > > INNER JOIN OrderDtl with (nolock)
> > > ON (ShipDtl.company = OrderDtl.company)
> > > AND (ShipDtl.ordernum = OrderDtl.ordernum)
> > > AND (ShipDtl.orderline = OrderDtl.orderline))
> > > INNER JOIN ShipHead with (nolock)
> > > ON (ShipDtl.company = ShipHead.company)
> > > AND (ShipDtl.packnum = ShipHead.packnum)
> > > WHERE shipdtl.shipcmpl = 0 and shiphead.invoiced = 1 and openline =
1
> and orderdtl.orderqty = (shipdtl.ourinventoryshipqty +
> shipdtl.ourjobshipqty)
> > > ORDER BY shipdtl.ordernum DESC
> > >
> > > They can close them manually - which they LOVE doing.
> > >
> > > You will also find that the ship date is filled in improperly as
well.
> In V8 it filled in on invoicing, now shipping randomly fills it in. Not
a
> problem unless your manifesting system uses that date for freighting -
> then you get really odd results in closing shipment days.
> > >
> > >
> > >
> > > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> ,
> "joshserwe" <jserwe@> wrote:
> > > >
> > > > We are in Epicor 9.05.607a, and have random orders not closing
> automatically upon shipment. Has anyone else experienced this issue?
Does
> something on the shipment cause it to not mark the "shipped complete"
> check box checked even though it is for the entire quantity of the
> release?
> > > > Thank you in advance for your help!
> > > > Josh
> > > >
> > >
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>





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