Quantity tolerances for IR before GR
Dear all,
I have the following problem:
-My customer is receiving MIRO invoices before doing GR. In some cases the vendors are sending double invoices with different references but to same PO. This is not acceptable and my customer want quantity tolerance differences of 10 % when IR before GR. I went to transaction OMR6 and put 10 % under tolerance key DQ percentage difference but still quantity of 120 PC when PO is on 100 PC could be posted without any warning or error.
Is there something else that I need to activate or should I use another tolerance key?
Best regards, Åsa
Hi Åsa,
I was checking this and this error message is working, but, with a PO for third party process.
In my client case, the PO was created with reference to a Sales Order.
I made a test without this reference, and, you are right, the error message is not working.
The only that I can suggest you is the following:
- Customising solution: With OMR6, you can make that the Invoice can be blocked if they are creating this with more amount than the allowed (I think, you already made this).
- Custom solution: Make a custom program that can validate the total amount and send an error message if the amount is higher than the allowed.
I hope this help.
Kind regards,
Sandra
Similar Messages
-
SUS Quantity tolerance for confirmation -How to set an warning or error Msg
Hello All,
Does anyone knows how do i configure SUS, so the system will check quantity tolerance in PO confirmation so the Supplier can knows that he is within or over the tolerance?
I would like to set an error message so the supplier will confirm the PO within the tolerance or will reject it.
Thanx a lot,
Sheila Silvatry the following:
in transaction SPRO
goto supplier relatioship management-> cross application basic settings ->set tolerence checks ,
create a new tolerence group, for this group assign the folowing tolerence keys as required.
PM: Quantity variance (converted to currency amount) - <b>this is the one relevant for you i guess.</b>If a confirmation is expected for a purchase order item, the system calculates the purchase order confirmation net price multiplied by the purchase order confirmation quantity. The system compares this sum with the defined upper and lower limits. You can also define percentage limits for the quantity variance check. Then the percentage variance from the expected quantity calculated - independent of the purchase order price - and this is compared with the defined percentage limits.
PZ: Time overrun compared to purchase order
The system determines how many days the delivery date has exceeded the planned time interval by. If the delivery date of the purchase order confirmation is earlier than the delivery date of the purchase order, the system takes the purchase order date - the confirmation date; If the delivery date of the purchase order confirmation is later than the delivery date of the purchase order, the system takes the purchase order confirmation date - the purchase order date. The system compares the number of days with the defined absolute upper limit.
PR: Price variance (value variance from expected value)
Here the variance between the purchase order confirmation and the purchase order price is checked. The system determines for the items the price variance as the product of the quantity in the purchase order confirmation multiplied by the price in the purchase order confirmation, and it compares this variance with the defined percentage and absolute upper and lower limits.
then
in transaction PPOMV_BBP, search for teh relevant vendor,
assign the attribute "tolerence group"(TOG) to the newly created tolerence group for the relevent vendor.
Regards,
Chander -
Quantity tolerance for purchasing organization
Dear Gurus,
Is it possible to configure quantity tolerance @ purch org level, if yes please let me know how. One alternative solution what i have given is to maintane qty tolerence in Info record through it will flow to Purchase order
Thanks in Advance
Mahesh M JHi
Tolerance limit can be maintained at company code level.
This can be done at SPRO- SAP IMG- Material Management- Inventory management and physical inventory - Goods receipt - Set tolerance limits
Tcode: OMC0
Check this out.
And also maintian the tolerance limit in info record ( For the vendor, material, pur org and plant combination). It will default the tolerance limit while creating PO.
Thanks
Raman -
Quantity tolerance for PO based IV
Hi All,
In import scenario we have PO based IV.My requirement is if PO qty is 100 and then if I try to post IV for 110 quantity(GR not done) the system should issue a warning or error message.
As per my knowledge I have done the following settings.
1.Have maintained the tolerarnce limits for the Compnay code in OMR6 for the tolerance key
DQ - Exceed amount: quantity variance.
2.Have maintined the message M8 -081 "Quantity invoiced greater than goods receipt quantity" and M8-087 "Invoice quantity greater than PO quantity (item without GR)" as error in OMRM.
Despite these settings I am not getting any error or warning message if I try to post IV for a quantity freater than PO quantity.
Please guide me if any I am missing out on any settings.
Thanks
GarimaHi Amir,
I have done as per the link given by you. In my PO Gr based IV flag is not set and have maintained tolerance key DQ.
Please let me know if anything else also needs to be done.
Thanks -
Quantity Tolerance for material in the PO and GR
Hi Gurus,
I have this requirement, specific material type( i.e ERSA) quantity in the PO is 100 then if I GR it, I want to have converted the 100 quantity to 150. How can this be happen? Changing the tolerance in the info record or material master?i have tried it but still doesnu2019t work?How can I do that? Converting the PO quantity to a specific quantity without changing the original figures in the PO. Please help.
Thanks!The system will not automatically convert the 100 qty to 150 qty while GRN....
We have to set the Over delivery tolerance in PO line item for what you want to excess recieve the materials while doing GRN based on your PO qty...and also
we can set the unlimited tab in PO line item for recieveing excess materials during GRN. -
Setting tolerances for Incoming Inv - Vendor specific quantity tolerance
Hello SAP Gurus,
My concern is incoming EDI based Vendor invoices are getting blocked due to quantity variations. Being inter Company, I wanted to set quantity tolerances specific to one Vendor so that invoices are not blocked. As I have seen wiki http://wiki.sdn.sap.com/wiki/display/ERPSCM/MM-IV-LIV-CRESetTolerancesforIncoming+Invoice under Vendor specific tolerances there is *no quantity specifc settings* however I found value specific tolerance whereas my requirement is to set against quantity. Is it possible to maintain Vendor specific quantity settings? Is there any requirement to maintain quantity tolerance or value tolerance itself enough to handle?
Pls. help at the earliest.
Regards,
Krish
Edited by: Krish9 on Jun 12, 2011 7:30 AM
Edited by: Krish9 on Jun 12, 2011 2:56 PMDear Madhava Bheemakumar,
Try this,
Goto SPRO-> Material Management->Logistic Invoie Verification->Define Attributes of System Messages
check Message Number 083 Exist or not ? if not Add the same.
or
Check SE91->M8 Messages , Verify which Message number is the correct one for your creteria add the same in above Path.
Best Regards,
KSK.
Note : Let me know your comments. -
Payment block with a quantity reason when IR before GR
Hi,
Currently, system sets payment block with a quantity variance reason when IR before GR for standard PO items. But this payment bock does not working for a Service PO items.
In our system, we didn't maintain a talerance key DW as expained in the help below.
Can anyone help this out to set payment block with a quantity variance when IR before GR for a Service PO item?
DW: Quantity variance when GR quantity = zero
If a goods receipt is defined for an order item but none has as yet
been posted, the system multiplies the net order price by (quantity
invoiced + total quantity invoiced so far).
The system then compares the outcome with the absolute upper
tolerance limit defined.
If you have not maintained tolerance key DW for your company code,
the system blocks an invoice for which no goods receipt has been
posted yet. If you want to prevent this block, then set the
tolerance limits for your company code for tolerance key DW to Do
not check.Hi,
We are on ECC6. I'm not sure if the answer from Chris is a correct.
Anyone has used this fucntionality?
Hi,
There is a flag that can be maintained in table T165 Srv. IR before GR(SRV_IR_BEFORE_GR) that can be set to allow Invoice Receipts to be posted before GR's for service items. You will also need to set message SE 260 and 650 to warnings in customising or in view V_160M.
This will allow you to remove the GR based IV flag but will not allow invoices to be blocked, in order to do that you need to create an implementation for the BADI for the LIV release check.RegardsChris -
I have a question with reference to following tolerances:
1- Tolerance key "PE" set at upper limit of 10%
2- Vendor specific tolerance set @ Auto accept + diff $ 5
Absolute upper limit $ 50
% upper limit 2%
Invoice block-
3- Small diff key "BD" $25
4- Price variance Absolute upper limit $ 5
% upper limit 5%
How will these tolerances work- the order? what comes first? which key supersedes the other and in what order?
In short I am trying to figure out is that the system looks at all of these 4 keys at the same time or does it look at any other way?
need help- is there any specific documentation I should look at?
Thanks
RajHello
When processing an invoice, the R/3 System checks each item for variances between the invoice and the purchase order or goods receipt. The different types of variances are defined in tolerance keys.
The system uses the following tolerance keys to check for variances:
AN: Amount for item without order reference
If you activate the item amount check, the system checks every line item in an invoice with no order reference against the absolute upper limit defined.
AP: Amount for item with order reference
If you activate the item amount check, the system checks specific line items in an invoice with order reference against the absolute upper limit defined. Which invoice items are checked depends on how you configure the item amount check.
BD: Form small differences automatically
The system checks the balance of the invoice against the absolute upper limit defined. If the upper limit is not exceeded, the system automatically creates a posting line called Expense/Income from Small Differences, making the balance zero and allowing the system to post the document.
BR: Percentage OPUn variance (IR before GR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units : quantity invoiced in order units and quantity ordered in order price quantity units : quantity ordered in order units. The system compares the variance with the upper and lower percentage tolerance limits.
BW: Percentage OPUn variance (GR before IR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units: quantity invoiced in order units and goods receipt quantity in order price quantity units : goods receipt quantity in order units. The system compares the variance with the upper and lower percentage limits defined.
DQ: Exceed amount: quantity variance
If a goods receipt has been defined for an order item and a goods receipt has already been posted, the system multiplies the net order price by (quantity invoiced - (total quantity delivered - total quantity invoiced)).
If no goods receipt has been defined, the system multiplies the net order price by (quantity invoiced - (quantity ordered - total quantity invoiced)).
The system compares the outcome with the absolute upper and lower limits defined.
This allows relatively high quantity variances for invoice items for small amounts, but only small quantity variances for invoice items for larger amounts.
You can also configure percentage limits for the quantity variance check. In this case, the system calculates the percentage variance from the expected quantity, irrespective of the order price, and compares the outcome with the percentage limits configured.
The system also carries out a quantity variance check for planned delivery costs.
DW: Quantity variance when GR quantity = zero
If a goods receipt is defined for an order item but none has as yet been posted, the system multiplies the net order price by (quantity invoiced + total quantity invoiced so far).
The system then compares the outcome with the absolute upper tolerance limit defined.
If you have not maintained tolerance key DW for your company code, the system blocks an invoice for which no goods receipt has been posted yet. If you want to prevent this block, then set the tolerance limits for your company code for tolerance key BW to Do not check.
KW: Variance from condition value
The system calculates the amount by which each delivery costs item varies from the product of quantity invoiced * planned delivery costs/ planned quantity. It compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
LA: Amount of blanket purchase order
The system calculates the sum of the value invoiced so far for the order item and the value of the current invoice and compares it with the value limit of the purchase order. It then compares the difference with the upper percentage and absolute tolerances defined.
LD: Blanket purchase order time limit exceeded
The system determines the number of days by which the invoice is outside the planned time interval. If the posting date of the invoice is before the validity period, the system calculates the number of days between the posting date and the start of the validity period. If the posting date of the invoice is after the validity period, the system calculates the number of days between the posting date and the end of the validity period. The system compares the number of days with the with the absolute upper limit defined.
PP: Price variance
The system determines by how much each invoice item varies from the product of quantity invoiced * order price. It then compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks if a price check has been defined for subsequent debits/credits. If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product of the quantity to be debited/credited * order price and compares this with the upper and lower tolerance limits (absolute limits and percentage limits).
PS: Price variance: estimated price
If the price in an order item is marked as an estimated price, for this item, the system calculates the difference between the invoice value and the product of quantity invoiced * order price and compares the variance with the upper and lower tolerance limits defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks whether a price check has been defined for subsequent debits/credits, If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product quantity to be debited/credited * order price. It then compares the variance with the upper and lower tolerance limits defined (absolute limits and percentage limits).
ST: Date variance (value x days)
The system calculates for each item the product of amount * (scheduled delivery date - date invoice entered) and compares this product with the absolute upper limit defined. This allows relatively high schedule variances for invoice items for small amounts, but only small schedule variances for invoice items for large amounts.
VP: Moving average price variance
When a stock posting line is created as a result of an invoice item, the system calculates the new moving average price that results from the posting. It compares the percentage variance of the new moving average price to the old price using the percentage tolerance limits defined.
Variances are allowed within predefined tolerance limits. If a variance exceeds a tolerance limit, however, the system issues a message informing the user. If an upper limit (except with BD and VP) is exceeded, the invoice is blocked for payment when you post it. You must then release the invoice in a separate step. If the tolerance limit for BD is breached, the system cannot post the invoice.
Note that if you set all limits for a tolerance key to Do not check , the system does not check that tolerance limit. Therefore any variance would be accepted. This does not make sense particularly in the case of the tolerance key Form small differences automatically.
Regards -
LIV tolerance for price variance from PO to LIV
Hi Friends,
I am finding difficulty in setting up the tolerance key for price variance from PO value to invoice value. Suppose if PO price is $100 then system should allow upto $105 with out blocking means with percentage of 5%. If it exceeds 5% system should block the invoice.
Please suggest the tolerance key to use and if any other settings required.
Thanks...
Best RegardsHi,
Following is the SAP help on the Tolerance settings for Invoice. Check the config and decide what is best for you (from your brief explanation it looks like AP and PP may be relevant fro your case)
===================
Set Tolerance Limits
In this step, you specify the tolerance limits for each tolerance key
for each company code.
When processing an invoice, the R/3 System checks each item for
variances between the invoice and the purchase order or goods receipt.
The different types of variances are defined in tolerance keys.
The system uses the following tolerance keys to check for variances:
o AN: Amount for item without order reference
If you activate the item amount check, the system checks every line
item in an invoice with no order reference against the absolute
upper limit defined.
o AP: Amount for item with order reference
If you activate the item amount check, the system checks specific
line items in an invoice with order reference against the absolute
upper limit defined. Which invoice items are checked depends on how
you configure the item amount check.
o BD: Form small differences automatically
The system checks the balance of the invoice against the absolute
upper limit defined. If the upper limit is not exceeded, the system
automatically creates a posting line called Expense/Income from
Small Differences, making the balance zero and allowing the system
to post the document.
o BR: Percentage OPUn variance (IR before GR)
The system calculates the percentage variance between the following
ratios: quantity invoiced in order price quantity units : quantity
invoiced in order units and quantity ordered in order price quantity
units : quantity ordered in order units. The system compares the
variance with the upper and lower percentage tolerance limits.
o BW: Percentage OPUn variance (GR before IR)
The system calculates the percentage variance between the following
ratios: quantity invoiced in order price quantity units: quantity
invoiced in order units and goods receipt quantity in order price
quantity units : goods receipt quantity in order units. The system
compares the variance with the upper and lower percentage limits
defined.
o DQ: Exceed amount: quantity variance
If a goods receipt has been defined for an order item and a goods
receipt has already been posted, the system multiplies the net order
price by (quantity invoiced - (total quantity delivered - total
quantity invoiced)).
If no goods receipt has been defined, the system multiplies the net
order price by (quantity invoiced - (quantity ordered - total
quantity invoiced)).
The system compares the outcome with the absolute upper and lower
limits defined.
This allows relatively high quantity variances for invoice items for
small amounts, but only small quantity variances for invoice items
for larger amounts.
You can also configure percentage limits for the quantity variance
check. In this case, the system calculates the percentage variance
from the expected quantity, irrespective of the order price, and
compares the outcome with the percentage limits configured.
The system also carries out a quantity variance check for planned
delivery costs.
o DW: Quantity variance when GR quantity = zero
If a goods receipt is defined for an order item but none has as yet
been posted, the system multiplies the net order price by (quantity
invoiced + total quantity invoiced so far).
The system then compares the outcome with the absolute upper
tolerance limit defined.
If you have not maintained tolerance key DW for your company code,
the system blocks an invoice for which no goods receipt has been
posted yet. If you want to prevent this block, then set the
tolerance limits for your company code for tolerance key DW to Do
not check.
o KW: Variance from condition value
The system calculates the amount by which each delivery costs item
varies from the product of quantity invoiced * planned delivery
costs/ planned quantity. It compares the variance with the upper and
lower limits defined (absolute limits and percentage limits).
o LA: Amount of blanket purchase order
The system determines the number of days by which the invoice is
outside the planned time interval. If the posting date of the
invoice is before the validity period, the system calculates the
number of days between the posting date and the start of the
validity period. If the posting date of the invoice is after the
validity period, the system calculates the number of days between
the posting date and the end of the validity period. The system
compares the number of days with the with the absolute upper limit
defined.
o PP: Price variance
The system determines by how much each invoice item varies from the
product of quantity invoiced * order price. It then compares the
variance with the upper and lower limits defined (absolute limits
and percentage limits).
When posting a subsequent debit/credit, the system first checks if a
price check has been defined for subsequent debits/credits. If so,
the system calculates the difference between (value of subsequent
debit/credit + value invoiced so far) / quantity invoiced so far *
quantity to be debited/credited and the product of the quantity to
be debited/credited * order price and compares this with the upper
and lower tolerance limits (absolute limits and percentage limits).
o PS: Price variance: estimated price
If the price in an order item is marked as an estimated price, for
this item, the system calculates the difference between the invoice
value and the product of quantity invoiced * order price and
compares the variance with the upper and lower tolerance limits
defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks
whether a price check has been defined for subsequent
debits/credits, If so, the system calculates the difference between
(value of subsequent debit/credit + value invoiced so far) /
quantity invoiced so far * quantity to be debited/credited and the
product quantity to be debited/credited * order price. It then
compares the variance with the upper and lower tolerance limits
defined (absolute limits and percentage limits).
o ST: Date variance (value x days)
The system calculates for each item the product of amount *
(scheduled delivery date - date invoice entered) and compares this
product with the absolute upper limit defined. This allows
relatively high schedule variances for invoice items for small
amounts, but only small schedule variances for invoice items for
large amounts.
o VP: Moving average price variance
When a stock posting line is created as a result of an invoice item,
the system calculates the new moving average price that results from
the posting. It compares the percentage variance of the new moving
average price to the old price using the percentage tolerance limits
defined.
Variances are allowed within predefined tolerance limits. If a variance
exceeds a tolerance limit, however, the system issues a message
informing the user. If an upper limit (except with BD and VP) is
exceeded, the invoice is blocked for payment when you post it. You must
then release the invoice in a separate step. If the tolerance limit for
BD is breached, the system cannot post the invoice.
Note that if you set all limits for a tolerance key to Do not check, the
system does not check that tolerance limit. Therefore any variance would
be accepted. This does not make sense particularly in the case of the
tolerance key Form small differences automatically.
Activities
Configure the tolerance limits for the individual tolerance keys.
Lower limit Upper limit
Absolute Percentage Absolute Percentage
AN - - X -
AP - - X -
BD X - X -
BR - X - X
BW - X - X
DQ - - X -
DW - - X -
KW X X X X
LA - - X X
LD X - X -
PP X X X X
PS X X X X
ST - - X -
VP - X - X
===============================================
Best Regards,
Siva -
Purchase Order Goods Receipt quantity tolerance setting not working.
Team,
We are using the IS-Oil solution, ECC 6.0 REL 605 SP LEVEL 009 .
The issue that I have is as follows:
Purchase Order Goods Receipt quantity tolerance setting not working, I had set up a 10% tolerance on QTY received in the GR process via the PIR and also the Purchase Value Key in the material master and also changed the message to a warning in OMCQ for message number M0722.
I had performed a similar configuration and master data maintenance on a different NON IS-OIL client install and it worked fine.
I believe it is the IS-OIL component in the Inventory update portion of the GR process that is causing the error.
I have searched for OSS notes, however they mention that there is no solution.
Setting the PO line item as Unlimited will not be best practice for the business and will not be used.
Has anyone come across this issue? and how was it resolved, your help and guidance will be greatly appreciated.
ThanksHello,
Please check the Tolerance levels in O588
Also you can use the BAdI OIB_QCI_ROUND_QTY: A new method, CHECK_TOLERANCE
Best Regards,
R.Brahmankar -
A save request exceeded the quantity limits for a given structure type.
I am running PI7.1 SP6..
I have created all the objects and done all of the configuration in the Enterprise Service Builder and the Integration Builder and I am trying to publish the Webservice in the Service Registry, but after displaying the WSDL, and then publishing the Webservice, I get the following error:
com.sap.aii.ib.core.uddi.RegistryClientException: A save request exceeded the quantity limits for a given structure type.
Number of Business Entities exceeds your limit of 1 (2)
at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishServices(RegistryClientDelegateProvider.java:338)
at com.sap.aii.ibdir.server.wsquery.WSQUDDISrvPublishTB.execute(WSQUDDISrvPublishTB.java:112)
at com.sap.aii.ibdir.core.simulation.DefaultTaskBroker.execute(DefaultTaskBroker.java:158)
at com.sap.aii.ibdir.server.simulation.TaskQueryService.specialQuery(TaskQueryService.java:31)
at com.sap.aii.ib.server.query.SpecialQueryServiceProvider$SpecialQueryServiceImpl.specialQuery(SpecialQueryServiceProvider.java:63)
at com.sap.aii.ib.server.query.QueryServiceImpl.specialQuery(QueryServiceImpl.java:443)
at com.sap.aii.ib.server.query.QueryServiceBean.specialQuery(QueryServiceBean.java:112)
at sun.reflect.GeneratedMethodAccessor534.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at $Proxy2177.specialQuery(Unknown Source)
at sun.reflect.GeneratedMethodAccessor533.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Caused by: com.sap.esi.uddi.sr.api.ws.PublishServicesFault: A save request exceeded the quantity limits for a given structure type.
Number of Business Entities exceeds your limit of 1 (2)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.JAXWSUtil.deserializeException(JAXWSUtil.java:357)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.JAXWSUtil.processFault(JAXWSUtil.java:327)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:987)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:703)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:673)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:167)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:120)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:83)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:64)
at $Proxy2689.publishServices(Unknown Source)
at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishServices(ServicesRegistryProxyFacade.java:358)
at sun.reflect.GeneratedMethodAccessor1059.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at $Proxy255.publishServices(Unknown Source)
at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishServices(RegistryClientDelegateProvider.java:335)
... 41 more
As always, these errors are so informative!
It has published the Webservice in the Service Registry, but not with the End Points...
has anyone come across the message before and know how to fix it so I can successfully publish the Webservice???
I have searched SDN and OSS - also opened an OSS note about another error I am experiencing...Hi Barry
Have you already published for the same server or this is first time you tried and got error ?
Did you referred Troubleshooting guide
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e05829a5-55aa-2a10-f694-ba8e30c3c122
Master installation guide
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0301486-758c-2a10-9d84-a195556df422
Thanks
Gaurav -
Hi gurus,
I need to set quantity tolerance in the invoice.
I have set tolerances at:
- MM -> Logistics invoice verification -> Incoming Invoice -> Configure Vendor-Specific Tolerances : Here you can just set value tolerances.
- OMR6
If we try to invoice more quantity that there is in de GR the systems shows this error:
Quantity invoiced greater than goods receipt quantity
Message no. M8504
The message has to be an error that's right but it should consider the tolerances limits.
I have also checked tolerances in GR OMC0 but they don't work either.
What am i doing wrong? Do ou hace any ideas to set quantity tolerances in MIRO?
Thanks in Advance,
AdrianaHey there,
If its a GR Based Invoice Verification, the you will raise an invoice for what has been received.
You cannot increase the quantity in case of a GR based invoice verification.
Please uncheck this item in the PO and then try to do the Invoice Receipt.
However if you want to do a invoice for 10.01 units, cancell your original GR which was for 10 and redo the GR for 10.01 and then do the invoice posting in MIRO.
Lemme know if this would work
Thanks -
There are still batch split items with quantity X for item
Our current system is ECC6. The deletion of item in the delivery (TO
confirmed) is different before ECC6 (4.6C). In 4.6, unless quantity of
batch split items are zeroed out in the delivery, the item cannot be
deleted. Message "There are still batch split items with quantity X for
item" is encountered. In ECC, line item can be deleted even batch split
items are not 0. The message doesn't exist in ECC6.
Please advise how to activate this message.In ECC6, the logic has been completely changed during item deletion.
Now, there is no way to activate the message VL224 when deleting batch item.
In 46c,
FORM XLIPS_LOESCHEN_PRUEFEN is called with XL_ERROR = 'X'.
Main program SAPFV50P
Source code of FV50PFLP_XLIPS_LOESCHEN_RC
FORM XLIPS_LOESCHEN_RC
IF IF_TABIX IS INITIAL.
REFRESH LT_REASONS.
PERFORM XLIPS_LOESCHEN_PRUEFEN TABLES LT_REASONS <<<<<<
USING LF_POSNR
CHARX <<<<<<<
IF_ALL
CHANGING LF_EXIT.
In ECC6,
The FORM is called with XL_ERROR = SPACE. That's why the error is not issued.
Actually, they are called from different place in ECC and 46c. The logic has been completely changed.
Main Program SAPMV50A
Source code of MV50AF0D
FORM DELETE_ITEMS_CHECK
perform xlips_loeschen_pruefen(sapfv50p) tables ct_reasons <<<<<
using ls_admin-posnr
space
space <<<<
'GHK' "n_766525
changing lf_exit. -
Set tolerance for Invoice confirmation
Dear Experts,
We are using SRM 550 , Classic Scenario
When we make the invoice verification process it allowed only the order price,
When I change the price to lower value we got Error Message :
Average price too low: below tolerance limit of 0.00 and ILS (Item 1)
I saw in IMG that the following errors message are set by Item
PRICE TOLERANCE BBP_IV 069
PRICE TOLERANCE BBP_IV 071
Now we would like to set the Upper and Lower tolerance for the Invoice ,
we set in IMG:
spro > SRM > Enterprise Buyer > Cross application basic settings > set tolerance checks.
We have set a new Tolerance Group- new entry ( it was empty)
But Tolerance Key we can not find the one for the Invoice
We have only this keys:
CF Document Tolerances for GR
DA VALUE OVERRUN
DQ OVERRUN QTY IN CURRENCY AMT
LA AMOUNT BLANKET PURCHASE ORDER
LD TIME OVERRUN BLANKET PO
PM OVERRUN QTY IN CRCY AMT (PO)
PP PRICE DEVIATION
PR PRICE VARIANCE (PO)
PZ TIME OVERRUN (PO)
TX TAXES (INV)
Which one is for the Invoice Verification tolerances?
Please advise where and how can we set it ?
Regards,
MosheHi
PP is the tolerance key required by you.
PP: Price variance (value variance from expected value)
You only use this tolerance for invoice entry.
The variance from the expected value is checked here, based on the preceding document (purchase order price or confirmation value).
The system determines by how much each invoice item varies from the product of quantity invoiced multiplied by the order price. It then compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
PR is for deviations while creating Confirmations.
Make sure you enter the tolerance key in vendor master too.
Regards
Virender Singh -
Quantity Tolerance in Invoice Verification
All,
I have an issue in Direct Trading flow. PO qty received at 10,500, sales order qty 10,500, billing document 10,500 and invoice qty at 10,500.05. The system is not allowing me to close the sales order due to the weight discrepancy in logistics invoice.
Is there any customizing available to set a quantity tolerance in Invoice Verification (as the one existing for Amount)?
I tried to check final invoice in the invoice tab of my PO but it did not work : sales order is still "Being processed".
Thanks in advance,
Laurehi,
Your question is little confusing...Do you wanna check the duplicate invoice check...then check SPRO settings here:SPRO >> MM >> LIV >> Check for duplicate invoices...
If you want to have the tolerances applied then check here:
SPRO>> MM >> LIV >> Incoming invoice >> set up vendor specific tolerances...but remember that this will be in terms of amount with respect to that quantity...so if the tolerance is 0% then the amount shd be exactly same...otherwise the system will block the invoice for qty variance...
Hope it helps..
Regards
Priyanka.P
Maybe you are looking for
-
How to delete from Nokia C5-03?
How to do delete music and other unnessary things from Nokia C5-03? I have not found delete or remove area. Help me.
-
LION Compatiblity with ATO Autralian Taxation Software
Here is , How to set up ECI and AUSKey ATO (Australian Taxation Office) Software on a new Mac running LION OSX 10.7 A) Install Java for Lion – <http://support.apple.com/kb/DL1421> B) Enable applet plug-in by going to GO>UTILITIES>Open Java Preference
-
How to create xml file from relational tables in 10gR2
Hi, I am very new to XML and was wondering how to create an XML file from querying relational tables. Some child tables may contain multiple rows that need to be returned in certain instances. Other queries will just be single or multiple rows from o
-
Problem with OCI call and how to install and use 'DEBUG_EXTPROC' on Linux
Hi, Can any one let me know how I can install and use this debug_extproc package. I have installed oracle XE server on Linux machine(32-bit). When I use : DEBUG_EXTPROC.STARTUP_EXTPROC_AGENT' ... i get an error saying that : it is not declared. I tri
-
Airport Express: Internet Access Works But Not "Seen" in Admin. Util. ??
Hi All -- I have a friend with the set-up described below and a seemingly impossible problem. he's asked for my help, and so I'm asking for yours, because frankly the situation just has me stumped. Here goes: Set-Up & Other Relevant Facts • DSL conne