Ship to nowhere?

Lynn,



Sorry, but from what you've told me, I don't think I can help.



Steve

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Lynn Thomas 83
Sent: Wednesday, April 30, 2008 1:41 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Ship to nowhere?



Well, I tried it in the test db, and ran right smack into a problem.
The serial number already exists, even though it's been shipped out,
so I can't receive them back to fulfill the PO.

Thinking cap back on...

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"Lynn Thomas 83" <thomasl@...> wrote:
>
> Steve,
>
> 'Interesting' is a word with many definitions....
>
> The first cycle is easy enough, up to the point of invoicing, which
> we're not doing here at all. I can't, in fact. We didn't license any
> of Vantage's financial modules, a circumstance which has led to a
> number of 'interesting' discoveries. The most recent one involves
> shipping, but that's another tale altogether.
>
> Hmm, not all of the parts on this order are manufactured. By itself
> that's not a huge issue in handling things. Actually, it shouldn't be
> a problem at all. From a shipping point of view, each of those is
> just another line item exactly like a mnufactured part. We shall not
> inquire into why the gov't doesn't buy them directly. We just won't.
>
> The second cycle logic works. On first reading it seemed painfully
> convoluted for what in physical practice is pretty simple, but after
> thinking on it more carefully, it makes a lot of sense. Of course,
> Murphy gets his due, and there's at least one potentially major
> hiccup. I cannot create a distinct set of part numbers. It's not the
> number of items in question, although that's large (>200), but rather
> trying to deal with the various stakeholders. I'll spare you the
> details, but it's a non-starter. Again, invoicing doesn't happen.
> From our point of view all the money is magic. There are a few things
> we total up, but nothing actually changes hands. The two individual
> items we've shipped (and the shipping transaction records are messed
> up, which was the most recent 'interesting' discovery) we created the
> sales order as you described.
>
> I wonder if this might not be much easier if I had a separate company
> for this warehouse?
>
> Off to play with a test db, I think.
>
> Thank you!
>
> Lynn
>
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"Ashton, Steve" <Steve.Ashton@> wrote:
> >
> > This is interesting. I think you have two separate Vantage cycles.
> >
> >
> >
> > The first cycle is the blanket order where you commit to make and
sell
> > your manufactured parts.
> >
> > 1. create Sales Order
> > 2. create Job (part numbers should be on the manufactured parts
> > list)
> > 3. ship parts from job (you need the packing slip to initiate the
> > invoice. The ship-to address could be "Receive to Secure Locker on
> > PO#xxxx")
> > 4. Invoice parts
> >
> >
> >
> > The second cycle is the release order where you commit to stock and
> > distribute the customer's parts
> >
> > 1. Set up your customer as a Vendor.
> > 2. Set up distinct part numbers on the purchase parts list (they
> > are customer owned versions of the parts you made and the costs
will be
> > different)
> > 3. Create a PO to buy the purchased parts at $0.00 & receive them
> > to the secure locker (reference this PO# on the ship to address
above)
> > 4. Create sales order for any service or subcontractor demand.
> > 5. Ship parts from the customer-owned inventory.
> > 6. Invoice parts at the agreed price ($0.00?)
> >
> >
> >
> > This sounds like it would work. You should try it in your test
database.
> >
> >
> > Steve Ashton x 4260
> >
> > ________________________________
> >
> > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf
> > Of Lynn Thomas 83
> > Sent: Thursday, April 24, 2008 12:11 PM
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] Re: Ship to nowhere?
> >
> >
> >
> > We will invoice at A, so the government owns the parts, but we
> > maintain custody and handling of them. In fact, we're not using
> > Vantage for financials at all, so in one sense it doesn't matter.
I'm
> > mostly interested in figuring out a straightforward way to keep
track
> > of the physical, as opposed to fiscal, facts.
> >
> > Yes, the whole arrangement is quite strange if you think in terms of
a
> > commercial business model. But it's the arrangement I have.
> >
> > Lynn Thomas
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> ,
> > "Ashton, Steve" <Steve.Ashton@> wrote:
> > >
> > > When would you invoice the customer?
> > >
> > > A) Upon shipment of the blanket order to the repair parts
warehouse
> > > or
> > >
> > > B) Upon shipment of a release order from the repair parts
warehouse
> > > to the customer?
> > >
> > >
> > >
> > > Steve Ashton
> > > Database Specialist
> > > Decoustics Limited
> > > 65 Disco Road
> > > Toronto, Ontario
> > > Canada M9W 1M2
> > > T (647) 259-4260
> > > F (416) 679-8838
> > >
> > > sashton@ <mailto:sashton@>
> > > Steve.Ashton@ <mailto:Steve.Ashton2@>
> > >
> > >
> > > ________________________________
> > >
> > > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
> > [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
] On
> > Behalf
> > > Of Lynn Thomas 83
> > > Sent: Thursday, April 24, 2008 8:26 AM
> > > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
> > > Subject: [Vantage] Ship to nowhere?
> > >
> > >
> > >
> > > I have a logic question, I think. We have a government contract
for
> > > maintenance on something we produce. The repair parts must be
> > > physically separate from production materials - no mixing of the
two
> > > allowed.
> > >
> > > I have an order for parts to stock the repair parts warehouse,
which
> > > is fine, wonderful, and all that. What I can't quite figure out is
> > > how to show the order lines as being fulfilled and 'shipped', to
deal
> > > with that order, when what physically happens is they arrive and
we
> > > put them into the secure locker where they sit until we get an
order
> > > to ship something to a [sub-]customer, when we pull the part
from that
> > > warehouse's inventory and ship it to whomever needs it, or issue
it to
> > > our repair crew to fix something returned to us. Essentially, it's
a
> > > 'Buy and hold' order.
> > >
> > > I can work either half of the problem easily, but the flow from
one to
> > > the other eludes me. We're in the process of implementing
8.03.403D
> > > from scratch.
> > >
> > > Has anyone else done something similar?
> > >
> > > Lynn Thomas
> > > SAIC
> > >
> > >
> > >
> > >
> > >
> > > [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]
I have a logic question, I think. We have a government contract for
maintenance on something we produce. The repair parts must be
physically separate from production materials - no mixing of the two
allowed.

