on 01-19-2016 11:43 AM
Hi John,
This is a technical issue that can have various reasons. You can check if you have a substitution that modifies ANEK data during asset postings. Such a substitution can be a possible cause of AAPO158.
Otherwise I think the cause of the error can only be identified with debugging. You might need to create a support ticket then.
Best regards, Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John,
No. You cannot perform the exact same thing as KO88 reversal manually. The settlement and its reversal also update special settlement information (e.g. which items are settled) that would not be affected by normal postings.
Of course it depends on your requirements if some workarounds might work for you - If it is just about adjusting values, you can think about a negative posting to the order that you will settle like normal. However, this would not be the same as KO88 reversal.
From my perspective, the only good solution is that you adjust your substitution in a way that it does not cause the AAPO158 problem. Of course you have to discuss such a change internally so that it still fits your requirements, but I’m sure there is a way to do so. For example maybe it’s already enough to just avoid the substitution in case of reversal.
Best regards, Michael
Hi John
1. Can you check how many docs you have for this asset, in AB08? Are there two?
2. If yes, in a TEST system, can you replicate the same scenario and reverse one asset document from AB08?
Br, Ajay M
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
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.