Ansicht
Dokumentation

RJIUTI00 - IS-M/SD: Service Program for Changing Audit Report Type for Edition

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Data in Customer Master  
This documentation is copyright by SAP AG.

Description

It is not usually possible to change the audit report type for an edition once sales orders have been recorded. However, if you do want to include a 'productive' edition in circulation auditing after it has been assigned sales orders (for example, because it is now being included in circulation auditing as a new product), this report can be used to achieve the following:

• Make changes possible for the audit report type for the edition

• Enter the auditing category of the audit report type in the existing orders for sales orders, offers with a specified subsequent sales document type, complaints and returns.

This updates delivery quantities in the appropriate statistics tables (daily circulation statistics or circulation book, according to the audit report type) for the next shipping date due for update for the edition in question. All new returns are also updated correctly afterwards.

Selection options

You must first specify the edition on the initial screen. You should also specify the new audit report type for the edition.

Tip

You can also use this program to correct incorrect category definitions for orders caused by errors in Customizing entries. If you have corrected the Customizing entries in the meantime, you can start this program and change the audit report type in the edition to 'self'. Do not select the checkbox 'Change correctly categ.orders'; this only corrects the orders that contain errors.

You can also use the following parameters to control the program flow:

• Change correctly categ.orders
  If you select this parameter, the program also changes orders belonging to an auditing category that matches the new audit report type according to the Customizing settings. Otherwise, these orders remain unchanged.

• Maximum number of problem orders accepted and
  Maximum LUW size
  The first of these parameters determines the number of orders that cannot be categorized or that are inconsistent at which the program is to be cancelled. The second parameter controls the technical size of an LUW (logical unit of work), i.e. how many orders are to be passed on to the update program at once.

Caution

The settings for these two parameters must be carefully balanced. This is explained in the following two examples:

Example 1: You specify that the program is to be cancelled when more than 100 problem orders are identified and that orders are to be updated in data packages of 500. During the program run, the limit of 100 problem orders is exceeded by the 610th order to be processed and processing is cancelled. However, the first 500 orders correctly processed were transferred as a data package for update, so that they are now categorized according to the NEW audit report type. This although the edition itself will now not be changed.

Example 2: You specify that the program is to be cancelled when more than 0 problem orders are encountered and that orders are to be updated in data packages of 99 999 999. During processing, a problem is identified with the xth (x < 99 999 999) order and the program is cancelled. No orders were updated yet: the program is cancelled but the database remains unchanged.

• Detailed log (per order)
  If you select this parameter, a note is written in the log for each order stating how the order was recategorized. If a high data volume is expected, you are advised against selecting this parameter.

• Test run (no database changes)
  Select this parameter if you do not want the program to make any changes to the database. In this case, it simply creates a log.

Processing that should not be performed parallel to this program

• Edition processing

• Order processing (for any editions)

Please also note the following

Circulation figures already updated in the statistics tables (IVW, WEMF or circulation book) cannot be corrected. Please make sure that you carry out the change of audit report type in accordance with the date of the update of circulation data. For example, you updated circulation data up to December 31st of one year. You now use this program to change the audit report type for an edition. The circulation data is then updated using the new audit report type for the edition from January 1st.

Output

The program displays a general log of the actions performed containing information on

• Controlling selection criteria

• Number of orders processed (affected, updated, correctable, unchanged, processed with errors)

• Start and end time of program run

The log also contains information on any problems and inconsistencies identified during processing.

The log is also stored on the database as a general application log. This means you can display it at any time (transaction SLG1). It is stored under the object name JICATYPE.

ROGBILLS - Synchronize billing plans   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 5474 Date: 20240520 Time: 085055     sap01-206 ( 105 ms )