New extension for SE16N transaction

I’m quite sure very few of you know about this brilliant extension to an old SE16N transaction we used to work with almost daily.

Today we have a new solution, mostly developed for HANA database, but it still works and brought some new features to the classic ERP on old-way databases. 

Meet SE16H instead of SE16N. It has number of unique features like presort order on the selection screen, text tables to read field descriptions, building JOIN tables on-fly. 

Play with it and find it more convenient than old granny SE16N.

Decoupled infotypes

Have you seen Decoupled infotypes branch in SPRO? Opened it several times, closed and opened again. No results. Looks really complex. Couple days ago I decided to make a move and figure out what’s that.

Main thesis’ are, which I’ve found in different sources:

  • PA20/30 works with both old and new technology. PM01 transaction creates infotypes with both techs. Also it knows how to migrate infotype.
  • Main advantage is decoupled infotypes more look like classic MVC programming model, where M = Model, V – View, C – Controller. Different levels of responsibility and strong communication between levels. It’s convenient model for developers.
  • For end users it means faster interaction, more speed, new glamour features like all data in one screen, fastest ad-hoc reporting in BW way and etc. HR renewals, let’s say.
  • Some ESS/MSS services don’t work with old infotypes anymore. You need to migrate. Globally SAP advise to start migration to decoupled infotypes right away.

Generally speaking what’s decoupled infotypes? It’s a way to save all data in transparent tables instead of packing them into something else like cluster tables. Just imagine how much time do you need to extract one wage types from cluster table (load everything, unpack all internal tables, loop through them for a record) or just do one select statement on indexed table? It’s times of time!