BTP_DL -
The following messages are stored in message class BTP_DL: .
It is part of development package BTP_DL in software component CA-LT. This development package consists of objects that can be grouped under "BTP Application Data Layer Basis".
It is part of development package BTP_DL in software component CA-LT. This development package consists of objects that can be grouped under "BTP Application Data Layer Basis".
Message Nr ▲ | Message Text |
|---|---|
| 001 | No phase type assigned to solution |
| 002 | No execution plan variant assigned to solution |
| 003 | Non of the assigned phase types is contained in the pattern &1 |
| 004 | No roadmap contained in solution item list of &1 |
| 005 | Only one roadmap allowed per solution |
| 006 | Combined conversion packages, analyses, and LTR solutions are forbidden |
| 007 | Only one analysis allowed in a solution |
| 008 | No conversion package, no analysis, and no LTR solution contained |
| 009 | Solutions with conversion packages must have landscape template &1 |
| 010 | Solutions with an analysis must have landscape template &1 or &2 |
| 011 | Solution has no portfolio items |
| 012 | No master parent set for requirement |
| 013 | A package number must be specified for process type SLOP |
| 014 | Package &1 does not exist in CNVPACK in client 000 |
| 015 | No Solution Manager roadmap GUID specified |
| 016 | No web dynpro component specified |
| 017 | No analysis application specified |
| 018 | Web dynpro component &1 does not exist in this system |
| 019 | No docu object assigned |
| 020 | No description entered |
| 021 | No DOCUTYPE specified |
| 022 | No DOCUOBJ specified |
| 023 | General text &1 does not exist in this system |
| 024 | A requirement cannot be its own master parent |
| 025 | For process types different to SLOP no package number must be specified |
| 026 | All contained PCL packages must have same process type |
| 027 | Parameters updated |
| 028 | Solution of requirement must not be contained in optional solutions |
| 029 | Different roadmaps for '&1' and '&2' |
| 030 | Answer no. &1 is assigned to the invalid value &2. |
| 031 | &1 &2 is consistent |
| 032 | &1 &2 is initial |
| 033 | No items contained in project template |
| 034 | Not all mandatory RFC connections are specified |
| 035 | Not all mandatory systems are specified |
| 036 | System type &1 is not source or target of an RFC connection |
| 037 | RFC connection &1 from &2 to &3 is mandatory but &4 is optional |
| 038 | RFC destination &1 cannot be checked (source system not defined) |
| 039 | RFC destination &1 cannot be checked (source system not defined) |
| 040 | No default Solution Manager project found |
| 041 | No work center project found for Solution Manager project &1 |
| 042 | Related docu object &1 is hidden |
| 043 | Solution item &1 is hidden |
| 044 | Landscape type &1 is hidden |
| 045 | Execution plan variant &1 is hidden |
| 046 | Phase type &1 is hidden |
| 047 | System type &1 is hidden |
| 048 | Tag &1 is hidden |
| 049 | Attribute &1 is hidden |
| 050 | Docu object &1 is hidden |
| 051 | Additional docu object &1 is hidden |
| 052 | Project type &1 is hidden |
| 053 | No project type specified |
| 054 | Project phase &1 is hidden |
| 055 | No phase type set |
| 056 | Master parent &1 is hidden |
| 057 | Additional child &1 is hidden |
| 058 | Solution &1 is hidden |
| 059 | Adhoc analysis &1 is hidden |
| 060 | Optional solution &1 is hidden |
| 061 | Solution of requirement must not be contained in required solutions |
| 062 | Required solution &1 is hidden |
| 063 | Required solution '&1' is also assigned as optional solution |
| 064 | Solution &1 not specified |
| 065 | For solutions &1 and &2 there is already configuration set &3 defined |
| 066 | Same solutions &1 specified twice |
| 067 | If no package number is specified then a process type is required |
| 068 | Neither HTTPS nor HTTP is configured. Check transaction SMICM. |
| 069 | Internal error: System Landscape Type not found |
| 070 | System landscape &1 uses same RFC connections |
| 071 | Project Phase: &1 |
| 072 | &1 &2 &3 |
| 073 | No messages available |
| 074 | &1 messages of type 'information' |
| 075 | No package created yet |
| 076 | Package Phase: &1 |
| 077 | No phases available |
| 078 | No steps available |
| 079 | Not executed yet |
| 080 | Log not available |
| 081 | Step: &1 |
| 082 | There is a newer version available of &1 |
| 083 | Required solution &2 of requirement &1 is missing |
| 084 | Item &1 has a different scenario |
| 085 | Step &1 contains &2 solution(s) |
| 086 | Step &1 contains solution '&2' |
| 087 | Check step &1 for combining with step &2 |
| 088 | Combining of '&1' with '&2' is not possible |
| 089 | Combining of '&1' with '&2' is possible |
| 090 | Exactly one RFC destination must be flagged for PIFD initialization |
| 091 | Solutions &1 and &2 differ in used system landscape type |
| 092 | Exactly one RFC destination must be flagged for PIFD validation |
| 093 | The RFC destination used for PIFD initialization must not be optional |
| 094 | TDMS solutions '&1' and '&2' are not compatible |
| 095 | Step has already been started |
| 096 | '&1' is obsolete |
| 097 | Only one LTR solution allowed in a solution |
| 098 | Analyses and LTR solutions cannot be used together in a solution |
| 099 | No help portal path specified |
| 100 | Project Template Status |
| 101 | History |
| 102 | &1 &2 has been added by user &3 |
| 103 | &1 &2 has been removed by user &3 |
| 104 | TDMS requirements '&1' and '&2' are not compatible |
| 110 | Project &1 in Scenario &2 not found |
| 111 | No Project for Package &1 found |
| 112 | Input required |
| 120 | Project template &1 has been copied to &2 |
| 121 | New version &1 of project template &2 has been created |
| 122 | New phase '&1' has been added to project execution plan |
| 123 | Solution '&1' has been added to phase '&2' |
| 150 | No server entered for system &1 |
| 151 | No system number entered for system &1 |
| 152 | No language entered for system &1 |
| 153 | No user entered for system &1 |
| 154 | No password entered for system &1 |
| 155 | Setting password in &1 for RFC destination &2 failed: &3 |
| 156 | Distribution of RFC destination &1 failed |
| 157 | Class &1 does not exist |