Metadata-driven navigation
Menu simulator
Browse the live menu model from ZM_MENU, inspect what each item resolves to, and preview report-backed entries against the replicated data schema when live access is enabled.
Menu controls
108 menusCASHIERS
4 itemsSelected item
030 · Cashier Transaction Type
P
program
- Menu type
- P program launcher · strong signal
- Raw launch
CASHIER_TRANS_TYPE- Resolved key
CASHIER_TRANS_TYPE- Suffix
- none
- Security groups
- DEV, TST
- Before
(none)- After
(none)
Program target
Open program detail- Description
- A CASHIER TRANSACTION TYPE MAINT.
- Program type
- MDL
- Base table
- CASH_TRN_TYPE
- Field count
- 51
How it works
1869 rows mapped
The simulator follows the Freshmark metadata chain instead of hard-coded routes. Each click starts with
ZM_MENU, resolves the launch target, and then cross-references the matching program or report definition.
Menus
108 distinctZM_KEY groups
Programs
1763 fromZP_PGMS
Reports
142 fromZE_ENQ
1
Load menu rows
Read ordered entries from ZM_MENU for the chosen ZM_KEY.
resolve
2
Parse launch target
Split ZM_PGM into a base key plus any launch suffix.
cross-reference
3
Classify the item
Match the base key to a submenu, a program in ZP_PGMS, or a report in ZE_ENQ.
inspect
4
Open detail or preview
Submenus expand the tree, programs show metadata, and reports can run a limited live preview against replicated data.
program
Runtime screen or workflowProgram-backed items resolve through ZP_PGMS and field metadata in ZX_PGMS_FIELDS.
report
Queryable report definitionReport-backed items resolve through ZE_ENQ and can expose the base table, filters, and preview SQL.
Menu type key
7 codes observed
These are the one-letter codes from ZM_MENU.ZM_TYPE. Where the meaning is still inferred rather than proven,
the legend says so explicitly.
Current path:
CASHIERS contains 4 rows.
Row 030 currently resolves as program.