Unit price rounding issue

I'm from Australia. We have stock items some have 10% GST and some don't have. there is a rounding issue on SAP since 2005A. For example, we input $9.55 pre GST price ($10.50 is gst inclusive). When processing invoice, the gross price will display $10.51, a user has to change it to $10.50 manually. The more quanaity, the more rounding error. We check with our supplier, only temporary patch on it. Can standard SAP fix the rounding issue ?
Thanks
KC

normaly It will not happen .
have any add-on and FMS in same filed ? if not then make FMS to copy same data from Base document.
Thanks
Manvendra Singh Niranjan

Similar Messages

Net price rounding issue in PO

Hi,
Please note that I am facing net price rounding issue in PO.
For. e.g.
In a PO line item of Qty 25 PC of base price 6 INR, there is a discount of 3.64 INR.
So gross price = 150 INR (25*6)
Net value = 150 - 3.64 = 146.36
No net price = 146.36 / 25 = 5.8544
When we round of two decimal places 5.85 INR (since INR is two decimal curr)
When we show in PO output we will show like below
Material X 25 5.85 146.25 (this is calculated by multiplying qty with net price of 5.85 INR)
So there becomes a difference of .11 INR due to rounding issue.
Net value in PO and PO output are differing. Net price of material & net value should match exactly in PO & PO output
without any differences.
Please throw your views.
Note: can we make discount condition statistical & take it to separate G/L account during GRN?
Regards,
Partha

Hi,
As per the note 80193 rounding, I defined a condition type NETP and it captures the rounding difference.
So now netprice (after discount) * quanity = netvalue (after discount) relationship matches.
But my concern is that the rounding difference is not getting captured in G/L accounts (neither in GR/IR clearing account nor in separate accounts).
Please throw your comments.
Partha

Unit Price in Issue for Production for Item with wrong UoM

Dear All,
In issue for production the item cost being picked does not match either our Last Purchase Price or Price List1. In some cases the price considered is an average:
Eg:- For Item A with Purchase UoM in Nos. and Inventroy UoM in Gms, we had not enetred the conversion factor i.e 1 No=100g. Thus GRN was made for 25 Nos. @ Rs.450/Unit. But actual stock was 2500g. Hence to rectify the stock we made an OB entry for 2475 as on GRN date with zero Price. Thus total stock was 2500 and Value 25*450=RS.11250
When we did an Issue for Production for this item: Qty:400g, the unit price considered was Rs.28.125 when the actual price to be considered is Rs.450[Unit Cost]/100 [UoM Conversion]=Rs4.5. We had entered Rs.4.5 in Price List1 and had selected this price list in the BoM as we had not entered a conversion factor in the Item Master Data and SAP does not allow alterations to this tab once the Item is involved in transactions.
I think the system calculated the price as follows: (25450+14750)/400=Rs.28.175
How do we avoid/correct this in the future?

If you need the stock price correct, the only option might be creating a new item with correct information in the first place. Once you have error data to start with, there is no way to corrected as you wish.
Thanks,
Gordon

Price Rounding Issue - AFS Pricing

Hello Friends,
We are facing an issue in sales order pricing & its subsequent effect in invoice. We use AFS pricing, where different grid sizes have its basic price.
We have a basic price condition which come thru a master record, and this can be overridden by a manual price condition.
When such manual condition is entered, it applies to all the quantity of the line item irrespective of the number of grid sizes.
So suppose I had 6 grid sizes in the line item (which also results into 6 schedule lines) list price will be shown across all the grid sizes, see DOC1
But when I enter a manual price EUR 7, it applies to the total quantity that is 6. So the net value in this case will be EUR 7, See DOC2
By calculation, 7/6 = 1.166666666666667
So when now I create the invoice, the value gets rounded for all the grid sizes & it becomes 1.17
Here when system calculate the net value it will sum up 1.17, six times & the resultant net value is EUR 7.02, see DOC3
As a result most of the time there is difference between the order value & the invoice value.
Please suggest what action should be taken.
Regards,
Dhananjay Borate

