Hierarchy

⤷

⤷

⤷

Basic Data
Data Element | VSEVENT |
Short Description | CO-Event in Validation or Substitution |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | VSEVENT | |
Data Type | NUMC | Character string with only digits |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
Value Table | TKAZ |
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 | Event |
Medium | 15 | Event |
Long | 20 | Application Event |
Heading | 7 | Event |
Documentation
Definition
Event callup points, for which the system provides the data for processing in various structures.
Use
The system provides the following callup points for validation:
- 0001: Document row
This callup point is used for all CO-relevant postings in external accounting, as well as for all CO-internal postings. The system stores the data in the structures COBK (CO-object: document header ) and COBL (account assignment block).
- 0002: CO-internal posting: Sender-Receiver-Validation
Used only for CO-internal postings and only for the validation of sender-receiver relationships. The data exists in the following structures:
- COBL_GENERAL (Sender/Receiver Header Information from COBL)
- COBL_RECEIVER (Receiver Object Information)
- COBL_SENDER (Sender Object Information)
Note that you can only use these three structures for validation at callup point 0002. It is also not possible to switch sender structure (COBL_SENDER) and receiver structure (COBL_REVCEIVER)
The structures of callup point 0002 contain additional fields that are not available in the structures of callup point 0001. For example, COBL_RECEIVER and COBL_SENDER contain the sender- or receiver company code, while COBL does not contain the partner company code.
You can specify in the sender and receiver structures for which account assignment type (true or statistical) the validation is to be executed on the objects. In the sender structure (COBL_SENDER) you can use the substructure "Account assignment types of CO account assignments for partner objects" (COBLP_COKZ). In the receiver structure (COBL_RECEIVER) you can use substructure "Account assignment types of CO account assignments" (COBL_COKZ).
To provide a better overview, the system offers you only the organizational units of the true account assignment objects in the structures COBL_SENDER and COBL_RECEIVER. It is therefore not possible to carry out a validation of organizational units for statistical objects.
For system performance reasons, the system does not fill the structures COBL_SENDER and COBL_RECEIVER with statistically assigned objects during periodic allocations. Validation is therefore only possible for true account assignment objects for periodic allocations.
- 0100: Document header
This callup point is used for manual postings in CO, for example, during the reposting of costs or during activity allocation. The data is available in the structure COBK (CO object: document header).
Caution
If you are allocating costs to profitability segments using assessment, the system does not always fill the "PAOBJNR" field (profitability segment). If account-based Profitability Analysis is active, the field is filled. If it is not active, the "PAOBJNR" may not always be filled (this is due to technical restrictions).
The "CO_KAERG" field (account assignment type: Profitability segment) is always filled by the system.
Examples
Supplementary Documentation - VSEVENT 0001
Use
The following event callup points are provided by the R/3 System for substitution:
- 0001: Document rows
Used for all CO-relevant postings in external accounting, as well as for all CO-internal postings. The system provides this data in both of the structures, COBK (CO Object: Doc. header) and COBL (account assignment block).
- 0010: Order
Used for the collective processing of orders.
- 0100: Document header
Used for manual postings in CO, for example, for the reposting of costs or with activity allocation. The data is provided in the COBK structure (CO Object: Document header).
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in |