Notation endings length

Software: Logic 8.0.2
Problem:
1. In notation mode - cannot change the length of 1st & 2nd endings. I tried doing what the manual suggests - grab the end and lengthen. Doesn't work. My software is updated. I think it's a bug. It used to work. Now it does not.
2. Sometimes in notation edit mode. "Part view". I may double click an item - then it jumps to "Score view" and all my preferences are then gone (like 4 bars per line)....GRRR... another bug!! Don't know how to get it back to "part view" after it morphs into "Score view"...another BUG!!!

chakatania wrote:
Software: Logic 8.0.2
Problem:
1. In notation mode - cannot change the length of 1st & 2nd endings. I tried doing what the manual suggests - grab the end and lengthen. Doesn't work. My software is updated. I think it's a bug. It used to work. Now it does not.
Hi
This works fine here. Is your issue specific to 1 particular project, or all (including a brand new one from the default empty template)?
CCT

Similar Messages

Is it possible to change the length of a note in the score editor?

I thought I saw somewhere that it was now possible to adjust the length of a note in the score editor graphically, i.e. by clicking on the note and somehow adjust its length directly to change it from 1/4 note to 1/8 (for example).
I don't want to do this by going over to the "Length" dialog on the left because I hate having to switch from thinking in terms of music notation and then having to think (temporarily) in MIDI ticks per beat, etc.
I must admit that I'm finding it extremely frustrating to simply enter music into Logic in a score....I thought this was supposed to be one of its strengths but it seems to be providing amazing capabilities at the expense of ease of use for beginners.

dhjdhj wrote:
I thought I saw somewhere that it was now possible to adjust the length of a note in the score editor graphically, i.e. by clicking on the note and somehow adjust its length directly to change it from 1/4 note to 1/8 (for example).
greetings dh... are you into Key Commands? There are two which will help you do the above in a trice:
• Nudge Region/Event Length Right by SMPTE Frame
• Nudge Region/Event Length Left by SMPTE Frame
I set mine to the simple letter o and n
- I click on a note and press o repeatedly.. it grows and grows longer and longer
– I click on a note and press n repeatedly.. it shrinks and shrinks shorter and shorter
All by little increments
If you keep a Piano Roll window open while you do this, you can see the length do this exactly
man, it is VERY quick and handy for changing the length of notes
It really helps to have a view of the midi Piano Roll to cross check the exact length and position of the notes.
Check out the Key Commands:
• Set Next Higher division
• Set Next lower division
These change the note value in the transport bar near the time signature. Your time signature may be 4/4 but the "grid" on which the notes are appear in the Piano Roll could be displayed in quarter, 8th or 16th notes. If you experiment with these commands, then you can match the note lengths easily to the grid display visually (with the above nudge length commands)
Also - you may like to experiment with the following 3 KEY Key Commands:
1 • Nudge Region/Event Position Right by Nudge Value
2 • Nudge Region/Event Position Left by Nudge Value
This will move your selected notes forward in time or back in time according to the
value that is set in the Transport bar - say it is 16ths .. then each press of the key will move the notes a 16th
or if the value is 8th notes, then each press of the key forward or backwards will move the selected notes forward or back by this amount
... amazingly useful when you are taking a whole phrase and pasting it somewhere else, or if say you started to write a phrase in the Score Editor and you started on the wrong beat.. then you just Nudge back and forth
3 • Set Nudge Value to Division
.. this will in a trice change change the Nudge Value to whatever Note division value is set in the Transport bar
HTH and forgive me if I have given you too much information
..problem is I spent too much time in the Transport Bar in Los Angeles last year drinking with the iSchwartz and other Logic reprobrates... you should join us some time

Convert from scientific notation

