Rounding value for abetment

Dear Expert
We want to map the rounding value for abetment per unit of material , presently we have created a condition type zmrp which represent market price value and abetment is calculated on the basis of ZMRP which 65%of ZMRP . e.g
for a x material 17.50 ZMRP
Abetment condition type value is 65% of ZMRP =11.375 we want here system should round up the value 11.38 and calculate the value accordingly but what system is doing presently is that it round up the condition value as whole not for indivual unit . WE want round up before multiplying the qunaity of productsnot after.i.e unit value system should round up
Regards

Hi,
Create a new Alternate calculation base value routine using VOFM. This routine should calculate the base value for the condition type as round to commercial value for the unit price. Assign this routine to your condition type in V/08 customization in alt. calculation base value field. This way SAP will first calculate unit rounded price and then will multiply that price to the order quantity to calculate final price as you desired. Let me know if you need a more help on the same.
Thanks
Kapil Sharma

Similar Messages

Rounding value for purchase order quantity

Hi Guru ,
i need help for logic LOT SIZE MRP.
In particolar i need of use the parameters of rounding for create the planned order multiple of the value.
Example for a requirement of 3800 pz whit a value rounding of 500 i vould want that the system create a planned order of the 4000pz.
I have tried insert this value 500 in the field "Rounding value for purchase order quantity" in the view MRP1 but after run MRP the system create a planned order of the same quantity of the requirement.
Thanks a lot for help
Daniele
PP TEAM

Dear,
OMI4, for lot size select Lot for lot order qty with rounding.
Either you can use the Rounding Value or you can use a Rounding profile in MRP2 view to round of your order qty and rouding value in MRP1 view.
Further you can check
Check FM MD_ROUNDING_VALUE
Regards,
R.Brahmankar

Rounding value for PR Quantity

Dear Expert,
Can we have rounding value for order quantity in Purchase Requisition? So we do not need to calculate the PO quantity based on the rounding value we have determined in material master / get the error message "Order quantity violates rounding rules while we creating the Purchase order.
And What is rounding profile? can we use this to set the rounding value for PR quantity?
Hope to see ur feedback soon.
Thanks
Pauline

Hi Dick Hua,
Thanks for your feedback.
i understand what you are trying to explain to me , can we do some changes / customizing from your statement, so that the manually created PR can have effect on rounding value, same as when we run the MRP.
Can you tell me What is rounding profile used for? can I used rounding profile to solve my customizing?
Thanks
Pauline

Rounding value for direct procurement

Hi,
I an sourcing the same material from another plant within the same client. The materiale is some times purchased as a standard material using rounding value and going to stock. But, in some cases the material is procured as direct procurement. When purchasing for direct procurement will it then be possible not to use the rounding value but just order the exact quantity?
thanks,
Anders

Hi Andres,
I think, you do not need to take any action on this requirement. SAP works the way you wanted, by standard. For example, you have a setup with a vendor (may be via info record or material master itself may have rounding qty etc)...not a problem. The parameters you use in material master will control for procurement process either triggered from planning (or production ) or manual purchases. When you create a SO# and if it triggers a purchase requisition, it sends exact quantity required only, into the preqs. By standard SAP config, the message about rounding rules is just warning. I don't think you will be stuck with this message when you try to convert the 3rd party Preq to PO. Even if there is a message, it must just warning.
Let me know with these inputs, if you test both types of PO#s, how it goes.
Regards

Rounding values for display

Hi all hope you can help.
I have a numeric DB column say 566785.8975. The value of the information in the column cant be changed. The application performs two functions data input for the owners and view for the customers.
Idealy I want to only display to two decimal points for the customers
I have tried using the the ROUND command with no success using source as a PL/SQL expression or function and a value of ROUND(GROSS,2) where GROSS is the column name
any ideas?
Thanks