I have an order for parts to stock the repair parts warehouse, which
is fine, wonderful, and all that. What I can't quite figure out is
how to show the order lines as being fulfilled and 'shipped', to deal
with that order, when what physically happens is they arrive and we
put them into the secure locker where they sit until we get an order
to ship something to a [sub-]customer, when we pull the part from that
warehouse's inventory and ship it to whomever needs it, or issue it to
our repair crew to fix something returned to us. Essentially, it's a
'Buy and hold' order.

I can work either half of the problem easily, but the flow from one to
the other eludes me. We're in the process of implementing 8.03.403D
from scratch.

Has anyone else done something similar?

Lynn Thomas
SAIC
When would you invoice the customer?

A) Upon shipment of the blanket order to the repair parts warehouse
or

B) Upon shipment of a release order from the repair parts warehouse
to the customer?



Steve Ashton
Database Specialist
Decoustics Limited
65 Disco Road
Toronto, Ontario
Canada M9W 1M2
T (647) 259-4260
F (416) 679-8838

sashton@... <mailto:sashton@...>
Steve.Ashton@... <mailto:Steve.Ashton2@...>


________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Lynn Thomas 83
Sent: Thursday, April 24, 2008 8:26 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Ship to nowhere?



I have a logic question, I think. We have a government contract for
maintenance on something we produce. The repair parts must be
physically separate from production materials - no mixing of the two
allowed.

I have an order for parts to stock the repair parts warehouse, which
is fine, wonderful, and all that. What I can't quite figure out is
how to show the order lines as being fulfilled and 'shipped', to deal
with that order, when what physically happens is they arrive and we
put them into the secure locker where they sit until we get an order
to ship something to a [sub-]customer, when we pull the part from that
warehouse's inventory and ship it to whomever needs it, or issue it to
our repair crew to fix something returned to us. Essentially, it's a
'Buy and hold' order.

