Ship Via on Releases

Yahoo Archive
1
We are implementing Vantage and have found the same issue. We intent to work
around it with the BPM approach, but haven't built that yet. I agree that it
doesn't make much sense either.



Additionally, for us putting different ship via's on each release is even
more hampered by the fact that there is only one freight billing type
available for the entire order.



Brad Boes

Corporate Technology Manager

Metalworks, Inc.

email: bboes@...

voice: 231-845-3130

cell: 231-690-5091

fax: 231-845-1043





[Non-text portions of this message have been removed]
2
Hi,
Anyone had an issue with this:When you ship a release, it takes the
ship via from the FIRST release reagardless of what the ship via says
on the release that you're actually shipping.
Apparently, this is working as designed. Epicor actually PLANNED to
ignore the ship via on the releases even though you can put a
different ship via on each release.
Below is the response from Epicor:
--------------------------------------
Call # 1475211ESC

I send you this email in order to follow up this issue.

As I mentioned you this is way how system works and it is designed
logic that I know was developed for product and what I tested on local
implementation.

What I can suggest you to do is change order of releases and always
make first release ship via for shipment or make one shipment by
released as shipment is always taking first open release and their
respective information

Also, I can request to Development team an enhancement for product
where this functionality can be added on next version of system.

Hope it makes sense to you. If you need more information please let me
know.

Thanks and have a good day.

Daniel Flores
Vista/Vantage Application Support
www.epicor.com
Tel.: (800)-483-4049
Fax: (952) 582-5566
E-Mail: dflores@...
3
"Logic" is used tounge in cheek here.

You might be able to get this working with a BPM directive to copy
the address you actually want to the customer shipment. We have good
success with these.

Matthew

--- In vantage@yahoogroups.com, "cpsadp" <cpsadp@...> wrote:
>
> Hi,
> Anyone had an issue with this:When you ship a release, it takes
the
> ship via from the FIRST release reagardless of what the ship via
says
> on the release that you're actually shipping.
> Apparently, this is working as designed. Epicor actually PLANNED
to
> ignore the ship via on the releases even though you can put a
> different ship via on each release.
> Below is the response from Epicor:
> --------------------------------------
> Call # 1475211ESC
>
> I send you this email in order to follow up this issue.
>
> As I mentioned you this is way how system works and it is designed
> logic that I know was developed for product and what I tested on
local
> implementation.
>
> What I can suggest you to do is change order of releases and
always
> make first release ship via for shipment or make one shipment by
> released as shipment is always taking first open release and their
> respective information
>
> Also, I can request to Development team an enhancement for product
> where this functionality can be added on next version of system.
>
> Hope it makes sense to you. If you need more information please
let me
> know.
>
> Thanks and have a good day.
>
> Daniel Flores
> Vista/Vantage Application Support
> www.epicor.com
> Tel.: (800)-483-4049
> Fax: (952) 582-5566
> E-Mail: dflores@...
>
4
I am on V 8.03.403d and Customer Shipment Entry uses the Ship Via from
the Sales Order Release.



Todd



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of macfarmw
Sent: Friday, February 29, 2008 7:19 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Ship Via on Releases



"Logic" is used tounge in cheek here.

You might be able to get this working with a BPM directive to copy
the address you actually want to the customer shipment. We have good
success with these.

Matthew

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"cpsadp" <cpsadp@...> wrote:
>
> Hi,
> Anyone had an issue with this:When you ship a release, it takes
the
> ship via from the FIRST release reagardless of what the ship via
says
> on the release that you're actually shipping.
> Apparently, this is working as designed. Epicor actually PLANNED
to
> ignore the ship via on the releases even though you can put a
> different ship via on each release.
> Below is the response from Epicor:
> --------------------------------------
> Call # 1475211ESC
>
> I send you this email in order to follow up this issue.
>
> As I mentioned you this is way how system works and it is designed
> logic that I know was developed for product and what I tested on
local
> implementation.
>
> What I can suggest you to do is change order of releases and
always
> make first release ship via for shipment or make one shipment by
> released as shipment is always taking first open release and their
> respective information
>
> Also, I can request to Development team an enhancement for product
> where this functionality can be added on next version of system.
>
> Hope it makes sense to you. If you need more information please
let me
> know.
>
> Thanks and have a good day.
>
> Daniel Flores
> Vista/Vantage Application Support
> www.epicor.com
> Tel.: (800)-483-4049
> Fax: (952) 582-5566
> E-Mail: dflores@...
>