Hi Bjorn - the problem with the TO_CHARing (having suggested it in the first place - sorry) is if you want to use automated row processing to update the page.
However, you could have an item (your gross_read_only) which is not linked to a DB column, and then all your automated fetches and updates would work fine.
You can set the value of this item using a SELECT statement within the item source, or a computation when the page is rendered.
In either case, SELECT just the read_only item (TO_CHAR it as described), and I see no reason why it shouldn't work.
In other words - for the item source:
SELECT to_char( GROSS, '999G999G999G999G990D00') GROSS_READ_ONLY
FROM TABLE
where ID = :P1_ID_ITEM
or in a PL/SQL item computation:
declare
l_value VARCHAR2(4000);
begin
select to_char(GROSS, 'FML999G999G999G999G990D00') into l_value
FROM TABLE
where ID = :P1_ID_ITEM;
return l_value;
(or :P1_READ_ONLY_ITEM := l_value in a page computation)
end;
Does this help?
John.

BADI for Changing Deployment Rounding Value

Hello All,
During my Deployment run I need to consider the rounding value from the /sapapo/marm table and not from the product master. So I need a badi or user exit to change the rounding value for deployment run. Do let me know how I can achieve this.
Thanks,
Siva.

Dear Tiemin,
Thanks for your reply. But I need a BADI which needs to work when there is no Fair Share situation. It will be great if you provide me which suits for it.
Thanks,
Siva.

Report Region rounding numbers for no apparent reason

I have a report region. It is a function returning query. The results are consistently displaying rounded values for the dollar amounts. The format for the number mask is FML999G999G999G999G990D00 . The query is shown below. I am at a loss for why this is happening. Any help is greatly appreciated...
Adam
DECLARE
str_Query VARCHAR2(2000);
BEGIN
str_Query := 'SELECT xatr.Refund_ID, '||
'xatr.Refund_ID, '||
'xatr.Invoice_Header_ID, '||
'xatr.Line_Description, '||
'xatr.Refund_Amount, '||
'xatr.Interest_Amount, '||
'xatr.Refund_Total, '||
'xatr.Date_Paid, '||
'xatr.Check_No '||
'FROM XXMC_AP.XXMC_AP_TAX_RECONCILIATION@'||:P0_INSTANCE||' xatr, '||
'XXMC_AP.XXMC_AP_TAXREF_INTERIM@'||:P0_INSTANCE||' xati '||
'WHERE xatr.Refund_ID = xati.Refund_ID '||
'AND ( xati.Process_Step = ''Loading'' '||
'OR xati.Process_Step = ''Reconciling'')';
RETURN str_Query;
END;

I was working with two different tables. The first table contained all the data. The second table contained a subset that was populated by a stored procedure. The second table, which was where the rounding was coming from, had the number fields setup with a precision of 15. This forced the number to an integer and the apparent rounding. I removed the precision and it worked fine.

Can't find roundness setting for rounded rectangle (CS5)

I know I'm missing something obvious, but I can't seem to find the control to set the roundness value for a rounded rectangle.
Per help, there should be a roundness control in the properties window, but I've been looking for 15 min. and can't seem to find it.
tia,

Thanks Linda. I was clicking on the yellow dots but somehow avoided sliding them...
And I missed Auto Shape Properties, as opposed to the Auto Shapes window.
A Fireworks 4 user is like a rube in the big city for the 1st. time...
-williamc

Need rounding off value for partial Goods receipt

Hi,
My requirement is that the PO value,PO tax value ,GR value and Invoice value(IR) should get rounded off.
When I am using the PO value which is rounded off in PO, but at the time of posting partial goods receipt the value for the GR/IR clearing or the stock value is not getting rounded off for these G/ls.
What should I do for this to get the rounded off values in GR.
Regards,
Goraksh

Hi Goraksh,
The problem is that the pricing (incl. the rule 17) is not normally called at the time of GR. As Jürgen wrote, the system just uses the "net value" field of the PO.
I have however a "wild" idea. If the price in the PO comes from the info record or from a contract (and not changed manually there), then you can set the "pricing date category" = 5 there, meaning "GR date". This causes the pricing to be called again at the time of GR and your formula 17 will fire.
The side effect of course is that the price that you had in the PO, printed and sent to the vendor will not be binding: if you change the PIR price before the GR, the GR will be posted to the new PIR price, despite the fact that the PO printout showed something else. So the question is if the price printed on the PO is indeed binding in your business case - in many business cases it is the current vendor price that matters for the billing by the vendor, not the one that you prined on the PO. For such business cases you should have had pricing date category 5 anyway...
BR
Raf

