Issue with Pricing in Invoice.

Hi,
I have one condition ZIST in my pricing. Whenever I create the invoice manually through VF01, all the items are showing up proper values of ZIST, however header is not showing the proper value (Header is showing the value which is suppose to be at the header minus correction value with respect to rounding off). But when I click on ACTIVATE button on the header pricing screen, system updates the correct value of ZIST.
If I dont click on activate button then Invoice gets saved with wrong ZIST value at the header.
I dont know how should I tackle this issue, Do I need to write a code somewhere to carru out the pricing again to update the right value of ZIST.
Edited by: sanjay kulkarni on Sep 22, 2009 4:00 AM

Thanks for ur response.
Actually in my case netwr value is correct and all the line items are also in good shape, problem is only with header level pricing, that too only one condition is showing wrong value and that needs ACTIVATE to click to get updated with correct value.
In my case its very diffucult to replicate the senario and the one example we have for testing is a huge invoice. Also my pricing procedure has many routines hooked to diffrent condition tyeps. Hence it would be tedious job to debug and see each and every routine from the pricing.
Still, I would try to do it. But I would appreciate if you can let me know what did your developer do wrong in the routines so that I would also concentrate on the same line.

Similar Messages

I have an issue with pricing condition ZPRO (basic price )

Hello gurus
I have an issue with pricing condition ZPRO (basic price ).
users created a sales order, and the basic price ZPRO which is mannual is added twice ,now i want to put a check so that condition tpye zpro is not accepted twice by the system. please let me know how can i restrict system from accepting condition type zpro twice during sales order.
regds
Edited by: sapuser09 on Jul 26, 2011 8:44 AM

Hi,
Solution for this is very simple. Don't make any changes to the sales order user exit. Use condition exclusion for the condition type.
Do customization in the following path of IMG
Sales and distribution---- > Basic Functions--- > Pricing--
> Condition exclusion -- > Condition exclusion for groups of conditions
First In Define condition exclusion groups you have to define condition exclusion group (ZXXX)
Then in Assign condition types to the exclusion groups you have to assign condition type to the exclusion group (ZXXX ZPRO)
Then in Maintain Condition exclusion for pricing procedures select the pricing procedure where you have the problem and click Exclusion box present in Dialog structure box
You will be faced with Change view exclusion overview screen Click new entries
You will be faced with New entries overview of added entries screen.
Take serial no as 10 Condition exclusion procedure as B (Best condition with in condition type) In the exclusion group1 add the exclusion group ZXXX.
Save it and create order.
In the order pricing you will again observe that ZPRO appearing twice but only one will be active.
Changing user exit for this issue is not at all required and it must be only the last resort Try replicating the issue in your sand box system. As I had mentioned it will be picked twice but only one will be active.
Hope this helps.
Edited by: mokirala tilak on Aug 10, 2011 10:19 AM

Issue during pricing in invoice

Hello everyone,
I have a question regarding pricing during invoicing.
We have a tax condition type used to calculate VAT on free goods sale. As we want tax to be computed based on 'sales order reason' entered during sales order, i created a new condition table with one of the fields as 'order reason' AUGRU assigned from structure KOMV. This table is assigned to existing access sequence and the tax based on order reason is correctly picked up during the order creation.
But this tax condition is missed during the billing creation. The copy control settings are set such that tax conditions are redetermined during billing. Hence the system is trying to redetermine the tax based on order reason. As it is failing to find the order reason during billing, the retrieval of condition record is failing.
I guess the issue is because the order reason is maintained at header level in order but at item level in invoice. In the field catalog of access seq, as i assigned AUGRU to header structure KOMV, the system is failing to find the order reason during invoice as its maintained at item level. I tried to assign AUGRU to item structure KOMP but that field is not available in KOMP.
Please let me know how to get around the problem.
Thanks,
Kits008

I have a full cycle testing.
Now, I understand where is problem occurred.
For sales order pricing, the order reason can pass to KOMK from order header and can be used in pricing determination procedure.
But for billing document, the order reason in "VBRP-AUGRU_AUFT", if you carry out a new pricing , then the system caused a problem like the post.
I suggest you implement the user exit (USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ))
If you have further problem, please reply the post.
Flex Yang
FI/CO, MM, SD Certificated

