Demand created from EDI

Yahoo Archive
1
Yes, those are some big obstacles! I guess you have a good perspective
- at least SOME of the data will not need to be typed in/changed.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Steven Gotschall
Sent: Friday, August 28, 2009 12:31 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Demand created from EDI





One big issue is that most of our orders are drop shipments. The EDI
order contains the shipto info, but since it probably does not exist in
the customer record, it would not be easy for me to create a foolproof
system of getting the shipto information into the customer shipto table
and getting that shipto ID into the resulting APP file for import. In 9
I understand there is a way to use a one time drop shipment address, so
I will revisit this issue when we upgrade to 9 at the end of the year.

Another issue is that most of our products have many options available
which are defined in the part number itself. We have a hard time trying
to explain our part numbering system to our customers so what happens a
lot is they will order item XYZ with options A,D,K,L spelled out in some
free form text record of the EDI data, but the actual part number ends
up being XYZ-A-D-K-L.

There are other minor things like having to adjust the required dates
sometimes. But until we go to 9, I would say 90% of our EDI orders will
need some editing before being processed into a PO. Its still better
then having to manually enter everything from a faxed order.

________________________________
From: Karen Schoenung <kschoenung@...
<mailto:kschoenung%40fisher-barton.com> >
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Sent: Friday, August 28, 2009 1:06:41 PM
Subject: RE: [Vantage] Demand created from EDI


You're welcome. It seems strange that you say "All of our EDI orders
are going to require some fixing up before creating purchase orders from
them."

What is the issue?

From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On
Behalf
Of Steven Gotschall
Sent: Friday, August 28, 2009 12:00 PM
To: vantage@yahoogroups .com
Subject: Re: [Vantage] Demand created from EDI

I just realized that the Demand Mass Reivew has a Demand Entry button
where you can launch Demand Entry for the selected demand. This should
work for us.

Thanks Karen for pointing me in the right direction.

____________ _________ _________ __
From: Karen Schoenung <kschoenung@fisher- barton.com
<mailto:kschoenung% 40fisher- barton.com> >
To: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
Sent: Friday, August 28, 2009 12:17:34 PM
Subject: RE: [Vantage] Demand created from EDI

If they are "firm" releases, you can use Demand Mass Review...I am not
sure about "unfirm", we asked for these to show in Demand Mass Review in
a later version too - but we are live on 407b and SQL.

From: vantage@yahoogroups .com [mailto:vantage@ yahoogroups .com] On
Behalf
Of sgotschall
Sent: Friday, August 28, 2009 10:33 AM
To: vantage@yahoogroups .com
Subject: [Vantage] Demand created from EDI

Vantage 8.03.408A Progress

I've run across a problem with the demand entry part of EDI. I can get
the EDI order into Vantage as a demand. I can then go to the Demand
entry screen and open the demand and fix what needs to be fixed and then
turn it into a Sales Order. The problem is going to be down the line
when I have thousands of demand entries against the contract for any one
Customer. The Demand entry screen requires two entries to call up a
demand, the contract and the PO. After you enter the contract (in my
case, select the customer), if you press the "PO..." button, every PO
(demand) ever created against that contract shows up on the search with
no way of telling which ones have been posted (PO created), and which
ones still need to be reviewed and posted.

I can create a BAQ that shows unposted demand, but using the BAQ or
quick search inside the demand entry form doesn't work. I think the
reason is that the form is based on a multikey search which isn't
supported by a BAQ (a BAQ can only return one key).

I can create a dashboard that our Customer Service could use to view all
the new demand, and then they could open up the Demand Entry form and
manually select each one, one by one to be processed, but this seems
like a clunky way of doing it and more time consuming than it should be.
Does anyone have a better way of reviewing the open demand generated by
edi and processing them into purchase orders?

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

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

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

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





[Non-text portions of this message have been removed]
2
Vantage 8.03.408A Progress

