R3 version: 6.3.6000.151
We are testing R3 before we upgrade from R2, and I found what appears to be a bug in the credit card processing system. Here are the steps to reproduce it...
- In Call Center, create an order with two lines on it.
- Enter a credit card as payment and submit the order. At this point the payment amount authorized is the same as the order total. (e.g., $100)
- Invoice one line of the order. (e.g. $25)
- Notice that the amount that was invoiced ($25) was captured (or “finalized”) by AX, which is correct, but AX also requested a new authorization for the entire order amount ($100) instead of the remaining order amount ($75).
What AX should have done in step 4 is authorize just the remaining order amount ($75 in the above example), instead of the full order amount.
I stepped through the code during the process (step 4 above) and found that the payment (MCRCustPaymTable) is staying in an "authorized" status, and the logic to calculate how much to authorize subtracts payments in "posted" status. Since the payment isn't in "posted" status yet, AX thinks the entire order amount still needs authorized.
I performed an LCS issue search for "credit card" and checked all 100+ results, but none of them refer to this problem.
Two questions about this:
- Has anyone else seen this?
- If so, is the problem a configuration issue, or does it require fixing the bug in code?
Thanks in advance for any advice.
djz