Rounding Value is not considered for MB lot size

Hi
I have a scenario where MB (Monthly Lot size) lot size is used with rounding value. Example as below:
Lot size: MB
Min Lot size: 15000
Rounding Value: 20000
DEMAND: 16000
When MRP run, System is creating the 16000 as P Req instead of 20000 which is the rounding value.
Pl let me know, if I need to apply OSS note / any other solution for this.
Thanks,
JK
Edited by: Janakiram Katakam on May 17, 2010 4:57 AM

Dear ,
Are you using any Rouding Profile in MRP1 view ?
What is the Setup in OMI4 for MB-Lot Size .Remove the tick mark in Last Lot Exat if it is marked .By specifing the rounding value, the system will determine during lot size calculation that lot size qty is a multiple of of an order unit(eg : pallet size if mtrl is delivered in entire pallets...).
Please check what is the Lot Size Indicator or Lot size procedure assinged to it ?
2.you can use rounding profiles...its used to define the setting of rounding up or rounding down the order proposal qty into deliverable quantities...rounding profile maintenance the t-code is OWD1. Here for static rounding profile
Rounding profiles are defined under:
spro-> purchasing->consumption based planning->planning->lot size calculation ->maintain rounding profiles...
it consist of threshold value and rounding value...
the threshold val is the value from which the system rounds the value of the next deliverable units upto...
the rounding value is from which the systemshd round up to as soon as threshold value is exceeded...
Otherwise , Check FM MD_ROUNDING_VALUE
Regards
JH
Regards
JH

Displaying blank value for the Rounding Value field in MM03 transaction

Hello All,
We are using BDC to create a material master record.Some users are not loading the rouding value in the MRP1 screen. The rounding value is stored in the MARC table which has the data type as QUAN. Thus when there is no value being passed it implicitly converts the blank value to 0.00. The users do not want the rounding value to be displayed as 0 when they view the material record using mm03. Kindly let me know if there is any way to display the rounding value as blank if no value is present.
Thanks in Advance.
Regards,
Avinash Sai N S

Hai siddharth,
I have enabled the BADi HRPBSIN_ADDITIONAL_CHECKS to do validations for loans. Can u pls explain is there any FM or wat can be used to set default value for the field in portal.
Pls give some suggestions,
thnaks,
Nalla B.

How to get rounding diffrence for agreement?

I am passing 3 parameters to this function
1.Agreemnt number
2.Start date
3.End date
I want to calculate Rounding difference for the each agreement.
Here Problem is, when executing this function; I am getting correct value first time.
While executing second time it thing, it shows different value as result.
Can anybody solve this?
Or give me another idea to get rounding difference instead of using this function?
FUNCTION ysdf_rebate_settlement_amount.
""Local Interface:
*" IMPORTING
*" VALUE(IV_AGREEMENT) TYPE KNUMA
*" VALUE(IV_FROM_DATE) TYPE DATUM
*" VALUE(IV_TO_DATE) TYPE DATUM
*" EXPORTING
*" REFERENCE(EV_ACCRUED_AMOUNT) TYPE KWERT
*" REFERENCE(EV_SETTLED_AMOUNT) TYPE KWERT
*" REFERENCE(EV_ACCR_REV_AMOUNT) TYPE KWERT
*" EXCEPTIONS
*" NO_AGREEMENT
*" NOT_SALES_VOL_DEPENDENT
*" OTHER_ERRORS
DATA:
 lv_accrued_amt TYPE kwert,
 lv_settled_amt TYPE kwert,
 lv_reversal_amt TYPE kwert,
 lv_kawrt TYPE kawrt,
 lv_kbetr TYPE kbetr,
 lv_kstbs TYPE kstbs,
 lv_kwert TYPE kwert,
 lv_datab TYPE datum, "Start date
 lv_datbi TYPE datum, "End date
 lw_kona TYPE kona,
 lw_t6b1 TYPE t6b1,
 lw_konp TYPE konpdb,
 lw_s060 TYPE s060,
 lt_konp TYPE STANDARD TABLE OF konpdb,
 lt_s060 TYPE STANDARD TABLE OF s060,
 lt_scales TYPE STANDARD TABLE OF condscale,
 lt_xvakes TYPE STANDARD TABLE OF vakevb.
