Brad,
   I am glad to hear that an authorized Infor Affiliate was able to assist
   the customer and resolve the issue.  It sounds like the "savings" did not
   turn out to be much of a savings at all.
   Thanks,
   Shane Barger
   VP of Consulting
   (513) 631-8800 x 113
   (513) 631-5242 fax
   ---------- Original Message ----------
   FROM:      Brad Blair [1]<bblair@xxxxxxxxxxx>
   TO:        MAPICS ERP System Discussion [2]<mapics-l@xxxxxxxxxxxx>
   CC:
   DATE:      Fri, 9 Jul 2010 13:18:20 -0400
   SUBJECT:   Re: [MAPICS-L] Product structure routings
     EPILOGUE:
     The guy in question was a consultant who was hired in an effort to "save
     ; money" from another consulting group the company had been using.  He'd
     told the company he was experienced in manufacturing and XA.
     He did create a significant issue that had repercussions at the company.
      The original consulting company has bailed them out of the fix they
   were
     in and will in all likelihood continue to be the "go to" resource for IT
     and XA support at the company.
     Enough Said!!
     Bradford C. Blair
     From:        Ronald Kral [3]<ronkral169@xxxxxxxxx>
     To:        MAPICS ERP System Discussion [4]<mapics-l@xxxxxxxxxxxx>
     Date:   &nbs p;    07/09/2010 11:22 AM
     Subject:        Re: [MAPICS-L] Product structure routings
     Sent by:        [5]mapics-l-bounces@xxxxxxxxxxxx
     --------------------------------------------------------------------------
     bob and jeff:
     perhaps a light bulb went off and guy finally came to realize that this
     mapics discussion forum at midrange has become nothing more hover board
     for
     out of work affiliates. guy is asking us for help and assistance into a
     real
     problem and you insult him because you were not able to get any easy
     billable work out of him. the few surviving affiliates remind me of
     overpriced day laborers lined up on the curb wai ting for the pickup
   truck.
     this discussion forum has become their $2000 per day marketing tool and
     they
     only need one or two suckers to fall for it.
     guy, please report any affiliate or consultant that might have harvested
     your email.
     r.k.
     On Fri, Jul 9, 2010 at 8:48 AM, Bob Voltz [6]<bob.voltz@xxxxxxxxxx>
   wrote:
     > The original poster has not responded in several days.  I wonder if he
     is
     > too busy dealing with the disaster he caused?....;-)
     >
     >
     > -----Original Message-----
     > From: [7]mapics-l-bounces@xxxxxxxxxxxx
     [8][[1]mailto:mapics-l-bounces@xxxxxxxxxxxx]
     > On Behalf Of Dale Gindlesperger
     > Sent: Friday, July 09, 2010 9:44 AM
     > To: MAPICS ERP System Discussion
     >  Subject: Re: [MAPICS-L] Product structure routings
     >
     > As a former IT Manager (and very successful XA implementer), I agree
     with
     > Jeff's comments on this completely.  In fact, I used Jeff himself a
   lot
     in
     > those situations, if only to make sure I had looked at all the various
     > options.  It's really expensive to spend time and money running down a
     bad
     > or dead-end path and having to start over later.  I've found it pays
   to
     > talk
     > to others with experience before starting a major project.
     >
    & nbsp;> If, for some reason, you don't want to use your affiliate,
   there's a lot
     of
     > other good consultants out there.  This thread is great for advice and
     > information (I use it a LOT, both ways), but sometimes you need more -
     > especially on a key project.
     >
     > Dale (Cork) Gindlesperger, CPIM
     >
     >
     >
     > --- On Fri, 7/9/10, Jeff Snyder [9]<jeffreygsnyder@xxxxxxxxxxx> wrote:
     >
     > From: Jeff Snyder [10]<jeffreygsnyder@xxxxxxxxxxx>
     > Subject: Re: [MAPICS-L] Product structure routings
     > To: "mapics midrange" [11]<mapics- l@xxxxxxxxxxxx>
     > Date: Friday, July 9, 2010, 9:11 AM
     >
     >
     > Guy,
     >
     >
     >
     > If you are indeed new to XA, you and the implementation team need the
     full
     > gambit of classes and piloting before you can determine the best
     'method'
     > for accomplishing your 'shared vision'.  Contact your local affiliate
   to
     > assist. If un-happy with their knowledge there are quite a few of us
   on
     > this
     > web that would be willing to help layout a project plan and get you
     > successfully up and running, and steer you of potholes and tangents.
     >
     >  I just feel email consulting is not going to suffice in your
   particular
     > project.
     >< BR>  >
     >
     > Just my 2 cents.
     >
     >
     >
     > Jeff Snyder, CPIM, CSCP
     >
     > Guide Technologies, LLC
     >
     > > From: [12]guyhenza@xxxxxxxxxxx
     > > To: [13]mapics-l@xxxxxxxxxxxx
     > > Date: Wed, 7 Jul 2010 13:03:15 -0400
     > > Subject: [MAPICS-L] Product structure routings
     > >
     > >
     > > I'm new to MAPICS, just started at QS/T
     > >
     > >
     > > The product structure person is entering a component item in AMEU1
   and
     > getting an message "E AM-4832 ONLY INVENTORY ITEMS ALLOWED". The it em
     that
     > does work, 702, has an item type code of 3 and an item class of R7.
   The
     > item
     > that is getting the error, 794, is item type code 4 and item class P7.
     > >
     > >
     > >
     > > I can not find any the source code for this program and the only
     manual I
     > can find just tells me how to set up user ids.
     > >
     > >
     > >
     > > How do I find what item type code and item class are allowed on a
   BOM?
     > >
     > >
     > > Regards,
     > >
     > > Guy Henza
     > > _________________________________________________________________
     > > Hotmail is redefining busy with tools for the New Busy. Get more
   from  > your
     > inbox.
     > >
     >
     >
     [2]
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:W
     > L:en-US:WM_HMP:042010_2
     > > _______________________________________________
     > > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
     > > To post a message email: [14]MAPICS-L@xxxxxxxxxxxx
     > > To subscribe, unsubscribe, or change list options,
     > > visit: [3]
