Manage mandatory/optional fields for movement types
You can supress a field in MIGO transacction or make it mandatory/optional
LOGISTICS KNOWLEDGE
7/13/20262 min read
The system is working properly as a check is done on both tables T004F (FI) and T156B (MM). These two tables define what data is required, optional or supressed when using MIGO transaction. The problem is due to inconsistent settings of field statuses of account groups versus material movements. The following schema shows which combinations are valid and which are not. For instance: if a field is suppressed on a material movement and the same field is mandatory on an account group, then a material document cannot be posted
Use SAP standard report RM07CUFA in SE38 tcode to quickly compare MM and FI field statuses. It shows the inconsistencies and allows to directly jump to respective configuration and update the settings. Otherwise you should compare the field statuses configuration entering transactions OBC4 for FI and OMBW for MM movements. After running the RM07CUFA report, as shown in the example below, inconsistencies are clearly marked in red, so you can quickly click on them to correct them as needed.
On the next screen, you can correct the necessary settings and save in a transport request. These changes in particular can also be made in transaction OMBW.
You may have encountered the error M7 093 with text "Fld selectn for mvmt type & / acct & differs for & (&)" or one of its variations in another language, as shown in the table below. This is a standard message that SAP issues when there are field selection inconsistencies between Inventory Management movement types and Financial Accounting (FI) G/L account field status groups.
Beware that this configuration should also be consistent with the settings made in path Materials Management > Inventory Management and Physical Inventory > Settings for Goods Movements (MIGO) > Field Selection per Movement Type.
© 2024. All rights reserved. Functitech