Ansicht
Dokumentation

RJVVERS3 - IS-M/SD: Shipping Preparation for Ad Pre-Print Distribution

General Data in Customer Master   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Description

Program RJVVERS2 carries out shipping preparation for ad pre-print distribution.

Ad pre-print distribution takes place based on the IS-M/SD ad pre-print order.

Which data is updated?

Program RJVVERS2 performs shipping preparation for ad pre-print distribution, i.e. it generates deliveries for ad pre-print distribution on a distribution date (JVTLFNG). The distribution date from the ad pre-print order item is copied as the shipping date for the delivery.
Shipping preparation for ad pre-print distribution can only be carried out for ad pre-prints in plants for which ad pre-print distribution has not yet been performed on the distribution date.
If this is the case, even partially, the selected ad pre-prints in the plants for which ad pre-print distribution already took place are listed in the log. Ad pre-print distribution is performed for the selected ad pre-prints (for each plant) for which this is not the case.
Delivery-order assignments for ad pre-print distribution are not updated.

Selection options

Shipping preparation for ad pre-print distribution selects ad pre-print orders for distribution for a particular distribution date. The selection can be restricted to certain plants and ad pre-print publications.

You can either enter a distribution date or have the system determine it. If the parameter 'Soonest possible distribution date' is selected, the system determines the soonest possible distribution date that corresponds to your selection criteria. If the system is unable to determine a unique distribution date, shipping preparation does not take place. There is therefore no point in choosing automatic determination unless you specify selection criteria that permit selection of a unique distribution date. (It is always possible to determine a unique distribution date if the function 'Set shipping date' was last used for the selection criteria for the same distribution (shipping) date or if it was also carried out with automatic determination of the soonest possible distribution date.)

It is possible to delete ad pre-print distribution after it has been carried out. The deletion run deletes all deliveries that match the selection criteria on condition that bundling has not taken place for these deliveries. Deletion is only performed provided that none of the selected deliveries has been packed.

You can select a further parameter to perform a test run (without database updates).

Requirements

Meaning of the order deadline:

Shipping preparation can only take place if the closing date (for ad pre-print distribution) has been reached. If shipping preparation is restarted for a shipping date for which it has already been carried out, the system only selects ad pre-print orders for which ad pre-print distribution has not yet taken place.

General IS-M control parameters in Customizing:

Shipping preparation is active is ad pre-print distribution takes place on the basis of the M/SD ad pre-print order.

Shipping preparation is not active in the system if distribution is processed using distribution orders in M/AM.

If distribution is processed in M/AM, deliveries for distribution are generated using a separate function.

Which data must be maintained?

There must be ad pre-print orders for distribution that correspond to the selection criteria.

The function 'Set shipping date' should have been carried out on the distribution date for all selected ad pre-print orders for distribution.

Which types of processing cannot be run parallel to shipping preparation for ad pre-print distribution?

When carrying out distribution:
- Editing of selected ad pre-print distribution orders
- Release run for a change number

When deleting distribution:
- Delivery processing, netchange, regenerative planning

Output

Output structure

List of selected ad pre-prints for which ad pre-print distribution had already been performed:

The report lists the ad pre-prints (for each plant) for which ad pre-print distribution had already been performed on the distribution date.

Error log if the function 'Set shipping date' has not yet been carried out:

The report lists the shipping dates (more precisely, shipping date, logistical delivery type and plants) for which the function 'Set shipping date' has not yet been carried out.

List if shipping preparation was performed:
The report lists the deliveries created or deleted by shipping preparation.
If the deletion run selects deliveries for which packing has already been performed, bundling must be deleted before the deliveries can be deleted. In this case, the packed deliveries are included in the list for the deletion run.

Fields output

List if 'Set shipping date' has not been performed:

Fields for function 'Set shipping date':
- Plant
- Logistical delivery type

List of deliveries processed:
- Shipping date for delivery
- Publication date of issue
- Quantity
- Actual mix type:
- Actual publication:
Ad pre-print publication
- Loading/unloading point
- Actual delivery type
= Delivery type for ad pre-print distribution
- Carrier route
- Delivery round
- Geographical unit
- Customer group
- Sales document type grouping
- Subsequent delivery number
- Delivery number:
If the delivery is being created, number assignment will not
have taken place at the time of output.

BAL Application Log Documentation   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 5909 Date: 20240531 Time: 233549     sap01-206 ( 97 ms )