I've run across a problem with the demand entry part of EDI. I can get the EDI order into Vantage as a demand. I can then go to the Demand entry screen and open the demand and fix what needs to be fixed and then turn it into a Sales Order. The problem is going to be down the line when I have thousands of demand entries against the contract for any one Customer. The Demand entry screen requires two entries to call up a demand, the contract and the PO. After you enter the contract (in my case, select the customer), if you press the "POÂ…" button, every PO (demand) ever created against that contract shows up on the search with no way of telling which ones have been posted (PO created), and which ones still need to be reviewed and posted.

I can create a BAQ that shows unposted demand, but using the BAQ or quick search inside the demand entry form doesn't work. I think the reason is that the form is based on a multikey search which isn't supported by a BAQ (a BAQ can only return one key).

I can create a dashboard that our Customer Service could use to view all the new demand, and then they could open up the Demand Entry form and manually select each one, one by one to be processed, but this seems like a clunky way of doing it and more time consuming than it should be. Does anyone have a better way of reviewing the open demand generated by edi and processing them into purchase orders?
3
If they are "firm" releases, you can use Demand Mass Review...I am not
sure about "unfirm", we asked for these to show in Demand Mass Review in
a later version too - but we are live on 407b and SQL.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of sgotschall
Sent: Friday, August 28, 2009 10:33 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Demand created from EDI





Vantage 8.03.408A Progress

I've run across a problem with the demand entry part of EDI. I can get
the EDI order into Vantage as a demand. I can then go to the Demand
entry screen and open the demand and fix what needs to be fixed and then
turn it into a Sales Order. The problem is going to be down the line
when I have thousands of demand entries against the contract for any one
Customer. The Demand entry screen requires two entries to call up a
demand, the contract and the PO. After you enter the contract (in my
case, select the customer), if you press the "PO..." button, every PO
(demand) ever created against that contract shows up on the search with
no way of telling which ones have been posted (PO created), and which
ones still need to be reviewed and posted.

I can create a BAQ that shows unposted demand, but using the BAQ or
quick search inside the demand entry form doesn't work. I think the
reason is that the form is based on a multikey search which isn't
supported by a BAQ (a BAQ can only return one key).

I can create a dashboard that our Customer Service could use to view all
the new demand, and then they could open up the Demand Entry form and
manually select each one, one by one to be processed, but this seems
like a clunky way of doing it and more time consuming than it should be.
Does anyone have a better way of reviewing the open demand generated by
edi and processing them into purchase orders?





[Non-text portions of this message have been removed]
4
In 408A, Demand Mass Review allows you to filter by the three different demand types, but that still doesn't solve my overall problem. The Demand Mass Review will allow us to see the unposted demand by part or demand, but you still have to open up Demand Entry and enter each contract and PO manually to make changes and process them. What I was looking for is an easier way to select unposted demand for updating and pocessing.Â

It really should be a simple thing. Just have a Demand Entry Search screen on Demand Entry like the one in Demand Mass Review that only show unposted (unprocessed) demand, or just add the "posted" column to the search results so you can sort them that way. You can process from Mass Review, but you can't edit and this is the stickler. All of our EDI orders are going to require some fixing up before creating purchase orders from them.



________________________________
From: Karen Schoenung <kschoenung@...>
To: vantage@yahoogroups.com
Sent: Friday, August 28, 2009 12:17:34 PM
Subject: RE: [Vantage] Demand created from EDI

Â
If they are "firm" releases, you can use Demand Mass Review...I am not
sure about "unfirm", we asked for these to show in Demand Mass Review in
a later version too - but we are live on 407b and SQL.

From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On Behalf
Of sgotschall
Sent: Friday, August 28, 2009 10:33 AM
To: vantage@yahoogroups .com
Subject: [Vantage] Demand created from EDI

Vantage 8.03.408A Progress

I've run across a problem with the demand entry part of EDI. I can get
the EDI order into Vantage as a demand. I can then go to the Demand
entry screen and open the demand and fix what needs to be fixed and then
turn it into a Sales Order. The problem is going to be down the line
when I have thousands of demand entries against the contract for any one
Customer. The Demand entry screen requires two entries to call up a
demand, the contract and the PO. After you enter the contract (in my
case, select the customer), if you press the "PO..." button, every PO
(demand) ever created against that contract shows up on the search with
no way of telling which ones have been posted (PO created), and which
ones still need to be reviewed and posted.

