Description

This program is used for regenerative planning of circulation planning.

Which data is updated?
The program determines the daily quantities of an issue with which thecustomer is supplied by the publisher, based on the orders on hand.These daily quantities per issue are recorded along with otheradditional information in the deliveries (JVTLFNG).
In addition, the program updates information on which orders aresupplied by which deliveries (JVTLFZUO).
The program sets the status of the planning trigger (see 'Selectionoptions').
If there are netchange records in the system for orders for whichplanning took place by means of regenerative planning, the programdeletes these records.

Selection options
Regenerative planning for circulation planning is controlled byplanning triggers. Planning triggers relevant for planning should havethe following characteristics:
- The period of the planning trigger should not be in the past
- The lock date should be past
- The planning status should be something other than 'Planning
completed'
The selection screen also allows you to restrict the relevant planningtriggers to certain plants, editions and trigger periods.
Planning takes place for the selected planning triggers in sequence.
Once planning is completed, the status of the planning trigger is setto 'Planning completed' or 'Deletion completed'.
Further parameters allow you to select a test run (without databaseupdates) and a compact list (displaying the triggers withoutdeliveries).

Precondition

Which data must be maintained?
There must be planning triggers that correspond to the selectioncriteria.

Which types of processing cannot be carried out parallel toregenerative planning?
- Processing generation trigger
- Automatic generation of issues
- Issue numbering
- Editing planning trigger
- Netchange for circulation planning
- Editing deliveries
- Editing orders
- Shipping preparation
- LIS update for deliveries

Output

Output structure

Structure of compact list (only triggers, no deliveries):
The following triggers are listed in sequence:
- Those for which planning was possible (with problem notes)
- Those that cannot start planning
- Those for which planning was not possible (with problem notes)

Structure of comprehensive list (triggers and deliveries):
Title page:
The first page contains an overview of all selected planning-relatedtriggers (trigger-specific problem notes or error notes are notincluded on the title sheet).
Log of regenerative planning for each trigger:
The report begins a new page for each trigger, displaying the planningtrigger again, this time including the trigger-specific problem anderror notes.
The following information is then listed for each trigger for whichplanning took place successfully:
- Deliveries deleted for trigger
- Netchange records deleted for trigger
- New deliveries for trigger
Overview of selected planning triggers for which planning could not bestarted.
(Cause: Trigger extends into past, lock date is not yet past, planningstatus is 'Planning OK' and 'Deletion OK')
Last page:
Overview of the selected planning triggers for which planning could notbe performed successfully (including error notes)

Which fields are output?

Planning trigger list:
Fields for planning trigger:
- Plant
- Publication
- Edition
- Delivery type
- Start of planning trigger
- End of planning trigger
- Lock date
- Planning trigger status
Problem notes for planning trigger:
(If checkboxes are selected, planning is still performed for the
trigger)
- No delivery viability sets for the planning trigger
- No order items for planning for the planning trigger
- No issues for planning for the planning trigger
Error notes for planning trigger
(If one of these checkboxes is selected, planning does not take place
for the trigger)
- Planning trigger / deliveries locked for trigger
(If orders are being processed, this is listed in the log as a
planning trigger lock)
- Issue generation not complete for the period

List for delivery:
Fields for delivery:
- Publication date of issue
- Shipping date of delivery
- Quantity
- Order-related delivery viability set:
= Delivery viability set from order
- Actual mix type:
Generally the mix type from the order item.
Exception: With the combination type 'Substitution' or
'Combination', this is the mix type of the combination edition.
- Actual publication:
Generally the publication for the order item.
Exception: With the combination type 'Combination', this
is the combination publication.
- Actual edition
Generally, the edition for the order item.
Exception: With the combination type 'Substitution' or
'Combination', this is the combination edition.
- Loading/unloading point
- Actual delivery type
Generally, the delivery type for the order item.
Exceptions: If 'pickup' is arranged in the order, the
actual delivery type is that of the order-related delivery
viability set. If an alternative delivery type is defined
for combination, this is taken as the actual delivery type.
- Logistical delivery type
= Logistical delivery type assigned to the actual delivery type
(A delivery type can also be a logistical delivery type itself).
The delivery also contains furtherdelivery types
besides the actual and logistical delivery types.
- Combination type:
Determines whether the issue is purchased directly from the
order item or using the combination types 'Substitution' or
'Combination'.
- Customer group
- Sales document type grouping
- Type of liability account
- Shipping outsorting type
Shipping outsorting only takes place for the sales document type
grouping "ABO"
- Delivery type
- Subsequent delivery number
- Delivery number:
When a delivery is created, only the internal delivery number
is displayed on the list.
Internal program fields:
- Internal delivery number

List of netchange records:
- Order number
- Publication
- Edition
- Plant
- Delivery type