| CABALOCO011 |
Document number missing |
| CABALOCO012 |
Original document & not found in reference table |
| CABALOCO013 |
Cannot cancel document & |
| CABALOCO014 |
Original document with counter & not found in interface table for & |
| CABALOCO015 |
System error: & & & & |
| CABALOCO016 |
An error occurred when determining the account assignment |
| CABALOCO017 |
It is not possible to enter a CO account assignment |
| CABALOCO018 |
It is not possible to enter a statistical key figure |
| CABA_EXTERN_HR000 |
A currency could not be determined for personnel no. & on & |
| CABA_EXTERN_HR001 |
Wage type & does not exist in table T511 |
| CABA_EXTERN_HR002 |
No authorization for wage type & on & |
| CABA_EXTERN_HR003 |
No infotype 0001 for personnel number & on & |
| CABA_EXTERN_HR004 |
Error when reading T001P |
| CABA_EXTERN_HR005 |
Number of hours entered & too great |
| CABA_EXTERN_HR006 |
Wage type & is not permitted in the time sheet |
| CABA_EXTERN_HR007 |
No entry in table & for & |
| CABA_EXTERN_HR008 |
Fund Accounting not supported in 4.6C |
| CABA_EXTERN_HR009 |
Personnel number &1 does not exist in the HR system |
| CABA_EXTERN_HR010 |
No infotype &1 exists for personnel number &2 on &3 |
| CABA_EXTERN_HR011 |
No short text found |
| CABA_EXTERN_HR012 |
No value found for search help |
| CABA_EXTERN_HR013 |
Search help is not supported for this field |
| CACSAC000 |
**** Read Modules: Commission Documents ******************************* |
| CACSAC001 |
No commission document found for this selection |
| CACSAC002 |
Unable to enhance &1; no document information exists |
| CACSAC003 |
Error while assigning to field symbol |
| CACSAC004 |
Combining data did not succeed |
| CACSAC005 |
Read from archive |
| CACSAC099 |
Document &1 is currently locked by user &2 |
| CACSAC100 |
**** Messages for document posting **** |
| CACSAC1001 |
Error while creating fulfillment level periods (Seq &1, Item &2) |
| CACSAC1002 |
No function module exists to determine release periods; release type &1 |
| CACSAC1003 |
Start determination of release periods; release type &1 with FM &2 |
| CACSAC1004 |
No function module exists to create the release periods; release type &1 |
| CACSAC1005 |
Start creation of release periods; release type &1 with FM &2 |
| CACSAC1006 |
Actual commission for remuneration &1 requires settlement scheduling |
| CACSAC1007 |
No function module exists to enter fulfillment levels; release type &1 |
| CACSAC1008 |
Error while creating fulfillment level periods for item &3 |
| CACSAC1009 |
Error while creating fulfillment level for item &3 |
| CACSAC101 |
The document posting is locked by another process |
| CACSAC1010 |
Error while creating fulfillment level |
| CACSAC1011 |
Release rule &1 with release type &2 found for remuneration line &3 |
| CACSAC1012 |
System cannot read fulfillment level of GUID &1 |
| CACSAC1013 |
Threshold value reached for settlement schedule item with GUID &1 |
| CACSAC1014 |
Threshold value reached for settlement schedule item with GUID &1 |
| CACSAC1015 |
Error in transfer of actual commn notification to log of calling program |
| CACSAC1016 |
Error while determining release rules for commission contract |
| CACSAC1017 |
Deletion of fulfillment level for stt.schedule item(s) &1/&2 failed |
| CACSAC1018 |
The result of release rule determination is invalid |
| CACSAC1019 |
It is not possible to assign fulfillment lvl intervals to stt.sched.items |
| CACSAC102 |
Update mode V3: Schedule CACS_TRIGGER_V3 report daily |
| CACSAC1020 |
Object-dependent parameters for release type &1 are initial |
| CACSAC1021 |
Function module & was called incorrectly |
| CACSAC1022 |
Transfer of fulfillment periods for remuneration line &1 not possible |
| CACSAC1023 |
Incorrect object type class &1 was transferred - &2 expected |
| CACSAC1024 |
Incorrect tool &1 was transferred - &2 expected |
| CACSAC103 |
Update mode V3 deactivated: CACS_TRIGGER_V3 report no longer necessary |
| CACSAC104 |
Technical error: incorrect call of module CACS00_DOC_POST2 |
| CACSAC1104 |
Change of settlement schedule item failed |
| CACSAC200 |
**********Credentialing Messages*********************** |
| CACSAC201 |
Field FLG_BLOCKED_CRD is missing in _S_DOCREM |
| CACSACTCMD001 |
Settlement release; agreement(s) valid longer than commission contract |
| CACSACTCMD002 |
Time intervals for release rules &1 and &2 must not overlap |
| CACSACTCMD003 |
Start of release rule &1 must not be before &2 |
| CACSACTCMD004 |
Stt. release agrmnt with RELAGR_ID &1 and RELRU_ID &2 does not exist |
| CACSACTCMD005 |
End of release rule &1 must not be after &2 |
| CACSACTCMD006 |
Enter a number for the release agreement |
| CACSACTCMD007 |
Release rule & not permitted |
| CACSACTCMD008 |
Enter a release rule for settlement release agreement & |
| CACSACTCMD009 |
Release rule &1 is already assigned to commission contract &2 |
| CACSACTCMD010 |
Release agreement no. &1 already assigned to commission contract &2 |
| CACSACTCMD011 |
Incorrect period management SY-SUBRC & |
| CACSACTCMD013 |
Enter a numerical value for the priority |
| CACSACTCMD014 |
Function module & was called incorrectly |
| CACSAPPK000 |
&1 &2 &3 &4 |
| CACSAPPK001 |
No tables found for application &1 |
| CACSAPPK002 |
Cross-client table &1 for application &2 is not empty |
| CACSAPPK003 |
Client-specific table &1 is not empty for application &2 |
| CACSAPPK004 |
Master data table &1 is not empty for application &2 |
| CACSAPPK005 |
Transaction data table &1 is not empty for application &2 |
| CACSAPPK006 |
Database table &1 does not exist |
| CACSAPPK007 |
No application field exists for application-dependent table &1 |
| CACSAPPK008 |
RFC destination client &1 is different from selected client &2 |
| CACSAPPK009 |
RFC destination Sysid &1 is different from selected Sysid &2 |
| CACSAPPK010 |
Error while generating application &2 in table &1 |
| CACSAPPK011 |
Source application is identical to target application &1 |
| CACSAPPK012 |
Application cloner: process was started |
| CACSAPPK013 |
Cloning source application &1 to target application &2 |
| CACSAPPK014 |
P R O D U C T I V E R U N |
| CACSAPPK015 |
T E S T R U N |
| CACSAPPK016 |
Strict consistency - tables must be identical |
| CACSAPPK017 |
Weak consistency - "Move-corresponding" is used |
| CACSAPPK018 |
Source application is read locally from client &1 |
| CACSAPPK019 |
Source application is read from remote system &1 client &2 |
| CACSAPPK020 |
Target application definition is edited locally in client &1 |
| CACSAPPK021 |
Target application definition is edited in remote system &1 in client &2 |
| CACSAPPK022 |
Target application may be used locally in client &1 |
| CACSAPPK023 |
Cloning cross-client data |
| CACSAPPK024 |
Checking that application data is empty |
| CACSAPPK025 |
Checking that client-dependent data is empty |