Hierarchy
⤷ BC-MID-ALE (Application Component) ALE Integration Technology
⤷ SALE (Package) Application Link Enabling
Attribute
Message class | B1 | ||
Short Description | ALE group messages | ||
Message Number | 712 | ||
Documentation status | |||
Authorization check Error Message | |||
Changed On |
Message Text
Help Document
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) component for distributing master data objects via lists.
You can continue to work with your system if even this error does occur.
However, if you use ALE and in particular use it to distribute master data objects via lists, then problems may occur if you do not fix this error.
This XPRA can be restarted, but it is not essential that it be executed again. The problem may also be fixed manually, for example in the case that only a few table entries are affected.
Diagnosis
There is an entry in the TBDLI table that contains a reference to the class type in the client . This entry also exists in the TCLA table, and is assigned to the classification object . There are, however, no message types for this classification object in the TBDME table.
The only possible values for the classification object are MARA for material, KNA1 for customer and LFA1 for vendor.
Probably the TBDLI entry is an older entry that is no longer used.
System Response
The entry
in the TBDLI table could not be transferred to the TBDLT table. The entry was not deleted in the TBDLI table. When the XPRA is started again then another attempt will be made to copy this entry to the TBDLT table.
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
Change class type in client . The possible classification objects are MARA for material, KNA1 for customer and LFA1 for vendor. You can find the activity in the IMG under Cross-application components -> Distribution (ALE) -> Distribution scenarios -> Master data distribution -> Distribution via lists -> Maintaining class types. The accompanying text includes more information on this activity. An alternative is to use the transaction O02E.
Option 2: Maintain the TBDLT table by hand
Execute the following IMG activity: Cross-application components -> Distribution (ALE) -> Distribution scenarios -> Master data distribution -> Distribution via lists -> Allocate listings to the logical system. The accompanying text includes more information on this activity. An alternative is to use the transaction BD68.
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in |