This website is not affiliated with, sponsored by, or approved by SAP AG.

tolerance key checking during IR

Logistics : MM and its sub-modules (WM, IM, PO, LIS)

Moderators: Snowy, thx4allthefish, svetja, Ha Tran

tolerance key checking during IR

Postby Guest on Wed Jan 04, 2006 8:49 am

In OMR6, we have so many tolerance key and every tolerance key have diff value defined.

PP Price variance
PS Price variance: estimated price
ST Date variance (value x days)
VP Moving average price variance

When we post the invoice against to the PO, how does the system know which tolerance key we want to check? where is this assignment?

Guest
 

Postby Lakshman on Wed Jan 04, 2006 9:22 am

You cannot control which tolerance keys are to be checked for process A and which for process B. You can only control whether a tolerance key is to be checked or not (in the t-code you have mentioned).
Lakshman
Lakshman
 
Posts: 206
Joined: Wed Dec 18, 2002 11:01 am
Location: Racine, Wisconsin

Postby Ha Tran on Wed Jan 04, 2006 8:30 pm

Hi,

As soon as a certain tolerance key is activated for your own company code in Transaction OMR6, that tolerance key will be checked ie. the system will check all tolerance keys and pop up the related message (either W or E dependent on how you set up in OMRM Transaction).

Cheers,
HT
Ha Tran
 
Posts: 28130
Joined: Sun Mar 30, 2003 8:29 pm
Location: Perth, Western Australia

Postby Guest on Thu Jan 05, 2006 9:46 am

My only question now is what the usage of BD Form small differences automatically???

I know PP (Price variance) use to check the price variance enter in the MIRO against to the price in GR. But what about BD???
Guest
 

Postby Ha Tran on Thu Jan 05, 2006 7:17 pm

Hi,

Basically, the BD Transaction/Event Key is used in the case of so-called Total-Based Invoice Reduction. It does particularly refer to the scenario where a vendor invoices a material with higher conditions that agreed in the purchase order. If Invoice Verification determines a difference between the net total of the invoice items and the invoice document (minus tax and unplanned delivery costs), for invoice with small differences it is often too much work to try and find the reason for the difference. Instead, the system can post the invoice if the difference falls within a predefined vendor-specific tolerance. A typical example is that if the total value of the invoice document is 100,502 USD while the net total of the invoice items is 100,500 USD, then the posting lines of the accounting document during IR posting is -
Dr GR/IR Clearing Account (WRX) 100,500
Cr Vendor Account 100,502
Dr Clearing Account for Invoice reduction (BD) 2

At the same time, the Credit Memo will be also created with the following posting lines -
Dr Vendor Account 2
Cr Clearing Account for Invoice Reduction (BD) 2

Cheers,
HT
Ha Tran
 
Posts: 28130
Joined: Sun Mar 30, 2003 8:29 pm
Location: Perth, Western Australia

Postby Guest on Tue Jan 10, 2006 1:07 pm

HT,

Thanks for the detail explanation. However, to make it simple, let say I have 100 USD as invoice amount received from the vendor. I then enter the 100 USD (no other cost involve, i.e. zero tax , no delivery charge, etc) at the invoice hearder. Then enter the PO number at the item invoice item, the amount is defaulted automatically, which is 102 USD.

Now, because I set the value in BD key is 2 USD, then I can post it right?

Lily
Guest
 

Postby Ha Tran on Tue Jan 10, 2006 8:31 pm

Hi,

As I have said the BD Tolerance Key is used for the case of Total-Based Invoice Reduction scenario ie. the vendor invoiced amount is higher than the proposed amount. Therefore, in OMR6, you can only set the Upper Limit instead of Lower Limit. If the invoiced amount is 102 while the proposed amount is 100, then BD will be applicable.

Cheers,
HT
Ha Tran
 
Posts: 28130
Joined: Sun Mar 30, 2003 8:29 pm
Location: Perth, Western Australia

Re: tolerance key checking during IR

Postby johny on Wed Jan 11, 2006 4:21 am

Anonymous wrote:In OMR6, we have so many tolerance key and every tolerance key have diff value defined.

PP Price variance
PS Price variance: estimated price
ST Date variance (value x days)
VP Moving average price variance

