Line Item For Price Variance

Hi,
What non FI datasource in RSA5 can i find the line item for Price Variance?
Thanks

Hi Sam,
I think 0CO_OM_CCA_9 will word best for me.
what does it mean by: Actual Costs Using Delta Extraction ?
Also would the field REFBN Reference Dosument Number have the invoice number & the PO Number?
Thanks

Similar Messages

Display Variance line items for Orders

Hello Sapients,
I am trying to execute Transaction code KOB3 (Display Variance line items for Orders) ( /n > Accounting> Controlling > Product Cost Controlling > Cost Object Controlling > Product Cost by Order > Information System > Reports for Product Cost by Order > Line Items > KOB3 )
But for some reason I do not see any thing.
Your Advise is greatly appreciated.
Thanks and Regards
Ravi

There is no problem with Authorization.
And i am checking for the correct cost elements and prorcess orders.
Not only KOB3 but also the related reports are not working (viz: GR55-> 7KV9)
thanks and Regards
Ravi

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 Regards

Hi,
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

Line item net price not updated in overview screen net price&line item

Hi ,
We have down payment order with 10 line items
In orders with billing plan, the sales line item net price, if we entered manual condition price (ZPNP) ,gets updated in item condition net value. But it does not simultaneously gets updated at once in 1) Sales order overview screen net value 2) Billing plan header 3)Sales order overview screen line item condition net value. Updation at these three places happens only after clicked on header conditions.
However, in case of the last item in the sales order, the updation happens simultaneously in all the 3 places i.e. 1) item condition net value. 2) Sales order overview screen net value 3) Billing plan header 4) Sales order overview screen line item condition net value.
This is also true for the order with only single line item. We are faced a information popup message every time we change the item net price u201CItem 000100(100 is last line item number in sales order) exists already; the entry ignored u201C. This happens in case of all line items except the last line item. Also this does not happen in case where there is a single line item in order.
Our requirement: The moment the net price of an item is change manually, it should get updated at all the 4 places mentioned above like it does in case of the last line item.
Kindly help me to fix this problem.
Regards,
Adikesav

Hi,
Can u elaborate ur query ?
By this FM you cannot create a SO . Use FM --> BAPI_SALESORDER_CREATEFROMDAT2
Regards,
MAdhukar Shetty

Help on GOA screen control at line item for only material

Hello All
scenario:-
1. create a GOA
for a material with has alternative UOM ( CAR - ORDER UNIT ; 1 CAR - 34 ea) . So i created GOA FOR MATERILA LINE ITEM.
FOR CAR .
2. I released GOA and distributed GOA for CAR as Oeder Unit UOM.
3. now my buyer go to GOA and change UOM as EA and price I AND CHANGE THE PRICE IN THE SAME LINE ITEM.
4. No PO released against the COntract in the ECC
5. Unfortunately buyer could change this UOM from CAR to EA. now GOA shows as EA in the line item
6. this info taken to ECC via IDOC but this info never updated in ECC contract.
7. my PO release as CAR forever rather than EA since my ECC contract always shows as CAR
i can lock this item i can create a new line item, no issues.
how buyer knows each time ? if the system allows buyer always try to change rather than entering new item. it is not buyer fault. it is srm fault.
Now ican u suggest some code in ui control badi , if the PO not releases system should not allow to change the UOM in the GOA line item for a material.
PS:- once PO released against contract . srm will not allow to change the UOM . that is fine.
SAP has to correct this problem and release the note.
Muthu

Hi Donald/SCot/ kiran/ jay...
are you having the same problem in SRM 700. front end validation is required here toooooo...
please help me.
I could not accept this functionality ..
why SRM allows to change the UOM by the buyer after release the GOA for the same line item
if srm allows to do edit, SAP SRM and ECC has to update the same UOM in the existing purchasing contract. IDOCs carry all new uom but why not updated in ECC purchasing contract.
decided to write own logic in ui badi to protect this. what to do
Muthu

FB60 - Two line items for tax amount (Posting Key - 50)

Hi,
I am facing some issue in FB60 invoice posting. For the same vendor(say V1) I am posting 2 different invoices for 100 USD - the company code, G/L, CostCenter & Tax Jursdiction code are different in both the cases. Once I do FB60 and got to document overview screen this is what I see...
Case1 - in the document overview screen I see a Posting key(PK) 31(invoice amount), PK50(tax amount) & PK40(total amount)...which is fine.
Case2 - in second case the document overview shows two line items for PK50(credit - tax amount) and tax amount is different.
Two questions...
1) Why there are two tax items (PK50 items) - is that dependent on tax rule or vendor or company code?
2)My client says the tax amount should be same in both cases - but I am wondering how can it be, when tax codes are different in both the cases? Where can I check how these tax values are getting calculated.
Any adivse/hints will be greatly appreciated/rewarded.
Thanks
Kiran