I can create a BAQ that shows unposted demand, but using the BAQ or
quick search inside the demand entry form doesn't work. I think the
reason is that the form is based on a multikey search which isn't
supported by a BAQ (a BAQ can only return one key).

I can create a dashboard that our Customer Service could use to view all
the new demand, and then they could open up the Demand Entry form and
manually select each one, one by one to be processed, but this seems
like a clunky way of doing it and more time consuming than it should be.
Does anyone have a better way of reviewing the open demand generated by
edi and processing them into purchase orders?

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







[Non-text portions of this message have been removed]
5
I just realized that the Demand Mass Reivew has a Demand Entry button where you can launch Demand Entry for the selected demand. This should work for us.

Thanks Karen for pointing me in the right direction.




________________________________
From: Karen Schoenung <kschoenung@...>
To: vantage@yahoogroups.com
Sent: Friday, August 28, 2009 12:17:34 PM
Subject: RE: [Vantage] Demand created from EDI

Â
If they are "firm" releases, you can use Demand Mass Review...I am not
sure about "unfirm", we asked for these to show in Demand Mass Review in
a later version too - but we are live on 407b and SQL.

From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On Behalf
Of sgotschall
Sent: Friday, August 28, 2009 10:33 AM
To: vantage@yahoogroups .com
Subject: [Vantage] Demand created from EDI

Vantage 8.03.408A Progress

I've run across a problem with the demand entry part of EDI. I can get
the EDI order into Vantage as a demand. I can then go to the Demand
entry screen and open the demand and fix what needs to be fixed and then
turn it into a Sales Order. The problem is going to be down the line
when I have thousands of demand entries against the contract for any one
Customer. The Demand entry screen requires two entries to call up a
demand, the contract and the PO. After you enter the contract (in my
case, select the customer), if you press the "PO..." button, every PO
(demand) ever created against that contract shows up on the search with
no way of telling which ones have been posted (PO created), and which
ones still need to be reviewed and posted.

I can create a BAQ that shows unposted demand, but using the BAQ or
quick search inside the demand entry form doesn't work. I think the
reason is that the form is based on a multikey search which isn't
supported by a BAQ (a BAQ can only return one key).

I can create a dashboard that our Customer Service could use to view all
the new demand, and then they could open up the Demand Entry form and
manually select each one, one by one to be processed, but this seems
like a clunky way of doing it and more time consuming than it should be.
Does anyone have a better way of reviewing the open demand generated by
edi and processing them into purchase orders?

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







[Non-text portions of this message have been removed]
6
You're welcome. It seems strange that you say "All of our EDI orders
are going to require some fixing up before creating purchase orders from
them."



What is the issue?





From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Steven Gotschall
Sent: Friday, August 28, 2009 12:00 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Demand created from EDI





I just realized that the Demand Mass Reivew has a Demand Entry button
where you can launch Demand Entry for the selected demand. This should
work for us.

Thanks Karen for pointing me in the right direction.

________________________________
From: Karen Schoenung <kschoenung@...
<mailto:kschoenung%40fisher-barton.com> >
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Sent: Friday, August 28, 2009 12:17:34 PM
Subject: RE: [Vantage] Demand created from EDI


If they are "firm" releases, you can use Demand Mass Review...I am not
sure about "unfirm", we asked for these to show in Demand Mass Review in
a later version too - but we are live on 407b and SQL.

From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On
Behalf
Of sgotschall
Sent: Friday, August 28, 2009 10:33 AM
To: vantage@yahoogroups .com
Subject: [Vantage] Demand created from EDI

Vantage 8.03.408A Progress

I've run across a problem with the demand entry part of EDI. I can get
the EDI order into Vantage as a demand. I can then go to the Demand
entry screen and open the demand and fix what needs to be fixed and then
turn it into a Sales Order. The problem is going to be down the line
when I have thousands of demand entries against the contract for any one
Customer. The Demand entry screen requires two entries to call up a
demand, the contract and the PO. After you enter the contract (in my
case, select the customer), if you press the "PO..." button, every PO
(demand) ever created against that contract shows up on the search with
no way of telling which ones have been posted (PO created), and which
ones still need to be reviewed and posted.