Dear Dhananjay Borate,
You can avoid this issue working this the following options:
Every Condition Type, in the "Control Data Box 1" have the option to apply a "Rouding Rule" with three different options:
Empty.
                     In the standard rounding rule '_', values are rounded off according to business standards:
                         10.454 -> 10.45 DEM
                         10.455 -> 10.46 DEM
"A"
                    In rounding rule 'A', values are always rounded up:
                        10.459 -> 10.46 DEM
                        10.451 -> 10.46 DEM
"B"
                   In rounding rule 'B', values are always rounded down:
                      1045.9 -> 1045 LIT
                      1045.1 -> 1045 LIT
Also you can use, in the "Gruop Condition ", the Rounding difference comparison.
         Indicator that controls whether rounding difference is settled for group conditions with a group key routine. If the indicator is set, the system compares the condition value at header level with the total of the condition values at item level. The difference is then added to the largest item.
Use the Conditons Types:
PDIF - Diff.value (own)
DIFF - Rounding Offwith the Conditions that apply to your needs. The standard gives this ones as examples: [Requirement: Routine 13 - Rounding as perT001R], [Condition Formula 16] and [Basis Type 4]
Regards,
Johnattan.

Unit price in Invoice form(Rounding up issues)

Hi Gurus!
In my smartform I have used a formula to get the unit price of an item line which is giving me rounding up issues as it is calulating upto the 3 decimal places that I require in my output. Is it possible to grab the unit price field (KEBTR) directly into my form for the unit price so that I get the actual amount as in SAP into my invoice output rather than caluclting it in my code so that there is no discripancies.
Like it shows on my form sometimes 98.999 or sometime 99.001 instaed of 99.00 as is in under the condition tab of the invoice, I would like it to show straght as is in SAP 99.000 rather tahn doing caluction and coming to a smallest decimal value.
CLEAR: g_unit_price, g_min_charge_flag, g_item_tot, g_skto_kwert.
* get skto amount (Cash discount)
LOOP AT gt_konv INTO gs_konv WHERE kposn = gs_gen_del-itm_number AND
kschl = 'SKTO'. "Cash discount
g_skto_kwert = gs_konv-kwert.
EXIT.
ENDLOOP.
* For rental contracts there is no delivery so surcharges must be removed from net.
IF is_bil_invoice-hd_gen-bil_type = 'ZFV'.
CLEAR gs_gen_del-kzwi3.
LOOP AT gt_konv INTO gs_konv WHERE
kposn = gs_gen_del-itm_number AND
stunr BETWEEN 230 AND 289.
gs_gen_del-kzwi3 = gs_gen_del-kzwi3 + gs_konv-kwert.
ENDLOOP.
ENDIF.
g_item_tot = gs_gen_del-netwr - gs_gen_del-kzwi3.
IF gs_gen_del-fkimg <> 0.
g_unit_price = g_item_tot / gs_gen_del-fkimg.
ENDIF.
Thanks
Edited by: Aarav Agnihotri on Jun 11, 2009 6:58 PM

Hi Aarav,
Check this links
[Rounding|Rounding]
[Rounding off value|Re: Rounding off value]
Read Above for a clear idea about Rounding values.
[Rounding of the Values|Rounding of the Values]
[Quantity & Rounding condition values|Re: Quantity & Rounding condition values]
[Rounding down values|Re: Rounding down values]
For More results Search In SDN...
Thanks & regards,
Dileep .C

Unit price issues

HI!
In m my smartform Im getting the unit price for my invoice from the condition table directly instead of calculating it (Total / Quantity) which creates the rounding up issues. SO this works fine for us but the problem occurs when the condition pricing is like 300/ 1000 L or 4000/ 1000Kgs , what happens is that in the output the unit price and quantity when multiplied contradicts , though the net price per line item shows correctly but suppose qty is 3 L and the unit price is 300/1000L so total os .9 dollars which is correct but in the form out put it shows qty= 3 unit price 300 and total .9 dollrs, which si contracdictory, so what I did I used a calculation gaain and divided by condition price by condition pricing unit so when its 300/1000L it would show .3 /L which is now ok but another problem rose with metric ton, since the selling unit is MT and the unit price now after dividing by condition pricngi unit makes it per KG so output would show like qty =3 unit price 4 and total = 12000 dollars , so heer unit price is wrong as it should have been 4000/ Ton as the total os 12000 dollars.
Is theer a way out to show the correct unit pricing as per the sales unit. I had used the code to just divide the total price of line item divided by the Quantity but then the rounding up issues came up which was not required .
read table is_bil_invoice-it_kond into gs_kond
with key bil_number = gs_gen_del-bil_number
itm_number = gs_gen_del-itm_number.
if sy-subrc = 0.
g_unit_price = gs_kond-kbetr / gs_kond-kpein.
else.
** Loop around and get the price for it
loop at is_bil_invoice-it_kond into gs_kond
where bil_number = gs_gen_del-bil_number and
itm_number = gs_gen_del-itm_number.
    if gs_gen_del-fkimg <> 0.
         g_unit_price = gs_kond-kbetr / gs_kond-kpein.
      endif.
