Leading Zero in 0CALMONTH

Hello,
I am new to BW and appreciate some help. Thank You in advance.
I have a flat file with a date field in the format MMYYYY. The infosource has 0CALMONTH field. When I preview the data befor upload creates error on the record with single digit month (For Example 12006). No error if the record is '112005'.
If I try to convert the CSV file record as text '012006, then it works. I cannot do for all records.
What am I doing wrong. I know it can be done, but it does not work in this file.
Thank You

Hi,
AFAIR, there is a conversion exit for 0CALMONTH.
Look it its description in help.
You may use MM.YYYY external format for upload. It is acceptable.
Best regards,
Eugene

Similar Messages

Adding leading zeros in abap objects.

Can anyone explain me
1. How to add leading zeros to a field in abap objects.
For eg:
data: dmb(6) type c value '123456',
actually the output value of c should have leading zeros added to it for length 16.
i.e '0000000000123456' . If the length of dmb is less than 16 then leading zeros should be added to that value to make it 16 as length.
Please tell me how to do it in ABAP Objects.

Hi Camila
Try to use the statement
DATA: ALPHABET(15) VALUE ' ABCDEFGHIJ',
 M1(4) VALUE 'ABCD',
 M2(6) VALUE 'BJJCA '.
SHIFT ALPHABET LEFT DELETING LEADING M1.
The field
ALPHABET
remains unchanged.
SHIFT ALPHABET LEFT DELETING LEADING SPACE.
The field ALPHABET now has the following contents:
'ABCDEFGHIJ '.
SHIFT ALPHABET RIGHT DELETING TRAILING M2.
ALPHABET now has the following contents:
' ABCDEFGHI'.
IN CHARACTER MODE
Effect
This is the default setting (see above), and the addition is therefore optional.
Note
Performance:
For performance reasons, you should avoid using SHIFT in WHILE loops.
The runtime required to shift a field with length 10 by one character to the right or left requires about 5 msn (standardized microseconds). A cyclical shift requires around 7 msn. The runtime for the ...
LEFT DELETING LEADING
... variant is around 3.5 msn, for ...
RIGHT DELETING TRAILING
... around 4.5 msn.
Reward all helpfull answers
Regards
Pavan

How do I use the print function to output a numeric variable with a fixed amount of leading zeroes

I need to create an output from a T-SQL query that picks a numeric variable and uses the print function to output with leading zeroes if it is less than three characters long when converted to string. For example if the variable is 12 the output should
be 012 and if the variable is 3 the output should be 003.
Presently the syntax I am using is PRINT STR(@CLUSTER,3) . But if @CLUSTER which is numeric is less than three characters I get spaces in front.
Please help!

>> I need to create an output from a T-SQL query .. <<
NO! NO! In RDBMS, we have a presentation layer that handles displays. We do not ever do it in the database. This is fundamental. But more than that, the purpose of PRINT is for debugging in T-SQL and never for output.
You are still writing 1960's COBOL or BASIC, but you want to to it in SQL. You probably picked the wrong data type (a numeric that should be a string) and are trying to repair your design error.
--CELKO-- Books in Celko Series for Morgan-Kaufmann Publishing: Analytics and OLAP in SQL / Data and Databases: Concepts in Practice Data / Measurements and Standards in SQL SQL for Smarties / SQL Programming Style / SQL Puzzles and Answers / Thinking
in Sets / Trees and Hierarchies in SQL

IR - Column with leading Zeros issue

Hello,
I've got an IR report which includes as "default report settings" 1 column with leading 0s. In order to export to Excel that column as text rather than as a numeric I followed a workaround proposed before in this forum (excel copy drops leading zeros
In essence this workaround is to create an identifical column but in "excel text format" and display the columns depending on the request value: INSTR(NVL(:REQUEST,'YABBADABBADO'),'CSV') <> 0 for example.
This works just fine for the default report.
The problem arise when a user creates his own customise report that includes the mentioned column and saves it as a named report. Here, when the results are exported to excel the "excel" column does not appear.
In fact, just hiding one of the displayed columns produces the same undesired result.
I would appreciate any comments or suggestions.
Many thanks
Edited by: Javier Gil on Jul 20, 2010 7:52 AM

