Adding Data/Criteria to a MRP system

  • Thread starter Thread starter RD
  • Start date Start date
R

RD

I have a need to analyze existing sales data against previous performance
periods (model years, fiscal years, quarters, months, weeks, etc.). My
management team has always reviewed historical sales numbers using the Model
Name convention (1700CC) versus Part Number (52017). Prior to the
implementation of the new/present MRP system we had a customized order entry
system that just included a products table. Sales Order's were placed with
the use of Descriptive based drop-down fields, which usually was a model
name. The new system forces us to use a P/N in place of a Model Name,
consequently, reporting has become very complex. The MRP system also doesn't
contain a field that we can simply call model name. Therefore, I can no
longer create a report that generates the number of units and dollars sold
by model name. Instead, I have to use a p/n.

Is there a way to create an association between the two (P/N and Model Name)
for both current and previous models? Keep in mind that I cannot change the
MRP structures without upsetting the MRP vendor.
 
RD,

Although you can't or don't want to change the MRP structure
( good idea! ) you could create another table to hold your
Models and their associated P/N's and then create a query to
tie the two together as a basis for your reports.

tblModels
ModelName PartNumber ModelDescription
1700CC 52017 "Blah, Blah"

--

Gary Miller
Gary Miller Computer Services
Sisters, OR
________________________
 
Dear RD:

You should be able to create a new table to make the association of
P/Ns with ModelNames. Add all the old Model Names to this table. You
should be able to accomplish this with a query.

You may have to manually assign the new P/Ns to these, but some
computer support may be possible to make this easier.

At this point you may have multiple ModelNames for some of the P/Ns.
You may want a facility to choose the preferred ModelName for each
P/N.

There may also be P/Ns at this point without a Model Name. You can
query to get a list of these and then add Model Names for them as
needed.

Whether you can add a table to the MRP database or if you must create
a new database for this is a good question. Working with this in a
different database will be a little more difficult, and would preclude
creating relationships. But it should still be doable.

I consider this response of mine to be a bit thin, just an outline
really, but your question is not really full of details. The whole
thing would need some serious study, no doubt about it.

Tom Ellison
Microsoft Access MVP
Ellison Enterprises - Your One Stop IT Experts
 
Back
Top