CLEAR :
 ev_accrued_amount,
 ev_settled_amount,
 ev_accr_rev_amount.
Validate agreement number and get agreement details.
SELECT SINGLE *
 INTO lw_kona
 FROM kona
 WHERE knuma = iv_agreement
 AND abtyp = c_abtyp_a. "Rebate Agreement
IF sy-subrc NE 0.
Rebate agreement & does not exist!
 MESSAGE e061(yfr2sd) WITH iv_agreement
 RAISING no_agreement.
ENDIF.
SELECT SINGLE * FROM t001
 WHERE bukrs = lw_kona-bukrs.
Start date = later of the requested start date
and the agreement start date.
IF iv_to_date > lw_kona-datbi.
 lv_datbi = lw_kona-datbi.
ELSE.
 lv_datbi = iv_to_date.
ENDIF.
End date = earlier of the requested end date
and the agreement end date.
IF iv_from_date < lw_kona-datab.
 lv_datab = lw_kona-datab.
ELSE.
 lv_datab = iv_from_date.
ENDIF.
Retrieve configuration data once and keep in global variables
for better performance when repeated calls are made.
IF r_kobog_excl[] IS INITIAL.
 PERFORM get_global_data.
ENDIF.
Agreement must be completely dependent on sales volume.
IF lw_kona-kobog IN r_kobog_excl.
 MESSAGE e062(yfr2sd) WITH iv_agreement
 RAISING not_sales_vol_dependent.
ENDIF.
Get a list of condition record numbers for the given agreement
PERFORM get_condition_numbers USING lw_kona iv_from_date iv_to_date.
Read condition records and scales.
CALL FUNCTION 'SD_KONP_SELECT'
 EXPORTING
 scale_read = 'X'
 TABLES
 condition_item = lt_konp
 condition_number = r_knumh
 condition_scale = lt_scales.
Accrual amount calculation for all conditions.
LOOP AT lt_konp INTO lw_konp.
 konp = lw_konp.
 CLEAR lw_s060.
Determine the turnover for rebate
 CALL FUNCTION 'SD_BONUS_TURN_OVER'
 EXPORTING
 agreement_waers = lw_kona-waers
 condition_krech = lw_konp-krech
 condition_item = lw_konp-kopos
 condition_number = lw_konp-knumh
 period_datab = lv_datab
 period_datbi = lv_datbi
 agreement_knuma = lw_kona-knuma
 IMPORTING
 turn_over = lw_s060.
Errors?
 IF NOT lw_s060 IS INITIAL AND
 lw_s060-krech IS INITIAL.
 MESSAGE e779(vk) RAISING other_errors.
 ENDIF.
If condition is active (not logically deleted).
 IF lw_konp-loevm_ko = space.
record found?
 IF lw_s060-knumh IS INITIAL.
 lv_kstbs = 0.
 lv_kawrt = 0.
 ELSE.
 lv_kawrt = lw_s060-kawrt_k.
 lv_kstbs = lw_s060-kstbs.
 ENDIF.
 IF lw_konp-stfkz = 'D'.
Tiered scales calculation
 CALL FUNCTION 'SD_GRADUATED_SCALE_EVALUATION'
 EXPORTING
 i_arrangement = lw_kona
 i_condition_record = konp
 i_scale_base = lv_kstbs
 i_condition_base = lv_kawrt
 i_bukrs = lw_kona-bukrs
 i_currency_date = lv_datbi
 i_value_rounding = c_yes
 i_t001 = t001
 IMPORTING
 e_arrang_value = lv_kwert
 TABLES
 t_condition_scale = lt_scales
 EXCEPTIONS
 error_message = 1.
 ELSE.