* g_unit_price = g_item_tot / gs_gen_del-fkimg.
    endif.
endloop.
endif.
* Get unit price and tot price.
g_item_tot = gs_gen_del-netwr - gs_gen_del-kzwi3.
*IF gs_gen_del-fkimg <> 0.
* g_unit_price = g_item_tot / gs_gen_del-fkimg.
*ENDIF.
thanks

Well we would ike to grab the unit price directly from the condition mentioned in the billing documents , thats the reason this issue has errupted , We would like to pull it directly from teh document onto the invoice but as I said when its given per 1000 L or /1000 Kgs then the problem occurs as teh quantity may be in MT and the unit price in the condition on document maybe like 4000 dollars per 1000 KGS so it takes 4000 and multiplies bny quantity which is in MT which is 1000 times more than teh correct value. SO as per my piece of code its grabbing the unit price directly from teh condition in the billing document . If I just divide this unit price that I am gettimng from the condition table in Doc by the condition rate KPEIN then it works ok except in few cases like MT. The quantity will show 3 MT suppose and the unit price will be 4000/1000 = $4/ kgs so this will contradict the units but in case of per 1000L it would be ok as the resultant will be in litres only but in case of MT its converted to Kgs so basically a client will see 3 MT QTY for 4 / Kgs and price will be 12000 dollars which dosent look alright though teh resultant is correct prioce.
SO this becomes a special case when we dont need to divide by condition unit rate . My question is can be give such kind of exceptions in our code and proceed or will be wrong.
Thanks

How to round unit price in XSL-FO Standard Purchase Order

I have been trying to round the unit price of the Standard Purchase Order stylesheet that is written in XSL-FO. Please could someone suggest I how I could achieve this? As my attempt have been unsuccessful. In the stylesheet the following line of code returns the unit price.
<xsl:value-of select="UNIT_PRICE"/>
Thank you,
Mark

I assume you are talking about number formatting:
You can use the XPATH function format-number:
<xsl:value-of select="format-number(UNIT_PRICE,"####.#")"/>
This will ONLY work if UNIT_PRICE is a correct XSL number (meaning no thousand seperator). Otherwise you can probabley remove the , out of say 1,234,567 using the
translate function translate(UNIT_PRICE,",","") - Please check any XSL reference for additional information.
Hope that helps,
Klaus

Unit Price after Discount/Rounding

For sales documents, we are currently using the Discount% column to include additional fees to an item's unit price. Ex: sales price list u/p of $0.60 * Discount of -5% = billed u/p of $0.63 (Price after Discount includes $0.03 hub fee). We have this setup as we are calculating commission based on the price list u/p. The above example rounds nicely, but the problem comes about when the figures are not even. For example an item with list price of 4.54 must be billed at 4.65. The resulting discount% is -2.4229074... Although rounding will show the correct u/p of 4.65, the row/doc total calculations will be carried out at 4.649999... For high volume orders, this will create a noticeable price discrepency. Is there a way to enter the Price after Discount field manually? Thank you.

Hi Allen,
Check in:
Administration -> System Initialization -> Document Settings -> Generla Tab:
'Calculate Row Total Using Unit Price'.
If this box is checked in 2005 the field 'Price after Discount' will not be active even if it is set as active in the Form Settings of the document.
In 2007 for a database that was created in 2007 this field cannot be activated as far as I know.
From what I remember a db that has been upgraded from 2005 to 2007 this field can still be activated.
I hope it helps.
Jesper

