CNV_10030 - Nachrichtenklasse f�r Paket 10030
The following messages are stored in message class CNV_10030: Nachrichtenklasse f�r Paket 10030.
It is part of development package CNV_10030 in software component CA-DT-CNV-BAS. This development package consists of objects that can be grouped under "CNV package 10030".
It is part of development package CNV_10030 in software component CA-DT-CNV-BAS. This development package consists of objects that can be grouped under "CNV package 10030".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Transaction was canceled by user |
| 002 | Package no. &1 does not lie in the interval for customer package numbers |
| 003 | &2 records were inserted in table &1 |
| 004 | Error while writing to table &1 |
| 005 | All required read-only fields exist |
| 006 | &2 records were deleted from table &1 |
| 007 | All required determination records are available |
| 008 | Activity "Analyze Tables and Fields for Org. Units" is running |
| 009 | No conversion package or customer-specific package is blended |
| 010 | Client &1 does not contain any determination objects |
| 011 | Client &1 is used as the delivery client |
| 012 | &1 programs were scheduled for modification |
| 014 | &1 target determination object records were created |
| 015 | &1 parameters were set specifically for CWB |
| 016 | Check the results in "Job Monitor: Analyze Tables/Fields for Org. Units" |
| 017 | Check the logs in "Job Monitor: Load Determination Data" |
| 018 | &1 cardinality requirements were loaded |
| 019 | &1 determination paths were flagged with cardinality check |
| 020 | &1 additional cardinality requirements were created |
| 021 | &1 package-specific parameters were loaded |
| 022 | &1 path-specific parameters were loaded |
| 023 | &1 parameters were set package-dependent |
| 024 | &1 existing logs were deleted |
| 025 | &1 jobs were scheduled, but not yet started |
| 026 | No analysis should be carried out |
| 027 | &1 records for package dependencies were created |
| 028 | Scheduling of more jobs was not necessary |
| 029 | Cross-package parameter for F4 help for package number was set |
| 030 | Program &1 does not exist |
| 031 | Enter at least a package number or a program |
| 032 | Program &1 was modified successfully |
| 033 | Program &1 does not have a place for modification |
| 034 | Program &1 did not require modification |
| 035 | Error in prog. &1: &2 and &3 must not follow directly one after the other |
| 036 | Error in program &1: Indicator for end of block after &2 is missing |
| 037 | Error in program &1: Indicator for start of block after &2 is missing |
| 038 | &1 jobs were scheduled; they are started on &2 at &3 |
| 039 | The scheduled jobs are started on &2 at &2 |
| 040 | &1 paths were marked as to be loaded |
| 041 | &1 paths were excluded as suggestions |
| 042 | The org. package is not contained in package &1 |
| 043 | Activity "Initial Load of Objects" was not yet executed |
| 044 | &1 object types were selected for mandatory loading |
| 045 | Activity "Identify Settings for Org. Unit Determination" is running |
| 046 | Edit determination paths for org. units is running |
| 047 | No recalculation of memory requirements |
| 048 | Incorrect source package number &3 for field &1-&2 (to be converted) |
| 049 | Function module &1 for determination of INDX structures does not exist |
| 050 | Table name &2 has more than 30 characters; define a representative |
| 051 | Package &1 is not the active package (currently package &2 is active) |
| 052 | Package-independent parameter for determining package name was set |
| 053 | Dependent package &1 cannot be assigned to package &2; TDetObj &3 missing |
| 054 | Dependent package &1 cannot be assigned to package &2; TDetObj &3 missing |
| 055 | Package-independent parameter for determining customer namespace was set |
| 056 | &1 tables have conflict detection enabled |
| 057 | &1 non-transparent field definitions were marked for loaded |
| 058 | For &1 no assignment of determination has been delivered |
| 059 | For &1-&2 no assignment of determination has been delivered |
| 060 | For &1 no assignment of determination has been delivered |
| 061 | For &1 the suggested assignment of determination was released by syst. |
| 062 | For &1-&2 no assignment of determination has been delivered |
| 063 | For &1-&2 the suggested assignment of determination was released by syst. |
| 064 | For &1 the suggested assignment of determination was released by syst. |
| 065 | For &1-&2 the suggested assignment of determination was released by syst. |
| 067 | All required evaluation records are available |
| 068 | Activity "Identify Settings for Non-transparent Fields" is running |
| 069 | Activity "Edit Rule Assignments for Non-transparent Fields" is running |
| 070 | If you execute the activity again; messages of the last run do not appear |
| 071 | If you execute the activity again; messages of the last run do not appear |
| 080 | Source package number for field &1-&2 (to be converted) was not specified |
| 083 | &1 package-specific parameters for CWB were loaded |
| 088 | Check of the path settings |
| 089 | Calculation of storage requirements for determination paths |
| 090 | A determination for field &1-&2 (to be converted) is not released |
| 091 | Field &1-&2 (to be converted) does not have a determination assigned |
| 092 | All fields to be converted have determination assigned |
| 093 | All assignments are maintained correctly |
| 094 | Transaction CNV_10030_MEMTMON shows required memory space per table |
| 095 | For field &1-&2 (to be converted), TDetObject &3 is not defined as such |
| 096 | A determination for table &1 has not been released |
| 097 | Table &1 does not have a determination assigned |
| 098 | All relevant tables have determination assigned |
| 100 | Table &1 is not relevant for the conversion |
| 101 | Table &1 does not contain any relevant fields for the conversion |
| 102 | There is no record for table &1 in table CNV_10030_PTABLE |
| 103 | There is no record for table &1 in table CNV_10030_PFIELD |
| 104 | Delimitation at the time of the selection is not possible for table &2 |
| 105 | Delimitation at event 'selection' is not possible for INDX table &2 |
| 106 | Possible delimitation should take place only at the time of the selection |
| 107 | This is a table-specific scenario |
| 108 | A possible determination at the time of selection should not take place |
| 110 | Best guess mode active for &1 |
| 111 | Activity &1 is still running in package &2 , phase &3 |
| 112 | Best guess mode active for &1 |
| 159 | No rule assignment delivered for component &3 of non-transp. field &1-&2 |
| 162 | No rule assignment delivered for component &3 of non-transp. field &1-&2 |
| 163 | For comp. &3 of &1-&2 the suggested rule assignm. was released by system |
| 165 | For comp. &3 of &1-&2 the suggested rule assignm. was released by system |
| 166 | For component &3 of &1-&2, the suggested rule assignment is not released |
| 167 | Component &3 of non-transparent field &1-&2 does not have a rule assigned |
| 168 | All relevant components of non-transparent fields have a rule assigned |
| 169 | There is no record for table &1 in table CNV_10020_TABREF |
| 170 | &1 data includes for direct determination have been generated |
| 171 | &1 program includes for direct determination have been generated |
| 172 | There is no record for cluster table &1 in table CNV_10020_TABREF |
| 173 | Parameter component &1 does not exist for parameter field value &2 |