SAP MM在ML81N事务代码界面报错- Customizing incorrectly maintained –之对策
笔者在很多项目的SAP系统里都遇到这个信息，在ML81N为服务采购订单创建service entry sheet的时候。这个信息，看起来说是有错误，并不影响我们正常的执行完毕ML81N，不过每次都要弹出这信息来，让人很是烦恼！
如今笔者在1909版本的S/4 HANA系统上再次遇到这个报错信息。
笔者很是不解，如果是SAP系统的一个bug, 为啥在历次产品升级换代的时候不将这个bug给修复呢？感觉这是SAP公司留下来这个问题不解决来故意恶心人的。
笔者不想再被这个报错信息所恶心了，所以决定将其彻底解决。经过查资料，有如下发现：
============================
Background Info:
Our company just upgrade ECC 6.0 and we encountered a similar problem as described in the prior threads. I just want to share this with others who may have come across similar issue and are scratching their heads on how to go about solving this. This resolution works for us but I can't guarantee it would work for all. At least it's one of many solutions out there. Here goes...
Problem Description:
After SAP upgrade, user encounters the message "Customizing incorrectly maintained" whenever he/she executes the transaction ML81N. This message appears multiple times within the transaction. Additionally, the GR document number will not be displayed at the completion of service entry (which was there prior to the upgrade). This doesn't prevent users from entering service entry sheets. The document number can still be obtained from its corresponding PO.
The Solution:
Maintain table T162V to match the number of items and sequence as shown in the "Control View" of the grid inside transaction ML81N. The same items and sequences should be applied to all layouts in table T162V (there were 0, 1, 2, 3, 4 and 5 at the time of this our upgrade). This modification will affect all clients within the system (i.e., cross client change). After applying this, the message disappeared and the document numbers were starting to show once again.
Hope this may help some of us system supporters out there.
============================
在界面上的Basic Data的Grid界面里，点击标题栏最右边的按钮，
系统弹出小窗口，
点击’Administrator’, 进入如下界面，
可以发现layout里，列数（字段数，栏位数）总共是83列。如上图。
执行事务代码SM31， 输入表名T162V, 显示其数据，
其中layout有6个，从0到5。
SE16导出该表的数据来分析，发现同一个字段在不同的布局里其顺序各不相同，如下图示：
所以解决方案就是要该表中布局0-5里的各个元素的position修改成一致，并且保证每个布局里的字段数都是83，就可以解决这个报错了。这个工作量不小的。