I can create a BAQ that shows unposted demand, but using the BAQ or
quick search inside the demand entry form doesn't work. I think the
reason is that the form is based on a multikey search which isn't
supported by a BAQ (a BAQ can only return one key).

I can create a dashboard that our Customer Service could use to view all
the new demand, and then they could open up the Demand Entry form and
manually select each one, one by one to be processed, but this seems
like a clunky way of doing it and more time consuming than it should be.
Does anyone have a better way of reviewing the open demand generated by
edi and processing them into purchase orders?

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

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





[Non-text portions of this message have been removed]
7
One big issue is that most of our orders are drop shipments. The EDI order contains the shipto info, but since it probably does not exist in the customer record, it would not be easy for me to create a foolproof system of getting the shipto information into the customer shipto table and getting that shipto ID into the resulting APP file for import. In 9 I understand there is a way to use a one time drop shipment address, so I will revisit this issue when we upgrade to 9 at the end of the year.

Another issue is that most of our products have many options available which are defined in the part number itself. We have a hard time trying to explain our part numbering system to our customers so what happens a lot is they will order item XYZ with options A,D,K,L spelled out in some free form text record of the EDI data, but the actual part number ends up being XYZ-A-D-K-L.Â

There are other minor things like having to adjust the required dates sometimes. But until we go to 9, I would say 90% of our EDI orders will need some editing before being processed into a PO. Its still better then having to manually enter everything from a faxed order.



________________________________
From: Karen Schoenung <kschoenung@...>
To: vantage@yahoogroups.com
Sent: Friday, August 28, 2009 1:06:41 PM
Subject: RE: [Vantage] Demand created from EDI

Â
You're welcome. It seems strange that you say "All of our EDI orders
are going to require some fixing up before creating purchase orders from
them."

What is the issue?

From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On Behalf
Of Steven Gotschall
Sent: Friday, August 28, 2009 12:00 PM
To: vantage@yahoogroups .com
Subject: Re: [Vantage] Demand created from EDI

I just realized that the Demand Mass Reivew has a Demand Entry button
where you can launch Demand Entry for the selected demand. This should
work for us.

Thanks Karen for pointing me in the right direction.

____________ _________ _________ __
From: Karen Schoenung <kschoenung@fisher- barton.com
<mailto:kschoenung% 40fisher- barton.com> >
To: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
Sent: Friday, August 28, 2009 12:17:34 PM
Subject: RE: [Vantage] Demand created from EDI

If they are "firm" releases, you can use Demand Mass Review...I am not
sure about "unfirm", we asked for these to show in Demand Mass Review in
a later version too - but we are live on 407b and SQL.

From: vantage@yahoogroups .com [mailto:vantage@ yahoogroups .com] On
Behalf
Of sgotschall
Sent: Friday, August 28, 2009 10:33 AM
To: vantage@yahoogroups .com
Subject: [Vantage] Demand created from EDI

Vantage 8.03.408A Progress

I've run across a problem with the demand entry part of EDI. I can get
the EDI order into Vantage as a demand. I can then go to the Demand
entry screen and open the demand and fix what needs to be fixed and then
turn it into a Sales Order. The problem is going to be down the line
when I have thousands of demand entries against the contract for any one
Customer. The Demand entry screen requires two entries to call up a
demand, the contract and the PO. After you enter the contract (in my
case, select the customer), if you press the "PO..." button, every PO
(demand) ever created against that contract shows up on the search with
no way of telling which ones have been posted (PO created), and which
ones still need to be reviewed and posted.

I can create a BAQ that shows unposted demand, but using the BAQ or
quick search inside the demand entry form doesn't work. I think the
reason is that the form is based on a multikey search which isn't
supported by a BAQ (a BAQ can only return one key).

I can create a dashboard that our Customer Service could use to view all
the new demand, and then they could open up the Demand Entry form and
manually select each one, one by one to be processed, but this seems
like a clunky way of doing it and more time consuming than it should be.
Does anyone have a better way of reviewing the open demand generated by
edi and processing them into purchase orders?

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

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

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







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