Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
ICM (Application Component) Incentive and Commission Management (ICM)⤷
CACSCC (Package) ICM: Commission Case 'Light'
Basic Data
| Data Element | CACSBUSOBJID |
| Short Description | Identification of Triggering Business Object |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CACSOBJID30 | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| 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 | Bus.Obj.ID |
| Medium | 15 | Business Obj.ID |
| Long | 20 | Business Object ID |
| Heading | 20 | Business Object ID |
Documentation
Definition
Identification for a business object in the operational system.
A specialization of object key. See also: Triggering business object.
Further information
A commission case is a copy (primary entry) in the commission system of a business transaction in a business object from a different application. This "sending" application defines what it understands by a business object or a business transaction.
The triggering and remunerating business transactions both operate on the business object. If the triggering business transaction is not the remunerating business transaction, then this is assumed to be the operation of the triggering business transaction on the remunerating one, meaning that it is also an indirect operation on the business object.
The business object and business transaction must both be specified in full. If the remunerating or the triggering business transaction is not filled then it is taken from the other case each time.
The combination of the remunerating business transaction and the business object (both categorized and versioned) is also the external identification of the commission case, and requires corresponding rules to be unique:
- This means that a business object or business transaction must never be reported in the commission system in a lower version than the latest version of the object or case.
- In addition, the combination of business object and business transaction does not already have to be known to the system (including their versions). However, it is not enough to simply report a newer business transaction version.
- If the business object was already reported to the commission system then at least one of the two fields Business Object Version or Business Object Start Date must also be different to the versions of the business objects already reported. This means that a business object must not be in the commission system twice with the same business object version and business object start.
These rules apply to the triggering and remunerating business transactions (always in combination with the business object).
A new version of a remunerating business transaction always creates a new version of a commission case. The triggering method in this case can only be Change or Reset. Create is, in this case, never allowed.
History
| Last changed by/on | SAP | 20031111 |
| SAP Release Created in |
