Hierarchy
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR⤷
PT (Application Component) Personnel Time Management⤷
PTIM (Package) HR Time Management Application Development
Basic Data
| Data Element | TAG |
| Short Description | Current day of accounting |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR2 | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| 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 | 5 | Day |
| Medium | 10 | Curr.day |
| Long | 20 | Current day |
| Heading | 5 | Day |
Supplementary Documentation - TAGBN 0001
Use
The system adds this value to the current date or desired start date. It enters the resulting date as the start date in the maintenance notification, if you entered the priority in the initial screen for processing the PM notification.
If the value for the relative start date is blank, the system enters the system date as the desired start date.
Procedure
Examples
The current date is 02/23, the priority is 2, the value for the relative start date is 4.
The system calculates the start date 02/27 from these entries.
Dependencies
Supplementary Documentation - TAGE1 0001
Use
Two minimum periods (expressed in days) determine which purchasing document items are to be archived.
In the fields Residence time 1 and 2, enter the number of days to be taken into account for archiving.
- Residence time 1 for items without deletion indicator
Before the deletion indicator is set for a document item, the system checks whan the relevant item was last changed.
Changes taken into account include a change in the order quantity and a goods receipt, for example.
The date of the last change is compared with the current date.
If no change has taken place within the specified residence time 1, a deletion indicator is set for the item.
- Residence time 2 for items with deletion indicators
For document items for which the deletion indicator has been set manually or during the archiving run, the system checks how many days have elapsed since the deletion indicator was set.
The complete document is not archived until: - The deletion indicator has been set for all the items of a document
- None of the items have been changed within the specified Residence time 2 (i.e. the last change was the setting of the deletion indicator.
After this, archived documents can be deleted from the database.
Dependencies
You can choose between a one-step and a two-step archiving procedure.
With the one-step procedure, a deletion indicator is set for the items of the purchasing document. In the process, the Residence time 1 is taken into account.
These documents are then archived in the same archiving run.
Residence time 2 is not taken into account.
In the two-step procedure, the deletion indicator is set in a first archiving run, taking the residence time 1 into account. In a second archiving run, the documents are archived taking into account the residence time 2.
Supplementary Documentation - TAGE1 0002
Use
Two minimum periods (expressed in days) determine which purchasing document items are to be archived.
In the fields Residence time 1 and 2, enter the number of days to be taken into account for archiving.
- Residence time 1 for items without deletion indicator
Before the deletion indicator is set for a document item, the system checks whan the relevant item was last changed.
Changes taken into account include a change in the order quantity and a goods receipt, for example.
The date of the last change is compared with the current date.
If no change has taken place within the specified residence time 1, a deletion indicator is set for the item.
- Residence time 2 for items with deletion indicators
For document items for which the deletion indicator has been set manually or during the archiving run, the system checks how many days have elapsed since the deletion indicator was set.
The complete document is not archived until: - The deletion indicator has been set for all the items of a document
- None of the items have been changed within the specified Residence time 2 (i.e. the last change was the setting of the deletion indicator.
After this, archived documents can be deleted from the database.
Dependencies
You can choose between a one-step and a two-step archiving procedure.
With the one-step procedure, a deletion indicator is set for the items of the purchasing document. In the process, the Residence time 1 is taken into account.
These documents are then archived in the same archiving run.
Residence time 2 is not taken into account.
In the two-step procedure, the deletion indicator is set in a first archiving run, taking the residence time 1 into account. In a second archiving run, the documents are archived taking into account the residence time 2.
Supplementary Documentation - TAGE1 0003
Use
Two minimum periods (expressed in days) determine which purchasing document items are to be archived.
In the fields Residence time 1 and 2, enter the number of days to be taken into account for archiving.
- Residence time 1 for items without deletion indicator
Before the deletion indicator is set for a document item, the system checks whan the relevant item was last changed.
Changes taken into account include a change in the order quantity and a goods receipt, for example.
The date of the last change is compared with the current date.
If no change has taken place within the specified residence time 1, a deletion indicator is set for the item.
- Residence time 2 for items with deletion indicators
For document items for which the deletion indicator has been set manually or during the archiving run, the system checks how many days have elapsed since the deletion indicator was set.
The complete document is not archived until: - The deletion indicator has been set for all the items of a document
- None of the items have been changed within the specified Residence time 2 (i.e. the last change was the setting of the deletion indicator.
After this, archived documents can be deleted from the database.
Dependencies
You can choose between a one-step and a two-step archiving procedure.
With the one-step procedure, a deletion indicator is set for the items of the purchasing document. In the process, the Residence time 1 is taken into account.
These documents are then archived in the same archiving run.
Residence time 2 is not taken into account.
In the two-step procedure, the deletion indicator is set in a first archiving run, taking the residence time 1 into account. In a second archiving run, the documents are archived taking into account the residence time 2.
Supplementary Documentation - TAGE1 0004
Use
Two minimum periods (expressed in days) determine which purchasing document items are to be archived.
In the fields Residence time 1 and 2, enter the number of days to be taken into account for archiving.
- Residence time 1 for items without deletion indicator
Before the deletion indicator is set for a document item, the system checks whan the relevant item was last changed.
Changes taken into account include a change in the order quantity and a goods receipt, for example.
The date of the last change is compared with the current date.
If no change has taken place within the specified residence time 1, a deletion indicator is set for the item.
- Residence time 2 for items with deletion indicators
For document items for which the deletion indicator has been set manually or during the archiving run, the system checks how many days have elapsed since the deletion indicator was set.
The complete document is not archived until: - The deletion indicator has been set for all the items of a document
- None of the items have been changed within the specified Residence time 2 (i.e. the last change was the setting of the deletion indicator.
After this, archived documents can be deleted from the database.
Dependencies
You can choose between a one-step and a two-step archiving procedure.
With the one-step procedure, a deletion indicator is set for the items of the purchasing document. In the process, the Residence time 1 is taken into account.
These documents are then archived in the same archiving run.
Residence time 2 is not taken into account.
In the two-step procedure, the deletion indicator is set in a first archiving run, taking the residence time 1 into account. In a second archiving run, the documents are archived taking into account the residence time 2.
Supplementary Documentation - TAGE1 0005
Use
Two minimum periods (expressed in days) determine which purchasing document items are to be archived.
In the fields Residence time 1 and 2, enter the number of days to be taken into account for archiving.
- Residence time 1 for items without deletion indicator
Before the deletion indicator is set for a document item, the system checks whan the relevant item was last changed.
Changes taken into account include a change in the order quantity and a goods receipt, for example.
The date of the last change is compared with the current date.
If no change has taken place within the specified residence time 1, a deletion indicator is set for the item.
- Residence time 2 for items with deletion indicators
For document items for which the deletion indicator has been set manually or during the archiving run, the system checks how many days have elapsed since the deletion indicator was set.
The complete document is not archived until: - The deletion indicator has been set for all the items of a document
- None of the items have been changed within the specified Residence time 2 (i.e. the last change was the setting of the deletion indicator.
After this, archived documents can be deleted from the database.
Dependencies
You can choose between a one-step and a two-step archiving procedure.
With the one-step procedure, a deletion indicator is set for the items of the purchasing document. In the process, the Residence time 1 is taken into account.
These documents are then archived in the same archiving run.
Residence time 2 is not taken into account.
In the two-step procedure, the deletion indicator is set in a first archiving run, taking the residence time 1 into account. In a second archiving run, the documents are archived taking into account the residence time 2.
Supplementary Documentation - TAGE2 0001
Use
Two minimum periods (expressed in days) determine which purchasing document items are to be archived.
In the fields Residence time 1 and 2, enter the number of days to be taken into account for archiving.
- Residence time 1 for items without deletion indicator
Before the deletion indicator is set for a document item, the system checks whan the relevant item was last changed.
Changes taken into account include a change in the order quantity and a goods receipt, for example.
The date of the last change is compared with the current date.
If no change has taken place within the specified residence time 1, a deletion indicator is set for the item.
- Residence time 2 for items with deletion indicators
For document items for which the deletion indicator has been set manually or during the archiving run, the system checks how many days have elapsed since the deletion indicator was set.
The complete document is not archived until: - The deletion indicator has been set for all the items of a document
- None of the items have been changed within the specified Residence time 2 (i.e. the last change was the setting of the deletion indicator.
After this, archived documents can be deleted from the database.
Dependencies
You can choose between a one-step and a two-step archiving procedure.
With the one-step procedure, a deletion indicator is set for the items of the purchasing document. In the process, the Residence time 1 is taken into account.
These documents are then archived in the same archiving run.
Residence time 2 is not taken into account.
In the two-step procedure, the deletion indicator is set in a first archiving run, taking the residence time 1 into account. In a second archiving run, the documents are archived taking into account the residence time 2.
Supplementary Documentation - TAGE2 0002
Use
Two minimum periods (expressed in days) determine which purchasing document items are to be archived.
In the fields Residence time 1 and 2, enter the number of days to be taken into account for archiving.
- Residence time 1 for items without deletion indicator
Before the deletion indicator is set for a document item, the system checks whan the relevant item was last changed.
Changes taken into account include a change in the order quantity and a goods receipt, for example.
The date of the last change is compared with the current date.
If no change has taken place within the specified residence time 1, a deletion indicator is set for the item.
- Residence time 2 for items with deletion indicators
For document items for which the deletion indicator has been set manually or during the archiving run, the system checks how many days have elapsed since the deletion indicator was set.
The complete document is not archived until: - The deletion indicator has been set for all the items of a document
- None of the items have been changed within the specified Residence time 2 (i.e. the last change was the setting of the deletion indicator.
After this, archived documents can be deleted from the database.
Dependencies
You can choose between a one-step and a two-step archiving procedure.
With the one-step procedure, a deletion indicator is set for the items of the purchasing document. In the process, the Residence time 1 is taken into account.
These documents are then archived in the same archiving run.
Residence time 2 is not taken into account.
In the two-step procedure, the deletion indicator is set in a first archiving run, taking the residence time 1 into account. In a second archiving run, the documents are archived taking into account the residence time 2.
Supplementary Documentation - TAGE2 0003
Use
Two minimum periods (expressed in days) determine which purchasing document items are to be archived.
In the fields Residence time 1 and 2, enter the number of days to be taken into account for archiving.
- Residence time 1 for items without deletion indicator
Before the deletion indicator is set for a document item, the system checks whan the relevant item was last changed.
Changes taken into account include a change in the order quantity and a goods receipt, for example.
The date of the last change is compared with the current date.
If no change has taken place within the specified residence time 1, a deletion indicator is set for the item.
- Residence time 2 for items with deletion indicators
For document items for which the deletion indicator has been set manually or during the archiving run, the system checks how many days have elapsed since the deletion indicator was set.
The complete document is not archived until: - The deletion indicator has been set for all the items of a document
- None of the items have been changed within the specified Residence time 2 (i.e. the last change was the setting of the deletion indicator.
After this, archived documents can be deleted from the database.
Dependencies
You can choose between a one-step and a two-step archiving procedure.
With the one-step procedure, a deletion indicator is set for the items of the purchasing document. In the process, the Residence time 1 is taken into account.
These documents are then archived in the same archiving run.
Residence time 2 is not taken into account.
In the two-step procedure, the deletion indicator is set in a first archiving run, taking the residence time 1 into account. In a second archiving run, the documents are archived taking into account the residence time 2.
Supplementary Documentation - TAGE2 0004
Use
Two minimum periods (expressed in days) determine which purchasing document items are to be archived.
In the fields Residence time 1 and 2, enter the number of days to be taken into account for archiving.
- Residence time 1 for items without deletion indicator
Before the deletion indicator is set for a document item, the system checks whan the relevant item was last changed.
Changes taken into account include a change in the order quantity and a goods receipt, for example.
The date of the last change is compared with the current date.
If no change has taken place within the specified residence time 1, a deletion indicator is set for the item.
- Residence time 2 for items with deletion indicators
For document items for which the deletion indicator has been set manually or during the archiving run, the system checks how many days have elapsed since the deletion indicator was set.
The complete document is not archived until: - The deletion indicator has been set for all the items of a document
- None of the items have been changed within the specified Residence time 2 (i.e. the last change was the setting of the deletion indicator.
After this, archived documents can be deleted from the database.
Dependencies
You can choose between a one-step and a two-step archiving procedure.
With the one-step procedure, a deletion indicator is set for the items of the purchasing document. In the process, the Residence time 1 is taken into account.
These documents are then archived in the same archiving run.
Residence time 2 is not taken into account.
In the two-step procedure, the deletion indicator is set in a first archiving run, taking the residence time 1 into account. In a second archiving run, the documents are archived taking into account the residence time 2.
Supplementary Documentation - TAGEN 0001
Use
The system adds this value to the current date or desired start date. It enters the resulting date as the end date in the maintenance notification, if you entered the priority in the initial screen for processing the PM notification.
Procedure
Examples
The current date is 02/23, the priority is 2, the value for the relative end date is 4.
The system calculates the end date 02/27 from these entries.
Supplementary Documentation - TAGINEIP 0001
Examples
Examples for creation and interpretation of a generation rule
Example for a non-daily edition
The frequency rule is explained here as it would be for publication:
- Repetition period : Year
- Grid divider : 1
- Grid factor : 1
This results in 12 individual periods:
- Individual period 1 : January
- Individual period 2 : February
...
- Individual period 12: December
In the generation rule, the individual periods are displayed in a tabular view containing the following columns:
- Individual period
- Planned variant type (StIVTy)
- Current day in individual period (DP)
- Current week in individual period (WP)
- Current month in individual period (MP)
- Public holiday collision (PHolKoll.)
The variant types must now be defined for each individual period:
Example of a generation rule (non-daily)
In the sequence MP/WP/DP, the FIRST entry is a time offset and all
others are absolute times.
Ind.period StIVTy DP WP MP PHolColl.
-----------------------------------------------------------
1 MZ 0 0 0 X
2 MZ 0 0 0 +
3 MZ 0 0 2 -
4 MZ 0 3 2 +
5 MZ 4 3 2 +
6 MZ 4 3 0 +
7 MZ 4 0 0 +
8 MZ 0 0 0 +
9 MZ 0 0 0 +
10 MZ 0 0 0 +
11 MZ 0 0 0 +
12 MZ 0 0 0 +
Interpretation of this generation rule
The individual period date is the start of the individual period irrespective of any additional time offset, absolute time and public holiday collisions that may have been specified.
Individual period 1 (= January):
-StIVTy=MZ: The January issue of the monthly magazine (MZ)
has the individual period date January 1st.
No time offset or absolute times are specified.
The provisional publication date remains January
1st. The system now checks whether this date is a
public holiday. January 1st is a public holiday.
The indicator for public holiday collision
defines that publication is still to take place on
a public holiday. This means that the publication
date for the January issue is January 1st.
tag für die Januarausgabe ist damit der 1.Januar.
(If a '+' was entered in this field, the issue
would be published on the workday following the
public holiday)
Individual period 2 (= February):
-StIVTy=MZ: The February issue of the monthly magazine (MZ)
has the individual period date February 1st.
No time offset or absolute times are specified.
The provisional publication date remains
February 1st. The system now checks whether this
date is a public holiday. February 1st is not a
public holiday. (The indicator for public holiday
collision is therefore ignored.) This means that
the publication date for the February issue is
February 1st.
(If February 1st were a public holiday, the
February issue would be published on the workday
following it.)
Individual period 3 (= March):
-StIVTy=MZ: The March issue of the monthly magazine (MZ) has
the individual period date March 1st. A time
offset of 2 months into the future is specified.
This means the provisional publication date is
May 1st. May 1st is a public holiday. The indicator
for public holiday collision defines that
publication is to take place on the last workday
before the public holiday. (Non-working days in
the factory calendar are taken into account here.)
Individual period 4 (= April):
-StIVTy=MZ: The April issue of the monthly magazine (MZ) has
the individual period date April 1st. A time
offset of 2 months is specified together with an
absolute time of 3 for the week. This means that
the provisional publication date is moved 2 months
into the future, to June 1st, and then to the 3rd
week in this month, to the beginning of this 3rd
week in June (the Monday). (A week is assigned
to a month if the whole of the week starting
from the Monday belongs to that month.) The public
holiday collision is handled as above.
Individual period 5 (= May):
-StIVTy=MZ: The May issue of the monthly magazine (MZ) has
the individual period date May 1st. A time
offset of 2 months is specified together with an
absolute time of 3 for the week and 4 for the
day. This means that the provisional publication
date is moved 2 months into the future, to June 1st,
and then to the 3rd week in this month and the
Supplementary Documentation - TAGINEIP 0002
Examples
Examples for creation and interpretation of a generation rule
1. Example of a non-daily truck route
The frequency rule is explained here as it would be for a truck route run monthly:
- Repetition period : Year
- Grid : Month
- Grid divider : 1
- Grid factor : 1
This results in 12 individual periods:
- Individual period 1 : January
- Individual period 2 : February
...
- Individual period 12: December
In the generation rule, the individual periods are displayed in a tabular view containing the following columns (truck route generation data):
- Individual period
- Generate truck route (GTRte)
- Current day in individual period (DP)
- Current week in individual period (WP)
- Current month in individual period (MP)
- Public holiday collision (PHColl.)
You must now define the truck route generation data for each individual period.
2. Example of a generation rule (non-daily)
In the sequence MP/WP/DP, the FIRST entry is a time offset and all others are absolute times.
Ind.period GTRte DP WP MP PHolColl.
-----------------------------------------------------------
1 X 0 0 0 X
2 X 0 0 0 +
3 X 0 0 2 -
4 X 0 3 2 +
5 X 4 3 2 +
6 X 4 3 0 +
7 X 4 0 0 +
8 X 0 0 0 +
9 X 0 0 0 +
10 X 0 0 0 +
11 X 0 0 0 +
12 X 0 0 0 +
Interpretation of this generation rule
The individual period date is the start of the individual period irrespective of any additional time offset, absolute time and public holiday collisions that may have been specified.
Individual period 1 ( = January):
-GTRte=X : The January truck route has the individual period date
January 1st. No time offset or absolute times are
specified. The provisional shipping date remains
January 1st. The system now checks if this date
is a public holiday. January 1st is a public
holiday. The indicator for public holiday collision
defines that the truck route is still to be run on a
public holiday. This means that the shipping date
for the January issue is January 1st.
(If a '+' was entered in this field, the truck route
would be run on the workday following the public
holiday.)
Individual period 2 ( = February):
-GTRte=X : The February truck route has the individual period date
February 1st. No time offset or absolute times are
specified. The provisional shipping date remains
February 1st. The system now checks if this date
is a public holiday. February 1st is not a public
holiday. (The indicator for public holiday collision
is therefore ignored.) This means that the shipping
date for the February issue is February 1st.
(If February 1st were a public holiday, the February
truck route would run on the workday following it.)
Individual period 3 ( = March):
-GTRte=X : The March truck route has the individual period date
March 1st. A time offset of 2 months into the
future is specified. This means the provisional
shipping date is May 1st. May 1st is a public
holiday. The indicator for public holiday collision
defines that the truck route is to be run on the last
workday before the public holiday. (Non-working
days in the factory calendar are taken into account
here.)
Individual period 4 ( = April):
-GTRte=X : The April truck route has the individual period date
April 1st. A time offset of 2 months is specified
together with an absolute time of 3 for the week.
This means that the provisional shipping date is
moved 2 months into the future, to June 1st, and
then to the 3rd week in this month, to the beginning
of this 3rd week in June (the Monday). (A week is
assigned to a month if the whole of the week starting
from the Monday belongs to that month.) The public
holiday collision is handled as above.
Individual period 5 ( = May):
-GTRte=X : The May truck route has the individual period date
May 1st. A time offset of 2 months is specified
together with an absolute time of 3 for the week
and 4 for the day. This means that the provisional
shipping date is moved 2 months into the future, to
June 1st, and then to the 3rd week in this month
and the 4th day in this week, the Thursday of the
3rd week in June. The public holiday collision is
handled as above.
Individual period 6 ( = June):
-GTRte=X : The June truck route has the individual period&#x
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
Supplementary Documentation - TAGRUPPE 0001
Use
The service category entered here refers in each case to the service in the in-house service catalog and not to the service in the billing catalog.
Procedure
Examples
Dependencies
Supplementary Documentation - TAGTY 0001
Procedure
Please note the difference between 0 and BLANK:
If the day type is BLANK, the System uses the day type which is valid for the respective calendar day.
If you want to change the day type manually to Work/paid, enter 0 in this field.
History
| Last changed by/on | SAP | 19920312 |
| SAP Release Created in |