I can work either half of the problem easily, but the flow from one to
the other eludes me. We're in the process of implementing 8.03.403D
from scratch.

Has anyone else done something similar?

Lynn Thomas
SAIC





[Non-text portions of this message have been removed]
We will invoice at A, so the government owns the parts, but we
maintain custody and handling of them. In fact, we're not using
Vantage for financials at all, so in one sense it doesn't matter. I'm
mostly interested in figuring out a straightforward way to keep track
of the physical, as opposed to fiscal, facts.

Yes, the whole arrangement is quite strange if you think in terms of a
commercial business model. But it's the arrangement I have.

Lynn Thomas

--- In vantage@yahoogroups.com, "Ashton, Steve" <Steve.Ashton@...> wrote:
>
> When would you invoice the customer?
>
> A) Upon shipment of the blanket order to the repair parts warehouse
> or
>
> B) Upon shipment of a release order from the repair parts warehouse
> to the customer?
>
>
>
> Steve Ashton
> Database Specialist
> Decoustics Limited
> 65 Disco Road
> Toronto, Ontario
> Canada M9W 1M2
> T (647) 259-4260
> F (416) 679-8838
>
> sashton@... <mailto:sashton@...>
> Steve.Ashton@... <mailto:Steve.Ashton2@...>
>
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of Lynn Thomas 83
> Sent: Thursday, April 24, 2008 8:26 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Ship to nowhere?
>
>
>
> I have a logic question, I think. We have a government contract for
> maintenance on something we produce. The repair parts must be
> physically separate from production materials - no mixing of the two
> allowed.
>
> I have an order for parts to stock the repair parts warehouse, which
> is fine, wonderful, and all that. What I can't quite figure out is
> how to show the order lines as being fulfilled and 'shipped', to deal
> with that order, when what physically happens is they arrive and we
> put them into the secure locker where they sit until we get an order
> to ship something to a [sub-]customer, when we pull the part from that
> warehouse's inventory and ship it to whomever needs it, or issue it to
> our repair crew to fix something returned to us. Essentially, it's a
> 'Buy and hold' order.
>
> I can work either half of the problem easily, but the flow from one to
> the other eludes me. We're in the process of implementing 8.03.403D
> from scratch.
>
> Has anyone else done something similar?
>
> Lynn Thomas
> SAIC
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
This is interesting. I think you have two separate Vantage cycles.



The first cycle is the blanket order where you commit to make and sell
your manufactured parts.

1. create Sales Order
2. create Job (part numbers should be on the manufactured parts
list)
3. ship parts from job (you need the packing slip to initiate the
invoice. The ship-to address could be "Receive to Secure Locker on
PO#xxxx")
4. Invoice parts



The second cycle is the release order where you commit to stock and
distribute the customer's parts

1. Set up your customer as a Vendor.
2. Set up distinct part numbers on the purchase parts list (they
are customer owned versions of the parts you made and the costs will be
different)
3. Create a PO to buy the purchased parts at $0.00 & receive them
to the secure locker (reference this PO# on the ship to address above)
4. Create sales order for any service or subcontractor demand.
5. Ship parts from the customer-owned inventory.
6. Invoice parts at the agreed price ($0.00?)



This sounds like it would work. You should try it in your test database.


Steve Ashton x 4260

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Lynn Thomas 83
Sent: Thursday, April 24, 2008 12:11 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Ship to nowhere?



We will invoice at A, so the government owns the parts, but we
maintain custody and handling of them. In fact, we're not using
Vantage for financials at all, so in one sense it doesn't matter. I'm
mostly interested in figuring out a straightforward way to keep track
of the physical, as opposed to fiscal, facts.

Yes, the whole arrangement is quite strange if you think in terms of a
commercial business model. But it's the arrangement I have.

Lynn Thomas

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"Ashton, Steve" <Steve.Ashton@...> wrote:
>
> When would you invoice the customer?
>
> A) Upon shipment of the blanket order to the repair parts warehouse
> or
>
> B) Upon shipment of a release order from the repair parts warehouse
> to the customer?
>
>
>
> Steve Ashton
> Database Specialist
> Decoustics Limited
> 65 Disco Road
> Toronto, Ontario
> Canada M9W 1M2
> T (647) 259-4260
> F (416) 679-8838
>
> sashton@... <mailto:sashton@...>
> Steve.Ashton@... <mailto:Steve.Ashton2@...>
>
>
> ________________________________
>
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf
> Of Lynn Thomas 83
> Sent: Thursday, April 24, 2008 8:26 AM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Ship to nowhere?
>
>
>
> I have a logic question, I think. We have a government contract for
> maintenance on something we produce. The repair parts must be
> physically separate from production materials - no mixing of the two
> allowed.
>
> I have an order for parts to stock the repair parts warehouse, which
> is fine, wonderful, and all that. What I can't quite figure out is
> how to show the order lines as being fulfilled and 'shipped', to deal
> with that order, when what physically happens is they arrive and we
> put them into the secure locker where they sit until we get an order
> to ship something to a [sub-]customer, when we pull the part from that
> warehouse's inventory and ship it to whomever needs it, or issue it to
> our repair crew to fix something returned to us. Essentially, it's a
> 'Buy and hold' order.
>
> I can work either half of the problem easily, but the flow from one to
> the other eludes me. We're in the process of implementing 8.03.403D
> from scratch.
>
> Has anyone else done something similar?
>
> Lynn Thomas
> SAIC
>
>
>
>
>
> [Non-text portions of this message have been removed]
>





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

