Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions⤷
VZ (Package) Application development R/3 RV central functions
Basic Data
| Data Element | BEDSD |
| Short Description | Transfer of requirements / Begin assembly order from SD |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | Reqmts |
| Medium | 15 | Requirements |
| Long | 20 | Transfer of reqs. |
| Heading | 2 | Rq |
Documentation
Definition
Transfer of requirements is to be carried out for the respective transaction.
The selection of this indicator is the precondition for transfer of
requirements. You can deactivate transfer of requirements at schedule line level. Conversely, it can simply be left inactive at schedule line level, as long as it is not already activated in the requirements class.
Example
You do not set an indicator for maintaining the requirements class: Transfer of requirements is not carried out, irrespective of the specification you make at schedule line level for the transaction.
You set an indicator for maintaining the requirements class: In this case you can still decide at schedule line level, whether or not you require transfer of requirments for the relevant transaction.
History
| Last changed by/on | SAP | 19950721 |
| SAP Release Created in |