AKu
I got the same scenario also
this second document display because of material price change u can double click that document

Set Tolerance Limits for Price Variance when PO-based Purch.Requisition

We must garanty that Price from Purch.Requisition will be the same at PO.
IF some variance occur a error messag must be sent to user and PO could not be saved.
I found at customzing under SPRO > Materials Management > Purchasing > Purch.requisition > Set Tolerance Limits for Price Variance .
Reading the help of customizing it mean the system consists what we need..
I have created tolerance limit NB, and set limits for all checks as 0,01.
When I will activate messages as recommended on help no messages 601 and 602 have the text that guide us to correctly setting.
The help mention that after create tolerance limit we must set this tolerance by document type..but I didnt find this field at customzing
Does anyone can help me ?
See the help on customizing below
Set Tolerance Limits for Price Variance
In this step, you can define percentage-based and value-based (absolute) tolerance limits for price variances between purchase orders and purchase requisitions. Variance types are mapped out in the SAP system by tolerance keys.
You define the tolerance limits for each tolerance key and assign your tolerance key to the document types for purchase requisitions. The tolerance limit then applies for all documents of this document type.
When processing a purchase order, the system checks whether the unit price of a purchase order item differs from the unit price of a purchase requisition item. If you have configured, activated and defined tolerance limits in document types, variances are permitted in the tolerance limits. If the variance exceeds the tolerance limit, the system issues a warning. If you have defined a percentage-based and a value-based absolute tolerance limit, the strictest of the two variances will apply for this check.
Note
You can determine whether the system messages (601 and 602) appear as warnings or error messages in step "Define Attributes of System Messages".
To do this, go to the Materials Management IMG and choose Purchasing -> Environment Data -> Define Attributes of System Messages.
Requirements
The tolerance key must be defined in step Define Tolerance Key.
Activities
1. Define tolerance limits for each tolerance key.
2. Define the tolerance key in step Define Document Types.
Thx and best regards,
Ale

HI
SET TOLERANCE LIMITS FOR PURCHASE REQUISITION UNDER THE DEFINE DOCUMENTS FOR PR
AFTER SETTING TOLERANCE LIMITS WHILE CREATING PURCHASE U WILL GET BASED ON TOLERANCE LIMITS THERE FOUR WAYS TO SET TOLERANCE LITS
1
ABSOLUTE VALUE
2
PERCANTAGE
3
TOTAL PO VALUE
4
QUANITY BASED PRICE PER UNIT
OK BYE

Double line Item For Tax

Hi SAP Gurus,
I have a issue related to invoice verification.
We have following tax procedure
Basic Price + Excise + Frieght + VAT = Gross Price
But here frieght is taxable on which VAT is caluculated.
But while doing MIRO system is showing two line items for Tax condition (VAT)
1. One line item VAT amt calculated on (Basic price + Excise duty)
2. Second line item VAT amt calculated on (Frieght amt.)
I have maintained single line item in OBCN.
My client want to have single line item.
Pls tell me how to solve this.
Regards
Gitesh

Hi
DCGR means freight GR. System automatically creates this at the time of MIGO, if freight condition is mentioned in PO itself.
Hence in MIGO creation systems creates one material GR and with the same number one DCGR.
You can see it from purchase order history through PO.

Set Tolerance Limits for Price Variance for PR missing from SPRO

I'm looking into setting up tolerance limits for price variance at the PR level. But when i navigate here:
SPRO > Materials Management > Purchasing > Purch.requisition > Set Tolerance Limits for Price Variance
I'm not seeing that available in SPRO. It's available for PO's but not PR's. We want to be able to set tolerances on the PR to be applied to the PO for non stock items (material master). Please advise

Hi,
There is no standard configuration option to set the tolerance limit at PR level. You may set the tolerance limit for PO and control the price change. If you want the same functionality at PR level, then you have to go for development. Please check whether the BAdI: ME_PROCESS_REQ_CUST can fulfill your requirement. You may set the tolerance limit in OLME - PO - Set Tolerance Limits for Price Variance itself and write the logic in the BAdI to check the price variance in PR based on the same configuration (table T169G and similar).
You may check the similar thread: PR VS PO Price Tolerance
Regards,
AKPT

