EAN number missing leading zeroes

Hi,
I have configured two types of EAN/UPC numbers, one being 12 characters and one being 14. In our business, we have a situation where a material has a case UPC number 00099999123456 and a package UPC of 099999123456.
When these values are displayed on the material master I will see either
099999123456 or
00099999123456
but not both values with the correct number of leading zeroes.
Is there a way to have the correct value with the right number leading zeros when the EAN number is the same except for the leading zeroes?
The standard conversion routines i've looked at do not take into account there could be a different number of leading zeroes based on the EAN type assigned as the type is not a import parameter for CONVERSION_EXIT_EAN11_OUTPUT.
thanks!

Hi,
As per your query this is related to your configuration setting. Pls consult with SD/FI consultant and also consult with ABAPER. If configuration is ok then may be your have develop a programe and the programe may be wrong.
Anil

Similar Messages

Need formula to take text from one cell, add that to a serial number with leading zeros

I'm trying to create a spreasdheet cell that simplifies creating videotape Numbers from a job name in cell and appends a serial number with leading zeros, and that would survive an export to EXCEL.
The result would look like
A Column
Job Name
B ColumnTape #
Formula needed for B
ClientName-TapeType-
ClientName-TapeType-001
=
ClientName-TapeType-
ClientName-TapeType-002
=
I've tried using a custom cell format that had the text in front of the (Integer) drag and drop, with three integers and leading zeros.
That worked, but requires recreating the custom cell format for each client and tape type.
So, I've used the formula =A2& in order to play around with different things, but haven't hit on something that adjusts for increased numbers and retains the leading zeros.
I don't mind doing a starter for the first row and then adding +1 in the formulas for the rows below.
I've done that using the custom cell formats for the first B cell and then using =Bx+1 in the following cells. It works, but I'm hoping to find something simpler or that can be copied and pasted in multiple rows on one paste.
Thanks in advance.
Suggestions much appreciated!
Ted

Ted,
This expression in B will give you the pattern I believe you are looking for:
=A&RIGHT("00"&ROW()-1, 3)
Here's a screen shot...
Jerry

Missing leading zeros using debug

How we will find the particular record containing the missing leading zero and how we will add the missing leading zeroes using debug

Hi,
I would suggest to check out the psa. By sorting the data by different criteria you will see duplicates. Additionally you can filter the records based on different restrictions on each field and might be able to find the records containing or not containing fields with leading zeroes.....
But anyway, some manual work has to be done.
regards
Siggi

Need hel attendant console- missing leading zero

I have a customer wher we did an upgrade from 4.1(3) to CUCM 7.1(2), we installed the AC plugin from the CUCM, and the AC is working but now the cutomer complains that they can't dial back from the AC because they are missing the leading zeros from the incomming calling numbers, on the phone the numbers are displayed with the zeros, what can be doen to have the leading zeros on the AC
Thanks

Bradley,
I cannot comment on the implementation you have gone through but I can comment on your comments about CUEAC.
There is going to be a new release in June this year which will support directory integration directly to AD as well as the CUCM sync which is available today.
The GUI iteself is to undergo a redesign in version 10, the date on this release is not yet known.
Incremental search is something which is not on the roadmap but is something I will discuss with the Product Manager to see if it can be considered.

Re: Material number with leading zeros (40 char long)

Hello Experts,
I am working on SAP ME 6.1.4.15.
I am having a problem with the material number appearing in production order / planned order request document in MEINT and failing there since the material it is looking for is with leading zeros (for example 1291 appearing as 0000000000000000000000000000000000001291) - a total of 40 char long.
But this material exists in ME as 1291 only. Can any one throw any light on this as to what could be the reason and how to solve it?
Thanks
Srinivas

Dear Srinivas,
SAP Note 1799009 - 'Presence of leading zeros is inconsistent over IDOC thus SAP MEINT cannot handle all inbound IDOC consistently' should help to resolve the problem.
Regards,
Alex.

EBS check number with leading zeros

