Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
ME0C (Package) Customizing R/3 Purchasing
IMG Activity
| ID | SIMG_CFMENUOLMEOMFA | Define Screen Layout at Document Level |
| Transaction Code | S_ALR_87002267 | IMG Activity: SIMG_CFMENUOLMEOMFA |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUOLMEOMFA | Define Screen Layout at Document Level |
| Customizing Activity | SIMG_CFMENUOLMEOMFA | Define Screen Layout at Document Level |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOLMEOMF4 |
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:
- 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. - 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.
- 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. - 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.
- 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
- Check the predefined input attributes.
- 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:
- In user parameter EFB in the step Define Function Authorization for Buyers.
- Under the release indicator in the step Set Up Release Procedure with Classification for purchase requisitions.
Further Notes
You cannot use the following fields as mandatory fields:
- Delivery address
- Texts
Business Attributes
| ASAP Roadmap ID | 261 | Define Screen Control |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CFMENUOLMEOMF4 | 0 | HLA0006041 | Purchase Orders |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| VV_162_K | V - View | SM30 | 06 | Field Selection at Document Level |
History
| Last changed by/on | SAP | 20000120 |
| SAP Release Created in |
