Description

This program performs netchange for circulation planning.

Which data is updated?
The program updates deliveries (JVTLFNG) if changes have been made toorders in periods for which planning was already performed - that is tosay, the program updates the daily quantities of an issue that aresupplied by a publisher to its customers if these changes were madeafter regenerative planning of circulation planning.
The program also updates the information as to which orders aresupplied by which deliveries (JVTLFZUO).
The netchange records evaluated by this program (JVTNCT1 - JVTNCT5) aredeleted once the deliveries have been updated.
Note: Deliveries (and delivery assignments) for the delivery types'Subsequent delivery' and 'Correction delivery' are not updated by thisprogram. These deliveries are updated directly in order processing.
If the program is executed as a live run without specifying anyselection criteria for orders, the status table for the closing date,JVTANNSTAT, is updated - meaning that the indicator XNETCHANGE isselected for all shipping dates set in JVTANNSTAT.

Selection options
Netchange for circulation planning is controlled by order changes madeafter regenerative planning of the planning data. Information on theseorder changes is recorded in the netchange files (JVTNCT1 - JVTNCT5).You can restrict netchange to certain orders on the selection screen,so that only the selected orders from the netchange files are subjectto 'subsequent planning'.
You can select a parameter to have the report executed as a test run(without database updates).
No further parameters are displayed on the selection screen, since theyare not normally required.

• 'Update active'

This parameter controls whether the database changes are made by theupdate or in dialog processing. Database changes are normally madewithout update during maintenance of report variants or by means ofSUBMIT calls of this program. However, this should not be donenormally.

• 'Ignore errors'

This parameter controls whether or not errors are to be ignored in thedatabase operations. The default setting is of course not to ignoreerrors, and you should not change this default setting.
(So what is the purpose of this parameter? If errors occur duringnetchange for individual orders, it may be necessary to repeatregenerative planning for all orders in a planning trigger for the sakeof time. For this reason, some programs allow you to perform processingdifferently for individual orders in an exceptional situation of thiskind after a comprehensive error analysis. When this kind ofexceptional processing is performed, netchange may be started forindividual orders with the specification that errors in databaseoperations are to be ignored. This should only be done in genuineexceptions and never during normal operations.

Precondition

Which data must be maintained?
There must be netchange records that correspond to the selectioncriteria.

Which types of processing cannot be performed parallel to regenerativeplanning?


• Regenerative planning of circulation planning


• Netchange of circulation planning


• Processing deliveries


• Shipping preparation

Output

Output structure
Orders for which 'subsequent planning' was performed by netchange
The report lists all orders for which subsequent planning was performed(if an order is listed n times, n changes relevant to netchange weremade to the order).
Planning-related periods modified by netchange
A planning-related period must be shortened if netchange could not beperformed periodically (for example, due to a system breakdown). Theperiod must be shortened so that no past deliveries or deliveries forwhich the shipping date has already been set are updated. Thisprocedure (and this output) only take place in exceptional cases.
Deliveries created, modified and deleted by netchange
Deliveries created, modified and deleted by netchange

Fields output

1. List of orders for which subsequent planning was performed:


• Order number

2. List of modified item periods relevant for netchange:
Fields for netchange files:


• Order number


• Item number from order


• Change number


• Item period from netchange file relevant for netchange


• Modified item period relevant for program

3. List of delivery:
Fields for delivery:


• Publication date of issue


• Shipping date of delivery


• Quantity after netchange

New delivery quantity determined by netchange

• Order-related delivery viability set

Delivery viability set from order

• Actual mix type

Generally, the mix type from the order item.
Except with combination type 'Substitution' or 'Combination',
where it is the mix type for the combination edition.

• Actual publication

Generally, the publication from the order item.
Except with combination type 'Combination', where it is the
combination publication.

• Actual edition

Generally the edition from the order item.
Except with combination type 'Substitution' or 'Combination',
where it is the combination edition.

• Loading/unloading point


• Actual delivery type

Generally, the delivery type from the order item.
Except when 'Pickup' is specified in the order, in which
case this is the delivery type from the order-related delivery
viability set. If an alternative delivery type is defined
for combination, this is the actual delivery type if the
combination type is 'Combination'.

• Logistical delivery type

Logistical delivery type assigned to the actual delivery type
(a delivery type can also be a logistical delivery type itself).
In addition to the actual and logistical delivery types, the
delivery also contains furtherdelivery types.

• Combination type

Indicates 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 typegrouping "ABO"

• Delivery type


• Subsequent delivery number


• Delivery number

If you created a new delivery, only the internal delivery number
is listed.
Internal program fields:

• Quantity before netchange

Quantity before it was changed by netchange

• Internal delivery number

4. List of assignment: Delivery for order schedule line
Fields for delivery-order assignment:


• Delivery number


• Subsequent delivery number


• Order number


• Item number from order


• Schedule line from order


• Standard schedule line quantity reduced by partial suspensions

This quantity is only displayed in the following special cases:
Schedule line is a partial suspension:
The quantity is a negative schedule line quantity
Schedule line is a standard schedule line with partial suspension(s):
Entry = standard schedule line quantity - partial suspension quantity

• Schedule line type

This is only displayed in the following special cases:
Schedule line is a partial suspension
Schedule line is a standard schedule line with partial suspensions

• Indicator: Delivery contains pickup

Internal program fields:

• Internal delivery number