Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
IM-FA-IA (Application Component) Appropriation Requests⤷
AIR (Package) IM appropr.reqs.(master data, planning, preinvestment anal.)
IMG Activity
| ID | OANF_LAYOUT | Specify Tab Layout for Appropriation Requests |
| Transaction Code | S_ALR_87099780 | (empty) |
| Created on | 19990322 | |
| Customizing Attributes | OANF_LAYOUT | Specify Tab Layout for Appropriation Requests |
| Customizing Activity | OANF_LAYOUT | Specify Tab Layout for Appropriation Requests |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OANF_LAYOUT |
The master data of appropriation requests has been distributed to several tab pages because of the large number of possible fields involved. You can specify the content of these tab pages yourself. You thereby avoid having half-empty tab pages that might result if you suppress a number of field in the screen layout. You can specify the following for the tab layout of these tab pages:
- Number of tab pages (maximum of 8)
- Titles of the tab pages
- The field groups that appear on each tab page, and the position in which they appear
Note
All field groups that contain required fields have to be placed on tab pages (that is, you cannot omit a field group of this kind).
You can organize your user fields using customer enhancement AAIR0002.
Example
Requirements
Standard settings
You enter the tab layout in the appropriation request type. If you do not enter your own tab layout there, the system uses the standard tab layout.
SAP provides a tab ayout rule containing all field groups.
SAP provides 11 pre-defined field groups.
Recommendation
Some of the same organizational units appear in both the "Requesting organizational units" field group and in the "Responsible organizational units" field groups. When you make an entry in one of these "mirror" fields (such as responsible company code and requesting company code), and the other corresponding field is blank or 0, the system automatically copies the entered value to the 'mirror' field. If you place these two field groups on different tab pages, this exchange of values is no longer transparent. SAP therefore recommends that you place both of these field groups on one tab page.
Activities
Create layout rules:
- Enter a key and a description for the tab layout rule.
- Specify the number of tab pages and their titles. The number in the "Tab page" column specifies the position at which the tab page appears (from left to right).
- Specify which field groups appear on the tab pages. The number in the "Position" column specifies the position at which the field group appears on the tab page, from the top down.
Further notes
For more information on master data maintenance, refer to the SAP Library IM -> "Appropriation Requests".
For more information on customer enchancement AAIR0002, refer to the documentation on customer enhancements (transaction SMOD).
Business Attributes
| ASAP Roadmap ID | 105 | Define functions and processes |
| Mandatory / Optional | 2 | Optional 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 | OANF_LAYOUT | 0 | HLA0100182 | Basic Data |
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 |
| VC_TAMLAY_00 | C - View cluster | OITO |
History
| Last changed by/on | SAP | 19990430 |
| SAP Release Created in |
