IUUC_MAIN SAP Message class IUUC: Main Message class

IUUC_MAIN is a standard message class available within your SAP system (depending on your version and release level). Below is a list of all the messages available for within this class and a link to any long text associated with each message. These messages are very simple to use and can be implemented into your ABAP code using the MESSAGE statement and the following syntax.

MESSAGE I001(IUUC_MAIN).

Note the value "I" represents an information messsage but can be replaced with E for error, W for warning, S for Status/Success, A for Abend/Termination and X for exit which does not display a message and causes a runtime error. Click here for more information about SAP Messages.

Messages can also contain the & symbol, this means custom values can be added to the message when it is displayed, this is done using the WITH statement

MESSAGE I001(IUUC_MAIN) with ld_field1.

Message class details can be viewed directly within your SAP system by entering the object name IUUC_MAIN into the relevant SAP transaction such as SE91 or SE80.

000 - &1 &2 &3 &4

001 - Create logging table for &1 failed

002 - Original table &1 not found in the sender system

003 - Logging table &1 couldn't be created successfully

004 - Function &1 started on &2 at &3

005 - Function &1 finished on &2 at &3

006 - Run &1 aborted due to unknown operation flag &4 in &2 at &3

007 - Deletion of triggers failed for table &1

008 - Logging table &1 does not exist in the sender system

009 - &1 trigger creation failed for table &2

010 - no IUUC data found for migration object &1

011 - Tabclass missing for migration object &1

012 - For table &1, logging table not yet generated - can't create trigger!

013 - No objects to be processed for this selection

014 - &1 jobs scheduled for &2

015 - Start of finding of logging table entries for ID &1 on &2 at &3

016 - End of finding of logging table entries for ID &1 on &2 at &3

017 - Logging table &1 could not be truncated

018 - number assignment for logging table failed: &1

019 - job scheduled for detection of entries in logging tables

020 - For periodic job scheduling, specifiy day and time of last job start

021 - &1 job(s) scheduled for trigger deletion in receiver system

022 - table entries of table &1 could not be deleted in receiver system

023 - Unicode Conversion Package not installed. Activation is not possible

024 - Relevant sender dictionary could not be determined

025 - Mass transfer &2 already contains table &1

026 - Table &1 does not exist on DB - might be pool or cluster table?

027 - no conflicts to be processed - activity can be skipped

028 - There are still conflicts left to be processed - activity not completed

029 - No valid license key - contact SAP, see SAP note 1265126

030 - IUUC usage scenario has been successfully defined

031 - Function not yet possible, because repository upgrade not yet finished

032 - Table list definition successfully completed

033 - Delta replay has been started - track progress with transaction MWBMON

034 - Select at least one of the systems (sender / receiver)

035 - For &1 tables, logging tables were created

036 - For &1 tables, the creation of logging tables failed

037 - You first need to delete all triggers - triggers still active for MT &1

038 - First delete all logging tables for mass transfer &1

039 - &1 trigger successfully created for table &2 at &3 &4

040 - Logging table &1 created for table &2 at &3 &4

041 - All process option conflicts have been resolved

042 - Table comparison didn't find any differences - Congratulations!

043 - Table comparison found differences; for details, view the spool list

044 - Number of transfer jobs not maintained in table IUUC_MT_HEADER for MT &1

045 - &1 job(s) scheduled for trigger deletion in sender system

046 - Trigger syntax error occurred:

047 - activity not allowed in case of full incrementality

048 - Transfer controller job has been started

049 - Data transfer for remaining tables started - track progress in trx MWBMON

050 - &1 positions were deleted from table DMC_IU_E071 with piece list &2

051 - &1 positions were read from table DMC_IU_E071 with piece list &2

052 - No positions available in table DMC_IU_E071 with piece list &2

053 - Key length exceeds the maximum for table &1

054 - Table &1 already has 16 key fields

055 - Keyfield difference check completed - no differences found

056 - Please enter rfc destination for upgrade reference system

057 - Process option changed to &1 for table &2

058 - Number of entries differs for some tables - see spool list for details

