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.
Selected item
020 · Print Goods Received Note
- Menu type
- P program launcher · strong signal
- Raw launch
GOODS_RECIEVED_TST- Resolved key
GOODS_RECIEVED_TST- Suffix
- none
- Security groups
- DEV, GAT, CAC
- Before
(none)- After
(none)
Program target
Open program detail- Description
- GOOD RECEIVED NOTE TEST
- Program type
- DSP
- Base table
- STK_DETS_GATE
- Field count
- 26
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
Read ordered entries from ZM_MENU for the chosen ZM_KEY.
Split ZM_PGM into a base key plus any launch suffix.
Match the base key to a submenu, a program in ZP_PGMS, or a report in ZE_ENQ.
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.
NEW_DEL contains 2 rows.
Row 020 currently resolves as program.