CACS_STDCTR - Standard contract: Messages for standard contract
The following messages are stored in message class CACS_STDCTR: Standard contract: Messages for standard contract.
It is part of development package CACSC8 in software component ICM. This development package consists of objects that can be grouped under "ICM: Standard Contract: Global Types".
It is part of development package CACSC8 in software component ICM. This development package consists of objects that can be grouped under "ICM: Standard Contract: Global Types".
Message Nr ▲ | Message Text |
|---|---|
| 000 | No standard contract &1 exists at time-spot &2 (technical &3) |
| 001 | Agreement assignment of contract &1 to &4 &3 contains errors |
| 002 | No text found in languague &2 for standard contract &1 |
| 003 | Agreement type &1(&2) is not allowed |
| 004 | Agreement type &1(&2) only allows one agreement for each std contract |
| 005 | Agreement &1/&3(&2) is not assigned to standard contract &4 |
| 006 | Cannot determine system parameters |
| 007 | Error in versioning while loading header data (BD &1, TD &2) |
| 008 | Cannot instantiate assignment of agreement &1 of type &2 |
| 009 | Assignment of agreement type &1 cannot be instantiated |
| 010 | Configuration has errors; Check following messages |
| 011 | Contract type &1 is not allowed |
| 012 | Effective interval (start &1, end &2) is invalid |
| 013 | Error in BAdI implementation &1 for application &2 |
| 014 | Error in BAdI enhancement &1 for consistency check of application &2 |
| 015 | Invalid application &1 |
| 016 | Application cannot be changed |
| 017 | ID of contract must not be changed |
| 018 | Contract type must not be changed |
| 019 | Origin of contract must not be changed |
| 020 | Error in BAdI enhancement &1 of change level for application &2 |
| 021 | ID must not be blank |
| 022 | Contract type must not be blank |
| 023 | Enter a description |
| 024 | Standard contract &1 does not exist in application &2 |
| 025 | Error in assignment of agreements (type &1); Note following messages |
| 026 | Error while activating contract header for contract &1, application &2 |
| 027 | Error while deleting contract &1 of application &2 |
| 028 | Error while deleting agreement assignment &1 type &2 in contract &3 |
| 029 | Agreement type must not be initial |
| 030 | Change to standard contract &1, appl. &2 is not allowed in this system |
| 031 | Effective interval &1-&2 is not within the permitted interval |
| 032 | Agreement &1 (type &2: &3) must not be changed |
| 033 | Assigned standard contract ID &1 violates namespace convention |
| 034 | Error while ending agreement assignment &1 type &2 in contract &3 |
| 035 | Error while ending contract &1 of application &2 |
| 036 | Error while ending agreement assignment &1 type &2 in contract &3 |
| 037 | Error while resetting activation of contract &1, application &2 (header) |
| 038 | Error while resetting activation (contract &1, appl. &2), agreement &3 |
| 039 | Cannot add universal agreement &1 &2 type &3 &4 |
| 040 | Error while writing to database: Appl. &1 contract &2 to &3 |
| 041 | Error while writing to database: Appl. &1 contract &2 (subobject) |
| 042 | Error while writing assignment (type &1, ID &2) for contract &3 |
| 043 | Error while writing assignment (contract &1, type &2, ID &3) (rule) |
| 044 | Error while deleting assignment (type &1, ID &2) contract &3 (version 0) |
| 045 | Error while deleting contract &1, appl. &2 to &3 (version zero) |
| 046 | Error on the database: read subsequent messages |
| 047 | Object cannot be loaded at time-spot &1 / &2 |
| 048 | Effective interval &1-&2 for agreement &3 (type &4) is not allowed |
| 049 | Error while reading deleted agreement assignments |
| 050 | Log error; contact your system administrator |
| 051 | Only one agreement is allowed for each contract for agreement type &1(&2) |
| 052 | At least one agreement is required for agreement type &1(&2) |
| 053 | Value &1 is not allowed for field &2 |
| 054 | At least one agreement is recommended for agreement type &1(&2) |
| 055 | No remuneration agreement has been assigned to liability agreement &1 |
| 056 | Additional commission case agreement is missing for target agreement &1 |
| 057 | Standard contract &1 (appl. &2) is still in use |
| 058 | Termination date is empty |
| 059 | No settlement agreement was assigned |
| 060 | Template contract &1 is not available at time-spot &2 / &3 in appl. &4 |
| 061 | Contract &1 in application &2 cannot be instantiated |
| 062 | Required agreement type &1 (&2) is not assigned continuously |
| 063 | No stt.scheduling agreement exists for settlement release agreement &1 |
| 064 | Agreement type &1(&2) is not (completely) covered by agr.type &3(&4) |
| 065 | Tgt agrmt &1 is not completely covered by addit.comn case agreement |
| 066 | Stt.release agreement &1 is not completely covered by stt.sched.agrmt |
| 067 | Liability agreement &1 is not completely covered by remunerat.agreement |
| 068 | Move-forward date is empty |
| 069 | Error while moving forward contract &1 in application &2 |
| 070 | Agrmnt type &1(&2) of universal agrmnt &3 is not allowed for ctr.type &4 |
| 071 | Error while activating contract &1, application &2 |
| 072 | Error while moving forward agreement assignment &1 type &2 in ctrct &3 |
| 073 | Error while extending agreement assignment &1 type &2 in contract &3 |
| 074 | Extention date is initial |
| 075 | Error while extending contract &1 of application &2 |
| 076 | Recommended agreement type &1 (&2) was not completely assigned |
| 077 | Error while adding time slice to agrmnt assgnmnt &1 type &2 contract &3 |
| 078 | Agreement &1 (type &2) already assigned from &3 to &4 |
| 079 | Agreement &1 in interval &2 to &3 has multiple assignments |
| 080 | **** Transport |
| 081 | Error while generating SD transport data for agreement &1 |
| 101 | Error in rule characteristics of agreement &1 |
| 102 | It is not possible to cut a time slice |
| 850 | ******* For Migration/XPRA *** |
| 851 | No entries in client table of ICM |
| 852 | No contract types defined |
| 853 | No agreement types exist |
| 854 | No standard contracts exist |
| 855 | No agreement assignments exist |
| 856 | Error while writing to table &1 |
| 857 | No application exists |
| 858 | XPRA '&1' was started at '&2 &3' |
| 859 | XPRA '&1' was ended successfully on '&2 &3' |
| 860 | Version zero is not allowed in APPL &1 standard contract &2 |
| 861 | Effective start date APPL &1 in contract &2, version &3 is not allowed |
| 862 | Effective end date APPL &1 in contract &2, version &3 is not allowed |
| 863 | Technical start date APPL &1 in contract &2, version &3 is not allowed |
| 864 | Technical end date APPL &1 in contract &2, version &3 is not allowed |
| 865 | Cannot determine system parameters |