Can someone help me with this? I cannot get this working even using some of the tips I found on this site and elsewhere:
Round this and format this with 2 decimals: '-2.58069E-11'.
Now I realize this would end up -2.58, but it is giving me an error instead.
Error converting data type varchar to numeric.
SELECT CAST('2.58069E-11' AS NUMERIC(24,2))
SELECT CAST('2.58069E-11' AS NUMERIC(24,12))
I tried 12 just to make sure that there was enough room for the decimals
If I use ISNUMERIC, it returns 1, so SQL Server considers it a number (at least with that function)
The next example works, but it is not what I want.
SELECT CAST('2.58069E-11' AS REAL) just returns the same thing with the 'E', (as REAL, of course)
In these example I haven't done the rounding yet.
I get all kinds of negative and positive numbers with different decimal lengths, but the scientific notation is particularly tricky.

Before I put this to bed, I have found out both the above solutions are wrong when using a regular decimal:
Try this:
SELECT CAST(CAST('-1131658.27' AS REAL) AS NUMERIC(24,2))
And this:
SELECT CAST(CONVERT(REAL, -1131658.27) as DECIMAL(24,12))
They both yield -1131658.25, and -1131658.250000000000, respectively.
This is probably some floating point error, but how do I take care of it?

Lax validation errors on schema import ('version' exceeds maximum length)

I have a schema as per below. I'm trying to import it into Oracle 10.2.0.2.0. However, I'm getting the following lax validation error:
Error loading ora_business_rule.xsd:ORA-30951: Element or attribute at Xpath /schema[@version] exceeds maximum length
I can fix it by modifying the attribute and shortening it but I'd like to know why it's occuring. Insofar as I can tell there is no imposed limit on the size of schema attributes according to the W3C standard. Which then makes me wonder: does Oracle impose limits on the length of all attributes or is this specific to 'version' ? If there is a limit, what is the upper bound (in bytes) ? Where is this documented?
Cheers,
Daniel
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:br="http://foo.com/BusinessRule_PSG_V001" targetNamespace="http://foo.com/BusinessRule_PSG_V001" elementFormDefault="qualified" attributeFormDefault="unqualified" version="last committed on $LastChangedDate: 2006-05-19 11:00:52 +1000 (Fri, 19 May 2006) $">
     <xs:element name="edit">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="edit_id" type="xs:string"/>
                    <xs:element ref="br:business_rule"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="derivation">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="derivation_id" type="xs:string"/>
                    <xs:element ref="br:derivation_type"/>
                    <xs:element ref="br:business_rule"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="derivation_type">
          <xs:simpleType>
               <xs:restriction base="xs:NMTOKENS">
                    <xs:enumeration value="complex"/>
                    <xs:enumeration value="format"/>
                    <xs:enumeration value="formula"/>
                    <xs:enumeration value="recode"/>
                    <xs:enumeration value="SAS code"/>
                    <xs:enumeration value="transfer"/>
                    <xs:enumeration value="count"/>
                    <xs:enumeration value="sum"/>
                    <xs:enumeration value="max"/>
                    <xs:enumeration value="min"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="business_rule"></xs:element>
</xs:schema>

Opps -- Sorry it's a decision we took when looking at Version
When we registered the Schema for Schemas during XDB bootstrap the Version attriubte was mapped to varchar2(12).
SQL> desc xdb.xdb$schema_T
Name                                      Null?    Type
SCHEMA_URL                                         VARCHAR2(700)
TARGET_NAMESPACE                                   VARCHAR2(2000)
VERSION                                            VARCHAR2(12)
NUM_PROPS                                          NUMBER(38)
FINAL_DEFAULT                                      XDB.XDB$DERIVATIONCHOICE
BLOCK_DEFAULT                                      XDB.XDB$DERIVATIONCHOICE
ELEMENT_FORM_DFLT                                  XDB.XDB$FORMCHOICE
ATTRIBUTE_FORM_DFLT                                XDB.XDB$FORMCHOICE
ELEMENTS                                           XDB.XDB$XMLTYPE_REF_LIST_T
SIMPLE_TYPE                                        XDB.XDB$XMLTYPE_REF_LIST_T
COMPLEX_TYPES                                      XDB.XDB$XMLTYPE_REF_LIST_T
ATTRIBUTES                                         XDB.XDB$XMLTYPE_REF_LIST_T
IMPORTS                                            XDB.XDB$IMPORT_LIST_T
INCLUDES                                           XDB.XDB$INCLUDE_LIST_T
FLAGS                                              RAW(4)
SYS_XDBPD$                                         XDB.XDB$RAW_LIST_T
ANNOTATIONS                                        XDB.XDB$ANNOTATION_LIST_T
MAP_TO_NCHAR                                       RAW(1)
MAP_TO_LOB                                         RAW(1)
GROUPS                                             XDB.XDB$XMLTYPE_REF_LIST_T
ATTRGROUPS                                         XDB.XDB$XMLTYPE_REF_LIST_T
ID                                                 VARCHAR2(256)
VARRAY_AS_TAB                                      RAW(1)
SCHEMA_OWNER                                       VARCHAR2(30)
NOTATIONS                                          XDB.XDB$NOTATION_LIST_T
LANG                                               VARCHAR2(4000)
SQL>