Unit price formula syntex issue in Contract line item

Hi All,
I have uploaded price condotion XML from SRM to Sourcing. I have defined integarted Master agreement and added 0ICT item price condition for service and materila. I was able to add line item and publish to SRM.
I tried creating new custom price condition in Sourcing adn saved. After this I am not able to add line item in master agreement. It is showing systex error in unit price formula under document setup->formula.
I faced this error in past when I haven't added item price condition in master agreement type as default for material and service.
I don't know what went wrong. I have inactivated the custom price condition, imported the standard SRM again via XML and deleted priviously added price condition from the master agreement type and defualt with new one but no luck. I tried creating new master agreement type also but same error.
Please let me know if anybody has faced the issue in past and able to fix it.
Regards,
Deepak

Hi Avinash,
Thank you very much dear...It is appearing in the report as you said.
I am wondering why it is not appearing in the standard Plan line item reports CJI4 or S_ALR_87013542 ? any clue.. Anyhow I have given points for your reply.
Thanks once again for ur reply..
Regards
Tajammul

Wrong Unit Price in a Good Issue Document using DI

Hi,
in my addon I want to create a new Goods Receipt document, using DI.
In the Lines, I set the ItemCode, I set the Quantity, and I set the Price, then I add the document, but when I go to Sap, in the Goods Receipt created, the Unit Price is wrong. I've try to set Quantity and LineTotal, Quantity and Price, Quantity Price and LineTotal but all the combinations is not correct, and the Unit Price is not equals to the price that I have set.
I have try to change the Price List, but nothing is happened.
This is my simple code:
Dim entrataMerce As SAPbobsCOM.Documents = myDB.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oInventoryGenEntry)
entrataMerce.CardCode = cardCode
entrataMerce.Series = series
entrataMerce.Lines.ItemCode = itemCode
entrataMerce.Lines.Quantity = 1
entrataMerce.Lines.Price = 100
entrataMerce.Lines.WarehouseCode = whsCode
entrataMerce.Add()
Where is the error?
Thanks
Marco

Instead of Price, try using UnitPrice? This is a confusing area of the DI :/

PO Unit Price issue

Hi Gurus.
Have the following scenario:
-- PO Qty is changed in Purchase order as per the Quantity delivered. In doing , the System automatically changes the Material Price
-- Hence when the last invoice is made with reference to PO, the System shows different price than the original one.
for example
1. The PO Qty was initially 462 KM and was changed to 458.7 KM. Hence the Unite Price changed to 40.65 from 40.62 as below
Gross price = 36.92 /KM EUR
Surcharges = 1710 (total)
Unit Price = 36.92+(1710/458.7) = 40.65/KM
2. The PO Qty was again changed from 458.7 KM to 444.4 KM as below
Now the unit price was revised to 36.92+(1710/444.4)= 40.77/ KM
Requirement: Unit price not to be changed even after the change in the quantity, pls confirm is it possibble
Thankyou very much

Hi,
As per standard SAP your requirement can't be met, please refer the Note 304178 - Absolute conditions in purchasing documents. I have pasted what is contained in the note, this cant be done.
Summary
Symptom
Absolute conditions, for example, used at item level in the purchase order item, are calculated down to the item quantity.For the goods receipt, if a quantity differing from the item quantity is posted, this absolute condition is nevertheless quantity-dependent since it is only calculated proportionally.
Other terms
Delivery costs, freight costs, freight, absolute value, FRB1
Reason and Prerequisites
For the goods receipt, the actual posted quantity is not yet available, as far as the program is concerned, at price determination.If the actual posted quantity is available later, the condition technique is not used again for the calculation.Therefore the only option remaining is the proportionalization of the condition values.
Solution
None.

Pricing Conditions Rounding Issue

