Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions⤷
VZ0C (Package) Customizing R/3 RV central functions
Basic Data
| Data Element | SPAAU |
| Short Description | Reference division for document types (by sales area) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SPART | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| Value Table | TSPA |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | SPA | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Division |
| Medium | 15 | RevDiv-DocType |
| Long | 20 | RevDivision-DocType |
| Heading | 10 | RefDivDoc |
Documentation
Definition
Specifies a division as a reference for sales document types.
Use
You can share sales document type data between different divisions. You define sales document types in a central division and then use it as a reference division. Each division to which you assign the reference can use the same sales document types defined in the reference division. The sales document types are maintained centrally in the reference division.
Procedure
If all sales document types are allowed for all divisions, leave the field blank. Otherwise, enter the division you want to use as a reference.
Example
Division Reference division
01 01
02 01
03 01
04 04
In this example, only divisions 01 and 04 have sales document types defined. Divisions 01, 02, and 03 share the sales document types defined for division 01. Division 04 has its own sales document types. When you create a sales order in division 03, the system checks the sales document type against the types defined for division 01. You do not maintain sales document types in divisions 02 and 03, since they are never used.
History
| Last changed by/on | SAP | 19991102 |
| SAP Release Created in |
