Re: Incorporating capture of Demand with InterSite Logistics module

Dear Paul

1. If you do not want to raise an invoice for the inventory shipped from ISL
I would question why you really need to add a shipment record. But if you do
raise a shipment record then COM will want to take that shipment to its next
logical stage - an invoice.

2. The writers of ISL/MISL are Agility they have modified it to add a
shipment record, the process is basically that they stop the COM order being
deleted at the ISL ship time and then ship the COM order from OFFLINE
SHIPPING. The IW from the shipping warehouse to the intersite warehouse is
suppressed and replaced by the SA that results from the Offline Ship. I have
seen it working/worked with it/implemented it.

3. If you only require the shipment for analysis perhaps the data could be
located from the IMHIST.

Regards
Rob Cull
Independent MAPICS Business Analyst in UK.






In a message dated 7/2/02 12:39:49 Pacific Daylight Time,
paul.connolly@selkirk.co.uk writes:

<< 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
  >>