When we upload EBS, we are getting the check number in the record 16 (reference field). But unlike the check number posted in SAP, the check number in the BAI file has 2 leading zeros. Now since check number is coming in record 16, instead of record 88 we are not able to solve this problem through String configuration.
So, we thought of following solutions(Options):
1. Modify the check lot numbers to have two leading zeros plus associated changes like the form and so on.
2. Modify the check number in the incoming file u2013 strip the check number with two leading zeros with the use of customer enhancement. (After upload and before posting)
Can we solve the problem of leading zeros (before the check number) through any configuration steps instead of changing the SAP script form for check(Check lot) or going for customer enhancement.
Thanks
Ron

You are correct, since the check numbers are coming through only in the 16 records and not in the 88 records, you cannot use a search string to resolve the issue with leading zeros. Also, I do not know of any other configuration that can be used to reformat the reference values in the 16 records.
The 2 solutions you have listed are both valid options. Although with the first option (changing the check lots), you would need to make sure the business users approved of changing the check lots before going forward with that option. And you would still have to manually clear checks that had been issued prior to the check lot change.
At my company, we went with the second option - using ABAP code to update the check numbers from the file to match those in SAP (we actually had to add leading zeros to the check numbers). In our case, we had already created a pre-processor program for other re-formatting of the file that was needed prior to loading it into SAP - so we added the check number logic to that.
However, if you do not have a pre-processor program, I know there is a user exit available for EBS - exit EXIT_RFEBBU10_001, include ZXF01U01. I have heard of others using this exit to update the check numbers from 16 records. The exit is called during the FF.5 processing.
Regards,
Shannon

How can I format a number with leading zeros?

I need to convert an int to occupy exactly 3 positions in a StringBuffer... I need the space in the StringBuffer to be filled with leading zeros where appropriate. Can anyone show me how to do this correctly please ?
At the moment I am using a pretty dumb workaround to fill the target with "000" first and then parse the int into either 1 2 or 3 positions depending on its value ... it works, but there must be a more correct way to do this ...
Thanks in advance ...

Have you had a look at the class java.text.DecimalFormat? It does exactly what you want... example:
StringBuffer sb = new StringBuffer();
DecimalFormat format = new DecimalFormat("000");
format.format(2, sb, new FieldPosition(0));
System.out.println(sb);
prints out the string 002.

Decimal(19,2) column data missing leading zero when value 1.0 through OLEDB

My column is defined as type decimal(19,2). When I select data through OLEDB(C++), I got .12 if the value is 0.12. The leading 0 is always missing. How do I define a right format of this kind of column? Here is my code fragment.
// Construct the binding array element for each column
for( iCol = 0; iCol < cColumns; iCol++ )
// Bind this column as DBTYPE_WSTR, which tells the provider to
// copy a Unicode string representation of the data into our buffer,
// converting from the native type if necessary
rgBindings[iCol].wType = DBTYPE_STR;

why do you need to do this? 0.12 and .12 represents same value so if your concern is more in terms of displaying value then you can use format functions in front end to display it.
there's no need of changing base datatype to string just for this need IMHO
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs
It may be convinient for front-end to just display anything from a db query.

Auto increment number with leading zeros

hello,
i have data column (serial number) that auto generate from script component, i'm using counter +1 and it successful store the number to my db. but the problem is there any idea to store the number to 00001 rather that 1.
im using this method in my script component
dim counter as integer = 0
counter =counter + 1
row.NoSerial = counter
TQ

Why should you send it through the file? WHy not simply create a calculated column based on identity field or sequence based field (if 2012 version and above) in the destination table and ignore it from the file altogether. ANyways its going to be
a sequential auotogenerated value isnt it?
http://www.sqlteam.com/article/custom-auto-generated-sequences-with-sql-server
If you want to bring it as 00001 etc you need to make it as varchar and use derived column expressions in SSIS as source is text file.
I would prefer doing this in sqlserver if its just a sequential number and has no direct relationship to the incoming file data fields.
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Leading Zeros in SU Number

