Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
WAUF (Package) Application development R/3 Purchasing, Allocation table
Basic Data
| Data Element | AUFAR |
| Short Description | Allocation Table Type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | AUFAR | |
| Data Type | CHAR | Character String |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| Value Table | T620 |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ATG | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | AT Type |
| Medium | 15 | Alloc. tbl type |
| Long | 22 | Allocation Table Type |
| Heading | 4 | Type |
Documentation
Definition
Indicates that different types of allocation tables.
Use
The allocation table type controls
- maintenance functions
- the fields that have to be maintained
- the default values proposed by the system
Supplementary Documentation - AUFART 0000
Use
If you generate a sales order from a message, the system always proposes the order type specified in Customizing. You can change this value.
Procedure
Enter the desired order types here.
Examples
Dependencies
Settings (such as the way order costs are settled) depend on the order type.
Supplementary Documentation - AUFART 0001
Use
You can specify an order type here, whose print control is to be referred to from another order type.
Supplementary Documentation - AUFART 0002
Use
The order type stores parameters affecting the way that orders are to be processed.
For example, using the order type, you can specify:
- which number range is to be used for the order type
- the criteria by which routings are to be selected
- how the orders are to be costed.
Procedure
Examples
Dependencies
In Kanban, order types are relevant only with production orders.
Supplementary Documentation - AUFART 0003
Procedure
Enter the value that should in future be proposed as a possible entry.
Supplementary Documentation - AUFART 0005
Use
The order type entered here is used only when you need to create different order types from one message type. This is because a portion of the orders should be invoiced to your customers through service contracts.
This order type must allow a settlement to service contracts.
Supplementary Documentation - AUFART 0120
Use
If the order in question is a planned order, this field displays the order type (such as normal purchase order or warehouse order) this planned order is provided.
Procedure
Examples
Dependencies
Supplementary Documentation - AUFART 1000
Definition
Use
Procedure
Enter the order types for which process instructions are to be generated.
Examples
Dependencies
Supplementary Documentation - AUFART 2000
Use
The network type differentiates networks according to their purpose.
Supplementary Documentation - AUFART 5100
Definition
Key differentiating orders according to their use.
Use
The order type stores parameters affecting the way that orders are to be processed.
Examples
Using the order type, you can specify:
- Which number range is to be used for the order type
- The criteria by which master recipes are to be selected
- How the orders are to be costed.
History
| Last changed by/on | SAP | 20020124 |
| SAP Release Created in |
