SAP ABAP Data Element /ISDFPS/BSART_RECEIVER (Receiver Document Type)
Hierarchy
☛
EA-DFPS (Software Component) SAP Enterprise Extension Defense Forces & Public Security
⤷
IS-DFS-MM (Application Component) Materials Management
⤷
/ISDFPS/MM_CS (Package) DFPS Enhancements MM (Cross System)
EA-DFPS (Software Component) SAP Enterprise Extension Defense Forces & Public Security⤷
IS-DFS-MM (Application Component) Materials Management⤷
/ISDFPS/MM_CS (Package) DFPS Enhancements MM (Cross System)
Basic Data
| Data Element | /ISDFPS/BSART_RECEIVER |
| Short Description | Receiver 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 | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Receiv. DT |
| Medium | 15 | Receiver DT |
| Long | 20 | Receiver Doc. Type |
| Heading | 10 | Receiv. DT |
Documentation
Definition
Specifies the document type for a recipient purchase order in a cross-system replenishment scenario.
Use
The recipient purchase order is only required for technical reasons and must be assigned document types that meet certain criteria. They can therefore not be either ATP- or delivery-relevant. Different recipient document types are only used to identify processes. They should be copied from standard document type EUB.
Dependencies
Example
History
| Last changed by/on | SAP | 20050409 |
| SAP Release Created in | 200 |
