/SAPCND/MASTERDATA - For the test of masterdata only
The following messages are stored in message class /SAPCND/MASTERDATA: For the test of masterdata only.
It is part of development package /SAPCND/TEST_T in software component AP-PRC-CON. This development package consists of objects that can be grouped under "Test tools for condition technique".
It is part of development package /SAPCND/TEST_T in software component AP-PRC-CON. This development package consists of objects that can be grouped under "Test tools for condition technique".
Message Nr ▲ | Message Text |
---|---|
000 | * Test function modules and reports for creating master data * |
001 | Condition record is successfully created. |
002 | Condition record(s) not created due to time period overlap. |
003 | Condition record(s) not created due to errors (see log). |
004 | Primary key (VARNUMH) must be filled. |
005 | Condition record is successfully deleted. |
006 | Record values mismatch between API and database for field &1. |
007 | Condition record in DB not selected by the API |
008 | No Condition record for change selected |
009 | API creates &1 and not &2 condition records |
010 | No Condition record for delete selected |
011 | The BADI &1 does not have active implementation |
012 | The application &1 is not registered for ABAP Unit test |
013 | The usage &1 is not registered for ABAP Unit test |
014 | Condition maintenance group &1 does not have any group items. |
015 | Application &1 returned wrong condition maintenance group &2 |
016 | Usage &1 did not participate in change condition records testing |
017 | Condition record created by API not present in database for &1 &2 &3. |
018 | Errors in condition record maintenance (see log). |
019 | Overlapping condition records not detected for &1 &2. |
020 | Error release status not set for overlapping condition records for &1 &2. |
021 | Overlap condition records detected as expected. |
022 | Overlapping condition records not resolved for &1 &2. |
023 | Release status not reset after resolution of overlap for &1 &2. |
024 | Overlap condition records resolved as expected. |
025 | Overlap functionality cannot be tested due to error in condition record. |
026 | Scale table &1 is not initial for application &2 usage &3 for scale dim 0 |
027 | Scale table &1 is initial for application &2 usage &3 for scale dim > 0. |
028 | Record values mismatch between API and database for scales field. |
029 | Mismatch between the API and DB in &1 table |
032 | Condition maintenance not rejected even though KOPOS is greater than 1. |
033 | Condition record was selected in change mode even though KOPOS > 1. |
035 | Cond. record was not deleted successfully from the condition table |
036 | Cond. record was not deleted successfully from the condindx table |
040 | Creation of condition record with scales failed for application &1 |
041 | Runtime for &1 of &2 condition records is &3 microseconds. |
043 | Maintenance of cond. rec. was possible even for wrong key CT field |
044 | CT key fields check not possible as the test cond. record has problems |
045 | CT ky fields could be changed for existing condition record |
046 | Not all error messages were detected in validity window tests |
053 | Scales tables are initial for a condition record which has scales. |
054 | Maintenance mode is &1, where &2 is expected. |
056 | Dbaction value is not set to 'U' during update. |
058 | Unable to create working set handles for application &1 during setup. |
059 | No suitable configuration found to continue the CT fields test |
060 | No record was selected for lock verification (sceanrio &1). |
062 | Unable to carry out &1 test for application &2 (group &3). |
101 | Lock is not present as expected (&1, &2, &3). |
102 | Lock is erroneously present (&1, &2, &3). |
106 | *Messages for Simulation in pricing report 106 - 130* |
107 | Condition records deleted successfully. |
108 | Condition record found in DB with release status ' &1 ' as expected. |
109 | Condition record with expected release status ' &1 ' not found. |
110 | Cond. records with same key field values found, but no overlap detected. |
111 | Condition records with different release status found as expected. |
112 | Cond. record which had status 'released' is found with deleted marked. |
113 | Cond. record which had status 'B' is not found in DB as expected. |