Rounding Issue with Pricing Conditions

Currently we have in place a pricing hierchery that consists of two pricing conditions. ZP for base price and ZD for a +-differential. Both conditions begin with 00. ZP00. ZP01, ZP03, ZP04. If a ZP01 exists it overrides a ZP00. If a ZP03 exists it overrides ZP00,ZP01, etc. So basically the higher the number means it overrides anything underneath it. The ZD conditions are setup exactly the same way. I am currently running into a round issue. We settle all transactions in USD however the manual and differentials are often based on prices that go out more than 2 decimal places. SAP is treating the calculation for the ZP and ZD as two separate calculations. It rounds each of them and then combines for a total price. So if the base price ZP02 is $2.245 multiplied by quantity 3,999 = $8,977.755 which it rounds to $8,977.76 and the differential ZD02 is $.0235 this = $93.9765 which it rounds to $93.98 for a total price of $9,071.74. However if you add the ZD02 + the ZD02 you get a total unit price of $2.2685. This multiplied times the quantity 3,999 = $9,071.731 which is correct. But because SAP does each calc separately the price comes out to $9,071.74 or off 1CT. I have seen various solutions on how to fix this from user exits to creating additional conditions that takes both ZP and ZD conditions and calculates them as one but I was hoping someone had come up with something better? Or if there was a preferred method?

Currently we have in place a pricing hierchery that consists of two pricing conditions. ZP for base price and ZD for a +-differential. Both conditions begin with 00. ZP00. ZP01, ZP03, ZP04. If a ZP01 exists it overrides a ZP00. If a ZP03 exists it overrides ZP00,ZP01, etc. So basically the higher the number means it overrides anything underneath it. The ZD conditions are setup exactly the same way. I am currently running into a round issue. We settle all transactions in USD however the manual and differentials are often based on prices that go out more than 2 decimal places. SAP is treating the calculation for the ZP and ZD as two separate calculations. It rounds each of them and then combines for a total price. So if the base price ZP02 is $2.245 multiplied by quantity 3,999 = $8,977.755 which it rounds to $8,977.76 and the differential ZD02 is $.0235 this = $93.9765 which it rounds to $93.98 for a total price of $9,071.74. However if you add the ZD02 + the ZD02 you get a total unit price of $2.2685. This multiplied times the quantity 3,999 = $9,071.731 which is correct. But because SAP does each calc separately the price comes out to $9,071.74 or off 1CT. I have seen various solutions on how to fix this from user exits to creating additional conditions that takes both ZP and ZD conditions and calculates them as one but I was hoping someone had come up with something better? Or if there was a preferred method?

Issue with release of Invoice in closed financial period

Hi All,
A billing document was created in Nov-2006 & because of wrong data maintained in the billing document , it was not released for accounting. This wrong data was corrected in billing document in Jan-2008 & it was subsequently released from block stage using VFX3.
But system has released this document in Nov,2006. As the books of 2006 are closed, i would like to reverse this release & then release the invoice for Mar-2008, to ensure the books of 2006 are not impacted.
If there is any other way to resolve this, please let me know.
Edited by: Vivek on Mar 13, 2008 9:29 PM

Hi,
Thanks for the inputs, if i post a cancel invoice, i would like to know what will be the impact in terms of FI as the invoice is actually of 2006, so what all impacts would i need to be aware of?
Vivek

Issue with Scale base routines in Pricing

