/SAPAPO/MC013X40 - Messages for conversion CDP -> IBASE
The following messages are stored in message class /SAPAPO/MC013X40: Messages for conversion CDP -> IBASE.
It is part of development package /SAPAPO/MC01 in software component SCM-APO-PPS. This development package consists of objects that can be grouped under "Simple Classification with Mapping between Classified Objcts".
It is part of development package /SAPAPO/MC01 in software component SCM-APO-PPS. This development package consists of objects that can be grouped under "Simple Classification with Mapping between Classified Objcts".
Message Nr ▲ | Message Text |
---|---|
001 | Customizing for class type '&1' is incomplete |
002 | Object type '&1' is not assigned in the class system |
003 | Object type '&2' is not assigned to class type '&1' |
004 | Conversion was not executed |
005 | Class status with attribute 'Unrestricted' in class type '&1' is missing |
006 | Classification/configuration for product '&1' cannot be created |
007 | Classification for resource '&1' cannot be created |
008 | Data for class '&1' cannot be converted |
009 | Configuration for product '&1' location '&2' cannot be converted |
010 | CDP data for plan '&1' cannot be converted |
011 | Class '&1' does not exist in the class system |
013 | An incorrect characteristic is assigned to class '&1' |
014 | Characteristic '&2' is not assigned to class '&1' |
015 | Class '&1' cannot be converted |
016 | CDP is not active in the client |
101 | In client '&1', there are classes without R/3 mapping entries |
102 | In client '&1', there are characteristics without R/3 mapping entries |
103 | In client '&1', characteristic '&2' is used in ATP and in CBF |
104 | In client '&1', '&2' characteristics were created successfully |
105 | In client '&1', problems occurred during creation of characteristics |
106 | In client '&1', '&2' classes were created successfully |
107 | In client '&1', problems occurred during creation of classes |
108 | In client '&1', problems occurred during update of int. character. number |
109 | In client '&1', problems occurred during update of internal class number |
110 | In client '&1','&2' internal charact. numbers were converted successfully |
111 | In client '&1', '&2' internal class numbers were converted successfully |
112 | In client '&1', problems occurred when creating classes/characteristics |
113 | In client '&1', '&2' class-charact. assignments were created successfully |
114 | In client '&1', the necessary conversions were successful |
115 | No conversions were required in client '&1' |
116 | Data cannot be converted in client &1 |
117 | The system cannot process the conversion for char. &2 in client &1 |
118 | Only part of the data was converted in client &1 |
119 | The class type in table KSML in client &1 requires no correction |
120 | No transfer of data from SAP R/3 is required for client &1 |
121 | &2 entries in table KSML were corrected for KLART 400 in client &1 |
122 | Data from characteristic &2 could not be converted in client &1 |
123 | The system cannot process conversion for class &2 in client &1 |
124 | Errors occurred when correcting the class type in client &1 |
125 | Data from characteristic &2 could not be converted in client &1 |
126 | Errors occurred when deleting obsolete char./classes in client &1 |
200 | PPM plan & was not converted |
300 | No client contains data relevant for the conversion |
301 | CDP master data conversion in status & |
302 | The job for converting the CDP data is not yet finished |
303 | The CDP data conversion has not been started |
304 | The CDP conversion report was scheduled in client &1 |
305 | The CDP conversion report could not be scheduled in all clients |
306 | The CDP conversion report was scheduled successfully in all clients |
307 | The CDP conversion report could not be scheduled in client &1 |