PBED table — Independent Requirements Period Data Table

One row in PBED represents the planned quantity and consumption status for a single period of a single independent requirements record. The record itself, meaning which material, which plant, which planning version, and whether it is an SOP forecast or a planned independent requirement, is defined in the header table PBIM, not in PBED. PBED only carries the pointer back to that header plus the period breakdown: how much was planned for that period and how much of it has already been consumed by sales orders or by MRP netting. In practice PBED is what a report like the demand management overview or an SOP planning table reads when it renders a row of monthly or weekly figures for a material. Because it is a pool table rather than a transparent table, it is not always browsable the way a normal master data table is.

Always restrict on MANDT first. Never select PBED cold on PERIO or PLNMG across the whole client, the table can hold a very large number of rows once several materials carry multi-year demand plans in weekly buckets. The workable path is to look up PBDNR in PBIM for the material, plant, and version in question, then select PBED for that specific PBDNR and the period range of interest. Because it is a pool table, some generic table browsers show it through the pool container rather than as a standalone object, and ad hoc joins in reporting tools may need the pool to be unwound first. Treat direct SE16N-style edits as off limits, changes belong in the demand management transactions so that PBIM control totals stay consistent with the period detail.

Symptom: the demand management overview shows a different total for a material in a given month than what planning expects. Find the PBDNR in PBIM for that material, plant, and requirements version, then select PBED where PBDNR equals that value and PERIO matches the month. Compare PLNMG against what was entered and VMNG against what should have been consumed by confirmed sales orders. A mismatch between PLNMG minus VMNG and the on-screen open quantity confirms whether the discrepancy is a planning entry or a consumption logic issue.

PBED and PBIM are part of the classic demand management and flexible planning data model, which predates S/4HANA and has not been rebuilt around a CDS-based data model in the way MRP and production order tables have. Where classic demand management and SOP functionality is still used on S/4HANA, PBED continues to be the underlying storage. Organizations moving forward with newer demand planning tooling outside core ERP typically stop writing to PBED for new processes but the table itself has not been announced as removed.

Discrepancies in independent requirement quantities are a demand planning or MRP controller question first, not a basis or technical question. Basis gets involved only if pool table access itself is failing or performance on large selections needs tuning. Data model questions about the pointer structure between PBIM and PBED belong to whoever owns the PP-MD or PP-SOP configuration.

PBIM is the header table every PBED row depends on and is the correct starting point for any lookup. The demand management maintenance transactions (single item and collective independent requirement maintenance) write both tables together. MDKP and MDTB carry the planning file entries that the MRP run touches when it processes the requirements held in PBED, and PLAF holds the planned orders generated as a result.