Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
ICM (Application Component) Incentive and Commission Management (ICM)⤷
CRDPRV (Package) Credentialing: Private Objects (DDIC, etc.)
Basic Data
| Data Element | CRDPARTNERTYP |
| Short Description | Credentialing: Allowed Partner Types |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CRDPARTNERTYPD | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| Value Table | TCRD_PTYPES |
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 | Part.Type |
| Medium | 15 | Partner Type |
| Long | 20 | Partner Type |
| Heading | 10 | Part.Type |
Documentation
Definition
Indicates the partner type.
Credentialing generally works on the basis of the SAP central business partner, which is identified with the partner type in Credentialing of 01.
However it is possible to use other partners, which calls for the introduction of a specific field that lets you differentiate between partner types.
Use
Define your own partner type if you want to use it for Credentialing.
Note that Credentialing supports only one partner type for each credentialing application. The partner type is consequently only relevant in cross-application structures and tables.
Dependencies
Example
Possible additional partner types may be objects from external systems, such as machines that may be assigned an operational authorization or elements of organizational management that may not be linked to SAP Business Partner, such as users.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in | 700 |
