In this document the methods are described for creation of custom list transactions over any M3 standard or customer-built M3 table with no coding required. If data is only needed from one single table, we recommend that you use MDBREADMI instead. MDBREADMI provides better performance but less functionality.
A new M3 Custom list MI transaction is created in 'Custom List MI. Open' (CMS015).
When creating a new transaction ID, most of the settings are retrieved from an information browser category. An existing one is either selected or a new one is created in 'Information Browse Category. Open' (CMS010). See the section about 'Information Browser Categories'.
After a new transaction ID has been created, the list can be simulated by the related option 'Simulate list' (Ctrl+11).
A transaction ID is activated by the related option 'Update MI repository' (Ctrl+20). The status is set to 20 and the settings cannot be changed anymore.
The MI repository can then be displayed using the related option 'Display MI repository' (Ctrl+22).
If any settings must be changed, use the related option 'Delete MI repository' (Ctrl+21) first.
These settings are completed per transaction ID on (CMS015/E).
A sorting of the list is based on the sorting option selected for the sorting order. All system-defined and user-defined sorting options (indexes) for the master table are available.
Use 'Browse' in the 'Sorting order' field to launch 'Sorting Order. Open' (CRS022).
The view defines the 'Output' fields. Use 'Browse' in the 'View' field to launch 'View. Open' (CRS020). Fields can be added or deleted.
A filter is used for selections. Filter fields are used as mandatory input fields. A value must be specified in the filter field and only records containing the same value as the filter are then displayed. The filters are selected starting from the first sorting field and then field by field throughout the sorting definition.
Any field from the master table can be used as a 'From' and 'To' selection field. A maximum of three selection fields can be used simultaneously. Selection fields are used as optional input fields.
A search query can be used as an input field. The SQRY field is then used as a mandatory input field. A search query cannot be used in combination with filter or selection fields.
Bookmark fields can be included as 'Output' fields. The YPGM (Browse program) and KSTR (key string) fields are added as the final output fields. The Browse program is retrieved from (MNS120) based on the master table.
Aggregation is used to accumulate several records into one record. Aggregation levels are used to indicate how records in the list will be aggregated. Key fields that are not included in the aggregation level will be aggregated. Aggregation levels are selected starting from the first key field and then field by field throughout the sorting option definition.
This is used to insert a subtotal record if the value in a specific key field is updated. Any key field in the selected sorting option can be used as break level for subtotal.