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