Entering content frameFunction documentation Postprocessing The Data Transfer Locate the document in its SAP Library structure


The application enables you to postprocess data transfer runs that were not completely transferred to SAP R/3.


Test/Post: You can either do a test run or an actual transfer (posting) for postprocessing.

You have the following options:

The options best suited to postprocessing depend upon the type of error that occurred.

If, for example, the posting period was locked for the required transaction during the data transfer, you do not normally need to make any changes to the data to be posted. The data transfer can be repeated automatically once the period lock has been removed.

If an error occurred that can only be sorted out by correcting the transferred data, this can be done semiautomatically or manually. Semiautomatic postprocessing is suitable if errors need to be corrected at document header level (for example, incorrect posting date or incorrect reference). If individual posting rows are incorrect, you need to deal with this manually.

Ignore Warnings: If this indicator has been set, the documents are posted even if warning messages are issued during the document check. If this indicator has not been set, warning messages that are issued during the document check prevent the document from being posted.

External Number Assignment: If this indicator has been set, the application expects the final document numbers to be included during the data transfer.

Data Transfer ID: This parameter determines the data transfer that is to be postprocessed.

Initially you can select the documents for postprocessing from the whole postprocessing list. You can select individual documents, document groups or all documents for postprocessing.

In the semiautomatic mode, it is possible to correct information on the document header such as the controlling area, version or posting date and to have these corrected documents automatically posted.

If a data transfer contains only documents from one category, the system only shows the fields that are relevant for their correction. If a data transfer contains documents for different transactions (e.g. activity allocation and reposting of primary costs) all the fields are displayed that can be changed for at least one of the transactions. The corrected values are then transferred to the documents if they are valid entries for the transaction of the relevant document. If, for example, the version is changed, the value is not transferred to documents for reposting primary costs.

If documents are manually postprocessed, the application takes you to the transactions for manual actual postings:

These transactions enable you to check and correct the documents. You can then directly post the corrected document. To reverse individual CO documents, the corresponding reversal transactions must be called up directly.

For more information, see Reverse Manual Actual Postings.


It is not possible to write the changes back to the postprocessing list to then start the posting later.

If postprocessed documents are successfully posted then they are deleted from the postprocessing list.

Postprocessing can be repeated as long as there are still unprocessed documents in the postprocessing list for the selected ID.



Leaving content frame