Automatic Data Collection of Documents You can use the following procedures for automatically collecting documents of all posting levels:
In addition to collecting the documents in the data stream
Documents
, automatic data collection of documents updates the totals data in the data stream
Totals Records
.
Note
You can collect documents even if the data stream
Documents
is
not
defined in the data basis. In this case, the system only updates the totals data in the data stream
Totals Records
.
Flexible upload of documents with posting level 30 (business application
Consolidation of Investments
) does
not
allow you to transfer the activity number of the source document. For more information, see
Automatic Data Collection of Activities
.
If the system is not able to replicate the documents of the source data to the documents in the target data with a one-to-one (1:1) relationship, then which documents are written depends on their posting level and document type . The table that follows shows which rules the system uses when writing documents:
Posting Level |
Written in Target Data |
01, 10 |
One document per consolidation unit and document type |
20 |
One document per consolidation unit/partner unit and document type |
02, 12 |
One document per consolidation group and document type |
22 |
One document per consolidation group/consolidation unit and document type |
30 |
Depends on the business application defined in the document type:
|
Example
In the following example, the source data has the following data records with posting level 20 (two-sided elimination entries with the key fields
Consolidation Unit
and
Partner Unit
):
Document Number |
Consolidation Unit |
Partner Unit |
… |
Not available |
C1000 |
C2000 |
… |
Not available |
C1000 |
C3000 |
… |
Not available |
C2000 |
C1000 |
… |
Not available |
C2000 |
C3000 |
… |
Not available |
C1000 |
C3000 |
… |
Due the missing document numbers, the source data cannot be written to the target data with a one-to-one (1:1) relationship. Thus, the system writes the documents using the aforementioned rules. The two records with the pair
C1000/C2000
are written as one document. The same applies to the two records with the pair
C1000/C3000
.
Document Number |
Consolidation Unit |
Partner Unit |
… |
Generated |
C1000 |
C2000 |
… |
Generated |
C1000 |
C3000 |
… |
Generated |
C2000 |
C3000 |
… |
If the system is able to collect and write the documents with a one-to-one (1:1) relationship (for example, when copying documents of the current period), the system saves the number of the source document in the target document in characteristic
Reference Document Number
(InfoObject 0BCS_DOCNRR). The document number of the target document is generated by the system. The reference document number allows you to refer back to the source document.