How do I add a sharp to chords in Notation

How can I add a sharp to the chords for example C7(sharp9)in the notation. I do not have a sharp sign on my Mac keyboard. Somehow the notation program in Logic is not as user friendly as Cubase. Can one change the amount of bars per leger line and is one able to adjust individual bar lengths. Also, how does one increase the size of the accidentals on the stave.
thanks
Carlo

Hi Carlo
You can drag a sharp or flat sign from the Inspector on the right of the Score. Make sure you open the Part Box and experiment with the different categories
You can change the amount of bars per line with the Layout Tool, depending also on the Setting for maximum number of bars per line in the Project Settings ( see snapshot below lower left hand box)
You cannot adjust individual bar lengths in Logic - ( this is a severe limitation of the Score Editor)
You can adjust the size of accidentals in Chords but not in normal use of - however this is something I have never needed to do. It is one aspect of Logic Score Editor that is pretty acceptable.
You can change the distant of Accidentals in relation to each other ( very useful when you have a complex chord with many accidentals) and also the distance from the note. This shrinks or expands the bar slightly ( which therefore gives you some opportunity to adjust bar size).
You can change the distance from the beginning of the bar to where the first note is set.
Look closely at the options in Project Settings
Hope this helps
M S
!!

To Quantize Note Lengths...

To make Quantizing Note Lengths more intuitive:
Can anyone recommend a good course in Pascal or Objective-C ?

Mike Connelly wrote:
This isn't a big deal for me since I don't have to quantize note lengths very often and can usually find something else that works, but it would be a nice feature to have included.
I agree with ya. I also see your point about quantizing note endings to snap to the grid. You're right that the shortcut doesn't perform that function. Since I don't worry about my non perfect event endings too much, the few times I do want to change them it's usually to quantize more or less similar notes so I use the shortcut. Outside of that, it may not be as useful.
If you have Cubase already and find it works better for you, then why bother with Logic?
I agree with this too. ET-Cubase is great! Version 5 is very nice and apparently does some things better than Logic 9 can do. I find Logic 9 to be the best overall DAW package in existence for my personal workflow, projects, musical ideas and taste. If Logic is such a hassle for you and Cubase is an apparent godsend I think you know the decision to make.

Converting scientific notation string to number?

This is raising an error:
> ToNumber (u201C2.75E-05u201D)
How do you convert scientific notation strings to numbers?
This is coming from XML. I can probably have the XML written so that it's not scientific notation.
Tim

Here's a not-so-pretty way:
Local StringVar Array x;
Local StringVar mantissa;
Local StringVar exponent := "0";
// Split into mantissa and exponent parts.
x:= Split("24.2233E+2", "e", 2, 1);
mantissa := x[1];
If (UBound(x) = 2)
Then
    exponent := x[2];
// CDbl cannot interpret leading positive sign, so removie
If Left(mantissa, 1) = "+"
Then
    mantissa := Right(mantissa, Length(mantissa) - 1);
If Left(exponent, 1) = "+"
Then
    exponent := Right(exponent, Length(exponent) - 1);
// Compute number
CDbl(mantissa) * 10 ^ CDbl(exponent);
Sincerely,
Ted Ueda

