Hierarchy
IS-M (Software Component) SAP MEDIA⤷
IS-M (Application Component) SAP Media⤷
JSD (Package) Appl. dev. R/3 Publishing Sales and Distribution System
Basic Data
| Data Element | MOINEIP |
| Short Description | Current month in individual period |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | MOINEIP | |
| Data Type | DEC | Counter or amount field with comma and sign |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| 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 | MthInIPer. |
| Medium | 15 | Mth in ind.per. |
| Long | 20 | Month in ind.period |
| Heading | 2 | MP |
Documentation
Definition
The current month in the individual period is part of the scheduling of non-daily publications.
Within the generation rule, the generation date for each individual period for non-dailies can be specified in greater detail using time offsets and absolute times. The generation date, which is determined initially from the frequency rule data - grid/repetition period/grid divider/grid factor - can be moved by means of a 'time offset' (positive and negative values are possible) and positioned exactly using one or more 'absolute times' (only positive values allowed).
In the sequence month/week/day in individual period, the first non-initial entry is a 'time offset specification' and all others are 'absolute time specifications'.
For example: Month in individual period:
Week in individual period: 4-
The week is the 'time offset specification' and the day is the 'absolute time specification'.
The following restriction applies to 'time offset specifications': a time offset can only be specified up to the grid size.
For example, if the grid is a week, the time offset cannot be set to a month.
'Absolute times' can only be specified if there is a time offset. The time offset is the basis for assigning the absolute time specification.
e.g. Time offset = weekly entry
Absolute time = daily entry 3
Means: the 3rd day in the week (moved by the time offset).
e.g. Time offset = monthly entry
Absolute time = weekly entry 2
Absolute time = daily entry 3
Means: 3rd day in the 2nd week determined by the monthly
time offset.
e.g. Time offset = monthly entry
Absolute time = daily entry 13
Means: 13th day in month determined by time offset.
Since 'month in individual period' is the largest move that can be made, the entry is always interpreted as a time offset:
e.g.: If the month in the individual period is 3, the generation
date is postponed by 3 months (if the entry is 3-, it is
moved back 3 months into the past).
Supplementary Documentation - MOINEIP 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 - MOINEIP 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
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