This e-mail and any attachments may contain confidential and privileged
information. If you are not the intended recipient, please notify the
sender immediately by return e-mail, delete this e-mail and destroy any
copies. Any dissemination or use of this information by a person other
than the intended recipient is unauthorized and may be illegal.

[Non-text portions of this message have been removed]
5
Thanks, but it's not the actual address that's the problem. It's the
ship via; the shipping method. The system lets us put a different
ship method onto each release, but then refuses to populate the
correct shipping method at time of shipment.


--- In vantage@yahoogroups.com, "macfarmw" <matthew_macfarland@...>
wrote:
>
> "Logic" is used tounge in cheek here.
>
> You might be able to get this working with a BPM directive to copy
> the address you actually want to the customer shipment. We have
good
> success with these.
>
> Matthew
>
> --- In vantage@yahoogroups.com, "cpsadp" <cpsadp@> wrote:
> >
> > Hi,
> > Anyone had an issue with this:When you ship a release, it takes
> the
> > ship via from the FIRST release reagardless of what the ship via
> says
> > on the release that you're actually shipping.
> > Apparently, this is working as designed. Epicor actually PLANNED
> to
> > ignore the ship via on the releases even though you can put a
> > different ship via on each release.
> > Below is the response from Epicor:
> > --------------------------------------
> > Call # 1475211ESC
> >
> > I send you this email in order to follow up this issue.
> >
> > As I mentioned you this is way how system works and it is
designed
> > logic that I know was developed for product and what I tested on
> local
> > implementation.
> >
> > What I can suggest you to do is change order of releases and
> always
> > make first release ship via for shipment or make one shipment by
> > released as shipment is always taking first open release and
their
> > respective information
> >
> > Also, I can request to Development team an enhancement for
product
> > where this functionality can be added on next version of system.
> >
> > Hope it makes sense to you. If you need more information please
> let me
> > know.
> >
> > Thanks and have a good day.
> >
> > Daniel Flores
> > Vista/Vantage Application Support
> > www.epicor.com
> > Tel.: (800)-483-4049
> > Fax: (952) 582-5566
> > E-Mail: dflores@
> >
>
6
Even when you have multiple releases? I think that we tested this
functionality in 8.03.400 something and it still used the same flawed
logic.

--- In vantage@yahoogroups.com, "Todd Hofert" <todd@...> wrote:
>
> I am on V 8.03.403d and Customer Shipment Entry uses the Ship Via
from
> the Sales Order Release.
>
>
>
> Todd
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf
> Of macfarmw
> Sent: Friday, February 29, 2008 7:19 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Ship Via on Releases
>
>
>
> "Logic" is used tounge in cheek here.
>
> You might be able to get this working with a BPM directive to copy
> the address you actually want to the customer shipment. We have
good
> success with these.
>
> Matthew
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "cpsadp" <cpsadp@> wrote:
> >
> > Hi,
> > Anyone had an issue with this:When you ship a release, it takes
> the
> > ship via from the FIRST release reagardless of what the ship via
> says
> > on the release that you're actually shipping.
> > Apparently, this is working as designed. Epicor actually PLANNED
> to
> > ignore the ship via on the releases even though you can put a
> > different ship via on each release.
> > Below is the response from Epicor:
> > --------------------------------------
> > Call # 1475211ESC
> >
> > I send you this email in order to follow up this issue.
> >
> > As I mentioned you this is way how system works and it is
designed
> > logic that I know was developed for product and what I tested on
> local
> > implementation.
> >
> > What I can suggest you to do is change order of releases and
> always
> > make first release ship via for shipment or make one shipment by
> > released as shipment is always taking first open release and
their
> > respective information
> >
> > Also, I can request to Development team an enhancement for
product
> > where this functionality can be added on next version of system.
> >
> > Hope it makes sense to you. If you need more information please
> let me
> > know.
> >
> > Thanks and have a good day.
> >
> > Daniel Flores
> > Vista/Vantage Application Support
> > www.epicor.com
> > Tel.: (800)-483-4049
> > Fax: (952) 582-5566
> > E-Mail: dflores@
> >
>
>
>
>
>
> This e-mail and any attachments may contain confidential and
privileged
> information. If you are not the intended recipient, please notify
the
> sender immediately by return e-mail, delete this e-mail and destroy
any
> copies. Any dissemination or use of this information by a person
other
> than the intended recipient is unauthorized and may be illegal.
>
> [Non-text portions of this message have been removed]
>