Hierarchy

⤷

⤷

IMG Activity
ID | ISP_PERIODIZITAT | Maintain Frequencies |
Transaction Code | S_KK4_74001803 | IMG Activity: ISP_PERIODIZITAT |
Created on | 19990816 | |
Customizing Attributes | ISP_PERIODIZITAT | Maintain Frequencies |
Customizing Activity | ISP_PERIODIZITAT | Maintenance of Frequency Rules |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | ISP_PERIODIZITÄT |
In this step, you define frequencies for the publication of editions or media products.
These determine how frequently the editions or media issues are published. When you define frequency, you subdivide a publication period that recurs cyclically into concrete sections (grids).
You must specify the frequency in the master record for an edition (together with the factory calendar) so that automatic issue generation can take place.
If you record your product master data using the media product master, specify the frequency in the master record of the media product. It is used together with the factory calendar when the issue sequence (sequence of issues for the media product) is created automatically.
Example
According to the frequency defined, a certain title can be published daily, weekly, twice a month, monthly, every two months, every quarter, every four months or every six months.
Recommendation
- Restrict the frequencies in the standard delivery to those you actually require.
- If an edition is published less frequently than once a month, we recommend that you create the issues manually. This means you do not need a frequency or a generation rule and you do not have to generate the issues.
Activities
- Check which publication frequencies are used in your company.
- To create a frequency, please proceed as follows:
- Freq. (key for frequency)
- Enter an alphanumeric key of up to 5 characters.
- Rep (repetition period)
- Choose the desired repetition period, e.g. WK MON or YR. The further subdivisions refer to this repetition period, e.g. "12 times a year".
- Gr. (grid)
- Choose the desired publication grid, for example
- DAY, WK or MON.
- GDv (grid divider)
- To copy the chosen grid unchanged, enter the divider 1 in this field.
- To subdivide the grid, enter the appropriate divider. For example, the divider 2 specified for the grid MON means "publication twice a month".
- GFc (grid factor)
- To copy the grid unchanged, enter the factor 1.
- To multiply the size of the grid, enter the appropriate factor. For example, factor 3 specified for the grid MON means "publication each quarter".
- MRp (maximum number of repetitions)
- If the maximum number of repetitions of the grid in the period can be determined automatically, this field is not available for entries.
- Otherwise, enter the appropriate value. For example, the number of repetitions of a day in a month can be 28, 29, 30 or 31.
- D (indicates a daily)
- The system sets this indicator automatically. It determines that the issue with the publication frequency specified is processed as a "periodical with daily publication" in planning.
- Short and long text
- Enter descriptive texts in these fields.
Further notes
You cannot change a frequency on which a generation rule is based because the content of the generation rule (e.g. the number of publication periods generated) depends on the frequency.
Note: You will also use the frequencies defined here when generating daily truck routes. This means the activity is also included among the Customizing settings for truck routes.
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
JDVTJD03 | V - View | SM30 | 0000000000 | Generated table maintenance: JDVTJD03 |
History
Last changed by/on | SAP | 20000818 |
SAP Release Created in |