Id | Title |
---|---|
CACSVERSMSG405 | Dynamic sorting of table &1 failed |
CACSVERSMSG406 | Key field &1 is initial; selection condition is imcomplete |
CACSWIZARD300 | No regions allowed due to the selection made in previous steps |
CACSWIZARD400 | No processes allowed due to the selection made in previous steps |
CACSY001 | &1: &2 entries found in table &3 |
CACSY002 | Selection option: &1 |
CACSY003 | Sign: &1, option: &2, lower limit: &3, upper limit: &4 |
CACSY004 | You have not selected any restricting selection options |
CACSY005 | &1 data record(s) have been transferred to totals table &2 |
CACSY006 | &1 data records have been deleted from totals table &2 |
CACSY007 | The program is finished - see the log |
CACSY008 | The following restricting selection options were selected |
CACSY009 | Select a package size that is greater than zero (mass processing) |
CACSY010 | The namespace has been converted successfully |
CACSY011 | The new namespace was not changed (transport) |
CACSY012 | You cannot save a rule set without a name |
CACSY022 | &1: &2 entries repaired/to be repaired in &3 (&4) |
CACSY100 | *** Messages for re-generation of totals table *** |
CACSY101 | &1 is not a totals table from application &2 |
CACSY102 | Choose a commission application then choose ENTER |
CACSY103 | Check the application |
CACSY104 | Outstanding update runs for totals tables are now being started |
CACSY105 | Restart the report later |
CACSY106 | Delete the cancelled update modules using transation SM13 |
CACSY107 | Totals table generation program &1 was generated |
CACSY108 | Unknown serious error type in totals table! Contact SAP |
CACSY200 | Messages for XPRAS ****************************************************** |
CACSY201 | Table &1: Contents successfully deleted |
CACSY202 | Table &1: &2 entries were not inserted as they already exist |
CACSY203 | Table &1: Contents successfully converted |
CACSY204 | Contract version &1 not converted |
CACSY205 | Table &1: The contents were not completely converted |
CACSY206 | Table &1: Type &2 cannot be assigned to a mapping event |
CACSY207 | Version &1 not converted |
CACSY208 | Backup tables filled; no rerun of program '&1' possible |
CACSY209 | Error while creating backup table '&1'; conversion canceled |
CACSY210 | Conversion of tables '&1' '&2' is canceled |
CACSY211 | Following clients/applications were converted: |
CACSY212 | Client '&1' application: '&2' |
CACSY220 | No entry found in TCACS_APPLCUST for transaction &1 |
CACSY222 | No entry found in TCACS_APPLCUST for transaction &1 |
CACSY300 | Table & does not exist |
CACSY301 | Analyze table & |
CACSY302 | Total number of agreements with numerical ID: & |
CACSY303 | No contradictory table entries |
CACSY304 | Contradictory table entries |
CACSY305 | Related table & |
CACSY306 | Key ID: & |
CACSY307 | Set up & |
CACSY308 | STCAGR_ID ending in & |
CACSY309 | Total number of combination types with numerical ID: & |
CACSY310 | COMBTP_ID ending in & |
CACSY311 | SRCH_ID ending in & |
CACSY312 | & records with value "000000000000" instead of blank; check Customizing |
CACS_2A000 | &1 &2 &3 &4 |
CACS_2A001 | Error while transferring message to caller's log |
CACS_2A002 | Function module &1 was called incorrectly |
CACS_2A003 | Logical service &3 (for OTC &1 and method &2) is not RFC-enabled |
CACS_2A004 | Transfer of fulfillment periods for remuneration line &1 not possible |
CACS_2A005 | An error has occurred while posting release types |
CACS_2A006 | LOS function &1 for object type &2 and object ID &3 found (method &4) |
CACS_2A007 | An error has occurred while deleting release types |
CACS_2A008 | Buffers do not match |
CACS_2A009 | Error in buffer administration for settlement schedule numbers |
CACS_2A010 | Object-dependent parameters for release type &1 are initial |
CACS_2A011 | An error has occurred while processing GUID &1 |
CACS_2A012 | Error while creating fulfillment level for item &3 |
CACS_2A013 | System cannot read fulfillment level of GUID &1 |
CACS_2A800 | XPRA '&1' was started on '&2 &3' |
CACS_2A801 | &1 line(s) in table &2 and client &3 are not converted |
CACS_2A802 | XPRA '&1' was ended successfully on '&2 &3' |
CACS_2A803 | Error in database operation |
CACS_2A804 | No settlement schedule line found for FFL-Guid &1 (client &2) |
CACS_2A805 | Cannot determine a tool for application &1 OTC &2 and Obj.ID &3 |
CACS_71000 | &1 &2 &3 &4 |
CACS_71001 | Function module &1 was incorrectly called |
CACS_71002 | Error while creating fulfillment level |
CACS_71003 | Deletion of fulfillment level for stt.schedule item(s) &1/&2 failed |
CACS_71004 | Error while creating fulfillment level periods (Seq &1, Item &2) |
CACS_71005 | It is not possible to assign fulfillment lvl intervals to stt.sched.items |
CACS_71006 | Object-dependent parameters for release type &1 are initial |
CACS_71007 | No commission contract partner is assigned to commission contract &1 |
CACS_71008 | Incorrect object type class &1 was transferred - &2 expected |
CACS_71009 | Incorrect tool &1 was transferred - &2 expected |
CACS_71010 | Selection criteria must contain a contract number |
CACS_71011 | Error calling function module &1 |
CACS_71012 | Selection criterion for contract number must NOT be initial |
CACS_71013 | An error has occurred while generating program &1 |
CACS_71014 | Database operation on table &1 failed |
CACS_71015 | Credentialing for participation &1 failed |
CACS_71016 | Credentialing was switched off |
CACS_71017 | Credentials check for remuneration line &1, item &2 was successful |
CACS_71018 | Credentials check for document type &1 failed |
CACS_71019 | Error while creating an application log |
CACS_71020 | Error while saving application log |
CACS_71021 | Credentials check for remuneration line &1, item &2 failed |
CACS_71022 | Fatal error while determining credential |
CACS_71023 | Fatal error while determining credentialing application |
CACS_71024 | &1 |
CACS_71025 | Insufficient data for credentials check |