From: dleroux on
Has anyone come up with a fix for this issue:

If a SKU is set for "Transfer" replenishment and there is an existing
transfer order to that SKU location, then purchase planning will not generate
any further transfer action messages for that SKU/location.

For example, assume a Dallas SKU for an item which is replenished via
transfer order from Houston and that Dallas needs 200 of this item. If there
were no existing transfer order supplying Dallas, then purchase planning
would generate a transfer requisition to send 200 to Dallas. Now if you
create a transfer order for Dallas - even qty 1, then the planning function
will not generate the transfer requsition to bring Dallas up to the 200 it
needs.

This does not happen in 4.0 SP1 (I am assume the same would hold true for
any later versions.) Before I start working on retrofitting 4.0 code back
into 3.7 I thought I would see if there had been a fix in 3.7.

Thanks in advance
From: Daniel Rimmelzwaan on
You could check with your partner to make sure that you are on the latest
3.7 build, but I would seriously doubt that there is a fix for your
particular issue. Support for 3.7 has been discontinued for quite a few
years now.

"dleroux" <dleroux(a)discussions.microsoft.com> wrote in message
news:B4C49B6D-76F1-4E2C-A5B6-74A9E0591E80(a)microsoft.com...
> Has anyone come up with a fix for this issue:
>
> If a SKU is set for "Transfer" replenishment and there is an existing
> transfer order to that SKU location, then purchase planning will not
> generate
> any further transfer action messages for that SKU/location.
>
> For example, assume a Dallas SKU for an item which is replenished via
> transfer order from Houston and that Dallas needs 200 of this item. If
> there
> were no existing transfer order supplying Dallas, then purchase planning
> would generate a transfer requisition to send 200 to Dallas. Now if you
> create a transfer order for Dallas - even qty 1, then the planning
> function
> will not generate the transfer requsition to bring Dallas up to the 200 it
> needs.
>
> This does not happen in 4.0 SP1 (I am assume the same would hold true for
> any later versions.) Before I start working on retrofitting 4.0 code back
> into 3.7 I thought I would see if there had been a fix in 3.7.
>
> Thanks in advance