Determining allowed fields/components
Last updated
Was this helpful?
Last updated
Was this helpful?
Most of the screen configuration relies on referencing fields / components available within pre-defined structures that have been set up to work with each screen. Full details of which structures can be used as standard for a particular app/screen are provided in the configuration guide for the relevant app and can also be found using transaction /TCTM/WM_AMD_DTYPES.
Pressing F4 while the cursor is in the field will show the fields that can be used for the structures relevant to the particular screen. However, the following prerequisites must have been performed in the system in order for data to be available to display:
Table /TCTM/WM_DU needs to be populated with data for the particular app transaction and screen.
This is achieved by someone having set their userid with PID /TCTM/WM_SAVE_DU and then running through the app transaction in PreBilt.
The first time the app transaction is processed through the various screens by the user with the PID set, the data is written into the table /TCTM/WM_DU, and thus available for the F4 lookup.
The primary structure is the main structure that builds a table containing ancillary data from the secondary structures (structures with a prefix). Fields should be used from the secondary structures as best practice, and those fields should be in the format [prefix]-[field]. Fields in AMD with a prefix should not require a class.
The available structures can be viewed via standard SAP transactions (e.g., SE12). Enter the structure in the ‘View’ field and select ‘Display’:
The available fields/components will then be displayed on the left. The structure and component can be used to add a field as needed into an app screen.
In the example below, if structure /TCTM/LQUA was available as a structure in a particular app screen and the field ‘Blocking Reason’ (SPGRU) needed to be added, either add SPGRU or LQUA-SPGRU into the app master data for that screen.