Single line item for multiple line item payment.

Hi
I have booked the 3 vendor invoices (in FB60) for a single vendor. Now today i paid (with F-53) all the three invoices together. One payment document number was generated.
However when i saw the vendor line item, i saw that three debit line items was generated for the clearing the open invoices (i..e 3 credit line items). so when i say vendor line item report, there were total 6 cleared line items (3 for credit i.e invoice and 3 for debit i.e. payments)
But is it possible to get single debit line item for all the three invoices cleared. If yes, please let me know how i can get it.
If i will have one single line item for payment, vendor report would be simpler. Please help

Hi,
1. If you do payment through F-53, then each invoice have separate payment line item. This is not avoidable. If you do payment through F110, then you can group the line items for payment, so there only one payment line item for many number of invoices.
2. While clearing through F-44, system is generating automatic line items because, there are exchange rate fluctuations. You can't avoid these line items, as these automatic line items only match Debit and Credit amounts in order to post the document.
Rgds
Murali. N

Mass change of payment in customer line item for all open line item.

Hello,
We have updated the new payment as per the new agreement with customer in customer master. We want this new payment term should also be updated in all the open invoices which are not cleared. Is there are way we can do the mass change in Payment term as the open line item in the customer where line item are more than 50. Please let me know the transaction code for the mass change of payment term in Customer account balances.
Thanks and Regards,
Rajesh Kumar Mantri

Hi
you can find the way to change the payment terms
first check weather the payment term field is having change option in your document change rules in the line item for you customers.
Financial Accounting (New)Financial Accounting Global Settings (New)DocumentRules for Changing DocumentsDocument Change Rules, Line Item
if the payment term BSEG-ZTERM(payment term) is there for your customer and having deselcted check box for changing document you cannot change payment term for your company code.
This can done client level or company code level.
if the payterm can be changed you do changes to payment terms mass level.
Thanks
ANJI

Issue with report (S_ALR_87013611) that is actual/plan line items for Cost

Hi Gurus,
I am having issue with the report (S_ALR_87013611) that is actual/plan line items for Cost Center.
When i execute the report for a cost element 510200 the amount is 23,380.13, but when i drill down on it by double click on that amount the value in obj curr is 15468.91. Hence there is the differnce. When i futher drill down by double click on the amont of 15468.91 and i go to display group currency and take the total it is 23380.13 and display in local / doc currency the amount is 15468.91. I guess due to this there is difference. The cost center & the cost elements are the same i have checket it.
My concerns is that the group curr is USD and obj curr / local curr is USD. So is group curr and doc curr is USD then when i click on dislay curr and select group curr why the amounts are changing.
Kindly adivce

Try to look if there is any filtering criteria applied in the report to which you drill-down.
The difference can be also caused by the "value type" - some reports show actual and statistical costs together in one column while the others strictly show (are defined to show) only e.g. actual costs (type 04) and not the statistical costs (type 11)

How can I add a new line item for production order?

HI all,
How can I add a new line item for production order through BAPI/FM? Thanks in advance.

Hi Mil,
Unfortunetly SAP is not in front of me.
But if possible go to BAPI transaction , check for any production order's bapi for CHANGE purpose. Where you will be able to add your new line.
Reward if useful!

Same material can exist on multiple line items for the same order.

Hi
Is there any specific customising setting or web shop setting through which we can restrict user to add same material on multiple line items for the same order ?
Regards

No.
But if this is a must requirement, you can do an elaborate check during order save in ORDER_SAVE BAdI and return error. So, it will be only during order save.
Eawar Ram
http://www.parxlns.com

How to Close a Purchase Order line Item for GRN W/O Deleting the Line Item

Hi,
I want to Close a line item for Goods Receipt in a Purchase Order. How Do I do this?
My Requirement is that the system should not allow for Goods Receipt for the Line Item.
I know of 2 options which are difficult to Implement.
1) I delete the Line item
2) Put the delivery Completed Indicator - For this the system still allows for GR
any Other way of Closing the line Item
NS

Hi, you can close the Line item by, doing partial GRPO, i.e if u use the Copy From option in GRPO, there comes a Draw docuemnt wizard, there you can choose one line item, and then put GRPO for that line item,
The Wizard comes only in the Copy From option,
Close the Line item, by right clicking on that Line item and then 'close Row'
Edited by: Gayathri Panneerselvam on Dec 19, 2008 10:25 AM

Line Item For Price Variance

Similar Messages

Maybe you are looking for