I had an answer almost finished and fat fingered it right into the
ether...I will retype it tomorrow, but I wanted to thank you for your
response.

Lynn

--- In vantage@yahoogroups.com, "Ashton, Steve" <Steve.Ashton@...> wrote:
>
> This is interesting. I think you have two separate Vantage cycles.
>
>
>
> The first cycle is the blanket order where you commit to make and sell
> your manufactured parts.
>
> 1. create Sales Order
> 2. create Job (part numbers should be on the manufactured parts
> list)
> 3. ship parts from job (you need the packing slip to initiate the
> invoice. The ship-to address could be "Receive to Secure Locker on
> PO#xxxx")
> 4. Invoice parts
>
>
>
> The second cycle is the release order where you commit to stock and
> distribute the customer's parts
>
> 1. Set up your customer as a Vendor.
> 2. Set up distinct part numbers on the purchase parts list (they
> are customer owned versions of the parts you made and the costs will be
> different)
> 3. Create a PO to buy the purchased parts at $0.00 & receive them
> to the secure locker (reference this PO# on the ship to address above)
> 4. Create sales order for any service or subcontractor demand.
> 5. Ship parts from the customer-owned inventory.
> 6. Invoice parts at the agreed price ($0.00?)
>
>
>
> This sounds like it would work. You should try it in your test database.
>
>
> Steve Ashton x 4260
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of Lynn Thomas 83
> Sent: Thursday, April 24, 2008 12:11 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Ship to nowhere?
>
>
>
> We will invoice at A, so the government owns the parts, but we
> maintain custody and handling of them. In fact, we're not using
> Vantage for financials at all, so in one sense it doesn't matter. I'm
> mostly interested in figuring out a straightforward way to keep track
> of the physical, as opposed to fiscal, facts.
>
> Yes, the whole arrangement is quite strange if you think in terms of a
> commercial business model. But it's the arrangement I have.
>
> Lynn Thomas
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "Ashton, Steve" <Steve.Ashton@> wrote:
> >
> > When would you invoice the customer?
> >
> > A) Upon shipment of the blanket order to the repair parts warehouse
> > or
> >
> > B) Upon shipment of a release order from the repair parts warehouse
> > to the customer?
> >
> >
> >
> > Steve Ashton
> > Database Specialist
> > Decoustics Limited
> > 65 Disco Road
> > Toronto, Ontario
> > Canada M9W 1M2
> > T (647) 259-4260
> > F (416) 679-8838
> >
> > sashton@ <mailto:sashton@>
> > Steve.Ashton@ <mailto:Steve.Ashton2@>
> >
> >
> > ________________________________
> >
> > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
> Behalf
> > Of Lynn Thomas 83
> > Sent: Thursday, April 24, 2008 8:26 AM
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] Ship to nowhere?
> >
> >
> >
> > I have a logic question, I think. We have a government contract for
> > maintenance on something we produce. The repair parts must be
> > physically separate from production materials - no mixing of the two
> > allowed.
> >
> > I have an order for parts to stock the repair parts warehouse, which
> > is fine, wonderful, and all that. What I can't quite figure out is
> > how to show the order lines as being fulfilled and 'shipped', to deal
> > with that order, when what physically happens is they arrive and we
> > put them into the secure locker where they sit until we get an order
> > to ship something to a [sub-]customer, when we pull the part from that
> > warehouse's inventory and ship it to whomever needs it, or issue it to
> > our repair crew to fix something returned to us. Essentially, it's a
> > 'Buy and hold' order.
> >
> > I can work either half of the problem easily, but the flow from one to
> > the other eludes me. We're in the process of implementing 8.03.403D
> > from scratch.
> >
> > Has anyone else done something similar?
> >
> > Lynn Thomas
> > SAIC
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
Steve,

