Ansicht
Dokumentation

RJBDFOVT_DEL - Deletion of Fin. Objects for Variable Transacts without Archiving

RJBDFOVT_DEL - Deletion of Fin. Objects for Variable Transacts without Archiving

CPI1466 during Backup   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

The program RJBDFOVT_DEL deletes financial objects for variable transactions from the database. If you delete a financial object using this program, the financial object information is completely deleted (in contrast to the archiving process) and is no longer available in the system.

A financial object can contain several parts: a general part, a profitability analysis part (STC part), a risk part and a limit part. The entries you make on the initial screen determine which parts of the financial object are deleted.

If, as a result of the entries you make, only the general part of the financial object would remain after deletion, the system also deletes the general part when it deletes the parts you selected. If, for example, a financial object has only a general part and an STC part and you delete the STC part, the system then deletes the general part automatically. If only the general part of the financial object exists in the system and you want to delete that general part, you can do so by selecting all parts of the financial object on the initial deletion screen for example.

Integration

Prerequisites

Features

Selection

The initial screen includes several selection options. All selection criteria (with one exception) are linked by an 'AND' relationship. The Business Partner and External BP Number fields are the exception. These two fields are linked to one another by an 'OR' logical operator. This gives you the option of entering both the business partner and the external business partner number for the same deletion run. An 'AND' logical operator links these two fields to the other selection criteria.

Further restrictions:

Transaction End to field: The system selects transactions that have a transaction end date that is before or equal to the date entered in this field. If you do not enter a date, the system enters the maximum date (31.12.9999).

Indicator Delete financial objects for transactions without transaction end: If you set this indicator, the system also processes transactions for which no transaction end has been defined (in the master data).

Reconciliation Indicator: If you set this indicator, the system processes transactions that have the reconciliation indicator set. If you do not set this indicator, the system processes only those transactions for which the indicator is not set.

Restrictions for individual parts:

Single transaction costing part:

Delete STC part indicator: If you set this indicator, the system processes the profitability analysis parts (STC parts). If you do not set this indicator, the system does not process the profitability analysis parts.

STC Part Valid till field: The system selects STC parts that have a transaction end date that is before or equal to the date entered in this field. If you do not enter a date, the system enters the maximum date (31.12.9999).

Indicator Delete STC part without transaction end: If you set this indicator, the system also processes STC parts for which no transaction end has been defined.

Risk part:

Delete risk part indicator: If you set this indicator, the system processes the risk parts. If you do not set this indicator, the system does not process the risk parts.

Risk Part Valid till field: The system selects risk parts that have a transaction end date that is before or equal to the date entered in this field. If you do not enter a date, the system enters the maximum date (31.12.9999).

Indicator Delete risk part without transaction end: If you set this indicator, the system also processes risk parts for which no transaction end has been defined.

Limit part:

Delete limit part indicator: If you set this indicator, the system processes the limit parts. If you do not set this indicator, the system does not process the limit parts.

Limit Part Valid till field: The system selects limit parts that have a transaction end date that is before or equal to the date entered in this field. If you do not enter a date, the system enters the maximum date (31.12.9999).

Indicator Delete limit part without transaction end: If you set this indicator, the system also processes limit parts for which no transaction end has been defined.

Indicator Delete inactive parts only: If you set this indicator, the system processes inactive parts of the financial object only. If you do not set this indicator, the system processes both active and inactive parts of the financial object.

Control parameters:

Test Run indicator: If you set this indicator, the system carries out checks only and does not delete anything from the database.

Size of Processing Block field: You can use this field to control performance.

Standard Variants

Output

Once you have run the deletion program, the system displays and saves a log. If no errors occurred during the deletion run, the system flags the log with a green traffic light. If only minor errors occurred during the deletion run, the system flags the log with a yellow traffic light. If you started the run as an update run, the yellow traffic light indicates that the system has deleted all selected transactions or financial objects. If you started the run as a test run, the yellow traffic light indicates that the system would have deleted all the selected transactions or financial objects, had the run been an update run. If the system could not delete all selected transactions or financial objects, it flags the log with a red traffic light. You can use transaction SLG1 to display the log at a later point in time. The object for selecting deletion logs is called JB_DEL. You can specify a subobject in order to restrict further the choice of logs offered for display. The subobject for this deletion program is called FOVT.

To delete logs, use transaction SLG2.

Activities

Example






BAL Application Log Documentation   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 6678 Date: 20240531 Time: 215613     sap01-206 ( 160 ms )