High-impact Simplification Items

A Simplification Item is SAP's record of something that changed in S/4 — a table redesigned, a field removed, a process reworked — and a handful of them account for most of the pain a custom-code base feels in a conversion. The biggest are data-model changes. Pricing moved from the cluster-era `konv` to the transparent `prcd_elements`. Inventory's `mseg` is now augmented by the `matdoc` material-document table. The FI line-item world that used to live in `bseg` is subsumed by the universal journal `acdoca`. Output determination that ran on `nast` is replaced by the new Output Management framework.

Code that reads these tables directly will frequently still compile and even run on 758 for backward compatibility, which is exactly why these items are dangerous: nothing screams, but the source of truth for current data and analytics has moved. Reading `bseg` for new reporting, for instance, can quietly miss postings that only exist in `acdoca`. So the readiness variant flags the direct dependency precisely so you treat it as a decision, not an accident.

The clean remedy is the released interface views SAP ships over the new model — for the universal journal that means `I_OperationalAcctgDocItem` and its siblings in the `I_*` family, which are released (C1). Pointing a legacy `select` at the released interface view instead of the raw table gets you upgrade-safe, contract-backed access without rewriting all the surrounding logic at once. (SAP also ships old-name *compatibility views* that preserve the legacy table shape for a lift-and-shift; the durable target is the released interface view.)

ABAPselect * from bseg
  into table @data(lt_items)
  where bukrs = @lv_bukrs.

ABAPselect * from i_operationalacctgdocitem
  into table @data(lt_items)
" ... a released (c1) interface view over the acdoca universal journal
  where companycode = @lv_bukrs.

Source notes: clean-core-curriculum §8.6