Hi All,
This is regarding one issue I am facing in Invoice creation.
It happens randomly in some invoices (impact is in <5 % of invoices) that a discount condition value is incorrectly calculated when created through batch job.
This issue is not replicable in any of the lower environments.
When we cancel the invoice in produciton system and recreate it, the values are calculated correctly and we failed to replicate it even in production to find the root cause.
Here are the details:
We have a custom condition type which is a group condition (header as well as item) which is set in percentage where customer is supposed to get a discount (for eg. 1 % on the net price)
We have a Scale Base value routine which fetches the ‘scale base value’ from a custom table and assigns it to the item on the invoice (XKOMV-KSTBS).
All further calculation happens in standard SAP code where it checks the scales maintained in the condition record and applies the correct rate so the discount is applied accordingly.
Our pricing routine is working fine and is passing correct value to the scale base field.
The issue is in standard SAP code which applies the discount.
For all the impacted invoices, we have correct scale base values (fetched in our routine) but the corresponding discounts (KONV-KBETR and KONV-KWERT) are zero.
Only the last item in all the invoices shows a large negative value which is wrong .
Please guide me in finding the root cause.
Regards
Ritu

Hi,
These requirements should be met to fetch the condition record in the document.
1 = Different Payer
If this requirement is assigned to the condition type, the sold-to-party and payer should be different, so it will be picked up in the document.
2 = Item with Pricing
The item category of the item should be relevent for pricing.
3 = Foreign currency doc
The company code currency is derived from sales org in a sales document. But we can change the document currency in the sales document header also. And condition also can be maintianed in different currency. If this requirement is assigned, the company code currency and document currency should be different.
4 = Cost
If this requirement is set, the item should be relevent for cost determination (setting in item category)
5 = No Condit Exclusion
If this requirement is set, it will not consider the condition, if any condition exclusion is maintianed for it.
Prase

Pricing issue with Product hierarchy - Urgent

Hello,
I have an issue on pricing determination with product hierarchy.
I created product hierarchy as following,
level1 - A0001
level2 - A0001B0001
level3 - A0001B0001C0001
Then, assigned A0001B0001C0001 to material D in material master.
I created condition record with A0001B0001C0001(level 3), the system found the condition sucessfully when I created a sales order with material D.
However, I created condition record with A0001(level1) but the system didn't get the price when I created the sales order with material D. Since A0001B0001C0001 belongs to A0001, the system is supposed to get the price from the condition record with A0001...
Could you please let me know how to fix it?

Hi,
Thanks a lot for your kind explanation.
Here is the access sequence I defined. I wonder if there is anyway I can define PRODH1, PRODH2, PRODH3 in access sequnce the same way with customer hierarchy so that the system can check higher level data. If it's not allowed, I think I should define routine in requirement as you advised. Thanks!
*Accesses
AcNo       Description
1           Customer Hierarchy/Product Hiearchy
2           Customer Hierarchy/Product Hiearchy
3           Customer Hierarchy/Product Hiearchy
4           Customer Hierarchy/Product Hiearchy
Fields
AcNo   Condition    Doc. field      field lable
     1      HIENR      HIEBO01     CustomerHierarchy 01
             PRODH     PRODH       Product hierarchy
     2.     HIENR      HIEBO02     CustomerHierarchy 02
             PRODH     PRODH       Product hierarchy
     3      HIENR      HIEBO03     CustomerHierarchy 03
             PRODH     PRODH       Product hierarchy
     4       HIENR      HIEBO04     CustomerHierarchy 04
             PRODH     PRODH       Product hierarchy
I wonder if I can assign product hierachy fields, PRODH1, PRODH2, PRODH3 to access sequence like customer hierarchy so that the system can check higher level data to get the price...

Issue with cancelled invoice

Hi all,
We got an issue with cancelled invoices.
The user cancelled an invoice and in leiu of that created one more invoice against that.
When we extracted the deltas to BI, the cancelled invoice is appearing as cancelled Item wise but not the entire document is cancelled.
Please suggest what can be the issue and how to rectify this.
Regards
Kumar

Hi
Please check in the delivery document in VBUK and VBUP tables. Also check in the delivery document as the status showing 'C' should be Fully Picked and not fully invoiced.Also check the copy controls VTFL.Can you let us know what is the billing document type that has been used for cancelling billing document. Check in the F2 billing document type weather cancellation billing document type has been assigned or not.
Regards
Srinath

Issue with blocked invoices.

