首页 > 其他分享 >Define Screen Layout at Document Level(Purchase Order): 采购订单标准屏幕字段控制

Define Screen Layout at Document Level(Purchase Order): 采购订单标准屏幕字段控制

时间:2024-08-28 10:52:06浏览次数:12  
标签:Purchase selection Layout Level field key 采购 选择键 document

 

1. 维护视图: V_162

2.IMG 路径:输入T-code: OLME  Purchasing-->Purchase Order-->Define Screen Layout at Document Level

 

3. 英文文档

Define Screen Layout at Document Level

For all external purchasing documents and purchase requisitions, you can specify the input attributes of fields by using field selection keys.

A field selection key determines whether a field is:

  • A mandatory-entry field (input required)
  • An optional-entry field (input possible)
  • A display field (field displayed only, input not possible)
  • Suppressed

When the screen is assembled in the dialog transactions, for example, Change Purchase Order, certain field selection keys are combined.

Combination of field selection keys

When the screen is assembled, the dialog program combines up to six different field selection keys.

The successive combination of the field selection keys listed below according to the link rules determines which input characteristics the fields have in the document.

Two field selection keys are combined according to the link schema in the table below. The following key is used:

  • + For mandatory fields
  • . For optional fields
  • * For display fields
  • - For suppressed fields

Link rules for field selection keys

       

Field selection key 2

         

+

.

*

-

Field selection key 1

               
                 

+

       

+

+

*

-

.

       

+

.

*

-

*

       

*

*

*

-

-

       

-

-

-

-

Example

When you change a purchase order, the following field selection keys are combined for the field Terms of payment:

  • In field selection key 1 (transaction), this field is an optional field
  • In field selection key 2 (activity type - Change ACTV), this field is an optional field
  • In field selection key 3 (purchasing document type), this field is a display field

The combination of field selection keys 1 and 2 results in this field being an optional field.

The combination of an optional field with field selection key 3, in which the field is a display field, results in a display field.

Field selection key

YOu should not delete the field selection keys listed below, which the dialog program uses for control purposes, otherwise the dialog may terminate during processing:

1. Field selection key: transaction
The field selection key that corresponds to the transaction code: for example, field selection key ME22 for the transaction "Change Purchase Order". For the Enjoy Purchase Order transactions (creating, changing, displaying), there is only field selection key ME21N.

2. Field selection key: activity type
Is set from the activity type as follows:

    • AKTH    In creation mode
    • AKTV    In change mode
    • AKTA    In display mode
    • AKTE    With PO extension

You should note that you can also add items in change mode (for example, transaction ME22). Field selection key AKTH would be used for this item.

3. Field selection key: purchasing document type
The field selection key that you have assigned to the document type for the purchasing document. For example, field selection key UBF is assigned to document type UB, which is used for stock transfer orders (within a company code). In this key, the fields Price and Price unit are suppressed.

4. Field selection key: item category/document category
This is determined from the item and document categories as follows: The first two characters consist of the letters 'PT', the third character of the item category (internal representation), and the fourth of the document category:

    • A   for RFQs,
    • B   for purchase requisitions
    • F   for purchase orders
    • K   for contracts
    • L   for scheduling agreements

Accordingly, field selection key PT3F would be used for a subcontracting item in a purchase order.

  • Field selection key: function authorization/release status
    • Purchasing documents: Used for authorization control. If the user parameter EFB (function authorizations in Purchasing) has been assigned and a field selection key has been assigned to the relevant value, this field selection key is used. Otherwise, field selection key $$$$ is used if the user has insufficient authorization to display prices.
    • Purchase requisitions: If the purchase requisition is subject to a release strategy and a field selection key has been assigned to the current release indicator, this field selection key is used.
  • Field selection key: subitem/creation indicator
    • Purchasing documents: Is only used in the case of subitems. The field selection key is put together in the same way as for the item categories (field selection key 4), with the string 'UP', the subitem category, and the document type.
    • Purchase requisitions: the field selection key that is derived from the creation indicator in the purchase requisition, that is, ESTV, ESTF, or ESTD, is used in the case of purchase requisitions generated from within Sales and Distribution, from a production order, or through direct procurement.

5. Field selection key: purchase requisition
In addition to the available field selection keys, you can define a field selection key at function authorization level to influence the input characteristics of fields in the Enjoy Purchase Requisition.
You can use this field selection key to set up groups of users that have certain restrictions when editing purchase requisitions.

SAP Recommendation

SAP recommends that you accept the settings defined in the standard system. In this case, no action is required on your part.

Activities

1. Check the predefined input attributes.

