How to Change the MPS Bucket Size in EDGEBIC

Changing the MPS bucket size in EDGEBIC is a view control on the master production schedule grid: pick day, week, or period from the bucket dropdown and refresh. In EDGEBIC by User Solutions one grid row equals one bucket, so the choice decides how demand and supply are grouped, and therefore what you can see and decide. Crucially, switching the view does not re-bucket your committed build quantities, because those are stored against a specific granularity. This guide covers the switch and the storage detail behind it.

For working the grid as a whole, read how to work the MPS grid. For what the grid represents, see the master production schedule explained. This is documented behavior of EDGEBIC; the full task set is in the how-to hub.

Before You Start

• You need a product loaded on the MPS grid.
• Decide the granularity that matches the item's demand rhythm.
• Understand that committed quantities are stored per granularity, so switching the view shows a different set of commitments.

Step 1: Open the Grid for the Product

Open the MPS tab and select the product. The grid loads at whatever bucket size it last used.

Step 2: Set the Bucket Dropdown

Set the Bucket dropdown to your choice:

Step 3: Refresh

Click Refresh. The grid regroups to the new granularity. Rows collapse or expand accordingly: seven day rows become one week row, and a month of days becomes one period row.

Matching the Bucket to the Item

The right bucket size follows the item's demand rhythm, not a house standard. Two worked cases show why.

A fast mover with daily order flow keeps stocking out mid-week under week buckets. The reason is arithmetic: a week bucket sums Monday through Sunday into one row, so a Tuesday dip that recovers by Friday nets positive across the week and never shows. Drop that one product to day buckets and the Tuesday shortfall appears, with enough warning to build ahead of it. That single product on day buckets, alongside everything else on week, is exactly the right mix.

A slow, high-value item that orders monthly is the opposite problem. Viewed in day buckets over a quarter, it produces roughly ninety near-empty rows, and the one day that matters is buried in noise. Switch it to the period bucket (a calendar month) with a horizon of a few periods, and ninety rows become three or four meaningful monthly decisions that match how the item actually orders.

What Changes When You Change It

The grouping changes, which changes what you can see. A week bucket sums the week into one row and hides an intra-week dip that a day bucket would expose. A day bucket over a long horizon buries a monthly item in dozens of near-empty rows. The demand column, projected balance, available-to-promise, and the suggested quantity all regroup to the new granularity, so the arithmetic you read is now at that grain.

What does not change is your stored commitments. A committed build quantity is stored against the product, the bucket type, and the bucket date together. A day commitment and a week commitment for the same period are separate records. So switching the view to week does not convert your day commitments into week ones; it shows the week records and hides the day records. The day records are intact and return when you switch back. For the commitment mechanism itself, see how to firm an MPS quantity into a job.

This storage rule also enables a deliberate mixed plan. You can commit daily builds for the near term, where firm customer commitments demand day-level precision, and weekly totals for the far term, where that precision is false anyway. Both sets of commitments coexist because they carry different bucket types. You view each by toggling the dropdown: day mode shows the daily commitments, week mode shows the weekly ones. The one caution is that firming a weekly commitment produces an order due on the week's Monday, which will not align with a specific daily due date, so prefer daily commitments for firm customer promises and reserve weekly ones for the softer far horizon.

Bucket Size and Horizon Work Together

Bucket size never travels alone. The grid also has a bucket count, and the horizon you see is the bucket size multiplied by that count. Change the granularity and the same count now spans a different length of time: 14 day buckets is a two-week window, while 14 week buckets is a full quarter. So after switching bucket size, check the count too, or you can accidentally shrink a quarter-long view down to a fortnight, or blow a two-week view out to months of rows. The two controls are the pair that decides what the grid shows, and they are worth setting as a pair. For the count side, see how to set a planning horizon.

How to Check It Worked

Confirm the grid now shows rows at the granularity you picked: one row per day, per week, or per month. If you had committed quantities at a different granularity and they seem to have vanished, switch the bucket back and confirm they reappear. Their disappearance under a different granularity is the storage behavior working as designed, not lost data.

Common Mistakes

• Applying one granularity as a house standard. Bucket size is a per-product choice. A week standard hides mid-week stockouts on fast movers, and a day standard drowns slow items in noise. Match the bucket to the item.
• Switching mid-cycle and losing track of commitments. Because commitments are stored per granularity, flipping the view mid-plan changes which commitments you see. Pick a granularity per product and stay on it.
• Forgetting to refresh. Changing the bucket dropdown takes effect on refresh. Change the count too and the same applies.
• Reading a week bucket as safe when a day within it stocks out. A week that nets positive can still hide a Tuesday shortfall. Drop to day buckets to check anything time-sensitive.

What Comes Next

Bucket size and horizon are the two view controls that decide what the grid shows, so pair this with how to set a planning horizon. To read the shortfalls the grid exposes, see how to see net requirements for a product. The how-to hub links the rest.