SAP ABAP Message Class FAGL_VALIDATION (FAGL_VALIDATION)
Basic Data
Hierarchy
☛
SAP_FIN (Software Component) SAP_FIN
⤷
FI-GL (Application Component) General Ledger Accounting
⤷
FAGL_POSTING_SERV_EHP3 (Package) Services for Posting FI Documents (EhP3)
SAP_FIN (Software Component) SAP_FIN⤷
FI-GL (Application Component) General Ledger Accounting⤷
FAGL_POSTING_SERV_EHP3 (Package) Services for Posting FI Documents (EhP3) 
Attributes
| Message class |  |
FAGL_VALIDATION |
| Short Description |  |
|
| Changed On |  |
20100310 |
| Last Changed At |  |
181717 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
Test run; no changes made to the database | The short text describes the object sufficiently | |
| 2 | 001 |
Enter &1 as the source field or define a condition for &2 | The short text describes the object sufficiently | |
| 3 | 002 |
Groups are not permitted as conditions | The short text describes the object sufficiently | |
| 4 | 003 |
Groups of any kind are not permitted as target fields | The short text describes the object sufficiently | |
| 5 | 004 |
Field &1 is added automatically when set &2 is used | The short text describes the object sufficiently | |
| 6 | 005 |
When you enter a group, leave the group content fields empty | The short text describes the object sufficiently | |
| 7 | 006 |
An entry in this field is mandatory if you enter a group (&1) | The short text describes the object sufficiently | |
| 8 | 007 |
Record overlaps with a record that already exists in the database (&1) | The short text describes the object sufficiently | |
| 9 | 008 |
Date overlaps with a lock set by user &1 on &2 at &3 | The short text describes the object sufficiently | |
| 10 | 009 |
Inconsistencies found in locks on derivation tables (rules) | The short text describes the object sufficiently | |
| 11 | 010 |
The entire record is empty; enter data | The short text describes the object sufficiently | |
| 12 | 011 |
&1 is not a valid entry | The short text describes the object sufficiently | |
| 13 | 012 |
No authorization for rule of strategy &1, activity &2, auth. object &3 | The short text describes the object sufficiently | |
| 14 | 013 |
No strategy found (company code &1, ledger group &2) | The short text describes the object sufficiently | |
| 15 | 014 |
Validation is not active for company code &1 | The short text describes the object sufficiently | |
| 16 | 015 |
Save the validation strategy first | The short text describes the object sufficiently | |
| 17 | 016 |
Validation strategy &1 contains validation rules | The short text describes the object sufficiently | |
| 18 | 017 |
Validation strategy &1 (class &2,subclass &3,strategy &4) does not exist | The short text describes the object sufficiently | |
| 19 | 018 |
Validation strategy &1 is assigned to company code &2 | The short text describes the object sufficiently | |
| 20 | 019 |
Validation strategy &1 is assigned to ledger group &3 (company code &2) | The short text describes the object sufficiently | |
| 21 | 020 |
First save the new validation strategy | The short text describes the object sufficiently | |
| 22 | 030 |
Invalid account assignment combination in document/item &2; see long text | Space: object requires documentation | |
| 23 | 031 |
Error in validation of account assignment combinations | The short text describes the object sufficiently | |
| 24 | 298 |
Groups are not permitted as conditions | The short text describes the object sufficiently | |
| 25 | 300 |
Field &1 is added automatically when set &2 is used | The short text describes the object sufficiently | |
| 26 | 301 |
Enter &1 as the source field or define a condition for &2 | Space: object requires documentation | |
| 27 | 304 |
Groups of any kind are not permitted as target fields | The short text describes the object sufficiently | |
| 28 | 305 |
Your lock overlaps with the lock set by user &1 on &2 at &3 | The short text describes the object sufficiently | |
| 29 | 306 |
&1 is not a valid entry | The short text describes the object sufficiently | |
| 30 | 307 |
Controlling area or company code are mandatory with certain groups | The short text describes the object sufficiently | |
| 31 | 308 |
Inconsistencies found in locks on derivation tables (rules) | The short text describes the object sufficiently | |
| 32 | 309 |
Enter an area for the data selection; placeholders are permitted | The short text describes the object sufficiently | |
| 33 | 310 |
Date overlaps with a lock set by user &1 on &2 at &3 | The short text describes the object sufficiently | |
| 34 | 311 |
&1 records found with empty target fields | The short text describes the object sufficiently | |
| 35 | 312 |
Correct the overlaps between the target fields | The short text describes the object sufficiently | |
| 36 | 313 |
When you enter a group, leave the group content fields empty | The short text describes the object sufficiently | |
| 37 | 314 |
The entire record is empty; enter data | The short text describes the object sufficiently | |
| 38 | 315 |
Record overlaps with a record that already exists in the database (&1) | The short text describes the object sufficiently | |
| 39 | 316 |
Setting lock for group &1 failed (database table &2) | The short text describes the object sufficiently | |
| 40 | 317 |
Group is locked by user &1 since &2, &3 | The short text describes the object sufficiently | |
| 41 | 318 |
Some records were changed; changed records cannot be edited | The short text describes the object sufficiently | |
| 42 | 319 |
Deletion of data contained failed; lock is not removed | The short text describes the object sufficiently | |
| 43 | 320 |
An entry in this field is mandatory if you enter a group (&1) | The short text describes the object sufficiently | |
| 44 | 330 |
Changed: &1 | The short text describes the object sufficiently | |
| 45 | 331 |
Deleted: &1 | The short text describes the object sufficiently | |
| 46 | 332 |
Table &1 is being updated | The short text describes the object sufficiently | |
| 47 | 333 |
&1 derivation rules found | The short text describes the object sufficiently | |
| 48 | 334 |
&1 derivation rules found that use groups | The short text describes the object sufficiently | |
| 49 | 335 |
No action necessary for table &1 | The short text describes the object sufficiently | |
| 50 | 336 |
Start at &1 | The short text describes the object sufficiently | |
| 51 | 337 |
Ended at &1 (&2 milliseconds) | The short text describes the object sufficiently | |
| 52 | 338 |
Strategy: &1, environment: &2, step number: &3 | The short text describes the object sufficiently | |
| 53 | 339 |
Deleted records: &1 | The short text describes the object sufficiently | |
| 54 | 340 |
Modified or inserted records: &1 | The short text describes the object sufficiently | |
| 55 | 342 |
Use transaction FAGL_VALIDATE for changes | The short text describes the object sufficiently | |
| 56 | 351 |
Changes to the validity type are not permitted | Space: object requires documentation |
History
| Last changed on/by | |
20100310 | SAP |
| SAP Release Created in | 604 |