Currently, our system has two pricing condition types. ZP,ZD. The ZP conditions represent a base price and the ZD represent a differential(- discount or + surcharge). Both are based on the same hierarchy. ZP00,ZP01,ZP02.ZP03,ZP04. A ZP01 overrides a ZP00 and ZP03 overrides ZP00, ZP01,ZP02 and so on and so forth. All transactions are settled in USD. However, most of the time the ZP, ZDs are based on prices that extend out more than two decimal places. I am experiencing and issue because SAP calculates the ZP and ZD separately and is rounding each. For example the ZP or base price in this case is $2.245. This times quantity of 3,999Gal = $8,977.755. SAP rounds this to $8,977.76. SAP then calcs. the differential ZD $.0235X3,999Gal = $93.9765. SAP rounds to $93.98. This is a total price of $8,977.76+$93.98 =$9,071.74. However the unit price is ZP $2.245 + ZD $0.0235 = $2.2685. If you take this price multiplied by the quantity $2.2685 X 3,999Gal = $9,071.7315. So the actual total price is off by 1ct because SAP treats the ZP and ZD as two separate calculations. I have seen various ideas on how to fix, from creating another pricing condition, to user exits. I was wondering if there was a preferred method? Or if there is a simpler solution?

Good Evening,
1. Please review OSS NOTE 80183 regarding Rounding.
   Values calculated in pricing are always rounded to the amount of
   decimal places which the used document currency owns. As subsequent
   processing steps setup on this rounded value rounding differences can
   occur in the calculation of the price per unit or in subtotal line.
   To bypass such effects note 80183 describes possible solutions to
   reduce / bypass this effect.
   A few problems in rounding after applying note 80183, variant 2 have
   been recorded where it was recommended to use the formulas 919 and
   920 on all discounts and surcharges that appear before NETP and the
   problem was solved.
2. In transaction V/06 there is a field under header 'Control data1'
   which can effect how the system rounds off condition values during
   pricing:
   ->> Rounding rule
       The rule that determines how the system rounds off condition
       values during pricing. The last digit will be rounded.
Example
o In the standard rounding rule '_', values are rounded off according
   to business standards:
   10.454 -> 10.45 DEM
   10.455 -> 10.46 DEM
o In rounding rule 'A', values are always rounded up:
   10.459 -> 10.46 DEM
   10.451 -> 10.46 DEM
o In rounding rule 'B', values are always rounded down:
   1045.9 -> 1045 LIT
   1045.1 -> 1045 LIT
   In this example, the currency of the condition rate is Italian Lira.
   The Italian Lira does not have any places after the point.
3. Also check if the condition type is set as item condition as well
   as group condition in transaction V/06. What this means is that
   the system will calculate the value of the condition on header level
   and compares it with the sum of item values in the document.
   Any rounding difference (KONV-KDIFF) detected, will be populated
   in the line item with greatest value or in first line item if all are
   of equal value.
   In other cases where there is no adjustment because there is no
   rounding difference when comparing the header value and the sum of
   item values.
   ->> Solution to this scenario -
       If you remove the 'group condition' setting, the system will then
       calculate amount for the items directly and you will not get the
       rounding. You must decide which setting is more suited for your
       business. This is not a bug, but works as per designed.
       EXAMPLE: MWST - tax condition (a group condition)
                Item 10     16%   of 100.90 = 16.14
                Item 20     16%   of 100.90 = 16.14
                                       Total = 32.28
I hope this helps you!
Kind Regards,
Martina McElwain
SD Forum Moderator

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?

Unit Price Format in XSL-FO Code for Standard Purchase Order Printing

Hi All,
As I am new to XSL-FO, so i am not aware of doing XML,XSL-FO changes. I have an issue with the xsl-fo for standard po layout. My report layout gives ##,## instead of ##.## as my Unit Price. i.e. in the report for POs, it is showing unit price in the format as #,## eg: 0,32 or u can say like 1,70 instead it should show #.## something like 0.32 and 1.70 as my unit price. The piece of code related to unit price formatting in report as follows:
<xsl:choose>
<xsl:when test="(UNIT_PRICE,1,1 > 1) and (substring-before(UNIT_PRICE,',') > 0)">
<fo:table-cell xsl:use-decimal-format="euro2"> <fo:table-cell xsl:use-attribute-sets="table.cell5"> <fo:block xsl:use-attribute-sets="form_data1">
<xsl:value-of select="format-number(substring-before(UNIT_PRICE,','),'#.###','euro2')"/>,<xsl:if test="(substring(substring-after(UNIT_PRICE,','),3,1)) > 4"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,','),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,','),3,1)) =''"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,','),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,','),3,1)) = 1"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,','),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,','),3,1)) = 2"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,','),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,','),3,1)) = 3"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,','),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,','),3,1)) = 4"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,','),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,','),2,1)) = ''"><xsl:value-of select="((substring(substring-after(UNIT_PRICE,','),1,1))-(substring(substring-after(UNIT_PRICE,','),1,1)))"/></xsl:if>
          </fo:block>
     </fo:table-cell>
