CACS_STD - Higher Level Messages for Standard Contract

The following messages are stored in message class CACS_STD: Higher Level 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".
Message Nr
Message Text
001Cannot determine a system name
002Method CL_CACS_XH_ADMIN~CREATE cannot be executed without APPL
010*** 1-10 Reserved for System Messages
015Invalid call of method &1
016Error while generating data reference using RTTS
017Implementation of BAdI CACS_STDAGR_FACTORY contains errors
018No agreement assignment of contract &1 to &4 &3 exists
019Agreement assignment of contract &1 for &4 &3 was not activated
020Application &1 does not exist
021Enter at least one standard contract or a range
022Enter at least one contract type or a range
023Error while writing to database; changes are not saved
024&1 data record(s) modified with origin &2
030Error in SQL statement of search help
040Database accessing error
041Method &1: Reading of database table &2 returned no hits
042Method &1: Error while deleting database table &2
043Method &1: Error during MODIFY of database table &2
044Method &1: Error during dynamic SQL access of database table &2
100****** Version Management
101Version object has no inactive version
102Assign error (source field &1, field symbol &2)
103No valid version exists at time-spot &1 (tech. &2)
104Object does not exist on the database; no read generation is possible
105Error in versioning; note following messages
106Cannot resolve database table &1
107Error in SQL statement
108Database key is not filled
111No effectively valid version exists on date &1
112No effectively valid version at technical time-spot &1
120Error while assigning general type &1 to standard agreement
121Effective validity of agreement &1 of type &2 (&3) is too short
124Date &1 is not allowed for this process
130***** Text Class
131No key data
132Text does not exist on the database
133No control data found in table DD03L for text table &1
134Key for long text is too long
140*** Messages from Customizing
141No implementation exists for context &1
142No control data for standard contract exists for ICM application &1
143Cannot determine domain for table &1 field &2
144Cannot determine domain for data element &1
145No domain &1 exists
146Value &1 for domain &2 is not allowed
147Contract type &1 does not exist
148No agreement types are assigned to contract type &1 in application &2
149Agreement type &1 in application &2 is not assigned to contract type &3
150Agreement type &1 is not assigned to application &2
151No agreement types are assigned to application &1
152Choose a context
153No transport application exists for application &1
156No active version of contract &1 exist on database
200************* Facade
201Contract &1 already exists in application &2; it cannot be created again
202Cannot generate object for contract &1 in application &2
203Error in log; Processing was canceled
204Contract &1 does not exist in application &2; no read access possible
205Contract &1 (appl. &2) is not in buffer; Open in editing mode
206No application specified
207Choose a template
208Error while saving contract &1 (application &2)
209Error while activating contract &1 (application &2)
210Error while editing agreement assignment &1 (&2) in contract &3
211Error while editing descriptive text for contract &1
212Transferred version & is not valid
213Either the version is inactive or inactive subobjects exist
214Contract &1 (application &2) was activated
215Wildcards characters ( *, ? ) are not allowed
216You are not authorized to change standard contract &1
217Standard contract &1 does not exist
218Standard contract &1 does not have the required validity period
219Agreement &1/&2 does not have the required validity period
220Standard contract &1 (appl. &2) is locked (transport request &3)
221Error in data consistency
222Error while deleting ctr &1 (appl. &2); Note any subsequent messages
223Error while ending ctr &1 (applic. &2); Note any subsequent messages
224Standard contract &1 already exists; choose another ID
225Standard contract &1 in application &2 has no inactive parts
226Contract &1 (application &2) ends on &3
227Contract &1 (application &2) was deleted
228&1 is not a valid date
229No values for this selection in application &1
230You have no authorization for standard contract &1 (application &2)
231Authorization check was called with initial parameters
232You have no authorization for std contracts of contract type &1 (appl.&2)
233You have no authorization for area &1 of standard contracts (appl. &2)
234User in front end &1 is different from user in back end &2
235The applications defined for the user are inconsistent
236Standard contracts cannot be changed in system &1
237Rule characteristics cannot be changed in system &1
238Error while checking system settings in the authorization check
239No application is defined for user &
240Agreement assignment &1 &2 was deleted
241Cannot delete agreement assignment &1 &2
242Agreement type &1 is not allowed for method &2
243Error in Customizing (table &1, application &2)
244Rule characteristics for contract &1 cannot be edited in this system (&2)
245Cannot read data for standard contract &1 (application &2)
246No agreement is assigned to agreement type &1
247Select a standard contract
248Standard contract &1 (application &2) was imported
249Contract &1 (application &2) was exported
250Unexpected status of RFC layer: Object &1 in &2
251Effective internal &1 - &2 is not allowed
252Error while changing rule characteristics
253No rule characteristics exist in Customizing for agreement rule &1
254Effective dates of contract &1 (application &2) were extended up to &3
255The system cannot continue the process
256Inactive aspects of contract &1 (application &2) were deleted
257No authorization for &3 standard contract &1 (application &2)
258Choose the change interval within the contract validity
259Contract has inactive aspects: Only change interval &1 to &2 is possible
260Contract &1 is (partially) inactive; no termination is possible
261Contract &1 contains functional inconsistencies; it cannot be activated
262Agreement &1 (type &2: &3) is incorrect; no rule charas can be edited
263You have not changed any values
264Cannot determine application for user &
265No event was entered for agreement type &1 (application &2)
266Contract is already valid at time-spot &1; moving forward is not possible
267Contract &1 is (partially) inactive; moving forward is not possible
268Error while moving forward contract &1; changes are not activated
269Extended date &1 is too short: extension of contract &2 is not possible
270Contract &1 is (partially) inactive; it cannot be extended
271Error while extending contract &1; changes were not activated
272Contract &1 (application &2) was moved forward to &3
273Error while casting of exception &1
274Contract &1 (application &2) was saved
275Contract starts &1; ending contract on &2 is not possible
276Contract end &1; ending contract on &2 is not possible
277Entries exist, as parked
278Contract &1 (application &2) was saved as parked version
279More than one calculation tool exists in same agreement
280No condition records have been maintained
281No entry point determined for determination
282Cannot read determination mode
283Sample contract &1 has no remuneration type
284No LOS tool found
285More than one decision for remuneration type table &1
290Missing authorization for user &1 for RFC (Module: &2)
Privacy Policy