Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | NODE70000 |
| Short Description | Documentation for partner determination node |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| 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 | 1 |
| Medium | 15 | 1 |
| Long | 20 | 1 |
| Heading | 1 | 1 |
Documentation
Description
The key figures here refer to the core areas of partner determination within Sales and Distribution processing.
Partner determination has been shown to cause bottle-neck situations, as it often runs as part of a document and is implemented during the creation of a new partner-relevant document and all partner-relevant items. It is particularly important here to examine the number of partner relationships, which have already been pre-set in the structures of the partner master data and which should be reprocessed for every document and item.
Example:
A customer master record with the partner function sold-to party has one hundred (100) different ship-to parties. Customer branches to be supplied are represented in this way.
As well as this partner function there are a further 20 functions for the different business transactions, for which partner determination is carried out.
A fictional sales order has 20 items, which are all to be delivered to the different branches.
During processing of each document item, it then has to be determined which of the hundred ship-to parties is the right one.
When a large amount of transactions are carried out at the same time, this leads to higher response times for the key transactions.
In this example partner determination is not suitable as it unnecessarily increases the load on the system at the relevant points.
The situation can be improved by carrying out a comprehensive control of
partner determination, particularly when the optimization measures below are not used or are used in incomplete form. This results in response times to the nearest minute.
Control of partner determination is very similiar to that for condition technology and should undergo an analogue optimization evaluation. Partner determination is also used for other SAP applications.
Focus points
Those parts of the function with high resource requirements should be examined.
According to experience these are
the number and size of the pricing procedures used,
defined but unused partner functions,
the frequent use of partner functions in connection with partner hierarchies,
master data constellations, for example, for partner hierarchies can, if there is unsuitable modelling, lead to examinations of running time behaviour during document processing. Particularly when the hierarchies are flat and wide. Hierarchies can be used in Pricing and must be processed if necessary.
Example:
A partner hierarchy can consist of two nodes. 2000 individual partners are assigned to each node.
In this example, attempts should be made to reduce the number of partners per node by restructuring the hierarchies.
The definition and amendments to partner procedures, hierarchies and partner functions requires comprehensive action with regard to business and technical system connectivities. business and technical system connectivities. Particularly when different areas of a company are involved.
You should pay attention here to the remaining interaction between partner determination and Pricing modelling.
In addition further system parts (e.g. User-Exits), which are objects of individual procedures and extensions as part of the SAP introduction are included in the examination.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