When we post the invoice against to the PO, how does the system know which tolerance key we want to check? where is this assignment?


I think it is hard-coded by SAP
johny
 
Posts: 123
Joined: Mon Nov 24, 2003 8:48 am

Postby Guest on Wed Jan 11, 2006 7:19 am

Ha Tran wrote:Hi,

As I have said the BD Tolerance Key is used for the case of Total-Based Invoice Reduction scenario ie. the vendor invoiced amount is higher than the proposed amount. Therefore, in OMR6, you can only set the Upper Limit instead of Lower Limit. If the invoiced amount is 102 while the proposed amount is 100, then BD will be applicable.

Cheers,
HT


HT,

In that case, probably I confused with the PP Tolerance Key then. So, the BD will check the price between the invoice hearder and item. i.e.

PO Net Price = 100 USD
GR = 100 USD
Inovice received from vendor is 102 USD
value set in the BD key = 2 USD

Now, in MIRO, I would enter 102 in the Amount field (WRBTR).
Then enter the PO and the price defaulted automatically. (This price is based on the GR price, right?) Now, the price is 100 USD. Because of the BD key, then I was able to post the inovice.

Please confirm if my understanding is correct.

In that case, what is the use of PP Key?
Guest
 

Postby Ha Tran on Wed Jan 11, 2006 7:33 am

Hi,

Yes, this is how BD is going to work. Again, the basic difference between PP and BD is that in case of PP, the system will make the validation against each and every Invoice Line item whereas the BD is only applicable where there is a slight difference between the total value of invoiced items against the invoiced amount without validating each and every invoice item.

Cheers,
HT
Ha Tran
 
Posts: 28130
Joined: Sun Mar 30, 2003 8:29 pm
Location: Perth, Western Australia

Postby Guest on Sun Jan 15, 2006 3:37 am

Ha Tran wrote:Hi,

Yes, this is how BD is going to work. Again, the basic difference between PP and BD is that in case of PP, the system will make the validation against each and every Invoice Line item whereas the BD is only applicable where there is a slight difference between the total value of invoiced items against the invoiced amount without validating each and every invoice item.

Cheers,
HT


I am confused now. What do you means by:

"BD is only applicable where there is a slight difference between the total value of invoiced items against the invoiced amount without validating each and every invoice item."

i.e. In my BD setting, I have 2 USD as Upper Value. And my PP setting, I have 10 USD as Upper Value.

If the total amount of the invoice is 101 USD, and the invoice Item is 100 USD (which defaulted from PO), which key will be used for validation?
Guest
 

Postby Ha Tran on Mon Jan 16, 2006 1:30 am

Hi,

First of all, during LIV process, all tolerance keys are validated (as soon as they are activated in OMR6). During invoice entry, you can make manual change in either invoice header or invoice line item. If you are changing the invoice item, then PP tolearance key will be validated but if there is not any manual change in the invoice item but you manually update the invoice amount at the header level (to comply with the vendor invoice), then BD will be validated. In your example, since there is not any change in the invoice item (100 USD), therefore, PP tolerance key will not be validated but only BD (since you have to change your invoice amount at the header level from 100 into 101 to accommodate vendor invoice amount).

Cheers,
HT
Ha Tran
 
Posts: 28130
Joined: Sun Mar 30, 2003 8:29 pm
Location: Perth, Western Australia

Postby Guest on Mon Jan 16, 2006 9:18 am

HT,

Thanks for the note. I have a question now. Do you know under what business scenario that the amt in the item line will be changed? This should be defaulted based on GR... if we change, i.e. reduce the increase the amt in the item line (which is different from GR amt), then what will happen to the G/L account posting? no correct already...
Guest
 

Postby Ha Tran on Mon Jan 16, 2006 9:25 am

Hi,

The typical example is when you have accepted what you maintained in your PO pricing condition is not as accurate as expected and therefore, it is adjusted during LIV process.

Cheers,
HT
Ha Tran
 
Posts: 28130
Joined: Sun Mar 30, 2003 8:29 pm
Location: Perth, Western Australia


Return to Logistics MM

Who is online

Users browsing this forum: No registered users and 11 guests



This website is not affiliated with, sponsored by, or approved by SAP AG.