SAP ABAP Data Element TAGETOL1 (Tolerance days)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷
ME0C (Package) Customizing R/3 Purchasing

⤷

⤷

⤷

Basic Data
Data Element | TAGETOL1 |
Short Description | Tolerance days |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | NUM04 | |
Data Type | NUMC | Character string with only digits |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
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 | Tol. days |
Medium | 15 | Tolerance days |
Long | 20 | Tolerance in days |
Heading | 9 | Tol. days |
Documentation
Definition
Number of days that must have passed after the expiration of the validity period befor an outline agreement may be archived.
Use
Dependencies
Example
The validity end date of your agreement falls on November 30 and you have entered the value 30 as the tolerance in days. This means that an outline purchase agreement must remain in the system a further 30 days after the validity end date before it can be archived.
This outline agreement will thus not be taken into account by the archiving run until after December 30.
History
Last changed by/on | SAP | 19980218 |
SAP Release Created in |