TO_CHAR not Scientific Notation

I want to convert a number to a string but guarantee that the result will NOT be in scientific notation.
TO_CHAR(num, '9999999999.99999999999999') is not very convenient since the data type of the number is BINARY_DOUBLE and I will not know how many significant figures the number will have.

user3975338 wrote:
So is it safe to say there there is no built in feature that would ever output a the numeric string
'0.00000000000000000000000000000000000000000000000000000000000000000000000000000009'The scientific notation is only a matter of how the particular interface is displaying the number and how your NLS settings are for converting automatically between numbers and varchar.
e.g. in SQL*Plus you can change the format of a column easily...
SQL> ed
Wrote file afiedt.buf
1 with t as (select cast(1.0000000000000001E-001 as binary_double) as dbl from dual union all
2             select 4.0144896E+008 from dual union all
3             select 3.0976E+005 from dual union all
4             select 2.78784E+006 from dual union all
5             select 6.4E+001 from dual union all
6             select 2.7878400000000001E+003 from dual union all
7             select 2.4909766860524436E-011 from dual union all
8             select 1.0000000000000001E-001 from dual union all
9             select 7.7160493827160492E-005 from dual union all
10             select 6.9444444444444436E-004 from dual)
11 --
12 select dbl, dbl2, length(trim(dbl2)) as ldbl
13 from (
14    select dbl, rtrim(rtrim(to_char(dbl,'99999999999999990.999999999999999999999999999'),'0'),'.') as dbl2
15    from t
16*   )
SQL> /
       DBL DBL2                                                 LDBL
1.0E-001                  0.10000000000000001                   19
4.014E+008          401448960                                      9
3.098E+005             309760                                      6
2.788E+006            2787840                                      7
6.4E+001                 64                                      2
2.788E+003               2787.8400000000001                       18
2.491E-011                  0.000000000024909766860524436         29
1.0E-001                  0.10000000000000001                   19
7.716E-005                  0.000077160493827160492               23
6.944E-004                  0.00069444444444444436                22
10 rows selected.
SQL> col dbl format 999999999990.9999999999999999999999999999999
SQL> /
                                          DBL DBL2                                                 LDBL
            0.1000000000000000100000000000000                  0.10000000000000001                   19
    401448960.0000000000000000000000000000000          401448960                                      9
       309760.0000000000000000000000000000000             309760                                      6
      2787840.0000000000000000000000000000000            2787840                                      7
           64.0000000000000000000000000000000                 64                                      2
         2787.8400000000001000000000000000000               2787.8400000000001                       18
            0.0000000000249097668605244360000                  0.000000000024909766860524436         29
            0.1000000000000000100000000000000                  0.10000000000000001                   19
            0.0000771604938271604920000000000                  0.000077160493827160492               23
            0.0006944444444444443600000000000                  0.00069444444444444436                22
10 rows selected.
SQL>... see ... no scientific notation any more.

Inserting hyphen changes line-endings

When I run a multi-line insert statement to insert some text in SQL Developer, and the text contains a hyphen ( - ), the line endings all become space-LF, instead of just LF or CRLF. The "Line Terminator" settings in SQL Developer preferences have no effect here.
For example...
Running this insert statement:
INSERT INTO mytab
(mytab_name, mytab_sequence, mytab_label, mytab_image, mytab_text, mytab_comment, mytab_activity_date, mytab_source_ind)
VALUES ('bwskoacc.P_ViewHold', 2, 'DEFAULT', NULL,
'aaa
zzz
aaa'
, NULL, sysdate, 'L');
Results in this dump for the mytab_text field:
Typ=1 Len=11: a,a,a,^J,z,z,z,^J,a,a,a
Note the ^J which is a chr(10) linefeed. This is the dump I expected to see. There are no extra spaces, and the line endings are all just LFs.
Now, compare this insert statement which includes a dash:
INSERT INTO mytab
(mytab_name, mytab_sequence, mytab_label, mytab_image, mytab_text, mytab_comment, mytab_activity_date, mytab_source_ind)
VALUES ('bwskoacc.P_ViewHold', 2, 'DEFAULT', NULL,
'aaa
z-z
aaa'
, NULL, sysdate, 'L');
Results in this dump for the mytab_text field:
Typ=1 Len=13: a,a,a, ,^J,z,-,z, ,^J,a,a,a
Here's the decimal dump:
Typ=1 Len=13: 97,97,97,32,10,122,45,122,32,10,97,97,97
Note the space before each of the linefeeds. Note the length is now 13 instead of 11.
Why is a space being inserted before the linefeeds if I include a hyphen? I have tried inserting all kinds of different text, and found the only thing that has this effect is inserting a hyphen. What's special about a hyphen? Is the database adding the spaces, or is SQL Developer telling the database to add the spaces?
This is how the mytab_text field is defined:
mytab_TEXT VARCHAR2(2000 CHAR)
Thanks!
Edited by: user558000 on Jul 25, 2012 8:59 AM

