Rob,
Since they are replace POs, the PO, partnum and date combo will be the
same until they move a date.
Karen
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of robertb_versa@...
Sent: Tuesday, November 17, 2009 3:11 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] BPM to delete rows
Karen,
Eroding business activity a year ago squashed our planned purchase of
Service Connect - so I can't advise on that. (I'm sure others in the
group can. We're blessed w/ some superb group members out there.)
Do your customers reliably use unique PO #'s when transmitting EDI
orders? If so, Cust PO#, partnum & date (in combo) may enable you to ID
change versus new orders.
Rob
--- Original Message ---
From:"Karen Schoenung" <kschoenung@...
<mailto:kschoenung%40fisher-barton.com> >
Sent:Tue 11/17/09 1:05 pm
To:<vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> >
Subj:RE: [Vantage] BPM to delete rows
Rob,
We are trying to use Vantage EDI. These are always replacements. There
is no way to tell Vantage which release to update ? as the customer(s)
can move a date forward or back, can have several of these in one EDI
transaction. With the date match, we can at least have them close.
These likely are stock products and timing of processing will make the
pack issue not relevant.
I have logged a case now with Epicor?
I would be interested if you have any ideas about how to use Service
Connect to delete these closed releases or if you have an idea how to
match these releases and still keep the logic for firm zones, partial
shipments etc.
Thanks,
Karen
In system
1 11/24/2009 50
2 11/30/2009 100
3 12/08/2009 75
4 12/15/2009 60
Customer sends
1 11/24/2009 50
2 11/30/2009 0
3 12/02/2009 100
4 12/08/2009 75
5 12/09/2009 60
6 12/15/2009 0
Result wanted
1 11/24/2009 50
2 12/02/2009 100
3 12/08/2009 75
4 12/09/2009 60
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of Robert Brown
Sent: Tuesday, November 17, 2009 11:49 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: Re: [Vantage] BPM to delete rows
I figured there was more to it Karen. (Thx.)
Is to pure Vantage EDI or have you cooked up your own process? (If your
own process via Service Connect or some other method, can you adjust
inbound EDI packet schema & your process to differentiate between change
orders versus new orders and - again - simply update the existing versus
deleting existing and re-entering?)
BPMs are still greek to me so I can't help with the delete rows desire.
However, from .NET experience, I know that if you exclusively sell
stocked items at least you won't have the complication of also having to
manipulate make-direct linked jobs (which is what 98% of our order line
releases are).
Depending upon your ship processing (& your policies with customer order
changes - as well as how strictly they are adhered to), you may also
need to consider how to handle order releases already entered for
pending future shipment as a Pack ID detail.
Rob
________________________________
From: Karen Schoenung <kschoenung@...
<mailto:kschoenung%40fisher-barton.com>
<mailto:kschoenung%40fisher-barton.com> >
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Sent: Tue, November 17, 2009 12:24:09 PM
Subject: RE: [Vantage] BPM to delete rows
EDI and matching limitation for Vantage 8.03.407B
Releases are sent via EDI - matched by date only. If zero for date,
Vantage will close the release and will create a ne
[Non-text portions of this message have been removed]
Since they are replace POs, the PO, partnum and date combo will be the
same until they move a date.
Karen
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of robertb_versa@...
Sent: Tuesday, November 17, 2009 3:11 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] BPM to delete rows
Karen,
Eroding business activity a year ago squashed our planned purchase of
Service Connect - so I can't advise on that. (I'm sure others in the
group can. We're blessed w/ some superb group members out there.)
Do your customers reliably use unique PO #'s when transmitting EDI
orders? If so, Cust PO#, partnum & date (in combo) may enable you to ID
change versus new orders.
Rob
--- Original Message ---
From:"Karen Schoenung" <kschoenung@...
<mailto:kschoenung%40fisher-barton.com> >
Sent:Tue 11/17/09 1:05 pm
To:<vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> >
Subj:RE: [Vantage] BPM to delete rows
Rob,
We are trying to use Vantage EDI. These are always replacements. There
is no way to tell Vantage which release to update ? as the customer(s)
can move a date forward or back, can have several of these in one EDI
transaction. With the date match, we can at least have them close.
These likely are stock products and timing of processing will make the
pack issue not relevant.
I have logged a case now with Epicor?
I would be interested if you have any ideas about how to use Service
Connect to delete these closed releases or if you have an idea how to
match these releases and still keep the logic for firm zones, partial
shipments etc.
Thanks,
Karen
In system
1 11/24/2009 50
2 11/30/2009 100
3 12/08/2009 75
4 12/15/2009 60
Customer sends
1 11/24/2009 50
2 11/30/2009 0
3 12/02/2009 100
4 12/08/2009 75
5 12/09/2009 60
6 12/15/2009 0
Result wanted
1 11/24/2009 50
2 12/02/2009 100
3 12/08/2009 75
4 12/09/2009 60
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of Robert Brown
Sent: Tuesday, November 17, 2009 11:49 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: Re: [Vantage] BPM to delete rows
I figured there was more to it Karen. (Thx.)
Is to pure Vantage EDI or have you cooked up your own process? (If your
own process via Service Connect or some other method, can you adjust
inbound EDI packet schema & your process to differentiate between change
orders versus new orders and - again - simply update the existing versus
deleting existing and re-entering?)
BPMs are still greek to me so I can't help with the delete rows desire.
However, from .NET experience, I know that if you exclusively sell
stocked items at least you won't have the complication of also having to
manipulate make-direct linked jobs (which is what 98% of our order line
releases are).
Depending upon your ship processing (& your policies with customer order
changes - as well as how strictly they are adhered to), you may also
need to consider how to handle order releases already entered for
pending future shipment as a Pack ID detail.
Rob
________________________________
From: Karen Schoenung <kschoenung@...
<mailto:kschoenung%40fisher-barton.com>
<mailto:kschoenung%40fisher-barton.com> >
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Sent: Tue, November 17, 2009 12:24:09 PM
Subject: RE: [Vantage] BPM to delete rows
EDI and matching limitation for Vantage 8.03.407B
Releases are sent via EDI - matched by date only. If zero for date,
Vantage will close the release and will create a ne
[Non-text portions of this message have been removed]