Полагаю, помогут программы RGUREP*

Спасибо.
Чем больше узнаешь FI-SL, тем больше разочаровываешься
Ищешь не причины ошибок в таблицах, а устраняешь уже появившиеся ошибки

Причем, ни разу не удивляюсь. SAP выпустил ноту 764523, в которой сделал кучу утилит по исправлению ошибок в таблицах.
А причины ошибок устранять не хочет

Вообщем, выяснилось ,в чем была проблема.
Параллельно делались FI-проводки и перепроводились старые FI-документы.
База данных лечится с помощью ноты 1476280.

Так что, BADI тут соевсем не при чем

А что это за нота такая?
У меня говорит: "The requested SAP Note is either in reworking or is released internally only."
Может в нумере ошибка?

Сорри, думал, что ее выпустили.
Покамест она "Note 1476280 is a pilot released note. The note can only be accessed
as customer XXXXXX."

Note 1476280 - FI-SL: Creating ACTUAL tots recrds from line itms (per perd)

Summary
Symptom

The program RGUSLSEP displays inconsistencies between line items and totals records for the actual data of a Special Purpose Ledger.
The totals records do not correspond to the corresponding actual line items.

It would be too complex to implement a correction using the correction report RGUREP01 as only one period is affected.
Other terms

Inconsistencies
Reason and Prerequisites

The inconsistencies between the totals table of a Special Purpose Ledger and the relevant line item table can have various causes.
The most frequent causes are as follows:

* In Customizing for the ledger you have deactivated the "Write line items" indicator (GLSIP) indicator. For this reason, the system only updates the totals tables, but no line items.

* Line items are archived, but the corresponding totals records remain.

* Customer-specific posting programs


The creation of totals records from the corresponding actual line items only makes sense if the line items have been updated completely and correctly and have not been archived. The line item update must be activated for all documents transferred.
This must be the case before a correction is implemented.

Solution

Firstly execute the following analysis programs:

* RGUSLSEP: Compare totals records with total from line items
Enter the relevant Special Purpose ledger and the record type '0' as the parameters here, and the required additional selection parameters (fiscal year, version 001, company code).

* RGUREP11: Check object number consistency in the totals table
Enter the name of the totals table as the parameter. In transaction GCL3 you can determine the name of the totals table using the ledger.
Execute the report in the background.
If errors are displayed here, they must first be corrected. For the additional steps, contact SAP Support.



The program ZZ_SL_CORRECT_TOTALS_FROM_LI carries out the following processes:

* The totals records of the Special Purpose ledger are reset according to the selection. This means that the relevant balances are deleted for the period specified.

* The line items of the ledger are read according to the selection. The totals records are created again using these line items. In this process, the balances can always be created again for one period only.

The program ZZ_SL_CORRECT_TOTALS_FROM_LI does not check if line items have actually been written for the selection conditions or if these exist completely.

Therefore, it is very important to check your Customizing and relevant data thoroughly before the execution of the report ZZ_SL_CORRECT_TOTALS_FROM_LI. If you have archived line items required for the reconstruction, it does not make sense to create the totals records again from line items.
If the line item update has also been fully or partially deactivated in Customizing, this report should not be used.

You should execute the program ZZ_SL_CORRECT_TOTALS_FROM_LI in the test run first and then check the result carefully. You must only execute the report in the update run if you have ensured that the report delivers the required result.
When you execute the report ZZ_SL_CORRECT_TOTALS_FROM_LI in the update run you must ensure that no postings are made in the relevant period during the execution of the report.

Прикольна! Давно хотелось бы иметь такой инструментик.
Ждем окончательного релиза ноты.

Привет!
Если спустя 14 лет еще есть доступ к ноте 1476280, можно попросить поделиться кодом отчета ZZ_SL_CORRECT_TOTALS_FROM_LI?

Для истории.
Удалось выполнить процедуру восстановления итоговых записей спецрегистра по отдельным позициям с фильтром по регистру/БЕ/году/счету:
1. RGUUMS03 Удаление переменных данных таблицы итоговых записей
Удаляем только итоговые записи по регистру, БЕ, году, счету
2. RGUREP00 генератор программы RGUREP02
Указываем имя итоговой таблицы нашего спецрегистра и наиболее частотное поле – RACCT, запускаем
3. RGUREP02 Repair Program: Totals from Line Items for Pool and Transport Tables
Повторно создаем итоговые записи по регистру, БЕ, году, счету

Процедура работает нормально только если в момент работы фоновых заданий не проводятся новые документы по восстанавливаемой комбинации аналитик.