FDT_DEPLOYMENT - Messages for deployment
The following messages are stored in message class FDT_DEPLOYMENT: Messages for deployment.
It is part of development package SFDT_SERVICE in software component BC-SRV-BR. This development package consists of objects that can be grouped under "BRFplus: Services".
It is part of development package SFDT_SERVICE in software component BC-SRV-BR. This development package consists of objects that can be grouped under "BRFplus: Services".
Message Nr ▲ | Message Text |
|---|---|
| 000 | BRFplus deployment of &1 by &2 on &3 |
| 001 | BRFplus application &1 is assigned to package &2 |
| 002 | Report problems to application component &1 |
| 003 | Deployment failed due to runtime exception &1 |
| 004 | Deployment of application &1 failed |
| 005 | Use transaction FDT_DEPLOYMENT_LOG with external ID &1 for details |
| 006 | &1 objects were successfully deployed |
| 007 | &1 objects could not be activated |
| 008 | &1 objects could not be adapted to new version |
| 009 | Deployment of objects of multiple applications is not permitted |
| 010 | Deployment exit class &1 cannot be instantiated |
| 011 | Deployment exit &1 is not applicable for &2 |
| 012 | No applicable deployment exit found for &1 |
| 013 | Executing deployment exit class &1 for &2 failed |
| 014 | Deployment failed due to temporary restrictions |
| 015 | Deployment exit class &1 is executed for &2 |
| 016 | Checking if deployment exit &1 is applicable for &2 ... |
| 017 | Deployment is running in force mode. Customer changes might get lost. |
| 018 | Application TMP cannot be deployed |
| 019 | Unnamed objects cannot be deployed separately |
| 020 | Recursive deployment request is not permitted |
| 021 | Deployment into development client is not permitted |
| 022 | Specify at least one object to deploy |
| 023 | Check transport request '&1' |
| 024 | Deployment started from program &1 |
| 025 | End of deployment log &1 |
| 026 | Erraneous deployment exit class &1 detected (&2) |
| 027 | Undeclared exception &1 is thrown in &2 |
| 028 | At &1: &2 &3, line &4 |
| 030 | &1: Object is already deployed on latest version |
| 031 | &1: Deployment of object skipped |
| 032 | &1: Deployment of object failed |
| 033 | &1: Deployment of object succeeded |
| 034 | Deployment status of &1: &2 |
| 040 | Prior deployment status: &1 |
| 041 | Deployment objects with inactive version found |
| 042 | Deployment object &1 is inactive |
| 043 | No active version exists for deployable object &1 |
| 044 | Deployment failed &1 times at &2, no further attempts |
| 045 | No active version for deployable object &1 |
| 050 | Locking failed for arg &1, mode '&2' on &3 |
| 051 | Locked by user &1 in client &2, transaction '&3' |
| 052 | Locked with arg &1, mode '&2' |
| 060 | Reporting deployment status to CCMS monitoring failed |
| 061 | Object &1 is not a deployable object |
| 070 | Copying of objects succeeded |
| 071 | Copying of objects failed |
| 072 | Activation of objects succeeded |
| 073 | Activation of objects failed |
| 074 | Saving of objects succeeded |
| 075 | Saving of objects failed |
| 080 | |
| 100 | Object &1 not found (&2) |
| 101 | Object &1 has illegal type &2 (&3) |
| 102 | Changes for &1 cannot be adapted automatically |
| 103 | Named object &1 needs to be adapted manually |
| 104 | Object &1 not copied to new inactive version |
| 105 | Changes for type &1 cannot be adapted automatically |
| 109 | |
| 110 | Incompatible data object &1: Different types |
| 111 | Incompatible data object &1: Different ID and name |
| 112 | Incompatible element &1: Value list with different DDIC binding |
| 113 | Incompatible element &1: Value list with different GDT binding |
| 114 | Incompatible element &1: Value list with different binding type |
| 115 | Incompatible element &1: Different element type |
| 116 | Incompatible element &1: Length &2 less than &3 |
| 117 | Incompatible element &1: Decimals &2 less than &3 |
| 118 | Incompatible element &1: Digits &2 less than digits &3 |
| 119 | Incompatible element &1: Only positive numbers allowed |
| 120 | Incompatible element &1: Different timepoint type |
| 121 | Incompatible element &1: Different compound object |
| 122 | Incompatible element &1: New value list with active existence check |
| 123 | Incompatible element &1: Severity of existence check changed |
| 125 | Incompatible structure &1: Different number of components |
| 126 | Incompatible structure &1: Component &2 is missing or has different type |
| 130 | Ambiguous position of column &1 in new deployment version |
| 131 | A column has been deleted in new deployment version |
| 132 | No compatible column in new version for current column &1 |
| 133 | Adapting decision table data failed |
| 134 | Column &1 of new version changed to require input in table cells |
| 135 | Adaption of expression type &1 in decision table not supported |
| 136 | Additional column &1 in new version requires input in table cells |
| 140 | Message not found |
| 141 | Object ID is not provided |
| 142 | Function ID is not provided |
| 143 | Related Object ID is not provided |
| 144 | Object ID: &1, Function ID: &2, Related Object ID: &3 |
| 145 | Mark one log entry |
| 146 | System is currently locked due to upgrade, deployment not possible |