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 | HIGHL |
| Short Description | Partner determination: Search at higher levels |
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 | Higher lv. |
| Medium | 15 | Higher levels |
| Long | 25 | Search at higher levels |
| Heading | 1 | H |
Documentation
Definition
Determines that during partner determination, the system also searches for allocated partners at purchasing organization level when no partners are maintained at plant or vendor sub-range level.
Use
If you set this indicator, the system continues searching at higher levels (i.e. purchasing organization), if no partner can be determined at a given level (i.e.plant/vendor combination).
Note
If different plants are present in a purchasing document, then the system looks for partners at purchasing organization level.
Examples
You have maintained the following partner for vendor Miller (Miller International) with the partner role ordering address.
- Ordering address for purch. org 0001: B (Miller Germany)
- Different ordering address for plant Munich: C (Bavaria branch)
- No different ordering address for plant Stuttgart
The following combinations are possible:
Higher level plant system determines as ordering address
X Munich C
- Munich C
X Stuttgart B
- Stuttgart -
Example 1: Higher level selected
You have selected the indicator Higher level for the partner role ordering address
Result
If you create a purchase order for the Munich plant, the system determines the ordering address C.
If you create a purchase order for the Stuttgart plant, the system determines the ordering address B, because no partners are maintained for the Stuttgart plant. The system therefore looks at purchasing organization level and determines the ordering address B.
Example 2: Higher level not selected
You have not selected the indicator Higher level for the partner role ordering address.
Result
If you create a purchase order for the Munich plant, the system determines the ordering address C.
If you create a purchase order for the Stuttgart plant, the purchase order is transmitted to the address for vendor Miller, because no partner roles are maintained for the Stuttgart plant. The system does not look for partners at purchasing organization level.
Dependencies
Note the dependencies for the indicator End.
This indicator controls whether partner determination is carried out when you create, check, or save a purchasing document.
If partner determination is carried out at the beginning, then you use the plant proposed by the system.
If partner determination is carried out at the end, then the actual plants specified in the items are used.
If there are different plants in the items, then the system determines partners at purchasing organization level, regardless of whether the Higher level indicator is set or not.
If there are identical plants in the items, partner determination is carried out first at plant level.
For more information, see the SAP Library Purchasing (MM-PUR) -> Master Records from the Purchasing View -> Vendor Master Data -> Partner Roles in Purchasing and Maintaing Different Data.
History
| Last changed by/on | SAP | 19980218 |
| SAP Release Created in |
