on 04-09-2015 10:04 AM
Regarding this thread ECC 6.0 excluded the functionality of batch input in deprecation run (transaction AFAB).
Our asset accounting departement wishes to have this feature set up again. By choosing to display errors in the foreground, they are be able correct errors on-the-fly as they encounter.
How can I reproduce this behaviour in ECC 6.0?
Hi
You can execute AFAB in test mode and select field 'Error Analysis'. for more details, you can refer to the F1 help of the field.
Regards
George
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I reckon, executing AFAB in test mode and selecting field 'Error Analysis' is the best option instead of going retro.
Sudhakar*
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is a bad idea/request with no value.
Settlement does not run in batch mode.
Dunning does not run in batch mode.
Check correspondence does not run in batch mode.
Revaluation does not run in batch mode.
Why should the depreciation run be in (old, archaic, error prone) batch mode?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
110 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.