'Interesting' is a word with many definitions....

The first cycle is easy enough, up to the point of invoicing, which
we're not doing here at all. I can't, in fact. We didn't license any
of Vantage's financial modules, a circumstance which has led to a
number of 'interesting' discoveries. The most recent one involves
shipping, but that's another tale altogether.

Hmm, not all of the parts on this order are manufactured. By itself
that's not a huge issue in handling things. Actually, it shouldn't be
a problem at all. From a shipping point of view, each of those is
just another line item exactly like a mnufactured part. We shall not
inquire into why the gov't doesn't buy them directly. We just won't.

The second cycle logic works. On first reading it seemed painfully
convoluted for what in physical practice is pretty simple, but after
thinking on it more carefully, it makes a lot of sense. Of course,
Murphy gets his due, and there's at least one potentially major
hiccup. I cannot create a distinct set of part numbers. It's not the
number of items in question, although that's large (>200), but rather
trying to deal with the various stakeholders. I'll spare you the
details, but it's a non-starter. Again, invoicing doesn't happen.
From our point of view all the money is magic. There are a few things
we total up, but nothing actually changes hands. The two individual
items we've shipped (and the shipping transaction records are messed
up, which was the most recent 'interesting' discovery) we created the
sales order as you described.

I wonder if this might not be much easier if I had a separate company
for this warehouse?

Off to play with a test db, I think.

Thank you!

Lynn