059 - Critical process option change for table &1 comitted by user &2

060 - Process option NOT changed for table &1

061 - Manual execution of activity required; for details see activity document.

062 - Table &1 not found in the upgrade reference system

063 - Key field difference detected for table &1

064 - Process option &1 already set for table &2

065 - For table &1, a process option change is not allowed

066 - Clone release must not be lower than productive release

067 - &

068 - Original table &1 not found in the receiver system

069 - Number of expected logging tables different from existing logging tables

070 - For Table &1, &2 entries in sender, &3 entries in receiver

071 - Function &1 started on &2 at &3 for MT &4

072 - Function &1 finished on &2 at &3 for MT &4

073 - For table &1, no logging table exists

074 - Processing incomplete due to selections - activity set to error state

075 - Sequences successfully deleted in destination &1

076 - Deletion of sequences failed in destination &1

077 - Table &1 does not exist in the source system

078 - Table &1 not found in system &2

079 - Table &1 is not a cluster table in system &2

080 - Table &1 not found in mass transfer &2

081 - Table &1: Consider TReq set to &2

082 - Table &1 could not be created

083 - Table &1 could not be activated

084 - Table &1 could not be dropped

085 - Table &1 could not be renamed

086 - &1 successful for table &2

087 - No migration object exists for table &1

088 - Collective access plan &2 created for table &1

089 - Delimitation not possible for table &1

090 - Attention: Migration Object needs to be recreated!

091 - No parallelization data available for table &1

092 - Table &1: Don't specify both event and receiver field

093 - Table &1: Importing parameter missing for field-related rule!

094 - Start of field to field comparison for table &1 on &2 at &3

095 - End of field to field comparison for table &1 on &2 at &3

096 - Table &1 successfully deleted (rfc destination &2)

097 - Table deletion failed for table &1

098 - Table &1 added to mass transfer &2 with process option &3

099 - Table &1 wasn't specified; added with process option &2

100 - Table count for &1 failed in sender system (RFC destination &2)

101 - Table count for &1 failed in receiver system (RFC destination &2)

102 - Table count for &1 finished in sender system (RFC destination &2)

103 - Table count for &1 finished in receiver system (RFC destination &2)

104 - Table check for &1 already completed

105 - Select at least one Table Class

106 - Select at least one Process Option

107 - There are still triggers referring to logging table &1

108 - Definition of Cluster / Pool could not be determined

109 - Shadow dictionary for table &1 RFC destination &2 does not exist

110 - Selection from logging table failed

111 - Mismatch error occured during import of key data

112 - Mismatch error occured during import of sender data

113 - Mismatch error occured during import of receiver data

114 - Data selection failed (RFC destination &1)

115 - Triggers still exist at &1 - Sequences must not be deleted

116 - DELTA-Like Process Options not allowed for table &1

117 - For Table &1, the process option should not be set to DELTA, or DELTA_FIN

118 - Table &1 refers to clone table &2 - should not be set to COMPLETE

119 - Fieldname &1 invalid for table &2 (secondary index creation failed)

120 - Logging table deletion failed at least for some tables in system &1

121 - Table &1 exists already

122 - Table &1 created

123 - Check manually if all external interfaces have been disabled

124 - Error occured during field to field comparison of Table &1

125 - Process option of table &1 is &2

126 - Table &1 deleted (original table &2)

127 - DB trigger(s) successfully deleted for table &1

128 -

129 - In system &1, data class &2 is not defined

130 - No PARALLEL_FIELDNAME assigned to table &1 in IUUC_PERF_OPTION

131 - Data class &1 not assigned to a valid table space

132 - Tablespace Existence Check failed in remote system &1

133 - Table &1 is a &2 table, but only transparent tables can be processed

134 - Some triiggers (INS, UPD, DEL) are missing

135 - Client specific flag couldn't get read

136 - No header data found for mass transfer &1

137 - For table &1, no primary key exists

140 - Logical table &1 of cluster &2 added to mass transfer at &3 &4.

141 - Logging table &1 created in receiver for table &2 at &3 &4.

142 -