We are using SU Managment
How do we get rid of leading zeros in SU# number range. System is storing pallet ID # with leading zeros in the LEIN table. This is causing issues while we retrive SU data from the tables, systems ask to enter the SU# number with leading zeros.
My Pallet Tag is printed with out leading zeros SU # 1234567890 and when the user tries to put away using LM02 system does not read the pallet ID. It looking for 00000000001234567890.
Even on desktop LS33 if I try to display a pallet with SU # 1234567890 system looks for SU Num. with leading zeros. Is there a way to get the leading zeros off from SU#
Appriciate your help

Please check in SPRO whether the conversion exit is maintained for Storage Unit Management. Follow the below path to do so.
SPRO -> Storage Unit Management - > Master Data - > Define Number Ranges. In the Pop Up choose "Conversion exit for storage unit number" .
Here you can define the "length of SU Numbers "
Regards,
Kumaran

Leading zeros in item strings

We've recently done a system upgrade to 11.5.10.2. One of the problems we've found since the upgrade is that the Segment 2 from the item description strings has lost its leading zeros. Our string is in the format xxx-0000-0-xxx with segment 1 being the family, 2 being an item number within the family, 3 being the item level, and 4 being a manufacturer id. We previously didn't have any problem with missing leading zeros.
What was previously ERT-0101-1-ABC is now showing as ERT-101-1-ABC. If this were purely for display purposes it wouldn't be too important, but it's affected some of our interfaces and reports. Even wiithin the standard inventory/mrp/order management screens, the item format changes depending on the individual form.
It looks as if different screens/functions treat items in different ways - sometimes treating the string as a whole, other times apparently working each segment separately and then displaying a concatenated, lead zero less string. In the System Item segments value set for segment 2, I can see that Right-justify and Zero-fill Numbers is switched on. Is it this option that's failing?
We've already implemented some fixes by padding the segment out as we produce the XML files we need for export, but before we get our support contractors to build fixes in all over the place I thought I should ask if there's a more singular fix for this.
I can see some rather old issues logged in Oracle Support, but not a recent one related to this upgrade and zeros going missing.
Any help gratefully received. :)

Yes, the format validation for it is number. I'm reasonably certain it always used to be number, though.
Should their be any detriment elsewhere if I had it changed to Char?
The field (in our test system) is protected against update - how can I remove the protection to test this?
Thanks for your help so far :)

Eliminating Leading Zeros for Input

Hello,
I am very new to the world of Netweaver Portals and Web Dynpro, so please have some patience.
I have created an application in Web Dynpro which will display the Stock Requirements for a Material. Everything is working fine with the exception that the User needs to enter 10 leading zeros before they enter the material number. Is this something that I can correct in Web Dynpro, or is there something I need to do on the R/3 side?
In R/3, the user can simply type in the 7 digit material number, but in my Web Dynpro App, they need to enter a 17 digit number (10 leading zeros and the 7 digit mat number).
I have checked other topics, but couldn't find where this exact issue has been addressed. Thanks for your help.
Paul