--- In vantage@yahoogroups.com, "Ashton, Steve" <Steve.Ashton@...> wrote:
>
> This is interesting. I think you have two separate Vantage cycles.
>
>
>
> The first cycle is the blanket order where you commit to make and sell
> your manufactured parts.
>
> 1. create Sales Order
> 2. create Job (part numbers should be on the manufactured parts
> list)
> 3. ship parts from job (you need the packing slip to initiate the
> invoice. The ship-to address could be "Receive to Secure Locker on
> PO#xxxx")
> 4. Invoice parts
>
>
>
> The second cycle is the release order where you commit to stock and
> distribute the customer's parts
>
> 1. Set up your customer as a Vendor.
> 2. Set up distinct part numbers on the purchase parts list (they
> are customer owned versions of the parts you made and the costs will be
> different)
> 3. Create a PO to buy the purchased parts at $0.00 & receive them
> to the secure locker (reference this PO# on the ship to address above)
> 4. Create sales order for any service or subcontractor demand.
> 5. Ship parts from the customer-owned inventory.
> 6. Invoice parts at the agreed price ($0.00?)
>
>
>
> This sounds like it would work. You should try it in your test database.
>
>
> Steve Ashton x 4260
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of Lynn Thomas 83
> Sent: Thursday, April 24, 2008 12:11 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Ship to nowhere?
>
>
>
> We will invoice at A, so the government owns the parts, but we
> maintain custody and handling of them. In fact, we're not using
> Vantage for financials at all, so in one sense it doesn't matter. I'm
> mostly interested in figuring out a straightforward way to keep track
> of the physical, as opposed to fiscal, facts.
>
> Yes, the whole arrangement is quite strange if you think in terms of a
> commercial business model. But it's the arrangement I have.
>
> Lynn Thomas
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "Ashton, Steve" <Steve.Ashton@> wrote:
> >
> > When would you invoice the customer?
> >
> > A) Upon shipment of the blanket order to the repair parts warehouse
> > or
> >
> > B) Upon shipment of a release order from the repair parts warehouse
> > to the customer?
> >
> >
> >
> > Steve Ashton
> > Database Specialist
> > Decoustics Limited
> > 65 Disco Road
> > Toronto, Ontario
> > Canada M9W 1M2
> > T (647) 259-4260
> > F (416) 679-8838
> >
> > sashton@ <mailto:sashton@>
> > Steve.Ashton@ <mailto:Steve.Ashton2@>
> >
> >
> > ________________________________
> >
> > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
> Behalf
> > Of Lynn Thomas 83
> > Sent: Thursday, April 24, 2008 8:26 AM
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] Ship to nowhere?
> >
> >
> >
> > I have a logic question, I think. We have a government contract for
> > maintenance on something we produce. The repair parts must be
> > physically separate from production materials - no mixing of the two
> > allowed.
> >
> > I have an order for parts to stock the repair parts warehouse, which
> > is fine, wonderful, and all that. What I can't quite figure out is
> > how to show the order lines as being fulfilled and 'shipped', to deal
> > with that order, when what physically happens is they arrive and we
> > put them into the secure locker where they sit until we get an order
> > to ship something to a [sub-]customer, when we pull the part from that
> > warehouse's inventory and ship it to whomever needs it, or issue it to
> > our repair crew to fix something returned to us. Essentially, it's a
> > 'Buy and hold' order.
> >
> > I can work either half of the problem easily, but the flow from one to
> > the other eludes me. We're in the process of implementing 8.03.403D
> > from scratch.
> >
> > Has anyone else done something similar?
> >
> > Lynn Thomas
> > SAIC
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
Well, I tried it in the test db, and ran right smack into a problem.
The serial number already exists, even though it's been shipped out,
so I can't receive them back to fulfill the PO.

Thinking cap back on...

