Deletion – Periodic and Nonperiodic
Purpose
You use this component to delete transaction data in the consolidation system (SEM-BCS). You can delete the following types of data:
Reported financial data ( posting level 00)
Documents with posting levels 01, 02, 10, 12, 20, 22, or 30
Additional financial data
Implementation Considerations
There are two methods of deletion:
periodic
(for regularly scheduled deletions in the Consolidation Monitor) and
nonperiodic
(for “ad-hoc” deletions in the Consolidation Workbench).
You can use periodic deletion, for example, to make sure certain kinds of data are deleted prior to data entry.
You typically use nonperiodic deletion to correct unexpected errors discovered during data collection.
Integration
To perform periodic deletion, in the Consolidation Workbench you define a deletion method , assign the deletion method to a data collection method , which, in turn, you assign to a data collection task . You execute the task in the Consolidation Monitor.
To perform nonperiodic deletion, you define and execute a function with a selection screen in the Consolidation Workbench (see Nonperiodic Deletion ).
Features
Deletion of Reported Financial Data
To delete reported financial data with posting level 00, you choose the data type
Reported Financial Data.
The function processes the selected data as follows:
Input Type |
System Behavior |
Periodic |
The system resets to zero the period value of the selected period in the InfoCube for totals records. A document is not created. |
Cumulative |
The system overwrites the period value of the selected period in the InfoCube for totals records so that the cumulative value equals zero. A document is not created. |
Deletion of Documents with Posting Levels 01, 02, 10, 12, 20, 22, or 30
To delete documents that have the posting level 01, 02, 10, 12, 20, 22, or 30, you choose the data type
Documents.
The function processes the selected documents as follows:
Reversal or deletion of documents
How documents are processed depends on the setting you have made for repetition runs in Customizing for version combinations. The version combination or the document type determines whether a document is deleted or reversed. For more information, see “Definition of Valid Version Combinations” in Customizing of Versions
.
For cumulative deletion only: Inversion of Documents of Prior Periods (if applicable)
The document type determines whether documents of prior periods are inverted (see also “Inversion” in Document Type ).
For cumulative deletion only: Creation of correction documents (if applicable)
Resulting adjustments to totals data
The following table shows how the input type and the document type determine how documents are deleted:
Input Type |
System Behavior |
Periodic |
The selected document is either deleted or reversed. As a result, the system resets to zero the period value of the selected period in the InfoCube for totals records. |
Cumulative |
The selected document is either deleted or reversed. If automatic inversion is set in the document type, the system inverts the documents of the prior periods. When necessary, the system creates a correction document in the selected period to reset the cumulative value to zero. As a result, the system overwrites the period value of the selected period in the InfoCube for totals records so that the cumulative value equals zero. |
Deletion of Additional Financial Data
To delete additional financial data, you choose the appropriate data type. The system deletes the additional financial data for the selected period.
Deletion of additional financial data has no effect on the totals records or documents.
Activities
If you choose the
Sequence of Activities
data type, the system deletes the data of the selected period in both the
Sequence of Activities
data stream and the
Activity Sorting
data stream.
You can
not
delete data in the
Activity Numbers
data stream.
Constraints
The consolidation system cannot permanently delete data records that reside in an InfoCube. Since totals records are stored in an InfoCube, the system merely resets the totals data in the InfoCube back to zero. You can use functions in
SAPNetWeaver Business Intelligence (BI)
to permanently delete totals records.
Example
This example shows the effects of deletion of entries with posting levels 01, 02, 10, 12, 20, 22, or 30 on the
Totals Records
and
Documents
data streams, how these effects are dependent on the input type, and how cumulative deletion is dependent on whether automatic inversion has been defined for the given document type.
Task at Hand
You want to delete the postings with document type D1 for the period 006 . The following totals records and documents currently have document type D1 :
Period |
Doc. Type |
Item |
Period Value in Local Currency |
Period Value in Group Currency |
000 |
D1 |
(Asset) |
300 |
2,400 |
003 |
D1 |
(Asset) |
50 |
400 |
006 |
D1 |
(Asset) |
100 |
800 |
Period |
Doc. Type |
Doc. Number |
Item |
Period Value in Local Currency |
Period Value in Group Currency |
003 |
D1 |
38000 |
(Asset) |
50 |
0 |
006 |
D1 |
38001 |
(Asset) |
100 |
0 |
Deletion with Input TypePeriodic
Deletion with input type
periodic
creates a document 38002, which reverses document 38001. As a result, the system resets to zero the period value of the selected period in the InfoCube for totals records. After the deletion function, the totals records and documents with document type
D1
look as follows:
Period |
Doc. Type |
Item |
Period Value in Local Currency |
Period Value in Group Currency |
000 |
D1 |
(Asset) |
300 |
2,400 |
003 |
D1 |
(Asset) |
50 |
400 |
006 |
D1 |
(Asset) |
0 |
0 |
Period |
Doc. Type |
Doc. Number |
Item |
Period Value in Local Currency |
Period Value in Group Currency |
003 |
D1 |
38000 |
(Asset) |
50 |
0 |
006 |
D1 |
38001 |
(Asset) |
100 |
0 |
006 |
D1 |
38002 |
(Asset) |
–100 |
0 |
Documents 38001 and 38002 reference each other.
Deletion with Input TypeCumulativeand Automatic Inversion
When input type
cumulative
and automatic inversion are set, deletion of data with document type
D1
creates the following documents:
Document 38002 reverses document 38001.
Document 38003 inverts document 38000.
Document 38004 ensures that the cumulative value in the InfoCube for totals records equals zero.
As a result, the system overwrites the period value of the selected period in the InfoCube for totals records so that the cumulative value equals zero. After the deletion function, the totals records and documents with document type D1 look as follows:
Period |
Doc. Type |
Item |
Period Value in Local Currency |
Period Value in Group Currency |
000 |
D1 |
(Asset) |
300 |
2,400 |
003 |
D1 |
(Asset) |
50 |
400 |
006 |
D1 |
(Asset) |
–350 |
–2,800 |
Period |
Doc. Type |
Doc. Number |
Item |
Period Value in Local Currency |
Period Value in Group Currency |
003 |
D1 |
38000 |
(Asset) |
50 |
0 |
006 |
D1 |
38001 |
(Asset) |
100 |
0 |
006 |
D1 |
38002 |
(Asset) |
–100 |
0 |
006 |
D1 |
38003 |
(Asset) |
–50 |
0 |
006 |
D1 |
38004 |
(Asset) |
–300 |
0 |
Documents 38001 and 38002 reference each other, as do documents 38000 and 38003.
Deletion with Input TypeCumulativeWithout Automatic Inversion
When input type
cumulative
and
no
automatic inversion are set, deletion of data with document type
D1
creates the following documents:
Document 38002 reverses document 38001.
Document 38003 ensures that the cumulative value in the InfoCube for totals records equals zero.
As a result, the system overwrites the period value of the selected period in the InfoCube for totals records so that the cumulative value equals zero. After the deletion function, the totals records and documents with document type D1 look as follows:
Period |
Doc. Type |
Item |
Period Value in Local Currency |
Period Value in Group Currency |
000 |
D1 |
(Asset) |
300 |
2,000 |
003 |
D1 |
(Asset) |
50 |
400 |
006 |
D1 |
(Asset) |
–350 |
–2,400 |
Period |
Doc. Type |
Doc. Number |
Item |
Period Value in Local Currency |
Period Value in Group Currency |
003 |
D1 |
38000 |
(Asset) |
50 |
0 |
006 |
D1 |
38001 |
(Asset) |
100 |
0 |
006 |
D1 |
38002 |
(Asset) |
–100 |
0 |
006 |
D1 |
38003 |
(Asset) |
–350 |
0 |
Documents 38001 and 38002 reference each other.