SAP Note 18775 - Converting the period block without a loss of data

Symptom:

The period block chosen is too large. This makes it impossible to add any more fields, or Tables CE2xxxx and CE3xxxx (xxxx - operating concern) are not activated when you generate the operating concern. The log contains error message AD846: Table ... is too long.
Key word: KE01/KE02

Cause and prerequisites

See note 13136

Solution
This note is an addition to note number 13136 which enables you to set the period block to 1 without losing any data.
When you convert, you first need to save the data in tables CE2xxxx and CE3xxxx in operating system files. Then change the period block as described in note 13136. Finally, reload the data from the operating system files.

The following additional steps are necessary:
A. Import Programs RKEREOBL, RKEREOB0 and RKEREOB1.
These programs will be delivered in the standard system in Release
3.0A. For earlier releases, you can obtain these programs from
Sapserv3 in the directory /dist/permanent/Note.0018775 (file
R303599.K11). For information on how to load a transport from this
directory, see note 13719.
B. Create a data backup.
C. Start Program RKEREOBL. This program generates a program to save
the data of an operating concern (default: ZZREORG1) and a program
to reload the data (default: ZZREORG2).
D. Start the report to save the data. This program saves the data from
all clients. If the program runs without any error, you can begin
the conversion.
E. Convert the period block as described in note 13136 with the loss
of transaction data. CAUTION: Do not delete table CE1xxxx
(actual line items) as described in step 1. The data in this data
has not been saved. Only delete tables
CE2xxxx (planned line items) and CE3xxxx (object level).
F. If you had changed the storage parameters on the database for
tables CE2xxxx or CE3xxxx using SAPDBA or transaction SE14,
please make these changes again, because this settings are lost
during step E.
G. After the operating concern has been generated, reload the
transaction data using the corresponding program (from step C).
Before executing the program please enter /$SYNC into the OK-Code
field and generate the program ("SE38 -> Program -> Generate").

CAUTION: Make sure that no new transaction data is created while you
are executing steps D to G, since this could lead to
inconsistencies.