Determine condition rate (non-tiered calculation)
 CALL FUNCTION 'SD_BONUS_RATE_FROM_SCALE'
 EXPORTING
 condition_record = konp
 scale_base = lv_kstbs
 IMPORTING
 bonus_rate = lv_kbetr
 TABLES
 condition_scale = lt_scales.
Determine rebate amount for the condition
 CALL FUNCTION 'SD_BONUS_VALUE_CALCULATION'
 EXPORTING
 calculation_rule = lw_konp-krech
 condition_base = lv_kawrt
 condition_type = lw_konp-kschl
 currency = lw_kona-waers
 currency_date = lw_kona-datbi
 price_currency = lw_konp-konwa
 price_unit = lw_konp-kpein
 price_uom = lw_konp-kmein
 cumul_currency = lw_konp-kwaeh
 rate = lv_kbetr
 sales_organization = lw_kona-vkorg
 IMPORTING
 bonus_value = lv_kwert
 EXCEPTIONS
 error_message = 01.
 ENDIF.
 IF sy-subrc <> 0.
Error?
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4
 RAISING other_errors.
 ENDIF.
Percentage?
 lv_accrued_amt = lv_accrued_amt + lv_kwert.
 clear lv_kwert.
 IF lw_s060-krech NE c_krech_a.
 lv_reversal_amt = lv_reversal_amt + lw_s060-rrwrt.
 ENDIF.
 ELSE.
Clear the values
 CLEAR: lv_kawrt, lv_kstbs, lv_kwert, lv_kbetr.
 ENDIF.
ENDLOOP.
SELECT SUM( vbap~netwr )
 INTO lv_settled_amt
 FROM vbak
 INNER JOIN vbap
 ON vbapvbeln EQ vbakvbeln
 INNER JOIN vbkd
 ON vbkdvbeln EQ vbakvbeln
 WHERE vbak~knuma = lw_kona-knuma
 AND vbak~auart IN (c_auart_b1,c_auart_b3)
 AND vbap~abgru EQ space
 AND vbkd~fbuda BETWEEN iv_from_date
 AND iv_to_date
ev_accrued_amount = - lv_accrued_amt.
ev_settled_amount = lv_settled_amt.
ev_accr_rev_amount = lv_reversal_amt.
ENDFUNCTION.
Regards,
Ronn

Can you provide more details that's a very vague question. You research industry vendors such as MobileIron, Zenprise, AirWatch, BoxTone, etc. or configure your own server and push configuration profiles. Apple themselves do not offer any services of their own that they resell.

Java returning incorrect values for width and height of a Tiff image

