ISLM_API - API Messages
The following messages are stored in message class ISLM_API: API Messages.
It is part of development package S_INTSCN_LM_GEN in software component BC-ISM. This development package consists of objects that can be grouped under "General functions".
It is part of development package S_INTSCN_LM_GEN in software component BC-ISM. This development package consists of objects that can be grouped under "General functions".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1&2&3&4 |
| 001 | This function is only availabe for systems on SAP HANA |
| 002 | &1 |
| 003 | Failed to retrieve the Pipeline ID for Deployment. |
| 004 | Enter a valid Model name. |
| 006 | Insufficient authorization to generate intelligent scenario |
| 007 | Missing authorization: activity(&1) entity(&2) |
| 008 | Missing authorization: object(&2) activity(&1) scenario(&3) |
| 009 | Error occurred while generating intelligent scenario &1 |
| 010 | Error occurred while creating functional area |
| 011 | Error occurred while creating intelligent scenario |
| 012 | Error occurred while creating modeling context |
| 013 | Error occurred while creating model version |
| 014 | Error occurred while reading functional areas |
| 015 | Error occurred while reading model contents |
| 016 | Error occurred while reading intelligent scenarios |
| 017 | Error occurred while reading intelligent scenario |
| 018 | Error occurred while reading modeling contexts |
| 019 | Error occurred while reading modeling context |
| 020 | Error occurred while reading modeling context filters |
| 021 | Error occurred while reading hierarchy objects |
| 022 | Error occurred while reading model versions |
| 023 | Error occurred while reading model version |
| 024 | Error occurred while reading model version filters |
| 025 | Application cannot have a parent path |
| 026 | Mandatory filter not found |
| 027 | Error occurred while reading modeling contexts |
| 028 | Error occurred while deleting functional area |
| 029 | Error occurred while deleting intelligent scenario |
| 030 | Error occurred while deleting modeling context |
| 031 | Error occurred while deleting model version |
| 032 | Error occurred while scheduling model version training |
| 033 | Error occurred while training model version |
| 034 | Error occurred while activating model version |
| 035 | Invalid model version update |
| 036 | Error occurred while deactivating model version |
| 037 | Error occurred while reading targets |
| 038 | Error occurred while reading dataset key fields |
| 039 | Error occurred while reading parameters |
| 040 | Error occurred while reading validation rules |
| 041 | No data found |
| 042 | Invalid filter conditions |
| 043 | Error occurred while creating model |
| 044 | Error occurred while deleting model |
| 045 | Regeneration of class &1 is not necessary |
| 046 | Additional information was added to the log |
| 047 | Unknown exception occurred |
| 048 | Error occurred while reading model |
| 049 | Error occurred while updating model version |
| 050 | Error scheduling training (phase &1, subrc &2 ) |
| 051 | Insert error: table &1 subrc &2 |
| 052 | Error occurred while creating HANA workload class |
| 053 | Error occurred while creating HANA workload mapping |
| 054 | Error occurred while creating intelligent scenario draft |
| 055 | A intel. scenario draft can only be created in the context of a catalog |
| 056 | Error occurred while reading catalog |
| 057 | Error occurred while reading intelligent scenario draft |
| 058 | Error occurred while deleting intelligent scenario draft |
| 059 | Invalid scenario type |
| 060 | Invalid dataset type |
| 061 | Conversion from binary failed |
| 062 | ABAP data element &1 not compatible with DB type &2 |
| 063 | Supplied signature and existing signature are not consistent |
| 064 | Supplied ABAP data element &1 is not valid |
| 065 | Signature field &1 missing from submitted signature |
| 066 | Signature structure &1 not found in submitted signature |
| 067 | No save has occurred, please submit valid changes |
| 068 | Dataset and input signature are not consistent |
| 069 | Deleting intelligent scenario draft &1 &2... |
| 070 | Error occurred while updating intelligent scenario draft |
| 071 | No record found for key '&1' |
| 072 | Invalid filter, key '&1' must be specified |
| 073 | Only one filter may be specified for property &1 |
| 074 | Error occurred while creating model draft |
| 075 | Mandatory field &1 of type '&2' not found in model |
| 076 | Model type &1 incompatible with intelligent scenario type &2 |
| 077 | Only 1 draft model can exist under an intelligent scenario |
| 078 | 2 models with the same name cannot exist under a intelligent scenario |
| 079 | Model specification decoding failed |
| 080 | A model specification must be provided |
| 081 | Deleting model draft &1 &2... |
| 082 | Invalid model draft(s) supplied |
| 083 | Error occurred while deleting model draft |
| 084 | Invalid model update |
| 085 | Invalid property '&1' for table/view &2 |
| 086 | Invalid filter operator '&1' |
| 087 | Duplicate entries provided for property '&1' |
| 088 | Multiple operators on property '&1' are not permitted |
| 089 | Error occurred while queueing intelligent scenario regeneration |
| 090 | Model Training was successful |
| 091 | Model Training was unsuccessful |
| 092 | Error occurred while acquiring object lock (subrc &1) |
| 093 | Error occurred during Object hash generation (subrc &1) |
| 094 | Processing completed with errors. See spool list |
| 095 | Exception occurred in &1->&2 at line &3 |
| 096 | Error occurred during Specified Model training |
| 097 | Error occurred during Model Signature extraction |
| 098 | Invalid model version status for training |
| 099 | Error occurred during model information extraction |
| 100 | Error occurred during model import |
| 101 | Error occurred while creating model specification |
| 102 | Model specification updated |
| 103 | Model version activation was unsuccessful |
| 104 | Model version activation was successful |
| 105 | ISLM Delivery Unit version not found |
| 106 | Sign '&1' is not supported |
| 107 | Please provide exactly 1 target |
| 108 | Provided target &1 does not exist in dataset |
| 109 | Error occurred while creating configuration from model definition |
| 110 | Invalid method call for object type &1. |
| 111 | A model specification or definition must be provided. |
| 112 | Intelligent scenario class deleted successfully |
| 113 | Model version deleted successfully |
| 114 | Models deleted successfully |
| 115 | Modeling contexts deleted successfully |
| 116 | The intelligent scenario draft was deleted successfully |
| 117 | Please provide exactly 1 parent type |
| 118 | Please provide exactly 1 parent GUID |
| 119 | Error occurred during JSON deserialisation |
| 120 | Invalid adapter ID |
| 121 | Executor class missing for task type &. Please check configuration. |
| 122 | Only additional models in status 'Draft' can be deleted |
| 123 | Entity detail '&1' not found |
| 124 | A intelligent scenario must have a parent |
| 125 | Additional models can only be added to extensible intelligent scenarios |
| 126 | To publish your intelligent scenario, install the latest UMML4HANA 1 DU |
| 127 | The bindings of this model cannot be modified |
| 128 | Failed to retrieve model deployment. |
| 129 | Failed to retrieve use of Interface/s |
| 130 | Filter on field &1 is not supported |
| 131 | Error occurred while reading model &1 |
| 132 | |
| 133 | Error occurred while reading entity details |
| 134 | Error occurred while reading models |
| 135 | Error occurred while reading datasets |
| 136 | Failed to retrieve model deployment. |
| 137 | Task status is &1. It should be in pending status to process further. |
| 138 | Unknown error. Couldn't create model deployment. |
| 139 | Error occurred while reading scenario history |
| 140 | Invalid default: parameter '&1', value '&2' |
| 141 | Specified parameter &1 does not exist |
| 142 | Error occurred during creation of parameter GUID |
| 143 | For &1, the max. number of default values allowed is &2 |
| 144 | Error occurred while saving model version parameters |
| 145 | Invalid navigation |
| 146 | Invalid Model name (&1) |
| 147 | |
| 148 | |
| 149 | &1 intelligent scenarios will be processed. |
| 150 | &1 active model versions will be processed. |
| 151 | Error occurred while importing model version &1 _ &2 _ &3 |
| 152 | Error occurred while generating the apply for intelligent scenario &1 |
| 153 | &1 model versions have been processed successfully. |
| 154 | &1 intelligent scenarios have been processed successfully. |
| 155 | Model version &1 client &2 will not be processed |
| 156 | Model version &1 client &2 Intelligent Scenario &3 imported successfully |
| 157 | Intelligent scenario &1 has been processed successfully. |
| 158 | There are no active model versions to process |
| 159 | &1 model versions have not been processed correctly |
| 160 | &1 intelligent scenarios have not been processed correctly |
| 161 | Start processing model version &1 _ &2 _ &3 |
| 162 | Start processing the intelligent scenarios |
| 163 | Error occurred while processing intelligent scenario &1 |
| 164 | Start processing intelligent scenario &1 |
| 165 | Model Version: &1 |
| 166 | The reference entity ID cannot be left blank. |
| 167 | The reference entity type cannot be left blank. |
| 168 | Unknown error. Configuration data cannot be created. |
| 169 | Unknown error. Configuration data cannot be updated. |
| 170 | The model version GUID cannot be left blank. |
| 171 | The configuration GUID cannot be left blank. |
| 172 | Failed to retrieve Model version and Configuration details. |
| 173 | Unknown error. Model version parameters cannot be created. |
| 174 | Training Started At time already updated in ISLM_MDLVRSN table. |
| 175 | Training Ended At time already updated in ISLM_MDLVRSN table. |
| 176 | Training Started At time is mandatory for updating training duration. |
| 177 | Training Ended At time is mandatory for updating training duration. |
| 178 | Training Ended At time must be more than Training Started At time. |
| 179 | Deployment name : &1 |
| 180 | Model version name : &1 |
| 181 | Model definition inconsistency |
| 182 | Only one model version allowed |
| 200 | Dataset does not exist: &1 |
| 201 | Data reference &1 must reference the training dataset - &2. |
| 216 | |
| 249 | A draft intelligent scenario should have a model |
| 250 | The scenario name is missing |
| 251 | No parameters found for intelligent scenario (&1) |
| 252 | Unable to get edit lock on intelligent scenario (&1) |
| 253 | The table/view &1 does not exist |
| 254 | Generation of class &1 successful |
| 255 | Syntax error in generated class &1 |
| 256 | Error saving generated class &1 |
| 257 | Package &1 is local, which means the object is not transportable. |
| 258 | Object could not be added to the transport request |
| 259 | Object &1 could not be modified |
| 260 | Object &1 was updated successfully |
| 261 | Object &3 &1 was added to transport &2 |
| 262 | Class &1 is used in another object |
| 263 | Class &1 has not been generated |
| 264 | Package &1 does not exist |
| 265 | Object &1 already exists |
| 266 | Object &1 does not exist |
| 267 | You cannot move object &1 to package &2 |
| 268 | Could not generate class &1 |
| 269 | Class &1 deleted successfully |
| 270 | Could not delete class &1 |
| 271 | Class &1 was not fully deleted; it still exists in the repository |
| 272 | Run function &1 error with &2 |
| 273 | &1 intelligent scenario(s) found; report executed in &2 |
| 274 | Maintenance in process. Only display possible. |
| 275 | Error occurred while converting ABAP DDIC types to DB SQL types |
| 276 | DDIC type &1 not found |
| 277 | The object is locked by another TR &1 |
| 278 | Input parameter &1 has error |
| 279 | The value is: &1 |
| 280 | Signature and Dataset bindings cannot be updated simultaneously. |
| 281 | SQL Procedure updated |
| 282 | Drop not allowed for this/these model version SQL object(s). |
| 298 | Invalid model. Check that model exists and try again. |
| 299 | Invalid model version. Check that model version exists and try again. |
| 300 | The specified name is not valid. Please try again with a non-empty name. |
| 301 | The specified name is not unique. Please try again with a unique name. |
| 302 | The parent does not exist. Make sure the parent exists and try again. |
| 303 | A GUID could not be generated. Try again. |
| 304 | Enter a "High" value that is equal to or greater than the "Low" value. |
| 305 | Invalid scenario type. |
| 306 | Invalid bindings. Please try again with exactly one dataset bound. |
| 307 | Invalid binding. Check that referenced dataset exists and try again. |
| 308 | Invalid binding. Check that input structure exists and try again. |
| 309 | Binding mappings are not supported. Please try again without mappings. |
| 310 | Invalid signature type. Signature type must be 'Input' or 'Output'. |
| 311 | IT_CONFIG is a reserved signature name. Please try a different name. |
| 312 | Duplicate parameter. Please try again with unique parameter names. |
| 313 | A field is specified using a signature that does not exist. |
| 314 | Invalid input field type. Allowed values: "Input", "Key", "Target" |
| 315 | Invalid output field type. Allowed values: "Key", "Prediction" |
| 316 | Data element not found field &1/&2 |
| 317 | Invalid storage. Check that storage type exists and try again. |
| 318 | Target not specified. Please specify a target and try again. |
| 319 | Check that a prediction field is specified and try again. |
| 320 | Check that prediction type matches target type and try again. |
| 321 | Duplicate input field name. Please try again with unique names. |
| 322 | Duplicate input field position. Please try again with unique positions. |
| 323 | Duplicate output field name. Please try again with unique names. |
| 324 | Duplicate output field position. Please try again with unique positions. |
| 325 | Invalid dataset. Bound dataset does not have all required fields. |
| 326 | Mismatched keys. Check that the keys match for input and output. |
| 327 | Only one modeling context may be created per intelligent scenario. |
| 328 | The global modeling context cannot be deleted. |
| 329 | The dataset reference is malformed. Check the format and try again. |
| 330 | Invalid GUID. Check the GUID and try again. |
| 331 | Error occurred while parsing dataset reference. |
| 332 | Invalid binding. Dataset not valid for intelligent scenario |
| 333 | Invalid model version GUID. |
| 334 | EntityDetails are not supported for entity type '&1' |
| 335 | Input Key field/s not specified |
| 336 | Output Key field/s not specified |
| 337 | Invalid parent. Check the parent and try again. |
| 338 | Invalid binding. This model type should not have input bindings. |
| 339 | Table function name &1 is invalid |
| 340 | Table function &1 is inactive. |
| 341 | Errors occurred when trying to determine the status for table function &1 |
| 342 | The intelligent Scenario is not in a valid namespace |
| 343 | SQLView Name: &1 was generated successfuly. |
| 344 | Proposed CDS view name: &1 |
| 345 | A new CDS view will be generated for table function: &1 |
| 346 | A DCL exists on the apply view. The CDS view will be DCL-enabled. |
| 347 | An error occurred when trying to save the CDS view. |
| 348 | An error occurred when trying to add the object to TADIR. |
| 349 | Errors occurred while creating the CDS view. |
| 350 | Errors occurred while locking CDS View name: &1 |
| 351 | Table function &1 is not connected to intelligent scenario &2 |
| 352 | The table function and intelligent scenario are not in the same namespace |
| 353 | CDS view name could not be generated. Naming conflicts exist. |
| 354 | There are multiple DCLs for &1 |
| 355 | An exception occurred while trying to create the SQL name. |
| 356 | SQL view name could not be generated. |
| 357 | Invalid name class. |
| 358 | CDS view &1 created successfully. |
| 359 | Table function &1 doesn't have a correct corresponding CDS name. |
| 360 | Table function name could not be generated. Naming conflicts exist. |
| 361 | Class name could not be generated. Naming conflicts exist. |
| 362 | Apply dataset must be set before publishing the intelligent scenario. |
| 363 | DEFAULT model cannot be created. |
| 364 | DEFAULT is a SAP reserved name |
| 365 | Name conflict with existing object (&1 &2). Please modify name |
| 366 | Model name &1 is in an SAP namespace. Please use a customer namespace. |
| 367 | Please ensure that model &1 is in a valid ISLM supported namespace. |
| 368 | Invalid External ID. |
| 369 | External ID must include alphanumeric characters and hyphen(-) only. |
| 370 | Failed to generate access protection. Please open an incident. |
| 371 | The model definition is required to create a specification |
| 372 | The HEMI model name cannot be initial |
| 373 | The HEMI model is not ISLM compatible |
| 374 | Model specification should not be provided for HEMI models |
| 375 | Create model not supported. Please refer to SAP note 2764539. |
| 376 | The field "&1" won't be used in the training process. |
| 377 | Slash character ("/") is not supported. Please, check the field "&1". |
| 400 | Missing HANA library |
| 401 | Missing HANA function |
| 402 | PAI Engine setup required |
| 403 | PAI APL Adapter setup required |
| 404 | '/1ISLM/' namespace must be editable |
| 405 | '/1ISLM/' namespace not found |
| 406 | AMDP execution failed |
| 409 | Prediction class &1 for Intelligent Scenario &2 does not exist. |
| 410 | Prediction class &1 for Intelligent Scenario &2 is not active. |
| 450 | Invalid field length |
| 451 | The length has to be greater or equal to the number of decimals |
| 452 | Data type not supported |
| 453 | Couldn't read columns used in &1 or there are no columns |
| 454 | Key field/s inconsistency between initial IS model and new model |
| 455 | &1 dataset &2 and input signature are not consistent |
| 456 | Keys of training dataset &1 must match keys of Intelligent Scenario. |
| 457 | Keys of apply dataset &1 must match keys of Intelligent Scenario. |
| 458 | Dataset &1 (package &2) is HOME or LOCAL object |
| 459 | Published Intelligent Scenario in Package &1 cannot be deleted |
| 460 | A Published Intelligent Scenario cannot be deleted on this system |
| 461 | Class &1 (package &2) is HOME or LOCAL object |
| 462 | &1 &2 (package &3) is HOME or LOCAL object |
| 463 | A Published Intelligent Scenario cannot be updated on this system |
| 464 | Intelligent scenario cannnot be updated |
| 465 | Error occurred while updating intelligent scenario |
| 466 | Intelligent scenario update was successful |
| 498 | Model name: &1 |
| 499 | Model GUID: &1 |
| 500 | Created with &1 filters |
| 501 | Name: &1 |
| 502 | Parent: &1 |
| 503 | Deleting: &1 &2 |
| 504 | GUID: &1 |
| 505 | Filter index: &1 |
| 506 | > Field: &1 |
| 507 | > Low: &1 |
| 508 | > High: &1 |
| 509 | > Op: &1 |
| 510 | |
| 511 | > Low: Value is too long to be displayed |
| 512 | > High: Value is too long to be displayed |
| 513 | Deployment Name: &1 |
| 514 | > Parent: &1 |
| 515 | > GUID: &1 |
| 516 | > PS: &1 |
| 517 | PS: &1 |
| 518 | MC: &1 |
| 519 | Status: &1 |
| 520 | Parent name: &1 |
| 521 | Content name: &1 |
| 522 | Content version: &1 |
| 523 | > Name: &1 |
| 524 | Version: &1 |
| 525 | Filter at index &1 is not valid |
| 526 | Opearator &1 in filter at index &2 is not valid |
| 527 | MV: &1 |
| 528 | > Version: &1 |
| 529 | No signature fields found for PS: &1 |
| 530 | Deleting modeling context &1 &2 (&3) |
| 531 | Deleting model &1 &2 &3 (&4) |
| 532 | Deleting model version &1 &2 &3 (&4) |
| 533 | GUID &1 |
| 534 | Extracting model information |
| 535 | Importing model |
| 536 | Creating intelligent model |
| 537 | Intelligent scenario name can only contain the characters _, A-Z, 0-9. |
| 538 | Step &1 Runtime.... &2 |
| 539 | Load successful |
| 540 | Could not read columns of dataset &1 |
| 541 | Target name length can't exceed 27 for regression, 12 for classification. |
| 542 | Fields and dataset key fields will be overwritten. |
| 543 | Intelligent scenario &1 not found. Check the name and try again. |
| 544 | Operation successful |
| 545 | Operation cancelled |
| 546 | Bindings must be specified |
| 547 | Deleting model... |
| 548 | Previously active model versions and their parents cannot be deleted. |
| 549 | |
| 550 | User performed operations in the Intelligent Scenario Management App. |
| 551 | Transportable models cannot be deleted. |
| 552 | Catalog name must be supplied. |
| 553 | Transport number was not supplied. |
| 554 | Catalog could not be found. |
| 555 | Authorization missing for authorization object 'S_ABPLNGVS' |
| 556 | Intelligent scenario name is already assigned. |
| 557 | Authorization missing for authorization object 'S_DEVELOP' |
| 558 | Authorization missing for authorization object 'S_TRANSPRT' |
| 559 | Authorization missing for authorization object 'S_BTCH_NA1' |
| 560 | Authorization missing for authorization object 'S_TABU_DIS' |
| 561 | Deleting model deployment &1 &2 &3 (&4). |
| 562 | The model deployment is deleted successfully. |
| 563 | Delete the Intelligent Scenario class manually. |
| 564 | Task with status &1 not valid for execution |
| 565 | Task type &1 not supported |
| 566 | Task not found |
| 567 | Task type &1 not supported |
| 568 | Task type &1 not valid for training |
| 569 | Task &1 status: &2 |
| 570 | Transport conflict (objects contained already in &1) |
| 571 | Error occurred while reading task |
| 572 | Intelligent scenario with the same side-by-side scenario already exists. |
| 573 | Parent and reference intelligent scenario must match |
| 574 | Object type &1 not supported |
| 575 | Invalid serve flow end point uri for Inference Consumption |
| 576 | |
| 577 | The system is not properly configured for ATO. |
| 578 | Unable to release ATO related CDS View &1 |
| 579 | Model version not found. |
| 580 | Task Queue entry not found. |
| 581 | Model not found. |
| 582 | Delegate Execution not found. |
| 583 | Model Deploy not found. |
| 584 | Delegate Deployment not found. |
| 585 | Training is already scheduled for this model. Try again later. |
| 586 | Job scheduling is not configured. Contact the system administrator. |
| 587 | Is Job scheduling used: &1 |
| 588 | Deployment is already scheduled for this training. Retry later. |
| 589 | Model Deployment: &1 |
| 590 | &1 intelligent scenarios found in system. |
| 591 | &1 model versions found in client. |
| 592 | Client Copy executed in Test Mode. |
| 593 | Attempted to import &1 model version procedures. |
| 594 | &1 model version procedures imported successfully. |
| 595 | Regeneration started for &1 intelligent scenarios. |
| 596 | Intelligent scenario regeneration completed. |
| 597 | Processing skipped due to destination client settings |
| 598 | Inference version : &1 |
| 599 | MD: &1 |
| 600 | One or more objects are not avaliable for Table Function generation |
| 601 | Error during &1 generation |
| 602 | Error during &1 Save |
| 603 | Error during &1 Activate |
| 604 | Couldn`t create &1 object in Repository |
| 605 | &1 object generated successfully |
| 606 | Error reading DCL &1 |
| 607 | Couldn`t generate &1 source code |
| 608 | Unable to get edit lock &1 |
| 609 | &1 object type is not supported |
| 610 | Error Occured while Inserting PS generated objects to BOM |
| 611 | Table Function is not created for Intelligent scenario &1 |
| 612 | Table Function class is not created for Intelligent scenario &1 |
| 613 | Source DCL & is not active |
| 614 | Error occurred while adding object &1 type &2 to transport |
| 615 | Generation of &1 type &2 in progress |
| 616 | Couldn't lock &1 type &2 |
| 617 | &1 is not available for generation |
| 618 | Publishing not allowed due to system/ATO configuration combination |
| 619 | DCL object generated successfully |
| 620 | Error occurred in generation of intelligent scenario-related objects |
| 621 | Intelligent scenario &1 pk &2 is not ATO-enabled; please change to &3 |
| 622 | Training is already scheduled for this scenario version.Retry later. |
| 623 | |
| 624 | The intelligent scenario name or the development class was not supplied |
| 625 | Intelligent scenario has no CDS related objects attached |
| 626 | &1 is used by a non ISLM-generated object |
| 627 | Deletion not supported. &1 is being used by a DCL. |
| 628 | &1 type &2 was successfully deleted |
| 629 | An error occurred during the deletion of &1 object &2 |
| 630 | No classification of the object was found |
| 631 | An error occurred when adding object &1 to transport &2 |
| 632 | Intelligent Scenario draft is invalid, please recreate it. |
| 633 | &1 type &2 will be deleted |
| 634 | Function module &1 sy-subrc &2 |
| 635 | Errors occurred while checking the where-used list for the class of PS &1 |
| 636 | Errors occurred during the generated object check |
| 637 | Model name is too long. Please export model from PF again. |
| 638 | &1 type &2 was deleted previusly |
| 639 | Task type &1 is not supported for &2 and &3. |
| 640 | A ISLM task is required for the creation of engine tasks. |
| 641 | Error occurred while reading draft model. |
| 642 | The ISLM Task Processor requires a factory for task scheduling. |
| 643 | Error occurred during model draft validation. |
| 644 | Intelligent Scenario is in Draft state. |
| 645 | Model &1 is not in Draft state. Only Draft Models can be published. |
| 646 | &1 field &2 is a RAW datatype. This is not supported for &1 fields. |
| 647 | Draft models cannot query binding record count. |
| 648 | Invalid Intelligent Scenario as Associated object is missing. |
| 649 | |
| 650 | Invalid dataset |
| 651 | Errors found with dataset &1. |
| 652 | Data element &1 has not been released. |
| 653 | Deployment Version :&1 |
| 654 | Draft initial model and scenario must be in the same package to publish |
| 655 | Predictive scenario &1 not found. Check the name and try again. |
| 656 | GUID must be specified. |
| 657 | Check run table updated. |
| 658 | Check GUID &1 is updated. |
| 659 | Check run update failed. |
| 667 | Reason codes not supported in output configuration. |
| 668 | Negative numbers are not allowed for reason codes. |
| 669 | A maximum of &1 reason codes are allowed. |
| 670 | No apply view was found for the given intelligent scenario |
| 671 | Errors occured during the internal table creation |
| 673 | Error while reading feature toggle value. |
| 674 | Addition of additional info to intelligent scenario is not supported. |
| 675 | Additional info of type &1 is not supported. |
| 676 | Missing information for additional information of type &1. |
| 677 | For additional info of type &1, a maximum of &2 values are allowed. |
| 678 | For additional info of type &1, a maximum of 1 value is allowed. |
| 679 | The additional information key is invalid |
| 680 | The render type is invalid |
| 681 | Unable to add the key &1 |
| 682 | Unable to delete the key &1 |
| 683 | Unable to update the key &1 |
| 684 | Operation is not supported in the system |
| 685 | The URL is invalid |
| 686 | The additional information index is invalid |
| 687 | The Fiori ID &1 is invalid |
| 688 | Scope &1 is invalid |
| 700 | ATO object deletion is not supported |
| 701 | Model name must begin with ATO Prefix &1 |
| 720 | Client 000 is protected and may not be overwritten |
| 750 | Deactivating model version &1... |
| 751 | Model version &1 deactivated successfully |
| 840 | &1 >> Row: &4 Inc: &3 Prog: &2 |
| 841 | System error in class &1, method &2 |
| 850 | Job name &1, job count &2, scheduled successfully |
| 851 | Task scheduler was not able to update processed DATA |
| 852 | Task processing is supported only as background job |
| 853 | Another instance of job &1 is already running |
| 854 | Background job amount limit acquired, no task for process |
| 855 | Unable to acquire model for model version &1 |
| 856 | Task scheduled successfully |
| 857 | ID cannot be left blank. |
| 858 | Scenario Objects generation task created &1 |
| 859 | |
| 860 | |
| 861 | Prerequisite check class &1 for Intelligent Scenario &2 does not exist. |
| 862 | Prerequisite check class &1 for Intelligent Scenario &2 is not active. |
| 865 | Inference Triggered.. |
| 866 | Inference result was returned sucessfully. |
| 867 | Failed to retrieve inference result. |
| 868 | Assign a valid inference client that points to an active deployment. |
| 869 | For the Intelligent Scenario, no Active and Running Deployment are found. |
| 870 | No published Intelligent Scenario found for remote ML scenario. |
| 871 | The Connection name is invalid. |
| 872 | One Active Deployment is allowed per Intelligent Scenario. |
| 873 | A valid connection for the Intelligent Scenario is not found. |
| 874 | Please provide Model details |
| 875 | Please provide Parameters/Filters details |
| 876 | Provide the intelligent scenario name |
| 877 | Provide the intelligent scenario and parameter names |
| 878 | Intelligent Scenario Name or Parameter Name cannot be blank. |
| 879 | Intelligent Scenario name and Check Run can't be blank. |
| 880 | Prerequisite check job not configured.Contact your system administrator. |
| 881 | Error occurred while updating model. |
| 897 | Object &1 doesn't exist. |
| 898 | Unexpected error occurred, please contact system admin. |
| 899 | Method not implemented. |