Do you have any question about this error?
Message type: E = Error
Message class: SZDM_CC_CHKS_DETAILS - Detailed messages related to check classes
Message number: 101
Message text: Table &1 in metadata of SL API &2 does not exist in this system.
The properties of an API called by an after-import method (AIM) might be
incorrectly maintained.
In transaction SLAPI, you have declared table &V1& as a table which is
accessed by API &V2&. This table does not exist in this system. A GTADIR
query shows, however, that it exists in other development/maintenance
systems.
For more information about this check, see
<DS:TX.SZDM_CC_GENERAL_ZDO>here.</>
The metadata object of the API &V2& has been created. Table &V1& is
declared as accessed table, however this table does not exist.
You can maintain the required properties in a
<DS:TX.SCTS_SLAPI_REPOSITORY>Repository for Meta Data of an API called
by an After-Import Method</>.
Check and make sure that the correct tables are specified which are
accessed by the API.
To check and maintain the tables for the API &V2& to be called by
after-import methods, perform the following steps:
Call transaction SLAPI.
Select the line containing &V2&.
Choose "Used Database Tables".
Check table &V1& and adapt or remove it.
Check completeness of the tables and whether the attributes
<DS:DE.OB_LOCK_MODE>"Lock mode"</> and <DS:DE.OB_ACCESS_TYPE>"Access"</>
are correctly maintained.
Error message extract from SAP system. Copyright SAP SE.
SZDM_CC_CHKS_DETAILS101
- Table &1 in metadata of SL API &2 does not exist in this system. ?Get instant SAP help. Start your 7-day free trial now.
SZDM_CC_CHKS_DETAILS100
R3TR CLAS &1: Table &2 defined for Switch Badi can't be set to read only.
What causes this issue? INCLUDE SZDM_CC_LAT_DET_INTRO_PROC OBJECT DOKU ID TX In this case, the owner of the Switch-BADI implementation &v1& h...
SZDM_CC_CHKS_DETAILS099
R3TR OBJA &1: Table &2 accessed by an API cannot be set to read only.
What causes this issue? INCLUDE SZDM_CC_LAT_DET_INTRO_PROC OBJECT DOKU ID TX In this case the owner of the SLAPI implementation &v1& has spec...
SZDM_CC_CHKS_DETAILS102
Table &1 in metadata of XPRA &2 (SLAPI-ID: &3) does not exist
What causes this issue? The properties of an XPRA report are not correctly maintained. For more information about this check, see <DS:TX.SZDM_CC_G...
SZDM_CC_CHKS_DETAILS103
Table &1 in metadata of Switch-BADI &2 (SLAPI-ID: &3) does not exist
What causes this issue? The properties of Switch-BADI implementation are not correctly maintained. For more information about this check, see <DS:...
Click on this link to search all SAP messages.