SOAP_CFG_CC - SOAP Configuration Consistency Checks
The following messages are stored in message class SOAP_CFG_CC: SOAP Configuration Consistency Checks.
It is part of development package SOAP_CONFIG_CC in software component BC-ESI-WS-ABA-CFG. This development package consists of objects that can be grouped under "SOAP Configuration Consistency Check".
It is part of development package SOAP_CONFIG_CC in software component BC-ESI-WS-ABA-CFG. This development package consists of objects that can be grouped under "SOAP Configuration Consistency Check".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1&2&3&4 |
| 001 | Multiple Active Simplified Configurations for Service Definition &1 (&2) |
| 002 | Configuration &1 refers to missing or inactive Service Definition &2 |
| 003 | Configuration &1 not found in header table (SRT_CFG_DIR) |
| 004 | Not implemented: &1 |
| 005 | Configuration &1 refers to missing or inactive Proxy &2 |
| 006 | Configuration name &1 is not unique |
| 007 | Configuration key &1 is not unique |
| 008 | Configuration key &1 has no binding |
| 009 | Binding &1 refers to non-existing configuration &2 |
| 010 | Binding &1 is used by multiple configurations (&2) |
| 011 | Binding &1 has no value for field URL in table SRT_CFG_SRV_ASGN |
| 012 | ICF node &1 missing for binding &2 |
| 013 | Simplified configuration &1 has unexpected type (&2) |
| 014 | Simplified configuration &1 is incomplete (no details) |
| 015 | No binding exist for ICF path &1 |
| 016 | Invalid binding data for &1 of method '&2', actual '&3' expected '&4' |
| 017 | Could not get ICF node for URL &1: &2 |
| 018 | Invalid configuration key &1 |
| 019 | Method &1(&2) missing in configuration &3, binding &4 |
| 020 | Unknown method &1(&2) in configuration &3, binding &4 |
| 021 | Binding has no client assignment |
| 022 | Binding &1 has wrong value for '&2', actual '&3' expected '&4' |
| 023 | |
| 030 | ICF Path is used |
| 031 | Simplified Configuration is consistent |
| 032 | Configuration Key is valid |
| 033 | Configuration Key is unique |
| 034 | Configuration has at least one binding |
| 035 | Only one Simplified Configuration for each Service Definition |
| 036 | Configuration refers to existing Design-Time Object |
| 037 | Binding has ICF node |
| 038 | Binding is consistent with Design-Time Object |
| 039 | Binding has valid Configuration |
| 040 | Binding has unique Configuration |
| 041 | Binding has Client Assignment |
| 042 | Deletion failed: &1 is not a Web Service path. |
| 043 | Binding has wrong URL '&3' expected '&4' |
| 044 | Binding URL is not unique (&3) expected &4. |
| 050 | Service Group configuration is valid |
| 051 | Invalid Service Group Configuration &1:&2, no entry in header table |
| 052 | Service Group Configuration &1:&2 refers to not existing Service Group &1 |
| 053 | Service Group Configuration exists in design-time |
| 054 | Service Group Configuration consistent with design-time |
| 055 | Service Group Conf. &1:&2 consumer mismatch (config: &3, design-time: &4) |
| 056 | Service Group refers to existing Logical Ports only |
| 057 | Service Group Conf. &1:&2 refers to non-existing LP &3 of consumer &4 |
| 058 | Consumer Proxy of Service Group has Logical Port |
| 059 | Service Group Conf. &1:&2: No Logical Port for consumer &3 |
| 060 | Service Group &1 is configured multiple times: &2 |
| 061 | Service Group is configured only once |
| 062 | Service Group Conf. &1:&2 refers to non-existing Business Application ID |
| 063 | Service Group Conf. &1:&2 refers to initial Business Application ID |
| 064 | Service Group Conf. &1:&2 refers to multiple Business Application IDs |
| 065 | Service Group refers to existing Business Application ID only |
| 066 | Service Group Conf. &1:&2 refers to invalid Business Application ID |