Purchase Order Carryforward Does Not Net to Zero

Question

We are working in a year-end test client, copy of Production, in preparation for fiscal year end closing.
For purchase order carryforwards, we find a number of documents which do not net to zero in the sender year. This seems to occur most often for the case where a line item has split account assignments. In these cases, only one account assignment line is carried forward. The other account assignment lines are ignored.
This does not occur for all cases where we have split assignments. We have been unable to determine what is unique about the instances where the carryforward does not work properly.
Our system is R/3, 4.7, support stack 27.
Has anyone else encountered this problem? If so, can you give me any guidance as to how to address it?
Thank you.

Answer 1

Hello all. Since i didn't get any replies, I don't know if there is any interest in this. However, for future reference, in case any else encounters this issue and searches the forum, here is the answer which we found:
FMJ2 and FMJ3 process the carryforwards and reversals in blocks of 2000 lines. At the end of a block, the PO may be split up across blocks, with one or more assignment items processed in the first block, and the remaining items in the next block.
If you have selected "Block Documents" on the initial screen, when the first item is processed, it locks the PO. When the second block attempts to process the remaining items, there is an error that the PO is locked, and these items are not processed.
The developer is working on a correction to the code to handle this. In the meantime, there are two workarounds:
1) Uncheck "Block Documents"
or
2) After processing, use FMJ3 to reverse the carryforwards which received the error. Use FMJ2 to carry them forward again, in smaller groups which are not large enough to fill up a 2000 line block, and which therefore do not encounter the problem.