Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BF (Application Component) Basic Functions⤷
VA0C (Package) Customizing R/3 sales
Basic Data
| Data Element | SORT_TPAER |
| Short Description | Sequence in which partners are determined in the sales doc. |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUMC2 | |
| Data Type | NUMC | Character string with only digits |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| 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 | Sequence |
| Medium | 15 | Sequence |
| Long | 20 | Sequence |
| Heading | 5 | Seq. |
Documentation
Definition
Indicates the level of priority which the partner in the document with this function has during partner determination.
Use
If the field is blank, the system determines this partner first. If it contains a 1, it determines the partner in the second step, if the field contains a 2, it determines the partner in the third step, and so on.
Procedure
If you have specified a source partner function, then enter a figure in this field that is higher than the figure in this field for the source partner function.
If you haven't entered a source partner function, you don't need to enter anything here.
Example
Source Sequence
Sold-to party (SP) blank blank
Ship-to party (SH) blank blank
Forwarding agent (CR) SH 1
In this case, the sold-to party and the ship-to party are determined first. Then the forwarding agent is determined from the ship-to party master record.
Dependencies
If you have entered an alternative partner function in the Source partner function field, you must maintain this field.
History
| Last changed by/on | SAP | 19991102 |
| SAP Release Created in |
