RE: RE: Mapics data extract -- MAPICS-L

Michael,

I agree that a PTF doesn't necessarily mean a fix anymore. The practice of
shipping enhancements as PTF's is one of the things I do not agree with,
since some of the enhancements are mandatory and do change function. This is
what release levels are for. Unfortunately the last MAPICS releases have
been a means of shipping database changes for new third party applications,
not enhancing current code.

That along with the numerous bad fixes make for a very difficult support
strategy. You either examine and download lots of fixes or apply the cd and
cross your fingers and hope to keep running. Plus there are many things they
just don't fix, lots of them in COM. MAPICS COM cannot accurately calculate
a ship date. What other ERP systems shares this problem? 

I really did not claim that OEI was better than COM, simply that COM is the
main cause of system upgrades. OEI is a batch driven antique. COM is the
spawn of an obsolete development tool.

Why does COM need a rewrite?
1) BUGS, BUGS, BUGS, BUGS
2) Additional function shipped as API's and user exits? Wassup with that?
3) Difficult use, high support requirements.
4) Missing function...kits, serial number support, commissions, taxation,
superceded items, substitution items.

I don't have any problems with EC as a product. I am sure for some subset of
companies it makes sense. We looked at it and felt the cost/benefit of PC
products was far better. It does bring up the MAPICS pricing issue, tied
into the AS/400 pricing issue that has hampered MAPICS and IBM for quite
some time.

Regards

Konrad


-----Original Message-----
From: michael.franchino@xxxxxxxxxx [mailto:michael.franchino@xxxxxxxxxx] 
Sent: Friday, March 28, 2003 9:07 AM
To: MAPICS ERP System Discussion
Subject: RE: RE: Mapics data extract


Konrad,

First of all, a PTF doesn't necessarily mean a fix (obviously most of them 
are fixes to issues). Some PTFs are actually new function that has been 
added to the product. EC is constantly adding new functions or enhancing 
functions in our product where business requirements nessistate. 

EC is a REAL app that was designed and coded in 94-95 time frame and has 
been enhanced with every release. We don't support everything, but we hit 
many of the major transactions that the MAPICS customer base needs to do 
their job.

Why do you think that COM needs a MAJOR rewrite.  Obviously there are 
issues with COM in certain areas and a rewrite would be a welcome sight, 
but that is definetly not the direction of the company as you have already 
said. 

To say that OEI is better than COM is a little ridiculous. If you don't 
need the features that COM provides (Enhanced Pricing, Blanket order 
processing, Packing, integrated EDI solutions, expanded ship-to support, 
User Exit support, etc.) then staying with OE&I makes sense.


Michael Franchino
Custom Systems Corporation
http://www.cussys.com
(973) 726-0202 X214 (Phone) 
(973) 726-4552 (Fax)




Konrad Underkofler <kdunderk@xxxxxxxxxxxxx>
Sent by: mapics-l-bounces@xxxxxxxxxxxx
03/28/2003 08:49 AM
Please respond to MAPICS ERP System Discussion

 
        To:     "'MAPICS ERP System Discussion'" <mapics-l@xxxxxxxxxxxx>
        cc: 
        Subject:        RE: RE: Mapics data extract


Oh well, I just have to Paola...

> It is a good solid product
  PTF 4600+ and counting. R7 dead in water. We just had to download Rev 33
of the client so we could delete an item in EPDM! This is a product that 
has
been out for several years, how can it not delete items? 

> and is continually being updated as business needs change.
  I think I missed that. COM needs a complete rethink and rewrite. The 
last
real MAPICS app was REP done back in 90 or 91? Otherwise the functionality
is the same as it was this past decade. Most of the goodness resides in 
the
Mfg area, but flexibility is not included.

> On the other hand, with MAPICS you have a full customer support team 
> to
help guide you through problems, training, and issues.  So even though you
have employees coming and going over the years, you still have the support
team at MAPICS to help support your users. 

If they have not been laid off yet. MAPICS XA is clearly not MAPICS Inc
strategic application set anymore following years of effort, all
semi-successful to get off green screen AS/400 and its associated costs. I
believe most MAPICS development is being done in India now. 

So, in answer to the data extract question. 

1) Whatever version of MAPICS you have is probably just like the current 
one
in function with the exception of COM replacing OEI. My advice stick with
it. Depending on what release you are on, the upgrade path may be brutal. 
In
any case the older versions (ie pre COM) are good efficient machine users
and do not require outlandish CPW ratings to function.

2) Extracting data is more practical if you just get the customer and 
items
(ie CUSMAS and ITEMAS) and then cut over and start again. Run the existing
system till all transactions have cleared while bringing up the new one
merging the results on paper. 

3) Custom programs are far easier now than they used to be if you
requirements don't fit MAPICS well. You will easily spend enough in 
license
fees, upgrades, mods, consulting to make the custom solution doable in a 
lot
of cases. 

Regards

Konrad

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



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