I have some TIFF images (sorry, I cannot post them b/c of there confidential nature) that are returning the incorrect values for the width and height. I am using Image.getWidth(null) and have tried the relevant methods from BufferedImage. When I open the same files in external viewers (Irfanview, MS Office Document Imaging) they look fine and report the "correct" dimensions. When I re-save the files, my code works fine. Obviously, there is something wrong with the files, but why would the Java code fail and not the external viewers? Is there some way I can detect file problems?
Here is the code, the relevant section is in the print() routine.
* ImagePrinter.java
* Created on Feb 27, 2008
* Created by tso1207
import java.awt.Graphics2D;
import java.awt.Image;
import java.awt.print.PageFormat;
import java.awt.print.PrinterException;
import java.io.File;
import java.io.IOException;
import java.util.Iterator;
import javax.imageio.ImageIO;
import javax.imageio.ImageReader;
import javax.imageio.stream.FileImageInputStream;
import javax.imageio.stream.ImageInputStream;
import com.shelter.io.FileTypeIdentifier;
public class ImagePrinter extends FilePrintable
 private final ImageReader _reader;
 private final int _pageCount;
 private final boolean _isTiff;
 //for speed we will hold current page info in memory
 private Image _image = null;
 private int _imgWidth = 0;
 private int _imgHeight = 0;
 private int _currentPage = -1;
 public ImagePrinter(File imageFile) throws IOException
 super(imageFile);
 ImageInputStream fis = new FileImageInputStream(getFile());
 Iterator readerIter = ImageIO.getImageReaders(fis);
 ImageReader reader = null;
 while (readerIter.hasNext())
 reader = (ImageReader) readerIter.next();
 reader.setInput(fis);
 _reader = reader;
 int pageCount = 1;
 String mimeType = FileTypeIdentifier.getMimeType(imageFile, true);
 if (mimeType.equalsIgnoreCase("image/tiff"))
 _isTiff = true;
 pageCount = reader.getNumImages(true);
 else
 _isTiff = false;
 _pageCount = pageCount;
 public int print(java.awt.Graphics g, java.awt.print.PageFormat pf, int pageIndex)
 throws java.awt.print.PrinterException
 int drawX = 0, drawY = 0;
 double scaleRatio = 1;
 if (getCurrentPage() != (pageIndex - getPageOffset()))
 try
 setCurrentPage(pageIndex - getPageOffset());
 setImage(_reader.read(getCurrentPage()));
 setImgWidth(getImage().getWidth(null));
 setImgHeight(getImage().getHeight(null));
 catch (IndexOutOfBoundsException e)
 return NO_SUCH_PAGE;
 catch (IOException e)
 throw new PrinterException(e.getLocalizedMessage());
 if (!_isTiff && getImgWidth() > getImgHeight())
 pf.setOrientation(PageFormat.LANDSCAPE);
 else
 pf.setOrientation(PageFormat.PORTRAIT);
 Graphics2D g2 = (Graphics2D) g;
 g2.translate(pf.getImageableX(), pf.getImageableY());
 g2.setClip(0, 0, (int) pf.getImageableWidth(), (int) pf.getImageableHeight());
 scaleRatio =
 (double) ((getImgWidth() > getImgHeight())
 ? (pf.getImageableWidth() / getImgWidth())
 : (pf.getImageableHeight() / getImgHeight()));
 //check the scale ratio to make sure that we will not write something off the page
 if ((getImgWidth() * scaleRatio) > pf.getImageableWidth())
 scaleRatio = (pf.getImageableWidth() / getImgWidth());
 else if ((getImgHeight() * scaleRatio) > pf.getImageableHeight())
 scaleRatio = (pf.getImageableHeight() / getImgHeight());
 int drawWidth = getImgWidth();
 int drawHeight = getImgHeight();
 //center image
 if (scaleRatio < 1)
 drawX = (int) ((pf.getImageableWidth() - (getImgWidth() * scaleRatio)) / 2);
 drawY = (int) ((pf.getImageableHeight() - (getImgHeight() * scaleRatio)) / 2);
 drawWidth = (int) (getImgWidth() * scaleRatio);
 drawHeight = (int) (getImgHeight() * scaleRatio);
 else
 drawX = (int) (pf.getImageableWidth() - getImgWidth()) / 2;
 drawY = (int) (pf.getImageableHeight() - getImgHeight()) / 2;
 g2.drawImage(getImage(), drawX, drawY, drawWidth, drawHeight, null);
 g2.dispose();
 return PAGE_EXISTS;
 * 
 * Created By: TSO1207 - John Loyd
 * @since version XXX
 * @return
 public int getPageCount()
 return _pageCount;
 public void destroy()
 setImage(null);
 try
 _reader.reset();
 _reader.dispose();
 catch (Exception e)
 System.gc();
 * 
 * Created By: TSO1207 - John Loyd
 * @since Mar 25, 2008
 * @return
 public Image getImage()
 return _image;
 * 
 * Created By: TSO1207 - John Loyd
 * @since Mar 25, 2008
 * @return
 public int getImgHeight()
 return _imgHeight;
 * 
 * Created By: TSO1207 - John Loyd
 * @since Mar 25, 2008
 * @return
 public int getImgWidth()
 return _imgWidth;
 * 
 * Created By: TSO1207 - John Loyd
 * @since Mar 25, 2008
 * @param image
 public void setImage(Image image)
 _image = image;
 * 
 * Created By: TSO1207 - John Loyd
 * @since Mar 25, 2008
 * @param i
 public void setImgHeight(int i)
 _imgHeight = i;
 * 
 * Created By: TSO1207 - John Loyd
 * @since Mar 25, 2008
 * @param i
 public void setImgWidth(int i)
 _imgWidth = i;
 * 
 * Created By: TSO1207 - John Loyd
 * @since Mar 25, 2008
 * @return
 public int getCurrentPage()
 return _currentPage;
 * 
 * Created By: TSO1207 - John Loyd
 * @since Mar 25, 2008
 * @param i
 public void setCurrentPage(int i)
 _currentPage = i;
}Edited by: jloyd01 on Jul 3, 2008 8:26 AM

