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 | CRDOBJTYPE |
| Short Description | Credentialing: Object Types |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CRDOBJTYPED | |
| Data Type | CHAR | Character String |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| 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 | 6 | ObjTyp |
| Medium | 9 | Obj. Type |
| Long | 9 | Obj. Type |
| Heading | 9 | Obj. Type |
Documentation
Definition
Together with the transaction type, the object type restricts and describes the transaction that makes it necessary for a credentials check to be performed.
The permitted values are defined by the application scenario, and these values must be compared with the client of the credentialing system.
Use
The functional use of these data elements is to support the search for the requirements that have to be met when the credentials check is called.
It can be decided on the basis of the object type and transaction type (and context) which requirement is to be met. Additionally, the values of these fields can be used to make a first selection and then to handle the actual requirements determination with a more complex tool.
The standard delivery uses the determination of Incentive and Commission Management (ICM); access to this tool is determined by assigning a characteristics combination ID. If you use the determination, all the data delivered to the interface of the credentialing system can be used to determine the requirements that are to be met, as well as the transaction type, object type and context.
Dependencies
Example
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in | 700 |