--- In vantage@yahoogroups.com, "Lynn Thomas 83" <thomasl@...> wrote:
>
> Steve,
>
> 'Interesting' is a word with many definitions....
>
> The first cycle is easy enough, up to the point of invoicing, which
> we're not doing here at all. I can't, in fact. We didn't license any
> of Vantage's financial modules, a circumstance which has led to a
> number of 'interesting' discoveries. The most recent one involves
> shipping, but that's another tale altogether.
>
> Hmm, not all of the parts on this order are manufactured. By itself
> that's not a huge issue in handling things. Actually, it shouldn't be
> a problem at all. From a shipping point of view, each of those is
> just another line item exactly like a mnufactured part. We shall not
> inquire into why the gov't doesn't buy them directly. We just won't.
>
> The second cycle logic works. On first reading it seemed painfully
> convoluted for what in physical practice is pretty simple, but after
> thinking on it more carefully, it makes a lot of sense. Of course,
> Murphy gets his due, and there's at least one potentially major
> hiccup. I cannot create a distinct set of part numbers. It's not the
> number of items in question, although that's large (>200), but rather
> trying to deal with the various stakeholders. I'll spare you the
> details, but it's a non-starter. Again, invoicing doesn't happen.
> From our point of view all the money is magic. There are a few things
> we total up, but nothing actually changes hands. The two individual
> items we've shipped (and the shipping transaction records are messed
> up, which was the most recent 'interesting' discovery) we created the
> sales order as you described.
>
> I wonder if this might not be much easier if I had a separate company
> for this warehouse?
>
> Off to play with a test db, I think.
>
> Thank you!
>
> Lynn
>
>
> --- In vantage@yahoogroups.com, "Ashton, Steve" <Steve.Ashton@> wrote:
> >
> > This is interesting. I think you have two separate Vantage cycles.
> >
> >
> >
> > The first cycle is the blanket order where you commit to make and sell
> > your manufactured parts.
> >
> > 1. create Sales Order
> > 2. create Job (part numbers should be on the manufactured parts
> > list)
> > 3. ship parts from job (you need the packing slip to initiate the
> > invoice. The ship-to address could be "Receive to Secure Locker on
> > PO#xxxx")
> > 4. Invoice parts
> >
> >
> >
> > The second cycle is the release order where you commit to stock and
> > distribute the customer's parts
> >
> > 1. Set up your customer as a Vendor.
> > 2. Set up distinct part numbers on the purchase parts list (they
> > are customer owned versions of the parts you made and the costs
will be
> > different)
> > 3. Create a PO to buy the purchased parts at $0.00 & receive them
> > to the secure locker (reference this PO# on the ship to address above)
> > 4. Create sales order for any service or subcontractor demand.
> > 5. Ship parts from the customer-owned inventory.
> > 6. Invoice parts at the agreed price ($0.00?)
> >
> >
> >
> > This sounds like it would work. You should try it in your test
database.
> >
> >
> > Steve Ashton x 4260
> >
> > ________________________________
> >
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf
> > Of Lynn Thomas 83
> > Sent: Thursday, April 24, 2008 12:11 PM
> > To: vantage@yahoogroups.com
> > Subject: [Vantage] Re: Ship to nowhere?
> >
> >
> >
> > We will invoice at A, so the government owns the parts, but we
> > maintain custody and handling of them. In fact, we're not using
> > Vantage for financials at all, so in one sense it doesn't matter. I'm
> > mostly interested in figuring out a straightforward way to keep track
> > of the physical, as opposed to fiscal, facts.
> >
> > Yes, the whole arrangement is quite strange if you think in terms of a
> > commercial business model. But it's the arrangement I have.
> >
> > Lynn Thomas
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> > "Ashton, Steve" <Steve.Ashton@> wrote:
> > >
> > > When would you invoice the customer?
> > >
> > > A) Upon shipment of the blanket order to the repair parts warehouse
> > > or
> > >
> > > B) Upon shipment of a release order from the repair parts warehouse
> > > to the customer?
> > >
> > >
> > >
> > > Steve Ashton
> > > Database Specialist
> > > Decoustics Limited
> > > 65 Disco Road
> > > Toronto, Ontario
> > > Canada M9W 1M2
> > > T (647) 259-4260
> > > F (416) 679-8838
> > >
> > > sashton@ <mailto:sashton@>
> > > Steve.Ashton@ <mailto:Steve.Ashton2@>
> > >
> > >
> > > ________________________________
> > >
> > > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
] On
> > Behalf
> > > Of Lynn Thomas 83
> > > Sent: Thursday, April 24, 2008 8:26 AM
> > > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > > Subject: [Vantage] Ship to nowhere?
> > >
> > >
> > >
> > > I have a logic question, I think. We have a government contract for
> > > maintenance on something we produce. The repair parts must be
> > > physically separate from production materials - no mixing of the two
> > > allowed.
> > >
> > > I have an order for parts to stock the repair parts warehouse, which
> > > is fine, wonderful, and all that. What I can't quite figure out is
> > > how to show the order lines as being fulfilled and 'shipped', to
deal
> > > with that order, when what physically happens is they arrive and we
> > > put them into the secure locker where they sit until we get an order
> > > to ship something to a [sub-]customer, when we pull the part
from that
> > > warehouse's inventory and ship it to whomever needs it, or issue
it to
> > > our repair crew to fix something returned to us. Essentially, it's a
> > > 'Buy and hold' order.
> > >
> > > I can work either half of the problem easily, but the flow from
one to
> > > the other eludes me. We're in the process of implementing 8.03.403D
> > > from scratch.
> > >
> > > Has anyone else done something similar?
> > >
> > > Lynn Thomas
> > > SAIC
> > >
> > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>