cancel
Showing results for 
Search instead for 
Did you mean: 

Reproducing AFAB funktionality "batch input" with ECC 6.0

OO
Participant
0 Kudos

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?

Accepted Solutions (1)

Accepted Solutions (1)

former_member205615
Contributor
0 Kudos

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

OO
Participant
0 Kudos

OK, but with this will only provide a list of erroneous documents, e.g. in ARAL or ARMO.

This makes my error clearer, but I still habe to run the deprecation as a test in advance and cannot do a correction simultaneously.

former_member205615
Contributor
0 Kudos

Yes, you have to run AFAB in test mode first and then check the list of erroneous document.

Regards
George

Answers (2)

Answers (2)

former_member188063
Active Contributor
0 Kudos

I reckon, executing AFAB in test mode and selecting field 'Error Analysis' is the best option instead of going retro.

Sudhakar*

NathanGenez
Active Contributor
0 Kudos

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?