(Configured) Make-to-Order Jobs using Next Job, not Order Release for Job Number

We have set JCSyst.QuickJobID = OR (Order Release) in Company Configuration → Modules → Production → Quick Order ID:

It is our understanding that, for make-to-order parts, this should create jobs with job number format: SalesOrder-Line-Release.

When running MRP, we get job suggestions for these make-to-order parts with the usual number format (in our case UF00000xxx) which, when firmed, grab the next job number.

When using the Order Job Wizard on the Sales Order, we get the desired SO-Line-Release job number format.

We would prefer to use the SO-Line-Release format to distinguish make-to-order from make-to-stock jobs.

The offending parts are configured, which are the only make-to-order parts we use.

Any suggestions on how to change this behaviour?

Thanks very much.

1 Like

MRP is going to use the next job number every time, I believe. It is still linked to the order release via the JobProd table.

Is there a reason MRP is used instead of Order Job Wizard? I’ve also automated Order Job Wizard before, if it’s just a matter of the time it takes to make the job. I used certain markers set in the configurator doc rules to show that the rel is “ready” to have the job created. Then a scheduled function to execute Order Job Wizard and GetDetails.

1 Like

Thanks @kve.

We also produce a lot of make-to-stock materials. It’s preferable to use the same procedure (MRP) for make-to-order materials to keep the workflow consistent for our materials planning team. It would be ideal to have the job suggestions from MRP for make-to-order distinguished by their job # format.

We wanted to be sure that we weren’t missing a system setting before we explore any customizations.

1 Like

I think you’re missing another similar setting in Company Configuration on the Production > MRP tab called MRP Job ID. This should be set to Order Release. When this is set, MRP will create unfirmed jobs using the Order-Line-Release.

2 Likes

@mhellwig, that’s it, works perfectly now. Thanks very much.

1 Like