Kontakt

Ansicht
Dokumentation

RJPMEDAUSSHIFT - IS-M: Move Publication Date of Issue

RJPMEDAUSSHIFT - IS-M: Move Publication Date of Issue

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

Title

Move Publication Date for an Issue (Synchronized with M/SD)

Purpose

Report RJPMEDAUSSHIFT moves the publication date of an issue (synchronized with M/SD).
(In the case of media issues not synchronized with M/SD, you can change the publication directly in individual maintenance for the media issue. Report RJPMEDAUSSHIFT does not change the publication date for media issues that are not synchronized with M/SD.)

Integration

If you move the publication date of a media issue with this report, the system modifies the production unit, M/SD orders and M/AM orders accordingly.

This modification involves checks on a large volume of data, so that it may be advisable to execute the report in background processing.

Prerequisites

  • The media issue must exist in M/SD.
  • The new publication date must be between the publication dates of the previous and next media issues.
  • Planning must not have taken place in M/SD for the media product, i.e. the edition, on the old and new publication dates.

Selection

You can select the media issue to be moved by specifying the media issue.
You must also specify the new publication date and the issue change type (maintained in Customizing).
A further parameter allows you to choose to execute the report as a test run (without database updates).

Output

The layout of the log corresponds to the standards for application log display.

The modifications to objects affected are logged in sequence:

  • Modifications to media product data (media issue)
  • Modifications to M/SD product data (issue)
  • Modifications to M/AM product data (production unit)
  • Modifications to M/SD orders
  • Modifications to M/AM orders
    The order change type is used, among other things, to determine whether M/AM order items affected by moving an issue are modified directly or collected initially in a work area.
    M/AM orders collected in a work area can then be refreshed using the report Regenerate Order Items.
    This variant allows you to avoid refreshing an order item more than once. This was sometimes the case previously, when several issues created together in one order (for example, by means of a combined booking unit) were moved.
  • Modifications to M/SD renewals (refresh of renewal index)

The log for each object affected has the following structure:

  • 1.) Indication whether update or test run
  • 2.) Indication that object modification is beginning
  • 3.) Various information or error messages for object modification
  • 4.) Indication that object modification is completed

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

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

Activities

To define how the system is to respond when modifying objects (M/SD and M/AM orders) in Customizing under Tools -> Data Transfer -> Management of External Issues -> Maintain Issue Change Types.
(Note: You can also use the functions for moving issues in external issue management, which is why the Customizing settings are located in this section.)

  • You can specify for M/SD orders whether or not the from-/to-date is also to be moved for unlimited changes. (Note: M/SD orders are only moved for products for which copy numbers are displayed and checked. This setting is made for each publication in the product mix.)
  • You can specify for M/AM orders which status characteristic is to be selected for the order item.
  • You can specify for M/AM orders whether or not and how they are to be modified when issues are moved.
    If M/AM orders are modified, the item characteristic is not selected.






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

Length: 4930 Date: 20240531 Time: 233505     sap01-206 ( 66 ms )