SAP Note 13136 - Converting period block to 1

Symptom:

When you generated an operating concern, Tables CE2xxxx and CE3xxxx (xxxx = op.concern) were not activated. Log contains message AD846: Table ... is too long.

Cause and prerequisites

You are using an operating concern which was created before Release 2.2E with a period block greater than 1.
The operating concern contains a large number of value fields. In Tables CE2xxxx and CE3xxxx, the value fields were blocked in several periods. This caused the maximum length for the table, as defined in the database system, to be reached.
You will find further information in the documentation for the data element RKE_BLOCKF.

Solution
If the operating concern already contains data which cannot be deleted, note 18775. If the operating concern contains either no transaction data or only test data which can be deleted, you can change the period block as follows:

1. Delete Tables CE1xxxx, CE2xxxx and CE3xxxx in the database system
(Transaction SE14). If the database tables have not yet been created, you do not need to perform this step.
CAUTION: If test data exists, all transaction data in operating
concern xxxx will be deleted in all clients when you
carry out this step! If data was posted via the interfaces
(SD, CO-CCA, FI, ...) to CO-PA, this will lead to
inconsistencies between applications.
2. Delete the lock elements EKC2xxxx and EKC3xxxx (Transaction SE11).
3. Delete the tables CE2xxxx and CE3xxxx in the Data Dictionary
(Transaction SE11). You can ignore the warning telling you that the
tables are still used in programs, sinces the tables will be created
again in step 5.
4. To change the period block in Table TKEBB, enter the
following ABAP. Adapt operating concern "xxxx"
and then execute the program.

REPORT YYYYYYYY.
TABLES: TKEBB.
UPDATE TKEBB SET BLOCKF = 1 " Period block
WHERE ERKRS = 'xxxx'. " xxxx - Operating concern

5. Up to and including Release 2.2:
- Save the operating concern:
KE02 -> Value flds -> Op.concern -> Save
- Generate the operating concern:
KE02 -> Value flds -> Op.concern -> Generate
- Create the database tables CE1xxxx, CE2xxxx and CE3xxxx
in the database (Transaction SE14). If you had not already created
the tables beforehand, do not forget to create table CE4xxxx too.
In Release 3.0:
- Activate the data structures of the operating concern
(transaction KEA0)
- Generate the environment.
6. If you have used field KNDNR (customer) in a derivation structure,
see note 28586.

Key word: KE01/KE02, KEA0