Ansicht
Dokumentation

RNUMNDT0 - IS-H: INACTIVE - DO NOT USE Reset Client

RFUMSV00 - Advance Return for Tax on Sales/Purchases ABAP Short Reference
This documentation is copyright by SAP AG.

Description

CAUTION: This report is obsolete and is out of maintenance as of IS-H Release 607.

If you still need to use it, please contact SAP by creating a customer message.

This program enables you to delete the transaction data of the IS-H system for a client. You can delete change documents and restet number ranges in the process.

The objects that are deleted or reset are maintained in an object table in Customizing. You can create your own object sets for different purposes in this table.

The standard system contains an object set named CR (Client Reset). You can, however, create other object sets (see below).

Important: The deletion program only deletes data of the application component IS-H. Functions in IS-H also create data in other components of the SAP system, for example in Sales and Distribution (SD), in Financial Accounting (FI) or in Controlling (CO). This data in other SAP components is not generally reset by this program. With regard to SD, this means, for instance, that you can only use the deletion program if invoices have never been created or if existing invoices are deleted consistently using other utilities!

The program is generally not suited for creating a production client, since at present SD data (billing documents, etc.) cannot be reset. You can use this program in particular for purging a test client whose application data has become inconsistent after Customizing changes.

Warning

Thoroughly analyze the status of the client in which you want to execute the program. If necessary, contact your SAP consultant.

Carefully read the documentation in full.

Never use the program in a production client. It is essential to set the production indicator if one of your institutions is going live. This prevents the program from being executed.

Before using the program, check the objects in the table TNOBJ that are affected by the object you wish to specify.

Make a client copy with master and transaction data as a backup.

Initially run the program in test mode to create a list of the objects to be deleted and the number of data records.

Selection Screen

You can make the following specifications on the program selection screen:

Object (mandatory entry): name of the object set in the table TNOBJ.
Test mode: If you select test mode, the program generates a list of the relevant objects and the number of data records, without making changes in the database.

Procedure

The program reads all of the relevant object entries for the object.
The system checks whether each of the tables concerned:

Exists in the DDIC
Is not client-specific
Is not too wide (see technical details below)

When you execute the program in live mode online, a dialog box with a warning enables you to cancel the operation. This option is, of course, not available in background processing!
An entry is written to the system log in live mode.
Change documents are deleted (entries in the tables CDHDR and CDPOS).
Long texts are deleted (entries in the tables STXH and STXL).
Number ranges are reset.
Tables are deleted.
Addresses are deleted from central address management.
Entries are deleted in status management.
A log is output.

Output

For each object processed, the log contains a row with the following information.

Object type
Object key
Country version
Comment
Success (in test mode TEST)
Number of data records (not for number range objects; for long texts, the number of long text objects and not the number of lines; for change documents, the number of document objects and not the number of lines).

Requirements

You must maintain the table TNOBJ in Customizing. This table is located in the Section Reset Client of the IS-H Implementation Guide.

Technical Details

Tables are deleted in blocks of 5000 records, each block followed by a COMMIT. This value is stipulated in the field DEL_COMMIT in the program and can be changed using a modification should problems arise.
If the program terminates abnormally when a COMMIT takes place, the database can become inconsistent. Once you have corrected the cause of the termination, you can restart the program to delete the remaining table entries.
This block by block deletion involves the entries of the table to be deleted up to DEL_COMMIT being copied into an internal table. This table has a single character field of length 2000. If the table to be deleted is wider than 2000 characters, a run time error occurs, which is actually trapped as soon as you have specified the use on the selection screen. In such cases, the system issues an error message ('Table & is wider than & characters. Please read the long text.'). The long text of the error message tells you the width required for processing. You can then modify the length of the field LINE of the table ITAB at the top of the source code of the RNUMNDT0 program accordingly.

Delivered objects OE, LK and GPA

Object entries are delivered under the object names OE, LK and GPA for the IS-H master data organizational units, building units and business partners respectively.

You can use this program for deleting this master data. Note, however, that only the named objects are deleted. Entries in Customizing tables that are referenced to these objects are not deleted. For this reason, always check the table list in Customizing (TNOBJ) and the log list.

Example: When you delete the organizational units, the organizational unit-related form control entries are not deleted.

Customer-defined object entries

You can create your own object sets under the object names Z1 through Z9. Note, however, that during an upgrade, the table TNOBJ can be completely overwritten by SAP. For this reason, the object sets Z1 - Z9 should only be used temporarily for a particular use.

General Data in Customer Master ABAP Short Reference
This documentation is copyright by SAP AG.

Length: 6660 Date: 20240520 Time: 065610 sap01-206 ( 113 ms )

Ansicht Dokumentation