Figured it out. The files have a different vertical and horizontal resolutions. In this case the horizontal resolution is 200 DPI and the vertical is 100 DPI. The imgage width and height values are based on those resolution values. I wrote a section of code to take care of the problem (at least for TIFF 6.0)
 private void setPageSize(int pageNum) throws IOException
 IIOMetadata imageMetadata = _reader.getImageMetadata(pageNum);
 //Get the IFD (Image File Directory) which is the root of all the tags
 //for this image. From here we can get all the tags in the image.
 TIFFDirectory ifd = TIFFDirectory.createFromMetadata(imageMetadata);
 double xPixles = ifd.getTIFFField(256).getAsDouble(0);
 double yPixles = ifd.getTIFFField(257).getAsDouble(0);
 double xRes = ifd.getTIFFField(282).getAsDouble(0);
 double yres = ifd.getTIFFField(283).getAsDouble(0);
 int resUnits = ifd.getTIFFField(296).getAsInt(0);
 double imageWidth = xPixles / xRes;
 double imageHeight = yPixles / yres;
 //if units are in CM convert ot inches
 if (resUnits == 3)
 imageWidth = imageWidth * 0.3937;
 imageHeight = imageHeight * 0.3937;
 //convert to pixles in 72 DPI
 imageWidth = imageWidth * 72;
 imageHeight = imageHeight * 72;
 setImgWidth((int) Math.round(imageWidth));
 setImgHeight((int) Math.round(imageHeight));
 setImgAspectRatio(imageWidth / imageHeight);
 }

How to display rounding value in sales order

hi
i maintained each and everthing functionality in pricing procedure but it is not showing value of condition type DIFF while creating sales order so can explain this

Hello Kamesh,
i maintained each and everthing functionality in pricing procedure
but it is not showing value of condition type DIFF while creating
sales order so can explain this
For the Rounding Condition Type "DIFF", the main controlling paramters are Requirement :-13(Rounding as perT001R), Alt Calculation Type :-16(Rounding the total) and Alt Base :-4(Net value + tax). Hope the table T001R(Rounding Rules for Company Code and Currency) has rounding entries for the combination of Company code and Currency.
Kindly carry an analysis based on these above points and post an update here.
Regards,
Sarthak

How to use rounded values in BEx Formulas

Hello,
I have the following question. Is it possible to use rounded values up to a certain # of decimal points in BEx Formulas?
I have the following problem.
Consider this:
keyfigure val 1 = 0.416666667
keyfigure val 2 = 72
val 3 (BEx Formula) = val 2 / val 1 = 172.799999862
However, what I need to do is this.
val 1 & val 3 should rounded up to 2 decimal points. So, I really need the report to show this:
val1 = 0.42
val2 - 72
val 3 = val 2 /val 1 = 171.43
I changed the number of decimal places on val 1 and val3 to be 0.00. However, it appears that these rounded values are not taken into account in the Formulas, as if the OLAP still uses the original values from the backend with 9 decimal points. So, no matter how many decimal points I use on the Display tab for a key figure, my val3 or result of my formula is always taking into account the 9 digit decimal values, not rounded values that I want. So in the example above, my val 3 comes to 172.80, which it should be 171.43 instead of you use the rounded values in the calculation.
Please let me know if there is any workaround where I could force my BEx Formula to utilize the rounded values and not actual values from the backend DSO. Or any other solution.
Thank you

If you create a Formula in BEx Query Designer like the one below, it works:
val3 = val2 / ( TRUNC ( ( val1 * 100 + 0.5 ) ) / 100 )
The TRUNC function (among other things) actually ensures that your formula takes into account the rounded values that you want.

Rounding value for abetment

Similar Messages

Maybe you are looking for