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 | PDTEN |
| Short Description | Partner determination when document is saved |
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 | Partner |
| Medium | 17 | Partner at end |
| Long | 27 | Partner determ. at end |
| Heading | 6 | End |
Documentation
Definition
Use
If you set this indicator, the partner roles will be suggested from the vendor master record (or the contract, in the case of contract release orders) at the end of the document creation process (when you save or when the document is checked).
This late determination of the partner roles is advantageous if you have maintained variant data in the vendor master record (i.e. partners at plant and/or sub-range level). The system checks whether all document items have the same plant or sub-range. If so, it searches for partners that have been defined at just this level.
Procedure
Examples
Dependencies
In the automatic generation of POs, the partners are always determined at the start of the document generation process because all document items already exist. This also has the advantage that all partners are available at the time of price determination if, for example, you are using the "different invoicing party" in the price determination process.
History
| Last changed by/on | SAP | 19980218 |
| SAP Release Created in |