Hi All,
I am having an issue with few of our invoices are not releasing for payment.
Couple of them I noticed were due in June or July but were notpaid. These invoices were blocked due to price variance. Someone went and changed the price in P.O so the difference is within tolerance now. It should be released once 'MRBR' runs in batch everyday. but it's not.I dont see any reason it should be blocked now.
I know I can release it manually but we dont know how many are behaving this way.How should I find the reason why they are not getting released by MRBR.

Hi,
Do you have the workflow active?
Check transaction miro_workflow.
Cheers
Hein

Issue with VC/2 - not fetching the invoice details

Hi All,
We have an issue with TCode VC/2 in ECC 6. This is not fetching( not showing) the Invoice documents under the header "Last SD Documents".
It is fetching the sales documents like orders, credit memo/debit memo requests but not the invoice documents.
PLease help on this.
Thanks in advance.
Edited by: Harini Kesani on Jan 12, 2010 8:25 PM

Is it possible that 'last SD document' means 'last sales document', not 'last billing document'? Unfortunately, I'm unable to confirm - we don't use this transaction. You can also check what tables are used in this transaction (get help from an ABAPer or Basis) and then check if there is correct data in those tables. It might be using info structures or index tables, which may need to be populated first.

Issue with invoice

Hi Experts
I am facing an issue with invoice. When i am cancelling an invoice , the system is actually not clearing the accounting doc for original invoice and neither it is clearing the accounting doc for cancelled invoice.
Also if i see the customer line item of the accounting doc for the cancelled invoice , then instead of taking the posting key as 12 i.e. Reverse Invoice it is taking as 11 : Credit Memo which is quite unusual and as far as i know this is something standard and not modifiable.
Kindly let me know if you can suggest any solution or comments to this issue
Thanks

Hi,
Check copy controls in VTFF.
Cancelled invoice should have the original invoice number in header and original invoice should contain the cancelled tick at header.
Check if you are getting those status in the respective documents.
Also, your delivery or order with reference to which the invoice was created will become open or being processed.
Also try running std program for reorganization of status indexes in SE38 , program RVV05IVB.
Regards,
Amit

163; There seems to be an issue with the template that the site is using as there is a code to replace the pricing.

163;
There seems to be an issue with the template that the site is using as there is a code to replace the pricing.
<script>
// Script to extract the currency and decimals from the price
var price = "{tag_saleprice}";
var priceWithoutCurrency = price.replace( /^\D+/g, '')
var decimals = priceWithoutCurrency.substring(priceWithoutCurrency.length - 2, priceWithoutCurrency.length);
var roundedPrice = priceWithoutCurrency.substring(0, priceWithoutCurrency.length - 3);
$('.image-with-price.big span').html(roundedPrice+''+decimals+'');

