Hierarchy
BBPCRM (Software Component) BBPCRM⤷
SRM-EBP (Application Component) Enterprise Buyer⤷
BBP_APPLICATION (Package) Structure Package EBP⤷
ME (Package) Application development R/3 Purchasing
Basic Data
| Data Element | ESART |
| Short Description | Purchasing Document Type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BSART | |
| Data Type | CHAR | Character String |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| Value Table | T161 |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | BSA | |
| Default Component name | DOC_TYPE | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Doc. Type |
| Medium | 15 | Document Type |
| Long | 20 | Purchasing Doc. Type |
| Heading | 4 | Type |
Documentation
Definition
Identifier allowing differentiation between the various kinds of purchasing document in the SAP system.
On the basis of the purchasing document type, you can, for example, distinguish between a purchase order, an RFQ and a scheduling agreement.
Use
The purchasing document type controls, for instance, the number assignment of a purchase order, as well as the selection of the fields to be maintained.
Supplementary Documentation - ESART 0001
Use
When this SAP transaction is invoked, this value is proposed as document type.
Supplementary Documentation - ESART 0002
Use
The document type entered will always appear as the default value at the time of document creation.
Example
You create a new document type for purchase orders and you enter the new document type as default document type. The new document type then always appears as the default value during the creation of POs.
History
| Last changed by/on | SAP | 19981111 |
| SAP Release Created in |