http://lists.midrange.com/mailman/listinfo/mapics-l
     > > or email: [15]MAPICS-L-request@xxxxxxxxxxxx
     > > Before posting, please take a moment to review the archives
     > > at [4]http:// archive.midrange.com/mapics-l.
     > >
     >
     > _______________________________________________
     > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
     > To post a message email: [16]MAPICS-L@xxxxxxxxxxxx
     > To subscribe, unsubscribe, or change list options,
     > visit: [5]
http://lists.midrange.com/mailman/listinfo/mapics-l
     > or email: [17]MAPICS-L-request@xxxxxxxxxxxx
     > Before posting, please take a moment to review the archives
     > at [6]
http://archive.midrange.com/mapics-l.
     >
     >
     >
     >
     >
     > _______________________________________________
     > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
     > To post a message email: [18]MAPICS-L@xxxxxxxxxxxx
     > To subscribe, unsubscribe, or change list options,
     > visit: [7]
http://lists.midrange.com/mailman/listinfo/mapics-l
     > or email: [19]MAPICS-L-request@xxxxxxxxxxxx
     > Before posting, please take a moment to review the archives
     > at [8]
http://archive.midrange.com/mapics-l.
     >
     > _______________________________________________
     > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
     > To post a message email: [20]MAPICS-L@xxxxxxxxxxxx
     > To subscribe, unsubscr ibe, or change list options,
     > visit: [9]
http://lists.midrange.com/mailman/listinfo/mapics-l
     > or email: [21]MAPICS-L-request@xxxxxxxxxxxx
     > Before posting, please take a moment to review the archives
     > at [10]
http://archive.midrange.com/mapics-l.
     >
     >
     _______________________________________________
     This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
     To post a message email: [22]MAPICS-L@xxxxxxxxxxxx
     To subscribe, unsubscribe, or change list options,
     visit: [11]
http://lists.midrange.com/mailman/listinfo/mapics-l
     or email: [23]MAPICS-L-request@xxxxxxxxxxxx
     Before posting, please take a moment to review the archives
     at [12]