I have found a better method. In your IR query:
SELECT LPAD(v.vendor, 7, ' ') vendor,
/*Just LPAD to a length of the column defined in the database table or to 7, whichever is greater. */
FROM v, r
WHERE v.VENDOR = r.VENDOR
AND date_rcv <= to_date(:P150_CUTOFF,'yyyy/mm/dd')
AND inv_nbr = ' '
AND to_stores <> 'T'
AND (V.VENDOR = RPAD(:P150_VENDOR,10,' ') OR :P150_VENDOR = 'ALL')
When you download to Excel by Download/XLS (Request=XLS), it preserves the leading zeros.
In the case of dates, you should LPAD 10 minimum in this format.
LPAD(to_char(date_rcv,'MM/DD/YY'), 10, ' ') date_rcv,
I haven’t tried it yet but I think in the case of ‘MM/DD/YYYY’, you should LPAD 12 minimum in this format.
LPAD(to_char(date_rcv,'MM/DD/YYYY'), 12, ' ') date_rcv,
Drawbacks of this method:
Since the string has leading white spaces, you cannot use the filter for the ‘=’ comparison operator. Even filtering using leading white spaces will not return anything. You must use the LIKE and NOT LIKE operator instead.
Advantages of this method over the original one I posted yesterday:
1) You do not have to create another column for download, just one column will suffice.
2) Even though the query has leading white spaces, they will not display in the IR region.
Edited by: richardlee on Aug 5, 2010 11:10 AM
Edited by: richardlee on Aug 5, 2010 11:16 AM

IR truncating leading zeros in my popup window report

Hello,
I am using IR_columnname, for one of the columns in my report which is a popup window report.
My problem is that IR_column search filter in my popup window is truncating the leading zeros.
I am getting the value but it is truncating the leading zeros.
like say if the deptno is something like 020 or 0020 in the parent window.
the IR_columnname value is taking '20' (its truncating leading zeros) with this filter its not dispalying the result in my popup window.
can anyone help me out with this.
thanks.

How are you passing values to the IR filter? There could be a possibility that you source logic is truncating the leading zeros.
Thanks,
Manish

How do I add leading zero(s) to exported files' names?

I'm using Lightroom 1.4 on an iMac, with OS X 10.4. When I export a batch of photos, they get numbered automatically. For example, if they're pictures of my dog, I'll specify "Dog" as the name to be used and 1 as the starting number. Lightroom will then export them as "Dog-1.tif" and "Dog-2.tif" and so on.
The problem is that when I then load these files into another application, it thinks that "Dog -1.tif" should be followed by "Dog-11.tif," then "Dog-12.tif," and so on to "Dog-19.tif" and then "Dog-2.tif," "Dog-20.tif," "Dog-21.tif," etc.
One solution to this would be to have them numbered as 01, 02, 03. . . 09, 10, 11, etc. Rather than add those leading zeros to the file names manually, I'd like to have Lightroom put them in when it exports the files, but I can't figure out how to do that. I've tried entering 01 as the starting number in the "Export" dialogue box, but that doesn't do the trick.
Can anybody tell me how to get Lightroom to add a leading zero (or zeros, when I export more than 99 files at a time) to the file names?