2. Change the field input control facility in accordance with your requirements

If you create your own field selection keys you  can enter these at the following points:

  • In the step "Define document types" for the relevant document:

Further Notes

You cannot use the following fields as mandatory fields:

  • Delivery address
  • Texts

4. 中文文档

在文档级别定义屏幕布局

 

对于所有外部采购文档和采购申请,您可以使用字段选择键指定字段的输入属性。

 

字段选择键确定字段是否:

 

• 必填字段(必须输入)

• 可选字段(可以输入)

• 显示字段(仅显示字段,不能输入)

• 隐藏

 

在对话框事务(例如,更改采购订单)中组装屏幕时,会组合某些字段选择键。

 

字段选择键的组合

 

组装屏幕时,对话框程序最多组合六个不同的字段选择键。

 

根据链接规则,下面列出的字段选择键的连续组合决定了字段在文档中具有哪些输入特征。

 

根据下表中的链接模式组合两个字段选择键。使用以下键:

 

•+ 用于必填字段

•。对于可选字段

•* 对于显示字段

•- 对于隐藏字段

 

字段选择键的链接规则

 

字段选择键 2

+ . * -

字段选择键 1

 

+ + + * -

. + . * -

* * * * -

- - - - -

 

示例

 

更改采购订单时,以下字段选择键将组合用于字段付款条件:

•在字段选择键 1(交易)中,此字段为可选字段

•在字段选择键 2(活动类型 - 更改 ACTV)中,此字段为可选字段

•在字段选择键 3(采购单据类型)中,此字段为显示字段

 

字段选择键 1 和 2 的组合导致此字段为可选字段。

 

可选字段与字段选择键 3 的组合(其中字段为显示字段)导致显示字段。

 

字段选择键

 

您不应删除下面列出的字段选择键,对话框程序会使用这些字段选择键进行控制,否则对话框可能会在处理过程中终止:

 

1. 字段选择键:事务

与事务代码相对应的字段选择键:例如,事务“更改采购订单”的字段选择键 ME22。对于 Enjoy 采购订单事务(创建、更改、显示),只有字段选择键 ME21N。2. 字段选择键:活动类型

从活动类型设置如下:◦AKTH 在创建模式下

◦AKTV 在更改模式下

◦AKTA 在显示模式下

◦AKTE 带有 PO 扩展

您应该注意,您还可以在更改模式下添加项目(例如,事务 ME22)。字段选择键 AKTH 将用于此项目。3. 字段选择键:采购单据类型

您已分配给采购单据的单据类型的字段选择键。例如,字段选择键 UBF 分配给单据类型 UB,用于库存转移订单(在公司代码内)。在此键中,字段“价格”和“价格单位”被隐藏。4. 字段选择键:项目类别/文档类别

这由项目和文档类别确定,如下所示:前两个字符由字母“PT”、项目类别的第三个字符(内部表示)和文档类别的第四个字符组成:◦A 表示询价,

◦B 表示采购申请

◦F 表示采购订单

◦K 表示合同

◦L 表示计划协议

因此,字段选择键 PT3F 将用于采购订单中的分包项目。•字段选择键:功能授权/发布状态

◦采购单据:用于授权控制。如果已分配用户参数 EFB(采购中的功能授权),并且已将字段选择键分配给相关值,则使用此字段选择键。否则,如果用户没有足够的权限显示价格,则使用字段选择键 $$$$。

◦采购申请:如果采购申请受发布策略约束,并且已将字段选择键分配给当前发布指示器,则使用此字段选择键。

•字段选择键:子项/创建指示器

◦采购单据:仅用于子项。字段选择键的组合方式与项目类别(字段选择键 4)相同,包括字符串“UP”、子项类别和单据类型。

◦采购申请:从采购申请中的创建指示器(即 ESTV、ESTF 或 ESTD)派生的字段选择键用于从销售和分销、生产订单或通过直接采购生成的采购申请。

5. 字段选择键:采购申请

除了可用的字段选择键之外,您还可以在功能授权级别定义字段选择键,以影响 Enjoy 采购申请中字段的输入特性。

您可以使用此字段选择键设置在编辑采购申请时具有某些限制的用户组。

SAP 建议

SAP 建议您接受标准系统中定义的设置。在这种情况下,您无需采取任何行动。

活动

1. 检查预定义的输入属性。

2. 根据您的要求更改字段输入控制功能

如果您创建自己的字段选择键,您可以在以下位置输入这些字段选择键:

• 在相关文档的“定义文档类型”步骤中:

o RFQ/报价

o 采购申请

o 采购订单

o 合同

o 计划协议

