Charley,
Cameleon builds a config id based on the BOM and routing required to
build the specified configuration. So if 2 customers request the
identical configuration, Cameleon builds the same configuration -and
config id- and the config BOM & routing is sent to / stored only once in
EPDM.
All the rules and "raw data" to build configurations is stored in the
Cameleon configurator engine. A specific configuration consists of a BOM
and routing (or more than one, if a complex product requires multiple
product structure levels) that are loaded to EPDM as alternate item
processes, and linked to the config id in the customer order line item.
Keith Reichenbach | Infor XA Product Development | 678-319-8276 |
keith.reichenbach@xxxxxxxxx
-----------------------------------------------------
From: "Charley Simpson" <csimpson@xxxxxxxxxxxxxxxxxx>
Subject: [MAPICS-L] Cameleon questions...
XA R6
Howdy and Happy Friday!
Not being a big fan of RTFM, I thought I'd ask my questions here to see
if I could short-cut my search.
While familiar with other configurators, I have not worked with Cameleon
and we have no one on staff here who truly understands its structure,
its limitations, etc.
I am being told that Cameleon does not "re-use" an ID number and
structure (sorry if the terminology is incorrect) if a user, during a
CSM session, makes choices that exactly match a set of choices
previously made and shipped.
I am also interested in finding out exactly how the configs are ID'd and
stored. Is it using EPDM files as the repository for the config
structure?
TIA for any assistance.
Charley
Charley Simpson, CPIM
Director, Material Planning & Logistics
805-426-3410
www.turboneticsinc.com <
http://www.turboneticsinc.com/>
*** Please note that the information contained in this message may be
privileged and confidential and protected from disclosure. If the
reader of this message is not the intended recipient, or an employee or
agent responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution or copying
of this communication is strictly prohibited. If you have received this
communication in error, please notify us by replying to the message and
deleting it from your computer. Thank you. Turbonetics, Inc. ***
------------------------------
midrange.com
