LIS SIS Reporting Replaced by Embedded Analytics

Classic ECC behaviour

S/4HANA behaviour

Project impact

• Long-standing custom standard analysis reports used by sales or purchasing managers stop being maintained, and no one owns the decision to rebuild them until a month-end close surfaces the gap
• Interfaces and downstream Excel or Access tools that select directly from info structure tables break silently if those tables are no longer populated for the relevant scope, or simply go stale
• Authorization roles built around old LIS/SIS transaction codes become dead weight and do not map to the new CDS-based analytics roles, so access has to be rebuilt rather than migrated
• V3 background collective update jobs left running after cutover consume batch resources for consumers that no longer exist, and this often goes unnoticed for months
• Business users trained on drilldown-style standard analysis find the interaction model of Fiori analytical apps unfamiliar, and adoption stalls without dedicated retraining
• BW extraction built on LIS communication structures for the same logistics areas is affected by the same underlying change and needs its own review, not just the front-end reports

Migration actions

• Inventory every active info structure, standard and self-defined, including who consumes it and how often it is actually used, not just how often it was originally built to be used; this inventory is a pre-conversion gate, not optional cleanup, because it determines what silently stops mattering
• Check the simplification item relevant to the target release for any restriction on the specific info system in use (SIS, PURCHIS, PMIS, QM-IS, and so on), since availability is not identical across all of them
• For each info structure still needed, decide explicitly: keep running in compatibility mode for a defined transition period, or rebuild as an embedded analytics query or Fiori app now
• Rebuild the reports that matter as CDS-based queries or analytical apps and run them side by side with the old figures for at least one full close cycle before cutting business users over
• Migrate authorizations to the new analytics role model rather than trying to reuse old LIS transaction authorizations
• Decommission V3 collective update jobs only after confirming no remaining consumer depends on the populated info structure, and confirm this in writing with the business owner

Whose problem this is

Common pitfalls

• Assuming LIS will keep performing acceptably forever because the tables are still there; these tables are legacy pool structures, not optimized for HANA, and volume growth exposes that gap only in production
• Discovering during the first post-cutover month-end close that a critical manager report was built on a self-defined info structure nobody had documented or included in the inventory
• Leaving V3 collective update jobs scheduled after the consuming reports have been retired, so batch capacity is wasted on updates nobody reads
• Expecting the new CDS-based figure to match the old SIS figure exactly; aggregation timing and rounding logic differ enough that reconciliation differences appear at the first real close and get mistaken for a data error rather than a design difference
• Underestimating how many hidden consumers exist, particularly desktop macros and personal query tools pulling straight from S0xx tables, which only surface once they stop returning data