>What if I just wanted to name the images 0001, 0002, 0003, etc? Can't seem to figure that out.
In the Filename Template Editor, simply insert the [Sequence # (0001)] token as the only entry in the template field.

Remove the leading Zero from the Query output in SAP BW ?

Hi
Experts,
Vendor Number loaded as (0000010076) from R/3 to SAP BW.
How to remove Prefix of Zero for the Vendor Number(0000010076) from Quey outpt.
Regards.
ASIT

Hi,
Please check out this thread.
Remove leading zeros
Also check if there is any conversion routine used for that particular infoobject.
If ALPHA conversion is selected for your infoobject then it will automatically take away the leading zeros at query level.
Regards,
AL
Edited by: AL1112 on Sep 16, 2011 9:15 AM

How can we put the leading zeros for the extract file.

hello experts..
Iam extracting values from one ztable in this for one filed length will be 2, for this field i need leading zero s at the time of extract... please help me....

Hi,
Declare the field as NUMC data type, automatically you will get the leading zeroes.
Regards,
Subramanian

How can I remove the leading zeros on jpg files?

I'm looking for a way to remove the leading zeros on over 1000 jpg files, without changing the remaining digits in the file name. Is there some automated "batch" script?
i.e going from 003405607.jpg to 3405607.jpg

You could write an AppleScript. but it will be easier to get and use a third-party file renaming utility. I use the freeware NameChanger which works quite well.
https://www.macupdate.com/app/mac/21516/namechanger
Regards.

How to delete leading zeros in sap script

Hi
In sapscript iam facing an issue with num4 field.
Iam using this field to display Serial.No
it is displaying '1' as 0001 i want to display here 1 with out leading zeros.
If there any solution let me know

Hi,
Try below code
data: w_vbeln type vbak-vbeln,
w_char(10).
w_vbeln = '000012345'.
write w_vbeln to w_char no-zero.
or
The function Module 'CONVERSION_EXIT_ALPHA_OUTPUT' is used to remove the leading zeros in a field.
the following is a sample code which i have used for 'Commitment item' in my report. replace the field with your required field.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
EXPORTING
INPUT = IT_FMIT1-RFIPEX
IMPORTING
OUTPUT = IT_FMIT1-RFIPEX.
Regards,
Chandru

Visual Studio Projects Not Showing FileVesion Leading Zeroes in File Properties

I created a simple Visual Studio 2013 windows form application setting the AssemblyInfo.cs file as show below.
// You can specify all the values or you can default the Build and Revision Numbers
// by using the '*' as shown below:
// [assembly: AssemblyVersion("1.0.*")]
[assembly: AssemblyVersion("1.0.0.0227")]
[assembly: AssemblyFileVersion("1.0.0.0227")]
[assembly: AssemblyInformationalVersion("0.0.0.0227")]
I built the application and went to the Windows File Explorer and brought up the file properties. What I see is that the product version showing the leading zeros, but the file version field does not show the leading zeros.
It appears to be a bug either with Visual Studio or with Windows. Which one is it and is there a fix?

Hi Sarah,
We can't see the screenshot. Do you mean you use Windows Explorer to browse to the AssemblyInfo.cs file and check the property?
If you change the product version or the file version from the AssemblyInfo.cs file, you need to firstly rebuild the assembly, then if you go to the debug/release folder, check the property of the assembly file, the Details tab will show you the corresponding
changes of these properties. It's the assembly property but not the cs file property.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

How to retain leading zeros in module pool screen

Hi experts,
I have a ztable field of type NUMC4 being displayed on a module pool screen, the value in the field is '0001', but on the screen it displays value as '1' (without leading zeros), When I save the record, Even in the databse it stores as '1'.
But I have checked in debugging the field always contains '0001' in the program execution and I have also used 'CONVERSION_EXIT_ALPHA_INPUT' in the PBO but no use.
Pls suggest.
Thanks,
Deepak

Check the screen attributes for the field. There is an option to show leading zeroes.
edit.
And how did you see it was stored a 1 and not 0001? Using SE16N? Mind you: with SE16N conversion-exits are executed automatically thus showing 0001 as 1.
To make sure: double click on the record in SE16N and look if it's still 1 and not 0001.

Leading zero no longer showing up for hour in clock.

I know this is a nitpick, but the leading zero for the hour no longer shows up in the menu bar clock no matter what the settings are. Also there is no option to display the date in numeric form.

Hello Ben:
I had not noticed that before, but I do see what you mean.
I have not played with it, but take a look at system preferences>date & time and then click on +"open language & text."+ Perhaps that might be a way to have the display change. As I said, I have not played with it since I am OK with the current display.
Barry

CRM 7.0 Leading zeros on material in sales documents delta replication

Hi
During initial load of sales documents from ECC to CRM the item is replicated with leading zeros.
The consequences is that CRM do not find the product and the crm order gets an error message that the product is not maintianed in product master.
So my question is; how to replicate the order without leading zeros for items?
BR
Johan

Hello Johan,
You need to check txn:OMSL in ERP and you need to make sure that settings are in sync with CRM customizing path settings.
SPRO>IMG>Cross-Applicaiton Component>SAP Product>Basic Settings-->Define O/P Format..
Especially you need to check for the lexicographical flag.
If this flag is set, then 0123 is different from 123.
Hope this helps!
Best Regards,
Shanthala Kudva.

BAPI_PO_CHANGE document number leading zero problem

Hi experts,
The following code clears the "Delivery Complete" flag on a list of Purchase Orders uploaded from a CSV file.
The PO number is 9 digits long, however, in EKPO table it is stored as 10 digits (prefixed with a zero). The BAPI does not recognise the document number unless it is prefixed with a zero in the CSV file (which adds extra work for the user to create custom format in Excel to add the leading zero).
What code is required for the BAPI to recognise the 9 digit number without the leading zero?   Perhaps the leading zero could be hard-coded into the program?
Any advice is much appreciated. Thanks for your time.
REPORT Z_MASS_REMOVE_FDI_DCI_BAPI.
*Check if file exists
DATA: rc TYPE sy-ucomm.
CALL FUNCTION 'WS_QUERY'
       EXPORTING
            query    = 'FE' "File Exist?
            filename = 'X:\STO.TXT'
       IMPORTING
           return   = rc.
IF rc EQ 0.
WRITE: / 'File does not exist'.
ENDIF.
TYPES: BEGIN OF ty_tab,
        DOCNO(10),
        ITEM(4),
       END OF ty_tab.
DATA : it_tab TYPE STANDARD TABLE OF ty_tab,
       wa_tab TYPE ty_tab.
START-OF-SELECTION.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename = 'X:\STO.TXT'
*     FILETYPE = 'ASC
      has_field_separator = 'X'
*     HEADER_LENGTH = 0
*     READ_BY_LINE = 'X'
*     IMPORTING
*     FILELENGTH =
*     HEADER =
      TABLES
      data_tab = it_tab
      EXCEPTIONS
      file_open_error = 1
      file_read_error = 2
      no_batch = 3
      gui_refuse_filetransfer = 4
      invalid_type = 5
      no_authority = 6
      unknown_error = 7
      bad_data_format = 8
      header_not_allowed = 9
      separator_not_allowed = 10
      header_too_long = 11
      unknown_dp_error = 12
      access_denied = 13
      dp_out_of_memory = 14
      disk_full = 15
      dp_timeout = 16
      OTHERS = 17.
END-OF-SELECTION.
LOOP AT it_tab INTO wa_tab.
WRITE:/ 'DOCUMENT: ',
wa_tab-DOCNO,
' ITEM: ',
wa_tab-ITEM.
WRITE: / '-----------------------------------------------------------------------'.
DATA: s_header TYPE bapimepoheader,
        s_headerx TYPE bapimepoheaderx,
        s_item TYPE bapimepoitem,
        s_itemx TYPE bapimepoitemx,
        i_return TYPE bapiret2 OCCURS 0 WITH HEADER LINE,
        i_extension TYPE bapiparex OCCURS 0 WITH HEADER LINE,
        s_bapimepoheader TYPE bapimepoheader,
        s_bapimepoheaderx TYPE bapimepoheaderx,
        s_bapimepoitem TYPE bapimepoitem occurs 0 with header line,
        s_bapimepoitemX TYPE bapimepoitemX occurs 0 with header line,
        wa_message TYPE c LENGTH 100.
s_bapimepoheaderx-po_number = wa_tab-DOCNO.
s_bapimepoheader-po_number = wa_tab-DOCNO.
s_bapimepoitemx-PO_ITEM = wa_tab-ITEM.
s_bapimepoitem-PO_ITEM = wa_tab-ITEM.
*Remove Delivery Complete Indicator (DCI)
s_bapimepoitemx-NO_MORE_GR = 'X'.
s_bapimepoitem-NO_MORE_GR = ' '.
append s_bapimepoitem.
clear s_bapimepoitem.
append s_bapimepoitemx.
clear s_bapimepoitemx.
CALL FUNCTION 'BAPI_PO_CHANGE'
    EXPORTING
      purchaseorder = wa_tab-DOCNO
    TABLES
      return        = i_return
      poitem        = s_bapimepoitem
      poitemx      = s_bapimepoitemx.
*Message types: S Success, E Error, W Warning, I Info, A Abort
*Supress all Warning Messages
DELETE i_return WHERE ( TYPE EQ 'W' ).
*Commit only if no errors have been returned
read table i_return with key type = 'E'.
if sy-subrc ne 0.
    COMMIT WORK AND WAIT.
endif.
*Display Return Messages on Screen
LOOP AT i_return.
    WRITE: /   'RETURN MESSAGE: ',
    'ID: ',
    i_return-id,
    ' TYPE: ',
    i_return-type,
    ' NUMBER: ',
    i_return-number,
    i_return-message.
ENDLOOP.
WRITE: / '-----------------------------------------------------------------------'.
refresh : s_bapimepoitem,s_bapimepoitemx.
ENDLOOP.

hi,
Use the conversion exit to make it as 10 digit char CONVERSION_EXIT_ALPHA_INPUT.

Leading Zero in 0CALMONTH

Similar Messages

Maybe you are looking for