• 在用户参数 EFB 中,在“为买家定义功能授权”步骤中。

• 在“设置采购申请分类的发布程序”步骤中的发布指示器下。

进一步说明

您不能将以下字段用作必填字段:

• 送货地址

• 文本

标签:Purchase,selection,Layout,Level,field,key,采购,选择键,document
From: https://www.cnblogs.com/JackeyLove/p/18384137

相关文章

  • Android开发 - LayoutInflater 类将 XML 布局文件转换成对应的 View 对象解析
    LayoutInflater是什么LayoutInflater用于将XML布局文件转换成对应的View对象。它可以理解为一个“布局解析器”,帮助我们将静态的XML文件转换为可以动态操作的Java对象(View及其子类)LayoutInflater的主要作用在Android开发中,我们通常会在res/layout文件夹中......
  • 讨论TableLayoutPanel加载缓慢和闪烁问题解决方案
    WinForm加载多个自定义控件时,会出现很严重的闪烁问题,很卡,一块一块的加载(像打开网页时,网络很卡的那种感觉)简直没法忍受。在网上搜索了好久,网上大部分的方法是一下4种,但是都不能有效的解决问题。1、将DoubleBuffered设置true,用双缓存处理Form界面内容加载,可以提高页面显......
  • 【论文解读】Macroblock Level Rate Control for Low Delay H.264/AVC based Video Co
    级别:IEEE时间:2015作者:MinGao等机构:哈尔滨工业大学下载:MacroblockLevelRateControlforLowDelayH.264/AVCbasedVideoCommunication摘要算法目的:提出了一种针对低延迟H.264/AVC视频通信的宏块(MB)级别速率控制算法。算法基础:基于ρ域速率模型,该模型涉......
  • Level Up
    法一:题面给出了\(k,2k,3k\)这些数,容易想到调和级数。于是尝试对于每个\(k\),我们取找出升级的每段(也就是对怪物序列进行划分,每一段的等级相同,相邻两段等级相差一),然后看这篇题解;所以以后遇到处理\(\overset{r}{\underset{i=l}{\sum}}[a_i>x]\)这种式子就可以想根号算法法二:转换考虑......
  • Python导入包时提示“attempted relative import beyond top-level package”的解决办
    一篇很好的文章:python跨目录导包失败python不同路径导入包错误 在涉及到相对导入时,package所对应的文件夹必须正确的被python解释器视作package,而不是普通文件夹。否则由于不被视作package,无法利用package之间的嵌套关系实现python中包的相对导入。文件夹被python解释器视作......
  • LinerLayout布局|RecyclerView覆盖其它控件
    已解决,高度设置odp,按权重分配位置 <LinearLayoutxmlns:android="http://schemas.android.com/apk/res/android"android:layout_width="match_parent"android:layout_height="wrap_content"android:orientation="vertical&quo......
  • Android经典实战之约束布局ConstraintLayout的实用技巧和经验
    本文首发于公众号“AntDream”,欢迎微信搜索“AntDream”或扫描文章底部二维码关注,和我一起每天进步一点点ConstraintLayout是Android中一种强大的布局管理器,能够帮助你创建复杂而灵活的布局。它通过约束系统将一个View的位置和大小与其他View或父布局联系起来,使得......
  • M3KE: A Massive Multi-Level Multi-Subject Knowledge Evaluation Benchmark for Chi
    文章目录题目摘要简介相关工作M3KE实验结论题目M3KE:面向中文大型语言模型的海量多层次多学科知识评估基准论文地址:https://arxiv.org/abs/2305.10263项目地址:https://github.com/tjunlp-lab/M3KE摘要    大型语言模型最近在跨任务泛化、指令跟随等多个......
  • 摘要生成—通过摘要风格控制摘要的生成/抽取,原文阅读与理解:GEMINI: Controlling The S
    GEMINI:ControllingTheSentence-LevelSummaryStyleinAbstractiveTextSummarizationGEMINI:在抽象文本摘要中控制句子级摘要风格paper:https://arxiv.org/abs/2304.03548github:https://github.com/baoguangsheng/gemini本文介绍了一种自适应摘要抽取/生成方......
  • 新手常见错误:Language level is invalid or missing in pom.xml. Current project JDK
    目录Blue留声机:分析报错 Blue留声机:今天开一个maven的时候遇到这样一个报错,这个报错对于我来言是一个并不陌生的报错,早期学习spring框架的时候,遇到过这个问题,当时怎么也弄不出来(现在想想那个时候的我真菜),现在却对这种问题的解决游刃有余。好了,不多bb了,看看我一般处理bu......