MRP looks like its not considering the BoM

Hi John,
thanks as always for getting back to me,

So Im learning hear so please bear with me, ive got my process down as

  1. Update recycle thresholds
  2. Process MRP (As above)
  3. MRP Recalc
    Done

I then presume at this point,

  1. Calculate global scheduling
  2. run global scheduling

that should then “shuffle the dates” to match the “interdependencies” based on BoM levels material seq numbers etc.??

Thanks John Super appreciate you :pray:

You also need to run Generate Shop Capacity Process before Calculate Global Scheduling Order.

Yes, that will line up the dates in the correct order as long as your MOM is built correctly.

1 Like

Give me a few hours, im just working with our dedicated consultants on removing the plan as assembly flag from our Method, to see what that does, and then ill give this a try 100%

thanks boss

That will make all of your subassemblies get created in the Job instead of splitting them out onto a separate job. That is if the system has calculated that there will be a shortage.

If you do not have common components across your products, you most likely want Pull as Assembly. If you do have common components and want to leverage mins on them, you want Plan as Assembly.

Well John,
Before:

After:

That seems to have shuffled the order of them around, and its deffo made it “right” showing some overlap on jobs and my schedule start dates being blank didnt help in the calculate or global scheduling options but its doing things, if i re-run again, and put a week in advance ill see what it does to the demand, but, this is looking somewhat promising

John ill report back got 2 days of consultancy and ill bring this up to try and add in my workflow im building out for this, but thanks mate, how do i send you a pint :smiley:

1 Like

John, Not sure why but all of a sudden ive got Sub-Assemblies inside my MRP jobs? would you know why ive got that all of a sudden?

Ive not changed the pull/plan flags, the revisions havent changed but MRP is running and im getting jobs with subassemblies in now where i never have before…

Any ideas?

It could be a bunch of things, unfortunately. Are any of those parts Non-Stock or Phantom? Double check if they are Pull/Plan. What happens when you firm the suggestion?

1 Like

Ive changed nothing thats my head masher here… had my database refreshed to yesterday to give it a trial run again see if i get the same result… that i didnt get yesterday talking through all the above with everyone

sometimes it baffles me the behaviour in the application

If you refreshed the DB, what did you refresh from?

Morning All,
Im slowly growing into Pull as assembly, its taking some convincing on moving the WIP but if we do use sub assembly, yes its making sense all round and we can really leverage the use of the system vs the Plan as assembly, also it helps with this issue

I am however a novice on the WIP Movements, what essentially we are trying to acheive is:
We have machinery that can cut thousands of parts automated, we want to cut these in Min lots, but in Multiples of so we can load 1 pack of material in, and get the rounding right at that machine

we want to then consider the over-run quantity here, and our onhand inventory to generate pull quantities from stock and the movement requests “pick” but then the over run on the job we have just done, be considered as a material request to inventory

However, we cannot always move to the job quantity to the next job, as there is limited space, and we would like to then move the wip “periodically” or “trigger a request” to move WIP from 1 location (where its stored temporarly) and trigger movement requests as required to the machine thats requiring the matieral

so 3 things happening, our thousands of, are going to be some for job, some for stock, some pulled from stock,

Then 2 things, we put the WIP in our “holding area” as a movement request, we then start the job, and replenish the materials through movement requests, from the “Job WIP”, but the over-run quantity was put into inventory, that way we can move over-run to 1 area, and WIP items to another.

we want to trigger it all through MRP, Lots, Multiples, Movement Requests and keep it slick on that side of things, so shop floor users can do the doing, logitstics teams do the moving, as prompted… all in WIP materials…

I hope thats clear enough, and hope someone out there is experiencing the same thing to give us a hand :smiley:

Thanks all as always!