Error message - Customizing incorrectly maintained –in transaction code ML81N

I have encountered this information in the SAP system of many projects - customizing incorrectly maintained – when executing transaction code ml81n to create a service entry sheet for service purchase orders.

This message seems to say that there is an error, which does not affect our normal execution of ML81N, but it pops up every time, which is very annoying!

Now I encounter this error message again on the 1909 s / 4 Hana system.

I'm puzzled. If it's a bug in SAP system, why does not SAP fix it in previous product upgrades? I feel that SAP company left this bug unsolved to deliberately disgust us.

I don't want to be disgusted by this error message anymore, so I decided to solve it completely. After checking the data, the following findings are found:

------------------------------------------------------------------------------------

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.

------------------------------------------------------------------------------------

In the grid screen of basic data in ML81N transaction, click the button ,

then SAP pop up below window,

Click the button “Administrator”, then we got below screen,

We can see that the total number of columns (number of fields or number of columns) in the layout is 83. See above screen.

Execute the transaction code SM31, enter the table name T162V, and display its data,

There are 6 layouts, from 0 to 5.

Execute transaction code SE16 to download the data of this table for analysis. It is found that the order of the same field is different in different layouts, as shown in the following figure:

Therefore, the solution is to modify the position of each element in layout 0-5 in the table to be consistent, and ensure that the number of fields in each layout is 83, so as to solve the error. The workload is not small, you know that.

2021-12-16.

SAP MM Error message - Customizing incorrectly maintained – in transaction code ML81N相关推荐

  1. SAP MM在ML81N事务代码界面报错- Customizing incorrectly maintained –之对策

    SAP MM在ML81N事务代码界面报错- Customizing incorrectly maintained –之对策 笔者在很多项目的SAP系统里都遇到这个信息,在ML81N为服务采购订单创建s ...

  2. Could not open app - SAP UI5 error message

    Created by Wang, Jerry, last modified on Mar 10, 2015 要获取更多Jerry的原创文章,请关注公众号"汪子熙":

  3. SAP MM MB21创建预留单据报错- Error during conversion to alternative units of measure -

    SAP MM MB21创建预留单据报错- Error during conversion to alternative units of measure - 某日下午收到业务部门报错,说是创建预留单保 ...

  4. SAP MM 执行事务代码MRRL报错-No message was found for partner 100065 company code 0001-

    SAP MM 执行事务代码MRRL报错-No message was found for partner 100065 company code 0001- 1, 执行事务代码MRRL 触发invoi ...

  5. 如何处理Partner function occurs less than specified in customizing error message

    Created by Jerry Wang, last modified on Sep 20, 2014 在编辑individual object试图save的时候,遇到如下error message ...

  6. 如何解决error message Data cannot be maintained for set type COM_TA_R3_ID

    Created by Jerry Wang, last modified on Aug 05, 2014 SMW01里BDOC record包含如下error message: 在COMM_HIERA ...

  7. Error message COM_PRODUCT 503 Data cannot be maintained for set type COM_TA_R3_ID

    Created by Jerry Wang, last modified on May 29, 2015 当从ERP往CRM download equipment时,遇到如下错误: error mes ...

  8. 如何找到SAP CRM WebClient UI error message的来源

    Created by Jerry Wang, last modified on Mar 22, 2014 除了使用这篇blog介绍的方法之外, 本wiki提供了另外一种方法: 使用transactio ...

  9. SAP UI5:如何处理resource not found for the segment XXXXX error message

    Created by Jerry Wang, last modified on Dec 10, 2015 使用Postman 测试Odata request时遇到如下error message: 原因 ...

最新文章

  1. 【Android View事件分发机制】关于拦截事件的注意点
  2. java之servlet
  3. 嵌入式java基准测试_Java正则表达式库基准测试– 2015年
  4. Oracle 基础 —SQL语句优化的途径
  5. python中文视频教程-python中文视频教程(全38集)
  6. 表单数据序列化,后台如何接收(java)
  7. 设置UYVY格式YUV为黑色
  8. 写在2017年的总结
  9. Flutter入门(2)—创建项目
  10. Navicat Premium 15注册出现“rsa public key not find”
  11. VC2010升级到VC2015遇到问题及解决办法
  12. vyos -vyatta-config-commit save
  13. Hash表的平均查找长度ASL计算方法
  14. 如何判断绝缘接头质量的好坏?
  15. c语言硬币个数最小值,c语言 PTA day4 将一笔零钱换成5分、2分和1分的硬币,要求每种硬币至少有一枚,有几种不同的换法?...
  16. 山峰和山谷 Ridges and Valleys
  17. 读书笔记——戴尔·卡耐基(美)《人性的弱点》
  18. “有点笨”的数学大师迈克尔·弗里德曼
  19. 用友NC远程命令执行漏洞通告
  20. Linux菜鸟笔记——修改默认语系

热门文章

  1. 想成为系统高手就进来,就怕你学不完
  2. ArcSDE、ArcGis Engine、ArcGis Desktop的授权配置
  3. np.zeros(shape) 注意shape的规范格式为元组,不是list
  4. logistic loss公式的由来 xgboost 雪伦的推导中使用了该公式
  5. 2020-10-26关于虚拟机中的HWADDR和MACADDR地址
  6. 使用Log4j进行日志操作(牛小浩)不错的
  7. YOLOX:高性能目标检测的最新实践 | 报告详解
  8. iPhone开发:09年开发领域的最热看点!
  9. Tensorflow-gpu1.13.1 和 Tensorflow-gpu2.0.0共存之安装教程
  10. 没有绝对安全的系统!激光瞄准二极管,25米外从被物理隔绝的计算机中窃取数据...