FAGL_VALIDATION -
The following messages are stored in message class FAGL_VALIDATION: .
It is part of development package FAGL_POSTING_SERV_EHP3 in software component FI-GL-GL-A. This development package consists of objects that can be grouped under "Services for Posting FI Documents (EhP3)".
It is part of development package FAGL_POSTING_SERV_EHP3 in software component FI-GL-GL-A. This development package consists of objects that can be grouped under "Services for Posting FI Documents (EhP3)".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Test run; no changes made to the database |
| 001 | Enter &1 as the source field or define a condition for &2 |
| 002 | Groups are not permitted as conditions |
| 003 | Groups of any kind are not permitted as target fields |
| 004 | Field &1 is added automatically when set &2 is used |
| 005 | When you enter a group, leave the group content fields empty |
| 006 | An entry in this field is mandatory if you enter a group (&1) |
| 007 | Record overlaps with a record that already exists in the database (&1) |
| 008 | Date overlaps with a lock set by user &1 on &2 at &3 |
| 009 | Inconsistencies found in locks on derivation tables (rules) |
| 010 | The entire record is empty; enter data |
| 011 | &1 is not a valid entry |
| 012 | No authorization for rule of strategy &1, activity &2, auth. object &3 |
| 013 | No strategy found (company code &1, ledger group &2) |
| 014 | Validation is not active for company code &1 |
| 015 | Save the validation strategy first |
| 016 | Validation strategy &1 contains validation rules |
| 017 | Validation strategy &1 (class &2,subclass &3,strategy &4) does not exist |
| 018 | Validation strategy &1 is assigned to company code &2 |
| 019 | Validation strategy &1 is assigned to ledger group &3 (company code &2) |
| 020 | First save the new validation strategy |
| 030 | Invalid account assignment combination in document/item &2; see long text |
| 031 | Error in validation of account assignment combinations |
| 298 | Groups are not permitted as conditions |
| 300 | Field &1 is added automatically when set &2 is used |
| 301 | Enter &1 as the source field or define a condition for &2 |
| 304 | Groups of any kind are not permitted as target fields |
| 305 | Your lock overlaps with the lock set by user &1 on &2 at &3 |
| 306 | &1 is not a valid entry |
| 307 | Controlling area or company code are mandatory with certain groups |
| 308 | Inconsistencies found in locks on derivation tables (rules) |
| 309 | Enter an area for the data selection; placeholders are permitted |
| 310 | Date overlaps with a lock set by user &1 on &2 at &3 |
| 311 | &1 records found with empty target fields |
| 312 | Correct the overlaps between the target fields |
| 313 | When you enter a group, leave the group content fields empty |
| 314 | The entire record is empty; enter data |
| 315 | Record overlaps with a record that already exists in the database (&1) |
| 316 | Setting lock for group &1 failed (database table &2) |
| 317 | Group is locked by user &1 since &2, &3 |
| 318 | Some records were changed; changed records cannot be edited |
| 319 | Deletion of data contained failed; lock is not removed |
| 320 | An entry in this field is mandatory if you enter a group (&1) |
| 330 | Changed: &1 |
| 331 | Deleted: &1 |
| 332 | Table &1 is being updated |
| 333 | &1 derivation rules found |
| 334 | &1 derivation rules found that use groups |
| 335 | No action necessary for table &1 |
| 336 | Start at &1 |
| 337 | Ended at &1 (&2 milliseconds) |
| 338 | Strategy: &1, environment: &2, step number: &3 |
| 339 | Deleted records: &1 |
| 340 | Modified or inserted records: &1 |
| 342 | Use transaction FAGL_VALIDATE for changes |
| 351 | Changes to the validity type are not permitted |