Paul,
one possible solution for this issue might be to write some code to add the missing zeros. For example you can put the coding in a action method.
Please take a look at the following snippet:
// get the material number from context (this is the number entered by the user)
String id = wdThis.wdGetWelcomeComponentController().wdGetContext().currentContextElement().getMaterialID();
if(id.length() < 17) {
for(int i = 0; i < 17 - id.length(); i++) {
id = "0" + id;
// your id is now a 17 digit number
I that helps you.
Sebastian

Leading zero check got activated in production .

Hi,
We had a DIMP ( Discrete Industries Mill Products) addtional installation to our existing landscape on last weekedn. we have a strange issue after that.
Most of the select queries based on material number,vendor,customer are failing. with further analysis it was observed that select queries are failing because of leading zero's missing .
we are surprised since the same queries worked perfectly fine before ( and it still runs perfectly fine in qulaity client) but now it is failing.
we know workaround to change all custome programs with conversion exit addtion to material,lifnr,kunnar ect.. but does anybody know if there is any business function which got activated to check leading zero's in select queries and this got activated along with DIMP.
let me know if you have any helpful inputs.
PS: i wnat to restore my original settings for leading zero so we dont need to change nay programs.

Hi Santosh,
some more analysis is required: For the failed selects, where do the missing-leading-zero kunnr/matnr/lifnr come from?
If from screen input, check the screens are active, check the input fields data type, active, conversion exit correct?
It may be a good idea to check the whole system for inactive objects.
If from other sources, check the complete way the data goes before use in SELECT WHERE clause.
If you have found one errors source, this will lead to more.
There are a couple of SAP notes on DIMP, at least the activation process of DIMP should be checked.
Regards,
Clemens

Leading zeros remove from FB05 for assignment field in process open items b

Dear expert
At present i am using the electronic bank statement completed OT83 & OT51configuration, when i am running FF-5 the EBS soft copy has been uploaded and created batch input session.
I executed batch input session and the transactions has been posting through FB05 for outgoing payment clearing with assignment field ( where check number is laying correctly and matching EBS soft copy cheque number and SAP outgoing clearing account line item assignment cheque number ) in case of outgoing clearing is happening correctly.
but where as i have a problem incoming clrg cheque number which is displaying in assignment field and updated when client using FF68(check deposit / collections).
the user is punching all collections from customers using t.code FF68 and cheque number is updated with 6 digit number in the variant. it is like a JV.
after posting batch input session the cheque is number displaying in assignment field. the cheque number is updated with 6 digit number. but in the variant cheque number width 6 digit only but after posting FF68 & SM35 the system automatically taking leading zeros for the remaining length. Cheque number standard length in SAP 13 in table .
total 13 digit length but user punched only 6 digit only, because the cheque number 6 digit numberonly. so the remaining 7 digits it is occupaying 0000000.
while executing FF_5 and SM35 (thr FB05) the assignment field cheque number (0000000586585) and soft copy cheque number 6 digit (586585) is not matching , because of that i am unable to clear the incoming collections or incoming payments clrg.
so how can i remove the leading zeros after cheque number ( actually displaying 0000000586585 , but i want without zeros only cheque number 586585) in assignment field in FB05 using FF-5 & SM35).
is there any enhancement or user exit to remove leading zeros or any other way of work around .
Regards

Hi Amareswar,
In your case, request your bank to provide cheque number with leading zeros in electronic bank statement as the leading zeros in the assignment field is SAP system behaviour.
Alternatively, use 'Define Search String for Electronic Bank Statement' (refer http://help.sap.com/erp2005_ehp_05/helpdata/EN/6d/0cdf4b142e11d3963800a0c9426c73/frameset.htm for details) in the IMG, customize it to search for the cheque number provided in the note to payee field > then append leading zeros.
The first method is the solution we are using and it is the most cost effective.
Hope the above helps.
Kind regards,
John Chin

Leading zeros in CSV file.

Hi Team,
I need to retain leading zeros in CSV file.
I could eliminate this problem in XLS file by using this tag in the RTF Template:
<fo:bidi-override direction="ltr" unicode-bidi="bidi-override"><?XML_ELEMENT?></fo:bidi-override>.
So, when i do an Export from Publisher for excel document its gives me correct values. i.e zeros are retained.
But when i select "CSV" and then hit Export , it gets saved in txt file and the txt file has the zeros.
but when i rename it to ".csv" and open it does not retain zeros.
Can you please let us know how can we achieve this.
Thanks for help!
Bhupendra Gupta

Hi Bhupendra,
If its a number the leading zeros will be eliminated in CS in the default CSV .can't do much on this.
But if use the delimiter e-text and get the output file, you can get the leading zeros as needed..
Follow this
http://winrichman.blogspot.com/2009/09/delimiter-based-e-text.html
http://winrichman.blogspot.com/search/label/BIP%20E-text

EAN number missing leading zeroes

Similar Messages

Maybe you are looking for