Reset Transaction Data - OBR1

This program resets transaction data in a company code, initializes the number ranges, deletes data from test payment and dunning runs and deletes cross-company code transactions and customer credit control data. The program also includes data from Special Purpose Ledger and Controlling if the data was generated by transactions in Financial Accounting.

The program deletes the following:

• Document Header Supplement for Recurring Entry
• Accounting Document Header
• Document Segment
• Accounting Document Segment
• One-Time Data Document Segment
• Bill of Exchange Fields Document Segment
• Tax Data Document Segment
• Change Documents
• Document Long Texts
• Index Table for Customer Bills of Exchange Used
• Intercompany Posting Procedures
• Customer Payment History
• Prenumbered Checks
• Payment Medium File
• Open Item Account with Changed Reconciliation Account
• Consistent Payment Run Information
• Consistent Dunning Run Information
• Held Documents
• Documents for External Systems
• Parked Documents
• Data for External Tax Systems
• Information on Business Area Allocation
• Reconciliation Postings from the Reconciliation Ledger for the Company Code
• Cash Management Data for the Company Code
• Transactional Data from the Material Ledger and Actual Costing area

The following fields are initialized for dunning control and customer credit control:

• Customer Master (Dunning Data)
• Vendor Master (Dunning Data)
• Date of Last Dunning Notice
• Dunning Level
• Date of the Legal Dunning Proceedings
• Credit Management: Control Area Data
• Total of Order Values for Credit Limit Check
• Total of Receivables for Credit Limit Check
• Relevant Special Commitment for Credit Limit Check
• Date on which the credit limit was exceeded
• The indicator stating that the credit limit has to be reset is set.

Controlling data that can be allocated to the company code for deletion (including planning data) is deleted in the program run.


Points to note: 

• Run the reset program in background processing to avoid problems that can occur during runtime and the problem is the same whether it is deleting or display. 
• The system always writes the log for all the deletion entries. 
• The log lists the number of payment runs with included paying company code and without 
• Similar treatment for the Dunning run program as well. 
• There are some exceptions at the time of deletion, for example, If a primary cost element is in a controlling area that is assigned to a productive company code, the program does not delete any data in Cost Accounting. The log then informs you of this situation and lists the number of records per table that are not deleted.
• It is suggested to block the users from posting any transactions during this program run because this program takes a snapshot of the data before it starts deletion and ignores any documents posted during the program run, that means the program does not delete any documents that are being posted at the time of the program run.  
• You can control the waring message for each non-productive company code that is linked via the controlling are to the company code you are deleting.