Here are the screenshots for what it's worth.
Not sure why I can't post them in the original post. 
Mod edit: See [https://bugzilla.mozilla.org/show_bug.cgi?id=718813 bug 718813]
'''Again, when I set my DNS server to automatically detect the servers both problems disappear and I have no issues at all.'''
IMO opendns is either doing this on purpose (unlikely) or they're under some sort of attack/being used to attack the specific torrent sites although I'm open to other explanations. I believe using the automatic setting for DNS is using my own ISP's DNS servers (which again, work fine... but still...)
I'd rather not use Google's public DNS servers as Google is to commercial these days and I think there's potential privacy issues.
'''Again I have changed the setting for DNS servers back and forth several times to duplicate/verify the issue(s)... and the issues only happen with the opendns servers.'''

Issue with BAPI CONTRACT CREATE while uploading pricing conditions

Hi Experts
                    I am using BAPI CONTRACT CREATE to create Purchase Contract ME31K
I am facing the issue while passing pricing conditions Could you please help me regarding this
Could you please help me along with this what are the values has to pass
Thanks
Vijay Kumar Reddy

Hi Experts
                    I am using BAPI CONTRACT CREATE to create Purchase Contract ME31K
I am facing the issue while passing pricing conditions Could you please help me regarding this
      gs_oucondition-item_no = w_data-evrtp.
      gs_oucondition-serial_id = '1'.
      gs_oucondition-cond_count = '01'.
      gs_oucondition-cond_type = w_data-cond1.
      MOVE w_data-amnt1 TO gs_oucondition-cond_value.
      gs_oucondition-currency = w_data-curr1.
      gs_oucondition-numerator   = '1'.
      gs_oucondition-denominator = '1'.
      gs_oucondition-change_id   = 'I'.
      APPEND gs_oucondition TO gt_oucondition.
      CLEAR gs_oucondition.
      gs_ouconditionx-item_no = w_data-evrtp.
      gs_ouconditionx-serial_id = '1'.
      gs_ouconditionx-cond_count = '01'.
      gs_ouconditionx-item_nox = c_x.
      gs_ouconditionx-serial_idx = c_x.
      gs_ouconditionx-cond_countx = c_x.
      gs_ouconditionx-cond_type = c_x.
      gs_ouconditionx-cond_value = c_x.
      gs_ouconditionx-currency = c_x.
      gs_ouconditionx-numerator   = c_x.
      gs_ouconditionx-denominator = c_x.
      APPEND gs_ouconditionx TO gt_ouconditionx.
      CLEAR gs_ouconditionx.
Could you please help me along with this what are the values has to pass.
these are the parameters passing to the condition structure while executing bapi i am getting error like enter quantity conversion.
but with the same data i am able to create contract using SE37 by directly executing the Function module.
and if i have net price in my excel sheet also i am able to create contract using my program.
the only problem with pricing conditions alternatively there will be no net price..
Please really it will be a challenging question....
Thanks
Vijay Kumar Reddy

Issue in Pricing

Hi All,
We have an issue is we have created a credit memo with ref to the invoice, and Discount condition type has the value in the credit memo request. While creating the Creditmemo invoice Discount condition type is missing in the invoice means it was not copied from Creditmemo request (CR ) to Creditmemo (G2). Kindly advice what could be the issue? How to fix .
Thanks in advance..
regards,
SK

Hi Lakshmipathy,
Thanks for the reply. As per your i have checked the same but VOV8 and VOFA is having the same doc pri procedure. In VOKK Pricing procedure is assigned as ZSN0007. This one the one which was picked in the Credit note ( G2 ).
But Credit memo request ( CR ) created with reference to invoice, So the pricing procedure ZSN0002 from the invoice also copied in to the credit memo request. So Mismatch pricing procedures between Credit memo request and the Credit note.
First Question is if you try to create a Credit memo request with ref to Invoice F2, Will it copy the pricing procedure also? Basically we have differet pricing procedures for the std sales and the Credit/Debit memos.
Kindly advice how to solve the issue...
Regards,
SK

Return sales order( with ref. to Invoice) need to have less quantity

Hi Friends,
Here one issue is coming while creating a return sales order with ref. to invoice.
Example is:
In original invoice an article X is of price 10 having 10 quantity and hence total price 100.
but now customer wish to return only 5 articles and creating this Retun sales order with refernce to this invice
now in return sales order quantity is coming correct i.e 5 but the amount is still the same i.e 100.
But this should be 50( 5*10).
Please can someone help to find the reason why the price is not changing while quantity is changing.
I have already check the copy control but there also setting seems to be correct.
Also when i try to update the pricing via condition tab the price got changed. but that is manually.
Thanks
Punit.

Thanks Jignesh,
But can you please tell which pricing input should be the best.
As "price redetermine" option can't be selected as price keep changing.
also i did that for "same price and redetermine tax" but doesn't seems to be working.
Please if you can suggest any option where the price of the article will be same (the old one when article was sold) as proportionate to quantity without redetermining the price.
like article x has qty 10 and price 10 hence amount 100
but later price of article change to 11
then if i chose redetermine price then for five article this will be 55 which is again wrong( it should be 50 as at the time of sale the price was 10)
Hope I made the issue clear enough. Which setting in pricing one can recommend.
Regards
Punit
Thanks

Issue with Pricing in Invoice.

Similar Messages

Maybe you are looking for