Hierarchy
⤷ SD-BIL-IV-SBI (Application Component) Self-Billing Proced.
⤷ VASB (Package) Application Development R/3 Sales / Self-Billing Process
Basic Data
Data Element | DATEREPC |
Short Description | Date Limit for Duplicate Check |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DATE | |
Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 10 | |
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 | Date Limit |
Medium | 15 | Date Limit |
Long | 22 | DateLimitDuplicateChck |
Heading | 5 | DtLmt |
Documentation
Definition
Restricts the period of time for which the system checks for double-usage of external transmission number. When an external transmission number is transmitted by an EDI partner, the system always checks whether the number has already been transmitted.
Procedure
If this date limit field is empty, the system checks the complete period of time since EDI communication was begun.
If a date is set, the system checks only those transmissions whose creation date lies between the current date and the date limit (inclusive).
Examples
You should set a date limit if your EDI partner restarts numbering from a certain date, and therefore reuses numbers that are already in your system.
Dependencies
If the neighboring field "Yearly repetition" is checked, then only the day and month of the date limit are used. The system calculates the year dynamically according to the current year. This allows you to cover a yearly restart of numbering by setting the date limit only once.
For more information, see the field help for the 'Yearly repetition' field.
History
Last changed by/on | SAP | 20030411 |
SAP Release Created in |