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 | SENDR2 |
| Short Description | Send release order documentation to contract in R/2 |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SENDR2 | |
| 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 | Send R/2 |
| Medium | 13 | Send to R/2 |
| Long | 35 | Send release docu. to contr. in R/2 |
| Heading | 35 | Send release docu. to contr. in R/2 |
Documentation
Definition
If this selection parameter is active, data is selected which, in the standard system, is only needed when release documentation is sent to a centrally agreed contract in R/2.
For performance reasons, this parameter should not be active if data is being sent to a centrally agreed contract in mySAP ERP.
Further information:
The IDoc segment E1RDOCU, which reflects the fields of the release docu record (structure EKAB in mySAP ERP, structure BSEW in R/2), contains the fields from R/2 and mySAP ERP. The selection of all fields needed in R/2 requires the re-reading of the purchase order (to populate the fields EKAB-PLOEK, EKAB-WEPOS, and EKAB-REPOS) and the PO history records (to populate the fields EKAB-WEMNG, EKAB-REMNG).
This switch should only be activated if one of these fields is also needed in mySAP ERP (for example, within the framework of a modification).
History
| Last changed by/on | SAP | 19980218 |
| SAP Release Created in |
