In my last
post I wrote about a suite of Data Browser related tcodes. Those SE16* tcodes
exits in SAP systems that runs on S/4HANA Foundation such as SAP S4/HANA. This is
because they are part of software layer SAP_APPL or SAP_FIN. However, the tcodes mentioned were
ported to other software layer - SAP_ABA. Thus, are available in BW (as well as
SCM, CRM, Solution Manager, etc.) systems as well.
What is different is actually the particular
tcodes it self. In S/4 they follow SE16* but in other systems they follow S416*
or S4H16* names.
|
SAP_APPL name |
corresponding
SAP_ABAP name |
description |
|
SE16N |
S416N and S4H16N |
GTB |
|
SE16H |
S416H and S4H16H |
Enhanced GTB |
|
SE16D |
S416D and S4H16D |
GTB Display Mode |
|
SE16S |
S416S |
GSS |
|
SE16S |
S4H16S |
GSS Multi Text |
|
SE16SL |
S416SL |
GSS Column Based |
|
SE16SL |
S4H16SL |
GSS Depend Read |
|
SE16N_ROLE |
S416N_ROLE |
GTB Role Maintenance |
|
SE16J |
S416QL |
GTB Query Launcher |
|
SE16S_CUST |
S416S_CUST |
GSS: Maintenance of Search Patterns |
|
n/a |
S416S_DEP |
GSS: Maintenance of Dependencies |
|
n/a |
S416CD |
GTB: Display Change Documents |
GTB stands
for Generic Table Display
GSS stands
for Generic Smart Search
More
information:
2140828 - GTB: Documentation of
generic table display functions
1636416 - CO-OM tools: Functions
of transaction SE16H
2124497 - Downport of the SE16*
transactions to the software layer SAP_ABA
S416CD GTB: Display Change Documents
S416D Generic Table Browser Display
Mode
S416H Enhanced Generic Table Browser
S416N Generic Table Browser
S416N_ROLE GTB: Role Maintenance
S416QL GTB: Query Launcher
S416S Generic Smart Search: Text
Input
S416S_CUST GSS: Maintenance of Search Patterns
S416S_DEP GSS: Maintenance of Dependencies
S416SL Generic Smart Search (column
based)
S4H16D Generic Table Browser Display
Mode
S4H16H Enhanced Generic Table Browser
S4H16N Generic Table Browser
S4H16S Generic Smart Search: Multi Text
S4H16SL Generic Smart Search: dependent
read
