Id | Title |
---|---|
/SAPCND/MASTERDATA053 | Scales tables are initial for a condition record which has scales. |
/SAPCND/MASTERDATA054 | Maintenance mode is &1, where &2 is expected. |
/SAPCND/MASTERDATA056 | Dbaction value is not set to 'U' during update. |
/SAPCND/MASTERDATA058 | Unable to create working set handles for application &1 during setup. |
/SAPCND/MASTERDATA059 | No suitable configuration found to continue the CT fields test |
/SAPCND/MASTERDATA060 | No record was selected for lock verification (sceanrio &1). |
/SAPCND/MASTERDATA062 | Unable to carry out &1 test for application &2 (group &3). |
/SAPCND/MASTERDATA101 | Lock is not present as expected (&1, &2, &3). |
/SAPCND/MASTERDATA102 | Lock is erroneously present (&1, &2, &3). |
/SAPCND/MASTERDATA106 | *Messages for Simulation in pricing report 106 - 130* |
/SAPCND/MASTERDATA107 | Condition records deleted successfully. |
/SAPCND/MASTERDATA108 | Condition record found in DB with release status ' &1 ' as expected. |
/SAPCND/MASTERDATA109 | Condition record with expected release status ' &1 ' not found. |
/SAPCND/MASTERDATA110 | Cond. records with same key field values found, but no overlap detected. |
/SAPCND/MASTERDATA111 | Condition records with different release status found as expected. |
/SAPCND/MASTERDATA112 | Cond. record which had status 'released' is found with deleted marked. |
/SAPCND/MASTERDATA113 | Cond. record which had status 'B' is not found in DB as expected. |
/SAPCND/SY_CONFIG000 | * Field Check API Usage * |
/SAPCND/SY_CONFIG001 | Field value for field &1 in structure &2 (usage &3) is obsolete or legacy |
/SAPCND/SY_CONFIG002 | Field name &1 for usage &2 does not exist in the global field catalog |
/SAPCND/SY_CONFIG003 | Attribute type for field name &1 in usage &2 must be 'Usage' |
/SAPCND/SY_CONFIG004 | Usage field &1 references nonexistent usage &2 |
/SAPCND/SY_CONFIG005 | Field item for field &1 of usage &2 is not unique |
/SAPCND/SY_CONFIG006 | Specify a data element name for field &1 for usage &2 |
/SAPCND/SY_CONFIG007 | Field SCALE_TYPE is not a part of scale for usage &1 |
/SAPCND/SY_CONFIG008 | Data fields for field &1, usage &2 must remain empty |
/SAPCND/SY_CONFIG009 | Number of exernal fields must be >= 1 (usage &1, scale base type &2) |
/SAPCND/SY_CONFIG010 | Variables scale field &1 (usage &2) unknown |
/SAPCND/SY_CONFIG011 | Field SCALE_TYPE does not have data element /SAPCND/SCALE_TYPE |
/SAPCND/SY_CONFIG012 | Field name &1 (usage &2) may have a maximum of 16 characters |
/SAPCND/SY_CONFIG013 | Data field &1 for key field &2, usage &3 has no valid value |
/SAPCND/SY_CONFIG014 | Adapt all condition tables for usage &1 |
/SAPCND/SY_CONFIG015 | The required enhancement/change of usage &1 is not possible |
/SAPCND/SY_CONFIG016 | Usage &1 has &2 dim. scales and no scale fields |
/SAPCND/SY_CONFIG017 | Usage &1 has &2 dim. scales and no scale base types |
/SAPCND/SY_CONFIG018 | Usage &1 has no scales but has scale fields |
/SAPCND/SY_CONFIG019 | Usage &1 has no scales but has scale base types |
/SAPCND/SY_CONFIG020 | Usage field &1 has no usage assigned |
/SAPCND/SY_CONFIG021 | Usage &1 is still registered with application &2 |
/SAPCND/SY_CONFIG050 | * Field Check API Application * |
/SAPCND/SY_CONFIG051 | Field value for field &1 in structure &2 (appl. &3) is obsolete or legacy |
/SAPCND/SY_CONFIG052 | STRUCT_NOT_USED = ' ' for application &1 is only supported as legacy |
/SAPCND/SY_CONFIG053 | Field value SUPER_KAPPL = 'SUP' in appl. &1 only supported as legacy |
/SAPCND/SY_CONFIG054 | Field &1 is still registered for application &2 |
/SAPCND/SY_CONFIG055 | Registered task &1 still exists for application &2 |
/SAPCND/SY_CONFIG100 | * Field Check API Task * |
/SAPCND/SY_CONFIG101 | SCALEEVL_EXIST <> ' ' for &1 &2 is only supported as legacy |
/SAPCND/SY_CONFIG102 | Field value for field &1 in structure &2 (&3 &4) is obsolete or legacy |
/SAPCND/SY_CONFIG103 | Field DET_ENGINE_TYPE (&1 &2) should not be initial |
/SAPCND/SY_CONFIG104 | Field USE_NAMESPACE (&1 &2) should be flagged |
/SAPCND/SY_CONFIG105 | Signature for task (&1 &2) must be filled with two digits |
/SAPCND/SY_CONFIG106 | Condition table ID &1 still exists for task &2 |
/SAPCND/SY_CONFIG107 | ABAP determination for &1 &2 is now only supported as legacy |
/SAPCND/SY_CONFIG150 | * Field Check API Global Field Catalog * |
/SAPCND/SY_CONFIG151 | Attribute type for field name &1 must be &2 |
/SAPCND/SY_CONFIG152 | Field name &1 may have a maximum of 16 characters |
/SAPCND/SY_CONFIG153 | Data field &1 for key field &2 does not have a valid value |
/SAPCND/SY_CONFIG154 | Field value for field &1 in structure &2 is obsolete or legacy |
/SAPCND/SY_CONFIG155 | Data element &1 for field &2 is not registered in the field catalog |
/SAPCND/SY_CONFIG156 | Data element &1 does not exist actively in the DDIC |
/SAPCND/SY_CONFIG157 | Field name for data element &1 does not exist in the global field catalog |
/SAPCND/SY_CONFIG158 | Data element &1 from dependecy relationship is not registered globally |
/SAPCND/SY_CONFIG159 | Field name &1 from relationship relation is not registered globally |
/SAPCND/SY_CONFIG160 | Data element &1 cannot be in a dependency relationship |
/SAPCND/SY_CONFIG161 | External/internal relationship of field &1 to field &2 is not possible |
/SAPCND/SY_CONFIG162 | Dependeny of data element &1 (fields &2 &3) is not possible |
/SAPCND/SY_CONFIG163 | Dependency of data element &1 to application (fields &2 &3) questionable |
/SAPCND/SY_CONFIG164 | Field name &1 cannot be changed as application field in this environment |
/SAPCND/SY_CONFIG165 | Field name &1 cannot be changed as usage field in this environment |
/SAPCND/SY_CONFIG166 | Field &1 is a condition technqiue field |
/SAPCND/SY_CONFIG167 | Data element &1 is still being used in application &2 |
/SAPCND/SY_CONFIG168 | Data element &1 is still being used in usage &2 |
/SAPCND/SY_CONFIG169 | Data element &1 is used for condition technique fields |
/SAPCND/SY_CONFIG170 | Field &1 is still being used as an application field for application &2 |
/SAPCND/SY_CONFIG200 | * Authorization Check * |
/SAPCND/SY_CONFIG201 | No change authorization (see SU53) |
/SAPCND/SY_CONFIG202 | Condition technique configuration cannot be changed here |
/SAPCND/SY_CONFIG250 | * TADIR Registration * |
/SAPCND/SY_CONFIG251 | Object &1 &2 &3 is already registered (OSS Note 687921) |
/SAPCND/TRANSPORT000 | ** 000-099 transport (general,field catalog, condition tables) |
/SAPCND/TRANSPORT001 | Start of processing for request &1, time &2 |
/SAPCND/TRANSPORT002 | End of processing for request &1, time &2 |
/SAPCND/TRANSPORT003 | Object &1 &2 &3 can not be processed |
/SAPCND/TRANSPORT004 | Error when executing program &1 &2 |
/SAPCND/TRANSPORT005 | Error when importing condition table & |
/SAPCND/TRANSPORT006 | Check condition table &3 (application &1 / usage &2) |
/SAPCND/TRANSPORT007 | Field catalog: Processing objects for application &1 |
/SAPCND/TRANSPORT008 | Condition tables: Generating objects |
/SAPCND/TRANSPORT009 | Generation messages |
/SAPCND/TRANSPORT010 | Condition tables transported without relevant field catalog |
/SAPCND/TRANSPORT011 | Transport: Execution of method & |
/SAPCND/TRANSPORT012 | Object &1 &2 &3 &4 deleted. |
/SAPCND/TRANSPORT013 | Transport from field &1: Entry missing in table &2. |
/SAPCND/TRANSPORT014 | Transport from data element &1: Entry in table &2 missing. |
/SAPCND/TRANSPORT015 | Transport from dependencies for data element &1 incomplete. |
/SAPCND/TRANSPORT016 | Check Field Catalog: Application &1 / Field &2. |
/SAPCND/TRANSPORT017 | Check Condition Table: Applic. &1 / Usage &2 / Table &3. |
/SAPCND/TRANSPORT018 | Transport condition table &1: Entry in table &2 missing. |
/SAPCND/TRANSPORT019 | Field catalog &1/&2/: Item number already exists. |
/SAPCND/TRANSPORT020 | Start Execution: & & & & |