Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MG0C (Package) Customizing R/3 material master prior to 3.0
Basic Data
Data Element | BAUT |
Short Description | Parts |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | TEXT25 | |
Data Type | CHAR | Character String |
Length | 25 | |
Decimal Places | 0 | |
Output Length | 25 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Parts |
Medium | 15 | Parts |
Long | 20 | Parts |
Heading | 25 | Parts |
Documentation
Definition
The material type BAUT stands for assemblies. Assemblies are the individual functional parts of a product. A material master record of this material type does not contain any sales data and is managed on both a quantity and a value basis.
Supplementary Documentation - BAUTL 0001
Use
Procedure
Examples
Dependencies
The assembly which you enter in an item of the maintenance notification should be below the assembly contained in the header of the maintenance notification.
Supplementary Documentation - BAUTL 0002
Use
This field may contain the number of an allocated assembly.
Procedure
If you are in the create or change mode, enter the number of the assembly you want to allocate in this field.
Examples
Dependencies
Supplementary Documentation - BAUTL 0003
Procedure
You enter an assembly if you want to refer in greater detail to a particular area of a technical object.
Supplementary Documentation - BAUTL 0004
Use
Procedure
Examples
Dependencies
The assembly that you enter in an item of the quality notification must be below the material in the notification header.
Supplementary Documentation - BAUTL 0005
Procedure
Enter the value that should in future be proposed as a possible entry.
History
Last changed by/on | SAP | 19971006 |
SAP Release Created in |