on 03-13-2017 2:47 PM
Hello,
We have a problem related to MM partial invoice plan and WBS commitment.
We created a PO to buy a material cost 1000 $.
We used partial invoice plan (without GR) in order to divide invoices according to milestone. We divided it into three parts of invoicing date, e.g.
13.03.2017 500 $
13.04.2017 300 $
13.05.2017 200 $.
(Today is: 13.03.2017)
We want to work with:
MRIS – When the amount is exactly the same as the milestone amount.
MIRO: When the amount is greater than the milestone amount, But here we have 2 cases:
oCase 1: The difference amount won't be on account of the second milestone commitment amount. It will be simply difference.
oCase 2: The difference amount will be on account of the second milestone commitment amount.
Our problem relates to MIRO process (both cases):
Let me give an example:
On 13.03.2017 we run MIRO for the PO and got amount of 500 $.
The vendor was invoiced with 700 $.
On the Milestone line: 500 $
Now, we tried 3 cases to write the difference:
oCase 1: We put the difference on "Unplanned delivery costs".
oCase 2: We put the difference on "GL Account" tab.
oCase 3: We change the milestone amount to be 700 $ (instead of 500 $) only in the invoice item.
It each case the commitment of the second milestone reset and becomes zero.
On 13.04.2017 if we will run T-code MIRO, we will get the amount of the second milestone (300 $).
So, our problem is that between 13.03.2017 to 13.04.2017 we have a wrong information data from that PO on WBS with the commitment data.
Our question is how we can write invoice for the first milestone with amount greater than amount of PO milestone for each case:
oCase 1: The difference amount won't be on account of the second milestone commitment amount. It will be simply difference.
oCase 2: The difference amount will be on account of the second milestone commitment amount.
Best regards,
Lior
Hi Lior,
I can give some work around for oCase 1. When you book Miro use two g/l accounts on the debit side out which you can eliminate one from availability check , if you do config in OPTK.
for ocase 2 i think you can achieve this functionality defaultly. or probably i did not understand your question probably.
Thanking you
Vengaiah
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
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.