Ansicht
Dokumentation

RJDVASHIFT - IS-M: Move Publication Date of an Issue

BAL_S_LOG - Application Log: Log header data   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Title

Move publication date of issue

Purpose

Report RJDVASHIFT moves the publication date of an issue.

Integration

If you use this report to move the publication date of an issue, the production unit, M/SD orders and M/AM orders are modified accordingly.

These modifications involve checks on a large dataset, so that it is generally advisable to run the report in background processing.

Prerequisites

• The issue must exist in M/SD.

• The publication must be a title.

• The new publication date must be between the publication dates of the issues that come before and after the issue in question.

• Planning should not have taken place for the edition on the old and new publication dates.

Selection

To select the issue you want to move, specify the publication, edition, publication date or copy number.
You must also specify the new publication date and the issue change type (which is maintained in Customizing).
A further parameter allows you to run the report as a test run (without database updates).

Output

The log is formatted in accordance with the standards for application log display.

Modifications of objects affected are logged in the following sequence:

• Modification of M/SD product data (issue)

• Modification of M/AM product data (production unit)

• Modification of M/SD orders

• Modification of M/AM orders
  The order change type serves, among other things, to determine whether the M/AM order items affected by moving an issue are modified directly or collected first in a pool.
  The M/AM orders collected in a pool can then be updated by means of the report Regenerate Order Items.
  This variant prevents an order item being updated more than once. This might otherwise happen when you move several issues that are placed together in one order (for example, by means of a combined booking unit).

• Modification of M/SD renewal subscriptions (update renewal index)

The log for each object affected has the following structure:

• 1.) Note indicating update or test run

• 2.) Note indicating start of object modification

• 3.) Various individual information or error messages for object modification

• 4.) Note indicating completion of object modification

Example: log of modification of M/AM product data:
1.) Test run, no database updates
2.) Start: "Move issue" in M/AM product data
3.) No production unit found for issue xxxxx
4.) "Move issue" completed in M/AM product data

If this report is executed in background processing, you can also display the log using report RJDVAEXTERN_PROT. Unlike the spool list, this report provides you with the functions of the application log - for example, you can double click on messages here to display their long texts.

Activities

The control settings determining how the system is to respond when modifying objects (M/SD and M/AM orders) are made in Customizing under Tools -> Data Transfer -> External Issue Management -> Maintain Issue Change Types:
(Note: You can also use the function for moving an issue in external issue management, which is why the Customizing settings are located here.)

• You can specify for M/SD orders affected by the function whether or not the from-/to-date for unlimited changes is also to be moved.

• You can specify for M/AM orders which status characteristic is to be set in the order item.

• You can specify for M/AM orders whether or not M/AM orders are to be modified when issues are moved and if so, how.
  If the M/AM orders are modified, the item characteristic is not set.
  The program only modifies orders entered with a copy number.

CL_GUI_FRONTEND_SERVICES - Frontend Services   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 4550 Date: 20240520 Time: 084505     sap01-206 ( 57 ms )