SAP Message B1711 - Class type & does not exist in client &

Error message for XPRA report RBDXBDLT
This XPRA transfers the contents of the TBDLI table to the TBDLT table.
These tables are used in the ALE (Application Link Enabling) componentfor distributing master data objects via lists.
You can continue to work with your system if even this error doesoccur.

Hoever, if you use ALE and in particular use it to distribute masterdata objects via lists, then problems may occur if you do not fix thiserror.
This XPRA can be restarted, but it is not essential that it be executedagain. The problem may also be fixed manually, for example in the casethat only a few table entries are affected.

Diagnosis
There is an entry in the TBDLI table that contains a reference to theclass type &v1& in the client &v2&. This entry does not exist in theTCLA table.
Probably the TBDLI entry is an older entry that is no longer used.

System Response
The entry
V3
in the TBDLI table could not be transferred to the TBDLT table. Theentry was not deleted in the TBDLI table. When the XPRA is startedagain then another attempt will be made to copy this entry to the TBDLTtable.

Procedure
There are two ways of fixing this problem:
correct the Customizing and restart the XPRA
maintain the TBDLT table by hand

Option 1: Running the XPRA again
Create class type &v1& in client &v2&. The possible classificationobjects are MARA for material, KNA1 for customer and LFA1 for vendor.You can find the activity in the IMG under Cross-applicationcomponents -> Distribution (ALE) -> Distribution scenarios -> Masterdata distribution -> Distribution via lists -> Maintaining classtypes. The accompanying text includes more information on thisactivity. An alternative is to use the transaction O02D.

Option 2: Maintain the TBDLT table by hand
Execute the following IMG activity: Cross-application components ->Distribution (ALE) -> Distribution scenarios -> Master datadistribution -> Distribution via lists -> Allocate listings to thelogical system. The accompanying text includes more information onthis activity. An alternative is to use the transaction BD68.