FDT_DSM - BRFplus: Decision Service Manager
The following messages are stored in message class FDT_DSM: BRFplus: Decision Service Manager.
It is part of development package SFDT_BRS_DSM in software component BC-SRV-BR. This development package consists of objects that can be grouped under "Business Rule Services: Decision Service Manager".
It is part of development package SFDT_BRS_DSM in software component BC-SRV-BR. This development package consists of objects that can be grouped under "Business Rule Services: Decision Service Manager".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Error calling function module &1 |
| 001 | Communication failure using RFC connection &1 |
| 002 | RFC connection &1 does not exist |
| 003 | RFC connection &1 is not of type 'ABAP Connection' |
| 004 | System failure using RFC connection &1 |
| 005 | Exception &1 occurred while deploying service &2 |
| 006 | Managed system &1 does not exist |
| 007 | Missing lock on Decision Service Manager, please enqueue |
| 008 | Enqueue failed on decision service manager due to a system error |
| 009 | Classname &1 from managed system could not be used, new name &2 created |
| 010 | Application &1 has no managed system assigned |
| 011 | Managed system &1 does not exist |
| 012 | Managed system name &1 is already used |
| 013 | Error signing the generated code (sy-subrc &1) |
| 014 | &1 (object &2) is not allowed in decision service &3 |
| 015 | Objects of custom expression type (&1) are not deployable |
| 016 | Application exits are not allowed in remote services (service &1) |
| 017 | Select a service deployment first to show the &1 |
| 018 | Invalid selection; select a deployment to show the &1 |
| 019 | Error transforming the source code to a neutral code page (sy-subrc &1) |
| 020 | RFC connection &1: target system without Unicode support; see long text |
| 021 | Application exits are not allowed in remote services |
| 022 | Expression type &1 (object &2) is not allowed in remote services |
| 023 | Custom expression types (&1) are not allowed in remote services |
| 024 | &1 is already assigned to managed system &2 in client &3 |
| 025 | Add-on SAP NetWeaver Decision Service Management is not installed |
| 026 | Managed system name cannot be an empty string |
| 027 | Deployment failed; Managed system &1 does not exist |
| 028 | Please select the managed system to deploy the service |
| 029 | The DSM has unsaved changes, please save before deploying a new service |
| 030 | Managed system with RFC connection &2 already exists (&1) |
| 031 | &1 entries deleted from log |
| 032 | No matches for selection criteria, no entries deleted |
| 033 | Simulation of remote service in local system may result in errors |
| 034 | Approval workflow for service &1 started |
| 035 | Invalid selection; no service deleted |
| 036 | Cutoff timestamp is in the future |
| 037 | Deletion workflow for service &1 started with workflow ID &2 |
| 038 | No deployment exists in selected deletion time frame |
| 039 | &1 service deployment(s) successfully deleted |
| 040 | Authorization check for deployment in managed system failed |
| 041 | Authorization check for deletion in managed system failed |
| 042 | Authorization check for discarding deployments in managed system failed |
| 043 | Authorization check for retrieving XML from managed system failed |
| 044 | Authorization check for retrieving trace data from managed system failed |
| 045 | Authorization check for retrieving class code from managed system failed |
| 046 | No authorization to execute Decision Service Manager |
| 047 | Error signing the generated code : &1 |
| 048 | Managed system &1 created successfully |
| 049 | Deployment of service &1 to destination &2 has failed |
| 050 | Managed system &1 with RFC destination &2 has been created |
| 051 | Managed system &1 has been deleted |
| 052 | RFC destination from managed system &1 has been changed from &2 to &3 |
| 053 | Description of managed system &1 has been changed from &2 to &3 |
| 054 | Application &1 has been assigned to managed system &2 |
| 055 | Application &1: assignment changed from &2 to &3 |
| 056 | Assignment of application &1 to managed system &2 has been deleted |
| 057 | Service &1 has been deployed to managed system &2 |
| 058 | Deployments from &1 to managed system &2 for service &3 have been deleted |
| 059 | Deployment: Service &1 was already up to date in managed system &2 |
| 060 | All deployments for service &1 in managed system &2 have been deleted |
| 061 | Documentation of managed system &1 has been changed |
| 062 | Deployment of &1 to managed system &2 failed due to a syntax error |
| 063 | Deployment of &1 to managed system &2 failed due to a system error |
| 064 | Deployment of &1 to managed system &2 failed due to a communication error |
| 065 | System type of managed system &1 has been changed from &2 to &3 |
| 066 | Deployment from &1 in managed system &2 for service &3 has been deleted |
| 067 | Local DSM version of service is newer than deployed version |
| 068 | Local DSM version of service is older than deployed version |
| 069 | Object does not exist in the current Decision Service Management system |
| 070 | Object does not exist in this system; see long text |
| 071 | Cannot switch to edit mode - objects locked by user &1 |
| 072 | Service imported |
| 073 | Invalid combination of importing parameters in method &1 |
| 074 | Service was not imported |
| 075 | Application not found in DSM system; see long text |
| 077 | XML data exported (source: &1; target: &3; RFC: &2; time: &4) |
| 079 | Service '&1' is not active in managed system &2 |
| 080 | Deployment not possible due to usage of unit/currency exit class |
| 082 | No object selected |
| 086 | Enqueue failed; managed system &1 does not exist |
| 087 | Deploying services to production systems subject to license conditions |
| 088 | Select at least one managed system for deployment |
| 089 | Select at least one service for deployment |
| 090 | 50 of &1 available services are displayed |
| 091 | XML Export of &1 in remote system &2 was not succesful |
| 092 | Not all changes have been saved, please see the following messages |
| 100 | &1 uses more than &2 rules (&3), please split the ruleset |
| 101 | &1 uses more than &2 rules (&3), please split the loop expression |
| 102 | &1 uses more than &2 rows (&3), please split the decision table |
| 103 | &1 uses more than &2 nodes (&3), please split the tree |
| 104 | Service &1 uses more than &2 rules, please split the service |
| 105 | Service &1 uses more than &2 decision table rows please split the service |
| 106 | Service &1 uses more than &2 tree nodes, please split the service |
| 110 | Function module &1 is probably not existent in the managed system |
| 120 | No application or service selected; please select one from the table |
| 121 | No exit class specified; please enter exit name |
| 122 | Exception during call of exit class &1 |
| 123 | Exit class &1 not called in Decision Manager system due to non-existence |
| 130 | Exit class &1 does not implement interface IF_FDT_DSM_PARTNER_EXIT |
| 131 | ABAP platforms (managed system &1) don't support partner exits |
| 132 | Partner exit class &1 does not support the retrieval of deployments |
| 133 | Partner exit class &1 does not support the deletion of deployments |
| 134 | Partner exit class &1 does not support the testing of deployments |
| 135 | Partner exit class &1 does not support the deployment of services |
| 136 | Deployment of service &1 was activated from &2 to &3 |
| 137 | Partner exit class &1 does not support XML export from the managed system |
| 138 | Partner exit class &1 does not support the retrieval of source code |
| 139 | No managed system with active partner module type simulation available |
| 140 | Partner exit class &1 does not support the retrieval of traces |
| 150 | Enqueue on deployment exit not possible due to foreign lock |