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 | VAVARTYP |
| Short Description | Issue Variant Type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | VAVARTYP | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| Value Table | TJD05 |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ISSUE_VARIANT_TYPE | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | IssVarType |
| Medium | 15 | Issue Var.Type |
| Long | 20 | Issue Variant Type |
| Heading | 2 | VT |
Documentation
Definition
Issue variant types (media issue variant types) classify issues or media issues according to how they are made up of sections and columns. An issue variant type also classifies publication times.
To use the example of a daily newspaper, the issue variant type corresponds to a weekday (Monday edition, Tuesday edition and so on) or to the typical structure of an issue on a particular weekday.
Supplementary Documentation - VAVARTYPAF0001
Examples
Examples for creating/interpreting a generation rule
1. Daily edition
The frequency rule for a daily is always defined as follows:
- Repetition period : Week
- Grid : Day
- Grid divider : 1
- Grid factor : 1
This results in 7 individual periods:
- Indiv.period 1 : Monday
- Indiv.period 2 : Tuesday
...
- Indiv.period 7 : Sunday
The individual periods are displayed in the generation rule as a table containing the following columns:
- Individual period
- Planned issue type
- Actual issue type if date is day before a public holiday
- Actual issue type if date is a public holiday
- Actual issue type if day is day after a public holiday
- Actual issue type if day is two days after a public holiday
You must now define the issue types for each individual period:
Example of a generation rule (daily):
-------------------------------------
Ind.per. StITy ITyBPH ITyPH ITy1PH ITy2PH
-----------------------------------------------------------
1 MO SA MO MO
2 TU SA TU TU
3 WE SA WE WE
4 TH SA TH TH
5 FR SA FR FR
6 SA SA SA SA
7
Interpretation of this generation rule:
---------------------------------------
Individual period 1 (Monday):
-StITy =MO: A Monday issue is published as standard on Mondays
-ITyBPH=SA: If the Monday is the day before a public holiday
(Tuesday being the public holiday), an issue is
generated on Monday with the actual issue type
'Saturday' (the planned issue type remains 'Monday').
-ITyPH = : If the Monday is a public holiday, no issues are
generated that day.
-ITy1PH=MO: If the Monday is the day after a public holiday
(the public holiday being Sunday), an issue is
generated on Monday with the actual issue type
'Monday' (the planned issue type remains 'Monday').
-ITy2PH=MO: If the Monday is two days after a public holiday
(the public holiday being on Saturday), an issue
is generated on Monday with the actual issue type
'Monday' (the planned issue type remains 'Monday').
Individual period 2 (Tuesday):
-StITy =TU: A Tuesday issue is published as standard on Tuesdays
-ITyBPH=SA: If the Tuesday is the day before a public holiday
(Wednesday being the public holiday), an issue is
generated on Tuesday with the actual issue type
'Saturday' (the planned issue type remains 'Tuesday').
-ITyPH = : If the Tuesday is a public holiday, no issues are
generated that day.
-ITy1PH=TU: If the Tuesday is the day after a public holiday
(the public holiday being Monday), an issue is
generated on Tuesday with the actual issue type
'Tuesday' (the planned issue type remains 'Tuesday').
-ITy2PH=TU: If the Tuesday is two days after a public holiday
(the public holiday being on Sunday), an issue
is generated on Tuesday with the actual issue type
'Tuesday' (the planned issue type remains 'Tuesday').
The other individual periods are interpreted in the same way.
Meaning of factory calendar specified for edition:
When processing dailies, the factory calendar is not taken into account but simply the assigned public holiday calendar. (The factory calendar is defined in terms of working days and non-working days, so that Saturday is generally a non-working day but not a public holiday. Public holidays are defined in the public holiday calendar.) If the generation rule is defined for Saturday (individual period 6), generation is based on whether or not the Saturday is defined as a public holiday in the public holiday calendar. It is irrelevant in issue generation whether or not the Saturday in the factory calendar is a non-working day.
Supplementary Documentation - VAVARTYPF10001
Examples
Examples for creating/interpreting a generation rule
1. Daily edition
The frequency rule for a daily is always defined as follows:
- Repetition period : Week
- Grid : Day
- Grid divider : 1
- Grid factor : 1
This results in 7 individual periods:
- Indiv.period 1 : Monday
- Indiv.period 2 : Tuesday
...
- Indiv.period 7 : Sunday
The individual periods are displayed in the generation rule as a table containing the following columns:
- Individual period
- Planned issue type
- Actual issue type if date is day before a public holiday
- Actual issue type if date is a public holiday
- Actual issue type if day is day after a public holiday
- Actual issue type if day is two days after a public holiday
You must now define the issue types for each individual period:
Example of a generation rule (daily):
-------------------------------------
Ind.per. StITy ITyBPH ITyPH ITy1PH ITy2PH
-----------------------------------------------------------
1 MO SA MO MO
2 TU SA TU TU
3 WE SA WE WE
4 TH SA TH TH
5 FR SA FR FR
6 SA SA SA SA
7
Interpretation of this generation rule:
---------------------------------------
Individual period 1 (Monday):
-StITy =MO: A Monday issue is published as standard on Mondays
-ITyBPH=SA: If the Monday is the day before a public holiday
(Tuesday being the public holiday), an issue is
generated on Monday with the actual issue type
'Saturday' (the planned issue type remains 'Monday').
-ITyPH = : If the Monday is a public holiday, no issues are
generated that day.
-ITy1PH=MO: If the Monday is the day after a public holiday
(the public holiday being Sunday), an issue is
generated on Monday with the actual issue type
'Monday' (the planned issue type remains 'Monday').
-ITy2PH=MO: If the Monday is two days after a public holiday
(the public holiday being on Saturday), an issue
is generated on Monday with the actual issue type
'Monday' (the planned issue type remains 'Monday').
Individual period 2 (Tuesday):
-StITy =TU: A Tuesday issue is published as standard on Tuesdays
-ITyBPH=SA: If the Tuesday is the day before a public holiday
(Wednesday being the public holiday), an issue is
generated on Tuesday with the actual issue type
'Saturday' (the planned issue type remains 'Tuesday').
-ITyPH = : If the Tuesday is a public holiday, no issues are
generated that day.
-ITy1PH=TU: If the Tuesday is the day after a public holiday
(the public holiday being Monday), an issue is
generated on Tuesday with the actual issue type
'Tuesday' (the planned issue type remains 'Tuesday').
-ITy2PH=TU: If the Tuesday is two days after a public holiday
(the public holiday being on Sunday), an issue
is generated on Tuesday with the actual issue type
'Tuesday' (the planned issue type remains 'Tuesday').
The other individual periods are interpreted in the same way.
Meaning of factory calendar specified for edition:
When processing dailies, the factory calendar is not taken into account but simply the assigned public holiday calendar. (The factory calendar is defined in terms of working days and non-working days, so that Saturday is generally a non-working day but not a public holiday. Public holidays are defined in the public holiday calendar.) If the generation rule is defined for Saturday (individual period 6), generation is based on whether or not the Saturday is defined as a public holiday in the public holiday calendar. It is irrelevant in issue generation whether or not the Saturday in the factory calendar is a non-working day.
Supplementary Documentation - VAVARTYPF20001
Examples
Examples for creating/interpreting a generation rule
1. Daily edition
The frequency rule for a daily is always defined as follows:
- Repetition period : Week
- Grid : Day
- Grid divider : 1
- Grid factor : 1
This results in 7 individual periods:
- Indiv.period 1 : Monday
- Indiv.period 2 : Tuesday
...
- Indiv.period 7 : Sunday
The individual periods are displayed in the generation rule as a table containing the following columns:
- Individual period
- Planned issue type
- Actual issue type if date is day before a public holiday
- Actual issue type if date is a public holiday
- Actual issue type if day is day after a public holiday
- Actual issue type if day is two days after a public holiday
You must now define the issue types for each individual period:
Example of a generation rule (daily):
-------------------------------------
Ind.per. StITy ITyBPH ITyPH ITy1PH ITy2PH
-----------------------------------------------------------
1 MO SA MO MO
2 TU SA TU TU
3 WE SA WE WE
4 TH SA TH TH
5 FR SA FR FR
6 SA SA SA SA
7
Interpretation of this generation rule:
---------------------------------------
Individual period 1 (Monday):
-StITy =MO: A Monday issue is published as standard on Mondays
-ITyBPH=SA: If the Monday is the day before a public holiday
(Tuesday being the public holiday), an issue is
generated on Monday with the actual issue type
'Saturday' (the planned issue type remains 'Monday').
-ITyPH = : If the Monday is a public holiday, no issues are
generated that day.
-ITy1PH=MO: If the Monday is the day after a public holiday
(the public holiday being Sunday), an issue is
generated on Monday with the actual issue type
'Monday' (the planned issue type remains 'Monday').
-ITy2PH=MO: If the Monday is two days after a public holiday
(the public holiday being on Saturday), an issue
is generated on Monday with the actual issue type
'Monday' (the planned issue type remains 'Monday').
Individual period 2 (Tuesday):
-StITy =TU: A Tuesday issue is published as standard on Tuesdays
-ITyBPH=SA: If the Tuesday is the day before a public holiday
(Wednesday being the public holiday), an issue is
generated on Tuesday with the actual issue type
'Saturday' (the planned issue type remains 'Tuesday').
-ITyPH = : If the Tuesday is a public holiday, no issues are
generated that day.
-ITy1PH=TU: If the Tuesday is the day after a public holiday
(the public holiday being Monday), an issue is
generated on Tuesday with the actual issue type
'Tuesday' (the planned issue type remains 'Tuesday').
-ITy2PH=TU: If the Tuesday is two days after a public holiday
(the public holiday being on Sunday), an issue
is generated on Tuesday with the actual issue type
'Tuesday' (the planned issue type remains 'Tuesday').
The other individual periods are interpreted in the same way.
Meaning of factory calendar specified for edition:
When processing dailies, the factory calendar is not taken into account but simply the assigned public holiday calendar. (The factory calendar is defined in terms of working days and non-working days, so that Saturday is generally a non-working day but not a public holiday. Public holidays are defined in the public holiday calendar.) If the generation rule is defined for Saturday (individual period 6), generation is based on whether or not the Saturday is defined as a public holiday in the public holiday calendar. It is irrelevant in issue generation whether or not the Saturday in the factory calendar is a non-working day.
Supplementary Documentation - VAVARTYPST0001
Example
- Example of 'daily publication':
- The following is defined for individual period 1:
Standard issue type = MO (Monday issue)
On Monday August 2, 1993: Publication as type MO (the Monday is not a public holiday, is not the day before a public holiday and is not one or two days after a public holiday. If any of these conditions applied, the issue type defined would then be published on the Monday). - The following is defined for individual period 1:
Standard issue type = blank
On Monday August 2, 1993: No publication (if the Monday was a public holiday, the day before a public holiday or one/two days after a public holiday, the issue type defined would be published on the Monday).
Examples
Examples for creating/interpreting a generation rule
1. Daily edition
The frequency rule for a daily is always defined as follows:
- Repetition period : Week
- Grid : Day
- Grid divider : 1
- Grid factor : 1
This results in 7 individual periods:
- Indiv.period 1 : Monday
- Indiv.period 2 : Tuesday
...
- Indiv.period 7 : Sunday
The individual periods are displayed in the generation rule as a table containing the following columns:
- Individual period
- Planned issue type
- Actual issue type if date is day before a public holiday
- Actual issue type if date is a public holiday
- Actual issue type if day is day after a public holiday
- Actual issue type if day is two days after a public holiday
You must now define the issue types for each individual period:
Example of a generation rule (daily):
-------------------------------------
Ind.per. StITy ITyBPH ITyPH ITy1PH ITy2PH
-----------------------------------------------------------
1 MO SA MO MO
2 TU SA TU TU
3 WE SA WE WE
4 TH SA TH TH
5 FR SA FR FR
6 SA SA SA SA
7
Interpretation of this generation rule:
---------------------------------------
Individual period 1 (Monday):
-StITy =MO: A Monday issue is published as standard on Mondays
-ITyBPH=SA: If the Monday is the day before a public holiday
(Tuesday being the public holiday), an issue is
generated on Monday with the actual issue type
'Saturday' (the planned issue type remains 'Monday').
-ITyPH = : If the Monday is a public holiday, no issues are
generated that day.
-ITy1PH=MO: If the Monday is the day after a public holiday
(the public holiday being Sunday), an issue is
generated on Monday with the actual issue type
'Monday' (the planned issue type remains 'Monday').
-ITy2PH=MO: If the Monday is two days after a public holiday
(the public holiday being on Saturday), an issue
is generated on Monday with the actual issue type
'Monday' (the planned issue type remains 'Monday').
Individual period 2 (Tuesday):
-StITy =TU: A Tuesday issue is published as standard on Tuesdays
-ITyBPH=SA: If the Tuesday is the day before a public holiday
(Wednesday being the public holiday), an issue is
generated on Tuesday with the actual issue type
'Saturday' (the planned issue type remains 'Tuesday').
-ITyPH = : If the Tuesday is a public holiday, no issues are
generated that day.
-ITy1PH=TU: If the Tuesday is the day after a public holiday
(the public holiday being Monday), an issue is
generated on Tuesday with the actual issue type
'Tuesday' (the planned issue type remains 'Tuesday').
-ITy2PH=TU: If the Tuesday is two days after a public holiday
(the public holiday being on Sunday), an issue
is generated on Tuesday with the actual issue type
'Tuesday' (the planned issue type remains 'Tuesday').
The other individual periods are interpreted in the same way.
Meaning of factory calendar specified for edition:
When processing dailies, the factory calendar is not taken into account but simply the assigned public holiday calendar. (The factory calendar is defined in terms of working days and non-working days, so that Saturday is generally a non-working day but not a public holiday. Public holidays are defined in the public holiday calendar.) If the generation rule is defined for Saturday (individual period 6), generation is based on whether or not the Saturday is defined as a public holiday in the public holiday calendar. It is irrelevant in issue generation whether or not the Saturday in the factory calendar is a non-working day.
Supplementary Documentation - VAVARTYPST0002
Use
- Example of non-daily publication frequency: Monthly publication in year
- If the following setting is entered for individual period 1:
Standard issue type = MZ (Monthly issue)
According to time offset and absolute time specifications and public holiday collisions, January 5th was determined as the publication date for the January issue. This means that the January issue of the monthly magazine is published on January 5th. - If the following setting is specified:
Standard issue type = blank
The January issue is not published (in this case, it is also not possible to have it published on the basis of time offsets or public holiday collisions).
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 &#
Supplementary Documentation - VAVARTYPVF0001
Examples
Examples for creating/interpreting a generation rule
1. Daily edition
The frequency rule for a daily is always defined as follows:
- Repetition period : Week
- Grid : Day
- Grid divider : 1
- Grid factor : 1
This results in 7 individual periods:
- Indiv.period 1 : Monday
- Indiv.period 2 : Tuesday
...
- Indiv.period 7 : Sunday
The individual periods are displayed in the generation rule as a table containing the following columns:
- Individual period
- Planned issue type
- Actual issue type if date is day before a public holiday
- Actual issue type if date is a public holiday
- Actual issue type if day is day after a public holiday
- Actual issue type if day is two days after a public holiday
You must now define the issue types for each individual period:
Example of a generation rule (daily):
-------------------------------------
Ind.per. StITy ITyBPH ITyPH ITy1PH ITy2PH
-----------------------------------------------------------
1 MO SA MO MO
2 TU SA TU TU
3 WE SA WE WE
4 TH SA TH TH
5 FR SA FR FR
6 SA SA SA SA
7
Interpretation of this generation rule:
---------------------------------------
Individual period 1 (Monday):
-StITy =MO: A Monday issue is published as standard on Mondays
-ITyBPH=SA: If the Monday is the day before a public holiday
(Tuesday being the public holiday), an issue is
generated on Monday with the actual issue type
'Saturday' (the planned issue type remains 'Monday').
-ITyPH = : If the Monday is a public holiday, no issues are
generated that day.
-ITy1PH=MO: If the Monday is the day after a public holiday
(the public holiday being Sunday), an issue is
generated on Monday with the actual issue type
'Monday' (the planned issue type remains 'Monday').
-ITy2PH=MO: If the Monday is two days after a public holiday
(the public holiday being on Saturday), an issue
is generated on Monday with the actual issue type
'Monday' (the planned issue type remains 'Monday').
Individual period 2 (Tuesday):
-StITy =TU: A Tuesday issue is published as standard on Tuesdays
-ITyBPH=SA: If the Tuesday is the day before a public holiday
(Wednesday being the public holiday), an issue is
generated on Tuesday with the actual issue type
'Saturday' (the planned issue type remains 'Tuesday').
-ITyPH = : If the Tuesday is a public holiday, no issues are
generated that day.
-ITy1PH=TU: If the Tuesday is the day after a public holiday
(the public holiday being Monday), an issue is
generated on Tuesday with the actual issue type
'Tuesday' (the planned issue type remains 'Tuesday').
-ITy2PH=TU: If the Tuesday is two days after a public holiday
(the public holiday being on Sunday), an issue
is generated on Tuesday with the actual issue type
'Tuesday' (the planned issue type remains 'Tuesday').
The other individual periods are interpreted in the same way.
Meaning of factory calendar specified for edition:
When processing dailies, the factory calendar is not taken into account but simply the assigned public holiday calendar. (The factory calendar is defined in terms of working days and non-working days, so that Saturday is generally a non-working day but not a public holiday. Public holidays are defined in the public holiday calendar.) If the generation rule is defined for Saturday (individual period 6), generation is based on whether or not the Saturday is defined as a public holiday in the public holiday calendar. It is irrelevant in issue generation whether or not the Saturday in the factory calendar is a non-working day.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