</fo:table-cell>
</xsl:when>
<xsl:when test="(substring(UNIT_PRICE,1,1)=',')">
     <fo:table-cell xsl:use-attribute-sets="table.cell5"> <fo:block xsl:use-attribute-sets="form_data1">
     <xsl:value-of select="UNIT_PRICE"/>
     </fo:block>
     </fo:table-cell>
</xsl:when>
<xsl:when test="(UNIT_PRICE,1,1 > 1) and (substring-after(UNIT_PRICE,'.') > 0)">
<fo:table-cell xsl:use-decimal-format="euro2"> <fo:table-cell xsl:use-attribute-sets="table.cell5"> <fo:block xsl:use-attribute-sets="form_data1">
     <xsl:value-of select="format-number(substring-before(UNIT_PRICE,'.'),'#.###','euro2')"/>,<xsl:if test="(substring(substring-after(UNIT_PRICE,'.'),3,1)) > 4"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,'.'),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,'.'),3,1)) =''"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,'.'),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,'.'),3,1)) = 1"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,'.'),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,'.'),3,1)) = 2"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,'.'),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,'.'),3,1)) = 3"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,'.'),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,'.'),3,1)) = 4"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,'.'),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,'.'),2,1)) = ''"><xsl:value-of select="((substring(substring-after(UNIT_PRICE,'.'),1,1))-(substring(substring-after(UNIT_PRICE,'.'),1,1)))"/></xsl:if>
     </fo:block>
     </fo:table-cell>
</fo:table-cell>
</xsl:when>
<xsl:when test="(UNIT_PRICE,1,1 > 1 ) and (substring-after(UNIT_PRICE,',') ='') ">
<fo:table-cell xsl:use-decimal-format="euro"> <fo:table-cell xsl:use-attribute-sets="table.cell5"> <fo:block xsl:use-attribute-sets="form_data1">
<xsl:value-of select="format-number(UNIT_PRICE,'#,###.00','euro')"/>
          </fo:block>
     </fo:table-cell>
</fo:table-cell>
</xsl:when>
</xsl:choose>
PS: My decimal formats for euro and euro2 are:
<xsl:decimal-format name="euro" decimal-separator="," grouping-separator="."/>
<xsl:decimal-format name="euro2" grouping-separator="." NaN="0"/>
Any help or reply regarding this issue will be highly appreciated.
Regards,
Sumir

Hi Michele:
I can check out for you how to print page number in XSL-FO (There is an O'Reilly) book, but I think I help you better by recommending a different strategy - Don't write XSL-FO stylesheets. While Purchasing does not support RTF templates you can still write RTF templates and convert them to FO using the XML Publisher Template Builder for Word.
Download the matching Template Builder for Word (5.0) or XML Publisher Desktop 5.5 (includes the Template Builder) patch and then Create your template as an RTF template.
You can then EXPORT the template as XSL-FO stylesheet and upload as to Purchasing AS LONG AS THE VERSION OF THE DESKTOP and E-Businees Suite XML Publisher MATCH.
If you still want to write XSL stylesheet, you can just use the Template Builder to generate you the code and paste the code (e.g. for page numbers) into your stylesheet.
By the way - Purchasing will support RTF templates in future versions...
Hope that helps,
Klaus

Updating Unit Price in iProcurement

Hi All,
Updating Unit Price in i-proc requisitioned for non stock items.
To look in to how this should work out.
Currently users have to create a new requisition as this facility is not available.
What has to be done on the above said issue..?
Many thanks in advance and best regards,

what exactly are you trying to do? Non catalog items? How do you want the price updated? What do you mean by how this should work out?
Can you clarify your issue?

Unit price rounding issue

Similar Messages

Maybe you are looking for