Id | Title |
---|---|
RSSDK025 | The InfoSource must be saved before you can continue |
RSSDK029 | No InfoObjects in the InfoSource, Mapping not possible |
RSSDK030 | Extraction of the relevant RFC destinations... |
RSSDK031 | Extraction of existing UD Connect systems... |
RSSDK032 | Extraction of existing UD Connect data sources... |
RSSDK033 | Extraction of field list for selected UD Connect source objects... |
RSSDK034 | Select an unused row in the mapping table |
RSSDK035 | Select a row in the table for UDC source object elements |
RSSDK036 | You have not selected any rows |
RSSDK037 | This row is already assigned |
RSSDK040 | CleanUp is running... |
RSSDK041 | Structure & is being created... |
RSSDK042 | Function module & is being generated... |
RSSDK043 | Creating BI DataSource &... |
RSSDK044 | The required extraction elements were created successfully |
RSSDK049 | An error occurred during extraction of InfoObject information |
RSSDK050 | An error occurred in step & during cleanup |
RSSDK051 | An error occurred in step & during creation of the structure |
RSSDK052 | An error occurred in step & during generation of the function module |
RSSDK053 | An error occurred in step &2 during creation of DataSource &1 |
RSSDK054 | An error occurred during replication of DataSource & |
RSSDK055 | An error occurred during creation of extraction elements |
RSSDK056 | InfoObject & cannot be used for the extraction |
RSSDK057 | Source system assignment for BI Myself source system already exists |
RSSDK058 | Errors occurred during extraction of the existing UDC Connect sources: & |
RSSDK059 | Errors occurred during extraction of existing UD Connect source objects:& |
RSSDK060 | Errors occurred during extr. of existing element list of UDC source obj:& |
RSSDK061 | Problem while using BI Myself source system |
RSSDK062 | A problem occurred while preparing BW InfoSource step & |
RSSDK063 | A problem occurred while assigning the DataSource to the InfoSource |
RSSDK064 | A problem occurred when saving the assignment of DataSource to InfoSource |
RSSDK065 | InfoObject data type & is incompatible with UDS element type & |
RSSDK066 | Function group & for local generation does not exist |
RSSDK067 | UDC element & is already assigned to InfoObject & |
RSSDK100 | UDC adapter problem: connection area |
RSSDK110 | UDC adapter problem: metadata area |
RSSDK120 | UDC adapter problem: request execution area |
RSSDK130 | UDC adapter problem: result processing area |
RSSDPR_MESSAGES000 | An SDPR exception has occurred. No further details are available |
RSSDPR_MESSAGES001 | The value '&1' of parameter '&2' cannot be interpreted as an integer |
RSSDPR_MESSAGES002 | The parameter type for '&1' is '&2' does not match required type '&3' |
RSSDPR_MESSAGES003 | There is no existing entry for key '&1' in table '&2' |
RSSDPR_MESSAGES004 | Percentage value &3 for metric ID &1, delivery type &2 is out of range &4 |
RSSDPR_MESSAGES005 | Failed to access structure. Component with name '&2' does not exist. |
RSSDPR_MESSAGES006 | The algorithm class for metric ID '&1' does not exist |
RSSDPR_MESSAGES007 | The metric category '&1' does not exist |
RSSDPR_MESSAGES008 | No calculation rule for supplier &1, ship to &2, del. type &3, metric &4 |
RSSDPR_MESSAGES009 | No weight factor found for metr. ID '&1', del. type '&2', OT bucket '&3' |
RSSDPR_MESSAGES010 | Calculation error in the algorithm with metric ID: &1 |
RSSDPR_MESSAGES011 | Collector ODS key field '&1' is NOT filled with data |
RSSDPR_MESSAGES012 | No score found for metric ID '&1', key value '&2' in table '&3' |
RSSDPR_MESSAGES013 | Score calculatn error for supplier &1, ship-to:&2, del.type &3, metric:&4 |
RSSDPR_MESSAGES014 | No score in cache for supplier &1, ship-to: &2, del.type &3, metric &4 |
RSSDPR_MESSAGES015 | Failed to convert calendar month value '&1' to a fiscal period. |
RSSDPR_MESSAGES016 | Failed to convert calendar week value '&1' to a fiscal period. |
RSSDPR_MESSAGES017 | Failed to convert fiscal period value '&1' to a calendar week. |
RSSDPR_MESSAGES018 | Failed to convert fiscal period value '&1' to a calendar month. |
RSSDPR_MESSAGES019 | Calmonth and Calweek are both &1. |
RSSDPR_MESSAGES020 | The algorithm for metric ID '&1' is not invoked due to no lookup table |
RSSDPR_MESSAGES021 | Percentage value &3 for metric ID &1, del. type &2 is not in lookup tbl |
RSSDPR_MESSAGES022 | No calc-No valid data, no def. for mtc:&4, supl &1, ship-to &2, deltyp &3 |
RSSDPR_MESSAGES023 | No such combination for metric ID '&1' and delivery type '&2' |
RSSDPR_MESSAGES024 | Validation error in the algorithm with metric ID '&1' |
RSSDPR_MESSAGES025 | Error lines val. &3 for metric ID &1, del. type &2 is out of range &4 |
RSSDPR_MESSAGES026 | Unhandled error occurred in update rule &1 |
RSSDPR_MESSAGES028 | Table &1 customizing error - all weighting factors for denominator are 0 |
RSSDPR_MESSAGES029 | &1 &2 descriptor is not properly defined, score update aborted |
RSSDPR_MESSAGES030 | InfoObject 0APO_LOCNO does not exist in the system |
RSSDPR_MESSAGES031 | Invalid selection passed to function module RSSEM_CHA_VALUES_GET |
RSSDPR_MESSAGES032 | Unknown error when calling function module RSSEM_CHA_VALUES_GET |
RSSDPR_MESSAGES033 | Unable to find the APO Location in system (see appl.log for details) |
RSSDPR_MESSAGES034 | Wrong parameters passed (see application log for details) |
RSSDPR_MESSAGES035 | The struc field: &1 cannot be assigned to a variable of matching type &2 |
RSSDPR_MESSAGES036 | Value of field '&2' in database table: '&1' is out of domain '&3'. |
RSSDPR_MESSAGES037 | Return value of method DATA_EXIST for metric '&1' is not supported. |
RSSDPR_MESSAGES038 | Supplier ID '&1' with a non Default Ship-To Loc ID is not supported. |
RSSDPR_MESSAGES039 | Field ID '&1' is invalid in '&2'. |
RSSDPR_MESSAGES040 | ASN=&1,item=&2 |
RSSDPR_MESSAGES041 | Pur.Ord.=&1,item=&2,line=&3 |
RSSDPR_MESSAGES042 | Rel.Sch.=&1,item=&2,line=&3 |
RSSDPR_MESSAGES043 | Alert nr=&1,type=&2 |
RSSDPR_MESSAGES044 | Document &1 is inconsistent, because value for field &2 is missing |
RSSDPR_MESSAGES045 | Document &1 is inconsistent, because field &2 has invalid value &3 |
RSSDPR_MESSAGES046 | Document &1 is inconsistent, because field &2 is missing |
RSSDPR_MESSAGES047 | ConfID=&1 |
RSSEM001 | Program is inconsistent -> see long text |
RSSEM002 | The document could not be deleted |
RSSEM003 | The document could not be updated |
RSSEM004 | No URL document could be created |
RSSEM050 | ----------------- Master Data / Hierarchy Access ------------------------ |
RSSEM051 | Remote InfoObject &1 does not have a usable hierarchy DataSource |
RSSEM052 | Remote InfoObject &1 does not have a unique hierarchy DataSource |
RSSEM053 | RFC destination for logical system &1 could not be determined |
RSSEM054 | Error during access to hierarchies of &1 (DataSource &2/&3) |
RSSEM055 | System error during access to DataSource &1 in System &2 |
RSSEM056 | Communication error during access to DataSource &1 in System &2 |
RSSEM057 | Messages during access to DataSouce &1 in system &2: |
RSSEM058 | Error while executing transfer rules (&1, DataSource &2/&3) |
RSSEM059 | Transfer rule for hierarchy for &1 is not defined/not supported |
RSSEM060 | InfoObject &1 is not type-compatible with field &2 |