MRP and Customer Part Numbers

, ,

When MRP runs and creates Job Suggestions based off of Demand, should it be using the in-house PartNum (OrderDtl.PartNum) or the Customer Part Num (OrderDtl.XPartNum) for job creation?

I ask because it seems that for one of our facilities it is using the XPartNum, which is what we want. But at one of our other facilities it is using PartNum. I’ve poked around in Site Configuration and Site Maintenance and haven’t found anything that stands out as a setting for this. I don’t know if I am looking in the right area or if I should be poking around elsewhere.

I initially went to looking at the Site Config because it looked site dependent. But, it may be Customer dependent…this customer is only handled at this one facility.

Anyone have any thoughts?

2 Likes

I know in the Customer Part Cross Reference screen, there is a setting that the system uses when determining how to show it on reports (specific to each customer). Does that also maybe apply in this case? I’m not sure. Just thinking out loud.

3 Likes

I was thinking the same thing. I always thought it was solely for how you wanted them to display on Quotes/order Acks, etc… but perhaps it plays into MRP?

3 Likes

That is the field you are speaking of…I forgot all about that.
image

I just changed that to Print as Main Reference and am rerunning MRP on one of those parts to see what happens. I’ll keep y’all posted. :slight_smile:

2 Likes

Another place to check… Since you’re saying it may be customer specific…

On the Customer record, if you’re using “Ship-To”, there is a check box under Ship-To > Demand labeled “Use Customer Values”.

The field helps states: “Indicates if the demand fields from the customer should be used.”

NO CLUE if that has any impact… just stumbled on it. Perhaps worth a look.

1 Like

That didn’t seem to do it. The existing unfirm job was deleted (as expected) but the new unfirm job still did not have XRefPartNum populated.

I just checked the Customer config, and that is already selected.

:thinking:

Knowing me there is something very obvious that I am overlooking and it is just staring me right in the face.

And on the Customer > Documents > Detail tab, it is showing “Use Customer Part” for the Selected Options:
image

Just throwing out a couple of questions.

Did the part that you re-ran MRP for have a cross reference to a customer number?

What is the demand link for both parts? I’m wondering if it will use the customer part number when it is make to order but not when make to stock?

2 Likes

Yes, they are cross referenced.

That is what I am trying to look into now. Where would that be offhand? :slight_smile:

Check the header in Job Entry. The demand summary grid is usually the default grid on the botoom.

That is showing that it is Make to Stock:
image

image

I’m betting that the job should be Make to Order, shouldn’t it?

What about the job in the other site that is using the customer number?

This is an older job for the same customer. It was from a different plant. That plant is now closed and the orders are being handled at a different facility which is the one not showing the XPartNum.

This Job does have the XPartNum populated correctly.

It is also Make to Stock :face_with_diagonal_mouth:

image

I just know Epicor sets JobHead.XRefPartNum and JobHead.XRefCustNum it pulls it from OrderDtl.XPartNum and only shows the XPartNum on Reports like Packing Slip, Invoice.

image

That’s what I thought too…The Sales Order has OrderDtl.XPartNum populated, but when MRP runs it does not seem to be pulling that OrderDtl.XPartNum.

It is baffling me.

It will only do so during initial creation, from what I can tell. If the Job already exists then it won’t. Something about Reuse JobNum

I went and created a new SO for that Customer and Part. XPartNum was populated on OrderDtl. I re-ran MRP on it. Recycle MRP Jobs was not checked when I ran MRP. And we do not reuse Job Numbers.

I was hopeful, but cross reference was not set on the Job.

OK - this has me curious. There is a field in PartPlant called XRefPartNum. Is this perhaps where one site is populated and the next is not? What has me confused is that if the job is make to stock, it has no relationship with an order to get that XPartNum from.

Good thought with PartPlant, but none of the Parts in PartPlant have XRefPartNum set. Not just the parts for this customer, but ANY parts in the PartPlant table.

Yeah I don’t see any way to access that so I was really reaching.

So your job demand panes used to show a customer part number instead of your part number? Would that show as the part or the cross reference on the top of your job entry (like @hkeric.wci posted)? The fields on the Job Demand are driven by JobProd and JobPart tables. I don’t see any reference to customer xrefs in there. But there is in JobHead. I didn’t know that it would show customer part # in those areas.

Taking a different angle of approach: is it possible you actually have the customer’s part number loaded in your part master and maybe a default substitute part situation going on? Thinking outside of the box a little here.

1 Like

The Job would always show our Part Number in the Part Number field, and the Customer Part Number in the Cross reference field.

I thought about that as well:

SELECT * FROM Erp.Part WHERE PartNum IN (SELECT XPartNum FROM Erp.CustXPrt WHERE CustNum = 23)

No results returned, heh.

This rabbit hole keeps getting deeper.