Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KABR (Package) Appl. development: R/3 Cost Accounting order settlement
Basic Data
| Data Element | TDCHECKFLG |
| Short Description | Check transaction data |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | Tran.data |
| Medium | 15 | Check tran.data |
| Long | 25 | Check transaction data |
| Heading | 0 |
Documentation
Definition
Indicator for checking transaction data of individual objects in the settlement.
If you set the indicator, the system performs a check at the beginning of processing of a sender. This checks whether any transaction data was posted to that sender after the last settlement. If no transaction data was posted, then sender processing is stopped. In the statistics, this sender is in the "No transaction data available" category.
Error messages (that could have been issued during the settlement) are not issued.
The system also checks settlements from hierarchical settlement.
For security reasons, it does not check the last settlement with the exact date and time. Instead, it puts the time forward by 15 minutes. Due to this time change, many settled amounts are classified as new debits during the transaction data check for senders that are also settlement receivers in hierarchical settlement.
Transaction data checks are not made in the following situations, even if the indicator is set:
- The sender has a results analysis key, and an accrual calculation was already executed. In Customizing for accrual calculation, line item updates are not active for a version relevant for settlement.
- The sender has a variance key and variances have already been determined.
- The sender is a capital investment measure and has the technically completed status. Alternatively, the sender is an investment measure and the settlement was started with processing type 3.
- The settlement rule was changed since the last settlement.
- There is a valid distribution rule for fixed amounts.
- Both a periodic distribution rule and an overall distribution rule have been defined for the settlement of costs with the same origin, and only the periodic distribution rule was used for the last settlement.
History
| Last changed by/on | SAP | 20110901 |
| SAP Release Created in |
