Ansicht
Dokumentation

GU636 - Postings to &1 during the run may lead to incorrect results - GU 636

rdisp/max_wprun_time - Maximum work process run time   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Diagnosis

You want to perform a balance carryforward for ledger .

The system has determined that for the company code to be carried forward at least, there are still open posting periods in the old fiscal year . (Note that alongside company code , there may be open posting periods for other company codes that are to be carried forward. Please check whether this is the case.)

If postings are made to the old fiscal year when the balance is actively carried forward, the results of the balance carryforward may be incorrect.

Due to conceptional reasons and for performance reasons, the system is unable to ensure that postings are not made to the old fiscal year when the balance is actively carried forward.

System Response

A corresponding information message is issued (for the first affected company code with open posting periods in the old year).

Procedure

Make sure from an organizational perspective that when the balance is actively carried forward, postings are not made to the old fiscal year (for example, by temporarily closing the posting periods in the old year or starting the balance carryforward in a posting-free period).

If postings are made to the old year, however, and the results of the balance carryforward are incorrect, you can repeat the balance carryforward at any time when postings are no longer made to the old fiscal year. The results will then be correct.

Procedure for System Administration

Vendor Master (General Section)   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 1610 Date: 20240424 Time: 025256     sap01-206 ( 39 ms )