Change the decimal places of a field in screen table control

HI ,
I have a MENGE field having data element as , BSTMG (decimals 3 ).
This field MENGE , I have used in a table control. The value in this field is filled from a custom Z-table where the same data element BSTMG is used. So , for eq.) value in MENGE field is shown as 6.010
But the requirement is that the value should be displayed as only 2 decemals i.e.) 6.01
I dont want to change the domain of the field in the Z-table , to 2 decimal places , because the table is used in other developments also , so it will give a dump there which I have to correct in other developments also.
So , is there any way to change the decimal places of a field in screen table control , without changing the domain , in the table from where the value is fetched... ????
Edited by: abhijeet_7013 on Feb 14, 2011 3:18 PM

Hi, create a structure in local program with same field names and change the TYPE with some 2 decimal domain of MENGE. Populate this local stucture and use it in TABLE CONTROL.
Hope this helps...
Cheers

Similar Messages

Changing the Decimal places in the currency

Hi all
we are using the currecy SAR. Decimal places was set to 4, now that they want to revert back to 2 decimal places. i understand that by doing so they would be inconsistencies in the data allready recorded. how to avoid that?
is there any programmes / reports that would fix such inconsistencies?
any OSS notes?
thanks and regards
gkk

HI,
You should NOT change the decimal places in a productive system.
If you would do, the correction of the posted documents afterwards would be a remote consulting issue. Which you have to pay for SAP.
You see, all posting you have done until now, would get displayed in a wrong way, and the new posting wouldn't compare to the others.
Please check the note 137626 describes this.
If you really need to change the decimals, you should create a new currency type, for example your current is SAR, and now you should create a SA2. Then you should enter new rations and exchange rates for it, and work with the new one.
Also if you want to set the decimals to two digits from four, youshould not enter an entry in the OY04(TCURX).
In this table you can only enter a value, that discriminate from 2 decimals. If there is no entry in the table, it means the currency has two decimals.
Please assign points if it useful.
Regards
Ravinagh Boni

Removing the decimal places of currency field

Hi Gurus,
I have a currency type field ( to be more specific a field like BSEG-WRBTR) .
How do i eliminate the decimal places for this field.
ie if the value is 345678.91, i need to make it 345678.
Is there a standard keyword or something for this?
Points will be given to all the helpful answers.
Thanks,
Nobin.

You can use the FLOOR function to get the largest integer value without decimal.
Like:
DATA: W_RESULT TYPE I.
W_RESULT = FLOOR( P_AMT ).
Regards,
Naimesh Patel

Activation error while changing the data type of a field of a table

