LX Source Code Non-inclusion

. .
. . .
<vendor>

The expert internal programming staffs employed by long-time users shall be
very disappointed by this development. If it's true, it's tragic ...
especially for a company like mine which (for two decades) has been in the
business of helping BPCS/ERP LX users customize functionality to be in
harmony with distinct business process needs. Two Illustrations:

Using receipt of goods to trigger automatic invoice creation for A/P
payment processing. We couldn't deliver our Hop, Skip & Jump
accounts payable product to achieve that efficiency unless we could
tinker with points in a customer's vanilla ACP source code.

I can't think of a BPCS/ERP LX shop that hasn't had to tinker with
something to process customer orders "their way." I recall one
firm was required to invoice their government-related customers at
a price that was at least as low as the price given to any other
customer
over x time periods. Try configuring that in vanilla ERP LX.

Never fails ... if we call 10 BPCS/ERP LX users, we shall surely find at
least two who have decided to move to SAP or Oracle since the last phone
discussion. A "no source code policy" isn't going to slow down that exit
velocity.

Peace,
Milt Habeck
Unbeaten Path
www.unbeatenpath.com



</vendor>






From: On Behalf Of Bill
Sent: Friday, September 02, 2011 11:24 AM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] LX Source Code Non-inclusion

In our negotiations with Infor regarding upgrading to LX, I was surprised to
hear that the source code is normally no longer provided to licensees. To me
this sounds like a gigantic hindrance but maybe I'm misunderstanding the
impact of this non-inclusion.

Can I hear from some of you on LX as to your feelings to this policy?
How has it hindered you? Have you even been negatively affected by not being
able to get to the "guts" of the programs?

Bill