Skip to main content
Nov 9, 2016 12:53 AM UTC
Solved

Do Not Plan.

We are new to SPM only two months in since going live.  We are coming from the Xelus Plan Platform.  I have many many questions but for now I will address just one.  I hoping someone can tell me how to code a part so it does not plan.  Even though the part may have demand I do not want to see this part populate the work queue.  I want it to be invisible if you will.  I have made certain parts inactive or taken it off the ASL but they still populate the work queue.  If anyone is familiar with Xelus Plan All I needed to do is flag it not to plan (Do Not Plan Per Planner) This part wouldn't plan, update, forecast or populate the work queue until the flag was removed.  Very simple.  In SPM nothing seems to be simple.

I would appreciate any help/feed back from those of you using the SPM currently.

Thanks,

Jeff

nvermaAnswer
Nov 15, 2016 8:06 AM UTC

Hi Jeff,

Did you try making Part Active "No" and run core processes i.e. Sync DB, Order Plan Sync DB, Review process for Default segment? Also create a support ticket to get timely response on such questions.

Thanks,

Narendra

6 replies

nvermaAnswer
Nov 15, 2016 8:06 AM UTC

Hi Jeff,

Did you try making Part Active "No" and run core processes i.e. Sync DB, Order Plan Sync DB, Review process for Default segment? Also create a support ticket to get timely response on such questions.

Thanks,

Narendra

jvelascoAuthor
Nov 21, 2016 6:57 PM UTC

Narendra,

I have done this but on some parts it changes back to active and they still populate in the work queue.  But I'm testing this again on one part to see what happens.  I've also ran the db sync.

Thank you for your help!!!

Jeff

Nov 16, 2016 9:39 AM UTC

Good Morning Jeff,

I think what you may be wanting to do is to disable the part, or pair within the application. You can do this at multiple levels. If you want to disable the part for all locations you can configure the Active setting at the part level to have a value of No.

You can also create a SKU record which will be at the pair (Part / Location) level and set a similar setting. You may need to set this for multiple pairs depending on how you want the pair to behave across the application.  The setting at the SKU level is called SKU Active and would also need a value of No


You may also want to review your ordering parameters as you may have the setting Plan Non-Asl Pairs configured with a value of Yes, This could explain why you didn't see a change after removing the pair from the ASL.


As per the suggestion from Narendra, you may need to run the core processes after making changes.

If you are still facing challenges with the behaviour please can you share further a detailed example? Alternatively you may wish to open a support ticket should you still be facing some challenges with this topic.

All the best,

Alec.

jvelascoAuthor
Nov 21, 2016 7:00 PM UTC

Alec,

As I mentioned to Narendra I have tried to make the parts as not active.  But I will try the SKU Active setting and check the ordering parameters to see if it is planning for non-ASL parts.

Thanks,

Jeff

Mar 8, 2017 9:25 AM UTC

One way is to create a Planning Parameter called 'Do Not Plan'. Configure this parameter to not plan. Create a segment these parts and assign to this parameter. Make sure that this parameter is at the top of the parameters screen so it is handled first and the pairs are eliminated from planning.