SAP ABAP Message Class /SAPCND/MASTERDATA (For the test of masterdata only)
Basic Data
Hierarchy
☛
SAP_AP (Software Component) SAP Application Platform
⤷ AP-PRC-CON (Application Component) Condition Technique
⤷ /SAPCND/TEST_T (Package) Test tools for condition technique
⤷ AP-PRC-CON (Application Component) Condition Technique
⤷ /SAPCND/TEST_T (Package) Test tools for condition technique
Attributes
Message class | /SAPCND/MASTERDATA | |
Short Description | For the test of masterdata only | |
Changed On | 20110810 | |
Last Changed At | 084631 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | * Test function modules and reports for creating master data * | The short text describes the object sufficiently | |
2 | 001 | Condition record is successfully created. | The short text describes the object sufficiently | |
3 | 002 | Condition record(s) not created due to time period overlap. | The short text describes the object sufficiently | |
4 | 003 | Condition record(s) not created due to errors (see log). | The short text describes the object sufficiently | |
5 | 004 | Primary key (VARNUMH) must be filled. | The short text describes the object sufficiently | |
6 | 005 | Condition record is successfully deleted. | The short text describes the object sufficiently | |
7 | 006 | Record values mismatch between API and database for field &1. | The short text describes the object sufficiently | |
8 | 007 | Condition record in DB not selected by the API | The short text describes the object sufficiently | |
9 | 008 | No Condition record for change selected | The short text describes the object sufficiently | |
10 | 009 | API creates &1 and not &2 condition records | The short text describes the object sufficiently | |
11 | 010 | No Condition record for delete selected | The short text describes the object sufficiently | |
12 | 011 | The BADI &1 does not have active implementation | The short text describes the object sufficiently | |
13 | 012 | The application &1 is not registered for ABAP Unit test | The short text describes the object sufficiently | |
14 | 013 | The usage &1 is not registered for ABAP Unit test | The short text describes the object sufficiently | |
15 | 014 | Condition maintenance group &1 does not have any group items. | The short text describes the object sufficiently | |
16 | 015 | Application &1 returned wrong condition maintenance group &2 | The short text describes the object sufficiently | |
17 | 016 | Usage &1 did not participate in change condition records testing | The short text describes the object sufficiently | |
18 | 017 | Condition record created by API not present in database for &1 &2 &3. | The short text describes the object sufficiently | |
19 | 018 | Errors in condition record maintenance (see log). | The short text describes the object sufficiently | |
20 | 019 | Overlapping condition records not detected for &1 &2. | Space: object requires documentation | |
21 | 020 | Error release status not set for overlapping condition records for &1 &2. | Space: object requires documentation | |
22 | 021 | Overlap condition records detected as expected. | The short text describes the object sufficiently | |
23 | 022 | Overlapping condition records not resolved for &1 &2. | Space: object requires documentation | |
24 | 023 | Release status not reset after resolution of overlap for &1 &2. | Space: object requires documentation | |
25 | 024 | Overlap condition records resolved as expected. | The short text describes the object sufficiently | |
26 | 025 | Overlap functionality cannot be tested due to error in condition record. | The short text describes the object sufficiently | |
27 | 026 | Scale table &1 is not initial for application &2 usage &3 for scale dim 0 | The short text describes the object sufficiently | |
28 | 027 | Scale table &1 is initial for application &2 usage &3 for scale dim > 0. | The short text describes the object sufficiently | |
29 | 028 | Record values mismatch between API and database for scales field. | The short text describes the object sufficiently | |
30 | 029 | Mismatch between the API and DB in &1 table | The short text describes the object sufficiently | |
31 | 032 | Condition maintenance not rejected even though KOPOS is greater than 1. | The short text describes the object sufficiently | |
32 | 033 | Condition record was selected in change mode even though KOPOS > 1. | The short text describes the object sufficiently | |
33 | 035 | Cond. record was not deleted successfully from the condition table | The short text describes the object sufficiently | |
34 | 036 | Cond. record was not deleted successfully from the condindx table | The short text describes the object sufficiently | |
35 | 040 | Creation of condition record with scales failed for application &1 | The short text describes the object sufficiently | |
36 | 041 | Runtime for &1 of &2 condition records is &3 microseconds. | The short text describes the object sufficiently | |
37 | 043 | Maintenance of cond. rec. was possible even for wrong key CT field | The short text describes the object sufficiently | |
38 | 044 | CT key fields check not possible as the test cond. record has problems | The short text describes the object sufficiently | |
39 | 045 | CT ky fields could be changed for existing condition record | The short text describes the object sufficiently | |
40 | 046 | Not all error messages were detected in validity window tests | The short text describes the object sufficiently | |
41 | 053 | Scales tables are initial for a condition record which has scales. | The short text describes the object sufficiently | |
42 | 054 | Maintenance mode is &1, where &2 is expected. | The short text describes the object sufficiently | |
43 | 056 | Dbaction value is not set to 'U' during update. | The short text describes the object sufficiently | |
44 | 058 | Unable to create working set handles for application &1 during setup. | The short text describes the object sufficiently | |
45 | 059 | No suitable configuration found to continue the CT fields test | The short text describes the object sufficiently | |
46 | 060 | No record was selected for lock verification (sceanrio &1). | The short text describes the object sufficiently | |
47 | 062 | Unable to carry out &1 test for application &2 (group &3). | The short text describes the object sufficiently | |
48 | 101 | Lock is not present as expected (&1, &2, &3). | The short text describes the object sufficiently | |
49 | 102 | Lock is erroneously present (&1, &2, &3). | The short text describes the object sufficiently | |
50 | 106 | *Messages for Simulation in pricing report 106 - 130* | The short text describes the object sufficiently | |
51 | 107 | Condition records deleted successfully. | The short text describes the object sufficiently | |
52 | 108 | Condition record found in DB with release status ' &1 ' as expected. | The short text describes the object sufficiently | |
53 | 109 | Condition record with expected release status ' &1 ' not found. | The short text describes the object sufficiently | |
54 | 110 | Cond. records with same key field values found, but no overlap detected. | Space: object requires documentation | |
55 | 111 | Condition records with different release status found as expected. | The short text describes the object sufficiently | |
56 | 112 | Cond. record which had status 'released' is found with deleted marked. | The short text describes the object sufficiently | |
57 | 113 | Cond. record which had status 'B' is not found in DB as expected. | The short text describes the object sufficiently |
History
Last changed on/by | 20110810 | SAP | |
SAP Release Created in | 500 |