hi friends,
i am facing one problem while changing a data type of a field of a table.
i just created one table(Yqm32) .i have assigned charcter data type to one field(ztotal_count) .now i want to change this charcter data type to numeric data type.
while changing to NUMC data type activation error is comming as below.
Table is not yet classified
Field ZTOTAL_COUNT: Type change
ALTER TABLE is not possible
Structure change at field level (convert table YQM32)
Check on table YQM32 resulted in errors
Table YQM32 could not be activated
(E- Structure change at field level (convert table YQM32)
plz suggest.i need to change the data type from char to numc.
Thanks & Regards

Hi Pabitra......
From the SE11 change the table as u wanted and then from menubar select
UTILITIES--> DATABASE UTILITY
It will open database utility
there u select the Activate and adjust database button.
then the database table will get adjusted.
just try it once.........
Suresh......

Change the decimal places in screen MIGO field Order quantity - MENGE

Gurus
the scenario is in Screen MIGO , when gettin inside posting MIGO the functinal consultants need to give order quantity in the second screen and the technical name of that field is MENGE which can accept only 2 decimal places after point...now the requirement is we need to have 5 decimal places after point in that field...
how to achieve this....

still not solved.
impact analysis

Changing the Decimal places for Percentage in cost distribution in SC

Hi Gurus,
Is it possible to change the number decimal places for the Percentage field in cost Assignment tab in Shopping cart in cost distribution option?
The user wants 3 decimal places, currently we can enter only 2 decimal places.
I have gone thro' couple of blogs which are talking about changing the price decimal and not the percentage field decimal. (in IMG setting: General settings > Currencies > Set Decimal places)
So, if anyone come acorss this issue, please let me know.
Thanks and Regards,
Nowsath

Decimal Places Factor of the Receiver Weighting Factors
Specifies the number of valid decimal places with which the given weighting factors are valuated.
Example
You enter 123456 as the weighting factor. Depending on the factor, this number is interpreted as:
Factor Decimal places Weighting factor
1 0 123456
10 1 12345.6
100 2 1234.56
1000 3 123.456
10000 4 12.3456
100000 5 1.23456
1000000 6 0.123456
Please check with your FICO consulant .what settings you have in backend system.
http://help.sap.com/saphelp_nw04/helpdata/en/bb/bdbdc4575911d189240000e8323d3a/frameset.htm
Muthu

How to change the decimal places in the value axis of a chart in WAD?

Hello,
The key figure in my chart has 2 decimal places and I want the value axis to show the same. How to do that?
Thanks in advance, Nathalie

Hi,
change the Format property of the ValueAxis-Line to 0.00
Then the axis displays its values including two digits after the decimal.
Regards, Kai

Changing the length of a key field in a table

Hi,
I want to increase the length of the field from 2 to 4 in a standard SAP table and deliver it to the customers. This field is a key field in table. This field from this table is also used in view and view clusters.
What is the implication of changing the length to the customers. The customers would have already data in this field and they should not loose any data. Will the existing data for customers remain at length 2 or do they have to do some conversion?
Regards,
Srini.
Edited by: Srinivasa Raghavachar on Feb 7, 2008 12:45 PM

hi,
The database table can be adjusted to the changed definition in the ABAP Dictionary in three different
ways:
By deleting the database table and creating it again. The table on the database is deleted, the inactive
table is activated in the ABAP Dictionary, and the table is created again on the database. Data
existing in the table is lost.
By changing the database catalog (ALTER TABLE). The definition of the table on the database is
simply changed. Existing data is retained. However, indexes on the table might have to be built again.
By converting the table. This is the most time-consuming way to adjust a structure.
If the table does not contain any data, it is deleted in the database and created again with its new
structure. If data exists in the table, there is an attempt to adjust the structure with ALTER TABLE. If the
database system used is not able to do so, the structure is adjusted by converting the table.
Field 1     Field 2,    Field 3
NUMC,6 CHAR 8    CHAR, 60
Field 1    Field 2       Field 3
NUMC,6 CHAR, 8     CHAR,30
The following example shows the steps necessary during conversion.
Starting situation: Table TAB was changed in the ABAP Dictionary. The length of field 3 was reduced
from 60 to 30 places.
The ABAP Dictionary therefore has an active (field 3 has a length of 60 places) and an inactive (field 3
still has 30 places) version of the table.
The active version of the table was created in the database, which means that field 3 currently has 60
places in the database. A secondary index with the ID A11, which was also created in the database, is
defined for the table in the ABAP Dictionary.
The table already contains data.
Step 1: The table is locked against further structure changes. If the conversion terminates due to an
error, the table remains locked. This lock mechanism prevents further structure changes from being
made before the conversion has been completed correctly. Data could be lost in such a case.
Step 2: The table in the database is renamed. All the indexes on the table are deleted. The name of the
new (temporary) table is defined by the prefix QCM and the table name. The name of the temporary
Step 3: The inactive version of the table is activated in the ABAP Dictionary. The table is created on the
database with its new structure and with the primary index. The structure of the database table is the
same as the structure in the ABAP Dictinary after this step. The database table, however, does not
contain any data.
The system also tries to set a database lock for the table being converted. If the lock is set, application
programs cannot write to the table during the conversion.
The conversion is continued, however, even if the database lock cannot be set. In such a case
application programs can write to the table. Since in such a case not all of the data might have been
loaded back into the table, the table data might be inconsistent.
You should therefore always make sure that no applications access the table being converted
during the conversion process.
Step 4: The data is loaded back from the temporary table (QCM table) to the new table (with MOVECORRESPONDING).
The data exists in the database table and in the temporary table after this step.
When you reduce the size of fields, for example, the extra places are truncated when you reload the
data.
Since the data exists in both the original table and temporary table during the conversion, the storage
requirements increase during the process. You should therefore verify that sufficient space is available in
the corresponding tablespace before converting large tables.
There is a database commit after 16 MB when you copy the data from the QCM table to the original
table. A conversion process therefore needs 16 MB resources in the rollback segment. The existing
database lock is released with the Commit and then requested again before the next data area to be
converted is edited.
When you reduce the size of keys, only one record can be reloaded if there are several records whose
key cannot be distinguished. It is not possible to say which record this will be. In such a case you should
clean up the data of the table before converting.
Step 5: The secondary indexes defined in the ABAP Dictionary for the table are created again.
Step 6: The temporary table (QCM table) is deleted.
Step 7: The lock set at the beginning of the conversion is deleted.
If the conversion terminates, the table remains locked and a restart log is written.
Caution: The data of a table is not consistent during conversion. Programs therefore should not access
the table during conversion. Otherwise a program could for example use incorrect data when reading the
table since not all the records were copied back from the temporary table. Conversions therefore
should not run during production! You must at least deactivate all the applications that use tables to
be converted.
You must clean up terminated conversions. Programs that access the table might otherwise run
incorrectly. In this case you must find out why the conversion terminated (for example overflow of the
corresponding tablespace) and correct it. Then continue the terminated conversion.
Since the data exists in both the original table and temporary table during conversion, the storage
requirements increase during conversion. If the tablespace overflows when you reload the data from the
temporary table, the conversion will terminate. In this case you must extend the tablespace and start the
conversion in the database utility again.
If you shorten the key of a table (for example when you remove or shorten the field length of key fields),
you cannot distinguish between the new keys of existing records of the table. When you reload the data
from the temporary table, only one of these records can be loaded back into the table. It is not possible
to say which record this will be. If you want to copy certain records, you have to clean up the table
before the conversion.
During a conversion, the data is copied back to the database table from the temporary table with the
ABAP statement MOVE-CORRESPONDING. Therefore only those type changes that can be executed
with MOVE-CORRESPONDING are allowed. All other type changes cause the conversion to be
terminated when the data is loaded back into the original table. In this case you have to recreate the old
state prior to conversion. Using database tools, you have to delete the table, rename the QCM table to
its old name, reconstruct the runtime object (in the database utility), set the table structure in the
Dictionary back to its old state and then activate the table.
If a conversion terminates, the lock entry for the table set in the first step is retained. The table can no
longer be edited with the maintenance tools of the ABAP Dictionary (Transaction SE11).
A terminated conversion can be analyzed with the database utility (Transaction SE14) and then
resumed. The database utility provides an analysis tool with which you can find the cause of the error
and the current state of all the tables involved in the conversion.
You can usually find the precise reason for termination in the object log. If the object log does not
provide any information about the cause of the error, you have to analyze the syslog or the short dumps.
If there is a terminated conversion, two options are displayed as pushbuttons in the database utility:
After correcting the error, you can resume the conversion where it terminated with the Continue
adjustment option.
There is also the Unlock table option. This option only deletes the existing lock entry for the table .
You should never choose Unlock table for a terminated conversion if the data only exists in the
temporary table, i.e. if the conversion terminated in steps 3 or 4. table for table TAB is therefore QCMTAB.
Hope this is helpful,Do reward.

Changing of decimal places from 2 to 6 digits

Hi,
Currently, our PO price and GR/GI quantities are being limited to two (2) decimal places only. However, we want to maintain it into six (6) digits so that we can have a more accurate PO price and GR/GI quantities in our record.
We tried to do this in Tcode OY04 but the system issued as the following warning messages:
1. In a productive system, you must not delete the currencies in use or change the decimal places. This could make amounts in document already posted incorrect or invalid.
2. In the R/3 System tables currency fields are stored as decimal figures with a variable number of decimal places. The decimal point is not stored in the field in the database. Instead, each currency field refers to a currency key field. In this transaction you assign the number of decimal places to this currency key uniquely.
Can you please explain to me the warning messages further?
Thank you.

Hi Jack,
Please never try to change the decimal places in PRD system, you will be in deep deep trouble.
Let me give one example , If the current decimal is set to 2 digit and you are going to change it 3 digit, then USD 100.00 will become USD 10.000 for the already posted document.
Please not that, the decimal places are not sotred in the database, when you run a tcode to see any posted data the system queries the currency table and see the value for the decimals, if it finds 3 in OY04, it simply places the decial point afer 3 digit from right, if the decimal is set to 4m it will simple place the decimal point after 4 digit from right.
Hope this clears your doubt.
Best Regards
Hari K.

Without to change the setting.how to set the decimal place to 7 for an UDF.

Without to change the setting, how to set the decimal place to 7 for an UDF?

Hi
Once you create a UDF it will automatically be binded to the data source of data type that you gave at the time of creating UDF.
So i think you can not set the decimal places without changing the setting in display parameters.
i am not sure whether it will work or not one thing you can try is that create it as a alphanumeric data type and convert your decimal value to sting and then assign it to UDF,While retrieving for any manipulation you convert it as decimal.
Hope it helps you
Regards
Vishnu

Inscrease the decimal Places in Tcode QA32(UD)

Hi Guys,
I want to increases decimal point in Tcode QA32 .
My user requirement is to increases the decimal places from 3 to 4 in Inspection lot stock / to be posted.
We maintain 3 decimal places & I want 5 decimal places at the time of Usage Decision. But I couldn't found the required customizing setting.
Please suggest me....

Hello,
Changing Data Types and Lengths of Existing Fields
If a data element is assigned to the field, you must change the technical field attributes (data type, length, number of decimal places) in the domain of the data element.
Procedure for Fields with Data Elements
Double-click on the name of the data element.
The data element maintenance screen appears.
Double-click on the name of the domain.
The domain maintenance screen appears.
Choose Domain ® Display ® Change.
Make the required changes and save your entries.
Note that this change affects all the table fields that refer to the particular domain. Foreign keys could become inconsistent and conversions required. You should therefore consider the effects of this action before changing the domain by choosing in the maintenance screen of the domain and checking if the domain is used in other tables.
Choose .
The table is activated again and the table field is adjusted to the domain change.
Procedure for Fields with Direct Type Entry
Place the cursor on the field and choose Data element / Direct type.
Values can now be entered in fields Data type, Length, DecPlaces and Short text.
Change the entries for the data type, length and possibly the number of decimal places.
Save your entries.
Choose .
Note that a table conversion will normally be necessary (see Adjusting Database Structures) if you change the field attributes
NOTE: You need to have Access key.
Regards,
Alok Tiwari

Can we change the data type of a field based on the value of the field

HI Gurus,
My Requirement is as below -- Could you please guide me
in the Printable Adobe form -- for ex - as usual for dates fields in the Object Pallette the object type is a date/time field and for quantity/currency fields corresponding fields are taken
now in case the either the date, quantity or currency is initial in place of displaying 0.00 or empty date we need to display N/A (Not Applicable)
for this I would like to change the data type of the field
to put it simply --
we need to change the data type of date field from DATE&TIME to Char type to hold N/A or Quantity field to Char field to hold N/A
how can we realize this in SAP adobe forms
Thanks in Advace
Ramchander Rao.K

Hello Ramchander,
     You cannot change the data type of the field at run time in Adobe forms because the type of field you choose at the time of design level is associated with the data type itself.
If you want to achieve your requirement, then your main idea should be to set the data type as CHARACTER itself while designing the field in the adobe form itself. CHAR field will comfortably hold the value of Calculation/amount field, Currency field, Amount, Date, Time HHMMSS, Unit Accuracy, Currency key, Floating point number, Numeric text, Client, Language and many other data types.
After designing the field as TEXT field in Adobe form you have two options.
Option 1:
Select the Date field initially as type TEXT field or CHAR field in Adobe forms.
Suppose the name of the field is TEXTFIELD1, then write the Javascript code on this field in Initialize event as below.
if ( this.rawvalue == null )
     this.rawvalue = "N/A";
If the field is not blank, then it will show the date. Else it will show "N/A".
Option 2:
Select the Date field initially as type TEXT field or CHAR field in Adobe forms. Do the formatting part in ABAP itself. It will increase the performance. Avoid Javascript as much as possible.
Suppose you have a DATE variable l_dats of type DATS. Then take another variable l_date of type CHAR. Then write the below ABAP code.
MOVE l_dats TO l_date.
IF l_date IS INITIAL.
     l_date = 'N/A'.
ENDIF.
Bind the l_date to the TEXT field in the form.
Even in this case, if the field is not blank, then it will show the date. Else it will show "N/A".
But I will suggest you to use Option 2 of keeping the AMOUNT, QUANTITY, DATE, TIME fields etc as CHAR or TEXT fields in Adobe form and do the required formatting in ABAP itself.

The decimal place is wrong in GR55

Dear Expert:
We are using currency JPY
We now creating a new report using report painter, but unfortunately the decimal place is wrong,
the result is only one percentage of the real amount, how can I get this issue solved?
notice that we are using report painter, not ABAP programming, so function module BAPI_CURRENCY_CONV_TO_INTERNAL
is not applicable.

Dear Lu Meng
I was reading your question which seems not answered at all.
I have EXACTLY your same issue.
In ECC using a FAGLFLEXT Report Painter.
My zero decimal currencies such as HUF and JPY are showing in the report, with decimals, thus are factor of 100 too small. Even changing layout deimcals, etc has NO EFFECT.
Did you solve this sissue? OSS has nothing either?
Thanks for any assistance.
Richard

Decimal place in Quantity field

Hello experts,
Got a query regarding decimal places in the quantity field of a sales order.
The material UOM is maintained as EA. I have checked the transaction CUNI, where the decimal place is maintained as ZERO. Still , Sales order / Delivery documents which i am creating is allowing decimal places for in the quantity.
For eg: material quantity of 50 EA in sales order, during the delivery batch splitting is getting splitted as 25.095 EA and 24.050 EA. Can you pleae advise the reason for this and how to go about this...
Thanks,
Safeer Rahman

Thanks for your reply....
But , as i have already told the decimal place field is maintained as 0(zero) in CUNI for the UOM EA.... Still its allowing me to enter decimal values... for eg:. its allowing me to enter 50.038 EA. I don't know why its not giving an error message prompting me not to enter decimal values...
Any idea?
Thanks,
Safeer Rahman

Change of decimal places in productive system

Hello
We are on ECC 6.0 in a post Go Live environment.
In our productive system we have set the decimal places to 2. For our business requirements, we would like to maintain 3 decimal places to 3 for Logistics modules (SD / MM & PP) where as we would like to maintain 2 decimal places for Financials module.
Pls advise us of the methodology of this changeover as well as the possible side effects as a result of this change.
Thanks & Regards,

Hello
The number of decimal places saved on the database is determined by the Global Settings made in Customizing for that unit (unit of measure or currency unit). If no entry has been made in Customizing, the number of decimal places saved for this key figure and characteristic value is the number of decimal places shown in the planning table at the time of saving. If the key figure has no displayable unit (for example, if it is a percentage), all the decimal places are saved.
However, you need to perform some testing of scenarios to really know the impact 2 different decimals. Definitely, there is one aspect, whether any conversion is required or is it just a display of values in decimals.
Data from FI to other modules is not a issue, but data from other modules to FI should be able to take this extra decimal.
Although personally in my opinion it is not going to cause any errors, please test the same.
Check documentation on Key Figures
Reg
assign points if useful

Change the decimal places of a field in screen table control

Similar Messages

Maybe you are looking for