ERP_MKTTG_XPRA - Messages for XPRA ERP_MKTTG_XPRA
The following messages are stored in message class ERP_MKTTG_XPRA: Messages for XPRA ERP_MKTTG_XPRA.
It is part of development package CRM_MKTTG_EXCHANGE in software component LO-MD-BP-CM. This development package consists of objects that can be grouped under "target group exchange CRM <-> ERP (for conditions)".
It is part of development package CRM_MKTTG_EXCHANGE in software component LO-MD-BP-CM. This development package consists of objects that can be grouped under "target group exchange CRM <-> ERP (for conditions)".
Message Nr ▲ | Message Text |
---|---|
000 | Database table &1 does not exist |
001 | Table &1 does not have expected ERP structure |
002 | Table &1 is not empty; table is skipped from processing |
003 | DDIC object &1 still used; deletion not possible |
004 | DDIC object &1 not deleted |
005 | DDIC object &1 successfully deleted |
006 | Data base table &1 not dropped; data base does not exist |
007 | Checking table &1 for append structure |
008 | An unexpected error occured for table &1 at line &3 when calling &2 |
009 | &1 append structures found for table &2 |
010 | Reassigning append structure &1 |
011 | Append structures successfully reassigned |
012 | Activation of append structure &1 failed with return code &2 |
013 | Activation of table &1 failed with return code &2 |
014 | Database of table &1 was successfully dropped |
015 | Dropping of database table &1 skipped |
016 | Tables &1 and &2 do not exist in database |
017 | Reassigning database content for table &1 |
018 | Renaming of database table from &1 to &2 failed |
019 | Renaming of database index &1 failed |
020 | DDIC object &1 still used by &2 |
021 | TADIR deletion for &1 failed with return code &2 |
022 | TADIR was sucessfully deleted for &1 |
023 | Renaming of database table from &1 to &2 successfully completed |
024 | Renaming of database table from &1 to &2 was skipped |
025 | Table &1 has already been converted to &2; conversion skipped |
026 | Table &1 was successfully converted to &2 |
027 | Index &1 is already renamed; renaming not necessary |
028 | Table &1 was converted with warnings |
029 | Copying of indices fom table &1 to &2 failed |
030 | Afer copying indices activation of table &1 failed with return code &2 |
031 | Database indices were successfully copied from table &1 to &2 |
032 | Copying database indices from &1 to &2 |
033 | Processing table &1 |
034 | Database index successfully renamed from &1 to &2 |
035 | Table &1 is empty; no conversion necessary |
036 | XPRA ended with &1 warnings |
037 | XPRA ended with &1 errors |
038 | Copying index &1 |
039 | Exception with return code &1 |
040 | Identified extension index &1 |
041 | Activation of extension index &1 failed with return code &2 |
042 | Composition of TADIR name for extension index &1 failed |
043 | Reading of TADIR record for extension index &1 failed with return code &2 |
044 | Creation of TADIR record for extension index &1 failed |
045 | No DDIC object exists for table &1; processing stopped |
046 | Database table &1 could not be deleted |
047 | Regenerating condition table &1 |
048 | Regeneration of condition table &1 failed; check following log entries |
049 | Processing of table &1 ended with warnings |
050 | Extending length of field MATNR of table &1 failed |
051 | Extending length of field MATNR of table &1 |
052 | Length of field MATNR of table &1 successfully extended |
053 | Program cannot be executed if no upgrade is performed |
054 | Error during system upgrade check; Error code &1 |
055 | Database index &1 successfully dropped |
056 | Dropping of database index &1 failed |
200 | ZDM not enabled |