http://archive.midrange.com/mapics-l.
   References
     Visible links
     1. [24]mailto:mapics-l-bounces@xxxxxxxxxxxx
     2.
   [25]
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:W
     3. [26]
http://lists.midrange.com/mailman/listinfo/mapics-l
     4. [27]
http://archive.midrange.com/mapics-l
     5. [28]
http://lists.midrange.com/mailman/listinfo/mapics-l  6.
   [29]
http://archive.midrange.com/mapics-l
     7. [30]
http://lists.midrange.com/mailman/listinfo/mapics-l
     8. [31]
http://archive.midrange.com/mapics-l
     9. [32]
http://lists.midrange.com/mailman/listinfo/mapics-l
    10. [33]
http://archive.midrange.com/mapics-l
    11. [34]
http://lists.midrange.com/mailman/listinfo/mapics-l
    12. [35]
http://archive.midrange.com/mapi cs-l
   _______________________________________________
   This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
   To post a message email: [36]MAPICS-L@xxxxxxxxxxxx
   To subscribe, unsubscribe, or change list options,
   visit: [37]
http://lists.midrange.com/mailman/listinfo/mapics-l
   or email: [38]MAPICS-L-request@xxxxxxxxxxxx
   Before posting, please take a moment to review the archives
   at [39]
http://archive.midrange.com/mapics-l.
References
   Visible links
   1. mailto:bblair@xxxxxxxxxxx
   2. mailto:mapics-l@xxxxxxxxxxxx
   3. mailto:ronkral169@xxxxxxxxx
   4. mailto:mapics-l@xxxxxxxxxxxx
   5. mailto:mapics-l-bounces@xxxxxxxxxxxx
   6. mailto:bob.voltz@xxxxxxxxxx
   7. mailto:mapics-l-bounces@xxxxxxxxxxxx
   8. mailto:1]mailto:mapics-l-bounces@xxxxxxxxxxxx
   9. mailto:jeffreygsnyder@xxxxxxxxxxx
  10. mailto:jeffreygsnyder@xxxxxxxxxxx
  11. mailto:mapics-l@xxxxxxxxxxxx
  12. mailto:guyhenza@xxxxxxxxxxx
  13. mailto:mapics-l@xxxxxxxxxxxx
  14. mailto:MAPICS-L@xxxxxxxxxxxx
  15. mailto:MAPICS-L-request@xxxxxxxxxxxx
  16. mailto:MAPICS-L@xxxxxxxxxxxx
  17. mailto:MAPICS-L-request@xxxxxxxxxxxx
  18. mailto:MAPICS-L@xxxxxxxxxxxx
  19. mailto:MAPICS-L-request@xxxxxxxxxxxx
  20. mailto:MAPICS-L@xxxxxxxxxxxx
  21. mailto:MAPICS-L-request@xxxxxxxxxxxx
  22. mailto:MAPICS-L@xxxxxxxxxxxx
  23. mailto:MAPICS-L-request@xxxxxxxxxxxx
  24. mailto:mapics-l-bounces@xxxxxxxxxxxx
  25. 
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:W
  26. 
http://lists.midrange.com/mailman/listinfo/mapics-l
  27. 
http://archive.midrange.com/mapics-l
  28. 
http://lists.midrange.com/mailman/listinfo/mapics-l
  29. 
http://archive.midrange.com/mapics-l
  30. 
http://lists.midrange.com/mailman/listinfo/mapics-l
  31. 
http://archive.midrange.com/mapics-l
  32. 
http://lists.midrange.com/mailman/listinfo/mapics-l
  33. 
http://archive.midrange.com/mapics-l
  34. 
http://lists.midrange.com/mailman/listinfo/mapics-l
  35. 
http://archive.midrange.com/mapics-l
  36. mailto:MAPICS-L@xxxxxxxxxxxx
  37. 
http://lists.midrange.com/mailman/listinfo/mapics-l
  38. mailto:MAPICS-L-request@xxxxxxxxxxxx
  39. 
http://archive.midrange.com/mapics-l
As an Amazon Associate we earn from qualifying purchases.