zoukankan      html  css  js  c++  java
  • Retail Article Master Data 学习 (一) Input Screen

    First to give a short brief:

    The article master data is similar with material master data.

    The main part is also stored in tables like MARA, MARC, MARD, MVKE, etc.

    Besides the standard material master table, there are retai specific table like MEAN, MAW1, etc.

    I log this article to further study the artlcie master data. Especially the reference handling topic.

    First this section will be about the configure for input screen for article master data.

    When you visit MM43, there are many view and each view contains many fields:

          image

    How it works is:

    In MM41 / 42 / 43, there are different views.

    Under each view, there are several screens.

    In each screen, there are many subscreens.

    Take the screenshot above for example, the screen contains the subscreen of:

          image image image

          image

    These could all be found in the customizing under ‘Logistics – General’:

          image image

    You can customize your screen sequence. The standard retail screen sequence is ‘23’.

    The followings are some customized screen sequences.

          image

    OK. So the next question is How do you tell the system you want to use the customerized screen sequece?

    Don’t know yet…..

    Following, another setting – “Maintain User Settings”.

          image

    Here, you can specify a lot for me for other given users:

    - what screen sequence to use

    - default material type

    - the default Purchase org, the vendor, Sales org, Distribution Channel, default DC, etc…

          image

    Besides, in the marked selection, you can also define the default selection of views.

    These functions are all easing the user’s input effort.

          image

    What I did for my user:

    - set default screen sequence ‘23’

    - give default articel type, sales org, Dchannel, purchase org, verndor

    - give views, and preselect default views.

    Then when i hit MM41, i got the following – all the information i preconfiged are filled.

          image

  • 相关阅读:
    Kubernetes 内存资源限制实战
    kubernetes 资源管理概述
    终于对探针下手了
    容器和容器云
    理解 Kubernetes volume 和 共享存储
    理解 docker volume
    docker 镜像管理之 overlay2 最佳实践
    docker 资源限制之 cgroup
    Debug Assertion Failed!
    Qt 字符串转md5
  • 原文地址:https://www.cnblogs.com/sophyzhu/p/1899727.html
Copyright © 2011-2022 走看看