It definitely looks like a SQL Developer issue. Same database for both.
In sqlplus
SQL> INSERT INTO mytab
2 (mytab_name, mytab_sequence, mytab_label, mytab_image, mytab_text,
3 mytab_comment, mytab_activity_date, mytab_source_ind)
4 VALUES ('bwskoacc.P_ViewHold', 2, 'DEFAULT', NULL,
5 'aaa
6 z-z
7 aaa'
8 , NULL, sysdate, 'L');
1 row created.
SQL> select dump(mytab_text) from mytab;
DUMP(MYTAB_TEXT)
Typ=1 Len=11: 97,97,97,10,122,45,122,10,97,97,97Doing the insert from SQL developer gives:
DUMP(MYTAB_TEXT)
Typ=1 Len=13: 97,97,97,32,10,122,45,122,32,10,97,97,97John

Int printing out as scientific notation

maybe doing something stupid here but I can't seem to pick it up.
I have a Window that calls a subclass to display a calculator, and then returns the final value to the Window, if I input 10 digits it prints on as a 12345678E5
something like that.
Anywho here's the two methods that deal with value in the subclass( calculator )
public int ReturnNumber(){//the method that will return the value from the keyboard
   int final_number = Integer.parseInt(number);
    return final_number;   // returns value to question screen
private void NextButtonActionPerformed (java.awt.event.ActionEvent evt) {
   if ( value.length() != allowable_answers[currentQuestionNumber] ){
                 JOptionPane.showMessageDialog(this, "Please make a valid entry.", "Invalid",
                 JOptionPane.WARNING_MESSAGE );
                 value.replace(0,counter,"");
                 jTextField1.setText( null );
                 return;
    else {
            number = value.toString();
           setVisible(false);
           frame.final_number = ReturnNumber();
           frame.userMakeSelection = true;
           frame.FinalTimer.start();
           frame.ButtonSelected();Code from window that deals with the number
if(Numeric[currentQuestionNumber]){
            currentAnswers[currentQuestionNumber][1] = final_number;// currentAnswers is a float[][]
            numeric_question_value[currentQuestionNumber][0] = final_number;// used in poll frequency
          }// numeric is a int[]
        else
            currentAnswers[currentQuestionNumber][currentChoice] = currentChoice;Is from trying to jam an int into float?
Any suggestions
Jim

Is from trying to jam an int into float?That's exactly the cause. Here are some solutions:
- Use java.text.DecimalFormat to format the output or cast the float to an integer type when you want to print it (presicion might become a problem).
- Keep the number in an int or long all the time. This way you'll not lose any presicion.
Explanation can be found in the API docs of Float.toString():"If the argument is NaN, the result is the string "NaN".
Otherwise, the result is a string that represents the sign and magnitude (absolute value) of the argument. If the sign is negative, the first character of the result is '-' ('-'); if the sign is positive, no sign character appears in the result. As for the magnitude m:
If m is less than 10^-3 or not less than 10^7, then it is represented in so-called "computerized scientific notation." Let n be the unique integer such that 10n<=m<1; then let a be the mathematically exact quotient of m and 10n so that 1<a<10. The magnitude is then represented as the integer part of a, as a single decimal digit, followed by '.' (.), followed by decimal digits representing the fractional part of a, followed by the letter 'E' (E), followed by a representation of n as a decimal integer, as produced by the method Integer.toString(int) of one argument."

Feature Request - Storyboard import and Audio Notations

Ability to import and associate sotryboards for scene breakdown. Would be nice to import various graphic formats or even audio notations about the scene to help convey thoughts during collaboration.
Nice preview release. Headed in the right direction.

HI,
there are some features that could be very usefull :
-Time code counter : would estimate the length of written part, and add this duration in a "counter." hh:mn:ss;fr"
of course in 25, 24,and 29fps and the option to set the initial TC.
-Exporting sound track with various synthesis voices, in the most common audio files .aiff .wav .mp3
-Exporting XML timelines to NLE systems ; it would allow the whole team to start working.
Motion graphic designers, music composers, sound editors, could better figure out what the film will be.
The xml file would have audio files associated. (ie voice over would help a 3D team to sync their animations)
-Perfect interoperability with MSWord and Excel
-a "colors/category" column, user-defined with a sign counter. Would allow to figure out how much "stock shot" / "CGI" / "Robert de Niro" / "underwater"
is required.
-all commands should be assignable to keys by the user (Final Cut Pro does that very well)
-avoid F1, F2... etc as more and more people use portable computers.
-User defined workspaces : something very light with no disturbing figures or menus for a fluid writing, and something more complete for reviewing periods with statistics, exports etc etc etc

Bounced Files cut off at beginnings and endings.

Hello,
I am having trouble with bouncing files from Logic. This is a simple cut and bounce from Logic to create track IDs on CD. The problem is, after the bounce, the beginnings and endings are truncated with the result of awful clicks between tracks. The regions are meant to run continuously, and they do, in Logic. When I line them up in the burner program, though, they are not the same region length.
I have already tried increasing the division and adjusting the tempo and meter settings in the transport. As far as I can tell, the regions are exactly as they should be. I also checked the beginning and end times of the selected region in the bounce dialog.
What am I missing?

Hello,
I am having trouble with bouncing files from Logic. This is a simple cut and bounce from Logic to create track IDs on CD. The problem is, after the bounce, the beginnings and endings are truncated with the result of awful clicks between tracks. The regions are meant to run continuously, and they do, in Logic. When I line them up in the burner program, though, they are not the same region length.
I have already tried increasing the division and adjusting the tempo and meter settings in the transport. As far as I can tell, the regions are exactly as they should be. I also checked the beginning and end times of the selected region in the bounce dialog.
What am I missing?

Photo clip lengths - trouble adjusting!

I have a new project consisting of 80-100 photos, all with a transition in between. Via Project Properties (Apple Key - J), I can set the photo duration but it's only in even increments -- 2 seconds, 3 seconds, 4 seconds, etc. I want to pick 2 1/2 seconds but the slider scale won't let me do that.
If I try to select just a photo properties (Apple Key - R) manually, from 2:00 to 2:50, it auto-adjusts it to 3:20. Having it set to that (or higher) makes the overall project runtime too long. Can I get it to something between 2 and 2 1/2 seconds??

There is an interplay between clip length or photo length and the length of transitions.
For example, if you have two photos each with length 4 seconds and 0 frames, and a transition between them of 30 frames (1 second), then each photo will have a length of 3 seconds and 15 frames. Note: this behavior can be changed in either Preferences or Project Properties: I can't remember which (this applies to clips).
Further, when you set the length of the photo to 2:50, you are really setting it to 2 seconds and 50 frames. In the NTSC system, one second is approximately 30 frames, so 50 frames yields 1 second and 20 frames ( or a total of 3 seconds and 20 frames, as you observed.)
Two and a half seconds in this notation would be 2:15.

Sorting lines by length in automator?

I have a document with around 4,000 lines of text. Is there a way for me to automatically sort them by character length through the use of Automator and a bit of scripting?
Bonus points if there's a way to output the character length at the beginning of each line once the sorting is complete.
Little heads up, my knowledge of AppleScript is pretty non-existant so an idiot's guide would be much appreciated.

There's nothing wrong with the script, it's the format of your text file that's causing the problem.
Unfortuntely there isn't really such as thing as a 'plain' text file anymore. Text files come in a variety of formats (ASCII, Unicode, ISO, etc.) and use varying line endings (CR, LF, or CR/LF), and the particular combination used in your file is breaking the script.
The simplest solution is to save the file as standard UTF-8 Unicode, then the script works fine. If you don't have an application that can convert it you can incorporate the command line utility textutil into your shell command:
textutil -convert txt -o - $1 | awk '{print (length($0) " " $0 "</sentence>")}' | sort -n
This time it will invoke textutil to convert the file first (rather than just cat, then run the awk/sort commands.

New Decimal Notation Format Required For Indian Projects

Respected Members,
As at the user level or tcode SU01 only three decimal notations are provided.
But for country India the decimal notation format is totally different.
Given decimal notation format is
1,234,567.89
And the Required Format For India is
1,23,456.78
Becoz we mention the Rupees in this format only.
And this second format is not available in SPRO also .
How to create the desired decimal notation and add the corresponding functionality.
And if we use the given format (1,234,567.89) then when we converting the amount in words through Function module
SPELL_AMOUNT ,it is not converting properly even though we have maintain the entries in View V_T015Z.
Suppose our amount is 1,00,000 that is One lakh but it will show in the output ONE HUNDRED THOUSAND.
I know that there is another function Module HR_ch_ something to convert in words according to indian currency.
But it does not solve the issue properly.
THis DECIMAL NOTATION format for Indian Projects is a BIG MESS.
So kindly tell me any solution or it is the drawback of SAP.
So that we can ask SAP to append this Decimal Notation and required Functionality for the Indian Projects.
Kindly Send Your Valuable answer and Try To Make clear picture and SAP Technical People if Reading this thread then kindly give stress on the REQUIRED DECIMAL NOTATION.
THANKS A LOT.

Hi Manish please you can try this code
REPORT ZAMOUNT_CONVERSION.
DATA : RESULT1(20).
PARAMETERS : NUM TYPE P DECIMALS 2.
DATA : num2 type STRING.
DATA : col_amt(20) type n,"15
         col_b type i,
         num_1(20) type C,"15
         Length type i.
num_1 = num.
write : 'default format      :',num.
uline.
skip.
IF ( num >= 999999999 ).
       write num_1 using edit mask 'RR__,__,__,__,______' to col_amt.
       CONDENSE col_amt.
       length = STRLEN( col_amt ).
       if length = 16.
         REPLACE first OCCURRENCE OF ',' in col_amt with space.
         write :/'amount indian format:',col_amt.
       else.
       write :/'amount indian format:',col_amt.
       endif.
ELSEIF NUM < 999999999 AND NUM >= 9999999.
       write num_1 using edit mask 'RR__,__,__,______' to col_amt.
       condense col_amt .
       length = STRLEN( COL_AMT ).
       if length = 13.
         REPLACE first OCCURRENCE OF ',' in col_amt with space.
         write :/'amount indian format:',col_amt.
       else.
         write :/'amount indian format:',col_amt.
      endif.
ELSEIF NUM < 9999999 AND NUM >= 99999.
       write num_1 using edit mask 'RR__,__,______' to col_amt.
       condense col_amt .
       length = STRLEN( COL_AMT ).
       write :/'amount indian format:',col_amt.
ELSEIF NUM < 99999.
   data : dumy(10) type c.
   dumy = num .
   CONDENSE dumy.
   length = STRLEN( dumy ).
     if length <= 6.
       write :/'amount indian format:',num.
       else.
       write num_1 using edit mask 'RR__,______' to col_amt.
       write :/'amount indian format:',col_amt.
      endif.
   ENDIF.
   uline.
create a function module with this code .hope this will solve the issue.

Notation endings length

Similar Messages

Maybe you are looking for