Re: Incorporating capture of Demand with InterSite Logistics module

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
If you are using or are planning on using MMA you would need to be
careful.   MMA uses shipment history.   Also many sales analysis packages
use shipment history.




paul.connolly@selkirk.co.uk
Sent by: mapics-l-admin@midrange.com
07/02/2002 03:38 AM
Please respond to mapics-l


        To:     MAPICS-L@midrange.com
        cc:
        Subject:        Incorporating capture of Demand with InterSite 
Logistics module


Hello

We have just implemented the Intersite Logistics module into our MAPICS
portfolio. This has caused a major rethink on key activities relating to
information reporting for some commercial activities, notably 'Demand'
capture. The current set up is a UK manufacturing facility supplies some
of
its output to a Dutch-based warehouse all under one COM company and as one
legal financial entity. Therefore, product moved from the UK to the
Netherlands is strictly speaking a stock movement rather than a sale.
My problem is that a number of the reports I write, which query the COM
files of Open and Shipped customer orders, now have large holes in them
due
to the ISL triggered COM Open Orders "disappearing" from COM databases as
soon as the Order is shipped, i.e. the order is not passed into COM's
history files - although it is passed into the ISL's 'X......' history
files. From a sales reporting perspective this may be understandable.
However, when trying to balance the input, wip, and output figures for the
Manufacturing Business life becomes difficult due to the need to start
referring to the ISL historic files as well as the COM files.
Question:
If I was to attempt to capture ISL triggered COM orders into the shipment
history file, via programme modifications, what are the things to watch
out
for? Is it better to capture the shipment at ISL shipment processing time
or
to run a nightly batch job to query the ISL historic files and append
modified records to COM's shipment history files, via offline load, etc?

What are other people's experiences of the impact of ISL on COM-based
activities?

The current ISL-triggered COM Orders are for one item line only. If I
attempt to generate a Stock Pick Consolidated Pick List (consolidation
option 3) I appear to "lose" the X number reference for each COM Order
Line
on the Pick List - is this standard MAPICS functionality?

Are there any add-ons to ISL which address these, and any other, issues?

Cheers

Paul
Business Process Analyst
Selkirk Europe


_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l
or email: MAPICS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mapics-l.