Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FREP (Package) RF reporting
Basic Data
| Data Element | UMSVBSUD |
| Short Description | Update Run: Update Tax Items from Documents |
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 | Update tax |
| Medium | 15 | Update tax |
| Long | 20 | Update tax data |
| Heading | 10 | Update tax |
Documentation
This has the effect that only those tax items for updating the tax return are selected in which no date or time of an earlier run is noted.
The date and time of the current run are then marked in the tax items selected.
Use
This prevents individual items being reported twice in cases of organizational difficulties.
In countries that use the posting date as criteria for the tax return, no update is required, since after closing the posting month, the relevant period can be blocked for further postings.
Note
By updating the individual tax items, the runtime of the report is considerably extended. You should therefore only use this function in limited cases.
Dependencies
The tax return has to be done according to document date. Unfortunately, it is frequently the case that after the tax return has been done for a period, additional documents with a document date in this period are entered.
History
| Last changed by/on | SAP | 19990317 |
| SAP Release Created in |
