Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-BMT-OM (Application Component) Organizational Management⤷
SP00 (Package) Organization and Planning
Basic Data
| Data Element | TAGNR |
| Short Description | Day Number |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUM03 | |
| Data Type | NUMC | Character string with only digits |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | DAY_NO | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 8 | Day No. |
| Medium | 15 | Day Number |
| Long | 20 | Day Number |
| Heading | 3 | Day |
Documentation
Definition
The sequential number enables you to define a schedule model
made up of time blocks for example, or actions consisting of a
sequence of infotypes.
Supplementary Documentation - TAGNR 1000
Use
Every business event day within a schedule is provided with a day
number.
The day number is counted relative to the first business event day
(Day number = 001) that is, the day number is used to determine how many days after the business event start each individual
business event day is.
Missing day numbers within a schedule are interpreted as free days, that is, a free day exists if the day number of the business event
is greater than the number of the preceding business event day by
more than one.
Example 1: Week business event
Day numbers:
001
002
003
004
005
Example 2 : Two day training business event with 2 free days
Day numbers:
001
004
Example 3: Two-day training business event; The second business
event day is a week after the first one
Day numbers:
001
008
Procedure
Example
Dependencies
Supplementary Documentation - TAGNR 1022
Use
Every business event day within a schedule is assigned a day number.
The day number is counted relative to the first business event day (day number = 001). Each day number indicates how many days after the start of the business event it is.
Missing day numbers within a schedule are interpreted as free days. In other words, if a free day or days occur, this is indicated by a gap of one or more between the business event day numbers.
Example 1 : One-week business event with no free days
Day numbers:
001
002
003
004
005
Example 2: Business event with 2 free days
Day numbers:
001
004
Example 3: Two-day training business event; The second business
event day is a week after the first one
Day numbers:
001
008
Supplementary Documentation - TAGNR 3000
Use
The field is used as a flag here.
The flag displays whether a user-defined schedule has been set or not.
Value is 1 if a user-defined schedule is set, otherwise it is 0.
Procedure
Example
Dependencies
Supplementary Documentation - TAGNR 4023
Use
Every business event day within a schedule is provided with a
day number. The day number is relative to the first business event
day (day number = 001), that is, the day number is used to determine how many days after the business event start each individual business
event day is. Missing day numbers within a schedule are interpreted
as free days, that is, a free day exists if the day number of a
business event day is greater than the number of the preceding
business event day by more than one.
Example 1: Week business event
Day numbers:
001
002
003
004
005
Example 2: Two day business event with 2 free days
Day numbers:
001
004
Example 3: Two-day business event; The second business event day is
one week after the first one
Day numbers:
001
008
The field contains the day number of the corresponding day from the user-defined schedule which is set in infotype 1022 (schedule) for the business event.
Procedure
Example
Dependencies
History
| Last changed by/on | SAP | 20041216 |
| SAP Release Created in |
